The pilot needs traceable evidence outside Dana without turning every investigation into a manual rebuild.
Customer control over operational records pulls against preserving the relationships that make robot behavior explainable.
Who you’d be doing this for
“When the shift lead asks what changed, I’m copying IDs between systems instead of checking the robot.”
Evgeni Djordjevic · Robotics Engineer
Operates the pilot cell and investigates behavior changes across policy versions.
What is at stake
Robotics engineers are rebuilding policy and evaluation history by hand whenever a pilot run needs review. You have to weigh customer data control against the traceability needed to investigate robot behavior.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer data control vs investigation traceability
- pilot speed vs durable integration
- broad platform reuse vs robot-specific evidence
- customer ownership vs implementation scope
Why Applied Intuition
Dana’s robot-learning workflow must fit customers that operate heterogeneous fleets and retain their own operational evidence.
Written with these in mind
Not your kind of problem? 65 more at Applied Intuition, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.