Skip to content
Service & spare partsPlastics & PackagingTool & Mould Making

Plan mould maintenance by shot count

Every mould gets a maintenance plan and a life record with all faults and repairs.

Today

Moulds get maintained when they fail, and their history lives in notebooks. Unplanned mould repairs stop machines and put delivery dates at risk. For customer-owned moulds there is also no record to show the owner.

An example

At Norvelta the 8-cavity mould SW-1834 in 1.2343 reaches its maintenance interval in about 8,000 shots. The agent places the maintenance in Thursday's planned changeover and lists the two inserts that have already been replaced twice.
Fictional company, typical workflow.

Your data, wherever it lives

Today shot counts sit in the MES, moulds and their ownership in the ERP, repair orders in the CMMS and the history of each mould in spreadsheets and the tool shop's notebooks. demi reads it all, scanned notebooks included, understands it and links it into one record per mould, with your rights. The AI calculates every due date exactly from the booked shots and places maintenance in the next changeover before the wear limit, instead of someone matching spreadsheets and notebooks, and the tool shop confirms the date.

Where the data lives today

  • MES
  • ERP
  • Tickets
  • Office files
  • Scans & paper
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 MES, ERP, CMMS and spreadsheets. demi replaces nothing and joins moulds, shot counts from production bookings, repair orders, spare inserts and mould ownership into one record per mould. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Tool shop and production see the plan, and the record of a customer-owned mould can be shared with its owner, without internal costs. The tool shop confirms the maintenance, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent computes due dates from booked shot counts and fixed intervals, not from estimates, and schedules maintenance before the wear limit, ideally in a planned changeover. It summarises the mould's history and plans spare inserts, each fact citing its booking or order.

How it runs

  1. 1

    Clarify the data sources: MES, ERP and maintenance system

  2. 2

    Count shots per mould from the production bookings

  3. 3

    Compute due dates and place them in the next changeover

  4. 4

    Check spare inserts and order what is missing

  5. 5

    The tool shop confirms; the record is updated

What changes

  • Fewer unplanned mould failures

  • A complete life record for every mould

  • Maintenance in planned windows

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

+96 hfreed per year

Assumptions and calculation

demi plans the service from shot count, faults and repair history; you approve the date.

30 min → 18 min per case

How does it run today?

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

How we calculate

40 mould services × 30 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 96 h

Value per year, before demi costs

Freed per year+96 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€6,240

gained per year

96 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

Where do the shot counts come from?

From production bookings in the MES or ERP, per order and mould. Where machines report the counter directly, demi uses that value. If bookings are missing, demi shows the gap instead of filling it in.

Can we share the history with the mould owner?

Yes. The record of a customer-owned mould can be shared with its owner, with shot count, maintenance and repairs. Costs and internal notes stay hidden. Every share is recorded.

Does it plan spare inserts too?

Yes. From the repair history demi sees which inserts are replaced most often and checks before maintenance that spares are on hand. If one is missing, an order proposal goes to the tool shop.

What if production moves the changeover window?

Then demi recalculates and shows whether maintenance still falls before the wear limit. If it gets tight, the tool shop and production planning are notified.

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