Procurement: From Low Stock to Received, Without Leaving the System
Procurement is the second of ProAlert™'s fourteen operational disciplines. It covers everything from noticing that a part is running low through to a received purchase order. Because it sits on the same database as maintenance, the demand signal and the purchase order are never in two different systems, and nobody re-keys a receipt into inventory.
The bottom line: A CMMS (Computerized Maintenance Management System) usually stops at "you are low on this part." ProAlert continues into the quote, the approval chain, the order and the receipt. This is the discipline most plants are surprised to find in a platform like this, and it is the one that removes the most spreadsheets.
What This Replaces
In a plant running a CMMS and a separate purchasing system, the following sequence is manual, and it is usually a spreadsheet:
| Step | How it usually works | How it works here |
|---|---|---|
| A PM schedule for next quarter implies a set of parts | Somebody exports the schedule and reads off the parts by hand | Forward PM parts requirements is a screen |
| Work out which of those parts are not in stock | Cross-reference the export against an inventory report | Stock levels are on the same record as the requirement |
| Request quotes, raise the order, chase the approval | Email, then a second email asking about the first | RFQ (Request For Quotation) and a personal approvals queue |
| The part arrives | Somebody re-keys it into the CMMS inventory | Receiving updates inventory as the receipt is entered |
Every one of those handoffs is a place where the number in the maintenance system and the number in the purchasing system stop agreeing. Removing the handoff is the point.
Purchasing Capabilities
The Purchase Order States
Orders move through a defined state machine rather than a free-text status field, which is what makes the purchasing dashboard countable.
| Status | What it means |
|---|---|
| Draft | Order being assembled |
| Pending Approval | Submitted for authorization, sitting in an approver's queue |
| Approved | Cleared for sending |
| Sent | Transmitted to the vendor, who receives an email notification |
| Acknowledged | Vendor confirmed receipt |
| Partial Received | Some line items received, the rest still outstanding |
| Received | All lines fulfilled |
| Closed | Complete and archived |
Who Uses It
| Role | What they do here |
|---|---|
| Buyer / Purchasing | RFQs, purchase orders, supplier management, forecasts |
| Maintenance Planner | Forward PM parts requirements, stock levels ahead of scheduled work |
| Storeroom | Receipts, issues, transfers, cycle counts |
| Operator | Material requests from the floor on a phone |
| Approver (any role) | A personal pending-approvals queue |
| Controller / Finance | Spend visibility and approval governance |
Common Questions
| Question | Answer |
|---|---|
| Does this replace our ERP purchasing? | Not necessarily, and it depends on the plant. ProAlert covers maintenance and operational procurement: spare parts, consumables and tooling. Many customers keep production material purchasing in the ERP (Enterprise Resource Planning) system and use ProAlert for the maintenance side, connected through the REST API. That decision is part of deployment scoping. |
| Can we enforce who approves what? | Yes. Approval configuration is a first-class screen, with thresholds and approver roles set per organization, and chains can be multi-level. |
| Does it know what we will need next quarter? | For maintenance, yes. Forward PM parts requirements project the parts implied by the preventive maintenance schedule, and the forecasting view projects consumption from history. |
| Is it licensed separately? | Procurement is part of the CMMS side of the platform. Module entitlement is configured per facility in administration. |
See a PM schedule turn into a purchase order.
Book a 30-minute demo... we'll walk the forward parts requirement, the RFQ comparison and the approval queue on your own part categories.
