Sensor & Signal Readiness Checklist for Predictive Maintenance (Interactive)

{"Title":"Sensor & Signal Readiness Checklist for Predictive Maintenance","IntroductionHtml":"

Use this checklist to quickly assess whether the sensor signals and supporting data infrastructure are ready to support a practical predictive maintenance pilot. Each item asks for a short yes/no or numeric response and a place to record evidence or notes. Completing the checklist helps avoid common failures caused by poor sensor placement, unsynchronised timestamps, missing data, or unclear ownership.

","SubmitLabel":"Save Checklist","SuccessMessage":"Checklist saved. Use the notes and scores to prioritize fixes before starting a pilot.","DataType":"predictive_maintenance_sensor_readiness","SchemaVersion":"1.0","Fields":[{"Key":"sensor_location_ok","FieldType":"yesno","Label":"Are sensors located and mounted correctly for the intended measurement (vibration, temperature, current, etc.)?","HelpText":"Check that sensors are on correct measurement points, firmly mounted, oriented correctly, and isolated from unrelated vibrations or heat sources.","Required":true},{"Key":"sensor_location_evidence","FieldType":"textarea","Label":"Evidence / Notes about sensor location and mounting","HelpText":"Record photos, part IDs, mounting type (magnet/stud/adhesive), and any anomalies discovered.","Required":false},{"Key":"nominal_sampling_rate_hz","FieldType":"number","Label":"Measured nominal sampling rate (Hz)","HelpText":"Enter the sampling frequency recorded at the ingestion point (e.g., 1024 Hz). If the signal is event-based, enter nominal event frequency or leave blank and explain in notes.","Required":false},{"Key":"anti_aliasing_confirm","FieldType":"yesno","Label":"Is anti-aliasing (analogue or digital) applied appropriately for this sensor?","HelpText":"Confirm that analogue low-pass filters or digital decimation preserve the frequency band needed to detect expected failure modes.","Required":true},{"Key":"sampling_notes","FieldType":"textarea","Label":"Sampling & anti-aliasing notes","HelpText":"List expected failure frequencies, any down-sampling applied, and concerns about lost bandwidth.","Required":false},{"Key":"timestamp_sync_method","FieldType":"select","Label":"How are timestamps synchronized?","HelpText":"Accurate timestamps are critical for aligning signals and events across equipment and systems.","Options":[{"Label":"PTP (Precision Time Protocol)","Value":"ptp"},{"Label":"NTP (Network Time Protocol)","Value":"ntp"},{"Label":"Device-local (manual) / not synchronized","Value":"local"},{"Label":"Unknown","Value":"unknown"}],"Required":true},{"Key":"timestamp_skew_sec","FieldType":"number","Label":"Observed max timestamp skew (seconds)","HelpText":"Measure the largest observed difference between devices or between device and server. If unknown, enter -1 and add notes.","Required":false},{"Key":"timestamp_notes","FieldType":"textarea","Label":"Timestamp synchronization notes","HelpText":"Include any corrective actions planned (enable PTP, tighten NTP sync, apply gateway timestamping, etc.).","Required":false},{"Key":"data_completeness_percent","FieldType":"number","Label":"Percent of expected samples/events received over the assessment window (%)","HelpText":"Typical acceptance threshold: >95% for continuous signals. Enter integer 0-100.","Required":true},{"Key":"gap_events_count","FieldType":"number","Label":"Number of observed data gaps or outages in the window","HelpText":"Count distinct gap events (not lost samples). Use logs or historian reports where possible.","Required":false},{"Key":"gap_acceptability","FieldType":"radio","Label":"Are observed gaps acceptable for pilot use?","HelpText":"Consider whether gaps coincide with failures, shift changes, or network maintenance.","Options":[{"Label":"Acceptable","Value":"acceptable"},{"Label":"Unacceptable","Value":"unacceptable"},{"Label":"Unsure / needs further analysis","Value":"unsure"}],"Required":true},{"Key":"gaps_notes","FieldType":"textarea","Label":"Gap details and mitigation plan","HelpText":"Describe root causes (network, device reboot, ingestion pipeline) and planned mitigations.","Required":false},{"Key":"labels_consistent","FieldType":"yesno","Label":"Are signal names, tags, and event labels consistent and meaningful?","HelpText":"Consistent labeling simplifies model training and reduces human interpretation errors (use asset IDs, signal types, units).","Required":true},{"Key":"labeling_convention","FieldType":"text","Label":"Existing labeling convention or example label","HelpText":"Provide an example (e.g., PlantA.Line3.Motor5.VIB_X).","Required":false},{"Key":"label_notes","FieldType":"textarea","Label":"Labeling & tagging notes","HelpText":"List missing tags, mismatches between historian and OT systems, or needed normalization rules.","Required":false},{"Key":"owner_defined","FieldType":"yesno","Label":"Is there a defined owner for the signal (team or individual) and a contact?","HelpText":"Owner ownership ensures someone can investigate issues and provide context or failure history.","Required":true},{"Key":"signal_owner","FieldType":"text","Label":"Signal owner (role or contact)","HelpText":"Enter team name, role, or person (e.g., ReliabilityEngineer.TeamA).","Required":false},{"Key":"access_roles","FieldType":"text","Label":"Which roles currently have access to raw signals?","HelpText":"List roles/groups (e.g., OTAdmin, Reliability, DataScience).","Required":false},{"Key":"access_issues","FieldType":"textarea","Label":"Access problems or blockers","HelpText":"Note firewall, VLAN, historian export, or permission issues preventing data access.","Required":false},{"Key":"quick_test_passed","FieldType":"yesno","Label":"Did the quick data-acceptance test pass?","HelpText":"Quick test steps: stream 60–120s of data, visualise waveform, run a simple FFT or moving RMS, and confirm expected behavior.","Required":true},{"Key":"quick_test_details","FieldType":"textarea","Label":"Quick test observations and evidence","HelpText":"Record sample screenshots, expected vs observed behaviors, and links to saved artifacts.","Required":false},{"Key":"overall_readiness","FieldType":"scale","Label":"Overall sensor & signal readiness (1 = Not ready, 5 = Ready for pilot)","HelpText":"Use your judgment across all items. A score of 4–5 suggests proceed with a focused pilot; 1–3 suggests work on gaps first.","Required":true},{"Key":"recommended_next_steps","FieldType":"textarea","Label":"Recommended next steps (top 3 actions)","HelpText":"Be specific: e.g., remount sensor on Motor 5, enable PTP on edge gateway, normalize tag names, grant historian read access to DataScience.","Required":false}]}