1. Captured by the operator
The data is entered by the person living it, when and where it happens, offline and underground.
Inspections for every trade
One field-capture layer, for the whole site
The page for operations leadership and IT teams. One application to deploy, consistent data across the whole site.
TODAY
Each trade gets by with whatever it has on hand: paper here, a tool picked on its own there. Formats that don't talk to each other, training to repeat, licenses and contracts that keep multiplying, and field data that can't be consolidated across the site. Meanwhile, the heavy systems plan on outdated information, because the field never reaches them in time. And every tool that adds its own mobile app doesn't make the silos disappear: it moves them onto the worker's phone.
With Spotd
A single field-capture layer. The same form engine serves every trade, with a view by trade for each employee. Information is captured once, where it originates, even offline and underground. The supervisor validates and prioritizes, which makes them the quality checkpoint for the data. The routine runs and the information is routed to the right system with the right workflow. Spotd doesn't replace anything; it makes what's already in place work.
Each trade tracks what matters to it
The same capture feeds separate dashboards. Maintenance tracks its anomalies by equipment and its hour readings. Health and safety tracks its hazardous conditions and its rounds. Production tracks its progress and its quantities. Each one looks at what concerns it, from a common source.
That's what gives management a consistent picture across the site without forcing a single dashboard on everyone. The trades no longer argue over what the numbers mean, because they all come from the same entry.
One foundation
Every trade, one application.
- One application to deploy, train on and support
- A view by trade for each employee
- Forms configured in days, not IT projects
- Real adoption, because the field opens a single tool
Every system fed
Your systems finally get the reality of the shift.
- Mine planning
- Maintenance systems (CMMS or ERP)
- ERP and payroll
- EHS
- Historian and operational intelligence
For IT teams
One contract, one deployment.
- Connector-based integrations with the systems in place
- Data governance and role-based access management
- One foundation to maintain instead of six tools
- Technical file provided for your approval process
For management
Consistent data across the site.
- No more licenses multiplied by trade
- Uniform proof of compliance from one department to the next
- Operations run on fresh information
- The development plan built on field reality
BACKING IT UP
What makes the scenario work
01
One foundation to maintain
One application to deploy, teach and support, with a view by trade for each employee.
02
Forms your teams evolve themselves
The engine is configurable and each trade adjusts its own, in days rather than IT projects.
03
Routing to your systems
Every report goes to the right system, with the right workflow, with no re-entry.
THE FORMS
Your trades' forms, built in days
The form engine is configurable. We start with the ones you already have, then your teams build the rest themselves. Any type of form can be configured for any trade, in days rather than IT projects.
Production
- Drilling and depth report
- Breakthrough report
- Mobile equipment pre-op
- Tasks to complete and timesheet
Maintenance
- Vehicle and equipment pre-op
- Periodic mechanical inspection
- Service report
- Anomaly tracking by machine
Health and safety
- Workplace OHS
- Supervisor round
- Hazardous condition report
- Incident report
Environment
- Dike inspection
- Piezometer round
- Spill report
- Field campaign follow-up
Technical services
- Face inspection
- Rock mechanics reading
- Airflow reading
- Geotechnical checkpoint
Mill
- Daily inspection
- Operator round
- Checkpoint verification
- Non-compliance report
Each trade stays in control of its forms
An inspection changes, a requirement evolves, a new machine arrives on site. The trade concerned adjusts its own form, with no queue and no development request. That autonomy is what keeps a field tool alive after deployment.
An answer can be a number, a photo or a sentence spoken out loud
A field form that only offers checkboxes produces checked boxes. The engine accepts numeric readings, choices, lists, free text, signatures and instrument readings. Above all, it accepts the three formats that carry the most information in the field: photos, short videos and voice notes.
That's what raises the precision of what gets reported. A fifteen-second voice note conveys context a text field never will, especially from someone wearing gloves in the noise. A photo settles an ambiguity that three back-and-forths wouldn't have. The report becomes usable by whoever receives it.
Every asset carries its own file
The site's equipment, inspection points and infrastructure make up an inventory. A code affixed to the asset opens its form, and each inspection is added to its file. Location is captured automatically at the moment of entry, placing the asset and the work on the site without anyone having to specify it.
That file changes the nature of the decision. An anomaly flagged for the third time in a month no longer reads as an isolated incident. The history per asset lets you order the part, book the labor and schedule the repair before the breakdown, rather than after.
Who it's for
Operations leadership, IT teams, mining engineering, the control room. The people who see the silos from above and pay the price every week.
Your trades, your systems, your IT constraints. We'll build the picture with you
