INNORIX in Practice, Fleet-Scale Collection

We need to find out what happenedat a site six months ago.

The work on site ended long ago.But that day's records are now needed for an important business decision.

Scenario
A fictional operating scenario showing how a company secures and uses past data created in the field.

Back to today2026.11.16

TODAY, NOV 16, 2026

Customer quality inquiry

Product
Production lot P-260516-042
Production date
2026.05.16

Records to check

  • Production conditions at the time
  • Device operating records
  • Inspection results and original data
  • Software and configuration info

6 MONTHS AGO, MAY 16, 2026

The site that day

  • Device-017
  • Device-018
  • Device-024
  • Device-031
  1. 08:42Production started
  2. 10:16Device setting changed
  3. 11:48Production finished
  4. 13:20Quality inspection complete

Records created on site that day

Over six months, countless jobs were done on site.So where are that day's records now?

Back in the present, the question appears: where are the records from six months ago?

INNORIX in Practice

Today, Customer inquiry09:20

THE REQUEST, Today 09:20

An inquiry arrives about a product made six months ago.

The company runs 1,280 devices across 24 sites nationwide.

Every day it produces and inspects countless products, and each device writes a range of files about the work it does.

One Monday morning, a customer files a quality inquiry about a product delivered six months ago.

The production date and lot number are easy to find, but today's production data alone can't answer the inquiry.

The team needs to see what was actually done on site back then.

NOV 16, 09:20

Customer quality inquiry

Reference
QI-2026-118
Production lot
P-260516-042
Production date
2026.05.16
Production site
Site-008
Customer request
Confirm production conditions and inspection results

Records requested by Quality

Record neededPurpose
Production recordsWhen the work started and ended
Device operating logsHow the devices ran during production
Device configurationThe working conditions actually applied
Software informationPrograms and versions in use at the time
Inspection resultsThe final inspection verdict
Inspection original dataDetailed verification of the results
We know what was produced.Now we need to confirm how it was produced.

Live contextNow

09:202026.11.16

Date under investigation
2026.05.166 months ago

WHAT WE KNOW

Product lot and production date confirmed

WHAT WE NEED TO KNOW

Under what conditions was it produced?

Today 09:45

The site is no longer what it was six months ago.

The production management system shows the 6 devices involved in that job.

But the site’s operating environment changed a lot over those six months.

Some devices reached end of life and were replaced; others now run new software.

Production conditions were changed several times, too.

Checking how a device is set up today says nothing about how it was set up six months ago.

NOV 16, 09:45

Same site, a different operating environment than six months ago

MAY 16, 2026

Devices 6 months ago

  • Device-017Setup at the time
  • Device-018Setup at the time
  • Device-021Setup at the time
  • Device-024Setup at the time
  • Device-031Setup at the time
  • Device-043Setup at the time

NOV 16, 2026

Devices today

  • Device-117Replaced 017
  • Device-018Settings changed
  • Device-121Replaced 021
  • Device-024Software updated
  • Device-031Settings changed
  • Device-043Unchanged
Devices replaced
2
Setup changed
3
Unchanged
1
Looking at the site todaycan't tell you what it was like back then.

Live contextNow

09:452026.11.16

Devices involved then
6 devices2 replaced, 3 reconfigured

WHAT WE KNOW

2 of the 6 related devices replaced

WHAT WE NEED TO KNOW

Are the replaced devices’ records still there?

Today 10:10

Most of the records from that day are gone from the field devices.

Field devices write new files continuously as they do their work.

Operating logs are deleted or overwritten after a set period. Inspection originals, too, are kept only as long as the device’s storage allows.

Trying to collect those records from the devices now is no use: a file that no longer exists can’t be retrieved.

So instead of searching the field devices, the company starts checking whether the files had been collected into its archive back then.

NOV 16, 10:10

How long do files stay on site?

LOCAL DATA RETENTION

  • Still on the device
  • Past retention period
File typeOn-site retentionData from 6 months ago
Operating logs30 daysDeleted
Inspection originals60 daysDeleted
Production results90 daysDeleted
Device configurationCurrent settings onlyChanged
Collecting only once the need arisescan't recover past records that are already gone.

Live contextNow

10:102026.11.16

Devices involved then
6 devices2 replaced, 3 reconfigured

WHAT WE KNOW

No past records left on site

WHAT WE NEED TO KNOW

Did the company collect anything back then?

LET'S GO BACK TO THAT DAY

May 16, 2026

Six months earlier, an ordinary day was getting started on site.

  1. 05.166 months ago
  2. 06.16
  3. 07.16
  4. 08.16
  5. 09.16
  6. 10.16
  7. 11.16Today

What data was created on site that day?

INNORIX in Practice

Today, Customer inquiry09:20

6 months ago 08:42

Production starts at the site as on any other day.

May 16, 8:42 a.m.

A new production job starts at Site-008.

Production devices do the work, control devices manage the working conditions, and inspection devices get ready to check the finished products.

Each device writes files for its own purpose.

No one expects these records to be needed for a customer’s quality inquiry six months later.

MAY 16, 08:42

An ordinary day, with data coming from many different devices

  • Production device

    Device-017

    • production.csv
    • runtime.log
  • Process control device

    Device-018

    • conditions.json
    • control.log
  • Auxiliary production device

    Device-021

    • process.csv
    • operation.log
  • Inspection device

    Device-024

    • inspection.csv
    • measurements.csv
  • Vision inspection device

    Device-031

    • images/
    • image_results.json
  • Site management system

    Device-043

    • work_order.json
    • lot_history.csv
Even a single jobleaves different records on many devices.

SIX MONTHS EARLIER

08:422026.05.16

Work in progress
Production underway

FILES BEING CREATED

production.csv, conditions.json, inspection.csv and more

CURRENT STATE

Operating records created on 6 related devices

6 months ago 10:16

A device setting is changed during production.

At 10:16 a.m., the site operator adjusts the production conditions.

It is a routine change, made according to the procedures in place at the time.

The device’s working settings change, and the control system records the values before and after.

The production device starts logging its operation under the new conditions.

The finished production result alone reveals none of these steps in between.

MAY 16, 10:16

The process the final production result doesn’t show

PRODUCTION CONDITION HISTORY

Illustration of the condition change record written by the device at the time

FINAL PRODUCTION RECORD

production.csv

  • Production lot: P-260516-042
  • Start: 08:42
  • End: 11:48
  • Result: Completed

DETAILED DEVICE RECORD

condition_history.json

  • 10:16:03 Condition A
  • 10:16:08 Adjustment
  • 10:16:12 Condition B
  • 10:16:15 Applied
Files that record the outcome of the workare not the files that record how it was done.

SIX MONTHS EARLIER

10:162026.05.16

Work in progress
Production condition change

FILES BEING CREATED

condition_history.json, control.log

CURRENT STATE

Records being written on field devices

6 months ago 13:20

Production and inspection are complete.

Production finishes at 11:48 a.m., and inspection of the product is complete by 1:20 p.m.

The final inspection records a pass.

Besides the final verdict, the inspection devices also hold the original data from the inspection, such as measurements and images.

The site wraps up the job and starts preparing for the next production run.

MAY 16, 13:20

The work is done, but the files it produced remain.

Production lotP-260516-042

Inspection resultPassed

DataCreated bySize
Production recordsDevice-017, 021284 MB
Operating logsDevice-017, 018, 0211.8 GB
Setting change historyDevice-01824 MB
Software information6 related devices8 MB
Inspection results, measurementsDevice-024612 MB
Inspection original imagesDevice-03118.4 GB
Work orders and lot historyDevice-04342 MB

SUMMARY RESULTS

Inspection verdict and measurements

inspection_results.csv

ORIGINAL RECORDS

Original inspection data

inspection_originals/

That day, the site was already preparing for the next job.And these records were still on the devices.

SIX MONTHS EARLIER

13:202026.05.16

Work in progress
Production and inspection result files created

FILES BEING CREATED

inspection_results.csv, inspection_originals/

CURRENT STATE

Inspection results and original data created

THE RECORDS LEAVE THE FIELD, 6 months ago 23:00

The day's records are collected into the enterprise archive.

At 11 p.m., the company’s scheduled data collection kicks off.

Operating records, production data and inspection results from 24 sites nationwide flow into the enterprise archive.

Each device produces different data, so each has collection rules suited to its role.

The company couldn’t predict every way this data might be used.

But it was regularly securing the records its operations and quality checks depend on.

MAY 16, 23:00

Collecting the day's records from sites across the country

Sites
24
Devices collected
1,280
Schedule
Daily 23:00

Daily field records

Collection datasetSourceFile typesSchedule
Production recordsProduction devicesCSV, LOGDaily
Device conditionsControl devicesJSON, CSVDaily
Software informationAll related devicesJSONDaily
Inspection resultsInspection devicesCSVDaily
Inspection originalsVision inspection devicesTIFF, JPEGDaily
Work historySite management systemJSON, CSVDaily

COLLECTION RUN, MAY 16

Source deviceFilesStatus
Device-017Production recordsCompleted
Device-018Condition historyCompleted
Device-021Operation recordsCompleted
Device-024Inspection resultsCompleted
Device-031Inspection originalsCompleted
Device-043Work historyCompleted

Collection results at the time for the 6 devices now under investigation

The work on site is over,but its records now begin to live on at the company.

SIX MONTHS EARLIER

23:002026.05.16

Work in progress
Daily record collection

COLLECTION DESTINATION

Enterprise archive

CURRENT STATE

Scheduled collection running across all sites

6 months ago 23:48

Records are stored by the date and device that created them.

Sometimes different devices create files with the same name.

Files like runtime.log, result.csv and config.json are common to many devices.

Instead of dropping collected files into a single folder, the company stored them in a structure that keeps site, device and record date apart.

That structure matters months later, when a specific record has to be found again.

MAY 16, 23:48

Same file name, records from different devices

ENTERPRISE DATA ARCHIVE

  • Field-records/
  • 2026/
  • 05/
  • 16/
  • Site-008/
  • Device-017/
  • Device-018/
  • Device-021/
  • Device-024/
  • Device-031/
  • Device-043/

2026/05/16/Site-008/Device-017

FileSize
production.csv142 MB
runtime.log486 MB
device_config.json182 KB
software_version.json12 KB

ARCHIVED FILE IDENTITY

Source site
Site-008
Source device
Device-017
Record date
2026.05.16
File name
runtime.log
Collected at
2026.05.16 23:42:18
Destination
Enterprise archive
As important as securing the filesis being able to tell which site and which record each one is.

SIX MONTHS EARLIER

23:482026.05.16

Related devices collected
6 / 6

COLLECTION DESTINATION

Enterprise archive

CURRENT STATE

Stored in the enterprise archive

MAY — NOVEMBER 2026

For six months, the site kept changing.But that day's records stayed in the enterprise archive.

  • JulDevice-017 replacedOld device retired
  • SepDevice-021 replacedNew device introduced
  • NovPast records keptStored under the company’s retention policy

A device’s working lifeis not the useful life of the data it creates.

What changed at the company over six months

WhenChange on siteRecords kept by the company
MayProduct made and inspectedProduction, operating and inspection data secured
JunNew production conditions appliedRecords before and after the change kept
JulSome devices replacedRecords of the replaced devices kept
AugSoftware updatedOperating records from the previous version kept
SepMore devices replacedOld and new devices’ records kept apart
OctSite staff changedData kept by device, not by person
NovCustomer quality inquiry receivedData collected six months ago searched

The company kept collected data under a 24-month retention policy. Storage capacity, access rights and deletion are managed separately under its own data management standards.

BACK TO TODAY

November 16, 2026

Files that were routine work records six months agoare now key evidence for answering a customer inquiry.

MAY 16, WHEN CREATED

Routine work records

  • production.csv
  • condition_history.json
  • inspection_results.csv
  • inspection_originals/

NOV 16, WHEN NEEDED

Today's investigation evidence

  • production.csv
  • condition_history.json
  • inspection_results.csv
  • inspection_originals/

The files haven’t changed.Why the company needs them has.

INNORIX in Practice

Today, Customer inquiry09:20

Today 10:30

The company searches the collection records from six months ago.

From the production history, the quality team identifies the site and the devices involved.

Then it starts looking for the records collected into the enterprise archive on that date.

Whether or not a device is connected today, the completed collection history and the archived files are there to check.

Records from devices already replaced and no longer in service are part of the investigation, too.

NOV 16, 10:30

Searching past collection records, not the devices running today

File search

INNORIX Studio

Search conditions

Collection date
2026.05.16 – 2026.05.17
Source devices
6 related devices
Source site
Site-008
Transfer status
Completed

Search resultsPast collected files

File nameSourceCollectedSize
production.csvDevice-01705.16 23:42142 MB
runtime.logDevice-01705.16 23:42486 MB
condition_history.jsonDevice-01805.16 23:2824 MB
operation.logDevice-02105.16 23:34820 MB
inspection_results.csvDevice-02405.16 23:18612 MB
image_results.jsonDevice-03105.16 23:3118 MB
lot_history.csvDevice-04305.16 23:1242 MB

Device-017Current status: Retired

Past collection record2026.05.16 confirmed

The device is gone,but the records collected from it are still there.

Live contextNow

10:302026.11.16

Production date under investigation
2026.05.16Production lot P-260516-042

WHAT WE KNOW

Collection history from that day found

WHAT WE NEED TO KNOW

Is everything the investigation needs still there?

Today 11:20

Records collected from different devices are reviewed.

Using the collection history, the quality team locates the original files it needs in the enterprise archive.

The production records show when the work started and ended.

The device operating logs show how the devices ran during the job, and the setting records show when the working conditions changed.

The files collected from the inspection devices include not just the final verdict but detailed measurements and original images.

Files created for different purposes now come together in a single investigation.

NOV 16, 11:20

Checking one job takes many different records.

REQUIRED RECORDS

6 / 6Required record types secured

Source devices6

RecordSourceStatus
Production recordsDevice-017, 021, 043Available
Operating logsDevice-017, 018, 021Available
Device settings and change historyDevice-018Available
Software information6 related devicesAvailable
Inspection results and measurementsDevice-024Available
Inspection original imagesDevice-031Available
  • DEVICE-018

    condition_history.json

    • Timestamp: 10:16:08
    • Previous: Condition A
    • Current: Condition B

    When the working conditions changed

  • DEVICE-024

    inspection_results.csv

    • Lot: P-260516-042
    • Inspection: 13:20
    • Result: Passed

    Final inspection result at the time

  • DEVICE-017

    software_version.json

    • Device: Device-017
    • Version: 3.8.2
    • Date: 2026.05.16

    Software in use at the time

  • DEVICE-031

    inspection_originals/

    Original inspection data re-reviewed

Put together, the records each device left behindbecome the evidence of that day's work.

BACK TO TODAYNow

11:202026.11.16

Required record types secured
6 / 6

WHAT WE KNOW

Original data from the related devices secured

WHAT WE NEED TO KNOW

What can each record tell us?

RECONSTRUCTING THE PAST, Today 14:30

The work done on site six months ago is reconstructed.

The quality and engineering teams review the secured data together.

By lining up records from different devices in the order the work actually happened, they reconstruct what was done on site that day.

They can see when production started, when the working conditions changed, how the devices ran afterward, and the final inspection result.

It’s a review of the records created at the time, not of today’s device settings or anyone’s memory.

NOV 16, 14:30

May 16, 2026: the work on site, reconstructed

RECONSTRUCTED PRODUCTION HISTORY

Files collected from each device, compared in time order by the company’s engineering team

TimeConfirmed workEvidence
08:42Production of the lot startsproduction.csv
10:16Production conditions changedcondition_history.json
After 10:16Production under the new conditionsruntime.log
11:48Production finishedproduction.csv
13:20Final inspection completeinspection_results.csv
Before 13:20Inspection originals and measurements createdinspection_originals/
No one may remember the work from six months ago.But the records made at the time can be checked again.

BACK TO TODAYNow

14:302026.11.16

Work reconstructed
08:42 — 13:202026.05.16

WHAT WE KNOW

Time of the production condition change confirmed

WHAT WE NEED TO KNOW

What evidence can back the answer to the customer?

Today 16:40

The company answers the customer based on the records from that day.

At 4:40 p.m., the quality team pulls together the data it secured and the facts it confirmed.

It can show when the production conditions changed and what the work records looked like before and after.

The original data also confirms that the final inspection result was a pass.

Whether the condition change directly caused the issue the customer raised still needs further verification.

The company answers the customer, keeping confirmed facts separate from open questions, and prepares follow-up tests.

NOV 16, 16:40

Quality investigation report

REFERENCE QI-2026-118

Production lot P-260516-042

Production date: May 16, 2026

Confirmed facts

Production time
08:42 – 11:48
Working condition change
10:16
Software at the time
Secured and verified
Final inspection result
Passed
Inspection original data
Secured and reviewed

Further verification

Reproduction tests will be run to verify whether the production condition change is linked to the issue the customer reported.

Attachments and evidence

  • Production and operating recordsAvailable
  • Device settings and change history at the timeAvailable
  • Inspection results and original dataAvailable
Instead of guessing about the past,the company bases today's work on the records from that day.

Live contextNow

16:402026.11.16

Under investigation
2026.05.16Evidence-based investigation complete

WHAT WE KNOW

Production and inspection process from that day confirmed

NEXT ACTION

Customer answer and further verification

THE SAME QUESTION, TWO DIFFERENT SITUATIONS

Whether records from six months ago survivechanges what a company can do today.

WITHOUT HISTORICAL RECORDS

Looking for data only once it’s needed

  • Operating logs of past devicesDeleted
  • Device settings at the timeChanged
  • Records of replaced devicesUnavailable
  • Inspection original dataDeleted

The past has to be inferred from whatever data is left and from people’s memories.

Some facts remainimpossible to confirm.

WITH HISTORICAL RECORDS

Routine work records secured all along

  • Operating logs of past devicesSecured
  • Device settings at the timeSecured
  • Records of replaced devicesSecured
  • Inspection original dataSecured

The original data from the devices at the time is checked, records are compared, and follow-up verification goes ahead.

Past recordsback today's decisions.

INNORIX in Practice

Today, Customer inquiry09:20

FROM COLLECTION TO RETENTION

The company rethinks which records to keep, and for how long.

Prompted by this inquiry, the company reviews its existing collection and data retention policies.

There’s no need to keep every file from every device forever.

But it does need to decide which files matter for quality verification, customer response and work history, and secure them for the right length of time.

Even when devices are replaced or the operating environment changes, the records that matter must stay with the company.

ENTERPRISE DATA POLICY

Collection and retention policies shaped by how the data is used

Data typeCollectionRetentionPurpose
Production recordsDaily36 monthsProduction history checks
Operating logsDaily12 monthsDevice operations and troubleshooting
Error recordsWhen created24 monthsTechnical investigation
Device configurationDaily and on change36 monthsChecking past operating conditions
Inspection resultsDaily36 monthsQuality verification
Inspection originalsDaily24 monthsDetailed re-verification
Temporary work filesNot collected—No long-term retention needed

RETENTION PERIOD BY DATA TYPE

An example setup: INNORIX handles collection, while long-term storage, retention periods and deletion policies are managed in the enterprise archive.

What matters is not how much data you keep,but which records you need, and for how long.

THE VALUE OF KEEPING THE RECORDS

The routine work records created todaymay one day be needed for an important business decision.

That day's recordsToday's decision
Record created
2026.05.16
Time passed
6 months
Record needed
2026.11.16

Field devices get replaced, software changes, and people and work move on.The data a company needs can stay useful far longer than any of that.

The work on site may pass,but the records a company needs must remain.

THE TECHNOLOGY BEHIND THIS STORY

Fleet-Scale Collection

Collect files created across sites nationwide, on industrial devices and in a range of systems, into the enterprise archive.

Set up collection by data type and device role, and when past work records are needed, check the collection history and the archived data.

Explore the product