Forge
ForgeMaintForgeMaint

What needs attention — and when.
PM. Work orders. Asset health. Reliability.

ForgeMaint answers one question: what needs attention, and when? PM schedules driven by actual runtime. Work orders with schematics attached. Spare parts checked before dispatch. MTBF tracked per subsystem, not per machine. This is not ForgeOps — ForgeOps tells you what is happening right now. ForgeMaint tells you what needs to happen next.

Request EvaluationView Pricing
ForgeMaint — Maintenance
Work Orders
PM Schedule
Asset Health
WO #MachineDescriptionPriorityStatus
WO-2847VMC-01Spindle bearing
HIGH
OPEN
WO-2844HMC-01Coolant system
MED
IN PROGRESS
WO-2841ROBOT-1TCP calibration
LOW
DONE
PM Due This Week
2 tasks
VMC-01 Spindle belt inspection
Due in 2 days

Assign to: Tech-02 · Est. 45 min

Why it's different

"PM schedules that adapt to actual machine behavior — not fixed calendar intervals."

ForgeMaint reads ForgeOps runtime data: actual cycles run, actual hours, actual fault history. A machine that runs 3 shifts gets PM at 2,000 cycles. A machine that runs 1 shift gets it at 90 days. The interval is driven by usage, not a spreadsheet.

"Work orders arrive with the schematic attached — not a machine number and a fault code."

When ForgeOps dispatches a work order, ForgeMaint attaches the relevant schematic sheet from ForgeSchematics in real time. The technician on their iPad sees the wiring diagram for the specific subsystem before they touch anything. Not a binder from the cabinet.

"MTBF tracked per subsystem, not per machine — so you know which component is the problem."

A machine with 3 faults in 30 days could be one failing component or three different ones. ForgeMaint tracks MTBF at the subsystem level: Zone 4 conveyor drive (MTBF: 14 days), main PLC power supply (MTBF: 180 days). The component is the unit of analysis, not the machine.

From scheduled task to verified completion

1

Schedule

Automated

PM schedules generated from machine type, manufacturer recommendations, and actual runtime data from ForgeOps. Calendar-based and usage-based triggers. Technician assigned automatically based on skill and availability.

2

Dispatch

Automated

Work order pushed to technician's tablet. Machine schematic from ForgeSchematics attached. Spare parts list pre-populated from ForgeProcure inventory. Step-by-step procedure from ForgeKnowledge history of previous completions.

3

Execute

Manual

Technician follows work order on tablet. Checks off each step. Records findings, measurements, parts used. Photos attached. If an unexpected fault is found, creates a linked corrective work order without leaving the app.

4

Close and Learn

Automated

Work order closed. Completion recorded against PM schedule. Parts used deducted from ForgeProcure inventory. MTBF recalculated. ForgeKnowledge captures the full completion record — what was found, what was done, how long it took.

Deep detail

PM Schedule Management

Calendar-based and usage-based PM triggers. Adapts to actual runtime from ForgeOps — not fixed intervals.

Work Order Management

Work orders from ForgeOps arrive with context pre-filled. Technician gets machine, subsystem, fault history, schematic, and parts list — before they leave the office.

Asset Health Scoring

Every machine gets a health score based on fault rate, PM compliance, downtime, and age. At a glance — which machines need attention.

Spare Parts Integration

Parts required for a work order checked against ForgeProcure inventory automatically. If stock is low, a purchase request is created before the technician even starts.

MTBF and Reliability Tracking

Mean time between failures tracked per subsystem. Reliability trends over time. Identifies which components drive most of your downtime.

Mobile Technician Experience

Technicians work from their tablet — work orders, schematics, step-by-step procedures, parts list, and sign-off. All in one place, all offline-capable.

MTBF

Per subsystem

Not per machine — find the real problem

0 calls

Parts stockouts

ForgeProcure checked before dispatch

Schematic

On every work order

From ForgeSchematics, real-time

ForgeOps =/= ForgeMaint

Clean separation

What needs attention vs. what's happening

How ForgeMaint connects

Receives from

ForgeOpsWork order dispatch, fault history
ForgeMachineAsset registry, PM specs
ForgeSchematicsSchematics on work orders

Sends to

ForgeProcureParts requests
ForgeKnowledgeCompletion records
ForgeOpsMTBF feedback
Also in Forge
ForgeOpsWhat is happening right nowForgeMachineMachine lifecycle graphForgeProcureBOM-driven purchasingForgeKnowledgeDecision audit