DFO Segment 2 TO1.pdf

Task Order 1 STATEMENT OF WORK Screening Information Request (SIR) 693KA8-21-R-00001

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

WIDE AREA AUGMENTATION SYSTEM

Dual Frequency Operations (DFO) 2 [DFO-2]

Task Order 01 Program Management

Statement of Work

1 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the

1. Task Order Scope Task Order 1 defines the Contractor Program Management efforts for the achievement of Wide Area Augmentation System (WAAS) Dual Frequency Operations (DFO) 2 [DFO-2].

Definitions of key WAAS terminology are included in Appendix A of Section C of the IDIQ contract. Background information on WAAS is available at https://gps.faa.gov.

2. Supplies or Services & Cost/Price

The PRISM task order document will reflect the obligated funding and applicable lines of accounting. For informational purposes a RECAP of FUNDS is provided for administrative purposes as an attachment to this Task Order

2.1. Contract Line Item Numbers (CLINs)

This Task Order utilizes the following contract types: Time-and-Materials (T&M) and Cost Reimbursable (CR) as included in the following CLINS:

CLIN

CLIN Description Type Funds

Contract Type SOW Reference NTE Total

0001 Program Management F&E T&M 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9.

4.10, 4.11, 4.12

0002 Travel/Other Direct Costs

F&E CR 3.7, 3.9, 3.10 $ $

Remainder of the Page Left Intentionally Blank

2 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

3. Tasks

3.1. Program Management

The Contractor must assign a dedicated Program Manager (PM) to organize, plan, schedule, implement, control, analyze, and report on elements of the contract. The PM must have the resources and authority to ensure effective, efficient, and timely program execution.

The Contractor must develop and implement an integrated Program Management Plan (PMP) Contactor Data Requirements List (CDRL A001), which addresses the management of all Task Orders issued under this contract.

The Contractor is responsible for the management of subcontractors to ensure compliance with Task Order requirements.

3.2. Monthly Program Status Report

The Contractor must submit a Monthly Program Status Report (MPSR) (CDRL A002). This report must document the status of all Contract work efforts, including all issued Task Orders, for the previous month and through cumulative contract performance. The Contractor must provide contract status with a summarization of funding, to include contract data, performance data, and problems or areas of interest and must identify completed work efforts in the MPSR.

CDRL A002 Monthly Program Status Report

3.3. Contractor Work Breakdown Structure

The Contractor must establish and maintain a Contract Work Breakdown Structure (CWBS) (CDRL A003) and a dictionary in compliance with the Acquisition Management System (AMS) Work Breakdown Structure (WBS) policy. The CWBS must consider all Task Orders issued under the contract. Each Release activity must have unique WBS numbers.

CDRL A003 Contract Work Breakdown Structure

3.4. Earned Value Management and Integrated Master Schedule

The Contractor must deliver an Integrated Program Management Report (IPMR) (CDRL A004) each month starting 12 business days after the second full accounting month after Task Order award and include status for all active Task Orders. The Contractor’s Earned Value Management system must be able to generate reports to the Work Package level.

The Contractor must ensure that the results of program risk assessments are incorporated into the IPMR Estimate at Completion (EAC). Technical or schedule impacts to the EAC as a result of the risk assessment must be fully explained in the IPMR. The Contractor must include a monthly spend plan that identifies monthly planned expenditures for total estimated award value of all cost-reimbursable contract line items. The planned expenditures must be identified by Contract Line Item Number and must be delivered with the IPMR. The planned expenditures must be reconcilable to the IPMR Format 1.

CDRL A001 Program Management Plan

3 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The Contractor must develop and maintain an Integrated Master Schedule (IMS) (A005), in Microsoft Project format, based on a logical and efficient sequence of events designed to accomplish the tasks described in the contract and all issued task orders. The IMS must present a networked schedule with a critical path identified for design, development, integration, installation, and test activities. The IMS must be consistent with the CWBS. The IMS must incorporate activities for subcontracts consistent with the Contractor’s approved Earned Value Management System. The Contractor must submit all proposed baselined IMS changes that affect all issued Task Order milestones to the FAA for approval.

The Contractor must incorporate all issued Task Order CDRL deliveries into the IMS except for recurring monthly CDRLs. The IMS must include significant activities and milestones of the Contractor, subcontractors, and dependencies on the FAA. IMS activities must have constraints, dependencies, and relationships identified. The monthly IMS updates must reflect percent completion for baselined items and include additions for awarded Task Order items. The Contractor must notify the FAA of any changes to FAA schedule dependencies within 14 days of identification of those changes.

CDRL A004 Integrated Program Management Report

CDRL A005 Integrated Master Schedule

3.5. Integrated Baseline Review

The Contractor must support an Integrated Baseline Review (IBR) within one hundred and twenty (120) days of award of this Task Order. The FAA Program Management Office (PMO) may request delta IBRs in the event an issued Task Order is deemed significant enough to require baseline adjustment. The IBR will evaluate the Contractor’s implementation of the performance measurement baseline. At the IBR, the Contractor must demonstrate an understanding of the program scope, schedule, resources, and inherent risks; provide a management approach; and demonstrate adequate planning. The Contractor must follow IBR guidance provided in the “National Defense Industrial Association (NDIA) Program Managers' Guide to the Integrated Baseline Review Process”. As a result of the IBR, the FAA will provide the contractor with a Final IBR Report within 30 days of the conduct of the IBR. Should any formal Action Items exist, the contractor must provide an IBR Corrective Action Plan (A006) no later than thirty (30) days from the date of this final report.

CDRL A006 IBR Corrective Action Plan

3.6. Risk Management

The Contractor must establish, implement, and maintain a Risk Management program that provides an overall strategy and approach for effectively managing cost, schedule, and technical performance risks for the duration of the contract. The Contractor must use the Risk Thresholds in Section 4.3 of the “FAA Systems Engineering Manual” Version 1.1 as guidance. The Contractor must include a Risk Management Plan (RMP) in the PMP (CDRL A001). The RMP must describe the process for timely identification of risks; accurate risk assessment;

development and implementation of mitigation plans; and monitoring, tracking, and reporting of

4 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

risk items. The RMP must describe in detail the Contractor’s coordination with subcontractors, suppliers, and the FAA. The Contractor must include risks identified by the FAA within the risk management process.

3.7. Meetings

Unless otherwise requested by the FAA, meetings will be held at the Contractor's facilities within the United States or at the FAA Headquarters in Washington D.C. (or FAA support contractor facilities, as directed). During meetings, the Contractor and the FAA will discuss specific technical activities, including studies, test plans, test results, design issues, technical decisions, and implementation concerns. The Contractor must provide personnel with the requisite skills to actively engage in topics identified on the meeting agenda. The Contractor must facilitate meetings, providing facilities, materials, office equipment, clerical personnel, technical data, and subcontractor participation when requested by the FAA. Meetings must be conducted in accordance with the approved PMP and requirements of this Task Order.

The Contractor must provide the FAA with proposed agendas at least fifteen (15) working days before the meeting.

The Contractor must prepare and submit agendas, minutes, and presentation materials for meetings. Meetings are considered complete upon the FAA approval of the Meeting Minutes

(CDRL A007).

CDRL A007 Meeting Minutes

3.8. Post Award Conference

The Contractor must host and conduct the Post Award Conference to be held at a Contractor-designated site. The FAA will determine the specific date within two (2) weeks after the award of this Task Order. The Contractor must address the plans and schedules for the contract, identified program risks, and technical and programmatic findings and issues.

3.9. Quarterly Meetings

The Contractor must plan to host and conduct Quarterly Meetings, commencing within sixty (60) days after conduct of the Post Award Conference. The conduct of each meeting may include, as appropriate and subject to Task Order awards: 1) System Engineering Working Group (SEWG).

2) Design Reviews; 3) WAAS Integrity Performance Panel (WIPP); and, 4) Contractor Depot Logistics Support (CDLS) status.

3.10. Program Overview Meeting

The Contractor must host a Program Overview Meeting twice a year in conjunction with a scheduled Quarterly Meeting. The Contractor must provide general program status, contract funding status, all issued Task Order funding status, earned value management metrics, program risks, and program schedule status.

3.11. Data Collaboration Environment

The Data Collaboration Environment (DCE) supports cooperative work irrespective of geographic location. Members will have the ability to save and access data via the Internet with

5 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

appropriate access controls, support online meetings, provide revision controls for documents and maintain audit trails. The Contractor must implement and maintain a DCE in which information in electronic media format may be shared between the Contractor and the FAA. The DCE must be internet web-based and continuously accessible (twenty-four [24] hours a day, seven [7] days a week) from outside or inside the Contractor’s facilities. The Contractor must control access to the DCE and control the visibility of content stored in the DCE. The DCE must be capable of being partitioned into separate working areas with access to these areas protected by group and individual permissions defined by DCE Administrators. The Contractor must host shared folders and files with proper access security.

The Contractor must create directories within the DCE administratively controlled by the FAA for the electronic delivery of CDRLs and Contracts Letters.

The Contractor must maintain a searchable index of files within the DCE.

The DCE must support user profiles that include email notification for changes within directories accessible by the user.

The Contractor must ensure DCE data security and protect against data vulnerability.

The DCE must maintain a revision history of content changes and must be backed up to prevent the loss of data.

The DCE must have a mechanism for simplified file synchronization that allows users to maintain copies of all documentation offline.

4. System Engineering

4.1. System Engineering Management

The Contractor must prepare and deliver a Systems Engineering Management Plan (SEMP) (CDRL A008). The SEMP must define the Contractor’s system engineering management approach and supporting processes, as tailored to meet the requirements of each issued Task Order, as required. The Contractor must conduct activities associated with planning, managing, supporting, executing, and maintaining systems engineering processes for all issued Task Orders in accordance with the approved SEMP.

The Contractor must designate a focal point for FAA – Contractor technical interchange. The identified focal point must coordinate engineering and technical expertise across issued Task Orders and activities.

CDRL A008 System Engineering Management Plan

4.2. System Engineering Working Group

6 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The Contractor must schedule SEWG meetings as part of the Quarterly Meeting (Section3.9).

The SEWG will be co-chaired by the FAA and a representative from the Contractor and comprises representatives from the Contractor, FAA, and FAA support contractors.

For each SEWG, the Contractor must coordinate the agenda with the FAA no later than 15 working days before the SEWG meeting. The Contractor must submit presentation materials to the FAA no later than one (1) week before the SEWG meeting.

4.3. WAAS Integrity Performance Panel

The WAAS Integrity Performance Panel (WIPP) is a technical advisory group chartered by the FAA to provide oversight on integrity and performance aspects of WAAS. The WIPP includes representatives from the FAA, supporting contractors, supporting universities, and other government agencies. The WIPP is responsible for overseeing integrity analysis, algorithm development and validation, and performance monitoring. Integrity analysis includes the activities associated with ensuring that the Probability of Hazardously Misleading Information (PHMI) requirements of WAAS are continuously met. The Contractor must participate in the WIPP, prepare presentations and supporting materials, and present the results of any FAA-directed investigation or analyses. The Contractor must schedule a WIPP meeting as part of each Quarterly Meeting (Section 3.9) and coordinate the agenda with the FAA no later than 15 days prior to meeting conduct. Additionally, the contractor must support WIPP teleconferences that will be conducted on an as-needed basis.

4.4. Government Furnished Equipment Environment Maintenance

Upon installation and verification of the Government Furnished Equipment (GFE) Environments as directed via separate Task Order, the Contractor must maintain the GFE Environments, including the replacement of failed GFE Line Replaceable Units (LRUs) and other materials that comprise the GFE Environments. The Contractor must coordinate with the FAA Depot for replacement and repair of GFE WAAS baseline LRUs.

The Contractor may need to update GFE environments for each Release to account for hardware or software changes. The Contractor must coordinate all environment updates or modifications with the FAA as part of the baseline Configuration Management process via the Environment Change Control Board (ECCB). The Contractor must update all environment documentation and verification procedures affected by the environment changes. The Contractor will be responsible for all audits, updates, upgrades and HW/SW deployments to the GFE environments.

The Contractor must maintain environment documentation, including an update of functional verification procedures, with each change. The Contractor must provide a data backup capability that prevents the loss of FAA data.

The Contractor must allow for the installation of GFE data collection equipment at the Contractor’s facility. The data collection equipment, approximately the size of a desktop Personal Computer, will connect to GFE data circuits for transmission of data to the William J.

Hughes Technical Center from each of the GFE Shadow Environments located at the Contractor’s facility.

7 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The Contractor must assist the FAA as necessary with the integration of any development, integration, and test environment changes at FAA facilities resulting from Contractor Release development efforts.

The Contractor must provide the FAA full and unencumbered high-speed remote access to all GFE Environments for auditing, updates, upgrades, and software deployments.

The Contractor must develop and maintain a shared password vault with FAA for the GFE at contractor facility. The Contractor must provide remote monitoring and backup access to all GFE equipment at the contractor facility.

4.5. Joint Access Data Archive Enhancement to GFE Environments The various data analyses conducted for WAAS development, testing, performance monitoring, and anomaly analysis produce a large amount of valuable data. The FAA currently maintains a 365-day on-line archive in the FAA facility in Oklahoma City. A similar capability is necessary for the Contractor facility and is not part of the GFE environments provided. The Contractor must design, install, test, document, utilize, and maintain an enhancement to the GFE environments to provide this capability at the Contractor facility.

The Contractor’s implementation must support a minimum of 500 Terabytes of storage.

The Contractor must provide FAA with local and remote access to the Contractor data archive for the duration of the contract. The Contractor network must allow syncing of files up to 40 GB to be transferred to the FAA in under 4 hours using Secure File Transfer Protocol (SFTP) over Secure Shell (SSH).

All data should be backed up to LTO7 tape using NetBackup software. The Contractor’s library catalog must be remotely shared with the FAA. Alternatively, a cloud storage solution can be used provided the FAA has access to the cloud storage archive.

The Contractor’s archive design must store collected WAAS field system data for a rolling window of 7 years.

The Contractor’s archive design must store 1 year rolling window of shadow data for each WAAS GFE shadow system provided or constructed by the Contractor as directed under this Contract via separate Task Orders.

4.6. Software Licenses

The Contractor must obtain and maintain commercial software licenses for assemblers, compilers, code libraries, and other Commercial-Off-the-Shelf (COTS)/commercially available software systems, to include software upgrades, as required. See Attachment 2 for detailed list of licenses and estimated quantities.

To the extent that FAA is required to assent to third-party commercial software licensing terms to access the software, the Contractor must ensure that the following term applies to the third-

8 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

party license or that the FAA is provided an opportunity to review the license before the Contractor implements the software:

The licensor of the services described herein agrees to be bound by the FAA's Acquisition Management System in all applicable terms and conditions. All disputes and claims with the FAA arising under or in connection with this agreement will be adjudicated by the FAA’s Office of Dispute Resolution for Acquisition pursuant to Acquisition Management System (AMS) Clause 3.9.1-1 Contract Disputes (January 2020).

The Contractor must identify to the FAA any license issues or impacts – including any limitation, restrictions, or material license provisions that differ from existing software - to the software development baseline or software assurance baseline before making a determination to upgrade any software. The Contractor must report annually on software licenses, quantities, maintenance agreements, and FAA license rights, including transferability of such rights.

The Contractor must obtain FAA approval for the use of any open source software, identifying the open source software, its intended use, and the configuration management control(s) to be applied. The FAA will consider licensing restrictions, effects on transferability to the FAA, and intended use in determining approval.

At the completion of this Task Order, the FAA will provide direction to the Contractor regarding the transfer of commercial licenses and license agreements to the FAA.

4.7. Configuration Management

The Contractor must develop and deliver a Configuration Management Plan (CMP) (CDRL A016) tailored to the requirements of this Contract. The Contractor must identify a single point of contact for all configuration management related issues. The Contractor’s Configuration Management program must comply with MIL-HDBK-61B, Table A-3.

The Contractor must conduct activities for this Task Order in accordance with the approved CMP. The Contractor must maintain the CMP and must notify the FAA in advance of proposed changes. The Contractor must redeliver the CMP to the FAA for approval upon implementation of any approved change.

The Contractor must procure and implement the multi-site IBM ClearCase (CC) and ClearQuest (CQ) environment. The Contractor must provide a Secure File Transfer Protocol server for synchronization with the FAA’s CC/CQ installation. The FAA will provide the CC and CQ product versions at the time of the Task Order award. The Contractor must procure necessary licenses and server hardware necessary to implement the CC/CQ environment. The Contractor must follow FAA-provided setup and configuration instructions

4.8. WAAS Change Control Process

WAAS is a baselined, safety critical system within the National Airspace System (NAS).

WAAS changes are authorized by the Navigation Programs Configuration Control Board (NAV

CDRL A016 Configuration Management Plan

9 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

CCB) according to FAA configuration management policy as identified in FAA Order 1800.66.

The NAV CCB has delegated authority to the WAAS Change Review Board (WCRB) for tracking, reviewing, and pre-approving system change proposals. The WCRB developed the WAAS Change Control Process (WCCP) to establish the WAAS system level configuration management policy. The contractor must adhere to the WCCP by generating change and problem records and providing technical information, as requested, to the WCRB.

The primary change tracking record for WAAS is called the WAAS Problem Report (WPR). A WPR is used for documenting problems, proposing enhancements, and tracking anomalies. A collection of WPRs are grouped together using a WAAS Change Request (WCR). Each FAA or contractor developed Release will have at least one WCR and one or more WPRs.

4.8.1. Additional Change Control Processes

In addition to the WCCP, several other change control processes are used for WAAS. Each of these processes has its own control board and a change record that traces to a parent WPR. The contractor must support these processes by creating change records, attending control board meetings, and dispositioning contractor-generated change requests. The change control mechanisms are as follows:

Specification Change Request (SCR) An SCR is used to coordinate, review, and disposition proposed changes to WAAS system, hardware and software requirements specifications.

Problem Change Request (PCR) A PCR is used to coordinate, review, and disposition proposed changes to WAAS software and tools source code.

Hardware Change Request (HCR)

An HCR is used to coordinate, review, and disposition proposed changes to the WAAS hardware drawings.

The contractor must identify points-of-contact to be co-chairs for each of the control boards (SCR, PCR, and HCR).

4.9. Change Control Boards

The Contractor must establish Change Control Boards (CCBs) as identified in the Contractor’s CMP. The Contractor must allow the FAA to participate in the Contractor’s CCB meetings where any WAAS changes are discussed, approved, or revised. The Contractor must identify in their CMP the function of each CCB. The Contractor’s CCB must approve HCRs, PCRs, and SCRs per the Contractor’s CM process. The Contractor and the FAA are both responsible for generating WPRs. The FAA approves any subsequent Contractor work related to a WPR in accordance with the WCRB.

The Contractor must identify representatives to participate in the WAAS CCB meetings. If requested by the FAA, the identified Contractor representatives must participate in the FAA lead WAAS CCB meetings.

10 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the

With Contractor and FAA COR concurrence, the FAA and Contractor may hold joint CCB meetings.

4.10. Configuration Control Process

The Contractor must establish an internal CCB and establish and implement procedures to accomplish change control per the WCCP (Section 0) until the established operational baseline is updated to include the respective change.

4.11. Configuration Status Accounting

The Contractor must implement and maintain a Configuration Status Accounting System. The Contractor must provide a Configuration Status Accounting Report (CDRL A017) for each Release.

CDRL A017 Configuration Status Accounting Report

4.12. Quality Assurance

The Contractor must prepare and deliver a Quality System Plan (QSP) (CDRL A018). The Contractor must adhere to the QSP for the duration of this Contract. The QSP must describe the Contractor’s quality assurance program implemented in accordance with ANSI/ISO/ASQ Q9001-2008, FAA-STD-026A, and RTCA/DO-178B.

CDRL A018 Quality System Plan

5. Deliverables and Delivery Schedule The deliverables and their delivery schedule is outlined in the Contract Data Requirements List (CDRL) definitions (See Contract Section J--Attachment 1) in the Indefinite Delivery, Indefinite Quantity (IDIQ) contract.

6. Inspection and Acceptance The work efforts defined under this Task Order are considered complete upon conduct of required activities and upon delivery and approval of required CDRLs.

7. References/Applicable Documents All applicable standards and specifications referenced in the DFO-2 IDIQ Contract in addition to the following specifications, handbooks, orders, standards, and drawings form a part of this Task Order and are applicable to the extent specified herein.

7.1. FAA Standards, Specifications and Manuals

Document Number Document Title FAA-STD-026A Software Development for the National Airspace System (NAS), June 1, 2001 FAA Order 4600.27C Personal Property Management, September 4, 2015 FAA_SEM_V1.1 FAA System Engineering Manual, September 11, 2015 Acquisition Management System (AMS) – http://fast.faa.gov

11 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

FAA Air Traffic Organization Safety Management System Manual, Version 2.1, May 2008

FAA Order 1370.121 FAA Information Security and Privacy Program and Policy, December 23, 2016

Copies of the above listed FAA documents may be obtained from the following source:

Department of Transportation Library https://www.transportation.gov/library

7.2. Commercial Standards and Specifications

Document Number Document Title

ANSI/ISO/ASQ

9001:2015

Quality Management Systems: Requirements

RTCA/DO-178B Software Considerations in Airborne Systems and Equipment Certification

Copies of ASTM and RTCA documents may be obtained from the following sources:

American National Standards Institute (ANSI), https://www.ansi.org

RTCA, https://www.rtca.org/content/publications

7.3. Military Standards and Handbooks

Document Number Document Title GEIA-STD-0007 Logistics Product Data, October 2006 MIL-STD-2073-1D Standard Practice for Military Packaging, December 15, 1999 DI-MGMT-80227 Contractor’s Progress, Status and Management Report Data Item

Description DI-MGMT-81861 Integrated Program Management Report Data Item Description

Copies of the above listed Military Standards and Handbooks may be obtained from the following source: http://everyspec.com

7.4. Other Documents

Document Number Document Title NDIA Program Managers' Guide to the Integrated Baseline Review Process ANSI/EIA 748-D Earned Value Management Systems ANSI/EIA-649 National Consensus Standard for Configuration Management

Copies of NDIA and ANSI/EIA 748-D documents may be obtained from the following source:

National Defense Industrial Association https://www.transportation.gov/library https://www.ansi.org/ https://www.rtca.org/content/publications

12 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

https://www.ndia.org

Copies of ANSI standard EIA-649 may be obtained from the following source:

https://www.sae.org/standards

8. Period of Performance The period of performance of this Task Order is 6 years plus two (2) two-year options, subject to FAA’s exercise of options of the master contract under which the Task Order will be issued.

FAA anticipates concurrent award of the Contract and this Task Order.

9. Place of Performance The Contractor must perform the required tasks at the Contractor’s facilities.

10. Travel/ODC Travel/ODC costs are authorized for this task order. All travel will be handled in accordance with Section G.11 of the IDIQ contract.

11. Invoicing Invoicing will be completed in accordance in Section G.9 of the IDIQ contract.

12. Key Personnel The Contractor must identify personnel to fill the positions identified as key personnel below.

The Contractor must clearly state the roles/responsibilities and authorities held by each position and must describe for each position the span of control, degree of autonomy, and lines of communication. The Offeror is advised to use their best business acumen and expertise to determine the required labor categories and level of effort to fulfill the requirements of this Task Order SOW.

The Contractor must:

• describe the location of these positions in the proposed organizational structure for this Task Order;

• detail the lines of reporting and communications up through the management structure and up through the corporate offices and show lines of control and direction;

• define the personnel positions in their respective line organization’s structure; and,

• provide rationale for the selection of the key personnel.

Qualification statements must be submitted for key technical and management personnel to be assigned to this Task Order. Key Personnel positions will be staffed in accordance with Section H.10 of the IDIQ contract and in accordance with requirements outlined in “Minimum Qualifications for Key Personnel, Labor Category Descriptions, Resume Template”, attachment J-32.

The following key personnel labor categories have been identified for the task order:

1. Program Manager: Name/To Be Provided by Contractor https://www.ndia.org/

13 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

2. Contracting Lead: Name/To Be Provided by Contractor

3. Technical Director: Name/To Be Provided by Contractor

4. Senior Scheduler: Name/To Be Provided by Contractor

ATTACHMENT 1

FUNDING HISTORY

Funding Document Appropriation Amount

14 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

ATTACHMENT 2

Task Order Assumptions

SW Licenses:

Software Tool Tool Vendor Quantity

AIX 7.1.0 TL3 SP5 OS IBM 15

IBM XL C/C++ for AIX, V13.1.0.0 Compiler IBM 15 IBM Rational Developer for AIX and Linux SW License IBM 15 Red Hat Enterprise Linux 6.8 Server OS Red Hat 20 Matlab R2013a MathWorks 4 Parasoft C++ test 10.3.2.169 Parasoft 5 PRQA QA Framework 1.0.5 Programming Research LTD 2 ClearCase 8.0.1 IBM 5 BRASS 18.2.0.12 SNMP Research 1

Dynamic Graphics for C/C++, Java and .NET GLG Graphics Builder (Enterprise), v.3.4 Generic Logic Inc. 1 DOORS version 9.6.1 IBM 5 CRADLE version 7.0 3SL 5 BuilderXcessory PRO Version 6.3 Integrated Computer Solutions 5 SOPOS (IBM Antivirus) SW License IBM 2 VxWorks 6.6.3.1 Wind River 4 Microsoft Windows XP Microsoft 1 PKZIP 14.00.1128 PKWARE Inc. 400 Simple Agent Pro 9.5.1 SimpleSoft, Inc. 4

Travel: The Contractor should assume one technical meeting and one programmatic meeting per year at either FAA HQ or FAA’s National Airways Systems Engineering (NASE) facility in Oklahoma City, OK.

Issuance of Task Order: At Contract Start