Incident: MI5's Anti-Terror Supercomputer Delay Impacts Olympic Security

Published Date: 2012-07-14

Postmortem Analysis
Timeline 1. The software failure incident happened before the Olympics in 2012. 2. The article was published on 2012-07-14. 3. Therefore, the software failure incident likely happened in July 2012.
System 1. New 'electronic records management' system designed to help MI5 officers track terror suspects [13114]
Responsible Organization 1. The firm of IT consultants hired by MI5 was responsible for causing the software failure incident [13114].
Impacted Organization 1. MI5 - The software failure incident impacted MI5 as the supercomputer meant to help track terror suspects was not ready in time for the Olympics, leading to the termination of the IT consultants' contract [13114].
Software Causes 1. Technical and commercial difficulties leading to delays in implementation [13114] 2. Failure to meet deadlines by the IT consultants resulting in the termination of the contract [13114] 3. Risk assessment indicating it would be too risky to introduce new software just before the Olympics [13114]
Non-software Causes 1. Delays in implementation by the IT consultants hired by MI5 [13114] 2. Technical and commercial difficulties faced by the IT project [13114] 3. Concerns about the use of consultants and contractors not being as controlled as they should have been [13114] 4. Decision to postpone introducing the system until after the Olympics due to the risk of introducing new software just before the event [13114] 5. Staff reductions and early retirements within MI5, MI6, and GCHQ leading to a change in staff mix and loss of experienced personnel [13114]
Impacts 1. The software failure incident led to the delay in the implementation of the new intelligence-checking system designed to help MI5 track terror suspects, impacting the security operations during the Olympics [Article 13114]. 2. The delay in the software implementation forced MI5 to postpone the introduction of the system until after the Olympics, leaving the taxpayer out of pocket and requiring the security service to find a replacement contractor [Article 13114]. 3. The software failure incident contributed to the departure of almost 500 officers from MI5, MI6, and GCHQ, costing the taxpayer millions in exit packages, as part of a broader restructuring effort within the intelligence agencies [Article 13114]. 4. The software failure incident indirectly affected the criminal justice system, leading to the delay of criminal trials and the reassignment of police officers to assist at the Olympics, potentially impacting the timely resolution of legal cases and increasing costs for taxpayers [Article 13114].
Preventions 1. Proper project management and oversight to ensure deadlines are being met and progress is on track [13114]. 2. Thorough testing and trialing of the software before the scheduled implementation date to identify and address any issues or bugs [13114]. 3. Clear communication and collaboration between the security service and the IT consultants to address technical and commercial difficulties promptly [13114]. 4. Implementing a contingency plan in case of delays or failures in the software development process to mitigate the impact on operations [13114].
Fixes 1. Implement proper project management practices to ensure deadlines are met and projects are delivered on time [13114]. 2. Conduct thorough testing and trials of the software before critical events like the Olympics to identify and address any issues [13114]. 3. Improve oversight and control over IT security contracts to prevent technical and commercial difficulties that lead to project failures [13114]. 4. Enhance recruitment and retention strategies to retain skilled staff in the intelligence and security agencies, reducing the need for costly redundancies and early retirements [13114].
References 1. MI5 security service 2. Security sources 3. Jonathan Evans, director-general of the security service 4. Whitehall security source 5. Intelligence and Security Committee 6. GCHQ director Iain Lobban 7. District judge Graham Wilkinson

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident at MI5 with the supercomputer for tracking terror suspects is an example of a failure within the same organization. The article mentions that MI5 had to sack a firm of IT consultants after they failed to meet deadlines to implement the new intelligence-checking system, leading to the software not being ready in time for the Olympics [13114]. (b) The article does not provide information about similar incidents happening at other organizations or with their products and services.
Phase (Design/Operation) design (a) The software failure incident in the article is related to the design phase. The failure was due to contributing factors introduced by the system development process. The article mentions that a firm of IT consultants was sacked by MI5 after failing to meet deadlines to implement the new intelligence-checking system. The project was plagued by technical and commercial difficulties, leading to the termination of the contract with the IT firm [13114]. (b) The software failure incident in the article is not directly related to the operation phase or misuse of the system.
Boundary (Internal/External) within_system (a) The software failure incident related to the MI5 supercomputer collapse appears to be within the system. The failure was attributed to the firm of IT consultants failing to meet deadlines to implement the new intelligence-checking system, leading to the termination of their contract [13114]. Additionally, the project was plagued by technical and commercial difficulties, indicating internal challenges within the system [13114].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in the MI5 IT project was primarily due to non-human actions, specifically technical and commercial difficulties. The project faced challenges such as delays in implementation, technical issues, and the system not being ready in time for the Olympics despite costing up to £1 million [13114]. Additionally, the decision to postpone introducing the system until after the Olympics was made to avoid the risk of introducing new software just before the Games, indicating a cautious approach to technical implementation [13114]. (b) Human actions also played a role in the software failure incident. MI5 sacked a firm of IT consultants after they failed to meet deadlines to implement the new intelligence-checking system, leading to the termination of the contract [13114]. The director-general of the security service, Jonathan Evans, expressed concerns about the control over the use of consultants and contractors, indicating a need for better management of relationships with external parties involved in IT projects [13114].
Dimension (Hardware/Software) software (a) The software failure incident related to hardware: - The article does not specifically mention any hardware-related issues contributing to the software failure incident. It primarily focuses on the failure of the IT consultants to meet deadlines and implement the new intelligence-checking system, leading to the software not being ready in time for the Olympics [13114]. (b) The software failure incident related to software: - The software failure incident in this case is directly related to software issues. The article discusses how the supercomputer, designed to help MI5 track terror suspects, will not be ready in time for the Olympics due to the failure of the IT consultants to implement the new intelligence-checking system as planned. This delay in software development and implementation is the primary cause of the failure [13114].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the MI5 supercomputer was non-malicious. The failure was attributed to the firm of IT consultants failing to meet deadlines to implement the new intelligence-checking system, leading to the termination of their contract [13114]. The delays in implementing the system were due to technical and commercial difficulties, not malicious intent to harm the system.
Intent (Poor/Accidental Decisions) poor_decisions (a) The software failure incident related to the MI5 supercomputer was primarily due to poor decisions. The failure was attributed to the firm of IT consultants failing to meet deadlines to implement the new intelligence-checking system, leading to the termination of their contract by MI5 [13114]. Additionally, the project was plagued by technical and commercial difficulties, resulting in delays and cost overruns [13114]. MI5's director-general, Jonathan Evans, expressed concerns about the lack of control over the use of consultants and contractors, indicating a need for better management of such relationships in the future [13114].
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident related to development incompetence is evident in the article as it mentions that MI5 had to sack a firm of IT consultants after they failed to meet deadlines to implement the new intelligence-checking system. The project was estimated to have already cost up to £1 million and was plagued by technical and commercial difficulties, leading to the termination of the contract with the IT firm [13114]. Additionally, the director-general of the security service expressed concerns about costly IT security contracts that were not as controlled as they should have been, indicating a lack of proper management and oversight in the development process [13114]. (b) The software failure incident related to accidental factors is not explicitly mentioned in the articles provided.
Duration temporary The software failure incident related to the MI5 supercomputer collapse was temporary. The failure was due to contributing factors introduced by certain circumstances, specifically the failure of the IT consultants to meet deadlines and implement the new intelligence-checking system in time for the Olympics. The incident led to the termination of the IT consultants' contract and the decision to postpone the implementation of the system until after the Olympics [13114].
Behaviour crash, omission, timing, value, other (a) crash: The software failure incident in the article is related to a crash as the supercomputer system designed to help MI5 track terror suspects will not be ready in time for the Olympics, leading to a failure in performing its intended functions [13114]. (b) omission: The software failure incident can also be related to omission as the new intelligence-checking system was not implemented in time, omitting the performance of its intended functions before the start of the Games [13114]. (c) timing: The software failure incident can be related to timing as the decision to postpone the implementation of the system until after the Olympics was made due to the risk of introducing new software just before the Games, indicating a failure in timing of the system deployment [13114]. (d) value: The software failure incident can be related to a failure in value as the project, estimated to have already cost up to £1 million, faced technical and commercial difficulties leading to the termination of the contract with the IT consultants, indicating a failure in delivering the intended value [13114]. (e) byzantine: The software failure incident does not exhibit behavior related to a byzantine failure as there is no mention of inconsistent responses or interactions in the system's behavior in the article [13114]. (f) other: The other behavior exhibited in the software failure incident is a delay in the implementation of the system, which can be considered a failure in meeting deadlines and causing a setback in the operational readiness of the software [13114].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property, delay, non-human, theoretical_consequence (a) death: There is no mention of any deaths resulting from the software failure incident reported in the articles [13114]. (b) harm: There is no mention of physical harm to individuals resulting from the software failure incident reported in the articles [13114]. (c) basic: There is no mention of people's access to food or shelter being impacted due to the software failure incident reported in the articles [13114]. (d) property: The software failure incident led to financial consequences as the project, estimated to have already cost up to £1 million, had to be postponed, leaving the taxpayer out of pocket while MI5 had to find a replacement contractor [13114]. (e) delay: The software failure incident caused a delay in the implementation of the new intelligence-checking system, which was supposed to be ready in time for the Olympics but had to be postponed until after the Games [13114]. (f) non-human: The software failure incident impacted the implementation of a computer system designed to help MI5 officers track terror suspects, which is a non-human entity [13114]. (g) no_consequence: There were observed consequences of financial loss and delay resulting from the software failure incident reported in the articles [13114]. (h) theoretical_consequence: There were potential consequences discussed, such as the impact on the service's capability and the risk of introducing new software just before the Olympics, but these did not materialize as immediate concerns [13114]. (i) other: There are no other consequences described in the articles beyond the financial loss and delay resulting from the software failure incident [13114].
Domain information, government (a) The failed system was intended to support the government industry, specifically the security service MI5, in tracking terror suspects and carrying out secret searches on suspects, including those who may pose a threat at the Olympics [13114]. The system was designed to bring together all MI5 intelligence material for officers to carry out complete searches of old and current records [13114]. (l) The failed system was directly related to the government industry, as it was a supercomputer intended to assist MI5 officers in their security operations, particularly in the context of the Olympics and tracking potential terror suspects [13114]. The system's failure led to delays and concerns about security measures during the event [13114].

Sources

Back to List