Digital twins start with a survey, not a dashboard

Most digital twin projects begin with a demo of the viewer and end with an argument about the data. The 3D model is the easy part; every vendor can spin a city on a screen. The hard part is that the model has to agree with the ground, and the ground was never captured to the accuracy the use case needs.

Start from the decision, not the visualization. If the twin exists to replace field inspections, it needs survey-grade capture of the assets being inspected — not a decorative mesh draped over old imagery. If it exists for planning, coarser capture is fine but the parcel and utility layers underneath must be authoritative. Accuracy requirements flow from the questions the twin must answer.

The second failure mode is staleness. A twin captured once is a souvenir; the value is in the update cycle. Before building anything, decide what gets re-captured, how often, and by which sensor — then size the budget for years two and three, not just the launch.

Teams that succeed treat the twin as a survey program with a good interface, not a visualization program with a data problem. That ordering is the whole trick.