INNORIX in Practice, Fleet-Scale Distribution

A company that never knows when or where its devices will connect

2,400 devices that join the network from different places, at different times.

Monday

08:30

Devices in operation

2,400

Devices on the road1,200

Devices at industrial sites800

Devices in remote areas400

  • Connected
  • Not connected

Connected now

1,260

Waiting for the next connection

1,140

Files have to reach the devices that are not connected right now, too.

A fictional story of a company whose devices connect unpredictably. Each mark stands for 20 devices; connection states are approximate.

INNORIX in practiceScene 1 / 14

Monday — MondayWhere do this company’s devices work?

Scene 1 / 14

Where do this company’s devices work?

The company runs 2,400 devices that work in many different places across the country.

Its devices do not stay in one place, and each works in a different environment.

Some change their connection state while they move; some can use a network only after their work is done.

Some work for days where no outside network can be reached.

THE OPERATING ENVIRONMENT

Mobile devices

1,200

Devices on the move

Vehicles and mobile work devices. Their connection changes with the route and the coverage.

Field equipment

800

Devices at industrial sites

Devices whose outside network is restricted or unstable while they work.

Remote devices

400

Devices in remote areas

Devices with no lasting network, whose next connection is hard to predict.

What they have in common

No device can be assumed to stay online. Nor can every device be expected to be connected at the same time.

The company’s problem is not simply that its network is unstable.

It is that the time a device connects cannot be fitted to the company’s schedule.

The way files are distributed has to take that into account.

AT THIS MOMENTNow

Monday08:30

Devices in operation

2,400

Connected now1,260
Not connected now1,140
Target file versionv2.8
Files delivered0
Not delivered yet2,400
Next story, Monday, 08:30Not every device is connected. →

Monday 08:30Scene 2 / 14

New files are ready.

But 1,140 devices are not connected.

The development team has prepared a new program and business data for every device.

The company wants them on every device as soon as possible.

But only 1,260 of the 2,400 devices are connected right now.

New files are ready for 2,400 devices.

Network connections now

v2.8 delivery result

0.0%

0 / 2,400

MONDAY, 08:30

Operating package v2.8

Distribution files for all devices

1.2GB

FileSize
application_package.zip800MB
operating_data.zip350MB
device_configuration.zip50MB

Device connections now

Device groupTotalConnectedNot connected
Mobile devices1,200730470
Field equipment800350450
Remote devices400180220
Total2,4001,2601,140

The operations team knows it cannot wait until every device is connected.

A device connected in the morning may well be offline in the afternoon.

Nor does it work to target only the devices connected right now.

Then the distribution would have to be run again for every device that connects later.

AT THIS MOMENTNow

Monday08:30

Devices in operation

2,400

Connected now1,260
Not connected now1,140
Target file versionv2.8
Files delivered0
Not delivered yet2,400
Next story, Monday, 09:00Files go to connected devices first. →

Monday 09:00Scene 3 / 14

The distribution starts for every device.

Now for devices that are connected; when they connect, for those that are not.

The team does not choose the targets by who is connected right now.

It makes all 2,400 devices that need the files the distribution’s target.

Devices that can connect now are sent the files first; the rest receive them later, under the retry conditions and distribution policy that were set.

Some devices are offline, but the distribution starts for every device.

Network connections now

v2.8 delivery result

0.0%

0 / 2,400

INNORIX Studio

Flows

Operating package v2.8 distribution

Source
Central file server
Dataset
Operating package v2.8, 1.2GB
Target
All operating devices, 2,400 devices
Start
Monday 09:00
Unavailable devices
Retry when they can connect
Interrupted transfers
Resume from where they stopped
Completed devices
Never sent again
Distribution period
Set by the operations team

Devices that can receive now

1,260

Transfers start in turn as resources allow

Devices not connected now

1,140

Sent at their next connection, by the retry policy

What the team manages is not a list of devices that are online; it is the list of devices that need the files.

The goal, the same files on every device, stays; each device simply receives them at a different time, as its connection allows.

AT THIS MOMENTNow

Monday09:00

Devices in operation

2,400

Connected now1,260
Not connected now1,140
Target file versionv2.8
Files delivered0
Not delivered yet2,400
Next story, Monday, 14:20Devices connected for minutes →

Monday 14:20Scene 4 / 14

Some devices connect for only a few minutes.

Being connected does not mean the whole file can be delivered.

One of the company’s mobile devices connected to a network at 2:20 pm.

It can use the network briefly before it moves on to its next job.

The files it needs come to 1.2GB.

But the connection drops again after 7 minutes 24 seconds.

Files keep arriving while connections keep changing.

Network connections now

v2.8 delivery result

61.7%

1,480 / 2,400

MONDAY, DEVICE-0418

Device-0418

Mobile work device

Files to deliver

1.2GB

Network connection

  1. Connected
  2. Offline
  3. Connected
  4. Offline
  5. Connected

Delivered so far

A conceptual graph of the connection windows. The time between them is not drawn to scale.

TimeDevice stateDelivered
14:20Connected, transfer starts0MB
14:27:24Connection ends420MB
16:30Connected again elsewhere420MB
16:36Connection ends810MB
19:12Connected again, transfer resumes810MB
19:17Files delivered1,200MB

Result

One package delivered over three connections.

A scenario in which the parts already sent are kept and the rest follows on later connections.

The device connected again at 4:30 pm, somewhere else.

It was a different network from the first one.

Instead of resending the files from the beginning at each connection, the company carries on from the transfer state left on the device.

At 7:17 pm the device had every file it needed.

Its place and network changed several times; the files the company meant to deliver did not.

AT THIS MOMENTNow

Monday14:20

Devices in operation

2,400

Connected now910
Not connected now1,490
Target file versionv2.8
Files delivered1,480
Not delivered yet920
Next story, Monday, 18:00The number of offline devices keeps changing. →

INTERACTIVE EXPERIENCE

What if a device connects for a different time every time?

Change the connection times and the network speed, and compare sending the file from the beginning each time with resuming from where it stopped.

INTERMITTENT CONNECTIVITY

The device’s network

File size to deliver

Three network connections

From the beginning every time

Connection 1525MB

Connection 2450MB

Connection 3375MB

Complete file delivered

0%

The parts sent in each connection never add up to a complete file.

Resume from where it stopped

Connection 1525MB

Connection 2975MB

Connection 31,200MB

Delivered of the whole file

100.0%

The data from each connection was joined into the whole file.

A simple model that assumes a constant effective speed while connected. It leaves out authentication, connection setup, retransmission, file verification and other real transfer overhead.

INNORIX in practiceScene 1 / 14

Monday — MondayWhere do this company’s devices work?

Monday 18:00Scene 5 / 14

The number of offline devices keeps changing.

But the number of devices that have the files keeps growing.

The team checks the results of the distribution that started this morning.

Some devices connected this morning got the files and have gone offline again.

Some that were offline this morning connected in the afternoon and got the files.

What the company needs to know is not simply how many devices are connected.

It is how many devices have the files they need.

MONDAY, CONNECTION AND DELIVERY

Two different operating states

  • Connected now
  • Devices with the files

The number of connected devices goes up and down; the number that have received the same files only adds up.

At 6 pm

Connected now

780

32.5% of all devices connected

Files delivered

1,740

72.5% of all devices delivered

Delivery stateConnectedNot connectedTotal
Delivered6101,1301,740
Not yet complete170490660
Total7801,6202,400

Of the 1,620 devices offline now, 1,130 already have the files they need.

Being offline is no reason to send them the files again.

Of the 780 connected now, 170 are still waiting for their files to finish.

This is why whether a device is connected and whether its files are delivered are managed apart.

AT THIS MOMENTNow

Monday18:00

Devices in operation

2,400

Connected now780
Not connected now1,620
Target file versionv2.8
Files delivered1,740
Not delivered yet660
Next story, Tuesday, 03:15Devices that connect while the team sleeps →

AFTER OFFICE HOURS

The team’s day is over.
The devices’ day is not.

Monday 18:00

1,740

Files delivered

Tuesday 03:15

1,930

Files delivered

While no one was at work,
190 more devices received the files they needed.

INNORIX in practiceScene 1 / 14

Monday — MondayWhere do this company’s devices work?

Tuesday 03:15Scene 6 / 14

Devices do not know office hours.

Some connect for the first time before dawn.

Some devices working in remote areas have reached a place with an outside network.

The company’s operations team is not at work.

But when a device connects has nothing to do with anyone’s working hours.

Devices connect again before dawn, outside working hours.

Network connections now

v2.8 delivery result

80.4%

1,930 / 2,400

TUESDAY, 03:15

Connections and deliveries out of hours

DeviceConnected atDelivery state
Device-061200:24Completed
Device-192401:16Completed
Device-221602:47Resumed
Device-234003:02Completed
Device-238203:12Transferring

Since the last check

Newly delivered

190

Delivered in total

1,930

The company cannot ask devices to stay connected until someone comes in to work.

A retry policy set up in advance acts on each device that connects again, and the files it needs are sent while it is connected.

Here, setting how long a distribution stays open and when it retries matters more than choosing one time to send.

AT THIS MOMENTNow

Tuesday03:15

Devices in operation

2,400

Connected now840
Not connected now1,560
Target file versionv2.8
Files delivered1,930
Not delivered yet470
Next story, Tuesday, 09:00Nobody re-selects yesterday’s offline devices. →

Tuesday 09:00Scene 7 / 14

Nobody re-selects the devices that were offline yesterday.

After coming in, the team checks last night’s results.

Devices that already have the files are marked complete.

For those that do not, the team checks their connection state and transfer history to judge whether anything more needs doing.

INNORIX Studio

Runs

Operating package v2.8 distribution

83.8%

Targets

2,400

Completed

2,010

Transferring

125

Waiting to connect

265

Device groupTargetsCompletedNot complete
Mobile devices1,2001,080120
Field equipment800680120
Remote devices400250150

Each device’s connection history and delivery state can be checked.

A device that has not received its files yet is not taken to have a problem.

Some cannot connect because of scheduled work; some can connect but not for long enough to finish.

The team responds with each device’s real working conditions in mind.

AT THIS MOMENTNow

Tuesday09:00

Devices in operation

2,400

Target file versionv2.8
Files delivered2,010
Not delivered yet390
Next story, Wednesday, 11:00A new version is ready. →

Wednesday 11:00Scene 8 / 14

A new file is ready before the previous one has finished.

Which file should go to devices that have been offline for days?

On Wednesday morning the development team prepared v2.9, a package with new business data and a new program.

But the v2.8 distribution started on Monday has not finished on every device.

Some devices still run v2.7, and some have not started receiving v2.8.

The latest file’s distribution is prepared apart from the previous results.

Network connections now

v2.9 delivery result

0.0%

0 / 2,400

WEDNESDAY, 11:00

Different delivery states

v2.8 not started

140

Last delivered: v2.7

v2.8 partly sent

80

File not complete yet

v2.8 delivered

2,180

Target for the new file

A conceptual picture of the number of devices.

Newly prepared file

Operating package v2.9

Complete package, no dependency on earlier versions

1.5GB

The development team confirmed that v2.9 is a complete package that does not need the earlier files.

So the company decides that devices without v2.8 do not need both the old and the new files.

Had the program needed a certain version installed first, a different order would have been needed.

This time the policy is changed to deliver only the new complete package.

AT THIS MOMENTNow

Wednesday11:00

Devices in operation

2,400

Connected now1,370
Not connected now1,030
Target file versionv2.9
Files delivered0
Not delivered yet2,400
Next story, Wednesday, 11:00Run it by what the file is for. →

Wednesday 11:00Scene 9 / 14

Run it by what the file is for, not by the device.

CHANGING THE DISTRIBUTION POLICY

Delivering every earlier file in order

A device on v2.7

Operating package v2.8

1.2GB

Operating package v2.9

1.5GB

Total to transfer

2.7GB

Delivering only the new complete package

A device on v2.7

Operating package v2.8

Removed from the earlier distribution

Operating package v2.9

1.5GB

Total to transfer

1.5GB

The team’s decision

For devices the earlier distribution did not finish, stop sending the old file and make them targets of the new complete package.

Where a transfer is already running, check the policy for file conflicts and partial files first.

Calculated for devices that have not started v2.8. Not all software can skip an earlier version.

For devices with little time on a network, sending a file they do not need is a cost in itself.

The company rebuilds the distribution around the conditions in which the file can be used and the final file each device needs.

AT THIS MOMENTNow

Wednesday11:00

Devices in operation

2,400

Connected now1,370
Not connected now1,030
Target file versionv2.9
Files delivered0
Not delivered yet2,400
Next story, Thursday, 15:00The network keeps changing too. →

Thursday 15:00Scene 10 / 14

The network a device connects through keeps changing too.

The same device uses different networks.

The company’s mobile devices move between several places in a day.

In one place they use a mobile network; in another they join the site’s Wi-Fi.

After work they may use the wired network at the depot.

The kind of network a device uses, and its speed, keep changing even within one day.

THURSDAY, DEVICE-0826

Three networks used by one device

TimeNetworkAssumed average speed
09:10Mobile network2Mbps
12:40Site Wi-Fi15Mbps
19:20Depot wired network100Mbps

Operating package v2.9, 1.5GB

09:10, Mobile80MB / 1,500MB

12:40, Site Wi-Fi650MB / 1,500MB

19:20, Wired1,500MB / 1,500MB

Networks used

3

Files delivered

1.5GB

The company does not ask devices to stay on one network.

Wherever the needed route and authentication hold, files are delivered as the device’s connection allows.

However the network changes, what matters is keeping one delivery state for each device.

AT THIS MOMENTNow

Thursday15:00

Devices in operation

2,400

Target file versionv2.9
Next story, Friday, 18:00Devices offline for days →

Friday 18:00Scene 11 / 14

90 devices still do not have the latest file.

A device that does not connect is not the same as one that connects with a problem.

It is Friday afternoon.

2,310 of the 2,400 devices have received the new v2.9 package.

90 devices do not have the whole file yet.

The team does not treat them all as simply incomplete.

Devices without the latest file are followed up continuously.

Network connections now

v2.9 delivery result

96.3%

2,310 / 2,400

FRIDAY, 18:00

Devices in operation

2,400

v2.9 delivered

2,310

Not yet complete

90

Overall delivery rate 96.25%

Why the rest are not complete

No connection since the new distribution48

Waiting for the device’s next connection.

Partly sent, connection too short25

The rest follows on the next connection.

Delivering files now10

Checking the transfer result.

Storage space needed5

Checking the device’s storage.

Authentication or connection settings to check2

The team and the site staff check further.

There is no need to send someone out to all 90 devices.

Most have simply not reached a network yet or have not had enough time to finish.

Only 7 actually need action, for storage space or authentication settings.

The team separates the devices to wait for from the devices to act on.

AT THIS MOMENTNow

Friday18:00

Devices in operation

2,400

Connected now1,120
Not connected now1,280
Target file versionv2.9
Files delivered2,310
Not delivered yet90
Next story, Friday, 18:00When devices stay offline longer →

Friday 18:00Scene 12 / 14

The longer a device stays offline, the more the company’s response changes.

LAST CONNECTION REVIEW

Devices with no recent connection

Since last connectionDevicesCompany rule
48 to 72 hours28Wait for connection
72 to 96 hours14Check the work schedule
96 hours or more6Site staff check if needed

Device-2387

Remote work device

Last connection

Monday 02:10

Field work schedule

Working until late Sunday in an area with no outside network.

For an office device, days without a connection might be a problem.

For some of this company’s devices it is simply how they work.

The team judges how long a device has been offline against its real working conditions.

AT THIS MOMENTNow

Friday18:00

Devices in operation

2,400

Connected now1,120
Not connected now1,280
Target file versionv2.9
Files delivered2,310
Not delivered yet90
Next story, Sunday, 23:40Connected again after 6 days →

THE WEEKEND

The offices are empty,
but the devices are still moving.

Friday

2,310

Files delivered

Saturday

2,356

Files delivered

Sunday

2,380

Files delivered

Every time a device connects again,
one more device has the files it needs.

INNORIX in practiceScene 1 / 14

Monday — MondayWhere do this company’s devices work?

Sunday 23:40Scene 13 / 14

A device offline for days is back.

Device-2387 has connected again.

A device that had not reached an outside network since early Monday has finished its work and come back.

It connected again at 11:40 pm on Sunday.

Meanwhile the company had prepared two new packages.

The file it needs now is v2.9, the one most recently chosen for distribution.

A device offline for a long time connects again and receives the files it needs.

Network connections now

v2.9 delivery result

99.2%

2,380 / 2,400

SUNDAY, 23:40

Device-2387

Remote work device

Connected

Connections over the past week

6 days 21 hours 30 minutes since the last connection

Last delivered file
Operating package v2.7
Current target file
Operating package v2.9
Earlier v2.8 distribution
Excluded by the operating policy
Size to deliver
1.5GB
New distribution
Transfer started

Delivery log

23:40

Device connection confirmed

0%
23:41

v2.9 transfer started

0%
23:46

Delivering

62%
23:49

Files delivered

100%

The device had not reached a network for more than 6 days.

Yet no one had to create a new distribution to get the new file to it.

It received the file it needs under the targets and retry policy already decided.

At 11:49 pm on Sunday the delivery was complete.

Applying the program and getting ready for work is up to the company’s own device systems.

AT THIS MOMENTNow

Sunday23:40

Devices in operation

2,400

Connected now660
Not connected now1,740
Target file versionv2.9
Files delivered2,380
Not delivered yet20
Next story, Next Monday, 08:30The company’s week begins again →

Next Monday 08:30Scene 14 / 14

A new week begins.

Every device was never connected at once, yet almost every device has the files it needs.

The team checks the past week’s distribution results.

There was never a moment in the week when all 2,400 devices were connected at once.

Each connected at a different time, and for a different length of time.

Even so, the latest files kept going out to every device.

The results of the past distribution are checked, whatever the devices’ connection state.

Network connections now

v2.9 delivery result

99.9%

2,398 / 2,400

MONDAY, THE WEEKLY REVIEW

Operating file v2.9 results

Devices in operation

2,400

Files delivered

2,398

Not yet complete

2

Latest file delivery rate 99.92%

Device groupTotalCompletedNot complete
Mobile devices1,2001,2000
Field equipment8007991
Remote devices4003991

Devices to check today

Device-1832

Field equipment

Storage space needed

Device-2396

Remote work device

No connection for a long time

The company keeps following up the two devices that are not complete.

For the one that needs storage space it asks the site to act; for the one still offline it checks the work schedule and when it can connect.

Files are never assumed to have reached every device.

What the company can check is the real delivery result of each device.

AT THIS MOMENTNow

Next Monday08:30

Devices in operation

2,400

Connected now1,290
Not connected now1,110
Target file versionv2.9
Files delivered2,398
Not delivered yet2

What happened at the company this week

ONE WEEK OF DISTRIBUTION

Connections were irregular; the distribution carried on.

  • Connected at each point
  • v2.8 delivered
  • v2.9 delivered

The v2.8 distribution is set to stop sending to unfinished targets on Wednesday. The earlier record and the new results are kept apart.

WhenWhat happened
Monday morningv2.8 distribution to every device starts
Monday afternoonFiles delivered over short connections
Tuesday before dawnDistribution carries on while no one is at work
WednesdaySwitch to distributing the new v2.9
ThursdayTransfers over each device’s changing networks
FridayDevices to wait for and devices to act on separated
WeekendTransfers to devices offline for a long time
Next MondayLatest delivery results and remaining devices checked

What the company set was never a time when every device had to receive the files at once.

It was which files go to which devices, and under what conditions.

However differently each device connects, that purpose holds.

BEYOND ALWAYS-ON ENVIRONMENTS

Devices do not have to be connected
all the time to be run.

Next Monday, 08:30

Devices on a network now

1,290

53.75%

Devices with the latest files

2,398

99.92%

2 of 2,400 devices not complete

Devices are in different places,
and connect at different times.

A company’s file distribution has to keep going in step with how its devices actually work.

INNORIX

The technology behind this story

Fleet-Scale Distribution

From mobile devices to equipment at industrial sites and in remote areas: deliver the files devices need wherever and whenever they connect, and keep track of the results.

View the product