USCA19BPAC1009.pdf

ORDER FOR SUPPLIES OR SERVICES

IMPORTANT: Mark all packages and papers with contract and/or order numbers.

1. DATE OF ORDER 2. CONTRACT NO. (If any) 6. SHIP TO:

Office of Probation and Pretrial Services Administrative Office of the United States Courts One Columbus Circle, N.E.

Suite 4-300 Washington, DC 20544-0001

3. ORDER NO.

USCA19BPAC1009

4. REQUISITION/REFERENCE NO.

Manish Patel, 202-502-3258 Procurement Management Division Administrative Office of the United States Courts One Columbus Circle, N.E.

Suite 3-250 Washington, DC 20544-0001

5. ISSUING OFFICE (Address correspondence to)

7. TO:

8. TYPE OF ORDER

a. PURCHASE

REFERENCE YOUR: ____________

Please furnish the following on the terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.

X b. DELIVERY -- Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-numbered contract.

9. ACCOUNTING AND APPROPRIATION DATA 10. REQUISITIONING OFFICE

11. NOT USED 12. F.O.B. POINT

14. GOVERNMENT B/L NO. 15. DELIVER TO F.O.B. POINT ON

OR BEFORE (Date)

16. DISCOUNT TERMS13. PLACE OF

a. INSPECTION b. ACCEPTANCE

17. SCHEDULE

CLIN NO.

(a)

SUPPLIES OR SERVICES

(b)

QUANTITY

ORDERED

(c) UNIT (d)

UNIT PRICE

(e)

AMOUNT

(f)

QUANTITY

ACCEPTED

(g)

See Lines

SEE BILLING

INSTRUCTIONS

ON

REVERSE

18. SHIPPING POINT 19. GROSS SHIPPING WEIGHT 20. INVOICE NO.

$20,000.00 17(h) TOT.

(Cont.

pages)

21. MAIL INVOICE TO:

a. NAME Office of Probation and Pretrial Services

b. STREET ADDRESS(or P.O. Box) Administrative Office of the United States Courts, One Columbus Circle, N.E., Suite 4-300

c. CITY Washington

d. STATE

DC

e. ZIP CODE 20544-0001

$20,000.00

17(i)

GRAND

TOTAL

22. UNITED STATES OF AMERICA BY (Signature)

23. NAME (Typed)

Manish Patel

TITLE: CONTRACTING/ORDERING OFFICER

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION NOT USABLE

OPTIONAL FORM 347 (REV. 02/2012)

Prescribed by GSA/FAR 48 CFR 53.213(f)

USCA19BPAC1009 - Page 1 of 14

Supplies or Services and Prices/Costs

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0001 Task 1: Discovery - Analysis and Roadmap in accordance with section 2.0 under C-1

Requirements. Pricing in accordance with

Attachment XX - IOC Pricing. (Time and

Materials).

1 Not-To-

Exceed

$0.00 $0.00

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0002 Task 2: Delivery of Initial Operating Capability in accordance with section 3.0 under C-1

Requirements. Pricing in accordance with

Attachment XX - IOC Pricing. (Time and

Materials).

1 Not-To-

Exceed

$0.00 $0.00

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0003 Task 3: IOC Pilot Implementation Guide and

Training in accordance with section 4.0 under C-1

Requirements (Firm Fixed Price).

1 Lot $0.00 $0.00

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0004 Travel 1 Not-To-

Exceed

$20,000.00 $20,000.00

Descriptions/Specifications/Statement of Work

C-1 Requirements

1.0 Scope

This BPA Call is for an initial discovery phase, program management, end-to-end development leading to a high-quality and secure Initial Operating Capability (IOC). The contractor shall also execute develop a pilot im-plementation guide and training. The IOC is defined as the development of the initial capabilities to manage pretrial investigations, collateral investigations, pretrial risk assessment (PTRA), presentence investigations, formal court reports related to pretrial and presentence, and related analytics and metrics for selected probation

USCA19BPAC1009 - Page 2 of 14 and pretrial services (PPS) Districts.

The contractor shall also provide program management support to establish control, risk management, commu-nication, monitoring and notification mechanisms, ensuring that tasks stay on track and important milestones are met. The contractor shall establish roles and responsibilities, and how the contractor shall collaborate and communicate with the Government. The program management support shall also require the contractor to sup-port any transition of the contractor's work to another entity, either the government or another contractor. The contractor shall develop a transition out plan to include data transfer, data translation, application services above/beyond basic SaaS, custom code, configuration, workflows, automated test scripts and any third party tools/software licenses including runtime/SDK's.

2.0 Task 1: Discovery - Analysis and Roadmap

Considering the following overarching principles, the contractor shall complete an analysis and assessment of the current probation and pretrial services product portfolio as identified in Attachment 2 – Current PPS Portfo-lio Interfaces, Attachment 5 - PPS CCMS Pretrial and Lifecycle Business Capability, Attachment 6 - PPS CCMS Presentence Business Capability, and Attachment 7 - PPS CCMS Post Conviction Business Capability.

The analysis and assessment shall involve, but not be limited to, interviews with Government and other con-tractors, reviews of existing documentation and code to support the PPS-CCMS strategic portfolio/product strategy and roadmap, and developing a data migration strategy/plan. A draft roadmap is referenced in Attach-ment 3 – PPS-CCMS Roadmap.

The new solution shall integrate with existing legacy systems in the PPS portfolio to provide a seamless experi-ence for users. The contractor should take into account the following overarching prin-ciples:

• Subsume legacy system capabilities into the PPS Client Case Management solution to the maximum extent possible to avoid building an interface to the legacy system.

• Adapt to the interfaces used by as-is legacy systems, if they exist.

• Use standard Application Programming Interface (API) technologies such as RESTful (preferred), Web Services Description Language (WSDL), and Simple Object Access Protocol (SOAP), Extensible Markup Language (XML), JSON.

• Use standardized data elements wherever possible such as National Information Exchange Model (NIEM), National Crime Information Center (NCIC) Standards and the AOUSC Data mod-el.

• Keep all PII content within data exchanges to a minimum.

• Document all interface designs using a standard interface control document format.

• Leverage enterprise integration mechanisms being developed by the AOUSC to the extent possible (API Gateway and Enterprise Service Bus).

• Use standard methods for securing interfaces.

3.0 Task 2: Delivery of Initial Operating Capability (IOC)

The contractor shall execute an Agile design, development, test, validation, and acceptance methodology to best meet the successful delivery and deployment of the IOC.

The contractor shall provide comprehensive and requirement/business analysis in collaboration with Govern-ment stakeholders, subject matter experts and/or product owners to translate requirements and needs into action-able features, stories and tasks. The contractor shall collaborate with the Government PMO to prioritize the de-tailed development product backlog leading to the acceptance and delivery of the IOC.

3.1 Initial Operating Capability (IOC)

The contractor shall design, develop, test and deliver an IOC of the new PPS Client Case Management Solution that is FedRamp High certified. The IOC delivered shall include all of the functionality needed to manage pre-trial investigations, collateral investigations, pretrial risk assessment (PTRA), presentence investigations, formal court reports, and related analytics and metrics for PPS Districts. The IOC shall include the Business

USCA19BPAC1009 - Page 3 of 14 and System Capabilities found in Attachment 4 - RTM for IOC, and the high level requirements found in At-tachment 5 - PPS CCMS Pretrial and Lifecycle Business Capability and Attachment 6 - PPS CCMS Presentence Business Capability. The contractor shall obtain Government acceptance and authorization to operate prior to deployment to ensure all business and security objectives are achieved.

3.2 IOC Interfaces

The IOC shall include the following system interfaces and data exchanges between the PPS CCMS IOC and ex-isting legacy systems to support pilot operations. Further interface details can be found in Attachment 2 – Cur-rent PPS Portfolio Interfaces.

System Data Exchanges SIRS The solution shall provide a service to allow SIRS to push, upon risk assessment certification, the current risk assessment certification data for officers in order to provide officers access to the risk assessment capability in the solution.

Legacy PACTS - The solution shall query legacy PACTS for existing clients and ingest data into the Solution’s client and case record.

- The solution shall push client and case data to legacy PACTS if a client is released to supervision.

ATLAS - The solution shall query ATLAS to run record check as well as ingest data into the solution’s client record.

DSS - The solution shall send periodic client and case data for ingestion into DSS.

- The solution shall query DSS to ingest CM/ECF data for the presentence investigation process.

Offense Level Calculator (OLC) The solution shall utilize the OLC, a web-based applic-ation providing presentence officers with an automated tool to calculate the federal sentencing guidelines used in the creation of Presentence Reports delivered to judges.

Guideline Manual Application

(GMA)

The solution shall utilize the GMA, an application used by presentence officers to determine the appropriate United States Sentencing Commission (USSC) guidelines that apply to criminal charges in order to ac-curately calculate the offense level.

E-designate The solution shall push (send) client sentence record data and documents to the United States Marshals Of-fice eDesignate Bridge.

ESS/USSC The solution shall push (send) a clients sentencing packet (documents) to the United States Sentencing Commission after a person is sentenced to criminal charges.

District Systems The solution shall provide services for individual dis-tricts to integrate directly with the system.

3.3 Official Court Reports

The IOC shall have the capability to create, customize, and electronically manage the delivery of official court reports, such as Bail and Presentence Reports, containing data captured during the investigation processes. The IOC shall provide the capability to develop report templates and/or modify nationally provided reports to meet local district needs.

3.4 IOC Analytics, Metrics, and Reports

The IOC shall have the capability to deliver Judicial-mandated metrics, ad-hoc reporting and dashboards for all pretrial and presentence investigation data captured in the IOC to support workload, evidence-based outcome

USCA19BPAC1009 - Page 4 of 14 practices and decision making at the district and national levels. Workload can fluctuate significantly based on actual events (see Table 1).

Table 1 – PACTS Workload Statistics:

2016 2017 2018 % Growth from 2016 to

% Growth from 2017 to 2018

Clients (Supervision)

80,102 123,186 144,143 54% 17%

Pretrial Client Intake

101,193 156,081 180,173 54% 15%

Cases 127,386 200,749 236,231 58% 18% Documents 4,527,183 7,011,498 7,113,699 55% 1% Images (Photos) 117,756 179,636 193,761 53% 8% Chronos 11,807,313 17,723,214 16,268,147 50% -8%

3.5 IOC Documentation

The contractor shall provide all required technical documentation to ensuring the quality and security of the IOC to include, but not limited to:

• SaaS Service Architecture

• SaaS Service Management and Operational Management Guide

• Test Results, Deficiency Reporting, Tracking and Resolution Plan

• FedRamp Accredidation Package

• Release Notes

4.0 Task 3: IOC Pilot Implementation Guide and Training

The contractor shall provide an implementation (rollout) guide along with user guides and training materials.

The Government's System Development and Support Office (SDSO), Training Division is responsible for train-ing probation and pretrial services staff. The contractor shall properly sequence and adequately staff to provide train-the-trainer support to the Government’s SDSO, Training Division for the IOC.

The contractor shall develop, update and provide user manuals and training guides for the solution as well as any additional tools or services to support the use of the application. These user manuals and training guides should use a variety of training modalities that help users understand how to successfully provision services and provides best practices for using available services. All administrators and users shall be provided access to on-line training resources and shall receive comprehensive training and updated training with new software re-leases.

5.0 Meetings

5.1 Kick-off Meeting

The contractor shall participate in a kick-off meeting with the Government within ten business days after the award date or other mutually agreed upon timeframe. The kick-off meeting will be held at the Government’s fa-cility in Washington, DC.

The meeting is intended to:

- Initiate the communication process between the Government and contractor by introducing key task parti-cipants and discussing roles and responsibilities.

- To ensure the contractor has a full understanding of the objectives and requirements for successful delivery of the PPS CCM solution.

5.2 Other Meetings

The contractor shall participate in other facilitated meetings (e.g., planning, reviews, demonstrations etc.) as re-quired and necessary with the Governement to ensure the successful delivery and execution of the requirements.

USCA19BPAC1009 - Page 5 of 14

Applicable Clauses

F-1 Deliverables

The contractor shall submit electronic copies of deliverables to the COR and other government staff, as neces-sary, via email unless notified otherwise. All deliverables submitted in electronic format shall be free of any known computer virus or defects. If a virus or defect is found, the deliverable will not be accepted. The replace-ment file shall be provided within two (2) business days after notification of the presence of a virus.

The deliverables are as follows:

Deliverable Description Task Deadline Customer Journey Maps Diagram(s) that depict the stages users go through when interacting with the Solution.

2 Initial due 30 days after Award. Update as required.

Data Migration Plan Detailed plan describing the process and set of pro-cedures that will be used to migrate data, including documents and photo im-ages, from the legacy sys-tems to the new solution (e.g., data selection, prepar-ation, extraction, trans-formaion, and transfer) to ensure the correct form and quality.

1 Initial due 90 days after Discovery period. Update as required.

FedRamp Accredidation Package

All FedRamp security doc-umentation for the Solution required by the AO to com-plete a risk assessment of the system relative to NIST and JISF controls. Required documents include:

- System Security Plan

- Security Assessment Plan

- Security Assessment Re-port

- Continuous Monitoring Scorecard and Plan

- Plan of Actions and Mile-stone Report

- Security Control Imple-mentation Worksheet

All Update before approval of IOC product release and for any substantive change in the system.

Implementation (Rollout) Plan

Detailed plan describing the strategy, process and set of procedures that will be used to implement the delivered solution into an operational environment.

3 Initial due 90 days after Discovery period. Update as required.

USCA19BPAC1009 - Page 6 of 14

At a minimum, the plan should describe the change management and training activities required for dis-trict and user readiness and acceptance.

Incremental Delivery of Capabilities (Product De-livery)

Releaseable, working soft-ware based on the priorit-ized and committed back-log to include relevant quality and performance metrics.

2 At the end of each Agile development cycle.

Government acceptance of final IOC (all functionality to support all Pretrial Ser-vices Investigation and Bail Report activities) and re-quired integrations by the end of the period of per-formance.

Invoices Fully itemized invoice for services provided during a given month.

All Monthly

Milestone and Deliverable Schedule

Definitive milestone and/or deliverable schedule identi-fying all the activities needed to meet the object-ives of the contract.

All Initial due 30 days from Award. Revisions due at start and end of each Agile development cycle or as re-quired.

Portfolio/Product Roadmap High-level roadmap identi-fying the capabilities, key milestones and deliverables needed for the full operat-ing capability.

1 Initial due 30 days after Discovery period. Update as required.

Product Backlog Contains the list of all gov-ernment approved and pri-oritized features, user stor-ies, acceptance criteria, business value, tasks and release tags to implement all functional and non-functional requirements.

2 Initial within 30 days from Award. Update throughout Agile development cycles.

Product Demos Demos of releasable, work-ing software based on the prioritized and committed backlog to include relevant progress, risks and metrics.

The demo may include, but not limited to, working in-tegration with internal and external applications, demonstrating proper data storage etc.

2 At end of each Agile devel-opment cycle and prior to release.

Program/Project Manage-ment Plan

Detailed plan on how the Contractor will manage and coordinate the project based on the objectives in the BPA. The plan shall in-

All Within 10 business days after Award. Update as re-quired.

USCA19BPAC1009 - Page 7 of 14 clude the communications strategy outlining all com-munications, including type and frequency, between the Contractor and Govern-ment.

Progress Status report Detailed report describing accomplishments, risks, is-sues, plans, labor hours, ODCs etc.

All Monthly

Release notes Describes what is being changed in the current product release from the previous product release.

2 Incremental delivery at the end of each Agile develop-ment cycle. Final content before each product re-lease. Update as needed.

IOC specific to delivered capabilities for Pretrial Ser-vices Investigations and Bail Reports.

SaaS Cloud Services Con- Ops

Detailed description of the Solution from concept to operations. The document should define the necessary operational and quality control processes and pro-cedures to validate and im-plement, operate and main-tain the system to include, but not limited to, configur-ation management, integra-tion, data migration, test and validation.

1 Initial due 90 days after Discovery period. Update as required.

SaaS Service Architecture Detailed description of the architecture and design of the system including in-ternal components and their functions, interface con-trols, virtual machines, net-work components, and communications pathways.

2 Initial due 90 days after Discovery period. Update as required.

SaaS Service Management and Operational Manage-ment Guide

Describes the operations roles and responsibilities and standard procedures that will be used for monit-oring, patching, updating, user account management, monitoring, and incident management. The docu-ment should also include the processes and proced-ures to support continuity of operations and disaster recovery.

2 Initial due on completion of IOC. Update as required.

Test Results, Deficiency Report showing the results 2 At the end of each Agile

USCA19BPAC1009 - Page 8 of 14

Reporting, Tracking and Resolution Plan of all testing to include mit-igations for any deficien-cies.

development cycle.

Government acceptance prior to each product re-lease.

Train-the-Trainer Training Training to government trainers on the product cap-abilities and features.

3 Before each product re-lease.

Transition-Out Plan (TOP) The Contractor shall fully support the transition of the Contractor’s work which is turned over to another en-tity, either the AO or a suc-cessor contractor, by devel-oping and maintaining a Transition-Out Plan (TOP).

The TOP shall include sup-port activities for all trans-ition efforts to minimize disruption of services.

All 6 months from award.

User Guides and Training Materials

Materials use to train end users on the product capab-ilities and features. Can be online manuals, instruc-tional videos, online courseware, or in person course materials. Materials shall be delivered in the original format to facilitate reuse and customization by the government.

The AO currently uses Adobe Illustrator or Pho-toshop, and Camtasia or Captivate for videos and re-cordings

3 Incremental delivery at the end of each Agile develop-ment cycle. Final content before each product re-lease. Update as required.

IOC specific to delivered capabilities for Pretrial Ser-vices and Presentence In-vestigations.

Customer Satisfaction Sur-vey

Survey to gauge customer satisfaction of IOC and re-lated services based on a combination of Customer Satisfaction Scores (CSAT), Customer Effort Scores (CES) and Net Pro-moter Scores (NPS) that will be to used to gather in-put from users on a quarterly basis once the Solution is operations. The survey will be developed in collaboration with, and ap-proved by, the Govern-ment.

2 Initial due on completion of IOC. Update as required.

USCA19BPAC1009 - Page 9 of 14

F-2 Place of Performance and Hours of Operation

The primary place of performance shall be at the contractor facility within the Continental United States (CONUS) or at the Administrative Office of the U.S. Courts location in Washington, D.C.

Performance related to user acceptance and the IOC implementation plan may take place at selected probation and pretrial services offices within the CONUS.

Performance related to training support may take place at the training center in San Antonio, TX and/or selected probation and pretrial services offices within the CONUS. Specific sites will be determined in collaboration with the Government prior to the IOC pilot.

Normal business hours are 8AM Eastern to 5PM Eastern. The Government will provide ample notice for any work required outside of normal business hours. Normal workdays are Monday through Friday except US Fed-eral Holidays.

F-3 Completion Term

All work related to this BPA call is expected to be completed in approximately nine months.

H-1 Key Personnel

The following positions are considered key personnel by the government under this BPA call pursuant to clause 2-65 Key Personnel in base agreement. The required skills, experience, and qualifications are described below.

These positions must be filled by contractor personnel. Subcontractor personnel are not permitted to serve as key personnel.

Program Manager (Labor Category Level - Senior) Responsible for all contract activities. Sets policies and procedures, technical standards and methods, and prior-ities. Coordinates the management of all work performed on tasks under the contract. Coordinates the efforts of subcontractors, team members, and vendors. Acts as the central point of contact with the Contracting Officer, the Contracting Officer’s Technical Representative, and other client officials. Exercises full authority to act for the company in the performance of the required work and services under all task orders. Works independently, or under the general direction of senior level company management, on all phases of performance including contract management, project/task order management, coordination of resource needs, coordination with cor-porate resources and management. Reports to senior company management on contract and task performance and issues. Has direct accountability for the technical correctness, timeliness, quality and security of deliver-ables, and the implementation and measurement of corporate and client quality standards and methodologies.

Has a broad and deep knowledge of the IT industry, business administration, and human resource management and has excellent oral and written communications skills.

Experience: Minimum of six (6) years of experience with the management of large scale, complex systems.

Experience in applying agile concepts and methodologies with CRM platforms highly desired.

Education: Bachelor’s degree in related field. PMP and related Agile certifications.

Solutions Architect (Labor Category Level - Senior) Responsible for delivering a portfolio of solutions in response to disruptive forces, and driving achieving tar-geted business outcomes. Solutions include systems (including applications, technologies, processes and in-formation), shared infrastructure services and shared application services. Solution architect provides the neces-sary leadership, analysis and design tasks related to the development of an enterprise's solution architecture.

This individual creates deliverables that help develop a direction for managing the organization's portfolio of "to be" and "as is" solutions. These include systems (meaning not just applications, but also processes and informa-

USCA19BPAC1009 - Page 10 of 14 tion), shared infrastructure services, and shared application services and components to better match targeted business outcome objectives.

Experience: Minimum of eight (8) years of experience in one or multiple IT functional areas. Experience with IT infrastructure, cloud development, engineering and software architecture design and DevSecOps.

Education: Bachelor’s degree in related field.

Data Architect (Labor Category Level - Senior) Defines fine how the data will be stored, consumed, integrated and managed by different data entities and IT systems, as well as any applications using or processing that data in some way. It is closely aligned with busi-ness architecture . The data architect “provides a standard common business vocabulary, expresses strategic data requirements, outlines high level integrated designs and aligns with enterprise strategy and related business architecture.”

Data architect is expected to set data architecture principles, create models of data that enable the implementa-tion of the intended business architecture, create diagrams showing key data entities, and create an inventory of the data needed to implement the architecture vision. Responsibilities include: Organizing data at the macro level, data models for a new application, logical data model as a standard for the golden source and for consum-ing applications to inherit and provide logical data model with elements and business rules.

Experience: Twelve (12) years of progressive experience in database management, and eight (8) years of which must include management of large scale, complex systems. The individual shall possess extensive amount of experience in data migration from legacy systems to a CRM platform.

Education: Bachelor’s degree in related field.

Delivery Manager (Labor Category Level - Senior) Sets up teams for successful delivery by removing obstacles (or blockers to progress), constantly helping the team to become more self-organizing, and enabling the work the team does rather than impose how it’s done.

Manages one or more agile projects, typically to deliver a specific product or transformation via a multi-disciplinary, high-skilled digital team. Adept at delivering complex digital projects, breaking down barriers to the team, and both planning at a higher level and getting into the detail to make things happen when needed.

Defines project delivery needs and feeds these into the portfolio/program process to enable resources to be ap-propriately allocated.

Primarily responsible for:

• Deliver projects and products using the appropriate agile project management methodology, learning & iterat-ing frequently.

• Work with the Product Manager to define the roadmap for any given product and translate this into user stor-ies.

• Lead the collaborative, dynamic planning process -- prioritizing the work that needs to be done against the ca-pacity and capability of the team.

• Matrix-managing a multi-disciplinary team.

• Ensure all products are built to an appropriate level of quality for the stage (alpha/beta/production).

• Actively and openly share knowledge of best practices.

Experiences: Five (5) years of progressive experience in Agile continuous integration and continuous delivery (CI/CD) in Federal government system delivery setting transitioning from legacy to modernizing applications.

Education: Bachelor’s degree in related field.

Information Systems Security Officer (Labor Category Level - Senior) Responsible for developing security plans for IT security systems that anticipate, identify, evaluate, mitigate, and minimize risks associated with IT systems vulnerabilities; ensuring procedural development and imple-

USCA19BPAC1009 - Page 11 of 14 mentation are in compliance with security and organizational requirements; documenting hardware and soft-ware system security implementations (e.g., hardware firmware upgrades, operating system patches and config-uration changes); and developing best practices, operating procedures, and configuration guidance for the tech-nologies used. Working knowledge of NIST 800 series special publications and the NIST Risk Management Framework.

Experience: Minimum of five (5) years of demonstrated experience in the Information Security (or Cybersecur-ity) field. Strong experience with FedRAMP and Continuous, Diagnostic and Monitoring (CDM) methods and standards.

Education: Bachelor’s degree in related field. Certified Information Systems Security Professional (CISSP).

H-2 Travel

Any travel must be approved by the COR and will be in accordance with Clause7-45 Travel that is included in the base agreement.

H-3 Government Furnished Equipment

The Government will furnish to contractor employees performing work on government premises on-site office space, furniture, telephone service (for official government business only), and other necessary equipment and supplies applicable to performing the requirements set forth in this BPA Call. For contractor personnel working off government premises, the Government will provide the applicable equipment and software to perform the requirements outlined in this BPA Call. The contractor shall be responsible for proper utilization and safeguard-ing of all Government property provided for contractor use. Contractor employees must immediately report damage, theft, or loss of Government property to the COR.

H-4 Key Performance Indicators

The contractor shall be responsible for meeting the key performance indicators (KPI) stated below. The table below provides the a description of the KPI, the acceptable standard, and the Government's method of measure-ment.

KPI Name Description Measurement Standard AQL Measurement Frequency

Concurrent Users Ability to scale to handle a high level of users.

Number of con-current users ac-cessing the sys-tem at the same time

1,000 concurrent users

100% of the time Test results with Delivery of IOC

Response Time User response times shall be sub-second for in-teractive user activity.

Number of seconds it takes for a transaction to be completed from the initial user input and the system's response back to the user.

Does not include communication with external sys-tems processing.

<0.5 seconds to <0.1 seconds

100% of the time. Test results with Delivery of IOC

Data Availability Data availability to all instances of the system within

Number of seconds to view and access data

<0.5 seconds to <0.1 seconds

100% of the time. Test results with Delivery of IOC

USCA19BPAC1009 - Page 12 of 14 the prescribed period.

once the transac-tion has com-pleted.

Defect Detection Effectiveness

Effectiveness of processes to en-sure product qual-ity and minimize the escape of bugs/defects into production

Trend analysis of Ratio of Defects as measured by:

# of bugs identi-fied and resolved in release during the development cycle/# of bugs found in release during develop-ment cycle + # of escaped defects found by users in production Example:

20/20+5 = 80% 20/20+0 = 100%

Zero (0) EMRs Emergency Modi-fication Requests (EMRs) are defined as:

- Software defects that have a signi-ficant negative impact on court operations, and have no suitable temporary work-around;

- Software defects that cause corrup-tion or loss of data, unexpected or severe degreda-tion in perform-ance, system crashes, or sudden and severe in-crease in court staff workload.

EMRs will be val-idated by the Government as such and require a fix as soon as pos-sible using an ex-pedited release cycle.

100% for bugs/ defects identified as EMRs.

Delivery of IOC.

Security Controls The Contractor’s Solution shall provide the re-quisite security as indicated in the Objectives.

Review pf JISF, FedRamp Secur-ity Controls, CJI Assessments

Meets all security requirements as indicated in the Objectives

100% currency and adherence

Delivery of IOC.

Security Vulner-abilities

The Contractor's Solution shall en-sure the timely resolution to all reported security vulnerabilities.

Rate at which vul-nerabilities are re-solved as docu-mented in POAMs

7 days for zero-day patches; 30 days for High/ Criticals; 90 for Moderates; 180 for Lows

100% of the time. Delivery of IOC.

J-1 Attachments

Attachment 2 - Current PPS Portfolio Interfaces Attachment 3 - PPS-CCMS Roadmap

USCA19BPAC1009 - Page 13 of 14

Attachment 4 - RTM for IOC Attachment 5 - PPS CCMS Pretrial and Lifecycle Business Capability Attachment 6 - PPS CCMS Presentence Business Capability Attachment 7 - PPS CCMS Post Conviction Business Capability

USCA19BPAC1009 - Page 14 of 14