PLATE 17 OF 20
Digital machinery, software and connected functions.
Software, digital delivery, data, and machine behaviour that changes after placement.
Pillar guide
Software in machinery, overview: The software lifecycle for a machine: specification, architecture, coding, testing, and documentation as one chain.
Supporting guides
| Guide | What it covers |
|---|---|
| Software updates after placing | Updates that change safety behaviour, and updates that do not, handled by different routes. |
| Connected machinery and data | Connectivity that adds functions, and the safety and information questions connectivity raises. |
| Systems for digital instructions | A delivery system that meets the Regulation conditions: printable, downloadable, saveable, and durable. |
| Machine learning behaviour in machinery | Behaviour that evolves after placing, and why Annex I listing matters for safety components of this kind. |
| Cybersecurity at the machinery interface | Where cybersecurity measures meet machinery safety, without blending the two regimes into one claim. |
| Systems for digital declarations | A declaration link that stays available, tested, and aligned with the technical record over ten years. |
| Software version control for machines | Versioning that lets any machine be matched to the software it actually runs, and the assessment behind it. |
| Digital models and the real machine | Models and simulations as design aids, and why a model result is not a machine test. |
| Data logging for safety review | Logs that help a safety review, and the limits of what a log can prove about a machine. |
| Remote access to machinery | Remote operation and maintenance access, and the safety controls that govern it. |
| Recording digital changes | A change record for software and digital functions that mirrors the product change record. |