Data and AI
AI pays back on accurate, contextualised operational data. Build that foundation with the AI strategy, and each delivers more because of the other.
Contextualised data →Everyone in a factory touches the same orders and machines. They just ask very different questions of them. Pick a role to see what that person is measured on, and which shopfloor applications make the biggest difference to their day.
Can we grow and protect our margins, without building another factory?
The CEO rarely sees the shopfloor directly, but almost every promise the business makes depends on it. Capacity, margin, customer service and reputation are all decided where the product is made.
AI pays back on accurate, contextualised operational data. Build that foundation with the AI strategy, and each delivers more because of the other.
Contextualised data →Standard OEE across sites shows where hidden capacity sits, which is usually the cheapest growth available.
What is MES/MOM? →Fast, precise traceability turns a potential company-wide recall into a contained, documented event.
Manufacturing traceability →Investors and customers increasingly ask for product-level carbon and energy data, which only the shopfloor can provide.
ESG and shopfloor data →Capacity questions answered with estimates and a capex request
A clear view of hidden capacity across the network, site by site
A recall scoped broadly, just to be safe
A recall scoped to the exact lots and customers affected
Talk about growth and risk, not software. Show what hidden capacity is worth in revenue, and what a contained recall saves compared with a broad one. Keep it to one page.
What does a unit really cost to make, and what will we get back for the money we invest?
The CFO cares about cost and confidence in the numbers. Much of manufacturing cost is decided on the shopfloor, but the finance team usually only sees it after the month closes.
Accurate, real-time inventory and WIP free up working capital and remove surprises at the stock count.
WMS vs MES inventory →Actual material and labour consumption per order replaces standards, so product costs reflect reality.
What is MES/MOM? →Real cycle times feeding the plan mean fewer expediting costs and less overtime.
APS vs ERP scheduling →A clean operational data foundation lets finance model the impact of changes before committing the money.
Contextualised data →Variances explained at month end, if at all
Cost variances visible by order as production happens
Business cases built on vendor promises
Business cases built on measured losses from your own lines
Bring numbers you can defend. Measure the losses first, put a value on one point of OEE, include your own people's time in the costs, and show a clear rollout plan for the whole programme.
Are all our plants performing to their potential, and can we run them the same way?
The COO runs the operating network. Their job is consistency at scale: the same standards and measures everywhere, with best practice from one site spreading to the rest.
One definition of OEE and downtime across every plant turns site comparisons into a source of improvement rather than argument.
What is MES/MOM? →Digital instructions and skills management let new starters perform like experienced ones much sooner.
Connected worker vs MES →Faster, data-driven rescheduling helps the network absorb disruption.
APS vs ERP scheduling →Comparable data across sites is what makes network-level analytics and AI possible.
Contextualised data →Best practice stuck in the best plant
A standard template rolled out across sites
Monthly performance packs, rebuilt by hand
Live, comparable performance for every plant
Frame it as a standard way of operating, not a set of site projects. Show the gap between the best and worst plants on the same measure, and what closing half of it would be worth.
How do we connect the shopfloor to the business securely, with an architecture we can support for years?
The CIO owns the architecture and the risk. The shopfloor is where IT meets OT, and where integration and security decisions have the longest consequences.
Contextualised data captured at the point of work is the foundation for every analytics and AI ambition the business has.
Contextualised data →A shopfloor platform at ISA-95 level 3 gives a clean boundary between ERP and the equipment.
What is MES/MOM? →Genealogy is a data model problem as much as a process one, and it needs designing once, properly.
Manufacturing traceability →Clear ownership of stock across systems stops two of them arguing about the same bins.
WMS vs MES inventory →ERP wired to PLCs through custom code
A layered architecture with a clear role for each system
Every site with its own integrations
A standard integration pattern reused at every site
Talk architecture and cost of ownership. Show where each capability will live, how integrations follow a standard, and how OT security is designed in from the start.
How do we move from pilots to value at scale, and show it?
Digital and transformation leaders are judged on outcomes, not technology. Their biggest risk is promising projects that never scale beyond one line.
AI and a consistent operational data foundation scale together. Each new site adds history the models can learn from.
Contextualised data →Frontline tools are where adoption is won or lost, and where trust in digital starts.
Connected worker vs MES →Production execution is usually the backbone that other use cases build on.
What is MES/MOM? →Quality use cases often show measurable value quickly, which builds momentum across the programme.
QMS and MES quality →A portfolio of disconnected pilots
A platform that each new use case builds on
Value claimed in slides
Value measured on the line, before and after
Show a roadmap from first site to network, with measures agreed up front. Emphasise the platform decision, because it decides how cheaply each next use case can scale.
Which plant needs my attention this week, and why?
Operations leaders sit between the board's targets and the plants' reality. They need comparable facts quickly, so they can focus support where it makes the biggest difference.
Consistent OEE and loss data across sites shows exactly where to focus support and capital.
What is MES/MOM? →Network-wide visibility of quality issues stops one site's problem becoming every site's problem.
QMS and MES quality →Live order status lets you rebalance work between plants when demand or supply shifts.
APS vs ERP scheduling →Comparable data makes it possible to spot patterns across the network rather than plant by plant.
Contextualised data →Weekly calls to find out what happened
Exceptions flagged as they happen, with the context attached
Investment decided on the loudest case
Investment decided on measured losses
Lead with the network view: the gap between sites on the same measure, and what a standard template would cost compared with every plant solving the same problem alone.
Are we going to hit the plan this week, and if not, what's stopping us?
The plant manager owns the numbers and the people. They need one version of the truth for the morning meeting, and the confidence that the plant runs the same way when they're not on the floor.
Real-time output and downtime, with reasons, means the morning meeting starts from facts rather than debate.
What is MES/MOM? →Digital instructions and skills enforcement make the plant less dependent on a few experienced people.
Connected worker vs MES →Complaints and audits answered in minutes, not days.
Manufacturing traceability →Production and maintenance working from the same downtime data ends the blame game.
Maintenance →The morning meeting starts with an argument about the numbers
The morning meeting starts with yesterday's top losses, agreed
A complaint takes three days to trace
A complaint traced before the customer call ends
Focus on the problems that hurt most at your site and put a value on them. That makes the case for your site, and strengthens the company-wide one.
Where are our biggest losses, and did the last improvement actually stick?
CI and lean leaders live on data about losses. Too often they spend more time collecting and cleaning that data than acting on it.
Automatic loss capture, including micro-stops, gives a continuous loss tree instead of a one-off study.
What is MES/MOM? →Digital standard work makes the standard easy to follow and easy to check.
Connected worker vs MES →First pass yield by step shows where hidden rework sits.
QMS and MES quality →Pattern finding across shifts and products points improvement teams at the right problems.
Contextualised data →Two weeks of manual study before every project
Loss data ready for every improvement project
Gains that drift back after the kaizen event
Gains sustained, with the data to prove it
Show how much CI time goes on collecting data, and how many improvements fade. Automated loss capture frees the team to improve rather than measure.
Which lines are behind right now, and what do I need to do about it?
Production managers run the shifts that make the plan real. They balance people and machines hour by hour, and need to know about problems while there's still time to fix them.
Live line status and downtime reasons let you act within the shift, not the day after.
What is MES/MOM? →A prioritised list of released orders that reflects reality shows what to run next and why it changed.
APS vs ERP scheduling →Skills checks and digital handover keep every shift starting from the same picture.
Connected worker vs MES →Line-side material visibility stops lines waiting for parts the system thought were there.
WMS vs MES inventory →Walking the floor to find out what's happening
Exceptions on screen, with reasons, as they happen
Handover on a scrap of paper
Handover built from what actually ran and stopped
Focus on the shift: how much output is lost to problems found too late, and to waiting for materials or people. Show how live data turns those into decisions made in time.
Are we making it right every time, and can we prove it?
Quality leaders protect the customer and the licence to operate. They need problems caught on the line, and evidence ready for any auditor at any time.
Checks triggered by what's actually running, with SPC at the line, catch drift before it becomes scrap.
QMS and MES quality →Complete genealogy turns recalls and complaints into precise, documented answers.
Manufacturing traceability →Digital instructions and sign-offs build the quality record as the work is done.
Connected worker vs MES →Contextualised data makes root cause analysis faster, because the process conditions are already linked to the result.
Contextualised data →Defects found at final inspection
Drift caught at the point of work
Days preparing for an audit
Audit evidence available on demand
Lead with the cost of poor quality and the time spent on audits and investigations. Show how quality built into the process reduces both.
Which assets are going to let us down next, and are we spending maintenance effort in the right place?
Maintenance leaders are judged on availability and cost. They need accurate data about how equipment is really running, not end-of-shift guesses.
Stops captured from the equipment, with reasons, give reliable MTBF and MTTR and a fair split of the causes.
Maintenance →Condition data combined with downtime history is the starting point for predictive maintenance.
Contextualised data →Maintenance windows planned around the production schedule, rather than fighting it.
APS vs ERP scheduling →Operators raising faults from their own screen, and carrying out autonomous maintenance, catch problems early.
Connected worker vs MES →MTBF calculated from paper logs
MTBF calculated from every recorded stop
PM by the calendar
PM triggered by actual run hours and cycles
Show the gap between recorded and actual downtime, and the share of reactive work. Usage-based maintenance and shared downtime data are quick, low-risk wins.
Can we deliver what the customer wants on time, with the capacity we actually have?
Planners turn demand into a schedule the factory can follow. Their plans are only as good as the data about real capacity and what actually happened yesterday.
Real cycle times and setup times feeding back make every new plan more realistic.
APS vs ERP scheduling →Accurate stock and WIP, updated as material is consumed, mean the plan starts from reality.
WMS vs MES inventory →Live order progress shows early when a job will finish late.
What is MES/MOM? →Patterns in actual performance help forecast capacity and lead times more accurately.
Contextualised data →Schedules rebuilt by hand after every disruption
Disruption visible immediately, with the facts to reschedule
Standard times that are years old
Standards updated from what the line actually does
Show how far planned times are from actuals, and how often the schedule is overridden. Better feedback is often worth more than a more sophisticated scheduler.
Is the right material at the right line, at the right time, without piles of stock everywhere?
Logistics and warehouse leaders keep material flowing. The handover between the warehouse and the line is where stock disappears and lines stop.
Material tracked to the line, with consumption recorded as it happens, keeps the system and the shelf in step.
WMS vs MES inventory →Replenishment triggered by the actual production schedule stops lines waiting.
APS vs ERP scheduling →Lot tracking from receipt to finished goods makes FIFO and shelf life enforceable.
Manufacturing traceability →Quality holds visible at every point where material can be moved or consumed.
QMS and MES quality →Lines stopping for material that's somewhere in the building
Material called to the line before it's needed
Stock counts that never match
Inventory accurate enough to trust without counting
Count the line stoppages caused by missing material, and the stock adjustments at every count. Show how tracking material to the line fixes both.
Is the process running the way it was designed, and when it isn't, why not?
Engineers design and improve the process. They need detailed data linked to products and recipes, and a quick way to get changes onto the shopfloor.
Process data linked to the order and the outcome is what analytics and AI need to find root causes.
Contextualised data →SPC and capability data from the line show where the process drifts.
QMS and MES quality →Digital work instructions mean an engineering change reaches every workstation at once.
Connected worker vs MES →As-built records show exactly what went into each unit, for investigations and ramp-up.
Manufacturing traceability →Correlating spreadsheets by timestamp
Process data already linked to the order and the lot
A revision change that takes days to reach the floor
A revision live at every station as soon as it's released
Show how long investigations and engineering changes take today. Linked data and digital instructions shorten both, which speeds up every new product introduction.
Are our people safe, and can we prove our environmental performance with real data?
EHS and sustainability leaders need procedures followed every time, and environmental data they can stand behind when customers and regulators ask.
Energy and waste measured by machine and product turn ESG reporting from estimates into facts.
ESG and shopfloor data →Digital safety checks and skills enforcement make sure the right people follow the right procedure.
Connected worker vs MES →Well-maintained equipment is safer and uses less energy.
Maintenance →Product-level data makes it possible to answer customer carbon questions.
Manufacturing traceability →Sustainability figures estimated once a year
Energy and waste measured by product, every day
Safety sign-offs on paper
Digital sign-offs, checked before work starts
Lead with customer and regulatory pressure for real data. Show how the same shopfloor data that drives efficiency also proves sustainability.
How do we connect every machine and system reliably and securely, in a way we can support for ten years?
Architects and OT managers make the connections work. They balance the shopfloor's need for availability with the business's need for data, and live with every integration decision for years.
Publishing contextualised data, rather than raw tags, makes every downstream consumer simpler.
Contextualised data →A shopfloor platform at level 3 gives the control layer and ERP a single, well-defined partner.
What is MES/MOM? →Machine connectivity serves maintenance and production from the same connection.
Maintenance →Genealogy depends on reliable, time-synchronised data from the equipment.
Manufacturing traceability →Every interface designed from scratch
Standard interface patterns, with OPC UA and MQTT at the machine layer
Security reviewed at the end of the project
Security designed into the architecture from the start
Talk standards and supportability: OPC UA and MQTT, with clear ISA-95 layering and security zones. Show which interface pattern each connection uses, and why.
How do we get new people productive quickly, and keep the experienced ones?
HR and training leaders face a shrinking, more mobile workforce. The shopfloor tools people use every day shape how quickly they learn and whether they stay.
Digital work instructions and skills tracking capture expert knowledge and guide new starters step by step.
Connected worker vs MES →AI assistants can answer an operator's question from the SOPs at the moment they need it.
Contextualised data →Guided work with built-in checks lets new people get it right first time.
QMS and MES quality →Modern, intuitive shopfloor screens make the job easier to learn and more satisfying.
What is MES/MOM? →Weeks of shadowing before working alone
Guided from the first shift, with checks built in
Training records in a spreadsheet
Skills checked automatically before work starts
Show the cost of turnover and slow onboarding. Connected worker tools turn tribal knowledge into instructions, and make the job more attractive to the people you're trying to hire.
What's going wrong on my shift right now, and who do I need?
Supervisors and team leaders keep the shift running. They juggle people and problems in real time, and are often the ones filling in the paperwork at the end.
Digital handover and skills visibility mean you start the shift knowing what's waiting and who can do what.
Connected worker vs MES →Live line status with downtime reasons shows where to go first.
What is MES/MOM? →Faults raised from the line go straight to maintenance, with the context they need.
Maintenance →A clear, prioritised list of released orders removes the guesswork about what to run next.
APS vs ERP scheduling →An hour of paperwork after every shift
The shift record built automatically as you go
Finding out about a stopped line on a walk round
Alerts as soon as a line stops, with the reason
Talk about time and hassle: the hours spent on paperwork and chasing information. Show a supervisor what their shift looks like on one screen.
What do I make next, and who helps me when something goes wrong?
Operators do the work that everything else depends on. The best shopfloor systems make their job easier, not just better recorded.
Clear, current instructions and simple checklists on one screen, in your language.
Connected worker vs MES →Counts and downtime captured from the machine, so you're not writing them down.
What is MES/MOM? →Checks prompted at the right moment, so nothing is missed and nothing is done twice.
QMS and MES quality →Raising a fault in a couple of taps, and seeing when help is coming.
Maintenance →Writing everything on paper, then typing it in again
Data captured once, mostly from the machine
Hunting for the right instruction
The right instruction shown for the job you're running
Involve operators early and ask what slows them down. If the system makes the job easier, adoption follows. If it only adds data entry, it won't stick.
What's broken, what happened before it broke, and do we have the part?
Technicians keep the equipment running. They need to know what happened before a failure and what was done last time, without searching through paper logs.
Fault reports with the machine state and recent history attached shorten diagnosis.
Maintenance →Digital procedures and checklists on a tablet at the machine, with sign-off built in.
Connected worker vs MES →An assistant that can find what was done the last few times this fault happened.
Contextualised data →Spare parts availability visible before the job starts.
WMS vs MES inventory →Arriving at a breakdown with no history
The fault and the last repair on your screen
Work orders written up from memory
Work recorded as you go, at the machine
Show how much repair time goes on diagnosis and finding parts. Better fault information is one of the fastest ways to cut MTTR.
Has this batch been checked properly, and is the evidence complete?
Quality technicians carry out the checks that protect the customer. They need to know what to check and when, and to record results once.
Checks triggered by events such as a material or tool change, with results captured straight from the gauge.
QMS and MES quality →Every result linked to the lot and the operator automatically.
Manufacturing traceability →Digital checklists and sign-offs complete the record as you go.
Connected worker vs MES →Holds that block material in every system, as soon as they're placed.
WMS vs MES inventory →Checks done by the clock, results typed in later
Checks triggered by events, results captured at the gauge
Batches waiting for missing paperwork
Records complete at the end of the batch
Show how much time goes on paperwork and chasing missing records. Event-driven checks and direct gauge capture improve both speed and accuracy.
A filler stops for 14 minutes at 02:10. The same event looks very different depending on who's looking. With connected operations, they're all working from the same facts.
Clears the jam, and selects the reason on the screen in two taps.
Sees the line stop live, and checks whether the shift can still hit its target.
Gets the fault with the alarm history attached, and sees it's the third this week.
Sees MTBF on the filler falling, and brings forward a planned repair.
Sees the order will finish 20 minutes late, and adjusts the next job.
Sees the stop in the morning's top losses, already agreed by everyone.
Sees the cost of the lost output in the month's numbers, with no reconciliation.
New articles on shopfloor AI, smart factory strategy and the MES/MOM lessons I wish someone had told me before my first implementation.