SYSE.20:5 - Worked Case: Power-Converter Integration
A team is preparing an integration recommendation for a power converter. The recommendation will be used by a separate release decision. During one laboratory run, five Work occurrences obtain:
| Work occurrence | Interval on the run clock | Directly relevant relation |
|---|---|---|
| physical-model correction | minutes 0–25 | overlaps simulation during minutes 10–25 |
| numerical simulation | minutes 10–35 | depends on a compatible solver service and named model editions |
| rig reconfiguration | minutes 30–50 | must finish and receive rig-release authority before closed-loop test |
| closed-loop test | minutes 50–75 | uses the released rig and named converter configuration |
| evidence review | minutes 70–90 | overlaps the final five minutes of test; its recommendation remains conditional until test evidence arrives |
A platform team also performs solver-service recovery during minutes 32–43. That provider Work overlaps the run but remains a separate Work occurrence. Earlier laboratory training is capability-development Work; it is neither simultaneous with nor part of this run. Support capability claims with evidence of the trained Agents’ ability under the relevant conditions; the training’s earlier date establishes only temporal order.
Each Work occurrence has a performing Agent, an enacted Method, and the relevant assignment and authority when the receiving claim needs them. The case gives no basis for treating all five Methods as parts of one composite Method. It does establish three different Work relations: temporal overlap, the rig-change-before-test guard, and simulation dependence on a provider result.
The decision uses three selected structures:
- a Work structure containing the relations in the table;
- a subject structure containing the converter, control board, power stage, rig, load bank, and platform under their actual component, connection, and service relations; and
- a representation-use structure connecting model editions, solver configuration, simulated results, measured traces, and release criteria to the converter configuration and intended claim.
This is the complete selected set for this case because no other inspected structure changes the choice. The live conflict is clear: simulation starts while the model is changing and continues while the solver service is degraded; review can therefore receive a simulation result that no longer corresponds to the tested configuration.
The Agent admits three reconfiguration alternatives as the fixed option set:
| Option | Changed relation | Main gain | Moved burden |
|---|---|---|---|
| A — total serialization | Every project Work occurrence waits for the previous one; provider recovery blocks simulation. | Simple evidence order. | Feedback is slower and laboratory time is idle. |
| B — guarded overlap | Overlap remains; every simulation result names model, solver-service, and intended converter configurations; the rig-release guard remains; evidence review marks provisional results. | Fast feedback with usable configuration correspondence. | More traceability and service-health checking. |
| C — laboratory-local solver service | Guarded overlap remains and simulation uses a local service. | Shared-service outages no longer block the run. | Solver validation, security, configuration, and maintenance move to the laboratory. |
An authorized engineering lead compares the options. The rule rejects an option that breaks evidence-reference eligibility, the rig-release guard, or the lead’s authority boundary. Among surviving options, it prefers useful overlap and then the option with the lower continuing service burden. Current evidence supports the lead’s choice of B. A failed compatibility replay would reopen that decision; validated evidence of a lower continuing burden could support a later choice of C.
The decision requests separate implementation Work to update the applicable MethodDescription and WorkPlan.
The next representative run tests the new references, provisional-result rule, and rig guard. The architecture
account supplies the platform-design constraint to SYSE.12. Its description of a guarded-overlap variant may
enter SYSE.21 as one project observation; cultural continuation requires later evidence from other Work and
Agents.