AI that reads the paperwork.
Not a chatbot bolted on the side. MetlSys uses AI in exactly two places it earns its keep: reading the trade’s paperwork into structured records, and answering questions from your live data. Everything it writes, a person confirms.
Ask your live data a question.
It answers from your orders, stock, works orders and ledger — as they are right now.
Guide MODE
Explains how to use MetlSys and takes you to the right screen. New starters stop interrupting the person who knows.
Report MODE
Turns a plain question into a read-only query on your live data — tables and charts on demand, no report writer needed.
Act MODE
Drafts stock codes, POs, quotes, GRNs and allocations — then stops. Nothing posts until a person confirms it.
The guardrail:report queries are read-only and boxed to your company’s data. Write actions are typed, listed, and executed only after explicit confirmation. Your data isn’t used to train AI models.
Example: asked “What's my stock position on 316L bright bar?”, the assistant answers from live company data with a table of batches. Report mode is read-only; write actions always require explicit confirmation.
Paperwork in, records out.
Each capture produces a draft your team reviews — the AI proposes, it never posts by itself.
Mill cert extraction
Reads heat, grade, standard, cert type, chemistry and mechanicals from the MTC PDF and matches it to the batch.
THE MOST ERROR-PRONE TYPING IN THE BUILDING, GONE.
PO & paperwork capture
Customer POs, supplier confirmations, delivery notes and subcontract paperwork become reviewable drafts.
ORDERS KEYED ONCE — BY THE CUSTOMER, NOT BY YOU.
Natural-language stock search
“What 316L bar is over 180 days old?” is a query, not a request to the one person who knows the codes.
ANSWERS WHILE THE CUSTOMER IS STILL ON THE PHONE.
KPI alerts & forecasting
Baselines watch on-time delivery, aged debt and works-order lateness; demand forecasting flags shortages and suggests reorders.
PROBLEMS SURFACE THEMSELVES BEFORE THE MONTH-END MEETING DOES.
Keying a mill certificate, before and after.
No invented time savings — count the steps yourself.
BEFORE · BY HAND
- 01Find the cert in the email chain
- 02Read the heat number off the PDF
- 03Type chemistry into the record — twice, after the first typo
- 04File the PDF somewhere findable
- 05Match it to the right batch by hand
AFTER · WITH METLSYS
- 01Drop the PDF on the GRN
- 02Review what the AI extracted
- 03Confirm — cert filed, matched by heat, gate-ready
SAME CERT · SAME RECORD · [STAT-TBC] MEASURED TIME
New starters find their own way.
Guide mode answers “how do I book in a delivery?” with the steps and a button to the screen itself. A searchable help centre covers every module, and support tickets get AI triage grounded in that same help content — so answers are consistent, not improvised.
The result: onboarding a new office person stops depending on the one veteran who knows where everything is.
“How do I raise a credit note?”
STEPS + A BUTTON STRAIGHT TO THE SCREEN
“Why can't I despatch this batch?”
NAMES THE FAILING CERTIFICATE GATE AND WHO CAN OVERRIDE
“Where do remnants go after a cut?”
EXPLAINS THE WORKS-ORDER OUTPUTS — WITH THE HELP ARTICLE LINKED
Bring your worst PDF.
A crumpled mill cert, a handwritten delivery note, a customer PO in a strange format — watch the capture handle it live.