The new devices did not take over the old ones’ work.
As the business grew, the company brought in 2,800 new devices. The existing ones could still do their work, so it began running two generations side by side.
2021, THE SECOND GENERATION
Existing devices
1,200
2016 Legacy
Embedded Linux, ARM 32-bit
Keep doing the existing work.
Newly introduced
2,800
2021 Standard
Windows, Linux, x86-64
Use the extended work and new programs.
The company’s devices in 2021
2016 devices
2021 devices
Memory
512MB
4~8GB
Storage
4GB
64~128GB
Program
Legacy
Standard
Package format
tar.gz
zip, tar.gz
Work
Basic
Basic and extended
Devices running together
4,000
From then on, the company had devices doing the same work with different programs and files.
Because each site had different devices, distributing files site by site was no longer enough.
The development team prepares a new business feature: a lightweight package for old devices, a standard package for existing ones, and high-resolution resources and programs for new ones.
FILES PREPARED BY THE DEVELOPMENT TEAM
One business change, three distribution packages
2016 devices, 1,200
Legacy package180MB
legacy_v3.8.tar.gz
ARM 32-bit, lightweight program
2021 devices, 2,800
Standard package1.2GB
standard_v6.2.zip
x86-64, existing and extended work
2026 devices, 1,000
New generation package4.8GB
nextgen_v2.1.zip
ARM 64-bit, new features and content
The development team prepared each package for its devices’ runtime environment.
What is needed is not to deliver the newest program to every device.
It is to deliver exactly the files each device can actually use.
Older devices receive a program they can run, and the newest receive files built to use their performance and features.
AT THIS MOMENTNow
09:30
All devices in operation
5,000
2016, Legacy devices
1,200
Embedded Linux
2021, Standard devices
2,800
Windows, Linux
2026, New generation
1,000
Android, Linux
The company’s current workBuilding datasets per device
Not every device needs its files delivered the same way.
The team sets apart the conditions of devices short of storage, devices that cannot receive files during work, and devices that use large resources.
DEVICE-SPECIFIC DISTRIBUTION
2016 LegacyEmbedded Linux, ARM 32-bit1,200
Storage of a typical device
0.6GB
Total 4GB
3.4GB in useFree
File to deliver
legacy_v3.8.tar.gz
File size
180MB
Scheduled window
02:00~04:00
Conditions
After work hours, limited concurrent transfers
Room for both the current program and the delivered file is considered. Devices short of space are found from their actual free capacity and handled separately.
2021 StandardWindows, Linux, x86-642,800
Storage of a typical device
22GB
Total 64GB
42GB in useFree
File to deliver
standard_v6.2.zip
File size
1.2GB
Scheduled window
23:00~05:00
Conditions
By each site’s end of work
Files for Windows and Linux are told apart too: even within one generation, targets follow the operating system and install path.
2026 New generationAndroid, Linux, ARM 64-bit1,000
Storage of a typical device
184GB
Total 256GB
72GB in useFree
File to deliver
nextgen_v2.1.zip
File size
4.8GB
Scheduled window
20:00~23:00
Conditions
Delivered ahead, during operation
Large content arrives before the time it is applied. File delivery and the actual program installation run on separate schedules.
Storage figures assume a typical device of each generation.
Doing the same work tomorrow does not mean every device must receive its files at the same time tonight.
The team sets up a suitable delivery environment for each device so the files are ready before work starts.
AT THIS MOMENTNow
10:30
All devices in operation
5,000
2016, Legacy devices
1,200
Embedded Linux
2021, Standard devices
2,800
Windows, Linux
2026, New generation
1,000
Android, Linux
The company’s current workPreparing delivery conditions per device
Common business data goes to every device. Programs and environment-specific resources are set up so each can be delivered to fit the operating system and device model.
COMMON AND DEVICE-SPECIFIC DATASETS
Common business dataset5,000
Common files every device uses
business_data.json12MB
business_policy.json96KB
Legacy dataset
1,200
legacy_v3.8.tar.gz
180MB
legacy_config.json
Settings per device
Standard dataset
2,800
standard_v6.2.zip
1.2GB
standard_config.json
Settings per device
New generation dataset
1,000
nextgen_v2.1.zip
4.8GB
nextgen_config.json
Settings per device
Targets per file
File
Legacy
Standard
New
Common business data
Target
Target
Target
Common operating policy
Target
Target
Target
Legacy program
Target
—
—
Standard program
—
Target
—
New program
—
—
Target
When a file a device needs changes, the team checks that dataset and its targets.
When the common business data changes, every device receives the right file; when only one generation’s program changes, only the files those devices need are delivered.
AT THIS MOMENTNow
11:00
All devices in operation
5,000
2016, Legacy devices
1,200
Embedded Linux
2021, Standard devices
2,800
Windows, Linux
2026, New generation
1,000
Android, Linux
The company’s current workRunning common and specific distribution
One site in the country decided to replace 20 old devices today.
It has 20 devices installed in 2016 and 30 installed in 2021.
The 30 devices from 2021 keep working; only the 20 from 2016 are replaced with new ones.
SITE 042, DEVICE REPLACEMENT DAY
08:00
Before
Devices able to work
50 / 50
Legacy
Standard
New generation
08:0010:0012:0014:0017:00
50 existing devices are running. The 20 Legacy devices to replace today are checked.
Scheduled targets during the replacement
Legacy application
20
Standard application
30
New generation application
0
For the company, replacing a device does not end with the hardware.
It delivers the programs and business data the new devices need and changes the device makeup of the existing targets.
The 30 devices not part of today’s work keep their existing distribution policy.
AT THIS MOMENTNow
One year later
All devices in operation
5,000
2016, Legacy devices
600
Embedded Linux
2021, Standard devices
2,800
Windows, Linux
2026, New generation
1,600
Android, Linux
The company’s current workGradual device replacement
The company changes Three years laterScene 15 / 15
The company will keep running different devices.
The 2016 devices have all been replaced. The 2021 devices are still at work, and another generation of devices joins the company.
THE EVOLUTION OF THE FLEET
The company’s devices keep changing.
2016
2021
2026
2027
2029
2029
All devices in operation
5,000
2016 Legacy0
2021 Standard2,800
2026~2027 New generation1,600
2029 Next generation600
Devices introduced and replaced over time
1,200
2016
4,000
2021
5,000
2026
5,000
2027
5,000
2029
The company will never run every device on the same OS and hardware.
While new technology arrives and new devices come in, the existing devices keep doing the company’s work.
What it needs is not a distribution environment that suits one generation, but one it can keep using across the environments of different devices.
AT THIS MOMENTNow
Three years later
All devices in operation
5,000
2021, Standard devices
2,800
Windows, Linux
2026, New generation
1,600
Android, Linux
2029, Next generation
600
A new operating environment
The company’s current workRunning devices for the long term
DIFFERENT GENERATIONS. SHARED OPERATIONS.
Devices made in different eras do not need separate operations.
Long-serving devices and devices installed yesterday each receive the files their environment needs.
2016
Long-serving devices
Keep receiving the files they need.
2021
The core of today’s work
Keep doing the existing work.
2026
Newly introduced devices
Join the company’s operations.
Devices change, the business carries on.
Whatever devices it brought in, and whenever, the company keeps delivering the files each device needs.
INNORIX
The technology behind this story
Fleet-Scale Distribution
INNORIX’s large-scale file distribution platform: it connects devices across operating systems and hardware, and builds and delivers the files each one needs.