From selection to exit
The partner decision involves the delivery model, the agreement and the service after introduction. Different approaches focus on different parts.
| Approach | Contribution | Connection to examine |
|---|---|---|
| A Simple Architectural Framework (ASAF): Supplier | Connects the intended supply chain, changes to it, current suppliers and policies. | Keep the relationship visible while the service changes and runs. |
| Sourcing Playbook | UK government guidance covering delivery-model choices, supplier relationships and transition/exit. | Apply the relevant commercial rules, while retaining the architecture’s dependency and handover questions. Government Commercial Agency, 2026. |
| Security supply-chain view | Examines access, information, service dependencies and controls across parties. | Connect supplier risks to business ownership and operational response. NIST CSF 2.0. |
| Interface contract | Records requests, accepted results, failure behaviour and version changes. | Connect technical behaviour to the commercial and operational responsibilities. See systems and integration. |
The interface contract is a general technique used in these examples. The Playbook addresses public-sector sourcing. This comparison draws selected architectural questions from public references; it does not review the complete methods.
Trade-offs
A single supplier can simplify coordination while concentrating dependency. Several suppliers can offer choice while requiring more shared definitions, integration and incident coordination. Compare the actual service and exit conditions rather than assuming either arrangement is preferable.
Methodology configuration
Relate these questions to existing sourcing, supplier-management and architecture records. Use Methodology configuration to map terms, records and reviews to your own approach.
Use the supplier example, then adapt the supplier record to agree confirmation, failure and exit responsibilities for a proposed partner arrangement.