Federal Aviation Administration

Configuration Management

  • Print
  • |  Updated: 2:21 pm ET June 24, 2009


FAA Order 1800.66 – NAS CM Procedure Updates (Updated 08/27/2008)

Since the release of the revised policy (1800.66 Change 1 and 2), the CM Policy Working Group has been revising the NAS CM procedures to:

  1. Support revised policy statements;
  2. Reflect current process requirements and operations; and
  3. Reflect the ATO realignment
The CM community briefing provides insight on currrent CM policy workgroup activities. As part of the coordination activity, the Enterprise CM organization is providing the CM community an opportunity to conduct an informal review of the procedure redlines and provide feedback. To view redlines available for review, click here.

FAA Order 1800.66 Change 2

FAA Order 1800.66, Change 2 was approved on September 19, 2007 is being released with changes 1 and 2 incorporated. This update of the policy statements represents the successful completion of our strategic initiative supporting Flight Plan goals for safety and organizational excellence. The Order captures the change in scope for the Federal Aviation Administration (FAA); supports GAO recommendations for CM by requiring control of both the NAS and Non-NAS IT; aligns with current Acquisition Management System (AMS) policy; and introduces requirements for traceability of all configuration managed systems to the FAA Enterprise Architecture (EA). FAA Order 1800.66, Part 1 has been reorganized to capture general, NAS and Non-NAS IT CM requirements. The remaining parts, including procedures, will be released at the end of FY-08 for the NAS and FY-09 for Non-NAS IT.

Key changes include:

  • Requirements for traceability to and from the FAA Enterprise Architecture in support of Flight Plan goals to make decisions based on reliable data and improve the security of the data through disciplined control over NAS and Non-NAS IT assets.
  • FAA Order 1800.66 will no longer reside in AMS as a stand-alone Order. Top-level requirements for configuration management will remain in AMS. To support alignment of the Order to AMS and clarify requirements external to the Order, changes to AMS are being coordinated through the Acquisition System Advisory Group (ASAG).
  • Includes requirements supporting the Safety Management System relative to NAS changes, information system security, the FAA Enterprise Architecture and top-level requirements management.
  • Defines top to bottom framework for configuration decision authority (e.g., hand-off of approved final program requirements, CCB authority).
  • Provides clarity for existing CM policy, such as baselining and management of top-level requirements approved by the JRC and external interfaces to the NAS.
  • Captures the current agency organization.

Many thanks to the FAA IT CM and CM Policy working groups for their efforts to develop and finalize the policy statements to meet our goal on time.

FAA Order 1800.66 Change 2 (PDF)

FAA Notice N JO 1800.2 – NAS Change Proposal (NCP) Process Support of the Safety Management System

This notice addresses changes to the FAA NAS Change Proposal (NCP) process to support the Safety Management System (SMS). The NCP process is described in detail in FAA Configuration Management policy Order 1800.66. FAA Form 1800-2 Casefile/NCP in conjunction with a signed Casefile/NCP Safety Risk Management (CNSRM) Checklist or Safety Risk Management Decision Memo (SRMDM) and, if required, an approved Safety Risk Management Document (SRMD) shall be used to support effective decisions regarding changes to operational NAS systems, equipment, and facilities. Signed CNSRM checklists, SRMDMs, and SRMDs need to be considered as inputs to the casefile/NCP process, otherwise organizations that originate casefile/NCPs may experience process delays.
quicklinks