Library.Reference:6.4 - The same organization can require different performance and provision
Consider a prospective diagnostic service with two accepted reports due by hour six of an eight-hour day. Each report needs two hours of analyst preparation followed by one hour of an authorized expert’s judgement and acceptance. The analyst has eight available hours. The expert has four allocable hours with no further fixed calendar restriction in this constructed case. The protocol in use is qualified, and the expert is authorized to accept both reports.
The expert must also perform one hour of support that keeps the service usable and one hour of development of the reusable diagnostic protocol. A feasible schedule gives the analyst preparation at hours 0–2 and 2–4, the expert support at 0–1, protocol development at 1–2, and reviews at 2–3 and 4–5. Both reports arrive before hour six; expert occupancy totals four hours.
Delivery, support and development are different functional contributions made by the same person. Their three rows establish no three organizational units or management ranks. The reusable report Method also differs from the two planned performances and the separate protocol-development work. Developing a protocol changes a Method used in delivery; that development need not be a constituent of each report-producing Method. Yet all three kinds of contribution draw on the same expert capacity. Their distinct boundaries must remain connected in the service account.
Change the case class: additional evidence now makes each qualified review take 1.5 expert-hours. Keep the reporting promise, preparation and authority unchanged. Expert demand becomes 3 + 1 + 1 = 5 hours against four available. A total of analyst and expert labour would hide the shortage: spare analyst time cannot supply the qualified expert judgement. An unchanged organization chart therefore carries an unavailable promise.
One bounded alternative defers the hour of protocol development. This works only if the current protocol remains qualified and the development commitment permits a one-day delay. Keep analyst preparation at 0–2 and 2–4; schedule support at 0–1 and reviews at 2–3.5 and 4–5.5. Both reports meet the deadline and expert occupancy is four hours. Today’s service is obtained by moving development into another period. This is not a sustainable recurring arrangement by arithmetic alone. If the protocol must change before today’s reports can be accepted, deferral fails at that dependency despite the hours fitting.
A different arrangement obtains one complete review from a qualified external provider. The provider must be able to receive the prepared material, return an acceptable result before hour six and supply the acceptance contribution allowed by the service’s rules. Count transfer, preparation, coordination and checking in the arrangement. The internal expert’s retained review, support and development require 1.5 + 1 + 1 = 3.5 hours, leaving at most 0.5 expert-hour for additional coordination and checking; those activities must fit their windows as well. That capacity remainder is a necessary condition, not a completed external-service schedule. The provider relation can support delivery without making the provider organization part of the internal team. If the provider cannot meet those conditions, state which commitment the available arrangement can meet. If you have authority to reduce or defer the promise, use it under the agreed terms. If another agent must decide or consent, seek that decision or consent. If the authority to change the promise is unclear or missing, state that limit and keep the change conditional.
Replacing judgement with an automated field-completeness check changes the supplied result. Complete fields do not establish the diagnostic conclusion the recipient needs. That proposal returns to the subject Method and acceptance criterion, whereas qualified external review returns primarily to provision, capacity and authority. The same slot in a route can conceal different contributions.
OPS.11.1 in Operations Management explains receiving completion, route, occupancy, provision and authority. STR.14 in Strategy reconciles the simultaneous service, support and development commitments. To develop the arrangement, use FPF C.32.MWA.PP:4.5–4.8: change the relation that makes the missing contribution obtainable, follow the moved burden, place qualified work in its receiving windows, and compare the complete alternatives. Its :4.9 gives the selected realization its remaining contribution and conditions. A proposed schedule or provider choice still needs effective commitments before performance can rely on it.
Here the changed premise is work content and qualified resource demand; in the controller it is the dynamic command interface. Both changes are found by returning from the required result to the contribution and relation that could defeat it. The resulting calculation then changes the feasible whole. System composition can remain intact in either case while the Method connection, permitted interface, provision or promise changes. C.32.MWA connects these accounts; the subject Methods supply the operations that make each conclusion warranted.