OPS.Reference:1.1 - Derive operating objects and units from the result
The starting object is a result somebody can use or a condition that must continue. A recipient may need a repaired device, a warranted answer to an investigated question, an available incident service or a specified amount of material. These results require different completion and observation rules. A physical item can continue through several transformations; a service can change the recipient’s system; an investigation can change what is known while leaving the eventual product undecided. An operation’s output is therefore identified through its receiving use before a convenient count is chosen.
Work becomes necessary through a difference between that required result and the current situation. Recover the actions that could close the difference from the relevant professional methods and from what competent performers actually do. Work backward to the inputs, intermediate results and conditions each action needs, then forward to check that their combination obtains the receiving result. This is how preparation, production, inspection, correction, transport and support enter the operating account when the result needs them. Examine repeated steps for a contribution that can be omitted without losing the receiving result or a required condition. An unexplained label such as “resolve the problem” leaves a method question open; assigning a duration to it supplies no way to resolve the problem.
Choose working units at the boundaries where a meaningful contribution can become ready, be assigned, be interrupted or completed, and be used by another action. Those boundaries need not coincide. A customer’s order can require several components; a machine batch can contain components for several orders; a diagnostic attempt can produce useful evidence without completing the case. The case remains the continuing matter, the attempt is one performance, and the evidence is its result. Combining them under one count loses the relation needed to decide what to do next. OPS.1 and OPS.3 establish the identities; OPS.11.1 constructs the corresponding work and completion relations.
The unit can itself need design. Split a large commitment where a smaller result would be usable, or where a separately ready contribution can be performed without defeating the whole. Keep together contributions that must be obtained or accepted together. Compare the saved waiting with added preparation, coordination, checking and unfinished inventory. In exploratory work, a worthwhile unit can be one interpretable test of a consequential hypothesis; the scientific or engineering method supplies the test and its interpretation, while Operations arranges its performance and use. A time allowance can bound the expenditure without promising that a question will be solved within it.
A resource is relevant through what it can contribute to this work under the required conditions. A qualified person’s hour, an available machine interval, information access and a consumable supply impose different constraints. A machine can remain occupied while its operator is free for other work. A person assigned to two departments remains one person. Recover usable capacity through capability, configuration, access and time, and retain the shared identity across the accounts that consume it. An aggregate headcount or equipment count can serve a broad comparison only while it preserves these consequential distinctions.