User Tools
Writing /app/www/public/data/meta/onboarding/ticketer/introduction_to_mobile_ticketer_-_crown.meta failed
onboarding:ticketer:introduction_to_mobile_ticketer_-_crown
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| onboarding:ticketer:introduction_to_mobile_ticketer_-_crown [2017/02/22 14:29] – adowling | onboarding:ticketer:introduction_to_mobile_ticketer_-_crown [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Introduction to Mobile Ticketer - Crown ====== | ||
| + | --- // | ||
| + | Note: Crown Castle is no longer a customer of Errigal. | ||
| + | |||
| + | < | ||
| + | In order to get a detailed overview of the Preventative Maintenance please first read the following wiki entry: [[onboarding: | ||
| + | |||
| + | 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: **/ | ||
| + | |||
| + | ==== 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/ | ||
| + | (Note: You can only manage co-location from an open ticket. A closed ticket will not provide the Add co-located remote button). | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | **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. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | **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. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | </ | ||
Page Tools
