THE MISSION
Technology with a
public purpose.
Northrop Grumman proposed CommandPoint as the core of a new Metropolitan Police command-and-control system, covering emergency, non-emergency, and internal calls, incident handling, and dispatch. Its July 2013 announcement described an environment handling 12,000–15,000 calls a day with more than 2,000 operators; those figures describe that historical operating context.
Northrop Grumman: Metropolitan Police CommandPoint announcement, July 23, 2013 ↗Why software quality mattered
Emergency-call technology must preserve an incident’s details while coordinating operators, resources, and dispatch decisions under pressure. The proposed platform included resource management, geographic information, and mobile capabilities. For such an environment, testing needs to examine the complete operational workflow rather than a collection of isolated features.
Northrop Grumman: Metropolitan Police CommandPoint announcement, July 23, 2013 ↗REPORTED ENGAGEMENT
Our reported contribution
Ji Tech reports vendor testing experience supporting Northrop Grumman on Metropolitan Police 999 technology. The reported quality contribution was to help identify software issues in a mission-critical environment. Engagement dates, components, and individual test deliverables remain to be documented; no operational rollout or response-time improvement is attributed to Ji Tech.
TESTING & MISSION READINESS
How testing helps the program move forward
The priorities below are an analysis of the public system context, not a verified list of tasks completed on this engagement.
Incident-to-dispatch continuity
Check that call details, locations, priorities, and updates remain consistent as a scenario moves between users and systems.
Concurrent and exceptional scenarios
Exercise busy periods, simultaneous updates, interrupted connections, and recovery without losing or duplicating an incident record.
Evidence for acceptance
Make defects reproducible, verify corrections, and show unresolved risks against the operator workflow before a release decision.
The goal: find defects earlier, verify corrections, and give stakeholders evidence for release decisions. Testing reduces risk; it does not guarantee defect-free software.
PUBLIC PROGRAM RECORD
The delivery record matters
The London Assembly’s October 2017 review records that the original £90 million contract entered into in 2014 was terminated in March 2016 after delays. The earlier announcement described an intended solution, not proof that it went live. This page presents testing experience in that context and does not claim successful delivery of the original replacement system.
London Assembly: Who’s paying the bill?, October 2017, section 4.7 ↗Discuss related capabilities
Explore Ji Tech’s services for a similar mission. These links describe current capabilities and do not add unverified deliverables to this project record.