FAA_SIR_693KA8-21-R-00001_DFO2_Amendment_0001.pdf

IANN T WASHINGTON Digitally signed by IANN T WASHINGTON Date: 2021.08.16 13:16:31 -04'00'

PART I – SECTION C STATEMENT of WORK Screening Information Request (SIR) 693KA8-21-R-00001/Amendment 0001

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 Contracting Officer.”

C.1 GENERAL

C.1.1 Objective The primary goal of this acquisition is to establish a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract for technical, acquisition, and logistics support for the Wide Area Augmentation System (WAAS) Phase 4B.

C.1.2 Background The WAAS Dual Frequency Operations (DFO) - 2 (DFO-2) procurement provides for the continuation of technical refresh and Dual Frequency (DF) capability development that was initiated under the WAAS Phase 4A - DFO Segment 1 contract. The objectives of the DFO-2 Contract are as follows:

1. Continue technical refresh with the introduction of commodity x86 processors and a transition from the Advanced Interactive Executive (AIX) Operating System to Linux, as well as integration of new Ground Uplink Stations (GUS) receivers and firmware, updated reference receivers, and other equipment to address obsolescence;

2. Introduction of automated requirements testing capabilities;

3. Transition WAAS telecommunications network to instead utilize FAA-mandated cloud-based network services;

4. Update WAAS security posture to support open network framework;

5. Develop and test operational capability introduction of WAAS DF services;

6. Continue WAAS Geostationary Earth Orbiting (GEO) constellation sustainment with GEO 8 and 9 integration and deployment;

7. Finalize the WAAS Dual Frequency service Full Operational Capability;

8. Incorporate Satellite Based Augmentation System (SBAS) authentication and resiliency updates as required by the International Civil Aviation Organization (ICAO); and,

9. Continue Contractor Depot Logistics Support (CDLS) services.

All modification must be developed and fielded while maintaining all operational and performance requirements for the existing Single Frequency User Service.

Definitions of key WAAS terminology are included in Appendix A. Background information on Satellite Based Augmentation System (WAAS) is available at http://gps.faa.gov.

C.1.2.1 Program Organizations The FAA WAAS Program Office, located at FAA Headquarters in Washington, D.C., is responsible for the design, development, and overall management of WAAS.

The WAAS Second Level Engineering Support organization is National Airway Systems Engineering (NASE) located at the Mike Monroney Aeronautical Center (MMAC), Oklahoma City, OK. NASE is responsible for the continued operation of WAAS and maintains the WAAS product baseline. NASE also conducts performance monitoring of WAAS and resolves anomalies. NASE validates Release performance and operational cutover procedures using its test environment before fielding. The term ‘Release’ refers to the collection of operational and non-operational hardware and software changes, documentation changes, and maintenance procedure changes that encompass a change to the WAAS operational baseline.

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.”

NASE will produce a Maintenance Release approximately once each calendar year. Generally, these Maintenance Releases include modifications to address maintenance issues, and in some cases additional changes are needed for specific fielding needs, e.g., relocation activities. There are occasional needs for a test-related modification when performance or integrity issues require resolution. The Contractor must coordinate NASE Maintenance Releases with all Contractor development and release efforts, including sharing a) the code baseline, b) hardware baseline, c) non-op tools baseline, d) requirements baseline, and e) configuration management activities.

These activities will be detailed within Task Order(s).

WAAS Operations Specialists are located at the National Operational Control Center and the Pacific Operations Control Center. The WAAS Operations Specialists perform continuous 24 by 7 by 365 real-time status and performance monitoring of WAAS. WAAS Operations Specialists initiate manual actions such as corrective and periodic maintenance. The WAAS Operations Specialists are also responsible for certification of WAAS Service.

The WAAS Test Group, located at the William J. Hughes Technical Center, Atlantic City, NJ, is responsible for oversight of WAAS testing and provides key technical experts for WAAS design, test, operation, and anomaly resolution. The WAAS Test Group conducts additional real-time and historical performance monitoring of GPS and WAAS.

The FAA’s Logistics Center (FAALC), located at the MMAC, provides depot-level support for WAAS equipment. Replacement components are provided through the FAALC via CDLS services for the WAAS.

C.1.2.2 Relationship and Coordination with Other Organizations The contractor must coordinate as articulated in each awarded Task Order with the internal FAA offices, Governmental organizations, and Non-Governmental organizations named in each awarded Task Order to carry out the specified tasks and responsibilities as prescribed in the contract and awarded Task Orders.

C.1.3 Scope As identified in individual task orders, the services provided under this contract will support the Navigation Branch of FAA. The Contractor must furnish the necessary personnel, materials, equipment, facilities, travel, and other services required to satisfy the task order requirements for technical, logistics, acquisition and business support services described therein. While Section C.5 of this Statement of Work (SOW) identifies task areas, the scope of each task order will be further defined with the relevant specificity. All Contractor work activities under this Contract will be issued via Task Orders in accordance with the procedures outlined in Section G.11.

The personnel in each labor category must conform to or exceed the staffing qualifications outlined in Attachment J-32 of this contract. In accordance with the procedures in section H.23, the Government may waive requirements of Contractor personnel for individuals who possess superior qualifications in terms of education, capabilities, experience, or accomplishments.

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.”

C.2 APPLICABLE DOCUMENTS

The following specifications, handbooks, standards, and drawings form a part of this contract and are applicable to the extent specified herein. The latest version of these documents as of the contract award date shall apply, unless the version is otherwise explicitly provided.

C.2.1 Order of Precedence In the event of a conflict between the text of this SOW and the references cited herein, the text of this SOW takes precedence. Nothing in the SOW, however, supersedes applicable laws and regulations unless a specific exemption has been obtained at the contract or task order level.

C.2.2 FAA Specifications FAA-E-2892e (Draft)

System Specification for the Wide Area Augmentation System, TBD, DRAFT

Section J of this Contract includes a copy of the draft FAA-E-2892e.

C.2.3 FAA Standards and Orders FAA-HF-STD-004A Standard Practice: Requirements for a Human Factors Program, September 27, 2016 FAA-STD-026A Software Development for the National Airspace System (NAS), June 1, FAA Air Traffic Organization Safety Management System Manual, Version 2.1, April 2019 FAA_SEM_V1 FAA System Engineering Manual, Version 1.1, September 11, 2015 FAA Order 1100.157A

National Systems Engineering Divisions Maintenance Program Procedures, Operational Support, June 9, 1995

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

Federal Aviation Administration https://www.faa.gov

C.2.4 Other Documents Acquisition Management System (AMS) – https://fast.faa.gov National Defense Industrial Association (NDIA) Program Managers' Guide to the Integrated Baseline Review Process ICAO SARPS Incorporate International Civil Aviation Organization (ICAO) International

Standards and Recommended Practices (SARPS) Annex 10, Volume I Volume I Radio Navigation Aids Seventh Edition, July 2018

RTCA/DO-178B Software Considerations in Airborne Systems and Equipment Certification, December 1, 1992 https://www.faa.gov/ https://fast.faa.gov/

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.”

RTCA/DO-229E Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System Airborne Equipment

SAE ARP 4754 Certification Considerations for Highly-Integrated or Complex Aircraft Systems, November 1996

SAE ARP 4761 Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment. December 1996

Copies of the above-listed documents may be obtained and/or purchased from the following sources:

Acquisition Management System (AMS) http://fast.faa.gov

National Defense Industrial Association https://www.ndia.org

International Civil Aviation Organization https://www.icao.int

RTCA Inc.

www.rtca.org

SAE International https://www.sae.org

C.3 CONTRACT MANAGEMENT

Contract management is a mandatory element of all TOs issued under the DFO-2 contract. The objective of contract management is to provide the necessary program management, project control and contract administration required to manage a high volume, multiple contract type TO process – ensuring that cost, schedule and quality requirements of each order are tracked, communicated to the Government, and ultimately attained. While project control and contract administration are necessary elements of all task orders, all Program Management work required under this contract will be procured under Task Order 1. The use of commercially available automated tools, process expertise and other metrics supporting task order management are encouraged to provide quicker access, improved accuracy and enhanced accessibility.

Additionally, these will promote timely monitoring of status/deliverables, facilitate tracking of the quality of work products, and assist with gauging overall customer satisfaction.

The Contractor must provide the appropriate program management and project controls necessary to manage the Task Orders; ensure that costs, schedule, and quality requirements for each Task Order are continually tracked with status communicated to the FAA; measure and report Earned Value Management; provide necessary Supply Chain Management, Contract Management, Resource Management and Subcontract Management; and ensure that each Task Order is successfully completed.

http://fast.faa.gov/ https://www.ndia.org/ https://www.icao.int/ https://www.sae.org/

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.”

The Contractor must furnish the necessary and appropriate personnel, materials, equipment, facilities, travel, and other services required to satisfy the specific requirements of each Task Order.

C.4 CORE CAPABILITIES

The Core Capabilities are capabilities that the Contractor must be capable of providing in order to perform the SOW requirements. The Government has the right to request work and deliverables requiring some, all or none of the Core Capabilities in the Task Orders issued under this Contract.

1. Satellite Navigation: Technical knowledge of and experience with GPS and SBAS.

Understanding of GPS-based Position, Navigation, and Timing as identified in the GPS Interface Standards, GPS-IS-200 and GPS-IS-705 and the associated Standard Positioning Service Performance Specification. Understanding of Minimum Operational Performance Standards for Global Positioning System / Satellite-Based Augmentation System Airborne Equipment (RTCA/DO-229). Working knowledge of ICAO SARPs specific to SBAS, including the technical baseline for DF SBAS.

2. Communications: Technical knowledge of and experience with both TDM and Ethernet-based terrestrial communications systems. Understanding of industry-standard routing and data transmission protocols and solutions. Technical knowledge of transitioning from TDM-based to Ethernet-based terrestrial communications networks.

3. Software Development: Demonstrated matured and repeatable software development processes. Technical knowledge and application of FAA-STD-026A in the development and verification of software-intense, geographically-dispersed, near-real-time safety-critical systems.

4. Software Certification: Demonstrated knowledge of, and experience with, software assurance process based on the FAA-approved means of compliance applied to the software development and verification of the safety-critical systems required assurance to RTCA DO-178B Software Level (SL) B or its equivalent. Demonstrated knowledge of and experience with the application of FAA Advisor Circular No 23.2010-1.

Demonstrated working relations with current FAA approved Designated Engineering Representatives.

5. Systems Engineering: Technical knowledge of, and experience with, developing and executing systems engineering according to a Systems Engineering Management Plan.

This includes a) requirements development and allocation, b) requirements management,

c) configuration management, d) risk identification, e) management and requirement validation and verification, f) reliability, availability and maintainability, g) hardware drawing generation, and h) updates. Also, technical knowledge and experience with Dynamic Object Oriented Requirements System, ClearCase/ClearQuest, and Cradle.

6. System Security: Technical knowledge of and experience with designing and developing a secure, robust system based on industry security best practices and adherence to

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.”

NIST/FAA standards to achieve compliance to FAA security requirements. Demonstrated expertise in risk mitigation when migrating to a cloud-based communication network.

7. Automated Requirements-Based Testing: Technical knowledge of, and experience with, different levels of requirements-based testing (System, software, unit), as well as the ability to describe an automated test environment for the requirements-based test.

Additionally, experience with development and implementation of an automated test environment, including tool integration and development. Commercial Off-the-Shelf (COTS) tools are preferred over proprietary tools.

8. System Test Development and Test Environment maintenance and management:

Technical knowledge of and experience with maintaining and enhancing development and test environments.

9. Standards Implementation: Technical knowledge and understanding of both national and international technical aviation standards (e.g., FAA, RTCA, and ICAO standards).

10. Integrated Logistics Support: Technical knowledge of and experience with managing logistics for deployed systems, including assessment of obsolescence, replacement of obsolete components, depot level repair, shipping, and procurement of replacement items.

C.5 TASK AREAS

If ordered by FAA, the Contractor must provide support in the areas articulated below. As stated in C.1.3, all Contractor work activities under this Contract will be issued via Task Orders in accordance with the procedures outlined in Section G.11.

• Integrate the new GUS receiver upgrade into the existing GUS sites:

Design and develop WAAS modifications that replace existing GUS Receivers with updated GUS Receivers provided as Government Furnished Equipment (GFE).

• Update WAAS DO-178B SL D processors and migrate to Linux operating system:

Design and develop WAAS modifications to replace existing DO-178B SL D processors with Intel x86 based processors. As part of this modification, the Contractor may be required to transition the WAAS from an AIX-based operating system and compiler to a Linux operating system and compatible compiler.

• Develop and enhance automated requirements-based testing capabilities for

WAAS software (SW), including operational software, software toolsets, and software test capabilities:

Design, develop and verify automated DO-178B SL D software test capabilities. The automated test capability will be focused on high-level requirements-based testing.

• Re-establish WAAS Operational Software DO-178B SL D and/or SL B Safety Baseline:

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.”

Modify DO-178B SL D software, operating system or compiler and will need to re-certify all SL D operation software, including tools used for operational baseline development, integration, and testing.

Modify WAAS DO-178B SL B software and will need to recertify the SL B codebase, including tools used for operational baseline development, integration and testing upon any such modification.

• Transition of WAAS Telecommunications Network (TCN) from existing Time Division Multiplex (TDM) based circuits to GFE Cloud-based communications networks:

Design, develop, and test modifications to the WAAS TCN that migrate from existing prime-line circuits to an FAA-provided cloud-based network. Such modifications would require the Contractor to develop transition strategies that continue to support WAAS performance and information security requirements.

• Update WAAS Security Architecture:

Implement information security requirements in accordance with the WAAS Performance Specification (FAA-E-2892e). The Contractor may be required to implement information security updates using a combination of commercially available tools and contractor-developed functionality.

• Conduct Technical Refresh of WAAS equipment:

Refresh WAAS equipment, including necessary modifications to software and hardware baselines and logistics requirements.

• Design and implementation of WAAS Dual Frequency Operation (DFO) Limited Operational Capability (LOC), Initial Operational Capability (IOC) and Full Operational Capability (FOC) service:

Design, develop and test WAAS Dual Frequency Operations LOC, IOC and FOC capabilities in accordance with the WAAS performance specification and Task Order requirements. The Contractor would need to 1) develop a separate software and hardware baseline; 2) modify and recertify DO-178B SL B and SL D operational software and tools; and, 3) construct additional hardware components.

• Modify the existing WAAS L1 service to process L1 and L5 GPS signals:

Design, develop and test WAAS algorithms and software to change from the use of GPS L1 C/A and L2 P(Y) for GPS ionospheric corrections to the use of GPS L1 C/A and L5 signals.

• Implement SBAS Resiliency:

Design, develop, and test WAAS modifications required to support the characterization of the current and projected operational threats to achieve resiliency, particularly in the cybersecurity domain.

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.”

• Implement SBAS Authentication:

Design, develop and test WAAS modifications required to support future SBAS authentication requirements as required per ICAO SARPS updates.

• Sustain the WAAS Geostationary Earth Orbit (GEO) satellite constellation by integrating FAA-provided WAAS GEO satellite payloads and supporting ground infrastructure:

Design, develop, and test WAAS hardware and software modifications required to integrate new WAAS Geostationary Satellite service leases into the WAAS and support removal of existing Geostationary Satellite service leases.

• Provide Contractor Depot Logistics Support (CDLS) in support of WAAS lifecycle maintenance:

Stand-up and support a contractor logistics facility that can support receipt and shipment of WAAS equipment and support test, repair and replacement of failed WAAS units.

• Conduct studies, analysis, architectural development, prototyping and development in support of Technology Opportunities for WAAS:

Perform analyses, develop WAAS architectural changes, develop prototypes, and conduct design and development activities. Such efforts may be in response to changes in GPS schedules and/or capabilities, modifications to driving program specifications or industry standards (such as DO-229 WAAS Minimum Operational Performance Standards (MOPS), Dual-Frequency Multi-Constellation MOPS, ICAO SARPS, etc.), changes in FAA and/or US security postures, the introduction of additional GPS and /or SBAS capabilities, etc., during the period of performance of this contract and task orders.

• Transition Planning:

Develop a transition plan for the startup of Contract work activities, which may include the transition of GFE development, integration and test environments for the WAAS. During this period, the Contractor will initiate and accept the transfer of relevant information, data, and equipment from the previous Contractor. The transition may also include the transition of spare equipment and component testing equipment and setups.

(Remainder of the Page Left Intentionally Blank)

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.”

APPENDIX A – DEFINITIONS

See FAA-E-2892e, Appendix A for a complete set of WAAS Definitions. Definitions specific to this Statement of Work are contained below.

Anomaly: An unexpected or unplanned event that is outside the normal, expected operation parameters. The event can be hardware, software or system related including both the operational system and shadow and development environments. Anomalies include performance degradation, faults and reported errors.

DFO Phase 4B: The follow-on segment to WAAS Phase 4A (originally DFO Segment 1) which included upgrades to the WAAS infrastructure to enable reception and collection of the L5 signal with the WAAS reference station network. WAAS DFO Phase 4B will fully implement the new Dual Frequency (DF) User Service.

DF Limited Operational Capability (LOC): The DF Limited Operational Capability (DF LOC) introduces Dual Frequency capabilities to the WAAS Program. DF LOC completion will result in an over-the-air DF SARPs and DF MOPS-compliant L5 Signal in Space that is for non-aviation use only.

DF Initial Operational Capability (IOC): The DF Initial Operational Capability (DF IOC) introduces Dual Frequency capabilities to the NAS. DF IOC is achieved upon DF Signal in Space commissioning and does not meet all WAAS DF Service performance requirements.

DF Full Operational Capability (FOC): The DF Full Operational Capability (DF FOC) is dependent on the achievement of the GPS III FOC capability. DF FOC is achieved upon satisfaction of all WAAS DF Service performance requirements.

Minimum Operational Performance Standards (MOPS): MOPS are technical aviation navigation aid guidance documents. MOPS are developed by RTCA, Inc. in conjunction with Government and Industry and become the basis for WAAS avionics certification.

Release: Refers to the collection of operational and non-operational hardware, software, documentation and maintenance procedures that encompass the WAAS operational baseline.

Software Level B Safety Baseline: DO-178B or similar FAA approved means of compliance Certification of all Software allocated to SL B

Software Level D Safety Baseline: DO-178B or similar FAA approved means of compliance Certification of all Software allocated to SL D

Shadow System: Test equipment compliment for testing of operational WAAS hardware and software system changes prior to fielding.

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 Contracting Officer.”

WAAS Non-Operational Software: Any software not meeting the criteria of operational software. Software that is used to test, validate, or analyze the performance of WAAS operational software or WAAS itself.

WAAS Operational Software: Software that executes on any WAAS operational hardware or that impacts any operational functionality of the WAAS. Any tool or tool component that is included as part of the operational software build or is used to generate any software included in any operational software build.

END OF SECTION C

PART I – SECTION G CONTRACT ADMINISTRATION DATA

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 Contracting Officer.”

G.1 CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (JULY 2019)

(AMS 3.1-1)

This screening information request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make the full text available, or offerors and contractors may obtain the full text via Internet at: https://fast.faa.gov/contractclauses.cfm.

(End of clause)

AMS Clause Number Title and Date 3.10.1-22 Contracting Officer's Representative (April 2012)

G.2 BACKGROUND

This section provides roles, responsibilities, and contract administration requirements for the DFO Segment 2 IDIQ Contract and each task order placed under this IDIQ contract.

Additional clauses and other requirements regarding contract administration may be designated at the Delivery/Task Order level.

G.3 ROLES AND RESPONSIBILITIES OF GOVERNMENT KEY PERSONNEL

This section describes the roles and responsibilities of Government personnel. Additional Key Personnel and Key Personnel Roles and Responsibilities may be defined in individual task orders.

G.3.1 CONTRACTING OFFICER

(a) The Contracting Officer is the only individual who can legally commit or obligate the

Government for the expenditure of public funds. The technical administration of this DFO Contract must not be construed to authorize the revision of the terms and conditions of the Contract. Any such revision must be authorized in writing by the Contracting Officer. The CO will designate the COR via a Designation Letter, which will specify the COR’s extent of authority.

(b) The Contracting Officer may designate, in writing, representatives to perform functions required to administer this contract, however, any implied or expressed actions taken by those representatives must be within the limits cited within the Contracting Officer’s written designations. If any individual alleges to be a representative of the Contracting Officer and the Contractor has not received a copy of the document designating that representative, the Contractor must refrain from acting upon the representative’s requirements and immediately contact the Contracting Officer to obtain a copy of the document designating that individual as a representative of the Contracting Officer.

(c) In the event the Contractor effects any change at the direction of any person other than the Contracting Officer, the change thereof will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof.

https://fast.faa.gov/contractclauses.cfm

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.”

(d) The Contractor must immediately notify the Contracting Officer for clarification when a question arises regarding the authority of any person to act for the Contracting Officer under the contract. The Contractor must submit request for modification(s) of this contract to the Contracting Officer, with a copy of the request to any appointed

COR/TOR.

(e) The designated Contracting Officer for the DFO IDIQ Contract is:

Name: Iann T. Washington

Address: Federal Aviation Administration

ATTN: AAQ-340

800 Independence Avenue, S.W.

Washington, D.C. 20591 Office Email: iann.washington@faa.gov

Task Orders may or may not have a Contracting Officer different from the IDIQ CO.

G.3.2 CONTRACTING OFFICER’S REPRESENTATIVE (COR) AND TASK ORDER

REPRESENTATIVE (TOR)

(a) The Contracting Officer may designate other Government personnel (known as the

Contracting Officer’s Representative) to act as his or her authorized representative for contract administration functions which do not involve changes to the scope, price, schedule, or terms and conditions of the contract. The designation will be in writing, signed by the Contracting Officer, and will set forth the authorities and limitations of the representative(s) under the contract. Such designation will not contain authority to sign contractual documents, order contract changes, modify contract terms, or create any commitment or liability on the part of the Government different from that set forth in the contract.

b) The DFO Contract COR is responsible for the technical administration of the DFO Contract and will be the technical liaison with the Contractor. The DFO Contract COR IS NOT authorized to change the scope of work or specifications as stated in the DFO Contract or any contract Task Order, to make any commitments or otherwise obligate the Government or authorize any changes which affect the task order price, delivery schedule, period of performance or other terms or conditions. The COR will be designated by CO via a Designation Letter, which will specify the COR’s extent of authority.

c) The Task Order Contracting Officer will also designate a Task Order Representative (TOR) for each awarded Task Order, who may be the same individual(s) who serves as the DFO Contract COR. The TOR will be designated by the task order CO via a Designation Letter, which will specify the extent of the TOR’s authority. The TOR is responsible for the day-to-day administration and oversight of the Task Order. The TOR will represent the CO and COR in the administration of technical details within the scope of the Task Order. The TOR is also responsible for the final inspection and acceptance of all Task Order deliverables and mailto:iann.washington@faa.gov

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.”

reports, and other responsibilities as may be specified. The TOR is not otherwise authorized to make any representations or commitments of any kind on behalf of the CO or the Government. The TOR does not have authority to alter the Contractor’s obligations or to change the Task Order scope of work, specifications, price, terms, or conditions. If, as a result of technical discussions, it is desirable to modify the Task Order scope of work, obligations, or the specification, changes will be issued through the issuance of a task order modification. .

d) The Contractor must immediately contact the IDIQ or Task Order Contracting Officer if there is any question regarding the authority of an individual to act on behalf of the Contracting Officer under this contract.

e) The COR is responsible for monitoring progress and overall technical management of the work hereunder and must be contacted regarding questions or problems of a technical nature. In no event, however, will any understanding or agreement, modification, change order, or other matter deviating from the terms of the contract between the Contractor and any person other than the Contracting Officer be effective or binding upon the Government, unless a contract modification or letter of direction is executed by the Contracting Officer prior to completion of this contract.

f) On all matters that pertain to contract terms, the Contractor must contact the IDIQ or Task

Order Contracting Officer. When, in the opinion of the Contractor, the COR requests effort outside the existing scope of the contract, the Contractor will promptly notify the IDIQ or Task Order Contracting Officer. The Contractor must not take any action under such a request, unless and until the Contracting Officer has issued a letter of direction or a contract modification.

g) The designated Contracting Officer Representative for the DFO IDIQ Contract is:

Name: TBD Address: Federal Aviation Administration

ATTN: TBD

800 Independence Avenue, S.W.

Washington, D.C. 20591 Office Email: TBD

G.3.3 OFFICER’S QUALITY RELIABILITY OFFICER (QRO) OR ALTERNATE

The FAA will designate a QRO/Alternate with the authority to perform surveillance of the contract work and conduct such inspections as are necessary to assure compliance with the contract terms and conditions and accept or reject the required material, equipment, or services in accordance with the terms of the contract. The QRO or Alternate does not have authority to change the contract price, schedule, quantities, or any terms and conditions of the contract.

G.4 CONTRACTING OFFICER SUPPORT PERSONNEL

(a) The Contracting Officer may designate certain individuals to assist in the administration of this Contract and Delivery/Task Orders.

(b) In no event will the designee(s) be empowered to change the contract scope of work, the

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.”

price, or the delivery schedule.

(c) The Contracting Officer must immediately be contacted for clarification if a question arises regarding the authority of any person to act for the Contracting Officer under this Contract and Delivery/Task Orders.

G.5 CORRESPONDENCE PROCEDURES

To promote timely and effective contract administration, correspondence submitted under this contract (except invoices and deliverable items) must be subject to the following procedures:

(a) All correspondence must contain a subject line commencing with the contract number as follows:

SUBJECT: Contract Number (TBD); TASK ORDER NUMBER; TOPIC: (Insert Brief Topic of Correspondence) & Unique Document Number

Technical Correspondence of a routine nature: must be addressed to the designated COR with an information copy of the correspondence to the Contracting Officer.

(b) Other correspondence including technical correspondence where patent or technical data issues (if any) are involved, and correspondence which proposes or otherwise involves waivers, deviations, or modifications to the contract requirements, terms or conditions, etc., must be addressed to the Contracting Officer, with an information copy of the correspondence to the

COR.

(c) The Contractor must use discretion in the use of "express" or "overnight" mail. These premium services should be used sparingly and in situations where the regular U.S. mail system would not be adequate for the timely transfer of technical or contract related documentation. Use of electronic mail is encouraged where appropriate.

G.6 ELECTRONIC COMMUNICATIONS

The Contractor must assure an electronic means for communicating with FAA personnel. The Contractor must ensure that the communications are compatible with the FAA’s electronic mail system, which is currently Microsoft Outlook. The Contractor must also ensure that the Contractor’s electronic mail has the capability to send and receive attachments.

All contract reports and deliverables, including invoices, must be provided in electronic format with all linkages and interdependencies.

G.7 TECHNICAL DIRECTION

(a) Performance of the work under this contract will be subject to the technical direction of the

COR identified in G.3. The term technical direction is defined to include, without limitation, the following:

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.”

(1) Directions to the Contractor which redirect the contract effort, shift work emphasis between work areas or tasks, require pursuit of certain lines of inquiry, fill in details or otherwise serve to accomplish the contractual Statement of Work provided that there is no cost or schedule impact or change in the contract requirement consistent with Section C;

(2) Provision of written information to the Contractor which assists in the interpretation of drawings, specifications, or technical portions of the work description; and

(3) Review and where required by the contract, approve technical reports, drawings, specifications, and technical information to be delivered by the Contractor to the Government under the contract.

(b) Technical direction must be issued in writing by the COR and must be within the scope of Section C, Statement of Work. The COR does not have the authority to and may not issue any technical direction which:

(1) Constitutes an assignment of additional work outside the Statement of Work;

(2) Constitutes a change as defined in the FAA Clauses 3.10.1-12 Changes—Fixed Price, 3.10.1-14 Changes – Time and Materials or Labor Hours, and 3.10.1-13 Changes - - Cost Reimbursement;

(3) In any manner causes an increase or decrease in the total estimated contract cost, the fixed fee (if any), or the time required for contract performance;

(4) Changes any of the expressed terms, conditions, or specifications of the contract; or

(5) Interferes with the Contractor's right to perform the terms and conditions of the contract.

G.8 ACCOUNTING AND APPROPRIATION DATA

Accounting and appropriation data for obligations under this contract will be set forth in individual Delivery/Task Orders.

G.9 PREPARATION OF INVOICES

G.9.1 General

(a) An Invoice must be prepared and submitted for payments under this contract, unless otherwise specified in the individual Delivery/Task Order.

(b) Per AMS, a Proper Invoice includes the following:

(1) For FAA to make payment under a contract, a proper invoice must be submitted to FAA by the contractor. If the invoice does not meet the definition of a proper invoice per section (2) below, it must be rejected within seven (7) days of receipt.

(2) A proper invoice contains the following:

(a) Name and address of contractor;

(b) Invoice date;

(c) Contract number (to include applicable order numbers and Contract Line Item Numbers (CLINs);

(d) Description, quantity, unit of measure, unit price, and extended price of supplies delivered or services performed;

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.”

(e) Shipping and payment terms, to include, when applicable:

(i) Shipment number and date of shipment,

(ii) Bill of lading number and weight (for government bills of lading), and

(iii) Prompt payment discount terms.

(f) Contractor or bank address where electronic payment is to be sent;

(g) Name, title, phone number, and mailing address of person to be notified of a defective invoice;

(h) Other information required by the contract (i.e. certified payrolls, evidence of shipment, etc.); and

(i) Invoice number, account number, and/or any other identifying umber agreed under the contract.

G.9.2 Billing Instructions

(a) The Contractor must submit invoices no more often than monthly unless otherwise authorized, in writing, by the Contracting Officer. All invoices for payment under this contract must include the following information:

1. The Contract Number;

2. The Invoice Number and Date prepared;

3. The Contractor’s name, mailing address, and telephone number;

4. Delivery/Task Order period of performance in the invoice must match exactly the period of performance used in the Contractor’s Integrated Program Management Report

(IPMR);

5. Billing period covered by month, day, and year;

6. Dollar amount for the current billing period grouped and totaled by Task Order number and CLIN number; the Contractor must itemize individual labor by name, CLIN, labor category, labor rate, hours, and total cost;

7. Cumulative dollar amount for the contract grouped and totaled by Task Order number and CLIN number; the Contractor must itemize labor by individual name, CLIN, labor category, labor rate, hours, and extended cost; additionally, when applicable, the invoice must break out dollar amounts by subtask and type of funding as obligated on the task order by the FAA, e.g. F&E or Operations;

1. Supporting or backup documentation as follows:

a. Travel Expense Claims (Include receipts for lodging, rental car, airfare, and other expenses greater than $75);

b. Receipts for all invoiced purchases and ODCs greater than $75; and

c. Copies of the COR’s authorizations for each trip and ODC expense invoiced;

8. Certification and signature of an appropriate management official as follows:

“This is to certify that the services set forth herein were performed during the period stated, and that incurred costs billed were actually expended. “

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

Signature of Contractor’s Authorized Official Date Signer's name typed or printed Signer's Title

(b) The Federal Aviation Administration intends to make payment within 30 days of receipt of a properly prepared invoice submitted to the billing office below at either address or sent via email to 9-AMC-AMZ-FAA-APInvoices@faa.gov:

U.S. MAIL: FAA Accounts Payable Branch, AMZ-110

PO Box 25710 Oklahoma City, OK 73125

FEDEX: FAA Accounts Payable Branch, AMZ-110 6500 S MacArthur Blvd.

Oklahoma City, OK 73169

The Contractor must submit an original copy of all invoices to the above designated billing office not more than once monthly. All invoices must comply with the FAA Acquisition Management System (FAAAMS) Clause 3.3.1-17, Prompt Payment. The Contractor must provide simultaneously with the original, an electronic copy of each certified invoice to the Contracting Officer along with attachments to both the Contracting Officer and the Contracting Officer’s Representative in a format which will allow data manipulation.

The Contracting Officer will authorize payment in amounts determined to be allowable, allocable, and reasonable in accordance with the FAA AMS. The payment will be made pursuant to the “Payment by Electronic Funds Transfer - Central Contractor Registration” clause, AMS Clause 3.3.1-34, in Section I of this contract.

G.10 METHOD OF PAYMENT

Payments under this Contract will be made by wire transfer through the Treasury Financial Communications System.

The Contractor must forward the following information in writing to the paying office (see clause G.9) not later than 7 calendar days after receipt of notice of award.

(a) Full name (where practicable), title, phone number, and complete mailing address of responsible official(s) (i) to whom check payments are to be sent, and (ii) who may be contacted concerning the bank account information requested below.

(b) The following bank account information is required to accomplish wire transfers:

1. Name, address, and telegraphic abbreviation of the receiving financial institution.

mailto:9-AMC-AMZ-FAA-APInvoices@faa.gov

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.”

2. Receiving financial institution's 9-digit American Banker's Association (ABA) identifying number for routing transfer of funds. (Provide this number only if the receiving financial institution has access to the Federal Reserve Communications System).

3. Recipient's name and account number and the receiving financial institution to be credited with the funds.

4. If the receiving financial institution does not have access to the Federal Reserve Communications System, provide the name of the correspondent financial institution through which the receiving financial institution receives electronic funds transfer messages. If a correspondent financial institution is specified, also provide:

(c) Address and telegraphic abbreviation of the correspondent financial institution, and the correspondent financial institution's 9-digit ABA identifying number for routing transfer of funds.

G.11 TRAVEL

All Contractor travel must be authorized in a Task Order and specifically approved by the Contracting Officer or COR in writing, via e-mail, before commencing travel. The Contractor will be reimbursed for travel expenses in accordance with the Federal Travel Regulation, and the following:

(a) The contractor must use alternate airports when available and within a reasonable commuting distance if it will result in lower costs;

(b) The contractor must conduct a cost analysis prior to the start of travel to determine the overall most cost-effective means and then use the most cost-effective means; and

(c) The Contractor must, when possible, use discount hotel rates, marked CRC in the Federal Travel Directory, which the GSA publishes monthly. Questions on travel must be addressed to the CO.

G.12 OTHER DIRECT COST (ODC) REIMBURSEMENT

(a) Any ODC must be preapproved by the Contracting Officer or COR, via e-mail, and is subject to the limits defined in the associated TO. If preapproved, the contractor will be reimbursed for allocable, allowable, and reasonable ODCs. All ODCs submitted for preapproval must be within the scope of the TO.

(b) The Contractor’s facility costs (including but not limited to office space, office equipment, utilities, office supplies, and office furniture) are not an allowable ODC expense.

(c) Cellular phone usage charges are not an allowable ODC expense unless required to perform time- critical duties and roles and preapproved by the Task Order Manager and either the Contracting Officer or COR.

(d) All ODC expenses must be consistent with the costs of comparable items or services.

(e) The Contractor must submit a copy of the Contracting Officer’s or COR’s authorization for the expense and a copy of the receipt when invoicing an ODC expense.

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.”

All materials required for performance under the TOs issued pursuant to this contract that are not Government-furnished, must be furnished by the Contractor. When requisitioning procedures reveal that required materials are not available from Government supply sources, the Contractor must identify them in each TO proposal. Ownership of supplies acquired by the Contractor with Government funds, for performance of this contract, must vest with the Government. The Contractor must include a detailed description of all proposed materials in individual TO proposals. Materials are defined in the clause at AMS 3.3.1-5 Payments under Time-and- Materials and Labor-Hour Contracts (July 2018).

G.13 ORDERING PROCEDURES

G.13.1 General Information All Delivery/Task Orders under the DFO Segment 2 IDIQ Contract must:

a. Be solicited and awarded by an authorized, warranted CO within the FAA;

b. Be within the scope of Section C and all other terms and conditions of the DFO Segment

2 IDIQ contract;

c. Identify the Labor Categories that will perform the Delivery/Task Order work;

d. Comply with the ordering procedures in AMS, Ordering, and other applicable agency specific regulatory supplements.

All costs associated with the preparation, presentation, and discussion of the Contractor’s proposal in response to a task order solicitation will be at the Contractor’s sole and exclusive expense the Government’s expense, as a direct charge to this contract under Task Order 001.

These costs will be subject to a price ceiling as identified by the Task Order CO at the time of request for proposal.