Caregroup Case Study

806 Words2 Pages

Leading up to the collapse of the Caregroup, a researcher on the CareGroup network started an experiment with a knowledge management system application. The software was designed to locate and automatically copy information across the network. The researcher left the software up and running in its initial configuration. The software hadn’t been tested for the environment and began copying data in large volumes from other computers. By the afternoon of November 13, 2002 (the day of the collapse) the software was moving large terabytes of data across the network.
Although the large data transfers monopolized the services on the local network, the main network components still functioned properly.

The impact of the knowledge management system
They began to duplicate each other’s functionality. The messages began repeating each other in an endless loop until the network totally disabled.

The lessons learned from the CareGroup network collapse:

1. Don’t hesitate to bring in experts to make sure your network is configured properly. Correct assessment, however the lesson doesn’t factor in when to bring in an expert. Despite an over-reliance on technology, there needs to be a timeframe for this expert and how their analysis will support overall technological requirements.

2. Do not let any one individual in your IT group become the sole point of failure. Correct assessment; ironically it was a knowledge management system that led to the crash of the network. Succession planning is key ingredient to success for businesses.

3. Keep your working knowledge current. Correct evaluation. Technology changes rapidly and it’s important to understand industry standards, methodologies, and best
Beware of users armed with just enough knowledge to be dangerous. This is half-way correct. While the user’s experimentation led to the failure, the article doesn’t shed light on the policy for exploratory testing etc. While the user is culpable, a deeper dive into the culture may yield additional lessons learned for Caregroup. Some questions may involve include? 1) what are the corporate standards for testing? 2) how are test environments configured? 3) Who approves test scenarios 3) Should we use mock data when simulating test cases etc?

5. Institute rigorous network change control. Correct assessment and probably the most important lesson. Caregroup can review ITIL methodology for best practices around incident end event management.

6. Adapt to externalities. Correct evaluation, however additional analysis is required. The IT department needs to collaborate with the business to better understand how organization changes impact applications and systems. Moreover, IT needs to strengthen the IT-business alignment to stay abreast of future changes. One methodology that may assist here is business architecture, a blueprint of the business that supports aligning strategic objectives and tactical demands.

7. There are limits to customer-centric responsiveness. Correct assessment however it may be tricky to implement. This is where business-IT alignment becomes critical. While IT may not always meet customer objective, it’s important to build the relationships and not alienate

Open Document