DRAFT FLITES Performance Work Statement (PWS) 12 Nov 24.pdf

CUI//BASIC//NOFORN

FA8770-25-R-B001

Section J, Attachment 2 10 Apr 24

DRAFT

DEPARTMENT OF THE AIR FORCE

AIR FORCE LIFECYCLE MANAGEMENT CENTER

FOUNDATIONAL LOGISTICS INFORMATION TECHNOLOGY ENTERPRISE SYSTEM

WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433

PERFORMANCE WORK STATEMENT

FLITES Program Manager Date

Controlled by: AFLCMC/GB Controlled by: AFLCMC/GBS CUI Category: BASIC Distribution/Dissemination Control: NOFORN POC: Capability Delivery Manager (CDM), GBS

Table of Contents

1. Purpose / Scope

1.1. Place of Performance

1.2. Definitions

2. Requirements

2.1. Software Licenses (Contractor’s Product)

2.1.15. Regression Testing

2.2. Cybersecurity Compliance

2.3. Technical Support Services

2.3.1. Requirement Overview

2.3.2. Hosting Support

2.3.3. Training

2.3.4. Integration and Interoperability Support

2.3.5. Program Support

2.3.6. Support Services

2.3.7. Configuration Support

2.3.8. Audit Readiness

2.3.9. Development Support

2.3.10. Project Coordination Support

2.4. Travel

3. Documentation/Deliverables

4. Other Direct Costs

5. Foreign Nationals

6. In/Out Processing

7. Acronyms

1. Purpose / Scope

The purpose of this Performance Work Statement (PWS) is for the Government to obtain the Contractor's product and software licenses, software maintenance, and Technical Support Services necessary to enable the Government to develop, configure, integrate, deploy, and sustain FLITES in a Government-approved cloud environment.

The product shall allow the Government to create FLITES, utilizing agile principles to develop, configure, integrate, and deploy the product.

1.1. Place of Performance

Depending on the services performed, the place of performance shall be at the discretion of the Contractor.

1.2. Definitions

1.2.1. Contractor. Contractor is defined as Contractor and its partners, subcontractors, and/or authorized agents.

1.2.2. Contractor's Product. Contractor's Product is defined as anything covered by the licenses.

1.2.3. FLITES Product. FLITES Product is defined as the FLITES code built upon the foundation of the Contractor's Product.

1.2.4. Government. Government is defined as the United States Government (USG), Department of Defense (DoD), United States Air Force (USAF), Air Force Materiel Command (AFMC), Lifecycle Management Center (LCMC), Business Enterprise Services (BES) Directorate (AFLCMC/GB), Enterprise Logistics Systems (AFLCMC/GB4), Enterprise Logistics Readiness Portfolio (AFLCMC/GBS), Foundational Logistics Information Technology Enterprise System (FLITES), and its partners and authorized agents.

2. Requirements

The Contractor shall provide the product, software maintenance (as applicable), and related technical support services.

2.1. Software Licenses (Contractor’s Product)

2.1.1. The Contractor shall deliver or make available licenses for use across the

Government with licensing terms, structures, and conditions which are consistent with federal procurement law and provide the Government with the most favorable terms possible. (A004, DI-AVCS- 80700A, Computer Software Product End Item)

2.1.2. The Contractor shall deliver a Contractor’s product that allows the Government the ability to develop, configure, integrate, deploy, sustain, and maintain the FLITES requirements. (A004, DI-AVCS-80700A, Computer Software Product End Item)

2.1.3. The Contractor shall deliver a Contractor’s product that allows the Government to comply with the Agile Applications DevSecOps specifications. (A004, DI-AVCS-80700A, Computer Software Product End Item)

2.1.4. The Contractor shall deliver a quarterly license usage and status report.

(A002, DI-MISC-80508B, Technical Reports for Study/Services)

2.1.5. The Contractor’s product shall allow the Government to establish multiple software environments to support the lifecycle of FLITES to include Development/Configuration, Multiple Testing Environments, Training, Staging/Pre-Production Demonstration, Production, and Mission Continuity or Failover Environment.

2.1.6. The Contractor’s product shall adhere to Open Systems Architecture (OSA) standards, protocols and guidelines, and implementation of current commercial techniques and standards.

2.1.7. Licensing terms and conditions shall fully account for the Contractor’s product and all maintenance updates delivered as part of the application Continuous Integration/Continuous Delivery (CI/CD) Pipeline Process.

2.1.8. The Contractor’s product shall enable access the Application and Software Development Kit (SDK) licenses, with terms and conditions that are free of limitations with respect to:

2.1.8.1. Acquisition program, functional area command/unit level, or departmental affiliation, including authorized Government agents.

2.1.8.2. Hosting location/site.

2.1.8.3. Lifecycle phase; licenses will offer full FLITES product lifecycle support, to include software development, configuration, integration, testing, operations and maintenance, insofar as it pertains to the Contractor’s product.

2.1.8.4. End-user device (laptop, phone, tablet, etc.).

2.1.9. The Contractor shall deliver supporting instructions and technical documentation, to include notes, automated test materials, installation and maintenance scripts, and configuration set-ups, with each delivery of the Contractor’s product. (A007, DI-IPSC-81442A, Software Version Description; A008, DI-IPSC-81439A/T, Software Test Description; A009, DI-IPSC-81440A/T, Software Test Report)

2.1.10. The Contractor’s product shall enable accomplishment of software maintenance support tasks, e.g., Contractor’s product upgrades, patches, bug fixes, and supporting instructions and other documentation. This support includes release notes, automated test materials, installation and maintenance scripts, configuration setups within the SDK, Air Force unique configurations or development, and data dictionary and attribute matrix for interfaces and data loads. (A004, DI-AVCS-80700A, Computer Software Product End Item; A007, DI-IPSC-81442A, Software Version Description;

A008, DI-IPSC-81439A/T, Software Test Description; A009, DI-IPSC- 81440A/T, Software Test Report)

2.1.11. The Contractor’s product shall support FLITES product enhancements and/or new requirements through existing features in the Contractor’s product, through road-mapping new features into future releases of the Contractor’s product, and/or through development by the FLITES Team using the Contractor’s product SDK tool suite.

2.1.12. The Contractor’s product shall adapt to changing statutes, regulations, business rules, functional and technical requirements, lifecycle support requirements, and instructions with minimal to no core product changes.

2.1.13. The Contractor shall deliver the Contractor’s product requiring minimal to no changes to the FLITES product.

2.1.14. The Contractor shall deliver all software licenses and software maintenance.

2.1.15. Regression Testing

2.1.15.1. The Contractor shall, prior to delivery of the Contractor’s product, regression test the Contractor’s product.

2.1.15.2. The Contractor shall deliver a preview version of the Contractor’s product against which the Government will perform FLITES-specific regression testing.

2.1.15.3. The Contractor shall provide draft release notes identifying changes to the part of the Contractor’s product used by the Government, e.g., degradation of functionality.

2.1.15.4. The Contractor shall support Government test execution and test result evaluation, e.g., findings review.

2.1.15.5. The Contractor shall support Government analysis for issue determination, e.g., the FLITES product issue versus the Contractor’s product issue.

2.1.15.6. The Contractor shall support and participate in meetings to discuss test findings and determine risks/issues/blockers to Government release acceptance.

(A002, DI-MISC-80508B, Technical Reports for Study/Services; A004, DI-AVCS-80700A, Computer Software Product End Item; A007, DI- IPSC-81442A, Software Version Description; A008, DI-IPSC-81439A/T, Software Test Description; A009, DI-IPSC-81440A/T, Software Test Report)

2.2. Cybersecurity Compliance

2.2.1. The Contractor’s product shall meet cybersecurity directives, regulations, and guidance. Cybersecurity includes adherence to Risk Management Framework (RMF) and Authorization to Operate (ATO) controls, and Contractor’s product remediation. (A002, DI-MISC-80508B, Technical Reports for Study/Services)

2.2.2. The Contractor shall create, maintain, and deliver Cybersecurity documentation for the Contractor’s product.

2.2.3. The Contractor shall deliver an overall plan and methodology for how cybersecurity shall be managed, tested, evaluated, and flowed down to the Government for the Contractor’s product to include zero-day security threats (A002, DI-MISC-80508B, Technical Report for Study/Services)

2.2.4. The Contractor shall support cybersecurity configuration, development, and application control testing in support of the Risk Management Framework (RMF) process to obtain and maintain an Authority to Operate (ATO) or continuous ATO and certification from the DoD Authorizing Official

2.2.5. The Contractor shall respond to cybersecurity risk management, including threat analysis, system exposure to threats, as well as integration of cybersecurity with systems engineering and risk management processes, as events occur.

2.2.6. The Contractor shall provide Contractor’s product remediation, i.e., patches, bug fixes and updates, based on cybersecurity findings as they occur.

2.2.7. The Contractor shall provide data protection security measures in the Contractor’s product that protect program information from unauthorized disclosure (data at rest, data in motion).

2.2.8. The Contractor shall deliver Contractor’s product guides and best practices for the installation, security configuration, operation and maintenance, log monitoring, backup and recovery, and replication for contingency recovery.

(A002, DI-MISC-80508B, Technical Report for Study/Services)

2.2.9. The Contractor shall implement and help assess the security controls in accordance with (IAW) RMF DoD implementation guidance.

2.2.10. The Contractor shall assist in the remediation of identified security vulnerabilities.

2.2.11. The Contractor shall provide evidence of internal cyber-secure Contractor’s product development (example ISO 27001 certification).

2.2.12. The Contractor shall provide evidence that One Network and sub- Contractors provide a cyber-secure development support environment.

Which includes but not limited to the sub-Contractor Alion GIT server and laptops used to store FLITES test data and documentation. Evidence should consist of meeting NIST Special Publication 800-171, Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems.

2.2.13. The Contractor shall provide evidence that Information Systems Vulnerability Information (ISVI) for the Contractor’s product and FLITES product is securely stored on Contractor devices and securely transmitted to FLITES cybersecurity team. Refer to:

https://www.archives.gov/cui/registry/category-detail/info-systems-vulnerability-info.html

2.3. Technical Support Services

2.3.1. Requirement Overview

2.3.1.1. The Contractor shall coordinate and execute a collaborative project kickoff meeting with the Government. (A003, DI- ADMN-81373, Presentation Materials)

2.3.1.2. The Contractor shall support visioning / planning sessions to prioritize requirements and objectives, aligning the requirements into appropriate sprints for successful delivery.

2.3.1.3. The Contractor shall support the cross-reference of the Jira instances used by the Government and the Contractor for all FLITES product and Contractor’s product issues elevated to the Contractor for resolution, ensuring no loss of information or momentum.

2.3.1.4. The Contractor shall support the configuration, development, integration, deployment and sustainment activities and requirements per the sprint requirements, with a sprint demonstration at the end of each sprint. The Contractor shall address issues in subsequent sprints.

https://www.archives.gov/cui/registry/category-detail/info-systems-vulnerability-info.html https://www.archives.gov/cui/registry/category-detail/info-systems-vulnerability-info.html

2.3.1.5. The Contractor shall provide sufficiently trained staff to accomplish all requirements and/or tasks.

2.3.1.6. The Contractor shall provide support to the IPO, assistance with the creation of a go-live plan with mitigation strategies for any particular release with integration, data migration, hosting and cyber accreditation issues identified.

2.3.1.7. The Contractor shall provide production support while active licenses are in place. Technical issues will be raised to the Contractor through its reporting system and the Contractor shall respond in a timely manner, based on the severity of the item and/or issue and detailed in the reporting system.

2.3.1.8. The Contractor shall provide support and documentation of issues identified by the Government in the Government’s Jira system, with triage sessions held at least weekly to prioritize each issue/request and determine appropriate remedial action.

Depending on the severity and code base impacted, issues shall be raised into One Network’s Jira System for triage.

2.3.1.9. The Contractor shall work with the Government to establish a change management process to effectively manage changes requested and/or required by the Government. This process shall continue to evolve, as needed, to improve processes and communication.

2.3.1.10. The Contractor shall provide support to the IPO in maintaining development and testing instances.

2.3.1.11. The Contractor shall provide sustainment support for the first limited deployment release, and subsequent FLITES releases when in production that require models of and processors modifications to the Contractor’s product.

2.3.1.12. The Contractor shall provide data standardization to share data across the Contractor’s product and Air Force enterprise.

2.3.1.13. The Contractor shall ensure the Contractor’s product is structured with a focus on planning and maintenance Bill of Material (BOM), including Part Number Supply Support Request (PNSSR), Local Manufactured and Local Purchased (L&P), parts integration with Integrated Logistics System – Supply (ILS- S), indentures, Weapon System Support Program (WSSP), and warranty management.

2.3.2. Hosting Support

2.3.2.1. The Contractor shall provide hosting support, including application installation of the Contractor’s product and ongoing maintenance services as required for release of the Contractor’s product to Government-approved Impact level 4 (IL-4) controlled unclassified cloud hosting environments.

2.3.2.2. The Contractor shall provide services and expertise related to Contractor’s product installation, application and continuous integration/continuous delivery pipeline support, integration delivery, and remediation assistance. (A002, DI-MISC-80508B, Technical Reports for Study/Services)

2.3.3. Training

2.3.3.1. This area identifies the training support required to enable the Government to construct and sustain a secure, reliable, resilient, and scalable FLITES product.

2.3.3.2. The Contractor shall deliver product training and training materials to enable the successful transfer of operational and Contractor’s product knowledge.

2.3.3.3. The Contractor shall provide training support including installation of the Contractor’s product and administration, SDK and Application Programming Interface (API) use, end-user communication, and mobile device and peripheral operations.

2.3.3.4. The Contractor shall provide training which shall be formal (classroom) and informal, e.g., over the shoulder, Computer Based Training (CBT). Formal training shall be accomplished no more than twice a year to educate the IPO on the software.

2.3.3.5. IPO Training

2.3.3.5.1. The Contractor shall provide informal training on all interim drops/releases (release notes, demo, etc.). The informal training may require Training Materials (CDRL A006) to be delivered no more than four (4) – six (6) times annually. Training consists of a technical walk through and detailed training of all new or newly revised features, i.e., Bill of Materials Management, additional Assistance Requests, etc.

2.3.3.5.2. The Contractor shall provide SDK and Application

Programming Interface (API) training for the Contractor’s product.

2.3.3.5.3. The Contractor shall provide Database Administration (DBA) training for the Contractor’s product.

2.3.3.5.4. The Contractor shall provide refresher Contractor’s product application integration training (i.e., proper use of built in adaptors to industry products using standardized communication methods to include, but not be limited to HTTP/S, Web services, S/FTP, MQ Series).

2.3.3.5.5. The Contractor shall provide technical training and oversight guidance to FLITES personnel on the configuration and maintenance of the Contractor’s product using both Out of the Box (OOTB) and SDK features, as well as related APIs.

2.3.3.5.6. The Contractor shall deliver training materials for the services listed herein.

2.3.3.6. User Community Training and Training Materials

2.3.3.6.1. The Contractor shall deliver User Manuals and Training Materials for the Contractor’s product that pertain to the foundational elements of the FLITES product, i.e., application overview, screen navigation, menu structure, chat capability, email notifications, export capability, glossary entries, etc., to include delivery of any content developed for Learning Management System (LMS).

2.3.3.6.2. The Contractor shall support training planning, to include delivery of the Contractor’s product training, recommendations and lessons learned regarding delivery, timing, cadence, and order of training delivery, and recommendations on various LMS supporting the training of this material.

(A006, DI-ILSS-80872/T, Training Materials)

2.3.4. Integration and Interoperability Support

2.3.4.1. The Contractor shall provide Integration and Interoperability support, to include assistance with application, data and technical architecture necessary to implement and sustain the FLITES product.

2.3.4.2. Integration and Interoperability support shall include compliance with all requirements, assistance with application APIs and related components.

(A002, DI-MISC-80508B, Technical Reports for Study/Services)

2.3.5. Program Support

2.3.5.1. The Contractor shall coordinate all work with the Government Product Owner(s), e.g., the FLITES Program Manager, and Proxy Product Owner(s) using an agile delivery method. (A003, DI-ADMN-81373, Presentation Materials)

2.3.5.2. Program Support shall include coordination of delivery of the Contractor’s product, release of the FLITES product, responses to enhancement requests, and participation as a FLITES team member in all agile activities. (A003, DI-ADMN-81373, Presentation Materials)

2.3.5.3. The Contractor shall participate in the work driven by prioritized story points as directed by the FLITES Product Owner(s).

2.3.5.4. The Contractor shall participate in agile meetings, ceremonies, and daily activities.

2.3.5.5. The Contractor shall use Government-provided tools such as Jira to record work progress and status.

2.3.5.6. The Contractor shall coordinate and deliver all Contractor’s product in accordance with prioritized stories and the FLITES roadmap.

2.3.5.7. The Contractor shall provide a Software Version Description for each Contractor’s product. (A007, DI-IPSC-81442A, Software Version Description)

2.3.5.8. The Contractor shall support the interoperability of the FLITES product and integration with hosting services that govern application management, security, auditing, and system monitoring.

2.3.5.9. The Contractor shall comply with current and future DoD engineering and security mandates by regularly updating the Contractor’s product.

2.3.5.10. The Contractor shall advise and support the Government on FLITES product integration with shared enterprise core services, such as Lightweight Directory Access Protocol (LDAP), Domain Name System (DNS), Online Certificate Status Protocol (OCSP), Edge Gateway, MySQL, Active Directory Federation Services, Common Access Card (CAC) and Public Key Infrastructure (PKI) authentication, etc.

2.3.5.11. The Contractor shall advise and support the IPO on the use and integration of adapters to industry products, i.e., as Oracle EBiz and Financial suite, and communication methods, i.e., HTTP/S, Web services, S/FTP, MQ Series.

2.3.5.12. The Contractor shall advise the IPO on hosting challenges through the identification and/or resolution of hosting problems as they occur.

2.3.5.13. The Contractor shall provide sustainment support for FLITES 1.0-1.2 and subsequent FLITES releases when models of and processors modifications to the Contractor’s product is needed.

2.3.5.14. The Contractor shall provide data standardization to share data across the Defense Core and AF enterprise.

2.3.5.15. The Contractor shall provide Contractor’s product structure with a focus on planning and maintenance. This includes PNSSR, Local Manufactured and L&P, parts integration with ILS-S, indentures, WSSP, and warranty management.

2.3.5.16. The Contractor shall advise the IPO with evaluation and integration of new pipeline tools.

2.3.5.17. The Contractor shall provide application and integration troubleshooting and reach-back expertise.

2.3.6. Support Services

2.3.6.1. The Contractor shall provide support to enable the Government to serve as the System Integrator (SI), allowing the Government to operate and maintain FLITES and includes, but is not limited to, architectural, testing and operational support services. (CDRL A002, Technical Report – Study/Services; CDRL A007, Software Version Description; CDRL A008, Software Test Description; and CDRL A009 Software Test Report.

2.3.6.2. The Contractor shall provide Contractor’s product technical information such as architectural artifacts at the system, subsystem, API, and database level describing Contractor’s product features, functions, SDKs and applicable add-ins.

(A002, DI-MISC-80508B, Technical Report for Study/Services).

2.3.6.3. The Contractor shall provide test methodologies and artifacts to reduce redundant testing by the Government while increasing the level of acceptability of the delivered system (A008, DI-IPSC- 81439A/T, Software Test Description; A009, DI-IPSC- 81440A/T, Software Test Report).

2.3.6.4. The Contractor shall provide targeted regression testing. The Contractor shall utilize a targeted regression testing method, as determined by Contractor’s developers and product managers, where the testing focuses on features/modules directly related to changes, features/modules adjacent to changes but not directly related, and features/modules entirely unrelated but of high priority. The test suite will consist of sanity testing in addition to re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after the Contractor’s product code changes. (A008, DI- IPSC-81439A/T, Software Test Description; A009, DI-IPSC- 81440A/T, Software Test Report).

2.3.6.5. The Contractor shall provide testing expertise and remediation services to support all aspects of the product build for the Contractor’s product and FLITES product. This includes component assembly, data loads, exchange management, performance, security, regression, user acceptance and unit/system testing and test remediation.

2.3.6.6. The Contractor shall execute remediation activities, i.e., implement product changes to the Contractor’s product and FLITES product to address Test and Security findings.

2.3.6.7. The Contractor shall provide access to support materials such as, but not limited to, user blogs, discussion forums, on-line help, user training, FAQs, hosted chat, telephone, email and web-based technical support (A006, DI-ILSS-80872/T, Training Materials).

2.3.6.8. Provide installation and release materials associated with Contractor’s product. (A007, DI-IPSC-81442A, Software Version Description)

2.3.7. Configuration Support

2.3.7.1. The Contractor shall provide configuration support to establish the services and related materials to enable the Government to properly configure and implement the technical requirements.

2.3.7.2. The Contractor shall provide application setup expertise and materials needed for use of the Contractor’s product. This support includes data attribute mapping, workflow configuration, business rule creation and management, role creation and mapping, user Interface ‘form’ mapping and technical setup, initial data load, error resolution stemming from configuration, setup and data load activities.

2.3.7.3. The Contractor shall ensure the Contractor’s product and, by extension, the FLITES product comply with architectural guidelines and standards.

2.3.7.4. The Contractor shall deliver configuration materials and supporting documentation. (A002, DI-MISC-80508B, Technical Report for Study/Services; A006, DI-ILSS-80872/T, Training Materials).

2.3.8. Audit Readiness

2.3.8.1. The Contractor shall provide support for design, document, and implement programmatic, functional, and technical compliance and controls in accordance with Air Force Instruction 17-101, RMF methodology for Air Force Information Technology.

Contractor support shall include applicable controls noted in applicable guidance/governance and technical requirements, e.g., Financial Improvement and Audit Readiness (FIAR) Information Technology Control Guidance. (A002, DI-MISC-80508B, Technical Reports for Study/Services)

2.3.8.2. The Contractor shall provide support to enable the IPO to execute and support financial and system audits on demand. (A009, DI- IPSC-81440A/T, Software Test Report)

2.3.8.3. The Contractor shall ensure the Contractor’s product complies with Audit requirements.

2.3.8.4. The Contractor shall support Audit Readiness reviews as requested in prioritized Jira stories.

2.3.8.5. The Contractor shall generate system level audit readiness documentation and supporting materials as identified in prioritized agile stories (A002, DI-MISC-80508B, Technical Reports for Study/Services).

2.3.8.6. The Contractor shall remediate errors and omissions based on audit findings related to the Contractor’s product.

2.3.8.7. The Contractor shall advise the IPO by identifying and/or solving audit readiness issues before or as they occur.

2.3.9. Development Support

2.3.9.1. The Contractor shall utilize agile methodologies IAW the IPO sprint teams and the technical requirements to support FLITES development.

2.3.9.2. The Contractor shall provide development support to include identifying all development work to be performed by the Contractor. Development work shall be applied directly to the Contractor’s product, through use of the SDK, or a combination thereof. (A002, DI-MISC-80508B, Technical Reports for Study / Services; A006, DI-ILSS-80872/T, Training Materials; A007, DI-IPSC-81442A, Software Version Description; A008, DI- IPSC-81439A/T, Software Test Description; A009, DI-IPSC- 81440A/T, Software Test Report)

2.3.9.3. The Contractor shall assist in design, build/configure, test and deliver operational capabilities, features or functions when changes to the Contractor’s product is applicable.

2.3.9.4. The Contractor’s deliverables, e.g., Contractor’s product, platforms and services, shall conform to the Section 508 AFI 33- 393 and DoD standards.

2.3.9.5. The Contractor shall conduct requirement, code, and user acceptance walkthroughs and applicable agile ceremonies when they apply to the Contractor’s product modifications.

2.3.9.6. The Contractor shall execute all work in accordance with the agile delivery methodology and workload prioritization established by the FLITES Product Owner(s) and Proxy Product Owner(s).

2.3.9.7. The Contractor shall remediate all test and security findings when related to the Contractor’s product.

2.3.9.8. The Contractor shall adhere to applicable standards and guidelines regarding architecture, integration and interoperability, CI/CD pipeline management and tool use.

2.3.9.9. The Contractor shall deliver supporting architectural, test, training and other product supporting artifacts for the Contractor’s product. (A002, DI-MISC-80508B, Technical Report – Study/Services; A006, DI-ILSS-80872/T, Training Materials; A007, DI-IPSC-81442A, Software Version Description; A008, DI-IPSC-81439A/T, Software Test Description; A009, DI-IPSC-81440A/T, Software Test Report).

2.3.9.10. The Contractor shall develop test scripts in JUnit (Java), Selenium, and other automated test software packages, in coordination with developers, to test the FLITES product developed using the Contractor’s product.

2.3.9.11. The Contractor shall utilize best practices in implementing these scripts with test driven development orientation.

2.3.9.12. The Contractor shall transition these test scripts to Selenium WebDriver and maintain them as new functionality is implemented.

2.3.9.13. The Contractor shall configure Selenium scripts to run on AWS within Cloud 1 (C1) utilizing test automation in coordination with the Platform Team.

2.3.9.14. The Contractor shall leverage Selenium IDE and Grid when applicable to generate test results.

2.3.9.15. The Contractor shall convert existing test scripts into Selenium scripts to be executed in an automated fashion.

2.3.9.16. The Contractor shall advise of methods for extracting test results into a data repository for reporting and analysis.

2.3.9.17. The Contractor shall perform failure analysis (and develop automated reporting) to give developers clear direction to patch issues.

2.3.9.18. The Contractor shall develop test scripts in JMeter, and other automated test software packages, for performance and capacity testing, providing guidance to the Platform Team on performance improving measures.

2.3.9.19. The Contractor shall be familiar with Jira and Agile principles for project tracking and engagement.

2.3.9.20. The Contractor shall provide documentation of technical design and implementation decisions associated with these test tools in the Jira stories.

2.3.10. Project Coordination Support

2.3.10.1. The Contractor shall conduct clerical and administrative program support including monitoring labor hours by resource and labor categories, preparing program reports, documenting details for monthly invoicing, facilitating the onboarding/offboarding of vendor resources, and managing contract deliverables.

2.3.10.2. The Contractor shall provide support to the Government.

2.3.10.3. The Contractor shall track, assemble, and compile accountable hours by resource and labor category.

2.3.10.4. The Contractor shall manage hourly reporting against budgets and forecasts.

2.3.10.5. The Contractor shall prepare ongoing program performance reports.

2.3.10.6. The Contractor shall liaise with, preparing backup for and directly working with One Network Finance and the Government team.

2.3.10.7. The Contractor shall maintain and report program budgets, forecasts, resources, contract management, timesheet compliance and tracking, and program operations.

2.3.10.8. The Contractor shall act as liaison between multiple parties / stakeholders withing the Program Team Organization.

2.3.10.9. The Contractor shall provide project administrative duties with resource planning / assignments, onboarding / offboarding, scheduling, and Statement of Work tracking, approvals, and storage.

2.3.10.10. The Contractor shall Collect and prepare data input for CDRLs, monthly invoice details / reporting, sub-contractor / small business reporting, financial reporting, and executive briefings.

2.3.10.11. The Contractor shall coordinate with One Network Accounting / FLITES COR for invoice processing, payment / receivable processing, and purchase order preparation.

2.3.10.12. The Contractor shall assist with compiling artifacts for tracking and management project performance.

2.3.10.13. The Contractor shall estimate, track, manage, and report travel expenses.

2.3.10.14. The Contractor shall estimate, track, manage, and report other direct cost.

2.4. Travel

The Contractor shall identify required travel and estimate expenses. All travel shall be in accordance with DoD Joint Travel Regulations and approved by the IPO.

3. Documentation/Deliverables

The Contractor shall provide the necessary documentation to support configure, develop, integrate, deploy, sustain and maintain FLITES.

3.1. The Contractor shall provide monthly expenditure reports for Government visibility into expenditures for labor, materials, travel and other contract charges.

(A001, DI-FNCL-80331A, Funds and Man-hours Expenditure Report).

3.2. The Contractor shall produce and deliver any requested technical information using the Technical Report for Study/Services. (A002, DI-MISC-80508B, Technical Report for Study/Services)

3.3. The Contractor shall produce and deliver any requested presentation materials.

(A003, DI-ADMN-81373, Presentation Materials)

3.4. The Contractor shall produce and deliver any requested computer software information for the Contractor’s product. (A004, DI-AVCS-80700A, Computer Software Product End Item)

3.5. The Contractor shall develop and maintain a Data Accession List (DAL) that includes data referenced within the PWS and all existing data, internally generated data, and computer software used by the Contractor to develop, test, and manage the program and not otherwise delivered. The Contractor shall provide the Government access to all electronically available DAL items, e.g., reports, documents, spreadsheets, charts, upon their inclusion in the DAL. (A005, DI- MGMT-81453B, Data Accession List)

3.6. The Contractor shall produce and deliver any requested training materials. (A006, DI-ILSS-80872/T, Training Materials)

3.7. The Contractor shall produce and deliver software version information for all deliveries of the Contractor’s product. (A007, DI-IPSC-81442A, Software Version Description)

3.8. The Contractor shall produce and deliver software test plans, approaches, and data for all deliveries of the Contractor’s product. (A008, DI-IPSC-81439A/T, Software Test Description)

3.9. The Contractor shall produce and deliver software test reports, approaches, data and results for all deliveries of the Contractor’s product. (A009, DI-IPSC- 81440A/T, Software Test Report)

4. Other Direct Costs

All Other Direct Costs (ODC) shall be on a cost reimbursable basis. The Contractor shall identify required ODCs with an estimate for the same. The Contractor shall request approval to incur ODCs from the Contracting Officer (CO) in writing by providing current quotes.

5. Foreign Nationals

The Contractor shall not involve any foreign national (resident aliens exempt) in work performed under this Statement of Work. The Contractor shall obtain an export authorization in accordance with 22 CFR 124 and 125 and approved through the Procurement Contracting Officer for any foreign national involvement.

6. In/Out Processing

The Contractor shall ensure all Contractor personnel in-process with the unit security manager/information systems security officer on the first duty day in the Government activity and out-process with the unit security manager/information systems security officer no later than (NLT) the period of performance end date of this task order or no later than the last duty day in the Government activity, whichever occurs first. When the Contractor obtains knowledge that a Contractor team member is no longer going to be supporting the program, the Contractor shall notify the COR and PM within 3 business days of obtaining that knowledge, if possible. The team member will then follow procedures IAW AFFARS 5352.242-9001 Common Access Cards (CAC) for Contractor personnel to turn in their CAC card. This process will facilitate review of contractual security requirements, verification of personnel security clearances or investigations, issuance/retrieval of CACs, issuance/termination of computer accounts and building accesses.

7. Acronyms

AF Air Force API Application Programming Interface ATO Authorization to Operate BOM Bill of Material C1 Cloud 1 CAC Common Access Card CBT Computer Based Training CDM Capability Delivery Manager CDRL Contract Data Requirements List CI/CD Continuous Integration/Continuous Delivery CO Contracting Officer COTS Commercial-off-the-shelf CTR Contractor DAL Data Accession List DBA Database Administration DNS Domain Name System DoDC Defense Core FIAR Financial Improvement and Audit Readiness FLITES Foundational Logistics Information Technology Enterprise System IAW In accordance with IDIQ Indefinite Delivery, Indefinite Quantity IL-2 Impact level 2 IL-4 Impact level 4 ILS-S Integrated Logistics System – Supply IPO Integrated Program Office ISVI Information Systems Vulnerability Information L&P Local Manufactured and Local Purchased LDAP Lightweight Directory Access Protocol LMS Learning Management System MDM Master Data Management NLT No later than OCSP Online Certificate Status Protocol ODC Other Direct Costs OOTB Out of the Box PKI Public Key Infrastructure PLT Platform

PNSSR Part Number Supply Support Request QASP Quality Assurance Surveillance Plan RMF Risk Management Framework SCC Supply Chain Core SDK Software Development Kit PWS Performance Work Statement WSSP Weapon System Support Program