Services organized by standard family
Most projects become confusing when functional safety, cybersecurity, and legal metrology are discussed in the same pile. This page keeps them separate, while still showing where the evidence may overlap.
01
For safety functions, risk reduction, SIL/PL, software safety lifecycle, and safety manual evidence.
ESS, BMS, PCS, and EMS protection functions and software safety evidence
Machinery control system PLr, category, MTTFd, DC, and CCF reasoning
FMEDA and safety manual review for chips, AFEs, MCUs, and modules
IEC 60730 Annex H / UL 1998 software Class B/C evidence
Cross-domain readiness support for energy storage systems, BMS, PCS, and EMS products where functional safety evidence, software controls, and cybersecurity scope must be defended together.
Review of chip, module, and subsystem functional safety evidence, including FMEDA assumptions, diagnostic coverage, failure rate usage, safety manual claims, and assessor-facing argument structure.
Comprehensive assessment of your current safety or cybersecurity processes against standard requirements.
Systematic identification and analysis of potential hazards and associated risks for your products.
Expert guidance on Safety Integrity Level (SIL) or Performance Level (PL) determination for safety functions.
Assessment of software development processes and software safety according to UL 1998 and IEC 61508-3.
Establish and implement a comprehensive functional safety management system according to IEC 61508.
02
For product cybersecurity regulations, industrial control security, RED cybersecurity, machinery cybersecurity, and vulnerability response evidence.
EU CRA technical documentation, SBOM, risk assessment, and vulnerability handling
EN 18031 RED cybersecurity applicability and evidence package preparation
EN 50742 / SRSL machinery cybersecurity assessment with IEC 62443 alignment
UL 2941 cybersecurity readiness for ESS, remote maintenance, and vulnerability response
Navigate the EU Cyber Resilience Act requirements and achieve compliance for your products.
Assessment-route planning for radio equipment and connected products under the EN 18031 series, including requirement applicability, evidence mapping, and review-ready technical documentation.
Support for machinery cybersecurity projects using the SRSL concept, including threat modelling, safety impact reasoning, Method A/B route selection, and IEC 62443 alignment.
Cybersecurity readiness support for energy storage systems using UL 2941 as the assessment frame and IEC 62443 as technical support for controls, processes, and vulnerability handling.
Comprehensive cybersecurity risk assessment for industrial control systems and connected products.
Integrate security into your product development lifecycle from concept to deployment.
Establish processes for vulnerability disclosure, handling, and coordinated vulnerability response.
Implement IEC 62443-4-1 Secure Development Lifecycle (SDL) with 8 practices and achieve target maturity level (ML1-ML4).
Systematic threat identification and analysis using STRIDE methodology for industrial control systems.
Identify security vulnerabilities through controlled penetration testing and comprehensive assessments.
Market-entry support for products facing Australian cybersecurity expectations, including requirement screening, evidence gap review, and alignment with existing CRA, EN 303 645, or IEC 62443 work.
03
For measuring instrument software, legally relevant functions, Type P/U, risk classes, and WELMEC Guide 7.2 extensions.
Software assessment for electricity, heat, water, gas, and other measuring instruments
Type P / Type U software structure and legally relevant function boundary
Risk class B/C/D and O/L/T/S/D extension evidence
Software download, data transmission, audit trail, and software separation evidence
Delivery model
Within each standard domain, the engagement can stay light or become hands-on depending on your documentation maturity and certification pressure.
For teams that know the route and can fill the documents internally, but need assessor-facing structure.
For teams with existing risk analysis, design notes, test records, or process files that need review readiness checked.
For projects under certification pressure, or teams that want compliance and evidence planned during design.
Send the product type, target market, known standards, and the current blocker. I will help you identify the smallest useful next step.