Incident: Passport Issuance Disrupted by Software Glitch at Delhi Passport Office

Published Date: 2012-04-24

Postmortem Analysis
Timeline 1. The software failure incident at the Bhikaji Cama Regional Passport Office (RPO) happened on Monday morning, and the system crashed again on Tuesday morning [11468]. 2. The article was published on 2012-04-24. 3. Therefore, the software failure incident happened in April 2012.
System 1. Entire system at the Bhikaji Cama Regional Passport Office (RPO) 2. Computer at the Bhikaji Cama RPO 3. National Informatics Centre (NIC) system
Responsible Organization 1. The National Informatics Centre (NIC) was responsible for causing the software failure incident at the Bhikaji Cama Regional Passport Office (RPO) [11468].
Impacted Organization 1. Delhiites who applied for a passport through the tatkal scheme at the Bhikaji Cama Place passport office [11468]
Software Causes 1. The software glitch caused the entire system to crash at the Bhikaji Cama Regional Passport Office, leading to nonissuance of passports [11468]. 2. The system crashed multiple times due to software issues, disrupting operations at the RPO [11468]. 3. The National Informatics Centre (NIC) had to repair the system due to software failures, but the system crashed again, indicating ongoing software issues [11468]. 4. A computer crash occurred due to software problems, and the NIC took several days to fix the issue, highlighting software inefficiencies [11468].
Non-software Causes 1. Bureaucratic red tape and inefficiency within the National Informatics Centre (NIC) delayed the fixing of the system after a computer crash [11468].
Impacts 1. Delays in passport issuance and processing, causing inconvenience to applicants like Sanjeev Anand who faced a harrowing time trying to get his passport [11468]. 2. Disruption of operations at the Bhikaji Cama Regional Passport Office, leading to nonissuance of passports and a standstill in work [11468]. 3. Failure of the system to issue tatkal passports within the promised 24-hour timeframe, undermining the government's claim of efficiency [11468]. 4. Increased workload and pressure on other Passport Seva Kendras (PSKs) to accept applications usually handled by the Bhikaji Cama RPO, potentially affecting their efficiency and service quality [11468].
Preventions 1. Regular maintenance and monitoring of the software system could have prevented the software failure incident [11468]. 2. Implementing redundancy and backup systems to ensure continuity of operations in case of a system crash [11468]. 3. Conducting thorough testing and quality assurance procedures before deploying the software system to identify and rectify any potential glitches or issues [11468].
Fixes 1. Implementing a more robust system maintenance and monitoring process to prevent future crashes and failures [11468]. 2. Conducting regular system checks and updates to ensure the software is functioning properly [11468]. 3. Improving the response time and efficiency of the National Informatics Centre (NIC) in addressing software glitches and failures [11468]. 4. Enhancing coordination between different passport offices and Passport Seva Kendras (PSKs) to ensure smooth operations and backup plans in case of failures [11468].
References 1. Senior officials of the ministry of external affairs (MEA) [Article 11468] 2. National Informatics Centre (NIC) [Article 11468] 3. Sanjeev Anand, a senior private sector executive [Article 11468] 4. A senior official [Article 11468]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident happened again at the Bhikaji Cama Regional Passport Office (RPO) in Delhi. The system crashed on Monday morning, and then it crashed once again on Tuesday morning, leading to a standstill in operations at the RPO [11468]. (b) The incident at the Bhikaji Cama RPO in Delhi also impacted other Passport Seva Kendras (PSKs) as they were told to gear up and accept applications usually submitted at the affected RPO. This indicates that the software failure incident had implications beyond just one organization [11468].
Phase (Design/Operation) design, operation (a) The software failure incident in the article can be attributed to the design phase. The glitch was a result of a system failure at the Bhikaji Cama Regional Passport Office, which paralyzed operations and led to the nonissuance of passports. The article mentions that the National Informatics Centre (NIC) had to repair the system multiple times, indicating a design flaw or issue introduced during system development or updates [11468]. (b) Additionally, the software failure incident can also be linked to the operation phase. The article highlights that the system crashed during operation at the Bhikaji Cama RPO, stopping all services including printing of passport booklets. This operational failure disrupted the normal functioning of the passport office and caused inconvenience to applicants [11468].
Boundary (Internal/External) within_system (a) The software failure incident at the Bhikaji Cama Place passport office in Delhi was primarily within the system. The glitch occurred within the system managed by the National Informatics Centre (NIC) at the Regional Passport Office (RPO) [11468]. The system crashed multiple times, leading to the nonissuance of passports and halting of operations at the RPO. The NIC was responsible for repairing the system, indicating that the failure originated from within the system itself.
Nature (Human/Non-human) non-human_actions (a) The software failure incident in the article was primarily due to non-human actions, specifically a software glitch that caused the system to crash at the Bhikaji Cama Regional Passport Office. The glitch paralyzed operations and led to the nonissuance of passports, raising concerns about the functioning of the new system introduced over the past two years [11468]. The National Informatics Centre (NIC) was involved in repairing the system, indicating that the failure was related to technical issues rather than human actions. (b) While the article does not explicitly mention any human actions contributing to the software failure incident, it does highlight bureaucratic red tape and inefficiency affecting the resolution of the technical problem. A senior official criticized the delay in fixing the system due to the NIC's inability to address the snag promptly, emphasizing the inefficiencies within the technical body managing the system [11468].
Dimension (Hardware/Software) hardware, software (a) The software failure incident mentioned in the article was primarily due to hardware issues. It was reported that a computer had crashed, and the National Informatics Centre (NIC) took several days to fix the problem by putting in a component that costs a mere Rs 40,000 [11468]. This indicates that the root cause of the failure originated in the hardware component of the system. (b) The software glitch that occurred at the Bhikaji Cama Regional Passport Office (RPO) was a contributing factor that originated in the software. The glitch led to the system crashing multiple times, halting passport issuance operations at the office [11468]. This software failure raised concerns about the functioning of the new system introduced over the past two years.
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident described in Article 11468 was non-malicious. The incident was attributed to a software glitch that caused the system to crash at the Bhikaji Cama Regional Passport Office, leading to the nonissuance of passports. The glitch was not intentional but rather a technical issue that affected the functioning of the passport issuance system [11468].
Intent (Poor/Accidental Decisions) poor_decisions (a) The software failure incident at the Bhikaji Cama Place passport office in Delhi was primarily due to poor decisions. The incident highlighted bureaucratic red tape and inefficiency within the National Informatics Centre (NIC), which manages the system. A senior official mentioned that it took the NIC five to six days to fix a component in the computer, which cost a mere Rs 40,000. This delay in resolving the issue showcases poor decision-making and inefficiency within the technical body responsible for managing the system [11468].
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident reported in Article 11468 can be attributed to development incompetence. The article mentions that a computer had crashed, and the National Informatics Centre (NIC), which manages the system, took five to six days to fix the issue due to a component that costs a mere Rs 40,000. This delay in resolving the technical problem highlights bureaucratic red tape and inefficiency within the NIC, which is a technical body that should ideally handle such issues promptly [11468].
Duration temporary The software failure incident reported in Article 11468 was temporary. The system crashed at the Bhikaji Cama Regional Passport Office on Monday morning, stopping all services, including the printing of passport booklets. The National Informatics Centre (NIC) repaired the system by Monday afternoon, but unfortunately, the system crashed again on Tuesday morning, bringing work to a standstill at the RPO [11468]. This indicates that the software failure was temporary and not permanent.
Behaviour crash (a) The software failure incident in Article 11468 can be categorized as a crash. The system at the Bhikaji Cama Regional Passport Office crashed on multiple occasions, leading to a complete halt in operations and nonissuance of passports [11468]. The system crashed on Monday morning, stopping all services, including the printing of passport booklets. Despite repairs by the National Informatics Centre (NIC), the system crashed again on Tuesday morning, causing work to come to a standstill [11468].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence delay (e) delay: People had to postpone an activity due to the software failure [11468]. The software glitch at the Bhikaji Cama Place passport office led to a halt in operations, causing a delay in the issuance of passports. This resulted in individuals like Sanjeev Anand facing a harrowing time trying to get their passports as there was no movement for four consecutive days. Additionally, the system crashes on Monday and Tuesday brought work to a standstill at the Regional Passport Office, leading to delays in processing passport applications under the tatkal scheme.
Domain government The software failure incident reported in Article 11468 is related to the government industry. The system failure occurred at the Bhikaji Cama Regional Passport Office (RPO) in Delhi, which handles passport applications under the tatkal scheme. The malfunction of the system led to the paralysis of operations and nonissuance of passports, impacting the government's passport issuance process [11468]. The National Informatics Centre (NIC) was involved in managing and repairing the system, highlighting the government's role in overseeing the passport application process [11468]. Additionally, the Ministry of External Affairs (MEA) officials were mentioned in the article, further emphasizing the government's involvement in the passport issuance system [11468].

Sources

Back to List