NORAD ANTI-DRUG NETWORK STANDARD OPERATING PROCEDURES
This instruction establishes standardized Anti-Drug Network (ADNET) operating procedures for North American Aerospace Defense Command (NORAD) organizations. In the event that procedural conflicts exist between ADNET employment documents, the procedures in this instruction will prevail unless otherwise directed by the office of primary responsibility (OPR). Copies of this instruction may be provided to non-NORAD units to encourage the use of these procedures when coordinating counterdrug (CD) operations with NORAD units. This publication applies to the Air National Guard (ANG) when published in the ANG IND2. This publication does not apply to the Air Force Reserve.
SUMMARY OF REVISIONS
Revises the list of current references. Revises the responsibilities attributed to each administration level of the system. Adds and defines responsibilities at the Unit System Administration level. Deletes track classification definitions, which is located in reference 1.3. Deletes OTH-B information.
1.1. CINCNORAD/CONPLAN 3310-96, (Tab A to Appendix 1 to Annex C, S/RELCANUS).
1.2. ADNET Standard Operating Procedures (Draft Version 2).
1.3. NR55-1, Aerospace Reporting System (to be published as NI10-19).
1.4. NI10-15, Identification of Air Traffic.
1.5. JOTS II 2.0 Unified Build User's Guide.
1.6. ADNET OSA System Administrator Manual (Draft Version 2).
1.7. Anti-drug Network Classification and Handling Guide.
1.8. Anti-drug Network Security Policy.
2.1. The aerial and maritime transit of illegal drugs into North America is a threat to the national security
of both the US and Canada. To counter this threat, the 1989 National Defense Authorization Act assigned Department of Defense (DoD) as the lead federal agency in the detection and monitoring of illegal airborne and maritime drug trafficking into the United States. To accomplish this mission, the Chairman, Joint Chiefs of Staff (CJCS) tasked the Commander in Chief, Atlantic (now CINCUSACOM), Commander in Chief, Forces Command (now Commander FORSCOM), Commander in Chief, Pacific (USCINCPAC), Commander in Chief, Southern Command (USCINCSO) and Commander in Chief, North American Aerospace Defense Command (CINCNORAD) to conduct detection and monitoring operations within their respective areas of responsibility and/or operations. Authority for Canadian Forces to conduct CD operations resides in the NORAD Agreement and is also reiterated in the Department of National Defence (DND) publication Defence Development Planning Guidance 1995 (DDPG 95).
2.2. To accomplish this mission, NORAD will conduct operations to detect and monitor aerial transit of drug trafficking aircraft into North America; coordinate with other federal, state and local agencies engaged in detecting, monitoring and apprehending aerial drug traffic; and integrate NORAD operations into an effective CD command, control, communications and intelligence (C3I) network.
2.3. The implementation of ADNET was directed by the Joint Chiefs of Staff (JCS) to support the integration of DoD into an effective C3I network. This system provides the capability for all agencies involved in CD operations, DoD, DND and law enforcement agencies (LEA), to coordinate operational as well as intelligence matters over a secure and expedient computerized system. The ADNET is the primary means to conduct and coordinate CD operations; secure voice or hard copy messages are used as backup.
3.1. NORAD System Manager. HQ NORAD Air Sovereignty Operations Branch (N/J3OD) is the ADNET Management Office and has responsibility for all funding issues, overall ADNET policy and future system configuration plans, instruction rewrite and administration, approval and promulgation, and release message authority to agencies outside of the direct NORAD chain of command. N/J3OD will act as the NORAD representative at ADNET Configuration Control Board conferences. Any issues pertaining to the aforementioned responsibilities can be addressed to N/J3OD, 250 South Peterson Blvd, Suite 116, Peterson AFB CO 80914-3260.
3.2. NORAD System Administrator. Cheyenne Mountain Operations Center (CMOC), Chief Current Operations Division (CMOC/J3O) will act as the ADNET System Administrator and has responsibility for day-to-day system operations and configuration management, training concerns for NORAD personnel, and is the single point of contact for daily operational concerns. CMOC/J3OCA will act as the NORAD representative at ADNET Engineering Review Board conferences. For systems improvements, NORAD units should forward proposals to CMOC/J3OA, Cheyenne Mountain Air Station, Colorado 80914-6020, Attention: ADNET System Administrator.
3.3. Unit System Administrator. Each NORAD unit equipped with an ADNET terminal will appoint, in writing, a System Administrator and an alternate for the management of the system. The appointment letter must include the individuals' names, office symbols and phone numbers; info copies of the appointment letter must be sent to CMOC/J3OA, HQ NORAD/J3OD, and Continental NORAD Region Director of Counterdrug Operations (CONR/DOD) for CONUS Sector Air Operations Centers (SAOC). System Administrator's responsibilities include: training of personnel, reporting maintenance problems, keeping a detailed description of the hardware and software configuration, and loading new software. The System Administrator must be trained and able to distinguish among problems related to hardware,
software, the UNIX operating system, and communications equipment. In addition, the System Administrator is responsible for net control and system operational instructions and point of contact lists.
3.3.1. N/J3OD is the OPR for the scheduling of HQ NORAD/CMOC personnel to attend the System Administrator Course.
3.3.2. NORAD Regions headquarters are the OPR for scheduling region and sector personnel to attend the System Administrator Course (Info N/J3OD).
3.3.3. Reference 1.2 established the following as Regional Coordinators (RCs): Trouble Management Desk, Open System Applications (TMDOSA), Joint Interagency Task Force (JIATF) East, JIATF West, Joint Task Force-6, Southern Region Operations Center (SROC), NORAD and CONR. The role of the RC is to control ADNET information flow and accuracy. The NORAD Air Defense Operations Center (ADOC) is the NORAD ADNET RC for HQ NORAD and Canadian agencies. CONR is designated RC for CONUS sectors and the Alaska NORAD Region (ANR). RC responsibilities as defined below are delegated to CONR to match NORAD's operational structure and procedures. Specific RC responsibilities are assigned as follows:
220.127.116.11.1. Establish contact broadcast distribution lists to be used by NORAD units.
18.104.22.168.2. Coordinate and de-conflict CD operational matters between RCs.
22.214.171.124.3. Monitor CD operations and related information transmitted over the ADNET by other RCs as required.
126.96.36.199.4. Ensure intelligence data is passed to agencies with a need-to-know.
188.8.131.52.5. Assume CONR RC responsibilities when CONR is unable to perform assigned duties due to system malfunctions.
184.108.40.206. NORAD Regions:
220.127.116.11.1. CONR Region Operations Control Center (RAOC) will assume NORAD RC's responsibilities when the ADOC is unable to perform the duties listed above due to system problems or as directed by the ADOC. When assuming RC's responsibilities, CONR will notify all ADNET RCs via Operations Note (OPNOTE) and will use the contact distribution list assigned to the ADOC.
18.104.22.168.2. Manage the ADNET air picture for their area of responsibility. Correlate track information, ensure validity of track data, resolve contact ambiguities and broadcast a consolidated air picture to the agencies specified in this instruction. These tasks can be delegated to a designated SAOC as an alternate NORAD Region air picture manager.
22.214.171.124.3. Coordinate contact handover with adjacent Regions through voice coordination and OPNOTEs as required. Ensure contact and track handover are completed NLT Air Defense Identification Zone (ADIZ) penetration for a track heading towards US or Canadian airspace, or as soon as it is tactically and operationally possible when employing NORAD assets. This task can be delegated to the SAOC conducting the operation, at the discretion of the RAOC.
126.96.36.199.4. Distribute intelligence information received from assets employed or from outside agencies to the ADOC and appropriate SAOCs.
188.8.131.52.5. Ensure all subordinate units have the appropriate message distribution addressees for their respective areas of operations.
184.108.40.206. NORAD SAOCs:
220.127.116.11.1. Maintain an up-to-date ADNET air picture displaying on-going counterdrug operations, to include DoD, DND, Royal Canadian Mounted Police (RCMP), and LEA assets being employed. Correlate track information, ensure validity of track data, and resolve contact ambiguities within their area of responsibility.
18.104.22.168.2. Coordinate contact handover with adjacent sectors through OPNOTEs, followed by a telephone call. Ensure contact and track handover are completed NLT ADIZ penetration for a track entering US or Canadian airspace, or as soon as it is tactically and operationally possible when employing NORAD assets.
22.214.171.124.3. Report intelligence information received from assets employed or from outside agencies to the RAOC, other affected SAOCs, and the ADOC.
126.96.36.199.4. In coordination with the applicable RAOC, designate an alternate SAOC to take over the above responsibilities in the event the ADNET becomes degraded or non-operational.
4. Procedures. The following are basic guidelines for ADNET use:
4.1. Desktop Setup, Maps, and Plot Control. These will be tailored by each user to fit operational requirements.
4.2. Plot Control. Track symbology will be assigned as defined in reference 1.4.
4.3. Contacts. Airborne, maritime, and ground targets detected and identified by available sensors and suspected to be associated with drug trafficking will be displayed on ADNET. Users will select and display contacts as needed to satisfy operational needs. As a minimum, contacts on the following tracks will be broadcast to the pertinent RAOC and NORAD ADOC: Target of Interests (TOI), Unknowns, Special-17 tracks, E-3s on associated missions (when reporting a suspect track) or on dedicated missions, and other tracks as directed by NORAD ADOC or the RAOCs.
4.3.1. When a track is detected, the agency detecting the track will establish a contact and transmit it to all designated users. The contact originator will maintain the track until it can be handed over to another command with better tracking capability or the track enters another RC's area of responsibility/operations. The detecting agency with the most recent contact will advise all users via OPNOTE when the track fades or contact is lost. ADNET tracks will be initiated NLT 5 minutes after detection, transmitted to other RCs (and pertinent adjacent sector) or users as required, and updated at least every 10 minutes or as directed by the ADOC. Contacts will be transmitted by NORAD units as the situation dictates to designated addressees as follows:
188.8.131.52. All CONUS SAOCs will transmit sector-generated contacts to CONR.
184.108.40.206. CONUS Region. Will transmit tracks to any other appropriate RC.
220.127.116.11. Canada East. Will forward tell to NORAD ADOC for all CANR.
18.104.22.168. Alaskan NORAD Region. Forward tell to NORAD ADOC.
22.214.171.124. ADOC. Will transmit contacts to all other RCs and required agencies.
4.3.2. Contact names (track numbers) will be designated by the originating agency and will be maintained by the agency accepting tracking responsibility until the track is terminated. NORAD track numbers will be used as contact names for all tracks detected by all sensors within the NORAD system (see NR55-1 (NI10-19)). NORAD ADOC or CONR as appropriate will assign an ADNET track number to suspect aircraft tracked by NORAD sensors for record purposes and to be used when transmitting contact data to other RCs.
4.3.3. NORAD RAOCs will ensure smooth contact handovers between subordinate units and other RCs. Handover coordination will be accomplished using OPNOTEs followed by a telephone call, or by secure telephone as backup.
4.4. Messages. This function provides the capability to send messages over a secure and expedient mode of communication. This option is the primary means for coordinating current NORAD CD operations. See reference 1.5. for detailed instructions on the use of this option. NORAD units will develop procedures to delete OPNOTEs stored in the ADNET (on a daily basis) to ensure optimum system performance.
4.4.1. All ADNET messages will be considered official record traffic. ADNET users must ensure only authorized personnel have access to their terminals and only official message traffic related to counterdrug operations/intelligence will be transmitted.
4.4.2. CMOC/J3OA will develop, maintain and distribute specific formats for coordination of operational matters to include employment of NORAD assets and support to outside agencies. ADNET users are encouraged to submit to N/J3OD and CMOC/J3OA requirements for new formats or recommendations to improve formats in use.
4.4.3. Individuals sending text messages must include their name, rank, and phone number at the end of the text.
4.4.4. Agencies requesting support of NORAD assets will forward the completed NORAD Counterdrug Asset Request format (attachment 1) to NORAD ADOC, with an information copy to the applicable NORAD Region Headquarters.
4.4.5. CD intelligence messages will be sent to applicable NORAD Region Air Operations Centers (RAOC), and the NORAD ADOC.
4.4.6. NORAD Forms 61, NORAD Track Record, may be processed between the RAOCs, SAOCs and ADOC.
5. System Reliability. As an operational system, the ADNET is required to be operational at all times to support the mission (see reference 1.2.). NORAD units will conduct a system "NET STATUS" check at least every 8 hours to ensure their ADNET terminal is operational and can communicate with other agencies; communications check OPNOTEs will not be used to check system connectivity.
6. Exercises. NORAD units will exercise the ADNET procedures established in this instruction during local, regional, and NORAD-wide exercises. The following procedures apply during exercises.
6.1. ADNET tracks will be developed to simulate the latest smuggling trends observed or profiles suspected of being used within the applicable sectors.
6.2. Contact names (track numbers) will be designated by the exercise designer and will consist of four letters (N for NORAD and EXE for exercise) and a three-digit sequential number to indicate the exercise track number. Contacts will not be transmitted to agencies or units outside NORAD, unless they have been included in the planning and coordination of the exercise, and they have agreed to participate. Other DoD and LEA agencies will be simulated by the NORAD unit being exercised or as directed in exercise plans for NORAD wide exercises.
6.3. OPNOTEs. All exercise OPNOTEs will be labeled to indicate that the information provided is for exercise only, and all non-NORAD units or agencies are to disregard such information. In addition, the NORAD unit implementing the exercise will send a daily OPNOTE to all ADNET addressees indicating the dates and times they will be exercising ADNET procedures. All possible efforts will be made to prevent exercise data from being transmitted to non-players.
7. System Upgrades. System change proposals will be routed through the Unit System Administrator, RC, System Administrator, and then the System Manager if necessary.
8. Security. The ADNET provides the capability to exchange information up to the SECRET (RELCANUS) level. ADNET terminals must be located in a facility certified to the SECRET level, and accessible only to those individuals with the appropriate security clearance and need-to-know. In addition, only information concerning counterdrug operations can be displayed, processed or transmitted over the ADNET. Classified information without a RELCANUS caveat will not be transmitted over the ADNET.
8.1. Before information is sent to another user, operators will ensure the proper security classification and markings are included IAW AFI31-401 Information Security Program Instruction. Information on controlled operations and SANDKEY specific data such as cover names will not be entered into the ADNET. Information placed into ADNET becomes accessible to other ADNET users; therefore, extreme caution must be exercised when information is disseminated.
8.2. All ADNET users must be aware that the ADNET is monitored to ensure proper communications security (COMSEC) procedures are observed. Use of the ADNET by an individual constitutes consent to monitoring for COMSEC purposes.
RODNEY S. LUSEY, Colonel, USA
1. NORAD Counterdrug Asset Request Format
2. Example of Exercise ADNET OPNOTE
Line 1: Date of the request.
Line 2: Time of the request.
Line 3: Requesting Agency.
Line 4: Requester's name, rank and phone number (DSN and or commercial).
Line 5: Asset requested (E-3, interceptors, etc.).
Line 6: Intelligence assessment (definite, probable or possible and summary
to include target profile -altitude, heading, airspeed and route if
Line 7: Operational Requirements (E-3 orbit point, option, on/off station
times, search times, etc.).
NOTE: For long-range requests such as a Ground Mobile Radar (GMR) deployment, appropriate Drug Law Enforcement Agency (DLEA) will forward requests through the respective SAOC, Region, or to N/J3OD.
2. (U) EXERCISE TRACKS WILL BE NAMED AS NEXE + TRACK NUMBER. ALL EXER-
CISE OPNOTES WILL BE CLEARLY LABELED AS EXERCISE INPUTS AND WILL BE
TRANSMITTED TO EXERCISE PARTICIPANTS ONLY. IN THE EVENT YOU RECEIVED
AN EXERCISE ADNET CONTACT OR OPNOTE, PLEASE DISREGARD.
3. (U) REQUEST NOTIFY SUBORDINATE ADNET USERS OF THE PENDING EXERCISE.
POC IS MAJOR PACKOWSKI, DSN 268-3644.