EAM 202 · FOUNDATION
How are physical assets represented?
Use functional locations for place and system structure, equipment for individually managed assets, and BOMs, classes, documents, counters, and warranties for context.
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
Functional-location hierarchy
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →02Equipment identity and installation
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →03BOM, classification, documents, and counters
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →DESIGN DISCIPLINE
Do not confuse a capability with one process
The same capability can participate in several streams. Configure it only for approved scenarios.
See how this capability changes across valid integration models.