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

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:45:20 UTC

A.1.STM:4.2 - Keep role, holder and future description distinct

The SoI role relates a System to the product use and common purpose explained in section 4.1. A holder is the actual System occupying that place; a description states what the participants intend or believe about it. These can be discussed together without treating them as the same object. An existing pump remains the project’s SoI when it fails a performance test: success is what the participants seek, not a condition that makes a failed SoI disappear from the undertaking.

Use ordinary role wording under A.2:4.9 while it is enough. If classification matters, define the local system-role kind under A.2 and C.3 through its System candidate domain and the work-facing distinction the project needs. For a SoI classification, the criterion must express that product-use and cooperation relation together with the designation grounds. A rig investigated only to support another system does not thereby take that other system’s role in the wider project. A criterion that selects merely whatever an observer studies answers a different question. If the needed criterion or its governing relations are unavailable, retain the ordinary project account and leave that technical classification unresolved.

If assignment identity matters, A.2.1 requires an obtaining occurrence with an actual System holder under a declared species. System recognition, project designation, classification and assignment remain different claims; none is created by writing the role’s name.

A new system can be intended before any holder exists. Agree the SoI role, intended use, required characteristics and boundary hypothesis in a plan or description. Describe the intended holder, its proposed identity rule and how later instances would be recognized. Before identity inception, this is prospective content, not an actual System or assignment occurrence. A.15.PROD separates production participation, the first satisfaction of the entity’s identity rule, and completion. After inception, relate the actual holder to the earlier description and evaluate the claims needed now.

Design reasoning also works with types, variants and repeated provision. A project may intend a series of systems satisfying a common specification rather than one already named individual. State the common intended use, the distinguishing requirements and what counts as one resulting instance; track actual holders as they become identifiable. The specification, the kind it describes and a collection of instances do not thereby become one System. Where materially different SoI families have different users or use conditions, preserve their separate SoI accounts before comparing shared builders. A vague umbrella such as “equipment” does not supply that comparison.