Your site already has a digital twin. It's the DXF.
How Drox turns the site layout you already have into a live record of what's built, what's tested and what's holding things up.
"Digital twin" has come to mean many things. For some it's a photoreal 3D model. For others it's a SCADA dashboard that only becomes useful after energisation. During construction, neither answers the question the project manager is actually asking every afternoon:
Where are we up to, out there, right now?
The answer usually sits in five places: a progress spreadsheet, a stack of test sheets, photos on somebody's phone, an NCR register, and the site layout drawing pinned to the wall of the site office, with highlighter on it.
Drox's digital twin starts from that drawing.
Start with the drawing you already have
Every solar farm and BESS project already has a site layout. It's a DXF with every block, tracker, inverter, pile and string drawn and labelled, and it's what the team works from.
Upload it to Drox and it becomes more than a picture:
Drox reads every block in the file, from inverters and tracker rows down to individual piles, and builds its own model of the site from them.
AI suggests what things are. It names kinds of equipment, sorts them into categories, and groups them into construction levels such as piling, tracker install and modules. Where you correct it, your answer stays.
Positions come from the drawing itself. Nothing a model returns places, moves or counts anything. A pile is where the drafter put it.
The DXF stays as the background, drawn as it is, so the drawing on screen is the same one the team already knows.
Tags, areas and a status somebody set
Any piece of equipment can become a tag: one inverter, every copy of a tracker block, or everything inside a box drawn on the map. Parts of the site become areas: Block 3, the substation compound, the MV trench route.
Each tag and area carries a status from the project's own list, for example Piled, Racked, Modules, Installed, Commissioned or Defective. Every status change is an update with a note, photos and files. Updates are never edited, so the history of a tag is the history of the asset.
Separately, red dots show trouble from the rest of the project: an overdue inspection form, an open defect, an incident, a late task. Status and trouble never share a colour, so you can always tell "not started" from "blocked".
Twenty piles done in a day don't need twenty posts. Group them, post once, and the update lands on every tag with the same photo, the same note and its own history entry.
Progress you don't have to type
A work package is the chunk of work a project manager actually plans: "Block 3 piling" or "Block 3 tracker install". It has a crew, dates and an activity, and it covers a set of tags or areas.
Its progress is counted, not typed. If the activity is Racked and 412 of the 600 trackers in scope are at Racked or beyond, the package is 69% done. A tracker already marked Modules counts as racked whether or not anybody pressed Racked. When the status on site changes, the number follows.
Scrub through time
A timeline runs along the bottom of the map:
Drag it back and the site replays its own history: which blocks were piled by which day, and where the red dots were.
Drag it forward and it shows the plan, with each package's work spread over its dates and drawn as an outline.
Build view fades the drawing and paints the tags solid, so the picture is simply "what's in the ground".
It's the conversation you'd otherwise have over a highlighted printout, except the colours come from the record.
Testing on the same map
Commissioning teams test at a scale spreadsheets struggle with: thousands of strings, one sheet per test per block. In Drox, a test sheet is a form field holding a table of places: one row per string under the block, with readings, limits and pass/fail worked out the same way everywhere.
Rows are saved as they're tested, offline if need be. The Tests view on the map shows the results where the strings are, and a daily summary says what was tested and what failed.
Out on site
The field app carries the same model onto the phone:
open work packages, the crew's own first;
a light map of the package's tags with a GPS dot;
the status a tap away;
Where am I?, which takes the phone's GPS fix and opens the area you're standing in.
When the drawing changes
Drawings get revised. In a model built on them, that's where things usually go wrong: tags vanish or end up attached to the wrong block. In Drox, a revised drawing is reviewed before it changes the record:
Anything gone, moved, renamed or shifted is listed for someone to tick off.
A tracked tag the new file no longer has is marked gone, never deleted, and stays on the map dashed with its history.
Every earlier version of the drawing is kept and can be opened.
Ask it
The Drox assistant reads the same site model. "How far is Block 4 piling?" "Which inverters are still waiting on commissioning?" "What's blocking the substation area?" The answer comes from the record the map is drawn from, with the same access rules as the screens.
What it isn't
It isn't a 3D render, and it doesn't replace your SCADA after handover. It's a working record of construction, built from the drawing you already have and kept current by the people doing the work. That's the twin a project actually uses every day between notice to proceed and energisation.
Want to see your own site layout in Drox? Book a demo and bring the DXF.
