Performance Work Statement_SRT Mission Planning Software.pdf

PERFORMANCE WORK STATEMENT

FOR

Mission Planning Software

AT

DEA Special Response Team (SRT)

16 July 2026

Contents

SECTION I

DESCRIPTION OF SERVICES

1.0 General

1.1.1 Scope

1.2 Background

SECTION II

2.0 Task and Technical Requirements

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1

SECTION VI

6.0 Quality Control

6.1 6.2

SECTION VII

1.0 DEFINITIONS AND ABBREVIATIONS

SECTION I

DESCRIPTION OF SERVICES

1.0 General.

The Drug Enforcement Administration (DEA) Special Response Team (SRT) program provides specialized equipment and tactical expertise to support investigations and associated high-risk special operations conducted by DEA Special Agents and partner law enforcement agencies.

SRTs are tactical teams that strive to preserve life, ensure public safety, enforce the law, and assist with stabilizing communities impacted by illicit drug distribution. The use of trained tactical teams to perform high-risk enforcement operations can increase operational safety and success. The SRT program was established in 2016 to be DEA’s tactical response to high-risk domestic enforcement operations. There are currently 23 teams, one for each domestic field division, consisting of approximately 430 active certified personnel. To effectively support these operations and enhance the safety of law enforcement personnel and others, the SRT program requires a purpose-built, solutions-based software platform which will provide real-time visibility into the status of operations, support critical communication capabilities, and track essential training and personnel management information.

1.1.1 Scope. The contractor shall deliver a currently available, ready-to-install Mission Planning Software solution that complies with Department of Justice (DOJ) and Criminal Justice Information Services (CJIS) security standards. The software must automate tactical resource management, reduce human error in operations planning, and provide a unified operational view.

This scope encompasses software licensing, initial system integration, data synchronization with legacy warehouses, and user training.

The need for this operational planning software is urgent and compelling to ensure the safety of DEA enforcement personnel. The software must be currently available and ready to install within 14 days of contract award, to meet DEA SRT’s current tasking of crowd control and surge operations that are active and ongoing.

1.2 Background.

Like many other law enforcement agencies, the DEA is currently dependent on manual processes and fragmented software, communications, and record keeping solutions. This situation delays situational awareness, hinders unified command, limits communication, and compromises informed decision-making. SRT currently uses a SharePoint site to store and share files, which authorized personnel are given access to.

Critical information, such as equipment inventories, personnel training information, and operational data, is tracked in spreadsheets that must be manually updated. There is a lack of a centralized capability to track real time data, such as locations of agents and suspects. Due to the reliance on manual data entry and lack of real-time visibility, there is the risk that information that SRT personnel rely on may be incomplete or outdated, which impacts the capability for units to plan and respond to quickly evolving and high-risk situations.

Commonly used commercial communications and collaboration platforms were designed to facilitate business and consumer needs. They were not designed with the intent of being used to dispatch and manage tactical team members, perimeter units, medics, dispatchers, negotiators, drone operators, command staff, and case agents who are tasked with performing rapidly evolving, high-risk operations. These operations can also sometimes result in critical incidents, which impose additional obligations on law enforcement, such as documentation and reporting.

SECTION II

2.0 Task and Technical Requirements

The Contractor shall provide all personnel, software licenses, technical support, maintenance, documentation, training, and materials necessary to furnish a commercially available Mission Planning Software solution that supports the operational requirements of the DEA Special Response Team (SRT). The Contractor shall configure, implement, maintain, and support the software solution throughout the period of performance. The Contractor shall make the software available within 14 days of contract award. All contractor performance shall meet or exceed the performance standards identified in Section III.

2.1 Accessibility: The Contractor shall deliver a secure mobile software solution for Government-approved devices. This solution must enable authorized users to access data information via mobile devices (e.g., tablets, phones), manage mission plans, conduct briefings, and log operational activities. System availability must meet or exceed 99.9% monthly, excluding scheduled maintenance.

2.2 After-Action Reporting: The Contractor shall provide automated workflows that capture operational information, compile standardized after-action reports, archive incident records, and export reports in Government-approved formats. The system shall generate requested reports within five (5) minutes under normal operating conditions.

2.3 Data Security/Encrypted Messaging: The Contractor shall provide encrypted communications and encrypted storage for Law Enforcement Sensitive (LES) information in accordance with applicable DOJ, CJIS, and DEA security requirements. The Contractor shall maintain all required security updates throughout the period of performance.

2.4 Dispatch and Negotiator Logs: The Contractor shall provide secure dispatch and negotiator logging capabilities to track communication and support active listening and intelligence gathering to understand a subject's behavior. These logs should include time stamps, audit history, searchable records, and export functionality.

2.5 Planning and Decision Support: The Contractor shall feature operational planning capabilities that assist authorized personnel with mission planning, routing, resource allocation, and operational risk assessment.

2.6 Interoperability: The Contractor shall securely synchronize approved Government information systems and data repositories using supported interfaces while maintaining data integrity. Data synchronization shall be completed within five (5) minutes under normal operating conditions.

2.7 Inventory and Logistics: The Contractor shall provide inventory management capabilities for tactical equipment, vehicles, and specialized assets, including automated notifications for maintenance schedules, inspection requirements, and inventory shortages. Inventory updates shall be reflected in the system in real time.

2.8 Operational Notifications: The Contractor shall provide a real-time notification and emergency alert system for authorized personnel, featuring streamlined templates for planning and active operations and a silent-setting bypass for critical alerts. Under normal operating conditions, the system must deliver at least 95% of operational alerts within 30 seconds.

2.9 Operational Planning: The Contractor shall provide interactive planning tools that support operational mapping, route development, route plotting, building layouts, deployment symbol overlays, and collaborative planning.

2.10 Personnel Management: The contractor shall maintain personnel records, including member information and roles within the operation which includes an estimated time of arrival (ETA) tracker, team assignments, training hours, operation participation statistics, qualifications, certifications, availability, equipment issued, and automatic roster development. Operational roster updates shall occur within thirty (30) seconds during active operations.

2.11 Intelligence Sharing: The Contractor shall provide secure intelligence sharing capabilities, including authorized live video, drone feeds, photographs, documents, and operational intelligence. Live video streams shall maintain latency of two (2) seconds or less under normal network conditions.

2.12 Records Management: The contractor shall provide centralized management of personnel records (including medical and training documentation), equipment, analytics, operational documentation, training records, analytics with audit logging, retention capabilities, and DEA related documents.

2.13 Simulation and Contingency Planning: The Contractor shall provide mission simulation capabilities that allow operational personnel to develop, evaluate, and revise contingency plans prior to mission execution.

2.14 Document Repository and Collaboration: The contractor shall provide a centralized repository that supports team members to load, access, and share data and documentation (policies, rosters, equipment logs), instantly fulfill discovery obligations, and convert data to a Portable Document Format (PDF) format. This will include a team calendar and a chat tool.

2.15 User Interface: The Contractor shall provide a user interface that enables authorized users to efficiently complete routine operational tasks while minimizing unnecessary navigation and reducing operator workload and supporting the availability requirement identified in Task 2.1.

2.16 Mapping and GPS: The Contractor shall provide GPS-enabled mapping capabilities including satellite imagery, operational overlays, three-dimensional (3D) architectural floor plans, and real-time location tracking where authorized. The solution shall display location information with an accuracy of approximately five (5) meters when supported by the connected GPS device and operating environment.

2.17 DEA Branding and Customization: The Contractor shall customize the user interface (UI), outputs, and administrative configurations of the commercially available Mission Planning Software to uniquely reflect the DEA’s identity and operational structure.

2.17.1 Visual Branding: The software solution must natively display the DEA name, logo, official emblems, and division identifiers across all platform dashboards, secure mobile applications, login screens, and user communication spaces.

2.17.2 Document and Reporting Customization: All automated outputs including after-action reports (Task 2.2), dispatch logs (Task 2.4), and roster exports, shall be hardcoded to auto-populate the designated DEA letterhead, metadata tags, and specific classification/handling markings (e.g., "Law Enforcement Sensitive") required by the DEA.

2.17.3 Configuration Control: The platform must provide an administrative portal allowing designated DEA administrators to customize team naming conventions, localized asset categories, and mission planning templates without requiring additional developer coding or contract modifications.

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into measurable performance objectives directly tied to mission-essential tasks. The performance thresholds define the minimum acceptable levels of service required for each objective. The Government will evaluate performance on an 'Acceptable' or 'Unacceptable' basis. Meeting these thresholds is critical to mission success.

Performance Objective

PWS

Paragraph Performance Threshold

Acceptable Quality Level

Method of Surveillance

System Availability

2.1, 2.15 99.9% monthly uptime ≥99.9% Automated system logs.

Secure Communications

2.3 Zero unencrypted LES

transmissions

100% Security audit

Report Generation

2.2 Reports generated within

5 minutes

95% Operational testing

Operational Notifications

2.8 Alerts delivered within 30

seconds

95% Random sampling

Personnel Management

2.10 Roster updates within 30

seconds

100% Random Sampling / User Feedback

Intelligence Sharing

2.11 Video latency ≤2 seconds 95% Operational

testing

GPS Accuracy 2.16 Approx. 5-meter accuracy when supported

95% Government verification

Data Synchronization

2.6 Synchronization within 5

minutes

95% System logs

Inventory Management

2.7 Inventory changes

reflected in real time

100% Government inspection

DEA Branding Customization

2.17 100% of core dashboards, user login screens, and system-generated forms accurately display DEA logos, names, and security markings prior to final system acceptance/go-live.

100% Visual inspection and user-acceptance testing (UAT) by the

COR.

Configuration Control Integrity

2.17.3 System updates or

software patches must result in 0% loss or corruption of DEA-configured templates, Post-deployment verification testing by the COR after every system update.

custom fields, or localized metadata.

Quality Control Management

6.4 Draft QCP submitted

within 14 calendar days of award. 100% compliance with approved quality inspection schedules and bug-remediation timelines.

100% Inspection of deliverables;

Review of monthly QC audit logs.

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

Deliverable PWS Paragraph Due Date Acceptance Criteria

Mission Planning Software Licenses and Provisioned Software Solution

1.1.1; 2.0;

2.1–2.16

Before system go-live; the final calendar date shall be established from the contract award date.

The required licenses are furnished, the solution is configured, and authorized Government users can access the required capabilities from Government-approved devices.

Initial System Integration, Data Migration, and Synchronization

1.1.1; 1.2;

2.6; 2.12;

2.14

Before system go-live; the final calendar date shall be established from the contract award date.

Government-approved legacy data and SharePoint content are migrated or made accessible;

required interfaces synchronize data while maintaining data integrity; and the Government validates the transferred data.

DEA Branding & Configuration

2.17 Before system go-

live.

The software accurately displays the DEA's name, logo, and division markings on all interfaces and system-generated forms.

User Training 1.1.1; 2.0 Before system go-live.

The Contractor provides training to the Government-designated users on the configured solution and its required operational capabilities.

Quality Control Plan 6.0 Within 14 calendar days after contract award.

The plan explicitly details the Contractor’s methods to monitor, identify, prevent, and correct defective services relative to Section III thresholds.

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 The Government will not furnish property or services for this requirement.

5.2 The contractor will not be required to acquire any property.

SECTION VI

6.0 Quality Control

The Contractor shall establish, implement, and maintain a complete Quality Control Plan (QCP) to ensure the requirements of this contract are provided as specified.

6.1 QCP Submission: The Contractor shall submit a comprehensive draft QCP to the Contracting Officer (CO) and Contracting Officer’s Representative (COR) within fourteen (14) calendar days of contract award for Government review and approval. Any subsequent changes to the approved QCP shall be submitted to the CO and COR for approval five (5) working days before implementation.

The QCP shall document the Contractor's specific inspection system and methods, including how the Contractor will monitor, identify, prevent, and correct defective services before the service performance becomes unacceptable. It shall explicitly detail the quality metrics, automated tracking logs, and remediation pathways for the performance thresholds outlined in Section III (Service Summary), including system availability (99.9%), data synchronization speeds, and encryption auditing.

6.2 Quality Control Records: The Contractor shall maintain files of all quality control inspections, audits, and corrective actions taken throughout the contract period of performance.

These records shall be made available to the Government upon request within two (2) business days.

SECTION VII

APPENDIX 1

1.0 DEFINITIONS AND ABBREVIATIONS

Contracting Officer (CO): The duly appointed Government agent authorized to award or administer contracts. The contracting officer is the only person authorized to contractually obligate the Government.

Government Furnished Property (GFP): Facilities, equipment, tools, supplies, parts, or any other items furnished for the concessionaire's use by the Government. A full list, if applicable, is in Section V.

Performance Threshold: The minimum performance level of a performance objective required by the Government.