SYSE.13:8 - Common Failures and Repairs
These recurring failures can change the engineering decision:
| Failure | Repair |
|---|---|
| Treat one identifier as one bearer everywhere | Name the bearer and reference scheme for each use; state supported mappings among schemes. |
| Treat configuration item as a universal kind | Use it as a local designation of an already identified System, part, software package, or description chosen for this decision. |
| Treat a variant as an installed unit | Keep the variant description and unit separate and require realization evidence. |
| Treat latest as applicable | Name the edition and effectivity; current publication does not establish compatibility with the unit. |
| Treat a baseline or green status as reality | Keep the reference or status episteme separate from the observed actual configuration. |
| Make one product-data system the ontology | Use it as a resource and recover Systems, parts, epistemes, relations, schemes, and losses outside its schema when needed. |
| Inventory everything before deciding | Select the smallest item boundaries and claims that can change the receiving decision. |