Start with risk. Close the loop with evidence.
We apply a consistent system safety engineering approach alongside industry-specific requirements, connecting hazard identification, requirements allocation, architecture analysis, verification and safety argumentation.
Clear inputs and outputs at every step.
Select a lifecycle step to explore its engineering focus and typical outputs.
Hazard & Risk Identification
Identify hazards, affected parties and the conditions that create risk, starting from operating scenarios, system boundaries and reasonably foreseeable abnormal conditions.
Typical outputsProduct and scenario definitions, hazard records, risk analysis and assumptions requiring confirmation.
Bring standards into the product design.
Confirm the applicable editions, target markets, product scope and safety objectives at project initiation, then define the work.
| Domain | Standards & specifications | Engineering application |
|---|---|---|
| Automotive | ISO 26262 | Functional safety engineering for vehicles, ECUs and semiconductors |
| Industrial control | IEC 61508 / ISO 13849 | Safety-related control systems and safety lifecycles |
| Industrial drives | IEC 61800-5-2 | Safety-related power drive systems and safety functions |
| Rail | EN 50126 series / EN 50129 | RAMS and safety argumentation for safety-related systems |
| Industrial robotics | ISO 10218-1 / -2 | Safety of industrial robots and integrated applications |
| Medical devices | ISO 14971 / IEC 62304 | Risk management and applicable software lifecycle processes |
| Aviation | ARP4754 / ARP4761 / DO-178C / DO-254 | System, hardware and software safety support within the agreed project scope |
This table outlines our engineering service areas. Products, regulations and integration boundaries may require several standards in combination; applicability is assessed for each project.
Review the engineering detail.
What is the safe state for this hazard?
Is the safe state defined for the specific hazard? Are the response time, conditions for maintaining it and recovery conditions clear?
Will the safety action actually work?
Follow the path from monitoring and control through the drive to the actuator. Identify evidence gaps in interfaces, diagnostics, independence and supplier black boxes.
What supports the safety claim?
Connect hazards, requirements, design decisions, analytical conclusions and test results. Track assumptions, findings and corrective actions.
Start with a specific safety question.
Tell us about your product, operating scenario and project stage so we can define practical engineering support.