SOP automation for MRO, pharma and lab

The only person who knows that pump retires in March.

Procedo turns your training recordings into approved, audit-ready procedures — and answers your technicians in plain language, citing the exact step and the second of video it came from.

Runs on your hardwareHash-chained audit log21 CFR Part 11 ready
07:42TuesdayP-3

The seal starts weeping onto the plinth.

Nine years without trouble. By eight the line behind it has stopped and a supervisor is asking for an ETA.

Fault · mechanical seal
08:10The fixfrom memory

R. Mehta locks it out and strips the seal.

Nineteen years on this plant, and no manual comes off the shelf. Sleeve cleaned to bare metal, fingers nowhere near the carbon face, gland brought down in a star.

No procedure opened
11:05Back on linefixed

It runs. The job card says “seal replaced”.

Three words for forty minutes of judgement. Nobody wrote down the part that mattered, because the line was down and writing it down was never the urgent thing.

Knowledge held by: one person
MarchRetirement—

Nineteen years drives out of the gate.

The pump is fine. The plant is fine. What just left is the only copy of how this particular machine goes back together.

Handover: none
AprilSame sealagain

Same weep, same plinth, same stopped line.

The new engineer has the drawing, the spares and the torque chart. What nobody has is the sentence about the carbon face.

Fault · unresolved
04:18On the screenMNT-SOP-0142

The sentence he said, on a tablet, nine months later.

Procedo read the eighteen minutes, drafted the procedure and had it approved. The answer carries step 6 and the second it was spoken — not a document to go and find.

MNT-SOP-0142 §6 · 04:18
09:20The fixby the book

Same job. Right the first time.

No guessing at the gland torque, no fingerprint on the carbon face. The procedure says what the man said, and the step is pinned to the part it acts on.

Following §6 · 18 N·m star
11:40Back on linelogged

And this time it is written down.

Who did it, which revision they followed and when — in the chained trail. The next person to meet this pump will not have to find anybody.

Audit trail · rev 3 · signed

Scroll — this pump has a year to get through

Asset P-3Goulds 3196 · 2×3-8MNT-SOP-0142 · rev 3Running · 1450 rpm
18:42 becomes 9 stepsOne night-shift recording becomes a numbered procedure with hazards called out, in about six minutes.
Every answer citedNot "see the manual" — the step number and the second of video the answer came from.
Nothing auto-publishesA named reviewer approves each revision. Pharma and lab sites sign electronically.
Air-gapped optionTranscription, drafting and search run on your own GPUs. No recording leaves the plant.

The actual problem

Tribal knowledge doesn't survive a shift change.

Three things are true on every site we walk, and none of them are solved by writing another document.

01

It lives in one person's head

The technician who can hear a failing bearing learned it across nineteen years. None of it is written down, and the write-up never happens, because the write-up is always less urgent than the line that's down right now.

02

The binder is already wrong

Last revised before two retrofits and a drive change. Nobody trusts it, so nobody opens it, so it drifts further out of date. The real procedure is a photo of a whiteboard in someone's phone.

03

The video is eighteen minutes long

Someone did record the rebuild. Nobody is going to scrub through it at 3am with a pump down and a supervisor asking for an ETA. Recording it was never the hard part — finding the forty seconds that matter is.

Where the thirty-five minutes goes

Minutes · one stoppage · same scale
Today35 min
4Walk to the control room · 4 min
9Find the binder or the drive · 9 min
6Realise it is the wrong revision · 6 min
11Call someone who has done it · 11 min
5Re-read the right step · 5 min
With Procedo1 min
Ask, then read the cited step · 1 min
0 min102030
Walk to the control room
Find the binder or the drive
Realise it is the wrong revision
Call someone who has done it
Re-read the right step
Ask, then read the cited step
A stoppage doesn't cost you the repair time. It costs you the half hour before the repair starts. Procedo doesn't make anyone turn a spanner faster — it removes the hunting.
View as table
StageMinutes
Walk to the control room4
Find the binder or the drive9
Realise it is the wrong revision6
Call someone who has done it11
Re-read the right step5
Today, total35
With Procedo, total1

The product

One recording. Three ways in.

The video, the transcript and the approved procedure are the same object seen three ways — and the chat answers from all three. Switch between them.

Videos / P3-seal-replacement.mp4PUMP18:42Processed · 11 chapters · 9 steps
04:18:1204:18 · Seal face handling
Chapter 04 · 04:12 – 05:30R. Mehta · night shift · 11 Mar
01Isolation and LOTO00:00
02Draining the casing02:40
04Seal face handling04:12
07Coupling alignment12:05

Mechanical seal replacement — centrifugal pump P-3

MNT-SOP-0142 · rev 3 · APPROVED 11 Mar by A. Fernandes
ISO 55001 · OSHA 29 CFR 1910.147 · effective 12 Mar

Purpose

Replace the mechanical seal on P-3 without damaging the shaft sleeve or disturbing coupling alignment.

Prerequisites

Personal lock and tag · lint-free wipes and IPA · torque wrench 5–25 N·m · replacement seal kit 3196-MS-2 · dial indicator.

Steps
  1. 01Lock out P-3 at MCC-4. Verify zero energy and apply your personal lock.
  2. 02Close suction and discharge isolation valves. Tag both.
  3. !Drain the casing to the pit. Confirm 0 psi at the gauge before loosening the gland.
  4. 06Slide the seal assembly off the shaft sleeve. Do not touch the carbon face.
  5. 08Torque gland nuts to 18 N·m in a star pattern.
Troubleshooting

Weeping after start-up → contaminated face, grit under the elastomer, or uneven gland torque. Re-check in that order.

Content hash sha256 9f2c4e1b…41ab7d30
Computed over the number, version, title and steps. Edit any step and the hash moves — which is what the audit chain watches.

The mechanism

What a citation actually is.

Drawn as the machine it would be if you had to build it out of metal: a reel of tape, a reading head on a rail, an index drum of eleven chapters, an engraved plate of steps. The lit rod is the citation.

Fig 1Transcription bench · MNT-SOP-0142
Running the chapters · drag to turn it, or pick one belowCH 04 04:52 step 3/9 conf 91%
Trace rod — the citation
Active step, chapter mark, gate lamp
Tape — the recording
Reading head and index drum
The drum detents into one of eleven chapters, the head travels to that point on the tape, and the rod lands on the step that chapter produced. The dial reads the confidence behind it. Every number shown comes from the same model that moves the parts.

How it works

Record it once. Procedo keeps answering for it.

Three steps, and only the first one asks anything of the person who knows the machine.

STEP 01

Point a phone at the job

Shop noise, accents, three people talking over each other. The industry vocabulary is loaded before transcription, so the words come out right.

  • Whisper transcription, then topic segmentation into chapters
  • Pack terms bias the decoder — "septum", "LOTO", "TIR" survive
  • Original stored in S3; the container's disk is scratch
STEP 02

Procedo drafts the procedure

Purpose, scope, prerequisites, numbered steps, safety warnings and troubleshooting — the sections your framework requires, filled from what was said and shown.

  • Torque values, part numbers and clearances pulled verbatim
  • Hazards promoted out of the step text and flagged
  • Nothing stated that isn't in the recording
STEP 03

Your reviewer signs it off

A draft answers nobody. It becomes the live procedure when a named person approves that revision — electronically, where the framework demands it.

  • Revision history with a diff of what changed
  • Content hash recomputed on every edit
  • Approved revision is the only one the chat retrieves from

Industry packs

Your framework, not a generic template.

A pack sets the vocabulary loaded before transcription, the sections the SOP must carry, the numbering, and whether an electronic signature is required before a procedure goes live.

MNT-SOP

Industrial maintenance, repair & operations

ISO 55001OSHA 29 CFR 1910.147 (LOTO)

Equipment auto-categorised across PLC, motors and drives, pumps, hydraulics, conveyors, boilers, switchgear, presses and safety work. Lock-out/tag-out is flagged as a hazard rather than buried in a step.

VFDP&IDarc flashPSVCMMSvibration analysis

Approval required · signature optional

QA-SOP

Pharmaceutical manufacturing & QC

21 CFR Part 211 · Schedule MICH Q10 · ALCOA+

Written for sites carrying USFDA 483 risk. References and attachments are required sections, not optional ones, and every record carries ALCOA+ attributes so the trail stands up in an inspection.

OOSCAPAdeviationBMRasepticIQ OQ PQ

Electronic signature required

SOP

Laboratory instrument service

ISO 1702521 CFR Part 11

HPLC, GC-MS, UV-Vis and FTIR service work. Column installation, inlet liners, septa and detector baselines are in the decoder's vocabulary before a word is transcribed — which is the difference between a usable transcript and a funny one.

retention timemobile phasedegasserneedle washFID

Electronic signature required

Where it fits

It sits beside the CMMS, not instead of it.

Your work orders stay where they are. Procedo is the layer that makes the procedure attached to them worth opening.

InTraining recordingsPhone video, screen capture, a handheld on a rebuild.
InExisting SOPsThe PDFs and Word files already in the drive.
InWork ordersFrom SAP PM, Maximo, Fiix or whatever you run.
Procedo

Transcribe → draft → approve → index

01Transcribe and segment~4 min
02Draft against the industry pack~2 min
03Human approval and signatureyour pace
04Embed and index for retrieval~20 s
05Answer, with citations~3 s
OutThe technician's phoneAsk in plain language, get the step and the clip.
OutBack onto the work orderThe approved procedure, linked where the job already lives.
OutThe inspector's exportProcedures, revisions and the full chained trail.

Nobody has to change how they work. The technician still opens the work order. The planner still schedules in the CMMS. The only new habit is recording the job once, by the person who already knows how to do it.

Accuracy and control

How you know the procedure is right.

This is the question that decides the deal, so here is the whole answer rather than a reassuring sentence.

Grounding

Nothing appears that wasn't said or shown

Steps are drafted from the transcript and the frames, not from what a model knows about pumps in general. If the recording never states a torque figure, the step doesn't carry one — it says the figure is missing, which is a useful thing for a reviewer to see.

Refusal

An unsupported answer says so

Every answer carries its sources and a confidence. Below the threshold, or with no passage in an approved SOP behind it, the chat says it doesn't have that rather than producing a plausible paragraph. Silence is the correct output at 3am.

Integrity

The procedure is hashed, not just saved

A SHA-256 is computed over the number, version, title and steps — content_hash. Change a torque value and the hash moves. The audit chain records the move, so a silent edit isn't a thing that can happen.

Ownership

A person signs, not a model

Procedo drafts. A named reviewer approves. On pharma and lab packs that approval is an electronic signature, and the approved revision is the only one retrieval will touch. The responsibility stays where your framework already puts it.

Compliance

Built for the audit you haven't scheduled yet.

Six things an inspector asks for, answered by the system rather than by a person going through folders.

Immutable log

Hash-chained audit trail

Every upload, edit, approval, question and answer is written to a chained log. Altering an earlier entry breaks the chain, and the break is visible.

Approval

Named sign-off before publish

A draft is a draft. It answers nobody until a named reviewer approves that specific revision, and the record says who and when.

Data residency

On-premise or air-gapped

Whisper and the drafting model run on your hardware if you need them to. For defence and pharma sites, nothing crosses the boundary.

Access

Scoped by line and area

A contractor on the packing hall doesn't see switchgear procedures. Roles map to areas, and every view is logged against a person.

Signature

21 CFR Part 11 where it applies

Pharma and lab packs require an electronic signature before a revision becomes effective, with the signer, meaning and timestamp bound to the record.

Export

Everything leaves in one file

Procedures, revision history and the full trail export for an inspector, or for the day you decide to run this somewhere else.

Audit trail — MNT-SOP-0142 · last five entries
TimeActorActionObjectChain
11 Mar 14:22A. Fernandesapproverev 39f2c…41ab
11 Mar 14:08R. Mehtaeditstep 8 torque 14 → 18 N·m41ab…7d30
11 Mar 09:51S. Kulkarnicommenthazard before step 37d30…b612
11 Mar 06:14procedodraftrev 1 generatedb612…0c87
11 Mar 05:58R. MehtauploadP3-seal-replacement.mp40c87…genesis

Deployment

Useful in week two. Not month six.

There is no data migration and no integration project to start. The first SOP exists before anything is installed.

Phase
Week 0Week 1Week 2Week 3Week 4
Send one videoNo commitment
We return the SOP
InstallDocker or hosted
VM, SSO, first users
Load the backlog10–20 recordings
Reviewer approves the first batch
Technicians askLive on one area
Gaps show up as unanswered questions
Close the loopRecord to fill gaps
Ongoing

The fourth row is the one that matters. Questions nobody can answer are a list of the recordings you should make next — which is the first time most sites have had a ranked, evidence-backed answer to “what should we document?”

What it's worth

Your numbers, not someone else's case study.

The cost isn't the software. It's the half-hour a technician spends finding the right procedure while the line is stopped. Put your own figures in.

Downtime cost recovered per year$367,200

Assuming Procedo answers in under a minute — which is what a cited answer against an approved SOP actually takes.

Hours back per year82
Per technician per year$9,180

We don't publish other companies' savings figures, because they tell you nothing about your plant. Run it with your worst line and your real downtime rate.

Packaging

Priced per site. Never per question.

Charging by the seat would mean charging you for technicians asking questions, which is the one behaviour the whole product exists to encourage.

Pilot

One area

Prove it on the line that hurts most, with a fixed scope and a fixed fee.

  • Up to 25 recordings
  • Hosted, one industry pack
  • Unlimited technicians
  • Six weeks, then decide

Fixed fee · no auto-renewal

Site

One plant

Everything one plant records, with the integrations and the sign-off your auditor expects.

  • Unlimited recordings and users
  • On-premise or hosted
  • SSO, role scoping by area
  • CMMS work-order linking
  • Electronic signature where required

Annual · per site

Enterprise

Multi-site

Several plants, shared procedures, and the environments that can't touch a network.

  • Air-gapped deployment on your GPUs
  • Custom industry pack built with you
  • Cross-site SOP library
  • Named support engineer

Annual · negotiated

No per-question or per-minute charge. Transcription on your own hardware costs you electricity, not licence fees — so the more your team asks, the better the deal gets rather than the worse.

What you're already thinking

The four objections we get every time.

Asked on every call, so answered here instead of on the call.

Our recordings are terrible.

They all are. Compressor noise, phone held sideways, half of it in Marathi. That's the normal case, not the edge case — send us the worst one you have and judge the output rather than the promise.

Plant data can't go to a cloud.

Then it doesn't. Transcription, drafting and search all run on hardware you own, inside your boundary. The hosted option exists because some sites prefer it, not because anything requires it.

We already have SOPs.

You have documents. The question is whether a technician on nights can get the right step out of them in under a minute, and whether the document matches the machine after the last retrofit. Procedo is about retrieval and currency, not page count.

This will hallucinate and hurt someone.

That's the right fear, and it's why nothing publishes without a named approval, every answer carries its sources and confidence, and an answer with no passage behind it in an approved SOP says so instead of guessing.

Next step

Send us one video. Judge the SOP.

Pick your worst recording — the noisy one, the one where three people talk over each other, the one nobody has ever watched twice. We'll send back the procedure Procedo writes from it, with the hazards it flagged and the timestamps it cited. No deck, no discovery call first.

Typical turnaround 24 hours
Recording deleted after review unless you ask us to keep it
Procedo is a product of Ailoitte