Public Sector

Most departments run technology bought under four schemes, in four budget years, by four different agencies.

Each procurement was correct on its own. None of them was done together. So no single officer holds one list of what is installed across the district offices, what is still under OEM support, and what stops being supported inside the next two budget years. That is the question an auditor asks first and the one that takes longest to answer. It is also the question that decides whether a sanction is spent before 31 March or surrendered.

What SECCOM builds here. SECCOM builds command and control environments, department networks across districts, data centre white space, surveillance and access estates, and the field systems a city or a utility runs on. The work is specified against the standards a tender evaluator can check. It is handed over as documents you can check: an as-built drawing set, certification results for every link, a list of every feed and the department that owns it, and a list of every device with its serial number and the date its support ends. On an SITC scope that pack is the testing and commissioning evidence, and it is what the O&M years are afterwards measured against. Where the deliverable is a room, SECCOM designs it from the operator outward. Where the deliverable is a corridor, a ward or a feeder, SECCOM surveys what is already installed and measures a baseline first, so anyone can check later whether it actually improved.

Where SECCOM usually starts. Integrated Command and Control Centres (ICCC), Emergency and Crisis Operations Centres and Multi-Agency Coordination are the three that most often bring a department to SECCOM, because the room is the visible deliverable and the hard part is the interface list behind it. Sovereign and Regulated-Environment Security follows quickly, because the question that stalls a government programme is who can reach the data and what can be produced to prove it. Procurement, Fulfilment and Multi-Site Logistics is the fifth, and it is usually where a department finds out that its rollout is paced by the district office that can receive last.

Ask SECCOM to inventory the technology estate of one district office. What is installed, what is under support, what loses OEM support inside two budget years, and what can integrate with what. One office is usually enough to show the shape of the rest.

Proof. Pre-qualification decides who is allowed to bid at all. After that a government buyer asks for three things: past performance on comparable work, evidence that the OEM will stand behind the SI on this specific deal, and documents that survive audit. SECCOM's strongest answer to the second is Cisco Public Sector Partner of the Year FY24. It is not a badge. It tells a department that on a Cisco-based programme, Cisco itself is committed to the deal alongside SECCOM. Alongside it SECCOM produces OEM authorisation letters against the specific bill of materials, current specialisation letters, and the delivery documents named above. Where SECCOM holds no credential in an area, the page for that area says so.