OPS.13:4 - Solution

OPS.13:4.1 - Recover the service and the parties’ current position

Identify the promising party, recipient, accepted result, eligible demand, start and end events, horizon, required service level and any agreed exceptions. Use the recipient’s service boundary. Waiting that begins before an internal queue is visible can still matter to the promise.

Keep three statements distinguishable:

Recover outstanding commitments, including work already admitted and obligations to other recipients that a new plan would displace. A newly requested target does not silently replace them. When an existing promise is wider than the currently supportable result, keep the unresolved part explicit.

If the desired improvement or its comparison is still arbitrary, use OPS.21 to construct a meaningful aim. An ambition can exceed the current expectation while exposing a worthwhile improvement question. Establish its actual service promise here only after the work, resources and parties support it.

Ask what acceptance requires. A completed test attempt, a passed test with applicable evidence, the customer’s acceptance of that evidence and an authorized product release can occur at different times and under different authorities.

OPS.13:4.2 - Obtain the work, resource and dependency basis

Map the required work far enough to identify consequential dependencies and timing. Recover the remaining work on already admitted items, upstream readiness, actual resource windows, needed skills and configurations, setup, handover, recovery and downstream acceptance. Use OPS.10 when the capacity comparison needs development.

Check the resources’ availability for the required time, assignment and use. A provider’s offer remains conditional until its resource decision is made. A person already assigned elsewhere supplies no additional simultaneous capacity merely because their skill is suitable.

Use OPS.12 where the proposed arrangement changes human conditions. Obtain the exact professional result needed by a disputed capability, protection or release claim. A forecast can state an unresolved condition, while a commitment that depends on it needs either the result or an explicit agreement about that condition.

Keep existing evidence when it fits this demand, configuration and horizon. If a historical service forecast excludes stalled items or concerns a different work mix, inspect that limitation before relying on it. OPS.15 helps reconstruct the eligible population and observation basis.

OPS.13:4.3 - Test the proposed promise at the required level

Start with a transparent load and time-window bound. If known work already exceeds usable resources before the deadline, select another plan or resource decision before adding a sophisticated model. Where order matters, lay out a feasible sequence with the required resources available together.

Compare the normal case with adverse and changed-condition cases that can alter this service decision. Include relevant repeats, absence, arrival bursts, failed inputs or delayed acceptance. State how each case consumes resources and which result it supports. Reserve time protects a named scenario only while its location, capability and availability fit that scenario.

A finite set of cases establishes what those cases show. A time-plus-probability promise needs a defensible forecast for the eligible population under sufficiently matching conditions. Inspect model assumptions, data coverage, dependence and the consequence of errors. Obtain appropriate forecasting or statistical expertise when that claim exceeds the available method.

Preserve customer classes or conditions whose losses matter separately. A favorable overall service proportion can coexist with an unacceptable result for a protected class. The target and the permitted consequence come from the service decision; the forecast supplies evidence for that decision.

OPS.13:4.4 - Choose and agree a supported response

Select among the supported alternatives: keep the proposed promise, change its scope or time, change the resource arrangement, refuse the request or obtain a missing result. Compare consequential financial differences with OPS.14 when payment, displaced use or funding changes feasibility or preference.

State the selected result in the parties’ ordinary service terms. Include the conditions on which they rely, the relevant uncertainty and the observation that would require another decision. Make any requested recipient action explicit, such as timely provision of an input or acceptance by a specified date.

For an existing promise, obtain an authorized acceptance or refusal of the proposed revision. Until that agreement changes, continue to report the old obligation and its current risk. Record an unresolved position as unresolved. Internal replanning alone cannot discharge the promise.

A short confirmation in the existing service account can be sufficient. Add detail where the commitment’s consequences require it, such as several recipients, contractual terms or a consequential uncertainty. Qualified legal or commercial work supplies those terms when needed.

OPS.13:4.5 - Observe early enough to act

Choose the observations and review point from how quickly the plan can become infeasible and how long recovery takes. Confirm resource decisions before they are needed. Follow readiness, actual progress, repeats, acceptance and protected conditions where a change would affect the promise.

Work backward from the last time a useful response can start. Include the delay before detecting the problem, conveying it to someone who can decide, making that decision and obtaining the remedy. Use OPS.10.2 when resource windows or other work affect the remedy’s timing. For a response intended to preserve the promise, the whole detection-to-remedy sequence must fit the remaining usable window. If no such response fits, use the early information to compare another remedy or a service revision. A percentage of reserve consumed can help direct attention; it supplies neither a delay probability nor the resources needed to respond.

Use this response timing to choose a periodic review, an event signal or both. A report of a consequential change can require action before a dashboard threshold is crossed. Where the current account supports continuation and no shared decision is needed, a status meeting need not interrupt the work. Preserve other purposes for meeting, such as learning or resolving an actual disagreement.

When the basis changes, calculate the affected service consequence and contact the responsible parties while a useful choice remains. Preserve what can still be performed under existing authority. Use observed delivery and acceptance to determine which promised results were fulfilled, and retain any remaining obligation. A changed forecast records the new outlook.