Requirement
A group runs online operations across several regions. Regional teams procure and maintain devices independently, with accounts, images and operational data spread across spreadsheets and chat threads. The group wants a shared platform while preserving regional autonomy.
- Three-level permission structure: group, region, team;
- Unified instance and image management with batch operations;
- Aggregated operational data with cost attribution by region;
- Integration with the existing ticketing system.
Solution structure
The platform carries the group structure through tenancy: the group is the top-level tenant, regions are sub-tenants, and teams are authorised by role beneath them. Instances, images and tasks are managed inside tenant boundaries, with aggregated data shown at group level.
Technical highlights
- Tenancy and tiered authorisation mapped to the organisation;
- Batch tasks by group for configuration, applications and image switching;
- OpenAPI integration embedding provisioning and recycling into ticketing;
- Metering and attribution supporting internal settlement.
Implementation
A pilot with headquarters and one region validates the permission model and ticketing integration; expansion then follows, focusing on image standardisation and legacy device migration.
Outcome structure
Operations move from per-device manual work to grouped batch execution; permissions follow organisational changes, reducing orphaned accounts; usage data aggregates by region for cost attribution. Actual results depend on real project data.