Template

Condition-Based Maintenance: Sensor & Data Specification (Interactive Template)

A fillable sensor and data specification template teams can use to capture clear, structured requirements for CBM pilots — sensor types, mounting, sampling, data formats, interfaces, preprocessing, governance, pilot validation criteria, and quick placement/grounding tips. Submissions are saved as structured JSON for reuse, review, and pilot planning.

Interactive Tool

Condition-Based Maintenance: Sensor & Data Specification

Use this form to capture clear, actionable sensor and data requirements for condition-based maintenance pilots. Complete as much detail as possible and attach sample data or vendor datasheets where available. Quick tips: place sensors close to the source, avoid mounting on thin or loose panels, keep cable runs short and shielded, and provide solid grounding. Include a short test recording during commissioning to verify signal quality.

Unique identifier and common name for the asset
Plant, area, line, or GPS coordinates
What the asset does and critical operating modes
Choose the sensor technology
If known
e.g., g, mm/s, °C, Pa, V, A
Enter desired samples per second. For waveform data, choose rate high enough to capture expected frequencies.
Nyquist margin, anti-alias filtering, and whether synchronized multi-channel sampling is required
How data will be recorded or exported
Typical min/max values under healthy conditions
e.g., ±50 g, 24-bit ADC, or 0–10 V
Describe patterns, frequencies, amplitudes or events that indicate failure
Select preprocessing steps the edge or server must perform
Select required timing precision
Example: Plant-Line-Asset-SensorType-Location-Channel
Stud mount, adhesive, magnetic, orientation relative to shaft/flow etc.
Quick tips on proximity to source, avoiding loose panels, thermal gradients, etc.
Suggested grounding practice and cable shielding to reduce noise
Voltage, current, local power source or battery life for wireless sensors
How sensor data will be transmitted or collected
e.g., M12, BNC, shielded twisted pair
Estimate longest practical cable run
e.g., >20 dB or acceptable noise floor
Will the sensor or gateway pre-process data before sending?
Describe algorithms, thresholds, or downsampling to execute at the edge
Local historian, cloud bucket, CMMS, filename conventions
Retention duration and aggregation rules, e.g., raw for 90 days then aggregated
Who should access raw data, processed data, and metadata
Name and contact for the owner of the data
Person responsible for data quality, metadata and labeling
Encryption, VPN, or data classification concerns
Define measurable acceptance criteria, e.g., detection sensitivity, false alarm rate, data completeness
Total hours of captured data planned for initial pilot
Links to sample files, screenshots, or vendor datasheets
Any other relevant information
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.