“Where’s the latest program?”
A laptop. A USB drive. A folder named “final.” Bring approved files and their version history into the machine’s record.
INTRODUCING RESTART BY BLUE RIDGE PLC
Your machines.
With a memory.
Your manuals. Your maintenance history. Your machine’s signals.
Connected intelligence, from first symptom to restart.
Know the machine. Understand the change. Prove recovery.
MACHINE WORKSPACE
Read-onlyProcess pump
Why won’t the pump start?
Fault investigator · 3 sources connected
The low-level input is blocking the start.
The sample logic and recorded input state agree: LS-104 is active. The drive is ready. The physical cause still needs a qualified technician’s check.
The right file. With its history.
Original programs, exports, and the context that makes them useful.
Sample records only. These are not downloadable machine programs.
A backup is only the beginning.
Know what is recorded. Know what has actually been tested.
3/5RECORDED
Recovery not yet proven
Two gaps to close.
The HMI restore test and spare-controller compatibility need evidence.
- ✓ Original file and version recorded
- ✓ Software and firmware identified
- ✓ Recovery procedure recorded
- ○ Spare controller compatibility Open
- ○ Isolated HMI restore test Open
MOTOR & BEARING CONDITION
SYNTHETIC EXAMPLESee the change. Check the cause.
Saved vibration spectrumReference Comparison
Relative amplitude · illustrative unitsRecorded shaft speed: 1,797 rpm
Qualified indication
A new peak needs a second look.
The comparison has more energy near 108 Hz. A single spectrum cannot confirm a bearing fault or justify replacement.
Next check Repeat under comparable speed, load, and sensor placement. Have a qualified technician review competing explanations.
Evidence & limits +
Original synthetic example, PT-104 motor. Reference and comparison are fictional spectra. Recorded speed: 1,797 rpm. Sampling-rate example: 12,000 Hz. No live sensor, model call, or fault classifier is connected.
In a pilot, retain the original measurement, units, speed, load, sensor location, method, and reviewer. An indication remains separate from a confirmed diagnosis.
PT-104 · Illustrative sample dataAI proposes. Your team decides.
Explore the product direction with sample answers and records. Open the existing logic demonstration ↗
WHEN EVERY MINUTE MATTERS
The machine stops.
The search shouldn’t begin.
“Didn’t we fix this already?”
Keep the symptoms, the evidence, and what actually worked. Let the next shift start where the last one left off.
“Will that backup restore?”
See the software, firmware, procedure, and test evidence behind the file. Make the missing pieces visible before a failure.
BUILT AROUND YOUR MACHINE
AI that connects
the dots.
A manual gives you the specification. A service note gives you the history. A vibration record shows what changed. RESTART brings them to the same question.
Manuals & drawingsThe way it was designed.
↘Maintenance historyWhat your team learned.
→Saved measurementsHow the machine is changing.
→Recovery files & testsWhat you can prove.
↗One machine.
One shared memory.
One shared memory.
THE RESULTA better next step.
A better next step.
With the evidence.
Cited answers, clear unknowns, and a record that stays with the machine.
See it in the demo →01 / ARCHIVIST
Organize what you know.
02 / INVESTIGATOR
Trace the likely cause.
03 / CHANGE REVIEWER
Explain what changed.
04 / CONDITION ANALYST
Qualify the signal.
05 / RECOVERY PLANNER
Surface what’s missing.
Inside the RESTART architecture +
AnythingLLM · Your workspace
Ask a machine question. Retrieve approved documents and maintenance history with sources attached.
Docling · Your document intelligence
Extract useful structure from manuals, forms, and drawings. Keep original files and page references.
Scoped evidence MCP · Your machine record
Give agents permission to read a specific asset’s versions, changes, and recovery-test evidence.
Predictive Maintenance MCP · Your condition evidence
Analyze saved vibration measurements, explain competing interpretations, and prepare findings for technician review.
Evidence before confidence. Extraction checks compare field values and their sources against technician-reviewed examples. An ExtractBench-based evaluation workflow is part of the proposed quality approach, not a claim of validated accuracy.
This is the architecture for a scoped RESTART pilot. The website is an interactive demonstration with illustrative records, not a connected AI service. Local models and isolated storage are available design options; deployment, permissions, and integration compatibility must be validated for each pilot.
PLC/HMI program capture uses the appropriate vendor engineering tools. Vibration analysis needs measured signals and operating context. Neither proves that a saved program will restore a machine.
PREDICTIVE MAINTENANCE · PART OF RESTART
Catch the change.
Keep the evidence.
A motor sounds different. A bearing runs rough. Give the next decision something better than a hunch.
Bring saved vibration measurements into the same record as the manual, repair history, and recovery files. Compare with a reference. See what the evidence supports—and what still needs a technician’s check.
Explore machine healthSaved measurementsSource-linked findingsTechnician review
PT-104 / DRIVE MOTORILLUSTRATIVE
OBSERVATIONChange detectedComparison against a saved reference
DECISIONReview requiredA signal is not a confirmed fault
Product preview · synthetic records · no equipment connected
BE READY FOR THE NEXT FAILURE
A file is good.
Proof is better.
RESTART’s recovery record is designed to show exactly where you stand—from a file found to a restore test witnessed.
Keep original files, dependencies, test results, and open gaps together. Give the next technician the whole picture.
Explore recovery proof →↻RESTART
MACHINE RECORDSAMPLE
MACHINE RECORDSAMPLE
Process pump
PT-104 · Line 3
Program baselinev4 · Recorded
Software & firmwareIdentified
Restore procedureRecorded
HMI restore testAwaiting evidence
○
Recovery not yet provenThe next action is clear.
SMALL START. USEFUL FROM DAY ONE.
One machine.
A clearer way forward.
Start where downtime hurts and knowledge is hard to find.
Bring the evidence.
Choose one critical machine. Gather the available logic export, manuals, drawings, service notes, and any saved vibration measurements.
Build its memory.
Agree on the supported formats and scope. Connect the records and identify what’s missing.
Prove the useful part.
Review real fault questions, machine-health indications, and recovery gaps with your team. Measure results before expanding.
SOMETHING TO KEEP
Take the first step
to the shop floor.
Our free, printable checklist helps you find the gaps in one machine’s recovery record. No account. No plant connection.
Open the free checklist ↗SOFTWARE WITH SOMEONE BEHIND IT
Built for the floor.
Backed by Blue Ridge.
Machine knowledge matters most when someone knows how to use it.
Blue Ridge PLC is a department of Blue Ridge Electric Service in Winchester, Virginia. Bring a PLC problem, a recurring communication fault, or a machine whose records need attention. We’ll help define the next practical step.
Old-school
plant service.
New intelligence.
A FEW GOOD QUESTIONS
Clear answers.
From the start.
Can I try it without connecting to a PLC?+
Yes. The interactive preview uses illustrative records and runs in your browser. The free checklist can be printed or kept locally. Neither connects to plant equipment.
Can we start with a motor or pump?+
Yes. A machine-health pilot can start with saved vibration measurements, the equipment manual, and maintenance history. Sampling rate, units, sensor location, speed, and operating conditions need to be known. Indications are reviewed by a qualified technician; AI does not authorize repairs or bearing replacement. This work is scoped separately from the PLC pilot.
Which controllers does the current pilot support?+
The existing PLC First Response Pilot is Rockwell-first: ControlLogix and CompactLogix L5X exports for one qualified, non-safety-critical cell. Manuals, drawings, and other files can provide supporting evidence. Broader RESTART ingestion and recovery workflows are scoped separately, not assumed to support every proprietary format.
What does a paid engagement cost?+
The current PLC First Response Pilot is $24,000 for 90 days: one qualified cell, 2–5 accounts, five reviewed acceptance scenarios, scheduled engineer review, and a final report. RESTART-specific recovery work and ongoing coverage are scoped and quoted separately. There is no automatic renewal. See the current pilot scope ↗
Will AI change our PLC program?+
No. RESTART’s direction is offline and read-only engineering: retrieve, explain, compare, and prepare evidence. Qualified people retain authority over equipment, program transfers, and recovery testing. Read the authority policy ↗
Does this help with NIST recovery practices?+
Asset records, backup documentation, and restore-test evidence can support an OT recovery process informed by NIST SP 800-82 Rev. 3 ↗. RESTART is not a NIST certification or a guarantee of regulatory compliance. Requirements depend on your site and review.
Is this an emergency response subscription?+
The current pilot includes scheduled engineering review within the agreed scope. Emergency response, onsite work, restoration, and after-hours availability require a separate agreement.
LET’S START WITH YOUR MACHINE
Make the next
restart easier.
Tell us what keeps stopping.
We’ll help you find the right starting point.
A short conversation. One machine.
No equipment access needed to begin.