SYSE.15:5 - Worked Case: Methods for a Heat-Pump Controller Change
An engineering team is changing the controller of an occupied-building heat-pump plant. Its current process description points to a V diagram, a Systems Engineering handbook, a simulation repository, an issue tracker, a hardware-in-the-loop bench, an AI coding service, and a release checklist. The V diagram, handbook, and checklist are descriptions. The repository and issue tracker store or carry records. The bench is a platform System. The AI service may be an Agent, provider resource, or tool depending on the actual arrangement and agency. Calling this heterogeneous set our model-based process does not make it one Method.
The engineering lead acts as the Agent authorized to choose Methods for this controller project. Release authority remains with another Agent. The team starts from recurring results rather than the list of assets:
| Needed result | Candidate or retained Method | Evidence and current gap |
|---|---|---|
| Operating situations and protected room-temperature and equipment conditions | Recover operating situations, affected Systems, and required effects before choosing a controller concept. | Existing operating records cover normal weather; rare grid events remain an explicit gap. |
| Plant-response prediction | Identify physical parameters and simulate the heat-pump, building, sensor, and controller interaction. | Earlier predictions omitted measured sensor latency. |
| Controller implementation candidate | Generate a bounded code candidate, then perform an independent implementation review. | Use AI is not a Method; the reusable generation-and-review ways and their different results are stated separately. |
| Integration observation | Exercise the actual controller interface and plant model on the hardware-in-the-loop bench. | Bench time is scarce; occupied-building trials require separate safety and release conditions. |
| Configuration, assurance, and release decisions | Use the corresponding configuration, assurance, and release Methods for the identified controller and plant conditions. | None of these decisions follows from the V diagram or a green code check. |
The hardware-in-the-loop trial Method meets both experimental-engineering and cyber-physical-integration Method criteria. The team also uses it as a part of two stated whole Methods: controller integration and release-evidence development. Those classifications and whole–part relations are recorded separately. The modeling result informs the controller choice, but that result use does not make modeling a stage of one universal lifecycle.
In a representative three-day slice, an AI coding Agent performs bounded generation Work, a controls engineer reviews the candidate, and a test engineer performs the bench trial. If the coding service lacks enough agency to perform the assigned Work, it is recorded as a tool used by the controls engineer instead. The trial reveals sensor latency that destabilizes the candidate despite an acceptable simulation prediction. The release Agent withholds the candidate, and the controls engineer revises the physical model. Faster code generation did not shorten the limiting integration and assurance Work.
The repertoire account retains operating-situation recovery, linked concept development, physical modeling, bounded implementation generation, independent review, hardware-in-the-loop trial, configuration, assurance, and release Methods. It retains an occupied-building trial only under the stated safety, plant-state, weather, and release conditions. The V diagram remains an overview. The phrase AI workflow Method remains unresolved.
Scarce bench time leaves several possible repairs. The team can use OPS.11.1 to compare available time with
already assigned work and revise allocation under the existing authority. It can also compare trial Methods
that occupy the bench for less time while preserving the required integration result and evidence conditions.
A shorter trial that misses the sensor-latency failure would not serve the present use. New bench provision or a
different way of obtaining the result belongs to SYSE.12 or SYSE.24 when that contribution is needed. None of
these options is selected merely by observing scarcity.
Simultaneous modeling, generation, review, trial, and assurance conflicts go to SYSE.20. Evidence of wider use,
selection, retention, or loss can later inform SYSE.21; this project choice does not establish a cultural trend.
When the full pattern is unnecessary. If one identified Method already supplies a well-understood result for the same System and conditions, and no interaction, specialization, capability, provider, or currentness question can change the decision, use that Method and its direct evidence patterns.