FAA Configuration Management Authority:

• Coordinates the development and establishment of FAA configuration management policy, processes, and guidance;
• Assists lines of business, staff offices, service organizations, service areas, and other solution providers with development of CCB charters and operating procedures;
• Provides training, facilities, and electronic tools to document, monitor, and report configuration management information;
• Maintains a mechanism for assigning hardware names, asset tags, and identifiers for systems, interface documentation, and system documentation;
• Make accessible the NAS-MD-001, NAS Master Configuration Index Subsystem Baseline Configuration and Documentation Listing, using data available from the CM information management system. All configuration control boards follow the direction of the FAA Configuration Management Authority regarding the type, content, and availability of information in the information management system to ensure validity of data in NAS-MD-001.

A cross-functional team comprised of senior managers advises the Configuration Management Authority, serves as forum for addressing and resolving issues, and assists in the implementation of configuration management policy and solutions.

NAS Configuration Control Board:

• Controls changes to NAS systems and associated documentation not assigned to a lower-level CCB or not identified for control by the Joint Resources Council;
• Baselines Interface Requirements Documents and controls non-FAA or non-baseline system interfaces to the NAS;
• Approves service organization, service area, and other solution provider CCB charters and updates;
• Resolves problems regarding NAS system requirements among service organizations or other solution providers;
• Approves changes to NAS technical documentation and ensures traceability of requirements from the NAS level to the system and subsystem level;
• Manages changes to the final program requirements document, and notifies the investment decision authority if those changes affect cost, schedule, or performance.

Service Organization Configuration Control Boards:

• Approve or disapprove proposed changes to configuration items under their purview for the lifecycle of the configuration item;
• Ensure all changes have been fully analyzed and coordinated with all organizations affected by the change;
• Refer to the NAS Configuration Control Board proposed changes that exceed their approval authority;
• Establish functional, allocated, product, and operational baselines for all NAS systems;
• Manage the site configurations of FAA facilities in accordance with FAA-STD-058, FAA Standard Facility Configuration.

Service-Area Configuration Control Boards:

• Control changes to facility equipment layout drawings, critical power panel designations, and unique regional equipment, as identified in their charters;
• Regularly validate the accuracy of baselined facility space and power panel documentation.

The service-area configuration management plan identifies the facilities that are subject to verification and audit and specifies the audit interval. The plan also documents the configuration management program, including the methodology and processes used to accomplish service-area configuration management tasks.

Non-NAS Information Technology Configuration Control Board:

• Manages non-NAS information technology systems and associated documentation not assigned to a lower-level CCB or not identified for control by the Joint Resources Council except for data exchange standards;
• Baselines Interface Requirements Documents to non-NAS systems;
• Approves line of business staff office and other solution provider CCB charters and updates;
• Approves changes to non-NAS information technology technical documentation and ensures the traceability of requirements;
• Baselines the final program requirements document or specification.

Non-NAS Line of Business Staff Office or Solution Provider Configuration Control Boards:

• Approve or disapprove proposed changes to configuration items under their purview for the lifecycle of the items;
• Ensures all changes are fully analyzed and coordinated with all organizations affected by the change;
• Refers changes to the Non-NAS IT CCB proposed changes that exceed their approval authority;
• Establish functional, allocated, product and operational baselines for all non-NAS systems. This includes establishing and documenting site configurations, including as-built equipment layout drawings and critical power panel designations, and creating baseline documentation for FAA information technology facilities.

NAS and Non-NAS Information Technology Acquisition-Level Configuration Management:

Service organizations, LOB staff offices, and other solution providers charged with providing solutions to Enterprise Architecture requirements do the following:

• Establish, implement, and maintain configuration management plan(s) that document the configuration management program, including the methodology and processes used to accomplish configuration management tasks;
• Include requirements for configuration management planning, process, procedures and products in all acquisition contracts;
• Document transition plans and activities for field organizations; and
• Manage the lifecycle of configuration items and associated baseline documentation, which may include training material, courseware, and logistics support documentation assigned to them.
  

Planning and Management:  Plan, coordinate, document, and manage all tasks necessary to manage the configuration of assigned enterprise architecture products throughout all phases of the lifecycle management process. A configuration management plan formalizes processes and procedures and roles and responsibilities, and ensures continuity of configuration management practices at all levels of management.

Configuration Identification: Identify the configuration items of the total product and develop documentation to define each. This activity includes development of a top-down configuration management structure for the product, and the assignment of unique identifiers for the units and groups of units in the product. Configuration identification and product information is maintained and be readily available to all FAA decision-makers. 

Baseline Management: Establish and maintain a configuration baseline that represents technical aspects of approved product requirements. Baselined documentation is maintained by the appropriate line of business program office, staff office, or service organization, and is accessible in a secure environment through the program support library. 

Configuration Change Management:  Identify, document, coordinate, evaluate, and adjudicate proposed changes to a configuration baseline. Approved changes are documented, implemented, verified, and tracked to ensure incorporation into all impacted assets and their support infrastructure. 

Configuration Status Accounting:  Capture, store, and access the configuration information needed to manage products and product information. Configuration information must be electronically available for use by decision-makers over the lifecycle of the asset.

Configuration Verification and Audit:  Periodically audit operational products to ensure consistency between the product and its baseline documentation. This activity includes verification of facility baselines, the incorporation of approved modifications, and product audits after commissioning.

Information/Data Management:  Manage configuration data and information according to requirements in FAA Order 1375.1, Information/Data Management Policy.