Hosted or in-house: questions to ask about a utility server

Every flexible exports, emergency backstop or dynamic connections programme needs a CSIP-AUS utility server. One of the first decisions a network makes is whether to build and run that server itself or have it hosted.

There is no single right answer. These are the questions we suggest teams work through, whichever way they decide.

Who looks after it after go-live?

A utility server stays in service for as long as the fleet it serves. Someone has to watch it, keep it up to date and answer the call when something looks wrong, in the middle of summer as well as the quiet months.

How will it grow with the fleet?

New device models, new programmes and steady growth all arrive over time. It helps to know early how the service will take that on without a rebuild.

How will partners get connected?

Manufacturers and aggregators need a clear path onto the programme, somewhere to test, and someone to talk to when things don’t work first time.

How will it fit around your own systems?

Your DERMS or envelope engine, identity, data platform and monitoring all need to work with the server, not around it.

What does your team want to spend its time on?

For many networks the answer is the programme itself: the customers, the envelopes and the outcomes for the network.

If you are working through these questions now, we would be glad to compare notes.