
The whole mine’s data, at a glance.
The figures of the site, a card per domain, a heat map of what was fed today, and the quality issues to look at.
- Late feeds and refused rows stand out.
- Each domain opens its tables and reports.
All the data of the mine in one standard model, with the KPIs defined once, the reports ready, and every AI answer traced to its numbers.
Every system has its own numbers.
Production, the plant, the laboratory, maintenance, energy and safety each keep their data in their own system, and each report computes its KPIs its own way.
Answers from AI are only useful when the numbers behind them are the same as the reports.

Filon is the data layer under OneStop. Your systems and OneStop’s apps write to it, it checks every row and files it in one standard model of the mine, and the reports, the AI and your own programs all read the same numbers from it.
Your systems send their rows to one address, with an API key of your company. Or a person imports a CSV file.
PUT/api/v1/filon/{site}/mine.loads[{ "truck": "HT-101",
"loader": "SH-02",
"material": "HG",
"payloadTonnes": 238.4,
… }]
One truck load, for example. JSON or CSV, with your own codes.

15 domains
One model of a mine site in 122 tables, the same at every site, switched on per site from its mining method.

403 KPIs
Each defined once, with its formula, in English and in French.

65 report pages
Ready by area and adapted to your type of mine, from the site overview to costs.
Then read it your way: the reports, your own pages, Ask Filon and the API.
Your systems push their rows through the API: fleet management, the LIMS, maintenance, the ERP, PI or a script. A person can also import a CSV file. OneStop’s own apps keep their data in Filon as they work.
Every row is checked before it is kept: known fields, types, times with their offset, references by code, the site. A row that fails is refused, never guessed, and listed with its reason.
Each company has its own database, never shared with another. Inside it is one standard model of a mine site: the same tables and names at every site.
One semantic layer computes every KPI the same way for the reports, your own pages, Ask Filon and the API.
Filon’s 65 report pages read the model directly, by area, from the site overview to costs. The same numbers feed the pages you build and the answers of Ask Filon.
Your programs read the same data back with an API key of your company: the rows of any table, the model, the KPIs and a KPI query.
BeforeThe same KPI computed three ways in three reports.
With OneStopEach KPI defined once, with its formula and the reports that use it.
BeforeMonths to build reports for each area.
With OneStop65 report pages ready, by area, adapted to your mining method.
BeforeLate or refused data found at month-end.
With OneStopEach feed’s health every day, and refused rows explained.
Your systems push JSON or CSV through the API, or you import a CSV with columns matched by the AI.
Every row lands in the model of the mine, in your company’s own database.
Data quality checks run every night; each feed shows whether it is on time.
Reports, the dictionary of KPIs, your own pages, Ask Filon and the API.
Each screen below is from the Demo section of OneStop, on a simulated mine. Ask us for a visit to try them yourself.

The figures of the site, a card per domain, a heat map of what was fed today, and the quality issues to look at.

An interactive diagram of the model, with a sheet per table and examples of what to push.

Operations, mine, processing, geology and planning, maintenance, energy, environment, health and safety, and finance.

The definition and the formula of each KPI, in English and in French, its values at your site and the reports that use it.

The AI answers with the site’s own numbers, the same as the reports, and shows how each was computed.

An OpenAPI description to download for your tools, and a "Try it" on your own Filon that only checks a push unless you choose to write.
The OneStop apps share one sign-in, one subscription and one data model, Filon. Here is what this app exchanges with the others.
Core, mine, stockpiles, plant, laboratory, maintenance, energy, environment, safety, supply, planning, finance, workforce, alarms and more, in one database per company.
Push JSON or CSV through the API, or import a CSV with columns matched by the AI.
Each feed on time, late or with refused rows, a 7-day heat map, and the AI explains the errors.
By area, searchable, adapted to your type of mine.
Definition, formula, values at your site and the reports that use each one.
AI answers with their numbers traced, and report pages you build with the AI.
No. Your systems keep running; they push their data to Filon, which brings it into one model.
Yes. Each company has its own database, and personal data and free text are encrypted with the company’s own key.
Yes. The Demo section has Filon on ten simulated mines, fed live; it is read only.
What it reads, what it writes and who sees it. The whole picture: Security and trust.
One database per company, never shared.
Personal data and free text are encrypted with your company’s own key; the data browser marks them with a lock.
The API explorer only checks a push unless you choose to write.
What is true of this app is true of every app of TTech OneStop: your data, your people and your language come first.
The apps read your data through your own AVEVA CONNECT and write back only their own results, in their own streams. Your existing data is never changed.
OneStop runs in the browser. Your administrator sets up one connection to your AVEVA CONNECT, once, and every app uses it.
Your people sign in with their Microsoft work account. Your own admins decide who uses which app.
Every score, alert and AI answer shows its reason and where its numbers come from, in plain words.
Every screen, every message and every report, in the language each person chooses.
Subscribe to the apps you need and add others later. Try each one first in the demo, on ten simulated mines.
Book a demo on our simulated mines, or tell us how you want to use it on yours.