OPS.3:0 - Use This When
Use this pattern when one card, ticket, order, object identifier, case file, event row, or status label is being asked to stand for several different things. Enter when the subject of a measure or the item waiting in a queue is unclear, an incident record is treated as the incident, a resource is treated as its availability, or two views cannot agree because they identify their subjects differently.
The first useful move is to resolve one decision-bearing subject and the claim needed about it. An existing account or a short explanation can carry this result:
Subject
Shas identity conditionI. The decision-bearing claimQaboutSand its relationsRis qualified for time or horizonTand supported byE. State a formal kind, represented view, governing rule or missing condition when the receiving use depends on it.
Repeat for distinctions that can change the decision or the grounds for a conclusion the user needs. Stop with an account of the relevant subjects and their relations.
Use the method when a record label, metric denominator, queue item, or “work object” has several plausible referents. Assurance is claim-specific: entity kinds, Work, relations, commitments, state, evidence, event occurrence, control participation, resource availability, and representation each retain their FPF or specialist tests.
Use an existing subject pattern or an adequate subject account when it answers the identity or relation question. Add the Operations correspondence needed for this decision. For example, a ticket number may identify the record while the field installation and the incident have separate identities.
OPS.3:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| operating subject | The entity or relation the operating question concerns. It may be, for example, a case subject, material, a service or an account whose identity or state matters to the decision. |
| case | One bounded continuing Work situation organized around a named subject, commitments, current facts, evidence, authority, permissible next Work, and closure conditions. The case is neither its file nor every Work item within it. |
| Work occurrence | Actual dated Work admitted through its governing pattern. A ticket, plan, or event record does not establish that Work occurred. |
| Work item | A bounded item admitted to a selected workflow or coordination account with stated start, finish, subject/result relation, and receiving use. |
| queue membership | An obtaining relation placing one eligible item in one named waiting or service order under a policy and time window. A column or list is a representation. |
| buffer membership | An obtaining relation to a bounded protective or coordination reserve with purpose, policy, extent, and receiving use. It is not inferred from spare inventory or a board column. |
| resource relation | A relation that matters to the provision or use of a resource. For planned work, identify what is available, accessible or allocated under the stated conditions. For a claim about performed Work, identify the support it received or the resource it consumed. |
| event | An occurrence or change under its subject rule and time boundary. An event record or timestamp is evidence about it, not the event by identity. |
| record or trace | A claim-bearing episteme about subjects, Work, events, relations, or decisions, recorded on an identified carrier. Its claims have stated sources and scope limits. |
| state claim | A qualified claim about one subject at a stated time or horizon with provenance, uncertainty and conditions; include authority where the claimed state or receiving action depends on it. A status label is one possible representation. |
| control participant meaning | Observer, controller, plant or supervisor as the participant meaning in an actual control relation. Qualify a selected control structure when that claim is needed. The label does not establish that the relation obtains. |
| operating-subject account | The smallest relation-specific set of identities, direct relations, records, state claims, and any limits the decision maker needs to know. |