Free self-assessment

How much working capital is your MRO inventory holding idle?

Eighteen questions across six dimensions of capital efficiency. Your score on screen in about four minutes, plus the specific places capital is sitting still instead of working.

Scored against the same criticality, demand and network-pooling logic the nine MRO360 agents apply against live ERP data.

  • About 4 minutes
  • Score shown free, no email
  • Full diagnosis available after

Six places MRO capital goes to sit down.

Three questions each. None of them ask how much you spend. They ask whether the money you have already spent is doing anything.

01

Stock visibility

Whether a planner can find a part that exists. Parts that cannot be found get bought again, so the same capital is committed twice and counted once.

The leak: duplicate purchasing against stock you already own, at another site or under another description.

MRO360: Search AI
02

Risk-based stocking

Whether stocking levels follow criticality or follow habit. Most operations hold too much of the cheap and predictable, and too little of the part that stops a line.

The leak: capital allocated evenly across a catalogue where risk is distributed very unevenly.

MRO360: Equipment Criticality, Spare Parts Criticality
03

Demand accuracy

Whether forecasts see the maintenance calendar or only the past. An inaccurate forecast is paid for twice, once in buffer stock and again in expediting when the buffer was in the wrong place.

The leak: safety stock sized against uncertainty that better information would remove.

MRO360: Multi-Variant AI Forecasting, Reorder Point
04

Dead and obsolete stock

Whether non-moving and discontinued stock is identified early with a disposition path, or discovered at audit when the only remaining option is a write-off.

The leak: carrying cost on inventory with no future consumption, plus the write-down when it is finally acknowledged.

MRO360: Stock Velocity, Obso Check AI, Spare Seek AI
05

Emergency spend

Whether shortages are anticipated or discovered. Every emergency order pays a premium for information you already had somewhere in your systems.

The leak: premium pricing and expedited freight on orders that a few days of warning would have made routine.

MRO360: Work Order Planning, Vendor Intelligence
06

Network pooling

Whether the plant network operates as one balance sheet or several. Plant A raising an emergency order for a part sitting unused at Plant B is the purest form of this leak.

The leak: the same part stocked independently at every site, so total holding scales with plant count rather than with risk.

MRO360: Interplant Transfer Intelligence

Each dimension scores out of 9. The index is the total, normalised to 100.

Start the assessment

Score your capital efficiency.

Answer for how the operation runs on an ordinary Tuesday, not how the process document describes it.

Step 1 of 7 0 of 18 answered

What your score means.

Four tiers. The distance between them is not how much you spend on inventory. It is whether the decision to hold it gets revisited.

0 to 25

Leaking

Capital decisions follow the consequence.

  • Holding levels reflect caution, not measured risk
  • Dead stock surfaces at audit
  • Emergency orders are routine, not exceptional
  • Each site buys as though it were the only site

To move up: make existing stock findable and score parts at part level. Those two together usually account for the largest share of the first-tier gain.

26 to 50

Contained

Controls exist, but run on periodic effort.

  • Frameworks documented, refreshed occasionally
  • Forecasts built on history, not the maintenance calendar
  • Reorder points reviewed annually at best
  • Dead stock reported, but nobody owns disposition

To move up: replace the refresh cycle with continuous recalculation. The work is not more analysis, it is removing the dependency on someone doing the analysis again.

51 to 75

Efficient

Leakage is visible before it becomes a write-off.

  • Parts availability confirmed before work order release
  • Supplier reliability visible at the purchasing decision
  • Obsolete stock flagged with substitutes identified
  • Cross-site stock visible to planners

To move up: close the continuity gaps. Capability here often depends on specific individuals, and the score falls when they change roles.

76 to 100

Compounding

Decisions recalculate without being asked to.

  • Reorder points and forecasts update continuously
  • Planner queues filtered to items genuinely at risk
  • Transfer considered before external purchase, every time
  • Overrides captured, so accuracy improves rather than decays

The remaining constraint: breadth. Capability at one plant is not capability across a network, and the two rarely score the same.

One caution on self-scoring. Most people score their own operation about one tier higher than their planners would. If your result looks flattering, hand the same eighteen questions to whoever actually raises the purchase requisitions and compare.

What actually closes these gaps.

Every dimension in this index describes an information failure with a price attached. MRO360 runs nine AI-native agents as a layer above your existing ERP, CMMS and EAM. Nothing gets replaced, and every write-back needs human approval.

Your gap
What runs today

Stock visibility

Parts you cannot find get bought again.

البحث بالذكاء الاصطناعي takes a plain description, the way you would ask a colleague, and returns ranked matches, cross-references and substitutes without a material code. Multi-site stock, bin locations and surplus elsewhere in the network appear in the same result.

Risk-based stocking

Capital spread evenly across uneven risk.

درجة أهمية المعدات و Spare Parts Criticality score assets and parts separately, so a part is not assumed critical simply because the machine above it is. The same part can score differently at different sites, because local redundancy and lead time differ. Engineer overrides are captured, so accuracy improves rather than decays.

Demand accuracy

Buffer stock absorbing avoidable uncertainty.

التنبؤ باستخدام الذكاء الاصطناعي متعدد المتغيرات reads the maintenance calendar alongside consumption history, and forecasts planned, corrective and shutdown demand separately instead of averaging them together. نقطة إعادة الطلب then recalculates min, max and safety stock against actual supplier lead-time variability and each part's criticality tier, rather than holding a level set once at configuration.

Dead and obsolete stock

Capital with no future consumption.

سرعة حركة الأسهم classifies every part as fast, slow or non-moving per plant, continuously. Obso Check AI flags manufacturer discontinuation, and Spare Seek AI returns qualified substitutes with vendor names and landed cost. The output is a disposition path, not a flag someone has to research.

Emergency spend

Premium pricing for information you already held.

تخطيط أوامر العمل checks on-hand stock and incoming purchase orders against planned demand before release, and surfaces only the orders genuinely at risk. معلومات عن الموردين scores supplier reliability from actual goods receipt history, so delivery risk is visible before the order is committed rather than after it slips.

Network pooling

Holding that scales with plant count.

نظام نقل المعلومات بين النباتات matches one site's need against another's surplus before an external purchase order is raised, ranking options by transfer distance, logistics cost, criticality urgency and lead time. The decision stays with your team. The network behaves as one pool of capital rather than several.

The honest limit

Software cannot decide what your critical assets are, and it cannot make a stocking policy your reliability team disagrees with stick. What it can do is remove the dependency on someone finding time to redo the analysis. If your score is low because nobody owns the decision, that is not a technology gap, and a POC will tell you so.

How MRO360 works

قبل أن تضغط على زر «إرسال».

What MRO, reliability and supply chain leads usually ask before a first conversation.

Is the score free, or does it need my email?
Your score and tier appear immediately, with no email required. The detailed diagnosis, all six dimension scores, your weakest areas explained, and the order to fix them in, is behind a short form. That part is also free, with no paywall and no partial version. It is sent by a member of the MRO team rather than a no-reply address.
How is the score actually calculated?
Eighteen questions, three per dimension, each scored 0 to 3 against a defined maturity progression. Each dimension totals 9, the six dimensions total 54, and that is normalised to 100. There is no weighting and no hidden adjustment, so a low score in one dimension cannot be masked by a strong one elsewhere. It is a self-assessment, not a benchmark against other companies, and it is only as accurate as your answers.
Does this tell me how much capital I could release?
It tells you where the capital is sitting and in what order to address it. It does not give you a figure, because a credible number requires your actual inventory master, consumption history and lead times, not six answers on a web page. Any vendor giving you a dollar figure from a questionnaire is estimating, and you should ask them what they estimated from. A POC produces the number from your own data.
What does an MRO360 POC actually look like?
A typical POC runs 2 to 4 weeks. You send a sample of your spare parts master, a subset of historical work orders, and optionally a few asset BOMs. We run criticality analysis, dead-stock detection and forecast accuracy for one plant, then walk you through the output, the logic behind it, and the gaps we found in your data. No deployment, no IT change.
Which EAM and ERP systems does MRO360 work with?
SAP S/4HANA, SAP ECC (MM-IM, MM-CBP, PM), Oracle EBS, IBM Maximo, Infor EAM, Hexagon APM and other major platforms. MRO360 runs as an AI-native layer above your existing stack, reading material and equipment records, goods movement, work orders, notifications, purchase orders and lead times. Nothing is replaced, and approved changes write back only after human sign-off.
How long is a full rollout across multiple plants?
Deployments typically run 8 to 14 weeks for the first plant, with subsequent plants at 4 to 6 weeks each. Criticality learning from the first site carries into the second, which is where the difference comes from.
What happens to our data during a POC?
A mutual NDA is executed before any data moves. POC data is used only to produce your POC output, is held separately from other customer environments, and is deleted on request at the end. If your security team needs to review this before you share anything, say so and we will start there instead.
بياناتك آمنة ولا تُستخدم إلا للأغراض المقصودة. نحن نولي أولوية لخصوصيتك ونحمي معلوماتك.