Requisition
How does a requisition differ from a Purchase Order in reliability engineering accounting?
A requisition initiates 'encumbrance accounting' to reserve funds internally and is never sent to a vendor, whereas a Purchase Order is the external, legally binding commercial commitment that executes the payment.
What role does the requisition play in the Reliability Centered Maintenance (RCM) data loop?
It bridges the shop floor and finance, ensuring that every dollar spent on spare parts is directly tied to an asset health event (Work Order), allowing reliability engineers to analyze cost-per-failure and optimize maintenance strategies based on evidence rather than convention.
In Smart Materials workflows (e.g., Hexagon PPM), what data triggers the transition from requisition to procurement?
The requisition contains the required material quantity plus contingency, specification, and engineering requirement definitions; once released, it triggers the procurement module to create an inquiry or add to a blanket order.
A requisition is a formal, internal document or electronic request used by maintenance personnel to request the purchase of goods (spare parts, materials) or services for business operations. It serves as an internal 'ask' that triggers an approval workflow before a legally binding Purchase Order (PO) is generated to an external vendor.
In a CMMS environment like ServiceGrid, the process begins when a technician identifies a needed part for a specific Work Order (e.g., WO #4590). The technician completes the requisition form with details like OEM part numbers and quantity, then submits it for supervisory approval. Once approved, the system either retrieves the item from inventory or converts the requisition into a PO for vendor ordering. This ensures that every dollar spent on spare parts is directly tied to an asset health event, allowing reliability engineers to analyze cost-per-failure and optimize maintenance strategies.
Missing Work Order Association: Submitting a requisition without linking it to a specific repair job leads to unbudgeted costs and inability to track reliability data against the failure.
Incomplete Technical Specifications: Providing vague item descriptions or missing OEM part numbers results in vendor delays, incorrect part delivery, and prolonged downtime during emergency breakdowns.
Skipping Approval Workflow (Financial Firewall Breach): Bypassing managerial approval to 'rush' an order commits capital without verifying budget availability, undermining the MRO Financial Firewall and causing encumbrance accounting errors.