Education
Campus infrastructure that holds up when everyone arrives at once
Universities and schools run estates and networks for a population that arrives and leaves in waves. The load is predictable by timetable and unforgiving when the timetable changes.
Context
Industry context
What shapes technology decisions in this sector.
Campus technology divides into infrastructure, connectivity and the software that people actually use. The three are usually procured separately and then have to behave as one environment.
Demand is timetabled rather than steady. Utilities, networks and access systems all see sharp changes at known times, which makes baselining useful and averages misleading.
Operational staffing is the constraint that shapes design. There are usually few operations staff relative to the number of buildings, so anything requiring constant attention will be worked around.
Constraints
Key operational challenges
The conditions any solution here has to work within.
- Campus utilities and buildings whose consumption changes sharply with the timetable.
- Networks that must serve many devices nobody centrally manages.
- Access control and safety systems usually managed separately from everything else.
- Limited operational staff relative to the number of sites.
Capabilities
Relevant ZouhThings capabilities
What we can bring to this sector, stated as capability rather than track record.
Digital infrastructure
Designed for campus-wide infrastructure — networks, connectivity and the systems that monitor buildings and utilities.
Connected campus systems
Can support bringing lighting, cooling, water, access control and safety equipment into one monitored environment.
Systems integration
Relevant where infrastructure, network and administrative software were bought separately and now need to exchange data.
Cybersecurity for open networks
Designed for environments serving many devices nobody centrally manages, where segmentation and access control carry the load.
Enterprise software
Can support the administrative and operational applications a campus runs on, including bilingual interfaces for staff and students.
Solutions
Relevant solutions
Solution areas that apply here. Each links to how it is delivered.
Platforms
Relevant platforms
Platforms that would apply to this sector.
- thethings.io
Applications
Example use cases
Possible applications, to show the shape of the work.
Campus utilities monitoring
Possible use cases include monitoring electricity, water and cooling per building against the timetable rather than as a monthly total.
Network and connectivity visibility
Can support seeing where connectivity is degrading across a campus before it is reported by users.
Access and safety system integration
May enable access control, lifts and fire-safety equipment reporting into one operational view.
Consolidated administrative software
Designed for reducing the number of separate systems staff have to reconcile by hand.
These are possible use cases, described to illustrate what the technology can support in this sector. They are not descriptions of completed work, and none should be read as a reference. Where a confirmed project exists, it will be named and linked under Related projects.
Security
Security considerations
What has to be decided early rather than added later.
Segmentation as the primary control
Relevant because a campus network carries many unmanaged devices; separating infrastructure from general access is the main defence.
Identity and access for a changing population
Designed for a population that turns over annually, so access provisioning and revocation are routine operations rather than exceptions.
Protecting administrative systems
Can support keeping administrative and student-record systems off the same path as open network access.
Update paths across many sites
Designed so infrastructure firmware and software can be updated across buildings without a visit to each.
This describes how we approach security in this sector. It is not a claim to hold any specific certification, accreditation or compliance attestation — where one exists, it will be named.
Integration
Integration considerations
Where the difficulty usually sits in this sector.
Existing building and network equipment
Designed for working with installed controllers, switches and building management rather than assuming replacement.
One environment from separate procurements
Can support normalising data from systems bought at different times by different departments.
Behaviour outside term
Relevant because a system tuned to term-time load has to behave sensibly when a campus is nearly empty.
Handover to a small team
Documentation and alert routing designed for the number of operations staff actually available.
Evidence
Related projects
Confirmed work in this sector, where any is published.
No project is published for this sector yet. When one is confirmed and approved for publication, it will appear here — so an empty section means exactly that, rather than work we cannot discuss.
Next step
Discuss a requirement in this sector
The useful conversation is usually about a specific asset, site or corridor rather than the sector in general.