Attachment 2 - Draft Statement of Work for E-STAR_Final.pdf

Pre-Decision Draft

U.S. DEPARTMENT OF HOMELAND SECURITY

U.S. CUSTOMS AND BORDER PROTECTION

DRAFT STATEMENT OF WORK

FOR

CBP ENFORCEMENT ACTION STATISTICAL ANALYSIS AND

REPORTING SYSTEM

(E-STAR)

CBP OPERATIONS SUPPORT LAW ENFORCEMENT SAFETY AND

COMPLIANCE DIRECTORATE

JUNE 2025

CBP/LESC E-STAR Statement of Work

Pre-Decisional Draft Page | 2

Table of Contents

PART I: GENERAL INFORMATION

A. SCOPE

PART II: TASKS

A. DOCUMENTATION

B. GOVERNMENT MONITORING

C. GOVERNMENT ACCEPTANCE PERIOD

D. TRAVEL

E. MATERIALS

F. SPECIFIC TASKS

PART III: REQUIREMENTS

A. OPEN ARCHITECTURE REQUIREMENTS

B. PERSONNEL/LABOR CATEGORY REQUIREMENTS

PART IV: DELIVERABLES

A. MANAGEMENT APPROACH PLAN

B. QUALITY CONTROL PLAN (QCP)

C. PROJECT IMPLEMENTATION PLAN

D. WRITTEN STATUS REPORT (WSR)

E. WEEKLY MEETING WITH COR AND PROGRAM MANAGER

F. DELIVERABLE SCHEDULE

PART V: SUPPORTING INFORMATION

A. SECURITY REQUIREMENTS:

B. PLACE OF PERFORMANCE:

C. PERIOD OF PERFORMANCE:

D. GOVERNMENT FURNISHED EQUIPMENT (GFE) AND GOVERNMENT FURNISHED

INFORMATION (GFI)

E. DEFINITIONS

APPENDIX A: EXAMPLES OF CURRENT REPORTING

Page | 3

PART I: GENERAL INFORMATION

U.S. Customs and Border Protection (CBP) intends to modernize its approach to incident reporting and analysis, currently supported by the E-STAR system. The objective is to implement a cost-effective, adaptable system capable of integration with other technologies. The proposed solution shall include a user-facing reporting interface, a centralized data storage infrastructure accessible to all CBP components, the environments specified within this Statement of Work (SOW) and must meet the essential requirements outlined in the Scope.

CBP is interested in transitioning from an in-house reporting system to a system that prioritizes efficiency and innovation and reduce lifecycle cost.

Table 1.1- Stakeholder Summary

A. SCOPE

The system shall provide comprehensive capabilities for reporting, tracking, analyzing, and managing incidents related to use of force, assaults against CBP personnel, vehicle pursuits, and other relevant events. The system must meet all of the essential requirements outlined below.

1. The system shall provide the ability for end users to report on and LESC to provide data analytics for the following types of incidents:

Reportable Use of Force by a CBP employee Unintentional Firearm Discharge by a CBP employee Non-Use of Force Intentional Firearm Discharge by a CBP employee Vehicle Pursuit by a CBP employee Failure to Yield (FTY) without a pursuit Assault (including assaultive resistance) against a CBP employee

2. The system shall also be flexible to allow the Government to add additional incident types and configure existing forms/form fields without the need for complex computer programming (no-code or low-code). In other words, system administrators shall be able to add or amend fields and forms via a customer-facing form builder tool.

3. The system shall have the following functionality for each type of incident report:

Stakeholder Role

Contractor The Contractor shall be responsible for performing the professional services as described within this SOW.

Law Enforcement Safety and Compliance (LESC) Directorate 440 Koonce Road, Harper’s Ferry, WV 25425

LESC will be the client representing the interest of CBP.

LESC will be the Project Manager (PM) for CBP.

Office of the Commissioner Final approval/funding of project Office of Information Technology

(OIT)

Participating IT Stakeholder Responsible for overseeing data transfer / Application Programming Interface (API) buildouts

Office of Operations Support (OS) Parent Component of LESC who will be overseeing the development of the new reporting system

Page | 4

Specify whether the incident involved a mass encounter Allow file attachments to be uploaded for supporting documentation Allow an incident report to be opened in Edit, Review and View-Only Modes

(restricting each mode by user role) Generate batch incident reports for bulk data requests Redact an incident report – individual reports and in bulk Print an incident report - individual reports and in bulk Mark an incident as non-statistical

4. An additional desired feature is a partner agency access portal for personnel that are without

CBP Active Directory access and not included in CBP’s Organizational Code structure.

5. The system shall provide automatic email alerts and notifications that can be configured based on user roles.

6. The system shall include an automated information extraction capability to support custom searches in support of responding to Freedom of Information Act (FOIA) requests.

7. The system shall include an automated report validation capability to identify when a report is incomplete.

8. The system shall be compatible with data visualization software products currently in use at CBP

(such as PowerBI, Qlik, Tableau). “Compatible” includes the ability to implement an automated connection between system data and the data visualization software so that data does not have to manually exported and uploaded.

9. The system shall seamlessly integrate with CBP's existing system (Active Directory) to obtain and maintain accurate user information, including organizational codes and identification numbers. The Contractor shall propose a robust and reliable method for ensuring data synchronization and user authentication.

The system shall provide a robust role and access management system, up to and including System Administrators, that allows CBP (LESC) to control user access to sensitive data and functionalities based on their organizational roles and responsibilities.

10. To minimize disruption and training costs, the system should, to the extent practicable, maintain consistency with existing CBP terminology and naming conventions, including the name of the system (E-STAR) and incident event logic. However, the Contractor may propose alternative names, labels, or definitions that would improve usability or clarity, provided that they are clearly documented and justified. The CBP logo must be displayed on all official reports. The Contractor may add their brand name to the product, but it may not appear on official reports.

11. The home page should provide users with a clear and intuitive overview of the system, including access to key functionalities, important notifications, and relevant resources. The Contractor should propose a home page design that optimizes usability and efficiency.

Page | 5

12. The system shall provide a comprehensive incident report form or forms that allow users to enter and manage all relevant data related to use of force incidents, assaults, vehicle pursuits, and other reportable events, including demographic information on involved personnel, subjects, bystanders and witnesses, as well as relevant information on weapons, devices and techniques employed during the incident. The Contractor should propose a design that optimizes data entry efficiency, accuracy, and completeness.

13. The system shall support concurrent access and editing of incident reports by multiple users, allowing for collaborative data entry and management.

14. The system shall provide robust search functionality that allows users to quickly and easily locate specific incident reports based on a variety of criteria, including incident date, location, involved parties, and keywords. The search functionality should support wildcard searches and full-text searches of narratives and addendums.

15. The system shall provide comprehensive dashboards and reporting capabilities that allow users to generate a variety of visualizations and reports on incident data. A list of required reports is identified in Appendix A. The reporting system should support ad-hoc reporting, scheduled reporting, data visualization, and raw data exports.

16. The system shall provide a centralized training and reference page that allows users to access training materials, documentation, and support resources (including videos). The system shall allow system administrators to update training materials as needed.

17. The system shall provide a comprehensive help system that offers users clear and concise guidance on how to use the system and understand key concepts and terminology. The help system should be easily accessible from all pages within the system and should be easily updated by system administrators.

18. The reporting system shall be designed to be intuitive and user-friendly, minimizing the need for extensive training. The Contractor shall employ industry-standard usability principles and conduct user research to ensure a positive user experience. User acceptance testing will be conducted to validate the system's usability.

19. The contractor shall migrate all existing E-STAR data into the contractor’s system, which must be hosted in an environment that is FedRAMP High authorized or equivalent security requirements.

20. While the cloud environment will remain contractor-owned, CBP will retain ownership of all data stored in the contractor’s cloud.

21. The Contractor shall create scripts and/or applications to perform the migration of data from the current E-STAR system the new E-STAR system. The provided deliverable shall support and account for the migration of the data as well as the overall reconciliation and tracking of moved data.

Page | 6

22. After migration, the data shall be arranged in a manner that LESC shall be able to perform granular searches of the data and have the capability to perform data analysis, ad hoc requests, and FOIA requests.

23. The system shall be capable of handling non-numerical values in historical data. When a data field does not have a valid numerical value because that data field was not collected in earlier years, the system shall record a designated non-numerical value (e.g., blank space, 'null,' or '¯').

The value '0' is not acceptable for this purpose. The system shall not include non-numerical values in statistical calculations. For example, if in 2023 CBP began capturing an FTY data value, then the data chart could show:

Fiscal Year Total FTY Data

FY22 Ø

FY23 100

FY24 100

TOTAL 200

24. Other than routine maintenance and security updates, the Contractor shall not make any changes to the reporting system as it applies to the E-STAR interface, data collection, E-STAR data storage, E-STAR reports, user roles, user permissions, dashboards, E-STAR historical data, and E-STAR training environments without prior written guidance and approval from LESC.

25. The Contractor shall provide data reporting for a variety of purposes including trend analysis, statistical reporting, and compliance auditing. The reports shall be accessible for CBP to run and maintain without requiring ongoing Contractor support after Go-Live.

26. The system shall retain audit logs tracking all activity in the system.

27. The system shall allow E-STAR incidents to be linked to one another.

28. The system shall allow data to be imported from one E-STAR incident to another E-STAR incident.

29. The Contractor shall include a rapid integration solution that automates the flow of data from disparate systems into and out of the product.

a. The Contractor shall import biographical information of involved persons from the E3 system.

b. The Contractor shall import information on weapon issuance and firearms/less-lethal use of force training from Firearms, Armor and Credentials Tracking System (FACTS).

c. The Contractor shall import information on training and certifications from CBP’s

Learning Management System (ACADIS).

Page | 7

d. The Contractor shall import and export information on incidents between the new E- STAR system and Verified Information Tracking and Accountability System (VerITAS).

e. The Contractor shall integrate with the Enterprise GIS Dashboard (EGIS) mapping tool

(CBP’s enterprise instance of the Esri Portal for ArcGIS) or incorporate a muti-tenant Map Service Architecture system for GPS coordinates. The system shall support satellite view, street view, CBP organizational boundaries, CBP facilities and tactical infrastructure, landmarks designated by CBP, and latitude/longitude coordinates. The Contractor should propose a solution that is compatible with CBP's existing GIS infrastructure or provides equivalent or superior mapping capabilities

f. Before a connection is established with any of the above-listed integrations, the Government reserves the right to substitute one or more of those integrations with a different identified system integration without additional cost to the Government.

g. If additional integrations are required in addition to the E3, FACTS, ACADIS, EGIS and

VerITAS integrations already included herein, they will be added by CBP’s exercise of an option included in the contract.

h. Any connection to Active Directory and/or ICAM/OKTA, the Single Sign-On (SSO) application, shall be included in the product.

30. In addition to CBP workstations (i.e. laptop) the system shall maintain full functionality for field end users on a CBP mobile device (phone or tablet).

31. The reporting system shall be designed to meet all CBP Office of Information Technology (OIT) information security standards to include established performance standards and CBP’s Privacy and Security Standards (2120-010A).

PART II: TASKS

A. DOCUMENTATION

1. The SOW will be the governing document if there are any conflicts with documents, statements, or agreements between the Government and the Contractor.

B. GOVERNMENT MONITORING

1. Contractor work shall be subject to government inspection without notice, as required by the Government.

Page | 8

C. GOVERNMENT ACCEPTANCE PERIOD

1. The Contractor shall work in partnership with CBP to determine readiness by conducting functional testing and an end-to-end system review. The Contractor program manager and CBP’s project manager shall work closely together to plan and execute readiness scenarios, to include regularly scheduled demonstrations of the product by the contractor.

2. The Contractor shall conduct Functional Acceptance Testing (FAT) via use cases approved by the Government.

3. All discovered issues, bugs, malfunctions, and inconsistencies during and after training shall be entered into the service portal for triage, follow-up, and a remediation plan.

4. After FAT is completed, user acceptance testing shall also be required as a condition of project completion.

D. TRAVEL

1. There will be a degree of local travel for required in-person meetings, testing, training, and project milestones. The Contractor is responsible for all travel cost.

E. MATERIALS

CBP will:

1. Ensure reasonable availability for meetings, phone or email of knowledgeable Government personnel to provide timely and accurate documentation and information to the Contractor.

2. Identify holidays, non-workdays, or major events that may impact the project.

3. Ensure agency desktop workstations, mobile systems, and devices can access the product.

4. Make available relevant systems if needed for assessment by the Contractor (including making these systems available to Contractor via remote access, if possible).

5. Provide the Contractor with remote access to CBP’s reporting system account when required.

The Contractor shall:

1. Propose a user management structure that optimizes cost efficiency and user accessibility sized for not less than 500 concurrent users logged in system-wide and five concurrent users logged into a single report. The system should also be appropriately sized to accommodate the full production data set as it expands.

a. Manual license management (for example, end user calls a help desk to ask a support technician to activate their license) is not a viable option for the E-STAR system.

Page | 9

2. Assist CBP in identifying any existing integrations between the Vendor’s products and other

CBP or DHS systems that are applied to E-STAR to realize cost efficiencies.

3. Identify and recommend to CBP any additional opportunities to deploy and maintain E-STAR in a more cost-effective manner while still delivering the entire scope outlined in this SOW.

4. Provide a minimum one-year labor warranty including coverage for the system as a whole.

F. SPECIFIC TASKS

1. Specific tasks related to this contract are described in the Scope section. The Contractor is encouraged to propose alternative tasks or approaches that would improve the efficiency or effectiveness of the project.

PART III: REQUIREMENTS

A. OPEN ARCHITECTURE REQUIREMENTS

1. As part of the system design, the contractor shall ensure that the reporting system—including the interface, data structures, dashboards, and all supporting components—is developed in full compliance with open architecture principles. This design approach is intended to maximize system flexibility, interoperability, and integration readiness with existing and future U.S.

Customs and Border Protection (CBP) systems, as well as with partner agency platforms.

2. To satisfy this design criterion, the system must incorporate the following foundational elements:

1. Open Standards: All interfaces and protocols shall be based on widely accepted, publicly available standards. This ensures compatibility with a broad range of technologies and minimizes reliance on proprietary solutions.

2. Modularity: The system shall be architected using distinct, loosely coupled modules that can be independently developed, tested, deployed, and maintained. This allows for scalable expansion and targeted updates without impacting the broader system.

3. Interoperability: All modules and system components shall be designed to work seamlessly together, regardless of the vendor or origin, by leveraging open standards and well-defined interfaces. This is critical to ensure seamless data exchange and operational coordination across systems.

4. Flexibility: The system’s architecture shall allow for configurability and reusability, enabling the system to be adapted to evolving operational needs. System components should be able to be mixed, matched, or replaced to support mission-specific functionality.

Page | 10

3. The adoption of an open architecture framework is a non-negotiable design requirement and essential for future-proofing the system, promoting interagency collaboration, and supporting innovation across the enterprise. The contractor shall demonstrate compliance through design documentation, integration testing, and ongoing lifecycle reporting.

4. Open Architecture Compliance Checklist. This checklist is intended to ensure vendor compliance with open architecture principles as part of the system design criteria for the reporting system. Vendors must provide evidence for each item listed below to demonstrate adherence.

Requirement Compliance Indicator Vendor Documentation

Open Standards

All interfaces and protocols conform to publicly available and widely accepted standards (e.g., REST, JSON, XML, HTTPS, etc.).

Design documentation with reference to standards used; API specifications.

Modularity

System architecture is composed of distinct modules that are logically separated and independently manageable.

System architecture diagram;

Module interface definitions.

Independent Module Lifecycle

Modules can be updated, replaced, or maintained without requiring changes to the entire system.

Documentation of version control and update process; Evidence of modular deployment capabilities.

Interoperability Modules support standardized interfaces enabling integration with CBP systems and external platforms.

Integration test plans and results;

List of tested third-party integrations.

Flexible Configuration

The system can be easily tailored to meet specific CBP operational or mission needs through configuration (not custom code).

Configuration management plan;

User documentation on system customization.

Non-Proprietary Dependencies

No reliance on proprietary or closed-source components that inhibit future integrations or modifications.

Software bill of materials (SBOM); License disclosures.

Cross-Agency Integration Readiness

System demonstrates ability to integrate with other government agency systems using shared data standards and transport protocols.

Documentation of supported interagency standards; Results of any existing or simulated interagency data exchange.

Lifecycle Reporting

The vendor will provide regular updates on system integration status, modularity compliance, and any deviations.

Project management reports;

Change management logs.

Waiver Management (if needed)

Justification and request process in place for any deviation from open architecture principles.

Waiver request documentation;

Approval/denial record.

Page | 11

B. PERSONNEL/LABOR CATEGORY REQUIREMENTS

1. The Contractor personnel will require a limited CBP background investigation to access the E- STAR production, test, or training environments.

2. The Contractor shall ensure that employees requiring a background investigation submit all required paperwork for the background investigation as quickly as possible.

3. Project delays resulting from a lack of CBP-cleared Contractor personnel will not constitute a change in scope or result in additional cost to CBP.

PART IV: DELIVERABLES

A. MANAGEMENT APPROACH PLAN

1. The Contractor shall assign a project manager who will work with the CBP Contracting Officer’s Representative (COR) and Project Manager to ensure completion of deliverables.

2. The Contractor’s project manager shall ensure all team members from the Contractor and CBP are continually updated on the status of the project.

3. All project requirements are documented during the kick-off and discovery phases of the project.

4. Once CBP and the Contractor agree on all requirements, the Contractor’s project manager shall work with CBP’s project manager to develop a project plan for Contractor’s implementation.

B. QUALITY CONTROL PLAN (QCP)

1. The Contractor shall provide a quality control plan for ensuring quality of all deliverables and addressing any deficiencies identified by the Government.

C. PROJECT IMPLEMENTATION PLAN

1. Interfaces

1. CBP and Contractor tasks related to interface setup start immediately after project kick-off. It is critical for CBP interface SME and the Contractor project interface resources to work closely together to scope, set-up, and test all interfaces.

2. The Contractor shall provide any relevant Contractor API documentation to CBP.

3. The Contractor shall conduct integration acceptance testing demonstrating the functionality of each integration to CBP.

Page | 12

4. Any CBP stakeholders with direct access to the data warehouse, such as the Border Enforcement Management Systems (BEMS) and any subset IT team, will be given the same degree of accessibility.

2. Training

a. The Contractor shall provide training guides that outline the covered topics, intended audience, facility needs, and duration of the training.

b. The Contractor shall provide CBP with all the necessary training materials and digital assets to facilitate any of the training formats listed below. Training sessions shall be conducted in an environment containing necessary configurations, forms, and workflows, as well as any additional training beyond the default method.

c. The Contractor shall train CBP’s designated users in full system functionality prior to going live, which shall include but shall not be limited to all LESC, Border Patrol Academy, Field Operations Academy, Air and Marine Operations Academy instructor personnel. LESC, Academy and field use of force instructors are responsible for training all agency end-users. The Contractor provides all training materials for successful training and assists CBP’s trainers in creating the course and training schedule.

d. The training plan contains an agreed-upon schedule that makes efficient use of time and resources to avoid undue staffing impacts on the agency. Training materials will be evaluated as part of the User Acceptance Testing (UAT) and training sessions will occur after the UAT has been successfully completed.

e. Training sessions provided by the Contractor are conducted on a schedule agreed by CBP and the Contractor.

f. For the duration of the contract, the Contractor shall provide CBP with updated training materials as system updates occur. All training materials, guides, digital assets, and plans shall be focused on end-users and/or administrators based off the nature of the system update.

3. System Acceptance Testing (SAT)

a. The Contractor shall create System Acceptance Test Plan.

b. The Contractor shall install the SAT candidate software release into the SAT E-STAR platform.

c. The Contractor shall perform testing of installed software prior to handoff to CBP for Systems Acceptance Testing.

d. The Contractor shall provide direct support to CBP during SAT testing to include dedicated development team members and a daily debrief on test results.

Page | 13

System performance load and stress testing shall begin as early as feasible during the execution of solution phase and shall be conducted at appropriate intervals prior to the submission of the request for the system release to ensure acceptable performance in production.

4. User Acceptance Testing (UAT)

a. UAT is the critical step for identifying whether the OPR modules are ready to be deployed.

b. The Contractor shall help to prepare or update a UAT Plan and test scenarios/scripts for users to follow during the initial structured portion of the UAT (following structured testing the users are encouraged to conduct their own free-form testing). The Contractor shall assist CBP during the preparation and execution of the acceptance test by establishing test data and maintaining the test environment.

c. The Contractor shall correct any errors identified by the LESC team. The Contractor shall document the results of the testing in the Test Report. Upon receipt of the report, CBP will examine the test results and decide as to the readiness of the new or modified code and/or system changes/additions to be released into the production environment.

d. The Contractor shall provide direct support to CBP during SAT testing, to include dedicated development team members and a daily debrief on test results.

5. Go-Live

a. Go-Live will be the moment when the new reporting system is “turned on”.

b. The Contractor shall work with CBP to build, coordinate, and execute a Go-Live plan to ensure successful system acceptance. The Contractor shall coordinate the Go-Live event.

c. The Contractor acknowledges that all CBP users are expected to have access to the system on Go-Live. The Contractor shall work with CBP to develop a Go-Live plan that ensures a smooth transition to the new system. The Contractor shall provide training and support to a level approved by the LESC in order to enable CBP users to effectively utilize the system as quickly as possible after Go-Live.

6. Transition-In Plan

a. The Contractor shall develop a detailed Transition-In Plan that outlines the Contractor's approach to data migration, system integration, user training, and go-live support. The Transition-In Plan shall include a detailed schedule, resource allocation, and risk management plan.

b. The Contractor shall be responsible for validating the accuracy and completeness of the migrated data. The Contractor shall develop and implement a data validation plan.

Page | 14

c. The Contractor shall query the data to identify completeness, missing values, and other measures of data integrity across records and provide CBP with detailed findings. The contractor shall provide CBP with the opportunity to review/validate data at CBP’s discretion.

d. This process is considered complete once all data has been converted and available within the product and CBP has confirmed validation of the converted data, with seamless integration.

7. Transition-Out Plan

a. The Contractor shall configure and make available to CBP throughout the contract, a read-only data store containing all field and form data that allows CBP to utilize available data for reporting and analytical purposes. The data store shall be in a widely supported format that is compatible with CBP's existing systems and tools.

b. The Contractor shall compile a data relationship map and a data dictionary explaining the location and meaning of all data fields, including data input by end users as well as metadata captured by the system.

8. Special Considerations

c. The Contractor shall offer options to add additional 3rd Party interface development deliverables on a per-interface basis.

d. The Contractor shall include a maintenance plan to meet CBP's evolving needs.

9. Support

a. The Contractor shall provide updates and enhancements to the product. CBP will automatically receive all updates and enhancements.

b. The Contractor shall remain available following the implementation and live release of the system to make changes to the data fields and other aspects of the application based on changing requirements, structural data needs, and changes to CBP policy requirements.

c. The Contractor shall perform corrective maintenance as needed.

d. The contractor shall allow end users to request 24/7 technical support from the contractor.

The contractor shall provide a technical support plan including a schedule of priority for technical support events.

e. Following final acceptance, CBP reserves the right to request future modification.

Page | 15

f. CBPs engagement model calls for full-time dedicated development and implementation support during the first six months to facilitate rapid knowledge acquisition and skill development.

D. WRITTEN STATUS REPORT (WSR)

1. The Contractor shall provide a written WSR documenting activities completed in support of scoped deliverables. The WSR covering the previous month’s activities shall be submitted no later than the 5th calendar day of the following month.

E. WEEKLY MEETING WITH COR AND PROGRAM MANAGER

1. The Contractor shall establish a regular meeting cadence with the COR and Program Manager, with meetings sufficiently frequent to keep the COR and Program Manager apprised of project status and potential issues. The meeting cadence will be at least one meeting per week.

F. DELIVERABLE SCHEDULE

1. Summary of deliverables follows. Copies are to be provided to CBP as indicated below.

Deliverables that have a set due date on the table below must be delivered on the date specified.

For deliverables without a set due date in the table below, the Contractor shall provide a delivery schedule specifying a proposed due date. Project milestones and delivery schedule should be outlined in the proposal.

2. The Contractor shall be responsible for managing the deliverable schedule and ensuring that all deliverables are submitted on time and in accordance with the requirements outlined in this SOW. The Contractor should propose a delivery schedule that is the most logical, efficient and economical for system development. The proposed due dates do not need to be in the order in which the deliverables are listed on the table. Multiple deliverables may be provided on the same date if this increases the efficiency of system development.

3. While the management approach, staffing, quality control, project implementation, transition-in, and transition-out plans are not due with the proposal, the vendor should speak to each of these areas in their oral presentations.

DELIVERABLE DISTRIBUTION DUE DATE

Oral Presentation N/A Due with Proposal Key Personnel Resumes N/A Due with Proposal

Management Approach Plan N/A Draft 1 Week after Award Final 3 Weeks after Award

Staffing Plan N/A Draft 2 Weeks after Award Final 4Weeks after Award

Quality Control Plan N/A Draft 5 Weeks after Award Final 7 Weeks after Award

Project Implementation Plan (including Transition-In/Out Plan)

COR and CBP Program Manager

Draft 6 Weeks after Award Final 8 Weeks after Award

Page | 16

Written Status Report (WSR) COR and CBP Program Manager

Monthly, On or Before the 5th of each month (or alternate cadence determined by CBP)

Weekly Meeting COR and CBP Program Manager

Weekly (or alternate cadence determined by CBP)

Invoices COR and CBP Program Manager

Due Upon Completion of Work Scheduled During the Period of Performance

Staffing Status Report COR and CBP Program Manager

Delivery schedule to be included in Contractor’s proposal

System Ready for Go-Live Notification Report

COR and CBP Program Manager

1 Week after system is ready for Go- Live)

PART V: SUPPORTING INFORMATION

A. SECURITY REQUIREMENTS:

1. All work under this SOW is UNCLASSIFIED, but may require secure handling of information designated as for official use only (FOUO) and/or personally identifiable information (PII),

2. Access to CBP facilities shall be requested at least 1 week prior to the date access is scheduled, including submitting personal information required by campus security for all personnel requiring access, per visit.

B. PLACE OF PERFORMANCE:

1. CBP LESC Policy, Force Review, and Compliance Branch 440 Koonce Road Harper’s Ferry, WV 25425

C. PERIOD OF PERFORMANCE:

1. The contract term shall be for one year from the date of the award with four one-year option periods, subject to CBP’s option to extend the term of the contract in accordance with the clause Federal Acquisition Regulation (FAR) 52.217-9 entitled, "Option to Extend the Term of the Contract".

2. The contractor shall propose a schedule for implementation and sustainment of the system over the life of the contract.

D. GOVERNMENT FURNISHED EQUIPMENT (GFE) AND GOVERNMENT FURNISHED

INFORMATION (GFI)

1. CBP laptops will be issued to CBP-cleared Contractor personnel where required to complete contract deliverables.

Page | 17

E. DEFINITIONS

CBP TERMINOLOGY DEFINITION

CBP U.S. Customs and Border Protection

E-STAR Enforcement Action Statistical Analysis and Reporting System

FACTS Firearms, Armor and Credentials Tracking System

LESC Law Enforcement Safety and Compliance

BEMS Border Enforcement Management Systems

OIT Office of Information Technology

PARTIES

Agency Customs and Border Protection (CBP) who is identified within this SOW

End-Users Specific agency groups using the system

Professional Services The services that the Contractor provides within the scope of this

SOW

SYSTEMS

CJIS

The Federal Bureau of Investigation’s criminal justice information system

DataStore The database the Contractor provides allowing CBP to query data

Product The software solution being implemented as part of this SOW

Production Environment The operational environment where the product is accessed

Development Environment The pre-production environment where all Contractor-specific development and configuration take place

Systems Acceptance Testing Environment

The environment where testing, Functional Acceptance Testing (FAT), and User Acceptance Testing (UAT) takes place and is accessible to system administrators

Training Environment The environment where training takes place and is accessible to users at all times.

Service Portal An online portal provided by the Contractor where issues identified are entered and triaged

Page | 18

PROJECT & MILESTONES

Project Scope of this SOW as defined by the work to be completed described herein

Project Change Order (PCO)

A material change in scope executed between the Contractor and CBP that is outlined in a change order form. All work completed will be assumed to be part of the original scope unless documented in a project change order

Milestone Event that constitutes completion of work as listed in a project plan submitted by the Contractor

Go-Live End-users are activated, and the agency is actively using the product

Cutover Successful implementation of interfaces and data conversion.

Third-Party Products and Services

Software, hardware, and services that are not owned by the Contractor but are being provided by the Contractor for this project

ACCEPTANCE

Functional Acceptance Testing

(FAT)

Testing the functionality of the system as confirmed by the agency

Integration Acceptance Testing

(IAT)

Scheduled events for testing each integration point and associated functionality in collaboration with the agency and the agency’s Contractors

User Acceptance Testing (UAT) Testing the functionality of the system as configured for the agency from an end-user’s perspective

Page | 19

APPENDIX A: EXAMPLES OF CURRENT REPORTING

The following list provides a representative list of reports that have been generated via the E-STAR system recently or are currently in use.

Assault report summary Use of force report summary Vehicle pursuit report:

o Bystanders injury report o Officer/agent injury report o Overall summary report o Overall injury report o Subject drivers injury report o Subject passengers injury report o VP/FTY summary report

Old vehicle pursuit o Vehicle contraband seized report o Vehicle pursuit collateral damage report

End of year vehicle pursuit commissioner report Summary reports o Assault report Seven-day report o 7-day snapshot o Monday morning report

CBP VP report o CBP UOF by type reference sheet

Other o Incident review read ahead report

Dashboards o E-STAR QLIK dashboards

Excel spreadsheet exports (raw data files) o Daily AFU files o Weekly raw o Weekly VP AFU o Monthly CBP Stat reports