<?xml version='1.0'?>

<reference anchor='RFC1297'>

<front>
<title abbrev='NOC TT REQUIREMENTS'>NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")</title>
<author initials='D.' surname='Johnson' fullname='Dale S. Johnson'>
<organization>Merit NOC</organization>
<address>
<postal>
<street>1075 Beal Avenue</street>
<city>Ann Arbor</city>
<region>MI</region>
<code>48109-2112</code>
<country>US</country></postal>
<phone>+1 313 936 2270</phone>
<email>dsj@merit.edu</email></address></author>
<date month='January' year='1992' />
<abstract>
<t>Professional quality handling of network problems requires some kind of problem tracking system, herein referred to as a "trouble ticket" system.  A basic trouble ticket system acts like a hospital chart, coordinating the work of multiple people who may need to work on the problem.</t>
<t>Once the basic trouble ticket system is in place, however, there are many extensions that can aid Network Operations efficiency. Information in the tickets can be used to produce statistical reports.  Operator efficiency and accuracy may be increased by automating trouble ticket entry with information from the network Alert system.  The Alert system may be used to monitor trouble ticket progress.  Trouble tickets may be also used to communicate network health information between NOCs, to telcom vendors, and to other internal sales and engineering audiences.</t>
<t>This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers.</t></abstract></front>

<seriesInfo name='RFC' value='1297' />
</reference>
