SYSE.18 - Decide Whether and How to Integrate Systems Governed by Different Agents

SYSE.18:0 - Use This When

Use this pattern when one use depends on several actual Systems, but decisions that can change that use—for example, a constituent’s operating condition, configuration, commitment, interface, or later modification—belong to different Agents. The integrating Agent cannot command every change that can defeat the use.

Begin with the shared use and the actual constituent Systems that can defeat it. For each constituent, state how it affects that use, who can decide the relevant change, what authority that Agent has, and which configuration, interface, commitment, evidence, or withdrawal condition the decision relies on. Then compare only the coordination alternatives that the relevant Agents can actually decide.

The first useful result is a bounded constituent-integration decision. It states the selected coordination alternative, the deciding Agent’s authority, decisions required from other Agents, accepted losses, unsupported dependencies, and next Work. If integration Work is later performed, identify that Work, its actual transformation or newly obtaining relation, and the observed-coordination claim separately from the decision episteme.

Use ordinary architecture and integration patterns when one deciding Agent controls every constituent change that can alter the use. Use the neighboring practice that owns a different question—for example, Organization Change when an organization is the System being changed, Corporate Governance for ownership and governing-body decisions, Operations Management for continuing allocation and coordination Work, or a configuration or other specialist pattern for its own subject.

SYSE.18:0.1 - Terms and Distinctions

Name in this pattern	What it denotes
shared use	One named result or use whose conditions depend on several Systems. Any hierarchy or whole–part claim needs its own relation.
constituent System	An independently identified actual System whose participation, result, failure, change, or withdrawal can alter the shared use. Constituent names that use-relative relation; state any proper-part relation separately.
independently governed	A decision relevant to the use—for example, a commitment, operating choice, configuration change, or withdrawal—is controlled outside the integrating Agent’s authority. Independence concerns the named decision, not every aspect of the System.
system of systems	A source or domain label that prompts recovery of the actual Systems and relations relevant to the shared use. Classify those Systems and relations directly rather than treating the label as a universal kind.
interoperability	The evidence-backed ability of named Systems, under a stated configuration and conditions, to exchange results through identified interfaces and make those results usable for the shared use. Interface descriptions are epistemes about this ability, not participants in the exchange.
commitment	An obtaining duty relation with a bearer, referents, scope, validity, governing rule, and instituting basis. Record its content, later Work, delivered result, and evidence of fulfilment as separately grounded claims.
constituent-integration decision	The episteme that selects one bounded coordination alternative within stated authority and records outside decisions, unsupported dependencies, next Work, and reopen conditions.
observed-coordination claim	A later evidence-backed claim that named Systems coordinated for the shared use under stated configurations and conditions. Record the earlier decision, performed Work, commitments, observation, and claim interval separately.

A System described, for example, as an owner, operator, integrator, supplier, or decision maker is an Agent only when the agency claim is warranted. State the direct predicate and participants for every relied-on claim. Use the applicable pattern when the decision depends on agency, authority, a commitment, performed Work, capability, or evidence; state constituent participation and the shared use separately.

SYSE.18:1 - Problem Frame

For example, district drainage can depend on separately governed pump stations, gates, drainage networks, dispatch Systems, provider organizations, and public infrastructure. A product can likewise depend on independently evolving software, communication, payment, and energy Systems or regulatory organizations. Each constituent can remain useful elsewhere and change for reasons outside the integrating project.

Drawing a larger boundary does not create authority or interoperability. A model or interface description can carry claims. An agreement can institute a commitment. A meeting is Work. A governing body is a System whose participating Agents may make authorized decisions. For constituent Work, identify its performing Agent; for another Agent’s decision, identify that Agent’s authority.

SYSE.18:2 - Problem

An integrating team needs answers to seven practical questions:

Which shared use, conditions, interval, and engineering decision are at issue?
Which actual Systems can defeat the use by changing, failing, withdrawing, or withholding a result?
Which direct relation connects each System to the shared use, and what does that relation change?
Which Agent controls each relevant decision, and what authority, permission, or escalation relation obtains?
Which configurations, interfaces, capacities, timings, commitments, and evidence make coordination possible?
What can the integrating Agent change, and which decisions must come from other Agents?
What actual observation would show that the changed arrangement works for this use?

Missing answers produce four recurring errors: interface syntax is mistaken for interoperability, an agreement for performance, a constituent label for parthood, or an integration team for authority over Systems it does not govern.

SYSE.18:3 - Forces

Recurring tensions include:

The shared use needs coherent results; constituents retain other uses, priorities, owners, and decision centres.
Integration benefits from stable interfaces and commitments; Systems and environments continue to change.
Receiving decisions need comparable evidence; every source keeps its provenance, limits, and authority.
One Agent can compare shared-use options while several Agents separately permit constituent changes.
Some coordination can be agreed in advance; operating conditions can require continuing reconfiguration.
A broad account reveals dependencies, while the current decision must remain feasible within actual authority.

SYSE.18:4 - Solution

Recover the constituent arrangement from the shared use, make distributed decisions and dependencies explicit, and choose one bounded coordination alternative within the deciding Agent’s authority.

SYSE.18:4.1 - Perform the Move

Name the shared use and decision. State the result, use interval, conditions, constituent Systems, and the Agent authorized to make the current integration decision.
Identify actual constituent Systems by consequence. Include a System only when a stated consequence of its condition or behavior—for example, participation, a supplied result, failure, change, or withdrawal—can alter the shared use. Keep a future candidate as an intended System referent in plan or decision content until it exists and can be recognized.
State the relied-on relation. For each constituent, say in ordinary language how its behavior, state, result, or availability changes the shared use. Then apply the pattern that governs the actual relation—for example, a transformation, performed Work, commitment, capability, transfer, interface, availability, or evidence relation. Use a separate predicate for each unlike claim.
Recover decisions and authority. For every choice that can alter the use, identify the deciding Agent, assignment when relevant, direct authority or permission, conflict, and escalation. Compare the actual decision centres and feedback; neither centralization nor decentralization is beneficial by label.
Check commitments, interfaces, configurations, and evidence. Record each commitment, later Work, delivered result, interface description, actual exchange, and fulfilment evidence as its own claim. State the relevant conditions used by the decision—for example, notice, withdrawal, capacity, timing, recovery, or currentness.
Generate feasible coordination alternatives. Consider alternatives such as retaining the arrangement, changing an interface or commitment, adding a mediating System, buffer, or fallback, replacing a constituent for this use, narrowing the use, or stopping. Preserve alternatives that require decisions from different Agents.
Choose within actual authority. Record the selected alternative, deciding Agent, authority, accepted losses, decisions still required elsewhere, unsupported dependencies, authorized next Work, and any evidence still needed for reliance on the selected arrangement.
Perform and observe only when authorized. If integration Work occurs, identify the performing Agent, Method, dated Work, actual transformation or newly obtaining relation, resulting configuration, and evidence. Use a representative occurrence to support only the coordination claim actually observed.

The numbered presentation is an A.22.CGUS learning unfolding, not a required sequence for constituent Work. Constituent operation, engineering, governance, and integration can be simultaneous; only stated dependencies and temporal relations establish order.

SYSE.18:4.2 - Record the Result

Field	Required content
shared use	Result or use, conditions, interval, affected Systems, current decision, and deciding Agent.
constituent Systems and relations	Actual Systems, configurations, other uses, reasons for inclusion, and one direct relation or stated gap for every relied-on contribution or constraint.
decisions and authority	Ownership and other governing relations, deciding Agents, assignments when relevant, authority, permissions, conflicts, escalation, and decision-centre boundaries.
commitments and interoperability	Commitments with bearers and conditions; interfaces, capacities, timings, actual exchange or use evidence, notice, withdrawal, and failure-recovery conditions.
alternatives and choice	Considered feasible coordination alternatives; selected alternative and selection basis; deciding authority, accepted losses, outside decisions, unsupported dependencies, and next Work.
later integration, when current	Performing Agent, Method, dated Work, actual change or newly obtaining relation, resulting configuration, representative observation, and evidence limits.
decision use and reopen	Decision contribution supplied to next Work; separately supported observed-coordination claim when available; fallback, gaps, and conditions for reopening each affected claim.

The first useful decision does not wait for implementation. Identify the earlier decision, performed Work, and later observed-coordination claim separately. An observed coordination result does not establish that every constituent commitment was fulfilled.

SYSE.18:4.3 - What Changes in Practice

Engineers stop using system of systems as an explanation. They can name which Systems matter, what each Agent can decide, what the integration Agent can change, which dependencies remain unsupported, and what observation is needed before the shared use may rely on the changed arrangement.

SYSE.18:5 - Worked Case: Emergency Discharge Across Four Independently Governed Systems

Emergency discharge in one district depends on four actual Systems:

a flood-pump station, whose configuration and release are decided by the station-owner organization;
an upstream gate System, whose schedules and overrides are decided by the river-control agency;
a municipal drainage network, whose capacity commitments and outage notices are decided by the municipal operator organization; and
an emergency-dispatch System, whose regional agency decides which acknowledgement and escalation Methods are used.

The four Systems contribute to one use. Company membership and whole–part relations require separate evidence. The current configuration and interface evidence supports pumping, gate scheduling, network reception, and dispatch acknowledgement under stated loads and conditions. Four separate commitments bind named Agents under conditions concerning station configuration, the gate envelope, drainage capacity, and dispatch availability. Later Work and delivered results require their own evidence.

A tabletop exercise exposes one material mismatch: the municipal operator commits to four hours of outage notice, while the station fallback needs six. The integration Agent has authority over a station-side buffer and the existing dispatch escalation condition. The municipal operator retains authority over the notice commitment.

The current options are to accept the two-hour gap, add a temporary buffer, request a changed municipal commitment, narrow the discharge use, or stop the increment. The integration decision selects a temporary two-hour buffer plus dispatch escalation while leaving the municipal commitment unchanged. The decision records the external commitment request as a separate possible improvement, not as an accomplished change.

An integration team later installs a mobile buffer System. Identify the installation Work, installed buffer, installation evidence, and newly obtaining buffer-availability relation separately. A representative exercise supports that the buffer absorbs the stated two-hour load and that dispatch acknowledges and escalates under the tested condition. The observation is limited to that load and interval; constituent commitments keep their previous values.

Before installation, the decision identifies the next Work within the integrating Agent’s authority. After the exercise, a separate current observed-coordination claim can inform SYSE.11. A change in a relied-on relation, condition, configuration, or use reopens only the affected claim and decision.

When the full pattern is unnecessary. Use ordinary architecture, configuration, integration, and Work patterns when one Agent has authority over every configuration, release, commitment, and operating decision that can change the integration result.

SYSE.18:6 - Bias Annotation

Systems-of-Systems literature is influenced by defence, formal model federation, and software orchestration. Use each source for the Method and case it actually studies. A cross-domain constituent classification, governance form, representation, or integration Method needs its own evidence. Official attention and conformance describe publications or declared rules; project use and effectiveness need evidence from performed Work and outcomes.

Compare several decision centres by their actual authority, operations, outcomes, and feedback. Distributed and centralized arrangements can each help or harm; the label decides nothing.

SYSE.18:7 - Conformance Checklist

One shared use, conditions, interval, affected Systems, current decision, and deciding Agent are stated.
Every constituent is an actual System included because its participation, output, failure, change, or withdrawal can alter the use.
Each relied-on relation has its own predicate and participants; no umbrella contribution relation replaces it.
Independence is stated for named decisions and relations, not as an absolute property.
Every deciding Agent, assignment when relevant, authority, permission, conflict, and escalation is stated.
Interface syntax is supplemented by configuration-bound exchange and use evidence where interoperability is claimed.
The selected alternative remains within the deciding Agent’s authority and names outside decisions and unsupported dependencies.
Any claimed coordination change identifies performing Agent, Method, dated Work, actual change or relation, configuration, representative observation, and evidence limits.
The decision episteme, performed Work, world-side change, and observed-coordination claim are identified and grounded separately.

SYSE.18:8 - Common Failures and Repairs

These recurring failures hide a relation, deciding Agent, or evidence boundary:

Failure	Repair
System of systems is treated as a kind and explanation	Recover actual Systems, use-relative relations, and decision boundaries.
Participation is treated as parthood	State the direct relation and keep Work, capability, commitment, interface, resource, and evidence claims separate.
Interface syntax is treated as interoperability	Obtain configuration-bound evidence that results are exchanged and usable.
Agreement is treated as performance	Separate commitment, later Work, delivered result, and fulfilment evidence.
Integrator is assumed to own constituent decisions	Name each deciding Agent and authority; state which decision each blocker prevents.
Decision record is treated as coordination change	Perform authorized Work and identify the actual transformation or relation before claiming a changed condition.
Decentralized is assumed to be better	Compare decision centres, operations, outcomes, and feedback for this use.
Model federation is treated as physical integration	Separate description consistency, actual configuration, integration Work, and operating evidence.

SYSE.18:9 - Consequences

Distributed authority and unsupported dependencies become visible before integration fails. The integrating Agent can make a bounded useful change within its authority. The conditions relied on by the shared use and the monitoring Work needed to maintain them become explicit.

The cost is negotiation and maintenance of constituent claims. Keep the account focused on Systems that can affect the shared use, and reopen only the claims a change affects.

SYSE.18:10 - Rationale

Shared use depends on actual relations among Systems while authority and evolution remain distributed. Treating every constituent as an owned component hides withdrawal and decision boundaries. Engineers can act through named interfaces, commitments, buffers, and fallbacks. Separate decisions, Work, changes, and observations make bounded integration possible.

SYSE.18:11 - SoTA and Source Use

Source line	Retained contribution	Limit and guard
Papadopoulos, Tortola, and Geyer 2024 and Baldwin et al. 2024	Several interdependent decision centres should be compared through their setting, operations, outcomes, and feedback over time.	The reviews report broad terminology, beneficial and harmful outcomes, and long-term evidence gaps; they establish no universally better governance arrangement.
Raz et al. 2024	Connect mission tasks, constituent capabilities, candidate configurations, consistency, and bounded alternative evaluation.	One simplified defence-funded demonstration establishes neither a universal ontology nor cross-domain effectiveness.
Swickline, Mazzuchi, and Sarkani 2024	Preserve separately maintained model sources while forming a larger behaviour and structure description.	One SysML/Cameo Method and lunar-rover case supplies description Work, not physical integration or universal architecture.
Ashfaq et al. 2026	A systematic review retains several runtime-composition problems, solution families, tools, and evaluations for dynamic software-intensive Systems.	Software-intensive scope and unresolved sociotechnical alignment prevent a universal integration Method.
SEBoK, “Applying the Systems Approach,” 2026 revision	Concurrent, iterative, and recursive use of Systems Engineering across several Systems of interest.	Older lifecycle and requirements framing and component stop rules are not retained as this pattern’s structure.

This is a bounded expert synthesis, not evidence of field prevalence or causal superiority. Reopen a used source claim when later systematic comparison changes its decision-centre, outcome, feedback, integration, or transfer boundary.

SYSE.18:12 - Relations

A compatible SYSE.6 result supplies architecture constraints for the same shared use. Ground constituent participation, commitments, authority, and interoperability under their direct patterns.
A.1.SCR governs actual System recognition; A.22 governs selected structures; E.18.NET governs a transformation-flow network only when its members and relations are independently established.
A.6.P, A.2.2, A.2.8, and A.10 separately govern service wording, capability, commitment, and evidence claims.
A.2.1, A.2.8.PER, A.15.1, A.3.1, A.3.4, and A.15.PROD govern assignment, permission, Work, Method, actual change, and production claims. Another Agent’s decision authority still needs its own direct claim.
A specialist practice retains its own decisions and authority—for example, Organization Change, Corporate Governance, Operations, Configuration, Maintenance, safety, security, law, finance, or contracting.
SYSE.11 can use a compatible observed-coordination claim for the same constituent Systems, configuration, shared use, and interval. Ground any later fulfilment or authority claim separately.