INNORIX in Practice, Fleet-Scale Distribution

A company running devices installed ten years ago
alongside devices installed yesterday

The devices arrived at different times, but the company’s work carries on today.

Introduced 2016

10 years ago

Legacy devices

Embedded Linux

Limited storage and computing power

1,200

Introduced 2021

5 years ago

Standard devices

Windows, Linux

The main devices of existing work

2,800

Introduced 2026

Yesterday

New generation devices

Android, Linux

New programs and work environments

1,000

November 16, 2026

5,000 different devices
are at work in the same company today.

A fictional operations story about file distribution in a company where generations of devices coexist.

INNORIX in practiceScene 1 / 15

The past ten years2016

The past ten years 2016Scene 1 / 15

The company brought in its first industrial devices.

1,200 industrial devices started work at sites across the country. Their programs and files were built for those devices’ performance and environment.

2016, THE FIRST GENERATION

2016 industrial devices

1,200

Operating system
Embedded Linux
Processor
ARM 32-bit
Memory
512MB
Total storage
4GB
Main work
Basic business tasks
Program
Legacy application

Files delivered to these devices at the time

  • legacy_application.tar.gz180MB
  • business_data.json12MB
  • device_config.json64KB

The company used these devices for years, replacing parts and improving programs to extend their life.

Being old did not mean a device could no longer do any of the work.

AT THIS MOMENTNow

2016

All devices in operation

1,200

2016, Legacy devices

1,200

Embedded Linux

The company’s current workRunning the first devices

Next story, 2021A second generation →

The past ten years 2021Scene 2 / 15

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 devices2021 devices
Memory512MB4~8GB
Storage4GB64~128GB
ProgramLegacyStandard
Package formattar.gzzip, tar.gz
WorkBasicBasic 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.

AT THIS MOMENTNow

2021

All devices in operation

4,000

2016, Legacy devices

1,200

Embedded Linux

2021, Standard devices

2,800

Windows, Linux

The company’s current workRunning two generations

Next story, 2026Three generations together →

The company today 2026Scene 3 / 15

Before long, the company has three generations of devices.

1,000 devices of a new generation arrived. Their operating systems, performance, storage and program versions all differ.

TODAY'S INFRASTRUCTURE

One company, three generations of devices

Introduced 2016

Legacy

1,200

24% of all devices

OS
Embedded Linux
Processor
ARM 32-bit
Memory
512MB
Storage
4GB

Introduced 2021

Standard

2,800

56% of all devices

OS
Windows, Linux
Processor
x86-64
Memory
4~8GB
Storage
64~128GB

Introduced 2026

New generation

1,000

20% of all devices

OS
Android, Linux
Processor
ARM 64-bit
Memory
8~16GB
Storage
256GB

All devices in operation5,000

For the company, running three generations is not just a matter of managing three kinds of hardware.

Even within one generation, devices need different files depending on their OS, program version and location.

But those differences do not mean every kind of device needs its own file distribution environment.

AT THIS MOMENTNow

2026

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 workChecking each device’s environment

Next story, 08:30The same work begins →

The company today 08:30Scene 4 / 15

Different devices start the same morning.

Devices across the country start their own work. The services users get are much the same, but the hardware and programs behind them differ.

MONDAY MORNING, 08:30

The same business data, different user environments

2016 devices

Today’s work

2026.11.16

Task A

Task B

Task C

Basic environment

Uses today’s business data

2021 devices

Today’s work

2026.11.16

Task A

Task B

Task C

Task details

Extended environment

Uses today’s business data

2026 devices

Today’s work

New service content

2026.11.16

Task A

Task B

Task C

New environment

Uses today’s business data

COMMON BUSINESS DATA

business_data_20261116.json12MB

Today’s business data, shared by all three generations.

The service users see can be the same while the programs running on the devices differ.

The company keeps the files everyone uses apart from the files only certain devices need.

AT THIS MOMENTNow

08: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 the day’s business data

Next story, 09:30One task, three kinds of files →

Files per device 09:30Scene 5 / 15

Different files are prepared for the same work.

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

Next story, 10:00Different devices at one site →

10:00Scene 6 / 15

Even one site has different devices.

The company’s devices were not installed in different places by the year they arrived.

Old and new devices work side by side within a single site.

Which device needs which file cannot be decided by the site’s location alone.

DEVICES WITHIN EACH SITE

Sites and device types are different ways to group devices.

Site201620212026Total
Site A1824850
Site B0361450
Site C3218050
Site D4163050
Site E005050

2016 models2021 models2026 models

The operations team tells apart where a device is installed and the environment that will use the files.

To manage a site’s work it looks at devices by region and location; to distribute programs it builds targets by device model and OS.

AT THIS MOMENTNow

10: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 workBuilding datasets per device

Next story, 10:30Different delivery conditions →

Files per device 10:30Scene 7 / 15

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

Next story, 11:00Common and specific files →

Files per device 11:00Scene 8 / 15

Some files are shared by every 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

FileLegacyStandardNew
Common business dataTargetTargetTarget
Common operating policyTargetTargetTarget
Legacy programTarget——
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

Next story, 14:00120 devices from yesterday →

THE NEW ARRIVALS

120 devices installed yesterday.

These devices still need the files to do the company’s work.

By this morning the company had prepared the files its existing generations of devices need.

Now it is the turn of the devices installed yesterday to join the company’s work.

Existing 2026 devices

880

Running in the existing environment

Installed yesterday

120

Preparing the initial environment

All 2026 devices

1,000

Getting the new devices ready to work begins.

INNORIX in practiceScene 1 / 15

The past ten years2016

New devices join 14:00Scene 9 / 15

Yesterday’s devices still need to be made ready for work.

The last 120 of the 1,000 new-generation devices receive their first programs, settings and business data.

New devices installed yesterday120Setting up their first work environment

NEW DEVICE ONBOARDING

The work after the hardware is installed

Yesterday, site installation team

Device installation

Hardware installed
Done
Basic OS setup
Done
Network connected
Done
INNORIX connected
Done

Today, distribution team

Work environment

Business program
Scheduled
Service resources
Scheduled
Device settings
Scheduled
Today’s business data
Scheduled

Initial dataset for new devices

FilePurposeSize
nextgen_application.zipBusiness program1.2GB
service_resources.zipService content3.6GB
device_config.jsonDevice settings64KB
business_data.jsonToday’s business data12MB
Initial delivery per device
About 4.8GB
New devices
120
Total data delivered
About 577GB

The company sets up the first delivery to new devices as a job of its own.

The 880 existing devices already run the same program and do not need the installation files again.

Only the 120 devices installed yesterday are targeted for the first delivery.

AT THIS MOMENTNow

14: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 workFirst file delivery to new devices

Next story, 15:30Files that fit each device →

15:30Scene 10 / 15

New devices receive the files that fit their environment.

Not all 120 new devices run the same OS.

80 run on Android and 40 on Linux.

They share the common service content, but their programs and some settings files differ.

NEW DEVICES, PLATFORM DIFFERENCES

Android

80

Program per platform
application.apk
Settings
android_config.json
Target path
Delivery path for Android

Linux

40

Program per platform
application_linux_arm64.tar.gz
Settings
linux_config.json
Target path
Delivery path for Linux

Shared files

  • service_resources.zip3.6GB
  • business_data.json12MB

For all 120 new devices

The operations team delivers the files Android devices and Linux devices each need.

A different OS does not mean a separate transfer product or a completely separate operating system.

Once the files arrive, the company applies the programs and checks the work following its own installation and service procedures.

AT THIS MOMENTNow

15: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 workFirst file delivery to new devices

Next story, 17:00Joining daily operations →

New devices join 17:00Scene 11 / 15

New devices join the company’s everyday distribution.

The first file delivery and a separate service check are complete. The new devices join the existing device group and the scheduled targets.

New devices installed yesterday120First files delivered and service checked

17:00, READY FOR DAILY OPERATIONS

New devices join the existing operations.

Before onboarding

4,880

Devices in daily work

Legacy
1,200
Standard
2,800
New generation
880
Being prepared
120

After onboarding

5,000

Devices in daily work

Legacy
1,200
Standard
2,800
New generation
1,000
Being prepared
0

Existing distribution the new devices join

FlowBeforeAfter
Daily business data4,8805,000
Common business policy4,8805,000
New generation resources8801,000
Legacy application1,2001,200
Standard application2,8002,800

Adding new devices does not mean rebuilding the distribution of the existing ones from scratch.

New devices join the right device group and scheduled targets, and the delivery conditions are checked.

From tomorrow, the new devices receive their everyday work files along with the existing ones.

AT THIS MOMENTNow

17: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 workJoining the scheduled targets

Next story, 23:00Night distribution, three generations →

End of the day 23:00Scene 12 / 15

A night when every device receives different files.

Distribution set up per generation and operating system runs on its own schedule. The company checks the results in one operating environment.

TONIGHT'S DISTRIBUTION SCHEDULE

Different distribution schedules run by one company

These are the windows set for each device group’s distribution, not actual transfer times or a promise that they all finish together.

DistributionTargetsWindow
New generation package1,00020:00~23:00
Standard package2,80023:00~05:00
Legacy package1,20002:00~04:00
Common business data5,00005:00~06:00

The company does not run every device under the same conditions as the newest.

Ten-year-old devices get the workload and hours they can handle, and new devices are run so they can use larger files.

AT THIS MOMENTNow

23: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 the night distribution

Next story, Next day 06:30Checking the results →

Next day 06:30Scene 13 / 15

Devices differ in age, but their results are checked the same way.

Before work the next day.

The operations team checks the results of last night’s distribution.

The small files sent to old devices and the large content sent to the newest are checked in the same environment.

THE NEXT MORNING, 06:30

Distribution results by device

RunsNight distribution

FlowTargetsDoneResult
Legacy package1,2001,1964 to check
Standard package2,8002,800Completed
New generation package1,0001,000Completed
Common business data5,0005,000Completed

Checking 4 Legacy devices

Not enough storage
3
Waiting for connection
1

Transfers to the unfinished devices continue once storage is freed and the connection is back.

The team found 4 of the 2016 devices needed a closer look.

It does not restart the work for all 5,000 devices; it checks only the ones that need it.

At 7:20 a.m., delivery to the 4 unfinished devices completes too.

Old and new devices alike received the files they need.

Applying the programs and starting work then follow the company’s own procedures.

AT THIS MOMENTNow

Next day 06: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 workChecking the night distribution

Next story, One year laterReplacing the oldest devices →

ONE YEAR LATER

The company’s devices begin to change again.

Devices do not last forever. The company decided to replace its longest-serving devices, a few at a time.

2026

5,000

2016 Legacy1,200

2021 Standard2,800

2026 New1,000

2027

5,000

2016 Legacy600

2021 Standard2,800

2026~2027 New1,600

600 devices are replaced.

But the company’s work carries on as before.

INNORIX in practiceScene 1 / 15

The past ten years2016

The company changes One year laterScene 14 / 15

Some of the devices that served ten years retire.

600 old devices are replaced with new ones. Existing devices that can still run stay, and devices are replaced in order of need.

GRADUAL DEVICE REPLACEMENT

The company’s replacement plan

Legacy devicesStandard devicesNew generation devices

PeriodReplacedLegacy leftAll devices
Q11501,0505,000
Q21509005,000
Q31507505,000
Q41506005,000

The company does not build a new file transfer environment at each site where devices are replaced.

When an old device retires it leaves the scheduled targets; when a new one is installed it receives its first files and joins the right targets.

The 600 old devices not yet replaced keep receiving the files they need, as before.

New devices arriving does not stop the company from distributing programs for the existing ones.

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

Next story, Three years laterAnother generation arrives →

The day one site replaces its devices

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

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.

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

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.

See the product