U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
Air Traffic Organization Policy

ORDER
JO 7210.3
Y
Effective Date:
April 3, 2014
 
     
Subject:  Facility Operation and Administration
       

Section 8. Ocean21

6-8-1. GENERAL

a. Ocean21 is an Air Traffic Control (ATC) System deployed in designated en route and oceanic airspace. Ocean21 includes both surveillance and flight data processing, which provides the controllers with automated decision support tools to establish, monitor, and maintain separation between aircraft, and aircraft to airspace and terrain.

b. Ocean21 capabilities include:

1. MEARTS based radar surveillance processing.

2. Conflict Prediction and Reporting for conflict probe.

3. Automatic Dependence Surveillance-Addressable (ADS-A).

4. Automatic Dependence Surveillance-Broadcast (ADS-B).

5. Controller Pilot Data Link Communications (CPDLC).

6. ATC Interfacility Data Communications (AIDC).

7. Decision Support Tools used primarily for situation awareness.

8. Electronic Flight Data including Electronic Flight Strips.

6-8-2. OPERATIONAL SUPERVISOR-IN-CHARGE RESPONSIBILITIES

In addition to the watch supervision described in Chapter 2, Administration of Facilities, Section 6, Watch Supervision-Terminal/En Route, facilities must provide in facility directives the operational duties and procedures for the Supervisor-In-Charge associated with the Ocean21 System. Responsibilities and procedures must include but are not limited to the following:

a. Disseminate flight information received at the Supervisor workstation in a timely manner. 

b. Supervisor workstation message management.

c. Ocean21 data management when a channel changeover is being performed. 

d. Assignment of Error Repair responsibilities.

6-8-3. ERROR REPAIR POSITION RESPONSIBILITIES

Facilities must define responsibilities and develop procedures associated with the Ocean21 System for the Error Repair position. Responsibilities and procedures must include but are not limited to:

a. Disseminate messages received at the workstation in a timely manner.

b. Edit and repair messages.

6-8-4. FACILITY MANAGER RESPONSIBILITIES

a. Ensure LOAs, SOPs, MOUs and Sector Position Binders are current to support Ocean21.

1. Facility managers must consider Ocean21 functions and limitations when reviewing current LOAs and/or negotiating future LOAs.

2. Consider the following items when reviewing LOAs:

(a) Interfacility coordination procedures.

(b) Outage notification.

(c) Degraded functions notification.

(d) Automated Information Transfer Procedures.

b. Ensure all facility directives, where applicable, support Ocean21. Directives should include but are not limited to:

1. System problem reporting.

2. Airspace and sector configuration.

3. Use of surveillance sources.

4. Use of paper strips and strip marking. 

5. Electronic flight data management. 

6. Conflict Probe/Decision Support Tools use, limitations, and exceptions. 

7. Internal coordination.

8. Contingency plans.

9. Controller preference management.

6-8-5. TRANSFER OF POSITION

In addition to the procedures outlined in para 6, Step-by-Step Process, of Appendix D, Standard Operating Practice (SOP) for the Transfer of Position Responsibility, in FAAO JO 7110.65, Air Traffic Control, ensure facility directives include, at a minimum, the following procedures:

a. Position relief briefing checklist.

b. Sign-over procedures.

6-8-6. OCEAN21 CHANNEL CHANGEOVERS

Facilities must identify the procedures for a channel changeover that include a checklist detailing actions to be taken, and roles and responsibilities.

6-8-7. OUTAGES

In accordance with Chapter 8, NAS En Route Automation, and requirements in this chapter, facilities must develop and maintain procedures for the transition to and from, and during Ocean21 degraded operations. A facility directive must include a checklist detailing actions, roles, and responsibilities during planned and unplanned outage or degraded operation.

6-8-8. CONTROLLER PILOT DATA LINK COMMUNICATIONS

Facility managers must ensure that local procedures are developed for the use of CPDLC. These procedures must include but not be limited to:

a. The use of free-text messages in air-to-ground communication.

b. Data link limitations and exceptions.

c. Lost communications procedures.

d. Frequency assignment for automated transfer.

Return to Air Traffic Publications Library Return to Order Home Page Return to Table of Contents