• What standards do I need to follow for a consumer robot?

Consumer robots typically need to comply with CE marking, Machinery Regulation, EMC, and product safety standards relevant to their function. Cybersecurity and update mechanisms are increasingly important as connected features expand.

• What standards do I need to follow for an industrial robot?

Industrial robots are primarily governed by ISO 10218, covering safety requirements for robot systems and integration. Additional standards may apply depending on the environment, EMC exposure, and human–robot interaction.

• What standards do I need to follow for a medical robot?

Medical robots must comply with medical device regulations (e.g. EU MDR or FDA frameworks), including risk management, traceability and clinical validation. Safety, software lifecycle control and documentation requirements are significantly stricter than in industrial robotics.

• What standards do I need to follow for an aerospace-based robot?

Aerospace robots typically build on ISO 10218 as a baseline for robotic safety, combined with aerospace-specific standards depending on mission profile. Environmental and mechanical robustness is often validated using MIL-STD-810, while space-bound systems may additionally need to comply with NASA standards such as NASA-STD-7001 for payload vibration and structural integrity. The exact certification scope depends strongly on whether the robot operates in atmospheric, suborbital, or orbital environments.

• What standards do I need to follow for a defence-focused robot?

Defence-focused robots typically build on ISO 10218 as the baseline for robotic safety, combined with military qualification standards. MIL-STD-810 is commonly applied to validate environmental robustness, while additional defence-specific regulations cover security, supply chain qualification and controlled update processes. The exact requirements depend on deployment conditions and mission criticality.

• How early should I consider safety and certification in my project?

From the very start of your project. Safety and certification must be considered during system architecture definition. Leaving this until late in development often triggers redesigns, re-testing and costly delays.

• Can pre-certified platforms reduce certification effort?

Yes. Using pre-validated modules, motherboards or box PCs can significantly reduce certification scope, documentation effort and audit risk.