Transform: from schedule to product

What it is. Classic SCOR called this process Make; SCOR DS renamed it Transform, and the rename is doing real work. The process covers the scheduling and creation of products — transformation in the broad sense, from discrete manufacturing and process production to kitting, assembly, refurbishment, and the maintenance of the assets that do the transforming. A distribution business that never runs a machine still transforms: kitting is Transform, and so is the refurbishment leg of a returns operation. Scheduling sits inside the process, not upstream of it — deciding when and where to make something is Transform work, which is why a schedule nobody can execute is a Transform failure, not a planning footnote.

The questions it answers. Can the released schedule actually happen on demonstrated — not nameplate — capacity? When a line is over commitment, what spills, where, and at what cost? What is work-in-process hiding: how much cash sits between raw material and finished goods, and is it growing while output stays flat? Are the costs of transformation — labor, indirect, tooling — moving with volume, or drifting independently of it?

The metrics that matter.

Measure	SCOR DS	What it tells you
Schedule adherence	practice measure	Whether the plan the plant accepted is the plan the plant ran
Direct Labor Cost	CO.2.7	Sustained growth ahead of volume usually means overtime has become structural
Indirect Cost Related to Production	CO.2.8	The overhead that volume changes don’t automatically fix
Inventory Days of Supply — Work in Process (WIP)	AM.3.2	How long value sits mid-transformation; growing WIP at flat output is a flow problem
Transform Supply Chain Agility	AG.2.3	How much sustained schedule change the transform stage can take without breaking

The decisions that live here. A line is at 112% of demonstrated capacity for the week. Three levers exist — overtime, alternate routing, re-promising — and they have different costs, different risks, and different owners, which is precisely why the call tends to stall in email. The capacity-spillover caselet prices all three and lands on a blend, written back to the ERP and MES as revised orders and routings. The general rule stands regardless of tooling: capacity problems found at schedule release cost money; capacity problems found at the due date cost customers.

SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures.