or strategic expectations in future time periods to ensure that the operational capability supports the strategy. But how does this reconciliation actually occur in a true bidirectional fashion?
Between the strategic and operational ranges is the tactical range. As we will see in Chapters 3 and 5, this tactical range is unique, and for it to perform the necessary reconciliation it must become a bidirectional reconciliation hub for the key characteristics of a CAS.
A flow-based operating model is an operating model specifically designed on the fundamental principle of flow. Chapter 1 firmly established two things:
Promoting and protecting flow is the key to increased return on investment. This is the very essence of Plossl’s Law.
Flow can be a unifying factor, not just in operations but also between functions, to advance their individual primary objectives.
A flow-based operating model makes the following critical assumptions:
Assets must be as closely synchronized to actual demand as possible. The cost of being wrong has grown dramatically with the rise of complexity and volatility. Synchronizing assets as close as possible to actual demand minimizes that risk.
Variability cannot be eliminated but its impact on system flow can be effectively controlled and mitigated with the right operating model design. Every process, even when under statistical control, still experiences variability within its control limits; that is a given. The accumulation of this variability between processes is really the only relevant thing when it comes to managing system performance.
Focusing on precisely synchronized planning and scheduling across all materials and resources is largely wasted effort. Most MRP and shop-floor schedules are unrealistic as soon as they are released. Constantly rescheduling to attempt to account for variation actually introduces additional variability and subsequent confusion.
Some level of inventory is required at some stage in the supply chain because the customer tolerance time is insufficient to procure and make everything to order. Inventory cannot be entirely eliminated. At the same time, inventory should not be everywhere. The choice of where to place inventory is highly strategic since it determines the customer lead time and the level of working capital.
Batching decisions should be based on flow considerations instead of cost considerations. Batches are an actual bona fide limitation for most companies. How those batch sizes are determined, however, is a choice. Unfortunately, the vast majority of batching decisions are driven by cost performance metrics instead of flow-based determinants.
Some level of protective capacity must exist in any environment with multiple interacting resources. Resources have disparate levels of capacity relative to their respective required tasks and volume. The perfectly balanced line is still a mythical creature with an enormous price tag. This disparity means that precaution must be taken against misusing or wasting points of additional capacity.
Inventory is an asset and should be treated as any other asset on the balance sheet. Some lean enthusiasts like to promote that inventory is a liability; however, whether inventory is an asset or a liability depends on the position and quantity of that inventory. Production assets such as machines are added only when there is a positive return on investment. Inventory targets must be the result of a strategic choice for return on investment as well.
Capability must be established based on the expected future for the company. Since it is not possible to predict the future precisely, the capability range is established by the combination of inventory placement and protective capacity. The size of this range is dependent on the uncertainty of the future. The establishment of this range is dependent on a comprehensive risk assessment of the market and supply chain.
The objective of the operating model is to maximize margin by focusing on increasing service levels, enable premium pricing by providing a unique competitive market position, leverage constrained resources, and identify available capacity that can be used for incremental margin positive opportunities. This is in contrast to the more common expectation that the operating model should be developed to minimize unit cost and inventory while maximizing efficiency and utilization.
Thus, the question becomes: is there a well-defined and proven flow-based operational model that can scale to the multi-echelon enterprise level? Chapter 4 will focus on that model—the Demand Driven Operating Model.
If flow of relevant information, material, and services becomes the common focus for decision making in day to day operations and throughout the organization, then we need an appropriate suite of metrics for each of the relevant time ranges to support that focus. Appropriate metrics will allow us to maintain organizational coherence to that ROI objective now and in the future. Flow-based metrics should neither be a source of variability nor exacerbate variability.
Force fitting or failing to remove non-flow-based metrics in the deployed metrics suite will directly lead to conflicts and distortions throughout the organization—it will obscure what is relevant! Obscuring what is relevant directly leads to more variability, which in turn directly inhibits the flow of relevant information, materials, and services. Worse yet, when we do this, we are doing it to ourselves; it is self-imposed variation that directly hurts our ROI performance and causes great stress to the organization’s personnel.
Any suite of flow-based metrics must consider three additional prerequisites:
The metrics must fit the appropriate range.
The metrics must be reconcilable between ranges.
The metrics must fit the flow-based operating model.
These four prerequisites for relevant information define what it means to think, communicate, and behave systemically—the only way to protect and promote flow. If an organization and its personnel do not have this thoughtware installed, then the flow of relevant information and
or strategic expectations in future time periods to ensure that the operational capability supports the strategy. But how does this reconciliation actually occur in a true bidirectional fashion?
