Skip to content
Service & spare partsFor every industry

Maintenance plan from manual and history

demi builds maintenance plans per asset from manufacturer data, your own history and inspection logs, and plans the spare parts too.

Today

Maintenance intervals are copied from the manual once and never adjusted to real wear. Inspection logs are on paper or in free text. Spare parts are ordered only when the part is already missing.

An example

At Talwerk Antriebstechnik the agent builds plans for 24 machining centers and 6 gearbox test rigs from their manuals. Because the history of 3 test rigs shows repeated shaft seal leaks, it proposes a shorter inspection interval there and lists 9 seal kits for next quarter. The maintenance manager approves the change.
Fictional company, typical workflow.

Your data, wherever it lives

Manufacturer manuals sit today as PDFs in the DMS, work orders and failures as free text in the CMMS, intervals in spreadsheets, inspection logs often only as paper scans, condition data in the controllers and spare-part usage in the ERP. demi reads, understands and links them per asset, with your rights. The AI builds the plan in minutes instead of half a day, backs every adjusted interval with the manual section or past orders and plans the spare parts too, and the maintenance manager approves.

Where the data lives today

  • PDFs
  • DMS & archive
  • Tickets
  • Office files
  • Scans & paper
  • Machines & sensors
  • ERP
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the CMMS, ERP, DMS and spreadsheets. demi replaces nothing and joins manuals, maintenance orders, inspection logs, condition data and spare-part usage for each asset. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Maintenance planning owns the plan. An authorized person approves changes to safety-relevant intervals, and every change is recorded with its reason.

  3. 3 · ActIntelligence Layer

    The agent reads the manufacturer intervals from the manuals, checks them against recorded failures and proposes adjusted intervals, each citing the manual page or orders it rests on. It calculates the spare parts needed from the plan and recorded usage, not by estimate.

How it runs

  1. 1

    Connect manuals, orders and logs per asset

  2. 2

    Extract manufacturer intervals and keep the source

  3. 3

    Check them against recorded failures and findings

  4. 4

    Propose adjusted intervals and get them approved

  5. 5

    Derive the spare parts needed for the coming months

What changes

  • Plans based on real wear

  • Spare parts in stock when needed

  • Fewer unplanned failures

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+144 hfreed per year

Assumptions and calculation

demi builds the plan from maker data, history and inspection records; you check and approve it.

4 h → 2.8 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

10 maintenance plans × 4 h × 30% × 1.0 (manual) × 12 months = 144 h

Value per year, before demi costs

Freed per year+144 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$9,360

gained per year

144 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Can demi read maintenance intervals from manuals?

Yes, from PDFs and scans. The agent finds intervals, tasks and parts in the manual and shows the page they come from. Vague entries such as "as required" are flagged for clarification instead of being filled with an invented value.

How does demi use our failure history?

The agent assigns orders, findings and replaced parts to the asset and the component. If a part keeps failing before the manufacturer's interval, it proposes a shorter one; if it shows no findings over many intervals, a longer one. Every proposal links to the orders behind it.

Does demi plan the spare parts as well?

Yes. From the plan and past usage the agent works out which parts are needed when and compares that with ERP stock. demi writes back only after approval.

Who decides when a safety-relevant interval changes?

Always a person. The agent marks safety-relevant tasks and never changes them on its own. An authorized person in maintenance reviews the proposal and its reasoning and approves it; the log records who decided what and when.

Our inspection logs are free text. Does that still work?

Yes. demi reads free text and handwritten scans and pulls out finding, component and date. Anything the agent cannot assign with confidence goes to your team. Your records get cleaner step by step, and nobody has to retype old logs.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases