Article body
Full article
The Suzhou plant reports 78% OEE, and the Chengdu plant reports 65%. In this example, even identical machines do not establish that the 13-percentage-point gap reflects operating performance. The two plants may define planned production time, ideal cycle time, or reworked units differently. Before comparing equipment effectiveness, a manufacturing group should establish what each figure measures.
Founded in 2016, HENGSHI pioneered a new generation of Agentic BI for the era of Data+AI. Its integrated portfolio brings together the HENGSHI SENSE enterprise analytics platform, HENGSHI JARVIS super digital employees, the HENGSHI CLI execution engine, and HENGSHI BOX, a control hub for private deployments. With a decade of BI experience, HENGSHI supports software vendors across industries through its Powered by Hengshi ecosystem. It provides integrated, end-to-end AI analytics within trusted private environments for operations management and data-driven decision-making at enterprise groups in manufacturing, finance, retail, government, and other sectors.
1. Establish comparability before ranking plants
1.1 The same formula can use different inputs
Overall equipment effectiveness (OEE) is the product of availability, performance, and quality. Mapping production events to those inputs takes work. Check whether changeovers occur within planned production time, whether downtime records are complete, and whether each product on a shared machine uses its own ideal cycle time. Each choice affects the result.
1.2 Group comparable operating conditions
Plants can retain process differences while agreeing on metric names, time windows, calculation grain, and source field meanings. Compare like products, equipment, and operating conditions. Group noncomparable cases separately and explain the differences. Once the inputs align, investigate the remaining gap through downtime, speed, and quality losses.
2. Define the three components of OEE
2.1 The time base, ideal cycle time, and good-unit rule
OEE uses planned production time. A calendar-time denominator measures a different concept. Counting reworked units that eventually pass as first-pass good units obscures quality loss. Track asset utilization and final acceptance with separately named metrics when they are needed.
| Component | Calculation | Definitions to standardize |
|---|---|---|
| Availability | Run time ÷ planned production time | Identify planned production time and consistently record changeovers, failures, and other stops within it |
| Performance | Ideal cycle time × total units ÷ run time | Maintain the ideal cycle time by equipment, product, and process. Align time and quantity units |
| Quality | First-pass good units ÷ total units | Specify the inspection point and how rework is handled |
2.2 Recalculate a sample by hand
This example illustrates the business formula. Its variables are separate from HENGSHI interface parameters. Suppose a line has 480 minutes of planned production time and runs for 400 minutes. Ideal cycle time is 0.5 minutes per unit. It produces 600 units, of which 570 pass on the first attempt.
availability = 400 / 480
performance = (0.5 * 600) / 400
quality = 570 / 600
oee = availability * performance * quality # 0.59375, or 59.375%
Use a cycle time that reflects the speed achievable under ideal process conditions. An arbitrary historical average may introduce a different benchmark. For the same output, a faster benchmark means a shorter ideal time per unit and a lower calculated performance rate. Investigate cycle times and input definitions when performance exceeds 100%.
3. Govern the calculation with HENGSHI metrics
3.1 Separate the calculation from its business context
HENGSHI SENSE supports atomic metrics and business metrics. Atomic metrics define the calculation. Business metrics add filters, analysis dimensions, and time axes. Start with the underlying measures, including planned time, run time, total units, and first-pass good units. Define each component ratio and OEE from those measures so different dashboards can use the same definitions.
3.2 Use dimensions and grain across the enterprise
Align plant, workshop, line, product, shift, and production date in the data model. Business metrics can use analysis dimensions and reuse dimensions, time axes, and filters through a shared metric grain. Group and plant dashboards can then use the same definitions at the appropriate scope. Settle facility codes, shift boundaries, and product master data during implementation.
3.3 Distribute the same dashboard within authorized data scopes
HENGSHI provides row and column permissions. Row rules support simple and expression filters, with user attributes available in supported conditions. Define access for plant managers, workshop managers, and shift supervisors and test with representative accounts. Maintain the mappings between users, plants, and workshops. Check permissions separately on newly joined datasets before relying on any existing rules.
4. Keep the group dashboard accurate over time
4.1 Recalculate from the base measures
Suppose two comparable lines have 100 and 900 minutes of planned production and OEE values of 90% and 50%, respectively. The simple average is 70%. The planned-time-weighted result is 54%. Use the agreed rollup rule and calculate from the underlying quantities so lines of different sizes receive the intended weights.
When combining products or processes, check the product-specific cycle time, overlapping intervals, and duplicate output counts. One approach is to calculate ideal time for good units at the equipment, product, and period grain and roll it up within the approved scope. HENGSHI supports the metric expression and its reuse. Process owners decide which production runs are comparable.
4.2 Keep a history of definition changes
An engineering change may alter ideal cycle times or inspection rules. Maintain versions, effective dates, and scope in source data or the definition record. Decide whether historical reports retain the old definition or are recalculated. Publish that choice in the model and metric description so readers can interpret the trend.
4.3 Let Data Agent work with defined metrics
When a workshop manager asks which line lost the most effectiveness last week, the question still needs a facility, a time window, a comparison period, and an OEE definition. Use HENGSHI Data Agent for natural-language analysis and provide the work context through metric names, definitions, and applicability notes. Test common questions. When several definitions fit, the result should identify the one used or request clarification.
5. Give each level of the organization the same basis for decisions
Manufacturing groups need metrics they can reuse, explain, and access within the right scope. HENGSHI SENSE connects definitions, business dimensions, dashboards, and access controls. Start with a few representative production lines to validate inputs and calculations, then expand to more plants. A dependable OEE metric can help teams investigate production losses as well as preparing monthly reports.