School & Campus Operations
A missed punch can become a register dispute. A late bus can become a queue of worried calls. A new smart board can become another disconnected tool. Connect the signal to the person who can resolve it—not just another dashboard.
Connected Campus is a separately ordered integration service, not part of the base ERP subscription. Your approved order specifies the devices and services to connect, staff responsibilities, delivery dates and checks that must be passed and accepted before your agreed launch.
Connect attendance, transport and classroom technology to the decisions your people make every day. Your separately ordered rollout turns the selected uses below into an agreed, tested way of working.
The problem
Devices spread across vendors and campus zones leave staff chasing the wrong person when a signal disappears.
Connect the list of devices, their locations, current status and support contacts to the agreed process for handling unexpected or missing events.
The problem
Uncertain identity matches and records uploaded late can leave teachers resolving attendance differences during lessons.
Apply the agreed rules for repeated scans and identity matching. Send uncertain events for review, update attendance from accepted events and retain the decision history.
The problem
A map alone cannot explain the delay, name the person checking it or tell families when the next update will come.
Bring the selected route updates into an agreed response: name the responsible person, record the reason, identify who takes over if needed and approve the message to families.
The problem
A board, device and learning app can still leave a teacher repeating the same roster, attendance and assignment context.
Start from the assigned class and learner context, then connect the selected tools to attendance, learning and communication actions.
The problem
Identity and location data should reach the people who need it—not everyone who can open a dashboard.
Agree the minimum data needed, who may access it and how long it is kept for each use. Keep provider passwords and access keys outside everyday user screens.
The problem
A working device is not an operating service until someone owns network failures, uncertain records and staff support.
Agree the checks that must pass before launch, practise what staff do when something fails, train the responsible team and name the hardware, provider and BCO support contacts.
The connected classroom story is not more screens. It connects a classroom event to the teacher, administrator or support team authorised to respond, with clear rules and responsibility.
Receive an agreed device event, route update or staff action.
Check what happened against your campus rules, agreed limits and staff permissions.
Name who will act, why and by when.
Keep the action and result before changing the automatic rules.
Choose the workflows that matter, then commission the device and provider integrations around them. Your order defines the scope, schedule and acceptance criteria; the agreed solution is configured, tested and accepted before go-live.
Connected Campus is a commissioned integration service, separate from the base ERP subscription. The approved proposal and order define the included hardware, provider services, integrations and delivery dates.
Your proposal itemises hardware, connectivity, installation, warranty and provider usage. These are separate unless expressly included in your approved order.
Yes, where the selected models support the agreed integration. We assess the device model, the supplier’s connection method, the data it provides and support responsibilities before including the integration in your order.
Connected Campus is a commissioned integration service, separate from the base ERP subscription. Your order sets device and provider scope, delivery dates, responsibilities and acceptance criteria. The agreed integrations are configured, tested and accepted before the agreed launch.
Demonstrations and initial tests use fictional or institution-approved test data. Your implementation plan defines the minimum data, consent, permitted access and storage period needed for the selected use.