Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:25:10 UTC

OCE.1:4.1.1 - Derive the organization-change focus from product use

Start with what should become possible or remain possible when the product is used. Name the system being created, maintained or changed, its users and relevant surrounding conditions. In a service, identify the system whose condition the service changes or preserves. Recover the obligations that depend on this use: a promised delivery, acceptable result, response interval or continuing availability. The user, beneficiary, buyer, payer and investor can be different parties. Funding makes work possible; usefulness and fitness for use need their own grounds.

Then work back to what the creator must be able to supply and which organizational change could obtain that ability. The reason for a workshop can be repeatable production of a surface suitable for a customer’s assembly under an agreed order flow. For this machining service, the changed part in use is the system-of-interest (SoI); the workshop is the creator. The workshop needs the relevant technique, people, measurement, material and equipment together. Purchasing a machine closes a supply contribution; it leaves workshop capability open if the machinist, measurement or material access is missing. If the planned product or means proves infeasible, reconsider the affected choice. Another means may provide the same required capability.

Keep the product and the organization in view together. In creating or changing an organization as creator, retain the product-side SoI as the common reference for the work. Name the organization as the creator being engineered, or system-in-hand. For its design, consider its use, functions, arrangement, characteristics, limits, means of realization and its own creators. These engineering questions do not require renaming it SoI. Its project can have a separate budget, contract and acceptance. Outsourcing the same reorganization, opening a new contract or calling the contractor a producer of enterprises leaves this product basis unchanged.

Retain several uses when the decision is shared. For a common laboratory, recover the test regimes, result requirements, timing and obligations of the product lines that use it. Keep differences that alter capacity, equipment, competence or priority. Group common demands, then examine their joint use of scarce means. Neither a single convenient product nor an undifferentiated name such as “pump products” is sufficient when the differences change the design. The focus need not cover unrelated product work. OCE.3:5.4 shows how two uses alter a shared laboratory decision.

Distinguish a supplier’s product from the same creator work under a new contract. A machine-tool maker can have the tool as its SoI while the receiving factory uses it as a creator. An engine maker can supply an engine for a stated aircraft application or class of applications while an aircraft maker treats it as a subsystem. Recover the supplier’s substantive obligation for a usable supply, the receiving use, actual decision boundaries and acceptance. A customer may specify the design and use concept; owning the whole product strategy is not a prerequisite. Use the supplier’s actual obligation and the receiving use to judge the SoI within the agreed scope. Moving the factory’s existing organization-change work to a consultant leaves it work on the aircraft’s creator. Renaming that work or its payment does not create the supplier case.

A firm can itself be bought, sold or valued, and its assets can have value separately from continued production. Keep that economic object and decision available. In engineering the operating organization, justify its capability through the products or classes of future use it is to support. A price or transaction does not replace this basis. A real change of product direction requires its own decision and revised grounds.

Make local completion finite. Identify the capability or other contribution this project must deliver, who may accept it, the conditions to demonstrate and the obligations that continue afterwards. For a claim that the capability has been realized, use applicable evidence or qualify it through OCE.9. Acceptance can occur before future product operation when the agreed evidence supports the local claim. Preserve assumptions about future use, accepted risks and who will decide when new evidence arrives; the contractor’s responsibility stays within its agreed scope.

When intended use is uncertain, retain specific possibilities and the inquiry needed to distinguish them. A bounded research project can finish with a warranted answer or a reason to stop expenditure. Independent research retains its own knowledge question and subject standards; research for a capability decision additionally establishes what that answer warrants for the decision. A research result is not realized organization capability. Noncommercial contributions, preservation of an existing service and preparation for future use can justify work without an immediate sale or an invented finished product.