For the people at the machine

Technicians are there to fix things, not to write them up.

Every tool that asks a maintenance technician to document more gets used for three weeks. Norlan is built the other way round: your technicians solve the problem the way they already do, out loud and with their hands dirty, and the writing is the software's job. What the plant needs to keep gets kept, with their name on it.

Book a demo See a machine's thread

Rotary filler RF-880 · Berlin

Note · R. Ortega · 12 Mar

Note

0:09

“Manifold needs re-torquing after the first hour at full speed. Every time, not in the manual. Half a turn on the two front bolts.”

Attached to the assetCited by the assistant

Does not open a thread.Turn into an incident

What technicians ask for

“Simple systems to capture experience. On the phone, with the photo and the video, while the job is happening.”

That is the whole of it. A thread is what happens when you stop asking them for a report and keep the conversation instead.

Will they use it?

What has to be true for a technician to keep using it.

None of these is a feature. They are the reasons a tool survives contact with a real shift, and they were written from what technicians told us during validation.

They talk instead of typing

Gloves on, torch in one hand, the line waiting. A voice note is transcribed and attached to the machine, and it counts as much as a typed report.

Nobody grades their writing

Typos, half sentences and the word they use for that part rather than the one in the manual. Norlan tidies it into something the next person can follow.

They stay the author

The AI proposes the wording, never the facts. The technician's name is on what they found, and nothing gets published because a model was confident.

They ask the machine before they phone someone

The machine answers at three in the morning, with the manual page and what was done to it last time, so nobody has to wake the one person who knows.

Not another feed to keep up with

The thread is the machine's history, not a plant social network. It is there when they open the asset, and it does not chase anyone on their day off.

One phone, in front of the machine

The thread, the photos, the step-by-step guides and the manuals on the phone they already carry, not on a terminal at the other end of the plant.

What they send, and what gets recorded

They talk. Norlan writes.

Norlan takes the writing off their hands and keeps them as the author. They talk, take a photo, type in their own language with the typos of someone holding a torch. Norlan records what the plant needs.

Voice, clean-up and self-corrections
Plant context: asset, component, cause
Reading in another language

What the technician sent

T. Walker · Maintenance

0:41

“uh… so, the, the motor on the detector, the one on line two, um… it's making a weird noise, like, after the format change… [4 s] … I checked the relay and, eh… nothing, so… yeah. [6 s] … no no, wait — not the motor, I mean the belt, the conveyor belt. And it's line one, not two. [2 s] … that's it.”

06:31

What Norlan records

Abnormal noise from the conveyor belt after the format change. Relay K4 checked — no fault found.

Metal detector MD-3000S1-PK-L1-0051Conveyor belt

Transcribed
Self-corrections applied
Cleaned up
Anchored to the asset

Original kept · Author: T. Walker · A person confirms before it publishes

What maintenance managers ask about their teams

Is this more paperwork for my technicians?

Less, in the moment that matters. The conversation where they are solving the problem is the record, and a voice note counts as much as typing. The one deliberate act is approving a procedure, and that sits with you, not with the person holding the torch.

Do they have to write in good English or in the manual's words?

No. They write or talk the way they would to a colleague, in their own language, with the name they use for the part. Norlan does the tidying and they check it. If it gets a fact wrong they correct it, and the corrected version is what stays.

Will my senior technicians get phoned even more?

The opposite is the point. Most of the calls they get are questions the machine's own record could answer, and Norlan answers those at three in the morning without waking anyone. The ones that reach them are the ones that genuinely need them.

What happens to what they know when they leave?

It stays with the machine, attributed to them. That is the whole idea: the exceptions your best people carry stop being something the plant loses when they retire, change shift or go on leave.

How much training does it take?

An hour at the machine. It looks like the group chat they already use, on the phone they already carry, and the manuals are loaded before they open it for the first time.

Book a demo

A 30-minute walkthrough built around the plant's machines, not a canned demo.

We start with the operation — which failures repeat, who gets called when something breaks, what the CMMS does not hold — and then show how Norlan would work on it.

What we usually cover

How an incident flows today, from detection to fix
Where the conversation actually happens: the systems, or calls and WhatsApp
What takes longer — the diagnosis, or getting the right people and information together
How much of what a technician knows is written down, and what happens when they are away
Which tools are really in play: CMMS, ERP, mobile, paper
What a pilot would measure, and how

Pick a time that suits the plant. Bring one failure that keeps coming back.

Book a demo

The call is with the people who build the product, with no qualification call first. Norlan is pre-general-availability and shaped with maintenance teams in pharma and food processing.