Section
23. Contingency
Plan Support
System (CPSS)
17-23-1. PURPOSE
This section
prescribes
policies and
guidelines for
managing ARTCC
Operational
Contingency Plan
(OCP) data
within the
Contingency Plan
Support System
(CPSS). The CPSS
is maintained
via the RMT.
17-23-2. DEFINITION
The CPSS, as
defined in FAA
Order JO
1900.47, Air
Traffic
Organization
Operational
Contingency
Plan, is a
software
application used
to collect,
share, publish,
and distribute
OCPs for
operational
access and use
by field
facilities, the
ATCSCC, and
customers during
ATC Zero events.
17-23-3. RESPONSIBILITIES
a. The
ATCSCC must:
1. Manage
the CPSS
database
following FAA
Order JO
1900.47, Air
Traffic
Organization
Operational
Contingency
Plan.
2. Designate
a POC for the
management of
the CPSS
database.
b. ARTCCs
must:
1. Develop
and maintain the
accuracy of OCP
data within CPSS
following FAA
Order JO
1900.47, Air
Traffic
Organization
Operational
Contingency
Plan.
2. Designate
a POC to
coordinate with
the ATCSCC on
the management
of the ARTCC's
CPSS database
information.
3. Coordinate
with all
affected
facilities when
changing CPSS
data before
including them
in the CPSS
database.
4. Ensure
that CPSS data
are available to
operational
positions.
NOTE-
Before
publication in
the CPSS, the
facility must
ensure that
hardcopy, or
other electronic
means of making
this information
available, is
provided to
operational
personnel and
the ATCSCC.
5. Tell
all affected
offices when
making any
change to the
National
Airspace System
that might
affect internal
or adjacent
ARTCC
contingency
plans (for
example, airway
changes,
frequency
changes,
airspace
redesign, airway
realignment,
etc.)
6. Report
unusable,
inaccurate, or
unsatisfactory
CPSS information
directly to the
ATCSCC CPSS POC.
Real-time
implementation
problems should
be reported to
the ATCSCC
National System
Strategy Team
and to the
ATCSCC CPSS POC.
Reports must
include the
facility plan
name, affected
sectors,
specific
description of
the impact, and
if appropriate,
suggestion for
modification.
7. Coordinate
with underlying
terminal
facilities for
all matters
pertaining to
CPSS data
information.
c. Service
Center
Operations
Support Group
must:
1. Review
CPSS data for
currency and
consistency.
2. Serve
as liaison
between ARTCCs
and ATCSCC on
CPSS matters.
3. Serve
as information
and training
resource for
ARTCCs to help
them maintain
current and
accurate
information in
CPSS.
17-23-4. PROCEDURES
a. OCP
data for each
ARTCC must be
published within
CPSS via the
national RMT
database.
Updates to the
RMT database
will coincide
with the 56-day
chart update
cycle.
b. OCP
data must be
processed in
accordance with
the following
timelines:
1. All
revisions to
CPSS data must
be provided to
the ATCSCC CPSS
POC at least 30
days before each
chart date.
2. The
ATCSCC POC must
enter all
revisions to the
CPSS data at
least 14 days
before the chart
update. The RMT
database will
then be locked.
|