Condition monitoring and diagnostics of machines — General guidelines

What the authority record establishes

ISO 17359 gives general procedures for setting up a condition-monitoring program for machines.

Voluntary guidance unless adopted through policy, contract, or another authority

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

It requires predictive-maintenance buyers to evaluate the monitoring program, asset context, methods, data, thresholds, diagnosis, and action chain rather than the alert screen alone.

Affected operating stages

• Program Definition
• Asset Review
• Measurement
• Assessment
• Diagnosis
• Action
• Review

Capabilities to examine

Condition Monitoring And Sensor Ingestion

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for condition monitoring and sensor ingestion.

Anomaly Detection And Failure Prediction

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for anomaly detection and failure prediction.

Vibration And Machinery Diagnostics

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for vibration and machinery diagnostics.

Asset Health And Performance Analytics

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset health and performance analytics.

ERP MES SCADA And Historian Integration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP MES SCADA and historian integration.

Maintenance Knowledge And Assisted Triage

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for maintenance knowledge and assisted triage.

Affected buyer audiences

• reliability engineers
• condition-monitoring teams
• maintenance leaders
• operations

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

The standard does not validate a sensor, algorithm, diagnosis, maintenance recommendation, or future-failure prediction.