Tab 03g SOW SCTS.pdf

SECTION C

Statement of Work

6973GH-20-R-00030

SCT Support Contract

Federal Aviation Administration

Configuration, Logistics, and Management Resource Solutions (CLMRS)

Supply Chain Transformation Support Contract

Section C: Statement of Work

May 2021

Federal Aviation Administration

800 Independence Avenue, SW

Washington, DC 20591

DRAFT

6973GH-22-R-00030

SCT Support Contract

Contents

C.1 GENERAL

C.1.1 Introduction C.1.2 Scope of Work

C.2 CONTRACTOR REQUIREMENTS

C.2.1 Program Management C.2.2 Program Control and Status Reporting C.2.3 Post Award Conference C.2.4 Program Management Reviews/Business Management Reviews C.2.5 Meetings, Reviews and Conferences C.2.6 Engineering Services C.2.7 Information System Security C.2.8 System Authorization Documentation C.2.9 Test and Evaluation C.2.10 System Implementation C.2.11 Technical Documents C.2.12 Training C.2.13 In Service Management C.2.14 NAS Supply Support

C.3 DELIVERABLES

C.4 PERSONNEL

C.5 PERIOD OF PERFORMANCE

C.6 PLACE OF PERFORMANCE

C.7 ORIENTATION PLAN AND PHASE-IN SCHEDULE

C.7.1 Phase-In C.7.2 Phase-Out

C.8 GOVERNMENT FURNISHED PROPERTY

C.9 HOURS OF OPERATION

C.10 OBSERVANCE OF LEGAL HOLIDAYS AND FACILITY CLOSURES

C.11 TRAVEL

C.12 SECURITY

C.13 QUALITY ASSURANCE MONITORING FORM

C.14 ACRONYMS

6973GH-22-R-00030

SCT Support Contract

C.1 GENERAL

C.1.1 Introduction

Logistics Center Support System (LCSS)

The Logistics Transformation Office (AJW-L400) provides lifecycle business and information technology resources to enable the FAA Logistics Center (FAALC, AJW-L) to fulfill its mission, implement FAALC business needs, maintain FAALC's warehoused inventory of National

Airspace System (NAS) parts, and support FAA Headquarters strategic goals. FAALC is located at the Mike Monroney Aeronautical Center (MMAC) in Oklahoma City, Oklahoma.

The LCSS Program is mandated to replace the legacy supply support information system known as the Logistics and Inventory System (LIS), the primary enabling platform supporting the

Logistics Center Mission, by January 2022. LIS is a mission support system required to provide the repair parts needed to support the NAS. These parts keep equipment operating such as air traffic controller equipment and the radars at major airports.

Configuration Management Automation (CMA)

FAA Order 1800.66 describes configuration management (CM) policy and processes required across the FAA. In addition, FAA Order 1800.66 defines CM as a management process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design, and operational information throughout its life cycle.

The Order requires all FAA lines of business, staff offices, service organizations, service areas, and solution providers to apply CM to all FAA systems, programs, investments and assets as found in the FAA Enterprise Architecture (EA); and, across all phases of a system’s life cycle including initiation, acquisition, development, implementation, operation, maintenance and disposal.

FAA’s primary CM system is Web Configuration Management (WebCM). WebCM collects

NAS Configuration Items data and associated status and maintains the Master Configuration

Index (MCI) which details the as-is National Airspace System (NAS) configuration. In addition, WebCM manages proposed changes to Configuration Indices (CIs) in the NAS environment. Developed on dated technology, WebCM has limited capabilities and functionality and is unable to support a CM system as required by FAA Order 1800.66. The current CM data requires significant manual intervention to sustain its’ reliability.

NAS Supply Chain Management (SCM)

The FAA is undergoing agency-wide supply chain transformation which includes the AJW

CONOPS One NAS Supply Chain initiative. This initiative is to align site spares quantities and locations with criticality levels and demand to provide efficient and cost-effective sparing that meets Air Traffic Service requirements provided by Technical Operations.

The NAS Supply Support Team (AJW-136) is within Technical Operations, Operations Support

(AJW-1) and provides the support structure, methodology, tools, procedures, performance monitoring and assurance necessary for the proper operation and maintenance of the National

Airspace System and the Technical Operations Service Unit. The multiple Operations Support

6973GH-22-R-00030

SCT Support Contract

Groups ensure compliance with the FAA’s maintenance and supply chain management principles, policy, and processes. NAS Integration and Support Group (NISG) (AJW-13) provides policies, management, visibility, and processes for the Technical Operations lifecycle management support for NAS systems through initial acquisition, solution implementation, receiving and installing equipment, maintenance, and final disposition. The NAS Supply

Support Team (NSST) is currently virtually re-aligned under the AJW-L, Logistics Center.

NSST (AJW-136) provides agency supply chain management policy in support of NAS service management. NSST manages agency’s supply chain programs such as, the Maintenance Support

Program (MSP), Field Spares Inventory (FSI), Project Materiel Management (PMM), and

Contractor Depot Logistics Support (CDLS) and serves as the agency’s Logistic Element

Managers (LEM) for the Integrated Logistic Support (ILS) elements Supply Support (SS) and

Packing, Handling, Shipping & Transportation (PHS&T).

C.1.2 Scope of Work

The services required by this contract must be performed in accordance with the requirements in this Statement of Work (SOW). This SOW defines requirements to provide engineering and support services to implement the LCSS and CMA systems using the IFS platform. The

Contractor will be responsible for software coding and customization of the IFS platform.

Associated support services include program management, system integration, security, test and evaluation, system implementation and in-service support, training, technical documentation.

This SOW additionally defines requirements to provide integrated logistics support (ILS), supply chain management (SCM), in-service lifecycle management and support of agency optimization initiatives for NAS supply chain and maintenance. Associated support services incorporate planning, requirements, design, development, testing, training, implementation, and maintenance support for Logistic Center, NISG and NSST programs, applications, and databases.

The Contractor must adhere to Scaled Agile Framework (SAFe) procedures. The FAA Business owners determine the priority of work in accordance with the FAA’s strategic objectives and within scope of this SOW. The Contractor will develop Program Increment (PI) objectives, on an incremental basis, for approval by the FAA, and perform services that will be documented, delivered, and demonstrated per the tasks in this SOW.

C.2 CONTRACTOR REQUIREMENTS

C.2.1 Program Management

The Contractor must plan, organize, direct, and control all the activities necessary to meet the requirements of this SOW. The Contractor must assign a Program Manager who has the resources and the authority to ensure efficient and timely program execution and must serve as the primary point of contact for all work performed under this contract to include directing project tasks, staffing, financial/budget tracking, and status reporting at a minimum. The

Program Manager must be prepared at all times to discuss with the Government, the current status of all contract requirements.

The Contractor must describe their management approach to accomplish the required work efforts in a Program Management Plan (PMP).

6973GH-22-R-00030

SCT Support Contract

Deliverable: Program Management Plan (PMP) due 30 days ACA.

C.2.2 Program Control and Status Reporting

The Contractor must continuously monitor performance under this contract to provide the

Government with a timely assessment of program progress or problems and to control all contract activities. The Contractor must prepare and deliver to the Government a Monthly Status

Report (MSR) that provides an assessment of the program's progress, identifies problems encountered or foreseen, updates the program schedule, risks, and provides the status of any open action items assigned to the Contractor. The report must be delivered by the tenth day of each month to the COR and/or CO. The MSR shall include at a minimum:

Work progress (Burn Down Charts, Team Velocity, etc.)

Software Delivery metrics for all Contractor contributed work

Identified risks and technical issues with associated recommendations or proposed solutions or contingency

Schedule deviations and plan to recover

Updated project plans as approved by the COR

Current staffing roster including associated labor categories and work location

Predictability rate of each program increment for the contractor workload, which will be in accordance with SAFe Standards. By SAFe standards, it is expected that the contractor perform at a Predictability rate of 80%.

Deliverable:

1. Monthly Status Reports, starting 30 days ACA

2. Contingency Operations Plans

C.2.3 Post Award Conference

The Contractor must schedule and conduct a Post Award Conference (PAC) within thirty (30) calendar days after contract award to ensure that both the Contractor and the Government have a clear and mutual understanding of the contract requirements. Briefing materials must be provided to the Government at least two (2) business days prior to the PAC. At a minimum, the

PAC must include a discussion of the following:

a) Organization chart and roles of the Contractor’s contract management team members

b) Program management approach

c) Contract requirement clarifications

d) Integrated master schedule

e) Deliverables and delivery schedules

f) Government Furnished Property (GFP), Government Furnished Information (GFI), or services, if applicable

g) Staffing requirements/locations

h) Transition-In plan and timeline

i) Invoicing and billing procedures

j) The Contractor’s overall responsibilities across all functional areas

k) Requested waivers and deviations, if any

6973GH-22-R-00030

SCT Support Contract

Deliverable: Post Award Conference with briefing materials, minutes, and action items; PAC will be held within 30 days ACA. Materials due 5 business days prior to PAC.

C.2.4 Program Management Reviews/Business Management Reviews

The Contractor must conduct Program Management Reviews (PMRs) and Business Management

Reviews (BMRs) quarterly and present orally the program’s management, technical, schedule and cost status. PMRs/BMRs will be conducted in a location proposed by the Government. The date of the review will be proposed by the Government after the award; however, the Contracting

Officer (CO) reserves the right to modify the meeting schedule to accommodate special program needs. The Contractor must provide briefing materials at least three (3) calendar days prior to the conduct of the review and ensure that the appropriate contractor personnel will be present. The

Contractor must record and submit meeting minutes within 7 business days and track action items and report on them until they are closed. Topics to be addressed at the PMRs/BMRs include, but are not limited to:

a) Major accomplishments since the last PMR/BMR;

b) Expected major accomplishments prior to the next PMR/BMR;

c) Review of action items from previous PMR/BMR;

d) Status of software development, integration and /or configuration.

e) Configuration Status Accounting Updates;

f) Status of test and evaluation activities;

g) Contractor deliverables to be delivered within the following ninety (90) calendar days, and status of changes from the previous PMR/BMR;

h) Schedule status including identification of major drivers behind schedule variances and the action plans to resolve these variances, if applicable;

i) Program risks or issues and status of risk mitigation activities;

j) Cost/Funding status

k) Current staffing roster and any changes since the last PMR/BMR or expected changes prior to the next PMR/BMR

Deliverable: Program Management Reviews/Business Management Reviews with briefing materials, minutes, and action items; PMR/BMR to be performed quarterly starting 90 days

ACA.

C.2.5 Meetings, Reviews and Conferences

The Contractor must support recurring meetings, reviews, and conferences to discuss program progress, identify potential problems and resolve identified issues. The Contractor must ensure participation of qualified and responsible personnel at all meetings, reviews, and conferences.

The Contractor must prepare agendas, meeting minutes, action item lists, and briefing materials for each meeting, review, and conference. The Contractor must provide an agenda two (2) business days prior to the start of each meeting unless different notification is specified. Meeting minutes and action item lists must be provided no later than three (3) business days after the completion of each meeting unless different notification is specified.

6973GH-22-R-00030

SCT Support Contract

C.2.5.2 Quality Management

The Contractor must establish and maintain a quality management system in accordance with industry best practice as a means of assuring compliance with requirements of this contract. The

Contractor must describe their quality management approach in the PMP. The FAA project managers will conduct frequent, informal, exploratory interviews with FAA stakeholders, team leads, SMEs, testers, and other team members to determine if the contractor’s services and deliverables are designed according to FAA standards and the scope-of-work. Their findings will be documented within the Quality Assurance Monitoring Form, found in Section C.13 of this

SOW and addressed appropriately. Special attention will also be given to the work documented in the JIRA tickets submitted by the Contractor, Iteration Demonstrations performed by the

Contractor, quarterly PMRs and/or BMRs, and PI Predictability at the end of each PI.

Each PI is one quarter of a year. The PO decomposes the FAA’s strategic objectives into two week increments and summarizes them into PI objectives. Those PI objectives are provided a planned value score by the FAA business owner, and at the conclusion of each PI, the business owner provides an actual business value achieved based on product delivered.

Deliverable: Quality Assurance Plan due 30 days ACA

C.2.5.3 Monthly Project Activity Report

Contractor must prepare and deliver a monthly project activity report that describes the status of project tasks and deliverables. The activity report must include descriptions of work done for the past month, work planned for the next month and project issues. The report must show for each individual project the number of hours with costs worked that month and cumulative hours with costs. The report must be delivered by the tenth day of each month.

Deliverable: Monthly Project Activity Report starting 30 days ACA.

C.2.5.4 Monthly Financial Report

Contractor must prepare and deliver a monthly Task Order financial report no later than the 5th of each month. This report must include the status of the current funding levels and current labor hours and dollars, as well as a comparison between planned and actual expenses. The financial report must include the following:

Contract line items (CLINs) used during the month

Hours billed to the CLINSs

Personnel who billed to each of the CLINs, itemized by CLIN and personnel

Amount of funding used during the reporting period

Amount of funds remaining on the contract

Projected date for 75% of funds spent

Projected date for exhaustion of funds

Deliverable: Monthly Financial Report starting 30 days ACA.

6973GH-22-R-00030

SCT Support Contract

C.2.6 Engineering Services

C.2.6.1 Software Development Services

The Contractor must provide relevant engineering services to the support the development of IFS applications specific to the LCSS and CMA programs. IFS is a COTS Software Platform that the

FAA customizes for LCSS and CMA. The engineering services must support the development and sustainment of the LCSS and CMA IFS products and associated applications in containers via Red Hat OpenShift. Contractor will be responsible for software coding and customization of the LCSS and CMA IFS applications. Services include but not limited to the development of software code and sustainment of operators, self-healing infrastructure, and rolling updates. The

Contractor will conduct all development, integration, test, and activities in accordance with this

SOW and is responsible for implementing the requirements. The Contractor must define, document, and follow an approach for using modular design, standards-based interfaces, and widely supported consensus-based standards. To meet these requirements, the following system architecture approach characteristics must be utilized:

1. Open Architecture – The Contractor must develop and maintain an architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

2. Modular, Open Design – The Contractor must develop an architecture that is layered and modular and uses standards-based commercial off-the-shelf (COTS)/Non-development item (NDI) hardware, operating systems, and/or middleware that all utilize either non-proprietary or non-vendor unique key Application Programming Interfaces (APIs).

3. Inter-Component Dependencies – The Contractor’s design approach must result in a layered system design, maximizing software independence from the hardware, thereby facilitating technology refresh. The design must isolate the application software layers from the infrastructure software (such as the operating system) to enhance portability and to facilitate technology refresh. The design must be able to survive a change to the computing infrastructure with minimal or no changes required to the application logic.

The interfaces between the layers must be built to open standards or available to the

Government with at least Government Purpose Rights.

4. Modular Open Systems Approach (MOSA) –The Contractor’s design approach must produce a system that consists of hierarchical collections of software configuration items

(components). The Contractor’s design approach must emphasize the selection of components that are available commercially.

5. Treatment of Proprietary or Vendor-Unique Elements –The Contractor must explain the use of proprietary, vendor-unique, closed components or interfaces. If applicable, the

Contractor will define its process for identifying and justifying proprietary, vendor-unique or closed interfaces, code modules, hardware, firmware, or software to be used.

When interfaces, hardware, firmware, or modules that are proprietary or vendor-unique are required, the Contractor must demonstrate to the Government that those proprietary elements do not preclude or hinder other component or module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system.

6. Maintain, enhance, and operate a DevOps pipeline.

6973GH-22-R-00030

SCT Support Contract

7. Operate applications on a Cloud environment.

8. Maintain databases utilizing Oracle.

9. Deploy and maintain infrastructure as code using Terraform and Ansible tools.

10. Implement Federal security standards to include FIPS

The Contractor must support the development and sustainment of a Software Development Plan

(SDP) which describes the software development and integration approach including all aspects of performance, quality, maintainability, reliability, schedule, data processing reserves, future growth requirements and software coding standards. The SDP also includes the plans, processes, and procedures for requirements management, software engineering management, software design, software programs, FAA provided network environments requirements, and human factors.

As part of this contract, the Contractor may receive government furnished property/information

(GFP/I) and be tasked to support the development/modification of software and instructions for configuration, and optimization. Any results of these activities would become government property/information.

Deliverables as Required:

1. Software Code

2. Architecture Updates Design Documents

3. Specifications

4. Configuration Management Documentation

5. Site Plans and Topologies

6. Design artifacts

7. JIRA Tickets documenting software coding plans, status, and results which are approved by the FAA in the PI Planning Sessions

C.2.6.2 Technical Interchange Meetings

The Contractor must conduct and support Technical Interchange Meetings (TIMs) as required by the FAA. TIMs will not be conducted for routine interactions between program and technical personnel associated with meeting the requirements of this contract. The Contractor must provide personnel to support the meeting with the requisite skills to actively engage in topics identified on the meeting agenda. Unless otherwise approved by the Government, Contractor personnel must attend the meeting in person.

C.2.6.3 Risk, Issue and Opportunity Management Meeting

The Contractor must support the FAA Risk, Issue, Opportunity (RIO) management process. The

Contractor must participate in monthly joint FAA/Contractor risk meetings.

C.2.6.4 Specifications and Technical Documentations

The contractor must provide technical support in the development and maintenance of specifications and other technical documents required for the development of IFS solutions. The contractor will provide support to the following documents as required by the FAA:

6973GH-22-R-00030

SCT Support Contract

C.2.6.4.1 Software Requirements Specification (SRS)

The Contractor must support the development and sustainment of a Software Requirements

Specification (SRS). The SRS includes requirements for all interactions between the systems and its users, external systems, and data sources. The SRS provides the detail and clarity needed to guide software design, implementation, and test (such as performance requirements, security requirements, extensibility requirements, quality standards or design constraints). It defines the rules, calculations, data manipulations, limits, exceptions, human factors, and software standards needed to fulfill the intent of system requirements. The SRS must include requirements for

COTS and non-developmental software (NDS), and provide traceability to system requirements, interface requirements, and data migration requirements.

C.2.6.4.2 Interface Requirements Specification (IRS)

The Contractor must support the development and sustainment of an Interface Requirements

Specification document (IRS) for all interfaces interacting with external systems. External systems include but are not limited to Procurement Information System for Management

(PRISM), Delphi, Facility Service and Equipment Profile (FSEP), Defense Logistics

Management System (DLMS), Federal Express (FEDEX), United Parcel Service (UPS), and

Warehouse Management System (WMS). The IRS specifies the requirements imposed on one or more systems, subsystems, user stories, manual operations, or other system components to achieve one or more interfaces among these entities.

C.2.6.4.3 Data Migration Specification (DMS)

The Contractor must support the development and sustainment of The Data Migration

Specification (DMS), which defines the approach, plan, ownership roles, data source identification, and data and technical requirements for migrating legacy data into new IFS-based systems. The DMS must address the needs of all environments that require access to legacy data and support all activities and program phases (development to in-service).

C.2.6.4.4 System Design Document (SDD)

The Contractor must support the establishment and sustainment of a data management program to include a System Design Document (SDD). The SDD must capture design decisions relating to user interaction behavior; user story, workflow, reporting, and processing (business) rules;

data migration and data management; external interface exchanges; security, reliability, maintainability and other performance areas. The SDD must provide traceability between its specified components and design elements/approaches and the related system, software, interface, and data migration requirements captured in the SRS, IRS, and DMS.

C.2.7 Information System Security

The Contractor must support activities necessary to achieve annual system authorization by the

FAA Authorizing Official (AO) IAW Federal Regulations, Federal Laws, NIST, Department of

Transportation Compendium and FAA Order 1370.121, FAA Information Security and Privacy

Program and Policy. The Contractor must support the review and update of annual security deliverables, as required.

6973GH-22-R-00030

SCT Support Contract

The Contractor must comply with the current fiscal year version of the FAA Security

Authorization Handbook, NIST Special Publications 800-18, Guide for Development of Security

Plans for Information Technology Systems, NIST 800-53 Rev. 4, and Recommended Security controls for Federal Information Systems.

The Contractor must support the FAA in the annual and ongoing security assessment to ensure the system is authorized to operate. The Contractor must implement security controls IAW

Federal Regulations, Federal Laws, NIST, Department of Transportation Compendium and FAA policies and guideline. The Contractor must support the update of the security documentation following any architectural changes, software modifications, additions, and updates. The

Contractor must also provide support to assist with vulnerability assessments, risk and requirements analysis, and design reviews. Support includes, but is not limited to, research, drafting, and processing approvals.

The Contractor must support an independent risk assessment conducted by an agent provided by the FAA. The Contractor must implement all required documentation updates resulting from the risk assessment. Upon FAA request, the Contractor must provide cost estimates to address recommended system changes resulting from the risk assessment.

The Contractor must work with the FAA to address and resolve system weaknesses. The

Contractor must ensure that the system is configured to only allow authorized individuals access to the system. The Contractor must ensure that all delivered software is free of malicious code.

Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling, must also be addressed expeditiously. The

Contractor also must inform the FAA of the methods used to identify and test for new and/or additional vulnerabilities that appear during the system’s operational life cycle.

C.2.8 System Authorization Documentation

The Contractor must support the FAA in the development of system authorization documentation for a “Moderate” impact level system. The Contractor must support the development of the

System Security Plan (SSP), System Characterization Document (SCD), Information System

Contingency Plan (ISCP) and System Privacy Documentation (SPD).

C.2.9 Test and Evaluation

The Contractor must support the FAA in planning, documenting, and conducting a Test and

Evaluation (T&E) program for significant enhancements to the system to verify that the IFS

Solution meets the functional, interface, compliance, and performance requirements in the intended environment and with the intended users.

The T&E program will include, at a minimum, the following test phases:

1. Development Test (DT)

a. Component Development and Test

b. Component Integration and Test

c. Formal System Integration and Test

2. Operational Test

6973GH-22-R-00030

SCT Support Contract

a. System Regression

3. Production Readiness Test (PRT)

The Contractor must support the FAA in the development of a Master Test Plan (CMTP). The

T&E program must be consistent with the FAA’s development methodology. The FAA encourages the use of automation testing to the extent possible. The CMTP will include the T&E program methodology, test approaches, and test coordination activities The CMTP will serve as the overall test control document for the testing program. The CMTP will describe the overall test strategy for the IFS Solution test program. The CMTP will include the test approach for the both informal and formal test activities. The plan will describe the approach for managing test software configurations (including integration testing) to ensure that the CMTP and testing activities remain current and relevant to the evolution of IFS Solution releases.

The CMTP will contain a Development Test (DT) Verification Requirements Traceability

Matrix (VRTM). The DT VRTM will contain, at a minimum, a listing of all the approved requirements with its correlated test phase, test verification method, subordinate DT test plan(s), and projected test activities. A current version of the DT VRTM must be submitted as part of each test plan review and as a revision to the CMTP prior to each test phase identifying the success criteria for each requirement and tracing the verification of each requirement to one or more test activities. The Contractor must support updating the DT VRTM to include post-test results for every test.

The CMTP must correlate each requirement to a test phase and test verification method (I

(Inspection); A (Analysis); D (Demonstration); T (Test)).

Test procedures and test reports must clearly indicate the associated CMTP DT VRTM requirements. At the request of the FAA, the Contractor may support the development and submission of separate test plans and test procedures for individual tests to allow those tests to progress prior to the submittal and approval of the test plans and test procedures for other tests.

C.2.9.1 Development Test (DT)

The Contractor must support DT for all new or modified system requirements. The Contractor must support all testing required to verify the requirements in the DT VRTM located in the

CMTP. The DT test phase includes: Component Development and Test, Component Integration and Test, and System Integration and Test, and each test type contains test activities. DT must serve to ensure the system has met requirements. DT also verifies that the system is fully integrated and stable. DT must consist of continual quality control.

C.2.9.2 Component Development and Test

The Contractor must support iterative Component Development and Test activities to verify all requirements. The Contractor must perform these test activities in the Contractor or FAA provided Development Environment. The Government reserves the right to observe these activities.

The Contractor must support unit testing (or its equivalent) to ensure the individual function or parts of the code is working as expected, in accordance with the Contractor chosen test methodology as described in the CMTP.

6973GH-22-R-00030

SCT Support Contract

C.2.9.3 Component Integration and Test

The Contractor must support Component Integration and Test activities to verify the individual functions being developed work together without degrading the system IAW the Contractor

Master Test Plan (CMTP). The Contractor must support these Component Integration and Test in the FAA provided test environment. The Government reserves the right to observe these activities.

DT Integration testing must verify the proper installation and functioning of the system in the

Integration Test Environment. DT Integration testing must also address performance/load requirements compared to the established performance baseline for each software version. DT

Integration testing must include the verification of system interfaces.

The Contractor must support regression testing for any builds introduced to address defects found during Component Integration and Test.

C.2.9.4 System Integration and Test

The Contractor must support System Integration and Test activities to reduce risk and demonstrate that the system, as a whole, meets requirements. The Contractor must perform these test activities in the FAA provided test environment. The Contractor, using Government approved test plans and test procedures, must perform the following formal activities: DT

Performance/Load testing, DT Compliance testing, DT System (end-to-end) testing and DT

System Regression testing. The Contractor must execute System Integration and Test activities to verify the system, performance, and compliance requirements and ensure the system's overall readiness leading up to the Government conducted Operational Test (OT).

The Contractor must support formal DT Performance/Load Testing to verify system processing time and stress thresholds. These tests also serve to measure system scalability, reliability, and resource usage. The Contractor may integrate these tests throughout DT System (end-to-end)

Testing.

The Contractor must support formal DT Compliance Testing to validate the system developed meets the requirements. The Contractor may integrate these tests throughout DT System (end-to-end) Testing.

The Contractor must support formal, Government witnessed, DT System testing as defined in the approved CMTP. DT System testing must address verification of integrated software components to address specification items under conditions that emulate the projected production conditions. The Contractor must conduct these tests on the FAA Test Environment with the baseline software.

The Contractor must support DT System Regression testing when issues are identified during formal System Integration and Test activities that prevent the Contractor from meeting the exit criteria established by the Government for the CMA DT program.

6973GH-22-R-00030

SCT Support Contract

The Contractor must support the FAA Test Team the ability to witnesses the status of all System

Integration and Test activities. The Contractor must perform any required DT System Regression tests based on results of formal testing.

C.2.9.4.1 Government Operational Test

The Contractor must provide services to support the execution of Government Operational Test activities in the FAA test environment. The Contractor must provide the Government with a copy of all tools developed to support test conduct, including but not limited to test scripts, test data, interface drivers (in lieu of actual interfaces), scenarios, simulators, and test databases. All

Contractor provided test tools, scenarios, and simulators must be validated and approved by the

FAA. The Contractor must support capturing and analyzing issues during Government test conduct.

C.2.9.4.2 Production Readiness Test

The Contractor must support Government-conducted Production Readiness Tests (PRT) to verify the fully integrated software and environment, and to address system level specification items that require additional verification from DT System testing prior to production deployment. PRT will be conducted in the Test Environment.

C.2.9.5 Test Documentation

C.2.9.5.1 Test Readiness Reviews (TRRs)

The Contractor must support the FAA in conducting a Test Readiness Reviews (TRRs) prior to

System Integration and Test to ensure test readiness.

C.2.9.5.2 Test Plans

The Contractor must support the development of Test Plan(s) for System Integration and Test activities. The Test Plan must cover all aspects of test. The FAA and Contractor will develop test procedures from test descriptions contained in the test plan.

Specific methods for performance measurement must be included. In addition, a requirements matrix must be included; this matrix must be excerpted from the Contractor Master Test Plan’s

(CMTP) DT Verification Requirements Traceability Matrix (VRTM) and must reflect the specific test for which this Test Plan is being delivered.

Deliverables: Software Test Plans

C.2.9.5.3 Test Procedures

The Contractor must support the FAA in preparing test procedures that cover all requirements and testing addressed in the approved CMTP and Test Plan for all formal test activities.

Deliverables: Software Test Procedures

C.2.9.5.5 Test Reports

The Contractor must support the FAA in providing quick-look and final test reports at the completion of System Integration and Test. The quick-look test reports will allow the

6973GH-22-R-00030

SCT Support Contract

Government to render a decision without delay if preliminary test results reveal no significant problems. The final test report must capture a complete set of test artifacts to support the results.

Deliverables: Software Test Reports

C.2.9.6 Program Trouble Reports (PTR)

The Contractor must support the FAA in tracking, reporting, and maintaining Problem Trouble

Reports (PTRs) as part of the test and evaluation program. The Contractor must provide

Government access to all PTRs. The Contractor must assign a unique identification number to each PTR. The Contractor must identify the proposed regression testing, or future modification(s) to the testing program required to validate the successful corrective action. If a component fails during formal test, the Contractor must perform failure analysis to identify the cause of failure and document the failure in a PTR. The Contractor must perform any corrective actions necessary to ensure full specification compliance.

C.2.10 System Implementation

The Contractor will support the FAA in implementing and integrating the IFS Solution into the

Government provisioned environments. The implementation and integration of the IFS Solution must be accomplished such that the performance and functional requirements identified by the

FAA are accomplished.

The Contractor must assist the FAA in developing and delivering an IFS Solution

Implementation and Integration Plan that describes the activities, requirements, constraints, and processes and procedures necessary to ensure successful solution implementation and integration into the Government hosting environments.

C.2.10.1 System Installation and Deployment

The FAA will support the IFS Solution installation and deployment. The Contractor must support the installation and deployment of the software at FAA facilities, as requested.

The Contractor must provide engineering services to support developing detailed Installation

Instruction Package to be used by Contractor and the FAA while performing installation and deployment into FAA hosted environments. The Installation Instructions must include an installation checklist including at a minimum: pre-installation, pre-production installation, production installation and post-production installation checkout activities.

C.2.11 Technical Documents

The Contractor must support the FAA in providing all documentation required for operation and support of the IFS Solution. As directed by the Government, the Contractor must develop and deliver the following technical documentation:

C.2.11.1 System Administrator Manual (SAM)

The Contractor must assist with the development of a System Administrator Manual (SAM), which provides system administrators and maintenance staff with instructions sufficient to install, operate, monitor, and maintain the IFS Solution.

6973GH-22-R-00030

SCT Support Contract

Instructions must cover all the systems and subsystems, and COTS software. Topics that must be covered include, but are not limited to, system diagnostics, problem handling procedures and aspects of software maintenance, such as processes required for modification of system configuration files and installation of operating system patches.

C.2.11.2 Software User Manual (SUM)

The Contractor must support the development of a Software User Manual (SUM) which provides user instructions sufficient to execute all IFS Solution user functionality for their intended purposes. Functions described must include, but are not limited to, login; security; workflow, information, and forms input instructions; report generation; and error messages. The SUM must provide the steps for executing the functions and describe the expected output and measures to be taken if error messages appear.

C.2.11.3 Database Administration Guide

The Contractor must support the development and sustainment of a Database Administrator’s

Guide (DAG) which provides information and procedures specific to IFS Solution database administration roles. The administrator manuals must include the routine maintenance procedures and daily administrative procedures that are required to maintain the system. The administrative manuals must provide descriptions and procedures for session initiation;

contingencies and alternate states and modes of operation; assistance and problem reporting;

procedures for using all functions of the system; system backup and restoration procedures;

troubleshooting procedures; and error messages.

C.2.11.4 System Security and Network Configuration Manual

The Contractor must support the development and sustainment of a System Security and

Network Configuration Manual (SSNCM) that describes all the information and the procedures necessary to enable a trained specialist to administer all IFS Solution security and network configuration parameters.

C.2.12 Training

System users will need the knowledge and training required to operate, monitor, maintain, test, and support the system. The Contractor must support the design and development of training materials as requested by the FAA.

C.2.13 In Service Management

The Contractor must provide support in documenting the maintenance approach for the IFS

Solution in a Software Maintenance Plan (SMP). The SMP must provide all documentation necessary for the FAA to support and maintain the IFS Solution. The Contractor must support the Government with any new releases of the software and/or security patches for the solution.

As ordered, the Contractor must provide Tier 2 and/or 3 level support for the IFS Solution.

Tier 2 - Maintenance support for problems not resolved by FAA Tier 1 help desk functions.

Tier 3 – Support required for correction of system software problems.

6973GH-22-R-00030

SCT Support Contract o Tier 3 support is used when Tier 2 support cannot resolve the issue, or the issue is a software fault requiring software maintenance or development action.

C.2.14 NAS Supply Support

C.2.14.1 Administrative Support Services

The contractor must provide the following general administrative support to the organization by performing the following tasks:

Perform word processing, data entry, and reproduction services utilizing Excel, Access, PowerPoint software, Create reports, letters, memos, and other administrative correspondence required for effective organizational and customer communication, Schedule meetings, conferences and travel when directed. Provide support with meeting management including planning, coordinating, and facilitating of meetings, Prepare and distribute minutes for weekly, monthly, quarterly and/or ad hoc meetings.

Conduct research, coordinate actions and issues, provide recommendations and resolutions, and update office records, databases and files for assigned programs, Reproduce and assemble program materials; establish and maintain program files;

track administrative support actions; and coordinate intra-and inter-office activities and functions, Participate in the financial planning process by providing critical analysis and assessment reports, of office budgets, and tracking office expenditures, and

Support and assist with reconciliation of budget data reports and compile clear and concise reports for management.

C.2.14.2 Lifecycle Management (In-Service Management) and Integrated Logistics Support

(ILS)

In-Service Management is one phase of Acquisitions Management System (AMS) and is a parallel description for overall lifecycle management. In-Service Decision is a point in time that we have activities before “pre” and after “post”. NSST must provide supply support recommendations, analyses, support and expertise to ensure coordination between Technical

Operations’ In-service Managers (AJW-13) and the Logistic Center (AJW-L) and stakeholders, such as the Program Management Organization (AJM). Integrated logistics support as prescribed in AMS policy section 4.3, is the critical functional discipline that plans, establishes, and maintains an integrated logistics support system for the lifecycle all FAA products and services.

The objective is to provide the required level of service to the end user at optimal lifecycle cost to the FAA for new investment programs and the sustainment of fielded products and services.

The contractor must provide both "pre" and "post" in-service management and integrated logistic support that includes the following:

6973GH-22-R-00030

SCT Support Contract

Review, disseminate, track, and provide feedback on program documentation and other deliverables through completion/acceptance. Manage and track NISG NAS program artifacts, including maintenance of document repositories, Provide recommendation for planning for In Service Decision (ISD) activities and, coordination with FAA Program Offices for NISG NAS programs, Conduct planning and coordination associated with the Integrated Logistics Support

Plan (ILSP) and Implementation Strategy and Planning Document (ISPD) for NAS programs and provide recommendations, Recommend tailoring the In-Service Review (ISR) Checklist to facilitate resolution of readiness issues prior to ISD and provide recommendations, Verify that logistics-related activities in the ISR checklist are complete so the product or service will be operationally suitable at the ISD, Coordinate with program offices to develop action plans and resolve those actions to satisfy the ISD entrance criteria stipulated in their ISR Checklist, Support the development, tracking and reporting of NISG program schedules and status, Plan, coordinate and provide recommendations to support systems/services/projects through feedback to stakeholders regarding lessons learned using Line of Business

(LOB) telecoms, legacy systems workshops, briefings, and/or recommended changes to policy, Provide platform specific (Surveillance, Automation, Navigation, Communications, Weather, Environmental) project material management support for managing agency-wide assets.

C.2.14.3 Supply Chain Management (SCM)

The FAA is currently utilizing multiple SCM programs and sources of supply which interact and align with standardized processes to manage and fund FAA supply chain inventory. F&E Capital

Improvement Programs are the beginning of the FAA supply chain for most NAS facilities/system. F&E Projects provide materiel and equipment for installation and are the source for initial supply chain assets, such as depot and field level spares and test equipment. The

Maintenance Support Program (MSP) enables TechOps to procure replacement parts and services from the FAA Logistics Center (FAALC) and Contractor Depot Logistics Support

(CDLS). The Field Spares Inventory (FSI) Program utilizes tools and processes to execute the baseline initiative and maintain a perpetual field spares inventory throughout FAA facilities. This is comprised of barcoding, and recording spare parts, their physical location and movement throughout the NAS. In the future, FSI Asset Marking System (AMS) will be migrated into the

FAA’s enterprise-wide system, Logistics Center Support System (LCSS), which will add increased functionality and interoperability with F&E Project Materiel Management, MSP and other supply chain programs and further enable optimization of the FAA supply chain.

The contractor must provide the following SCM program support, performing the following task:

Provide platform specific (Surveillance, Automation, Navigation, Communications, Weather, Environmental) project material management support for managing agency-wide assets, 6973GH-22-R-00030

SCT Support Contract

Review current FAA policy and procedure documents, provide input, draft and/or recommend revisions.

Review current supporting data systems, such as the LIS Project Management System

(PMMS), Project Materiel Shipping and Receiving System (PMSRS).

Review and develop materials for virtual and/or on-site familiarization sessions for NSST programs, tools and system, Provide support at the site on inventory processes, Asset Marking System (AMS), scanning, and barcoding utilizing tools which includes:

o Developing and delivering briefing material o Perform Baseline inventory process for field spares assets which includes;

o Visit, barcode, and record in AMS field spare inventories at field storage sites.

Deliver a comprehensive report of each site visit with recommendations, Reporting on site inventory progress within 30 days of the site visit, Collect a rolling list of site recommendations for agency policy improvements, Develop and provide NSST Programs Metrics, Review Results of Field work which includes:

o Spot check inventory and reconcile inventory in AMS, o Spot check LCSS financial records with NAS parts activity, Process Service Order Agreements (SOA) and creation of PRISM requisitions for NSST programs, Maintain NSST Programs’ KSNs with program related documents, schedules, briefing, and presentations.

Execute and maintain a FSI Quality Management program for on-going monitoring of FSI accuracy, Maintain and update NSST Programs’ (MSP/FSI/PMM) data visualizations utilizing

Tableau, generating dashboards, Provide consulting and technical support for system enhancements, modifications, and development, Evaluate current systems and make recommendations, Evaluate and analyze interface and source information systems, such as LCSS/ IFS, Facility

Service and Equipment Profile (FSEP), Warehouse Management (WMS), and AMS, Delphi, and Corporate Work Plan (CWP), to incorporate in project planning, develop interfaces with other systems to meet requirements, Review technical documentation for impact on systems and business processes that affect

Technical Operations capabilities, Provide program expertise to include costing, timelines, resources, and impact statements, Facilitate stakeholder sessions to develop program, functional, and system requirements, Review legacy systems and technical documentation to develop system requirements and product backlogs, Assist in prioritizing requirements and bug fixes for product releases, Develop…