AIAI33-107
AIR INTELLIGENCE AGENCY INSTRUCTION 33-107
6 NOVEMBER 1992
HQ AIR INTELLIGENCE AGENCY
Communications
COMMUNICATIONS-COMPUTER SYSTEMS MANAGEMENT
This regulation provides guidance for the management and operation of the communications-computer function (SC) at all Air Force Intelligence Command (AFIC) command levels. It establishes policy and responsibilities for managing AFIC CRITICOMM support facilities (CSF), remote CSFS, customer-operated remotes (COR), data processing centers (DPC), systems control facilities, and the Self Inspection Program. It consolidates unit SC responsibilities established by Air Force and HQ AFIC directives and serves as a reference to guide communications-computer systems officers in the management of required duties. When a conflict occurs between the guidance contained in this publication and other directives, precedence will be given to the applicable higher-level directive. It applies to all personnel utilizing and operating these services. It does not apply to AFIC-gained Air National Guard or Air Force Reserve units. Requests for waivers to any part of this regulation will be processed through command channels to HQ AFIC/SCM.
Corrected copy of AFIC REGULATION 700-7.
Updates commander's and major command (MAJCOM) responsibility. Includes data processing centers (DPC), system control facilities, and the self inspections program.
AFR 700-7/ESC Sup 1, 30 September 1989.
HQ AFIC/SCM
MSgt Collins and Mr. Jolly
HQ AFIC/SC
Col Norman M. Slocum
HQ AFIC/IMOE
TSgt Marcia J. Bryan
28
F; X:
HQ AFIC/SCM
10
HQ AFIC/IMOE
2
AUL/LSE
1
HQ USAF/SCM, Washington DC 20330-5190
1
AFCSDD, Keesler AFB MS 39534-6340
2
SSC, Gunter AFB AL 36114-6343
2
CHAPTER 1
INTRODUCTION
1.1. Introduction. The prime system used by the Dep nt of Defense (DOD) to send and receive electrical messages is the automated digital network (AUTODIN). AUTODIN is a computer-controlled, worldwide telecommunications network managed by the Defense Information Systems Agency (DISA) that transmits narrative messages and data pattern messages on a store-and-forward message switching principle.
1.2. Authorized Users. Authorized users are member of the DOD, military departments, and subdivisions of military departments. They are authorized to send and receive messages to conduct official government business. The following non-DOD organizations may use the system:
1.2.1. American National Red Cross. Certain administrative and emergency welfare messages are authorized to fulfill this organization's mission. The subject matter covered within this context is that of the death or severe illness of DOD personnel or their immediate family members. The messages will not take precedence over normal military communications.
1.2.2. Federal Credit Unions. When commercial record communications facilities are not available, certain specifically designated federal credit unions operating on military installations may be authorized to support military personnel at those locations.
1.2.3. Military Banking Facilities. Certain commercial banking facilities authorized to do business on military installations may be authorized to originate messages relative to Air Force accounting and finance offices concerning military pay, allotments, record errors, or other matters directly related to the banking support of military personnel.
1.2.4. Using the System. Contractors and foreign governments may use the system under conditions explained in Allied Communications Publication (ACP) 121 US Supplement 10.
CHAPTER 2
MANAGEMENT POLICIES AND RESPONSIBILITIES
2.1. Basic Policy. The use of electrically recorded messages is limited to the transaction of official business that can most effectively and efficiently be handled by electrical transmission. It is the responsibility of the originator to ensure that appropriate method of transfer is used. Members will not use the system to send personal or unofficial messages (retirement announcements, etcetera).
2.2. Major Command (MAJCOM) Responsibilities:
2.2.1. Annually review recurring communicationscomputer processing reports and products to ensure that:
2.2.1.1. Redundant or duplicative reports are combined where feasible.
2.2.1.2. Reports are brief, addressed only to essential addressees, and the precedence is consistent with the urgency of the subject.
2.2.2. Conduct annual reviews of all recurring reports sent as electrical messages. Identify those reports which:
2.2.2.1. Must be sent by electrical means when required to meet suspense dates.
2.2.2.2. May be sent by nonelectrical means when:
2.2.2.2.1. Suspense dates permit.
2.2.2.2.2. MIMINIZE is in effect.
2.2.3. Conduct annual reviews of regulatory guidance to ensure it is accurate and properly addresses AFIC's responsibilities.
2.2.4. Manage the critical intelligence (CRITIC) communications program.
2.3. Commanders' Responsibilities. Commanders at all levels will control electrical messages. This includes enforcing compliance with this regulation, appointing individuals authorized to release or receipt for messages, limiting the number of authorized message releasers to no more than necessary to accomplish the mission and taking prompt action to correct deficiencies which lead to uneconomical use of CSF, remote CSF, COR, and DPC resources. Subordinate unit commanders must restrict authority to release IMMEDIATE and higher-precedence messages to persons who have essential operational functions during crises. At HQ AFIC, this authority is delegated to command center staff duty noncommissioned officers (NCO), directorates, deputy chiefs of staff (DCS), and their assistants. Also, the commanders of Air Force Cryptologic Support Center (AFCSC), Air Force Electronic Warfare Center (AFEWC), Joint Electronic Warfare Center (JEWC), wings and their deputies, are specifically authorized to release IMMEDIATE and higher-precedence messages. Readiness center chiefs are authorized to release IMMEDIATE and higher-precedence messages when these areas have been activated by proper authority. Each functional activity or unit will set up a current list of personnel authorized to release messages to the COR, remote CSF, and CSF or through the base information transfer system (BITS). Messages should be screened to determine if a letter could suffice.
2.4. Communication-Computer Systems Officer (CSO). The Chief, C-CS Management (or SC) is directly responsible to the AFIC unit commander for management of C-CS operations, security, programs, and resources. For units that do not have an SC, the commander may appoint an office of prime responsibility (OPR) to carry out the C-CS management duties and responsibilities described in this regulation.
2.4.1. The communications-computer systems officer will:
2.4.1.1. Ensure readiness of the information processing equipment and personnel to support the needs of the user.
2.4.1.2. Monitor and evaluate operations and implement procedures to improve operations. If a service is no longer required, the CSO will initiate a computer systems requirements document (CSRD) to terminate the service.
2.4.1.3. Ensure procedures are established to cover control, handling, security, upkeep, care, reuse, and storage of message mediums.
2.4.1.4. Ensure output products are picked up at the CSF, remote CSF, and DPC only by the user, user's authorized representative, or forwarded through the base information transfer system (BITS) for collateral message traffic.
2.4.1.5. Ensure excess equipment is identified and disposition action initiated. (DOD 7950.1-M.)
2.4.1.6. Conduct and document at least one self inspection per year.
2.4.1.7. Develop operating instructions as needed and ensure they are reviewed annually for currency and accuracy. Document the review.
2.4.1.8. Ensure a training program is developed and maintained per AFR 50-23, On-the-Job Training, and AFR 40410, Training and Development. The CSO should also be familiar with the procedures in AFR 509, Special Training.
2.4.1.9. Ensure a customer education and support program is established to emphasize the efficient and effective use of the communications-computer systems under the SC purview. The program will contain the following as a minimum:
2.4.1.9.1. How to prepare outgoing message traffic to include, floppy diskette handling procedures. Ensure that a policy statement indicating that customers are required to bring message traffic to the CSF or remote CSF as soon as possible after the date-time-group has been assigned.
2.4.1.9.2. Use of special handling designators.
2.4.1.9.3. Use of address indicating group (AIG).
2.4.1.9.4. Types of general messages.
2.4.1.9.5. Customer responsibilities such as prompt delivery of products to the CSF, remote CSF, and DPC for transmission or processing and proper marking and receipting for classified products.
2.4.1.9.6. Use of service action request and tracer action.
2.4.1.9.7. Customer responsibilities for operating and maintaining their remote terminals to include outage reporting procedures.
2.4.1.9.8. Emphasis on using the postal system vice electrical transmission on routine precedence correspondence.
2.4.1.9.9. Timely pickup of products and notification to the DPC of processing schedule changes or delays as soon as possible.
2.4.1.9.10. Contingency and alternate site agreements, plans, requirements and procedures. Ensure users also understand the processing limitations to be expected when such plans are invoked.
2.4.1.9.11. MINIMIZE procedures and responsibilities.
2.4.1.10. Remote terminal security.
2.4.1.10.1. Focal point to resolve communicationscomputer system complaints and problems.
2.4.1.10.2. Training available including assistance in understanding the technical processing aspect of their respective systems.
2.4.1.10.3. Minimizing product copy requirements.
2.4.1.10.4. Bulk delivery of products.
2.4.1.11. Ensure contingency plans are established at least once a year.
2.4.1.12. Ensure adequate destruction facilities are available to meet the needs of the CSF, remote CSF, and DPC.
2.4.2. Operations Management. The wing or group SC will oversee the implementation of AFIC policy related to the management and operation of C-CS within its theater of operation. The unit SC is the OPR for C-CS operations.
2.5. Message Originator's Responsibilities. The originator is the commander or authority in whose name a message is sent. The originator is responsible for the overall functions necessary to prepare and release messages. This responsibility is normally fulfilled through the message drafter and releaser.
2.5.1. Confirm Electrical Transmission. Message originators may request the remote CSF or CSF to confirm when an electrically transmitted message has reached its addressee or servicing base telecommunications center or CSF. Limit such requests only to those messages whose nondelivery would have a severe military, political, or loss-of-life impact. Do not request confirmation of delivery on general messages, other messages having wide distribution, or nonelectrically transmitted messages. Exceptions are messages originated by or addressed to the AFIC Commander Vice Commander, or Chief of Staff when on temporary duty (TDY). Message originators will contact their servicing remote CSF or CSF for special instructions to annotate confirmation of delivery on their messages.
2.5.2. Central Point of Distribution. Each supported unit must establish a central point of distribution. All addressees below a two-letter functional address symbol (FAS) will establish their copy requirement with their central distribution point.
NOTE: CSFs and remote CSFs are not required to deliver messages to addressees below the two-letter. Requests for waiver must be obtained from the respective wing.
2.5.3. Use of DSSCS Channels for Message Processing. All AFIC message originators will use DSSCS channels for recipients served by the DSSCS networks. If there is a mix of both DSSCS and general service (GENSER) addressees, send only one message by GENSER provided the classification criterions allow. Units unable to adhere to this policy should submit a request to HQ AFIC/SCM for waiver explaining the reason for noncompliance. Waivers will be granted on a case-by-case basis. Ensure that your respective wing is included as information addressees on all waiver requests.
2.5.4. Service Action Request. Customers must complete AFIC Form 108, Service Action Request, for service action on a specific message (retransmission, tracer, copies of message in nonreceipt). Deliver the AFIC Form 108 to the servicing CSF or remote CSF. Originators or addressees can use AFIC Form 108 to initiate tracer action to determine excessive delays or nonreceipt. Coordinate with your servicing CSF or remote CSF before initiating tracer action. STREAMLINER remote users may originate a service message to the host for service actions.
2.6. Message Drafters' Responsibilities. The drafter writes the message following the procedures outlined in AFR 10-1 and local Customer Education Guide. Additionally, strict compliance to AFR 700-31, ESCR 4-104, DIA Compartment Address Book (DIACAB), and USSID 505 will be used for preparing message addressees. Subject matter and staff action message delivery distribution indicators (DDI) and guidance for their use are contained in USSID 519. A maximum of 14 DDIs may be included on a DSSCS message. If this block or option is not filled in, the default DDI "SOA" will added automatically.
2.7. Message Releasers' Responsibilities. releaser sends a message for the commander and is responsible for correct message preparation. The releaser will ensure:
2.7.1. The message is prepared according to AFR 10-1 and Customer Education Guide.
2.7.2. Delivery of ZEN addressees, whether on or off base, is the responsibility of the message originator.
2.7.3. The message is released promptly.
2.7.4. That messages containing USAFINTEL 201-1 information are not sent to activities that cannot receive such information. See AFICR 4-104, USSID 505, or DIACAB, or contact your CSF or remote CSF.
2.7.5. A separate date-time-group (DTG) must be assigned to each message, otherwise messages cannot be accepted for processing by the CSF or remote CSF.
2.7.6. Message precedence is appropriate.
2.8. At HQ AFIC. At HQ AFIC, electronic distribution may be effected for originated message traffic destined for following organizations and units. ZEN IS NOT REQUIRED. Electronic Distribution:
CHAPTER 3
FACILITY MANAGEMENT
3.1. Facility Management Policy. Facilities housing communications-computer systems must meet the minimum requirements of this section.
3.2. Access to the CSF, Remote CSF, or DPC. Equipment rooms are normally designated controlled or restricted areas. They must comply with the policies and procedures contained in AFR 125-37, The Resources Protection Program, or AFR 207-1, The Air Force Physical Security Program. In general, traffic into and through the equipment rooms must be kept to a minimum. Facilities containing communications security (COMSEC) equipment must provide the degree of protection to COMSEC material as required by DOD 5200.1-R/AFR 205-1 and AF 56 series. Authorized visitors to the computer room are allowed as long as the visitors do not disrupt operations. All persons entering the facility who do not require daily access must sign in on the visitors' register and be escorted by a cleared individual at all times. CSF, remote CSF, or DPC personnel must be constantly alert for possible sabotage or inadvertent disruptions. Persons will not be allowed to enter the CSF, remote CSF, or DPC if they are carrying any object (a magnet, radio, beeper, pager, or other recording or transmitting device) that may interfere with or damage equipment of supplies. All objects (such as briefcases, closed cartons, handbags) will be exarrdned for content. Anyone refusing may be denied access.
3.3. Fire or Safety Practices in the CSF, Remote CSF, or DPC. The Air Force policy governing the fire protection program is contained in AFR 92-1, Fire Protection Program, and supplements. All CSF, remote CSF, or DPC personnel will be trained annually on fire suppression systems and fire reporting procedures. This training will include, as a minimum, fire evacuation routes, proper use of firefighting equipment, and firefighting techniques. Fire drills will be conducted at least semiannually. Both training and drills will be documented as recurring training. Manual suppression of the Halon system will be included in the training program to preclude unnecessary recharging of the system because of false alarms. The rules in the Air Force Occupational Safety and Health (AFOSH) 127 services standards apply to all communications-computer systems operations. Where the possibility of electrical shock exists, safety equipment will be provided. Equipment operators must be trained to use the electrical safety equipment and also trained in an approved method of cardiopulmonary resuscitation (CPR) annually.
3.4. Emergency Lighting. Emergency battery operated lighting must be provided to ensure the safe shutdown of equipment and exit of personnel in case of total power failure.
3.5. Noise LeveL. Schedule noise level evaluations from Bioenvironmental Engineering Services when hazardous noise levels are suspected. If hazardous noise is found, action must be taken to reduce noise levels or exposures and to make sure that Bioenvironmental Engineering Services conducts appropriate followup noise surveys as long as a hazardous noise level exists. Evaluations are also to be requested within 30 days of full operation of new equipment, changed operations, or other significant workplace modifications.
3.6. Temperature and Humidity. AFM 88-15, Air Force Design Manual Criteria and Standards for Air Force Construction, chapter 20, contains guidance in this area. If vendor or contract specifications are more stringent, they must be used in place of AFM 88-15. When the upper and lower limits of temperature and humidity are approached, extreme care is needed to ensure continued operation. Appropriate local procedures will be established to ensure that near limit conditions are closely monitored and prompt action is taken when required. As a minimum, a recording thermometer or hygrometer should be used in each computer room to provide a daily record of temperature and humidity. Recording devices must be calibrated at lease every 6 months. Recorders must be strategically located to record surrounding atmospheric conditions: however, do not place recorders on processing equipment or where outside conditions affect the readings (against outside walls or near windows and doors). Readings will be recorded 24 hours a day, 7 days a week, even if the equipment is not in use. The charts must be changed at proper intervals to avoid any overlaps (RADAY change). Mark the location of the recorder (post number, for instance) on each chart when multiple recorders are installed. When the temperature or humidity exceeds tolerances, make a notation on the shift activity or master station log of the cause. For large sites, several recorders may be needed to monitor conditions properly. Entries must be annotated in the master station log when the base civil engineering personnel are called and when the equipment is powered down due to temperature or humidity problems. If limits were exceeded and the system was not powered down, an explanation of what occurred must be attached to the recording chart. To help prevent temperature and humidity fluctuation, the doors to the computer room will be kept closed when not in use. The recording charts must be retained according to AFR 12-50 for evaluating the cause of damage to automated data processing (ADP) equipment or communication components. Recording devices are not required in CSFS, remote CSFS, or DPCs that have an energy management control system.
3.7. Environmental Control Failure. CSFS, remote CSFS, or DPCs must establish procedures to guide shift supervisors when power and air conditioning equipment fails. When the limits of temperature or humidity are about to be exceeded, immediate action will be taken to carry out emergency procedures. The emergency procedures will tell how to maintain the temperature and humidity within tolerance and the actions to take when they cannot be maintained. If emergency actions aren't successful and environment limits are exceeded, document the incident fully and retain in file. The documentation will include the chart records of temperature and humidity from the hydrotherrnograph equipment with annotation of the circumstances that resulted in the incident.
3.8. Facility Equipment Room Cleanliness:
3.8.1. CSF, remote CSF, or DPC equipment rooms must be kept as free of dust as possible. Air conditioner filters must be checked monthly and changed as required.
3.8.2. Tile covered floors will be kept clean. Steel wool buffin- pads will not be used.
3.8.3. Raised floors, where installed, will not be wet mopped. Inspect subfloor under the raised floor at least once every 60 days and clean as necessary.
3.8.4. Carpeting, when used in equipment rooms, must comply with vendor contract specifications.
3.8.5. Smoking, eating, and drinking are not permitted while directly involved in operating equipment. Smoking in any facility will not be waived and eating and drinking will be allowed only within a designated area of the larger room if there is not an available area off the CSF, remote CSF, or DPC floor. This area must be more than five feet from any ADP equipment, cryptographic equipment, or tape libraries. A partition should be used to set off the break area from the rest of the room. Of critical importance is that food and drink are kept away from equipment and diligent efforts are made to ensure that beverages are not spilled on raised floors.
3.9. Storage Areas. Adequate storage space (apart from the CSF, remote CSF, or DPC equipment room) must be provided for communications-computer systems equipment supplies and input and output material. Operators should condition paper stock by subjecting them to environmental conditions similar to those of the computer room for a minimum of 8 hours before use, if possible.
3.10. Supply. An adequate supply of items such as paper, magnetic tape, and disk packs requires advance planning, budgeting and continuing review to make sure they are available at the appropriate time and in the required quantity and quality:
3.10.1. Stock Levels. The CSF, remote CSF, or DPC manager will coordinate with the publications distribution office and the unit supply liaison to establish and maintain stock levels. Records of supply use will be kept for management purposes.
3.10.2. Defective Supplies. Forms, ribbons, paper, etcetera, must meet required specifications. Machine failures, work stoppages, and processing failures due to inferior supplies will be documented. Procedures for reporting blank form deficiencies are in AFR 9-1, The Air Force Forms Management Program. Report other material deficiencies to base supply or the base contracting office, whichever is appropriate.
3.10.3. Disposal. Dispose of unused or excess paper stocks and special forms that have accumulated through normal processing according to DOD Manual 4160.21. Destroy paper on which personal data or sensitive information was recorded according to the Privacy Act requirements (AFR 12-35 and AFR 20516). Destroy classified waste according to DOD 5200.1-R/AFR 205-1 and USAFINTEL 201-1. All burnable waste must be destroyed as classified, if the CSF, remote CSF, or DPC uses cryptographic equipment. Place specifically marked containers in break areas for unclassified nonburnable waste (such as cans, bottles, ribbon spools, etcetera).
CHAPTER 4
OPERATIONS MANAGEMENT
4.1. Operations Management Policy. This section provides policies for managing the operation of communications-computer systems and facilities.
4.2. Basic Responsibilities. Information systems operations managers must be responsive to mission needs and must use management principles which leads to effective mission support at the lowest cost.
4.2.1. CSFs and remote CSFs will use standards or other measurements as developed by Allied Communications Publications (ACP), Defense Information Systems Agency (DISA) circulars, Joint Army, Navy, Air Force Publications (JANAP), MAJCOM and other directives applicable to evaluate performance.
4.2.2. Inventory, accountability, and performance records will be kept to allocate work, develop standards or norms, and plan future work. In addition, they will be used to compute rental or maintenance charges, discounts, credits, and liquidated damages, and will verify communications-computer systems equipment is used for approved applications and products. All communications-computer systems records will be maintained as required in AFR 12-20, Management of Documentation, and AFR 12-50, Disposition of Air Force Documentation.
4.2.3. Communications personnel may not alter the contents of information systems products except with permission of the originator or releaser.
4.2.4. Communications personnel may not divulge, release, or publish the contents of information systems products (including voice) to any person other than the addressee, addressee's representative, or person authorized by local or command directives. Refer persons who request access to information systems products to the originator or addressee of the material.
4.3. Operations During Severe Weather Conditions. When severe weather conditions exist (electrical or thunderstorms within 10 statute miles of an installation, ice storms, high wind conditions, etcetera), the DPC will normally power down their equipment, unless the user's mission dictates otherwise. The CSO will ensure local procedures are developed and will implement those procedures based on an evaluation of weather reports, contractual liabilities, and user mission requirements to determine if the equipment should remain powered up. Any CSF, remote CSF, or DPC whose users must continue processing during severe weather conditions on a recurring basis will install an alternate power source, such as a motor generator, to ensure processing continues with no interruption to the customer (see AFR 1 1-4 for host tenant support agreements).
4.4. Contingency and Alternate Site Agreements, Plans, Requirements, and Procedures. Every systems manager is responsible for developing and coordinating detailed plans to support operations under emergency conditions. The CSO must develop, test, and maintain contingency plans required to support unit and base plans. Ensure contingency plans are tested at least once a year. The CSF, remote CSF, or DPC manager must develop plans to ensure the survival and recovery of communications-computer systems resources in a contingency and the capability to respond and provide communications-computer systems support in the event of a disaster. To ensure minimum disruption of operations and support, backup data files must be positioned in off-site storage locations, if available. In addition, one or more alternate processing sites may be identified. Alternate site agreements will be reviewed on an annual basis. Each CSF and remote CSF will establish a contingency and alternate site agreement for processing incoming and outgoing messages in the event communications becomes totally disabled. This agreement should be established for both Defense Special Security Communications System (DSSCS) and general service (GENSER) traffic handling. CSFS, DPCS, or CORs unable to establish such an agreement will advise HQ AFIC/SCM on the reasons the agreement cannot be established. For those stations that are directly connected to AUTODIN, submit your alternate routing requests according to DISA OPLAN 1-84.
4.5. Operating Instructions. Develop operating instructions as needed and ensure they are reviewed annually for currency and accuracy. The following areas of operations are suggested:
4.5.1. Temperature and humfidity controls.
4.5.2. Magnetic media controls.
4.5.3. Management of remote processing facilities.
4.5.4. Physical security and accountability.
4.5.5. Shift activity and turnover (shift change) log.
4.5.6. Power up and power down procedures.
4.5.7. Housekeeping to include cleaning schedules, methods, etcetera.
4.5.8. Marking, control, storage, and disposal of input output, and waste.
4.5.9. Personal data subject to the Privacy Act of 1974. Include distribution, storage, and disposal of input and output.
4.5.10. Service messages.
4.5.11. Special handling messages.
4.5.12. CRITIC processing.
4.5.13. RADAY procedures.
4.5.14. Duties and responsibilities of shift supervisor.
4.5.15. COMSEC, receipt, control, accountability, inventory, and destruction.
4.6. Publications:
4.6.1. The following regulations and publications are some of the most commonly used publications.
4.6.1.1. DOD 5200.IR/AFR 205-1, Information Security Program.
4.6.1.2. JANAP-128, Automated Digital Network (AUTODIN) Operating Procedures.
4.6.1.3. JANAP-102, (C) Status of Noncryptographic JANAPs and ACPS.
4.6.1.4. ACP-117 Series, Allied Routing Indicator Publications.
4.6.1.5. ACP-121 Communications Instructions General.
4.6.1.6. ACP-121 US SUP-1 (C) Communications.
4.6.1.7. ACP-122, (C) Communications Instructions Security.
4.6.1.8. ACP-127, Communications Instructions-Tape Relay Procedures.
4.6.1.9. ACP-131, Communications Instructions--Operating Signals.
4.6.1.10. AFR 50-23, On-the-Job Training. (PA)
4.6.1.11. AFR 56 series.
4.6.1.12. AFR 205-2, Release of Intelligence Material to US Contractors.
4.6.1.13. AFR 205-4, Industrial Security Program Regulation.
4.6.1.14. AFR 205-16, Automatic Data Processing Security Policy.
4.6.1.15. AFR 205-43, (C) Safeguarding NATO Classified Information (U).
4.6.1.16. AFR 700-1, Managing Air Force Communications-Computer Systems.
4.6.1.17. AFR 700-3, Information Systems Requirements Processing.
4.6.1.18. AFR 700-4, Volume 1, Information Systems Program Management; Volume II, Information Systems Acquisition and Major Automated information Systems Review Requirements.
4.6.1.19. AFR 700-5, Communications-Computers Systems Requirements Board.
4.6.1.20. AFR 700-6, Information System Operations Management.
4.6.1.21. AFR 700-7, Information Processing Center Operations Management.
4.6.1.22. AFR 700-10, Information Systems Security (FOUO).
4.6.1.23. AFR 700-12, Developing and Processing Communications-Computer Systems Publications.
4.6.1.24. AFR 700-26, Management of Small Computers.
4.6.1.25. AFR 700-31, Message Address Directory.
4.6.2. MAJCOM Publcations and Regulations:
4.6.2.1. AFICR 4-104, (C) AFIC Address Directory (U).
4.6.2.2. ESCR 56-10, Automated Information System Security Procedures.
4.6.2.3. ESCR 205-1, Emergency Disposition of Classified Material.
4.6.2.4. ESCR 700-6, Communications Policies and Procedures.
4.6.2.5. AFICR 700-7, Communications-Computer Systems Management.
4.6.2.6. AFICR 700-8, Communications Reports.
4.6.2.7. AFICP 123-700-2, CRITICOMM and Computer Systems Management.
4.6.2.8. AFICP 123-56-2, Comm-Computer System Security.
4.6.2.9. AFICVA 11-1, Headquarters AFIC Staff Directory.
4.6.2.10. AFICVA 11-2, AFIC Telephone Directory (C).
4.6.3. NSA/CSS Publications. These publications are ordered directly from NSACSSM61. Units ordering publications must be listed in USSID 505 or DIA Compartmented Address Book.
4.6.3.1. COI-101, (S) Critical Intelligence Communications Systems (CRITICOMM) Operating Instructions General (U).
4.6.3.2. COI-104, (C) CRITICOMM Operating Instructions Facilities Control Procedures (U).
4.6.3.3. DOI-102, (S) DSSCS Operating Instructions Routing Indicators. (U)
4.6.3.4. DOI-101, (S) (S-HVCCO) Defense Special Security Communications System (DSSCS) Address Groups.
4.6.3.5. DOI-103, (C) Defense Special Security Communications System (DSSCS) Operating Instructions (U) System/Data Procedures.
4.6.3.6. USSID-505, (S-HVCCO) SIGINT Organizations (FOUO).
4.6.3.7. USSID-507, (C-HVCCO) SIGINT MINIMIZE Procedures (FOUO).
4.6.3.8. USSID-508, (C-HVCCO) Use of Operations Communications (OPSCOMM) (FOUO).
4.6.3.9. USSID-519, (TS-HVOOC) Delivery Distribution Indicator (DDI) (FOUO).
4.6.3.10. USSID-536 (C) Telecommunications Field Engineering Support Program (FOUO).
4.6.3.11. USAFINTEL 201-1, (S-HVCCO) Security, Use, and Dissemination of Sensitive Compartmented Information (SCI) (U).
4.7. Customer Education and Customer Support. Each CSF, remote CSF, or DPC must set up and maintain a sound customer support program tailored to fit the local situation. The purpose of such a program is to improve service to users by training them to use the systems effectively and efficiently. Local programs may vary in the form of presentation but each will cover all appropriate aspects of communications-computet systems. Management personnel must be intimately familiar with the mission and support required by base activities. These individuals must take the lead in establishing the forum and encouraging the free flow of information between the users and the CSF, remote CSF, or DPC. The user perspective of the support being received is vital to measuring the effectiveness. Good customer relations translates to effective mission support.
4.7.1. Customer Visits. A visit by management personnel will be performed as needed to representative user locations for each automated data system (if a user is responsible for multiple systems a single visit will suffice). Management personnel will use the visits to better determine the needed user interface, pinpoint possible customer dissatisfaction, and provide visibility of the CSF, remote CSF, or DPCs interface and importance to mission accomplishment. Document visits made, issues discussed, and actions taken.
4.7.2. Customer Education Guide. Each CSF or remote CSF will publish a Customer Education Guide to include the following as a minimum.
4.7.2.1. How to handle misrouted messages.
4.7.2.2. How to request service actions.
4.7.2.3. Examples of PLA updates (for remote users).
4.7.2.4. Requests for retransmissions (RETO) (for remote users).
4.7.2.5. Procedures for floppy diskettes.
4.7.2.6. MINIMIZE.
4.7.2.7. Message Management Letters
4.7.2.8. Standardization of PLAs - AFR 700-3 1, USSID 505, DIACAB, etcetera.
4.7.2.9. Use or DAGs and AIGS.
4.7.3. Customer Questionnaires. Questionnaires are a viable method of determining customer satisfaction and for determining system weaknesses and procedural complaints before they become problems. Questionnaires should be sent to customers periodically throughout the year.
4.8. Address Indicator Group (AIG) Management. HQ AFIC/IMOA is responsible for AIG assignments within the command. Forward your AIG assignment request to that office. Originators and recipients of AIGs will provide their servicing CSF or remote CSF copies of newly established, recapitulations, modification, or cancellations of AIG messages on which they are an addressee. 'Me CSF or remote CSF cannot ensure delivery unless they are provided current information.
4.8.1. Responsible Authority. The responsible authority for an AIG is the activity charged with overseeing an AIG's use and administration. The responsible authority will:
4.8.1.1. Make sure that each assigned AIG is required and that its address composition is kept current.
4.8.1.2. Make sure that only authorized message originators use the AIGs as directed by HQ AFIC/IMOA.
4.8.1.3. Send AIG modifications, cancellations, and recapitulations to the CSF or remote CSF, manager, addressees, and users at least 5 days before the effective date unless emergency dictates otherwise.
4.8.1.3.1. Modification of an AIG consists of addressee additions, deletions, and changes.
4.8.1.3.2. Cancellation of an AIG consists of identifying AIGs that are no longer needed and publishing a notice terminating their use.
4.8.1.3.3. Recapitulation of an AIG consists of publishing an accurately revised total address composition. Do this when numerous modifications have been made, but at least once a year during the 13th month following initial establishment or last recapitulation.
4.8.1.4. Send promulgations, modifications, cancellations, or recapitulations of AIGs which include naval units at sea or mobile units as addressees to Naval Telecommunications System Integration Center (NAVTTELSYSSIC), NAVCOMU, Washington DC 20301; Naval Communications Area Master Station Atlantic (NAVCAMS LANT), Norfolk VA 23511; and Naval Conununications Area Master Station East Pac (NAVCAMS EASTPAC), Honolulu HI 96318, for information.
4.8.2. AIG Address Composition. Use addressees for Air Force activities listed in AFR 700-31 in the address composition of AIGS. For other DOD, Army (USA), and Navy (USN) addressees, use the PLA as indicated in Department of the Army (DA) Pamphlet 25-1 1, USN PLAD 1, or USMCEB Publication Number 6 (all are part of AFR 700-3 1). Do not:
4.8.2.1. Create AIGs with less than 16 addressees.
4.8.2.2. Use the locations of emergency relocation sites (ERS), alternate headquarters (ALT HQ) (ACP 117 US SUPP-4), naval units afloat, mobile units, or task force organization addressees.
4.8.2.3. Use collective address designators, such as general message titles.
4.8.2.4. Include commands or activities served by commercial means. (Contact your servicing CSF or remote CSF for assistance in this area.)
4.8.2.5. Include addressees of other nations, International Pact Organizations (IPO), non-DOD or DOD addressees served by non-DOD telecommunications facilities unless you have prior coordination and a statement to that effect in the request for assignment of an AIG.
4.8.3. AIG User Responsibilities. Only the responsible authority and those activities designated by the responsible authority may use an AIG. The following applies:
4.8.3.1. Spell out AIGs and only address them as "ACCTION" addressees. If an AIG must be sent for "INFORMATION," type it as an action address (example: TO AIG ONE TWO THREE), and state in the first line of the message text, "AIG ONE TWO THREE TAKE FOR INFORMATION ONLY."
4.8.3.2. When using two or more AIGs and an addressee is listed in more than one AIG, CSFs and remote CSFs must prevent duplicate delivery of terminated message traffic, (STREAMLINER automatically prevents duplication of addressees on AIGS).
4.8.3.3. Add-on addressees may not know the address composition of the addressed AIGS. If the originator thinks this information is important to the add-on addressees, the originator will provide them the address list upon request.
4.8.4. AIG Addressee Responsibilities. Addressees must tell their servicing CSF or remote CSF when they are included in an AIG and if they are authorized to use the AIG. They must also furnish a copy of any promulgations, recapitulations, modifications, or cancellations of the AIG.
4.8.4.1. Do not readdress AIG messages, except in operational emergencies, unless the readdressing action is to addressees not included in the original transmission. If the operational urgency of the subject does not allow time for an AIG address composition review, the message may be readdressed with add-on addressees.
4.8.4.2. If addressees determine that they no longer need to be included in an AIG or if their titles or addresses change, they will tell the responsible authority.
4.8.4.3. Upon relocation to or activation of an ALT HQ, or ERS, the command will tell the responsible authority and other authorized AIG users. Prompt notification to CSFs and remote CSFs will ease message processing.
4.8.5. Security Classification of AIGS. Before classifying the address composition of an AIG, the responsible authority must carefully consider:
4.8.5.1. If an ERS or ALT HQ is addressed without giving its location, the address composition may be unclassified.
4.8.5.2. If the address composition has classified or sensitive order-of-battle information, it should be classified.
4.8.5.3. If correspondence dealing with classified AIGs contains any information which can be associated with the AIG address composition, classify it at least Confidential. However, modifications to a classified AIG need not be classified if the modification does not give any sensitive information which formed the basis for the original security classification.
4.8.6. Numbering AIG Modifications:
4.8.6.1. Give each AIG modification a sequential number. Number modifications continuously until the AIG is recapitulated.
4.8.6.2. Show the identification of the modification in the subject line of the letter or message as follows: the abbreviation AIG, the AIG number, a slant (/) sign, and a modification number. For example, SUBJ; AIG 8552/4MODIFICATION.
4.8.6.3. Each recapitulation will be modification number one, thereby starting a new series of modification numbers. When a recapitulation also includes modifications, take care to include addressees that are being deleted from or added to the AIG in the address of the message. The text of the recapitulation identifies those activities being added, deleted, or amended.
4.8.7. Request for AIG Information. Forward information requests concerning the identification of the responsible authority of AIGs or an unknown responsible authority to the local CSF or remote CSF for assistance. If the CSF or remote CSF cannot provide the needed information, forward the request to HQ AFIC/IMOA, Command AIG Manager.
4.8.8. CSF and Remote CSF Responsibilities for AIGS. Maintain a separate folder for each incoming and outgoing AIG message addressed to or from the unit. These folders are used to provide customer support pertaining to AIG messages. The folders will contain the following messages:
4.8.8.1. AIG promulgations and, or establishment (messages and letters).
4.8.8.2. AIG recapitulations.
4.8.8.3. AIG modification correspondence (messages and letters). When the AIG is cancelled by the cognizant authority, the folder will be destroyed according to AFR 12-50.
4.9. DSSCS Address Groups (DAG) Management. Any authorized activity may use DAGs assigned under the provisions of DOI-101. Use of these DAGs is not limited to, nor necessarily associated with, a particular subject. Do not use them in place of special-purpose address groups, such as distribution symbols assigned under the provisions of USSID 309. Request all DAGs through HQ AFIC/SCM. DAGs are alphabetic groups used in the message address to represent a predetermined group of action or information addressees. You may use them, as required, in both action and information elements of a special intelligence message address. As with AIGS, if you use FASS, you must separate them from the PLA immediately with double slants (//), and end them with double slants. You may add addresses to a message with a DAG by typing the unit designation and FAS (if required) of the addressee. (Do not include the installation name and geographical location on messages containing DAGS.) You may delete addressees of the DAG by leaving nine spaces from the left margin, typing the prosign "LESS," space, and the PLA of the addressee to be deleted. Each deleted PLA must be preceded by the prosign "LESS". "LESS" addressees must be listed after "ADDED" addressees.
4.9.1. Provide the following information when requesting a DAG assignment:
4.9.1.1. Responsible authority: (unit, FAS).
4.9.1.2. Action addressees: (Addressees listed in alphanumeric order, no office symbols permitted).
4.9.1.3. Information addressees: (Addressees listed in alphanumeric order, no office symbols permitted).
4.9.1.4. Estimated frequency of use:
4.9.1.5. Primary purpose of the new DAG: (Give usage of DAG).
4.9.1.6. Point of contact (POC): (name, phone numbers, STU-HI if available).
4.9.1.7. Remarks: (Optional-For information not covered by above fields).
NOTE: Ensure that the proper classification is assigned to protect the relationship between addressees.
4.9.2. Forward the DAG Request to HQ AFICISCM. HQ AFIC/SCMO will review the request and, upon approval, forward it for processing. See attachment I for an example of a DAG request. Also, forward DAG change requests to HQ AFIC/SCM and include the reason for changes.
4.9.3. CSF and Remote CSF Responsibilities for DAGS. Maintain a separate folder for each incoming and outgoing DAG message addressed to or from the unit. These folders are used to provide customer support pertaining to DAG messages. The folders will contain the following messages:
4.9.3.1. DAG promulgations and, or establishment (messages and letters).
4.9.3.2. DAG recapitulations.
4.9.3.3. DAG modification correspondence (messages and letters).
4.10. MINIMIZE. MINIMIZE is a condition that a commander or other authority may impose on users of telecommunications systems in an emergency or exercise. The aim is to limit the volume of routine traffic in the communications system and ensure the flow of essential traffic. Essential traffic is that which deals directly with the success of the mission or safety of life. For DSSCS minimize information, consult USSID 507 and USSID 508.
4.10.1. Basis for Imposition. The need for MINIMIZE is a decision the co er must make based, in part, on the following:
4.10.1.1. Capability to act on orders from higher headquarters.
4.10.1.2. Impact on subordinates and on other commanders.
4.10.1.3. Operational necessity, based on present indications or past experience.
4.10.1.4. Excessive loading of the communications networks, particularly those switched networks of the DCS Defense Switch Network (DSN) (previously called AUTOVON), and automated digital network (AUTODIN).
4.10.2. Application. Commanders may impose MINIMIZE on all those who use United States military telecommunications, however, before this is done, the scope of its applicability must be weighed. Commanders must limit MINIMIZE to the least number of users affected by the emergency or exercise. For example, a cable break that stops communications from Guam to Okinawa need not call for MIN in the whole Pacific. As changes in the situation make it necessary, MINIMUM may be expanded, reduced, or canceled completely.
4.10.3. Imposition Authority. Commanders may impose MINIMIZE on their command or a part of their command unless prohibited by higher authority. They may also ask other commanders and chiefs of government agencies to impose MINIMUM on all users who communicate with activities in the MINIMIZE area. MINIMIZE imposition authority is as follows:
4.10.3.1. Worldwide. Only the JCS has the authority to impose MINIMIZE worldwide on all users of GENSER message traffic. DIRNSA shall determine when DSSCS MINIMIZE is to be imposed on CRIIICOMM facilities. See DOI-103, USSID 507, and COT-101, chapter 6.
4.10.3.2. Within AFIC. The Commander of AFIC may impose MINIMIZE only on voice or record communications originated within AFIC.
4.10.3.3. Automatic Imposition. MINIMIZE is automatically imposed on those who use record and voice communications when defense readiness conditions (DEFCON) I and 2 are declared.
4.10.4. Planning. Planning is essential if MINIMIZE is to work. To prepare for MINIMIZE, CSF and remote CSF customers will put instructions in local directives to explain MINIMIZE and ensure compliance.
4.10.4.1. Set up strict written guides to control, monitor, and evaluate the use and responsiveness of communications facilities during MINIMIZE.
4.10.4.2. Identify reports to be sent by nonelectrical means during MINIMIZE. Make sure that those who send such reports know what is required under MINIMIZE.
4.10.4.3. Check the format of the recurring reports to be sent electrically during MINIMIZE to see that authorized abbreviations are used.
4.10.5. Control of Communications. When MINIMIZE is imposed, control electrically recorded messages as follows:
4.10.5.1. CSF and Remote CSF Personnel:
4.10.5.1.1. Determine if MINIMIZE is for GENSER or DSSCS. Put all narrative messages on hand but not yet sent, into two groups: Priority and higher-precedence messages and Routine precedence messages. Send the Priority and higher-precedence messages in the normal way. Return those that have Routine precedence to the releasing officials to see if they should be sent under MINIMIZE.
4.10.5.1.2. Send all subsequent message traffic in the normal way. Return those messages which do not have the words "MINIMIZE CONSIDERED" and the releaser's initials.
4.10.5.1.3. The message drafter who wants to send a message will stamp, type, or write in ink "MINIMIZE CONSIDERED" in the SPECIAL INSTRUCTIONS block of the DD Form 173, Joint Messageform, or if message is delivered on floppy disk, place this statement on the AFIC Form 156, Diskette Messageform, and provide his or her initials.
4.10.5.2. At CSFs and remote CSFS: Upon receipt of a message which imposes MINIMIZE, forward a copy electrically to all connected in-house and distant remote ' terminals using general message "ALREMOTES."
NOTE: At HQ AFIC, forward a copy to the AFIC Command Center and complete an AFIC Form 48, Request For Reproduction Bindery Service, requesting a total of 85 copies. Take the AFIC Form 48 to HQ AFIC/IMR as soon as possible. After reproduction, HQ AFIC/INM will call the 6960 ESG/IMAC for pickup and distribution to HQ AFIC staff offices, collocated units, and San Antonio area subordinate units.
4.10.5.3. Cancellation or Modification. The imposing or higher authority can cancel or modify MINIMIZE. The cancellation message uses the words, "CANCEL MINIMIZE," followed by the scope (area and mediums of electrical communications) or the condition to be canceled. The message canceling or modifying MINIMIZE refers to the message which imposed MINIMIZE and, if cancellation is not immediate, includes the date and time that MINIMIZE is to be canceled.
4.11. Methods and Results (M&R). M&R personnel provide quality control and statistical reporting. They provide CSF and remote CSF management personnel information and recommendations on the quality of service provided the user.
4.11.1. Analysis Methods. M&R personnel can use various methods to check the efficiency of the CSF and remote CSF operation. The two most commonly used are visual observation and statistical comparison. Visual observation consists of looking at operations in progress. Since this method gives real-time evaluation, managers must use it for analysis of rules, performance, and operator proficiency. A statistical comparison is generally an after-the-fact method for getting data and analyzing it for trends. Managers must use this type of analysis for evaluating such things as handling time, volunx, and error rate.
4.11.2. Analysis Areas. There are many areas in the communications-computer system which will help performance analysis obtain information to check the effectiveness and efficiency of the CSF or remote CSF. The following describes some of these areas.
4.11.2.1. Customer Satisfaction (Effectiveness). The quality of service that the CSF or remote CSF provides is measured, first, by the users of the service and, second, by the personnel operating the CSF or remote CSF. Analysis personnel must perform customer visits, conduct user group meetings, and develop questionnaires to obtain user feedback. Management personnel then must use this feedback to enhance user satisfaction and eliminate deficiencies.
4.11.2.2. Internal CSF and Remote CSF Operations (Efficiency). The M&R function will take a critical look at the internal procedures. These are the more traditional areas of traffic analysis. In these areas, M&R checks various aspects to find the accuracy, speed, and reliability of message processing. In comparing the results to system standards and to the station's past records, managers can develop an accurate picture of current performances and trends.
4.11.2.3. Operating Procedures. Check adherence to directives (such as ACPS, JANAPS, DOls, COls, operating instructions, etcetera). When rules are not being followed, inform management. If there are deficiencies in the directives, make recomniendations via chain of command to get them changed.
4.11.2.4. Operator Proficiency. Check operator's proficiency to see how well they are working and if they need training. Checks will cover all operator rules (such as CRITIC processing, message distribution, STREAMLINER operations, etcetera).
4.11.2.5. Workload. Get data on the volume of message processing in the CSF. Examine the data by analyzing the type of information, precedence, classification, Defense Special Security Communications System (DSSCS) or General Service (GENSER), and peak periods. Management must use what is learned to plan work schedules, operating hours, and guides for information flow.
4.11.2.6. Handling Times. Check CSF and remote CSF in-station handling time for processing message traffic to determine trends, problem areas, and improve processing time. Where the volume of message traffic is large, it is not practical to check every message to determine handling times. Therefore, CSFs and remote CSFs will use some form of sampling which accurately shows the time used for processing. When a sample method is used, only a percentage of the total volume of message traffic is checked. The more samples selected for checking, the more accurate the standard will be. A check of approximately 5 to 10% of the total traffic volume over the operating period shows an accurate in-station handling time. The following criterions will be used within AFIC:
PRECEDENCE OBJECTIVES SPEED OF SERVICE CRITIC 2 minutes FLASH 6 minutes IMMEDIATE 12 minutes PRIORTY 33 minutes ROUTINE 179 minutes
PRECEDENCE OBJECTIVES SPEED OF SERVICE
CRITIC 2 minutes
FLASH Not fixed. Handled as fast as
humanly possible with an objective
of less than 10 minutes.
IMMEDIATE 30 minutes
PRIORITY 60 minutes
ROUTINE 180 minutes
4.11.3. Service Messages. These are used by CSFS, remote CSFS, and CORs for exchanging information regarding misrouted, incomplete delivery instructions, or errors committed during message transmission. Service message files will be used to check problem trends and help eliminate them through the use of planned training programs. Service messages directed to a remote terminal will handled by that remote (except HQ AFIC, Security Hill remotes). Informational and procedural assistance will be given by the host.
4.11.4. Equipment and Circuit Performance. Check the efficiency of the equipment and circuits, since they have a great effect on speed, reliability, accuracy, and security of messages processed. M&R analysis activities must bring poor trends to the attention of CSF and remote CSF management personnel who must then work with the applicable agency to resolve the problems.
4.11.5. Communications Operating Performance Summary (COMOPS) and Communications Improvement Memorandum (CIM). Use the COMOPS and CIM provided under the message quality control program according to ACP 121, US Supplement I 0 and JANAP 128. The information provided is excellent for analysis purposes, since it gives data on errors committed. M&R analysis activities must try to find the cause of the errors and give management personnel recommendations for eliminating them. The AFIC standard regarding CIMs is 25% -error rate.
4.12. Retention of Messages:
4.12.1. Claims of Loss. To satisfy claims of loss or nonreceipt of messages, CSFs and remote CSFs will keep a temporary reference file of the hard page copy of messages sent by the activities they service. Due to the bulk of such files and other operational considerations, keep originated message on file for IO days. Electronic record copies will be kept for 30 days.
4.12.2. Retain:
4.12.2.1. History (journal) tapes 30 days.
4.12.2.2. Service directories 30 days
4.12.2.3. Floppy diskettes 30 days.
4.12.3. Cryptographic Compromise. Message page copy, floppy diskettes, and records which are involved in a cryptographic compromise will be retained until directed to be destroyed.
4.12.4. Rescinded or Superseded. General messages addressed to the CSF, remote CSF, or COR will remain on file, either in hard page copy or electronically, until rescinded or superseded by the responsible authority. See attachment 3 for a list of general message tides.
CHAPTER 5
MESSAGE HANDLING AND ADMINISTRATIVE PROCEDURES
5.1. Introduction. This section provides procedures for message processing. First class communications service requires close cooperation between users and the CSF and remote CSF.
5.2. Outgoing Message Processing:
5.2.1. Message Originator Responsibilities. The releasing official makes sure that:
5.2.1.1. IMMEDIATE and higher-precedence messages are delivered to the CSF and remote CSF as fast as possible. The base information transfer system (BITS) may be used to deliver Priority and Routine precedence messages to the CSF. BITS will not be used to deliver Immediate and Flash precedence messages to the CSF.
5.2.1.2. Message originators may request the COR or CSF to confirm when an electrically transmitted message has reached its addressee or servicing base telecommunications center or CSF. Limit such requests only to those messages whose nondelivery would have a severe military, political, or loss-of-life impact. Do not request confirmation of delivery on general messages, other messages having wide distribution, or nonelectrically transmitted messages. Exceptions are messages originated by or addressed to the AFIC Commander, Vice Commander, or Chief of Staff, when on temporary duty (TDY). Message originators will contact their servicing COR or CSF for special instructions to annotate confirmation of delivery on their messages.
5.2.1.3. Security regulations are followed when sending classified messages to the CSF. Package and receipt for such messages according to DOD 5200.1R/AFR 205-1. Messages which require special handling will not be delivered to the CSF via BITS.
5.2.1.4. If additional copies of an outgoing message are needed to be sent by nonelectrical means, or copies for local or staff distribution, the releaser makes sure the original hard page copy with signature and DTG entered is used to make the additional copies. The releaser is responsible for copying and distributing copies of outgoing messages. The CSF will not reproduce additional copies of outgoing messages for customer-related responsibilities.
5.2.2. CSF or COR Responsibilities:
5.2.2.1. Immediately timestamp all messages (except CRITICs). Review 10% of the total traffic volume over the entire operating period to show an accurate instation handling time. If handling times cannot be car, advise HQ AFIC/SCM of the circumstances. Keep a record of these times on file for 6 months. Use AFIC standards for instation handling times.
5.2.2.2. The following mediums will be used for message preparation:
5.2.2.2.1. Narrative. DD Form 173, Joint Messageform or plain bond paper as allowed in AFR 10-1. Review the form to ensure all blocks are properly completed per AFR I 0- 1.
NOTE: AFIC policy is to reduce narrative (DD Form 173 and plain bond paper) wherever possible, therefore, all units should encourage the use of floppy diskette processing.
5.2.2.2.2. Floppy Diskette. The "ABOVEBOARD" program is the software used to generate messages on floppy diskette for processing by the CSF, remote CSF, or COR. Confine processing messages on floppy diskettes to activities from within the special compartmented information facility (SCIF) and authorized customers located outside the SCIF in govemment-approved facilities. Customers outside the SCIF can prepare messages on floppy diskettes in ABOVEBOARD or they may use any word processing software and save the file as an ASCII text file. Government-approved facilities are any building, room within a building, or area within a building, authorized for processing classified information. Access to these buildings or rooms is controlled in such a way that classified information cannot be inadvertently viewed or accessed by uncleared or unauthorized personnel. Approval authority for this determination is the base security police. All floppy diskettes delivered to the CSF, remote CSF, or COR from outside of a SCIF will be write-protected. The write-protect tab will not be removed while the diskettes are being processed. This will ensure that no information is written to the diskette while it is being processed. The following special handling messages can be processed on floppy diskette provided they do not contain an SCI caveat above SI: INSPECDIS, EYES ONLY, EXCLUSIVE FOR, LIMDIS, and PERSONAL FOR.
5.2.3. Transmitting Floppy Diskettes from Outside the SCIF:
5.2.3.1. Before processing disks from outside the SCEF, units wishing to use this procedure will supply the CSF or remote CSF with new blank disks.
5.2.3.2. CSF personnel will format the disks in MS DOS as nonbootable and each unit will be re sponsible for developing their own accounting procedures.
5.2.3.3. When the diskette is received with message traffic for transmission, ensure the disk is writeprotected.
5.2.3.4. Place the disk in a stand alone PC to assure that it contains only the message traffic listed on the AFIC Form 156, Diskette Messageform, to be sent. Also, run a VIRUS check against the disk using the VIRUS check program.
5.2.3.5. After the messages have been transmitted, CSF or remote CSF personnel will verify that no residue message traffic is on the diskette.
5.2.4. Transmitting Floppy Diskette from Within the SCIF:
5.2.4.1. When the diskette is received with message traffic for transngssion, ensure the disk is writeprotected if it is not marked "SYSTEM HIGH". Place the diskette in a stand alone PC to ensure that it contains only the message traffic listed on the AFIC Form 156.
5.2.4.2. The use of a local area network (LAN) to facilitate message processing (sending or receiving) is authorized. Security and integrity procedures must be in place to ensure proper message handling. 'Mere must be an air gap between the STREAMLINER terminal and the LAN node.
5.3. Incoming Message Processing. The addressee and CSF, remote CSF, and COR each have responsibilities in the message distribution process.
5.3.1. The Addressee:
5.3.1.1. Must establish a central point of distribution for messages addressed below the 2-letter functional address symbol (FAS).
5.3.1.2. Provide the SC personnel a message management letter (MML) which identifies personnel authorized to pick up unclassified messages, those authorized to receipt for classified messages and individuals authorized to receipt for messages requiring special handling (SPECAT, LIMDIS, etcetera). The MML will contain the name, grade, social security account number or civilian identification card number, current security access, and specific special handling designator to which the individual has been granted access. The NML should be classified as appropriate and contain the statement: "This letter contains Privacy Act Information. Release of information herewith not to be made without written consent of individuals." For SPECAT messages, the letter will designate the specific special handling or category designator for which the individual has been granted access. Do not use all inclusive phrases (such as "cleared for all SPECATS" or "cleared for all SPECAT codewords"). The program and codewords must be identified in the letter and each tide, and signature of the authorizing official. Authorizing officials are organization or activity commanders or the appropriate directorate chief at intermediate headquarters or MAJCOM level. The commanders' signature verifies the security access of all individuals listed on the letter. The authorization letter must be updated semiannually or as changes occur.
NOTE: If an appropriate authorization list is not on file at the CSF, remote CSF, or COR, the SC will call the organization or activity commander, deputy commander, acting commander, or the appropriate directorate chief at the intermediate headquarters or MAJCOM level. The commander may personally receipt for the message (after proper identification).
5.3.1.3. Provide the CSF or remote CSF a list of representatives to be notified by telephone on receipt of Priority or higher precedence messages during and after normal duty hours (24 hours). Telephone answering machines will not be used to replace a person who can answer and take responsibility for the high precedence message notification. This list must be reviewed and updated at least semiannually. Addressees may opt not to be notified on Priority messages, but this option must be in writing and on file. This requirement may be combined with the message management letter.
5.3.1.4. Provide for immiediate pickup of messages that are high-precedence or those that require special handling.
5.3.1.5. Message distribution is based on address or FAS or delivery instructions in the first several lines of text. All organizations expecting to receive messages must provide comprehensive subjective routing lists for their activity. At HQ AFIC, major staff offices and attached organizations will provide a comprehensive subjective routing list for their activity to the AFIC Command Center and the CSF. This list will be used to determine distribution of messages received without functional address symbols (FAS) or delivery instructions within the text. It is the responsibility of the office of primary responsibility (OPR) to ensure that all subjective routing guides are kept current.
5.3.1.6. Notify the CSF, remote CSF, or COR when they are included in an AIG. Addressees must also provide a copy of any new establishments, recapitulations, modifications, or cancellations of the AIG. If the addressees determine that they no longer need to be included in a AIG or if their title or address changes, they will notify the applicable authority of the AIG and the SC.
5.3.2. SC Responsibilities. These responsibilities include:
5.3.2.1. Delivering message traffic on floppy diskette that can only be accomplished for customers inside of a SCEF.
5.3.2.2. Developing procedures for delivery of message traffic on floppy diskettes to all customers inside of a SCIF that receive over-the-counter service.
5.3.2.3. Receiving and handling properly all incoming messages. This responsibility starts with the time of receipt (TOR) and continues until the time of delivery to the addressee. Processing all incoming messages in order of precedence on a first-in-first-out bases (except CRMCS, which are processed ahead of all other message traffic). Commanders will not authorize CSF personnel to pick up messages from originators or deliver messages to addressees location.
5.3.2.4. Protecting information against loss or compromise.
5.3.2.5. Ensuring the messages are legible. Reviewing message headers for content indicator codes or operating signals that require action.
5.3.2.6. Distributing only one (1) copy of each message to the appropriate 2-letter internal distribution office or single office for an organization. Any additional message reproduction requirements for a specific FAS will be made by the internal distribution office.
5.3.2.7. Ensuring messages are only released to the intended addressee, or forwarding the message through BITS or on a LAN so designated for message distribution.
5.3.2.8. Ensuring classified and privacy messages are delivered properly. Collateral Top Secret messages will be delivered according to DOD 5200.1-R/AFR 205-1, paragraph 7-300.a.2(AF). In the case of Collateral Top Secret SPECAT messages, they will be delivered according to the instructions for SPECAT. The person authorized to receive the SPECAT message is required to notify the unit Top Secret control authority (TSCA) of the message receipt. Envelope all SPECAT, Collateral Top Secret, LIMDIS, INSPECDIS, and other privacy messages, before effecting delivery.
5.3.2.8.1. "PERSONAL FOR" messages will be delivered only to the individual named or designated representative. The following rules apply:
5.3.2.8.1.1. They may be classified or unclassified.
5.3.2.8.1.2. They will not be readdressed.
5.3.2.8.1.3. They will be placed in an envelope.
5.3.2.8.1.4. The will not be delivered through normal delivery channels or BITS unless specifically requested by the individual named.
5.3.2.8.1.5. The caveat maybe used either as "PERSONAL FOR (NAME)," or "PERSONAL FOR (NAME) FROM (NAME) EYES ONLY," etcetera, or any combination thereof.
5.3.2.8.2. Inspector distribution (INSPECDIS). The Inspector General activities use this designator within and between Air Force activities only. Place INSPECDIS right after the security classification or other appropriate control designator. It flags the message for distribution only to the office addressed and for viewing only by Inspector General personnel. Limit the handling of these messages to the minimum number of personnel needed to get the message from the writer to the reader. INSPECDIS may be used with both classified and unclassified messages.
5.3.2.9. Annotation Procedures. Unless machine printed, mark or stamp all incoming messages with the time of receipt (TOR), receiving operator's initials or prosign, and the appropriate security classification.
5.3.2.9.1. Review Procedures. Scan all incoming messages received in the for legibility and completeness as follows:
5.3.2.9.1.1. Correct minor garbles that do not affect the readability of a message and process the message for delivery to addressees.
5.3.2.9.1.2. Get a retransmission in whole or in part by initiating a service action if a message is received incomplete or garbled.
5.3.2.9.1.3. Release PRIORITY and higher-precedence messages to the addressees marked "SUBJECT TO CORRECTION."
5.3.2.9.2. Hold routine precedence messages until a reply to the service action or corrected copies are received.
5.3.2.9.2.1. When a reply is received, attach it to an AFIC Form 1503, and forward it to the appropriate agency. In the remarks section of the AFIC Form 1503, fully identify the portion of the message being forwarded. Include the "from line", the DTG, and the subject of the original message (if unclassified).
5.3.2.9.2.2. High precedence procedures. Ensure Immediate or higher-precedence messages are delivered to addressees in an expeditious manner.
5.3.2.10. Handling and logging incoming messages. Personnel will:
5.3.2.10.1. Record the receipt of messages on AFIC Form II 1, Channel Number Sheet, when no automated procedures are in place to record receipt of incoming messages.
5.3.2.10.2. Review the automated digital network (AUTODIN) and (CRMCOMM) heading for content indicator codes, operating signal, or communications identifiers (ZYVW, ZDKW, ZZSW, etcetera), that require attention or reply.
5.3.2.10.3. Disseminate incoming messages according to addressees listed in the action and information lines (format line 7 and 8).
5.3.2.10.4. Notify addressees of Priority and above precedence messages (during normal duty hours) for pickup. After normal duty hours, notify according to the message management letter. At HQ AFIC, after duty hours the Command Center will notify addressees on immediate and higher-precedence messages based on content.
5.3.2.10.5. Keep an AFIC Form 103, Message Delivery Register, on all messages, that require a receipt according to DOD 5200.IR/AFR 205-1 and USAFINTEL 201-1.
5.3.2.10.6. Use the AFIC Form 107, General Message Record, to record all active and rescinded general messages. Stations that have an automated data base for this function may use it instead of using AFIC Form 107. Ensure that all information contained on the form is also located in the automated database and that backup copies are available.
5.3.2.10.7. Place messages in distribution for the addressees. Commanders, upon request, may receive a copy of all messages addressed to their units; however, SC personnel will not be tasked to make up a read file.
5.3.2.10.8. Using separate files for each day, ensure messages are sequentially filed by time of receipt. Journal tapes may be used to satisfy this requirement. Floppy diskettes containing archive copies of receive and feedback messages may also be used to satisfy this requirement.
5.3.2.10.9. Destroy messages and other records according to AFM 12-50 and DOI- 103.
5.3.2.11. Preparing Distribution. Processes all inconiing electrical messages for distribution to the addressees according to the speed of handling required by the precedence, classification, and special handling instructions. SC does not process nonelectrical messages, memorandums, letters, forms, etcetera. Preparation rules for distribution are as follows:
5.3.2.11.1. Determining the local addressee. Narrative messages normally have the unit or activity and FASs in the address elements and delivery instruction (if used) in the first few lines of text. Use this address information to get the messages to the local addressees. Operators will read the first ten lines of text or until end of passing instructions, which ever is longer to find the message addressee or FAS if required.
5.3.2.11.2. AIG and DAG listings. If the message is addressed to an AIG or DAG and has an FAS assigned, address the message to the external FAS and the addressee element promulgated in the AIG.
5.4. Error Messages:
5.4.1. After contacting the originator, Priority and above messages will be corrected and transmitted if possible.
5.4.2. Return the copy of all Routine error message printouts and a AFIC Form 1503 to the originator for correction. It is the responsibility of the message originator or releaser to ensure that all messages returned due to errors are corrected and returned for further processing.
5.4.3. When fixing errors on DD Form 173 which are to be transmitted over an OSU, use only delete symbol editing or, if using a typewriter, a correction ribbon to make the corrections. All Routine precedence messages that do not contain a releaser's signature or have a security mismatch will be returned to the originator without further processing. SC personnel will call the message originator on Priority and higherprecedence messages and attempt to correct plain language addresses (PLA), and security mismatch and obtain verbal authorization to transmit the message. Use secure (STU-111) telephones or NSTS telephones when requesting information on classified messages. The originator, or CSF, remote CSF, or COR may cancel omitted messages because of major errors. The originator is required to draft another message referencing the message to be cancelled. Use 'ZFR" service wire procedures to cancel already transmitted messages. The originator will send a new message canceling the transmitted message and provide the correct information. If the errors are so major that a message cannot be sent, cite the errors and send the message and the AFIC Form 1503, Message Correction Notice, to the releaser for correction. Do not hold the message until the next duty day.
NOTE: (At HQ AFIC Only.) Messages which have been prepared by staff agencies for command section release that contain errors preventing processing will not be returned to the originator. Coordinate with the message drafter using secure telephone to obtain corrections to continue processing the message. Do not return the message. Always obtain the individuals name that approved the change. Enter this information in the duty report.
5.4.4. Pen-and-Ink Corrections. If the errors are minor, correct them after checking by telephone if the message is unclassified or by secure means if classified or by asking the message originator to come to the CSF, remote CSF, or COR.
5.5. Service Messages. Limit service messages to base telecommunications centers, CSFS, and remote CSFS. Do not send service messages to customers.
5.5.1. Prepare all service messages according to acts, JANAP-1 28, and DOI-1 03. Ensure they are answered in a timely manner as specified in the these references and are checked by the shift supervisor.
5.5.2. Develop local OIs to cover the processing of service messages.
5.6. Local Area Networks (LAN). AFIC encourages the use of LANs to enhance message distribution. The following procedures are the minimum that must be in place:
5.6.1. The key word or office symbol search that distributes messages to the users mailbox must:
5.6.1.1. Show every conceivable example of message classification. For example; the search command must be able to catch N A T 0 or NATO, PERSONAL FOR, or Personal For. The search process must be able to catch and place any special handling messages in an appropriate mailbox for review.
5.6.1.2. Allow users to access only their mailbox of messages unless there is an agreement between parties that all message traffic will be available to any or all users.
5.6.2. Detailed procedures for the operation of the LAN must be incorporated into an operating instruction (01) or handbook. The procedures for using the LAN and its limitations must be included in a customer education handbook.
CHAPTER 6
MAGNETIC MEDIA HANDLING AND STORAGE MANAGEMENT
6.1. Care and Handling of Magnetic Media. Improper handling of magnetic media cannot only lead to premature failure of the media, it could also cause a catastrophic loss of data. Never store magnetic media near electric motors or other electronic equipment as the magnetic fields generated by the equipment can destroy the data stored on the media. Proper care and preservation of magnetic media is necessary to get maximum use and efficiency while preserving information on the tape, diskette, or disk pack. Shortened life is generally attributed to improper handling and storage and packing techniques..
6.1.1. Magnetic Tape:
6.1.1.1. General. Tape reels should always be handled by the hub. Wrap around rings, canisters, or other such devices must be used to protect the reel and tape during storage. Reels must be returned to their containers before they are placed in storage. Magnetic tapes should always be stored in the vertical position, however, they may be temporarily stacked horizontally for up to 24 hours when in protective canisters. They must never be stacked more than five reels in height.
6.1.1.2. Shipping Tape. The outer shipping container must have a responsible degree of water resistance and the strength and rigidity to protect the tape from damage. Magnetic tape containers may be so marked, or an Optional Form 85, Fragile-Magnetic Tape Label ("FRAGILE, MAGNETIC TAPE, KEEP AWAY FROM ELECTRIC MOTORS, SCANNING DEVICES, AND MAGNETS") may be used. Ship classified tapes according to DOD 5200.1-R/AFR 205-1.
6.1.1.3. Tape Errors. The wind or rewind tension, capstans, read or write heads, and tension applied during tape starts may cause damage or excessive wear to the tape. Operators should maintain tape transports on a timely schedule (including cleaning the capstans and heads and removing accumulated oxide from the feed path mechanisms on the tape drives). Accomplish this according to vendor contract.
6.1.1.4. Tape Cleaning and Rehabilitation. Frequency of cleaning or certifying tapes will be documented in local OIs. Tapes are cleaned using equipment which passes the tape over a knife edge to remove any contaminates from the oxide surface. This equipment can remove the causes of about 90 percent of the tape errors. Although tapes are sample tested for quality control before sale, some tapes still have manufacturing defects. To prevent errors due to residue created during the manufacturing process, clean all new tapes prior to initial use. In addition, if a tape tester or certifier is available, check a sampling of all new tapes. Tapes, both analog and digital, containing defects can frequently be restored by cleaning or certifying.
6.1.1.5. Tape Certification Equipment. Tape certification equipment locates and stops at every error that was not removed by the first cleaning. If there is a large number of tape errors, run the tape through the tape cleaner a second time and recertify the tape. If errors are within the first or last 500 feet of the tape, cut off the bad portion. If errors are between the 5001900 foot mark "Destroy the tape".
6.1.2. Disk Packs:
6.1.2.1. Temperature Control. Disk surfaces expand and contract with significant changes in temperature. 'Me disk pack should, when possible, be conditioned to the computer room temperature for 16 to 24 hours before mounting on the drive. This prevents loss of data caused by a shift in track location as a disk pack becomes acclimated to the environment.
6.1.2.2. Disk Pack Storage. Make sure that disk packs are always stored with the bottom cover attached. This prevents contaminants from reaching the pack surfaces. Disk packs must not be stacked one on another. The computer room environment is best for disk pack storage.
6.1.3. Floppy Diskettes:
6.1.3.1. Storage. Diskettes should not be stored in such a way that they will sag, slump, or be compressed. When not in use, store diskettes in their protective envelope.
6.1.3.2. Handling. Proper diskette handling is essential to reliable operation. The surface of a diskette must never be touched or subjected to physical stress.
6.1.3.3. Shipping. When shipping diskettes, use packaging that will guarantee the integrity of the_ diskette. Use corrugated cardboard on each side of the diskette with the ridges of one sheet perpendicular to the ridges of the other. Ship classified diskettes according to DOD 5200.1-R/AFR 205-1 and other applicable security documents.
6.1.3.4. Transmission of Special Handling Messages. The following special handling messages can be processed on floppy diskette via STREAMLINER provided they do not contain an SCI caveat above SI:
6.2. Storing Magnetic Media:
6.2.1. On-Site Storage. Storage areas for computer programs and data must be in a fire-retardant vault area (when feasible) or in fire-retardant cabinets. Specifications for media storage vaults are in AFM 8815.
6.2.2. Off-Site Storage. Selected files, to include but not limited to operations programs, system builds, data base directories, etcetera must be kept in a secure area physically separated from the CSF or DPC. The selection of these files should be based on their need for recovery of the system in the event of catastrophic failure. When selecting the off-site storage location consider how close it is to the CSF or DPC, the environment (temperature and humidity), and the physical security of the building. Off-site storage must be provided even when on-site storage is available. This helps prevent losses from conditions such as fire. Frequency of update for the selected files stored offsite should be determined by the impact of using the selected files to reestablish the system. A priority schedule for recreating files, as well as those products specified in other areas of this regulation, should be placed at the off-site storage location.
6.3. Magnetic Media Libraries. The CSF or DPC will establish procedures to cover control, security, and upkeep of all storage media used by the organization to include analog and digital tapes, disk packs, diskettes, and optical disks.
6.3.1. Immediate Access Storage (IAS). IAS includes such parts as disks, disk packs, diskettes, drums, and mass memory. Because of the widespread use of disk storage devices, the term "disk" will be used in the paragraphs following hereafter. Procedures are intended to apply equally to other random access storage devices. The systems analyst in the CSF or CSF must record usage and have the option to record actual or estimated use, depending on the local installation or MAJCOM needs. Maintain accurate disk utilization and saturation records. Use available disk management and utilization software, as required, to effectively manage disk resources.
6.3.2. Access. Procedures must be designed to ensure only authorized personnel (those who have adequate security clearance and the need-to-know to perform duties) have access to the storage media to prevent unauthorized access to classified or privacy data, and to preclude the unauthorized removal of the storage media from the CSF or DPC. Access to tape libraries must be restricted to either tape librarians or designated operations personnel (supervisors or operators). Discovery that storage media has been damaged or is otherwise unusable must be reported to the functional system manager, with recovery prospects, as soon as possible. Contractor storage media brought into a CSF or DPC is also subjected to the established control procedures. Storage media may be reserved for use by a contractor; however, this media must be clear of all classified or privacy data unless the contractor has been authorized access to classified information per existing procedures.
6.3.3. Inventory Accountability. Records will show the current status of the library at any given moment. The information will provide the media on hand in the library, those temporarily out for cleaning or rehabilitation, magnetic media shipped out for use elsewhere, those on hand belonging to another center or organization, media stored at an off-site location, and media awaiting disposition. Procedures must be developed to make- sure that items sent to off base sites are returned in a reasonable time (tapes or disks prepared for mailing to other organizations should be marked "Copy and return within 'NN'days" if return is required). Control and inventory of classified magnetic media in the library must be as prescribed in DOD 5200. 1 -R/AFR 205-1 and AFR 205-16.
CHAPTER 7
SYSTEMS CONTROL FACILITY
7.1. Systems Control Facility. Instructions must be developed and published jointly between the local CSF and systems control facility (SCF) or patch and test facility (PTF) NCOICS. Include as a minimum:
7.1.1. Instructions for operating the SCF and PTF according to NSA COI-104 and COI-101 as well as procedures for using SCF and PTF order wires.
7.1.2. A requirement that all SCF and PTF operators be indoctrinated in the proper use of station equipment before being assigned to duty and at frequent intervals thereafter to maintain proficiency.
7.1.3. Instructions forbidding the use of unsecure telephones to set up cipher contact on CRMCOMM/ DSSCS circuits. Use the SCF or PTF printers instead. Use fixed station callsigns when coordinating circuit information via unsecure means (teletype or voice).
7.1.4. Requirements for familiarity and compliance with applicable AFKAOS, AFSALS, and AFKAMs when SCF or PTF has cryptoreset responsibilities.
7.1.5. Procedures to ensure that systems-control monitor rolls or electronically-archived notes are maintained on all unsecure SCF and M circuits. Cryptosecurity officers or qualified persons designated by them will screen the monitor rolls and ensure that necessary corrective action is initiated on detected violations.
7.1.6. Designation of an individual in the SCF and PTF as the station-circuit manager. In addition to preparing reports according to COI-101, and AFICR 700-8, the manager will maintain all circuit files. COI-104/AFIC Supplement I contains procedures and information on maintaining circuit history data cards.
7.2. General Operating Procedures:
7.2.1. Ensure that alternate routing procedures from the CSF to the local supplier are available for all appropriate black side circuits.
7.2.2. Notify local users of transmission failures, preemptions and subsequent restorative actions.
7.2.3. Label patch bays and interbays, by CCSD, restoration priority, etcetera.
7.2.4. Maintain block diagrams showing paths between connected stations that would pen-nit a reroute.
7.2.5. Ensure effective utilization of spare equipment for offpeak traffic periods to conduct scheduled maintenance.
7.2.6. Service interruption schedules should be requested IO days in advance.
7.2.7. The following reports must be submitted according to the appropriate guidelines:
7.2.7.1. Circuit Outage Reports.
7.2.7.2. Equipment Outage Reports.
7.2.7.3. Abnormal Conditions Reports.
7.2.7.4. Quarterly Network Reports.
7.2.7.5. Communications Outage Reports.
7.2.8. An effective circuit reliability program must be established to detect degrading trends and identify circuit and equipment deficiencies.
7.2.9. Out-of-service quality control (QC) tests and inservice PTCs must be conducted according to applicable directives.
7.2.10. FCO/PTF orderwire transcripts must be maintained for a period of 30 days.
7.2.11. Establish procedures on the proper use of the DCC ordering net in regards to use of station callsigns and high precedence alarms.
7.2.12. Maintain a DD Form 1441, Circuit Data, for each circuit.
7.2.13. Copies of the initial TSO and latest TSO reflecting current configuration and control office assignment must be maintained by the control office designated in the TSO.
7.2.14. Maintain current history folders on all circuits terminating or passing through the SCF.
7.2.15. Maintain a master station log annotating shift change, narrative information on power failures, complete system and equipment outages, circuit outages, unusual situations and other events deemed appropriate.
7.2.16. Log and document all service disruptions regardless of duration.
7.3. Contingency Operations:
7.3.1. Ensure that applicable contingency plans are immediately available in the SCF/PTF or collocated area.
7.3.2. Periodically exercise contingency plans allowing personnel to become familiar with the required responsibilities.
7.4. Training:
7.4.1. Include in your training plan AFR 50-23 and DISA 310-70-1, Volume 1.
7.4.2. Have inexperienced controllers demonstrate an understanding of the capabilities and application of equipment, patching, and test procedures prior to station qualification.
7.4.3. Ensure proper training and understanding of the alternate CRITICOMM system management program.
7.4.4. Six months after initial station qualification, perform a 10 percent task evaluation on all qualified tasks.
7.5. Systems Control Qualification Training:
7.5.1. AFR 50-23 provides policy and procedures to personnel who are responsible for planning, developing, conducting, managing, and evaluating Air Force enlisted speciality training (EST).
7.5.2. The EST has primary principles such as: realism, integration, flexibility, and simplicity. Each unit should develop their own training program and job qualification standard (JQS) unique to their station. Ensure that the training program and JQS are according to AFR 50-23.
CHAPTER 8
SELF INSPECTION PROGRAM
8.1. Self Inspection Program. The unit SC will designate individuals (inspectors) to conduct self inspections. Self inspections will be accomplished using AFICP 123-700-2 and AFICP 123-56-2. Inspections will be conducted according to unit procedures but at least annually or when a change in the SC occurs. Send a copy of the self imposition to the intermediate headquarters communications-computer systems officer.
8.1.1. The unit SC will review the results of the self inspection and refer any action items to the appropriate individual or office.
8.1.2. When required, priorities will be assigned indicating the order in which discrepancy items should be addressed. Followup status will be addressed at staff meetings or other means deemed appropriate, until all items are closed.
8.2. The Self Inspection Inspectors will:
8.2.1. Be responsible for ensuring the inspection is thorough, objective, and accurately documented.
8.2.2. Determine if the questions or item is applicable to the functional area or division inspected. If not, place "Nonapplicable (N/A)" next to the question number.
8.2.3. Answer the questions or item by explaining "how" the section is complying with the guidance or regulations. Do not simply answer "yes" or "no".
8.3. Intermediate Headquarters Responsibilities:
8.3.1. The intermediate headquarters will review all self inspections to determine if:
8.3.1.1. The self inspection was conducted in a timely manner.
8.3.1.2. Questions and answers have been adequately addressed.
8.3.1.3. MAJCOM guidance is warranted.
8.3.1.4. Staff assistance is required.
8.3.2. Intermediate headquarters will keep all self inspections on file for a minimum of 2 years. Notify the MAJCOM with any difficulties that cannot be resolved within the scope of the intermediate headquarters.
C. DOUGLAS COUTO
Lt Col, USAF
Director of Information Management
LIST OF GENERAL MESSAGE TITLES
A1.1. United States Air Force General Message Titles:
A1.1.1. ALMAJCOM-SOA. Message originator: HQ USAF, addressed to all major commands and separate operating agencies (SOA). SOAs will include direct reporting units.
A1.1.2. ALZICOM-SOA. Message originator: HQ USAF, addressed to Continental United States (CONUS) MAJCOMs and SOAS. SOAs will include direct reporting units.
A1.1.3. ALMAJCOM. Message originator: HQ USAF, addressed to all MAJCOMS.
A1.1.4. ALZICOM. Message originator: HQ USAF, addressed to CONUS MAJCOMS.
A1.1.5. ALPERSCOM. Messace originator and purpose: USAF Military Personnel Center, Randolph Air Force Base, Texas, addressed to all MAJCOMs and SOAs concerning general subject of military personnel.
A1.2. Non-USAF General Message Titles (APPLICABLE TO USAF ORGANIZATIONS):
A1.2.1. ALMILACT. Message originator and purpose: Joint Chief of Staff (JCS), uses to impose MINIMIZE or to issue other instructions or information having worldwide application.
A1.2.2. ALSVCACT. Messaae originator and purpose: JCS, uses to impose MINIMIZE or to issue other instructions on a classified basis having worldwide application.
A1.2.3. JAFPUB. Message originator and purpose: JCS uses to issue corrections to JANAPs and ACPS, including supplements that require wide distribution.
A1.2.4. EUCOMACT. Message originator and purpose: A general message title assigned to United States Commander in- Chief, Europe, (TJSCINCELTR) to impose MINIMIZE or other instructions or information which have USCINCEUR command application.
A1.2.5. JANAFPAC. Message originator and purpose. A general message title assigned to CINCPAC and addressed to US MAJCOMs within the Pacific Command on matters of joint interest. Redistribution is accomplished at the discretion of the receiving US MAJCOM.
A1.2.6. ANTCOMACT. Message originator and purpose: A general message assigned to Commander in Chief, Atlantic, to impose MINIMIZE or other instructions or information which have Atlantic Command application.
A1.2.7. PACOMACT. Message originator and purpose: A general message title assigned to CINCPAC to impose MINIMIZE or other instructions or information which have Pacific Command application.
A1.2.8. USSOCOMACT. Message originator and purpose: A general message tide assigned to US Commander in Chief, Southern Command, to impose MINIMIZE or other instructions or information which use military communications.
A1.3. AFIC General Message Title:
A1.3.1. ALAFICCOMSTA (AU AFIC CRITICOMM Support Facilities and STREAMLINER Customer-Operated Remote). Message originator and purpose: A general message assigned to AFIC used to issue guidance and instructions to all AFIC CRITICOMM facilities (CSFS, remote CSFS, and CORS) which have command application. Additionally, ALAFICCOMSTA is sent to all AFIC wings for information purposes of appropriate actions required with or by their subordinate units.
A1.3.2. ALREMOTES (AU Connected AFIC STREAMLINER Remotes). Message originator and purpose: A general message assigned to AFIC STREAMLINER facilities for use by the system administrator to issue MINIMIZE information and other guidance or instructions to all in-house and distant STREAMLINER remote customers.
HANDLING INSTRUCTIONS
Parentheses Required:
PHRASE GENSER SI Codewords NO NO EXCLUSIVE FOR (including Name) YES YES FOUO YES YES INSPECDIS YES YES LIMDIS NO NO NOFORN NO NO NOCONTRACT YES YES ORCON YES YES Passing Instruction YES YES PERSONAL FOR (Including, Name) YES YES PROPIN YES YES SIOP-ESI NO YES SPECAT NO YES WNINTEL YES YES RELEASABLE TO AUSTRALIA NO YES RELEASABLE TO UNITED KINGDOM NO YES RELEASABLE TO CANADA NO YES RELEASABLE TO BELGIUM NO YES RELEASABLE TO DENMARK NO YES RELEASABLE TO FRANCE NO YES RELEASABLE TO GERMANY NO YES RELEASABLE TO GREECE NO YES RELEASABLE TO ITALY NO YES RELEASABLE TO NETHERLANDS NO YES RELEASABLE TO NORWAY NO YES RELEASABLE TO PORTUGAL NO YES RELEASABLE TO TURKEY NO YES RELEASABLE TO NATO NO YES
1. If more than one country is used, separate them by a slant EXAMPLE: RELEASABLE TO UNITED KINGDOM/CANADA/AUSTRALIA.
2. In order to keep this regulation unclassified, some phrases
were omitted from this guide. If additional information is required,
contact your servicing CSF or remote CSF.