Successful Completion of Work order
- R
- D
- S
As is Script
- R
Rick, The Network Admin @ Verizon is going about his day, when he identified that some of the routes on his network aren’t performing to expectations in the OSDMC application
- 10 - 15 minutes later...
- R
He investigates the downgrade and identifies the problematic pathways.
These “next hop peering call flows” are better alternatives to these problematic pathways. - 10 minutes later...
- R
- D
Rick creates a spreadsheet of updated pathways for these routes and hands the spreadsheet off to Devika, one of his network operations specialists.
- D
- R
Using the spreadsheet provided by Rick, Devika , Network Operations Specialist @ Verizon begins the process of updating the LRTs on the affected SBCs to fix the affected call flows.
- 20 minutes later...
- D
Devika, using a CLI, updates the routes one by one for each targeted device.
- 8 hours later...
- D
8 hours later, Devika has finished adding all these new pathways to the targeted devices and approved the Change Request to initiate the work order in the Work Order Admin page.
The work order goes through several manual processes like - Ready > Running then Complete.
- 120 minutes later...
- R
After successful completion, Rick has to manually committe the work order and roll out all the changes to the devices.
This process is tedious, time consuming, and inefficient.
Future Script
- R
Rick, The Network Admin @ Verizon is going about his day, when he receives a notification in the new OSDMC software, that some of the routes on his network aren’t performing to expectations.
- 5 minutes later...
- R
The system automatically identifies the problematic routes for him, and suggests a recommendation containing a series of updates to meet the service-level agreements.
- 2 minutes later...
- R
Rick approves the proposed changes, and submits a Change Request with these recommended changes.
- D
- R
A notification is sent to Devika , Network Operations Specialist @ Verizon in the new OSDMC Software, that a new Change Request has been approved by Rick and is ready for implementation.
- 2 minutes later...
- D
Devika begins the process of updating the network function devices in the new OSDMC application.
- 5 minutes later...
- D
After reviewing the automatically generated list of affected devices, Devika approves the Change Request and initates the work order in the Work Order Admin page.
- 10 minutes later...
The work order automatically goes through several processes like - Ready > Running then Complete.
After successful completion, the system automatically committe the work order and roll out all the changes to the devices. - D
- R
- S
Devika, Rick, and Sarah, The System Architect @ Verizon, receive a notification in the new OSDMC Software, regarding the progress.
This process was quick and intuitive for everyone.