Who we work with

Education & Research

Education fleets are large, mixed, and provisioned in bursts — thousands of devices in the two weeks before a term, then almost nothing for months.

That rhythm punishes any process that needs a person per device. If enrolment is manual, the peak is absorbed by casual labour and overtime; if it is zero-touch, the peak is a delivery schedule. The difference is decided at purchase, not at deployment, because a device that was not registered to your organisation when it was supplied cannot be enrolled without somebody touching it.

The estates are also genuinely mixed. Apple in the creative and executive areas, Windows in administration, Chrome in classrooms, and a research population that will use whatever their field uses. Standardising all of it is neither achievable nor desirable — managing all of it to one standard is.

Research data is the part that gets underestimated. Pre-publication work, human research ethics data and industry-partnered projects carry real confidentiality obligations, and they typically live on devices with the least management.

Where the work goes

What we focus on in this sector

Scope is agreed per engagement. These are the areas that consistently carry the most value here.

01

Zero-touch at peak

Devices registered to Apple School or Business Manager and Android Enterprise at supply, so a term-start peak is limited by delivery rather than by labour.

02

One standard, several platforms

Apple, Windows and Android managed to a single operating standard and a single compliance report, rather than three consoles and three answers.

03

Research data in managed boundaries

Managed application and storage boundaries for sensitive research, on devices whose users have a great deal of autonomy.

04

Lifecycle discipline

Standardised models, tracked assets, planned replacement and sanitised disposal — the practices that make a constrained budget go furthest.

05

Predictable seasonal support

Support capacity planned against the academic calendar instead of a flat monthly average that is wrong twice a year.

Outcomes

What changes once it is running properly

  • A term-start rollout limited by delivery, not by build capacity
  • One compliance picture across a genuinely mixed estate
  • Research and student data inside a managed boundary
  • An asset register accurate enough to plan a refresh from
Services

What usually applies

A few of the organisations we have delivered for

Department of Defence
Department of Defence
Royal Australian Air Force
Royal Australian Air Force
Department of the Prime Minister and Cabinet
Department of the Prime Minister and Cabinet
Department of Foreign Affairs and Trade
Department of Foreign Affairs and Trade
Department of Home Affairs
Department of Home Affairs
Attorney-General’s Department
Attorney-General’s Department
Parliament of Australia
Parliament of Australia
Parliament of New South Wales
Parliament of New South Wales

Common questions

Can you handle a term-start peak?

Yes, and the way to handle it is to remove the labour from it. Devices registered to your organisation at the point of supply configure themselves on first boot, which turns a provisioning peak into a delivery schedule.

We have Macs, PCs and Chromebooks. Do we need one platform?

You need one operating standard, not one product. Several of our customers run more than one management platform deliberately; what matters is that compliance, patching and reporting are defined once and answered the same way for each.

How do we protect research data without obstructing researchers?

By putting the boundary around the data rather than around the person. Managed application and storage boundaries let a researcher work the way their field works while keeping the sensitive material somewhere the institution can account for.

Next step

Talk to us about Education & Research

Tell us what the environment looks like today. We will tell you honestly whether this is the right place to start.