In what a senior company official conceded was an oversight, the 430-store, New Jersey-based chain failed to publish any ahead-of-time advisories before yanking its E-Commerce site's plug in the wee hours. Nor did it post much in the way of an explanatory statement during the long downtime period that followed.
"The Burlington Coat Factory site is temporarily unavailable. Please check back later" was the extent of the message presented to visitors while the site was AWOL. Burlington Coat Factory Supervisor of Web Development Jack Follansbee acknowledged the blunder and said that the retailer should have told visitors when its site was expected to return.
"The messaging on the site could clearly have been better," Follansbee said. "It was an omission. We should have done something (a status page) a little more customized."
The outage had long been planned to start Tuesday night and last all day Wednesday and into the early morning hours of Thursday, Follansbee said. "Wednesday is actually the lowest revenue day for our Web site," he said.
The need for the upgrade seems to have been demonstrated earlier in the week, something visitors to www.coat.com might have learned the hard way, as the site began experiencing sporadic, short-lived outages as early as Monday, according to site monitoring companies Dotcom-Monitor and Alert-Bot. "On Monday, it went down for five minutes with an HTTP 503 server-too-busy outage," said AlertBot Sales and Marketing Manager Justin Noll, adding that the site was offline for brief periods up until shortly after 2:00 A.M. (New York time) Wednesday. At that point, the lights went out completely.
Follansbee said the site was actually taken down at 10:00 P.M. (New York time) Tuesday and was targeted to be back up at 2:00 A.M. (New York time) Thursday. (Editor's Note: It seems as though Burlington Coat missed its target to be back up by 2 AM. According to site monitor services, Coat.com returned to the living at about 9:50 AM Thursday.)
Follansbee said he was not surprised the site was sputtering before the patient was euthanized. "We've been trying to migrate off obsolete hardware," he said. Any intermittent outages were "related to getting off the infrastructure we are replacing. The deteriorating performance of the old hardware was one of the reasons for the upgrade."
The effort was to perform a major upgrade to the chain's Oracle Application Server in addition to "a complete hardware and software refresh of our E-Commerce platform," including an operating system upgrade and "getting off some old disk arrays that we've been trying to retire," Follansbee said. "Everything is being refreshed."
Internal projections had the database upgrade alone taking 19 hours. "We needed a full 24-hour outage to do the upgrade, to do the tidying up," he said, adding that some of these upgrades were attempted last year—under a different executive's jurisdiction—and had "failed." Why had it failed. "Nobody seems to remember," Follansbee said.
The changes will not deliver any immediate functionality improvements but will enable such improvements shortly, including an improved capability to handle the accounting backend operations needed for selling stored-value cards online.
Although Burlington Coat Factory's situation clearly doesn't qualify as mere site maintenance, one of Alert-Bot's Noll's pet peeves is the way some major retailers regularly take their E-Commerce sites offline for nightly tweaking.
"These major brands should not have scheduled maintenance," he said, noting there is technology available that allows companies to update sites without incurring extensive downtime. "You don’t need to take down your Web site to do updates, but you see these huge, Fortune 500 companies doing it. I don’t know if they're skimping on IT spending, but I can't see why they are updating every night for two or three hours. When we do consulting, we tell them the most amount of downtime we consider acceptable is 20 minutes per month for scheduled maintenance."
That said, the Burlington changes included extensive upgrades to key hardware plus multiple pieces of strategic software. By completely taking down the site, the E-Commerce group was theoretically able to complete all of its major changes in barely more than one day. (We stress: "In theory.") An attempt to perform these changes while maintaining site functionality would have almost certainly caused the upgrades to take far longer, an undesirable luxury right before the crucial holiday shopping season. Noll's point has merit in general, but Burlington's effort seems like a valid exception.