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
Connected 840Not connected 1,560
v2.8 delivery result
80.4%
1,930 / 2,400
TUESDAY, 03:15
Connections and deliveries out of hours
| Device | Connected at | Delivery state |
|---|
| Device-0612 | 00:24 | Completed |
| Device-1924 | 01:16 | Completed |
| Device-2216 | 02:47 | Resumed |
| Device-2340 | 03:02 | Completed |
| Device-2382 | 03:12 | Transferring |
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
Devices in operation2,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.
Operating package v2.8 distribution
83.8%
| Device group | Targets | Completed | Not complete |
|---|
| Mobile devices | 1,200 | 1,080 | 120 |
| Field equipment | 800 | 680 | 120 |
| Remote devices | 400 | 250 | 150 |
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
Devices in operation2,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
Connected 1,370Not connected 1,030
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
Devices in operation2,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
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
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
Devices in operation2,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
| Time | Network | Assumed average speed |
|---|
| 09:10 | Mobile network | 2Mbps |
| 12:40 | Site Wi-Fi | 15Mbps |
| 19:20 | Depot wired network | 100Mbps |
Operating package v2.9, 1.5GB
09:10, Mobile80MB / 1,500MB
12:40, Site Wi-Fi650MB / 1,500MB
19:20, Wired1,500MB / 1,500MB
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
Devices in operation2,400
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
Connected 1,120Not connected 1,280
v2.9 delivery result
96.3%
2,310 / 2,400
Devices in operation
2,400
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
Devices in operation2,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 connection | Devices | Company rule |
|---|
| 48 to 72 hours | 28 | Wait for connection |
| 72 to 96 hours | 14 | Check the work schedule |
| 96 hours or more | 6 | Site 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
Devices in operation2,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 →