Trust & data integrity
Useful data needs
a clear history.
Knowing where a reading came from and how it reached your dashboard is part of making it useful.
See the outcome of data processing
Ingestion runs let operators inspect processing results and failures. Accepting a submission does not mean every reading is already available: the completed run and resulting instrument values provide that confirmation.
Inspect runs and troubleshoot ingestion →
Keep the measurement context
Measurements are associated with instrument variables and timestamps. Source timestamp settings, units, sites, and positions help reviewers interpret the values in the correct setting.
Make calculations explicit
Calculated variables, time periods, and calibration constants record how derived values are configured. When settings change, use recalculation and review the resulting values for the relevant period.
Work with calculated variables →
Understand the review conditions
Anomaly definitions evaluate the conditions you configure. Missing-signal checks are triggered by newly processed, non-skipped project data; they are not an independent timer that continues checking when an entire project stops sending readings.
Understand anomaly evaluation →
Agree on service expectations
Use the evaluation to discuss support, data handling, retention, and availability requirements. Your agreement is the reference for the service commitments that apply to your deployment.