OCE.1:4 - Solution
Select the smallest organization-and-contribution focus that can orient the current change decision without dropping an obligation that could change it. Establish the product uses and contributions needed, then locate the organization and capability to create or change. Use A.1.SCR when an actual System claim needs recovery and A.1.CSD for affected-System discovery. Return the Work and capability questions, authority, participation questions and local result needed by downstream patterns.
Use an adequate existing strategy or organization-change brief as input. If it already establishes the contribution, organization, authority and consequence boundary needed here, reuse that content. If the direction remains disputed, seek the strategy decision or keep the focus conditional. Use its result wherever it settles or changes the organization question.
An ambiguous transformation request is enough to enter when the receiving decision lacks a clear organization or contribution. Before relying on the focus, obtain evidence for its claims about System identity, Work, contribution, assignment, authority, access, participation, capability and consequences.
OCE.1:4.1 - Pattern-Use Unfolding
- Name the receiving decision and first user. State who needs the focus, what decision it enables, the horizon, and what useful result permits a stop.
- Recover the intended outside contributions. Name the products or other results, receivers, uses, conditions and commitments that can change the decision. For creator work, follow §4.1.1 from product use to needed capability and local completion. Reuse a sufficient account. Seek a missing strategy or domain result when the focus depends on it.
- List materially different organization candidates. Consider a formal entity or unit, an organization spanning joint work, or one including providers when each is plausible. Use §0.2 to distinguish the arrangement where that matters and
A.1.SCRwhen System identity changes the decision. Keep actual organizations, proposed organizations and a return to a non-organization question distinct. - Recover changed Work and capability questions. Name the Work families, result or contribution relations, performer or coordination facts, and capability claims that could change. Do not infer them from a chart, proposed position, plan, or tool.
- Name other decision-relevant organization facts. Ask which holder assignments, authority relations, resource-access relations, information-use relations, material transfers, service provisions, coordination occurrences, and participation facts must be recovered next. If a source calls these an “interface”, select the boundary and direct relations before relying on it.
- Discover consequence-bearing Systems. Use
A.1.CSDfrom the organization, contribution, affected Work, horizon, and decision. Include employees, providers, customers, products, service Systems, neighboring organizations and other material Systems when supported. - Recover authority and specialist returns. Name the authority subject, decision scope, window, and basis. For any missing professional judgment or decision, state the question and identify the authority, practice or service that can answer it.
- Select, return, and reopen. State the organization and its status, contributions and obligations, included questions, affected-System scope, any exclusions or rejected candidates, the local completion condition and any further result needed. Name an observation that reopens the focus, such as a changed product use, commitment or authority.
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 product System being created, changed, sustained in use or retired, the extended enterprise organized for that undertaking, its participating organizations and agreements. Identify the agents entitled to establish or accept the objectives and commitments, the 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. For retirement, state the use that ends and the condition the assigned work must achieve. Each participant can have a bounded obligation; the present extended enterprise need not consist of the product’s original creators. 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, recover the agreements organizing the workshop and receiving organizations’ joint work. The changed part is the product SoI of that extended enterprise; 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.
OCE.1:4.2 - Record the Result
| Result position | Required content |
|---|---|
| use boundary | First user, receiving decision, horizon, and useful stop. |
| organization candidates | Candidate Systems or intended referents, supporting relations, any missing grounds, the selected organization and any material alternatives rejected. |
| intended contribution | Relevant product uses or other results, receivers, obligations, conditions, and unresolved value or performance questions; retain several where the decision depends on them. |
| changed Work and capability | Work families, current or intended status, supplied-result or contribution relations, and capability questions. |
| organization facts to recover | The particular questions still needed about assignment, authority, access, information use, transfer, service, coordination or participation. |
| affected Systems | A.1.CSD reference or bounded Systems, supported relations or modal paths, possible changed characteristics, gaps, and specialist returns. |
| authority | Subject, decision scope, window, basis, and evidence boundary; otherwise an authority blocker. |
| continuation | Local result, acceptance boundary and any remaining obligations, any further result needed and one observable reopen condition. |
OCE.1:4.3 - What Changes in Practice
The practitioner can explain which organization is being engineered, which product uses or other contributions justify its capability, and what its change project can finish. Downstream concepts answer to those contributions, Work and capability questions, affected Systems and actual authority. The focus remains bounded while retaining the products, providers and continuing obligations that can change the decision.