The robot safety engineer
OpenWrites the safety case for robots on a floor that reconfigures from a blueprint: what must be validated again, at which hub, before a changed cell runs.
An open invitation, not a vacancy: several people can take it at once, and it carries no number until you commit to something specific. This page says what Moduloa hopes for and where a first contribution could start.
Why Moduloa needs this
Since ISO 10218 was revised in 2025, safety belongs to the application, meaning the task, the layout and the surrounding controls, and is validated in place rather than shipped with the robot. A Moduloa floor is designed to change shape between products, so every blueprint revision that moves a fixture or changes a robot task changes the application. The people page says humanoids in production are a safety case before they are a feature, and no ratified standard yet covers a robot that can fall.
What you would bring
- Machinery risk assessment to ISO 12100 and CE conformity, with the EU Machinery Regulation 2023/1230 in view.
- Robot applications validated under ISO 10218-1 and -2 (2025), including power and force limiting, formerly ISO/TS 15066.
- Functional safety design to ISO 13849 or IEC 62061: safety PLCs, scanners, monitored stops.
- Mobile robot safety (ISO 3691-4) and a working knowledge of the draft ISO 25785-1 for robots that balance actively.
- OT security treated as a safety function (IEC 62443), which the people page asks for from day one.
Tasks that suit you
Each has a plain test for done. Ask to commit to one: name what you will deliver and a date no more than three months after it is accepted. Several people can work on the same task, each with its own deliverable.
- J-01 Hub criteria by domain and size · Two to three weeks · Ask to commit to J-01 →
- J-04 Robot task interface · Three to four weeks · Ask to commit to J-04 →
Other first deliverables
Each is specific enough that by its date anyone can tell whether it was delivered. Some are a task above in a smaller form. Name one, or a better one.
- A revalidation checklist for a reconfigurable cell: what a blueprint revision must trigger when it moves a fixture, changes a robot task or adds a station, written so the OS release flow could carry it as its safety review.
- A short spec of what a station's safety zones and a robot task's safety limits must contain to be validated, offered to the Factory OS data model sketch.
- A plain reading of ISO 10218:2025 for a floor where cells move: what falls on the hub as integrator and what on the author of the blueprint, with the open questions named.
What this is, and is not
Not a sign-off or a certificate: there is no installation to validate yet, and nothing written here certifies a real cell. On its own a seat carries no pay, no equity and no supplier position, and any paid work is agreed separately.
When your commitment is accepted, it shows on the task and on your seat card, and a first commitment takes the next permanent number on the register, with your name, a link and your date. When the work is delivered in the open you are aboard and a certificate is issued. Nothing is paid for a seat and none is for sale: on its own a seat carries no equity and no supplier position, and any paid work is agreed separately, on its own terms. The entry stays either way: a commitment not delivered by its date is marked lapsed and dated, never removed.
Pick a task that suits you and ask to commit to it, or name your own first deliverable: what you will deliver and a date no more than three months after it is accepted. Write to shk@moduloa.com, or use the link on any task, which opens the contact page with the subject filled in. It does not have to be large. It has to be specific enough that anyone can tell by its date whether it was delivered.
Read these first
- moduloa.com/journal/2026-07-23-you-cannot-certify-a-fall
- moduloa.com/manufacturing/os
- moduloa.com/manufacturing/execution
- moduloa.com/people
Also needed in JACQUARD · Assembly floor: The toolmaker · The test and flashing engineer · The robotics engineer · The intralogistics engineer · The hub partner · The pilot partner