Factory Systems / OEE
OEE & Production Performance
Plan Availability, Performance and Quality measurements to identify downtime, speed loss and rejected production.
OEE
Details and scope
Plan Availability, Performance and Quality measurements to identify downtime, speed loss and rejected production.
- Applications
- Availability: operating time / planned production time · Performance: ideal cycle time × total count / operating time · Quality: good count / total count; OEE = A × P × Q
- Project inputs
- Shift calendars and planned-stop exclusions · Ideal cycle time per product and total / rejected counts · Downtime reasons, product changes and data-gap rules
- Delivery scope
- OEE requires production and quality data, not only a run signal. Agree denominators and zero-data handling; live analytics availability is confirmed per project, while the demo is simulated.
- Project format
- Devices with setup or a scoped integration project
- Acceptance
- Validate against actual equipment and customer reference data
Operational uses
Plan Availability, Performance and Quality measurements to identify downtime, speed loss and rejected production.
- Availability: operating time / planned production time
- Performance: ideal cycle time × total count / operating time
- Quality: good count / total count; OEE = A × P × Q
Before system design
Select devices and integration around the actual site.
- Shift calendars and planned-stop exclusions
- Ideal cycle time per product and total / rejected counts
- Downtime reasons, product changes and data-gap rules
Scope and acceptance
OEE requires production and quality data, not only a run signal. Agree denominators and zero-data handling; live analytics availability is confirmed per project, while the demo is simulated.
- Validate readings and events against actual devices
- Specify devices, software licences, integration and training in the quotation
DETAILS & PLANNING
Plan your OEE project
From site inputs to daily use
OEE requires production and quality data, not only a run signal. Agree denominators and zero-data handling; live analytics availability is confirmed per project, while the demo is simulated.
- Shift calendars and planned-stop exclusions
- Ideal cycle time per product and total / rejected counts
- Downtime reasons, product changes and data-gap rules
Validate before rollout
Compare actual device data with displayed values and source events. Test disconnection, recovery, user permissions and handover documentation against jointly agreed operational scenarios.
- Correct readings and events
- Defined handling of missing data
- Operator acceptance of the workflow
Systems related to this page
Review each system’s scope before opening it or using the example to plan your project.
Simulated data · No physical PLC commands
Factory Operations
Explore machine states, energy, simulated readings and alarms with a 3D scene and example event history.
Demonstration with simulated data
Demo Center
Explore energy, machine monitoring and OEE examples with a 3D factory to understand data and workflows before planning a project.
Questions about this topic
Is this included in every cloud package?
Devices, licences, development and integration are assessed separately from cloud subscriptions. Confirm scope in the quotation.
Can we start with a pilot?
Start with selected read zones or a production line, and validate against actual equipment before adding devices and sites.
Choose hardware and software that work together
Start with your equipment and data points, then define the right site scope.