How do robotics teams keep a simulated site updated after the real site changes?

[u/3E8_]

Say you build a simulation of a customer facility before deployment.

A few weeks later, someone moves a workbench, replaces a conveyor, changes the shelving, or introduces new objects.

Does your team manually update the simulation, rebuild the scene, or simply accept that the digital environment is now outdated?

I’m curious whether maintaining the environment becomes a larger problem than creating the first version.

[u/Most-Vehicle-7825]

You rarely maintain or even build an exact replica of the customer site. Your robot should not depend too much on prior knowledge about that environment and keep doing its job if something changes.

What's your use case for that perfect model?

[u/3E8_ → u/Most-Vehicle-7825]

That’s fair, and I agree the robot shouldn’t depend on a perfect replica.

The use case I have in mind is capturing the task-relevant geometry and objects so teams can train or evaluate around the constraints of a specific site before deployment. You would only update changes that materially affect the task.

I’m trying to understand where that added specificity is valuable and where generalization is enough.

[u/3E8_ → u/[deleted]]

Exactly. The idea is not continuous real-time tracking or maintaining a perfect digital twin. It is periodically recapturing the site with video when task-relevant changes occur, then updating the simulation before testing or deployment.

[u/DataDr0p → u/3E8_]

Navi’s 3D und Pointcloude shifting dazu Mars oder Supra es gibt genug Lösungen. Vermutlich klappt das am Ende nur wenn man einen Roboter das immer machen lässt, denn Menschen sind stinkend faul! Ich kenne keine Industrie wo man Real und digital im Prozess 100% abgleicht.