OptimalSPARES™ Wiki / Using the app
The app
Using OptimalSPARES™
Three guided wizards take a storeroom from messy data to an optimised, ERP-ready stocking policy, and keep it optimised as demand and criticality change.
The three wizards
| Consultancy wizard | A guided assessment of the current storeroom: data quality, stock value, stockout history and the quick wins, to scope the work and the prize. |
|---|---|
| BoM builder wizard | Build and clean the equipment bills of materials, linking parts to assets so criticality and installed counts flow through. |
| Permanent optimisation wizard | The ongoing engine: recompute criticality, demand and the min, max and reorder points, and keep them synchronised with the ERP as things change. |
The other views
| Classification and cleanse | MMD 3.1 classification, data cleanse and de-duplication against a defined standard. |
|---|---|
| Criticality | Spare criticality from asset criticality, lead time, demand and alternatives. |
| Stocking policy | The min, max, reorder point and service level per part, with the model used shown. |
| ERP readiness | Validated, classified data and stocking parameters staged for load into SAP or another ERP. |
Connected to the platform
OptimalSPARES™ is the materials engine of the Optimal® ARaaS® platform. It takes asset criticality from OptimalAvailability Studio™, inspection and repair materials from OptimalIntegrity Studio™, and remaining-life signals from OptimalTREND™ so a forecast failure can trigger a just-in-time order, and it publishes a spares-health indicator to the ARaaS® Dashboard. The storeroom is wired to the strategy, not run in isolation.
A desk and store tool
OptimalSPARES™ is used by materials and reliability engineers and storeroom teams, at a desk and against the ERP, so it is browser-based with no separate mobile app. Its outputs, the stocking parameters and the purchase triggers, reach the field through the ERP and the CMMS.