How maintenance and reliability teams should use eMaint to structure assets, control incoming work, plan executable jobs, build preventive maintenance, support technicians in the field, manage parts, preserve trustworthy history, and turn completed work into better maintenance decisions.
eMaint forms, statuses, approval paths, fields, permissions and workflows can be configured differently from one organization to another. The recommendations below are therefore operating standards, not claims that every eMaint instance ships with the same workflow.
A healthy eMaint implementation connects the physical plant to a controlled work process. If the organization skips those relationships, the database may still contain thousands of records while providing very little help with planning, risk, repeat failures, or maintenance strategy.
Asset structure is one of the highest-leverage decisions in a CMMS. eMaint supports hierarchical asset organization by location, system, department or custom groupings, along with specifications, documents and custom fields. That flexibility should be used to create a structure technicians can navigate and analysts can trust.
SITE: DENVER MANUFACTURING
AREA: PACKAGING
SYSTEM: PACKAGING LINE 2
ASSET: PKG-L2-CV-210 — Discharge Conveyor
COMPONENT: CV-210-MTR-01 — Drive Motor
COMPONENT: CV-210-GBX-01 — Gear ReducerNot every physical component deserves its own maintainable asset record. Create a separate record when independent history, cost, condition, PM activity, replacement decisions, warranty, regulatory evidence, or lifecycle management actually matters.
| Asset field | Recommended purpose | Common failure |
|---|---|---|
| Asset ID | Stable unique identifier that survives description changes. | Duplicate or location-dependent names create fragmented history. |
| Description | Human-readable equipment name. | Technicians see codes they cannot identify in the field. |
| Parent / location | Places the asset in the plant hierarchy. | Work is charged to a line or department instead of the failed asset. |
| Criticality | Represents consequence and influences maintenance strategy. | Everything is labeled critical, so nothing is prioritized. |
| Specifications | Stores decision-relevant technical attributes. | Hundreds of fields are created and then abandoned. |
| Documents | Connects manuals, drawings, procedures and approved technical information. | Technicians search shared drives after the asset is already down. |
eMaint supports multiple ways to submit maintenance requests and configurable routing. The intake process should make it easy to report an abnormal condition without forcing the requester to invent a technical cause.
“Conveyor broken. Replace gearbox.”
The condition is unclear and the proposed repair is presented as fact before diagnosis.
“PKG-L2-CV-210 intermittently stops under load. Drive motor continues running while belt stops. Happened three times in the last hour. Line restarts after product is removed.”
This records the observed condition and useful operating context without inventing the cause.
Request review should then screen duplicates, validate the asset, identify immediate hazards, determine business consequence, and decide whether the item becomes emergency response, urgent corrective work, routine planned work, an inspection, an improvement, or another controlled work type.
eMaint supports configurable workflows, approval routing and custom work-order statuses. Use that flexibility to establish explicit work-control gates.
| Priority concept | Practical meaning | Typical response |
|---|---|---|
| Emergency | Immediate safety, environmental, regulatory, severe quality or major production consequence. | Interrupt normal work under the site's emergency process. |
| Urgent | Material risk with short time-to-consequence, but not an uncontrolled emergency. | Expedite review and planning. |
| Routine corrective | Valid defect with manageable consequence. | Enter normal planning and scheduling. |
| Improvement | Work intended to reduce chronic loss, improve maintainability or eliminate risk. | Plan and prioritize against expected value and consequence. |
For the conveyor example, the first controlled work order might be:
WO: 104582
ASSET: PKG-L2-CV-210
TYPE: Corrective
PRIORITY: Urgent
SCOPE: Investigate intermittent belt stoppage under load.
KNOWN CONDITION: Motor continues running while belt stops.
OBJECTIVE: Identify failure mechanism, restore reliable operation and document verification.Notice what is missing: “replace gearbox.” Until the gearbox is proven to be the failure mechanism, putting it into the scope converts an assumption into maintenance history.
Maintenance planning prepares the job before the asset is released. A well-configured eMaint workflow can support that discipline with statuses, required fields, procedures, parts, documents, assignments and approvals, but the organization must define the readiness standard.
What work is expected? What condition is known? What must be diagnosed?
Required craft, crew size, estimated hours and specialized support.
Required parts physically available, staged or credibly committed.
Special tools, test equipment, drawings, manuals, procedures and specifications.
LOTO boundary, hazards, confined space, hot work, line break or other controlled requirements.
Production release, sanitation, quality, contractor, crane/lift or other dependencies.
Troubleshooting can still be planned. “Troubleshoot conveyor drive system and determine cause of intermittent belt stoppage” is a legitimate planned scope when the diagnosis is not yet known, provided the technician receives the correct drawings, history, tools, access and decision boundaries.
eMaint documents recurring maintenance based on time, meter readings or conditions, and supports procedures and inspection-oriented work. That capability is valuable only when the maintenance basis is defensible.
| PM element | Question to answer |
|---|---|
| Failure mode | What specific failure or degradation mechanism is this task intended to manage? |
| Task | What must the technician actually do? |
| Acceptance criteria | What separates acceptable condition from a defect? |
| Interval basis | Why this calendar, meter or condition threshold? |
| Required evidence | What reading, observation, pass/fail result or work finding must be recorded? |
| Follow-up rule | What happens when the task finds an abnormal condition? |
Inspect conveyor monthly.
No failure mode, inspection point, method, limit or response.
Inspect drive-end bearing for abnormal noise, looseness and temperature relative to site-approved acceptance criteria. Record condition. Create corrective work when limits are exceeded.
The task still requires site-approved technical limits, but the maintenance purpose and response are clear.
High PM compliance proves that scheduled work was completed on time. It does not prove the task prevents failures, detects degradation early enough, uses the correct interval, or produces corrective follow-up.
Read: PM Compliance vs PM Effectiveness → Read: PM Frequency Optimization →
eMaint's current mobile capabilities include work-order and request management, asset history, photos/video, inspections, parts access, QR/barcode workflows, labor tracking, signatures and offline work that synchronizes after reconnection. Those features can reduce transcription and improve field history when the execution standard is clear.
eMaint supports spare-parts records, work-order parts booking, asset associations, reorder visibility, purchasing functions and cross-site inventory capabilities. The maintenance process should distinguish what the system says exists from what is physically available for the job.
| Control | Why it matters |
|---|---|
| Asset BOM | Helps planners and technicians identify likely parts without relying entirely on memory. |
| Critical spare flag | Connects stock strategy to failure consequence and replenishment risk. |
| Reservation / staging | Prevents a scheduled job from discovering that the “available” part was consumed elsewhere. |
| Issue to work order | Preserves cost and consumption history at the asset/job level. |
| Cycle counting | Tests whether system quantity matches physical quantity. |
| Reorder logic | Connects usage, lead time and consequence to replenishment. |
Recent eMaint X5 updates have included inventory controls such as blind-count options and cross-site part transfers. Those capabilities can improve control, but they still depend on technicians, planners and storeroom personnel using the transaction process consistently.
A work order should not be considered analytically useful merely because its status changed to complete. Closeout should preserve enough evidence for someone months later to understand what happened and whether the repair addressed the failure mechanism.
Changed bearing. Running.
Symptom: drive-end bearing noise and elevated housing temperature. Finding: inner-race damage; pulley misalignment observed during disassembly. Correction: replaced bearing and realigned pulley. Verification: conveyor operated loaded for 30 minutes with normal tracking, noise and temperature trend. Follow-up alignment check scheduled.
Useful structure: Symptom → Finding/Cause → Correction → Verification.
When the cause is unknown, record it as unknown or not confirmed. A fabricated root cause is worse than a blank one because it contaminates every future repeat-failure review.
eMaint supports failure codes and configurable completion controls. A 2025 eMaint Mobile update also added close validation that can require related fields before a work order is closed on mobile. Use required fields carefully: require what materially improves control and analysis, not every field the system can display.
eMaint provides reporting and dashboard capabilities for work, assets, inventory and maintenance performance. The correct question is not “Which KPIs can eMaint calculate?” It is “Which decisions can our data support without overstating confidence?”
| Metric | Useful for | Data dependency |
|---|---|---|
| Reactive work % | Understanding capacity consumed by unplanned demand. | Consistent work-type definitions and actual labor. |
| PM compliance | Execution discipline. | Correct due dates, completion dates and on-time rules. |
| Schedule compliance | Weekly schedule stability. | Frozen schedule baseline and break-in-work rules. |
| Backlog weeks | Work inventory relative to planned-work capacity. | Executable backlog status and realistic labor capacity. |
| Repeat failure rate | Repair effectiveness and chronic-loss detection. | Asset identity plus usable symptom/cause/correction history. |
| MTBF | Reliability trend for an appropriately defined repairable population. | Valid operating exposure and consistent functional-failure definition. |
| MTTR | Restoration / maintainability trend when the time boundary is defined. | Reliable event timing and clear distinction between active repair and delay. |
eMaint documents integrations with ERP platforms such as SAP and Oracle, SCADA/PLC data, REST API connectivity, the Connect2Assets framework and Fluke condition-monitoring tools. The vendor also describes sensor/condition thresholds triggering work orders with asset context attached.
A sensor alarm should not automatically be treated as proof of root cause. It is evidence of a condition. Maintenance still needs a controlled diagnostic and response process.
| Area | Minimum operating standard |
|---|---|
| Asset master | Unique ID, clear description, correct parent/location, lifecycle status, useful technical attributes, criticality where governed, and relevant approved documents. |
| Work request | Correct asset/location, observed condition, operating context, consequence and requester. |
| Work order | Controlled work type, priority, scope, asset, ownership and status. |
| Planning | Scope, labor, parts, tools/info, safety requirements, access/coordination and credible duration before Ready to Schedule. |
| PM | Failure-mode purpose, clear task, acceptance criteria, interval basis, required evidence and corrective follow-up rule. |
| Execution | Actual labor, parts, findings, measurements, correction, new defects and verification. |
| Closeout | Symptom, cause/finding when known, corrective action, verification and follow-up. Never invent cause. |
| Inventory | Asset/BOM relationship, critical-spare logic, physical accuracy, issue-to-work history and replenishment governance. |
| Reporting | Metric definitions documented; weak or missing source data disclosed before decisions are made. |
| Governance | Named owners for master data, work types, priorities, statuses, failure taxonomy, required fields, permissions and changes. |
XRVE recommendations in this guide are independent maintenance-practice guidance. Product-capability statements were checked against eMaint's current public materials.
eMaint and associated product names are trademarks of their respective owners. XRVE Reliability is not affiliated with, endorsed by, or sponsored by eMaint or Fluke Reliability. Product configurations, licensing and features can change; verify current vendor documentation and your own system configuration before treating a feature as available.
Return to the series hub for SAP PM and the upcoming MaintiMizer and Fiix field guides.
Browse CMMS Brand GuidesRegardless of platform, work history is only useful when asset identity, work type, dates, labor, failure information and closeout are governed.
Read the data-quality guideUse this guide with Free Studio to analyze sanitized, authorized facility data yourself, including work history, planning and failure-code patterns. XRVE offers recurring paid intelligence and separate expert-led system redesign when the organization needs sustained support.
Use Free Studio Review expert services