Parts on the record, purchasing in your ERP
Identify parts against the taxonomy, consume them on the work order, keep stock where it already lives
Which part sits where, and which job used it
A maintenance record is only as good as its lowest level. Magnus Reactor carries parts as level 9 of the taxonomy, so a bearing is not a line in a storeroom catalog but a named position inside a maintainable item, inside a subunit, inside an installed unit at a tag. The part master gives each item one identity per manufacturer; the class bill of materials says what an equipment class is built from; the as-built BOM says what this serial actually contains.
Stock balances, reservations, requisitions and goods receipt stay in your ERP, by design. Most operators already run purchasing there, and a second ledger of the same numbers is a reconciliation job nobody asked for. Magnus Reactor records the two things the ERP cannot: which position a part occupies, and which work order consumed it, at what quantity and unit cost.
See consumption on the work orderBenefits
Identify every part once
Give each part a master record with a part number unique per manufacturer, a description, a unit of measure, a supplier reference and an insurance-spare flag. One identity, referenced from every BOM and every work order.
Build the BOM from the class
Define the parts an equipment class is built from at levels 8 and 9, then instantiate the as-built bill of materials on each installed unit. New serials inherit the structure; deviations are recorded on the unit.
Record consumption where the work happens
Consume parts on the work order against the item position they went into, with quantity and unit cost. Materials accounting and the reliability record are the same entry, made once.
Integrate with the ERP, do not duplicate it
Stock, reservations, requisitions and goods receipt remain in the system your purchasing team already trusts. Magnus Reactor supplies the part identity and the consumption; your ERP keeps the ledger.
Identify, build, consume, trace
Identify each part once, per manufacturer
Register a part with the fields that make it findable and unambiguous: part number unique per manufacturer, manufacturer, description, unit of measure, supplier reference and an insurance-spare flag for the items you hold against a failure you hope never happens. The same master record is referenced from every class BOM, every as-built BOM and every consumption line, so a bearing carries one identity whether it sits on a pump in the fuel treatment module or on a compressor two plants away. ISO classes and your own company-authored classes reference the same part masters.
- Part number unique per organization and manufacturer
- Unit of measure carried into every consumption line
- Insurance-spare flag for strategic holdings
- Supplier reference for the purchasing hand-off
Define what an equipment class is built from
Describe the parts an equipment class contains at levels 8 and 9 of the taxonomy: the maintainable items and the parts inside them, each with a quantity. A centrifugal pump class names its impeller, its mechanical seal, its drive-end and non-drive-end bearings; every unit of that class starts from the same structure. Because the class BOM sits on the class, not the tag, it is authored once and applied to every installed unit, and the item tree it produces is the same tree failure events and work orders code against.
- Levels 8 and 9 derived from class item templates
- Quantity per part position
- One structure per class, applied to every unit
Record what this serial actually contains
Instantiate the class BOM on the installed unit to get the as-built bill of materials: the parts this particular serial is built from, in its particular positions. When the unit is overhauled with a different seal or the manufacturer supersedes a bearing, the change lands on the as-built BOM of that unit, not on the class. Because the BOM lives on the equipment unit rather than the tag, it travels with the serial through every change-out, so a spare in the warehouse keeps its parts list while the tag keeps its history.
- Derived from the class BOM, adjusted per unit
- Follows the serial through change-outs
- Visible from the installed unit on the tag record
Consume parts on the work order
Add a part line to the work order with the part master, the item position it went into, the quantity and the unit cost. The line is part of the same maintenance record that carries labor, resources and delays, so the cost of a job and the parts that went into it are one entry rather than a reconciliation between two systems. A work order held up waiting for a part records a spare-parts delay reason and a spare-part location, so the reliability record explains the downtime as well as the repair.
- Quantity and unit cost per consumption line
- Linked to the item position, not just the tag
- Spare-parts delay reason and spare-part location on the work order
Find every unit that contains a part
Ask where a part is used and get the answer across the register: every class BOM that names it, every as-built BOM that contains it, and every work order that consumed it. When a supplier issues a notice on a batch of seals, you know which serials carry them and which tags those serials are installed at today. When a part is proposed for de-stocking, you see how many positions still depend on it and how often it has actually been consumed, before the ERP decision is made.
- Where-used across class BOMs, as-built BOMs and work orders
- Resolves to the tag through the current installation
- Evidence for stocking decisions made in the ERP
From class to consumption
One chain of records, from the part's identity to the signal that a position is consuming too many of them.
Create the part master
Register the part with its manufacturer, description, unit of measure, supplier reference and the insurance-spare flag.
Part number unique per organization and manufacturer
Define the class bill of materials
Name the maintainable items and parts an equipment class is built from at levels 8 and 9, each with its quantity.
Every part position references a part master
Instantiate the as-built BOM
Apply the class BOM to the installed unit and record any deviation on that serial, so the parts list travels with it through change-outs.
Consume parts on the work order
Add each part used with the item position, the quantity and the unit cost, in the same record that carries labor and delays.
Consumption line names the item position it went into
Trace where a part is used
Query a part and see every class BOM, every as-built BOM and every work order across the register that references it.
Read the worst-actor signal
Consumption at level 9 reveals what stops at level 8: this bearing position has consumed four bearings in three years.
Hand stock and purchasing to the ERP
Raise the requisition in the ERP against the same part number. The supplier reference and unit of measure on the part master are the ones your purchasing system already uses, so the consumption line maps to an issue there without a second ledger.
Part of one record
Parts are one level of the same record every other product writes to.
Asset Management
Anchor the BOM at levels 8 and 9
The bill of materials is the bottom of the nine-level taxonomy in Asset Management: class item templates define levels 8 and 9, and the as-built BOM is instantiated on the installed unit at the tag.
Work Orders
Record consumption with quantity and cost
Each part line consumed in Work Orders names the part master, the item position, the quantity and the unit cost, inside the same maintenance record as labor, resources and delays.
IoT & Metering
Read the worst actor against service time
Consumption per position joins the operating hours recorded in IoT & Metering surveillance periods, so a bearing position that consumes bearings faster than its peers stands out against real service time.
Questions we are asked
In your ERP. Magnus Reactor does not keep a stock ledger. It records which position a part occupies, through the class and as-built bills of material, and which work order consumed it, at what quantity and unit cost. Purchasing, reservations and goods receipt stay where they already run, so there is no second inventory to reconcile.
Yes. A consumption line on the work order names the part master and the item position it went into, and the work order names the tag and the installed unit. Where-used resolves the other direction: from a part to every class BOM, as-built BOM and work order that references it across the register.
The as-built BOM lives on the equipment unit, the serial, not on the tag. When an overhauled unit is installed at the tag, the tag keeps its change-out history and the incoming serial brings its own parts list. The unit that came out keeps its BOM as a spare or in repair.
No. Define the class bill of materials once for the equipment class, and every installed unit of that class starts from it. Record deviations on individual units as you find them. Work orders can consume parts against the class positions from day one, and the as-built detail improves as jobs are done.
Consumption at level 9 gives failure events and work orders something to count. A worst-actor query at level 8 can say a pump's bearing subunit fails often; with parts recorded it can name the bearing position that consumes more bearings than its peers, at a known unit cost, against known operating hours.
The part master carries the supplier reference and unit of measure your ERP uses, so a consumption line maps to an issue in the ERP and a requisition can be raised there against the same part number. Magnus Reactor is the source for what was fitted where; the ERP remains the source for what is on the shelf.