Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order · Module 7 · Items and the Item Model
Why the item model is permanent
Lesson 62 of 188 · 2 min
You can add items forever. Restructuring how items are DEFINED is a different matter. That distinction is the whole lesson: adding is free, redefining is not. Item class determines which attributes exist, which are required, and who can maintain them. Moving forty thousand items between classes is a mass change with validation consequences on every one — every item revalidates against its new class, and every missing required attribute is a rejection. Forty thousand times. Item numbering is effectively permanent. A mixed-convention item master is a permanent irritation — in every report, every integration, and every conversation somebody has about a part for the next decade. And the master-versus-organization attribute decision. Set an attribute at master level and every organization shares it. Discovering later that one plant needs a different value means changing the attribute's control level, which is not a casual edit. Design the class hierarchy properly. Two days…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Items and the Item Model
- 1What we are building
- 2Why the item model is permanent
- 3The item object model
- 4Master versus organization attributes
- 5Designing the class hierarchy
- 6Item numbering
- 7Building item classes
- 8Item templates
- 9Creating items manually
- 10The attributes that matter most
- 11Assigning items to organizations
- 12Item statuses and lifecycle phases
- 13Importing items in bulk
- 14Data quality before migrationFree preview
- 15What breaks
- 16Lab briefing: the Halden item model
- 17Lab solution walkthrough