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.
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.
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.
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.
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
Seven meters short. The limit switch did not stop the hook.
A hoisting wire renewed shortly before an engine overhaul was 7 m shorter than the crane manufacturer specified. The hoist limit switch did not cut power, and the wire broke while a 1200 kg cylinder liner was being lifted. A scenario report on one value that the manual and the maintenance system stated differently.
Read the scenario report: Seven meters short. The limit switch did not stop the hook. →
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 →
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.
-
Maintaining content once instead of in many places
- The situation
- The same component has three names in three manuals, and one change triggers a search through twenty documents, before or after a system change.
- The result
- A written assessment of content model, terminology, variants and release paths, with measures ranked by effect and effort for the system already in use.
Full description on sainaveigel.com: Maintaining content once instead of in many places ↗
-
Keeping variants under control
- The situation
- Product and document variants multiply, and copies drift apart.
- The result
- A model for product and document variants, so that shared content is maintained once and differences are controlled deliberately.
Full description on sainaveigel.com: Keeping variants under control ↗
-
Controlling which version applies
- The situation
- Nobody can say quickly which version of a document applies, for whom and since when.
- The result
- A concept for the control of documents and records, from identification, versions, review and release to distribution, change and retention.
Full description on sainaveigel.com: Controlling which version applies ↗
-
Keeping manuals up to date
- The situation
- The machine keeps evolving, and the manual does not.
- The result
- Changes worked in every quarter and every delivered version frozen, so that the manual matches every machine that has shipped.
Full description on sainaveigel.com: Keeping manuals up to date ↗
-
Checking third-party documentation and passing on knowledge
- The situation
- Suppliers deliver in every quality and format, and knowledge that a few people have is passed on as a lecture and forgotten.
- The result
- Checking criteria and a checking procedure, plus short learning units built from the client’s own documentation. Release stays with a person.
Full description on sainaveigel.com: Checking third-party documentation and passing on knowledge ↗
-
Moving to DITA
- The situation
- The editorial team is moving to DITA from Word, FrameMaker or another system.
- The result
- A content model with topic types, metadata and reuse rules, and one manual migrated as a pilot.
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.
The other areas
-
01
Write it Safe
Information for use: emergency stop, HMI, interlocks, hazard points and the readability of safety information.
-
02
Prove it Safe
Evidence: lifecycle documentation, traceability and AI in the chain of safety evidence.
New issues on the third Friday of every month on LinkedIn.
Subscribe on LinkedIn