CODP
Difference between revisions of "CODP"
| Line 20: | Line 20: | ||
|- | |- | ||
| class="blanco top" | | | class="blanco top" | | ||
| − | === [[t: | + | === [[t:VMI|VMI]] ([[t:MTS|MTS]]) === |
[[t:VMI]] | [[t:VMI]] | ||
| Line 62: | Line 62: | ||
|- | |- | ||
| class="blanco top" | | | class="blanco top" | | ||
| − | === [[t: | + | === [[t:PTO|PTO]] ([[t:MTO|MTO]]) === |
[[t:PTO]] | [[t:PTO]] | ||
| class="blue top dotmeright" | | | class="blue top dotmeright" | | ||
| Line 82: | Line 82: | ||
|- | |- | ||
| class="blanco top" | | | class="blanco top" | | ||
| − | === [[t: | + | === [[t:ATO|ATO]] ([[t:MTO|MTO]]) === |
[[t:ATO]] | [[t:ATO]] | ||
| class="blue top dotmeright" | | | class="blue top dotmeright" | | ||
| Line 102: | Line 102: | ||
|- | |- | ||
| class="blanco top" rowspan=2 | | | class="blanco top" rowspan=2 | | ||
| − | === [[t: | + | === [[t:CTO|CTO]] ([[t:MTO|MTO]]) === |
[[t:CTO]] | [[t:CTO]] | ||
| class="blue top dotmeright" | | | class="blue top dotmeright" | | ||
| Line 150: | Line 150: | ||
{{#css: | {{#css: | ||
h1.subtitle {display:none;} | h1.subtitle {display:none;} | ||
| − | table td a, table td a:hover {color: white;} | + | table td a, table td a:hover!important {color: white;} |
table td.blanco a, table td.blanco a:hover {color: black;} | table td.blanco a, table td.blanco a:hover {color: black;} | ||
table td.green {background-color: #7AB800; text-align: center; color: white; } | table td.green {background-color: #7AB800; text-align: center; color: white; } | ||
Revision as of 03:54, 10 July 2017
Customer Order Decoupling Point is a Term describing the process or node in the supply chain network where the activities are no longer driven by individual orders. Managing Customer Order Decoupling Points is a Best Practice.
Understanding the Customer Order Decoupling Point of a supply chain is important for Supply Chain Management processes. The behavior of processes upstream and downstram of the Customer Order Decoupling Point is quite different:
- Upstream processes are driven by forecast based planning information, Materials are pushed downstream. Optimization is realized by balancing inventory and capacity.
- Downstream processes are driven by actual customer orders. Materials are pulled by the order. Optimization is realized by balancing capacity and lead-times.
The OpenReference Supply Chain Operations Domain recognizes these differences in behavior at level-2: Make-to-Stock (MTS), Make-to-Order (MTO, CTO, ATO, PTO), and Engineer-to-Order (ETO). Customer Order Decoupling Points typically resides in the first MTS process (when looking upstream):
Contents
Strategy |
Supplier | Receive, Store | Pre-build/ Produce | Assemble/ Finish | Package, Store | Pick, Load, Ship | Invoice | Customer |
VMI (MTS) |
D* |
S1 |
M1 |
M1 |
M1 |
D1 |
D1 |
S* |
MTS |
D* |
S1 |
M1 |
M1 |
M1 |
D1 |
D1 |
S* |
PTO (MTO) |
D* |
S1 |
M1 |
M1 |
M2 |
D2 |
D2 |
S* |
ATO (MTO) |
D* |
S1 |
M1 |
M2 |
M2 |
D2 |
D2 |
S* |
CTO (MTO) |
D* |
S1 |
M2 |
M2 |
M2 |
D2 |
D2 |
S* |
D* |
S2 | |||||||
| Supplier | Source | Make | Deliver | Customer | ||||
For Engineer-to-Order replace Customer Order with Customer Intent.
Use Cases
Community Importance Rating: