No new systems. No disruption. Live in weeks.
MineTwin connects to the infrastructure you already have. Your data stays in your environment. Your team does not change how it works; it gains a layer on top of what already exists.
We work with what you have
Fleet management, CMMS, environmental monitoring, HR, financials and your document store. Read-only integration into a lakehouse in your tenant. Nothing is replaced and nothing is written back.
Your site in 3D
Satellite terrain, your engineering drawings and the asset library, 90 assets across 20 categories. Every asset placed, every relationship mapped, your operational history loaded into the graph.
Your roles, your KPIs
Role profiles mapped to your org structure, 9 profiles covering 150 or more job titles. Safety targets, KPI definitions, environmental limits. The agent connects to your data and documents. No model training.
Ready before the next rotation
Orientation scripts written with your team, each stop referencing your equipment and procedures. Four durations, live Q&A, completion logged automatically.
A short list
- Read access to the systems above, or an export of each to start
- The asset register and the plant hierarchy as they exist today
- Drawings or survey data for the site; satellite terrain covers the rest
- An hour a week from someone who knows the site, for the orientation script
- An IT contact for the tenant, if the deployment is in your Azure
Your tenant or ours
Dedicated, in your Azure tenant. A deployment we build and operate inside your subscription. Your data never leaves your environment; your IT team holds the keys.
Hosted by MineTwin. The same platform on infrastructure we run, isolated per customer. Faster to start; the integration is still read-only.
Access is role-based at the data layer, so a person sees the same mine in the twin that they are allowed to see in the source systems.
Weeks from data access to a live environment
The build is the same every time; the variable is how fast data access is granted.
| Week | What happens | What you see |
|---|---|---|
| 1 | Connectors and exports land in the lakehouse. Register and hierarchy imported. | Twins listed and typed in Twin Builder |
| 2 | Terrain and placement. Roads and areas drawn. Streams bound to twins. | Your site in 3D with live state |
| 3 | Roles, KPIs and limits configured. Documents embedded. Agent connected. | Expert Agent answering on your data |
| 4 | Orientation authored with your team. Cohorts invited. | First rotation inducted in the twin |
30 days on your site
We connect to your data, build the twin, and put a working guide in front of your team. Your people ask it questions about your mine for a month. At the end you know whether it belongs in the operation, and the twin is already built if it does.
No new infrastructure to procure. No purchase commitment for the pilot.
Start with a conversation.
Tell us about the site and the systems it runs on. We will come back with a scope for the pilot.