Dassault Systèmes S.A. is a French company and a world leader in the production of 3D design software, 3D digital mock-up and product lifecycle management (PLM) solutions.
$15
per month
SAP PLM
Score 8.6 out of 10
N/A
SAP PLM is one component of the SAP Business Suite which also includes ERP, CRM, SCM, etc.
Very well suited for direct integration with CAD packages (Solidworks/ Auto desk Inventor or AutoCAD) and version control of CAD Model/Assemblies and Drawing files) and creating parts and document objects directly into Enovia and controlling their lifecycle from CAD Interface. Similarly, Enovia's Engineering central is already equipped with Industry standard ECR/ECO process which needs little customization for implementing Engineering Change management process. The hardest part in Enovia is controlling the disposition of released material for the downstream process in other ERP systems. For example, if a released material has gone for production or purchasing in ERP system/MRP system then dispositioning that material with Major revision (which may need manufacturing to stop the production due to faulty design) have no direct control to stop the downstream activities. Most cases its manual process to communicate with ERP team to for taking action. Similarly, revision of Documents (material Spec for example) linked to thousands of parts required special process (some time needs to schedule in the weekend).
SAP PLM is well suited for any industry that needs to track the creation of a product from the raw material stage all the way to the shipped product. I do not think it would be well suited for very small companies which do not have any materials, products, and inventory to track.
Every revision of a part or document is a separate object, hence unlike SAP status control of an object is easy. The lifecycle of each object can be controlled by its own policy.
It is easy to create new types of objects rather than pre-defined object types and control them by their own customized policy.
Efficient Security and access control model for design and supporting documents file checkout and check-in and easy reporting mechanisms for tracking business activity, like how many parts being created/revised/obsoleted and who has checked out how many times etc.
When a part/assembly has been released in Enovia and gone for production or downstream processing, Enovia doesn't have much control, hence, Enovia should come up with an easy controlling mechanism for various disposition of parts and seamless communication with an ERP or downstream process.
If a document is linked to thousands of materials then revising this document takes long time gets floated to the BOMs where the previous document versions are used. So, Enovia should have an efficient way to replace the floating process or another efficient mechanism for document revision processing.
When evaluating Enovia as a PLM product the following Enovia stacks came out as a positive feature compared to other PLMs available on the market. 1. User-friendly interface 2. Easy to Integrate with CAD systems for the manufacturing Industry 3. It is quite easy to implement the Interface with ERP/MRP system (like SAP, Oracle manufacturing) 4. Availability of 3rd party ENOVIA -SAP interface and easy to plug in between two systems
SAP PLM encompasses SAP BW and SAP PRD. We tend to focus more on the SAP PRD portion as it directly involves more closely to production. We selected SAP PLM because it gives us a great visibility in the life cycle of materials, products and overall costs. SAP PLM compliments the other packages very well
Easy learning curve for the users- Very user-friendly Interface for Engineering central make the users happy and easy to learn the BOM creation and Engineering change management process.
Time-saving - Seamless Creation and revision process of objects saves a huge amount of time compared to other systems.
Easy to copy existing business data and modify them as required.
Accurately able to order raw materials which are necessary for the current production run, thus reducing overhead.
The negative impact would be the initial cost of the software and how long it would take to ROI that cost.
It has allowed us to control batches of product creation much more closer and have the ability to cut some erroneous costs which were found in large batches.
