fpf.tools
Library / Systems Engineering Principles Framework
Jump to passage
In this reading
Source · lines 1651–1725

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:05:10 UTC

SYSE.2:5 - Archetypal Grounding

SYSE.2:5.1 - Pumping station under flood risk

In the preceding SYSE.1 use, the engineer retains the intended referent PumpingStation-P1 in decision content and records downstream exposure as unresolved. No actual PumpingStation-P1 exists yet. The first linked proposal says:

use claim: the intended referent would move water under the selected flood load without unacceptable downstream harm
system-concept claim: the description assigns pumping, positioning, power, control, and discharge functioning to the intended station referent
main uncertainty: downstream conditions may make the proposed discharge harmful
architecture question: which selected structures and possible bearers could support the claim

This is enough to use C.30 and C.32. A component pump test can contribute evidence about an actual bearer, but it establishes neither the not-yet-present station nor its outside effect. The engineer uses downstream-harm evidence to revise the use claim. The project-system choice reopens only if the station referent no longer supports the project decision.

SYSE.2:5.2 - Manufacturer’s ERP-enabled planning change

The manufacturer keeps PlanningSystem-P1 as an intended System referent in its project decision; actual System identity remains unestablished. Actual person Systems Planner-A and Planner-B perform PlanningWork-PW1. They use actual deployed software runtime ERP-Runtime-E3 and demand, capacity, material, and production-order records as resources and evidence. The records are epistemes; PlanningAPI-PA2 and the user interface are separately identified interfaces.

The linked use claim says that Planner-A and Planner-B would revise production commitments during PlanningWork-PW1 using current records and ERP-Runtime-E3. The system-concept claim describes a possible future organization in which these actual Systems, records, interfaces, and planning Methods could satisfy a separately tested A.1 System criterion. Data currentness and interface latency are the main uncertainties. The ERP vendor’s product project can instead select ERP-Runtime-E3 or its product referent for its own decision. Installation completion, an organization chart, and user acceptance establish neither the manufacturer’s production effect nor the intended composite PlanningSystem-P1.

SYSE.2:5.3 - Occupied building heat-pump control

For HeatPumpPlant-HP1, ControllerConfig-C2, the next heating season, and ArchitectureDecision-AD1, the three compatible input accounts use the same subject, configuration, use, horizon, evidence window, and receiving decision:

  • the SYSE.16 use-context account states the BuildingHeatingSystem-BH1 proper-part claim, energy and information transfers, plant-room access permission, and unsupported latency, override, insulation, and clearance assumptions;
  • the SYSE.17 affected-system account supplies the qualified AcousticResult-AR4, SafetyResult-SR7, ThermalResult-TR5, and their authority boundaries, including the unmeasured neighbour-noise and cabinet- clearance branches; and
  • the SYSE.8 provider-arrangement account supplies only the supported provider claims and design constraints: actual provider System MaintenanceTeam-MT4, the current access permission, expected diagnostic Work, the communications bearer, and the missing commitment and authority result for remote monitoring.

The three accounts change the linked proposal as follows:

use claim: occupied rooms remain within the selected thermal range while qualified neighbour-noise and maintenance-access constraints hold
system-concept claim: ControllerConfig-C2 includes a cycle-rate limit, a low-noise branch, a measurable cabinet-location alternative, and a latency-tested override-safe branch
main uncertainty: night acoustic measurement and plant-room clearance are unavailable; remote-monitoring authority and commitment are unresolved
architecture question: which controller, sensor, cabinet, communications, and operating structures support those qualified claims
reopen condition: a specialist result, measurement, provider result, or operating observation defeats one of the linked claims

The remote-monitoring branch remains conditional because the provider-authority and commitment result is unavailable. Realization and WorkPlan descriptions may include cabinet relocation, access preparation, and test Work. Keep those realization and WorkPlan descriptions distinct from the System concept. If no feasible architecture supports the linked claims, revise this proposal. Reopen SYSE.1 only if the failure changes the project focus itself.