Pdf importance of software testing in the process of. Mar 29, 2004 lexington software developer ipswitch inc. The massive blackout, a wake up call to utilities and consumers alike, compounded the concerns about climate change, the burgeoning population and scarcity of. Widearea measurement, protection and control wampac technology has been gaining momemtum following the northeast blackout in 2003.
Fifty million people were affected, including residents of new york, cleveland and detroit, as well as toronto and ottawa, canada. August 14, 20, will mark 10 years since more than 50 million people in the northeast were left in the dark after an overwhelmed electric system crashed into a devastating blackout. Northeast united states and canada august 1415, 2003 it took months before the real cause of the northeast blackout of 2003 was finally determined. Moreover, the existing grid is wasteful, with 285 percent more power loss today than in 1984. The utility industry is in the midst of energy modernization efforts that ramped up in large part following the northeast blackout of 2003. Energy modernization through microgrids microgrid knowledge. Moving forward on lessons learned from the blackout of 2003. Executive summary on the northeast blackout of 2003. Now there is an urgent and evolving need for more stringent standards to protect the bulk electric system bes of the north american power grid. Kingdon capital management lucked out with the northeast blackout of august 2003. Internationally, coverage of the story focused on the development of the. The blackout that exposed the flaws in the grid the new.
Not only do microgrids alleviate the risk of a regionwide power outage on the scale of the 2003 northeast blackout, but they enable formerly pure energy consumers to also become energy. It is hard to believe 15 years have passed since a massive power outage left 50 million people in the northeast and midwest in the dark, including metro detroit. Noaa captures northeast blackout noaa posted these satellite images online taken before and after of the historic blackout of the northeastern united states, which plunged millions of people into darkness. Power providers needed to develop a new system to alert real estate owners of potential power outages. Software bug in the alarm system in the control room of firstenergy the northeast blackout of 2003 was a widespread power outage throughout parts of the northeastern and midwestern united states, and the canadian province of ontario on august 14, 2003, beginning just after 4. Its been a decade since the great northeast blackout cut power to over 45 million people across the northeastern and midwestern united states and 10 million people in ontario, canada. While it may seem like trivia, it causes huge headaches for software developers is taken advantage of by highspeed traders triggered the 2003 northeast blackout has to be corrected for by gps satellites is now recognized as a major cause of world war i. Even if a developer puts in the best of efforts, there will be. A technician had shut it off to upgrade the software, and then gone to lunch. Jun 29, 2019 the great blackout of 2003 that occurred in northeast us is considered to be the worst in history. The foremost task of a tester is to find defects in the software and report them to developer so that they can be rectified.
The northeast blackout of 2003, which impacted the u. Satellite images of the night before left and night after right the 14 august 2003 blackout. New software tools streamline vegetation management programs. Set in a fictionalized version of chicago, the plot follows hacker aiden pearces search for revenge after the killing of his niece. In a matter of seconds, large portions of ohio, michigan, pennsylvania, massachusetts, new york, connecticut, new. The task force responsible for investigating the cause of the aug. Also data race was one of the causes that led to the northeast blackout of 2003 that affected more than 50 million people in the us and canada.
Blackout 2003 pic from space howardforums is a discussion board dedicated to mobile phones with over 1,000,000 members and growing. Find, read and cite all the research you need on researchgate. One of them was buried in a massive piece of software compiled. This is the second post in a microgrid knowledge series and focuses on why clean energy microgrids for health care and hospitals make sense. Nerc worked closely with the joint uscanada task force and all affected entities to investigate the causes of the august 14, 2003 blackout.
Northeast blackout leaves 50m people without power, august 14, 2003. Examples of great engineering projects everyday engineering. According to bert taube, director of business development for versant, a data management software company, energy utilities encounter many of the data management problems that other. The economic cost of the blackou t an issue paper on the northeastern blackout, august 14, 200 3. Compiler validation by program analysis of the crossproduct.
Significant information and reports about the blackout investigation are posted below. A major outage knocked out power across the eastern united states and parts of canada on august 14, 2003. The first cyber battle of the internet of things era. Impact of northeast blackout continues to emerge by jeremy johnson and alex lefebvre 20 august 2003 the blackout that began last thursday, cutting. A previouslyunknown software flaw in a widelydeployed general electric energy management system contributed to the devastating scope of the august 14th northeastern u. The blackout was, in fact, triggered on a hot day by an untrimmed tree in ohio and was aided by a hung alarm system. The main cause of this disaster was a software bug in the energy management system used by. Software crisis in software engineering computer notes. Innovation may be the lifeblood of technology, but once the electrons stop flowing even the best information system goes limp. New software tools streamline vegetation management programs, reports. On august 14, 2003, a series of faults caused by tree branches touching power lines in ohio, which were then complicated by human error, software issues, and equipment failures, led to the most widespread blackout in north american history. Northeast blackout of 2003 academic dictionaries and. The outage affected an area with an estimated 50 million people and 61,800 megawatts mw of electric load in the states of ohio, michigan, pennsylvania, new york, vermont, massachusetts, connect.
Northeast blackout of 2003 the northeast blackout of 2003 was a massive widespread power outage that occurred throughout parts of the northeastern and midwestern united states, and ontario, canada on thursday, august 14, 2003, at approximately 4. Initially, canadian defense minister john mccallum blamed an outage at a nuclear power plant in pennsylvania, which the states emergency management agency denied. Software failure cited in august blackout investigation. New monitoring tools keep your ac running when temperatures soar. The department of energy and natural resources canada jointly commissioned a task force that. The north american electric reliability corporation nerc critical infrastructure protection cip standards evolved after the great northeast blackout of 2003 that affected over 50 million people. In this page, i collect a list of wellknown software failures. Kajori banerjee senior member of technical staff oracle.
The northeast blackout in 2003 has been one of the major power system failures in the history of north america. To nobodys surprise, the final report on the blackout released by a. The southwest blackout of 2003 1218 words bartleby. The northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and the canadian province of ontario on thursday, august 14, 2003, just after 4. Icf consultings approach to these issues is strengthened by its expertise in. Taking after are 6 famous software disasters in as beneath.
The northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and the canadian province of ontario on thursday, august 14, 2003, just before 4. Tougher regulatory measures are in place, but were still a long way from a smart power grid. In many ways, the northeast blackout of 2003 was a learning opportunities for those involved. The engineers determined that the immediate source of the problem was a. Nov 06, 2017 clean energy microgrids for the commercial and industrial sector. It is part of the eastern interconnection grid operating an electric transmission system serving all or parts of delaware, illinois, indiana, kentucky, maryland, michigan, new jersey, north carolina, ohio, pennsylvania, tennessee, virginia, west virginia, and the district of columbia. The northeast blackout of 2003 was a widespread power outage throughout parts of the northeastern and midwestern united states, and the canadian province of ontario on august 1428, 2003, beginning just after 4.
Nov 06, 2017 clean energy microgrids for hospitals make electricity more reliable. Look beyond recycling to the higher goal of sustainability. Technical analysis of the august 14, 2003, blackout nerc. The northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and the canadian province of ontario on thursday. The blackout that exposed the flaws in the grid the new york. By thinkreliability staff on august 14, 2003, over 50 million people in the u. Description of outage investigation and process for development of recommendations. Northeast blackout of 2003 wikimili, the free encyclopedia. Clean energy microgrids for hospitals make electricity more. Northeast blackout of 2003 wikimili, the best wikipedia.
New york news coverage of the northeast blackout of 2003. Northeast blackout of 2003first energy outage reports. We examined the public health effects of the northeast blackout of august 2003 and the emergency response to the blackout by the new york city department of health and mental hygiene dohmh. Northeast blackout of 1965 or north america blackout of 1965. Presently, the two countries are investing heavily in ensuring that a similar incident is averted. The report makes clear that this blackout could have been prevented and that immediate actions must be taken in both the united states and canada to ensure that our electric system is more reliable. The northeast blackout struck 15 years ago today extremetech. Canada power system outage task force final report on the august 14, 2003 blackout in the united states and canada. The 2003 northeast blackoutfive years later scientific.
Edsa introduces paladin smartgrid, the first microgrid. This blackout affected an estimated 55 million people spread. The northeast blackout of 2003 was one of the most critical blackouts in the history which affected more than 50 million people in both the united states and canada. More than 35 million people were hit by the northeast blackout in 1965, one of the largest outages in north american history. Investigators found several factorsalarm system issues, software bugs, and an overloaded. Jan 05, 2016 forbes takes privacy seriously and is committed to transparency. Ces international announces 2003 highlights powergrid. Download the full report, the rise of clean energy microgrids. Pjm interconnection llc pjm is a regional transmission organization rto in the united states.
The northeast blackout of 2003 was a widespread power outage throughout parts of the. On august 14, 2003, more than 50 million people in the united states and canada were left in the dark thanks to one of the most widespread. Software failures in these technologyoriented areas have led to considerable loss in terms of time, money, and even human lives. Ten years ago today, large portions of the midwest and northeast united states and into canada went dark. Many others did not get their power back until two days later. The map shows an entire state or province as red, when in some cases only a small portion e. For some customers, power was not restored for nearly four days. The 2003 northeast blackoutfive years later scientific american. I was in the 2003 blackout and it definitely gave me food for thought as to what might happen if there was a major power outage that lasted more than 2 days as it lasted for me. I will start with a study of economic cost of software bugs. Et, 21 power plants shut down in just three minutes. Most did not get their power back until two days later. The relevant root cause information is included below. Embedded software is ubiquitous check your pockets.
Caused by inadequately pruned trees and a software bug, this cascading sequence of infrastructure failures holds important lessons for the world of everyday engineering. How and why the blackout began in ohio summary this chapter explains the major eventselectrical, computer, and humanthat occurred as the blackout evolved on august 14, 2003, and identifies the. Business continuity lessons from the blackout of 2003. Northeast blackout of 2003 was triggered by a local outage that went undetected due to a race condition in the ges monitoring software smartship uss yorktown had to be towed into a naval base after an unhandled division by. On august 14, 2003, utility companies took stock of a problem everybody knew was there, but few were aware of its potential destructive impact. Importance of qa in software development projects opensense. Nerc cip compliance version 6 for network security tufin. Final report on the august 14, 2003 blackout in the united.
On august 14, 2003, large portions of the midwest and northeast united states and ontario, canada, experienced an electric power blackout. Ten years later, we are still grappling with concerns over the vulnerability of the power grid. How could you accidentally cause a global blackout. I dont mean a 2 hour fun day but a major blackout like the northeast blackout of 2003. The northeast blackout revealed an electric system in disrepair. Software crisis in software engineering ecomputernotes. A collection of wellknown software failures software systems are pervasive in all aspects of society. The northeast blackout of 2003 wikipedia august 14, 2003 the northeast blackout of 2003 was a massive widespread power outage that occurred throughout parts of the northeastern and midwestern united states and ontario, canada on thursday, august 14, 2003.
The data collected from a widearea measurment system wams should be analysed and utilized within order of tens of milliseconds for wide area monitoring and controlling of power system interconnection. The united states and canada have many joint ventures of this nature, and their continued cooperation has given way to development in many areas. Then close the course by considering the great northeast blackout of 2003. Some atm networks hit hard by blackout atm marketplace. We investigated mortality in new york, ny, during the largest blackout in us history august 1415, 2003. Chinese hackers may have been responsible for the recent power outage in florida, and the widespread blackout that struck the northeastern u. Its been 15 years since the 2003 blackout that left metro. Cause, software bug in the alarm system in the control room of firstenergy. The main cause of this disaster was a software bug in the energy management system used by firstenergy corporation, located in akron, ohio. The atlantic has put together a photo essay of the event and how it impacted new yorkers, including those stuck in the citys transit systems. Power systems are already coping with spikes, surges, and even blackouts. Northeast blackout of 2003 or north america blackout of 2003. From electronic voting to online shopping, a significant part of our daily life is mediated by software. Importance of software testing in the process of software.
In more remote areas it took nearly a week to restore power. Nerc standards and compliance 101 mallory huggins, nerc standards developer adina mineo, nerc senior compliance operations auditor standards and compliance spring workshop. History has been witness to many such failures, some of which are listed below. Dec, 2018 the current model of power production and delivery wont sustain fastpaced business and human population growth. Another pdf file to the final analysis of the 2003 power blackour in the ne united states. This greatly exaggerates the actual area of the blackout. The northeast blackout leaves 55 million without power and occupants trapped in elevators and vestibules for hours. Geckil, economist aeg working paper 2003 2 introduction on thursday, august 14, 2003, an electrical disruption caused a loss of electrical service to consumers and industry acro ss the northeast. As a matter of fact, programming bugs can irritate, however, the defective programming can likewise be costly, humiliating, ruinous and savage.
Software bug contributed to blackout kevin poulsen, securityfocus 20040211. A map of the states and provinces affected by the w. Led a major failsafe control box upgrade project from the northeast blackout of 2003. It is the process of verification and validation of software. Utility vegetation management final report utility vegetation management final report march 2004 cn utility consulting, llc 1 i. Coauthor paul hines, now assistant professor of engineering at the university of vermont in. Business continuity lessons from the blackout of 2003 cio. Software failure cited in august blackout investigation computerworld. The power outage that left 50 million wo electricity retro report the new york times duration. A similar incident occurred in 2003, when a power grid collapse. Were most satisfied, however, with the fact that our systems delivered recordbreaking performance to our customers during some of the most demanding outage events in recent history, including the northeast blackout and hurricane isabel.
1505 522 324 221 1198 1425 876 125 88 164 525 1052 562 560 897 793 648 1156 1226 1426 541 405 1315 131 703 1118 294 1231 1431 1019 576 1123 580 1508 818 1352 468 1369 1052 1115 577 1345 646 333 352 163 651 13