Supply Chain Networks: Parties, Nodes, Links and Flows

From a supplier list to a network map

Knowing supplier names is not enough to understand a supply chain. We need to see the network: parties involved in fulfilling demand, places where storage, transformation or delivery occurs, and links through which materials, services or information move. In this course we use “node” as a practical mapping label for a meaningful location or party and “link” for the relationship or movement between two nodes. This is a course mapping convention, not a quoted external standard.

In the fictional desk-lamp case, the map may begin with a chip supplier that supplies a lighting-unit plant, which supplies final assembly, then a central warehouse, then distributors or customers. Arrows do not imply that every flow moves in the same direction: order confirmation may return from the supplier, cash may move opposite the product, and returns may move back from the customer.

Direct and sub-tier dependencies

A company may buy directly from the lighting-unit plant while depending indirectly on the chip supplier that sells to that plant. If the only chip supplier stops, the direct supplier may be affected and then final assembly may be affected even though the company has no direct purchase contract with the chip supplier. Mapping therefore reveals dependencies that a direct-supplier list can hide.

Add time to the map

A map is a question tool, not decoration

A network map can help examine concentration risk, information delay, handling points, path length or inventory position. But the diagram alone does not prove that a node is “bad.” An extra warehouse may support service while adding inventory and cost. A single supplier may be reasonable in one context and unsuitable in another. The map makes trade-offs visible; judgment requires objectives and data.