Uptime is the percentage of planned production time during which a piece of equipment or a line is actually operating and available for work, rather than stopped for failure, setup, or idling. In manufacturing documentation it appears in overall equipment effectiveness (OEE) reports, maintenance dashboards, service contracts, and capacity planning, where translators must distinguish scheduled uptime from total calendar time.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Uptime typically appears in translated maintenance manuals, OEE dashboards, service-level metrics, and production reports. Translators handle it in KPI tables, shift summaries, and troubleshooting guides, where it accompanies figures, formulas, and targets. Terminology work often involves clarifying the exact denominator—planned time, calendar time, or shift time—so the translated metric does not shift meaning.
A frequent mistranslation is rendering “uptime” as “availability” or as total running time without checking whether the source denominator is planned production time, calendar time, or shift time. That causes real confusion in OEE and service-level texts, where availability and reliability may be separate KPIs. Another error is literal “up time” splitting or using “正常运行时间” in contexts that imply runtime only, losing the scheduled-time ratio.
Check equipment names, units, safety instructions and interface labels against the source and approved references. Confirm any market-specific document requirements separately.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Construction-machinery technical documentation.
Read the published project →Tire-technology documentation across multiple Asian languages.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Smart Manufacturing solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.