Condition monitoring and diagnostics of machines — Data processing, communication and presentation — Part 1: General guidelines

What the authority record establishes

ISO 13374-1 establishes general guidelines for software specifications related to processing, communicating, and presenting machine condition-monitoring and diagnostic information.

Voluntary guidance

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 gives buyers a structured way to inspect data acquisition, manipulation, detection, assessment, prognosis, and presentation boundaries across monitoring stacks.

Affected operating stages

• Acquisition
• Processing
• Detection
• Assessment
• Prognosis
• Presentation

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.

API And Data Export

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 API and data export.

Affected buyer audiences

• condition-monitoring teams
• IT and OT
• reliability engineers
• software architects

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 establish data quality, diagnosis accuracy, interoperability in a configured system, or maintenance outcomes.