The approved policy and the policy running at the edge have diverged.
Fast policy improvement depends on local reliability, while the factory must preserve its existing robot-control environment.
Who you’d be doing this for
“I approved the new policy yesterday, and this morning the cell was still running the old one.”
Zhen Fujita · Robotics Engineer
Runs policy validation and releases for the customer’s production robot cell.
What is at stake
Approved policies are reaching the edge inconsistently, leaving robots on prior versions. You must weigh fast local deployment against a release path the customer can trust and operate.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- release speed vs. local reliability
- Dana visibility vs. customer system ownership
- automated activation vs. operator confidence
- one-customer fit vs. reusable integration pattern
Why Applied Intuition
Dana’s value depends on turning validated robot-learning work into repeatable operation inside customer environments.
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.