Here are a few scenarios discussed with customers and issues with each.  Neither of these scenarios suggests upgrading EPROMs in currently deployed systems.  There is risk anytime a computer is opened, and when cards and/or EPROMs are handled.  There is little or no benefit to upgrading the EPROM in most "deployed" systems.  They are usually input only and should already be performing to system specifications.

SCENARIO-A

Pooled spares - 2 deep.  No software upgrades.  The LRU for sparing is the 99% configured card.  

• If subsystem is running pre ICE306 software, cards will need the rev2 EPROMs.
• Each subsystem is free to run its own version of the ICE tree.
• If card needs an output module, E1 maintenance will swap that module.
  

SCENARIO-B

Pooled spares - 2 deep.  OK to upgrade software.  The LRU for sparing is the 99% configured card.  

• If subsystem is running pre ICE306 software, subsystem software must be upgraded.
• All subsystems would be rolled to current ICE version during other system upgrades.
• If card needs an output module, E1 maintenance will swap that module.
  

ICE-ACTIONS

• ICE will provide training slides on how to swap I/O modules and EPROMs.
• ICE will provide EPROM replacements for each card with non-standard revision.