Write it Safe. Prove it Safe.Safety information, evidence and controlled change
In Practice: 1

In Practice

All scenario sets →

Real Cases: 1

Real Cases

All real cases →

03Area

Keep it Safe

Keep safety intact through change.

Controlled content, variants, terminology and change paths, so that safety information stays valid when the product, the rules or the system change.

  1. The situation

    Variants multiply, copies drift apart, a regulation changes or a move to a new system is due, and nobody knows which statements are affected.

  2. The service

    Content model, terminology, variants and release paths checked, document control conceived, third-party documents checked against fixed criteria, knowledge handed over to the client’s team.

  3. The result

    A structure that shows which version applies, for whom and since when, kept by the client’s own people without lock-in.

Content and release stay with the manufacturer, and the quality management system remains theirs.

See the services Read the issues

03Newsletter section

Issues in this area

Products, regulations and systems keep changing after release, and safety information has to change with them. This section collects the issues on the points where change puts safety at risk: the meeting of safety and security, interfaces between systems and organizations, semantic drift in terms and signals, and new regulatory deadlines. The focus lies on controlled change, so that information stays valid when its context moves.

  1. Issue 25 ·

    Why Safety and Security must iterate — but never share a single process

    Safety and security work on the same technical system but defend against hazards that move in opposite directions, with different standards, methods and evidence. The issue argues that the two domains must exchange feedback but never merge into one process; the revised edition of October 1, 2026, adds a correction notice and an extended appendix.

  2. Issue 23 ·

    AI in machinery — why 2027 is currently more important than 2028

    Discussions about AI in machinery often focus on August 2, 2028, but for machinery with AI functions the relevant shift comes earlier, on January 20, 2027, when the Machinery Regulation (EU) 2023/1230 starts to apply. With reference to the Digital Omnibus Regulation, the issue explains why AI functions in machinery follow a sector-specific conformity route and which functions require assessment from 2027.

  3. Issue 17 ·

    From Semantic Drift to AI Drift: when signals change meaning

    Semantic drift is the moment when a signal, state or command still looks valid but no longer carries the meaning the system or the documentation assumes; AI drift extends the problem to interpretation itself. Using a robotic cell whose “ready” status changes meaning between versions, the issue applies the discipline of calibration to meaning: reference, tolerance and acceptance criteria.

  4. Issue 14 ·

    API Safety and MBSE: why interfaces must become system elements

    An unsafe API rarely fails as isolated software; it fails where system context, architecture, security constraints and verification evidence no longer fit together. The issue explains how Model-Based Systems Engineering places API documentation in a wider engineering context and treats interfaces as system elements with consequences for risk, verification and lifecycle.

  5. Issue 13 ·

    Where APIs hide inside modern interlinked machinery lines

    A modern food processing and packaging line is a cyber-physical system in which PLC safety logic, authenticated data flows, cloud services and external APIs interact. Using a representative line from intake to palletizing, the issue shows where APIs hide and why their documentation becomes part of the safety, security and compliance evidence.

  6. Issue 10 ·

    Why security fails: the blind spot between safety and security thinking

    Safety and security share the same formal structure but look in opposite directions, and most organizations design, audit, train and document them separately. The issue traces the resulting blind spot across ships, ports and industrial production lines and outlines how combined safety and security thinking can close it.

  7. Issue 9 ·

    ISPS and industrial security: one prevention logic for ships, ports, rail, machinery, and OT

    ISPS and industrial security follow the same prevention logic: identify intentional threats, assess vulnerabilities and consequences, define proportionate controls and verify them in a PDCA cycle. Using passenger ships, container ships, ship machinery, train manufacturers and train operators, the issue distinguishes security, which asks what people can do to a system, from safety, which asks what a system can do to people.

  8. Issue 8 ·

    Latency chains in IT/OT Security: why technical speed is a governance issue

    Every technical system is a chain of stages, and the slowest stage determines the behavior of the whole. The issue uses latency chains to make dependencies, control points and evidence chains in IT/OT visible and shows how ISO 27001 controls support governance under the Cyber Resilience Act.

  9. Issue 4 ·

    Industry rules change — Information discipline doesn’t

    Automotive, food processing, pharmaceuticals, chemicals and marine each have their own rules, but they share one failure mode: information drift on the way from regulators through manufacturers and integrators to operators. The issue borrows Information Lifecycle Management from IT so that safety information stays available, trusted and owned throughout its lifecycle.

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.

Real Cases

In Practice

03Keep 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.

Content and release stay with the manufacturer, and the quality management system remains theirs.

Billed at an hourly rate, with an estimate after reviewing your documents. You work directly with Saina Veigel.

Send an email All services at a glance

The other areas

  • 01

    Write it Safe

    Information for use: emergency stop, HMI, interlocks, hazard points and the readability of safety information.

    9 issues

  • 02

    Prove it Safe

    Evidence: lifecycle documentation, traceability and AI in the chain of safety evidence.

    9 issues

New issues on the third Friday of every month on LinkedIn.

Subscribe on LinkedIn