STR.14:5.1 - SensorCo reconciles the shared month

SensorCo has eighty engineer-days available from a shared team in the coming month. Current service requires fifty-two; another eight protect incident recovery. The same people are needed for the proposed service trial, platform work and learning support.

Three separate budget approvals would not make ninety fit within eighty. Removing the eight-day reserve would still leave eighty-two and would breach the supplied service-protection condition. The team instead compares a smaller whole and device-only continuation.

The smaller configuration preserves current service and the reserve. Its eight-day trial envelope must include a complete bounded preparation and, only when separately permitted, initial use and interpretation. The platform subset and targeted learning must be sufficient for that actual service scope. If they are not, seventy-eight is merely the cost of an inadequate fragment.

Two of the six platform days preserve device-compatible interfaces and maintenance instructions. Only four remain for the service-specific subset. Retaining the device fallback therefore postpones a two-day service-diagnostic enhancement. These two fallback days are already inside the seventy-eight; they are not the two unallocated days. The fallback remains available through the first staged decision under the case’s supplied conditions. Keeping it longer requires its own assessment.

The two unallocated days are not counted again as guaranteed incident reserve. They also do not prove that each critical day’s staffing or required skill is available. The capacity owner must resolve any such material collision before a dependent allocation.

In a constructed timing variant of the seventy-eight-day configuration, the only analyst qualified for the initial customer interpretation has eight working hours available on Tuesday. Current service needs six; the interpretation needs four on that same day. The customer cannot yet accept a later result, and no qualified substitute is available. The proposal demands ten hours from an eight-hour day even though its monthly total remains seventy-eight. Two unallocated engineer-days elsewhere in the month do not supply qualified Tuesday hours.

The capacity owner returns this timing conflict before the dependent trial-use allocation. A changed customer deadline or a qualified substitute could permit a revised schedule; without either, defer that use and reconsider the service proposal. The monthly arithmetic, protected reserve and costed fallback remain valid. The collision concerns later customer interpretation, not the separately authorized four-day internal preparation.

At the present decision, the Board authorizes only four internal preparation days, taken from the eight-day envelope. The larger eighteen-day development configuration remains conditional. This four-day choice displaces a different four-day device-diagnostic improvement; it is not the two-day cost of maintaining the fallback.

The platform provider, learning participants and service owner must supply their separate results when later realization is selected. OCE.9 can guide a complete bounded organization-capability increment; the applicable HCD contribution establishes the needed learning or transfer result. A platform tool and a training attendance record do not establish the organization’s ability to deliver the promised service.

The capacity calculation is not a complete economic appraisal. Customer time, vendor charges, data-use permission, financing and consequences for affected parties remain separately material conditions. If complete costing already makes the feasible service alternatives unattractive, device-only continuation can settle the choice without commissioning a trial.