Most safety work gets bolted on at the end.
We build it in from the start — hardware, firmware, and
certification delivered as one team, from the first schematic.
EV powertrains, power distribution, industrial controls.
ISO 26262, IEC 61508, UN R155.
We build safety-critical hardware and software, then carry it through certification — not brought in at the end, but involved from the first schematic.
ISO 26262 and IEC 61508 applied by engineers who have designed the systems these standards govern. From HARA and ASIL decomposition through safety case sign-off — covering automotive, power distribution, and industrial applications.
Discuss your projectISO/SAE 21434 and UN R155 applied to ECUs, PDUs, communication buses, and OTA update paths. TARA analysis, CSMS establishment, and threat modeling — done by the engineers who design these systems, not external reviewers.
Discuss your projectWe develop motor control firmware, PDU software, and embedded systems for safety-critical applications — from algorithm design to production-ready code, built to ISO 26262-6 from day one. Not adapted for safety after the fact.
Discuss your projectWe design and verify power electronics hardware — traction inverters, PDUs, onboard chargers, and BMS — for safety-critical applications. Circuit design, PCB layout, and hardware V&V per ISO 26262-5 and IEC 61508.
Discuss your projectMost safety consultants know the standard. Fewer have actually built the system it covers.
norxs has designed and shipped the systems these standards govern — traction inverters, PDUs, onboard chargers, motor controllers. We don't just audit your design. We can build it.
We work inside your engineering process, not alongside it. That means reading schematics, stepping through firmware, and applying requirements at the point where design decisions are actually made.
Most safety work gets split across vendors — one for functional safety, another for software, another for hardware. We cover all of it. One team, one conversation.
You work directly with the engineers doing the work, not an account manager relaying questions. Every engagement has a dedicated lead from first discussion through final deliverable — no handoffs, no intermediaries.
The methods, standards, and system types the norxs team works with directly — not as framework reviewers, but as engineers who have built these systems.
Full ASIL-D safety lifecycle for high-voltage SiC and IGBT inverter systems — HARA, safety goal derivation, ASIL decomposition, FMEA, FTA, DFA, hardware safety metrics (SPFM / LFM), and safety case compilation. Coverage from concept phase through integration V&V.
Structured TARA for automotive attack surfaces — ECUs, OTA update paths, CAN / Ethernet buses, and telematics interfaces. CSMS establishment per ISO/SAE 21434 and UN R155 type-approval preparation, including cybersecurity requirements cascaded to Tier-2 suppliers.
Software safety requirements allocation, ASIL decomposition at software level, and ASPICE-aligned development for embedded control systems — onboard chargers, inverter control MCUs, and BMS firmware. Includes software safety concept, unit test strategy, and pre-audit evidence packages.
We've built these systems before we consulted on them — traction inverters, PDUs, onboard chargers, embedded firmware. The safety work comes with that context already built in.
Every project has one lead engineer from the first schematic to the final safety case. No handoffs. No account managers in between. Just the engineers doing the work.
Led by a TÜV-certified Functional Safety Expert, Cybersecurity Professional, and SGS-certified AI Safety Professional (SC-AISP) with 15+ years across national research institutes and EV powertrain development — and a PhD in Electrical Engineering.
Internationally recognized certifications in functional safety and cybersecurity — earned alongside 15+ years of hands-on safety-critical system development, not instead of it.
Starting an ISO 26262 project, working through UN R155 type approval, or just not sure where to begin — reach out and we'll have a direct conversation.
*For Open Source License Inquiries (ISO 5230) or Security Vulnerability Reporting (ISO 18974 / NIST VDP), please use the form above or email us directly.
We'll get back to you as soon as we can — usually within a day or two.