OEE Calculation: Formula, Example & CalculatorOEE 计算：公式、完整算例与交互计算器

What does an OEE calculation measure?OEE 计算衡量什么？

OEE compresses three distinct loss dimensions into one percentage. Availability captures time lost while production was intended to run. Performance captures slow cycles and small stops while the process is considered running. Quality captures output that is not good on the first pass. Multiplication matters: a line with 90% in each factor has an OEE of 72.9%, not 90%.

OEE 把三个不同损失维度压缩为一个百分比。可用率反映计划运行期间的停机损失，性能率反映被视为运行时的慢周期与小停顿，质量率反映未能一次成为良品的产出。三者需要相乘：三个因素均为 90% 时，OEE 为 72.9%，不是 90%。

The score is useful for revealing where productive time is lost and tracking a stable process over time. It is not a financial return measure, maintenance KPI, labor-efficiency score, capacity-utilization rate, or substitute for safety, delivery, cost, and customer-quality measures.

该分数适合揭示有效生产时间损失并跟踪稳定流程的趋势。它不是财务回报、维修 KPI、劳动效率、产能利用率，也不能替代安全、交付、成本与客户质量指标。

The OEE formula and its three factorsOEE 公式及三个组成因素

The shortcut produces the same OEE when every input is defined consistently, but it hides which factor caused the loss. Use the three-factor method for operations improvement and the shortcut as an arithmetic cross-check. If the two results differ beyond rounding, investigate units, filters, event boundaries, or product-level cycle times.

当所有输入定义一致时，简式会得到相同 OEE，但会隐藏损失来自哪个因素。运营改进应使用三因素法，简式则用于算术交叉核验。若两种结果的差异超过舍入误差，应调查单位、筛选条件、事件边界或产品级理想周期。

Define the OEE time model before calculating计算前先定义 OEE 时间模型

Start with scheduled time, then document which periods are deliberately outside planned production: for example, an unscheduled shift, a period with no demand, or an approved non-production window. Planned Production Time is the denominator after those exclusions. Once time is designated for production, stops such as breakdowns, changeovers, material shortages, cleaning, or scheduled maintenance are normally losses within the model—not exclusions added later to improve the score.

先从排班时间开始，再记录哪些时间明确不属于计划生产，例如未排产班次、无需求时段或批准的非生产窗口。扣除这些排除项后得到计划生产时间。一旦某段时间被指定用于生产，故障、换型、缺料、清洁或计划维护通常应作为模型内损失，而不是事后为提高分数而排除。

Use one time unit throughout. If Ideal Cycle Time is seconds per part and Run Time is minutes, convert one of them before calculating. For batch, volume, continuous-process, or length-based production, replace part counts with a consistent output measure and define an ideal run rate appropriate to the process.

全过程使用同一时间单位。如果理想周期为秒/件而运行时间为分钟，计算前必须转换。对于批次、体积、连续流程或长度型生产，可用一致的产出度量替代件数，并为该流程定义合适的理想运行速度。

How to calculate OEE Availability如何计算 OEE 可用率

Availability includes any event that stops intended production long enough to meet the site's downtime threshold. Typical reasons include equipment failure, setup and adjustment, changeover, material shortage, operator absence, waiting for quality release, and planned maintenance performed during a production window. The category may differ by site; the arithmetic should not.

可用率包括任何达到现场停机阈值、使计划生产停止的事件。常见原因包括设备故障、设置与调整、换型、缺料、操作员缺席、等待质量放行，以及在生产窗口执行的计划维护。各现场分类可以不同，但算术口径应保持一致。

Set a documented threshold separating downtime events from small stops. If a three-minute stop is recorded in Stop Time, do not also let the missing output reduce Performance. Conversely, if small stops are inferred through speed loss, exclude them from Availability. The goal is a complete and mutually exclusive loss model.

应书面设定区分停机事件与小停顿的阈值。如果三分钟停顿已计入停机时间，就不能让缺失产量再次降低性能率；反之，如果小停顿通过速度损失推算，就应从可用率损失中排除。目标是建立完整且互斥的损失模型。

How to calculate OEE Performance如何计算 OEE 性能率

Performance measures how much net ideal production time was achieved within actual Run Time. It absorbs slow cycles and small stops not represented as downtime. The ideal cycle must describe a physically achievable, sustainable best rate for the specific product-process combination—not the recent average, budget rate, or a target slowed to make results look favorable.

性能率衡量实际运行时间中实现了多少理想净生产时间，涵盖未作为停机记录的慢周期与小停顿。理想周期必须表示特定产品—流程组合在物理上可实现、可持续的最佳速度，而不是近期平均、预算速度或为了让结果更好看而放慢的目标。

How to calculate OEE Quality如何计算 OEE 质量率

Define good output at the same measurement point as total output. Parts that require rework are generally not first-pass good even if recovered later; otherwise rework time and loss disappear from Quality. Record startup rejects, process defects, destructive-test samples, scrap, and rework consistently. If business reporting uses yield after rework, keep that measure separate from OEE Quality.

良品与总产量必须在同一测量点定义。需要返工的产品通常不属于一次通过良品，即使后来被修复，否则返工时间和损失会从质量率中消失。应一致记录启动废品、过程缺陷、破坏性测试样品、报废和返工。如果业务报告使用返工后良率，应与 OEE 质量率分开。

Count corrections, unit conversions, genealogy, and inspection timing can distort the factor. Late quality disposition may make today's production appear good and tomorrow's appear bad. Either restate the original production period after disposition or publish a controlled provisional/final status.

计数修正、单位换算、追溯关系与检验时点都可能扭曲质量率。延迟质量判定可能让今天产出看似良好、明天却变差。应在判定后重述原生产期间，或发布受控的暂定/最终状态。

Interactive OEE calculator交互式 OEE 计算器

Use one time unit. Scheduled time minus planned exclusions creates Planned Production Time; Stop Time must not exceed that value, and Good Count cannot exceed Total Count.

请使用统一时间单位。排班时间减计划排除得到计划生产时间；停机时间不得超过该值，良品数不得超过总产量。

A calculator validates arithmetic, not event definitions. Before comparing shifts, confirm the same production calendar, downtime threshold, ideal-cycle source, count point, good-part rule, unit, and aggregation method.

计算器只能验证算术，不能验证事件定义。比较班次前，应确认使用相同的生产日历、停机阈值、理想周期来源、计数点、良品规则、单位与聚合方法。

Worked OEE calculation exampleOEE 计算完整算例

Consider a hypothetical eight-hour shift: 480 scheduled minutes, 30 minutes deliberately outside planned production, 60 minutes of stop time, a 0.5-minute ideal cycle, 700 total units, and 665 first-pass good units. Planned Production Time is 450 minutes; Run Time is 390 minutes.

假设一个八小时班次：排班 480 分钟，30 分钟明确不属于计划生产，停机 60 分钟，理想周期 0.5 分钟/件，总产量 700 件，一次通过良品 665 件。计划生产时间为 450 分钟，运行时间为 390 分钟。

Availability = 390 ÷ 450 = 86.67%. Performance = (0.5 × 700) ÷ 390 = 89.74%. Quality = 665 ÷ 700 = 95.00%. OEE = 0.8667 × 0.8974 × 0.95 = 73.89%. The shortcut gives the same result: (665 × 0.5) ÷ 450 = 73.89%, equivalent to 332.5 fully productive minutes.

可用率 = 390 ÷ 450 = 86.67%；性能率 = (0.5 × 700) ÷ 390 = 89.74%；质量率 = 665 ÷ 700 = 95.00%；OEE = 0.8667 × 0.8974 × 0.95 = 73.89%。简式结果相同：(665 × 0.5) ÷ 450 = 73.89%，相当于 332.5 分钟完全有效生产时间。

The result does not say which corrective action has the best economics. It says Performance is the lowest factor in this example. The next step is to break its loss into slow-cycle and small-stop reasons, validate the ideal cycle, and compare recurrence, duration, output impact, cost, safety, and feasibility.

该结果并未说明哪项纠正行动最具经济性，只表明本例性能率最低。下一步应把性能损失拆分为慢周期和小停顿原因，验证理想周期，并比较发生频率、持续时间、产量影响、成本、安全与可行性。

Map OEE factors to a non-overlapping loss model把 OEE 因素映射到不重叠的损失模型

Keep reason codes few enough for reliable use but detailed enough to support action. Allow unknown and uncategorized codes; measure and reduce them rather than forcing a false reason. Separate automatic machine state from reviewed business reason, because a PLC can detect “stopped” but may not know whether the cause was maintenance, material, quality, or staffing.

原因代码数量应足以支持行动，但不能多到难以可靠使用。允许未知和未分类，并测量、逐步减少它们，而不是强行指定错误原因。应区分自动设备状态与复核后的业务原因，因为 PLC 能发现“停止”，却未必知道原因是维护、物料、质量还是人员。

Calculate OEE across products, shifts, and lines跨产品、班次与产线计算 OEE

Do not take a simple average of OEE percentages. A ten-minute run should not carry the same weight as a ten-hour run. Aggregate the underlying components: sum Run Time and Planned Production Time for Availability; sum Ideal Cycle Time × Total Count across product runs and divide by total Run Time for Performance; sum Good Count and Total Count for Quality. Then multiply the aggregate factors.

不要简单平均 OEE 百分比。十分钟运行不应与十小时运行具有相同权重。应聚合底层组成：可用率汇总运行时间与计划生产时间；性能率汇总各产品运行的“理想周期 × 总产量”，再除以总运行时间；质量率汇总良品数与总产量；最后相乘得到聚合 OEE。

For a production line, define the measurement boundary and bottleneck. Multiplying machine-level OEE values is not a valid line OEE. Starved and blocked time must follow a consistent line rule, and parallel equipment needs a capacity-aware denominator. Compare only like-for-like assets, products, and schedules unless differences are explicitly normalized.

对于生产线，应定义测量边界与瓶颈。把各设备 OEE 相乘并不能得到有效产线 OEE。缺料等待与阻塞时间必须遵循一致的产线规则，并行设备则需要考虑产能的分母。除非显式标准化差异，否则只应比较相似设备、产品与计划。

Interpret OEE without chasing a universal target解读 OEE 时不要盲目追逐统一目标

A higher score is not automatically better if the denominator changed, maintenance was deferred, quality definitions weakened, production was shifted elsewhere, or unsafe practices increased. Start with a trusted baseline for the same asset-product boundary, then monitor factor trends and loss reasons. Compare OEE with throughput, schedule attainment, changeover, maintenance, energy, safety, cost, and customer quality.

如果分母改变、维护被推迟、质量定义放宽、生产转移到别处或不安全做法增加，更高分数并不自动代表更好。应先为相同设备—产品边界建立可信基线，再监控因素趋势与损失原因，并将 OEE 与吞吐量、计划达成、换型、维护、能源、安全、成本和客户质量结合。

Use OEE as a loss-focused improvement measure, not a target that encourages gaming. A site with many changeovers, regulated cleaning, or deliberate flexibility may have a different practical profile from a stable high-volume line. External benchmarks rarely share identical calendars, loss thresholds, cycle standards, product mix, and quality rules.

应把 OEE 作为聚焦损失的改进指标，而不是诱导操纵的目标。频繁换型、受监管清洁或强调柔性的现场，其合理表现可能不同于稳定的大批量产线。外部基准很少具有完全相同的日历、损失阈值、周期标准、产品组合与质量规则。

A practical OEE implementation workflow可执行的 OEE 实施流程

1. Choose a decision boundary.选择决策边界。 Define asset or line, product, shift, calendar, owner, and the improvement decision OEE should support.定义设备或产线、产品、班次、日历、负责人以及 OEE 要支持的改进决策。
2. Approve the measurement contract.批准测量约定。 Document planned-time exclusions, downtime threshold, event precedence, ideal-cycle source, count point, and first-pass-good rule.记录计划时间排除、停机阈值、事件优先级、理想周期来源、计数点与一次通过良品规则。
3. Reconcile a representative pilot.核对代表性试点。 Compare automated events with operator logs, production reports, quality disposition, and counters across several shifts.跨多个班次，把自动事件与操作日志、生产报告、质量判定和计数器进行比较。
4. Publish factors and losses.发布因素与损失。 Show OEE with Availability, Performance, Quality, missing data, unknown time, and Pareto loss reasons.同时展示 OEE、可用率、性能率、质量率、缺失数据、未知时间与帕累托损失原因。
5. Close actions and preserve history.闭环行动并保留历史。 Assign owners, verify countermeasures, annotate structural changes, version standards, and avoid silently rewriting history.分配负责人、验证对策、标注结构变化、版本化标准，并避免静默改写历史。

OEE data-quality checks before publication发布 OEE 前的数据质量检查

• Planned Production Time is positive and does not exceed the relevant calendar window.计划生产时间为正，且不超过相关日历窗口。
• Stop intervals do not overlap, exceed the shift, or double-count a small-stop performance loss.停机区间不重叠、不超过班次，也不重复计算小停顿性能损失。
• Run Time equals Planned Production Time minus Stop Time within tolerance.运行时间在容差范围内等于计划生产时间减停机时间。
• Ideal cycle, product, cavity, unit, routing, and effective date are valid for each run.每次运行的理想周期、产品、模腔、单位、工艺路线与生效日期有效。
• Good Count is not greater than Total Count, and count resets or rollovers are handled.良品数不超过总产量，并正确处理计数器重置或回卷。
• Performance over 100%, negative values, zero denominators, missing reasons, and late quality changes enter an exception queue.性能率超过 100%、负值、零分母、缺失原因与延迟质量变化进入例外队列。
• Three-factor OEE agrees with the Fully Productive Time shortcut after unit conversion and rounding.完成单位换算与舍入后，三因素 OEE 与完全有效生产时间简式一致。

Report data completeness beside OEE. A precise percentage from incomplete stop events or stale cycle standards is less useful than a provisional score with explicit coverage. Freeze published periods or restate them through a controlled process with reason, approver, and audit trail.

应在 OEE 旁报告数据完整性。来自不完整停机事件或过时周期标准的精确百分比，不如明确覆盖范围的暂定分数有用。已发布期间应冻结，或通过记录原因、审批人和审计轨迹的受控流程进行重述。

Use OEE to prioritize manufacturing improvement使用 OEE 排定制造改进优先级

Decompose the lowest factor into loss reasons, then rank actions by productive-time impact, recurrence, cost, safety, customer effect, feasibility, and confidence. Availability actions may include reliability work, spares, changeover reduction, or material flow. Performance actions may address tooling, speed settings, microstops, sensors, standard work, or feed stability. Quality actions may focus on startup controls, process capability, material variation, error-proofing, and root-cause containment.

把最低因素拆解为损失原因，再按有效生产时间影响、重复频率、成本、安全、客户影响、可行性和置信度排序行动。可用率行动可能包括可靠性、备件、缩短换型或物料流；性能行动可能涉及工装、速度设置、微停、传感器、标准作业或供料稳定；质量行动可能聚焦启动控制、过程能力、材料波动、防错与根因遏制。

Track the baseline, countermeasure, owner, due date, expected loss reduction, validation window, actual result, and unintended effects. OEE can rise while total output falls if planned production time shrinks, so verify the improvement with absolute good output and business outcomes.

跟踪基线、对策、负责人、到期日、预期损失降低、验证窗口、实际结果与非预期影响。如果计划生产时间缩短，OEE 可能上升而总产量下降，因此必须用绝对良品产出和业务结果验证改进。

OEE calculation FAQOEE 计算常见问题

OEE formula sources and editorial limitationsOEE 公式来源与编辑限制

Vorne's OEE.com provides the factor definitions, preferred calculation, shortcut, and worked example in its OEE calculation reference. IBM describes Overall Equipment Effectiveness and the roles of Availability, Performance, and Quality in its OEE overview. SAP documents the same factor multiplication in its official OEE Calculations.

Vorne 的 OEE.com 在其OEE 计算参考中提供因素定义、推荐计算方法、简式与算例。IBM 在其OEE 概述中解释整体设备效率及可用率、性能率与质量率的作用。SAP 在官方OEE 计算文档中记录了同样的因素乘法。

Definitions still require local governance for calendars, planned exclusions, event thresholds, ideal rates, product mix, first-pass quality, and aggregation. This educational page and calculator do not replace manufacturing engineering, quality, safety, maintenance, accounting, statistical, or operational advice. For monitoring design, see InfiniSynapse's live guide to a focused data dashboard.

日历、计划排除、事件阈值、理想速度、产品组合、一次通过质量和聚合仍需本地治理。本教育页面和计算器不替代制造工程、质量、安全、维护、会计、统计或运营建议。关于监控设计，可参阅 InfiniSynapse 已上线的聚焦型数据仪表板指南。