Mold maintenance software helps injection molders schedule preventive maintenance using the cycles a tool has actually completed. It connects each mold’s shot count with its service history, maintenance tasks, and production commitments. That connection helps planners answer a practical question: can this mold finish the next order before its approved service limit?
Picture a tool with 12,000 shots remaining before maintenance. Production assigns it an 18,000-shot order because the press has capacity. The schedule looks workable until the mold needs to come out during the run.
An ERP implementation should expose that conflict before the order reaches the machine. To do this reliably, the system needs agreed counting rules, separate service intervals, and a clear process for releasing a serviced mold back to production.
What mold maintenance software should track
Set up mold maintenance software around a permanent asset ID. Part numbers, press assignments, and storage locations can change. The mold’s identity and history must survive those changes.
Record the mold owner, current revision, active cavities, location, and compatible presses. Then add the lifetime cycle count, last verified reading, and maintenance requirements. Link each completed service to the work performed and the count recorded at completion.
Keep two types of count visible:
- Lifetime cycles show the tool’s cumulative recorded use.
- Cycles since service show use since a particular maintenance task was completed.
A routine clean should not erase the lifetime count. It should also leave the baseline for a larger inspection unchanged unless it fulfilled that inspection’s approved scope.
For example, a mold may have separate requirements for vent cleaning, moving-component inspection, and a major teardown. Each requirement needs its own completion record and next due threshold.
Define what a shot means before connecting a counter
One molding cycle can produce several parts. A four-cavity mold completing 1,000 cycles has completed 1,000 shots, even if it produces 4,000 parts. Using finished-piece quantities as the maintenance counter will distort the service schedule.
Reject shots still use the mold. So do trial shots during setup. Include those cycles in the applicable usage count rather than relying only on accepted production quantities.
Dry cycling needs an explicit rule. A counter actuated by mold movement may register opening and closing without material being injected. If the approved maintenance plan uses actuation cycles, retain those counts; if it distinguishes molding shots from dry cycles, store both measures clearly.
Progressive Components’ OnDemand manual explains that traditional mold counters record opening and closing. It also describes tool-specific maintenance intervals and separate checklists. This makes the counting definition an implementation decision that must match the device and the maintenance plan.
Put that definition in the mold record. Otherwise, maintenance and production may discuss the same number while measuring different things.
Keep shot counts accurate when molds move between presses
There are three practical ways to capture usage: a counter attached to the mold, machine or MES data, and controlled manual readings. When configuring mold maintenance software, choose a primary source for each mold. Document how other sources will verify it.
A connected counter can simplify collection, but automation alone does not establish accuracy. An incorrect mold assignment can send perfectly valid machine readings to the wrong tool.
Record the mounting period
When using press data, associate the mold with a defined mounting period. Capture the machine count at installation and removal, together with timestamps and the manufacturing order.
Suppose a press reads 820,000 cycles when Mold M-24 is installed and 826,500 when it is removed. The mold gains 6,500 cycles for that period. It does not inherit the press’s full history.
If the mold moves to another press, repeat the process there. Add verified usage from both periods to the same mold record.
Handle resets and replacements explicitly
A replacement counter may start at zero while the mold already has hundreds of thousands of cycles. Preserve the previous total and record an approved starting offset for the new device. Keep the replacement date and supporting readings in the audit history.
For machine imports, flag unexpected negative differences, counter resets, and readings outside the mounting period. Prevent a retried import from adding the same cycles twice. If a reading is missing, show that the count is unverified until someone reconciles it.
Do not add both the mold counter and press counter for the same run. Use one to accumulate usage and the other to check it.
Calculate the next maintenance threshold
Configure mold maintenance software to calculate the next threshold for each task. For a recurring task that restarts after qualifying completion, use these calculations:
Next due count = lifetime count at last qualifying service + approved service interval
Shots remaining = next due count − current lifetime count
The following example uses an illustrative interval of 50,000 shots. It is a planning example, not a recommended interval for every mold.
| Planning field | Count | Meaning |
| Last qualifying service | 450,000 | Baseline for this maintenance task |
| Approved interval | 50,000 | Allowed usage between qualifying services |
| Next due count | 500,000 | Baseline plus interval |
| Current lifetime count | 488,000 | Latest verified accumulated usage |
| Shots remaining | 12,000 | Due count minus current count |
| Planned next order | 18,000 | Expected cycles including setup allowance |
| Projected end count | 506,000 | Current count plus planned usage |
The order would exceed the maintenance threshold by 6,000 shots. The planner should schedule service before the order, arrange a permitted split, or use another qualified tool. The software should make the conflict visible before release.
Define the trigger precisely. A task becomes due when its count reaches the threshold, not only after it exceeds it. If the counter is already above the threshold, display how many cycles overdue it is.
Some maintenance plans use fixed cumulative milestones instead of intervals that restart after service. Keep that rule explicit. Servicing early should move the next threshold only when the approved plan allows it.
Turn shots remaining into a production decision
Set advance alerts in mold maintenance software to give the tool room time to act. Waiting until the due count arrives can leave technicians searching for parts while production waits.
Forecast the next order’s usage
Estimate steady-production shots from required accepted parts, active cavities, and expected yield:
Expected production shots = required good parts ÷ (active cavities × expected yield)
For 36,000 good parts, four active cavities, and 96% expected yield, the estimate is 9,375 production shots. Adding a separate allowance of 125 startup shots gives 9,500 planned shots. Keep startup outside the yield calculation in this example to avoid counting it twice.
Against the earlier 12,000-shot balance, that order leaves approximately 2,500 shots before maintenance. The following order therefore needs another check. Recalculate when a cavity is disabled, order quantities change, or actual usage differs from the estimate.
Reserve maintenance capacity
At a 24-second cycle time, 12,000 shots represent 80 hours of cycling. That does not mean the mold will reach maintenance in 80 calendar hours. Shift patterns, planned stops, and the production sequence affect the date.
Use the schedule to estimate when the threshold will be reached. Then reserve time for mold removal, service, reinstallation, and the required first-off checks. Include technician availability and spare-part readiness in the plan.
Also mark the mold unavailable during maintenance. A free press cannot run an order if its required tool is in the tool room.
For a wider view of these connections, see Apagen’s guide to ERP software for plastic injection molding.
Set intervals for the tool and its operating conditions
There is no single shot-count interval suitable for every injection mold. Start with the mold maker’s instructions, customer requirements, and your approved maintenance procedures. Review those intervals using recorded inspection findings and failure history.
During the implementation workshop, ask the tool room which conditions should change the plan. Examples to review include the resin and fillers used, moving mechanisms, deposits around vents, and changes to the tool or process. Have the responsible tooling specialist approve the resulting rules.
Use shot counts alongside calendar and condition triggers. A stored mold may need a preservation inspection despite completing no new shots. A leak, sticking component, or abnormal inspection finding may require attention before the next scheduled threshold.
The software should flag those events independently. A count below the service limit is not proof that a mold is fit to run.
Close maintenance with evidence
Creating a request and completing the work are different events. If production continues after a request opens, the service baseline must reflect the count at actual completion.
Require the technician to record the task scope, findings, parts replaced, and completion count. Add photos or measurements where the procedure calls for them. The responsible reviewer should confirm that the work qualifies to restart the relevant interval.
For example, clearing a blocked vent may complete a cleaning task. It should leave an overdue teardown open if the teardown was not performed. Likewise, replacing an insert should preserve the parent mold’s history and identify the new component where separate tracking is required.
Define a release step after service. Depending on the work, that may involve assembly checks, leak testing, or first-off quality approval. Production should see when the mold is ready to run, rather than assuming that a closed maintenance request proves readiness.
How Odoo fits into mold maintenance software
Odoo for manufacturing can provide the ERP foundation for this workflow. Its documented Maintenance functions include equipment records and preventive or corrective maintenance requests. Requests can also reference a manufacturing order, helping teams connect a tooling issue with the run in which it occurred.
However, do not assume that standard Odoo automatically collects mold shots or triggers requests from cycle thresholds. Validate the required capability against your installed version, modules, and configuration. Shot-count integration and mold-specific planning rules may require an extension or custom development.
The Odoo Maintenance documentation is a useful starting point for separating standard functions from the proposed implementation.
A Manufacturing ERP project should demonstrate the complete workflow: collect a verified count, evaluate the service rule, identify a scheduling conflict, complete maintenance, and release the mold. A screen showing a shot-count field proves only one part of that process.
Pilot the workflow before connecting every machine
Begin with a small group of molds that represent different operating conditions. Include a tool that changes presses and another with several maintenance tasks. This reveals counting and scheduling problems that a single stationary mold may hide.
Validate the workflow with these scenarios:
- Move a mold between presses and reconcile the accumulated count.
- Replace a counter while preserving the lifetime history.
- Import the same production event twice and verify that usage increases once.
- Complete a minor task while keeping a separate major service due.
- Plan an order that crosses the threshold and confirm that the conflict appears.
- Complete maintenance and verify that release approval controls tool availability.
For management reporting, track overdue tasks by maintenance type, usage beyond due thresholds, tool-related unplanned stops, and the age of the latest verified reading. An apparently healthy count is less useful if nobody has updated it for several shifts.
Frequently asked questions
How many shots should a mold run before preventive maintenance?
Use the interval approved for that mold and maintenance task. Tool construction, operating conditions, and service history affect the decision. Begin with the mold maker’s guidance, then review the interval using documented inspections rather than copying another factory’s threshold.
Should rejected parts and trial runs count toward mold maintenance?
Yes, their molding cycles still use the tool, so accepted-piece totals alone are insufficient. Capture setup, trial, and reject cycles in the applicable usage measure. Define separately how your counter and approved plan treat dry opening and closing cycles.
How do we calculate maintenance shots for a multi-cavity mold?
Count cycles rather than multiplying them by the number of cavities. A four-cavity mold running 1,000 cycles has completed 1,000 shots. For future orders, use active cavities and expected yield to estimate the cycles needed to produce the required good parts.
How can we keep the mold’s count when it changes machines?
Keep one permanent mold record and assign each press run to it. Use verified start and end readings for each mounting period, or collect usage from a suitable mold-mounted counter. Reconcile those sources without adding the same run twice.
Does cleaning a mold reset its preventive maintenance counter?
It resets only the interval for a task whose approved scope the cleaning fulfills. Lifetime usage remains intact. Other tasks retain their own service baselines, so a face wipe cannot silently clear a major inspection requirement.
Can Odoo automatically schedule maintenance based on mold shots?
Odoo provides equipment and maintenance-request functions, but automatic shot-based triggers need validation in your specific setup. Confirm the counter connection, threshold logic, and mold availability rules. Ask the implementation team to demonstrate them using an actual press transfer and service completion.
What should we do if the next order crosses a maintenance threshold?
Resolve the conflict before releasing the order. Options may include servicing first, splitting the run at an approved point, or assigning another qualified mold. Any permitted deferral needs a recorded approval and revised limit under your maintenance procedure.
Book a demo of shot-based mold maintenance
Bring one mold’s service history, current counter reading, and next production order to an Apagen ERP demo. Ask the team to show how the proposed mold maintenance software workflow would calculate shots remaining, flag a scheduling conflict, and record completed service.
You can also email sales@apagen.com to discuss your requirements. Start with the tooling decisions your factory needs to make, then see how the ERP can support them.