Validate Instrumentation Data Acquisition: Frequency, Validation, Backup, Reporting

The checklist

Pre-Run Setup and Scheduling

1. 1Synchronize logger and gateway clocks via NTP/PTP using a verified time server; acceptance: drift ≤ 1 s per 24 h; evidence: time-sync screenshot and server address logged.
2. 2Configure sampling frequency per approved schedule using manufacturer software; acceptance: interval exactly matches plan (e.g., 60 s, 300 s); evidence: exported configuration file with version and timestamp.
3. 3Verify power availability (mains/UPS/battery) and estimate runtime; acceptance: ≥ 1.5× longest maintenance interval; evidence: photo of power setup, UPS status printout, runtime calculation.
4. 4Check local storage capacity versus expected data volume; acceptance: ≥ 14 days buffer at set rate; evidence: storage free-space screenshot and calculation sheet.

Data Acquisition Frequency Verification

1. 5Run a 30 min controlled acquisition and count records; acceptance: expected count within ±1 sample of theoretical; evidence: exported log and record-count summary.
2. 6Review timestamps for monotonic order and UTC timezone; acceptance: no duplicates, no gaps > 2× interval; evidence: CSV preview with checks report.
3. 7Confirm active channels match approved sensor list; acceptance: only authorised channels enabled; evidence: signed channel map and configuration export.
4. 8Validate event/threshold logging parameters where applicable; acceptance: trigger and hysteresis per plan; evidence: parameter screenshot and test event log.

Validation and Quality Control Steps

1. 9Apply plausibility range checks without interpreting trends; acceptance: values within defined engineering limits; evidence: automated QA report with zero hard-limit violations.
2. 10Calculate file checksums (SHA-256) on raw and exported datasets; acceptance: hashes stored with files; evidence: checksum manifest and verification log.
3. 11Ensure consistent missing-data code (e.g., -9999) across all channels; acceptance: single agreed code documented; evidence: configuration reference and file snippet.
4. 12Record calibration certificate IDs and validity dates for each sensor; acceptance: all active sensors listed and in date; evidence: calibration register with scanned certificates.
5. 13Enforce SI units and column metadata in outputs; acceptance: units declared (e.g., °C, m, kPa) and consistent; evidence: approved data dictionary and template check.

Data Backup and Redundancy

1. 14Configure automated daily backups to onsite NAS and offsite cloud; acceptance: two independent locations; evidence: backup job screenshots and schedules.
2. 15Perform monthly restore test from both locations; acceptance: 100% file recovery and checksum match; evidence: restore log and comparison report.
3. 16Enable write-once (immutable) export after daily acquisition; acceptance: WORM or locked folder policy active; evidence: storage policy screenshot and test write attempt.
4. 17Implement removable media rotation where used; acceptance: weekly rotation, labelled with date and volume ID; evidence: photos and hash report per media.

Reporting and Data Handover Format

1. 18Standardize CSV headers, order, encoding (UTF-8), and delimiter; acceptance: matches approved template; evidence: template file and validator pass screenshot.
2. 19Include a metadata sheet listing sensor IDs, coordinates, elevation reference, units, and sampling interval; acceptance: all fields complete; evidence: metadata CSV.
3. 20Provide daily summary with record counts, uptime, gaps, and alarms; acceptance: KPIs clearly shown; evidence: generated PDF and machine-readable JSON.
4. 21Use UTC timestamps, ISO 8601 format, and consistent file naming; acceptance: YYYY-MM-DD and versioned names; evidence: sample files and naming convention note.

Audit and Traceability

1. 22Maintain a change log for configuration edits; acceptance: date, reason, approver, before/after; evidence: signed change record.
2. 23Capture cabinet and seal photos at each visit; acceptance: date-stamped images stored by location; evidence: photo set in site folder.
3. 24Collect digital sign-off from operator and QA reviewer; acceptance: both signatures recorded; evidence: signed checklist PDF with QR verification.

Preview the printable checklist

Preview page one below. Open the image or download the PDF for all pages.

At a glance

• This checklist targets the acquisition layer only: it verifies logging frequency, time synchronisation, channel activation, and SI unit consistency. It prevents gaps and duplicates through structured tests, then documents proofs with screenshots, exported logs, and signatures for traceable compliance.
• Built-in validation steps flag incorrect headers, missing metadata, unsupported encodings, and checksum mismatches before data release. Teams confirm calibration references and consistent missing-data codes, ensuring downstream users receive clean, machine-readable files without manual fixes or assumptions.
• Resilient backup routines use two independent locations and routine restore tests, minimizing downtime and loss risk. Standardised CSV/JSON outputs, UTC timestamps, and clear file naming support automated ingestion pipelines and multi-stakeholder reporting with minimal friction during reviews and audits.
• Interactive online checklist with tick, comment, and export features secured by QR code.

How to use this interactive acquisition validation checklist

1. Preparation: Gather logger software, NTP/PTP access, checksum tool, storage calculator, approved templates, PPE, and site access permits. Confirm network connectivity, backup destinations, and authority requirements for retention.
2. Open the checklist, choose the project, and start Interactive Mode. Attach the monitoring plan, sensor list, and data dictionary. Set timezone to UTC and prefill sampling intervals.
3. Using the Interactive Checklist: Tick items as completed, add time-stamped comments, and upload screenshots, logs, and photos. Mention issues and tag reviewers for rapid resolution.
4. Export and share: Generate a clean PDF for stakeholders and an Excel/CSV evidence pack for records. Ensure filenames follow the naming convention and include UTC dates.
5. Sign-Off: Capture digital signatures from the operator and QA reviewer. Archive with QR authentication and distribute links to the project team for audit readiness.

Control acquisition frequency and time synchronisation

Getting frequency right starts with precise timekeeping. Synchronise logger clocks via NTP or PTP to limit drift and avoid duplicate or missing records during merges. Configure sampling intervals exactly per the monitoring plan, then prove performance with a short controlled run that counts expected versus actual records. Review timestamps for monotonic order, single timezone (UTC), and the absence of gaps larger than twice the configured interval. Lock approved channels and disable unused inputs to prevent stray columns in outputs. Finally, validate power and storage headroom so data does not stop during weekends or bad weather. These steps protect downstream processing pipelines and prevent retroactive fixes. The goal is clean, predictable time series at the source without discussing what the data means—only how it is acquired, stored, and handed over for others to interpret.

• Use NTP/PTP; target drift ≤ 1 s per 24 h.
• Test-run 30 min; record count within ±1 sample.
• Timestamps in UTC, ISO 8601, monotonic order only.
• Disable unauthorised channels to reduce spurious columns.

Structured validation without interpretation

Validation confirms data quality without inferring behaviour. Apply plausibility ranges and missing-data codes consistently, ensuring values sit within predefined engineering limits and that gaps are clearly marked. Compute checksums on raw and exported files to prove integrity end-to-end. Enforce SI units and consistent headers so machine workflows do not break. Track calibration certificates and link their IDs to channel metadata for traceability. These checks surface format and continuity issues early, before they contaminate reports. Avoid commenting on trends or causes; limit entries to pass/fail evidence like screenshots, manifests, and signed records. When a validation fails, document the defect with location, time, responsible party, and corrective action taken within the acquisition chain.

• Apply range checks; zero hard-limit violations allowed.
• Use a single missing-data code across all channels.
• Store SHA-256 hashes with datasets for integrity.
• Reference calibration IDs and expiry dates.

Backups, restore tests, and standardised reporting

Backups only count when restores work. Use two independent locations—onsite NAS and offsite cloud—and schedule daily jobs with monthly restore tests to confirm full recovery and matching checksums. Lock exports using write-once settings or retention rules to prevent accidental edits. For reporting, publish CSV with UTF-8 encoding and standardised headers, plus a metadata sheet covering IDs, coordinates, units, and sampling interval. Provide summary KPIs (counts, uptime, gaps) in both PDF and JSON to serve humans and machines. Adopt UTC timestamps and clear naming conventions to keep pipelines deterministic. Retention should follow approved project specifications and authority requirements, documented with owners and durations.

• Keep two copies; test restores monthly.
• Enable write-once or immutable folders for exports.
• Deliver CSV + JSON; include a complete metadata sheet.
• Use UTC and versioned, predictable file names.