Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-19 00:00:20 UTC

OPS.2:11 - SoTA-Echoing

The question is how to coordinate evolving case work with recurring procedures and shared resources. A strong alternative already integrates them. CMMN 1.1, §4.1 and §5.4.9 supports runtime case planning, procedural subwork and authorized planning roles. An adaptive project arrangement can likewise revise its plan when facts change. Both can already support coordination that changes with the case.

At PumpWorks, such an arrangement can retain T8’s procedure while a case manager selects incident diagnosis. If its case file, resource policy and decision rights also settle the shared E18 allocation and preserve the field-contact window, use it unchanged. OPS adds no gain by displaying the same decision in more tools. The remaining question arises when the case manager’s chosen action, the queue’s oldest-ready rule and the resource owner’s active limit produce incompatible starts. Sections 4.1.5 and 4.1.8 connect to OPS.17 to recover and compose the actual rules; section 5.2 makes the incident exception govern order without overriding eligibility or increasing the limit. The changed contact condition retires that exception while recurring validation survives.

This synthesis costs rule recovery, agreement on the one disputed decision, mapping of the shared subject and evidence, and maintenance of that correspondence. It can be more expensive than using a capable integrated case model, especially when one owner already maintains all relevant policies. Its conditional gain is avoiding an unsupported cross-view action when those policies were separately governed. Stop adding views when they cannot change the decision or its grounds. Retire a duplicate view when its continued use no longer warrants the cost of keeping it in agreement.

CMMN shows how planned and discretionary work can coexist. The DCR tradition supplies explicit conditions and responses. For the operating case, use applicable domain evidence and establish any required external authority from the arrangements or decisions that grant it. The Kanban Guide supplies the bounded flow-policy contribution. FPF C.43 supplies the ordinary control account; A.22, C.29, C.30.LCA and the applicable temporal patterns govern selected structures, mathematical representations and stronger control claims. Reopen when the integrated incumbent already settles the same conflicts more simply, or a new case defeats a relied-on composition rule.