09 / Campus infrastructure

Digital and physical infrastructure

Some things belong in the cloud and some belong on campus. Labs, classrooms, local networks and the systems that must keep working when the internet does not, all sit on your ground. Records, backups and anything the public touches are usually safer in the sovereign cloud.

We design, build and operate the on-campus side: smart classrooms and labs, and a compact data centre in a single engineered rack, connected to our sovereign cloud for backup, recovery and public services. We are specific about what each part can and cannot do.

The problem we solve

Campus server rooms are often a converted store cupboard with a domestic air conditioner, no fire suppression and a UPS that lasts four minutes. Hardware is bought project by project, with no common design, no monitoring and no one accountable at 2 a.m. Labs are built for teaching and then fail when used as exam centres, because the network, power and seating plan were never designed for it. Smart-classroom equipment bought under a grant sits unused because no one was trained. And when an auditor asks where the backups are, the answer is a disk in the same room as the server.

What you have at the end

  • Classrooms and labs that are used, supported and fit for both teaching and examinations.
  • An on-campus compute rack with defined power, cooling, security and monitoring, instead of an improvised server room.
  • A written split of what runs on campus and what runs in the sovereign cloud, and why.
  • Off-site, immutable backups and a tested recovery plan for everything on campus.
  • One accountable operator, with clear responsibilities between our team and yours.
  • Asset and utilisation records that support NAAC Criterion 4 evidence.

Scope of service

01

Smart campus and labs

We design and set up smart classrooms, computer labs, language labs and specialised labs as working teaching spaces: display and capture equipment, lab networks, managed endpoints, and the training that gets them used. Campus-wide network and Wi-Fi planning sits with our CIO-as-a-service team; this service builds and runs what the plan calls for.

Deliverables

  • Room and lab designs with equipment schedules
  • Installation, commissioning and acceptance testing
  • Endpoint management and lab imaging
  • Faculty and lab-assistant training
  • Asset register and utilisation reporting for NAAC Criterion 4
02

A data centre in a rack, on campus

A single, enclosed rack engineered as a small data centre: compute and storage nodes, network switching, a UPS sized to your load, in-rack or close-coupled cooling, fire detection and suppression, access control and environmental sensors, all monitored remotely. It runs the services that need to be local, such as exam-centre servers, lab systems, campus identity caches and building systems, and replicates backups to the sovereign cloud. It is not a Tier-rated facility and does not replace off-site disaster recovery. A reference specification, power range and lead time are given after the site survey, not as published figures on this page.

Deliverables

  • Site survey: power, earthing, floor loading, heat load and access
  • Engineered rack design with power and cooling calculations
  • Installation, burn-in and acceptance tests
  • Remote monitoring of power, temperature, humidity, door and hardware health
  • Backup replication to the sovereign cloud and a tested restore
03

Power, cooling and site readiness

Most on-campus failures are electrical or thermal, not digital. We specify the dedicated circuits, earthing, UPS runtime and generator changeover the equipment needs, and the cooling that matches its heat load. Where your building cannot support it safely, we tell you and propose an alternative.

Deliverables

  • Electrical and cooling requirements for your electrical contractor
  • UPS and generator changeover specification
  • Site-readiness checklist signed off before installation
04

Exam-ready labs and centres

Labs that also serve as examination centres need more than computers: locked-down endpoints, isolated networks, seating plans, CCTV coverage where required, and power that lasts the exam. We design labs to meet the requirements of our examinations service and of the external bodies whose exams you host.

Deliverables

  • Exam-mode endpoint and network configuration
  • Seating and invigilation layouts
  • Pre-exam readiness checks and a day-of runbook
05

Hybrid connectivity to the sovereign cloud

The rack and the cloud work as one system. We connect them over encrypted links, keep identity and directory services in step, and decide service by service where each workload lives, so a link outage degrades the campus gracefully instead of stopping it.

Deliverables

  • Workload placement decision record (campus or cloud, with reasons)
  • Encrypted site-to-cloud connectivity with failover
  • Synchronised identity, logging and time sources (CERT-In log retention in India)
06

Managed operations and maintenance

We operate what we install, with remote monitoring, patching, hardware replacement and periodic preventive maintenance. Physical tasks on site are carried out by trained institution staff or a local field engineer, and the division of responsibility is written down before go-live.

Deliverables

  • Responsibility matrix (Bit2Bit, institution, contractors)
  • Monitoring, patching and incident response
  • Preventive maintenance schedule and reports
  • Service levels as agreed in the contract. Standard figures are not published on this page.

How an engagement runs

  1. 01

    Survey

    We visit the campus, inspect rooms, labs, power and cooling, and list what exists, what works and what is unused.

  2. 02

    Placement and design

    We agree what runs on campus and what runs in the cloud, then design the labs, classrooms and rack around that split.

  3. 03

    Site readiness

    Your electrical and civil contractors prepare the site to our specification. We do not install until readiness is signed off.

  4. 04

    Install and prove

    Equipment is installed, tested under load and accepted. Backups are replicated to the cloud and a restore is demonstrated before handover.

  5. 05

    Operate

    We monitor and maintain the estate under a managed service, with quarterly reviews of utilisation, incidents and capacity.

Who this is for

Regulations covered

Questions, answered

Why keep anything on campus if you run a sovereign cloud?

Because some services must keep working when the internet link fails: exam-centre servers, lab systems and local identity. Everything else, including records, backups, recovery and public-facing services, is usually better in the cloud. We decide service by service and write down why.

What does the rack need from our building?

A secure location, dedicated electrical supply with proper earthing, generator backup if you want the rack to ride through long outages, and enough space and airflow for its cooling. The site survey gives you exact figures. If your building cannot meet them, we will say so.

Is the rack a substitute for disaster recovery?

No. A single rack on one campus is a single site. Disaster recovery comes from immutable off-site copies in the sovereign cloud and a tested restore, which we set up as part of backup and archival.

Who looks after it day to day?

We monitor and manage it remotely. Physical work such as replacing a disk or resetting a breaker is done by trained staff on your side or a local field engineer, as agreed in the responsibility matrix.

Can you work with hardware we already own?

Often, yes, if it is supported and in reasonable condition. The survey tells us what can be reused and what should be retired.

Book a free compliance and infrastructure audit.

A senior consultant reviews your data, systems and regulatory position with your team and gives you a written gap report. There is no cost and no obligation to buy anything.

A senior consultant reviews your data, systems and regulatory position with your team and gives you a written gap report, at no cost.