E-IDS Section C.docx

693KA7-20-C-00013 Modification #0002 Section C – Statement of Work

TABLE OF CONTENTS

PROGRAM SCOPE

The scope of this contract is to establish an Enterprise Information Display System (E-IDS) that the FAA will operate in support of ongoing FAA operations. E-IDS will utilize and integrate existing and future capabilities and data sources located on multiple networks to optimize FAA operations. E-IDS will be installed at current or new locations as needed.

The scope of this contract includes, but is not limited to, the following major components:

1. Establish and maintain a Program Management Office and perform Program Management to support and coordinate the work performed under this contract to ensure compliance with all terms and conditions, and to drive technical excellence and ensure the team meets schedule

2. Design, develop and test Enterprise Information Display System (E-IDS) in accordance with the Federal Aviation Administration (FAA) E-IDS System Specification Document (SSD) (Attachment J-1)

3. Develop a comprehensive training program for FAA E-IDS operators and maintainers, and ensure the FAA is capable of providing ongoing training

4. Implement E-IDS at the National Data Centers (NDCs), at field sites and on the EIM platform

5. Provide engineering services for system augmentation to insert system enhancements such as implementation of new features including items identified in the FAA Phased Approach for E-IDS, updates to accommodate changing data interfaces, and potential migration of E-IDS from the Integrated Enterprise Service Platform (IESP) to new FAA-provided cloud services

6. Provide as-needed staff augmentation for ongoing FAA system/site operations and maintenance support The Enterprise Information Display System (E-IDS) will provide an enterprise-level platform that implements, augments and/or replaces multiple types of IDSs in, or in support of the NAS, including but not limited to En Route, Terminal, Traffic Flow and Offshore domains with common hardware and software. E-IDS has identified 5 display systems for replacement. These are:

· Information Display System-4 (IDS-4)

· Automated Surface Observing System Controller Equipment-IDS (ACE-IDS)

· NAS Information Display System (NIDS)

· En Route Information Display System (ERIDS)

· Air Traffic Control (ATC) Auxiliary Information Display (AAID) The Terminal environment includes three distinct systems, each with a different hardware/software configuration: IDS-4, ACE-IDS and NIDS.

En Route includes ERIDS, a system that provides non-tactical information to FAA personnel in Air Route Traffic Control Centers (ARTCCs). Traffic Flow domain is present in both Terminal and En Route environments consisting of large monitors that display real-time, high-level traffic and Traffic Flow Management information.

The Alaska ARTCC has developed its own IDS, AAID.

Background In the National Airspace System (NAS), Air Traffic Management (ATM) personnel rely on a variety of decision support tools and sources of information to perform their jobs. Controllers use their primary radar displays to monitor air traffic and operational information and make tactical decisions resulting in potential new clearances and information to the aircraft. Traffic managers depend on automation and displays that help them to identify and resolve operational constraints and ensure efficient flows. Front Line Managers (FLMs) use a combination of these systems to ensure controllers in their operational areas are aware of the latest operational conditions. Operational Managers (OMs) use a combination of all these displays to monitor their facilities. These systems focus on dynamic, timely information.

However, operational personnel often need information in addition to that on their primary display (e.g. radar display, Traffic Situation Display (TSD), oceanic display) to assist in operational situations they encounter. Some of this information is dynamic, such as local weather conditions and equipment status. Other information changes infrequently and is essentially static, such as operational procedures, letters of agreement, and aircraft characteristics. The display of this information is provided through what is generally referred to as Information Display Systems (IDSs).

In the NAS, several varieties of IDSs are in use across the Air Route Traffic Control Centers (ARTCCs), Terminal Radar Approach Control Facilities (TRACONs), Combined Center Radar Approach Controls (CERAPs), and Airport Traffic Control Towers (ATCTs). Users of IDSs include: Air Traffic Controllers, FLMs, Traffic Management Coordinators (TMCs), OMs, and Technical Operations (Tech Ops) personnel. Specialists who tailor the information to meet the above user needs at each position include En Route Data Managers and Terminal System Administrators. This is a collateral job assigned to a controller or administrative specialist.

In the En Route environment, there are two IDSs: the En Route Information Display System (ERIDS) and the Air Traffic Control System (ATCS) Automated Information Display (AAID). In the continental United States, ERIDS is located in the twenty ARTCCs at the Air Traffic Control (ATC) sector positions; at the FLM position; in the Traffic Management Unit (TMU); and in the Center Weather Service Unit (CWSU). ERIDS is used to display Notices to Airmen (NOTAMs) and can be used to enter Pilot Reports (PIREPs). ERIDS also displays static information, such as publications, aeronautical charts, and Standard Operating Procedures (SOPs) and Letters of Agreement (LOAs). The AAID is a “home-grown” system made from Commercial-Off-The-Shelf (COTS) equipment.

The Anchorage Air Traffic Control Center (ZAN) provides En Route, Oceanic, International, and TRACON services so IDS-4 and AAID are used. It is the E-IDS Program Office intent that E-IDS replace both legacy systems at this site.

In the terminal environment, the IDS-4, NAS Information Display System (NIDS), and the Automated Surface Observation System (ASOS) Controller Equipment-IDS (ACE-IDS) are the systems in use. While many of these systems were deployed in the 1990s, not all were installed at every facility. For example, ACE-IDS was deployed to only 13 of the large and consolidated TRACONs and their connected ATCTs in the 2000s. The latest generation IDS is known as NIDS and is managed by the Information Display System Replacement (IDSR) program office. NIDS was planned for deployment in the terminal environment to replace IDS-4, but funding shortfalls prevented replacement at most terminal facilities. These IDSs differ in a variety of ways with respect to their access to information sources, their display capabilities, and the types of dynamic and static data needed for operations in different environments. Generally, static information that may be displayed includes charts, approach plates, and SOPs and LOAs, while dynamic information includes Traffic Management Initiatives (TMIs), local weather conditions, winds, and altimeter settings.

The FAA experiences several types of problems associated with utilizing multiple IDS platforms, including:

· Inefficiencies of sustainment and replacement activities. The existence of multiple, diverse IDSs creates inefficient activities needed to manage sustainment and replacement of these systems and their 5,000-plus workstations. Each IDS requires its own training programs; maintenance schedules and personnel; logistics and second-level support; and budgeting and scheduling for technology refreshes, upgrades, and end of life support.

· Limited ability to support continuity of operations and capitalize on FAA NextGen capabilities. Reliance on point-to-point connections to external systems, use of obsolete telecommunication technology, and older system designs severely limit the current IDSs’ ability to migrate and reconstitute their information displays at accommodating facilities. Most required sector information contained in a facility’s IDS cannot be retrieved and displayed at another facility, limiting the capability of the IDSs to support the continuity of business operations. E-IDS must support the continuity of business operations by means of leveraging a common hardware and software platform, provisioning modern interfaces, modernizing data administration, and enabling NAS-system-wide access to authoritative and site-specific information using the System Wide Information Management (SWIM) / NAS Enterprise Messaging System (NEMS) paradigm. Without SWIM interfaces, access to NextGen information services by IDSs will be limited, and access to current information will become problematic as existing support for point-to-point connections is retired. Although retrofitting existing IDSs for compatibility with SWIM/NEMS may be achieved by means of platform replacement, many other technology improvements would still be needed.

· Inefficiencies of Data Access and Management. The workload associated with the use of the IDSs depends on a combination of ease of access, data organization, and accuracy of the information. Analyses of the existing IDSs in each domain have identified operational shortfalls that result in workload levels that are considered excessive and could be improved with E-IDS. Current capabilities to search and retrieve information are cumbersome and add to the workload levels of the controllers, FLMs, and TMCs who use the IDSs. This is due to both the shortcomings of the user interface and the facility-specific data-organization methods. The reliance on manual updates to maintain the data also adds to the workload levels of the assigned Data Administrators and Systems Administrators at each facility. The part-time nature of the assignment can lead to lower proficiency due to limited training and experience.

Purpose The purpose of this Statement of Work (SOW) is to define the effort required to design, develop, test, implement, and support E-IDS. This SOW incorporates by reference the FAA E-IDS System Specification Document (SSD), provided in Section J (Attachment J-1) of this contract. This SOW also includes provisions for Program Management (PM), System Engineering (SE), System and Software Development, Test and Evaluation, Training, Implementation, Integrated Logistic Support and Operations and Maintenance, Engineering Services, and General Engineering/Technical Services. The Contract Data Requirements List (CDRL) contained in Section J of this contract defines the products to be delivered to the Government resulting from the effort defined in this SOW and is also incorporated by reference into this SOW.

APPLICABLE DOCUMENTS

The following specifications, standards, instructions, orders, guidelines, and handbooks form a part of this SOW and are applicable to the extent specified herein.

Inclusion of an applicable law or regulation in the below list does not imply exemption from any applicable law or regulation.

Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer (CO). Contractor requests should fully identify material desired and cite the solicitation or contract number.

Copies of military standards and specifications may be obtained by mail or by telephone from the Defense Automated Printing Service, Building 4, Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5094. For telephone requests, call (215) 697-2179, 7:30 AM to 4:00 PM, Monday through Friday. There is a charge for each ordered document.

FAA Orders, Specifications, and Standards Software / Systems Engineering

· FAA-STD-026A, DOT/FAA Standard: Software Development for the National Airspace (NAS) System

Configuration Management:

· FAA Order 1800.66 CHG 3, Configuration Management Policy

· FAA-STD-021A, Configuration Management

· FAA-STD-058, Standard Practice Facility Configuration Management

Human Factors:

· FAA Order 9550.8, Human Factors Policy, Oct 27, 1993

· DOT/FAA HF-STD-001B, Human Factors Design Standard

· DOT/FAA HF-STD-003, Human Factors Design Standard, Alarms and Alerts in the Technical Operations Environment, Aug 31, 2009

· DOT/FAA HF-STD-004A Human Factors Engineering Requirements, Sept 27, 2017

· DOT/FAA HF-STD-008, Air Traffic Control Traffic Control Tower Alert Standard, Aug 8, 2014

· DOT/FAA HF-STD-009, Technical Operations Graphical User Interface Standard, Jan 19, 2017

· DOT/FAA HF-STD-010, Color Use in Air Traffic Control System Displays, Dec 1, 2017

· DOT-VNTSC-FAA-95-3, Human Factors in the Design and Evaluation of Air Traffic Control Systems

· FAA-G-2100H, Electronic Equipment, General Requirements

· Human Factors Acquisition Job Aid, June 2012

Integration and Implementation:

· FAA Order 1050.1F, Environmental Impacts: Policies and Procedures

· FAA-G-2100H, Electronic Equipment, General Requirements

· FAA Order JO 1050.17A, Environmental Compliance at Air Traffic Organization Facilities

· FAA Order 1050.20A, Airway Facilities Asbestos Control Program

· FAA Order 4600.27C, Personal Property Management

· FAA JO 6000.50, Integrated Risk Management

Logistics, Supply Support, Operations, and Maintenance:

· FAA Order 6000.41B, Contractor-Assisted Maintenance for the National Airspace System

· FAA Acquisition Management System (AMS) Policy, Section 4.3, Integrated Logistic Support

· FAA Order 4250.9B, Field Materiel Management and Control

· FAA Order 6200.4H, National Test Equipment Program Management

· FAA Order 6000.30F, National Airspace System Maintenance Policy

· FAA Order 6000.15H, General Maintenance Handbook for National Airspace System (NAS) Facilities

· FAA Order JO 6000.53D Remote Maintenance Monitoring and Control Interface Development and Implementation

· FAA Order 4500.3D, Federal Catalog and Standardization Program

· FAA Order 4650.20A, Reporting and Replacement of Items Falling Under Warranty

· FAA Order 4140.1A, Integrated Material Management Program

· FAA-D-2494B, Technical Instruction Book Manuscript: Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books

· FAA-STD-002F, Engineering Drawing Preparation and Support.

· FAA-HDBK-006C, Reliability, Maintainability and Availability (RMA)

Quality Assurance:

· FAA Order JO 7210.634, ATO Quality Control

· FAA Order JO 7210.633, Air Traffic Organization Quality Assurance Program

Safety and Health:

· FAA Order 3900.57A CHG 1, Environmental and Occupational Safety and Health (EOSH) Requirements in the Planning and Execution of Construction and Maintenance Activities at NAS Facilities

· DOT/FAA, HF-STD-001B, Human Factors Design Standard (HFDS)

· FAA Order 6950.27A, Short Circuit Analysis and Protective Device Coordination Study

· FAA-G-2100H, Electronic Equipment, General Requirements

· FAA Order JO 3900.64, Air Traffic Organization Electrical Safety Program

· FAA Order JO 6980.25E, Maintenance of Batteries for Standby Power

· FAA Order 3900.19C, FAA Occupational Safety and Health Program

· FAA Order JO 1000.37A, Air Traffic Organization Safety Management System

· FAA Order 8040.4B, Safety Risk Management Policy

· FAA Order 8000.369B, Safety Management System Guidance

· FAA Order 1050.10, Prevention, Control, and Abatement of FAA Environmental Pollution

· FAA Order 1050.20A, Airway Facilities Asbestos Control Program

· SRMGSA Safety Risk Management Guidance for System Acquisitions

· ATO/SMS Safety Management System Manual

Security and Safety:

· FAA Order 1600.69C, Facility Security Management Program

· FAA Order 1600.1E, Personnel Security Program

· FAA Order 1600.72A, Contractor and Industrial Security Program

· FAA Order 1600.75, Protecting Sensitive Unclassified Information

· DOT Order 1681.1, DOT Implementation Policy for ICAM and HSPD-12

· DOT Departmental Cybersecurity Compendium Supplement to DOT Order 1351.37: Departmental Cybersecurity Policy

· DOT Order 1351.18, Departmental Privacy Risk Management Policy

· DOT Order 1351.19, PII Breach Notification Controls

· FAA JO 1370.48, NAS Identity and Access Management

· FAA Security Authorization Handbook

· FAA-STD-045A, NAS Communications Security Protocols and Mechanisms

· FAA Order 1370.121, FAA Information Security and Privacy Program & Policy

· FAA Order 1600.78, Personal Identity Verification (PIV) Card and other Identification Cards

· FAA Order 1600.78A, Personal Identity Verification (PIV) Card and Other Identification Cards

· FAA Order 1370.101A, Information Security Incident Reporting and Response Policy

· FAA Order 1600.1E, Personnel Security Program

· FAA ATO FY17 Information Systems Security Training Implementation Guidance

· FAA JO_Order 1370.123, National Airspace System (NAS), Identity and Access Management (IAM) Policy

Test and Evaluation:

· Federal Acquisition System (FAS) Acquisition Management System (AMS) Guidance, Test and Evaluation Process Guidelines

· FAA AMS Policy, Section 4.4, Test and Evaluation, 7/2016

· FAA William J. Hughes Technical Center Test and Evaluation Handbook, Version 4.0

· FAA Order NG 1810.8A, FAA William J. Hughes Technical Center’s Test and Evaluation (T&E) Policy

Training

· FAA Order JO 3000.57, ATO Technical Operations Training and Personnel Certification Programs

· FAA Order JO 3120.4P, Air Traffic Technical Training

· FAA-STD-028C, Contract Training Programs

· FAA Order JO 7110.65X CHG 3, Air Traffic Control Organization Policy

· FAA Order JO 3000.22A Air Traffic Organization Outcomes-based Technical Training

Other Government Standards and Guidelines

· 29 C.F.R. part 1910, Occupational Safety and Health Standards (General Industry)

· 29 C.F.R. § 1926.62 Occupational Health and Environmental Controls, Lead

· National Defense Industrial Association (NDIA) IBR Guide

· 29 CFR 1910.1001, Asbestos

· 29 CFR 1910.1025 Occupational Safety and Health Standards, Toxic Substances, Lead

· 29 CFR 1910.144, Safety Color Code for Marking Physical Hazards

· 29 CFR 1910.145, Specifications for Accident Prevention Signs and Tags

· 19 CFR 1910.147, Occupational Safety and Health Standards, General Environmental Controls, Control of Hazardous Energy (Lockout/Tagout)

· 29 CFR 1910, Subpart E, Means of Egress

· 19 CFR 1910 Subpart S, Occupational Safety and Health Administration (OSHA) Standards, Electrical

· 29 CFR 1910.303, Design Safety Standards for Electrical Systems

· 29 CFR 1910.22 Occupational Safety and Health Standards, Walking-Working Surfaces

· 29 CFR 1910.95, Occupational Noise Exposure

· 29 CFR 1910.1200, Hazard Communication

· 42 United States Code (USC) §4321, National Environmental Policy Act (NEPA)

· 40 CFR Subchapter C, Parts 50-97, Protection of the Environment, “Clean Air Act”

· 40 CFR 700-766, Protection of the Environment, “Toxic Substances Control Act” (TSCA)

· 40 C.F.R. Part 82, Protection of Stratospheric Ozone

· 40 CFR 260-280, Hazardous Waste Management System

· 49 CFR 170-180, Worker Protection Standard Industry Standards and Guidelines

Program Management

· ANSI/EIA Standard 748-C, Earned Value Management Systems (EVMS)

Systems Engineering / Software

· RTCA/DO-278A, Guidelines for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance

· IEEE 1517, Software Life Cycle Reuse Processes Information Technology – System and Software Life Cycle Processes – Reuse Processes

· ISO/IEC 12207 Systems and Software Engineering – Software Life Cycle Processes

· IEEE-Standard-830-1998 IEEE Recommended Practice for Software Requirements Specifications

· IEEE Standard 1016-2009 IEEE Standard for Information Technology – Systems Design – Software Design Descriptions

Integration and Implementation:

· American Society of Heating, Refrigeration, and Air Conditioning Engineers, Inc. (ASHRAE) Standard 55-2017, Thermal Environmental Conditions for Human Occupancy

· ASHRAE Standard 62.1-2016, Ventilation for Acceptable Indoor Air Quality

· Resource Conservation and Recovery Act of 1976 (RCRA), 42 U.S.C. §§ 6901-6992k

Logistics, Supply Support, Operations, and Maintenance:

· GEIA-STD-007B, Logistics Product Data

· SAE JA1011, Aug 2009, Evaluation Criteria for Reliability-Centered Maintenance (RCM) Processes

· ASTM D3951-18, Standard Practices for Commercial Packaging

Quality Assurance:

· International Organization for Standardization (ISO) 9001:2015, Quality Management Systems – Requirements

· ISO/IEC 90003, Software Engineering

Safety and Health:

· American National Standards Institute (ANSI) Z535-2011, Safety Alerting Standards

· NFPA 70, National Electric Code

· NFPA 70E, Standard for Electrical Safety in the Workplace

· NFPA 70, Article 110.26, National Electric Code, Spaces About Electrical Equipment

· Institute of Electrical and Electronics Engineers (IEEE) 1584, Guide for Performing Arc Flash Calculations

· NFPA 101, Life Safety Code

· NFPA 90A, Standard for Installation of Air-Conditioning and Ventilating Systems

Security and Safety

· National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Security and Privacy Controls for Federal Information Systems and Organizations

· Federal Information Security Management Act (FISMA), 44 U.S.C. §3541

· NIST FIPS 199, Standards for Security Categorization of Federal Information and Information Systems

· NIST FIPS 200, Minimum Security Requirements for Federal Information and Information Systems

· Homeland Security Presidential Directive Number 12 (HSPD-12), Policies for a Common Identification Standard for Federal Employees and Contractors

· Office of Management and Budget (OMB) Circular A-130, Management of Federal Information Resources

· OMB Memorandum M-06-16, Protection of Sensitive Agency Information

· OMB Memorandum M-11-11, Continued Implementation of Homeland Security Presidential Directive (HSPD) 12—Policy for a Common Identification Standard for Federal Employees and Contractors

· NIST SP 800-18, Guide for Developing Security Plans for Federal Information Systems

· NIST SP 800-25, Federal Agency Use of Public Key Technology for Digital Signatures and Authentication

· NIST SP 800-30, Guide for Conducting Risk Assessments

· NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure

· NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach

· NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View

· NIST SP 800-64, Security Considerations in the System Development Life Cycle

· NIST SP 800-81-2, Secure Domain Name (DNS) Deployment Guide

· NIST SP 800-122, Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)

· NIST SP 800-137, Information Security Continuous Monitoring for Federal Information Systems and Organizations

· NIST SP 800-175, Guideline for using Cryptographic Standards in the Federal Government Military Specifications, Standards, and Handbooks

· MIL-STD-2073-1, Standard Practice for Military Packaging

· MIL-STD-129R, Standard Practice Military Marking for Shipment and Storage

· MIL-STD-31000, Revision A, Technical Data Packages

· DOD-STD-1700, Data Management Program

· MIL-HDBK-61A, Configuration Management Guidance

· MIL-PRF-81705E, ESD Materials, Bags & Performance Specification Other Publications

· 41 C.F.R. part 101-42, Disposition of Personal Property with Special Handling Requirements

· National Environmental Policy Act of 1969 (NEPA), 42 U.S.C. §§ 4321 to 4370m-12

REQUIREMENTS

Program Management C.1.1.1 Program Management Organization The Contractor must establish and maintain a Program Management Organization to efficiently and effectively execute the requirements of the contract. The Contractor must assign a dedicated Program Manager (PM) to organize, anticipate, plan, schedule, implement, control, analyze, and report on all elements of the contract. The PM must have sufficient corporate authority and resources to direct, execute, and control all elements of the program, and ensure that products are delivered and implemented without disruption to the NAS.

The Contractor must ensure that Contractor team activities are managed to align with FAA directives, and ensure that activities and work products are compliant with all relevant and evolving Federal Government laws, regulations, policies, directives and instructions. The Contractor must manage the work to align with established and evolving FAA processes at all sites.

The Contractor must manage and track the functional and technical performance, including the performance of any subcontractors, against the project requirements, deliverables, and schedule. The Contractor must ensure that the various lifecycle activities performed by the Contractor are in alignment (for Contractor-internal activities and with the FAA), and that effective cross-functional communication and flow of information occurs.

The Contractor’s Program Management Organization must be responsive to Government program-management requirements, control E-IDS business and technical activity, ensure compliance with contract requirements, and effectively manage any subcontractors.

Program Management Plan The Contractor must develop, deliver, and implement an integrated Program Management Plan (PMP) (CDRL M002). The PMP must integrate the management of all functional areas (i.e., System Engineering, engineering data and specifications, software engineering, configuration management, product assurance, integrated logistics support, etc.) and define the specific objectives to be accomplished for the successful execution of the program. The PMP must address all practice areas defined by the FAA including Program Management, Contractor Management, RIO Management, Quality Assurance, Verification and Validation, and Measurement and Analysis.

The PMP must specify the work tasks, at an overview level, required to meet the objectives. The PMP must also discuss the staffing and other resources required to meet contract requirements. The PMP must include the Program Schedule that implements each program phase (e.g. Phase 1, Phase 2 and Phase 3). The PMP must include means to ensure that the costs allocated to each phase remain in synchronization with actual funding provided by the FAA.

CDRL M002 Program Management Plan (PMP) Performance Reporting Metrics The Contractor must establish and maintain a performance-management system to ensure that the appropriate metrics are in place to manage, monitor, and report program performance. The performance metrics defined by the Contractor must be tied to the Work Breakdown Structure (WBS) and must support effective program monitoring by the FAA and the Contractor. The Contractor must also define performance metrics to track Problem Tracking Report generation and resolution.

The Contractor must document its approach and specific performance metrics in the PMP (CDRL M002). The Contractor must report (CDRL M004) and discuss the status of these metrics at each monthly Program Management Review (PMR).

The Contractor must delete, modify, or implement new performance metrics as required by the FAA.

C.1.1.2 Meetings and Reviews The Contractor must support recurring meetings such as status meetings, Technical Interchange Meetings (TIMs), PMRs, Formal Design Reviews (i.e. System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR) and evaluations with the Government) to discuss program progress, and identify potential problems and resolve identified issues. The Contractor must ensure that appropriate Contractor personnel from various and relevant functional disciplines attend FAA meetings.

Meeting Agenda, Minutes, Decisions, and Action-Item Tracking The Contractor must prepare Agendas, Meeting Minutes, Action-Item Lists, and Presentation Materials as directed for each meeting, conference, review, and evaluation to maximize the benefits of any meetings held with the FAA. The Contractor must provide an agenda and notify the CO of its readiness five business days prior to the start of each meeting, conference, review, and evaluation. All CDRL items required for a meeting, conference, review, or evaluation are to be delivered in accordance with the (CDRL M004) requirements.

The following instructions are applicable to all meetings, reviews, conferences, and evaluations:

1. All PMRs will be held at a Contractor-provided facility within thirty (30) miles of Washington, DC, unless otherwise directed by or approved by the government. All other meetings, conferences, and evaluations will be held at the Contractor’s facility unless otherwise directed by or approved by the Government. The Contractor must provide teleconferencing capability, internet access, and facility locations to accommodate necessary participation as requested by the Government. The Contractor must propose a date for the meeting, review, conference, or evaluation for the Contracting Officer’s Representative (COR's) approval.

2. The Government reserves the right to revise and to direct the Contractor to revise all agendas and presentation materials. The Contractor must provide appropriate Contractor personnel to respond to Government questions. The Contractor must prepare and deliver a summary of open, pending, and closed action items and presentation materials prior to the start of each scheduled meeting, conference, review, and evaluation. The Government will revise the delivery times when necessary.

3. The Contractor must record and submit minutes. The Contractor must track FAA decisions and action items until the disposition of any action is mutually agreed to by the Contractor and the Government.

4. Each assigned action item must have a due date and responsible person assigned, who must provide the status of the action at agreed-upon intervals until the action is closed.

5. Once the disposition of the action has been completed by the Contractor and validated by the Government, the action must be closed. The Contractor must maintain a history of all closed action items.

6. Unless otherwise specified by the Government, the Contractor must respond to all action items with a written closure statement. If an action item cannot be closed promptly, a plan of action must be developed for closure.

CDRL M004 Agenda, Meeting Minutes, Action-Item List, and Presentation Materials Program Kickoff Meeting Within 3 weeks of contract award, the Contractor must conduct a project kickoff meeting with the FAA, at the Washington, DC, headquarters facility. Prior to the meeting, the Contractor must develop and deliver an agenda and meeting materials (CDRL M004) based on the Contractor’s past experience, lessons learned and Program-Management best practices. The kickoff meeting must also include the following agenda items:

· Establishing a collaborative team environment and clear communication paths

· Discussion of contract and technical transition-in activities, including issues, risks, and mitigations

· Discussion of FAA E-IDS near-term and longer-term activities and clarifying objectives, challenges, relevant stakeholders, and specific expectations

The Contractor must provide a report on the meeting in accordance with CDRL M004.

Program Management Reviews (PMRs) The Contractor must conduct monthly PMRs with the FAA to review the work effort being conducted; however, the FAA reserves the right to decrease the frequency in accordance with program needs. The Contractor must deliver a comprehensive briefing (CDRL M004) on work progress that must include, but is not limited to, the following items:

· Cost, schedule, and performance of the program, to include:

· Integrated Master Schedule (IMS) (CDRL M016)

· Current progress and look-ahead of ongoing work, to include development of deliverables

· New work planning

· Review of open action items from prior PMRs, future required actions, and continual funding status

· Anticipated differences among contract milestones, schedules, technical performance, cost, Estimate at Completion (EAC), and performance status including identification of major drivers behind and cost and schedule variances and the action plans to resolve these variances

· Software Size Estimate updates including any changes to the methodology used or the basis of the estimates

· Changes in organizational chart and planned versus actual staffing by functional discipline

· Current and anticipated risks and mitigations

· Known issues or obstacles impeding progress, and recommended solutions

· Trouble-ticket status and root-cause analysis

· Commercial-product obsolescence, supportability issues, and recommended actions

· Requests for deviations and waivers from the requirements and associated justification

· At the close of each quarter provide number (by product type) of environmentally sustainable electronic products provided by the Contractor during the previous Federal government fiscal year quarter.

The Contractor must adjust the meeting discussion topics as appropriate, and as directed by the FAA, throughout execution of the program to ensure effective program execution.

The Contractor must provide a report on the meeting in accordance with CDRL M004.

Support of Technical Reviews and Meetings The Contractor must ensure that Contractor staff with appropriate skill sets are in attendance to ensure success of the various informal technical meetings, technical working groups, and Technical Interchange Meetings (TIMs) held with the FAA throughout the program lifecycle. The Contractor must ensure that Contractor staff effectively prepare and document the meetings (CDRL M004), identify any risks or issues that occur because of any meeting decisions, and implement decisions as agreed to by the FAA.

Technical Interchange Meetings and Working Groups At the request of the Government, TIMs must be held to discuss issues that require mutual resolution or further clarification. The Contractor may also request that a TIM be held. The Government must approve all TIMs prior to their occurrence. Not all meetings are of sufficient importance to warrant a TIM. The Contractor must use best efforts to provide at least a three-day notice of intent to facilitate a TIM in order to ensure government attendance.

The Contractor must participate in E-IDS Working Groups. Working Groups are used to plan strategic activities, implement and track the execution of such activities, and identify and resolve the issues associated with these activities. Working groups may also be informal in nature to ensure effective communication and collaboration occurs between the FAA and Contractor, as well as between different project teams. E-IDS Working Groups may be conducted via teleconference or video conference or in person.

For both Working Groups and TIMs the Contractor must prepare meeting agendas, meeting minutes, and presentation materials, in accordance with (CDRL M004).

C.1.1.3 Program Control The Contractor must implement and conduct a program-control activity that ensures efficient and timely program execution. The program-control effort must be able to identify and report the status of the program at any time. The program-control activity must be designed in a way that allows identification of program anomalies and correction plans in a timely manner.

The Contractor must provide ongoing access to pertinent records and data, including but not limited to those supporting the cost data reported, during each program phase and throughout performance of the entire contract.

Contract Work Breakdown Structure (CWBS) The Contractor must generate and maintain a CWBS and CWBS Dictionary for this effort that is a WBS tailored to the E-IDS contract and that aligns with the WBS provided within Attachment J.16. The CWBS is the basis for the Contractor-defined lower-level CWBS elements, cost accounts, and work packages during the performance of the contract.

The CWBS matrix (WBS to functional responsibility) must include expansion down to and including the cost account level. The CWBS must describe the work that will be accomplished and must facilitate management data collection and reporting.

The Contractor must use the CWBS as the framework for reporting contract planning, budgeting, and schedule status. Contract modifications that modify, add, or delete scope of work under the contract must be incorporated into appropriate CWBS cost accounts for work package identification, definition, and procurement-request relationships, as in the basic contract.

During the performance of the contract, no change to the approved CWBS, associated definitions, or any of the reporting elements may be done by the Contractor without prior written approval from the Government Contracting Officer. The CWBS must be managed and submitted as part of the PMP (CDRL M002) E-IDS Program Schedule The Contractor must develop, update, maintain, and deliver a schedule, using Microsoft Project format, for discussion at the monthly PMR (CDRL M016) for the E-IDS program. The Contractor must portray an integrated schedule for the design, production, integration, test, delivery, installation, training, and support of E‑IDS in accordance with the contract. The schedule must document all dependencies.

The Contractor must ensure that the schedule is consistent with the Earned Value Management System (EVMS) and identify the program critical path.

Earned Value Management The Contractor must utilize an Earned Value Management Systems (EVMS) that complies with ANSI/EIA Standard 748, Earned Value Management Systems (EVMS), to plan, establish, control, and report the status of the effort. The Contractor must submit EVM status in accordance with (CDRL M016) to provide earned-value information for discussion in the monthly PMR. The Contractor must use outputs of its EVMS as the basis to report on program status during PMRs.

The Contractor must submit a monthly Contract Funds Status Report (CFSR) in accordance with (CDRL M014). The Contractor must provide documentation that its EVMS is certified in accordance with Section I of this contract.

The Contractor’s EVMS must provide for an early indication of cost and schedule problems, and their relation to technical progress. The Contractor’s EVMS must include, but is not limited to:

· Establishing the time-phased budgeted cost of work scheduled (including work authorization, budgeting, and scheduling), the budgeted cost for work performed, the actual cost of work performed, the budget at completion, the estimate at completion,…