Attachment C-1 Statement of Work_20MAR25_FINAL.pdf

Statement of Work AJM–2 Second Level Engineering Support Services i

Table of Contents

1. INTRODUCTION

2. REFERENCE DOCUMENTS

3. SCOPE

4. CONTRACT REQUIREMENTS

4.1 Reports and Reviews

4.1.1 Post-Award Conference

4.2.1 Contract Management Database

4.2.2 Task Order Status Review Meeting

4.2.3 Program Management Review (PMR)

4.2.4 Task Order Reports

4.2.4.1 Monthly Status Report

4.2.4.2 Monthly Financial Report

4.2.4.3 Manpower Report

5. TECHNICAL REQUIREMENTS

5.1 Maintenance Support

5.1.1 Technical Data Documentation

5.1.2 Support Equipment/Software

5.1.3 Maintenance Technical Handbook Support

5.2 System Support Directive Support

5.2.1 System Support Directives

5.2.2 SSD Analysis

5.2.3 SSD Design and Development

5.2.4 SSD Testing

5.2.5 SSD Documentation and Configuration

5.2.6 SSD Kits

5.3 Engineering Support

5.3.1 Engineering Studies

5.3.2 Optimization and Restoration of NAS Systems

5.3.3 Engineering Management

5.4 Documentation and Production Support

5.4.1 Document/Data Analysis and Review

ii

5.4.2 Installation Plans

5.4.3 Life-Cycle Logistic Support and Operation Documentation

5.5 Configuration Management

5.6 Technical Meetings, Reviews, Demonstrations

5.6.1 Design Reviews – Preliminary and Critical

5.6.2 Production Readiness Review (PRR)

5.7 System Production

5.8 Test Support

5.8.1 General Test Requirements

5.8.2 Test Reviews, Readiness and Post-Test

5.8.3 Test Documentation

5.8.3.1 Test Plan

5.8.3.2 Requirements Verification Traceability Matrix

5.8.3.3 Test Records and Reports

5.8.4 Quality Assurance (QA)

5.8.4.1 Reliability Verification

5.8.4.2 Maintainability Verification

5.8.4.3 Keysite Testing

5.9 Training

5.9.1 System Training

5.9.1.1 System Training Plan

5.9.1.2 FAA Academy Training

5.10 Asset Management and Logistics Support

5.11 Business Operations Support

5.12 Security

5.12.1 Information System Security Support

5.12.2 Data Breaches and Spills

5.12.3 Federal Cyber Security Policy and Regulation Monitoring

6. DELIVERABLES

6.1 Inspection and Acceptance

6.2 General Acceptance Criteria

7. PLACE OF PERFORMANCE

8. WORK HOURS AND WORK SCHEDULE

iii

8.1 Regular Work Schedule

8.2 Alternate Work Schedule

8.3 Excess Hours/Extended Work Week

8.4 Telework

. TRAVEL

9.1 Travel Request Pre-Authorization Requirements

10. OTHER DIRECT COSTS

10.1 ODC Approval Request Requirements

11. MINIMUM LABOR CATEGORY QUALIFICATIONS

12. PHASE IN AND PHASE OUT TRANSITIONS

12.1 Phase-In Transition Plan

12.1.1 On-boarding of Personnel

12.1.2 Phase-In Inventory

12.2 Phase-Out Transition Plan

12.2.1 Off-boarding of Personnel

12.2.2 Phase-Out Inventory

12.3 Phase-Out Execution

SOW Appendix A. List of Acronyms

SOW Appendix B. List of Current Systems

1. INTRODUCTION

The Air Traffic Systems (ATS), AJM-2, directorate is characterized by the systems that deliver to all segments of the National Airspace System (NAS). ATS is responsible for maintaining systems that support tactical operations today, as well as executing automation tools that are foundational to the Next Generation Air Transportation System (NextGen); the next generation of Air Traffic Control (ATC) services. ATS oversees these systems from initial concept through design and development and manages the deployment and sustainment of the systems. This Second Level Engineering (SLE) support effort is an ATS directorate requirement that will provide SLE support to both the Terminal Second Level Engineering Group (AJM-24) and the EnRoute & Oceanic Second Level Engineering Group (AJM-25).

The NAS contains systems that range from sunset phase to state-of-the-art Hardware (HW) and Software (SW). Older systems face problems that require unique engineering solutions because spare parts may be obsolete, unattainable, or depleted. Some systems contain SW developed with unique and specific languages, compilers, and support platforms no longer used or supported. The Federal Aviation Administration (FAA) needs supportable, functionally identical replacement items designed, developed, tested, acquired, and implemented to sustain NAS functionality and operations.

Other NAS systems include advanced technology and state-of-the-art HW and SW. These systems require functionally interchangeable HW, SW, and support replacements that cause minimal impact to performance standards and minimize expensive requalification testing. Analysis of field facilities problem reports and NAS Configuration Control Decisions (CCD) for casefiles identify specific FAA requirements and approve system implementation.

The FAA continues to modernize and improve NAS performance and support to meet the FAA’s short and long-term goals by executing the following:

a. Define support requirements,

b. Monitor development,

c. Perform system testing,

d. Receive program library baselines,

e. Support NAS integration/testing and commissioning, and

f. Assume level-2 maintenance responsibility.

The NAS is a network of controlled and uncontrolled airspace, both domestic and oceanic. The NAS includes the following systems and subsystems:

a. Radar target, and weather detection,

b. Flight data and supporting processing systems,

c. Air Traffic (AT) processing and display systems within the Enroute and Terminal Oceanic ATC environment,

d. Communications systems, flight plan data information systems, and

e. NAS maintenance and support systems.

The NAS is identified via the FAA’s Configuration Management Automation (CMA) website. FAA Order 1100.157, National Systems Engineering Divisions Maintenance Program Procedures, Operational Support (AOS), requires Operations Support Services to perform SLE upon many NAS systems/subsystems.

NAS field facilities personnel provide first-level NAS maintenance functions including, but not limited to1:

a. Making on-site repairs,

b. Conducting Preventive Maintenance (PM),

c. Certifying systems, and

d. Generating Program Trouble Reports (PTR) and casefiles.

NAS SLE includes, but is not limited to:

a. Assisting first-level personnel with remote or onsite restoration support,

b. Developing, testing, and producing engineering solutions in response to NAS PTRs and approved casefiles,

c. Conducting engineering studies and providing alternative analysis solutions,

d. Configuring and documenting maintenance, release, and control,

e. Assuring viability of new systems before the FAA deploys them into the NAS,

f. Safety management support,

g. Information System Security (ISS) support,

h. Integrated Capability Maturity Model (iCMM) support,

i. Process improvement support,

j. Test and Evaluation (T&E) Gold Standard support,

k. Air Traffic Organization (ATO) best practices support,

l. Program Management Office (PMO) support, and

m. Administrative system support.

1 High-level information on first-level engineering is provided for informational purposes only and are outside the scope of this effort.

2. REFERENCE DOCUMENTS

The following reference documents form a part of this SOW and are applicable to this Contract.

Individual Task Orders (TO) may specify additional reference documents that apply to specific TOs. The latest versions of these reference documents are applicable to performance under this Contract.

FAA Orders Number Title 1000.36x FAA Writing Standards 1100.157x

National Systems Engineering Divisions Maintenance Program Procedures, Operational Support (AOS)

1320.1x FAA Directives Management Job Order (JO) 1320.58x

Instructions for Writing Notices, Maintenance Technical Handbooks, and System Support Directives

1370.121x FAA Information Security and Privacy: Policy FAA 1800.66x Configuration Management Policy FAA 6000.15x General Maintenance Handbook for NAS Facilities including Change 1 Note: x denotes the current version of the document.

FAA Documents Number Title NAS System Engineering Manual

Commercial Standards

ANSI/EIA 748x Earned Value Management Systems ASTM D3951-18 Standard Practices for Commercial Packaging CISSP Certified Information Systems Security Professional CIS Center for Internet Security Benchmarks iCMM Integrated Capability Maturity Model T&E Gold Standard Test and Evaluation Gold Standard

Government Documents

MIL-HDBK-217x Reliability Prediction of Electronic Equipment

MIL-HDBK-470x Designing and Developing Maintainable Products and Systems

MIL-HDBK-781x Reliability Test Methods, Plans, and Environments for Engineering, Development Qualification, and Production

MIL-STD-1472 Human Engineering Design Criteria for Military Systems, Equipment, and Facilities

Government Documents Number Title OMB Circular A-11x Preparation, Submission, and Execution of the Budget

OMB Circular A-130x Managing Resources as a Strategic Resource

Federal Policies & Standards

FAA-STD-025x Standard, Preparation of Interface Documentation FISMA Federal Information Security Modernization Act National Institute of Standards & Technology (NIST) 800 Special

Publications (SP) NIST Federal Information Processing Standards (FIPS) DISA – STIG Defense Information Systems Agency Security Technical Implementation

Guides Authorization to Operate (ATO) ISS Requirements Matrix (updated annually) FAA Acquisition Management System (AMS) FAA National Airspace System (NAS) Capital Investment Plan FAA Continuity of Operations

3. SCOPE

AJM-2 requires SLE support as defined throughout this Statement of Work (SOW) to the systems and services defined below.

a. Enroute and Oceanic,

b. Terminal,

c. Communication, Flight Service, and Weather Engineering,

d. National Airway Systems Engineering,

e. ISS,

f. Administrative Computer Systems, and

g. Business Operations.

This list is not all-inclusive and, when in the best interest of the FAA, may change to allow for provision of required SLE.

Note: See Attachment B, List of Current Systems, for a list of current NAS systems receiving SLE support.

4. CONTRACT REQUIREMENTS

The Contractor must provide all necessary qualified personnel, services, tools, and materials to satisfy the requirements defined in this section.

4.1 Reports and Reviews

4.1.1 Post-Award Conference

The Contractor must participate in a Post-Award Conference to be held at a mutually agreeable date, time and location (in-person, virtual, hybrid), within ten (10) days2 from Contract award.

The purpose of the Post-Award Conference is to aid both FAA and Contractor personnel to:

1. Achieve a clear and mutual understanding of all contract, management, and technical requirements.

2. To identify and resolve potential problems.

The Contractor must attend and deliver the following within five (5) days after the Post-Award Conference to document, at a minimum, the meeting minutes and action items:

• Post-Award Conference Meeting Report

4.2.1 Contract Management Database

The Contractor must utilize the Government-provided Contract Management Database as a repository for the following information:

2 Reference to days in this SOW means business days unless specified otherwise.

a. Contract Number, Task Order Number and Task Order Name;

b. Contract and Task Order ceiling levels;

c. Expenditure levels against contract and TO ceiling;

d. Funded levels by TO and project level, as applicable;

e. Labor categories and number of resources;

f. Labor hours;

g. Travel and ODC requests;

h. EWW and AWS;

i. Reports and other records, as needed;

j. Other pertinent information.

The Contracting Officer Representative (COR)/Task Order Contracting Officer Representative (TOCOR) may request the Contractor to implement functional improvements to the Contract Management Database. The Contractor must maintain a backup that complies with the FAA Disaster Recovery Act

The Contractor must deliver the following within (30) days after start of contract:

• Contract Management Database Report

4.2.2 Task Order Status Review Meeting

The FAA may identify requirements within a TO for periodic status reviews. The FAA and the Contractor may see the need for periodic Status Reviews regarding an individual TO or a group of TOs within a system segment. The Contractor must follow guidelines for reviews and meetings, document its compliance and problems, and satisfy the informational requirements.

4.2.3 Program Management Review (PMR)

The Contractor must present a PMR quarterly. The PMR must include, at a minimum:

• Current organizational charts of Contractor support,

• List of Contractor personnel and labor categories,

• Status of Open Vacancies,

• Overall Contract status,

• Funding analysis/expenditure report at the Contract and TO level,

• Significant performance variances,

• Non-compliance and corresponding corrective actions,

• Expenditures and progress, and

• Other items the FAA or Contractor may identify.

The Contractor must submit a DRAFT version of the PMR presentation to the COR and Contracting Officer (CO) ten (10) days before the PMR. The CO and COR may provide comments no later than two (2) days before the PMR. The Contractor must address all comments before the PMR presentation moves from DRAFT version to FINAL version.

4.2.4 Task Order Reports

4.2.4.1 Monthly Status Report

The Contractor must provide a Monthly Status Report (MSR), for each active TO that at a minimum contains the following:

a. Travel completed in the current reporting period and any travel planned for the subsequent period.

b. Status of all efforts performed during the reporting period to include significant accomplishments during the reporting period, the general state of the program schedules, identified risks and mitigation strategies.

c. Identification of technical and schedule performance, activities, submittals, and events during the reporting period, including the identification of Other Direct Cost (ODC) items and travel.

The Contractor must clearly mark TOs that incurred no activity during the reporting period. T

d. Discussion of resource recruitment and retention and summarize any other pertinent staffing information that the FAA would need to be aware of as it pertains to the requirements of the

TO.

e. Include a projection of the 30-day outlook on technical accomplishment for each TO.

The MSR is due with submission of each TO invoice to both the CO and the COR. The Contractor must provide the MSR in Portable Document Format (PDF) or COR-approved equivalent format. The FAA will not process payment until receipt and review of the Monthly Status Report occurs.

4.2.4.2 Monthly Financial Report

The Contractor must provide a Monthly Financial Report (MFR) for each active TO, to the COR and CO with submission of the monthly TO invoice. The MFR must include the financial status of the current funding levels, current labor hours, and dollars expensed. The Contractor must report actual invoiced amounts incurred in such a way that it clearly aligns to the activities documented in the TO MSR. The MFR must include the following:

a. Project billed during the reporting period,

b. Hours billed to each Project

c. Estimated hours remaining by project,

d. Personnel who billed to each of the Project (itemized by Project and personnel),

e. Amount of funding invoiced during the reporting period and total cumulative funding invoiced,

f. Total funding remaining,

g. Projected date for 75% of funds spent, based upon future projections of known requirements,

h. Projected date for exhaustion of funds, at both TO and Project levels.

i. ODC and travel expenditures during the reporting period,

j. A monthly spreadsheet that details the hours and total dollars invoiced. This spreadsheet must provide detail to the resource, labor category, and project, and

k. A monthly financial projection for the next reporting period.

4.2.4.3 Manpower Report

The Contractor must provide a monthly Manpower Report under the Basic Contract. The Manpower Report must be provided in Microsoft Excel format and easily sorted to identify manpower resources at the IDIQ-level delineated by Task Order. This report furnishes a list of detailed information for all personnel supporting all tasks. The Manpower Report is due no later than the 15th of each calendar month. The information required is as follows:

1. Employee Full Name (Last Name, First Name, Middle Initial)

2. Task Order(s) assigned (if more than one, include column for the percent of time allocation for each effort)

3. Task Order Labor Category/Position Name

4. Position Status (e.g. vacant, onboard, pending onboarding, dissociated)

5. Organizational Information

a. Company of employment

b. Prime/Subcontractor status

c. Organization supported at a Division level (e.g. AJM-2541)

d. Project(s) supporting

e. Work Location

f. Work Schedule (e.g. Monday through Friday, 9:00 am to 5:00 pm)

g. Approved telework status (e.g. approved-hybrid, approved-situational, pending, not allowed)

h. FAA Email

6. Clearance information (if applicable)

a. Clearance level

b. Background Investigation Status

7. Date Disassociated from Contract (applicable to contractor employees no longer supporting the Basic Contract)

8. Badge Information:

a. Badge number

b. Badge Expiration Date

c. Facility where badge was issued

d. Date Badge Returned to Government

9. Training completion dates including, but not limited to, the following:

a. Contractor Rules of Behavior

b. Cyber Security Awareness

c. Annual FAA Privacy Awareness

5. TECHNICAL REQUIREMENTS

In conducting the following activities in support of the FAA’s mission, the Contractor must follow the FAA’s SLE processes and practices to resolve NAS issues or implement new requirements. The following consists of general information and requirements that must be used by the Contractor. Specific clarification and quantification of technical requirements will be provided by the Task Order Statement of Work.

5.1 Maintenance Support

This section describes general maintenance support requirements of the FAA. The Contractor will assist the government in supporting and maintaining Commercial Off-the-Shelf (COTS), semi-customized, and customized products. Any software or hardware product obtained, modified, deployed and maintained in the execution of this SOW is in accordance with Orders, Notices, Standard Operating Policies, AMS Engineering and Management, AMS 3.5-13 Rights in Data—General (Oct 2014), and AMS 3.5-16 Rights in

Data—Special Works (Jan 2009). Individual TO SOWs may further define requirements pertaining to HW, SW, or both.

5.1.1 Technical Data Documentation

The FAA must be able to obtain, repair, service, and replace items for the lifecycle of programs supporting the NAS. Processing of Technical Data Documentation is in compliance 4.14 Data Standardization and Management Revised 7/2008 and FAA Order 1375.1 FAA Information and Data Management. Technical Data Documentation used by the Contractor in support of requirements in this SOW remains the property of the FAA. This includes, but not limited to:

a) Engineering drawings and associated information, which would provide the detail as necessary to fabricate the SLE hardware and software.

b) Electronic and mechanical drawings for manufacturing data packages.

c) Master/prototype patterns used in the production.

d) Firmware service data and media.

e) Hardware and software specifications.

f) Essential process and tool information used in the development and manufacture.

g) Automatic test hardware, software, and program firmware test package including adapters and documentation.

h) Manufacturing support data including identification of component manufacturers and part numbers.

i) Essential training data for the designated low-level repair activity personnel.

Any items (data, software, hardware, documentation) developed under this contract must become the property of the FAA.

5.1.2 Support Equipment/Software

The FAA will maintain SLE developed software and configuration adaptations during its lifetime.

Therefore, the FAA requires the Contractor to provide all items pertaining to hard/firm/soft-ware compilation, simulation/modeling, and mission analysis, and Test Systems that are developed and utilized. The Contractor must provide the support tools to satisfy that intent. The FAA prefers common commercially available support tools that operate on standard commercially available platforms. A two-step process must be used to satisfy this requirement:

1. The Contractor must identify all tools, tool version levels, and procedures that are necessary to develop and maintain each item developed in response to each TO. The Contractor must categorize each tool as either commonly available from broad distributorship, or as peculiar.

2. If there are peculiar support tools that are not standard off the shelf items, e.g., contractor in-house tools, that must be used in order for the FAA to maintain the item (e.g., to implement emulations, equipment replacements and/or protocols), then the Contractor must deliver all peculiar software, hardware and procedures in executable form and with the source code to the FAA as part of this contract.

5.1.3 Maintenance Technical Handbook Support

The Contractor must support the FAA in the development of MTHBs In Accordance With (IAW) applicable orders and processes. The Contractor must provide all necessary services to accomplish this task, including but not limited to:

• Technical writing,

• Typing/word processing,

• Technical illustration,

• Proofing, and

• Preparing camera-ready copy, electronic files, or other formats as required by the COR.

In addition, the Contractor must provide MTHB testing, delivery, and packaging support as needed.

Requirements for MTHB testing, delivery, and packaging support will be defined further within individual TO SOWs.

5.2 System Support Directive Support

The Contractor must follow the FAA’s SLE processes and practices in completing tasks defined within this SOW. System Support Directives (SSD) and Maintenance Technical Handbooks (MTHB) are the governing documents defined in applicable FAA Orders, which describe the SW/HW development, delivery, and distribution as well as equipment preventative maintenance and certification. The Contractor must use the methodology contained within the SSD and MTHB when performing the following tasks.

5.2.1 System Support Directives

The Contractor must support FAA-issued SSDs to system modifications, safety modifications, technical data, and documentation releases for a system or systems. System modifications may include SW, HW, FW, or COTS items.

Applicable FAA Orders in Section 2 define SSDs. SSDs describe the HW/SW development, delivery, and distribution as well as the equipment program management and certification. The current SSD components include:

• System Support Modification (SSM)

• System Documentation Release (SDR)

• System Technical Release (STR)

The Contractor must ensure SSD modification does not degrade any component or their operations in implementation. The Contractor must notify the FAA of any suspected impact or risk when identified.

5.2.2 SSD Analysis

The Contractor must provide analysis of the affected areas and identify and propose corrective actions.

The Contractor must conduct a formal design review to demonstrate that corrective actions will not introduce additional problems. When the FAA or Contractor cannot replicate the problem, the Contractor must provide further analysis to support their conclusion to identify the root cause of the problem.

The Contractor must define and identify any changes and impacts during the engineering analysis. The Contractor must ensure that SSD modifications do not degrade any component or their operations in implementation. The Contractor must notify the FAA of any suspected impact or risk when identified.

The Contractor must provide resources to accomplish the analysis, need/change request, requirements packaging, design, development, production testing, system testing, documentation, key site testing, delivery and installation of modifications to NAS systems.

5.2.3 SSD Design and Development

The Contractor must minimize changes required to implement system modification(s) provided in the SSD. The Contractor must design, develop, and implement the modification with minimal changes to HW and the related SW programs.

The FAA may require the Contractor to design, develop, and fabricate prototypes for early evaluation prior to final design. These prototypes may include, but are not limited to, printed circuit boards, HW components, and SW components. The FAA will use prototypes to validate whether proposed solutions will work prior to implementing it into the system in a final design.

5.2.4 SSD Testing

The Contractor must verify SSDs via lab testing for procedure accuracy; any necessary changes will be redlined. Upon successful lab testing/verification, the SSD will be considered ready for delivery by the FAA.

The FAA may require full system testing in addition to modification testing. The FAA may require the Contractor to update system test procedures, as the SSD may create new, or void old, test cases. In each case, the Contractor must change procedures accordingly (with FAA concurrence) to adapt to the SSD applied to the new or modified tests.

The Contractor must conduct and include its findings for Production, System, and Keysite testing as required in the SSD.

The Contractor must provide quality control to ensure they resolved the Change Vehicle (CV) and updated the documentation to reflect the resolution. The quality control must ensure that test products are verifiable, validated, and repeatable.

5.2.5 SSD Documentation and Configuration

The Contractor must assist the FAA with the following documentation and Configuration Management (CM) tasks following SLE practices and policies provided by the FAA:

a. The Contractor must record and track all assigned Change Vehicles (CV) and prepare discrepancy reports for all problems identified.

b. The Contractor must prepare all documentation and coordinate with the FAA COR as applicable through all stages of processing.

c. The Contractor must provide technical editing and proofreading for all documents delivered as part of the SOW.

d. The Contractor must provide for the typing and data entry of all text from draft documents, with subsequent delivery of updated documents.

e. The Contractor must provide, as needed, electronic and mechanical drawings using Computer Aided Design (CAD) SW (e.g., Autocad) for the production of manufacturing data packages.

f. The Contractor must follow the FAA process for the review and delivery of SSDs. Upon FAA COR approval of CV and assignment of SSD number, the Contractor must support the preparation of all SSD documentation per the FAA specifications. The following must be provided/updated as required in support of SSD preparation:

(1) Details of required HW/SW changes,

(2) Logic, schematics, diagrams, drawings, parts list, and flowcharts,

(3) Test procedures and personnel for verification of modification,

(4) Test report following completion of testing,

(5) Personnel for field installation of modification,

(6) Installation procedures, and

(7) NAS documentation, Page Control Charts (PCC).

The Contractor must follow and adhere to all relevant FAA SOPs pertaining to Documentation and Configuration Management.

5.2.6 SSD Kits

The Contractor must support the production of SSD kits. SSD kits are the physical elements (HW, FW, etc.) needed to change the form, fit, function, or performance of NAS equipment to meet a required change, upgrade, or reconfiguration.

5.3 Engineering Support

5.3.1 Engineering Studies

An Engineering Study is an assignment to investigate problems, collect information, develop prototypes/proof of concept, and/or provide recommendations to resolve existing problems. In support of the FAA mission, the Contractor must provide resources to complete engineering studies that will complete required analysis, alternatives, and provide a recommendation. The Contractor must follow the engineering study process provided by the SLE organization.

5.3.2 Optimization and Restoration of NAS Systems

The Contractor must provide engineering support for the restoration, integration, optimization, and maintenance of NAS systems. SLE provides 24/7 field restoration support for NAS systems that may require telephone support or travel to the facility. The FAA will provide authorization for all field support activities. The Contractor must use the following guidelines whenever a visit to a site is required.

a. The Contractor must participate in a pre-investigative meeting involving site/regional members to:

(1) Develop a plan of action,

(2) Define roles, and

(3) Develop a schedule.

b. Prior to departing the site, the Contractor must support the activity to:

(1) Debrief site personnel,

(2) Determine status of the facility, and

(3) Determine required follow-up actions.

c. The Contractor must prepare a comprehensive trip report of the activities performed during the trip, any risks identified, and any required follow up actions. The trip report is to be submitted to the COR within three (3) days after return.

5.3.3 Engineering Management

The Contractor must provide visibility into engineering processes through all stages and must provide relevant data as defined within each TO. Relevant data includes, but is not limited to, initial estimates, revised estimates, tracking logs and notes, etc.

The Contractor must document HW, SW, and FW designs developed for this Contract. The Contractor must ensure the design meets the technical and support requirements of the SOW and specifications, and for subsequent life-cycle maintenance of the product.

The documentation must include:

• Specifications,

• Diagrams,

• Drawings, charts, tables, and lists, which describe the parts, and

• Layouts, interfaces, and characteristics responsive to the specification, which are applicable to each phase of development, e.g., architectural, preliminary design or detail (critical) design.

The FW design documentation must include:

• Data flow diagrams,

• Data references,

• Inter-routine functional flow diagrams,

• Diagrammed or descriptively annotated structured code routine flow and function exhibits, and

• Source code for unique FW.

The Contractor must provide traceability documentation to show which elements of the product design respond to requirements of individual TO specification.

The Contractor must deliver supporting documentation, listings, and magnetic media for all designs developed under each TO.

5.4 Documentation and Production Support

The Contractor must provide documentation support for producing directives for the NAS, including HW, SW, technical data, and facility modifications. These include, but are not limited to, MTHB, SSM, SDR, and STR.

The Contractor must support developing, editing, and updating documents following the most recent versions of FAA guidelines, Order JO 1320.58, and FAA-STD-025.

The Contractor must support the assessment, development and implementation of processes and Standard Operating Procedures (SOP).

5.4.1 Document/Data Analysis and Review

The Contractor must conduct document/data analysis and review of NAS system documentation, SLE documentation, FAA documentation, and documentation associated with new NAS technologies.

The analysis and review must provide a detailed analysis of the approach, evidence supporting the validity of data used, analysis of the document’s discussions, and conclusions.

In addition, the Contractor may be required to accompany FAA personnel to design review meetings Technical Interchange Meetings (TIM) and in process reviews as a technical advisor.

The Contractor must provide a Data Analysis Review Report to the COR within five business days, detailing the results of data analysis acquired during the TIM.

5.4.2 Installation Plans

The Contractor must document the installation plan used at each of the facilities. The FAA may require the Contractor to perform site surveys to obtain or update the installation drawings, lists, and other details for each facility.

5.4.3 Life-Cycle Logistic Support and Operation Documentation The Contractor must provide support for the completion of FAA Life-Cycle Logistic Support and Operations documentation. FAA Life-Cycle Logistic Support includes design disclosure packages consisting of drawings, lists, tools, specifications, procedures, processes, test/support HW and/or SW, and training data and maintenance data.

5.5 Configuration Management

The Contractor must support SLE in performing CM tasks. CM activities must follow FAA Directives and CM policies per Order 1800.66. This includes support for general configuration and documentation management tasks related to CM.

The Contractor must provide configuration identification and controls for all developed and delivered items. The Contractor must deliver CM documentation to the FAA ten (10) days before each demonstration, test activity, event, audit, or final delivery or as defined within the applicable TO SOW.

5.6 Technical Meetings, Reviews, Demonstrations

The Contractor must participate in Technical Meetings, Reviews, and Demonstrations as delineated within individual TO SOWs.

The Contractor must provide a Meeting Agenda and take and provide Meeting Minutes to include action items. The Meeting Agenda must include specific schedule, location, attendees, and topics for the meeting. The Contractor must distribute the Meeting Agenda in accordance with specific TO SOW or at minimum 5 business days after the meeting.

The FAA COR will provide the Contractor with clarification requests and discrepancies three (3) days prior to the meeting to include in the Meeting Agenda or in accordance with specific TO SOW.

The Contractor must provide and schedule facilities and equipment for the Technical Meetings, Reviews, and Demonstrations. The FAA encourages virtual and hybrid options for meetings, when appropriate.

The Contractor must provide Meeting Minutes and Action Items in accordance with specific TO SOW or at minimum 5 business days after the meeting.

In the instances of formal milestone meetings, (e.g. Detailed Design Reviews), when the Contractor presents a design, the Contractor must receive authorization from the FAA COR.

Following the meeting, the Contractor must provide the FAA COR with a written report detailing the results of an analysis of the data acquired in the meeting.

5.6.1 Design Reviews – Preliminary and Critical

The Contractor must conduct Preliminary Design Reviews (PDR) and Critical Design Reviews (CDR).

a. The PDR serves to examine, discuss and concur regarding design, integration and test methods, and support concepts. In addition, the Contractor must demonstrate its capability to successfully produce the articles as part of the PDR.

b. The CDR serves as a vehicle to examine, discuss, and come to an agreement on the Contractor's final design, integration and test methods, and support concepts. In addition, the Contractor must demonstrate its capability to successfully produce the articles as part of the CDR.

Each review must focus on variances from the original submittal and clarifications.

5.6.2 Production Readiness Review (PRR)

The Contractor must support a PRR to demonstrate that all discrepancy items have been resolved and that the Contractor's designs, processes, facilities, equipment, tools, and personnel are prepared in a manner which ensures the accuracy and success of production and deliveries.

The Contractor must address the following production readiness factors in the PRR:

a. The Contractor successfully tested a production-like unit.

b. The Contractor followed CM practices.

c. The Full Scale Development (FSD) item that was installed and tested for FAA acceptance must be of identical configuration to all of the production phase articles.

d. The design-disclosure and support documentation accurately and completely reflect the products.

Rework and re-verification of the articles is acceptable providing that the resultant system is identical in production quality, and acceptable to the FAA.

The FAA COR must verify and approve the first production unit and a designated key-site system (as required) following the PRR.

5.7 System Production

The Contractor must produce and provide the system IAW:

a. The documentation developed and approved during the FSD phase.

b. The qualification testing performed during FSD phase.

c. The FAA COR approved corrective/improvement actions, which were necessary as a result of

FSD documentation submittals, reviews and meetings, and qualification testing.

The Contractor must conduct a PRR before the FAA COR authorizes production of the system. The FAA will determine if the design disclosure package and the production and delivery planning for each site is acceptable before the system production is authorized.

5.8 Test Support

5.8.1 General Test Requirements

The Contractor must perform the following tests and correlate them to specification requirements within the Requirements Verification Traceability Matrix (RVTM):

a. Factory tests.

b. Diagnostic and built in tests for both the existing NAS programs and for the tests developed for the developed item.

c. Throughput, capacity, full system (end-to-end), and stability tests.

d. Modes of operation tests. This including failure modes and manual and automatic reconfiguration.

e. Supportability tests such as program assembly, build, comparison, and diagnostic tests;

verification of skill levels produced by the training project and the documentation; verification of documentation versus product.

The Contractor must verify there is no degradation to existing NAS security and safety features, operational and support system performance, and that all functions perform as before the installation except for improved throughput and capacity.

5.8.2 Test Reviews, Readiness and Post-Test

Test Readiness Reviews must be held whenever the contractor conducts demonstrations or tests for the purposes of validating its concept, approach, design or fabrication. A Post-Test Review must be conducted following each test to discuss the test results, discrepancies, understandings and resolutions.

The Contractor must prepare a Test Report, which documents the determinations and recommendations of the meeting and includes the test records as required by the TO.

5.8.3 Test Documentation

5.8.3.1 Test Plan

The Contractor must support the FAA in preparing Test Plans for FAA COR approval, IAW appropriate standards for reliability test methods, plans and environments for engineering development, quality, and production. The Test Plans will define the methods, levels, tools, facilities, algorithms, and acceptance tolerance limits to show the Contractor met the requirements of the specification and prior sections in the TO. The Contractor must arrange the Test Plan IAW the Government.

5.8.3.2 Requirements Verification Traceability Matrix

The Contractor must prepare an RVTM. The RVTM must identify all the requirements within the specification and applicable referenced specification requirements. The Contractor must receive FAA concurrence the RVTM meets the specific requirement. The identified requirements will be correlated in the RVTM to responsive test cases within the Contractor's test approach.

The Contractor must prepare test descriptions, procedures, scripts, and test results log for conduct of each verification step.

5.8.3.3 Test Records and Reports

The Contractor must record the test results and prepare Test Reports for each test. The data must identify the level of success, full description of failure or deviation from planned results, corrective actions, and retest or other disposition results.

5.8.4 Quality Assurance (QA)

5.8.4.1 Reliability Verification

The Contractor must comply with the appropriate specifications for reliability test methods, plans, and environments for engineering development, quality and production, and reliability prediction of electronic equipment. Specific reliability verification requirements may be further delineated within individual TO SOW.

The Contractor must provide verification that the item meets the reliability requirements stated in the specification and meets supportability requirements. The FAA may require analysis, testing, or prior test results to verify reliability.

5.8.4.2 Maintainability Verification

The Contractor must comply with the appropriate specifications for designing and developing maintainable products and systems.

The Contractor must provide verification the item meets the maintainability and supportability requirements defined within the specification provided. This includes training, logistic support, and documentation. The FAA may require analysis, testing or prior test results, to verify maintainability.

5.8.4.3 Keysite Testing

Testing at keysite(s) must prove deployability of the item. The requirements of the performance, installation and test acceptance must be met prior to installation of the remaining sites. Keysite testing will be performed to demonstrate that the item meets all the requirements called for in the acceptance test plan and must verify that performance and installation requirements of the specification and statement of work have been satisfied.

5.9 Training

5.9.1 System Training

The Contractor must provide system training as required. The system training must provide students with sufficient knowledge to operate the system at a level of proficiency that will allow them to understand and use all of the system capabilities and features.

In addition to system training, the FAA may specify other specialized training that the Contractor will be required to provide within individual TO SOWs.

The training may consist of both classroom and hands-on training, as required. The FAA encourages virtual and hybrid options for courses. The parties will identify the size of the class, location of the class, and the number of classes.

The Contractor must provide System Training Course materials for each student. The student will retain the course materials at the end of the course. The FAA reserves the right to record the training provided to satisfy its future training requirements. The System Training Course Materials, in hard and soft copy, must become the property of the FAA, with reproduction rights, for future training requirements of the FAA.

5.9.1.1 System Training Plan

The Contractor must prepare a Training Plan for each System Training course provided that defines the training approach for the System Training. The System Training Plan must include example course outlines, which provides adequate visibility into course materials for the FAA to determine acceptability of the Contractor’s training approach. The course outline must include the curriculum and identify any supporting training course materials. The System Training Plan must be delivered in hard and soft copy, and must become the property of the FAA, with reproduction rights, for future training requirements of the FAA.

5.9.1.2 FAA Academy Training

The Contractor may be required to support and participate in FAA Academy training conferences. The Contractor must assist the FAA in preparing Academy training materials -in accordance with FAA Academy requirements and agreements. Any required FAA Academy Training Material requirements will be delineated within individual TO SOWs. The training must be delivered in hard and soft copy, and must become the property of the FAA, with reproduction rights, for future training requirements of the

FAA.

The FAA COR must approve all submitted materials before training may begin.

5.10 Asset Management and Logistics Support

The Contractor must provide support in the areas of asset management and logistic support.

The Contractor must assist the FAA in the acquisition, maintenance, tracking, transfer and disposal of government property, which includes property delegation assignments utilizing FAA provided software and databases. The Contractor must assist the FAA in validating database against assets by performing audits. The Contractor must be familiar with Microsoft products to maintain tracking of assets and generate reports.

The Contractor must provide recommendation and assist the FAA in developing internal control compliance programs for acquiring and provisioning of logistics products in accordance with applicable Orders, Notices and Standard Operating Procedures. If the recommendation is industry standard, an ISO reference or similar reference must be provided.

The Contractor must participate in planning for new data processing systems in terms of defining the nature of information required, organizational responsibilities, computer network requirements, and the nature of output desired from inventory management systems.

The Contractor must monitor the quality of input and output of automated inventory management systems and recommending system and programming changes to improve timeliness, accuracy, and utility of inventory information for users.

The Contractor must identify, catalog, and maintain inventory. The Contractor must coordinate with the Asset Management team in the disposal of items of material.

The Contractor must participate in meetings, teleconferences, program reviews, in-service reviews.

Deliverables:

FRAMES/AITS Reports Monthly or as Required by the COR

Inventory Reports Monthly or as Required by the COR Audit Reports Five business days after completion of audit

5.11 Business Operations Support

Business Operations Support includes process improvement, ATO and PMO best practices, and Microsoft Office automation tools (e.g., Microsoft Word, Excel, and Project).

The Contractor must support policy and standards planning including resources, approach, schedules, and risk. The Contractor must prepare plans using FAA forms and templates.

The Contractor must provide technical documentation research, interviews, data analysis, engineering, and pilot study support. The FAA will use this in defining and developing policies and standards.

The Contractor must support policy and standards implementation including notification, coordination and control, familiarization and training, and field support. The Contractor must support policy and standards monitoring, reporting and improvement definition and analysis, compliance/non-compliance, and recommendation reporting. The Contractor must assist the FAA in the performance of financial, QA, and property and security audits. Additionally, the Contractor may be required to perform these audits independent of FAA supervision.

5.12 Security

The Contractor must take effective cybersecurity measures at the strategic, operational, and tactical levels. Additionally, the Contractor must:

• Coordinate with system Subject Matter Experts (SME) to determine if cybersecurity vulnerabilities identified by the Department of Homeland Security (DHS), the ATO Cybersecurity Group (ACG), Office of Information Technology (AIT), and/or other responsible entities affect FAA systems.

• Work with SMEs and FAA cybersecurity personnel to respond to security directives, accomplish required testing, and address security concerns.

• Support the FAA’s efforts to achieve its security obligations, including developing, maintaining, and modifying required cybersecurity documentation and briefings related to the authorization and annual reauthorization of FAA systems by the ATO Authorizing Official.

5.12.1 Information System Security Support

The Contractor must provide information system security support in any or all security domains as defined and described by the International Information Systems Security Certification Consortium (ISC²) ® Certified Information Systems Security Professional (CISSP) ® certification.

In all tasks performed, the Contractor must adhere to ISS policies, standards, orders, guidelines, and directives. FAA tasks performed at a Contractor’s facility are subject to the same requirements as those performed at FAA facilities. This includes:

a. Methods of storing, handling, marking, and disposing of classified and Sensitive Unclassified

Information (SUI)/Controlled Unclassified Information (CUI).

b. Conformance with rules of behavior for network access and use including Virtual Private

Networks (VPN) and telework.

c. Certification and authorization support activities in conformance with ISS Program Office methods and directives and applicable National Institute of Standards & Technology (NIST) Special Publications (SP).

d. Auditing of configurations of security devices and processes.

e. Recommendations for and adherence to physical security as it applies to Information

Technology (IT) and ISS.

f. Application development and updates.

5.12.2 Data Breaches and Spills

The Contractor must notify the FAA of any data breach or spill of SUI/CUI data in writing within 24 hours of discovery. The notice must include date, time, and location.

The Contractor must support the FAA in the Root Cause Analysis (RCA) of any breach or spill.

5.12.3 Federal Cyber Security Policy and Regulation Monitoring The Contractor must provide assistance and support activities necessary to achieve and maintain Cyber Security Authorization (SA), which is approved by the ATO Authorizing Official (AO) in accordance with the latest editions of the FAA Security Authorization Handbook and FAA Order 1370.121, FAA Information Security and Privacy: Policy.

The Contractor must support the FAA’s efforts to monitor federal cybersecurity policies and regulations and assess their subsequent effect/impact as it applies to the scope of this Contract.

6. DELIVERABLES

The Contractor must provide support to the FAA in the writing and/or reviewing of FAA program documentation. All documentation prepared on behalf of the FAA for this Contract must be reviewed by the FAA, IAW this Section. The documentation generated from this Contract is not intended for independent publishing. Requests to independently publish documentation must receive written permission from AJM-2. The Contractor must review and provide written comments on the technical accuracy and completeness of each document. No documents, reports, information, etc. may be released to the public or provided to any party other than the FAA and its contractors without written approval of the COR or TO COR. This use restriction, to include copyright when assignment is directed by the Contracting Officer, applies to documentation generated in accordance with AMS 3.5-16 Rights in Data—Special Works (Jan 2009).

The Contractor must prepare and review documents and express comments in a succinct, unambiguous, and factual manner.