SYSE.24 - Choose How the Project Will Obtain a Needed Engineering Result

SYSE.24:0 - Use This When

Use this pattern when a project needs one engineering result but someone has already assumed we will build it, we will buy it, a supplier will do it, or an AI agent can handle it. The assumed answer may be attractive, yet the other ways of obtaining the same result have not been described on a comparable basis.

Start by naming the result and its actual kind. It may be, for example, an engineered System, one usable System configuration, a reusable Method or MethodDescription, access to a capability, performed provider Work, or an engineering episteme. State who will use or rely on the result, what acceptance means for that use, and when the result must exist or the Work must occur.

The first useful result is a written comparison of at least two complete arrangements that would produce, perform, transfer, or make the same result available. One C.11 ChoiceResult then says: choose one arrangement or a retained tie-set now, reject the current set, perform one worthwhile probe, or reroute to another named question. Each arrangement says what result would exist or occur, which Agents would perform which Work, which Methods and Systems they would use, what relations would provide ownership or access, and what integration, configuration, assurance, support, capability, and exit conditions the project would accept.

An arrangement is complete enough for comparison when its omitted burden cannot reverse the choice. Purchase is a possible transfer or agreement inside an arrangement. An AI Agent is a possible performer inside an arrangement. Method development is an enabling branch unless the sought result is a Method or MethodDescription; in that case use A.15.6 to decide whether the Method is the project Method-of-interest for the current question. The short labels above identify parts or cues, while the comparison alternatives are whole arrangements.

Use SYSE.5 when the unresolved question is only how functions could be borne. Use SYSE.3 after an obtaining arrangement has been retained and the next difficulty is whether its realization branches can work. Use SYSE.8 when the project is designing an offering and the provider arrangement that will sustain another System’s use. Specialist decisions—for example, commercial, financial, legal, governance, organization, operations, asset, and capability-development decisions—remain with their specialist practices.

SYSE.24:0.1 - Precision Restoration

An Agent performs Work. Other participants—for example, tools, equipment, supplied Systems, materials, data, and the changed subject—retain their own relations. Name the decision-making person, team, organization, or other sufficiently agentic System and use the applicable FPF agency, assignment, and authority patterns when the decision relies on that Agent.

SYSE.24:1 - Problem Frame

Several recurring failures make this difficulty visible, often only after commitment. Internal development begins because building is prestigious or familiar. A polished supplier demonstration is accepted as if integration, configuration, assurance, migration, support, and exit were already included. Outsourcing is treated as removal of engineering responsibility. A continuing provider relation is compared with a one-time purchase price. An AI Agent is placed beside a department as a short label. Comparison becomes meaningful only after each label is expanded into an arrangement that names Work, Methods, means, assignments, integration, and acceptance.

The practical difficulty is not merely make versus buy. It is constructing several ways of obtaining the same result so that each way exposes the burdens and dependencies that can change the engineering choice. Until that happens, general decision theory receives a false OptionSet: its rows seek different results, use different acceptance conditions, and hide different Work.

SYSE.24:2 - Problem

An engineering result can be obtained through many arrangements. For example, a project may adapt a System it already has, acquire a ready product and integrate it, commission a custom result, obtain continuing provider Work or access, develop the result with its own Agents, or combine several contributions. The same visible result can depend on very different conditions, such as interfaces, provider capabilities, data custody, rights, configuration evidence, support, internal capability, and recovery arrangements.

Ordinary make-or-buy tables hide these differences. Documented recurring failures include placing a purchase price beside a fully burdened internal estimate, comparing an external demonstration with an internal production configuration, omitting integration or continued-access burdens, omitting assurance, and treating contract award as if the System, access, Work, or episteme had already been accepted and used.

The opposite failure is an exhaustive procurement programme before the engineering question is clear. A project team can spend months choosing contract or tender forms while the needed result, acceptance basis, interfaces, and capability consequences remain unsettled. The first pass therefore starts from one result and stops at the smallest decision that changes the team’s next Work.

SYSE.24:3 - Forces

The following eight tensions recur in this decision.

SYSE.24:4 - Solution

SYSE.24:4.1 - Name one result and one decision

Write one sentence containing these five elements:

• the result being sought and its actual kind;
• the receiving use and the Systems whose use or condition matters;
• the configuration, operating conditions, horizon, and acceptance claims;
• the decision-making Agent and the decision it is authorized to make; and
• the latest useful date for that decision.

If the sentence alternates among a product, access, performed Work, capability, and an evidence episteme, the decision still has several subjects. Split it or select the one result that changes the next commitment. If the project system-of-interest, its actual or intended status, or its intended use remains unclear, return to A.15.6, SYSE.1, SYSE.16, and SYSE.2.

The acceptance basis must be usable before arrangement generation. It can include several characteristics and thresholds; it need not reduce them to one score. State protected conditions and affected-System consequences that no arrangement may hide.

SYSE.24:4.2 - Generate complete ways of obtaining the result

Use the following six prompts to construct materially different arrangements:

• adapt or reuse an available System, capability, Method, or result;
• acquire a ready System and combine it with project integration, configuration, and assurance Work;
• commission provider Work that produces a custom result;
• obtain continuing provider Work, access, or operation under stated availability and recovery conditions;
• develop the result through Agents, Methods, and Systems within the chosen project boundary; or
• combine ready, provider, internal, and shared contributions.

For each applicable prompt, answer the eight common questions in §4.3 and write one whole possible-future arrangement. Put only whole arrangements in the OptionSet. The same purchase relation can occur in several arrangements; the same AI Agent can perform Work in internal, provider, or mixed arrangements; the same Method- development branch can enable several options.

Apply C.18 only when the team also runs a named open-ended generation effort whose archive, Front, descriptors, telemetry, lineage, or next governing relation must remain available. In that branch, identify the generation Method and fill the applicable C.18 generation, archive, or Front record. C.18 preserves that search result; it does not supply the domain Method for constructing an obtaining arrangement.

SYSE.24:4.3 - Describe every arrangement with the same questions

The following eight questions form the common comparison set. Answer a question only as far as it can change this comparison, but use the same basis for every option.

An unknown answer can remain unknown when it cannot change the choice. If it can reverse the choice, record it as the comparison defect and either obtain the specialist result or make it the subject of one bounded probe.

SYSE.24:4.4 - Restore parity before comparing

Apply the same five parity elements to every arrangement: acceptance conditions, operating environment, configuration boundary, evidence horizon, and burden categories. Assess ready demonstrations and internal-development options against representative project conditions. For a provider arrangement, count both the fee and the receiving team’s remaining Work, retained risks, and exit burden outside that fee. For internal development, include the opportunity cost, capability gap, assurance, support, and time until use.

Do not force unlike consequences into one weighted total when that would hide a protected condition or a non-compensable loss. Keep a tie-set or a partial order when the available evidence supports several non-dominated arrangements.

Apply C.11.CRC only when the missing input to arrangement comparison is what a finite proposed change contributes relative to the project’s current configuration. Name the current configuration S0, the finite change Δ, the realizable changed configuration S1, and the arrangement-choice decision that will use the comparison. Work applying C.11.CRC returns only that configuration-relative contribution claim. It neither constructs an obtaining arrangement nor chooses among arrangements.

SYSE.24:4.5 - Use specialist results without taking over their Methods

Use a specialist result only where it can change the comparison. Examples include:

• Strategy for the result’s contribution to a strategic choice and for option-set scope;
• Finance for funding, cash, valuation, and financial-risk claims;
• commercial and legal practice for offers, duties, remedies, rights, licences, and contracting;
• Governance or Administration for permission, accountability, tender, and public-procedure claims;
• Organization Change Engineering when the arrangement requires changing organizational structure, position responsibilities or decision rights;
• Operations Management for continuing demand, capacity, queues, allocating Work within an existing authorized arrangement, service, exceptions, and provider performance;
• Enterprise Asset Management for portfolio-level acquire, retain, modify, share, or retire decisions;
• Human Capability Development for a person’s capability-development programme; and
• safety, security, environmental, clinical, or other application practices for their acceptance and assurance results.

Assigning a new case to an already qualified performer under existing authority is an operating allocation. Changing an analyst position’s authority from preparing results to authorizing them changes the organizational arrangement. A needed capability-development result remains a separate contribution in either case.

The Systems Engineering comparison cites the specialist result it uses and preserves that result’s conditions. The responsible specialist practice and authorized Agent still supply such results as the contract form, spending decision, Work assignment, legal duty, or specialist assessment.

SYSE.24:4.6 - Choose, reject, probe, or reroute

Pass the completed OptionSet to C.11. State the DecisionSubject, comparison basis, ChoiceRule, and one lawful ChoiceResult:

• choose one arrangement or a retained tie-set now;
• reject the current set and return to candidate generation;
• perform one feasible probe whose result can still change the survivor set; or
• reroute because a named realization, organization, finance, law, authority, or other question now governs the decision.

For a chosen or retained arrangement, identify its first unsupported realization branch and continue with SYSE.3. The ChoiceResult is an episteme. Producing, performing, transferring, accepting, and using the sought result still depend on the applicable Agents, Work, Methods, and direct relations.

SYSE.24:4.7 - Observe use and reopen the choice

Reopen when a changed premise can change the choice. Such a premise may concern result identity, acceptance, provider or builder capability, an interface, configuration, evidence, a resource limit, support, an affected- System consequence, or exit. A later provider failure can reopen the obtaining arrangement without reopening the project system-of-interest. A changed project use can require a wider return to SYSE.1 or SYSE.2.

SYSE.24:4.8 - Record the first useful result

The written comparison and choice are usable when a reader can recover the following seven contents:

SYSE.24:4.9 - What Changes in Practice

The engineering team stops comparing buy, build, outsource, AI, and reuse as if those words named equivalent options. It compares complete ways of obtaining one result. This exposes integration, configuration, assurance, provider dependence, internal capability, and exit before the commitment makes them expensive.

SYSE.24:5 - Worked Cases

SYSE.24:5.1 - Climate control for a new greenhouse configuration

Small equipment company GreenHeat-4 needs a climate-control System for greenhouse GH-2. Until identity inception, GreenhouseClimateControl-GH2 remains the designator for the intended System in the WorkPlan and descriptions. The receiving use is control of heating, ventilation, misting, and shading during cold-night, rapid- solar-rise, and failed-humidity-sensor conditions. Acceptance requires bounded temperature and humidity performance, no unsafe actuator command after the sensor failure, identified software and controller configuration, recoverable observations, and a supported fallback to manual operation. GreenHeat-4’s authorized management team may choose the obtaining arrangement within its approved equipment budget; electrical-safety acceptance remains with the named specialist authority.

GreenHeat-4’s engineering team develops four complete arrangements:

The parity basis includes the same three operating conditions, commissioning date, interface set, configuration evidence, assurance burden, data access, support horizon, internal capability consequence, expected change latency, and exit condition for all four arrangements. The internal-only and commissioned-custom arrangements do not survive the commissioning-date condition. The ready-controller and hybrid arrangements form a tie-set.

The two survivors have different burdens. The ready-controller arrangement is estimated at EUR 84,000, nine weeks, and eighteen days of GreenHeat-4 engineering Work; later greenhouse-specific changes require a vendor release expected to take four to six weeks. The hybrid arrangement is estimated at EUR 96,000, eleven weeks, and thirty-two days of internal engineering Work; if the supervisory interface remains supported, the controls team can make a greenhouse-specific change within five working days. The operating plan expects at least three such changes during the next three years.

The management team is authorized to commit up to EUR 7,000, forty engineering hours, two hardware-in-the-loop laboratory days, and five elapsed working days to the obtaining decision. Those limits fit the remaining one-week decision reserve without moving the commissioning date. The electrical-safety specialist may authorize the failed-sensor injection in the laboratory; that authorization does not extend to a greenhouse trial.

The management team uses this ChoiceRule: preserve the failed-sensor, configuration-identity, and commissioning- date conditions first. Probe only when the probe stays within the stated limits and every possible outcome changes what the team may lawfully do. If both arrangements survive, choose the hybrid only when its added price is no more than EUR 15,000 and its added internal burden is no more than fifteen engineering days; otherwise choose the ready- controller arrangement.

The proposed replay costs EUR 5,500, thirty-two controls-engineering hours, eight integrator hours, two laboratory days, and five elapsed working days. It uses the intended sensor and actuator interfaces and injects the failed- humidity-sensor condition while checking configuration export and the supported supervisory API. Its possible observations have three decision effects:

• an unsafe local fallback or a configuration export that cannot reidentify the tested controller and software rejects both survivors and returns the team to arrangement generation;
• a safe fallback and usable configuration export combined with failed supervisory timing or withdrawn API support rejects the hybrid and retains the ready-controller arrangement; and
• a safe fallback, usable configuration export, and supported API within the timing limit retain both survivors; the price-and-burden branch of the ChoiceRule then selects the hybrid arrangement.

ChoiceResult-GH2-1 is probe again. Choosing either arrangement without the replay would leave a protected acceptance claim unsupported, while rejecting both would discard a survivor that one bounded replay can retain. This worked case stops at that first useful result. APP-SYSE-04 continues the case through performed replay and a later choice. SYSE.3 begins only after the replay retains an arrangement and exposes its first unsupported realization branch.

SYSE.24:5.2 - Obtain a pipeline-condition account rather than an inspection device

WaterUtility-North must decide which pipe sections enter its next replacement programme. The sought result is engineering episteme PipeConditionAccount-2027 for twelve kilometres of buried pipe; an inspection device is only one possible means. Acceptance requires stated coverage, location error, uncertainty for wall-loss estimates, blind-sample checks, raw observation access, configuration and date of the inspected pipe segments, and a supported relation from observations to replacement decisions. The utility’s engineering team compares four arrangements:

• a specialist provider’s field team performs inspection Work and supplies interpreted results but keeps the raw data;
• the utility acquires inspection equipment; its engineering team develops internal capability, performs the Work, and maintains the equipment and analysis Method;
• the utility leases equipment while the provider’s qualified field team operates it and the provider’s analysts supply raw observations and interpreted results; and
• a provider’s field team performs data collection while the utility’s engineering team controls the interpretation Method, acceptance checks, and continuing data custody.

The whole arrangements expose different calibration Systems, field access, operating interruption, performer capability, data rights, configuration identification, blind-sample evidence, support, future repeatability, internal capability, cost, and exit conditions. A purchase price is not compared with a provider invoice alone. The internal arrangement includes training, qualification, equipment maintenance, field Work, analysis, and the cost of delaying the replacement decision. The provider arrangements include acceptance and rework conditions, raw-data access, repeatability, and recovery if the provider leaves the market.

The utility needs the account once within three months and has no present inspection-equipment capability. Its asset-replacement board is authorized to choose the inspection arrangement within a EUR 250,000 ceiling and to allocate at most thirty utility analyst-days. Operations separately authorizes pipe access and interruption; the board cannot supply that result itself.

The equipment-purchase arrangement fails the time condition. The interpretation-without-raw-data arrangement fails the evidence-custody and exit conditions. The Finance result compares funding, the Operations result states pipe-access and interruption conditions, and the legal-practice result states data and remedy terms. The board uses those results but does not replace their Methods or authorities.

The two survivors are compared on the same basis:

The board’s ChoiceRule first rejects any arrangement that misses acceptance, raw-data custody, or the three- month limit. Among survivors, it prefers the arrangement that the utility can reproduce after provider exit when its total price stays within EUR 200,000 and its internal burden stays within thirty analyst-days. If the utility capability evidence or either resource limit fails, the rule retains provider interpretation instead; if both interpretation claims fail, it returns probe again on one shared blind dataset.

The evidence supports the utility-interpretation branch. ChoiceResult-PCA-2027-1 is choose now: the provider’s field team performs collection and the utility’s engineering team controls the interpretation Method, acceptance checks, and raw-data custody. A further probe would not change which arrangement survives because the utility capability and both resource limits have already been checked on the common basis. In the choice record, state the provider capability evidence still required for field collection, the blind-sample acceptance Work, and the first unsupported field-access branch for SYSE.3. Contracting, inspection, acceptance of PipeConditionAccount-2027, and pipe-replacement decisions still require their applicable Work.

SYSE.24:6 - Bias Annotation

The pattern favours one decision-usable result over a complete procurement programme and favours comparable whole arrangements over familiar make-or-buy labels. This makes hidden integration and capability burdens visible early. It may underdescribe specialist concerns—for example, sector-specific market engagement, tender, contracting, law, public accountability, finance, and post-award operations. Those Methods remain with their specialist practices.

The pattern also favours preserving several non-dominated arrangements when evidence does not support a winner. That can look slower than selecting a familiar supplier or internal team, but it prevents missing information from being disguised as certainty.

SYSE.24:7 - Conformance Checklist

The following eleven requirements form this pattern’s complete conformance checklist.

SYSE.24:8 - Common Anti-Patterns and How to Avoid Them

The following ten rows document recurring failures and their repairs.

SYSE.24:9 - Consequences

Projects gain a comparable choice before architecture, integration, supplier, capability, and assurance commitments become difficult to reverse. Reuse, acquisition, provider Work, access, internal development, and mixed arrangements can be considered without pretending that their short labels identify equivalent objects.

The cost is that an apparently simple purchase decision becomes an engineering decision with explicit interfaces, configuration, evidence, support, capability, and exit. Another practice may have to answer a named question first, so the first result may be a retained tie-set or one worthwhile probe rather than an immediate winner.

SYSE.24:10 - Rationale

General decision theory can compare options only after they answer the same decision question and carry a shared comparison basis. Systems Engineering adds the missing domain move: it constructs complete ways of obtaining an engineering result across a designated project system-of-interest and its builder arrangements when those structures matter, together with provider and internal Work, interfaces, configuration, assurance, and continuing change.

The obtaining arrangement is the unit of comparison. Comparing whole arrangements keeps their different contributions visible: an AI Agent can perform Work in several arrangements; Method development can enable an arrangement or be the sought result of a separate project.

The pattern stops before procurement becomes a universal Systems Engineering Method. Specialist areas—for example, market engagement, contracting, incentives, tender, public authority, finance, organization, and provider operation—have their own problem families and evidence. Systems Engineering keeps their consequences connected to the engineered result without taking over their decisions.

SYSE.24:11 - SoTA Echoing

The following five source rows show how this pattern uses and limits the literature.

These sources support the need for a connected obtaining decision but do not establish one complete Method for every sector. Reopen this synthesis when cross-sector evidence changes the common arrangement questions, or when several acquisition or procurement problem families remain after this pattern and the other named DPFs are applied.

SYSE.24:12 - Relations

The following relations locate this pattern’s inputs, specialist boundaries, and continuations.

• A.15.6 distinguishes an actual from an intended project system-of-interest and designates a project Method-of- interest only when that Method is the current question. SYSE.1, SYSE.16, SYSE.17, and SYSE.2 supply the relevant use, environment, affected Systems, and linked use-and-System concepts when their results fit this decision.
• The six prompts and eight common questions in §§4.2–4.3 guide the Agent’s Work of constructing complete obtaining arrangements. Apply C.18 only to a named open-ended generation effort when its generation Method, variants, archive or Front, descriptors, telemetry, lineage, and next governing relation need a durable record. C.19 governs how broadly to continue exploration. The deciding Agent performs comparison-and-choice Work by applying C.11 to the available arrangements and produces a ChoiceResult for the receiving project decision: choose now, reject current set, probe again, or reroute. The Agent applies C.11.CRC only when a configuration-relative contribution comparison is missing.
• SYSE.5 supplies functional and bearer alternatives; it does not choose how the project will obtain a needed result. SYSE.6 supplies architecture decisions for the engineered System.
• SYSE.8 may supply an offering-and-provider account when the sought result depends on continuing provision, access, custody, or responsibility. It does not choose the receiving project’s obtaining arrangement.
• SYSE.9 supplies a needed professional contribution and its receiving use. SYSE.10 supplies bounded research, model, experiment, and trial results used in the comparison.
• The realization Agent applies SYSE.3 to a retained obtaining arrangement and develops its first unsupported realization branch. Use the applicable FPF and DPF patterns separately for the realization network, WorkPlan, performed Work, and resulting facts.
• SYSE.12, SYSE.18, and SYSE.23 supply platform, independently governed constituent, and project-system- of-interest-and-builder evolvability results when those questions can change the arrangement.
• SYSE.13, SYSE.14, and SYSE.4 govern configuration, change and release, and claim-specific assurance.
• A.13, A.15.1, A.2.1, F.6, and the authority patterns establish actual Agent, Work, assignment, attribution, and permission facts separately; the obtaining-arrangement description remains an episteme.
• E.23.CDI and the Human Capability Development DPF govern capability-development questions. Organization Change Engineering, Operations Management, Strategy, Finance, Governance, Administration, Enterprise Asset Management, law, commercial practice, and application DPFs retain their own Methods, evidence, and decisions.

SYSE.24:End