NJUNS Users Guide

NJUNS Users Guide 

www.njuns.com 

The National Joint Utilities Notification system, NJUNS, is a national organization of 

member utilities formed for the purpose of improving the coordination of joint ventures. 

Our system offers utility companies a method of obtaining up-to-date information on a 

variety of shared concerns, including Pole Transfers, Joint Trenching & Permits for New 

Attachments to Poles. 

Copyright © 2012 NJUNS, Inc. 1 

Revised March 2017

General Information 

NJUNS Web Site 

The NJUNS web site www.njuns.com, contains general information about the company 

and the login portal to all modules. Important information about the status of the 

system, training schedules, member code lists, director information, and new user 

registration can be found here. 

Login 

Clicking on Login or visiting https://www.njuns.com/app/ will take you to the login 

screen. Enter your username (email address) and password to sign in. 

If you check the Remember me box, the system will remember your Username but not 

your password. 

Home Tab/Main Ribbon 

Below is the main ribbon and a description of the purpose of each icon when selected. 

General 

Home: Initial screen when logging into NJUNS. 


Revised March 2017

Favorites: Allows a user to add a ticket or list of tickets to its window and 

access them quickly via the Favorites icon on the Main Ribbon. 

Windows (Tabs) 

Data 

Close All: Closes all open tabs 

Close All Others: Closes all open tabs, except the one currently in view 

Ad Hoc Queries: This is currently not available to users, unless given access. 

Queries: Accesses all searches. See Queries (Search) for a detailed explanation. 

Reports: Accesses all reports. See Reports for a detailed explanation. 

Dashboards 

Members: Allows users to search for member code information. 

Pole Attachment: Opens the main Pole Attachment tab, which is the starting 

point for working in this module. See Pole Attachment for a detailed explanation. 

Project: Opens the main Project tab, which is the starting point for organizing PT 

or PA tickets that you may have associated with a project. See Project for a detailed 

explanation. 

Pole Transfer: Opens the main Pole Transfer tab, also known as PT+, which is 

the starting point for working in this module. See Pole Transfer for a detailed 

explanation. 

Ticket Lists 

After opening the Pole Transfer or Pole Attachment Module, users can view tickets from 

different lists by clicking on the dropdown: 

Tickets of Interest 

(Default PT+) 

This list shows tickets that have been created or updated 

within the previous 30 days where the user’s member code is 

the Creator, Pole Owner or Next To Go Member. 


Revised March 2017

Tickets of Interest 

(Default PA) 

This list shows open or validated tickets where the current 

member code is the Licensee or Pole Owner and it has been 

updated in the previous 30 days. 

Draft Tickets 

This list shows tickets in Draft Status where the Creator is the 

user’s current member code. 

Next To Go Tickets 

This list shows tickets where the user’s member code is the 

Next To Go Member. 

Searching for a NJUNS Ticket 

Quick Search 

If you know the ticket number 

or pole number, the easiest 

way to search for a ticket is to 

enter the number in the Search field and click on the Search icon. Clicking on the 

magnifying glass will display a list of results that match your search. Clicking on the 

Jump to Button will open your result in a new tab. 

Your member code must be associated with a ticket to view it. 

Ticket number searches require an exact match 

to the ticket number (no wildcards). If you 

aren’t sure of the exact pole number, use the 

wildcards with your entry or use the Query 

function. Experiment with wildcards to see the 

different results available. 


Revised March 2017

PT+ Module 

Creating a PT+ Ticket 

1. Click the Pole Transfer icon. 

2. When the main PT+ tab opens, click on new. 

If the pole owner’s member code is not the same as the creator’s, type in the proper 

pole owner’s member code. If the code is unknown, search for the correct code or 

company name and click on the Search icon. Searching by company name provides a 

list of all member codes associated with that company. 

3. Click OK once the pole owner code is selected. A new ticket will open in a 

separate tab. 


Revised March 2017


Revised March 2017 

For a list of field definitions, visit Appendix B. 

4. Fill out the ticket header fields. The fields outlined in a red boarder are required 

fields. Once you are finished, click Save in the main ribbon to save the ticket to the 

NJUNS database. This is required before you can begin adding work steps to the 

ticket. 

NOTE: When the ticket is saved to the database, the Ticket Number and Created On 

fields will be populated. 

5. The Add New Instance icon in the 

steps toolbar is now active. To add a 

step, click on this icon. 

6. Steps represent the work that needs to be completed. Create the steps for a PT+ 

ticket in the order that they are to be performed in the field.


Copying a Step 

Open the step to be copied and click the Copy icon in the main ribbon or select the step 

and click Copy the selected instance in the step toolbar. 


Revised March 2017

The new step will open in a new tab. Make any necessary edits and save the step to the 

ticket. To insert the new step in a certain order, enter the order number in the Order 

field. Unless a specific order is listed, steps will be added in sequential order. To move 

the step up to its correct position, based on field conditions, see Reordering PT+ Ticket 

Steps below. 

Reordering PT+ Steps 

NJUNS allows the ticket creator or pole owner to reorder steps in two different ways. 


Revised March 2017

Opening a PT+ Ticket 

When the Ticket Creator or Pole 

Owner is ready to open the ticket, 

the Ticket Status must be changed 

from Draft to Open. Select Open 

from the Ticket Status field dropdown 

menu and click save. 

Email notifications will be sent to the Ticket Creator, Pole Owner and all step members 

when a ticket is opened. 

Updating PT+ Steps 

The Ticket Creator and Pole Owner can update information on any step. Step members 

can only update their own step information. To update a step: 

1. Select the appropriate step and click Open selected instance (or double click on 

the step). 

2. Make appropriate changes to the step information and click save. The pole owner 

and the step member will receive an email when step information is updated. 

Completing PT+ Steps 

When the work is completed in the field, it is imperative that the NJUNS ticket be 

updated as quickly as possible. Failure to update a ticket step causes the ticket to 

remain on your Next To Go list. 

1. Select the appropriate step and click on 

the Open icon (or double click on the 

step). 

2. When the step tab opens, click the status 

drop-down menu and change the status 

from pending to complete and save. 

Note: The bulk update feature can also be used to complete steps. View the Bulk Update 

Quick Guide for more information. 


Revised March 2017

Closing a PT+ Ticket 

PT+ tickets can be closed three ways; manually, auto-close and bulk update. 

Manually Closing a PT+ Ticket 

1. Open the ticket and select 

the ticket status drop-down. 

Change the ticket status from 

Open to Closed. 

2. Click save to save the 

changes. 

NOTE: Only the ticket creator and pole owner can close a PT+ ticket. Tickets can 

only be closed after all steps are completed. 

Auto-Close 

Auto-close allows the ticket to close immediately after the last job step is completed, 

based on the Pole Owner’s member code. The auto-close feature will be from an ongoing 

basis, once turned on. Any previous tickets that are ready to be closed, will need to be 

manually closed. If you are interested in utilizing auto-close for your member code, 

email support@njuns.com. 

Bulk Update 

The bulk update feature can be used to Close tickets. View the Bulk Update Quick Guide 

for more information. 


Revised March 2017

Canceling a PT+ Ticket 

Canceling a ticket differs from closing one. Canceled should be used only to remove 

duplicate tickets or to remove tickets which are no longer required, from active status. 

Closing a Ticket should continue to be used to indicate that all work was completed in 

the field for that ticket. 

NOTE: Only the Creator and Pole Owner can cancel a ticket. 

1. Open the ticket and select the ticket status drop-down. Change the ticket status 

from Open to Cancelled. 

2. A Cancel Ticket Comment box will appear. This is a required field. 

3. Enter the reason for the ticket cancellation in the text box and click Save. An 

email notification will be sent to the creator, pole owner and all step members that the 

ticket has been cancelled. 


Revised March 2017

Adding Comments and File Attachments 

Adding Comments 

Comments may be added to a ticket by selecting the Comments tab on the ticket. A list 

of existing comments, if any, will appear with the newest at the top. 

Click on the Add New Instance icon to add a new comment to the ticket or project. 

The Priority and Text fields are both required to create a comment. Give the comment a 

priority using the drop-down menu. Enter text in the text box and click Save. Email 

notifications are sent to all members on the ticket when a comment is added. 

Adding File Attachments 

Users can attach photos, maps, word documents, spreadsheets and other items to a 

ticket or project. Click on the File Attachments tab to open a list of current file 

attachments for the ticket. To view an existing attachment, select it and click Open (or 

double click). 


Revised March 2017

To add a file attachment, click on Browse your files or use the drag and drop feature. 

Multiple file attachments can be added to the ticket at once. 

Once file is in the pending uploads section, comments can be added. When you are 

ready to upload the file(s), click on the upload icon. 

Email notifications are sent to all members on the ticket when a file attachment is 

added. 

NOTE: The maximum File Attachment size is 5 MB per attachment. File attachments 

will not be included in the email notification. 

Disputes 

The Dispute tab is designed for the Ticket Creator, Pole Owner or Step Member to add a 

dispute to a step, if there is an issue with that step. 

1. Open the step to be 

disputed. 

2. Click the Disputes Tab. 

3. Click the Add New 

Instance icon to add a 

new dispute. 


Revised March 2017

4. Select a dispute reason. This is a required field. See below for a list of dispute reason 

codes. 

5. Describe the dispute in the detail field, which is also a required field. 

6. Click Save. An email is sent to the Pole Owner and Step member and there is now an 

active dispute on the step. 

7. Notes can be added in the Conversation section of the dispute to document or discuss 

items. 

Note: An automated DISPUTE step is created when the dispute is added. For more 

information, visit our Dispute Process Quick Reference Guide. 

Project Module 

Creating a Project 

The Project module is designed as a folder to group tickets together however the 

individual member desires. It is strictly an organizing tool for tickets and not required. 


Revised March 2017

Tickets can be associated with multiple projects, so each facility owner can group their 

tickets as needed. 

NOTE: The Project List will show all projects that have 

been created or updated within the previous 365 days for 

the current code. 

1. Click the Project icon under Dashboards. The 

main Project screen will appear in a separate tab with a list of current Projects. 

2. Click New to create a new project. 

3. A new Project 

tab will open. 

Complete the fields 

to create the project. 


4. Click on the New icon or drop down arrow to create a new template or reuse an 

existing one. A template is not required but can be used to prepopulate certain PT+ 

header fields. 

5. Enter the information necessary to complete the template for your project. 


Revised March 2017


6. Click save to enter the template information in the database and associate the 

template with the PT+ Project. 

Adding Tickets to a Project 

You can toggle between the PT Tickets and PA Tickets tabs depending on which type of tickets 

you want to add to this project. 

1. To add existing tickets to a project, open the project and click on add existing 

instance icon from the toolbar. Search by the ticket number or use the drop down to 

search by tickets of interest or next to go tickets. Select the ticket(s) from the data 

grid and click Ok. 

2. To create new tickets, using the project information to help populate the ticket 

header, open the project and click Add new instance. 


Revised March 2017

Closing a Project 

1. Open the Project and select the 

Status drop-down menu. Change 

the status from Open to Closed. A 

project can be closed at any time, 

regardless of the status of the 

tickets. Closing a project does not 

affect the tickets within the project. 

2. Click Save. 

Canceling a Project 

1. Open the Project and select the Status 

drop-down menu. Change the status 

from Open to Canceled. A cancel 

project comment is required to cancel 

the project. 

A project can be canceled at any time, regardless of the status of the tickets. Canceling a 

project does not affect the tickets within the project. 

2. Click Save. 


Revised March 2017

Pole Attachment (PA) Module 

The Pole Attachment module allows an applicant to electronically request permission to 

attach to poles and provides the pole owner an opportunity to accept or reject individual 

locations and record make-ready costs per pole. After all locations are accepted or 

rejected, the pole owner can validate the permit. After the pole owner has granted permit 

validation, the applicant can approve the ticket and begin work when any make- ready is 

complete. 

Creating a PA Ticket 

1. Click on Pole Attachment from the Dashboards section. 

This will open the PA Ticket tab. 

2. Click on New to create a new PA ticket. A pop-up 

window will appear. Enter the member code of the pole 

owner in the text box and click enter. A new PA ticket 

for the selected pole owner will appear in a new tab. 

NOTE: The licensee/creator cannot be the same member code as the pole owner. 

3. Enter the information for the ticket header. 


Revised March 2017

For field definitions, visit Appendix B. 

4. Click Save to save the ticket header information. This will save the ticket to the 

database and assign a ticket number to the draft. 


Revised March 2017

Creating PA Steps 

1. In the steps section, click on Add new instance icon to begin adding steps to the 

ticket. One step for each pole should be created. 

For field definitions, visit Appendix B. 

2. Click Save once the step information is input. Repeat steps 1 and 2 for each 

individual pole location on the application or use the Copy icon to copy an 

existing step for modification. 

Copying a Step 

Open the step to be copied and click the Copy icon in the main ribbon or select the step 

and click Copy the selected instance in the step toolbar. 


Revised March 2017

The new step will open in 

a new tab. Make any 

necessary edits and save 

the step to the ticket. To 

insert the new step in a 

certain order, enter the 

order number in the 

Order field. Unless a 

specific order is listed, 

steps will be added in 

sequential order. To move the step up to its correct position, based on field conditions, 

see Reordering PT+ Ticket Steps below. 

Deleting a Step 

A step can be deleted from a ticket when 

the ticket is in draft status. Highlight the 

step to be deleted and click on the delete 

icon. 

A pop-up will appear asking to confirm 

the deletion of the step. Click Yes to 

delete the step(s). 

Opening a PA Ticket 

When the Ticket Creator/Licensee is 

ready to open the ticket, the Ticket 

Status must be changed from Draft to 

Open. Select Open from the Ticket 

Status field drop-down menu and click 

save. 

Emails will be sent to the Ticket Creator, Pole Owner and all step members when a ticket 

is opened. Now the pole owner can accept or reject location steps, add make-ready costs 

and grant permit validation for the ticket. 


Revised March 2017

Validating a PA Ticket 

After the attachment request is received, the pole owner/alt. pole owner can edit certain 

fields on the ticket. The Step Status needs to be changed from Awaiting Approval to 

either accepted or rejected and any make-ready costs for the individual pole should be 

added also. 

Updating a PA Step 

The Pole Owner has two options for updating steps in PA: 

1. Open each individual step and accept/reject by updating the step status. 

Click save to save the update the step. 

2. If a PA ticket has many steps, the 

pole owner has the option to mass 

update these steps, by using the execute 

action icon. 

Accept Selected 

This allows users to bulk accept the SELECTED 

steps. 

Reject Selected 

This allows users to bulk reject the SELECTED 

steps. 

NOTE: The pole owner/alt. pole owner must accept or reject every location 

before the permit can be validated. 


Revised March 2017

Permit Info 

The Permit Info section of the ticket is where the pole owner and alternate pole owner 

can list the permit number for the application. The permit number can be added at any 

time, prior to ticket validation. If a conditional approval is allowed by the pole owner, 

the permit number can be entered and the ticket not validated until after the final 

inspection of the attachment. 

Before changing the Ticket Status to Validated, any discussion on make-ready 

requirements and costs should be finalized and agree upon by both parties. 

After all location information is acceptable to all parties, the pole owner changes the 

Ticket Status from Open to Validated. 

Validating a PA Ticket 

1. Click on the down arrow on the Ticket 

Status field to open the menu of 

selections. 

2. Click Save. An email notification is sent 

to all members on the ticket, notifying 

them that the ticket was validated. 

When the ticket status is changed to 

Validated, the Pole Owner Granted date 

will be populated by the system. 


Revised March 2017

Updating a Validated Ticket 

If changes must be made to a Pole Attachment ticket, including adding new locations, 

prior to approval by the applicant, the permit must be returned to Draft status by the 

pole owner before any changes to the Ticket Locations can be made. 

NOTE: After the applicant has approved the permit, no changes, other than Comments, 

can be made to the ticket. 

After the validation has been removed the applicant can make changes to existing 

locations or add new locations for review by the pole owner. When all changes have 

been made, the applicant must return the ticket to Open status so the pole owner will be 

notified of the completed changes. 

Approving a PA Ticket 

After a permit is validated, the applicant can accept the conditions and approve the 

permit. 

1. Click on the Ticket Status drop-down to open the 

menu of selections. Select the approved status. 

2. Click Save. An email notification is sent to all 

members on the ticket, notifying them that the ticket was 

approved. 

Closing a PA Ticket 

After a permit is approved, the applicant or pole owner can close the ticket. 

1. Click on the Ticket Status dropdown menu and select 

Closed. 

2. Click Save. An email notification is sent to all members on 

the ticket, notifying them that the ticket was closed. 

NOTE: Once a PA Ticket is closed, it cannot be reopened. 


Revised March 2017

Canceling a PA Ticket 

A PA Ticket can be canceled until it is in Approved status. 

1. Click on the Ticket Status drop-down menu 

and select Cancelled. 

2. Click Save. An email notification is sent to 

all members on the ticket, notifying them that the 

ticket was cancelled. 

Queries and Reports 

Queries 

Click on the Queries icon to open the input. 

The available queries are PT+ Search, PA Advanced 

Search, PT+ Close Search and PT+ Step Search. If your 

company or state has requested other special queries, they 

will be listed here also. 

Select the appropriate query and click Open, or double click. 


Revised March 2017

PT+ Search 

Enter information in the fields necessary to return your desired output. The only 

required fields are outlined in red, but you can enter as much data as you have/need. 


Revised March 2017

NOTE: County, Place, Job Type 

and Priority code cannot be chosen 

until the State is selected. 

Click on Run in the top left hand 

corner when you are ready to run 

the query. The results will appear in 

a data grid like the one seen in the 

ticket lists. Users can customize the 

data grids as needed by adding or 

removing fields, filtering, sorting 

and exporting to Excel. 

PT+ Step Search 

This query allows users to search for step information based off certain parameters. The 

only required fields are outlined in red, but you can enter as much data as you 

have/need. This query returns step information to the results screen. 


Revised March 2017

Reports 

NJUNS provides users with a selection of canned 

reports. Click on the Reports icon to open the list of 

available reports. Below we explain some of our 

reports in detail. For a document with all reports and 

queries, visit http://web.njuns.com/wp- 

content/uploads/Queries-and-Reports-Quick- 

Guide.pdf 

PT+ Aging Report 

The PT+ Aging Report provides the same information as the automated Monday Report. 

However, the days over can be varied between 0 days and 90 days. 

1. Enter one member code by either typing it or using the Select Icon. 

2. Use the drop-down menu to select the desired Days Over interval. If you leave 

this blank, you will pull 0 days over. 

3. If desired, enter a date range. 

4. Click Run to begin the report. Like all reports, PT+ Aging will load the data 

directly to Excel and save the results to your PC. 


Revised March 2017

The result is a multiple page report. The Table of Contents Page lists each report with a 

description of the results. Click on the blue hyperlink or use the worksheet tabs to open 

the pages. Each report viewpoint has a detailed data page and a graphical representation 

of the data page. 

PT+ Detail Report 

Then PT+ Detail Report is a data dump and returns all ticket information. 

The required fields are outlined in read; other fields are needed to set the parameters for 

the output. Each Member Code field will accept multiple values. The more information 

added, the narrower the resulting data output will be. 

a & b) Ticket From & Ticket To: For entering a ticket number range to narrow the 

resulting output. 

c & d) Created Date From & Created Date To: For entering the Created Date range 

for the report. 


Revised March 2017

e & f) Updated Date From & Updated Date To: For entering a range of dates for 

tickets updated. 

g) Ticket Status: must be selected from a menu of statuses. Click on the select icon 

to open the Selector menu. Users can select one or more statuses. 

h, i & j) Ticket Creator, Pole Owner & Next To Go Member: used to set the criteria 

for the report output. Enter one or more member codes in the appropriate fields either 

by typing them in, separated by a comma, or by using the select icon . 

k) State: For state information. 

l) County: For county information. 

m, n, o, p & q) Step information fields: Used for step member, step status, job type 

and step completed date fields to report on step information. 

Once you have entered the parameters needed, click Run to run the report. PT+ Detail 

will load the data directly to Excel. The result is a report listing all ticket fields with the 

auto filter turned on. Use the power of Excel to manipulate your data to the desired 

format. 

PT+ Next to Go (Separated into 2 different reports: Pole Owner and 

Step Member) 

The Next To Go Report provides the user with a list of tickets and the next to go step. It 

does not return the full ticket. Both reports are run in the same manner. However, the 

PT+ Next To Go – Pole Owner searches for where the member code(s) input are the pole 

owner and pulls those tickets. The PT+ Next To Go – Step Member searches for where 

the member code(s) input are the next to go step member. 


Revised March 2017

1. Enter the member code or codes 

desired. 

2. Enter state information if you choose. 

3. Select one job type from the dropdown 

menu if desired. 

4. Click Run to run the report. 

The PT+ Next to Go reports will load the data 

directly to Excel. The result is a report listing 

the ticket header information and the next to go 

step information. There is also a red worksheet 

tab called NTG Stats. This provides a 

breakdown of the data in the report. 

Appendix A 

______________________________________________________________________ 

Favorites 

Favorites allows users to pin tickets to a Favorites tab to easily access tickets. This is a 

temporary way to easily access tickets. 

1. Select the data grid row or rows to create a favorite tab. The Tab name will reflect the current 

entity you are selecting from, however this can be renamed. 

2. Click on the Favorites icon (lightning bolt) 

from the toolbar and click on New Favorites Tab or 

select an existing Favorites tab. 


Revised March 2017

NOTE: For your Favorites list to be saved upon your next 

login, make sure to “pin” the Favorites list. The push pin icon 

will be turned down and an orange color if the Favorites are 

pinned. 

Creating a Map 

Microsoft’s Bing Map program is currently used 

to create maps for attachment to projects or 

tickets. Click the Create Map link on the ticket 

header to begin the process. 

If a County and Place have been entered prior to 

creating a map, it will zoom into the region area 

of the county selected. 

Map Creation Tools 

Zoom in (1” = 25 m is max) to allow the push pin 

locations and line segments to be as accurate as 

possible. The final version will adjust the scale 

so that it fits on the viewing screen. Because 

this map is dynamic, the viewer can zoom in or 

out as desired to see the map. 

Depending on the quality of the aerial 

photography available, you may have to 

experiment with zoom levels for optimum 

viewing when using Aerial View or Bird’s Eye 

View to locate poles. 

The saved version of the map will not contain 

the aerial photography, but it can be re-added 

to view at any time the map is open Pan Tool: allows the user to scroll the map in any 

direction to locate the desired area 

Zoom Bar: (magnifying glass) zooms the map into the desired level of detail. This can 

be done using the zoom tools, double clicking on the map or using the mouse scroll 

wheel. The map will zoom into the selected area. 


Revised March 2017

Eyeball: allows the user to add features to the map and to turn off the street and road 

labels, as needed. If aerial photography is available for the area, click on Aerial View 

to make it appear. If 3-D photography is available, click on Birds Eye View to make 

that level of photography available. This gives a slightly angled view of the location that 

may help better locate poles. 

Add a Point on mouse click: is used for identifying pole locations. To indicate pole 

locations, select the Pushpin tool, move the cursor to the desired location and click the 

left mouse button. Repeat until all pole locations are indicated on the map. 

Add a Line Segment on mouse click: is used to illustrate buried facilities or project 

boundary lines, select the tool, move the cursor to the line’s starting point, click and 

release the left mouse button, move the cursor to the next point and click the mouse 

button again. Continue connecting the dots until the line or polygon has been completed. 

Find a Place: If you know the exact address of the pole location, you can type it into the 

Search text box (ex. 1037 Main St, Stone Mountain, GA) and click on the magnifying glass 

and the map will zoom to that point (1” = 200m). This operates similarly to a GPS location 

search. You can then zoom further in manually before adding points or lines to the map. 

Add pole locations or lines, as needed, to describe the area relating to the ticket and click 

Apply Changes to attach the map to the ticket. After attached, the map can be edited 

until the ticket is closed. Only the creator or pole owner can edit the map. 

Working with Data Grids 

A data grid is the method in which ticket and steps are displayed in lists within NJUNS. 

Data grids allow the user to customize the columns that are currently being viewed. 

Below shows an example of a data grid and the customizable options: 

1. Sorting: By clicking on the column heading once, the column will sort A-Z. If you click 

on it again it will sort Z-A. 


Revised March 2017

2. Adding/Removing Fields: By right clicking on any of the column headings, a menu of 

available fields will appear. The fields with a check next to them are currently being 

showed, but you can deselect and select to add and remove the fields. 

3. Filter: By clicking on the filter icon to the left of the column heading, a box will appear to 

allow to you filter on that field. 

4. Reorder Columns: By dragging and dropping the column headings, you can reorder 

them. 

5. Export to Excel: By clicking on the export icon (6 th icon on the toolbar), you will be 

given the option to export your results to Excel. 

The data grid icons are identified below: 


Revised March 2017

NJUNS Email 

Notifications 

NJUNS email notifications are 

plain text or HTML with a specific 

subject line with indicators on 

Ticket Type (New, Header or Step 

Updated, Step Added, Status 

Change, Comment Added, File 

Attachment Added, Disputed 

Step, etc.), Ticket Number, Status, 

Ticket Type and Next To Go 

Member Code. On new tickets, all 

listed member codes receive an 

email. Subsequent emails are 

delivered to the appropriate 

parties. Changes to ticket data 

will be indicated by striking 

through the original data and 

indicating the current data 

underlined next to it. 

Instance Tool Ribbon 

The Instance Ribbon is a menu that only appears when a user has a ticket or step open. 

Save and Save & Close: Both icons save the ticket or step you are working on. Clicking 

save will save the ticket or step and leave the tab open. Selecting Save & Close will save the 

ticket or step and close the tab you were viewing. 

Cancel: Clears any changes not saved to the tab that is in view. By clicking Cancel, the 

window will refresh and any unsaved edits will disappear. 


Revised March 2017

Refresh: refreshes the ticket or step that the user is viewing. 

Favorites: Add tickets to your favorites list. See favorites section for more information. 

More > 

Copy Instance: function duplicates the current item being viewed into a new instance of 

that item. If you have a step open and hit copy, it will copy the step information onto a new 

step tab. If you have a ticket open, it will copy the header onto a new ticket tab. 

Copy Link: copies a hyperlink of the ticket you have open to your clipboard on our PC 

Mail Link: brings up the user’s default Email program and inputs the hyperlink to the ticket 

in the body of the email. 

NOTE: The email recipients must be registered users of NJUNS to view the link because the 

system will require the recipient to log in before opening the ticket view. 

Clone: allows the user to copy an entire ticket, including steps, to minimize ticket creation 

time for multiple tickets that are similar. The ticket number is assigned and step information 

is copied. Make any changes necessary and save them the same way you would when creating 

a new ticket. Change the status of the ticket from Draft to Open. 

Send Message: allows a user to send an email notification from the system to different 

parties on the ticket and even those who are not on the ticket. 

Analytics: allows a user to see who has viewed the ticket. 

Audit History: allows a user to track all changes and updates made to a ticket. 


Revised March 2017

NJUNS Audit: allows a user to track updates, like audit history, on tickets from the legacy 

system. These are any tickets older than November 2012. 

Print: The Print icon allows the user to view the ticket. When viewing 

a ticket, click Print and it will bring up the printer friendly version in a 

separate window. 

From this window, the entire ticket can be viewed, printed or saved to a 

file in one of several formats. 

PT+ Module 

NOTE: All fields indicated with a red border are required. 


Revised March 2017

When first created, all NJUNS PT+ tickets are in 

“Draft” status. This allows the user to create and 

update the ticket without sending emails to all 

parties listed on the ticket until they are ready. 

Ticket Status 

Instance Reason 

Displays the current status of the ticket and will change as 

the ticket status is updated. 

A read-only field explaining the reason for the ticket being in 

a certain status. 

Ticket Number 

A read-only field that is populated by the system when the 

ticket is saved. 

Created On 

A read-only field that is populated by the system when the 

ticket is saved, stating the date the ticket was created. 

Created By Member 

Defaults to the member code of the user creating the ticket. 

This field is not editable 

Contact Name 

Defaults to the user’s name creating the ticket. 

State 

Defaults to the state assigned to the member code in the 

Database. 

County 

A required field. Type the first few letters of the county name 

in the field, or select it from the drop down. County must be 

selected prior to trying to select Place. 

Place 

Operates similarly to County for selection, but is not a 

required field. 

Latitude 

For the pole owner’s Y coordinate from whatever GPS or grid 

program they use to identify pole locations. 


Revised March 2017

Longitude 

For the pole owner’s X coordinate from whatever GPS or grid 


Start Date 

Date that work should begin on a ticket. It defaults to the day 

after the ticket is opened. This field is read-only. 

Next To Go Member 

A read-only field that will indicate the first pending step 

member on the ticket. The value will change as steps are 

completed. 

Next To Go Step 

Remarks 

Works similarly to Next To Go Member but indicates the step 

number that is next to go. 

A 1,000 character field that allows the ticket creator or pole 

owner to provide additional information 

Create Map 

Allows the creator or pole owner to attach a map to the ticket. 

For instructions on creating maps, see Creating a Map. 

Pole Owner 

The Pole Owner member code of the ticket. It defaults to the 

code entered when initializing the creating ticket process. 

Ticket Type 

Allows the creator or pole owner to classify a ticket. It is a 

drop-down list of ticket types for selection. The ticket type 

selected should closely reflect the reason for the notification. 

Pole Number 

The pole number of the pole needing work. 

Contact Phone 

Defaults to the phone number listed in the user’s profile. 

Contact Phone Ext 

Defaults to the value in the user’s profile. 

House Number 

A non-required field to provide an address for the pole 

location. 


Revised March 2017

Street Name 

A non-required field for listing the street name of the pole 

location. 

Priority Code 

Misc. ID 

A number 0-9, is a required field used to indicate the sense of 

urgency for the ticket. If your state has standardized the 

priority code list, the description associated with the priority 

code number will be shown in a drop-down menu. If it has 

not, only the numbers will be shown and it needs to be 

defined locally. 

A field that can be used by the creator or pole owner to record 

additional data if needed. It is often used to reference internal 

systems. 

Work Requested 

Date 

The goal date that the pole owner wants all work on the ticket 

to be completed. It can be manually typed or selected using 

the Calendar. 


Revised March 2017

PT+ Ticket Step Fields 

Order 

Status 

Allows the user to number the step. If left blank the system will 

number your steps in sequential order. 

Defaults to Pending for all newly created steps. 

Member 

Job Type 

Required field for the step member code of the company owning the 

facilities referenced in that step. 

Required field that allows a user to select the type of work that needs 

to be completed. 

Number of 

Poles 

Days Interval 

Job ID 

Defaults to 1. NJUNS best practice is to create one ticket for each 

pole. 

Required field used to enter the number of days that the pole owner 

gives the step member to complete their work. 

Alpha/numeric field designed for the pole owner or step member to 

use for data pertaining to the step member’s job authorization. 


Revised March 2017

Next To Go 

(NTG) Start 

Date 

Read-only field populated by the system. For step #1 it will default 

to the day after the ticket is opened. For all other steps, it will be 

the day after the previous step’s completion date. If work steps are 

completed out of order, the system will adjust the next pending step 

start date based on the latest previous step completion date. 

Response 

Request Date 

Read-only field populated by the system as the Next To Go 

Start Date + the number of calendar days entered for the Days 

Interval field for that step. The initial value is determined based 

on step #1’s NTG Start Date and the intervals for each 

step on the ticket. It will repopulate based off the completion of 

the previous step. 

Completed Date Read-only field populated by the system when the step status is 

changed from Pending to Complete. 

Remarks 

A 1,000 character field and any remarks added here apply only to 

the specific job step. 

Instance Reason Read-only field explaining the reason for the ticket being in 

a certain status. 

Ticket 

A hyperlink indicating the ticket number associated with the step. 

Member Pole 

Number 

Is for the pole number used by the step member, if there is one. 

It is not intended to be the one for the pole owner, unless the 

pole owner is the step member. 

Latitude 

Is for the step member’s Y coordinate from whatever GPS or grid 


Longitude 

Is for the step member’s X coordinate from whatever GPS or grid 


q. Location Is a field to be used by the step member. It can be used to reference 

an internal system. 

Reference 

Is a field to be used by the step member. It can be used to reference 



Revised March 2017

Task ID 

Is a field to be used by the step member. It can be used to reference 


Project Module 

Name 

Enter the name of the project here. This is a required field. 

Project Number Read-only field that is populated by the system when the project is 

saved. 

Created by 

Member 

Read only field that defaults to the member code of the User. The 

hyperlink will provide information on the member code and primary 

contact. 

Status 

Defaults to open when the project is saved. It will remain open until 

closed by the member code that created it. 


Revised March 2017

Instance 

Reason 

Allows multiple reasons for the project being in a certain status. 

Currently, it will default to the same value as the Project Status. 

Ticket 

Template 

Allows the user to populate fields that will be used to create new PT+ 

tickets from project information. 

Project Template (Pole Transfer Only) 

Template Name 

The name of the template. This field is required. 

Contact Name 

Contact name to be used for new tickets. 

Contact Phone 

Enter phone number. 

Contact Phone Ext. Enter extension if applicable. 

Create Map 

A map can be created for the project. Click Create Map to 

create it. 


Revised March 2017

Remarks 

State 

1,000 character field to provide additional information 

about the project. 

Select the state from the drop-down list. 

County 

Select the county from the drop-down list. 

Street Name 

Enter if project will consist of work on one street or highway. 

Priority Code 

Code will apply to all tickets created for the project. 


Revised March 2017

PA Module 

PA Ticket Header Fields 

NOTE: If an application crosses state lines, create one ticket for each member state. 

Contact Name 

Defaults to user logged into the system. 

Contact Phone 

Defaults to the user logged into the system. 

Contact Phone 

Ext. 

Defaults to the user logged into the system. 


Revised March 2017

State 

Required Field that defaults to the state for the Creator. 

County 

Required field. State must be selected first. Click on the down 

arrow to expand the list. 

Place 

Map 

Not a required field. County must be completed for the field to 

become active. 

Used to identify the location of the poles. See Creating a Map 

for a detailed explanation. 

Pole Owner 

The member code selected at the start of the ticket creation process. 

Alt Pole Owner Used if there is a joint pole owner for the poles. 

Copy to 

Member 

Request 

Number 

Number of 

Poles 

Used if another member needs access to the ticket. 

Used if there is a Request Number for the application. 

Number of poles on the application. This number must match the 

number of steps on the application. 

Contract Date 

The date of the permit request 

Remarks 

A 1,000 character field used for additional information 

about the ticket. 


Revised March 2017

Pole Attachment Step Fields 

Job Type 

Select the job type that best describes the ticket being created. 

Owner Pole 

Number 

License Pole 

Number 

Pole Set Year 

If known, complete here. Otherwise leave blank for pole owner to 

complete. 

The applicant’s pole number for the location. 

The pole birthmark or pole owner’s records. 

Pole Height 

Pole Class 

Pole height from birthmark or pole owner’s records 

which is an integer field. 

Alpha/numeric field stating the class of the pole. 

Attachment 

Height 

PT Ticket 

Existing or proposed attachment height. 

Use if there is a PT+ ticket associated with the attachment. 


Revised March 2017

Response Date 

Number Power 

Supplies 

Is Anchor 

Attached 

The date that the step is accepted or rejected by the pole owner. 

The system will populate this date when the step is completed by 

the pole owner. 

Required Field for the number of power supplies being attached to the 

pole. 

If the answer is no, leave it blank. If yes, click once to add a check 

mark in the box. 

Is Engineering 

Complete 

If the answer is no, leave it blank. If yes, click once to add a check mark 

in the box. 

House Number 

Street Number of the pole location. 

Street Name 

Required Field. Street name of pole location. 

Pole Owner 

Cost 

Alternate Pole 

Owner Cost 

Other Cost 

Field to be completed by the pole owner if applicable. 



Remarks 

Any additional remarks about the individual pole location. This field 

holds 1000 characters or less. 


Revised March 2017

NJUNS Users Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?