---
title: "Step-by-Step: Implement Real-Time OEE Dashboards for Small CNC Shops (Edge-to-Cloud Monitoring)"
description: Practical guide for small CNC shops to implement edge-to-cloud real-time OEE dashboards, from data capture to dashboards and pilot validation.
image: https://www.jitbase.com/hubfs/blog-images/implement-real-time-oee-dashboards-small-cnc-shops-hero.jpg
---

[+1 438 942-8501](tel:+1%20438%20942-8501)

[Log In](https://app.jitbase.com/)

- [English](https://www.jitbase.com/blog/implement-real-time-oee-dashboards-small-cnc-shops)
- [Français](https://www.jitbase.com/fr/blog/trs-cnc-temps-reel-tableau-bord-production)

[![JITbase black logo](https://www.jitbase.com/hs-fs/hubfs/Logos/jitbase-logo-black-horiz.webp?width=175&height=88&name=jitbase-logo-black-horiz.webp)](https://www.jitbase.com)

- Solutions

   Back

  ##### [Machine Monitoring](https://www.jitbase.com/machine-monitoring)

    - ##### [Machine Monitoring](https://www.jitbase.com/machine-monitoring)
  
  Back
  
    - [Live Dashboard](https://www.jitbase.com/machine-monitoring)
    - [Track OEE](https://www.jitbase.com/machine-monitoring#Track-OEE)
    - [Track Downtime Reasons](https://jitbase.com/machine-monitoring#Track-Downtime-Reasons)
    - [Reporting](https://jitbase.com/machine-monitoring#Reporting)
    - [Timelines](https://jitbase.com/machine-monitoring#Timelines)
  
  ##### [Production Monitoring](https://www.jitbase.com/production-monitoring)

    - ##### [Production Monitoring](https://www.jitbase.com/production-monitoring)
  
  Back
  
    - [Accurate Standard Times](https://jitbase.com/program-monitoring#Accurate-Standard-Times)
    - [Tool path & M00 tracking](https://jitbase.com/program-monitoring#Tool-path-M00-tracking)
    - [Performance tracking](https://jitbase.com/program-monitoring#Performance)
    - [CNC Program Improvement](https://jitbase.com/program-monitoring#CNC-Program-Improvement)
    - [Overtime Reasons](https://jitbase.com/program-monitoring#Overtime-Reasons)
    - [Lights-out Operations](https://jitbase.com/program-monitoring#Light-Out-Ope)
  
  ##### [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management)

    - ##### [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management)
  
  Back
  
    - [Operator Workload](https://jitbase.com/workforce-management#Operator-Workload)
    - [Workforce Scheduling](https://jitbase.com/workforce-management/#Operator-Daily-Allocation)
    - [Live Job Tracking](https://jitbase.com/workforce-management#Live-Job-Tracking)
    - [Production Planning and Scheduling](https://jitbase.com/workforce-management#Job-Operation-Planning)
    - [Live guidance for Operators](https://jitbase.com/workforce-management#Live-guidance-for-Operators)
  
  ##### [Edge Platform](https://www.jitbase.com/edge-platform)

    - ##### [Edge Platform](https://www.jitbase.com/edge-platform)
  
  Back
  
    - [Manage your own infrastructure](https://www.jitbase.com/edge-platform#Manage-your-own-infrastructure)
    - [Send Machine data to local server](https://www.jitbase.com/edge-platform#Machine-data-to-local-server)
    - [Drivers for standard protocols](https://www.jitbase.com/edge-platform#Drivers-for-standard-protocols)
    - [Integrations](https://www.jitbase.com/edge-platform#Integrations)
- Resources

   Back

  ##### [Our Downloadable Resources](https://www.jitbase.com/download)

    - ##### [Our Downloadable Resources](https://www.jitbase.com/download)
  
  Back
  
    - [Case Studies](https://jitbase.com/download#case-studies)
    - [White Papers](https://jitbase.com/download#white-papers)
    - [Brochures](https://jitbase.com/download#brochures)
    - [Product & Integration](https://jitbase.com/download#Product-Integration)
    - [In the Media](https://jitbase.com/download#in-the-media)
  
  ##### [Education](https://www.jitbase.com/education)

    - ##### [Education](https://www.jitbase.com/education)
  
  Back
  
    - [Workforce Management vs. Machine Monitoring](https://jitbase.com/education#Workforce-Management-vs-Machine-Monitoring)
    - [How to start?](https://jitbase.com/education#How-to-start)
    - [Infrastructure & Cyber-Security](https://jitbase.com/education#Infrastructure-Cyber-Security)
    - [Why the Cloud?](https://jitbase.com/education#Why-the-Cloud)
    - [FAQ](https://jitbase.com/education#Education-FAQ)
  
  ##### [Forms](https://www.jitbase.com/demo)

    - ##### [Forms](https://www.jitbase.com/demo)
  
  Back
  
    - [Return on Investissement](https://www.jitbase.com/return-on-investment)
    - [Machines we connect](https://www.jitbase.com/machines-we-connect)
    - [Demo Request](https://www.jitbase.com/demo)
  
  ##### [Blog](https://www.jitbase.com/blog)

    - ##### [Blog](https://www.jitbase.com/blog)
  
  Back
  
    - [Machine Monitoring](https://www.jitbase.com/blog/tag/machine-monitoring)
    - [Labor Management](https://www.jitbase.com/blog/tag/labor-management)
    - [Production Planning and Scheduling](https://www.jitbase.com/blog/tag/production-planning-and-scheduling)
    - [Quality and Inspection](https://www.jitbase.com/blog/tag/quality-and-inspection)
- [Plans](https://www.jitbase.com/plans)
- Why JITbase

   Back

    - ##### [Why JITbase](https://www.jitbase.com/why-jitbase)
    - ##### [About Us](https://www.jitbase.com/about-us)
    - ##### [Partners](https://www.jitbase.com/partners)

[Connect Machines for Free](https://sso.jitbase.com/realms/webapp/protocol/openid-connect/registrations?client_id=website-registration&response_type=code&scope=openid&redirect_uri=https://admin.jitbase.com)

[+1 438 942-8501](tel:+1%20438%20942-8501) [Log In](https://app.jitbase.com/)

- [English](https://www.jitbase.com/blog/implement-real-time-oee-dashboards-small-cnc-shops)
- [Français](https://www.jitbase.com/fr/blog/trs-cnc-temps-reel-tableau-bord-production)

  

[Book a demo](https://www.jitbase.com/demo) [Connect Machines for Free](https://sso.jitbase.com/realms/webapp/protocol/openid-connect/registrations?client_id=website-registration&response_type=code&scope=openid&redirect_uri=https://admin.jitbase.com)

![CNC spindle machining a metal plate with visible sparks, illustrating real-time machine monitoring, OEE tracking, and performance optimization powered by JITbase.](https://www.jitbase.com/hubfs/blog-images/implement-real-time-oee-dashboards-small-cnc-shops-hero.jpg)

 Blog [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring)

# Step-by-Step: Implement Real-Time OEE Dashboards for Small CNC Shops (Edge-to-Cloud Monitoring)

[*written by* Judicael Deguenon on February 20, 2026](https://www.jitbase.com/blog/author/judicael-deguenon)

Real-time OEE dashboard implementation gives small CNC and contract shops a way to see machine availability, performance, and quality in minutes rather than days. Fast detection of stops and performance loss reduces unplanned downtime and helps production planners squeeze more throughput without adding headcount. This guide explains a practical, low-risk edge-to-cloud approach: define a narrow pilot, connect machines safely, capture accurate cycle/standard times from NC programs, map events to OEE, and validate with a short pilot.

**TL;DR:**

- Start with a 2–6 machine pilot; aim for ±15% OEE accuracy versus manual logs and collect 30–50 cycles per operation for baselines.
- Capture cycle time from program events (program start/stop, tool-change) plus spindle-on; set alerts for unplanned stops \>2 minutes and data gaps \>10 minutes.
- Use edge devices (MTConnect/OPC UA where available, I/O taps or sensors for legacy controls), push events via MQTT/HTTPS, sync clocks with NTP, and validate in a 1–2 week pilot before scaling.

## Step 1: Define scope, KPIs, and prerequisites for your OEE rollout

Deciding scope up front shortens delivery time and improves acceptance. For small shops, pick 2–6 machines that run repeat jobs, have engaged operators, and represent common control types (Fanuc, Siemens, Heidenhain). A narrow pilot reduces variables: fewer part numbers, simpler downtime taxonomies, and faster feedback from operators.

### Decide which machines and lines to include

- **Repeatability:** Include machines that run repeat jobs at least daily.
- **Mix of controls:** Include at least one modern control (supports MTConnect or OPC UA) and one legacy machine for retrofitting experience.
- **Operator buy-in:** Prioritize cells where operators can test simple acknowledgements and record downtime codes.

### Select primary KPIs and calculation rules (Availability, Performance, Quality)

- **Availability:** (Planned production time − Unplanned downtime) / Planned production time. Treat planned maintenance and scheduled breaks as excluded time.
- **Performance:** (Ideal cycle time × Total parts produced) / Actual run time. Count every part the machine made, good or not: rejects are penalized in Quality, not here, otherwise they would be counted twice in OEE. Define ideal cycle time per program or operation.
- **Quality:** Good parts / Total parts started. Decide how rework and secondary operations are counted.

The Quality figure is only as reliable as the count behind it, so set up [automatic part counting](https://www.jitbase.com/blog/part-counting-cnc-shops) and validate it before you trust the percentage.

Align KPI definitions with a standard such as ISO 22400 (key performance indicators for manufacturing operations management) to keep calculations consistent across systems.

### Prerequisites checklist (network, operator consent, ERP/MES touchpoints)

- **Network:** 1–3 days for basic LAN/VLAN setup; ensure reliable Wi‑Fi or wired Ethernet near machines.
- **Edge hardware:** procurement 1–2 weeks; pick devices that support MTConnect, OPC UA, Modbus, and discrete I/O.
- **Data taxonomy:** Agree on downtime code list and program-to-part mapping before capture begins.
- **Personnel:** Controls technician for wiring, IT contact for firewall rules, and a production lead for acceptance testing.
- **ERP/MES:** Identify APIs or CSV export points for master data sync (part numbers, jobs, work orders).

Sample acceptance criteria for a pilot:

- Dashboard OEE within ±15% of manual logs over one week.
- Cycle-time capture validated against 30–50 cycles per operation.
- Cycle capture reliability above 95% (cycles detected with a valid program\_id and a plausible duration).
- Operator ability to acknowledge an unplanned stop on the dashboard with \<2 minutes median response.

### Narrow pilot vs. shop-wide rollout

| Criterion | Narrow pilot | Shop-wide rollout |
| --- | --- | --- |
| Risk | Low | High |
| Initial cost | Controlled | Significant |
| Speed of feedback | Fast | Slow |
| Adoption | Gradual | Complex |

A pilot gives faster feedback, lower cost and simpler change management, which makes it the right way to prove value. A shop-wide rollout can have a faster total impact, but it raises the risk if definitions are inconsistent from one machine to the next.

For a deeper primer on machine-level OEE tracking and calculation nuances, see our article on how to [track machine OEE](https://www.jitbase.com/blog/how-to-effectively-track-the-oee-of-your-machine-tools).

## Step 2: Install edge hardware and connect CNC machines safely

Connecting reliably and safely is often the longest phase. The right approach depends on machine age and control capabilities.

### Choose an edge device and wiring options (serial, Ethernet I/O, spindle/probe taps)

- **Modern controls:** Prefer software interfaces (MTConnect or OPC UA) over physical taps.
- **Mid-life machines:** Use controller Ethernet or Modbus TCP if available.
- **Legacy controls:** Use discrete I/O taps (cycle start/stop, spindle-on), spindle current sensors, or probe sensors to detect cutting.
- **Edge device features to look for:** protocol adapters (MTConnect/OPC UA/Modbus), secure transport (MQTT with TLS or HTTPS), local buffering, and configurable event mapping.

For edge deployment patterns, see the [edge platform overview](https://www.jitbase.com/edge-platform). For retrofits on older machines, our primer on [industrial I/O modules](https://www.jitbase.com/blog/io-modules-industrial-automation) explains the digital and analog signals involved.

### Common CNC interface methods (MTConnect, OPC UA, discrete I/O, G-code parsing)

- **MTConnect:** Time-stamped device streams for modern controls; low implementation effort if the control supports it. Reference: [MTConnect standard documentation](https://www.mtconnect.org/).
- **OPC UA:** Secure, structured data modeling for PLCs and many controllers; useful for richer telemetry. Read more in the [OPC Foundation overview of OPC UA](https://opcfoundation.org/about/opc-technologies/opc-ua/).
- **Discrete I/O:** Reliable for basic state detection (cycle on/off, spindle on). Requires safe wiring and electrical checks.
- **G-code parsing:** Parse the NC program to extract feed/speed and program IDs. Useful when the control lacks modern interfaces, but it requires careful parsing rules.

### Network and security basics for shop floors

- Segregate the OT network from corporate IT using VLANs or firewall rules; coordinate with IT early.
- Use secure transport: MQTT over TLS or HTTPS with client certificates.
- Keep clocks synchronized with NTP to avoid timestamp drift.
- Consult authoritative guidance on smart manufacturing and cybersecurity when planning connectivity, such as [NIST's manufacturing resources](https://www.nist.gov/manufacturing).

Safety and electrical checklist before wiring:

- Lockout/tagout and machine owner consent.
- Confirm control voltages and I/O pinouts with machine manuals or the OEM.
- Use opto-isolated inputs for I/O taps and install sensors within guarded areas only when safe.
- Have a controls technician sign off on wiring and test under supervision.

Tradeoffs: control-protocol vs. external sensors

- **Control-protocol capture:** Higher fidelity (program IDs, feed/speed), less noise, but depends on supported interfaces.
- **Sensor-based capture:** Faster to install on legacy machines, lower cost, but may miss program-level context and requires debouncing for noisy signals.

**Not sure your machines can be connected?** Check which CNC machines and controllers JITbase connects to.

[See the machines we connect](https://www.jitbase.com/machines-we-connect)

## Step 3: Capture accurate cycle and standard times from CNC programs

Accurate cycle time capture is the backbone of performance calculation. The aim is to combine theoretical times from NC/CAM with measured cutting time derived from machine events.

### How to extract theoretical cycle times from G-code and CAM outputs

- Parse G-code and CAM output for feedrates (F), spindle speeds (S), canned cycles, and move distances to compute theoretical cutting time per block.
- Record program\_id, operation step, and the calculated theoretical cycle. For example:
  
    - Theoretical cycle = sum of (move distance / programmed feed) for cutting moves
    - If the program has dwell or probing, include those as program steps with expected durations
- Use CAM-exported cycle times where available; CAM systems often provide operation-level estimates that map directly to program IDs.

Cutting unnecessary M00 stops out of programs is one of the most direct ways to lengthen unattended run time. One shop's [CNC programming case study](https://www.jitbase.com/how-smarter-cnc-programming-saved-700k) reports $700,000 in annual savings from doing exactly that.

### Measuring real cycle times: event markers, spindle-on logic, and tool change handling

- Primary event markers:
  
    - Program start/stop
    - Tool-change start/complete
    - Spindle-on/spindle-off
    - Cycle start (M00/M01 behavior) and part-present signals when available
- Use spindle-on duration as the proxy for cutting time in many operations. But note: spindle-on may include air cuts and probing.
- Handle tools and secondary motions:
  
    - Exclude tool-change time from pure cutting-time performance metrics or treat it separately for setup analysis.
    - Flag cycles with long probe times or retracts for review.

Practical sample:

- program\_id: PRG123
- Operation: OP2
- Theoretical cycle = 45 sec (from CAM)
- Measured average cutting time (spindle-on) = 52 sec (from edge device over 40 cycles)
- Performance ratio = 45 / 52 = 0.865 (86.5%)

Collect at least 30–50 stable cycles per operation to get a representative baseline. This sample size reduces noise from occasional rework or fixturing errors.

### Reconcile theoretical vs. measured times and set standard-time baselines

- Create baseline rules:
  
    - If the measured average is more than 15% above the theoretical time, review for air cuts, feed overrides, or tool wear.
    - If spindle-on minutes are substantially lower than expected, verify sensor placement and debouncing.
- Store both theoretical and measured standard times in master data (ERP/MES) so scheduling and costing use validated figures.
- Tag anomalies: cycles with probing, inspection stops, or operator interventions should be flagged and excluded from baseline calculation until reviewed.

Common discrepancy sources: air cuts after roughing, manual probing, operator-initiated inspections, or program repeats for quality checks. Implement simple flags in the edge device to mark suspicious cycles for later review.

## Step 4: Configure edge-to-cloud data flow and map OEE calculations

A clear data model and reliable transport make dashboards accurate and resilient.

### Design the data model: events, telemetry, and master data (machines, parts, programs)

Recommended schema for events and telemetry:

- timestamp (ISO 8601)
- machine\_id
- event\_type (start, stop, error, heartbeat)
- program\_id
- part\_id or work\_order\_id
- cycle\_time (seconds)
- spindle\_on (boolean or seconds)
- operator\_id
- downtime\_code
- raw\_telemetry (optional compressed payload)

Decide which master data is authoritative (ERP/MES) and sync it to the edge for quick validation. For federal programs and resources that help small manufacturers adopt digital tools, see [Manufacturing.gov](https://www.manufacturing.gov/).

### Map raw events to OEE states and downtime codes

Mapping rules examples:

- **Availability:** map any unplanned stop event where downtime\_code is not in the planned list to downtime.
- **Performance:** compare measured cycle\_time to standard\_time for the program\_id; treat partial cycles (e.g., operator pause) as micro-stops if \<30 seconds.
- **Quality:** mark a part as bad when the operator inputs a reject code or when downstream inspection flags a rework.

Implement debouncing and deduplication rules:

- Ignore cycles \<1 second or \>10× theoretical time as invalid.
- Collapse spurious start/stop sequences within a configurable window (e.g., 5 seconds) as micro-stops.

### Set up secure, reliable transport (MQTT/HTTPS) and retention rules

- Choose push (the edge pushes events) for low latency; push reduces cloud polling and provides near-real-time visibility.
- Use MQTT over TLS for efficient small-message transport or HTTPS for simpler firewall traversal.
- Buffer locally on the edge for network outages and implement backfill strategies to avoid gaps.
- Retention suggestions:
  
    - Raw events: 30–90 days depending on storage; longer if traceability is required.
    - Aggregates: 1–3 years for trending and audits.
- Expected event volumes:
  
    - Idle machine: heartbeat every 30–60 seconds → 1–2 events/min.
    - Active machine: start/stop, spindle events, alarms → 3–10 events/min.
    - For 10 machines on a single active shift (about 8 hours), with idle heartbeats the rest of the day, plan for roughly 25,000–65,000 events/day; adjust for extra shifts or high-frequency telemetry.

Important: synchronize clocks with NTP on edge devices and cloud ingestion nodes to ensure correct ordering and aggregation.

Compare push vs. pull:

- **Push:** lower latency, better for alerts, requires device-to-cloud outbound connectivity.
- **Pull:** central polling, easier control by IT, slower, and can overload controllers with frequent requests.

**See OEE update live, machine by machine.** Follow availability, performance, and quality as production runs.

[Discover machine monitoring](https://www.jitbase.com/machine-monitoring)

## Step 5: Build real-time OEE dashboards, alerts, and run a pilot validation

Dashboards must present actionable signals for operators and managers, not raw logs.

### Dashboard design: KPIs, timeseries, and shop/shift/operator filters

Suggested widgets:

- Live OEE % per machine (1-minute refresh)
- Rolling 60-minute availability and performance plots
- Performance heatmap by program\_id across shifts
- Downtime Pareto chart (by downtime\_code)
- Program-level cycle-time variance table (theoretical vs. measured)

Role-based views:

- **Operator screen:** current job, simple acknowledge buttons for downtimes, part-count input.
- **Shop floor supervisor:** machine statuses, alerts, short-term trend.
- **Plant manager:** shift comparisons, top downtime drivers, and long-term trends.

Real-world example: a precision machining shop found that repeated finishing passes in its CNC programs were adding unplanned overtime. Once the repeats were flagged and the programs corrected, its OEE rose by 15%. The [shop OEE case study](https://www.jitbase.com/how-one-shop-increased-oee-by-15-on-repeat-jobs) has the details.

### Alert rules and escalation for downtime, performance loss, and data gaps

Sample alert thresholds:

- Unplanned stop \> 2 minutes: operator alert (SMS/onscreen).
- Performance drop \> 20% vs. standard over 10 consecutive cycles: supervisor alert.
- Data gap \> 10 minutes for a machine: admin/IT alert.

Escalation pattern:

- Level 1: operator acknowledgement within 2 minutes.
- Level 2: supervisor ping after 10 minutes unresolved.
- Level 3: production lead review for recurring patterns.

### Pilot validation plan: acceptance tests, operator training, and success metrics

Pilot checklist:

- Compare dashboard OEE vs. manual logs for at least 5 shifts and confirm ±15% accuracy.
- Run controlled test parts (known theoretical time) for 30–50 cycles to validate cycle capture.
- Train operators on the acknowledgement workflow; measure median time-to-acknowledge (goal \<2 minutes).
- Track data quality metrics: percent of cycles with missing program\_id, number of duplicate cycles per shift.

Expected outcomes and benchmarks:

- Time-to-detect improvement target: \<2 minutes for unplanned stops.
- Early-case OEE uplift: shops often observe a 5–15% OEE gain after addressing the top 1–2 downtime causes. For a broader Lean view of downtime reduction, see the [Lean Enterprise Institute](https://www.lean.org/).

Integrate dashboards with scheduling:

- Use program-level cycle-time baselines to feed short-term scheduling algorithms and reduce tardiness; see the benefits in our piece on [real-time scheduling benefits](https://www.jitbase.com/blog/how-real-time-data-enhances-manufacturing-scheduling-and-efficiency).

Operator workflow training and adoption:

- Keep operator interactions simple: acknowledge a stop, select a downtime code from a short list, and input part counts.
- For guidance on operator interactions and shop-floor UX, refer to [operator workflows](https://www.jitbase.com/blog/the-connected-worker-how-operators-interact-with-jitbase-on-the-shop-floor).

## Step 6: Troubleshooting and common mistakes during implementation

Expect hurdles. The fastest fixes address event mapping, noise, and network issues.

### Common root causes (incorrect event mapping, clock drift, noisy I/O)

- Using spindle-on alone for cutting detection produces false positives (probing, air cuts).
- Clock drift between edge and cloud causes misaligned cycle aggregation.
- Noisy discrete I/O leads to duplicate start/stop events.
- Missing program\_id when auto-repeat or subprograms run.

### Quick fixes and validation checks

- Validate spindle-on minutes vs. expected cycle-based cutting minutes. If spindle minutes are much higher, look for air moves or poor debouncing.
- Check NTP synchronization on every edge device and ingestion node.
- Implement software debouncing (e.g., collapse start/stop pulses within 2–5 seconds).
- Replay raw event logs for a sample shift and compare with operator notebooks or part count.
- Add a program\_id fallback: if program\_id is not present, match to the most recent known program or an operator-provided work order.

### When to involve controls technicians or IT

- Call a controls tech when wiring changes are required, or signal integrity appears compromised (ground loop noise, incorrect voltage).
- Escalate to IT for firewall or VLAN configuration, certificate management, or a network-wide outage affecting multiple edge devices.

Comparison: sensor-based vs. control-protocol errors

- **Sensor-based:** often local noise and placement issues; fix by repositioning the sensor or adding shielding and debouncing.
- **Control-protocol:** mapping errors or missing tags; fix by updating the adapter configuration or consulting OEM manuals.

Logging guidance for troubleshooting:

- Capture raw binary I/O traces for 10–20 minutes around any anomalous event.
- Record program source snippets when a program\_id mismatch occurs.
- Store a short video or operator note for any unexplained long stops for root-cause analysis.

**Put a number on real-time OEE.** Estimate the return on investment for your shop.

[See the return on investment](https://www.jitbase.com/return-on-investment)

## The Bottom Line

A focused, short pilot of 2–6 machines using edge-to-cloud telemetry gives small CNC shops near-real-time OEE visibility with minimal disruption. Prioritize accurate cycle capture (program events + spindle-on), robust timestamping, and simple operator workflows; validate results against manual logs and iterate quickly before scaling.

## Frequently Asked Questions

### How accurate will OEE be compared to manual logs?

Expect dashboard OEE to land within about 15% of manual logs, in either direction, during an initial pilot if event mappings and standard-time baselines are set correctly. Accuracy improves as you collect 30–50 cycles per operation, standardize downtime codes, and remove flagged anomalous cycles from the baseline.

To improve accuracy, reconcile program-level theoretical times with measured spindle-on durations and run controlled test parts for verification.

### What if my machine has no network interface?

Retrofit options include discrete I/O taps (cycle start/stop, spindle-on), spindle current sensors, or probe sensors to detect cutting. These options are quicker and cheaper to deploy but provide less program context than MTConnect or OPC UA.

Always follow lockout/tagout and consult a controls technician for safe wiring. If program-level context is needed later, consider a staged upgrade or a protocol gateway for that machine.

### How do I handle mixed-production runs with multiple part numbers?

Map program\_id to part\_id or work\_order\_id in master data and sync that data from ERP/MES. For operations where program\_id isn't unique, require operator input at job start or use barcode/RFID part tagging to attach part-level data to cycles.

Aggregate performance by part\_id for costing and by program\_id for cycle-time tuning. Exclude mixed or transient runs from baselines until you have 30–50 cycles per part-operation.

### Why do my dashboards show gaps or duplicate cycles?

Gaps commonly come from network outages or missing backfill on edge buffers; duplicates usually stem from noisy I/O or improper debouncing of start/stop signals. First verify edge-device buffers and NTP time sync, then replay raw logs to identify repeated pulse patterns.

Quick mitigations include enabling local buffering on edge, increasing software debounce windows, and implementing deduplication rules in ingestion (collapse identical events within a short timeframe).

### What is the difference between OEE and TEEP?

Both express productive time as a share of a reference time, but the reference is not the same. OEE is calculated on planned production time, with breaks and scheduled maintenance excluded. TEEP (total effective equipment performance) is calculated on all calendar time, 24 hours a day, 7 days a week.

For a given machine, TEEP is therefore always lower than or equal to OEE. This guide uses OEE on planned time. In everyday language the two terms are sometimes used interchangeably, so fix the definition and the reference time before comparing figures across machines, shifts or sites.

### How long before I see a return on investment?

Timing depends mainly on data quality and on how fast the shop acts on the first downtime causes. A pilot of one to two weeks is first used to validate the data; gains appear afterwards, once the main stop causes are analyzed and fixed.

In shops that follow this approach, a 5–15% OEE gain is often seen after addressing the top one or two downtime causes. To estimate the return on investment for your shop, start from your own downtime hours and your machine hourly rate.

#### SHARE

[mailto:email@example.com?subject=Mail%20from%20our%20Website](mailto:email@example.com?subject=Mail%20from%20our%20Website)

## Related Articles

[![Production supervisor reviewing shop-floor KPIs on a visual dashboard next to a CNC machine, illustrating real-time manufacturing performance tracking and KPI monitoring with JITbase.](https://www.jitbase.com/hs-fs/hubfs/blog-images/kpi-dashboards-manufacturing-production-kpis-hero.jpg?width=352&name=kpi-dashboards-manufacturing-production-kpis-hero.jpg)](https://www.jitbase.com/blog/kpi-dashboards-manufacturing-production-kpis)

[Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring)

### [KPI Dashboards for Manufacturing: The Complete Guide (2026)](https://www.jitbase.com/blog/kpi-dashboards-manufacturing-production-kpis)

Read more

[![Manufacturing engineers reviewing production workflow diagrams to build an OEE dashboard in a CNC shop.](https://www.jitbase.com/hs-fs/hubfs/blog-images/build-oee-dashboard-6-practical-steps-hero-1.jpg?width=352&name=build-oee-dashboard-6-practical-steps-hero-1.jpg)](https://www.jitbase.com/blog/build-oee-dashboard-6-practical-steps)

[Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring)

### [Build an OEE Dashboard in 6 Practical Steps: From Data Sources to Actionable Alerts for Small Manufacturers](https://www.jitbase.com/blog/build-oee-dashboard-6-practical-steps)

Read more

[![](https://www.jitbase.com/hs-fs/hubfs/blog-images/best-saas-product-analytics-dashboard-tools-hero.jpg?width=352&name=best-saas-product-analytics-dashboard-tools-hero.jpg)](https://www.jitbase.com/blog/bi-dashboards-vs-mes-power-bi-grafana-tableau-cnc-shops)

[Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring)

### [BI Dashboards for CNC Shops: Power BI, Grafana, Tableau, or a Dedicated MES?](https://www.jitbase.com/blog/bi-dashboards-vs-mes-power-bi-grafana-tableau-cnc-shops)

Most CNC shops already have some kind of BI tool in reach — Power BI comes bundled with Microsoft...

 --\>

Read more

[![Two managers reviewing a color-coded KPI board on a glass panel in a CNC machine shop — OEE dashboard with JITbase](https://www.jitbase.com/hs-fs/hubfs/blog-images/design-oee-kpi-dashboard-prove-roi-90-days-hero.jpg?width=352&name=design-oee-kpi-dashboard-prove-roi-90-days-hero.jpg)](https://www.jitbase.com/blog/kpi-dashboard-management-prove-oee-roi-90-days)

[Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring)

### [KPI Dashboard for Management: Prove OEE ROI in 90 Days](https://www.jitbase.com/blog/kpi-dashboard-management-prove-oee-roi-90-days)

Read more

[![JITbase block logo](https://www.jitbase.com/hs-fs/hubfs/eca01011d7169e8c6395a8d7eebe802d.webp?width=317&height=158&name=eca01011d7169e8c6395a8d7eebe802d.webp)](https://www.jitbase.com)

![image-2](https://www.jitbase.com/hs-fs/hubfs/image-2.webp?width=156&height=78&name=image-2.webp)

Solutions

- [Machine Monitoring](https://www.jitbase.com/machine-monitoring)
- [Production Monitoring](https://www.jitbase.com/production-monitoring)
- [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management)
- [Edge Platform](https://www.jitbase.com/edge-platform)
- [Plans](https://www.jitbase.com/plans)

<https://linkedin.com/company/jitbase> <https://www.facebook.com/jitbase> <https://www.youtube.com/channel/UC0hNdL3yfYCXDpsvQ65Onzg>

Resources

- [Download](https://www.jitbase.com/download)
- [Education](https://www.jitbase.com/education)
- [Return on Investment](https://www.jitbase.com/return-on-investment)
- [CNC Machines we connect](https://www.jitbase.com/machines-we-connect)
- [Demo Request](https://www.jitbase.com/demo)

Why JITbase

- [Why JITbase](https://www.jitbase.com/why-jitbase)
- [About Us](https://www.jitbase.com/about-us)
- [Partners](https://www.jitbase.com/partners)
- [Contact Us](https://www.jitbase.com/contact)

[Book a demo](https://www.jitbase.com/demo) [Connect Machines for Free](https://sso.jitbase.com/realms/webapp-ngen/protocol/openid-connect/registrations?client_id=website-frontend&response_type=code&scope=openid%20email&redirect_uri=https://admin.jitbase.com/next-gen)

<https://linkedin.com/company/jitbase> <https://www.facebook.com/jitbase> <https://www.youtube.com/channel/UC0hNdL3yfYCXDpsvQ65Onzg>

© 2026 All rights reserved.

- [Privacy Policy](https://www.jitbase.com/privacy-policy)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Judicael Deguenon",
    "url" : "https://www.jitbase.com/blog/author/judicael-deguenon"
  },
  "dateModified" : "2026-10-15T14:56:16.209Z",
  "datePublished" : "2026-02-20T18:23:13.000Z",
  "headline" : "Step-by-Step: Implement Real-Time OEE Dashboards for Small CNC Shops (Edge-to-Cloud Monitoring)",
  "image" : [ "https://www.jitbase.com/hubfs/blog-images/implement-real-time-oee-dashboards-small-cnc-shops-hero.jpg" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.jitbase.com/blog/implement-real-time-oee-dashboards-small-cnc-shops",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.jitbase.com/hubfs/logo%20jitbase%201.svg"
    },
    "name" : "JITbase"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Expect dashboard OEE to land within about 15% of manual logs, in either direction, during an initial pilot if event mappings and standard-time baselines are set correctly. Accuracy improves as you collect 30–50 cycles per operation, standardize downtime codes, and remove flagged anomalous cycles from the baseline. To improve accuracy, reconcile program-level theoretical times with measured spindle-on durations and run controlled test parts for verification."
    },
    "name" : "How accurate will OEE be compared to manual logs?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Retrofit options include discrete I/O taps (cycle start/stop, spindle-on), spindle current sensors, or probe sensors to detect cutting. These options are quicker and cheaper to deploy but provide less program context than MTConnect or OPC UA. Always follow lockout/tagout and consult a controls technician for safe wiring. If program-level context is needed later, consider a staged upgrade or a protocol gateway for that machine."
    },
    "name" : "What if my machine has no network interface?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Map program_id to part_id or work_order_id in master data and sync that data from ERP/MES. For operations where program_id isn't unique, require operator input at job start or use barcode/RFID part tagging to attach part-level data to cycles. Aggregate performance by part_id for costing and by program_id for cycle-time tuning. Exclude mixed or transient runs from baselines until you have 30–50 cycles per part-operation."
    },
    "name" : "How do I handle mixed-production runs with multiple part numbers?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Gaps commonly come from network outages or missing backfill on edge buffers; duplicates usually stem from noisy I/O or improper debouncing of start/stop signals. First verify edge-device buffers and NTP time sync, then replay raw logs to identify repeated pulse patterns. Quick mitigations include enabling local buffering on edge, increasing software debounce windows, and implementing deduplication rules in ingestion (collapse identical events within a short timeframe)."
    },
    "name" : "Why do my dashboards show gaps or duplicate cycles?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Both express productive time as a share of a reference time, but the reference is not the same. OEE is calculated on planned production time, with breaks and scheduled maintenance excluded. TEEP (total effective equipment performance) is calculated on all calendar time, 24 hours a day, 7 days a week. For a given machine, TEEP is therefore always lower than or equal to OEE. This guide uses OEE on planned time. In everyday language the two terms are sometimes used interchangeably, so fix the definition and the reference time before comparing figures across machines, shifts or sites."
    },
    "name" : "What is the difference between OEE and TEEP?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Timing depends mainly on data quality and on how fast the shop acts on the first downtime causes. A pilot of one to two weeks is first used to validate the data; gains appear afterwards, once the main stop causes are analyzed and fixed. In shops that follow this approach, a 5–15% OEE gain is often seen after addressing the top one or two downtime causes. To estimate the return on investment for your shop, start from your own downtime hours and your machine hourly rate."
    },
    "name" : "How long before I see a return on investment?"
  } ]
}
```