EBOMs

EBOM Overview

An EBOM (Engineering Bill of Materials) is not an object in ENOVIA, it is a set of special relationships between parts.

An EBOM is centered on an assembly part, a part with an ENOVIA Identity of Assembly.

An Assembly (parent) is a collection of parts (children) whose movement is at least partially (if not fully) constrained relative to each other in absence of any packaging.

Additional Assembly parts may be included in the EBOM with their associated Assemblies and/or Components.

Components are end parts in the EBOM hierarchy as they are single, manufactured parts that do not contain additional parts in order to make them whole or useful.

A Component does not have an EBOM, but it could if a physical assembly needs to be treated as a single part in ENOVIA.

EBOM Creation

EBOMs are made by adding sub-assemblies and/or components to an Assembly part.

See Create/Add EBOM Components to an Assembly.
EBOMs may also be imported to an Assembly. See Import a BOM.

EBOM Rules

Rule	Description
Assembly/Component Lifecycle Promotion	An Assembly cannot be promoted further in its Lifecycle than the earliest state of any of its child Assemblies or Components. For example, a parent Assembly cannot be in the Review state or beyond if any of its children are still in the Preliminary state.
Part Access	Access is granted on each individual part. If necessary, it is possible to give someone (using the Access page) the ability to view an Assembly but not its Components. For example, a supplier may need to access the fuser assembly of a printer EBOM, but they may not see any of the fuser components.
Mixing Development/Production Part Policies	Similar to the Assembly/Component Lifecycle promotion rule, an assembly in the Production Part policy cannot be Released if it contains components that are still in the Development Part policy.

EBOM Updates and Revision Rolling

Assemblies automatically update their component and/or sub-assembly parts to the latest revisions.

Revision rolling on components saves time and effort, because EBOMs automatically update to the new component revisions in Complete or Release states.

Revision rolling:

The plan of record is when the part is in the Complete or Release state.
When a new revision of a part is promoted to the Complete or Release state, its top-level assemblies automatically pick up the new part revision.