A campus is already a small power grid. Most are run from a dozen disconnected screens.

Many systems, no single view

A modern campus is a power network in miniature. Lecture halls, labs, server rooms, residences and sports facilities all draw at once, rooftop solar feeds in when the sun is up, a battery may sit in a basement, and a row of EV chargers fills overnight. The trouble is that each of these usually runs on its own controller, with its own screen, bought at a different time from a different supplier. Facilities teams end up watching half a dozen dashboards that do not talk to each other. Solar gets exported cheaply at noon, then grid power gets bought back at the evening peak, and a demand charge lands every month because nothing is timing the big loads against each other.

One layer that runs the whole site

An energy resource planning layer sits above all of it and runs the campus as one system. It watches every asset in real time, charges the battery from solar or cheap grid hours, then discharges it to flatten the evening peak. The same layer can island critical buildings if the grid drops, and it adapts on its own as term-time load patterns shift through the year.

Why 247 ERP fits a campus

247 ERP gives the estates team one screen for storage, generation, solar and the grid connection, with cost-first dispatch that shaves peak-demand charges automatically. Up to 20 conditions across 10 programs are set without writing code, and one installation scales to a whole estate of sites and substations as the campus grows.