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-18 23:40:20 UTC

OPS.2:0 - Use This When

Use this pattern when the same continuing Work is being called a project, process, case, workflow, queue, programme, or control loop and that choice changes coordination. Enter when one view hides a decision that another exposes: a process map may not show a permissible next action for an exceptional case, a project plan hides recurring service, a case file hides aggregate load, a queue hides commitments and subject state, or a loop diagram hides the operating account.

Choose the view and coordination method that answer the current question. For example:

For decision D about subjects S at grain G, use view V and coordination Method M under conditions C. If another view must be used with it, specify how their subjects correspond, which commitments and handoffs connect them, which rules apply and when to stop.

You may select one view or several compatible views, or keep the current arrangement when the existing coordination already answers the question.

A disagreement about how to coordinate the Work or a question the current view cannot answer gives a reason to use this method. Establish the structures, relations, performed Work, plans, control claims, authority, safety or evidence on which the selected decision relies through their applicable FPF or specialist methods.

Do not use OPS.2 to classify Work into a universal natural kind, infer performed Work from a plan, select a structure by diagram appearance, or prescribe one lifecycle. If the question concerns only the identity of an already selected structure, mathematical lens, or architecture view, use A.22, C.29, or C.30.LCA directly.

OPS.2:0.1 - Working Distinctions

Name used hereMeaning
WorkActual dated activity under its governing FPF pattern, including the enacted Method. Intended activity belongs to a plan or proposal. A management view describes or coordinates Work; it does not create another Work occurrence.
viewpoint questionThe question a view must answer for a named user and decision, such as dates and allocation, repeatability, changing subject state, aggregate waiting, or feedback and rate separation.
Work-management modeThe selected use of one or more descriptions and coordination Methods for the current Work and questions. The same Work can be coordinated through different views and Methods.
project viewA description emphasizing a time-bounded undertaking, commitments, intended results, decisions, dates, WorkPlan content, allocation, dependencies, and closure conditions.
programme viewA description coordinating several projects or change commitments and their dependencies or intended contributions. Claims about a containing System, a benefit or decision authority need their own grounds.
process viewA description emphasizing a recurring Method, inputs, results, repeated order or constraints, and control points. It does not prove that every occurrence follows the description.
case viewA description organized around a changing subject, current facts, commitments, discretionary or constrained next Work, exceptions, and closure conditions. The case is not its file.
queueing viewA description of eligible items, membership, order or service relation, waiting, arrival, departure, resource demand, and policy for one receiving question. The queue is not a board column.
control-structure viewA current FPF description of one selected control structure and its actual observation, actuation, reference, supervision, feedback, and rate-relevant relations. Use it when the decision depends on identifying that structure and its relations.
coordination MethodA reusable way of coordinating the Work under stated conditions. A view can expose what the Method needs without being that Method.
mixed-mode decisionAn explicit co-use account stating subject correspondence, scope and grain, commitments, handoff or coexistence conditions, decision rules, conflicts, and stops among unlike views and Methods.