Every machine, every subsystem, every revision, every fault, every PM, every engineering change — connected through a single authoritative graph. The foundation that ForgeOps, ForgeMaint, ForgeSchematics, and ForgeCAD all read from.
ForgeMachine is the authoritative source of record for every physical asset. Every other Forge product reads from and writes to this graph.
Machine identity
Serial number, model, manufacturer, installation date, and location — the root of every machine record.
Subsystem map
Every component, drive, spindle, axis, and sensor catalogued against the machine. PLC I/O signals mapped to physical subsystems.
Revision history
Every engineering change from ForgeCAD linked to the specific subsystem it affects. Full design provenance at the machine level.
Fault history
Every fault, alarm, and deviation recorded with timestamp, sensor readings, and resolution. Feeds MTBF calculations in ForgeOps.
PM record
Every preventive maintenance activity linked to the machine and subsystem. PM outcomes feed machine health scoring in ForgeMaint.
Job history
Every production job linked to the machine — cycle times, scrap counts, tool life consumed. The full production provenance of every part.
ForgeMachine is the authoritative record of every machine: subsystems, revision history, fault history, tooling, PLC I/O catalog, and engineering changes. ForgeOps, ForgeMaint, ForgeSchematics, and ForgeCAD all read from this graph.
Connects to 30+ real manufacturer devices via the Forge I/O catalog. When a sensor fires, ForgeMachine knows which physical component it belongs to — so ForgeOps dispatches a targeted repair, not a general inspection.
Constraint-aware scheduling across your machine list. If a job requires a specific fixture, tool, or material, ForgeMachine won't schedule it until all are available. NC programs and setup sheets pulled directly from ForgeCAD.
Availability, Performance, and Quality per machine, per shift, per week — calculated automatically from live cycle data. No one has to remember to log it. No end-of-shift data entry.
Every fault, PM, and engineering change links to the specific subsystem it affects. When ForgeMaint closes a work order, the component history updates — so the next fault has the full context behind it.
Operators see their queue, job details, and setup instructions on an iPad at the machine. When a job completes, cycle time feeds back into the graph for future scheduling and OEE — no printouts, no clipboards.