Review questions

Subject 1 Integrated Summary: Reading the Chain as a System

Reading a supply chain begins with the idea that the customer experiences the result of a system, not the result of one department. Even a simple desk-lamp order depends on sourcing, procurement, conversion and logistics decisions and on coordination among parties that may sit inside one organization or across several companies. Supply chain management is therefore broader than logistics management. Logistics remains essential because it deals with flows, storage and execution from origin to consumption and commonly includes transportation, warehousing, material handling, order fulfillment and inventory management. But logistics alone does not contain every sourcing, planning and conversion decision that shapes the final result.

To understand what is happening, trace four kinds of flow. Material or service moves through sourcing, conversion and delivery and can reverse direction in a return. Information moves both ways: forecast, order, confirmation, shipment status or exception decision. Cash moves between parties according to the transaction and often travels in the opposite direction to the main product flow. Returns move products or materials toward inspection, replacement or recovery. These flows interact. Weak demand information may cause an unsuitable purchase quantity, affecting material, inventory, cash and service. A delay visible at delivery is therefore not automatically a transportation-only problem. In the teaching example with forty late orders, twenty-six orders, or sixty-five percent, were not dispatched on time because a component was unavailable, while fourteen orders, or thirty-five percent, left on time and were delayed in transportation. This breakdown shows where to investigate; it does not establish root cause.

After tracing flows, map the network. In this course, “node” is a practical label for a meaningful location or party and “link” describes the relationship or movement between two nodes. A map can contain a chip supplier, lighting-unit plant, final assembly site, central warehouse, distributor and customer. The value is not the beauty of the diagram. It is the visibility of dependency: who relies on whom, what moves between them, and which decision may be affected if the link fails. Dependency can also be indirect. A company that buys from one direct supplier may in fact depend on a single sub-tier source for a critical component. Seeing that dependency does not give the company direct authority over the sub-tier supplier; it simply makes the exposure visible.

Add time and alternatives when the decision requires them. If component preparation takes two days, transportation three days and inspection one day, and the stages are sequential with no overlap and use the same time basis, the lead time for that path is six days. The number belongs to the defined path and assumptions, not to “the whole supply chain.” Before labeling a dependency high risk, examine how long existing coverage can sustain operations, whether a realistic alternative source exists, and how long switching or recovery would take. The number “one supplier” by itself does not determine risk severity.

Next move from the map to performance. SCOR distinguishes performance attributes from metrics. Attributes such as reliability, responsiveness, agility, cost and asset management frame what matters, while a metric turns a defined aspect into a number that can be monitored. If ninety-six of one hundred orders meet a defined delivery condition, the compliance rate is ninety-six percent. This does not establish that the entire customer experience was excellent, and it does not explain the other four orders. If inventory is 1,200 units at 15 monetary units each, the simplified amount tied in inventory is 18,000 monetary units. At 700 units it is 10,500, a difference of 7,500. We do not call the difference a final saving because a service effect or another cost may offset it.

That is why trade-off reasoning matters more than chasing one number. Suppose one policy delivers ninety-seven percent service with higher inventory and another delivers ninety-three percent with lower inventory, while the case requires a minimum service level of ninety-five percent. The second policy should not be selected merely because it releases inventory; as stated, it fails the condition. It can be modified or another option considered, then service, cost, cash, speed and reliability can be compared consistently. Higher inventory is not automatically better either. Judgment depends on the objective, condition, cost and risk.

Finally, use process thinking to locate the work. In the SCOR scope taught here, the top-level processes include Orchestrate, Plan, Order, Source, Transform, Fulfill and Return. This language helps place an activity or problem in a broader process and then select a suitable performance lens. Yet a process label does not establish cause. If sixty percent of late-order cases concentrate between order confirmation and preparation start, that is a reason to investigate the interface: define the timestamps consistently, inspect a sample to learn what was actually waiting, choose a before/after measure, and trial a limited change. Do not replace a system or increase inventory simply because the percentage looks large.

You can transfer this method to any supply chain: trace flows, map parties and dependencies, add time and alternatives, define clear measures, and then analyze performance trade-offs and interfaces. Keep asking: what does the evidence establish, and what remains an assumption? Used this way, a supply-chain map becomes a decision tool rather than a picture, and metrics become aids to understanding rather than goals disconnected from service and value.