03.30.08
The End of Quarter Rush – Avoiding the Terminal 5 Syndrome
Last week I spent three days in London conducting a series of meetings with customers, partners, analysts and local media. These trips are always insightful for me, but last week was a particularly interesting time to be in London. First, the French President Nicolas Sarkozy and his new wife Carla Bruni Sarkozy were visiting the UK, which generated a lot of attention in the local press. Second, there was a significant disappointment over the problems at Heathrow’s new Terminal 5. On the opening day of the new terminal, the baggage handling system failed leaving thousands of passengers without luggage and resulting in the cancellation of dozens of flights. Fortunately, I was not flying British Airways so I was not impacted.
The third reason I found this trip more interesting than others was the sense of urgency amongst everyone I met with. Everyone was rushing to finalize activities before the end of first quarter. This year’s first quarter is an important economic event to be sure. Not only will it be the first financial period for 2008, but the quarterly earnings will provide insights into how widespread and deep the recession has become. Of course, every CEO wants to be able to downplay the impact of the recession on their financial results during the upcoming quarterly earnings call. So there is added pressure on both sales and finance organizations to ensure that they reach their forecasted goals.
End of Quarter Stress
End of quarter stress is not unusual for leaders in sales and finance, but it is becoming increasingly challenging for IT operations personnel as well. I was speaking to a customer in the manufacturing sector last week. He was explaining how critical their IT infrastructure is for their quarter-end operations. The last three weeks of the quarter are extremely hectic for these types of manufacturers who are trying to outdo the previous quarter’s revenue results. Sales, order processing and warehousing operations are often operating 24 hours a day including Saturday and Sundays. Frequently, it all comes down to the last day of the quarter. Products that ship as late as one minute before midnight can still qualify for booking in the quarterly sales reports. IT systems must be able to keep pace with the performance requirements of demanding end-users during this stressful period. And they absolutely cannot have downtime – either scheduled or unscheduled. Order processing, warehouse management and transportation management are critical for manufacturers. It is no surprise that ERP applications must deliver 100% uptime to support business operations. However, I doubt many realize how mission critical B2B (EDI and XML) connectivity is for quarter-end activities. An interruption in electronic document flow with business partners can bring a company’s supply chain to a halt – much like the failure of a baggage handling system at Heathrow’s Terminal 5. As supply chains become increasingly digitally integrated more and more buyer-to-supplier communications are being sent electronically. A loss of connectivity even for a matter of a few hours can jeopardize a company’s ability to meet its quarterly financial targets. A loss of data, specifically new orders, could be catastrophic.
The Impact of IT Failures
The root cause of the meltdown at Heathrow was that the baggage handlers IDs were not recognized by computers. As a result not only were airport personnel not able to log in to the bagging handling system, but they also could not navigate physically around the airport in and out of secured areas. Eventually the system became overloaded and checking of baggage was suspended. Delays unloading and loading of baggage postponed and even cancelled some flights. Spanish owned BAA (British Airports Authority) had invested over £4B and 20 years of planning to construct the new concourse. And the bagging handlers and computer applications had undergone 18 months of extensive testing, which proves that even the most well designed and planned systems can fail under peak loads.
What would happen if B2B (EDI and XML) connectivity at a multi-billion dollar manufacturer were lost on the last day of the quarter? Electronic purchase orders from large customers and distributors would not be able to be received. Even orders placed prior to the outage could not be confirmed electronically. Third party logistics providers could not be notified of shipments that were ready for pickup. In effect, the company’s supply chain would be significantly handicapped. Of course, orders could be taken over the phone and then processed manually. However, this would likely be a nuisance to high volume buyers accustomed to utilizing highly automated ordering processes in their procurement systems. Theoretically, electronic documents would not be lost as a result of an interruption to B2B communications. Most B2B transactions are asynchronous. As a result, purchase orders, confirmations and shipping instructions would be held in a queue until the connectivity was re-established. But depending upon the length of outage and the time period it occurred, the backlog may not be recoverable. Suppose an outage occurred from 1PM to 5PM on March 31st. Sales, warehouse and transportation personnel would probably not be able to process the backlog of orders even if they worked until midnight.
I wonder how many companies and vendors will experience an outage in their B2B applications during this quarter’s final day…or how many are expecting to fulfill orders based upon incoming parts shipped via BA’s Cargo service…
Steve Keifer
© Copyright 2007 GXS, Inc. All Rights Reserved.
