Draft Performance Work Statement (PWS) revised 20261020_1.pdf

Draft

Performance Work Statement (PWS)

20 October 2026

Tactical Integration Platform

1. Introduction & Background

Headquarters United States Special Operations Command (HQ USSOCOM), Special Operations Forces Acquisition, Technology, and Logistics (SOF AT&L), requires an integrated contracting vehicle to rapidly discover, assess, prototype, integrate, test, and field mission‑relevant technologies and software-intensive capabilities across multiple Program Executive Offices and operational contexts. This contract vehicle addresses needs spanning Joint Acquisition Task Force (JATF) research and experimentation, PEO SOF Digital Applications (SDA) digital applications platform services, and PEO Tactical Information Systems (TIS) system-of-systems (SoS) integration, while ensuring cybersecurity Risk Management Framework (RMF) compliance and market analytics to monitor, evaluate, and incorporate commercial capabilities.

A common platform-as-a-service (PaaS) environment is required near MacDill AFB enabling collaboration among traditional and non-traditional vendors, users, and government program teams; an integration facility supporting interoperability, security, performance, and resilience across independent systems; and standardized RMF support to obtain and maintain Authorization to Operate (ATO) across programs.

2. Purpose

Establish a single contract vehicle to:

1. operate and evolve collaborative platform environments (unclassified through Classified),

2. integrate complex tactical information systems,

3. conduct research, development, prototyping, and experimentation,

4. provide engineering services,

5. deliver continuous RMF and cybersecurity support.

3. Scope

The contract vehicle covers mission support platform services, integration facility operations, engineering support services, cybersecurity RMF, including facilities, network connectivity, hardware/software support, data access coordination, documentation, and delivery of technical findings, all aligned to USSOCOM priorities and security requirements.

4. Functional Areas & Tasks

4.1 FA1 – Mission Support Platform (PaaS) & Collaborative Environments

Objective: Provide and sustain collaborative development environments with dedicated access to Commercial, SOFNET‑U, SOFNET‑S, and where authorized, classified networks; enable vendor/government/user collaboration, testing, integration, and configuration across classification levels.

Key Requirements (representative):

Location/Access:

Platform within five miles line of sight maximum distance to HQ USSOCOM at MacDill AFB;

Platform as a Service minimum operating hours 0700–1800, Mon–Fri (NOTE: Reason for the five miles is due to current limitation of tactical equipment that requires to be supported by the Government). The required minimum service level of support includes the necessary management, security, and resources to maintain the operation of the platform, security and logistics. There may be such times during extended exercise or evaluation periods that the PaaS will need to be open before or remain open after the minimum day/hours. These times should be considered on a case-by-case basis, approved by the Government, and coordinated with the contractor in advance of the time of execution.

Ensure 24 hours a day / 7 days a week facility access is available to meet mission and real-world operational requirements by exception.

Connectivity: Utilize existing and/or future USSOCOM‑approved direct connectivity (i.e., NIPR, SIPR, SOCRATES, etc.); provide line-of-sight radio/satellite antenna access as required for testing.

Workspace Capacity: Classified spaces for program teams (up to ~75 personnel) and unclassified vendor areas (up to ~150), ADA-compliant, facility clearance maintained. (NOTE:

Estimated required total workspaces anticipated are around 225).

Hardware/Software: Workstations for SOFNET‑U/S; VTC; server/switch/route hardware;

video wall; HPC; 3D prototyping equipment; licensing for needed applications.

Facility Management: Operations Asset intake, labeling, configuration management, interoperable wire connectivity, vendor development environment, segregated networks.

Dedicated personnel for prototyping coordination with the Area of Responsibility (AOR) and management of lab(s).

Meetings: Contract kick‑off, TIMs, monthly task/technical updates; minutes and action tracking required.

Security: Space shall satisfy the requirements to maintain a proper facility clearance. This includes implementing changes to the space to ensure secure spaces do not provide visual or audio bleed, badging and alarms are properly configured, and unauthorized access is not permitted. Additionally, proper procedures should be established and well published for any users within the secure spaces.

4.2 FA2 – Integration Facility & SoS Interoperability

Objective: Operate a cutting‑edge integration test platform (open and operationally representative environments) to verify communication, data exchange, security/privacy, performance/scalability, resilience/redundancy, emergent behaviors, and change/configuration management across PEO Tactical Information Systems (TIS) programs. Provide specialized support to cover all aspects of integration within the TIS portfolio.

Key Requirements (representative):

Colocation near HQ USSOCOM, (maximum 5 miles line of sight distance) DSCA‑approved secure location for classified network termination and processing (e.g., SOFNET‑S).

Secure Areas: classified room/area guarding against electronic surveillance and data leakage; direct connectivity to USSOCOM networks (SOFNET‑U/S/Gray/USBICES).

Install/Integrate/Maintain: One current version of each TIS Program of Record system;

IPN racks; flexible rack space for test/dev.

Documentation, Risk, Compliance: Maintain comprehensive test plans/cases/results and legal/regulatory compliance.

Staff Qualifications: At least half of integration personnel maintain DoD 8570.01‑M IAT Level II requirements.

Deliverables/Hours: Monthly Status Reports (MSRs); meeting minutes; After Action Review (AARs); trip reports; managed service availability 0700–1800 Mon–Fri with case‑by‑case extended hours.

4.3 FA3 – Engineering Support Services

Objective: Provide specialized engineering resources (software, electrical, mechanical, hardware, principal engineer) to design, prototype, integrate, test, and develop operational capabilities responsive to evolving mission needs.

Representative Labor Categories & Duties:

Senior Software Engineers — architecture, interoperability, metrics/process improvement; classified eligibility.

Software Engineers — cloud‑native solutions; design/coding/testing; classified eligibility.

Senior Electrical Engineer — trade‑offs; requirements; test strategy; classified eligible.

Mechanical Engineer — design/fabrication/test; classified eligibility.

Hardware Engineer — research/design/specs; project leadership; classified eligibility.

Principal Engineer SR — hybrid infrastructure/dev platforms; Kubernetes;

automation/APIs; classified cleared at start.

4.4 FA4 – Cybersecurity RMF Support

Objective: Deliver end‑to‑end RMF support to achieve and maintain ATO consistent with DoD, USSOCOM, and NIST guidance, including system categorization, control selection/implementation/assessment, RMF documentation, body‑of‑evidence artifacts, A&A coordination, continuous monitoring, risk analysis, and lifecycle integration of requirements.

5. Management, Meetings & Reporting

Kick‑off: Conduct a contract Kick‑off within 5–10 days of award (per contract specification).

Monthly Task/Technical Update Meetings: Hosted locally; agenda/materials provided in advance; minutes with attendees, action items, and priorities.

30/60/90‑Day Plan: Provide within 5 days of award as required by contract.

Monthly Status Reports (MSR): Accomplishments, plans, deliverables, issues/risks; due by 10th of each month (or as specified).

AARs, Trip Reports, Meeting Minutes: Per contract cadence (see Section. 10 – Contract

Data Requirement’s List (CDRLs))

6. Logistics

The Contractor shall provide comprehensive logistics support services to enable the efficient shipping, receiving, and material movement of associated task order equipment to and from off-site locations. This capability shall include coordination of transportation arrangements;

preparation, inspection, and verification of packaging and handling requirements; management of shipping documentation; and ensuring compliance with all applicable DoD, USSOCOM, and carrier regulations. The Contractor shall maintain continuous accountability and traceability of all government-furnished equipment (GFE) and program assets throughout the shipment lifecycle, to include monitoring in-transit visibility and ensuring proper documentation of receipts upon delivery.

Prior to initiating any outbound shipment, the Contractor shall obtain written approval from the Government COR. The Contractor shall ensure that all equipment is packaged, labeled, and transported in a manner consistent with program-specific logistics requirements, including evaluation of vendor packaging, coordination with lifecycle sustainment entities, and adherence to battery handling, IUID verification, and other material management standards as applicable to individual task orders.

The Contractor shall further support the return, redistribution, or staging of equipment for testing, fielding, refurbishment, or sustainment activities as directed under the contract.

7. Security Requirements

Security will be in accordance with the attached DD254. Performer team individual(s) supporting this task will be cleared at the CLASSIFIED level at the start of the task. Performer will require access to Communications Security (COMSEC), Sensitive Compartmented

Information (SCI) and Alternative Compensatory Control Measures (ACCM) material/information in performance of this effort. Contractor will require access to JWICS and SOCRATES computer systems only at government facilities. Contractor will require access to Commercial Solutions for Classified (CSfC) devices for use outside of cleared contractor facilities. Contractor is authorized to courier classified material/information up to SECRET in performance of official duties upon approval of and designation by the COR.

The contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor's management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The government shall be immediately notified of any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

The contractor shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

When no government employee or military member is available the contractor will be required to conduct security related functions (traditionally considered inherently governmental functions) such as opening/closing of security containers, end-of-day checks for processing and safeguarding classified information/material, and arming/de-arming USSOCOM Buildings, Secure Rooms, or SCIFs/SAPFs. If the contractor fails to properly conduct these responsibilities and a security violation/incident occurs, the government will have the option to take action against the company IA W U.S. law. In addition, the company will be responsible for reviewing preliminary inquiry reports for any security violation/incident for which an employee is found culpable and provide a written response to the GCA and Organizational Security Manager for actions taken against the employee.

In accordance with USDI & DOD CIO Memo, Security and Operational Guidance for Classified Portable Electronic Devices, dated 25 Sep 2015, cleared and trained DoD Contractors are authorized to use Commercial Solutions for Classified (CSfC) Mobile Devices outside of secure government and/or contractor facilities in order to effectively accomplish their mission.

Contractors requiring the use of CSfC devices will submit a USSOCOM IMT 33, CSJC Device User Agreement & Hand Receipt and an Authorization of Issuance (AOI) Memorandum to their Contracting Officer's Representative/Program Manager (COR/PM). Authorization of Issuance Memorandums must be endorsed at the 0-6 or GS/GM-15 level at a minimum. The COR/PM will forward the IMT 33 and AOI memo to their local Industrial Security Office. As acknowledged in the User Agreement, contractor will ensure safeguarding measures are adhered to, and necessary privacy is available to eliminate the possibility of compromise of classified information. HQ USSOCOM users will follow guidance as outlined in USSOCOM Manual 380- 19, Mobility and Wireless Communications. USSOCOM issued devices will not be introduced into cleared contractor facilities or be connected to SIPRNet other than through the USSOCOM network. Any misuse of the device outside of mission purposes or security incidents associated with or involving the device, may result in contractor's termination of access or subject the contractor to appropriate disciplinary or criminal action.

8. Place of Performance

Primary performance at Contractor facilities within the local commuting area of HQ USSOCOM at MacDill AFB, Florida, with tasks/deliveries at USSOCOM locations as specified in contract;

telework may be authorized as appropriate.

9. Travel

CONUS/OCONUS travel is anticipated and shall comply with the Joint Travel Regulations (JTR); TARs submitted to COR per timelines; trip reports due within 5 workdays of travel completion. Government assistance for billeting and transportation may be provided; compliance with TESA/SOFA when applicable.

Representative travel profiles (e.g., vendor integration, tech scouting, demos, user interviews) and departure locations (e.g., Tampa) may be identified in the contract.

10. Contract Data Requirements List (CDRLs)

A001 – Kick‑off Meeting Materials/Minutes (Due per the contract) A002 – 30/60/90‑Day Plan (Due within 5 days of award) A003 – Monthly Status Report (MSR) (Monthly; due NLT the 10th or per the contract) A004 – Meeting Minutes (Due NLT 5 workdays after meetings) A005 – After Action Report (AAR) (Due within two weeks after integration activities) A006 – Trip Reports (Due NLT 5 workdays post‑travel) A007 – Technical Reports/Findings (As requested / 30 days CoC) A008 – Financial Reports/Invoice Package (Monthly; per KO/COR instructions) A009 – Property/Inventory Reports (GFE/GFP/GFI/CAP) (As requested / periodic)

11. Government-Furnished Items & Information (GFE/GFP/GFI)

Government shall provide required equipment for platform operations and integration; contractor maintains asset records and use items only for performance; government provides maintenance or replacement for furnished equipment. Purchases require prior written KO/COR approval.

12. Materials & Contractor-Acquired Property (CAP)

Contractor may acquire materials/CAP (e.g., IT hardware/software accessories, raw materials, parts, subassemblies, fabrication supplies, WAN simulators, phones, 3D printers) with logs maintained; government retains title as applicable. Shipping/receiving support provided; COR approval required prior to shipping SOF systems.

13. Operations of Government Platforms and Vehicles

Contractor may be required to operate government vehicles (up to 2‑ton/24‑ft box truck), pallet jacks, and participate in maritime/tactical platforms or aircraft; operators must be qualified, unimpaired, and licensed. UAV operations must comply with FCC regulations (e.g., 47 CFR Parts 87/95) and other governing rules.

14. Intellectual Property & Government Rights

Government requires Government Purpose Rights (GPR) for five (5) years, thereafter unlimited rights; for non‑COTS software where GPR cannot be provided, require perpetual enterprise licenses supporting unlimited distribution/modification/use without additional fees beyond original license cost. Technical data and software must include appropriate distribution statements (e.g., Distribution D) and rights sufficient for government sustainment with third parties.

15. Special Contracting Requirements

Contractor shall not release/disclose project information without KO/COR written permission at least 21 days prior, with specifics on requester, timing/method, and content; vendor‑neutral posture required where applicable (e.g., no VAR sales during certain platform support periods).