ISO 17359 provides the framework for setting up condition monitoring programs on industrial machinery — defining how to select monitoring techniques, establish baseline measurements, set alarm thresholds, and document the program in a way that survives personnel turnover and audits. For cement plants, where rotating equipment failures carry million-dollar downtime consequences and regulatory visibility, ISO 17359 is not an aspirational standard — it is the defensible baseline that reliability engineers and auditors use to evaluate program maturity. The gap most cement plants face is not a lack of monitoring hardware but a lack of the structured documentation, alarm logic, and CMMS integration that transforms raw sensor data into an auditable condition monitoring program. This page covers the four pillars of ISO 17359 adoption for cement plants: asset criticality assessment, technique selection, alarm threshold establishment, and CMMS-backed records management. To see how OxMaint structures ISO 17359-aligned condition monitoring for cement plants, start a free trial or book a 30-minute demo with a cement plant reliability specialist.
ISO 17359 Condition Monitoring · Cement Plants · 2026
ISO 17359 Condition Monitoring Programs for Cement Plants
Asset criticality, monitoring technique selection, alarm thresholds, and CMMS records — the four-pillar framework that turns sensor data into an auditable condition monitoring program.
01
Asset Criticality Assessment
Determines which machines get what monitoring level
02
Technique Selection
Matches failure modes to the right measurement method
03
Alarm Threshold Logic
Sets alert and danger levels that detect without nuisance trips
04
CMMS Records Management
Creates the auditable evidence trail ISO 17359 requires
Pillar 1 — Asset Criticality Assessment
ISO 17359 requires every machine in the condition monitoring program to carry a documented criticality score. This score drives monitoring frequency, technique selection, and alarm response priority. Cement plants without a formal criticality register apply monitoring inconsistently — over-monitoring low-criticality assets while under-monitoring the ones that cause production stops.
Stops entire line (>8 hrs)
A — Critical
A — Critical
A — Critical
Stops one process unit (2–8 hrs)
B — Important
A — Critical
A — Critical
Has standby / spared (any duration)
C — General
B — Important
A — Critical
No process impact if fails
C — General
C — General
B — Important
A — Critical: continuous monitoring, 30-day route minimum
B — Important: 30–90 day route, alert-before-action threshold
C — General: 90-day route or condition-based inspection
Pillar 2 — Monitoring Technique Selection by Failure Mode
ISO 17359 Section 6 requires technique selection to be driven by failure mode analysis — not hardware availability. Cement plants commonly apply vibration analysis to every machine regardless of whether bearing defect frequencies are detectable, missing oil analysis on gearboxes where it would detect failure months earlier.
Vibration Analysis
Detects: bearing defects, imbalance, misalignment, looseness, gear mesh faults
Best Applied To
Ball mills, fans, separators, kiln drives, pumps above 15 kW
Not Effective For
Very slow shafts below 10 rpm, fluid film bearing instability alone
Route: 30 days (Critical), 60 days (Important)
Oil Analysis
Detects: wear particle generation, contamination, viscosity breakdown, additive depletion
Best Applied To
Gearboxes (raw mill, kiln drive), lube oil systems, hydraulic systems
Not Effective For
Grease-lubricated bearings, water-cooled components
Interval: 90 days on critical gearboxes, 180 days on general
Thermography (IR)
Detects: electrical connection hotspots, bearing overtemperature, refractory loss, conveyor belt slippage
Best Applied To
MCC panels, transformer connections, kiln shell, conveyor drive pulleys
Not Effective For
Subsurface defects, detection below insulation layers
Route: Quarterly for electrical, annual for mechanical
Ultrasonic Testing
Detects: early-stage bearing lubrication faults, compressed air leaks, valve seat leakage
Best Applied To
Slow-speed bearings (conveyor returns, kiln tire rollers), compressed air distribution
Not Effective For
High-background-noise areas near crushers without contact probe
Route: 60–90 days for bearing assets, quarterly for air systems
Configure Your ISO 17359 Monitoring Routes in OxMaint
OxMaint assigns each asset its monitoring technique, route frequency, and alarm thresholds in one register — then auto-generates work orders so no route gets skipped. Every reading feeds an auditable asset history.
Pillar 3 — Alarm Threshold Establishment
ISO 17359 requires alarm thresholds to be set from baseline measurements taken on the specific machine — not from generic industry tables. A kiln drive operating at 80% of its historical vibration baseline is a very different risk than the same machine at 80% of an ISO 10816 generic limit.
Step 1 — Establish Baseline
Measure and record vibration, temperature, and relevant parameter values on a machine known to be in good condition, at its normal operating load and speed. This baseline reading is the reference against which all future measurements are compared. ISO 17359 requires the baseline to be documented with operating conditions noted.
Step 2 — Set Alert at 150–175% of Baseline
Alert threshold signals a developing condition requiring investigation. Setting at 150–175% of baseline provides sufficient headroom above normal variation without delaying detection of genuine degradation trends. Alert level triggers work order creation and increased monitoring frequency — not immediate shutdown.
Step 3 — Set Danger at 250–300% of Baseline
Danger threshold represents imminent failure risk and triggers either automatic trip or immediate operator shutdown depending on machine criticality. The gap between Alert and Danger must be large enough to allow investigation and planned response — typically 30 minutes to several hours depending on failure progression rate.
Step 4 — Document and Review Annually
ISO 17359 requires threshold records to include the baseline measurement, the calculation method, the approving engineer's identity, and the effective date. Thresholds must be reviewed annually or after any major maintenance that could shift the machine's baseline characteristics — and every change must carry a documented work order trail.
Pillar 4 — CMMS Records the Standard Requires
ISO 17359 Section 9 defines the records a condition monitoring program must maintain. These are the five categories auditors check — and the ones OxMaint captures automatically with each work order.
| Record Category |
ISO 17359 Requirement |
OxMaint Capture |
| Baseline Measurements |
Documented at commissioning or program start, with operating conditions |
Asset-linked reading form with speed, load, and date fields |
| Periodic Route Data |
Each measurement with date, technician, equipment condition at time of reading |
Auto-scheduled work order with reading entry, sign-off, and photo |
| Alarm Events |
Date, threshold exceeded, response action taken, outcome |
Alarm event work order with response action and closure notes |
| Threshold Change History |
Before/after values, approving authority, change reason |
MOC-style work order with before/after fields and approval signature |
| Program Review Records |
Annual review showing technique effectiveness and criticality reassessment |
Annual PM template with checklist items covering each ISO 17359 review element |
Frequently Asked Questions
What is the difference between ISO 17359 and ISO 13373 for cement plants?
ISO 17359 is the overarching condition monitoring program standard — it covers program setup, criticality assessment, technique selection, and records management across all monitoring methods. ISO 13373 is a sub-standard focused specifically on vibration measurement procedures. For cement plants, ISO 17359 defines the program framework while ISO 13373 governs how vibration data is collected and analyzed within that framework. Most audits evaluate ISO 17359 program conformance first.
OxMaint supports both standards within the same asset register.
How do I establish baselines on machines that are already running?
For in-service machines without prior baseline records, the accepted approach under ISO 17359 is to take readings during a period of known stable operation — ideally after a scheduled maintenance event when the machine is confirmed to be in good condition. Record the operating conditions (speed, load, temperature) alongside the measurements. This retroactive baseline is valid as long as operating conditions are documented and the machine's health status at the time is noted.
Book a demo to see how OxMaint structures baseline entry workflows.
How often must a condition monitoring program be reviewed under ISO 17359?
ISO 17359 requires an annual program review covering technique effectiveness, criticality classification currency, alarm threshold validity, and personnel qualification status. The review must be documented with findings and any changes recorded. A CMMS-generated annual PM work order with a structured checklist is the most defensible way to demonstrate review compliance to auditors.
Does ISO 17359 require specific qualifications for condition monitoring personnel?
ISO 17359 references ISO 18436 for personnel qualification requirements — Category I for basic data collection, Category II for analysis and diagnosis, Category III for program management. The standard requires that the qualification level of personnel performing each activity is documented. CMMS work orders that capture technician identity and link to their qualification record provide the required evidence trail automatically.
Can a small cement plant implement ISO 17359 without a dedicated vibration analyst?
Yes. ISO 17359 allows route-based monitoring programs where operators or maintenance technicians collect readings on scheduled routes, with periodic analysis reviews performed by an external consultant or Category II analyst. The key requirement is that each step — collection, review, alarm response — has a defined responsible party and a documented record.
OxMaint structures these roles into the work order workflow so no step is undocumented.
Build Your ISO 17359 Program on a Platform That Documents Everything
OxMaint maps asset criticality, monitoring routes, alarm thresholds, and annual review tasks into a single CMMS platform — producing the records ISO 17359 requires without adding paperwork burden to your reliability team. Most cement plants are fully configured in 1–3 days.
