15 are reserved for the receiving command’s use. Most of the items are self-explanatory, but let’s cover two that aren’t as obvious. Item number 3 asks for the priority assigned. Critical  means  that  you  cannot  work  around  the problem to continue operating.  Urgent means that you can work around the problem, but a resolution is required immediately. Routine means the correction is needed, but you can work around the problem and live with it until it is fixed. When you start to fill in item 11, remember to enter a  complete,  detailed  description  of  the  problem  you  are experiencing. Include the screen or menu number, if applicable, the option number, if applicable, and any error message received. Various procedures will have to be followed for personal computers (PCs), depending on the problem. For  commercial  software  problems,  inform  the  software manufacturer   of   the   problem   giving   as   much information  as  possible.  Normanlly,  the  manufacturer will tell you how to correct the problem over the phone, or if the problem will be corrected with the release of the next version of the program. For hardware, it is usually  covered  by  either  a  maintenance  contract  or manufacturer’s warranty. With a maintenance contract, you will follow the instructions for repair as outlined in the  contract.  The  owner’s  manual  of  equipment covered by a manufacturer’s warranty will have a phone number to contact a repair technician. SOFTWARE TROUBLE REPORTS Normally, the trouble reports for the software are submitted  by  that  subsystem’s  coordinator,  after notifying the AIS facility. Some of the most common trouble reports for software include the following: l  Monthly  files  are  not  being  cleared  at  the beginning of the new month. l Report titles are wrong. . Bad data was entered into a file and cannot be removed through normal procedures. HARDWARE TROUBLE REPORTS It is the AIS facility’s responsibility to submit the trouble reports on system hardware problems. The common reasons for hardware trouble reports include the following: A file has become corrupted and no good save tapes are available to rebuild the file. The system keeps hitting 100 percent of capacity and locks up. The system keeps dropping I/O channels. If the hardware problem can be traced to a specific piece  of  equipment,  notify  the  maintenance  technicians to handle the problem. TECHNICAL ASSISTS After submitting a trouble report, you will need to coordinate with the central design activity to see if the problem can be taken care of over the phone or if it will require a technical assist. If it requires a technical assist, there   may   be   a   requirement   to   arrange   for transportation, entry to the facility, and/or escorts. You will need to schedule time for the technician to use the system  and  notify  the  users  that  the  system  is unavailable. OPERATIONAL GUIDELINES When  preparing  the  operational  guidelines  for  your facility,  you  should  consider  four  major  areas  as follows: .  Future  growth  capabilities; o Backup operations; l Contingency plans and disaster recoveries; and l Emergency responses. To develop these and other operational guidelines, you will need to review the current SOPS, command’s mission,   run   folders,   and   monthly   production schedules. While reviewing these, you are looking to make sure that the current and/or proposed operational guidelines will allow the AIS facility to meet the command’s   mission. FUTURE GROWTH CAPABILITIES Projecting future growth capabilities is often the most overlooked operational guideline. Projecting future growth should have been done when the system was designed, but it can be done at any time it is needed. Users are one of your last sources of information when it comes time to start projecting. They know how their workload has increased in the past and can forecast what it will be in the future. With this information, and 1-26