Ricoh installer deployment timings
This page tells you how long the Cirros Ricoh Installer takes on each device, and how to plan a rollout that runs several devices at once. The figures are for planning. They were measured on a live run on a Ricoh IM C300 and are rounded.
Two situations are covered. An upgrade removes an existing print-management suite from the device and then installs Cirros. A clean install goes onto a device with nothing to remove.
| Scenario | Time per device | What it includes |
|---|---|---|
| Upgrade from an existing suite | About 18 minutes | Remove the old suite, two reboots, then install |
| Clean install | About 8 minutes | Install and one reboot, no removal |
Per-device breakdown
Upgrade: removing an existing suite, then installing Cirros
| Phase | What happens | Duration |
|---|---|---|
| Discovery | The installer reads the device and detects the existing suite | About 1 minute |
| Remove the old apps | The five old apps are uninstalled, at about 45 seconds each | About 4 minutes |
| Release reboot | The device reboots to free the removed app slots | About 2 minutes |
| Readiness wait | The installer waits for the device to be ready to install after the reboot | About 2.5 minutes |
| Install Cirros (5 apps) | Authentication, Launcher, Print, Scan and Copy, at about 1 minute each | About 4 minutes |
| Configure | Login is enabled, toner save is turned off and the volume limit is set | About 1 minute |
| Final reboot | The device restarts to activate authentication and settle | About 2 minutes |
| Total | About 18 minutes |
Clean install: a device with nothing to remove
| Phase | What happens | Duration |
|---|---|---|
| Discovery | The installer reads the device | About 1 minute |
| Install Cirros (5 apps) | Authentication, Launcher, Print, Scan and Copy, at about 1 minute each | About 4 minutes |
| Configure | Login is enabled, toner save is turned off and the volume limit is set | About 1 minute |
| Final reboot | The device restarts to activate authentication and settle | About 2 minutes |
| Total | About 8 minutes |
Why the difference? A clean install skips the removal, the release reboot and the readiness wait. Those phases add about 6.5 minutes, and they only happen when an existing suite has to be removed first.
Running 10 devices at once
Devices are installed at the same time, and each one is independent. Ten devices do not take ten times as long. The time for a batch is roughly the per-device time plus a little overhead, as long as the installer's concurrency setting is at least 10.
Set the concurrency to 10 first. The bulk concurrency defaults to 8, and the maximum is 16. At 8, ten devices run as a wave of 8 and then a wave of 2, which roughly doubles the time. Raise the setting to 10 so that all ten run in a single wave.
| Scenario | Per device | 10 devices, concurrency 10 | 10 devices, default concurrency 8 |
|---|---|---|---|
| Upgrade from an existing suite | About 18 minutes | About 18 to 20 minutes | About 34 to 36 minutes (8 then 2) |
| Clean install | About 8 minutes | About 8 to 10 minutes | About 16 minutes (8 then 2) |
Planning a larger fleet
- Work in batches of 10. With concurrency set to 10, each batch of 10 devices is one wave. A site of 40 devices is four waves. That is about 80 minutes for upgrades, or about 40 minutes for clean installs.
- Use a rule of thumb. The number of batches is the number of devices divided by 10, rounded up. The total time is roughly the number of batches multiplied by the per-device time.
- Set credentials once. Set the shared Web Image Monitor credentials for the whole selection before you start, so no device stalls waiting for a login.
- Pilot first. Test on one device before you roll out to the rest. The steps are in the quick start.
What affects the time
- Reboots are the fixed cost. About 6.5 minutes of an upgrade is the two reboots and the settling time after them. The app installs and removals take only about a minute each. You cannot shorten the reboots, as they are the device restarting.
- The model matters. These figures are for an IM C300. Larger Smart Operation Panel models can take longer to come back from a reboot, which lengthens the two reboot phases. Treat 18 minutes and 8 minutes as representative, not as a limit.
- A device that does not respond. If a device answers but reports no apps, the installer's pre-flight check catches it and asks for a mains power-cycle. That device sits out the batch until it has been power-cycled and run again, so it does not hold up the others.