Keep Agent Hive close to the network.
Your data centreConnect to ITSM, OSS, NMS and automation inside the boundary you control.
- Your identity and roles
- Approved read and execution connectors
- Change history kept locally
The same research, applied to each domain’s evidence, rules and owners.
A worked example: a parameter change across a cluster of radio sites, planned against live network state and vendor rules, run in an approved window and closed only when service data confirms it, or an approved rollback restores the network.
The questionCan we roll out the new handover parameters to cluster 14 tonight, and how will we know it worked?
Start with the target, scope, maintenance window and rollback plan.
Pull in current state, recent changes, vendor rules, licences and service health.
Look for missing dependencies, unsupported combinations and policy exceptions.
Create target-specific commands, the schedule and clear recovery steps.
Compare KPIs and alarms after the change with the agreed baseline.
Keep a verified result, or run the approved rollback and check again.
Proceed on 20 cells. Site 14-10 runs software 20.9 without the handover licence; it needs a specialist before it joins the change.
The accountable engineer can change, approve or reject the proposed action.
Missing prerequisites and unsupported combinations go to a specialist.
Your team sets the point where uncertainty stops the workflow and asks for help.
Service limits and change policy decide when, and by whom, the change is reversed.
The request, network state, vendor rules and service data stay in their systems. Agent Hive connects the pieces that matter for this change.
Agent Hive
Agent HiveThe request, scope, window and approvals.
Inventory, configuration, KPIs and alarms.
Supported features by version, licences and change policy.
The run closes only after service data confirms the result, or an approved rollback restores the network.
Sites, cells, software versions, features and licences, joined to the vendor rules and change policies that govern them.
A parameter on one cell touches its neighbours. Agents map the dependencies before the window, so the watch list covers every cell that can feel the change.
Test on representative cases, review the evidence and let specialists decide what is safe to reuse. The next run uses a clear, approved version.
| Question | v1 | v2 | v3 |
|---|---|---|---|
| Does software 21.4 support the new handover feature?Vendor rules | ✓ | ✓ | ✓ |
| Which cells in cluster 14 lack the licence?Prerequisites | ✗ | ✓ | ✓ |
| Does the window conflict with another change?Policy | ~ | ✓ | ✓ |
| Generate commands for site 14-07 onlyExecution | ✓ | ✗ | ✓ |
| Drop rate rose 0.4 pt after the change: roll back?Assurance | ✗ | ✗ | ~ |
| Who can authorise a rollback at 02:00?Policy | ~ | ✓ | ✓ |
| Missing baseline for two cells: proceed?Thin evidence | ✗ | ✗ | ✓ |
Normal changes, missing evidence, vendor differences, rollbacks.
Validation, sources, policy handling and proposed action.
Specialists accept, correct or reject rules and templates.
The next run uses only what was approved.
The workflow can run in your data centre or private cloud. Each environment gets its own connectivity, identity, model access and execution rights.
Connect to ITSM, OSS, NMS and automation inside the boundary you control.
Connect through approved network paths and choose which models each agent may use.
| Runs in | QpiAI managed environment | A dedicated network in your cloud | Your data centre (Docker / Compose) | An isolated network |
|---|---|---|---|---|
| Operated by | QpiAI | Agreed per engagement | Your team | Your team |
| Tenancy | Multi-tenant, isolated | Single-tenant | Single-tenant | Single-tenant |
| Data at rest | Managed environment | Your cloud and region | Your network | Inside the perimeter |
| Models | Managed models | Approved endpoints | Local, or via a policy gateway | Local models only |
| Outbound | Operated by QpiAI | Private connections | One controlled egress path (hybrid) | None |
| Identity | Your identity rules | Enterprise identity | SSO and RBAC | Local SSO and RBAC |
| Updates | Rolled out by QpiAI | Agreed per engagement | New image version, pulled | Signed offline packages |
| Audit | Audit history | Audit history | Local audit history | Local audit history |
Air-gapped Graph, agents and models run inside an isolated network; updates arrive as signed offline packages.