|
Replacing or Upgrading a Subsystem
Replacing a subsystem with obsolete components
create an opportunity to upgrade incrementally with increased
functionality and may even have cost advantages. A new subsystem,
theoretically, doesn't affect the integrity of the entire
system. All that is needed is to match the connectivity requirements
and communication protocols. Or is it?
Requirements for replacing or upgrading a subsystem
On the surface, replacing a subsystem seems
very simple. The entire system depends on uniformity to operate
flawlessly. Everything must be uniform; documentation, staff
training, spare parts, technical support, test equipment,
and interaction with other subsystems. Without uniformity,
the reliability of the legacy system is questionable. And,
upgrading a single subsystem may require that similar subsystems
be retrofitted to insure uniformity.
Subsystem replacement isn't the proper solution
for component obsolescence. The overall cost both in the cost
of hardware and in the effort to cerfity proper functionality
will be greater than just the cost of a subsystem. The time
required to determine possible subsystem interaction problems
also move this solution beyond an acceptable time line. The
issue is how to keep the legacy system working as a whole,
flawlessly.
Next: Is it possible
to replace only the obsolete component?
|
