Monitoring
All systems on one screen: what works, what is down and why. Anything that can be polled over SNMP, Modbus or HTTP can be connected.
Techcom Mine · software for mines
All mine systems on a 3D model
Where every device stands and every cable runs, what is happening to them now and who is fixing it.
Why it matters
Every year a site runs more systems — and people's safety depends on many of them
- Communications
- Data networks
- Positioning
- Fire alarm
- Ventilation
- Video surveillance
- Power supply
Each system has its own software and its own owner, but nobody sees the whole picture. Techcom Mine brings them together on one 3D model of the site.
Planning growth
A new network is drawn on the model: the length of every cable and the device count by type are visible at once, and everything exports to Excel.
Asset records
What is installed on site and how much of it: where, since when, who is responsible, and which spare parts are in stock.
Response
An alarm, its cause, a ticket to the right team and a Telegram and email notification — in seconds, not after a walk-through.
The sooner the cause is found, the sooner the system people underground depend on is working again.
Measurements
35–40frames per second
A 4-million-triangle model on an office laptop with integrated graphics
0.5 sfrom alarm to screen
200 users at once; sign-in 0.24 s, page 0.6 s (p95)
10,000objects per mine
An edit is saved in 0.17 s, the editor opens in 2 s; 1,000 tags in People
≈1 ssensor event on screen
For streaming sources; ping follows the polling interval
Cascading alarms
One cause behind a hundred alarms
When a switch goes down, everything behind it goes dark. Techcom Mine knows how the network is built: it shows the cause instead of fifteen identical alarms and opens one ticket for the right team.
causeSwitch K-12, level −480no connection since 04:13
behind it14 devices“no connection because of K-12” — not separate alarms
actionTicket #184 → Comms teamnotification via Telegram and email
Features
From the mine model to a ticket for the team
Mine model
Import of STR, DTM, DXF, glTF, OBJ and Datamine. Workings, cables, equipment and marks on one model; several people edit at once.
Monitoring
Ping, SNMP, Modbus and HTTP polling. Status, latency, 24-hour availability and reading charts for every device.
Tickets and spare parts
An alarm turns into a ticket for the team on its own: deadlines, comments, photos. Spare parts stock and requests — right from the ticket.
People
Integration with existing personnel and vehicle positioning systems: tags on the model — who is underground, who is on the surface, where the vehicles are. A 2, 8 or 24-hour trail; Attention shows who has gone quiet.
Communication diagrams
The diagram builds itself from the model — level by level, no manual drawing in Visio.
Sensor thresholds
“CH₄ above 1 % for more than two minutes” — an alarm with a warning or alarm level, for a device type or a specific device.
No network underground
The offline version keeps the project on a laptop or tablet; edit without a connection, then sync with the server and review the differences.
Together, in real time
Several engineers edit the model at once: colleagues' edits appear immediately, and you can see who has an object open.
The dispatcher's phone
Alarm list, device card, ticket and model — in the phone's browser, no separate app.
Who it is for
Everyone sees what matters to them
Dispatcher
Sees the alarm and its cause at once, acknowledges it, calls the team. With positioning system integration, the same model shows where people are.
Communications engineer
A ticket with the location on the model, the device history and the spare parts in stock. Network changes live in the model, not in a folder.
Manager
Availability by system, overdue tickets, what fails most often and what spare parts cost.
Deployment
On the company network. No cloud, no internet
- server
- Docker on the company server; a browser on any PC and phone
- data
- The database stays with you; backups locally, over SFTP or to Google Drive
- access
- Roles and permissions, audit log, API keys
- notifications
- Email, Telegram, events pushed to your systems
- integration
- API for 1C:TOIR, Power BI and your own systems
- languages
- Русский, қазақша, English, Deutsch, Español
- step 1Mine modelFrom the surveyors — in any of the formats above
- step 2Network on the modelWe transfer the diagrams or run a network inventory
- step 3Equipment pollingWe connect monitoring
- step 4Training and launchDispatchers, engineers and managers — each in their own role
For the IT department
Fits inside your perimeter, not next to it
- hosting
- Docker Compose on your server; every library ships with it, no external services
- system monitoring
- /metrics for Prometheus, Grafana or Zabbix; /api/health; health checks on every container
- logs
- Line-by-line JSON for ELK or Loki; a request id in every message
- backups
- Daily, locally and off-site (SFTP, Google Drive); restores are tested automatically, recovery time is shown in the interface
- API and events
- /api/v1 with an OpenAPI 3.1 description and per-project keys; HTTP event notifications (webhook), HMAC-signed, with a delivery log
- access
- Roles and permissions, audit log: who, what, when and from which address
- workstation
- Chrome or Edge, integrated graphics of a modern Intel CPU, a Full HD screen — nothing to install
Questions we get asked
What engineers and IT ask before deployment
How is the model updated as the mine advances?
The survey department exports a file, and it is loaded as a new layer. The previous layer version is kept for rollback; equipment and cables are not touched when a layer is replaced, and the workings keep their look.
Which model formats do you accept?
Surpac STR and DTM, Datamine, DXF, glTF/GLB, OBJ; workings are built from strings automatically. Micromine and K-MINE — from sample files; LAS/LAZ and IFC — on request. Raw survey data is processed by your survey software.
How are equipment records kept?
A location tree of level → block → working; the location is suggested from the nearest working. Datasheet: manufacturer, model, serial number, commissioning date, owner; criticality A/B/C; status in service / under repair / dismantled. Excel export and import with a preview.
Where do alarms and tickets come from?
From polling and rules: loss of connection and reading thresholds with levels. A short dropout is not an alarm. If a node fails, there is one alarm for it, not one for every device behind it. The ticket is created automatically and goes to the team responsible for the zone, with no duplicates when the link flaps.
Where do notifications go?
Email and Telegram — to teams by zone and criticality, with repeats and a delivery log; to your systems — automatically over HTTP. SMS — through your gateway.
What happens if the link to the surface is lost?
The server sits on your network and does not depend on the internet. Devices behind the break show up as one alarm per node. On site you can work without a network using the offline version and sync the edits later.
How do we connect it to 1C:TOIR, SAP PM or Maximo?
There is a read-only API, and alarms and tickets are pushed to your system automatically — enough for it to create work orders. We build a ready connector for your system; we need access to its API.
What computer does a dispatcher need?
Any computer with Chrome or Edge: a 4-million-triangle model runs at 35–40 frames per second on integrated graphics. Nothing to install; on phones and tablets it works in the browser.
How do you update the system, and what if something breaks?
Every release passes more than 800 tests; before an update the server backs up the database itself, and a rollback takes one command. Support lines and response times are set in the contract.
Demo
Three synthetic mines — with alarms, people and tickets
Login on request — it arrives by email. Sign in as a dispatcher, engineer, manager or observer.
SevernySteeply dipping: sublevels and a ramp, radio communication
VostochnyFlat-lying, room-and-pillar, radio communication
ZapadnyVein deposit, rail haulage, LTE and access points