How to integrate AI cameras with your MES and ERP in 2026
Every plant keeps two records of the same shift that almost never meet: your Manufacturing Execution System (MES) and Enterprise Resource Planning (ERP) system log that a line stopped and what the stop cost, while your cameras hold the only account of why it happened. Spot AI reads that footage with its AI Operations Assistant on the cameras you already have, and its open APIs, webhooks, and read-only MCP endpoint put the video record next to your MES and ERP data, so operations leaders can see every line and plant in one view. When those records stay apart, the gap is expensive: Deloitte's 2017 maintenance research put unplanned downtime costs for industrial manufacturers at an estimated $50 billion a year (Source: Deloitte). It is also top of mind: in Deloitte's 2025 survey of 600 executives at large manufacturers, 92 percent expected smart manufacturing to be their main driver of competitiveness over the following three years (Source: Deloitte). This guide shows a manufacturing IT or operations leader how to integrate AI cameras with your MES and ERP, and do it without interrupting production.
Key takeaways
- Your MES and ERP report that a line stopped and what it cost; AI cameras add the visual reason, moving root cause from hours to minutes.
- Integration is software-led and camera-agnostic: Spot AI works with the cameras you already own over ONVIF, so there is no rip-and-replace.
- An edge-first IVR keeps full-resolution video inside the facility and sends only metadata to the cloud, which answers the first IT bandwidth and OT security questions.
- Spot AI's open APIs and webhooks carry camera events into the MES, the ERP, and adjacent workflows, and its read-only MCP endpoint lets approved AI tools query the same video data.
- A phased rollout, timed to planned downtime windows, proves OEE and safety gains on one line before you scale.
Key terms
- Manufacturing Execution System (MES): software that manages live production on the shop floor, tracking work orders, cycle counts, and machine status against the schedule.
- Enterprise Resource Planning (ERP): the system of record for the wider business, covering orders, inventory, and financials.
- Intelligent Video Recorder (IVR): Spot AI's edge-first recorder that keeps full-resolution video in the facility and passes only metadata to the cloud.
- Model Context Protocol (MCP): an open endpoint that lets an approved AI assistant query Spot AI data with read-only permissions.
The visibility gap between MES, ERP, and the shop floor
Two terms matter here. The MES manages what happens on the production floor in the moment, while the ERP handles the business layer around it, from purchase orders to inventory to cost. Both are excellent at recording that something occurred and what it meant on paper. Neither can show the physical reason. When Line 3 halts at 2:10 a.m., the MES logs the stop and the ERP absorbs the lost output, yet the answer to why sits in video no one has time to watch.
This is the gap AI cameras close. Read by video AI, the feeds a plant already records become a running account of the floor that plugs straight into the systems you run. Platforms such as Plex, Rockwell FactoryTalk, SAP, Siemens Opcenter, and AVEVA stay the backbone for execution and planning; video AI works alongside them as the visual layer, not a replacement. For a fuller view of the operations use cases, see how video analytics for manufacturing maps to OEE.
The hidden cost of disconnected systems
Data silos create blind spots
When cameras do not speak to the MES or ERP, safety data lives apart from production metrics and quality checks stay disconnected from machine status. The financial drag is real. The same 2017 research found that poor maintenance strategies alone can reduce a plant's overall productive capacity by 5 to 20 percent (Source: Deloitte). Add the shifts where no supervisor is on the floor, and the blind spots widen exactly when they cost the most.
Manual reviews drain supervisors
Without integration, supervisors lose hours to compliance audits and still miss the events that matter. After an incident, working out what actually happened becomes a search through footage rather than a quick query. Manufacturing recorded 2.8 recordable injury and illness cases per 100 full-time workers in 2023, down from 3.2 a year earlier, and those cases still trigger investigations that pull people off the line (Source: U.S. Bureau of Labor Statistics). Tying detections to a case record turns that search into minutes; here is how teams resolve incidents faster with cases.
Alert fatigue erodes trust
Conventional monitoring tools are prone to high false-positive rates, and a flood of nuisance alarms trains teams to tune them out. That "cried wolf" effect buries the signal that deserves attention and makes people slower to adopt the next system. Context-aware detections, tuned to the process rather than raw motion, are what keep an integration credible on the floor. The case for an open video intelligence system rests on getting this signal-to-noise balance right.
Where AI cameras fit alongside your MES and ERP
The clearest way to scope an integration is to map what each system already knows against what video AI adds. The table below sets out that division of labor.
System | What it already tells you | What AI cameras add |
|---|---|---|
MES (Plex, Rockwell FactoryTalk, Siemens Opcenter) | That a line stopped, cycle counts, and work-order status | The visual reason: what the operator, material, or machine was doing at that moment |
ERP (SAP and similar) | Orders, inventory, and the cost of the loss | Video of the quality events and SOP deviations behind an order |
SCADA and sensors | The sensor reading and machine state | Context a sensor cannot capture: an obstruction, a changeover step, a congested aisle |
Read across any row and the pattern holds: your systems own the numbers, video AI owns the reason behind them. That is why the integration complements rather than competes with the platforms already approved in your plant.
A reference architecture to integrate AI cameras with your MES and ERP
Core components
A durable connection rests on a few building blocks. Key components are:
- Edge processing on the IVR: video is analyzed inside the facility, so latency stays low and the network is not flooded with raw footage.
- Standardized protocols: Spot AI's open APIs and detection webhooks deliver event data your integration layer can map into the formats the MES already accepts, including industrial protocols such as OPC-UA where the plant uses them.
- Open APIs, webhooks, and a read-only MCP endpoint: the APIs and webhooks carry detections toward the MES, the ERP, and adjacent systems, and the MCP endpoint lets an approved AI assistant query Spot AI data with read-only permissions.
- Camera-agnostic inputs: any ONVIF-compatible IP camera already on site can feed the system; confirm IVR capacity and infrastructure before expanding coverage.
How data moves in both directions
An effective program uses data in both directions. Detections flow into your systems through Spot AI's APIs and webhooks, and context from those systems tells the team which runs to review and which standard to check them against. The table below shows the exchange.
Data flow direction | Information type | Business impact |
|---|---|---|
Camera to MES | SOP deviations and safety events | Timely alerts and compliance records |
Camera to ERP | Quality events and SOP deviations tied to the order | Order-level context for quality and cost reviews |
MES to team | Production schedule and changeover plan | Which runs and changeovers to review first |
ERP to team | Order specifications and quality standards | The standard each run is checked against |
When detections arrive through webhooks rather than manual re-keying, transcription errors drop and the time between an event and the action it should trigger shrinks. Your team can also build downstream workflows on those webhooks, from notifying the right people to opening a task in the YMS, PMS, or ERP.
Using MES data in continuous improvement work
Spot AI's AI Operations Assistant gives a continuous improvement (CI) lead the half of the story the MES can't tell. The MES shows which changeovers ran long, which shifts logged the most micro-stoppages, and which work orders fell behind rate. It can't show that two crews run the same changeover in a different order, or that material wasn't staged when the line went down. CI teams get the most from the pairing when every improvement cycle starts from an MES number and uses video to explain it:
- Pick the loss from the MES: rank lines by changeover minutes over standard or by stop time, and start where a recovered minute is worth the most.
- Find the reason on video: match the MES timestamps for the stop or changeover to the same window on video. Spot AI's AI Operations Assistant scores each changeover by phase and flags steps that were skipped, done wrong, or done out of order, so the team sees where the time went, not just the total. When the MES logs a quality deviation, Iris lets the team ask in plain language what the cameras saw at that moment.
- Compare shifts and crews: Spot AI's weekly reports summarize performance by line, shift, and crew, helping CI teams see where to investigate differences in how the process is run.
- Update the standard from the best run: when one crew keeps beating the standard, its method becomes the next version of the SOP, and Spot AI's operator scorecards, with video after each run, show every crew what changed.
- Confirm the gain in the MES: close the cycle in the same MES measure you started from, so operations and finance read the result in the plant's own terms.
Bring operators in early. Plants that worry the cameras will feel like Big Brother tend to do best with weekly or biweekly check-ins that tie positive incentives to hitting goals, and plants without documented standards often find the rollout is what gets the standard written down. For the wider program, see how continuous improvement runs on video evidence; for the ERP side, see how to connect camera data to SAP and Oracle.
A phased rollout that keeps production running
Start with one line and one target
Effective rollouts begin narrow. Pick one production line, one process, and one measurable target, such as tightening changeover on your highest-volume SKU. A contained pilot proves value fast and protects the momentum a broad, disruptive cutover tends to kill.
Frame the project with the 5 P's
A simple change-management frame keeps stakeholders aligned across shifts:
- Purpose: state why you are connecting cameras to the MES and ERP, and the outcome you expect.
- People: name the operators, IT and OT staff, and supervisors the change touches.
- Plan: phase the work with timelines and milestones that respect the production schedule.
- Process: document data flows, alert routes, and escalation paths before go-live.
- Proof: agree the metrics, from OEE to investigation time, that will show the result.
Time the work to planned downtime
Schedule the heavier integration steps during maintenance windows or seasonal slowdowns, and prepare infrastructure ahead of any cutover: run cabling, configure protocols, test the data exchange, and write a rollback plan. Aligning the work with existing OEE targets, rather than fighting them, is what lets a plant connect systems without losing output. This is the same discipline behind a strong manufacturing camera strategy.
Start where a hidden loss most affects a KPI you already report, usually changeover or unplanned stops, and record the baseline before the first camera goes live. A pilot scoped to one line and one number is far easier to defend to IT and finance than a plant-wide cutover.
Addressing IT and OT concerns
For the IT evaluator, the first question is what the integration does to the network. The answer starts with the edge-first IVR: Spot AI processes video locally and keeps full-resolution footage inside the facility, and only metadata travels to the cloud, which keeps wide-area bandwidth low. Because it is camera-agnostic and works with ONVIF cameras, it reuses the cameras already installed. Spot AI is NDAA-compliant and SOC 2 Type II, with role-based access, SSO, and video encrypted at rest and in transit; review camera traffic, remote access, and network segmentation with IT and OT before go-live. One platform serving safety, security, and operations also means one vendor approval and one architecture decision, rather than three separate video systems to govern.
Measuring integration ROI
Key performance indicators
Set the baseline before the first camera is pointed at a process, then track movement against it with a unit and a timeframe attached. The measures below map an integration to the numbers a plant already reports.
KPI category | What to measure | How to read a gain |
|---|---|---|
Efficiency | OEE and changeover time | Higher OEE and less shift-to-shift variance versus baseline |
Safety | Recordable cases and near-miss capture | Fewer recordable cases and earlier hazard detection versus baseline |
Quality | First-pass yield | Fewer escapes and less rework versus baseline |
Compliance | SOP adherence and audit findings | Higher adherence and cleaner audits versus baseline |
Financial | Cost per unit and investigation time | Lower cost and faster resolution versus baseline |
A realistic ROI timeline
Returns tend to arrive in stages rather than all at once. An illustrative project plan could use these review points:
- Months 1 to 3: install, connect, and establish the baseline on the pilot line.
- Months 4 to 6: measure the targeted metric against the baseline.
- Months 7 to 12: expand to more lines if the pilot meets its agreed success criteria.
- Year 2 and beyond: the program shifts to steady optimization and cross-site benchmarking.
Let customer outcomes, rather than vendor promises, carry the numbers. A $12 billion manufacturer reported a 15 percent reduction in changeover time within its first three weeks with Spot AI's AI Operations Assistant, a customer-reported result rather than a guarantee. Two other customers are still mid-project: a $48 billion pharmaceutical company is working to reduce roughly $10,000-a-minute downtime on specialized syringe machines, and a $3 billion furniture manufacturer is working to close a 16 percent average gap in loading efficiency. Each ties back to the same idea: small, repeated losses become recoverable once the reason is visible. More examples sit in the customer stories library, and a value-stream-mapping lens shows where to look first.
Tie every detection to a baseline metric before you count it as a saving: a changeover flagged against last quarter's average is a defensible case, while the same clip with no reference point is only an anecdote. Report the result in the plant's own terms, whether OEE, cost per unit, or recordable cases, so finance and operations read the same number.
Ready to connect the record your systems keep with the reason your cameras hold? Spot AI runs its AI Operations Assistant on the cameras you already have, with most sites live in days and no rip-and-replace, and its open APIs, webhooks, and read-only MCP endpoint put that video data next to your MES and ERP records. See how Spot AI approaches changeover and SOP checks on the lines your MES already tracks.
Frequently asked questions
How do you integrate AI cameras with an MES?
Effective integration pairs technical architecture with operational planning. On the technical side, process video on the edge for low latency, use open APIs and detection webhooks to move events toward the MES, and map them into the protocols the MES already uses, such as OPC-UA. Operationally, start with one high-impact use case such as changeover monitoring, prepare infrastructure during planned downtime, and define how each AI event triggers an action. Treat the connection as an ongoing program rather than a one-time project.
Will connecting cameras to my MES and ERP disrupt production?
It does not have to. Schedule the heavier work during maintenance windows or seasonal slowdowns, and complete cabling, network, and protocol testing before any system goes offline. A pilot on a single line proves value without touching the rest of the plant, and a rollback plan protects you if something needs reverting. Training key staff across shifts before go-live keeps the change smooth.
How does video AI handle IT bandwidth and OT security concerns?
Spot AI uses an edge-first Intelligent Video Recorder, so full-resolution video stays in the facility and only metadata travels to the cloud. That keeps wide-area bandwidth low; camera traffic and network segmentation inside the plant are still worth reviewing with IT and OT. The platform is NDAA-compliant and SOC 2 Type II and works with ONVIF IP cameras, which addresses the security and integration criteria IT and OT teams review first.
What is the ROI of integrating AI cameras with manufacturing systems?
Manufacturers typically look for gains across efficiency, safety, and quality. Common outcomes include higher OEE from standardized changeovers, fewer recordable safety cases, and faster incident investigations that drop from hours to minutes. Set a baseline first and agree when the pilot will be measured. Results are customer-reported and vary by site, so tie every claim to a unit, a timeframe, and a baseline.
What is AI-powered incident detection in manufacturing?
AI-powered incident detection uses video AI to identify defined operational and safety events from camera feeds as they happen. Instead of reviewing footage after the fact, teams receive alerts for the events they choose, such as a forklift entering a no-go zone or a missed step in a changeover. This turns a camera system from a passive recording tool into an insight-driven coworker that helps teams address risks and process drift before they cost downtime or an injury.
About the author
Joshua Foster is an IT Systems Engineer at Spot AI, where he focuses on designing and securing scalable enterprise networks, managing cloud-integrated infrastructure, and automating system workflows to enhance operational efficiency. He is passionate about cross-functional collaboration and takes pride in delivering robust technical solutions that empower both the Spot AI team and its customers.




