SEI Performance Work Statement.pdf

FA8629-22-R-5031

09 November 2021

SPECIAL WARFARE PROGRAM OFFICE

SYSTEMS ENGINEERING AND INTEGRATION

(SE&I)

PERFORMANCE WORK STATEMENT (PWS)

09 Nov 2021

Revision: 0

Prepared by

Special Warfare Branch ISR/SOF Directorate

Wright-Patterson Air Force Base

Page Intentionally Left Blank

REVISION PWS CHANGE ACTIVITY DATE

Table of Contents

1.0 PROGRAM OVERVIEW

1.1 Scope

1.2 Background

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS/DESCRIPTION OF SERVICES

3.1 Program Management

3.1.1 Key Personnel

3.1.1.1 Technical Integration Lead

3.1.1.2 Software Developer Lead

3.1.1.3 Training Staff

3.1.1.4 Cyber-Security Lead

3.1.1.5 Key Personnel Substitution

3.1.2 Subcontractor Management

3.1.3 Associate Contractor Agreements (ACA)

3.1.4 Non-Disclosure Agreements (NDAs)

3.1.5 Quality Management

3.1.6 Program Management Plan (PMP)

3.1.7 Risk Management

3.1.8 Integrated Master Schedule (IMS)

3.1.9 Post Award Conference (PAC)

3.1.10 Program Management Reviews (PMRs)

3.1.11 Monthly Status Report

3.1.12 Program Management Meetings

3.1.13 Finance

3.2 Lifecycle Systems Engineering

3.2.1 Technology Transition

3.2.2 Functional Baseline

3.2.3 Product Baseline

3.2.4 Operational Safety, Suitability, and Effectiveness (OSS&E)

3.2.5 Technical Management

3.2.6 Interoperability

3.2.7 Studies and Analysis

3.2.7.1 Continuous market research in support of SWAK modernization

3.2.7.2 Analyses

3.3 Software Development

3.3.1 Software Design and Development

3.3.2 Software Product Continuous Development

3.3.3 Development of New Software Suite Core

3.3.4 Software Change Request

3.4 Systems Integration

3.4.1 Integration of new capabilities SWAK

3.4.2 Human Systems Integration (HSI)

3.5 Buy, Try, Adapt, Decide

3.6 Configuration and Data Management

3.6.1 Configuration Management (CM)

3.6.2 Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)

3.6.2.1 In-Process Review

3.6.3 Request for Variance (RFV)

3.6.4 Deficiency Reporting (DR)

3.6.5 Data Management

3.7 Cybersecurity

3.8 Program Protection and Security

3.8.1 Program Protection Planning

3.8.2 Information Security

3.8.3 Operational Security

3.8.4 Anti-Tamper (AT)

3.8.5 Supply Chain Risk Management (SCRM) and Counterfeit Prevention

3.8.6 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.8.7 Software Assurance

3.9 Test and Evaluation (T&E)

3.10 Training Delivery Services

3.10.1 Training Guidance

3.10.1.1 New Equipment Training (NET)

3.10.2 Refresher or Part Task Training

3.10.3 Just-in-Time (JIT) Training

3.10.4 Instructor Qualification Standards

3.10.5 Training Device Integration

3.11 Procurement

3.11.1 SWAK End User Device procurement

3.11.2 Licenses

3.12 Transition-Out Services

3.13 Customer Support

3.13.1 Product Support Coordination with ICP

3.13.2 Help Desk Support

3.13.3 Field Service Representatives (FSRs)

3.13.4 Support to TACP Innovation Cells

3.14 Product Support Services

3.14.1 Transportation and shipping

3.14.2 Support Equipment

3.14.3 Item Unique Identifier/Identification (IUID)

3.15 Exercises and Demonstrations

3.16 Travel

3.17 Government Property (GP)

3.17.1 Government Furnished Property (GFP)

3.18 System Safety and Environment, Safety, and Occupational Health (ESOH)

3.18.1 System Safety

3.18.2 Subsystem Hazard Analysis (SSHA)

3.18.3 Hazardous Materials

3.19 Foreign Military Sales (FMS)

4.0 MEETINGS

ACRONYM LIST

1.0 PROGRAM OVERVIEW

1.1 Scope

This Performance Work Statement (PWS) defines the requirements for services required by the Air Force Life Cycle Management Center (AFLCMC) Intelligence, Surveillance, Reconnaissance and Special Operations Forces Directorate (ISR/SOF), Special Warfare (SW) Branch (AFLCMC/WISN), located at Wright-Patterson Air Force Base (WPAFB), Ohio (hereafter referred to as the Government). The Contractor will function as a single focal point to provide Systems Engineering and Integration (SE&I) support for the Special Warfare Acquisition Growth and Refresh (SWAGR), Guardian Angel (GA) and TACP Modernization (dismount solution only) programs. Customers of this effort: there are approximately 3,500 USAF SW operators assigned to Air Combat Command ACC/GA, ACC/TACP, Air Force Special Operations Command (AFSOC)/Special Tactics (ST), and Air Education & Training Command (AETC)/ Special Warfare Training Wing (SWTW). In addition to supporting the USAF, the SE&I contract will also provide support to SW Branch Foreign Military Sales (FMS) cases. The primary deliverable of this contract is services required to develop and sustain the system-of-systems known as the Special Warfare Assault Kit (SWAK).

The general requirements for this PWS include the following:

Program Management support Software Development services Lifecycle Systems Engineering support Systems Integration support Support for the Buy, Try, Adapt, Decide process (limited procurement of end-items) Configuration and Data Management support Cybersecurity support Program Protection and Security support Test and Evaluation support Training services Engineering Studies and Analysis Customer Support services to include support to TACP innovation cells Limited Product Support services Exercise and Demonstration support Travel EUD and software license procurement Management of Government Furnished Property System Safety and Environment, Safety and Occupational Health services Foreign Military Sales support Government meeting support Transition-Out services

1.2 Background

Since 2015, SWAK have been developed and delivered primarily via two contracts, known as Machine to machine (software development) (M2M) and Operational Control System (OCS).

This contract establishes a follow-on M2M software development capability as well as responsibility to integrate body-worn power and data management components, radios, and other peripherals that connect to the kit and fall within the SWAK cyber-security boundary. The SE&I contract will include procurement of End User Devices, and limited quantities of other components to support integration and assessments. Full production and fielding quantities of most radios and peripherals will be procured by other contracts after initial integration.

Requirements: The Battlefield Air Operations (BAO) Family of Systems (FoS) Capabilities Development Document (CDD) was validated in 2018, further expanding the scope of the AFSOC requirement to other AFSOC Special Tactics career fields beyond just JTAC roles, introducing new requirements for both the SWAK and other mission equipment. ACC-authored AF Form 1067s (requirements documents) for GA and TACP will also drive activity on this contract.

Prior efforts developed a Windows-based body-worn kit until 2016, then transitioned to an Android-based kit in 2017 using the Android-based TAK software core as the development and deployment platform (ATAK). Future requirements could include either transition to another operating system, or development between ATAK and other operating systems.

2.0 APPLICABLE DOCUMENTS

Applicable documents of the date shown form a part of this PWS to the extent specified herein.

If no specific issue or revision level is noted, the latest issue or revision level in effect at the time of contract award applies. In the event of a conflict between the documents referenced herein and the contents of this PWS, the contents of the PWS shall be considered the superseding requirement. Sub-tier documents referenced within the cited documents shall not be applicable to this PWS unless the sub-tier documents are specifically referenced within this PWS or otherwise noted. Sub-tier documents may be used for guidance only.

Document # Revision Date Title Paragraph Reference

Air Force Instructions

AFI 61-101 14 Mar 2013 Management of Science and Technology

3.2.1

AFI 91-202 AFGM

2021-01

15 Apr 2021 The US Air Force Mishap Prevention Program

3.18.1

Document # Revision Date Title Paragraph Reference

DoD Directives

DoD Directive 5230.25 Change 2 15 Oct 2018 Withholding Unclassified

Technical Data from Public Release

3.8

DoD Manuals

DoD Manual 5010.12 Change 1 31 Aug 2018 Procedures for the Acquisition and Management of Technical Data

3.8

DoD Manual 5200.01 Volumes 1-4 24 Feb 2012

DoD Information Security Program: Overview, Classification, and Declassification

3.8

DoD Instructions

DoD Instruction 2040.02 Change 1 31 Jul 2017 International Transfers of Technology, Articles, and Services

3.8

DoD Instruction 3200.14 Volumes 1-2 15 Oct 2018 Principles and Operational Parameters of the DoD Scientific and Technical Information Program (STIP)

3.8

DoD Instruction 4140.67 26 Apr 2013 DoD Counterfeit Prevention Policy

3.8

DoD Instruction 5200.08R Change 2 19 Oct 2020 DoD Physical Security Program

3.8

DoD Instruction 5200.39 Change 3 1 Oct 2020 Critical Program Information (CPI) Protection Within Research, Development, Test, and Evaluation (RDT&E)

3.8

DoD Instruction 5200.48 5 Oct 2021 Controlled Unclassified Information (CUI)

DoD Instruction 5230.24

Change 3 15 Oct 2018

Distribution Statements on Technical Documents

DoD Instruction 8320.04 Change 3 27 Aug 2019 IUID Standards for Tangible Personal Property

DoD Instruction 8510.01 Change 3 29 Dec 2020

Risk Management Framework (RMF) for DoD Information Technology (IT)

3.7

DoD Instruction 8582.01 9 Dec 2019 Security of Non-DOD Information Systems Processing Unclassified Nonpublic DOD Information

DoD Instruction 5200.44 Change 3 15 Oct 2018 Protection of Mission Critical Functions to Achieve trusted Systems and Networks

Other

DFARS Defense Federal Acquisition Regulation Supplement

Various

FAR Federal Acquisition Regulation

Various

AFMCI 63-1201 GM 21 Jul 2021 Implementing Operational Safety Suitability And Effectiveness (OSS&E) And Life Cycle Systems Engineering (LCSE)

3.3.3

MIL-HDBK-61A(SE) 7 Feb 2001 Configuration Management Guidance

3.6.1 3.6.2

MIL-STD-882E 11 May 2012 Department of Defense Standard Practice, System Safety

3.20.1 3.20.4

MIL-STD-1472H 15 SEP 2020 Department of Defense Design Criteria Standard:

Human Engineering

3.18.1

MIL-STD-2073-1E Change 4 2 Apr 2019 Department of Defense, Standard Practice for Military Packaging

3.15.3

NISPOM Rule 32 CFR Part

24 Feb 2021 National Industrial Security Program Operating Manual 32 Code of Federal Regulation Part 117

3.8

NISTIR 7622 Oct 2012 National Institute of Standards and Technology (NIST) Notional Supply Chain Risk Management Practices for Federal Information Systems

3.8

NIST Special Publication 800-53

Revision 5 Sep 2020 Recommended Security Controls for Federal Information Systems and Organizations

3.7

NIST Special Publication 800-160

Volume 1 21 Mar 2018 Systems Security Engineering:

Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems

3.7, 3.8

NIST Special Publication 800-171

Revision 1 Dec 2016 Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations

3.8

National Aerospace Standard (NAS) 411

4th Edition 30 Sep 2020 Hazardous Materials Management Program

3.20.4

TO 00-35D-54 1 Sep 2015 USAF Deficiency Reporting, Investigation, and Resolution

3.6.5

AFPAM 63-113 17 Oct 2013 Program Protection Planning for Life Cycle Management, 3.8

3.0 REQUIREMENTS/DESCRIPTION OF SERVICES

3.1 Program Management

The Contractor shall provide Program Management support to fully sustain (Software), manage, and modernize the existing SWAK. The Contractor shall lead the development and deployment of additional capabilities as directed by the Government.

3.1.1 Key Personnel

The following are the minimum personnel who shall be designated as “key”. The contractor shall propose appropriate labor categories for these positions. The Government does not intend to dictate the composition of the ideal team to perform this task order. Therefore, the Government encourages and will evaluate additional Key Personnel as proposed by the offeror. Key personnel positions shall remain assigned to the program for the duration of the contract.

Technical Integration Lead Lead Software Developer Training Lead and trainers Cyber-Security Lead

The Government desires that Key Personnel be assigned for the duration of the Task Order.

Desired attributes for all key personnel include:

Able to work in an environment of continuous change and short deadlines, Excellent customer service and communications skills both verbal and written, Experience with continuous process improvement practices.

3.1.1.1 Technical Integration Lead

The Technical Integration Lead shall meet the following minimum qualifications:

o Minimum 8 years managing complex integration efforts o PMP or equivalent Certification

The Contractor shall identify a Technical Integration Lead to serve as the key authority to manage the Integration tasks and processes identified in the PWS paragraphs 3.2-3.9.

The Technical Integration Lead shall provide oversight on Integration testing and evaluation, analyzing issues and deficiencies to improve operational processes and issuing recommendations for improvement.

The Technical Integration Lead shall work closely with technical personnel and apply project management procedures to ensure completion of system and performance requirements.

It is desirable that the Technical Integration Lead possess the following skills and attributes:

o Successfully integrated projects of similar size and scope, o Adept at evaluating and resolving difficulties and constraints in implementing complex solutions within Government networks, both CONUS and OCONUS, o Management and project task coordination, in programs similar in size and scope referenced under this PWS, for employees of various labor categories and skills, o Experience in presenting material to senior Government officials, o Demonstrated skill in managing projects within estimated cost while delivering on schedule, o Knowledge of Capability Maturity Model Integration (CMMI) Level III best practices, o Demonstrated knowledge of implementing project management principles.

3.1.1.2 Software Developer Lead

The Software Developer Lead shall meet the following minimum qualifications:

o Minimum 8 years of software development experience o Minimum 3 years leading a software development team

It is desirable that the Software Developer Lead possess the following skills and attributes:

o Successfully integrated software applications of similar size and scope, o Adept at evaluating and resolving difficulties and constraints in implementing complex solutions within Government networks, both CONUS and OCONUS, o Demonstrated knowledge and ability to manage, coordinate, and facilitate a team's effort in configuring and maintaining a DoD hosted application effectively and efficiently while adhering to DoD Policy and within the constraints of its operational environment such as the DIACAP Certification and Accreditation process, o Demonstrated knowledge of IT transformation practices similar to requirements of the solicitation, o Up-to-date knowledge of current and emerging network and infrastructure technologies, o Experience in presenting material to senior Government officials, o Knowledge of Capability Maturity Model Integration (CMMI) Level III best practices, o Knowledge of Information Technology Infrastructure Library (ITIL) best practices, o Knowledge of industry and Government best practices, and o Experience in communicating IT issues i.e. Data Warehouse, Infrastructure, Software.

o Certified SAFe 5 Agilist or similar certification o Certified Scrum Master (CSM) or similar certification o SAFe DevOps Practitioner (SDP) o SAFe Product Manager/Product Owner (SAFe PM/PO) o In-depth knowledge of ATAK and TAK Enterprise development

3.1.1.3 Training Staff

o The Training Staff shall meet the requirements outlined in paragraph 3.10.4.

3.1.1.4 Cyber-Security Lead

The Cyber-Security Lead shall meet the following minimum qualifications:

o Minimum 5 years of Information Systems Security Manager (ISSM) or Information Systems Security Engineer (ISSE) experience o Minimum 3 years of Risk Management Framework (RMF) for IT enterprise networks and/or Platform Information Technology (PIT) systems experience o Information Assurance Manager (IAM) or Information Assurance Technical (IAT) Level II Cybersecurity Certification, IAW AFMAN 17-1303, paragraphs 2.20, 5.6.5, 5.8, 6.7 and DoD 8570.01-M, paragraphs C3.4, C3.5, C4.4, C4.5 o Capable of leading/accomplishing all Cyber-related tasks in PWS paragraph 3.7 It is desirable that the Cyber-Security Lead possess the following skills, attributes and certifications:

o Knowledge/experience in implementing DevSecOps best practices o IAM and IAT Level III Cybersecurity Certification, IAW AFMAN 17-1303, paragraphs 2.20, 5.6.5, 5.8, 6.7 and DoD 8570.01-M, paragraphs C3.4, C3.5, C4.4, C4.5 o Experience in Information Technology (IT) networking and systems engineering o Capability to collaborate across multiple disciplines and communicate cybersecurity status with senior leadership and team stakeholders o Experience evaluating cybersecurity test reports and developing technical mitigations to develop Plans of Action and Milestones (POAMs)

3.1.1.5 Key Personnel Substitution

The Contractor shall provide personnel possessing the skills, knowledge, clearances and training to satisfactorily support SE&I contract capabilities. The contractor shall not replace any personnel designated by either the Government or the contractor as Key Personnel without the written concurrence of the CO. Prior to utilizing any personnel other than personnel specified in proposals in response to a TOR, the contractor shall notify the Government CO and the COR of the existing TO. This notification shall be no later than 14 calendar days in advance of any proposed substitution and shall include justification (including resume(s) and labor category of proposed substitution(s)) in sufficient detail to permit evaluation of the impact on TO performance. Substitute personnel qualifications must meet the requirements as defined in this PWS. If the Government CO and the COR determine that the proposed substitute personnel is unacceptable, or that the reduction of effort would be so substantial as to impair the successful performance of the work under the TO, the contractor may be subject to default action as prescribed by FAR 52.249-6 Termination (Cost Reimbursement) or FAR 52.249-8, Default (Fixed-Price Supply and Service). The Government reserves the right to evaluate the qualifications of all proposed substitutions of Key Personnel, and the Contracting Officer retains the sole authority to accept or reject any substitutions proffered by the contractor.

3.1.2 Subcontractor Management

The Contractor shall ensure that all tiers of subcontracts contain language that ensures compliance with all applicable requirements stated in this PWS. The Contractor shall inform of and invite the Government to all major supplier technical reviews.

3.1.3 Associate Contractor Agreements (ACA)

The Contractor shall enter into ACAs for any portion of the contract requiring joint participation with the Contractors identified in support of SE&I contract. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the performance of the SE&I contract. The agreements shall ensure the greatest degree of cooperation for SE&I while fulfilling the terms of the contract.

ACAs shall include the following information:

Identify all associate Contractors and their relationships Identify the program involved and relevant Government contracts of associate

Contractors Description of the associate Contractor interfaces by general subject matter Specify the categories of information to be exchanged or support to be provided Identify potential conflicts between relevant Government contracts and the ACA including agreements on protection of proprietary data and restrictions on employees Include expiration date (or event) of the ACA

A copy of the agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating Contractors.

The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate Contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government. All cost associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

The following are associate Contractors with whom agreements may be required:

Special Warfare Procurement Multiple-Award Contract (MAC) Primes; the SE&I Prime may have to share technical configuration information with MAC Primes for full-rate procurement of SWAK components through the MAC contract.

o Federal Resources, 235-G Log Canoe Cir, Stevensville, MD, 21666-2165, FA8629-20-D-5003 o WS Darley & Co, 325 Spring Lake Dr, Itasca, IL, 60143-2072, FA8629-20-D-o US21, Inc., 2721 Prosperity Ave Ste 300, Fairfax, VA, 22031-4341, FA8629-20- D-5053 o Atlantic Diving Supply, Inc. (d.b.a. ADS, Inc.), 621 Lynnhaven Pkwy Ste 160, Virginia Beach, VA, 23452-7383, FA8629-20-D-5054 o Tactical & Survival Specialties, Inc. (d.b.a. TSSI, Inc.), 3900 Early Rd, Harrisonburg, VA, 22801-9788, FA8629-20-D-5055 o Quantico Tactical, Inc., 9796 Aberdeen Rd, Aberdeen, NC, 28315-7742, FA8629- 20-D-5059 o Rapid Response Defense Systems, Inc. (d.b.a RRDS, Inc.), 12 Goodyear Ste 100, Irvine, CA, 92618-3764, FA8629-20-D-5060

Inventory Control Point (ICP) Primes; the SE&I Prime may need to keep the ICP Prime informed of configuration status and updates to fielded SWAK components and software.

o IAP Worldwide Services, Inc., 7315 N. Atlantic Ave. Cape Canaveral, FL, W15P7T-17-D-0146 Order W15P7T-20-F-0178

SW Technical Integration Support Center (TISC) Prime; the SE&I Prime may be required to push capability updates to the TISC and the TISC may need to provide technical information for upgrades that are common to the SE&I-developed SWAK system and the TISC-managed SAMS-ESA Kits.

o GDIT-ARMA Micro Weather Sensor (this sensor is currently being integrated with SWAK) o ISI

Device Manufacturer Purpose

Galaxy S7 Samsung EUD

Galaxy S9 TE Samsung EUD

Galaxy Tab Active 2 Samsung EUD/Training/Mission Planning

Galaxy S20TE Samsung EUD

Note 8 Samsung EUD

FZ-M1 (MK-1 and -2)/CF-19 Panasonic EUD/Mission Planning

TacROVER-p L-3 Video Data Link

TacROVER-e L-3 Video Data Link

Tactical Network ROVER (TNR) L-3 Video Data Link

AN/PRC-117G L3Harris Voice/Data Communications Radio

AN/PRC-152A L3Harris Voice/Data Communications Radio

AN/PRC-160 L3Harris Voice/Data Communications Radio

AN/PRC-161 ViaSat Voice/Data Communications Radio

AN/PRC-163 L3Harris Voice/Data Communications Radio

AN/PRC-167 L3Harris Voice/Data Communications Radio

Microlight RT-1922c Raytheon Data Communications Radio

Device Manufacturer Purpose

SAASM GPS Receiver Rockwell Collins (Raytheon)

Data Communications

OCS Kit Black Diamond Advanced Technologies

Power and Data Management

3.1.4 Non-Disclosure Agreements (NDAs)

The Contractor shall obtain NDAs with all applicable corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract.

3.1.5 Quality Management

The Contractor shall possess a certification for software development of Capability Maturity Model Integration (CMMI) Level 3 or better, or an equivalent. The Contractor shall demonstrate compliance with a quality management system using ISO 9001 (2015) or an equivalent.

3.1.6 Program Management Plan (PMP)

The Contractor shall develop a Program Management Plan (PMP) to use as a foundation for information and resource planning. The Contractor shall keep the PMP current and electronically accessible to the Government at all times. (A001, DI-MGMT-81797 “Program Management Plan”)

3.1.7 Risk Management

The Contractor shall ensure that risk management processes cover programmatic, cost, schedule, and technical risks and opportunities. The Risk Management Program shall identify, track, and report risks and develop risk reduction plans for SE&I efforts.

The Contractor shall work in conjunction with the Government to identify and analyze risks and report on the status of risk reduction efforts and monitoring plans that include steps to mitigate Medium and High Risks. Risks shall be identified in market research reports IAW paragraph

3.2.7 and associated reports. Technical and schedule risks shall be presented at Technical Interchange Meetings, Technology Transition Reviews, Test Readiness Reviews, and Program Management Reviews (PMRs). The projected cost impacts of each risk shall be presented at PMRs in addition to technical and schedule impacts. The Contractor shall include risks assessments and mitigation strategies as part of meeting agendas, briefings and meeting minutes.

(A002, DI-ADMN-81249C “Meeting Agenda”; A003, DI-ADMN-81250C/T “Meeting Minutes”; A004, DI-ADMN-81373/T “Presentation Material”; A005, DI-MISC-80508B “Technical Report – Study/Services”)

3.1.8 Integrated Master Schedule (IMS)

The Contractor shall create, manage, and maintain an overall IMS. The Contractor shall maintain and update the IMS to reflect Government approved changes in the Contractor’s detailed execution activities or schedule. The IMS shall include discrete activities of the Contractor. Any changes or updates shall be provided to the Government as they occur to the schedule. Any changes to contractual milestones within the IMS shall be made only after coordination with the Government and at the approval of the Contracting Officer. (A006, DI-MGMT-81861C/T “Integrated Program Management Data and Analysis Report (IPMDAR)”)

3.1.9 Post Award Conference (PAC)

The Contractor shall conduct a PAC at the Contractor's facility no later than (NLT) 30 days after contract award. The PAC shall introduce the key participants, identify points of contact and discuss all parties’ understanding of the scope of work. The purpose of this PAC is to ensure a common understanding between the Government and the Contractor of the overall contract requirements for SE&I and incorporate feedback and comments as part of their planning efforts.

The documents/information provided shall include, but is not limited to, the following:

Agenda Personnel Slides Meeting Minutes and Action Items

(A002, DI-ADMN-81249C “Meeting Agenda”; A003, DI-ADMN-81250C/T “Meeting Minutes”; A004, DI-ADMN-81373/T “Presentation Material”)

3.1.10 Program Management Reviews (PMRs)

The Contractor shall provide cost, schedule, and performance data to the Government for all task orders and delivery orders issued under this PWS at PMRs. A total of two (2) PMRs shall be held in each contract year. PMRs will typically be conducted at the Contractor’s facility. The Contractor shall be prepared to host virtual PMRs in the event of travel restrictions. The Contractor shall prepare agendas, briefings (to include design documentation) and minutes for the reviews. (A002, DI-ADMN-81249C “Meeting Agenda”; A003, DI-ADMN-81250C/T “Meeting Minutes”; A004, DI-ADMN-81373/T “Presentation Material”; A005, DI-MISC- 80508B “Technical Report – Study/Services”) The order of the following PMR topics can be re-arranged at the government’s discretion, as well as the actual topics, but should expect to include:

Within first 90 days of award o Kick-off/Initial PMR

Topics to be covered:

o Risk Management, Program Management, Contracting, Finance, Logistics, Engineering, Cybersecurity, and Tech Transition

3.1.11 Monthly Status Report

The Contractor shall provide a Monthly Status Report (MSR) tailored per CDRL instructions to the SE&I effort. (A007, DI-MGMT-80368A/T “Status Report”)

3.1.12 Program Management Meetings

The Contractor shall participate/facilitate/conduct the meetings detailed below. The Contractor shall provide the appropriate representation for all meetings.

Weekly Teleconference The Contractor shall conduct at least two (2) teleconference with the SWAK PM each week to provide the overall program status and identify any critical issues.

Monthly Status Meeting The Contractor shall facilitate monthly status meetings within the first five (5) business days of each month to provide the Government with status on the following items:

Overall program status Accomplished and planned activities by task area, including any identified issues and risks Notification of non-compliance with the software licensing policy Synopsis of on-going SWAK capability analysis and problem analysis reports Software configuration status Schedules and status updates to reflect current milestones Status on patches, releases, new versions, upgrades, etc. with Contractor’s IMS and brief content description Action items (open and closed within the past month) Previous month activities and planned activities by task area

This meeting may replace a weekly teleconference.

3.1.13 Finance

The contractor shall submit a Contract Funds Status Report detailing financial execution on all Cost-type efforts. (A008, DI-MGMT-81468A “Contract Funds Status Report (CFSR)”)

3.2 Lifecycle Systems Engineering

The Contractor shall design, develop, integrate, test, deliver, maintain, and modernize the SWAK at the direction of the Government. This includes updating End User Devices (EUDs) to current Maintenance Release installation provided by EUD’s manufacturer.

3.2.1 Technology Transition

The Contractor shall mature, productize and support the fielding activities associated with new hardware and software designated by the Government for inclusion into the current and future generations of SWAK. Any third-party software (open-source, freeware, etc.) that the Contractor intends to utilize/incorporate for the software baseline shall require Government approval.

Technology Transition products are typically Android Tactical Assault Kit (ATAK) compatible Plug-Ins and Applications sponsored by the Government as projects via various vehicles under Department of Defense (DoD) Technology Transfer Programs or Air Force Research Laboratory (AFRL) Technology Transition Programs such as Advanced Technology Demonstrations (ATDs). The SW Branch serves as the Transition Agent for multiple AFRL ATDs, as well as Small Business Innovative Research (SBIR) and Rapid Innovation Fund (RIF) in accordance with AFI 61-101, Management of Science and Technology, and AFLCMC/XZ, Guidance Memorandum Technology Transition Planning. These software products are generally higher priority requirements that augment or enhance the full spectrum of SW capabilities, and include the following:

Mission Planning Training Tactical Communications Mobility

Infiltration/Exfiltration Unmanned Systems Target Marking/Designation Mobile Weather Systems Visual Augmentation Personnel Recovery Technical Recovery Assault Zone Equipment

For Technology Transition software products the Guideline Entry Criteria are as follows:

Fully functional software product developed to a Technology Readiness Level of 4-6 Software Design Documentation to include software product specifications, software

(both source and executable), and any other technical data packages necessary for continued development and modifications to the software

Product Documentation to include software documentation (architecture, design, requirements, technical, user manuals), test reports (lab performance including comparisons to existing capability, user feedback), and listing of associated hardware

Relevant cost estimates identified for the product Unique security requirements identified for the product

3.2.2 Functional Baseline

The Contractor shall develop and provide configuration documentation satisfying or exceeding all the threshold requirements of the SWAK System Requirements Documents (SRDs). (A009, DI-SESS-82176 “Software Architecture Description (SWARD)”)

3.2.3 Product Baseline

The Contractor shall establish and maintain the product baseline for new SWAK components through delivery of a product Technical Data Package (TDP). Technical reviews are required at the beginning and end of a SWAK release cycle in conjunction with quarterly Technical Interchange Meetings (TIMs). (A010, DI-SESS-81000F “Product Engineering Design Data and Associated Lists”; A009, DI-SESS-82176 “Software Architecture Description (SWARD)”; A011, DI-IPSC-81442A “Software Version Description (SVD)”; A012, DI- IPSC-81435A “Software Design Description (SDD)”)

3.2.4 Operational Safety, Suitability, and Effectiveness (OSS&E) The Contractor shall support the establishment of OSS&E for all SWAK end-items.

Establishment shall include supporting the Government’s requirement to prepare OSS&E Baseline Documents for systems/subsystems/end-items prior to initial fielding releases, and/or subsequent modifications, necessary to document the information identified in Appendix A, Section 3.5 of AFMCI 63-1201. (A013, DI-MGMT-81453B “Data Accession List (DAL)”)

3.2.5 Technical Management

The Contractor shall support or conduct requirements reviews and technical Reviews for any new requirement to include integration efforts to the existing SWAK. Requirements for SWAK are gathered through the following, but not limited to, means:

Monthly stable build “black box”/functional testing by specific users with advanced access (SMEs, “super-users”, DT/OT entities who reflect the current using community, etc.)

SWAK User Group Conferences (quarterly – 2x in-person, 2x virtual) 1067 Requirements Documents Government approved Requirements Work Sheets (RWS)

The Contractor shall conduct Technical Interchange Meetings (TIMs) to review issues related to development, integration, testing, and sustainment of the new or modified capability. The Contractor shall be responsible for reviewing, providing scope (cost and schedule) and ability to put the required work on contract. The Contractor may propose holding reviews/meetings in conjunction with PMRs, Integrated Test Team (ITT) meetings, etc. The Contractor shall prepare agendas, briefings (to include design documentation) and minutes for the reviews. Technical baseline documentation shall be reviewed as applicable to each SWAK release cycle (paragraphs

3.2.2. and 3.2.3 above). (A002, DI-ADMN-81249C “Meeting Agenda”; A003, DI-ADMN- 81250C/T “Meeting Minutes”; A004, DI-ADMN-81373/T “Presentation Material”)

3.2.6 Interoperability

The Contractor shall ensure SWAK complies with DoD interoperability standards to include maintaining and gaining approval via GiG Technical Guidance Federation (GTG-F) of the system’s architecture models (DoDAF views) throughout the lifecycle.

3.2.7 Studies and Analysis

3.2.7.1 Continuous market research in support of SWAK modernization The Contractor shall perform continuous market research and studies (as directed by the government) of emerging concepts and technology alternatives to assist in identifying future capabilities for incorporation into SWAK. As a result of these studies, the Contractor shall produce Rough Orders of Magnitude (ROMs) with cost and schedule estimates. The basis for and results of any proposed effort shall be documented in a report. The identification of Trade- Offs and a Risk Assessment shall also be included in the report at program management reviews and as directed. (A005, DI-MISC-80508B “Technical Report – Study/Services”)

3.2.7.2 Analyses

The Contractor shall perform technical and engineering analyses of SW and conventional systems and end items (e.g. COTS/GOTS) technologies and concepts to include recommendations for integration. When alternatives exist, an Analysis of Alternatives shall be performed by the Contractor. Key design considerations are as follows:

Affordability Analysis Size, Weight, and Power (SWAP) Impacts Data Rights System Safety Environment, Safety, and Occupational Health (ESOH) Human Systems Integration (HSI) Open Systems Architectures Program Protection and Cybersecurity Reliability and Maintainability Critical Safety Item Diminishing Manufacturing Sources and Material Shortages (DMSMS) Interoperability and Dependency Packaging, Handling, Storage, and Transportation Technology Readiness Manufacturing Readiness Spectrum Impact Standardization Supportability Survivability (including CBRN) and Susceptibility Net-Ready KPP Compliance

3.3 Software Development

3.3.1 Software Design and Development

The Contractor shall develop, integrate, test and support fielding of Plug-Ins and Applications that are identified for future inclusion into the fielded SWAK Software Suite configuration baseline.

The Contractor shall employ a software development process that:

Enables rapid iteration Requires developers meet with end users, then start small and iterate quickly to deliver useful code Accept ~70% solutions in short time (months) and add functionality in future rapid iterations (weeks) Creates automated test cases/environments to enable continuous (and secure) integration and deployment to shift testing to the left Uses validated software development platforms that align with the TAK Enterprise’s development community and that permit continuous integration and evaluation Allows for purchasing/utilizing existing software where able to the benefit of the

Government (e.g., use of Git repos, Jira, Automated Testing tools, Fortify/Coverity, Visual Studio, etc.)

Uses modern software languages and operating systems (with all patches up-to-date) Incorporates Test and Evaluation into the development life cycle to facilitate DevSecOps

Provides easy and simple access to the Government, for contract deliverables, source code, build tools, test scripts, data

Uses Open Technology Development (OTD) to incentivize collaboration and transparency, which is consistent with federal source code policy – maximizing use of open standards, open source software and reuse of existing products

The Contractor shall support research, development, and maintenance of those software applications that augment, enhance, or support the capabilities of the SWAK Software Suite.

The Contractor shall update or provide system, test, and user documentation for the SWAK Software Suite. The Contractor shall provide the appropriate documentation for each application within the SWAK Software Suite or as an overarching document where applicable. The required documentation shall include the following:

Software Development Plan (SDP) Supplier’s Configuration Management Plan (SCMP) Software Architecture Description (SWARD) Interface Design Description IDD Software Version Description (SVD) Test Plan User guides Training guides

The Contractor shall maintain the current configuration baseline that preserves the integrity of the SWAK Software Suite. The Contractor’s processes shall be tailored based upon program requirements and in collaboration with the Government’s stated requirements.

The Contractor shall track all source code, and external dependencies of the source code, in a versioning system. The Contractor shall be able to recall the source code and its dependencies for any previous installation version. The Contractor shall track deficiencies, modifications and enhancements made to the SWAK Software Suite applications to account for software installation version differences. (A014, DI-IPSC-81427B “Software Development Plan (SDP)”; A015, DI-SESS-80858D/T “Supplier’s Configuration Management Plan”; A009, DI-SESS-82176 “Software Architecture Description (SWARD)”; A016, DI-IPSC-81436A “Interface Design Description (IDD)”; A011, DI-IPSC-81442A “Software Version Description (SVD)”; A012, DI-IPSC-81435A “Software Design Description (SDD)”; A017, DI-NDTI-80566A “Test Plan”; A018, DI-ILSS-80872/T “Training Materials”)

3.3.2 Software Product Continuous Development

The Contractor shall maintain (to include bug tracking, repair and testing) the currently fielded SWAK Software Suite and its associated Plug-ins. The SWAK Software Suite shall function on current SWAK operational hardware and support potential next-generation hardware platforms.

The Government will provide the Contractor with requirements which shall be developed within the multi-point release schedule (expected quarterly releases – 2 Engineering releases and 2 Fielded releases annually) derived from the SW Requirements Working Groups with the using

Commands. All changes to the fielded SWAK Software Suite shall be approved by the Government.

3.3.3 Development of New Software Suite Core

At the direction of the Government, the Contractor shall develop a new Software Suite Core in support of emerging needs of the SW using Commands, modernization of the SWAK, and modernization of the infrastructure and networks implemented to support the SWAK. The Government will provide the Contractor with requirements to perform research, development, design, testing and fielding of a new software core to support an operating system different than the existing operating system used with the SWAK Software Suite.

3.3.4 Software Change Request

The contractor shall document all government approved SCR’s using a proposed Agile Methodology.

3.4 Systems Integration

3.4.1 Integration of new capabilities SWAK

The Contractor shall integrate software applications, systems, subsystems, and components into the SWAK at the direction of the Government. The integration shall include all activities required to preserve the compatibility and interoperability identified in the applicable SWAK drawings, Department of Defense Architecture Framework (DoDAF) architectures, and the cyber security Authority to Operate (ATO). The Contractor shall coordinate with Original Equipment Manufacturer(s) (OEMs) when products procured from those sources require integration with the SWAK. The Contractor shall deliver an IDD and SVD to facilitate successful integration. (A016, DI-IPSC-81436A “Interface Design Description (IDD)”; A011, DI-IPSC-81442A “Software Version Description (SVD)”)

The contractor shall develop and implement a Development-Security-Operations (DevSecOps) methodology for the SWAK in accordance with commercial and DoD best practices to support the evolution of software development and systems integration processes for Assessment and Authorization (A&A). This requires supporting the transition from existing “As-Is” SWAK system development processes, to a “To-Be” DevSecOps approach to implement repeatable processes and enable continuous A&A objectives. The contractor shall align DevSecOps processes with multiple, external system development programs (i.e. software and hardware). In conjunction with DevSecOps processes, the contractor shall support digital engineering initiatives—utilizing risk assessment tools provided by the SW Branch and the Authorizing Official (AO) office—to support continuous assessment and monitoring IAW the Risk Management Framework (RMF). The DevSecOps methodology shall be utilized to maintain the existing SWAK ATO and documentation to support system updates/modifications, as well as to support future SWAK ATO cybersecurity risk assessments.

All integration activities shall be identified in the PMP, IAW Section 3.1.6 of the respective progress for all integration activities shall be identified and updated in the IMS, IAW Section

3.1.8 of this PWS. Upon request, the Contractor shall furnish evidence that supports cyber-security risk assessments and effective program protection IAW sections 3.7 and 3.8 of this

PWS.

3.4.2 Human Systems Integration (HSI)

The Contractor shall consider HSI impacts during program planning, design, and system modifications to optimize system performance and total ownership costs. The Contractor shall obtain approval from the Government prior to implementing design features with HSI impacts to ensure the system can be operated and maintained to provide the user with the ability to complete the respective mission sets. The contractor shall modernize SWAK to improve capability and operational suitability within the constraints of body-worn equipment and dismounted operating environments.

3.5 Buy, Try, Adapt, Decide

The Contractor shall support the Government in the Buy, Try, Adapt, Decide process. This process is unique to the SW Branch, with the objective to expeditiously determine if a commercially available item can meet a specific operational need of the warfighter when a solution is not currently fielded. For AFSOC ST-specific solutions, the Buy-Try-Adapt-Decide process may be coordinated by the Government through the SW TISC.

The “Buy” segment of the process requires the procurement of a COTS item in low quantity by the Contractor IAW section 3.18 of this PWS. As determined by the Government, the quantity procured shall serve to adequately support assessment of the COTS item’s performance against the requirements identified by the Government.

The “Try” segment refers to an Operational Utility Assessment (OUA), appropriately scaled, to characterize the performance of the COTS item against the Key Performance Parameters/Key System Attributes (KPPs/KSAs) established by the Government. As determined by the Government, OUAs shall include SW user representatives who will employ Tactics, Techniques, and Procedures (TTPs) consistent with the mission set for which the COTS item is intended.

The Contractor shall support the establishment of Concept of Operations (CONOPs) and assessment criteria, the determination of assessment readiness, the generation of data collection plans, the generation of a cybersecurity assessment, and deliver a summary report of the OUA performed. (A005, DI-MISC-80508B “Technical Report – Study/Services”)

The Contractor shall support the Government in the development of a Technology Readiness Assessment (TRA) of the COTS item. Based on the findings in the summary OUA report, this TRA may include a determination of the necessity of the COTS item to be modified or “adapted” for the item to be effectively employed IAW the CONOPs.

The “Adapt” segment refers to the required material modifications of the COTS item as stated in the TRA. At the direction of the Government, the Contractor shall coordinate with the OEM to modify the COTS item to achieve the KPPs/KSAs IAW the CONOPS. The Contractor shall develop a draft technical requirement set for an adapted version of the item and collaborate with the OEM to determine the feasibility of the modifications by establishing the cost, schedule and performance required to accomplish these modifications. Subsequent assessments shall be required to verify that the modifications have effectively achieved the performance of the COTS item against the KPPs/KSAs established by the Government.

When required, the Contractor shall support Government-provided Subject Matter Experts (SMEs) and assigned users who will collaborate to determine if the employment of the item necessitates any modifications to their TTPs. In the event that the COTS item is determined to meet the established requirements without modification, the “Adapt” segment of this process can be omitted, and the Government will move to the “Decide” segment of the process.

The “Decide” segment refers to the presentation of TRA findings to the originating requirements sponsor. The result of this presentation is to determine a positive or negative fielding decision for the COTS item to conclude the process. If a positive fielding decision is rendered, a procurement and fielding plan will be generated by the Government and a Delivery Order established on the SW MAC contract. In the event the new COTS item requires immediate fielding to CONUS and/or OCONUS units, at the direction of the Government, the Contractor shall deliver New Equipment Training (NET) IAW section 3.10.1 of this PWS. If a negative fielding decision is rendered, all documentation associated with the Buy-Try-Adapt-Decide process shall be delivered to the Government for retention. (A004, DI-ADMN-81373/T “Presentation Material”)

3.6 Configuration and Data Management

3.6.1 Configuration Management (CM)

The Contractor shall develop and maintain a Supplier’s Configuration Management Plan (SCMP) to control all aspects of the CM process using MIL-HDBK-61B as a guide and following the format of DI-SESS-80858D. The SCMP shall include event-based criteria for assumption of control of the CM process following acceptance by the Government of documents, designs or requirements. The SCMP shall include responsibilities for configuration identification, change control, data management, variances/waivers, audit plan, audits, interface management and subcontractor management.

The Contractor shall establish a process through the SCMP to ensure that configuration control is maintained on SWAK, and in functional, allocated and product baseline configuration identification documentation.

Change Control will be managed through periodic Configuration Control Boards (CCBs) for each Plug-In, build release and/or Configuration Item (CI) change. Configuration(s) shall not be changed without Government CCB approval.

The Contractor shall designate a CM representative to serve as a primary point of contact to the Government for all CM matters and be responsible for any subcontractor CM efforts. The Contractor shall notify the Government of any changes which affect the Contractor’s established CM process. The Contractor shall conduct, with the Government, a final system configuration baseline verification through the CCB process and Engineering Change Proposals (see PWS Para 3.6.2) prior to delivery of SWAK. (A015, DI-SESS-80858D/T “Supplier’s Configuration Management Plan”)

3.6.2 Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) Any Hardware (H/W) change to the SWAK which affects the form, fit, function, or interface shall be prepared as a Class 1 ECP. All Class I ECPs shall be dispositioned for implementation by the Government CCB. The Contractor shall notify the Government of all Class II ECP changes as required, including all substitute parts changes and documentation changes, through a Notice of Revision (NOR).

The Contractor shall submit ECPs to the Government for review, concurrence of classification and approval, including instances where the H/W change is carried out by a Subcontractor.