OpenDevelopment

The activities associated with receiving the request to create a [[t:WO|Production or Work order required to schedule and execute the Make activities. Make-To-Order processes require a production order or work order linked specifically to an order in the Deliver process (generally the Customer Order).

This is a M2 process; Demand is not aggregated, each individual Order (Sales Order or STO) results in a unique Production Order. Planning and scheduling primarily focus on meeting dates promised to customers, secondarily optimizing throughput (capacity utilization) and efficiency.

Use Cases

• Production Orders for Configurable product
• Customer-Direct Orders (customer orders are translated directly into matching production orders)
• Production Orders for custom sub-assemblies
• Production Orders for Custom Assemblies

For Configure-to-Order, and PTO variations of the Make-To-Order process the originating order (SO or STO) details generally include the Bill of Materials required to make and/or package the product. Order-to-Cash Quote-to-Cash Make Cycle Time Manufacturing BOM Plan-to-Produce

Hierarchy

ID	Name	Level	x
M2	Make-to-Order	2	M2
M201	Create Order	3	M201

Metric(s)

ID	Name	Level	x
RS13	Make Cycle Time	2	RS13

Term(s)

ID	Name	Clear	x
ATO	Assemble-to-Order		ATO
BOM	Bill of Materials		BOM
CTO	Configure-To-Order		CTO
M-BOM	Manufacturing BOM		M-BOM
O2C	Order-to-Cash		O2C
PTO	Package-to-Order		PTO
P2P	Plan-to-Produce		P2P
Q2C	Quote-to-Cash		Q2C
WO	Work Order		WO

Workflow

From Input(s)	Process	Output(s) To
wf_process wf_arrow D203 Sales Order	M201	wf_arrow wf_process Production Order M202

Note: Common inputs and outputs are listed in alphabetical order. Other inputs and outputs may be required to support varying use cases.Create Order Make-to-Order 320100 3 {{{keywords}}} {{{description}}}