Sensor Maturity & Readiness Assessment

A structured, savable audit for evaluating sensor coverage, signal health, sampling, data completeness, ownership, and organizational readiness for practical predictive maintenance pilots. Collects asset details, scored maturity questions, evidence notes, a recommended pilot scope, and an overall readiness score to prioritize action.

{"Title":"Sensor Maturity & Readiness Assessment","IntroductionHtml":"

Use this audit to quickly determine whether an asset (or group of assets) is ready for a practical predictive maintenance pilot. Score each area from 1 (poor / missing) to 5 (excellent / production-ready). Add notes or evidence where helpful. Saved responses create a record you can track, compare across assets, and use to prioritize pilot investments.

Scoring guidance: 1 = missing or unusable; 2 = very immature; 3 = basic coverage but gaps; 4 = mostly complete with minor issues; 5 = strong and ready for pilot.

","SubmitLabel":"Save Assessment","SuccessMessage":"Assessment saved. Use the readiness score and recommended next steps to prioritize sensorization and pilot planning.","DataType":"predictive_maintenance_sensor_assessment","SchemaVersion":"1.0","Fields":[{"Key":"assetIdentifier","Label":"Asset identifier (ID or name)","FieldType":"text","Required":true,"HelpText":"Give the asset name, line, equipment ID, or tag so others can find it."},{"Key":"assetLocation","Label":"Location / plant / cell","FieldType":"text","Required":false,"HelpText":"Where the asset is located (plant, building, cell, or area)."},{"Key":"assessorName","Label":"Assessor name","FieldType":"text","Required":true,"HelpText":"Person completing the assessment."},{"Key":"assessmentDate","Label":"Assessment date","FieldType":"text","Required":true,"HelpText":"Use YYYY-MM-DD or a short date to record when the audit was performed."},{"Key":"sensor_to_asset_mapping","Label":"Sensor-to-asset mapping completeness","FieldType":"scale","Required":true,"HelpText":"Do sensors cover all critical points on the asset (vibration bearings, bearings, motors, temperature points, pressure, flow, etc.)? Score sensor coverage and correctness.","Scale":{"Min":1,"Max":5}},{"Key":"signal_health_and_quality","Label":"Signal health and quality","FieldType":"scale","Required":true,"HelpText":"Are signals clean, within expected ranges, and free from frequent dropouts, noise, or clipping? Consider signal-to-noise, missing samples, and obvious faults.","Scale":{"Min":1,"Max":5}},{"Key":"sampling_frequency","Label":"Sampling frequency and configurability","FieldType":"scale","Required":true,"HelpText":"Are sampling rates appropriate for the failure modes you want to detect and configurable if needed? (e.g., vibration sampling rate, thermocouple logging interval).","Scale":{"Min":1,"Max":5}},{"Key":"data_completeness","Label":"Data completeness and retention","FieldType":"scale","Required":true,"HelpText":"Are data streams continuous for the period required to model failures, and is retention sufficient to include relevant failure examples? Consider gaps and storage policies.","Scale":{"Min":1,"Max":5}},{"Key":"timestamp_sync","Label":"Timestamp synchronization and ordering","FieldType":"scale","Required":true,"HelpText":"Are timestamps consistent across sensors and systems (NTP, timezone, sync) so events can be correlated accurately?","Scale":{"Min":1,"Max":5}},{"Key":"edge_buffering_and_resilience","Label":"Edge buffering & resilience","FieldType":"scale","Required":true,"HelpText":"Are edge devices buffering during network outages, and is data loss minimized? This matters for intermittent connectivity or remote locations.","Scale":{"Min":1,"Max":5}},{"Key":"data_ownership_and_access","Label":"Data ownership, access and connectivity","FieldType":"radio","Required":true,"HelpText":"Is it clear who owns the sensor data, who can access it, and are APIs or pipelines available?","Options":[{"Value":"clear_full_access","Label":"Clear ownership & full access"},{"Value":"partial_or_restricted","Label":"Partial or restricted access (needs approvals)"},{"Value":"no_access_or_unknown","Label":"No access / unknown"}]},{"Key":"labeling_and_failure_metadata","Label":"Labeling, failure history and metadata availability","FieldType":"scale","Required":true,"HelpText":"Is failure history labeled or logged (maintenance tickets, failure codes, operator notes) so models can learn? Are metadata and operating conditions recorded?","Scale":{"Min":1,"Max":5}},{"Key":"maintenance_process_maturity","Label":"Maintenance & failure investigation processes","FieldType":"scale","Required":true,"HelpText":"Are maintenance processes mature enough to validate predicted failures (clear escalation, response SLAs, and verification steps)?","Scale":{"Min":1,"Max":5}},{"Key":"signal_label_examples","Label":"Number of labeled failure examples (estimate)","FieldType":"number","Required":false,"HelpText":"Rough count of distinct labeled failure events (or '0' if none). Useful to estimate modeling feasibility."},{"Key":"data_accessibility_notes","Label":"Data access & integration notes","FieldType":"textarea","Required":false,"HelpText":"Record data sources ( historian / MQTT / edge gateway / PLC ), file formats, endpoints, and any known ETL or access blockers."},{"Key":"signal_health_notes","Label":"Signal health evidence or anomalies (notes)","FieldType":"textarea","Required":false,"HelpText":"Add example symptoms: repeated dropouts, large gaps, saturating signals, amplifier faults, or bad grounding evidence."},{"Key":"recommended_pilot_scope","Label":"Recommended pilot scope","FieldType":"select","Required":true,"HelpText":"Choose a pragmatic pilot scope based on assessment results.","Options":[{"Value":"single_asset","Label":"Single asset (one piece of equipment)"},{"Value":"asset_class","Label":"Asset class (same model/type across multiple locations)"},{"Value":"production_line","Label":"Full production line or cell"},{"Value":"fleet","Label":"Fleet-level (many similar assets across plant/enterprise)"}]},{"Key":"recommended_next_steps","Label":"Recommended next steps and quick wins","FieldType":"textarea","Required":false,"HelpText":"Concrete actions to improve readiness (e.g., add sensors to bearings, increase sampling to X kHz, implement edge buffering, map failure codes, run a labeling campaign)."},{"Key":"readiness_score","Label":"Overall readiness score (1-5)","FieldType":"number","Required":true,"HelpText":"Enter an overall readiness score (1 = not ready, 5 = ready). Optionally calculate the average of the scored fields above to produce this value, or enter a reasoned summary score."},{"Key":"immediate_risks","Label":"Immediate risks if pilot proceeds now","FieldType":"textarea","Required":false,"HelpText":"List quick risks such as high false alarm likelihood, missing critical sensors, lack of labeled failures, or no ownership for follow-up."},{"Key":"evidence_attachments","Label":"Evidence references (file names, ticket IDs, dataset paths)","FieldType":"textarea","Required":false,"HelpText":"Reference any supporting files, ticket numbers, dataset paths, or photos that support your answers so others can follow up."},{"Key":"assessor_confidence","Label":"Assessor confidence in these answers","FieldType":"scale","Required":true,"HelpText":"How confident are you in the answers provided? Lower confidence suggests follow-up discovery work.","Scale":{"Min":1,"Max":5}}]}

Discussion

Comments and conversation will live here.