The least glamorous line in an upgrade budget may be the one paying for old and new equipment to work together. The new system gets the demonstration. The switches still carrying its traffic get another year on the wall.
That awkward overlap is worth thinking about after Friday's FAA ground stop. In a November 14 update, SecurityWeek reported that investigators were examining a possible software-update connection to the communications failure. Officials described older network equipment struggling with changes. No official root cause has been announced, and officials have found no evidence of a cyberattack. The investigation is still open.
The FAA's own preliminary statement confirmed communication problems affecting multiple air route traffic control centers. WABC reported the consequences at Newark, JFK and LaGuardia: halted departures, stranded travelers and plans coming apart. Departures resumed Friday evening. For people trying to get somewhere, the condition of the equipment between two systems suddenly mattered a great deal.
I wouldn't turn an unfinished investigation into a verdict on a particular upgrade or supplier. I would take the opportunity to look at the less photogenic part of a business IT upgrade: everything the new purchase will continue depending on.
The equipment that isn't leaving yet
Replacing everything at once is a hard sell when the business still has wages, rent and customers to look after. A phased technology upgrade can be a perfectly sensible choice. You replace the application this year, the network next year, and the specialist device when its service contract ends.
Each purchase can be reasonable on its own. The interesting question is what happens during the months between them.
For a simple illustration, a small warehouse might buy handheld scanners while keeping its existing wireless network. A demonstration with one scanner says very little about the morning when receiving, picking and shipping all start using them together. A slow scan could be a wireless problem, an application problem or a combination. The person holding the parcel would mostly like to finish the job.
That's why I'd spend some of the upgrade budget on an ordinary working morning. Try the proposed equipment with the legacy network equipment that will actually remain. Include the busiest task, the awkward corner of the building and the device nobody volunteered to replace. This isn't a claim about what failed at the FAA. It's a useful way to examine your own transition before it becomes everyone's problem.
I'd also want the installer and the application provider looking at that trial together. Otherwise, the business can end up paying for a very articulate disagreement about whose part works.
The return path deserves the same attention. If the trial interrupts orders, what can safely be put back, and who makes that call? If moving records or changing equipment makes a quick return impractical, the plan needs another way to keep that work moving. A reassuring word about rollback is less useful than knowing what Monday would actually involve.
For the next proposal on your desk, a small addition could change the conversation: leave room in the price and schedule to test the old and new combination, agree on what would stop the change, and watch a complete cycle of real work before calling it finished.
The old equipment may still have another good year in it. I'd like that year included in the demonstration.
Your old technology still has a job to do
Tekmyster has experience with very old technology and the migrations that help businesses move beyond it. If your inventory, orders, invoicing or CRM still depend on aging equipment, we can assess your environment and help plan the transition around the work your business has to keep doing.
Give Tekmyster a call to learn how we can help prevent these issues in your business.
#FAA #Aviation #LegacyTechnology #LegacySystems #RetroComputing #VintageNetworking #NetworkModernization #BusinessContinuity #Tekmyster
Sources and further reading
