Differences

This shows you the differences between two versions of the page.

--- onboarding:nocportal:understanding_of_change_management_views [2016/09/30 12:19] – adowling
+++ onboarding:nocportal:understanding_of_change_management_views [2021/06/25 10:09] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Understanding of Change Management views ======
+Author/Assessor: Anna Dowling.
+Note: Crown Castle is no longer a customer of Errigal
+<del>***** **Change Management is currently only used by Crown Castle and should be tested using their data** *****
+The Change Management preferences can be located in the View Preferences window as previously described in [[onboarding:nocportal:understanding_of_preventative_maintenance_views|Understanding of Preventative Maintenance views]].They are labelled Change Management.
+{{:onboarding:nocportal:screen_shot_2016-09-30_at_11.43.32.png|}}
+In order to fully understand these views, we must discuss how the information is retrieved. Once again, this uses the same process as the previous section for [[onboarding:nocportal:understanding_of_preventative_maintenance_views|Understanding of Preventative Maintenance views]]. The SQLQuery domain is utilised to stored the queries related to this view.
+===== Open Change Requests =====
+  * The query used with the Open Change Requests checkbox is the **Default Open Change Request Tickets in Cluster Query**. As you may have noticed the results are pulled on a          per cluster basis, which ties in with the cluster selection which we do for map navigation.
+This query finds all network elements in the specified clusters/markets that have an open change request
+ticket.
+  * The query returns the hub names of all hubs with open change requests and the date scheduled for the start of the change
+    activity. Tickets are defined as open as long as their closed_date is null and all the returned information is taken from the f_change_request form.
+  * At a hub level, the **Default Change Request Ticket Details Query** is used. This retrieves the details of open change requests on a specified hub.
+===== Starts within next 48 hours only =====
+As the names suggests, this narrows results to change requests which have a start date of the next 48 hours set on the f_change_request form.
+===== Show Off-Air NE =====
+This allows us to view change request ticket results for network elements which are currently marked as off air. These will display on the map with two black stripes through the marker as demonstrated below:
+{{:onboarding:nocportal:screen_shot_2016-09-30_at_12.05.37.png|}}
+===== Change Request Markers =====
+As demonstrated above, change request markers are configured in blue. If you double click on the marker this provides ticket information, ticket status and form related information from the change_request form.
+{{:onboarding:nocportal:screen_shot_2016-09-30_at_12.11.02.png|}}
+Assessment:
+  - Find a cluster which returns tickets for open change requests using the **Default Open Change Request Tickets in Cluster Query**.
+  - Navigate to that cluster in the NOC Portal and select the Open Change Requests checkbox from the Change Management View Preference.
+  - Open a marker and retrieve the ticket_id.
+  - Locate that ticket in the Ticketer application and compare the results from the Change Request form to that displayed in the portal.
+  - Explain how the Queries mentioned above are configured for the Noc Portal.
+  - Explain how an off-air network element would display in the Noc Portal and provide an example.</del>

Sidebar

Internal Errigal Collaboration Wiki

Differences

Sidebar

Internal Errigal Collaboration Wiki

User Tools

Site Tools

Differences

Page Tools