Parts Overview
Parts OverviewParts are items that make up a product.
Historically, parts were physical items used in a product;
Parts may also be non-physical elements of a product, such as software licenses, warranties, and service agreements.
Parts are the most fundamental objects in ENOVIA.
All objects related to a part are defined and managed.
The integrity of the interconnections is maintained.
All related information is maintained throughout the life of the part.
View a typical part relationships in ENOVIA.
An Enterprise part is any part in ENOVIA with a Lexmark Part Name.
Enterprise parts may be created by Lexmark or non-Lexmark users.
They may be manufactured by Lexmark or other parties.
When a Lexmark Enterprise part is designated to be manufactured or supplied by a particular Company, a Manufacturer Equivalent Part (MEP) is created and associated with the Enterprise part.
MEPs may be Lexmark designs that are produced by the supplier Company or can be off-the-shelf components.
Part lifecycle, access, revisions, and change control are governed by one of two policies: Development or Production.
See Change Development Part to Production Part to change a part policy.
Must be in the Complete state to revise.
Are under development, not yet ready for large scale manufacturing.
Allow letter revisions (aka bubble levels) in the ranges of A-Z, AA-ZZ.
Allow numeric revisions in the range of 001 - 999 (once used, bubble levels are not allowed).
Latest revision in Complete state indicates current plan-of-record for the part.
Access defaults to all Lexmark users.
May be manufactured; changes require higher level of scrutiny.
Require an EC to promote out of Preliminary state and thus to get to Release.
Allow only numeric revisions in the range of 001 - 999.
Latest revision in Release state indicates current plan-of-record for part.
Access defaults to all Lexmark users.
Released parts are owned by Corporate (design owned by all of Lexmark, not just one project team or engineer).
To Release a new revision of an existing Release part, disposition codes must be assigned.
When Released, production parts are published to downstream applications such as SAP and Siebel.
Some Identities of production parts (Component and Made From) require a CAD Spec or part specification container to be attached, and for most part types, a file must be checked into the CAD Spec before Release.