Launch preparation D-30Scene 1 / 14
In a month, a new service starts nationwide.
The company has set the launch date of the new service it spent a year preparing.
6,000 devices running at 240 sites across the country are due to offer the new service.
D-DAY
09:00
Nationwide simultaneous launch
MonTueWedThuFriSatSun123456789101112131415161718192021222324252627282930
Planned launch date
| Team | Launch task |
|---|
| Service planning | Set the launch date and operating policy |
| Development | Prepare the programs and service resources |
| Distribution | Deliver the files every device needs |
| Field operations | Check device environments and validate |
| Service operations | Apply and start the service |
The service development team prepares the programs and resources; the distribution team plans how to deliver them to every device in the country.
A service being developed and a service being able to start nationwide are two different things.
The launch date is set. Now the devices across the country have to be ready.
AT THIS MOMENTNow
Until launch
30 days
Launch, D-DAY 09:00
Current distribution
Launch planning
- Target devices6,000
- Files delivered0
Launch readiness
- Field validationPlanned
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Prepare a real field validation environment
Next story, D-21Device environments checked →Launch preparation D-21Scene 2 / 14
Not all 6,000 devices share one environment.
Over the years the company has brought in many kinds of devices at different times.
Operating systems, program environments and each site’s network are checked, and the service files are sorted accordingly.
Devices receiving the new service
Model C
Embedded Linux
1,200
Common service resources
Content and data every device uses
Files for all 6,000 devices
24GB
File environment kept on each device
Current service
/service/current/
Existing service keeps running
New service
/service/next/
Files prepared before launch
The common resources every device needs and the program files of each model are set up separately.
So the existing service is not affected, the distribution team decides to deliver the new service’s files to a separate path.
One service nationwide, but the files to prepare differ from device to device.
AT THIS MOMENTNow
D-21
Devices and file layout
Until launch
21 days
Launch, D-DAY 09:00
Current distribution
Devices and file layout
- Target devices6,000
- Files delivered0
Launch readiness
- Field validationPlanned
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Pre-validation at 6 sites
Next story, D-14First distribution to 150 devices →Field validation D-14Scene 3 / 14
Try it in the field before distributing nationwide.
The company has chosen 6 sites with different operating environments.
The new service files go to 150 of the 6,000 devices.
Field validation target
150
6 sites chosen out of 240
| Validation site | Environment | Devices |
|---|
| Site A | High-speed network | 25 |
| Site B | Standard network | 25 |
| Site C | Restricted network | 25 |
| Site D | Mostly older devices | 25 |
| Site E | Mostly new devices | 25 |
| Site F | Mixed devices | 25 |
Distribution team, 14:30
The new service files reached 150 devices at 6 sites.
Service validation team, 15:00
We will start validating the new service on the real devices.
Site staff and the development team run the programs on real devices and validate the service environment.
Validation shows that one model’s configuration file has to be changed.
Before distributing nationwide, check it in the real operating environment first.
AT THIS MOMENTNow
Until launch
14 days
Launch, D-DAY 09:00
Current distribution
Field validation
- Target devices150
- Files delivered150
Launch readiness
- Field validationPlanned
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Prepare the fixed file
Next story, D-12A problem found in the field →Field validation D-12Scene 4 / 14
Not every file had to be sent again.
The development team analysed the problem found during validation.
Only the configuration file of the affected Model B devices needs fixing. The large common resources and the other models’ program files have not changed.
Field validation team10:20
Some service screens on Model B devices do not pick up their settings. Please check the configuration file of those devices.
Development team11:45
We found the cause and fixed the configuration file. The programs and common resources do not need to be sent again.
Changed files
| File | Size | Change |
|---|
| service_resources.zip | 24GB | Unchanged |
| model_b_application.zip | 3.6GB | Unchanged |
| model_b_config_v1.1.json | 128KB | Modified |
All validation devices
150
Fixed file delivered and revalidated
The fixed configuration file goes to the 30 validation devices of that model.
Validation is run again, and the nationwide distribution can now be prepared.
Changed files go again only to the devices that need them.
AT THIS MOMENTNow
D-12
Fixed file validation
Until launch
12 days
Launch, D-DAY 09:00
Current distribution
Fixed file validation
- Target devices30
- Files delivered30
Launch readiness
- Field validationDone
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Approve nationwide distribution
Next story, D-7Large resources sent early →Nationwide preparation D-7Scene 5 / 14
There is no need to wait for every file until the day before launch.
The new service needs 24GB of common resources on each device.
Instead of sending every file just before launch, the company starts distributing the large resources that will not change a week ahead.
Files for the nationwide launch
Files that can go out before launch day
Common service resources
24GB, all devices
From D-7Content and service data
Model program files
2.8~4.2GB, by model
From D-5Final configuration and content changes
About 80MB, final version
On D-1A rough picture to show the difference in file sizes.
D-7D-6D-5D-4D-3D-2D-1D-Day
09:00 service starts
Depending on each site’s network and devices, direct, regional and grid distribution are used.
The files wait in the new service’s path while the existing service keeps running.
The launch date and the date files are delivered do not have to be the same.
AT THIS MOMENTNow
D-7
Common resource pre-distribution
Until launch
7 days
Launch, D-DAY 09:00
Current distribution
Common resource pre-distribution
- Target devices6,000
- Files delivered4,200
Launch readiness
- Field validationDone
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Prepare programs and final files
Next story, D-5Every site distributes differently →Nationwide preparation D-5Scene 6 / 14
Every site distributes differently.
Not every site has the same network.
Some sites can take large files straight from headquarters. Other regions can use a regional server, and some sites have devices suited to grid distribution.
Common service resource distribution
The same files, delivered different ways.
Direct distribution
Sites that receive files straight from headquarters
80 sites, 2,000 devices
Source server
Delivered directly
Regional distribution
Files go to a regional hub, then to each site’s devices
100 sites, 2,500 devices
Grid distribution
A distributed environment spreads the load of a large distribution
60 sites, 1,500 devices
Nationwide target
240 sites, 6,000 devices
The way files arrive differs by region, but the service and launch date the company must prepare are the same.
The distribution team uses the method that suits each environment and checks the overall result.
AT THIS MOMENTNow
D-5
Common resource pre-distribution
Until launch
5 days
Launch, D-DAY 09:00
Current distribution
Common resource pre-distribution
- Target devices6,000
- Files delivered5,400
Launch readiness
- Field validationDone
- Common resources deliveredPlanned
- Final files deliveredPlanned
- Service startPlanned
Next
Prepare programs and final files
Next story, D-3Pre-distribution complete →Nationwide preparation D-3Scene 7 / 14
144TB of data is already on the devices nationwide.
The common resources have reached all 6,000 devices.
The logical volume of common resources delivered across all devices is 144TB.
3 days before launch
Common service resources delivered nationwide
Files delivered
6,000 / 6,000
Delivered to every device
Logical data delivered to all devices
144TB
24GB × 6,000 devices
| Region | Target devices | Completed |
|---|
| Capital region | 2,250 | 2,250 |
| Central region | 1,250 | 1,250 |
| Southern region | 2,000 | 2,000 |
| Other regions | 500 | 500 |
Files the launch needs
- Common service resources
- Delivered
- Model program files
- Delivered
- Final configuration and changes
- Due on D-1
Each model’s program files are delivered in advance as well. Only the final configuration files, not yet fixed, remain.
The amount of data to deliver the day before launch is now far smaller.
The data that could go before launch day is already in place.
AT THIS MOMENTNow
D-3
Common resources delivered
Until launch
3 days
Launch, D-DAY 09:00
Current distribution
Common resources delivered
- Target devices6,000
- Files delivered6,000
Launch readiness
- Field validationDone
- Common resources deliveredDone
- Final files deliveredPlanned
- Service startPlanned
Next
Fix the final version
Next story, 18:00Final service files fixed →