
Our guides to individual systems — ERP, MES, quality, maintenance, inventory — explain what each one does. The bridge guides explain how pairs of them work together. This guide steps back to the factory as a whole and looks at what connects all of them: the hand-offs, where something that happens in one area should cause something to happen in another.
In most SMEs, those hand-offs are made by people: a supervisor who calls maintenance, a storekeeper who tells purchase that stock is low, an inspector who walks to the supervisor's desk to stop a batch. Each hand-off is a delay and a chance to forget. Manufacturing automation, in the sense used here, means letting the software make those hand-offs.
Events and rules
The idea is simple. Every system records events: a job completed, a machine stopped, a reading out of limits, stock issued, a purchase order received. An automation rule says: when this event happens, under these conditions, do this. For example:
- When a machine stop is booked with reason "breakdown", then create a maintenance request for that machine and notify the technician on duty.
- When an in-process reading is out of limits, then put the job on hold and notify the quality inspector.
- When a work order is completed in the MES, then add the good quantity to finished-goods stock and make it available for dispatch.
- When stock of an item falls below its reorder level, then create a purchase request for the reorder quantity.
- When a preventive maintenance task is due next week, then check its spares and show the task to the planner.
None of these requires artificial intelligence. They require the event to be recorded reliably and the rule to be clear.
Mapping the hand-offs in your factory
Before automating anything, map the hand-offs that exist today. A practical way is to take each department and ask: what do you need to hear from other departments, and how do you hear it now?
| From | To | Hand-off | Typical way today |
|---|---|---|---|
| Sales | Planning | New order or change | Email, meeting |
| Planning | Stores, purchase | Material needed | List, phone |
| Stores | Production | Material ready | Supervisor checks |
| Production | Maintenance | Breakdown | Phone, shout |
| Production | Quality | First-off ready | Walk to inspector |
| Quality | Production | Hold / release | Verbal, tag on bin |
| Production | Stores, dispatch | Job complete | Slip, end-of-day count |
| Stores | Purchase | Low stock | Register, memory |
| Dispatch | Accounts, sales | Shipped | Copy of challan |
Most factories find a few dozen hand-offs. For each, note how often it happens, how long it takes and what goes wrong when it is missed.
Choosing what to automate
Automate first the hand-offs that score high on three tests:
- Frequency — happens many times a day.
- Cost of delay — a late hand-off stops a machine, delays a shipment or lets bad parts move.
- No judgement — the right action is the same every time.
Hand-offs that need judgement — whether to accept an urgent order, how to disposition a non-conforming lot — should stay with people. Automation can still help them by delivering the information and recording the decision, but it shouldn't make the decision.
Five hand-offs worth automating early
1. Completion to stock and dispatch
When the MES records a job as complete and passed, finished-goods stock updates and dispatch sees the goods. No slips, no end-of-day count. See our guide to one work order through ERP and MES.
2. Breakdown to maintenance
A stop booked as a breakdown creates a maintenance request automatically, with the machine's history attached. See fast breakdown reporting.
3. Failed check to hold
An out-of-limit reading puts the job on hold and calls quality, so suspect parts can't move. See in-process quality inside the MES.
4. Low stock to purchase request
Items below reorder level generate purchase requests for approval, with consumption history and open orders shown.
5. Production counts to tool life
Production bookings update die and mould counts, and maintenance becomes due automatically. See connecting MES and tool management.
Notifications: fewer and better
Many hand-offs end in a notification to a person. The temptation is to notify everyone about everything. The result is that people ignore notifications, including the important ones. Good notification design follows a few rules:
- Notify the person who can act, not everyone who might be interested.
- Include what they need to act — machine, job, reading, location — so they don't have to look it up.
- Escalate only when no one responds within a sensible time.
- Use the channel people already watch — the app on their phone, a shop-floor screen, email for less urgent items. Which external messaging channels can be used depends on your setup and is confirmed during scoping.
- Review weekly which notifications were acted on and which were ignored, and remove the ignored ones.
Scheduled automation
Not all automation is triggered by events. Some runs on a schedule: the daily owner's report at 7 am, the shift report at the end of each shift, weekly reviews of overdue actions, monthly reconciliations. These remove the routine work of compiling and sending. See our guide to the owner's automatic daily report.
One system or connected systems
When ERP, MES, quality, maintenance and inventory are modules of one system on one database, automation rules are straightforward: an event in one module is immediately visible to the others. When they are separate systems — for example an existing ERP plus a new MES — events must be passed between them through APIs, file exchanges or scheduled imports, where each system allows it. This works, but each connection needs care: what happens when one system is unavailable, how duplicates are avoided, how errors are reported. For SMEs building new, a single system usually makes automation far simpler. Where existing systems must stay, we confirm what each one supports during scoping.
Machine signals
Some events come from machines rather than people: run and stop status, cycle counts, alarms, temperatures. Where machines or add-on sensors can provide them, these signals can trigger the same rules — a machine stopped for more than ten minutes without a reason booked prompts the operator for a reason; a temperature out of range alerts the supervisor. Machine signals make some events automatic and more accurate, but they are not required to start. Most of the hand-offs above work with operator entries. Our guide to retrofitting old machines covers connecting older equipment.
Keeping people in control
Automation should make people's work easier, not take decisions away from them. A few principles help:
- Visible rules. Everyone should be able to see what rules exist and what they do.
- Overrides with reasons. An authorised person can override an automatic action — release a hold, cancel a purchase request — with a recorded reason.
- Audit trail. Every automatic action is recorded, so you can always see why something happened.
- Owner for each rule. Someone is responsible for each rule being correct and useful.
Approvals as automated hand-offs
Many hand-offs are approvals: a purchase request above a value limit, an excess material issue, a deviation to use material slightly out of specification, a rate change for a customer. On paper, approvals wait in someone's tray or in their phone's message history. As automated hand-offs, each request goes to the right approver with the information they need, reminders follow if it waits too long, and the decision is recorded with the time and the person. The rule that routes each approval — by value, department or type — is set once and applied consistently. Our guide to approval workflow automation covers this in detail.
Measuring what automation saves
Automation benefits are easy to claim and hard to see, because much of the saving is time and delay that simply stops happening. Measure a few things before and after each rule: how long the hand-off took (for example, from breakdown to technician notified), how often it was missed, how many phone calls or walks it involved, and the downstream effect (machine downtime, dispatch delays, suspect parts moved). A short before-and-after comparison for each rule builds confidence and helps decide which hand-offs to automate next.
When automation goes wrong
Automatic actions can fail in ways manual ones don't. A rule can fire on wrong data, a connection between systems can stop silently, or a change in the factory can make an old rule wrong. Build in three safeguards. First, a log of every automatic action, with the event that triggered it. Second, alerts when expected events stop arriving — for example, no production bookings from a section for two hours during a shift. Third, a periodic review of rules with their owners. These safeguards cost little and prevent the loss of trust that follows when automation quietly does the wrong thing.
A worked example
A plastics processor mapped its hand-offs and found over forty, most made by phone or by walking. It chose five to automate first: job completion to finished-goods stock, breakdown to maintenance request, failed dimensional check to hold, low stock of masterbatch and packing material to purchase request, and the owner's morning report.
The effect was mostly invisible in a good way: fewer calls, fewer walks across the floor, fewer surprises. Dispatch stopped waiting for end-of-day counts; maintenance requests reached technicians in seconds; suspect parts stopped at the machine. Over the following months the company added rules one at a time — tool life from shot counts, PM spares checks, overdue CAPA reminders — reviewing each one after a few weeks and removing notifications nobody acted on. The detailed story is in our use case for a plastics manufacturer.
Common mistakes
- Automating before the data is reliable — rules triggered by bad data cause wrong actions faster.
- Too many notifications — people stop reading them.
- Automating judgement — decisions that need a person become rigid and frustrating.
- No owner — rules nobody maintains slowly become wrong as the factory changes.
Documenting the rules
Keep a simple list of every automation rule: what triggers it, what it does, who owns it and when it was last reviewed. This list is invaluable when people change roles, when auditors ask how holds are applied, or when something unexpected happens.
Getting started
- Map the hand-offs between departments and how they happen today.
- Score them on frequency, cost of delay and need for judgement.
- Make sure the triggering events are recorded reliably.
- Automate three to five high-scoring hand-offs.
- Review after a month, adjust, and add the next few.
Automation done this way is unglamorous: a few dozen small rules, each removing a phone call, a walk or a forgotten message. Together they change how the factory feels — fewer surprises, faster responses and people spending their time on decisions rather than on passing information around.
Working with Corposol
Corposol builds custom manufacturing automation as part of connected manufacturing software for Indian SMEs — ERP, MES, quality, maintenance and inventory on one database, with the hand-offs between them automated step by step. All custom code is transferred to you on final payment.
Frequently asked questions
What does automation between factory systems mean?
An event recorded in one area — a machine stop, a failed check, a completed job, a low stock level — automatically triggers the next step in another: a maintenance request, a hold, a stock update, a purchase request — without someone noticing and passing the message on.
Do we need separate systems to benefit?
No. When ERP, MES, quality and maintenance are modules of one system, automation rules work on the same database. Where separate systems exist, they can be connected where each offers an API or import facility.
Which hand-offs should be automated first?
The ones that happen most often, cause the most delay when missed, and need no judgement — typically production completion to stock, breakdown to maintenance request, failed check to hold, and low stock to purchase request.
Can automation rules be changed by our own staff?
Simple rules — thresholds, recipients, escalation times — can be designed to be changed by authorised users. Structural changes to how systems connect are better made by the developers.
