02Area
Prove it Safe
Make safety traceable.
Evidence chains that connect requirements, risks, measures, tests and the released product information.
The situation
A submission, an audit or a phase gate has a fixed date, and nobody can show quickly which requirement led to which measure and where it is documented.
The service
The documents critical for the deadline separated from the rest, the order of the work set, evidence chains from requirement to released information version made visible.
The result
A documented path from the requirement to the released information version that the client’s own people can follow and maintain.
Testing, certification and the declaration of conformity stay with the manufacturer and the responsible bodies.
02Newsletter section
Issues in this area
Safety has to be demonstrable over the whole lifecycle of a product, not only at the moment of release. This section collects the issues on lifecycle documentation, traceability from the requirement to the released information and the role of AI in the chain of safety evidence. The focus lies on what makes evidence hold: clear relations between requirements, risks, measures and the information that documents them.
-
Tracing AI decisions and actions in R&D and V&V
An authorized AI workflow can produce a result without leaving enough evidence of how that result became a development decision or a verification outcome. Building on the AI TechDoc Knowledge blueprint “AI systems and the machine: levels and boundaries,” the issue asks for R&D and V&V whether the record can show who or what made a decision and triggered the next step.
-
From structure to meaning to evidence to using the EvoOntology AI-Model
When a guard-door switch changes, the update has to reach the machine configuration, the affected safety function, the inspection instruction and the released evidence. Using the MX-Y7B400 example, the issue shows how canonical models, ontologies and an AI-supported EvoOntology layer lead from structure to meaning to evidence, with every proposed model change going through technical review.
-
Lifecycle documentation: The new backbone of technical communication
Lifecycle documentation replaces the idea of a finished manual with a continuous, safety-relevant information flow from development through operation and maintenance to modernization and digital updates. The issue describes how the Machinery Regulation (EU) 2023/1230 formalizes this shift and what it means for maintenance documentation and the digital elements of machines.
-
When safety evidence becomes a system in Machine Safety and MedTech
Safety-critical products in machine safety and MedTech rarely lack documents; the problem starts when risk assessments, V&V results, manuals and post-market information must jointly prove that a product is still safe after a change. Drawing on research on model-based assurance evidence management and safety cases, the issue describes safety documentation as part of a managed evidence system across the lifecycle and across expectations in the EU, the United States, Canada and China.
-
When AI enters the Safety Evidence Chain
AI does not have to control a machine to become safety-relevant; it only has to change the information people use to operate, maintain or approve it. The issue looks at AI-supported technical documentation as part of the evidence chain, at the governance mindset of the EU AI Act and at what documentation teams need to control, from classifying AI use to tracing sources.
-
Implementing control: when motion becomes a safety function
Identifying a hazard point is only the beginning: the safety concept then has to define how control reduces the risk. Following on from issue 15, the issue traces cause and effect from hazardous movement and access situation through detection, control response and safe state to response time and the verification of the safety-related control function.
-
Evidential systems focus of interlocks
From the system side, an interlock provides evidence but does not by itself establish system truth. The issue follows the chain from safety inputs through diagnostic processing, safety functions, state and mode logic and safe states to validation and PL/SIL evidence under ISO 13849.
-
The Documentation Latency Chain: the hidden gap between machine reality and documented reality
Machines often change faster than the documentation around them: a component is replaced, firmware changes, a vulnerability is published. The issue introduces the term documentation latency chain for the time lag between machine reality and documented reality and shows how PLM and ILM together can close it across risk assessment, PL evidence, CRA evidence and manuals.
-
CE-focused view: E‑Stop versus Power‑Off as a conformity and evidence question
This follow-up to issue 1 is written for CE teams: the engineering is often correct, but the evidence chain from protective measures to information for safe use is not expressed clearly enough. It treats conformity evidence as one coherent safety argument across integrated lines, multiple suppliers and lifecycle changes and points to established machine safety experts in the DACH region for further orientation.
Articles in the blog “Read the Signs”
-
Penguins
No profile does not mean no obligation
For many OT components there is no product profile under EN 50770 yet. The Cyber Resilience Act applies all the same. The gap is not in the standard. It lies between the decision, the information and its evidence.
In Practice
-
When cross-cutting standards change the picture: three CRA scenarios
In the CRA standardization work, horizontal (Type B) standards address security aspects and processes shared by many products, and product-specific (Type C) standards address individual product types. The horizontal view helps where no product profile matches, makes the boundary of a profile assessment explicit, and organizes vulnerability handling across product families. In every case, the decisions and the evidence behind them have to be documented and linked.
View the scenarios: When cross-cutting standards change the picture: three CRA scenarios →
02Prove it Safe
Services in this area
Each service in short: the situation it fits and what results. The full description, with approach and limit, is on sainaveigel.com.
-
Securing a deadline that requires evidence
- The situation
- A submission, an audit, a certification or a phase gate has a fixed date, sometimes while a regulation changes at the same time.
- The result
- A delivery plan with interim states that can be shown every week, the finished documents and templates that make the next deadline calmer.
Full description on sainaveigel.com: Securing a deadline that requires evidence ↗
-
Evidence chains that hold in an audit
- The situation
- Requirements, risks, tests and documents sit in different systems, and the traceability is put together in a spreadsheet at the end.
- The result
- An evidence structure with clear linking rules and adapted templates, from the requirement to the released information version, in the tools the client already uses.
Full description on sainaveigel.com: Evidence chains that hold in an audit ↗
-
Safety messages that show where they come from
- The situation
- Safety messages come from the risk assessment, and it has to stay traceable why each one is there.
- The result
- Reusable safety messages in DITA, structured in line with IEC/IEEE 82079-1 and each linked to its hazard, so that a change in the risk assessment reaches every output.
Full description on sainaveigel.com: Safety messages that show where they come from ↗
Testing, certification and the declaration of conformity stay with the manufacturer and the responsible bodies.
Billed at an hourly rate, with an estimate after reviewing your documents. You work directly with Saina Veigel.
The other areas
-
01
Write it Safe
Information for use: emergency stop, HMI, interlocks, hazard points and the readability of safety information.
-
03
Keep it Safe
When rules, systems and signals change: safety and security, interfaces, semantic drift and new deadlines.
New issues on the third Friday of every month on LinkedIn.
Subscribe on LinkedIn