Data quality before migration

The client's item data is worse than they think. Said bluntly rather than diplomatically, because the diplomatic version does not get acted on. This is true on essentially every manufacturing implementation, and it is better to say it in week two than to discover it in test cycle two. The common defects. Duplicate parts under different numbers. Obsolete items nobody has flagged — often twenty to forty per cent of the master. That is not a typo: up to two items in five. Missing or wrong units of measure. Descriptions that are free text with no convention. Attributes held in spreadsheets outside the legacy system — which means the extract is not the data, and nobody will mention this until you ask. And parts referenced on BOMs that do not exist in the item master. The assessment to run, in week two: counts by type, duplicate detection on description similarity,…

In this module: Module 7 · Items and the Item Model

1. 1What we are building
2. 2Why the item model is permanent
3. 3The item object model
4. 4Master versus organization attributes
5. 5Designing the class hierarchy
6. 6Item numbering
7. 7Building item classes
8. 8Item templates
9. 9Creating items manually
10. 10The attributes that matter most
11. 11Assigning items to organizations
12. 12Item statuses and lifecycle phases
13. 13Importing items in bulk
14. 14Data quality before migrationFree preview
15. 15What breaks
16. 16Lab briefing: the Halden item model
17. 17Lab solution walkthrough