Telecom
Network changes, checked before they run. Against live state and vendor rules.
We check a network change against the live network and the vendor’s rules before the window opens.
What is hard here
Reach.
Most network changes go fine. The ones that fail usually touched an element whose current state nobody checked.
What we have learned
One shared element can carry a change far past its cell list, so we trace impact through the topology. After the window, service is compared with its baseline before the ticket closes.
“Is it safe to push this parameter change to 40 cells tonight?”
What Agent Hive used
- sourceChange request CR-5512 · handover offset on 40 cells, cluster 7servicenow
- sourceLive state · 3 cells with open alarms, 1 incident in the last 48 halarms, kpi
- checkVendor rule · offset range −6 to +6 dB; 2 cells would exceed itguide p.214
- checkLicence · feature X2 active on 38 of 40 cellsinventory
- workflowImpact · 2 enterprise sites and 1 hospital on first-tier neighbourstopology
- resultProceed on 35 cells; hold 5 pending fixes. Sent to the change owner.needs approval
Figures
Impact is traced.
Point at a part no egress · signed bundles in · data stays inside
Worked examples