UAI Draft PWS 14 Dec 2023.pdf

PERFORMANCE WORK STATEMENT (PWS) - DRAFT

Universal Armament Interface (UAI)

PART 1

GENERAL INFORMATION

1. GENERAL:

1.1. Description of Services/Introduction: The Contractor shall collaborate with government and industry entities as needed to provide system engineering and program management services and products to maintain and advance the Universal Armament Interface (UAI) as specified in this Performance Work

Statement (PWS). Performance shall include proposal, assessment, development, and implementation of changes to the areas of the UAI Core Documents (CD) and Formal Certification Document Set (FCDS), as called for in the UAI Interface Control Plan (ICP), and the associated Certification Tools (CT). The

Contractor shall also provide familiarization and UAI technical support as detailed in Section 5 below.

The Contractor shall leverage a broad-based expertise and knowledge of platform and stores systems to perform the task in this PWS.

1.2. Background: UAI was initially developed by the United States Air Force (USAF) in 2004 and now defines a standardized specification and method of integrating MIL-STD-1760 and AS5725 Miniature

Mission Store Interface (MMSI) guided weapons independent of platform Operational Flight Program

(OFP) update cycles. The primary components of UAI include the UAI ICP, CDs, FCDS, Launch

Acceptability Region (LAR) Tool, Mission Planning (MP) Software, and System Integration Laboratory

(SIL) and MP Certification Tools (CT). UAI provides standard data-driven interfaces and processes that increase interoperability and streamline the weapon system integration process.

1.3. Objectives: The Contractor shall produce a comprehensive and consistent body of technical specifications and hardware/software products that maintain backward compatibility for existing UAI compliant platforms and stores. At the same time, the technical specifications and hardware/software products, must continually advance to effectively incorporate new and evolving weapon system capabilities.

1.4. Scope: The Contractor shall perform development, and configuration control and management, of the

UAI technical specifications and hardware/software. The Contractor shall perform testing and formal qualification of UAI developed hardware/software. The Contractor shall obtain working agreements, data agreements, and licenses, as needed, to perform the scope of work in this PWS.

1.5. Period of Performance: The period of performance shall be for one (1) Base Period of 12 months, and four (4) 12-month options. The Period of Performance reads as follows:

Base

Option I

Option II

Option III

Option IV

1.6. General Information:

1.6.1. Quality Control: The Contractor shall utilize existing quality control programs in place during execution of this PWS.

1.6.2. Risk Management Framework: The Contractor shall support the development/update of RMF

Supporting Certification Documentation (SCD) as specified in the RMF Security Authorization

Package item.

1.6.3. Security Strategies: The Contractor shall adhere to all security strategies and requirements as stated in the RMF Security Authorization Package SCD, Cybersecurity strategy documents and appropriate regulations including Department of Defense Instruction (DoDI) 8500.01, DODI 8510.01

(RMF), and AFI 17-101 (RMF for AF IT).

1.6.4. Operational Security: OPSEC is required to reduce program vulnerability from successful adversary collection and exploitation of critical information. The Contractor shall apply OPSEC throughout the contract. OPSEC surveys to measure the effectiveness of the OPSEC program will be conducted by the government as needed.

1.6.5. Place of Performance: The work effort under this contract shall be performed at a contractor’s facility, government facility, or a place designated by the Government as essential to conduct UAI business.

1.6.6. Assumptions: The quantity and complexity of tasking is not fully known at this time. Therefore, the scope of the activity for these tasks shall be limited to not require more than the number of engineers or engineering hours proposed for this effort, including the other tasks in this Performance

Work Statement, unless otherwise mutually agreed to by the Government and the Contractor.

1.6.7. Data Rights: The Government has unlimited rights to all documents/materials produced under this contract. All documents and materials, to include the source code of any software produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

PART 2

ACRONYMS

2. ACRONYMS:

CC Common Component

CCP Certification Compliance Plan

CD Core Documents

COD Corrections of Deficiencies

COTS Commercial-Off-the-Shelf

CSCI Computer System Configuration Item

CS Carriage System

CT Certification Tool

FCDS Formal Certification Document Set

FQT Formal Qualification Test

GFE Government Furnished Equipment

ICD Interface Control Document

ICN Interface Change Notice

ICP Interface Control Plan

JMPS Joint Mission Planning System

LAR Launch Acceptability Region

MMSI Miniature Munitions Store Interface

MP Mission Planning

OFP Operational Flight Program

PDA Proprietary Data Agreement

PPP Program Protection Plan

PS Platform Store

PWS Performance Work Statement

RFC Request for Change

SCD Supporting Certification Documentation

SIL System Integration Lab

SJICWG Super Joint Interface Control Working Group

SRS Software Requirements Specification

TAA Technical Assistance Agreement

UAI Universal Armament Interface

UPC Unique Planning Components

UPS Universal Platform Simulator

USS Universal Store Simulator

VDD Version Description Document

VMT Variable Management Tool

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, and SERVICES

3. GOVERNMENT FURNISHED ITEMS and SERVICES:

3.1. Equipment: The Government will provide the USG-owned UAI SIL certification tools to perform the required services on this PWS.

3.2. Website Access: The Government will provide the contractor access to government sponsored websites as needed to fulfill tasking in this PWS, including, but not limited to service portals and MP

Central.

3.3. The Government will provide facilities and processing needed for any classified meetings or processing required by the UAI Industry Team.

PART 4

CONTRACTOR FURNISHED ITEMS and SERVICES

4. CONTRACTOR FURNISHED ITEMS and RESPONSIBILITIES:

4.1. General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Part 3 of this PWS.

4.2. Secret Facility Clearance: The Contractor shall possess and maintain a SECRET facility clearance from the Defense Information Security Service. The Contractor’s employees, performing work in support of this contract where access to SECRET information is required, shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office. In the event the current security level for the effort changes, the Contractor and Government shall come to an agreement involving any needed changes; and will complete a contract MOD as necessary.

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

The following tasks shall be in support of domestic and/or international UAI activities, as necessary.

5.1. Program Management Tasks: The Contractor shall:

5.1.1. Provide the services and products required to develop, maintain and deliver a planning and control system which encompasses program scheduling, technical progress, and cost reporting.

5.1.1.1. Deliver a monthly Status Report due on the 25 th of each month.

5.1.1.2. Deliver a quarterly Contract Funds Status Report due on the 25th of each month.

5.1.1.3. Deliver an annual Contract Summary Report with draft due NLT 30 day before period of performance ends and final due NLT 15 days before contract ends.

5.1.2. Perform tasks for Contract Data Requirements List (CDRL) delivery.

5.1.3. Perform tasks associated with establishing future performance periods of this contract.

5.1.4. Travel to support Program Management Reviews (PMR) and other meetings, as coordinated with the Government. This includes four PMRs, up to two other domestic meetings and up to two other international meetings per base/option period. Meeting minutes shall be captured for these meetings and provided within 5 business days after the meeting. Briefing material, where applicable, shall be provided 3 business days prior to the meeting with a final deliverable within 5 business days of the meeting.

5.1.4.1. The intent of the PMR is to provide a more comprehensive and detailed analysis of program execution. The Contractor shall provide detailed insight into the following for the PMR, but is not limited to:

• Details on cost, schedule, and performance for each PWS section.

• Identified risks/issues/opportunities and planned Correction Actions

• Decisions required by USG to support execution

5.1.5. Support international cooperative activities by executing export licenses and entering into appropriate agreements to include Technical Assistance Agreements (TAAs) and Proprietary Data

Agreements (PDAs), as necessary to complete the tasks in this PWS.

5.1.6. Make provisions to support industry collaboration and associated structure, as required.

5.2. Systems Engineering Tasks

5.2.1. The Contractor shall provide systems engineering and weapon system technical expertise and products in support of the UAI program and support the Super Joint Interface Control Working Group

(SJICWG) in accordance with UAI-ICP-R03 (or newest). To perform these tasks the Contractor shall:

5.2.1.1. Leverage weapon system knowledge, UAI technical expertise, customer inputs and inputs from UAI developing/implementing industry program contacts to provide the UAI program a technical roadmap suitable for developing a ten-year plan for enhancements to UAI on a prioritized basis according to weapon system requirements and capabilities.

5.2.1.2. Assess and analyze Requests for Changes (RFCs) for technical impact and workload assessment to generate Interface Change Notifications (ICNs). Review proposed changes to the

Interface Control Documents (ICDs) and certification compliance plans during ICN development and after ICNs are distributed for review.

5.2.1.3. Generate ICNs that are compatible/interoperable with current UAI capabilities in platforms and stores.

5.2.1.4. Review and assess detailed platform and store UAI document submissions to advise on compliance with UAI ICDs.

5.2.1.5. Deliver revisions of the UAI Core Documents and FCDS per UAI-ICP-R03 (or newest), including but not limited to:

• Platform Store (PS) ICD

• PS Certification Compliance Plan (CCP)

• Mission Planning (MP) ICD

• MP CCP

• LAR Process Document

• LAR Requirements Document

• LAR CCP

• PS Certification Tool (CT) System Specification

• PS CT Hardware Requirements

• UPS SRS

• USS SRS

• MP CT System Specification

• MP CT SRS

• LAR Analysis and Inspection Requirements

5.2.2. The Contractor shall review/update the following, as needed, but no more than once per each base/option period:

- SIL & MP CT User Manuals

- LAR Tool Set & User Manual

- SIL & MP CT Anomaly Logs

- UAI SIL CT & MP CT System Specifications

- UAI SIL CT UPS & USS requirements, scripting and testing

5.2.3. The Contractor shall maintain the UAI SIL CT Fault Reporting and Monitoring database.

5.2.4. Support the following types of meetings: Integrated Product Team (up to 48 meetings per base/option period), and program specific document reviews/technical meetings (up to 8 domestic meetings and up to 6 international meetings per base/option period). The Contractor shall provide the following: One person for half of the IPT meetings and up to 2 persons for the other half of IPT meetings. Up to two persons for the program specific meetings, both domestic and international.

5.2.5. Provide technical assistance to programs implementing UAI and the UAI SJICWG, including technical interchanges via onsite meetings, email, and telephone conferences.

5.2.6. Coordinate, facilitate and provide attendance for up to two (2) domestic UAI SJICWG meetings, for each base/option period. Each contractor to provide up to five persons to support each SJICWG.

5.2.7. Generate and maintain working drafts of the CDs and FCDS that incorporate system released

ICNs.

5.2.8. Propose to the appropriate Chair(s) changes to the UAI core documents.

5.2.9. Assign and maintain codes assigned for system identification (e.g., mission store, fuse, seeker/sensors) to support UAI.

5.2.10. Maintain a list of systems that are using the UAI interface and those that are UAI certified and deliver informally to the Government as requested

5.2.11. Establish and exercise administrative and configuration control in the support of UAI core documents and other UAI system documents, to include archiving.

5.2.12. Ensure all ICNs are correctly compiled, formatted, entered into the tracking system, and distributed to the appropriate JICWG members.

5.2.13. Provide system documents, ICNs, IFMs, minutes, action items, and other JICWG documents to authorized organizations and/or teams upon request of the appropriate Chair.

5.2.14. Manage JICWG and CCWG meetings in accordance with UAI-ICP-R03 or newest.

5.2.15. Maintain a list of working group memberships and make available to the appropriate working groups.

5.2.16. The Contractor shall manage the UAI CDs and FCDS using systems engineering best practices that may include but are not limited to incorporating processes that involve the use of model-based systems engineering.

5.3. Workshare Tasks: The Contractor shall make provisions to support the following workshare tasks.

5.3.1. Systems Integration Lab (SIL) Certification Tool (CT) Tasks

5.3.1.1. SIL CT Hardware: The Contractor shall:

5.3.1.1.1. Provide services to repair and maintain UAI SIL CTs.

5.3.1.2. SIL CT Universal Platform Simulator (UPS): The Contractor shall:

5.3.1.2.1. Provide integration familiarization and support of the UPS software with implementing programs (up to 4 domestic meetings and up to 2 international meetings per base/option period).

5.3.1.2.2. Analyze, design, and generate technical specifications to incorporate Platform/Store

(PS) ICNs (to PS ICD and PS CCP) into the UPS Software Requirements Specification (SRS).

5.3.1.2.3. Incorporation of UPS SRS changes into the UPS Computer System Configuration

Items (CSCI), Variable Management Tool (VMT) and UPS Script Files.

5.3.1.2.4. Perform testing and Formal Qualification Test as necessary to deliver UPS CSCI, VMT and UPS Script File updates up to once per each base/option period. The FQT will incorporate engineering releases and ICNs system released as coordinated with the Program

Office.

5.3.1.2.5. Maintain the VMT.

5.3.1.2.6. Incorporate any fixes for defects that prevent an implementing program from utilizing the UAI SIL Cert Tool into the UPS.

5.3.1.2.7. Deliver source code, an installable executable and a Version Description Document

(VDD) with each release of the UPS.

5.3.1.3. SIL CT Universal Store Simulator (USS): The Contractor shall:

5.3.1.3.1. Provide USS software engineering, design, programming and testing.

5.3.1.3.2. Provide integration familiarization and support of the USS software with implementing programs (up to 4 domestic meetings and up to 2 international meetings per base/option period).

5.3.1.3.3. Analyze, design and generate technical specifications to incorporate Platform/Store

ICNs (to PS ICD and PS CCP) into the USS SRS and Algorithm Description Documents.

5.3.1.3.4. Analyze, design, and generate computer program code to incorporate Platform/Store

ICNs (to PS ICD and PS CCP) into the USS software.

5.3.1.3.5. Analyze, design, and generate computer program code fixes for software defects that prevent an implementing program from utilizing the UAI SIL Cert Tool USS.

5.3.1.3.6. Release fixes (as required) on a limited basis as a CSCI engineering release.

5.3.1.3.7. Perform testing and FQTs as necessary to deliver USS CSCI up to once per each base/option period. The FQT will incorporate all current engineering releases and all ICNs system released prior to a cut-off date as coordinated with the Program Office.

5.3.1.3.8. Provide the USS in usable condition as a test asset to be interoperable with the UPS.

5.3.1.3.9. Maintain the User Manual addendum on USS setup and use of store profiles of various configurations for unique platform PS CCP testing, USS/Carriage System (CS) integration in Platform and CS SILs.

5.3.1.3.10. Deliver source code, an installable, executable file, and a VDD to the UAI Program

Office for FQT and Engineering releases of the USS CSCI.

5.3.1.3.11. Incorporate any fixes for defects that prevent an implementing program from utilizing the UAI SIL Cert Tool into the USS.

5.3.1.3.12. Maintain the status of Government Furnished Equipment (GFE) and report status annually.

5.3.2. Mission Planning (MP) Certification Tool (CT): The Contractor shall:

5.3.2.1. Provide MP software engineering design, computer program source code and installable executable for the MPCT software in response to approved changes to the MP ICD and MP CCP, authorized Corrections of Deficiencies (CODs) resulting from anomalies/recommendations reported by the MPCT users, changes to the Joint Mission Planning System (JMPS) framework, changes to the Next-generation Open Mission Systems (NOMS) framework, and changes to the

UAI Common Component (CC).

5.3.2.2. Perform the systems analysis design and programming tasks necessary to integrate the UAI

MPCT software with the JMPS framework, NOMS framework, and other known MP frameworks, including but not limited to web services.

5.3.2.3. Perform analysis design and computer programming integration of the UAI MPCT with newly developed platform Unique Planning Components (UPCs), newly developed store UPCs, and the UAI CC.

5.3.2.4. Perform testing and system level integration of the MPCT with the newly developed UPCs and the UAI CC and resolve questions and anomalies that arise in compliance tests of the newly developed UPCs and the UAI CC to certify they are compliant with the UAI MP ICD.

5.3.2.5. Deliver up to one (1) Engineering Release and one (1) Formal Release of the UAI MPCT as directed by the UAI PO per year. Provide Development Builds as requested by the UAI PO to support implementing programs.

5.3.3. UAI Common Component (UAI CC)

5.3.3.1. Main Software Development: The Contractor shall:

5.3.3.1.1. Implement software changes corresponding to changes to the UAI MP ICD, including new capabilities, maintenance and fixes or improvements. Perform FQT and deliver software releases.

5.3.3.1.2. Develop and maintain software compatibility and interoperability with all operating system and MP frameworks as required by implementing programs within the UAI MP JICWG.

5.3.3.1.3. Generate and implement test program code to fix any software defects that prevent an implementing program from utilizing UAI CC.

5.3.3.1.4. Support the development/update of the Risk Management Framework (RMF).

5.3.3.1.5. Comply with the latest JMPS and NOMS business and technical rules.

5.3.3.1.6. Implement Security Packs, Patches, and/or Hot Fixes. Ensure during development that all commercial-off-the-shelf (COTS) operating systems, applications, and utilities are updated to the appropriate service packs, security patches, and/or hot fixes as directed by the

Government or duly designated representative.

5.3.3.2. XML Data Utility: The Contractor Shall:

5.3.3.2.1. Maintain the automated tool that updates the necessary XML documents from MIL-

STD-3014 for UAI CC MiDEF development and provide the data to fielded versions of the UAI

CC when MIL-STD-3014 is updated.

5.3.3.2.1.1. Implement and deliver changes to the UAI CC XML documents when MIL-STD-

3014 changes are received.

5.3.3.2.2. Deliver updates to fielded releases to replace Class Code data files when MIL-STD-

3014 is updated.

5.3.3.3. Technical Assistance: The Contractor shall:

5.3.3.3.1. Conduct integration tests against MP framework updates, as required, to support

Platform and Store Unique Planning Component (UPC) development.

5.3.3.3.2. Establish and maintain effective interaction with other MP developers and the

Systems Engineering and Integration Team (SEIT).

5.3.3.3.3. Advise Government sustainers on potential impacts to fielded software of future MP framework security patches.

5.3.3.3.4. Provide UAI technical expertise to the Mission Planning Community, to include but not limited to:

- Component Interface Control Working Group (CICWG)

- Deficiency Review Boards (DRB)

- Interface Control Working Group (ICWG)

- Enterprise Program Management Reviews (MPER/MPLPR)

- Component Test Working Groups

- Security and Information Assurance Requirements Management Team

- Security Working Group, Joint Requirements Board

- Systems Engineering and Integration Contract Integration Verification, Validation, and

Evaluation Integrated Product Team (SEIC IVV&E IPT)

- NATO Industrial Advisories Group (NIAG)

5.3.3.3.5. Participate in the UAI MP JICWG as the interface manager for UAI CC on behalf of the UAI Program Office in accordance with UAI-ICP-R03 or newest.

5.3.4. Industry Team Supporting Infrastructure: The Contractor shall:

5.3.4.1. UAI Web Site: The Contractor shall provide and maintain a Government-accessible UAI web site to meet the requirements of this PWS and in accordance with the following specifications:

5.3.4.1.1. Establish and maintain infrastructure (i.e., servers, software, etc.) to support the

Program Office, Industry Team, UAI Super Joint Interface Control Working Group (SJICWG), SIL CT Users, and domestic and international UAI Participants. The UAI SJICWG site shall be in accordance with the UAI-ICP-R03 or latest.

5.3.4.1.2. All data, to include government, industry team, foreign and program-specific (e.g., annexes, supplements, etc.) on the sites shall be limited to non-proprietary (government and public releasable), non-competition sensitive, and unclassified information.

5.3.4.1.3. Provision shall be made to allow foreign data to be stored separately from US-only data by a separate web-site instance (e.g., URL) such that each country could have a unique, consolidated site.

5.3.4.1.3.1. Contractor will provide UAI Participants the ability to share data with each other on the UAI website as required.

5.3.4.1.4. Provision shall be made on the site to support audit controls to capture transfer of data.

5.3.4.1.5. All website data shall be backed up and provided to the UAI Program Office at their request no more than 2 times per base/option period.

5.3.4.1.6. Access to the site(s) shall:

1. Follow a username and password access control with the passwords using Microsoft strong password rules or certificate.

2. Incorporate file and list access controls to support the Interface Control Process.

3. Document the access controls in an exportable file that can be made available for review. This document shall capture user and document / list access controls. Informal audits with respect to the document shall be performed as required.

5.3.4.2. UAI Team Collaboration Facility: The Contractor shall provide and maintain physical meeting facilities and associated facility support for the Industry Team to allow face-to-face collaboration environment for UAI Super Joint Interface Control Working Group (SJICWG)

Secretariat function and technical support independent of individual contractor facilities.

5.3.4.3. Meeting Arrangements: The contractor shall coordinate and enter into a contract for facilities for offsite meetings including Super Joint Interface Control Working Groups (SJICWGs) and other off-site (non-UAI Dayton facility) meetings as required or as directed via coordination with the UAI Program Office.

5.4. Chief Engineer: The Contractor shall serve as Chief Engineer of the UAI Industry Team.

5.5. Lead Program Manager: The contractor shall serve as Lead Program Manager of the UAI Industry

Team.