SYSE.1 - Choose and Reopen the Project System-of-Interest
Status: Stable
SYSE.1:1 - Problem frame
Use this pattern when participants use a familiar project name but cannot say which system’s intended use gives their joint work its purpose. A product, tool, provider, organization, component or desired effect can occupy the discussion while referring to different subjects. The choice matters to use, architecture, realization, evidence and resource decisions.
The first useful result is a project-system choice account: the actual System or intended referent selected as the system-of-interest (SoI), its extended enterprise, agreed undertaking, intended use or withdrawal from use, the grounds for the choice and what would reopen it. When the immediate engineering subject differs, identify that subject and its bounded result alongside the product it serves.
Recover the intended use and any assumption that could change the choice. A.1.STM explains why receiving use and encompassing functioning ground construction and provision decisions. A contributor can use a provisional answer for the next concept question. Before joint work relies on it, compare the participants’ referents and contribution connections through §4.4.1. Reuse an adequate existing account.
A manufacturer may need to improve its planning organization while a vendor supplies a software product. Naming both projects does not settle their SoIs. The manufacturer’s product remains the common reference for work on its creator; the vendor’s independently supplied software can be its own SoI. Both the organizational work and the software supply can have finite results and acceptance conditions.
Use this pattern when a System designation is needed for the current coordination. Keep another recognized subject—such as Work, a Method, capability, state, material portion, description or research question—under its direct pattern when that answers the decision. Use A.1.SCR for unresolved System recognition. A System already identified for engineering can proceed to SYSE.2 without first being renamed the SoI.
At a consequential use of system of interest, our system, product, solution or the source phrase target system, ask which system’s useful functioning grounds the cooperation and which subject the local work changes. SoI is the product System’s role in an extended enterprise organized to create, change, sustain in use or retire it; system-in-hand names the immediate System being worked on. Explain what “our” refers to and who is responsible for the local result. Several named products or classes of future use may jointly ground a shared creator’s development. Their differences and competing demands remain visible.
SYSE.1:2 - Problem
Project names are chosen early, often before outside use, engineering boundaries, and realization constraints are understood. The first plausible referent then becomes an unstated premise in later decisions. A purchased tool can displace the product it serves; an organization can become the proposed SoI merely because the current project changes it; or a desired state can be forced into a System because the project is organized around achieving it.
The opposite error is also common: a useful tool, software product, or component is categorically excluded even when its own product project legitimately selects it. Compare referents for the current project and keep the choice revisable as understanding of the problem and solution changes together.
SYSE.1:3 - Forces
| Force | Tension |
|---|---|
| Coordination and revision | Contributors need shared product grounds now, while new evidence may change them. |
| Outside use and technical discovery | Outside use justifies the choice, while architecture and realization discoveries can revise the use and boundary. |
| Actual and intended Systems | Brownfield work can concern an existing System, while new development may only have an intended referent in decision or plan content. |
| Products and local projects | Several projects can serve the same product; independently supplied products can have different SoIs while their contributions and commitments remain connected. |
| Candidate breadth and decision cost | A single familiar candidate hides alternatives, while an exhaustive catalogue delays the next useful question. |
| Stable language and ontic precision | A shared designation aids communication, while agreement on a name alone can leave the referent and contribution connections unresolved. |
SYSE.1:4 - Solution
SYSE.1:4.1 - State the current project decision
Begin with the extended enterprise and decision that need a shared reference. Recover the participating organizations, the agreements organizing their joint work, and the agents who may establish or accept the objectives and commitments. An unknown or proposed enterprise remains unresolved or proposed; independently supported engineering can continue. Recover:
- the product or products, the agreed creation, change, sustaining in use or retirement, and the intended use or withdrawal from use that justify the work;
- the System or other subject the local work must create, change, sustain, retire or investigate;
- the contribution needed from that work and the conditions for accepting or stopping it; and
- the plan or decision that needs the SoI designation now.
For work that creates or develops an organization as a creator, retain the SoI on the product side. Name the organization as the creator being engineered. Its use, functions, structure, characteristics, realization and own creators can all require full engineering. The SoI name is not a prerequisite for those operations. The product and creator retain those roles when the organization is given a new label or the work is assigned to an external consultant under a new contract.
The local project can finish when its agreed contribution has been established. For example, a planning-system project can establish the ability to produce usable plans under specified order changes before the corresponding products enter service. Product usefulness, organizational capability, software installation and acceptance of a limited supplier contribution have different evidence. Preserve the responsibility and limits of each undertaking.
For a shared creator, retain the products or classes of future use that govern its capability, including differences that compete for the same resources. Do not select one convenient product to hide that competition. An unsettled future use can require research into concrete possibilities; do not invent a finished product to complete the account. Research retains its own epistemic result and stopping conditions.
A supplier can have a different product. A machine can be its maker’s SoI and a creator at the customer’s factory; an engine can be its maker’s SoI and an aircraft component. Recover the extended enterprise organized for that supply, the recipient or class of applications, substantive decision boundaries and acceptance obligations. The customer may specify the design and use. The supplier need not control the whole product strategy or accept responsibility for every larger system. These facts inform the judgement; the existence of a separate contract alone does not make the same servicing or organizational work a different product.
Keep each local project, commitment and result identifiable. A programme or portfolio can coordinate priority, resources, investment, risk or evidence without becoming one acting System. Use A.1.STM when the product purpose or its relation to the creator remains unresolved.
SYSE.1:4.2 - Recover the direct subject before forcing a System choice
Use A.15.6 when project, process, or case wording hides whether the current subject is performed Work, a
reusable Method, a selected structure, a transformation-flow structure, a changed referent, or another claim.
If that direct subject answers the decision, stop this pattern use and keep the subject under its own FPF
pattern.
When the decision does need a System, distinguish two cases:
- For an actual System, use
A.1.SCRwhen recognition is unresolved. Its constructive criterion supplies the tested System identity and boundary used in the comparison. - For a System that does not yet exist, keep the intended referent in the current plan, decision, or description. Do not describe it as an already acting System.
Recognition, choice of an engineering subject and SoI designation remain different claims. Recognizing an actual System does not determine its product role in an extended enterprise; selecting an intended referent does not make it physically present. An organization can be the immediate engineering subject while remaining a creator of the product SoI.
SYSE.1:4.3 - Generate and criticize materially different referents
Generate materially different product referents from the working situation using the existence and recognition conditions in §4.2. A product, component, tool or operating System can be a candidate when its intended use supplies the product grounds for the cooperation. Apply §4.1 to distinguish a supplier’s own product from work on the same creator under another project name.
For each candidate, compare the claims that matter now:
- the intended useful functioning and the receiving situation;
- the product boundary and its relation to the participants’ contributions;
- the participating and affected Systems;
- the part, interaction, containment, ownership, authority or other relations that can change the decision;
- characteristics, constraints, feasibility, evidence and uncertainty; and
- the assumption or observation that would defeat the candidate.
Alternatives for an organization, platform or production arrangement remain full engineering alternatives. Compare their functions, construction, obtaining ways and capability against the products or future uses they must serve. Choosing among those creators does not by itself change the product SoI.
Payment, delivery, ownership, organizational boundaries and local acceptance can inform the judgement. None alone establishes the SoI. A firm’s sale or valuation is an economic question; work on that firm’s productive capability engineers a creator. Preserve the economic question and its own evidence.
Retain several product candidates when learning can change their order or when they preserve valuable options. For several products served together, retain their common demands and consequential differences. Let the current decision, available resources and useful stop determine the comparison effort. Stop when you can ask the next engineering question and the reopening condition is clear.
SYSE.1:4.4 - Record a sufficient choice account
Start with the following content in any readable form:
Project-system choice account:
extended enterprise, participating organizations and current decision:
agreements, agents' objectives and limits of their commitments:
product SoI or intended referent, agreed undertaking and intended use or withdrawal:
immediate engineering subject and bounded result, when different:
current grounds and any main unresolved assumption:
local acceptance and receiving obligations that matter now:
reopen condition:
Include several products or classes of use where the creator must serve them together. Add alternatives, participation, authority, realization or evidence only when they change the choice or its use. A short existing explanation can suffice.
Stop when the project can ask the next concrete engineering question about the identified subject for the stated purpose. Supply SYSE.2 with that subject’s use, the product grounds it serves, the boundary question, alternatives and reopening condition. Engineering the creator does not require designating it as another SoI.
SYSE.1:4.4.1 - Establish enough common focus for the current coordination
When a decision depends on several contributors, compare their understanding through one concrete use or change. Include the participants whose contribution, receiving use or limits can change that decision. Existing compatible exchanges may supply the answer.
Establish which organizations participate in the extended enterprise and who can commit each relevant contribution. Establish from each contributor which products the joint work serves, what their work concerns, what they supply, to whom and under what conditions and limits. For each consequential connection, establish from the receiver what they expect and how they will use the contribution. A conversation, annotated case, asynchronous exchange or existing work that shows what the participants supply and expect can provide these answers.
For example, “install the planning software” and “produce a feasible production plan” can share a project name. Follow one order moved to an earlier date. Determine whether installation, current stock information, capacity decisions and the planner’s use connect to feasible commitments for the manufacturer’s products. A missing contribution can leave the planning capability unavailable even when installation is complete.
Use the available contributions to resolve a material mismatch with the party authorized to decide. Explain the selected product grounds and local engineering subject, then ask the affected contributors to use them on the same case. Enough common focus exists for this decision when those relying on it can identify these subjects, connect the contributions needed by their next action and identify any unresolved condition that limits it. They may retain different interests and preferred alternatives. Obtain permission and commitments separately where the next action needs them.
If participants still mean different subjects or cannot connect a needed contribution, retain the individual account as provisional and hold only the joint claim that relies on the unresolved connection. Name the missing answer; independently supported work can continue. Separate projects retain their own boundaries and acceptance. They can share a product SoI. When an independently supplied product has its own SoI, coordinate the receiving contribution between them; use SYSE.8 for provision or SYSE.9 for a specialist return where needed.
Keep the account aligned with the result: a provisional individual choice, sufficient common focus for a named decision, an unresolved mismatch or coordination between distinct product undertakings.
SYSE.1:4.5 - Reopen the choice from the answer that failed
Reopen the account when one of these changes the comparison:
- observed or expected use crosses the assumed boundary;
- authority or permission makes the intended change unavailable;
- an architecture candidate moves important functioning to another System;
- no feasible realization branch supports the selected referent;
- operating or assurance evidence defeats the reason for the choice; or
- a changed product or intended use materially changes the grounds of the cooperation.
A project split, new contract or changed performer can reopen local scope, provision or authority without changing the product SoI. Reconsider that designation when its product, use or extended-enterprise agreement grounds change.
An observed mismatch between contributors reopens the common-focus claim in §4.4.1 even when the individual choice remains defensible. Repeat only the exchange affected by that mismatch; reconsider the SoI designation if its product, intended-use or extended-enterprise agreement grounds have changed.
Return to the failed claim or linked claims that affect the next move. A changed use assumption may require SYSE.2 before the project focus
changes. A failed bearer or architecture candidate may return through C.30 or C.32. Reopen the
SoI designation when the evidence changes its product, intended use or extended-enterprise agreement grounds. Reopen the local engineering subject or acceptance separately when those are the affected claims.
SYSE.1:5 - Archetypal Grounding
SYSE.1:5.1 - Pumping station under flood risk
A flood-reduction project starts with the phrase “new pump”. The engineer compares the pump unit, the pumping station, the drainage-control System, and a provider arrangement. Flood-control use crosses the pump-unit boundary: positioning, power, control, discharge conditions, and downstream exposure belong to the station’s current use question. The operator, design organization and construction provider have agreed their work and decision responsibilities for obtaining the station. The engineer uses that extended-enterprise basis to propose the intended pumping station as SoI and records:
selected referent: intended pumping station
extended enterprise: operator, design organization and construction provider under the agreed responsibilities
current reason: move water under the selected flood load as part of flood-control use
main unresolved assumption: downstream exposure remains acceptable
reopen: use, architecture, realization, or operating evidence changes that assumption or boundary
SYSE.2 can now link the flood-load use claim to a station concept.
Later discovery that the proposed station increases downstream harm changes the linked use claim. It reopens
the project-system choice only when that changed claim defeats the reason or boundary used by the choice account.
SYSE.1:5.2 - Manufacturer and ERP vendor
A manufacturer, component suppliers and receiving operators have agreed the supply and acceptance obligations that organize the extended enterprises for water-supply and seasonal-irrigation installations. Its “new ERP” project begins because production plans repeatedly fail. The engineering lead compares software installation, a changed planning organization and an integrated planning arrangement. These are alternatives for improving the creator. The product grounds remain the two lines’ installations and their intended uses; their different configurations, delivery commitments and resource demands must fit the plans.
The lead selects the deployed planning arrangement as the immediate engineering subject. Its proposed local result is the ability to produce feasible production commitments from current orders, stock and capacity under specified changes. Current-information availability is the main unresolved assumption. This is enough to begin concept work without naming the planning organization a new SoI.
Before assigning joint work, she asks the contributors to follow one order moved to an earlier date. IT means the installed ERP runtime by “our system” and can supply software installation and data interfaces. The planner needs current stock and capacity information and a way to resolve conflicts between the two product lines. The stock controller expects the overnight update to remain sufficient. The independent software vendor supplies a standard ERP product and needs to preserve a supportable configuration.
The exchange exposes a missing contribution: rescheduling can use stock information that predates the moved order. Installation and software delivery alone cannot establish the planning capability. The manufacturer’s authorized decision holder retains the planning arrangement as the local engineering subject. The stock controller and planner investigate current-information and confirmation alternatives; IT identifies the required interfaces. Each contributor explains what the planner would receive, and the planner states what is still needed before issuing a production commitment. SYSE.2 can compare these arrangements while retaining the product obligations they serve.
If that information cannot be obtained, the joint planning-capability claim remains open. An independently supported interface investigation can continue. If the authorized scope covers only software deployment, acceptance can close that bounded contribution against its own criteria. It leaves the planning capability and product consequences unestablished. The smaller contract does not change the manufacturer’s product SoIs.
Now transfer the same planning-change work to an external consultant with a separate budget and completion date. The consultant may design the organization, its functions, responsibilities, tools and supporting work. Acceptance can establish its agreed capability under representative order changes and operating conditions before the resulting pumps enter service. The consultant’s responsibility remains limited to the accepted scope. The external contract creates neither another product purpose for this work nor a requirement to wait for every downstream product outcome before closing it.
The ERP vendor’s own product undertaking has different grounds: a usable software product supplied to customers under identified decision and acceptance boundaries. Recover the vendor’s agreements with contributing and receiving organizations that organize the software-product undertaking. In that extended enterprise the software can be the SoI while it is a means in the manufacturer’s planning arrangement. The parties coordinate their contributions and commitments without merging their projects or interests. A vendor label or a deployment contract by itself would not establish this independent product case.
SYSE.1:5.3 - Continuing building through several projects
For example, design, construction, operating retrofit, and heritage-restoration Work can concern one continuing building while using different plans, transformer Systems, access arrangements, and evidence. In an occupied retrofit, the owner, design organization and contractors agree the alteration and access responsibilities. The engineer identifies their extended enterprise and the continuing building as its SoI, with access during use as the main unresolved assumption.
Different descriptions of the same building can serve one project or several. One programme overseeing several projects does not become the performer of all Work. Each project account states its own reason for selecting the building and can reopen that choice when its reason or conditions change.
SYSE.1:6 - Biases to Watch
Two recurring biases matter in this decision. System inflation forces every important project subject into
U.System; use A.1.SCR and the direct-subject exit before choosing. First-candidate lock-in turns the first
plausible referent into permanent project scope; retain material alternatives and state the reopen condition.
SYSE.1:7 - Conformance Checklist
| ID | Requirement |
|---|---|
CC-SYSE1-1 | A conforming use SHALL name the current project and the decision that needs a project-system choice. |
CC-SYSE1-2 | It SHALL retain a direct non-System subject when System designation is not needed, and SHALL use A.1.SCR when actual System recognition remains load-bearing. |
CC-SYSE1-3 | It SHALL distinguish an actual System from an intended referent in plan, decision, or description content. |
CC-SYSE1-4 | The first useful account SHALL name the product SoI or intended referent, its actual or proposed extended enterprise, agreements, agents’ objectives and intended use or withdrawal from use, any main unresolved assumption and reopen condition; when the local engineering subject differs, it SHALL preserve that subject and the bounded result needed from it. |
CC-SYSE1-5 | When materially different actual Systems or intended System referents remain plausible, the account SHALL compare their decision-relevant claims and SHALL keep every non-System subject under its direct pattern rather than admit it as a candidate referent for the project system-of-interest. |
CC-SYSE1-6 | Additional account content SHALL be added only when it changes the current choice or a downstream use. |
CC-SYSE1-7 | A stop SHALL make the next use-and-system concept question askable; a reopen SHALL name evidence or a changed project condition that can alter the choice. |
CC-SYSE1-8 | Related projects SHALL retain their own work boundaries and acceptance while preserving a common product SoI where they serve the same product. A different contract or performer SHALL NOT alone justify another SoI for organizational work; an independent supplier product needs its own use, decision and acceptance grounds. |
CC-SYSE1-9 | Before coordinated Work relies on a shared focus, the relevant contributors SHALL establish a common referent and the contribution connections needed for that decision, or identify the unresolved mismatch and limit the dependent coordination. A written account alone SHALL NOT establish this result. |
SYSE.1:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Working symptom | Repair |
|---|---|---|
| Project-name shortcut | The noun in a charter or backlog is used as the selected System without a use or change reason. | State the current project decision, generate plausible referents, and compare how each changes the next question. |
| Tool or provider substitution | The immediate engineering subject replaces the product that justifies work on its creator. | Keep the product SoI, creator and local result distinct. Engineer the creator fully and accept its bounded contribution; establish separate product grounds before selecting a supplier product as another SoI. |
| Account-as-agreement | A clear choice recorded by one contributor is treated as the participants’ shared project focus. | Follow a concrete use through contributors and receivers; resolve the material mismatch or limit the coordination that depends on it. |
| First-candidate freeze | Work has started, so later use or feasibility evidence is treated as irrelevant to project focus. | Record the grounds and reopen condition with the first choice, including any main unresolved assumption; return evidence to that claim when it changes. |
| Important-subject inflation | A desired state, Work result, description, collection, capability, or transformation is called a System because the project centres on it. | Keep the direct subject and use its FPF pattern. Open SYSE.1 only if a System designation is required for the current project decision. |
| Programme-as-performer | Shared resources or one programme plan are treated as proof of one composite acting System. | Use the programme or portfolio grouping for its coordination decision and establish any System composition separately. |
SYSE.1:9 - Consequences
The cooperation gains defensible product grounds and an explicit local engineering subject. Contributors can compare what each must supply without treating a local completion as the final product result. Several projects can retain one product SoI; independent product undertakings can retain different SoIs and connected commitments. Architecture and realization evidence can reopen the claim it defeats.
The cost is visible uncertainty and, for a shared claim, comparison of participants’ understanding. Several candidates may remain open. Spend that effort where an unresolved difference can redirect architecture, provision or acceptance; reuse compatible established results.
SYSE.1:10 - Rationale
Engineering decisions need an identified subject. The system being engineered and the product whose use justifies the cooperation can be different Systems. Keeping both makes it possible to develop a creator’s full functioning and construction while using product requirements to judge its capability, priorities and shared resources.
SoI designation remains a choice under uncertainty. System recognition, a project name and a local contract do not settle it. Actual identity, intended reference, the product role in an extended enterprise and the account describing the choice have different grounds. Local acceptance establishes only the contribution it tests and can precede the product’s later use.
Outside use supplies the grounds of the comparison rather than a fixed calendar order. Problem framing, concepts, architecture, realization and evidence can develop together. Reopen the product choice, local subject or provision arrangement according to which premise changed.
SYSE.1:11 - SoTA-Echoing
The practice question is how to establish a defensible, shared and revisable project focus for the next engineering decision. The selected answer combines explicit framing and valuable alternatives with the contribution comparison in §4.4.1. The following research lines support parts of that synthesis; they do not establish its comparative effectiveness as a whole. The work titles, primary identifiers and evidence limits are in the public project-focus research sources.
| Current practice line | What changes in this pattern | Source and use | Adoption status |
|---|---|---|---|
| Design framing treats what matters to a design problem as revisable while problem and solution understanding develop together. | The Solution makes the project-system choice revisable and requires the use, assumptions, and contextual relations behind it. | Kelly and Gero (2022), Litster, Cardoso, and Hurst (2024), and Nickel, Hurst, and Duimering (2024). These conceptual and small empirical studies support explicit framing and revision, not one framing ontology or universal Method. | Adopt and bound. Adopt co-development and contextual comparison; let the project decision select the focus and establish actual System identity separately. |
| Set-based design retains alternatives while learning can change feasibility or trade-offs. | The Solution asks for materially different referents and preserves valuable alternatives when the decision needs them. | Toche, Pellerin, and Fortin (2020) review the set-based line; Al Handawi et al. (2024) demonstrate margin-based exploration in one aeroengine-component case. | Adapt. Retain alternatives and narrow them by evidence; let the receiving project determine candidate count and decision choreography. |
| Decision making under deep uncertainty uses robust alternatives, staged commitments, monitoring, and revision rather than prediction alone. | Record what would warrant reconsidering the first choice. If that choice depends on a materially uncertain assumption, identify it so later evidence can be brought to bear on it. | Haasnoot et al. (2013), Marchau et al. (2019), Lempert et al. (2024), and Akse (2024), mainly in climate, infrastructure, policy, and sociotechnical-transition settings. | Adapt. Use staged commitment and explicit reopening; let the receiving project establish its scenarios, thresholds, triggers, and decision Method. |
| Entrepreneurial-action research treats available means, commitments, contingencies, prediction, and judgement as context-dependent complements. | Candidate generation may use available Systems and commitments without treating them as proof of the project referent or of success. | Chen, Liu, and Chen (2021), Zhang et al. (2023), and Rapp, Olbrich, and Packard (2026). Meta-analytic associations and conceptual synthesis do not establish one causal engineering Method. | Adapt narrowly. Keep contingent action and revision as candidate pressure; leave business and Strategy decisions with their practices. |
The serious practice alternative is the NASA handbook’s Stakeholder Expectations Definition. Its iterative treatment uses operating scenarios to refine expectations, develop mutual understanding and obtain commitments. Those operations are useful here; its broader programme baseline is not required for every provisional choice.
Compare both ways on the ERP case at the same effort: the same contributors examine one moved order and its receiving use. A bounded expectations-and-scenario discussion can expose the stale-information gap. The §4.4.1 contribution comparison can expose it too. SYSE makes the designation question explicit alongside that discovery: which product use grounds the cooperation, which System is being engineered, and which contributions have separate acceptance boundaries? Its direct-subject exit remains available in §4.2.
For this next concept decision, the selected result is a revisable focus and the unresolved connection. A complete expectations set and broader commitments remain open. When the receiving decision needs those results, obtain them through the expectations treatment. When an existing scenario exchange already establishes the needed focus and connections, reuse it. A shorter account does not reduce the work participants need to establish a common focus. This comparison does not establish a general time or outcome advantage.
Reopen this methodological choice when contributors can repeat the designation but apply incompatible contribution paths, or when a bounded scenario or facilitated framing treatment resolves the same mismatch with less reconstruction. Repair the failed connection or use the better-suited treatment. Reconsider the retained research contribution when its evidence or transfer conditions no longer support the receiving use; keep the affected project’s assumptions and return in view.
These sources support comparing and revising project focus. Actual System recognition uses the FPF U.System criterion. FPF A.1.STM supplies the Library convention that organizational engineering retains the product SoI while fully engineering the creator. The research lines above do not establish that convention or its human effects. The pump, ERP and building cases apply it to their stated product, use and acceptance grounds.
SYSE.1:12 - Relations
A.15.6distinguishes project Work, process, case, Method, transformation, selected structure, and project system-of-interest wording before the practitioner uses this pattern to make a System choice.A.1.SCRsupplies the constructive recognition result when the comparison depends on whether a candidate is an actual acting or changed System. It also supplies the direct-subject exit when systemhood is not load-bearing.SYSE.16,SYSE.17,SYSE.2, andSYSE.8may use the project-system choice account when their question concerns compatible subjects, configuration, decision and evidence. Supply the immediate engineering subject and its relation to the product SoI separately when they differ; this imposes no temporal order.- An engineer uses
SYSE.2to develop linked use and concept claims whose failure may revise the choice. The resulting linked proposal helps frame the architecture question.C.30defines that question andC.32guides candidate synthesis; infeasibility or harm returns through the affected linked claims and reopens this pattern only when project focus changes. A.1.STMprovides the wider systems-mantra traversal when a practitioner must reconnect this local choice to intended product use, architecture, realization, change and recursive creators. It supplies the product/creator distinction while leaving the case-specific designation and actual Work order to their grounds.- The applicable FPF decision, authority, evidence, value, harm, temporal, and direct-relation patterns define or constrain those claims when the engineering question calls for them.