A.1.STM:4.1 - Establish the project system-of-interest, its use and the participants’ agreement
Start with the intended use because it tells the participants what their internal choices must accomplish. Describe the operating situation, its time or period, the affected participants and the changes or maintained conditions that matter to them. Ask what would be lost if the proposed system were absent, unusable or no longer maintained. The answer can concern a desired change, a condition that must continue, or a harmful effect that should cease. “Produce the deliverable” is insufficient while nobody can say what obtaining that deliverable is supposed to enable.
Follow the intended contribution toward its recipients: what will use the result next, and what will that use change or keep possible? Set out the boundary of the system being considered at the operating time, provisionally when the design is still open. From that boundary, move upward to the larger physical or operational whole of which it is, or is intended to be, a part. Identify the other parts and explain how their joint functioning produces the receiving result. For a pump, examine the water-supply installation: the pump’s contribution depends on the inlet supply, downstream path, power and control arrangements that make delivery possible. This account gives reasons for the pump’s required function before the choice of its internal construction.
Continue through the levels and supported inclusions whose conditions can change the decision. A pump can be part of a pump assembly that is itself part of a station; demands on the station can constrain both the assembly and the pump. One tree need not represent every relevant inclusion. State the whole, part relation and operating time for each relied-on connection, and reuse an adequate account already obtained for it.
Keep the two relations visible. Moving along receiving transformations follows what affects or enables what. Moving upward through system composition follows which system is part of which larger system at the time considered. A using system need not contain the used system, and a manufacturer is not its product’s suprasystem merely because it makes the product. A manager, owner or larger project is also not an encompassing System by title or scope. A.1 and A.14 govern a relied-on composition claim; C.30.STRAT helps when a level word still hides its meaning.
When the larger functioning whole or its composition is unknown, keep that question open and obtain the missing account. Inspect the operating arrangement, consult those who understand it, or investigate a proposed configuration. Describing neighbouring objects and their interactions can supply evidence for this work; it does not complete the upward move. State which function or construction judgement remains unsupported and continue inquiry or other work whose grounds are available. A.1:4.2’s possible participation in a larger assembly is a recognition condition; it does not identify the containing system and functioning needed for this project decision. Neither that condition nor the absence of current knowledge removes this inquiry.
Use the larger whole’s functioning to propose how the system’s functioning or other intended trajectory could meet the need. Refine the proposed SoI and its boundary, and describe it as a black box: what it encounters, what it does or permits, which conditions it must tolerate, and what its users or other affected participants regard as success. A functional name such as pump, learning aid or diagnostic instrument is a useful hypothesis; it does not settle the physical boundary or the A.1 system criterion.
For a system still to be created, this is a possible future operating situation. Describe the proposed holder, interactions, receiving changes and conditions without asserting that the holder or effects already exist. A desirable outcome gives a reason to investigate a design. Explaining how it could occur requires a mechanism and conditions: for example, how flow, pressure and the surrounding installation together could deliver water at the required outlet. Qualify that hypothesis with suitable engineering grounds and revise it when tests or later use disagree. The purpose alone supplies no causal connection.
Compare the participants’ accounts. Ask each relevant team and external participant to explain the proposed SoI in the same use situation and to locate its own contribution. Differences become actionable: one team may describe the provider organization, another the delivered system, and another the report about it; two teams may intend incompatible configurations under the same name. Resolve the consequential differences through inquiry, conversation, option comparison and, when needed, experiments or prototypes. C.11 helps choose among formed alternatives; it supplies neither the creative formation of those alternatives nor proof that several participants understand and accept the same choice.
Seek a working agreement adequate for the decisions being made: the systems-of-interest and project contexts involved, intended uses, relevant boundaries, success conditions and the contributions that rely on them. Participants may retain different interests. State a consequential unresolved disagreement and who can settle the affected decision; do not present a single chooser’s designation or a shared document title as evidence that agreement already exists. The useful result is a supported, revisable basis that the participants can use together. Inquiry and negotiation may still leave an important designation or agreement unresolved.
A project can seek several systems and other results. For example, a project may supply independently identifiable instruments to two laboratories, together with explanations and operator preparation. Recover each receiving use and the shared conditions that constrain the current decision. Neither the project label nor this plurality makes the instruments, explanations and preparation one System. When the question concerns one instrument, ordinary reasoning can follow that SoI alone while retaining any dependency that matters.
Different product undertakings can have different SoIs and boundaries. A supplier’s engine, an integrator’s aircraft and an operator’s transport installation need not be the same entity. Recover the usable supply, recipients, product decisions and fitness obligations at each boundary, then agree the contributions and conditions used in the joint work. The customer may specify the engine’s whole design and intended use; the supplier need not control the customer’s product strategy. The engine’s receiving use constrains its fitness without making its supplier responsible for every later aircraft. A separate project, budget or contractor for the same organizational work leaves its product-use basis in place.
Keep these answers distinguishable:
| Expression | What it selects | Practical consequence |
|---|---|---|
| System-of-interest (SoI) | The system whose intended use and expected benefit supply the common purpose of the relevant creator cooperation. | Recover that use, its recipients and contribution conditions. One or several product SoIs can constrain organizational work; each future system remains described until it exists. |
| Current subject of inquiry or local work; system-in-hand for a system | Whatever must be understood, obtained or changed for the present decision. | A creator can be fully engineered and locally accepted while the product SoI and its use continue to justify that work. Methods, epistemes and other subjects retain their own names. |
| Required functioning | The behaviour or contribution needed in use, such as circulating coolant at a required rate under stated conditions. | Supplies a demand to investigate; it does not yet select a construction or establish an actual effect. |
| System named by its function | The kind of system sought for that contribution, such as a coolant circulator. | Opens the search for suitable systems and constructions. This functional classification differs from the system’s role in the project. |
This Library uses system-of-interest (SoI) for the system identified in relation to the undertaking described below. The meaning here keeps the useful product and its creators’ common purpose in view. When another source uses system-of-interest merely for whichever system an observer investigates, recover that source meaning explicitly; use system-in-hand for the local system in the present account. “Our system” needs the relation that makes it ours: what we make, change, operate or provide.
A component, instrument or machine can be the SoI of a distinct product undertaking when it is supplied for use to identified recipients or a known class of recipients, with a bounded product decision and obligations for its fitness. For example, a test-rig manufacturer supplies a usable instrument to laboratories. In the pump cooperation, a laboratory developing its test capability remains a creator, and its rig can be the local system-in-hand. The actual supply and obligations explain the distinction; incorporation, internal transfer prices, a contract or the word project do not settle it.
An organization being created or changed remains a creator with its own engineering object. A new team, factory or business can have a complete design, agreed boundaries, a budget, a contract and finite acceptance. Its product or products still supply the SoI for this work. This applies equally to an internal team, an external consultant and a supplier of a ready-to-operate enterprise. Valuing or selling the organization makes it an object of an investment or transaction; its price, asset value and ownership rights do not replace the useful use of its products.
A changed product purpose requires reconsidering the sought results, recipients, boundaries, funding basis and dependent agreements with those entitled to change them. Participants may develop another offering or end one that is no longer justified. Make that decision explicit. A new label for the same organizational work changes none of those grounds.
A.1.STM:4.1.1 - Develop a creator from the use its products must support
For work that creates or develops an organization, connect three answers: what product use and benefit must become possible or remain possible; what the creator must be able to do for it; and what local result this work will deliver and how it will be accepted. Use this connection in the choice and provision of work. Reuse adequate existing answers; a separate form or a fresh account of the entire enterprise is unnecessary.
- Name the product use that gives the work its reason. State the required change or preserved condition in use, the recipients and conditions that can alter the decision. For a shared creator, name the products or application classes whose demands affect this choice. Necessary accounting, maintenance, learning, funding and future capability can deserve provision through the work they enable; proximity to a product drawing is not the test.
- Derive the needed capability. Explain what the creator must reliably provide under the expected workload and conditions: relevant Methods, people, means, access, cooperation and authority. Retain the creator’s own boundary and architecture questions. An agreed purpose gives a reason for that capability; it does not establish the mechanism, available resources or people’s ability to perform.
- Choose a finite local result and its acceptance. State which capability, or bounded contribution to it, this work must establish and what evidence can establish it now. Acceptance of an installed machine, a research report, a prepared team and a functioning workshop answers different questions. If workshop capability is promised, establish that the needed Methods, means, people and handovers can work together under the agreed conditions. A component delivery can close while the wider capability remains open.
- Make provision and trade-offs real. Obtain the resources, access, time and authorized agreements that the chosen capability requires. Where products compete for shared capacity, compare the affected uses and commitments together. State who may change the allocation or accept the loss; a local manager can decide within delegated authority, while a loss outside it goes to those entitled to decide. Neither one product’s improvement nor one department’s metric settles what happens to the others.
- Close this work at its agreed scope and retain the receiving connection. Judge the local result against its actual acceptance basis, including the evidence sufficient for the promised capability and the declared uncertainty. Do not wait for every future product to operate. Keep the expected product effect conditional on its remaining contributions and use conditions, and state which later observation would reopen the capability or product decision.
Unknown future uses can be represented by application classes, scenarios and explicit hypotheses. When the receiving result is an episteme or another non-System subject, keep that result and its use explicit; leave a needed systemic designation open instead of filling it with the creator.
Research may establish that a proposed benefit or capability is infeasible; a well-grounded negative result can support revision or stopping. Judge an independent research result by its epistemic question and acceptance criteria. When commissioned to inform a capability decision, also assess its fitness for that decision. Accepted knowledge does not itself establish the capability it investigates. A theorem, historical explanation or openly reusable knowledge needs no invented physical SoI or immediate commercial application.
Keep provision and benefit connected but distinguishable. A customer, user, payer and investor can be different participants. Funding, an internal allocation, income or an asset sale can make work possible without establishing product usefulness; a justified useful result can precede revenue or rely on subsidy. Give those who decide resources and acceptance the relevant product-use and capability consequences, together with the rights and financial conditions of the choice.