Industrial data, historians & data quality

Analytics is only as good as the signal that reaches it. These guides follow industrial data from the sensor to storage: checking units, timestamps and quality codes, choosing between a historian and a data lake, sizing retention and compression, and cleaning data without removing real events.

Start here

A suggested reading order.

  1. Check sensor data quality before building analytics

    Use simple checks for completeness, range, timing and context before trusting a trend or training a model.

    Industrial data · 2 min
  2. Write a data contract your automation and IT teams can both use

    Define meaning, timing, quality and ownership so an industrial tag remains understandable outside its source system.

    Industrial data · 2 min
  3. Historian vs Data Lake: Where Should Industrial Data Actually Live?

    Historians are optimized for fast time-series; data lakes for flexible analytics. The two are complementary - if you design the boundary.

    Industrial data · 2 min

Related tools

Try what you read.

PDF resources

Guides and worksheets to bring to a meeting.

All resources

Write a data contract your automation and IT teams can both use

Define meaning, timing, quality and ownership so an industrial tag remains understandable outside its source system.

2 pages · 169 KB

Every article on this topic

Open in the article list

Common questions

Historian or data lake?

A historian suits fast time-series queries and operational visibility; a data lake suits long-term analytics across many sources. Many plants use both.

How do I measure data quality?

Start by measuring missing data, stale values, clock drift, unit errors and flatline (frozen sensor) behavior.

Other topics

Planning an IT/OT project?

Describe your machine, data flow or production goal in a few sentences and the ASP Dijital team will reply by email.

Contact ASP Dijital