INNORIX in Practice, Fleet-Scale Collection

Devices generate data every day,but they do not connect every day.

Every device works in a different environment and connects to the network at a different time.Follow one week of data collection in exactly that kind of environment.

Scenario
A fictional one-week data collection scenario across 500 devices running on different network environments.

WednesdayConnection status of 500 devices

500 devices

FIELD OPERATIONS, 7 DAYS

MONTUEWEDTHUFRISATSUNMobile devicesRemote site devicesIndustrial equipmentField systems
  • Connected
  • Not connected
Devices in operation
500
Connected today
298
Not connected today
202
Collected today
324 GB
Even while devices are offline,data in the field keeps being created.

If you can't know when devices will connect, how can a business keep collecting their data?

INNORIX in Practice

Monday, Collection begins08:00

MONDAY, 08:00

500 devices start their workday.

The business runs 500 devices across many different sites.

Some are installed at company facilities, while others move to a new area every day. Some work for long periods in places where the network is hard to reach.

They operate in different environments, but all of them generate data: work records, operation logs, measurement results and more.

The business needs to collect that data continuously, to use it in daily work and to check how its devices are running.

MONDAY, 08:00

One company's devices run in very different environments.

  • Trucks lined up at a logistics depot and a worker holding a tablet

    Mobile devices180 devices

    Network access changes with each route and where the day’s work ends.

    Trip logs, location history, job results

  • A solar-powered sensor station on a misty mountain

    Remote site devices120 devices

    Run on their own for long stretches in areas with limited connectivity.

    Measurements, sensor logs, status information

  • An engineer on a production floor lined with equipment

    Industrial equipment140 devices

    Network access windows depend on work schedules and equipment policies.

    Work logs, inspection results, operation logs

  • A field worker with a laptop next to oil well equipment

    Field work systems60 devices

    Stay offline during field work and connect once the job is done.

    Job results, site images, reports

DAILY DATA GENERATION

Devices in operation
500
Data generation
Daily
Network connection
Irregular
When data is created andwhen it can be collected are two different things.

Live contextNow

08:00Monday

Connected today
342 devices
Not connected today
158 devices
Collected this week
0 GB

CURRENT DEVICE

All devices

CURRENT TASK

Checking scheduled collection targets

23:00

Some devices never connected today.

Over the course of Monday, 342 devices connected to the network.

The other 158 did not connect at all.

The connected devices sent the files designated for collection to company storage.

But the devices that stayed offline also hold files created today.

The business does not simply mark them as failed. It records that they cannot be collected yet and keeps them lined up for collection later.

MONDAY, 23:00

Not all data created today arrives today.

COLLECTED

342 devices

Connected and collected today

NOT YET CONNECTED

158 devices

Waiting to connect, data kept on the device

INNORIX STUDIO, FLOWS

Daily field collection

Source devices
Field devices, 500
Source files
/logs/, /measurements/, /results/
Destination
Enterprise field storage
Schedule
Every day
Collection condition
Device available
Save rule
Device / original data date

MONDAY COLLECTION RESULT

Collected
342 devices
Not connected
158 devices
Data collected
286 GB
Data that could not be collected todaymust not drop off the collection list.

Live contextNow

23:00Monday

Connected today
342 devices
Not connected today
158 devices
Collected this week
286 GB

CURRENT DEVICE

All devices

CURRENT TASK

Scheduled collection from reachable devices

TUESDAY, 10:20

A device connects at an unexpected time.

A mobile device that stayed offline the day before connects to the network at 10:20 a.m.

It was due to connect the previous evening, but a change in the field schedule brought it back a day late.

The business had no way of knowing exactly when it would connect.

Once the connection is detected, collection runs on the files that were missed.

Today's work isn't over yet, but yesterday's data can already be secured.

TUESDAY, 10:20

Not the scheduled time, but the time it actually connected.

FIELD DEVICE

Connected

Device-0178

Connection history

Local data accumulation

Last connected
Before Mon 18:00
Reconnected
Tue 10:20
Uncollected files
4.8 GB

INNORIX STUDIO, RUNS

Device-0178 collection

FileSizeStatus
operation_monday.log184 MBCompleted
route_history.csv26 MBCompleted
job_results.zip4.59 GBCompleted

Collection completed at10:27

Whenever a device comes back,data collection picks up with it.

Live contextNow

10:20Tuesday

Connected today
386 devices
Not connected today
114 devices
Collected this week
698 GB

CURRENT DEVICE

Device-0178

CURRENT TASK

Securing files missed the day before

WEDNESDAY, 14:10

A device offline for three days comes back.

A device working at a remote site connects for the first time on Wednesday afternoon.

From Monday to Wednesday it had been generating data without a single day off.

Its storage held 27.8GB of files created over the past three days.

The business needed more than just Wednesday’s data.

The data created on Monday and Tuesday had to be secured as well.

And Monday’s records must not be filed as Wednesday’s just because they were collected on Wednesday.

WEDNESDAY, 14:10

Three days of data are collected in a single connection.

DEVICE-0246, LOCAL STORAGE

  • MondayFiles created, not yet collected8.4 GB

  • TuesdayFiles created, not yet collected12.6 GB

  • WednesdayFiles created, not yet collected6.8 GB

Total uncollected data27.8 GB

ENTERPRISE FIELD STORAGE

How collected data is stored

  • /field-data/Device-0246/
  • /monday/8.4 GBCompleted
  • /tuesday/12.6 GBCompleted
  • /wednesday/6.8 GBCompleted
Data created
Monday–Wednesday
Actually collected
Wednesday 14:10–14:48
Even when data arrives late,you must be able to tell when it was created.

Live contextNow

14:10Wednesday

Connected today
298 devices
Not connected today
202 devices
Collected this week
1.022 TB

CURRENT DEVICE

Device-0246

CURRENT TASK

Collecting three days of accumulated files

DATA GENERATION & CONNECTIVITY

Time a device spends offlineis not time without data.

MondayTuesdayWednesdayThursdayFridaySaturdaySunday
Device-0178ConnectionConnectedConnectedNot connectedConnectedConnectedNot connectedConnected
Data generatedData generatedData generatedData generatedData generatedData generatedData generatedData generated
Device-0246ConnectionNot connectedNot connectedConnectedNot connectedConnectedNot connectedNot connected
Data generatedData generatedData generatedData generatedData generatedData generatedData generatedData generated
Device-0312ConnectionConnectedNot connectedConnectedConnectedNot connectedConnectedConnected
Data generatedData generatedData generatedData generatedData generatedData generatedData generatedData generated
  • Connected
  • Not connected
  • Data generated
When data is created
Driven by field work
Created continuously while the device is working.
When a device connects
Driven by the network
Depends on where the device is and its work schedule.
When data is collected
Driven by collection conditions
Runs once the device connects and collection conditions are met.

INNORIX in Practice

Monday, Collection begins08:00

THURSDAY, 09:40

A device drops offline mid-collection.

Thursday morning: an 18.6GB file is being collected from a mobile device.

Partway through, the device starts moving again and loses its network connection.

It was not connected long enough to collect everything that was needed.

11.2GB had already been transferred.

If collection had to start over from the beginning, the next connection might not be long enough for the whole file either.

So the business keeps the progress made so far and waits for the device to reconnect.

THURSDAY, 09:40

Devices are not always connected as long as collection needs.

INNORIX STUDIO, RUN DETAILS

Connection interrupted

Device-0312

field_capture_2026-11-12.bin

60.2%

Transferred 11.2 GBTotal 18.6 GB

  1. 09:24:00Collection started
  2. 09:32:005.6 GB transferred
  3. 09:40:0011.2 GB transferred
  4. 09:40:12Network connection lost
  5. 09:40:12Waiting for reconnection
Already transferred
11.2 GB
Transfer progress kept
Remaining
7.4 GB
Resumes at the next connection
A dropped connection is no reasonto throw away the progress already made.

Live contextNow

09:40Thursday

Connected today
421 devices
Not connected today
79 devices
Collected this week
1.34 TB
Device-0312 progress
60.2%
Remaining
7.4 GB

CURRENT DEVICE

Device-0312

CURRENT TASK

Connection lost, collection progress kept

16:25

The same device reconnects.

At 4:25 p.m., the device that lost its connection in the morning is back on the network.

About 6 hours and 45 minutes have passed since the morning’s collection was interrupted.

Collection resumes from exactly where the morning transfer left off.

The remaining 7.4GB is transferred and the whole file is collected.

Neither the first connection nor the second was long enough to collect the whole file from start to finish.

Yet by using both connections, the business secured the file it needed.

THURSDAY, 16:25

Two separate connections add up to one complete collection.

Transfer progress shown on a compressed timeline.

  1. Connection lost
  2. Collection resumed
  3. Collection complete

INNORIX STUDIO, RUN DETAILS

Completed

Device-0312

field_capture_2026-11-12.bin

100%

First connection
11.2 GB
Second connection
7.4 GB

Final result18.6 GB, Completed

A device does not need to stay connected for long.Collection can carry on across several connections.

Live contextNow

16:25Thursday

Connected today
421 devices
Not connected today
79 devices
Collected this week
1.57 TB

CURRENT DEVICE

Device-0312

CURRENT TASK

Remaining file data collected

FRIDAY, 18:00

Many devices return at about the same time.

As Friday evening arrives, devices that spent the week out in the field start returning to company sites.

More devices than usual connect to the network within a short window.

Some of them carry several days of uncollected data.

The business needs both the files created today and the files it could not collect earlier.

When connection times can’t be planned, collection requests can pile up in a single time window.

The business sets up its environment so every device’s collection is handled even then.

FRIDAY, 18:00

Devices scattered all week connect at about the same time.

NEW CONNECTIONS BY HOUR, EXAMPLE

Peak hours
Connected today
462 devices
Collected today
684 GB
Incl. earlier data
246 GB

INNORIX STUDIO, RUNS

Field device collection

DeviceCollection scopeDataStatus
Device-0084Friday1.2 GBCompleted
Device-0146Wed – Fri8.6 GBCompleted
Device-0238Mon – Fri16.4 GBTransferring
Device-0342Thu – Fri4.2 GBTransferring
Device-0461Fri2.8 GBWaiting

DAILY COLLECTION VOLUME

Created on Friday
438 GB
Missed in earlier days
246 GB
Each device connects at its own time with its own backlog,and each gets the collection it needs.

Live contextNow

18:00Friday

Connected today
462 devices
Not connected today
38 devices
Collected this week
2.254 TB

CURRENT DEVICE

All devices

CURRENT TASK

Handling a surge of collection jobs

SATURDAY, 11:30

Files that are not normally collected are now needed.

Saturday morning: the technical support team asks for detailed operation records to analyze how some devices are behaving.

The files collected day to day hold only basic operational information.

This analysis needs the last five days of detailed debug logs and diagnostic files.

There is no need to pull that data from all 500 devices.

Technical support asked for 32 devices.

But 11 of them are not connected to the network right now.

The business collects from the connected devices first and sets up a separate job to collect from the rest at their next connection.

SATURDAY, 11:30

Secure extra data while routine collection keeps running.

TECHNICAL SUPPORT REQUEST

We need detailed diagnostic records for the last 5 days.

Target devices
32
Period
Monday–Friday
Files needed
debug.log, diagnostics.bin
Destination
Technical support storage

SELECTED DEVICES

  1. 01 connected
  2. 02 connected
  3. 03 not connected
  4. 04 connected
  5. 05 connected
  6. 06 connected
  7. 07 connected
  8. 08 not connected
  9. 09 connected
  10. 10 not connected
  11. 11 connected
  12. 12 connected
  13. 13 not connected
  14. 14 connected
  15. 15 not connected
  16. 16 connected
  17. 17 connected
  18. 18 not connected
  19. 19 connected
  20. 20 not connected
  21. 21 connected
  22. 22 connected
  23. 23 not connected
  24. 24 connected
  25. 25 not connected
  26. 26 connected
  27. 27 connected
  28. 28 not connected
  29. 29 connected
  30. 30 not connected
  31. 31 connected
  32. 32 connected
Requested
32 devices
Connected
21 devices
Not connected
11 devices

INNORIX STUDIO, FLOWS

FlowDevicesScope
Daily field collection500Routine operation records
Technical diagnostics32Selected detailed records

Routine and additional collection run as independent Flows.

Even when you can’t tell when devices will connect,new collection jobs can be added at any time.

Live contextNow

11:30Saturday

Connected today
315 devices
Not connected today
185 devices
Collected this week
2.634 TB

CURRENT DEVICE

32 selected devices

CURRENT TASK

Selective additional collection

SUNDAY, 23:59

What did the week secure?

Sunday at midnight, the business reviews the past week of data collection.

Not all 500 devices connected every day.

Some connected several times a day; others connected only once all week.

482 devices delivered all of the target data created during the week.

13 still had some data left to collect, and 5 never connected at all.

The business does not just look at the total amount collected.

It checks which period of data was secured from which device, and which dates are still missing.

SUNDAY, WEEKLY COLLECTION REVIEW

Connection records and actual collection results are not the same.

Complete for the full period
482 96.4%
Some days missing
13 2.6%
Offline all week
5 1.0%

WEEKLY DATA AVAILABILITY, EXAMPLE

Collection status by device and data creation date

  • Collected
  • Uncollected data
  • Not connected
MonTueWedThuFriSatSun
Device-0042CollectedCollectedCollectedCollectedCollectedCollectedCollected
Device-0116CollectedCollectedCollectedCollectedCollectedCollectedCollected
Device-0178CollectedCollectedCollectedCollectedCollectedCollectedCollected
Device-0246CollectedCollectedCollectedCollectedCollectedCollectedUncollected data
Device-0312CollectedCollectedCollectedCollectedCollectedCollectedCollected
Device-0368CollectedCollectedCollectedCollectedUncollected dataUncollected dataUncollected data
Device-0412Not connectedNot connectedNot connectedNot connectedNot connectedNot connectedNot connected
Device-0476Not connectedNot connectedNot connectedNot connectedNot connectedNot connectedNot connected

WEEKLY COLLECTION VOLUME

2.93 TB

Includes data created that day and data from earlier days collected late.

What matters is not only how much data arrived,but also which data has not arrived yet.

Live contextNow

23:59Sunday

Connected today
278 devices
Not connected today
222 devices
Collected this week
2.93 TB
Complete for the full period
482 devices
Partially complete
13 devices
Not connected
5 devices

CURRENT DEVICE

All devices

CURRENT TASK

Reviewing the week's collected data

SEVEN DAYS OF FIELD COLLECTION

Different devices connected each day.Data collection never stopped.

Devices connected and data collected per day

Connected at least once this week
495 devices
Fully collected for the whole week
482 devices
Data secured this week
2.93 TB

Not every device connected every day,yet a full week of data was secured from almost all of them.

INNORIX in Practice

Monday, Collection begins08:00

NEXT MONDAY, 08:30

Work continues for devices that didn't connect last week.

A new week begins.

Two of the devices that never connected last week come online in the morning.

They still hold data created since last Monday.

While starting the new week's collection, the business also secures last week's missing data.

Last week being over doesn't make last week's target data disappear.

Data that can still be collected keeps being collected, and devices offline for a long time are flagged for the people in charge to check.

NEXT MONDAY, 08:30

The business week starts fresh,but unfinished collection carries over.

PREVIOUS WEEK, PREVIOUSLY UNCONNECTED DEVICES

  • Device0412Connected
  • Device0438Connected
  • Device0456Offline
  • Device0476Offline
  • Device0498Offline

INNORIX STUDIO, COLLECTION RUNS

DeviceData periodSizeStatus
Device-0412Previous week42.6 GBTransferring
Device-0438Previous week18.4 GBTransferring
Device-0456Previous weekUnknownOffline
Device-0476Previous weekUnknownOffline
Device-0498Previous weekUnknownOffline

PREVIOUS WEEK

Last week's data

Collection continues for devices that were offline or had files left uncollected.

THIS WEEK

This week's data

The regular scheduled collection runs on new data created across all 500 devices.

Collection is driven not by the calendar,but by the data the business has yet to secure.

Live contextNow

08:30Next Monday

Connected today
346 devices
Not connected today
154 devices
Collected this week
2.93 TB

CURRENT DEVICE

Device-0412, Device-0438

CURRENT TASK

Securing data missed in the previous period

DATA COLLECTION BEYOND CONNECTIVITY

No business can know in advancewhen every device will connect.

MONTUEWEDTHUFRISATSUN
Device-0178ConnectedConnectedNot connectedConnectedConnectedNot connectedConnected
Device-0246Not connectedNot connectedConnectedNot connectedConnectedNot connectedNot connected
Device-0312ConnectedNot connectedConnectedConnectedNot connectedConnectedConnected
Business collectionCollection runningCollection runningCollection runningCollection runningCollection runningCollection runningCollection running

Device connections were irregular,but data collection carried on all week.

In the field, new data is created even while devices are offline.A business has to make the most of every connection, resume interrupted work,and keep track of the data it has not secured yet.

Devices won't always be connected,but data collection never has to stop.

THE TECHNOLOGY BEHIND THIS STORY

Fleet-Scale Collection

Collect the files your business needs from devices running on different network environments.

Even when every device connects at a different time and connections drop mid-collection, keep track of collection targets and progress, and run collection whenever a device becomes available.

Explore the product