Sign inCreate free account

Industries

Requirements and safety functions for machinery and industrial equipment

A machine builder can keep what the machine must do, the hazards from its risk assessment, the safety functions that answer them and the tests that prove them in one OpenV project. The frame, the drives, the control and the guarding can each be a project under the machine. OpenV does not calculate a performance level or a safety integrity level, so that calculation stays in the tool you use for it and its result is recorded as an attribute.

Updated by Desktop Machine Shop, the makers of OpenV.

What these teams keep

A machine’s technical file rests on a risk assessment to ISO 12100, safety functions specified and validated to ISO 13849 or IEC 62061, and evidence that each requirement of the machine was met. Smaller firms often keep this in Word and spreadsheets, where a changed requirement does not show which tests to repeat.

Where it goes in OpenV

  • Each hazard from the risk assessment is an artifact, linked to the guard, interlock or control function that reduces it.
  • Safety functions are requirements with their required performance level as an attribute.
  • Each sub-assembly and each bought-in unit is a child project. A supplier of a spindle or a drive works in its own.
  • A change to a requirement flags its tests for review.
  • The plan dates the design reviews, the prototype and the release, and shows them for the whole machine on one chart.
  • A PDF from a baseline goes into the technical file.

A first project

OpenV’s own sample is a desktop CNC mill in fifteen projects: the mill, its frame, motion, control, enclosure and safety system, and their parts. Start smaller: one machine, its ten most important requirements, the hazards of its moving parts and the tests of its emergency stop.

What OpenV does not do

  • No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
  • No performance level or safety integrity level calculation.
  • No bill of materials and no link to a CAD or PLM system, though CAD files can be attached to an artifact.
  • No declaration of conformity or technical file template.
  • No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
  • OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.

Read more