CUST.6:4 - Solution
CUST.6:4.1 - Define the repeatable result and performer conditions
State what the next customer or recipient should be able to obtain and how adequate completion will be recognized. Identify the class of situations, not only the first customer’s name. Recover the family’s common conditions and permitted variations from CUST.3 when available.
Describe the intended performer’s preparation, decision authority, means and access. “Any consultant” is not a usable condition. “A practitioner who can interpret the customer’s status policy, operate the supported deployment tools and obtain the named security contribution” is more informative. Distinguish skills expected beforehand from preparation the offering provides.
Name the support intended to remain available. An assisted service can be repeatable when that assistance is scheduled, funded and capable of handling the intended cases. A method described as independent cannot depend on unrecognized rescue by its author.
CUST.6:4.2 - Reconstruct the successful work, including invisible contributions
Follow one useful delivery from preparation to continued use. For each consequential result, recover its inputs, operation, decisions, acceptance and exceptions. Ask the original performer what they noticed, inferred or corrected that the visible procedure omits.
Trace the difficult joins. A technically installed tool may still need interpreted inputs, a trained operator, an agreed acceptance example or a recovery route. Include receiving work: the customer may need to produce a monthly file, retain a local administrator or change a workflow.
Separate the recurring operation from incidental facts. Keep a local fact as an input when the method can explain how to use it. Keep a distinct branch when it changes the operation. Exclude the case when neither treatment preserves the result.
IS.3 — Construct and Adapt a Support Strategy with Its Recipients supplies the full construction and adaptation of support with its recipients. Use it when capability, help or local working arrangements are missing. Receive the obtainable support arrangement, then incorporate it into the delivery method rather than treating “training completed” as the result.
CUST.6:4.3 - Choose how each necessary contribution will be obtained
For each contribution, compare explaining it, preparing the performer through practice, automating it, providing a specialist, obtaining a partner result and narrowing the offering. Choose by the actual difficulty and repeated demand.
A rule that is explicit but unfamiliar may need examples and rehearsal. A perceptual or interpersonal skill cannot always be replaced by a written step. A computation may be automated after its input meaning and conditions are settled. Rare, consequential exceptions may be better served by an expert than by a much larger general tool.
Construct the joining operation where an output is not yet usable. If a mapping service returns a qualified correspondence, explain how the deployment performer applies it to the actual input and checks that its conditions still hold. A supplier link alone does not perform that conversion.
Retain the full supplying method where it already explains the contribution. For platform use, SYSE.26 — Design a Supported Platform-Use Path supplies the supported use path; SYSE.27 — Evolve Platform Interfaces and Contribution Paths supplies interface and contribution-path evolution. Receive their qualification, support and compatibility boundaries. CUST explains how those results join the customer’s complete delivery.
CUST.6:4.4 - Assemble a usable delivery method and its means
Build the account in the order the performer needs to understand and act. It should let them recognize fit, prepare, perform the work, make live choices, recognize an adequate result, handle foreseeable exceptions and obtain help. Explain why consequential conditions matter so they can adapt without deleting an invariant.
Supply the means required by that account: accessible tools, permitted templates, appropriate examples, test inputs, training or rehearsal, operating access and support. A useful package can combine several carriers and services. Its contents are selected by the obtaining problem, not by a fixed checklist of file types.
| Missing contribution | Constructive response |
|---|---|
| The performer cannot recognize a valid input | Explain the relevant meaning, show a valid and an invalid example, and provide the decision or escalation needed for ambiguity. |
| A local choice has no rule | State the purpose and consequence of the alternatives, the conditions selecting them and when to obtain a qualified decision. |
| The procedure assumes unavailable access | Change the obtaining route or arrange actual permission and access before promising execution. |
| An exception requires author rescue | Explain the repair, prepare a qualified helper or exclude the condition from ordinary use. |
| A result cannot be accepted | Supply an appropriate acceptance basis and the means to obtain its evidence. |
When material comes from a customer case, receive the permitted common contribution through MKT.14:4.3 within MKT.14 — Develop and Change a Programme for Selected Customer Organisations. Check the next recipient and purpose. Replace restricted material through a permitted route and requalify the affected properties. Renaming data or removing obvious identifiers does not by itself establish the right to reuse it.
CUST.6:4.5 - Perform the receiving connection
Give another appropriately prepared performer a case within the declared conditions, the intended materials and the support that will actually be offered. Let them perform the work. Keep the original author’s interventions visible instead of using them to make the trial appear smooth.
Distinguish three outcomes. The performer may obtain the result through the intended method; obtain it only through additional help; or fail to obtain it. In the second case, identify the extra contribution. It can become explicit supported assistance, a construction improvement or a reason to narrow the method. It is not automatically evidence that all assistance must be removed.
Use a consequential changed condition to test adaptation. A performer who succeeds only on a copied example has not yet shown how they will handle the claimed variation. Test the operation that changes; do not repeat unrelated qualification merely to increase the number of trials.
IS.5 — Sustain, Transfer, Extend or End Implementation Support supplies the full transfer and continuation method. Its result includes what the receiving practice can obtain and what support must remain. Use that result to decide whether the delivery method is ready for the proposed ordinary use, still assisted, restricted or unavailable. Do not claim universal transfer from a single constructed or rehearsed case.
CUST.6:4.6 - Make continued provision attainable
Identify who maintains the method, tools, examples and assistance when their assumptions change. Name the ordinary support contribution, response boundary, exception return and conditions for ending an obsolete variant. Include customer-side duties that affect continued result.
CUST.7 receives the actual recurring work, help and maintenance burden. If the specialist remains the bottleneck, adding partners may increase coordination without increasing the constrained capacity. CUST.8 receives the installed configurations and obligations affected by later changes.
When repetition exposes a family assumption rather than a delivery gap, return it to CUST.3. For example, two environments may need fundamentally different acceptance evidence. Do not keep adding instructions to preserve a false claim that they are one ordinary route.