Grid 'did all it could' after software failure

Milne, Roger
November 2007
Utility Week;11/2/2007, Vol. 28 Issue 4, p20
Trade Publication
The article reports that National Grid Gas has defended its handling of a software failure that meant shippers could not access the online computer system that handles nominations governing the movement of gas through the National Transmission System in Great Britain. Due to the failure, shippers were unable to register trades and consequently had problems balancing their positions. A spokesman for National Grid Gas said that the software problems caused a lot of problems and that the inability to reconcile positions proved frustrating.


Related Articles

  • Static Analysis and Dynamic Steering of Time-Dependent Systems. Vicario, Enrico // IEEE Transactions on Software Engineering;Aug2001, Vol. 27 Issue 8, p728 

    An enumerative technique is presented which supports reachability and timeliness analysis of time-dependent models. The technique assumes a dense model of time and uses equivalence classes to enable discrete and compact enumeration of the state space. Properties of timed reachability among...

  • Defense and Attack of Two-Component Multi-State Systems. Hausken, Kjell // International Journal of Performability Engineering;May2011, Vol. 7 Issue 3, p1 

    A two component system can be fully operational, in two states of intermediate degradation, or fail. Each component is protected by a defender which maximizes its reliability weighted against the defense costs, and attacked by an attacker which maximizes its unreliability weighted against the...

  • Focusing Audit Testing on High Risk Software Modules: A Methodology and an Application. Sherer, Susan A.; Paul, Jack W. // Journal of Information Systems;Fall93, Vol. 7 Issue 2, p65 

    This article presents a model and methodology for deriving the expected financial consequence of software failure in the subsystems, or modules, of a complex computer system. The model incorporates assessments of the magnitude of errors, as well as inherent and control risks. First, hazards,...

  • IT Failure Rates--70% or 10-15%? Glass, Robsrt L. // IEEE Software;May/Jun2005, Vol. 22 Issue 3, p112 

    The article focuses on the percentage of software projects failure rates. The author has seen software failure trumpeted from so many academic research papers that he had to quit counting. However, if one closely examines the citations they use to support the claims of crisis, over and over...

  • Quantitative Analysis of Faults and Failures in a Complex Software System. Fenton, Norman E.; Ohlsson, Niclas // IEEE Transactions on Software Engineering;Aug2000, Vol. 26 Issue 8, p797 

    The dearth of published empirical data on major industrial systems has been one of the reasons that software engineering has failed to establish a proper scientific basis. In this paper, we hope to provide a small contribution to the body of empirical knowledge. We describe a number of results...

  • Exploring the Role of Diagnosis in Software Failure. Hatton, Les // IEEE Software;Jul/Aug2001, Vol. 18 Issue 4, p34 

    Analyzes the repetitive failure in software-controlled systems. Evidence for repetitive failure in the system; Reasons for repetitive failure; Comparison of diagnostic distance with diagnostic quality.

  • Microsoft maintenance program fails. Kirk, Jeremy // Network World;7/16/2007, Vol. 24 Issue 27, p26 

    The article reports on the system failure of Microsoft's Software Assurance maintenance program in the U.S. The program guarantees updates to new products along with support and training tools, however, information technology (IT) procurement managers have found that the program may not save...

  • LETTERS. Bellair, David; McConnell, Steve; Land, Frank; Darroch, Fiona; Toleman, Mark; Kotula, Jeff // Software Practitioner;Mar/Apr2006, Vol. 16 Issue 2, p3 

    Several letters to the editor in response to articles in previous issues, including the grammatical use of the word wrong and wrongly, the failure rate of software project and "Bridging the Academic-Industry Divide: Academics Reach Out," by Fiona Darroch and Mark Toleman in the November 2005...

  • Microsoft says reported IE 7 bug not in browser.  // Network World;10/23/2006, Vol. 23 Issue 41, p5 

    The article reports on the alleged problematic component of Microsoft's Outlook Express electronic-mail client (e-mail) as detected by Secunia, a research firm in the U.S. According to the research firm, it is not a browser bug at all that flaws the Internet Explorer 7. Rather, it is on its...


Read the Article


Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics