OpenDevelopment

The activities associated with receiving, validating and entering Project Orders for Engineer-to-Order products and services. This may include capturing the customer intend, requirements, or design, creating product data, configuring the product and validating the existence and accuracy of customer data (sold-to, ship-to), pricing information, customer credit and product/item numbers. In many use cases this process is initiated by the receipt of a purchase order from the customer and the internally developed proposal.

Use Cases

• Large scale engineering projects
• Entering orders for custom product samples

Notes

Engineer-to-Order orders are typically called projects due to the complexity of such orders. Error-free Documentation Ratio Deliver Cycle Time Distribution Costs Order Management Cost Order-to-Cash Quote-to-Cash

Hierarchy

ID	Name	Level	x
D3	Deliver-To-Engineering-Order	2	D3
D303	Create Project Order	3	D303

Metric(s)

ID	Name	Level	x
DP15	Error-free Documentation Ratio	2	DP15
RS121	Entry-to-Processing Cycle Time	3	RS121
CO12	Distribution Costs	2	CO12
CO121	Order Management Cost	3	CO121

Term(s)

ID	Name	Clear	x
O2C	Order-to-Cash		O2C
Q2C	Quote-to-Cash		Q2C
SO	Sales Order		SO

Workflow

From Input(s)	Process	Output(s) To
	D303	wf_arrow wf_process Payment Terms D306

Note: Common inputs and outputs are listed in alphabetical order. Other inputs and outputs may be required to support varying use cases.Create Project Order Deliver-To-Engineering-Order 5430300 3 ETO, Engineer-to-Order, Order Management, Order Engineering, Order, Entry, Validation, Configuration, Validation, Supply Chain Receiving, validating and entering project orders for Engineer-to-Order products and services. This may include capturing the customer intend, requirements, or design, creating product data, configuring the product and validating the existence and accuracy of customer data (sold-to, ship-to), pricing information, customer credit and product/item numbers