PSUs

Built To Survive The Tender, And Still Work As One System After Award

A public sector undertaking buys like a company and is examined like a public body. Since 1997 we have been building the networks, data centres, control rooms and plant infrastructure behind Indian PSUs, and Cisco named us its Public Sector Partner of the Year in FY24 and again in FY25.

The file outlives everyone who worked on it. Three years after commissioning the question is what was bought, against which specification, and what shows that it was installed. It rarely reaches the people who answered it at the time. We build the record while we build the network, so the answer is a document rather than a reconstruction.

New capacity creates a standardisation problem. A new unit, a new terminal and a new renewable site each arrive needing the same layer underneath, and each can arrive with a different integrator, a different design and a different support arrangement. We set the common standard first, then apply it across sites without replacing what still works.

Where systems are notified as protected, the network has to prove things about itself. NCIIPC is the national nodal agency for Critical Information Infrastructure under Section 70A of the Information Technology Act, and a computer resource becomes a protected system when it is notified under Section 70. Where those obligations apply we translate them into zoning, controlled administrative access, logging and tested recovery, and we state what each control does to the operating path before it goes in, because a plant network runs on the shutdown calendar rather than the IT one.

One standard across sites built decades apart. Most PSUs run infrastructure assembled over successive plan periods, with a different integrator and a different generation of equipment at each location. Consolidating that onto one design is where the running cost actually falls. We survey what is already there, publish what passes certification, and replace what genuinely has to be replaced.