Work centres, capacities and routings as governed master data consistent with the BOMs and the site calendars.
Today routings are copied between plants and drift; a work centre closed last year still carries capacity in the planning run.
With Lima the routings are read where they live, matched on work centre code + site and routing group + item + site, assembled field by field and published as one golden record per real routings, with every source key underneath. The orders and confirmations on a work centre, and the routings that use it are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Operations name golden work centres, and the rules keep times and capacities inside the site's calendar.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Capacity | site → area → work centre |
| Process | routing → operation |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | setup and run times are non-negative capacity per shift is positive |
| Row | an active routing has an active BOM for the same item and site an operation's work centre is active at the routing's site |
| Business | planned capacity by area equals the sum of its work centres no released production order uses a routing with a closed work centre |
| Transactions in the bed | Read from |
|---|---|
| Production orders | SAP AFKO · AFVC; Oracle work orders |
| Confirmations | operation confirmations |
| Capacity load | planning |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the orders and confirmations on a work centre, and the routings that use it.
Production engineering edits; planners read; costing reads. The twelve layers apply on every door; see security.
POST /api/v1/golden/routing/lookup
{
"item": "M-2200417",
"site": "1210"
}200 OK
{
"routing": "RTG-50012",
"operations": 9,
"work_centres": 5,
"standard_time_min": 184,
"status": "released"
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Work centre read from CRHD · CRTX · KAKO.
Open the SAP S/4HANA page →Work centres and resources read from WIS_WORK_CENTERS_B · WIS_RESOURCES_B (REST: workCenters · resources).
Open the Oracle Fusion Cloud page →Work centre read from CONFORMED.WORK_CENTRE.
Open the Snowflake page →Work centre read from silver.work_centre.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
An industrial manufacturer with seven plants compared routing times with confirmations and found 14% of standard times more than 30% off. The rule now flags drift monthly; costing and capacity planning improved together.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Industrial manufacturing, High-tech and semiconductor, Life sciences. The industry pages show the domains each starts with.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.