Domain catalogue Supply chain

Routings and work centres

Work centres, capacities and routings as governed master data consistent with the BOMs and the site calendars.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSnowflakelakehouseDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN ROUTINGS AND WORK CENTRESRoutings and work centresone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the routings and work centres record comes from, how it is assembled, and who reads it. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

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.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Work centrecode, site, category, capacity per shift, calendar, cost centre
wins: production engineering
Routingitem, site, group, usage, status, lot range
wins: production engineering
Operationssequence, work centre, setup and run times, control key
wins: production engineering
Validitychange numbers, valid dates
wins: PLM and workflow
How records match

The keys, in order

work centre code + siterouting group + item + site

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.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Capacitysite → area → work centre
Processrouting → 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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columnsetup and run times are non-negative
capacity per shift is positive
Rowan active routing has an active BOM for the same item and site
an operation's work centre is active at the routing's site
Businessplanned capacity by area equals the sum of its work centres
no released production order uses a routing with a closed work centre
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Production ordersSAP AFKO · AFVC; Oracle work orders
Confirmationsoperation confirmations
Capacity loadplanning
actual vs standard timescapacity utilisationroutings changed per month

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.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Production engineering edits; planners read; costing reads. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/routing/lookup
{
  "item": "M-2200417",
  "site": "1210"
}
response
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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

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.

illustrative scenario · Routings and work centres
Terms on this page

Work centreA machine, line or team where operations are performed.
RoutingThe ordered operations to make an item at a site.
Control keyFlags on an operation: scheduling, costing, confirmation behaviour.
Golden recordThe one record for a real routings, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Industrial manufacturing, High-tech and semiconductor, Life sciences. The industry pages show the domains each starts with.

See your first domain built on your data

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.