SYSE.13:5 - Worked Case: Pump-Controller Variants and Ten Installed Units
A pump manufacturer is deciding which of ten installed controllers may receive a cold-start protection change. The first export gives all ten the same product number and the status current. Inspection results and source records show four different decision-relevant groups:
| Installed units | Observed configuration | Effect on the release decision |
|---|---|---|
| S001–S004 | Input board IO-A and the older installed firmware realization. | Outside the candidate firmware package’s hardware compatibility claim. |
| S005 | Input board IO-B and temperature sensor TS-2, but no current sensor calibration evidence. | Possible candidate after calibration evidence; not currently eligible. |
| S006–S008 | IO-B, TS-2, current calibration evidence, and an installed realization corresponding to the supported firmware lineage. | May enter the current release comparison, subject to installation and verification Work. |
| S009–S010 | IO-B and TS-2; the database says installed, but current calibration evidence is absent. | Possible candidates after the missing evidence is obtained; status alone is insufficient. |
The candidate firmware package is an episteme describing support for IO-B. It is not the software realization currently executing in any controller. Installation and observation are needed before that correspondence can be claimed.
The engineering and manufacturing bills of material use different item boundaries. Engineers maintain a directional mapping from the engineering board item to the manufacturing board-and-harness items. The mapping loses installation-routing detail and cannot be used in reverse without another check. They do not create configuration items for every fastener or database row because those differences cannot change this release.
The effectivity proposal names S006–S008, the supported operating-temperature conditions, the candidate package edition, and the required installation and verification Work. S001–S004 are excluded; S005 and S009–S010 retain explicit evidence gaps. A selected reference configuration supports comparison but does not claim that every installed unit realizes it.
The configuration basis can inform SYSE.14 and bound the integration Work in SYSE.11. It establishes neither
installation, permission, release, nor successful operation. A changed board, sensor, package edition,
calibration source, inspection, or release question reopens only the affected unit and correspondence claims.
When the full pattern is unnecessary. If a laboratory engineer needs only to know whether one already identified controller contains IO-B at the current inspection time, direct System, structure, temporal, and evidence patterns answer the question. A product-family configuration basis adds no value.