Run it across the whole group
Comparing sites only means something when they mean the same thing by the same word. Standard definitions across the estate, local control where it belongs, and one roll-up finance can trust.
Roll-up across the group
7 sitesNeoGen Group
Organisation
1642
7 sites
West
Region
877
4 sites
South
Region
765
3 sites
What rolls up, and what does not
Roll-up that reconciles
Cost, compliance and backlog aggregate from site to region to group, from the same underlying work orders.
Permissions that hold
What someone can see and do follows their role and their site, and changes when either of those changes.
Governance up front
Retention, residency and export are set at deployment to match your regulator, not our default.
Who can do what, and where
Those are two different questions. A manager at one site should not be approving spend at another.
- Role decides the action: view, raise, assign, close, approve
- Site decides the scope of what that role can see
- A move between sites changes access without raising a ticket
Permissions
4 roles| View | Raise | Assign | Close | Approve | |
|---|---|---|---|---|---|
| Requester | |||||
| Technician | |||||
| Manager | |||||
| Director |
Requester2 of 5
Can seeTheir own buildingTechnician3 of 5
Can seeJobs assigned to themManager4 of 5
Can seeTheir siteDirector5 of 5
Can seeThe whole region
Signing in
A second password to reset is a second reason not to use the system.
- People sign in with the account they already have
- Joiners and leavers handled from your directory
- A leaver loses access the day it is recorded, not at the next audit
Signing in
[Replace] providerSingle sign-on
Your existing identity provider
People use the account they already have. No second password to reset.
Automatic provisioning
On joining and leaving
A leaver loses access the same day HR records it, not at the next audit.
Enforced by group
Role from directory group
Moving someone between sites changes what they see, without a ticket.
The named provider is a deployment decision — confirm yours with us on the call.
Governance you set, not us
Retention and residency are compliance decisions. They should not be a vendor default you discover later.
- Record retention set to match your regulator
- Data residency chosen at deployment and fixed for your tenancy
- Export any period, any scope, in a format you can read without us
Governance controls
Set at deploymentRecord retention[Replace] years
Set to match your regulator, not our default.
Where data is stored[Replace] region
Chosen at deployment and fixed for your tenancy.
Export on demandAny period, any scope
Your data leaves in a format you can read without us.
Change historyEvery edit attributed
Closed records are sealed; corrections are new entries.
Ready to simplify your maintenance operations?
Book a personalized demo and see how NeoGen CMMS fits the way your team already works.
Enterprise questions
Can each site keep working the way it does now?
Largely, yes. Schedules, crews and stores stay local. What gets standardised is the vocabulary — asset classes and priority levels — because without that, a group report compares things that are not comparable.
How do you handle a site we acquire later?
The same way as the pilot: import its assets, set its critical schedules, attach it to the region. It inherits the group definitions and keeps its own operating detail.
Who can see cost data?
Whoever you decide. Cost visibility is a permission like any other, and by default a technician sees the job, not the budget.
What are the [Replace] values on this page?
Retention period, data residency region and identity provider are set per deployment. They are marked rather than guessed, because the honest answer depends on your regulator and your IT estate.