MMP.21:5 - Archetypal Grounding

The following constructed cases expose different comparison questions. Their calculations are not observations of a team’s performance.

MMP.21:5.1 - Compare centralized calculation with combined local summaries

Two teams must report the mean of all their measurements. The proposed arrangements are to send every measurement to one calculator, or to compute a summary in each team and combine the summaries. All values have the same meaning and units, and every included measurement has equal weight.

Represent a finite list (x=(x_1,\ldots,x_n)) by

[ T(x)=\left(\sum_{i=1}^{n}x_i,\ n\right). ]

Combine pairs by ((s,n)\oplus(t,m)=(s+t,n+m)). For concatenation of lists (x) and (y),

[ T(x,y)=T(x)\oplus T(y). ]

Both components follow from adding the sums and counts. Pair addition is associative, so repeated regrouping preserves the summary. For a nonempty combined list, recover the mean as total sum divided by total count. This supplies the composition and recovery needed by the parallel arrangement.

With lists ((0,4)) and ((10)), the summaries are ((4,2)) and ((10,1)). Their combination is ((14,3)), giving (14/3), the same mean as central calculation. Averaging the two local means instead gives ((2+10)/2=6), answering a different weighting question.

The mathematical comparison supports using sum-and-count summaries when this mean is the receiving result. Application requires consistent inclusion and weighting rules, with every included record assigned to one team and counted once. The algebra uses exact addition; a rounded implementation needs the relevant numerical error comparison. Whether the two teams use those rules needs grounds from their work.

Now the recipient asks how many measurements exceed (3). Replacing ((0,4)) by ((2,2)) leaves the local sum-and-count pair unchanged, and leaves the combined pair ((14,3)) unchanged, but changes the requested count from two to one. No rule using only that pair can distinguish the cases. The earlier mean-equivalence remains valid; the new question needs another retained quantity or a return to the measurements. The method decision must not treat the old summary as a substitute for all uses of the records.

MMP.21:5.2 - Compare parallel checks with their shared capacity exposed

A team considers one automated test bench versus two independent benches. Two preparations can run independently from time zero, each with its own analyst. Preparation A takes three minutes; preparation B takes two. Each subsequent check occupies a bench for four minutes. Both completed check results are required for one minute of final assembly.

For this calculation, durations are fixed, the work is nonpreemptive, and setup and transfer times are zero. Benches and the final assembler are available when needed, with no competing work. Checks initially require no continuously attending operator. The required completion time is at most ten minutes.

With two benches, check A runs from minute 3 to 7 and check B from 2 to 6. Assembly runs from 7 to 8. The model admits completion at minute 8.

With one bench, the two checks cannot overlap. A feasible schedule is B from 2 to 6, A from 6 to 10, and assembly from 10 to 11. No schedule finishes earlier: the bench cannot start a check before minute 2 and must perform eight minutes of check work before the final assembly minute. Thus eleven minutes is both a lower bound and an achieved value.

The one-bench arrangement fails the ten-minute criterion under these premises. The two-bench arrangement passes that criterion in the constructed schedule. Whether acquiring or allocating another bench is worthwhile remains a choice involving its availability and other burdens. The calculation does not supply those missing facts.

Changed premise. Both checks now require one qualified operator throughout, and only one such operator is available from minute 2 onward. Add a capacity-one operator constraint to the model. Two benches no longer permit overlap: there are still eight exclusive operator minutes, no check can begin before minute 2, and assembly follows both checks. The eleven-minute lower bound applies again and the same serial schedule attains it.

A hardware-only proposal therefore does not repair the deadline under the changed condition. The useful next comparison concerns an available arrangement that changes the limiting condition, or a justified change of requirement. Merely redrawing two parallel lanes leaves the conflict in place.

MMP.21:5.3 - Compare orders by the result a later action consumes

A publication team proposes two arrangements for an edit and a review: edit then review, or review then edit. The required result is that the released artifact is the revision to which the review result applies. Review quality is a separate criterion; this comparison concerns revision correspondence.

Use state ((v,c,p)): (v) is the working revision, (c) the reviewed revision, and (p) the released revision. Initially the state is ((0,\bot,\bot)), where (\bot) means none. Model an edit (E) as incrementing (v), a completed review (K) as setting (c=v), and release (P) as setting (p=v). No other operation occurs in the initial model.

Both orders finish with working revision 1. A model retaining only (v) would make them look equivalent and lose the distinction needed by release. The separating trace rejects the second ordering for the stated criterion.

Now the environment permits an additional edit after review but before release. Even the first ordering admits

[ (1,1,\bot)\ \longrightarrow\ (2,1,\bot)\ \longrightarrow\ (2,1,2). ]

Its earlier result depended on excluding this intervention. The team also offers an arrangement that retains an immutable copy of the reviewed revision and releases that copy. In the same situation it releases revision 1, giving (p=c=1), while the workspace contains revision 2. This arrangement satisfies the revision-correspondence criterion if the copy and its review association are actually preserved. It leaves a different question: is releasing revision 1 still useful and permitted, or does the receiving work require revision 2? C.39.RQ and C.32.MWA.PP retain that criterion and trade-off rather than silently replacing it.

The comparison supplies a condition for the release arrangement, not evidence that anyone performed the review or retained the copy. If source-copy retention or release selection needs implementation, that construction remains to be done.

MMP.21:5.4 - Use a mathematical construction to change how work is divided

• Situation: A repeated calculation gathers all measurements in one place, while the measurements are already available to several teams.
• Question: Can the teams return smaller contributions that preserve the required answer, and what must change when the recipient asks a different question?
• First useful result or blocker: A proposed distributed procedure with a derivation of its preserved answer and its resource consequences, or the information the proposed summaries lose.
• Start with: C.39.RQ for the receiving requirement, MMP.21 for the comparison, and MMP.22 to turn the mathematical construction into a changed procedure.
• Stop or return: Retain the current procedure when the new one has no worthwhile benefit. A changed required answer returns to the summary and recovery construction; if a team’s capability or support changes, reconsider the affected allocation or support before relying on the procedure.

1. Choose the answer to preserve. The recipient needs the mean of all included measurements, each with equal weight. The records have the same units and meaning. C.39.RQ retains those conditions when a team proposes sending local means instead of individual measurements.

2. Compare the mathematical constructions. MMP.21 exposes the weighting difference. For local lists (0,4,0,4) and (10,10), the local means are 2 and 10. Averaging those means gives 6; the mean of all six measurements is 28/6, or 14/3.

MATH.17 supplies an operation on summaries: represent a list by its sum and count, and combine two pairs by adding their respective components. This operation is associative. MATH.18 supplies the interpretation question: does summarizing a concatenated list give the same result as combining its summaries? Here both routes give the total sum and count. Division recovers the required mean when the total count is positive. The construction preserves this answer for any partition under the stated inclusion and weighting rules.

3. Construct the changed way of working. MMP.22 now uses that mathematical result to propose local sum-and-count calculation followed by pair addition and division. Every included record must be counted once; each team must have its assigned records and deliver the pair before the result is needed. These are requirements on the changed procedure and its support. The algebra does not establish that the teams already have those capabilities or connections.

For k nonempty teams and N scalar measurements, the proposal transmits 2k scalar values instead of N, apart from any identifiers and communication overhead. It can reduce that transfer when N exceeds 2k, while adding local calculation and coordination. In the small example, four scalar values replace six. C.32.MWA.PP and C.11.MV compare that contribution with the total burden; equality of the mean alone does not establish practical improvement. Rounded computation needs its numerical error allowance.

4. Describe and introduce only the supported change. A.3.2.DE makes the selected procedure and its conditions available to its users. B.1.5.CM addresses a claim that the participating Methods constitute a Method whole when that claim matters. A.3.1.MI addresses introduction into practice; A.3.1.WT supplies a trial only when the result it could obtain is worth the work. Existing adequate grounds can suffice for the decision being made.

5. Reopen the construction when the required result changes. The recipient now also needs the number of measurements greater than 3. Replacing the first list by (2,2,2,2) preserves its sum and count, hence the overall mean, but changes the total above 3 from four to two. The old pair cannot supply the new answer.

MMP.21 returns this separating case to MMP.22. Add a local count above 3 to the summary and combine those counts by addition, or retain access to the original records. The former mean calculation remains valid. Here three values per team would again transmit six scalars, so the original reduction in their number disappears. A later change of threshold can require a different retained contribution again. C.39.RQ preserves the revised requirement, while A.3.2.DE describes the revised instruction.