This regulation prescribes command policy and general in-station procedures for telecommunications supporting the Air Force Intelligence Command (AFIC) mission and certain base communications customers. It applies to all organizations operating a critical intelligence communications (CRITICOMM) support facility (CSF) or customer-operated remote (COR) supporting AFIC. NSA COI-101, NSA COI-104, and DOI-103 prescribe detailed CRITICOMM operating instructions (COI) and Defense Special Security Communications System (DSSCS) Operating Instructions (DOI). The regulations does not apply to AFIC-gained Air National Guard or Air Force Reserve units.

Introduction. Deviations from established procedures outlined in this document are not permitted unless specifically authorized by HQ AFIC/SCO. However, if a specified procedure in this directive is unacceptable to a station, the communications-computer officer or NCOIC may prescribe alternate temporary procedures to meet specific requirements. Forward any alternate procedures to HQ AFIC/SCO. HQ AFIC/SCO issues changes or revisions to this publication. Printed changes are distributed through normal administrative channels. Interim message changes are distributed by all AFIC CRITICOMM station (ALAFICCOMSTA) messages according to AFR 5-8/ESC Sup 1. Communications-Computer Systems officers or NCOICs will provide message changes to their Information Management Sections (IM) so that they may issue the message change to all holders of this regulation. Enter all changes immediately upon receipt. Send recommended changes to this regulation through normal command channels to HQ AFIC/ SCO. HQ AFIC/SCO reserves the right of approving or disapproving all recommendations. Use functional address symbols (FAS) listed in attachment 1, when addressing correspondence for CRITICOMM support of an AFIC unit. AFIC has operational control over all Air Force CRITICOMM facilities through planning and programming, establishing operational standards, and acting as the focal point for the Air Force's portion of the CRITICOMM/DSSCS network.

Corrected copy of AFIC REGULATION 700-6

This revision updates terms and definitions; adds a new section on remote CRITICOMM support facilities (CSF), deletes three tables, and outlines duties associated with customer-operated remotes (COR). Deletes AFIC 307 attachments.

ESCR 700-6, 30 September 1989.


Mr Jolly and MSgt Collins


Col Norman M. Slocum


TSgt Marsha J. Bryan










1. CRITICOMM Support Facility (CSF). CSFs are AFIC STREAMLINER communications operations that process critical intelligence message traffic and are tied into the Defense Communications System (DCS), the STREAMLINER system tied directly into the automatic digital network (AUTODIN).

2. Remote CSF. Remote CSFs are STREAMLINER remote operations that are operated by communications-computer operations personnel. They are not required to fulfill all the requirements of a CSF (STREAMLINER host). It must be noted that certain AFIC remote CSFs are connected to Army or Navy STREAMLINER systems and are required to comply with (in addition to certain provisions of this regulation) the host policies and procedures for operating their remote terminal.

3. Customer-Operated Remote (COR) Facility. A COR is defined as any remote communications terminal that is operated solely by the customers. Their work includes only those communications-computer system functions which are necessary to send and, or receive the COR's information. They rely on the host automated message processing exchange (AMPE) for network control. It must be noted that certain AFIC CORs are connected to Army or Navy STREAMLINER systems and are required to comply with (in addition to certain provisions of this regulation) the host policies and procedures for operating their remote terminal. The COR is responsible for ensuring proper message accountability and control of all originated and terminated message traffic. Accountability of message traffic can be satisfied by using AFIC Form 111, Channel Number Sheet, or AF Form 3133, General Purpose Form.

4. Standard Telecommunications Terminal Device (ST2D). The ST2D is a TEMPEST-tested approved personal computer connected to STREAMLINER or an OPSCOMM terminal.

5. Agency Standard Terminal Workstation (ASTW). The ASTW is a TEMPEST IBM PC/XT or PC/AT with various configuration options and TEMPEST peripherals. Specialized application software allows the ASTW to be used as a stand-alone PC, a telecommunications terminal device, or as a PC on a local area network (LAN).


6. Background. This section outlines certain policies and responsibilities for accomplishing the CRITICOMM operations mission. It outlines policies and the operational concept for CSFs, remote CSFs, and CORs. Specific functions and procedures for CSFs are in COI-101, DOI-102, DOI-103, COI-104, and other Air Force Communications-Computer Systems doctrines.

7. Terminal Station. CSFs are STREAMLINER sites connected to ASCs over which predetermined categories of classified traffic may be transmitted. The CSF normally serves only the cryptologic community and in some cases they provide general service (GENSER) base communications support, and perform some or all of the following functions:

7.1. Operate and manage DSSCS and GENSER circuits to ASCs, to include base message traffic service when other host base facilities are not available or as agreed upon by the memorandum of agreement (MOA).

7.2. Operate and manage CRITICOMM circuits to other terminal stations.

7.3. Process originated and terminated message traffic addressed to the unit.

7.4. Manage various voice systems.

7.5. Perform facility control and or patch and test functions as necessary.

8. 6948 ESS. The 6948 ESS often deploys mobile communications assets to serve as CRITICOMM facilities for emergency reaction forces. They are also tasked to augment stations during temporary abnormal conditions. This unit sets up temporary facilities and will fulfill the requirements specified for a permanent CSF except when otherwise indicated.


9. CSF/Remote CSF Layout. The unit SC will ensure that the layout of the communications-computer section is such that it will promote an efficient operation.

10. Primary and Emergency Power. All units must ensure that primary and emergency power is adequate for their communications-computer operation and advise appropriate personnel of power problems.

11. Operational and Personnel Management. The unit SC will develop policies for effective operations and personnel management to:

11.1. Ensure a cost-effective approach in managing resources.

11.2. Ensure that realignment or reconfiguration of operators will lead to manpower reductions or more effective utilization of assigned resources.

11.3. Ensure adequate scheduling of personnel during peak periods.

11.4. Ensure that only qualified personnel are assigned message preparation duties during heavy traffic periods.

11.5. Ensure that the number of personnel assigned to overhead administrative management positions are kept to a minimum to allow proper staffing of operational areas.

12. Communications Operating Performance Summary (COMOPS). For those units that receive the AUTODIN Switching Center (COMOPS), ensure that they are used as a management tool and are made available for all personnel to review.

13. AUTODIN Switching Center (ASC) Staff Visits. All units will ensure that any deficiencies noted by an ASC staff visit are corrected. A brief description of the noted deficiencies will be included in the unit's RCS: AFIC(Q) 7801 report to include corrective actions taken.

14. Remote CSFs. The following policies apply to remote CSFs:

14.1. DOI-101. You are only required to maintain a folder for each DSSCS address group (DAG) that is originated and received by the customers you support. The customer should provide you with a list of DAGs they originate or receive. They should also provide you with any updates so you can forward those onto the host STREAMLINER for inclusion in their database.

14.2. DOI-102. Your host STREAMLINER is responsible for ensuring that DOI-102 is maintained. You are only required to provide them with valid DSSCS message addressees. Valid DSSCS PLAs can be obtained from USSID-505, DIA Compartmented Address Book (DIACAB), which should be on file, and AFICR4-104. These documents should be available within the unit.

14.3. Remote CSF. The remote CSF is required to maintain the following publications: AFICR 700-6, AFR 700-7/AFIC Sup-1, AFR 700-8, Host Customer Education Guide. Other communications publications may be kept as deemed appropriate but are not mandatory for operation of a remote CSF.

14.4. AIGs. The remote CSF will keep on file all AIGS sent and received by the customers they support.


15. Standardization. COI-101, COI-104, and DOI-103 contain station operating procedures for CRITICOMM and DSSCS stations which will take precedence when there is a conflict with this regulation. ACP 121 US Sup 1, and JANAP 128, contain operating procedures for GENSER operations which will take precedence when there is a conflict with this regulation. Stations may supplement these publications with local station operating instructions (SOI) to meet operational requirements. Remote CSFs and CORs connected to a STREAMLINER facility will have on hand the latest Customer Education Guide from the host.

16. Section Structure and Duty Titles. Typical CSFs, remote CSFs, and CORs have three primary functions: receiving, transmitting, and preparing messages for delivery.

16.1. The sections normally included in a CSF are:

16.2. The functions normally included in a remote CSF are:

16.3. The functions normally included in a COR:

16.4. Use of duty titles in attachment 2 is recommended.

17. General Personnel Responsibilities. There are certain general responsibilities common to all supervisor or operator personnel performing duties in any section of a CSF and remote CSF.

17.1. Shift supervisors will:

17.1.1. Ensure that functions performed by their assigned personnel are carried out efficiently and that traffic is processed securely, accurately, and quickly.

17.1.2. Enforce procedures prescribed for message processing for both DSSCS and GENSER operations are employed.

17.1.3. Make sure that entries on station records are printed legible and that essential information is being recorded.

17.1.4. Keep operators informed of special instructions or changes in operating procedures.

17.1.5. Ensure that messages of Immediate or higher precedence are hand-carried from position to position and transmission is verified.

17.1.6. Ensure that assigned section operators do not leave their positions until properly relieved.

17.1.7. Ensure that the working areas are neat, safe, and presentable at all times.

17.1.8. Inform relieving section supervisors of changes in procedures, new or revised directives, unusual occurrences which may or have affected operations, and matters pending disposition.

17.1.9. Ensure only authorized plain language addressees (PLA) are entered into the STREAMLINER PLA data base. Use AFR 700-31, AFICR 4-104, USSID 505, ACP 117, and DOI-102, series for valid PLAs. Duplicate PLAs are not authorized.

NOTE: Ensure that operators comply with established directives in processing messages in a timely, reliable, and secure manner. Supervisors must be aware of and act immediately on any deviations.

17.2. STREAMLINER system administrators will:

17.2.1. Interface between the field STREAMLINER site, intermediate headquarters, and HQ AFIC/SCO.

17.2.2. Analyze and diagnose hardware, software, and operator problems.

17.2.3. Prepare and update STREAMLINER-related SOIs. Use as guides the STREAMLINER operator's manual, information from STREAMLINER technical bulletins, ALAFICCOMSTA messages, and system engineering documentation.

17.2.4. Prepare and forward to the NSACSS STREAMLINER Software Organization (T761), information copy to HQ AFIC/SCO, a monthly abort-code summary, when required.

17.2.5. Ensure that STREAMLINER operators are trained in the proper abort procedures so that dump tapes can be made and documented for the NSACSS STREAMLINER Software Organization (T761).

17.2.6. Build system patch tapes and check and correct any errors and build operational disk packs including the patches.

17.2.7. Maintain a log of significant hardware and software problems to analyze recurring problems and advise AFIC, NSACSS, appropriate Wing and their theater telecommunications field engineers as appropriate, when these problems cannot be resolved.

NOTE: Units will not, except in emergency situations, correspond directly with NSACSS. Unless otherwise directed, send all correspondence to your respective wing with an information copy to HQ AFIC/SCO. NSACSS offices may be included as information addressees.

17.2.8. Be responsible for repairing, testing, recertifying, receipting, issuing, shipping, or destroying all magnetic tapes or disk packs within the CSF.

17.2.9. Train and assist all site STREAMLINER personnel.

17.2.10. Assist with STREAMLINER utility program updates and STREAMLINER technical bulletins. These bulletins provide information about operations, programming, and maintenance of the STREAMLINER system. To make sure that the STREAMLINER system is operating at its maximum capability and with up-to-date software, enter all software patches received by the STREAMLINER technical bulletins into the system within 24-hours after receipt unless there is a situation which will prevent meeting the 24-hour deadline. All STREAMLINER units will acknowledge, by message to HQ AFIC/SCO, the following information on software patches:

17.2.11. Maintain a library of STREAMLINER-related instructions, directives, and other associated documentation.

17.2.12. Set up and maintain a magnetic tape and disk pack library system that will ensure proper control and disposition.

17.2.13. Not be assigned additional duties that will interfere with performing primary STREAMLINER system administrator duties.

17.2.14. Maintain a continuity folder describing all STREAMLINER related duties.

17.2.15. Perform PLA scrubdown, (with methods and result clerk), at least once a month to remove duplicate and invalid PLAs.

17.2.16. Prepare a customer education guide (in conjunction with the methods and results clerk) for local and remote users containing at least the following:

17.2.17. Provide technical assistance as requested by CORs.

17.2.18. Be responsible for the accuracy and checking of the switch supervisor console print out.

17.3. Methods and Results (M&R):

17.3.1. M&R Position. The M&R position is considered an overhead position and is not specifically identified in manning documents. M&R personnel provide quality control and statistical reporting. They provide CSF management personnel information and recommendations on the quality of service provided the user.

17.3.2. Operating Procedures. Check adherence to directives (such as ACPs, JANAPs, DOIs, COIs, OIs, etcetera). When rules are not being followed, inform management. If there are deficiencies in the directives, make recommendations via chain of command to get them changed.

17.3.3. 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).

17.3.4. Workload. Get data on the volume of message processing in the CSF. Examine the data by analyzing the type of information, precedence, classification, DSSCS and (GENSER), and peak periods. Management must use what is learned to plan work schedules, operating hours, and guides for information flow.

17.3.5. Handling Times. Check CSF in-station handling times for processing message traffic to determine trends, problem areas, and improve processing time. In CSFs where the volume of message traffic is large, it is not practical to check every message to determine handling times. Therefore, 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               SPEED OF SERVICE          

 CRITIC                  2 minutes                 

 FLASH                   6 minutes                 

 IMMEDIATE               12 minutes                

 PRIORITY                33 minutes                

 ROUTINE                 179 minutes               

PRECEDENCE               SPEED OF SERVICE         

CRITIC                   2 minutes                

FLASH                    Not fixed. Objective     
                         less than 10 minutes.    

IMMEDIATE                30 minutes               

PRIORITY                 60 minutes               

ROUTINE                  180 minutes              


18. CSF and Remote CSF Supervision and Assignment Standards. Before assigning persons to operational duties, OICs or NCOICs will interview individuals to determine familiarity with equipment and to review the individual's background in an effort to ascertain training requirements. They can determine proficiency by reviewing performance reports and other personnel data. All newly assigned persons will review OIs (as soon as possible if assigned as NCOIC) and become familiar with their position. The unit SC will ensure that all personnel assigned to the communications-computer section attend the unit's mission briefing (if not already required during initial unit in-processing).

19. Training Program. Well organized, efficient, and productive training programs are mandatory at all stations. Generally, a station's operational efficiency is no better than its training program.

19.1. Qualification Training:

19.1.1. Communications-Computer Systems Officers and NCOICs must ensure that material required for a productive training program is on hand and readily available for all personnel.

19.1.2. All training programs must be organized and presented so that each person recognizes the need and willingly accepts the training. All training should be administered at a rate equal to the trainee's learning ability to ensure that he or she understands each phase of training before going on to the next phase.

19.1.3. All 491X1 operators that perform primary duties in the CSF or remote CSF with a CRITIC mission, are expected to type a minimum of 35 words per minute with emphasis on accuracy.

19.1.4. Training may be obtained through formal on-base channels or through various typing tutorial programs.

19.1.5. Ensure duties that include the operation of a tech control, patch and test, or abbreviated patch and test are incorporated into the training plan.

NOTE: All training must be explicitly developed in the training program at each unit.

19.2. Proficiency Training. All units must set up and maintain a high degree of proficiency in CRITICOMM operations. A program of initial and continuing training and orientation is required. To be effective, you must adapt proficiency training to include all facets of each CSF and remote CSF.

19.2.1. The Air Force speciality (AFS) functional manager will determine whether or not individual training records are required.

19.2.2. Units will maintain standards on locally prepared proficiency tests from DOD 5200.1/AFR 205-1, applicable DOIs, COIs, JANAPs, ACPs, local publications, and MAJCOM operating documents dealing with applicable communications-computer operations.

19.2.3. The SC will continually review these tests for conformity with current operational doctrines. The training NCO determines the type of test to be administered each quarter to ensure a well-rounded training program. Administer at least one proficiency test quarterly, either written or practical. Post the test results in training records according to AFR 50-23.

19.2.4. Ensure that the training program requires periodic review of all pertinent CSF and COR documents.

19.2.5. Ensure that all personnel are tested quarterly in message routing and message preparation. Personnel failing these tests will be retested weekly. Document this testing in individual's training records.

19.2.6. Establish a formal written and practical examination for the award of the Special Experience Identifier (SEI) 038.

19.3. STREAMLINER Host Facilities. Ensure that an adequate training program for STREAMLINER operators covers all phases of STREAMLINER operations to include optical character reader (OCR), cathode ray tube (CRT), system console, ST2D/ ASTW, and the use of STREAMLINER utilities.

20. Quality Control (QC) Program. Each CSF will set up and maintain a continuing message QC monitoring program.

20.1. Set up and maintain an internal training and monitoring program to achieve the highest possible degree of operating efficiency.

20.2. Monthly, check a minimum of 10 percent of each operator's routing of messages, preparation of messages for transmissions, accuracy, and compliance with prescribed operating procedures. Advise supervisors and operators concerned of violations committed and appropriate corrective action required and obtain their acknowledgment.

20.3. Use a prescribed message QC test to minimize errors caused by malfunctioning equipment or circuits. This test should be sent as a minimum at the beginning of every shift change. Annotate logs and number sheets (when used) to indicate the times and results of these tests.

20.4. Improve indoctrination, supervision, and training of communications-computer systems personnel, as required, to gain increased proficiency.

20.5. Make needed improvements in any apparent or reported deficiencies by prescribing daily observation and in-station analysis of operating performance at the individual level.

20.6. Ensure the results of traffic analysis is made available to all personnel on a timely basis.

20.7. Report circuit and equipment failures or outages as required.


21. Publications. All CSFs and remote CSFs will establish a set of communications-computer systems publications. Remote CSFs and CORs will only maintain those publications necessary to operate their communications terminal.

22. Forms Prescribed and Required. Use the following forms listed below to record communications information and control messages in the CSF and remote CSF. Forms pertinent to COR operations are determine by the using activity and the host STREAMLINER. Forms required may vary.

22.1. The following prescribed forms (except AFIC Form 25) may be computer-generated on any automated system provided they contain all entries as shown on the original and are reproduced to satisfy OPR requirements:

22.1.1. AFIC Form 25, Secure Intercom Telephone Label.

22.1.2. AFIC Form 72, CRITIC Checklist.

22.1.3. AFIC Form 103, Message Delivery Register.

22.1.4. AFIC Form 106, CRITICOMM Message Register.

22.1.5. AFIC Form 107, General Message Record.

22.1.6. AFIC Form 108, Service Action Request.

22.1.7. AFIC Form 111, Channel Number Sheet.

22.1.8. AFIC Form 156, Diskette Message form.

22.1.9. AFIC Form 307, Magnetic Tape/Disk Pack Inventory.

22.1.10. AFIC Form 308, Library and History Record.

22.1.11. AFIC Form 1503, Message Correction Notice.

22.2. Additional forms required depending on the operation:

22.2.1. AF Form 614, Charge Out Record.

22.2.2. AF Form 3530, Special Category or Limited Distribution Message Envelope.

22.2.3. AFCOMSEC Form 5, Incoming/Outgoing Cryptographic Register.

22.2.4. DD Form 1441, Circuit Data Card.

22.2.5. DD Form 1753, Master Station Log.

22.2.6. DD Form 1765, Incoming Service Message Log.

22.2.7. DD Form 1766, Outgoing Service Message Log.

23. Logging Outgoing Messages. Log originated messages on AFIC Form 106 and close it out daily. When starting a register for a new day, bring forward the next unused consecutive station serial number (SSN) from the previous register. SSNs run from 0001 through 9998 and start again with 0001. SSN 9999 is reserved for CRITIC messages ONLY, you must not use it on any other message traffic. The SSN sequences will carry over from one register page to the next for each day. The Service Directory (SD) satisfies the requirement to keep a hard page file of outgoing SSNs for CSFs. Remote CSFs and CORs will print out the feedback file headers to satisfy their record keeping.

NOTE: CSFs, remote CSFs, and CORs need not use the AFIC Form 106 if magnetic media is used to accurately record and journal the originated message.

24. Logging Incoming Messages. All CSFs and remote CSFs will keep AFIC Form 103 on all messages that require a receipt according to DOD 5200.1R/AFR 205-1, AFR 205-43, and USAFINTEL 201-1. The Service Directory (SD) satisfies the requirement to keep a hard page file. CORs will print out the receive file headers to satisfy their record keeping.

NOTE: CSF and remote CSFs need not use the AFIC Form 106 if magnetic media is used to accurately record and journal the incoming message.

25. Station Records for CSFs and Remote CSFs:

25.1. Maintain station records to provide a comprehensive picture of all traffic movement, irregularities, or delays in traffic handling and outages or circuit failures.

25.2. Retain CRITICOMM/DSSCS records for the periods specified in DOI-103, and MAJCOM publications. Identify all records on the AFIC Form 80, Files Maintenance and Disposition Plan, approved by the records manager.

25.3. The supervisor will maintain an AFIC Form 72 for each valid CRITIC message, in-station CRITIC test, or NSA-directed test message. AFIC Form 72 will be kept on file for a minimum of one year.

25.4. Do not file station records until after reviewing them to ensure their accuracy and completion.

25.5. The automated master station log (MSL) must be signed at shift change. The off-going supervisor and the oncoming supervisor will affix their signature to the MSL. Use the print screen function to print the shift change portion of the MSL for signature. Attach the shift change signature pages to the completed MSL.


26. Instructional Messages. HQ AFIC/SCO sends out special or amplifying instructions for CRITICOM M and DSSCS CSF/CORs, addressed to ALAFICCOMSTA. These general messages are serially numbered starting with 1 for the first message originated during each calendar year, for example, ALAFICCOMSTA 1/91.

NOTE: See introduction to this regulation.

27. Maintaining Continuity of General Messages:

27.1. Maintain a separate record of receipt for all DSSCS (ALDSSCS), all CRITICOMM (ALCRITIC, ALAFICCOMSTA, ALREMOTES, JAFPUBS (Joint Armed Forces Publications)), and other general messages as appropriate, on AFIC Form 107, unless an automated process is employed. Hard page copies of messages addressed to and retained by the CSF, remote CSF and COR, JAFPUBS, ALMILACTS, ALAFICCOMSTA, etcetera, destroy when superseded or cancelled by issuing authority. Customer agency general messages hard page copies should be retained by the receiving station on which the CSF, remote CSF and COR are not an addressee, but which are used to provide distribution served, ALPERSCOM, ALSAFECOM, AFACOM, etcetera, destroy after one month. In certain justified instances, the retention of hard page copies of narrative messages may be extended not longer than three months based on operational considerations as determined by the commander.

27.2. To obtain missing ALAFICCOMSTA messages, as soon as you note a number missing, forward a request to HQ AFIC/SCO by routine precedence using DDI "XLK." COR operations should query their host STREAMLINER prior to requesting retransmission from headquarters. For those stations not connected to a STREAMLINER, send your request to HQ AFIC/SCO using DDI "XLK." To obtain missing ALREMOTE messages, forward a request to your connected host STREAMLINER.

27.3. Note that ALAFICCOMSTA messages are effective until the end of the calendar year in which they originated unless disposition instructions are provided earlier. HQ AFIC/SCO will provide an annual summary message giving the status of ALAFICCOMSTA messages.

27.4. Note that ALREMOTE messages are effective until cancelled by the host STREAMLINER who will provide disposition instruction for these messages.

28. Using CRITICOMM DSSCS and AUTODIN Facilities:

28.1. Send all traffic (special intelligence (SI), non-SI, and administrative messages) addressed to stations within the CRITICOMM network by DSSCS. Forward non-SI messages destined for stations that do not have access to DSSCS by GENSER message. Always use DSSCS network when possible. Use GENSER only when addresses cannot be reached by DSSCS.

28.2. All personnel who work in the CSF or remote CSF (operations, maintenance, systems control) must hold the highest access for which the CSF/COR is accredited; if accredited for GAMMA traffic, then the respective billet number must be approved for the GAMMA level. Sanitize the CSF, remote CSF whenever a noncleared person must visit.

29. CRITIC Message Handling. Personnel must be highly trained in handling and reporting CRITIC messages. CRITIC procedures should be memorized. Reviewing procedures for information during the processing of CRITICs is too late. When transmitting a CRITIC and the CRITIC path is timing out, operators should down the line which will allow the CRITIC to process to the next available path. The AFIC standard for the communications handling of CRITIC messages is 2 minutes. When the 2 minute threshold (120 seconds) is exceeded, explain the reason for not meeting the standard handling time in the CRITIC Handling Report (RCS-972) paragraph four. To ensure that CRITIC messages are handled and processed rapidly, supervisors will:

29.1. Assign persons on each shift specific tasks in processing CRITIC messages; preempting circuits, calling up prepared CRITIC headers, preparing text, and transmitting messages. Use the CRT/ASTW/ ST2D as the primary device for originating a CRITIC message.

29.2. Not use optical scanning unit (OSU) equipment to transmit CRITIC messages unless all other input devices are inoperative. If the OSU is used, all operators must be fully aware that the CRITIC validation process within STREAMLINER is changed. Specifically, if an error in the format is detected, the CRITIC will be directed to a local in-house CRT/ASTW/ST2D position for correction and reentry, causing the CRITIC message to be delayed.

29.3. Ensure that each operator assigned to a shift is thoroughly trained in each specific task.

29.4. Ensure that each CRITICOMM facility that supports an operational mission has a CRITIC alerting system (CRITIC alarm, such as a bell, voice intercom, internal telephone, or buzzer) installed between the appropriate operations area surveillance and warning (S&W) center and the CSF, remote CSF. Operations personnel will use this system to alert the CSF, remote CSF of an impending CRITIC message. Use this alarm only for valid CRITIC and NSA-directed CRITIC tests only.

29.5. Check the system used by operations to alert the CSF, remote CSF of an impending CRITIC message. Record such checks in the master station log. Checks should be made at the beginning of each shift.

29.6. Ensure that original transmissions are accurate to prevent follow up transmissions. Proofread the CRITIC immediately after transmission. Establish a service CRITIC mask that can be used to service CRITIC messages in the event the CRITIC must be serviced.

29.7. Ensure that SOIs identify all alternate routes and methods by which a CRITIC message can be transmitted as required by DOI-103 (including Military Affiliated Radio Station, automatic secure voice communications, secure terminals units, third generation (STU-III), operations communications (OPSCOMM), or defense CRITICOMM communications (DCC) orderwire). Alternate routes to transmit a CRITIC or NSA-directed CRITIC test message should be listed by order of precedence to facilitate timely message processing.

29.8. Ensure that SOIs on CRITIC handling are current and workable and include the precise format used by operations for passing the CRITIC into the CSF, remote CSF (stapled together, color coded, and clearly marked). CRITIC messages should be legible, if handwritten, and contain a date-time-group, classification, and releaser's signature. No CRITIC will be rejected for transmission because of improper format. Brief any problems with the CRITIC to the originator after transmitting the CRITIC and list those problems in paragraph four of the CRITIC handling report.

29.9. Complete applicable blocks on the AFIC Form 72 for each CRITIC, NSA-directed CRITIC, and in-station CRITIC test message. Ensure that a completed critique is done. Make sure that all required actions were taken. File the CRITIC, AFIC Form 72, and any amplifying information together.

29.10. Ensure that an acknowledgment of receipt is sent to STREAMLINER remote terminals from which CRITIC messages are received. A procedure wire "R W" will be sent within two minutes of receipt of the CRITIC message.

29.11. Note time stamp CRITIC messages. CRITIC messages will not be delayed to satisfy "normal" message processing.

30. NSA-Directed CRITIC Tests. NSA will schedule CRITIC exercise messages. The exercise message will be delivered to the CSF, remote CSF by means and procedures normally used for a valid CRITIC message. The CRITIC action officer will be contacted to ensure that management personnel are available to monitor NSA-directed CRITIC tests. The NSA-directed CRITIC test will be processed as a valid CRITIC unless otherwise notified. When required, CRITIC tests are transmitted by OPSCOMM circuits when directed by NSA. S&W personnel are responsible complete handling and processing of OPSCOMM CRITIC messages. They will notify SC personnel to stand by in the event OPSCOMM transmission should fail. If there is an abnormal condition during the release period (special mission or exercise, significant volume of high-precedence traffic, or complete outage of OPSCOMM circuits), the operations officer will reschedule or cancel the test.

31. CRITIC Handling Reports (RCS: NSA-972). Prepare and forward according to DOI-103. If a CRITIC was transmitted via means transparent to the communications function, the operations officer will provide the necessary information to the SC as outlined in USSID 301, paragraph 8.3.

31.1. All stations originating or relaying a CRITIC will include HQ AFIC/SCO and intermediate headquarters as information addressees on all CRITIC correspondence.

31.2. Indicate in parenthesis, after the subject line of the report, whether the CRITIC was an NSA-directed test or a valid CRITIC, and the CRITIC number.

31.3. When a CRITIC test is sent from the S&W center, SC personnel will assist the operations personnel in preparing and forwarding of the handling report.

31.4. Any problems or abnormalities associated with the processing of a CRITIC (valid or NSA-directed) will be included in paragraph four of the handling report.

32. In-Station CRITIC Tests:

32.1. Communicators who expect to be involved in CRITIC handling will perform at least two in-station CRITIC tests a month. The shift supervisor will administer these tests. Alert all personnel by announcing in a loud voice "in-station CRITIC test!" Additionally, management personnel, the superintendent, the NCOIC, or the M&R section are responsible for releasing and monitoring an in-station test for each shift at least once a month. Test procedures must be designed to prevent on-line transmission. The following examples are to be used as message narratives for in-station testing. Remote CSFs will perform CRITIC testing using a stand-alone PC.





32.2. CSFs will conduct CRITIC tests by using the off-line STREAMLINER system, if available. Use CRT, AN/FGT-10, ASTW, and ST2D equipment as available. Set up the test schedule so that a test is performed from each device (CRT, AN/FGT-10, ASTW and ST2D). Prepare the text of the test message according to para 22a. Shift supervisors will closely monitor these tests and ensure that the following procedures are followed exactly:

32.2.1. For test purposes, remove one CRT, FGR-10, ST2D/ASTW, and receive-only printer (ROP) from the on-line STREAMLINER system. Assign this equipment to the off-line system using the following procedures:

NOTE: Only switch those lines which are connected to the desired equipment. If a service position is used as the ROP, it will be necessary to delete the feedback logical line from the physical line normally used for feedback. Then assign the feedback logical to the physical line (ROP) used during the test. However, if the normal feedback ROP is used during the test, physical or logical line assignment changes are not required. Also, ensure that the CRT/ST2D/ASTW used in the test has CRITIC origination and origination correction assigned. Enter your station "SA" routing indicator in the "incoming" and "relay" tables. Assign it to logical line 1.

Example: 1,IN,A,YXXXXX,A3,1 Messages to be transmitted must be input in abbreviated paper format from FGR-10; use normal input from CRT. Example of self-addressed test message "From and To" lines:



NOTE: Construct the pseudo PLAs to conform with your station's operation. When the off-line system is set up correctly, the test message will process in house only. However, if it does not, the test message may be processed by STREAMLINER to the ASC, then returned to STREAMLINER (switch supervisor position) by the ASC; or it may not process at all. Correct problems noted before progressing with CRITIC testing. After completing the in-station CRITIC test, perform the following to return the off-line system and test devices to normal operations: Ensure that all test CRITICs are cleared from the system and none remain in CRT error queue and send queue. Boot the off-line CPU by depressing the halt, reset, and load switches. Remove the journal tape from the off-line system and degauss it. Change the LMU switches for the CRT, ROP, ST2D/ASTW, and AN/FGT-10 back to the on-line system. Using the on-line system console, "up" the CRT, ROP, ST2D/ASTW, and AN/FGT-10.

7.7.3. Operators designated to process CRITIC messages should be able to meet in-station timeliness standards for on-line CRITIC processing (2 minutes). Times for CRITIC handling are computed from time of file to time of transmission. Operator typing time is computed from time of file to time message is entered into the system (released for transmission by the operator).

7.7.4. The person administering the test will enter all pertinent information about the test on AFIC Form 72. Attach a hard-page copy of the in-station CRITIC message, the system console printouts and file it with the AFIC Form 72 for future reference.

7.8. Special Handling Messages. The following special handling messages can be processed on floppy diskette providing they do not contain an SCI caveat above SI: INSPECDIS, EYES ONLY, EXCLUSIVE FOR, LIMIDIS, and PERSONAL FOR. Standard SCI security accreditation and certification requirements must be met before processing SAR, SAP, and SPECAT messages on any system, floppy diskette, processor, or equipment. Local SOIs will include instructions for physical protection (need-to-know) of SPECAT and other special handling messages.

7.8.1. Deliver incoming EXCLUSIVE FOR and INSPECDIS messages (to include LIMDIS, SPECAT, etcetera) in a sealed envelope. Deliver all copies of INSPECDIS messages to the inspector general. Use AF Form 3530 to deliver INSPECDIS messages

7.8.2. If the message requires DSSCS protection, forward it by DSSCS to the CRITICOMM support facility serving the noncryptologic unit.

7.9. Handling AFIC/CC or CV Messages During Periods of Temporary Duty (TDY). To ensure that messages addressed to, or originated by, the AFIC Commander (CC) or Vice Commander (CV) during periods of TDY are handled properly, the following procedures will apply:

7.9.1. HQ AFIC/CCE will provide the CC's or CV's itinerary to all AFIC units including AFIC CSR, remote CSF to be visited.

7.9.2. Each CSF, remote CSF of units to be visited will be an addressee of all messages forwarded for the CC or CV. Only the action addressee's CSF/remote CSF will acknowledge receipt (ZDF-1 or ZDF-2) to HQ AFIC/CCE.

7.9.3. Each CSF, remote CSF to be visited will set up two folders; one for incoming messages addressed to the AFIC/CC or CV and one for messages originated by the AFIC/CC or CV. All messages will be logged on an AFIC Forms 103 (incoming) and 106 (outgoing) for processing to and from the AFIC/CC or CV.

7.9.4. The commander's executive officer will ensure that messages addressed to or from the AFIC/CC or CV are sequentially numbered (1,2,3, etcetera) for position control.

7.9.5. Any time a message is received and there are indications that a sequential message is missing, the CSF of the AFIC unit being visited will notify HQ AFIC/CCE by IMMEDIATE precedence message or telephone call (during duty hours) and AFIC Command Center after duty hours.

7.9.6. Persons preparing correspondence will: Ensure that ZFF1 and ZFF4 are placed in the "message handling instructions" block of the DD Form 173, Joint Message form, for all (GENSER) messages. NOTE: Messages released on floppy disk must have a date-time-group and will contain ZFF1 and ZFF4. Example: 250900Z NOV 90 ZFF1 ZFF4. Ensure that ZFF1 and ZFF4 are placed in the "message handling instructions" block of the DD Form 173 for all DSSCS (sensitive compartmented information (SCI)) messages. Place the "Z" signal following the DDIs, SOA/ZFF1, SOZ SOL SOD/ ZFF4. If no DDI is used, then put a slant (/) and the "Z" signal, /ZFF1 ZFF4).

NOTE: Messages released on floppy disk must have a date-time-group and will contain ZFF1 and ZFF4. Example: 251500Z NOV 90 ZFF1 ZFF4. For classification of CC's or CV's itineraries, see AFR 205-1/ESC Sup 1. Follow the procedures below to ensure efficient transmittal and delivery of messages addressed to or originated by the AFIC/CC or CV. Any CSF/COR having problems delivering messages will request guidance from HQ AFIC Command Center by immediate precedence message or telephone call. Log messages by nickname, serial number, time of receipt (TOR), time of transmission (TOT), or time of delivery (TOD) (as applicable) and adequate data to identify the message. Transmit report of delivery by Priority precedence service message to the originating station. Transmit requests for retransmission by Priority precedence to the CSF/COR NCOIC in service message format. Dual address to originating station and info the CC's next destination if the time element dictates. The following procedures are for transmission requests: If the message is SI and the noncryptologic unit is supported by an SSO communications center, transmit the message to the SSO with internal passing instructions. If there is no SSO-supported communications center, hold the message until the CC or CV arrives, and advise the message originator of your action. If, because of the time element, it is doubtful that the retransmission will reach the requesting station, dual address the retransmission to the station requesting retransmission and the commander's next destination listed on the itinerary.

Section H

8. Policy and Operations

8.1. Keyboard Operations. Manual keyboard transmission into the line are specifically forbidden except as required for maintenance, facility control, or teleconference operations or to pass a CRITIC message.

8.2. Preformatted Headers. If preformatted headers are used, preparing personnel must review them daily to ensure that they are not altered and are readily available. In addition, they must make periodic reviews (at least monthly) to ensure that they are being maintained in a current status to prevent misrouting messages. These periodic reviews must be documented; the method to be used for this documentation is left up to each OIC or NCOIC.

8.3. SOIs. Prepare SOIs according to AFR 5-8 and number them according to AFR 5-4. Review SOIs periodically to ensure that the contents are current. A record of review will be maintained.

8.4. Proofreading Messages. Proofread messages before transmitting them. Proofread OCR-originated messages after-the-fact using the feedback copy. High precedence messages will be proofread during or after transmission. Immediately send a voluntary correction (ZZS for DSSCS messages (see DOI-102 for CRITICs)) when high precedence messages require correction. Proofread at least 10 percent of terminated message traffic. Ensure that message traffic has been properly processed, legible, free of garbles, and mutilations. All messages found to have major errors will be reprotected by sending a corrected copy to all addressees or servicing for retransmissions.

8.5. Interlaced Messages. CRITICOMM stations reporting interlaced messages according to DOI-103 will include HQ AFIC/SCO and appropriate wing as information addressees on the initial report and all follow-up correspondence about the interlace.

8.6. Cryptographic Emergency Plans. AFIC units will publish these plans as annexes to the 69XX unit plans according to ESCR 28-1.

NOTE: These plans also apply to the emergency reaction unit (ERU) and emergency reaction special security office (ERSSO) in a deployed, nondeployed, or travel status. Although deployed plans are based on the situation and local environment, include the basic tasks or guidelines for emergency crypto-actions for deployed ERUs or ERSSOs in the unit emergency plans. Add amplifying details (such as facilities to use for destruction or location of hand-receipted materials) after arrival at the deployment site; however, spell out and practice general requirements for emergencies.

8.7. Clock Synchronization. Accuracy of date-time groups, time of filing, and date-time stamping are essential for reporting requirements. Consequently, observe standard practices to synchronize timeclocks used in the CSF, remote CSF to ensure that they are always synchronous throughout CRITICOMM and DSSCS. Stations that:

8.7.1. Do not have a master, synchronous clock system phased by time signals, will follow these procedures: Designate one clock as the master time clock within a station. Shift supervisors will get a time check for the master clock within the first hour of their tour of duty. If the clock isn't correct, reset it to the proper time and record this action in the duty report. The shift supervisor will ensure that all other clocks used in the CSF, remote CSF area are synchronized with the master clock. CSFs and remote CSFs that cannot receive a time check from one of the time standard stations will use the best time check source available to them.

NOTE: At stations where there is an unstable power supply, acquire a high quality battery-driven clock as a station master clock.

8.7.2. Have a master synchronous system to obtain a time check at the beginning of each radio day (0001Z) to ensure that the time is correct.

NOTE: Use wristwatches and other personal timepieces only as an emergency measure when recording times.

8.8. Circuit Performance. Operators must:

8.8.1. Act promptly to minimize circuit interruptions which delay vital communications. Close and rapid coordination is mandatory within and between all CSF, remote CSF stations.

8.8.2. Keep local facility control operations informed of the status of circuits at all times.

8.8.3. Ensure that a circuit is inoperative for an absolute minimum of time.

8.8.4. Be constantly alert to circuit conditions and message quality which may require a circuit to be declared inoperative.

8.8.5. Enter any excessive delay in processing traffic due to prolonged circuit outages or equipment in the supervisor's log.

8.8.6. Perform operator preventative maintenance as prescribed in SOIs.

8.9. Prevent Lost Message Hazards. Supervisors of CSFs and remote CSFs will enforce good housekeeping rules to prevent accidental loss of valid traffic; they will:

8.9.1. Ensure that enough tape racks, message trays or baskets, and covered waste receptacles are available.

8.9.2. Immediately discard all pieces of wastepaper in approved receptacles. Destroy all paper waste generated within the CSF, remote CSF as classified waste.

8.9.3. Ensure that uncovered waste receptacles are not placed near transmitting or receiving positions or near desks or tables on which messages are placed.

8.9.4. Ensure that pieces of tape or ribbons are not thrown on the floor and that any tapes or ribbons or other papers found on the floor are carefully inspected before discarding them.

8.10. Personal Signs:

8.10.1. Certain CSF and remote CSF records require initialing to indicate individual responsibility. Personal signs are assigned to all CRITICOMM and DSSCS operating and supervisor personnel. Such personal signs must not conflict with local channel designators or operating prosigns and no two personal signs will be alike within a station. Large stations may find it more practical to assign numbers to each person instead of initials to eliminate duplication and confusion.

8.10.2. Print personal signs legibly.

8.10.3. Maintain a current list of personal signs in use and post it within each station.

8.10.4. Do not electrically transmit personal signs.

Section I

9. Communications Continuity

9.1. Policy. The primary purpose of communications is to provide the most rapid, reliable, and secure means possible for timely delivery of critical information. To achieve this, a unit's communications circuits must be so designed that disrupting a part of the system does not affect the entire system.

9.2. Responsibility. To prevent the possibility of a complete loss of communications, the officer or NCO responsible for communications must make sure that:

9.2.1. Essential circuits do not come together except at user terminals.

9.2.2. Dual-access routes are available to the commercial or military facility serving the installation.

9.2.3. High priority circuits in a large facility are dispersed throughout available channels.

9.2.4. Where there is only one circuit, an alternate communications path is available and tested periodically. Also, ensure that records of tests are included in the supervisor's log.

9.2.5. All circuits are terminated on patch panels (if available) so they can be easily patched or switched between the primary and alternate paths.

NOTE: If the capacity of the BLACK patch panel will not permit terminating all dual-access lines, a separate switching arrangement may be included in the CSF/remote CSF.

Section J

10. STREAMLINER Operations

10.1. STREAMLINER Input and Output Line Continuity Status. To ensure that all input and output lines are in the correct status, "up" or "down," as appropriate, perform an INPUT/OUTPUT line report. Use the "IOL, ALL" option of STREAMLINER utility "LR" at the beginning of each shift change. Check this report with each line verified for correct status and enter the fact that the one-status check was made, to include applicable remarks, in the supervisor's log.

10.1.1. To determine INPUT line status, check the "line status" column. "Yes" indicates the line is up, "No," the line is down.

10.1.2. To determine OUTPUT line status, check the "line status" column "O"--line is available (UP); "1" -- line in test; "2" -- line has EOM (end of message) stop on it'; "3" -- line is busy out.

10.1.3. HAMSTRUNG, FIREBOAT, and ST2D communications terminals will be limited in functionality to message processing with ABOVEBOARD software only. Once they have been connected to a STREAMLINER port, these devices may not be used off-line for any other purpose except for maintenance. These terminals may not be disconnected and used as stand-alone terminals and then reconnected as comms terminals. If, prior to initial connection or, following maintenance, prior to reconnection, these terminals are used with any software other than ABOVEBOARD, they must be sanitized according to USSID 702 instructions before the connection can be made. ABOVEBOARD software must then be reloaded from the official distributed disks. In addition, qualified maintenance personnel must verify that the hardware is configurated according to the communications terminal's specifications. Once connected, strict software and hardware configuration control must be maintained.

10.2. STREAMLINER UTILITIES. Perform lengthy STREAMLINER utilities, such as service directories (SD), journal tape retrievals (TR), traffic statistics (TS), tape recovery (TR), and message trace (MT) by using the off-line system only, except when only one STREAMLINER system is operative. Then, the utilities must be operated using the on-line system. STREAMLINER utilities, regardless or length, will not, however, take precedence over restoring STREAMLINER remote circuits to operation. When it's necessary to use the on-line system to perform lengthy utilities and a STREAMLINER remote circuit experiences an outage, immediately abort the utility and restore the remote circuit to operations. The only exception to this rule is when the on-line system is required to retrieve FLASH or higher precedence traffic at which time, defer remote circuit restoration until all retrieval actions for the FLASH or higher precedence traffic is completed.

10.3. STREAMLINER Remote Requirements. Submit all STREAMLINER remote requirements through the normal Communications-computer systems requirements document (CSRD) process. Once the CSRD is received in SCO for evaluation, SCO will advise the requesting unit to submit the 18-question requirement (see 3.b.). Each request for remoting off STREAMLINER will be considered on a case-by-case basis. The formal consideration for a STREAMLINER remote is that the remote candidate, to include the facility and personnel, must be accredited for "system-high" operation. If the remote candidate is a computer with "backside" remotes, the "system-high" rule applies to the backside remotes also.

10.3.1. Studies addressing the feasibility of using STREAMLINER to automate remote terminals must: Consider or approve service or agency telecommunications automation and consolidation plans. Identify courses of action within reasonable financial constraints, using existing facilities where possible. Assess the impact of proposed major changes in customer procedures, organization, or operations. Ensure that the security protection afforded by the alternatives is equal to the security and sensitivity requirements of the information being processed.

10.3.2. Address all requirements for remote connectivity for STREAMLINER to HQ AFIC/SCO, intermediate headquarters, NSACSS/T761, and AFICNSALO providing the information contained in the STREAMLINER interface specification guide published by NSACSS/T761.

10.4. Marking STREAMLINER Documents and Working Aids. STREAMLINER stations will set up procedures to ensure that all magnetic tapes, disk packs, disks, SDs, TSs, and plain language address (PLA) tables are marked with the appropriate classification. STREAMLINER magnetic tapes and disk packs will remain under CSF control at all times. Station managers will ensure that:

10.4.1. Control numbers are assigned to all magnetic media and that a record of use is maintained.

10.4.2. All magnetic media, whether new or used, will be inventoried at the beginning of each shift change. Record any discrepancies noted in the master station log.

10.4.3. An SD is available for each journal tape used and that journal tapes are not degaussed earlier than 30 days after being closed.

10.4.4. When destroying journal tapes or disk packs, record the pertinent information on AFIC form 308 to include the witnessing and destruction official's signature. Assign the tape the same number as the one destroyed with a alphabetic suffix, (0039A). When 0039A is replaced, the next tape will be numbered 0039B. Floppy diskettes used with STREAMLINER will be inventoried and handled in accordance with ESCR 56-10 and marked in accordance with AFR 205-1/ESC Sup 1.

NOTE: AFIC Forms 307 and 308 can be used as an option to fulfill the above requirements.

10.5. On-Line Use of STREAMLINER Systems. Station managers will ensure that each STREAMLINER system (ALPHA and BRAVO) is used "on-line" on a rotating basis. Do not switch systems during "high" use times when a more appropriate time, after duty hours or on a weekend can satisfy this requirement or a PMI.

10.6. Customer-Operated Remote (COR) Facilities. This section outlines the operational concept for COR facilities and applicable policies, procedures, and responsibilities. CORs are connected on-line to a host STREAMLINER facility and operated by the customer to transmit and receive DSSCS and GENSER record message traffic.

10.6.1. Concept of Operations. COR facilities employ the minimum operating procedures required to provide secure, accurate, and expeditious message processing. This includes maintenance of those records required to ensure message continuity and record of receipt (when required). If a 491XX communicator is assigned to the unit, they will be identified to act as a "communications liaison" to assist the unit when problems are experienced in message processing. Additionally, if a 491XX is assigned, they will be responsible for the drafting of communication policies necessary to ensure secure and reliable communications.

10.6.2. Publications. COR facilities must maintain the host's STREAMLINER Customer Education Guide.

10.6.3. Forms. Those forms necessary to maintain message accountability and continuity are required. Non-AFIC COR facilities use comparable forms as prescribed by their major command or service (Army, Navy).

10.6.4. Equipment. Equipment identified in the requesting units accreditation package and approved for use by the STREAMLINER configuration control authority will be used as the end terminal equipment. This equipment is normally a personal computer which meets TEMPEST requirements.

10.6.5. Responsibilities. Processing Incoming and Outgoing Message Traffic. The COR facilities will ensure that continuity of incoming and outgoing message traffic is maintained at all times. This requirement can be satisfied by using the AFIC Form 111, Channel Number Sheet, or a general purpose form. General Personnel Responsibilities. There are certain general responsibilities common to all supervisory or operator personnel performing duties in the COR. The unit will appoint in writing a COR system administrator, who will: Develop station operating procedures for proper control of SPECAT, LIMDIS, Personal For, and other special handling caveats. Provide their host STREAMLINER with the name, telephone number (secure and unsecure) of the point of contact for the COR terminal. Provide the host STREAMLINER, when applicable, the part time hours of operations and procedures for notification of high-precedence message traffic during other than normal duty hours. Develop an alternate route agreement for processing high-precedence traffic during extended periods of outage on their terminal. Assign IDs to all personnel authorized to log on and process messages on the CORs terminal. Act as the focal point for system training, directing questions to their on-site communications consultant, the host, wing or MAJCOM as appropriate. Maintain the COR's magnetic media inventory. Load current versions of the ABOVEBOARD software on the COR's terminals.

10.6.6. Assistance Request. Whenever COR personnel require assistance with message processing, they will contact the on-site communication consultant, if one is available. If not, consult with the STREAMLINER host. This may be done via message addressed to "STREAMLINER HOST//ASSISTANCE REQUEST//, using DDI: "DSH," or another agreed upon messages address, or it may be accomplished via secure telephone (STU-III).

10.6.7. PLA Updates. CORs will submit all requests for additions, changes, or deletions to the host STREAMLINER plain language address tables. See attachment 1.

10.6.8. Routing Table Update. The host STREAMLINER station's database contains the majority of the DSSCS PLA and routing indicators listed in DOI-102. The system, however, contains only those address-indicating groups (AIG), DSSCS Address Groups (DAG), SPOTS, and GENSER PLAs most frequently used by the STREAMLINER host and users. STREAMLINER remote facilities must advise the host of routing or PLA additions, deletions, and changes in these circumstances: Active use of a new AIG, DAG, SPOT, or GENSER PLA. Addition or deletion of an addressee to an AIG, DAG, or SPOT unique to their operations that is presently in the tables. Active use of a new DSSCS or GENSER PLA. Deactivation or discontinued use of an AIG, DAG, or SPOT. Nonuse of a previously used GENSER PLA which is a service-unique (Army, Navy, or Air Force). Changes submitted to the host STREAMLINER for PLA input, will be sent at the precedence in which the remote requires action to be taken. See attachment 6.

10.7. Host STREAMLINER Stations. The host STREAMLINER station:

10.7.1. Conducts a staff assistance visit to its distant remote stations at least annually. Visits will deal with all phases of operations to include M&R functions and training.

10.7.2. Accomplishes a trip report to be maintained locally. Provide information copies of the report to the remote, HQ AFIC/SCO, and intermediate headquarters.

10.7.3. Set ups operating procedures and coordinate with the remote (local or distant) to ensure that circuit or message continuity is maintained at all times. Also, ensure that correct format and operating procedures are used.

10.7.4. Provides statistical data to remote stations with COI-101 reporting responsibilities in a timely manner to ensure submission of required reports to meet suspense dates.

10.7.5. Provides assistance on tracer actions, interlaces, message problems, straggler messages, and missing message traffic.

10.7.6. Ensures that a customer education guide is developed and provided to all distant and in-house STREAMLINER remotes detailing all the following necessary procedures for the handling of message traffic: How to handle misrouted messages. How to request service action from the host. Examples of PLA updates. Requests for retransmissions (RETO).

10.7.7. Informs customers that do not have error correction capabilities on their STREAMLINER remote, that they must use a "self addressed" DSSCS and GENSER PLA to ensure that their message traffic has been transmitted. If the 693 IW STREAMLINER remote terminal does not have error correction capabilities, they must place the PLA 693 IW// Feedback// and 693IW Kelly AFB TX//Feedback// as an addressee on all outgoing message traffic. The host STREAMLINER manager will point those PLAs to terminate on the 693 IW remote terminal.

10.7.8. Will incorporate into the customer education guide a provision that remote terminals who have a CRITIC mission, contact the STREAMLINER host via message at flash precedence or secure telephone, when they are in a potential CRITIC situation.

10.8. STREAMLINER Processing of Messages on Floppy Disk. Message input origination is not authorized on the on-line system (ASTW/ST2D) STREAMLINER connection. All messages will be created on stand-alone systems. Service messages and PLA updates can be originated on-line.

NOTE: There will be no deviations from these procedures. See AFR 700-7/ESC Sup 1 for more details.

10.9. Technical Control. In an effort to standardize procedures and define authority and responsibility, the following guidance is provided:

10.9.1. CRITICOMM multiplexor order (CMO), CRITICOMM network order (CNO), and telecommunications service order (TSO) are directed by National Security Agency and Defense Information Systems Agency respectively. They direct specific actions to activate, deactivate or change circuit routing, and in some cases, equipment. They provide specific end-to-end routing, channelizations, and circuit parameters, and as such constitute circuit configuration authority.

10.9.2. CMOs, CNOs, and TSOs do not specify in-house wiring and patching particulars. This determination must be a joint effort of the unit tech control and maintenance functions. The tech controllers by virture of their knowledge of overall station configuration and ergonomics, should determine in-house routing. Maintenance must review and coordinate on the selected routing to assess technical feasibility work required, and equipment and Plant In Place Record (PIPR) impact.

10.9.3. All work required to implement a CMO, CNO, or TSO will be done by maintenance personnel.

10.9.4. Configuration control of physical plant assets, that is, floor plan layouts, rack elevation drawings, wiring termination count sheets, and power and signal cable distribution resides in DCS/LE and is directed by AFICR 100-14. Any CMO, CNO, or TSO resulting in changes to the physical plant configuration must be forwarded to DCS/LE for approval. LE will assign a work unit code (WUC) for man-hour accounting and a self help project number for documentation tracking. If PIRP documentation is not affected on a WUC will be issued. For urgent or emergency orders, requests may be forwarded after the fact.

10.9.5. The important factor of implementing the above procedures is to foster close coordination between tech control and maintenance personnel.


Lt Col, USAF

Director of Information Management

3 Attachments

1. Funtional Address Symbols (FAS)

2. Terminal-Station Duty Titles and Job


3. Format for PLA DataBase Input

attachment 1


A1.1. SC--Used by the Director of Communications-Computer Systems (SC) or superintendent at the local unit level.

A1.2. SCO--Used by the NCOIC of CSF/COR operations.

A1.3. SCT--Used by the superintendent or NCOIC of the CRITICOMM Facility Control or patch and test facility.

A1.4. SCX--Used by the communications-computer systems plans and program management.

NOTE: A fourth (4th) letter may be added to any of the three-letter stem FAS, however, a request must be submitted to HQ AFIC/IMOA for approval.

attachment 2


NOTE: Use the following duty titles within terminal station on SOIs, records, and reports. Although not all duty titles are used at every AFIC location, the most commonly used are listed under CSF Duty Title General Job Description.

A2.1. Depending on local requirements, one person may perform several functions or several people may be required to perform one function. Some smaller stations may have no requirement for certain functions and may delete them.

A2.2. CSF Duty Title General Job Descriptions:

A2.2.1. Chief, Communication-Computer Systems--Responsible for operating the entire branch.

A2.2.2. CRITICOMM Support Facility Superintendent or NCOIC--Responsible for operating the CSF and for supervising all personnel assigned.

A2.2.3. Methods and Results NCOIC/Clerk--Provides quality control and statistical reporting.

A2.2.4. COMSEC Accounting NCO--Handles all COMSEC accounting matters.

A2.2.5. STREAMLINER System Administrator--Responsible for maintaining the STREAMLINER system's software and for coordinating hardware difficulties with maintenance and appropriate agencies.

A2.2.6. Shift Supervisor or Assistant--Supervises personnel and oversees the operations of the assigned shift.

A2.2.7. Transmit Operator--Responsible for ensuring that messages are transmitted in a timely manner without error.

A2.2.8. Service Section Operator--Responsible for handling incoming and outgoing services as appropriate.

A2.2.9. Cryptoset Operator--Responsible for the reset of the on-line cryptographic equipment according to current cryptographic operating instructions.

A2.2.10. Message Distribution Center clerk--Responsible for performing CSF/COR functions according to AFR 700-7/ESC Sup 1.

A2.2.11. Administrative Clerk--Performs administrative duties as required. This function is performed by 702XX administrative specialists.

attachment 3