In MCAD (e.g. NX, Solid Edge)
Articles appear once per structure level with a quantity specification
Example: Switch X is installed 5× → one entry, number 5
In ECAD (e.g. EPLAN®)
Item listing: each shoring individually with its own ComponentLocation
Structure is only created by filtering, e.g. according to function ("open door") or installation location
An article with 5 shoring → 5 entries, clearly about location and function
Result: Both systems depict reality correctly - but from completely different perspectives.
| Range | MCAD | ECAD | Structure | Physical tree structure | Article list with filter structure | Multiple shoring | An entry with quantity | Multiple entries (per location/function) | Identification of individual parts | Only logical via structure | Directly via ComponentLocation | Point of view | Geometric, mechanical | Functional, electrotechnical |
Workshops & department alignment
We synchronize MCAD and ECAD teams: understanding of the respective perspectives, conceptual worlds, structural logic.
Mapping the parts list logic
Comparison of article understanding, structural concepts and parts list models
Interfaces with semantic depth
We do not develop simple data transfer, but a "structurally intelligent" integration between ECAD and MCAD - for clean PLM data.
PLM integration with structural transformation
Merging in Siemens Teamcenter: Components with position, quantity and location - traceable, consistent, process-capable.
Clear and consistent parts lists
Comprehensible allocation of shoring locations and functions
Better coordination between ECAD & MCAD - fewer queries
Future-proof PLM database for development, purchasing, documentation & service
Clear component identification, even in replacement cases
ECAD: EPLAN® (focused and deeply integrated)
MCAD: Siemens NX, Solid Edge
PLM target system: Siemens Teamcenter / Teamcenter X
DE 
EN