Internal Errigal Collaboration Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Introduction to Mobile Ticketer - Crown ======
 --- //[[anna.dowling@errigal.com|Anna Dowling]] //

Note: Crown Castle is no longer a customer of Errigal.

<del>==== Introduction ====
In order to get a detailed overview of the Preventative Maintenance please first read the following wiki entry: [[onboarding:ticketer:ticketer_-_preventative_maintenance_introduction|Ticketer - Preventative Maintenance Introduction]]

As mentioned in the above entry, there are some differences between the Crown Castle and Extenet PM processes in relation to the mobile application. The main differences for Crown Castle are outlined below:

==== Workflows ====
  * Prev Maint Auto
  * Remote Acceptance

==== Acceptance Process ====

For Crown Castle, before a network element enters the PM process it has to go through an acceptance process. This happens when a new network element is added to the system. Quartz Jobs are used to manage this: **/Ticketer/quartz/list**. The ExternalElementUpdateJob (runs every 2 days) will create the external element entries for the new network elements, linked via the remote_id field. This job will also send an email indicating that an Acceptance ticket has been created and will need to be completed before the PM process can begin. The MaintenanceManagerJob (runs every 10 minutes) will then create the maintenance entry for the new network element.

==== Co-Location ====
Co-Location of an element is facilitated through the pm portal in the Mobile Ticketer and is actively used by Crown Castle. Co-location is for scheduling and bulk task purposes, and allows you to mark a unit(element) as co-located. When doing so, you can select additional units to also mark co-located. When complete, you can click Schedule Group/Create Tickets and the additional selected units will create tickets if they are not already yet created. 
(Note: You can only manage co-location from an open ticket. A closed ticket will not provide the Add co-located remote button). 

{{ :onboarding:ticketer:colocation.png |}}

**Adding Co-location**

Click Add co-located remote and use the selection menus to select a remote. When selected, you will be returned to the Co-Locate view, and the selected item will appear in the list. Once an element is added to a co-locate group, it will remain a member of the group indefinitely until manually removed. Click Schedule Group / Create Tickets to mark your ticket co-located, and create tickets, if necessary, for the additionally selected units. You will see your tickets button for Manage Co-Location now shows Manage Co-Location.

{{ :onboarding:ticketer:addtocologroup.png |}}

**Removing Co-location**

To remove an element from the co-locate group, simply open a ticket belonging to another member of the co-locate group, click Manage Co-location and click the remove icon (‘X’) at the far right of the element that you wish to remove. 

{{ :onboarding:ticketer:removecolocated.png |}}

</del>
Sidebar

Internal Errigal Collaboration Wiki

User Tools

Site Tools

Page Tools
