Cities Index.
Attachment 1 - Karpel -Contra Costa Form of LEA Interface Request Form - Richmond.pdf

Richmond City Council
March 1, 2022

Document
Attachment 1 - Karpel -Contra Costa Form of LEA Interface Request Form - Richmond.pdf
Meeting
March 1, 2022
Body
Richmond City Council
Original file
378 KB
Text extracted from the city's file for reading and search. Open the original on pub-richmond.escribemeetings.com. That file is the official record.

1 Karpel Interface Request Form
This Karpel Interface Request Form, dated February 1, 2022, is entered into between Karpel Computer Systems, Inc. (“Karpel”) and Contra Costa County (“County”) pursuant to the Software and Services Agreement, dated June 20, 2014, between County and Karpel.

IRF Process:

1. Complete the below form for each individual interface requested. Please provide as much detail as possible.

2. Karpel will review the request and fill in the scope of work. Karpel will reach out to have meetings as necessary to clear up any questions.

3. Karpel will sign and send an approved IRF to the County for signature.

4. After the County signs the IRF, Karpel will schedule the development effort on the Karpel side. Note that there may be additional development effort required from county IT or the interfacing vendor that can create dependencies or delays in the scheduling.

5. The County will be billed, as per the agreed upon amount defined below, 30 days after the Karpel development work is completed and handed off to the County for testing. If the County has not accepted the work as complete within 30 days of delivery, the County will send a request to its Karpel contact for an extension.

6. County will order payment upon acceptance of the work as complete, at which point the project will enter maintenance.

The Customer is responsible for the following items:

1. Provide access to network resources necessary to complete the interface enhancement.

2. Respond to requests for documents, approval, and feedback made within two business days.

3. Respond to technical and business questions related to the interface or enhancement that arise during development within two business days.

4. Act as a liaison between Karpel and third party software vendors. The project schedule may be delayed if a third party is unresponsive or uncooperative.

5. Test and verify the functionality of the interface or enhancement once deployed within an agreed upon timeframe.

Customer: Contra Costa CA
Primary Customer Contact Name and Email: Gwyneth Andrews , [email protected] Additional Contacts Names and Emails: Bruce Prell, [email protected] Julie Enea, [email protected]
Is this Part of a Go Live? No - this interface is being requested after our initial implementation
Interface Type: Law Enforcement - City of Richmond, CA 2 Third Party Vendor: Peregrine
Vendor Contact Information: Eric Tam, (510) 621-1819, for Peregrine and the City [email protected]
Acting Chief Louie Tirona
Additional Notes:

Pricing:

All Karpel Interfaces have a standard pricing of a $10,000 implementation fee and a $2,000 annual maintenance.

Karpel and County agree to the above terms and costs outlined above as signed below:

Contra Costa County Date:

By:

Name: Julie Enea
Title: Sr. Deputy CAO

Karpel Computer Systems, Inc. Date:

By:

Name:

Title:

Karpel and County agree to the defined scope of work as signed below:

Contra Costa County Date:

By:

Name: Julie Enea
Title: Sr. Deputy CAO

Karpel Computer Systems, Inc. Date:

By:

Name:

Title:

3 Scope of Work
Law Enforcement – Incident Referrals
One of the most common interfaces with PbK used by many of Karpel’s customers is importing incident information from Law Enforcement. For the purposes of this document, Law Enforcement referrals are considered an inbound interface, with data coming into Karpel and a simple success/failure returned synchronously. In some instances, case, charge disposition, financial information and other data may be sent outbound back to law enforcement, but that is far less common than importing.

In some jurisdictions, law enforcement referrals may actually be sent to PbK from the court – in cases where the local police or sheriff file certain incidents with the courts prior to the prosecution. That scenario would use the same law enforcement inbound mechanism.

Data Elements
The primary data elements for an import from law enforcement are:
• Defendant pedigree information
o Person’s names and identifying numbers
o Date of birth
o Height, weight, hair/eye color – physical characteristics o Contact information – addresses, phone numbers, email, etc. o Optionally – aliases, gang information, mug shot, etc. • Victims and Witnesses (collection)
o Names
o Date of birth
o Contact information
• Charges (collection)
o Incident date & time
o Incident location
o Charge and statute codes
o Charge description
o Severity
• Documents (optional collection)
o Document title
o Document category
o Binary Data
• Arrest information
o Date & Time
o Booking Officer
o Person Booked
• Referral Information
o Referring officer
o Referring law enforcement agency
4 PBK Experience
When arrest information is imported into PBK using our standard import referral data exchange, the records are exposed to the user in the Arrest Transfer Record Search Results section of PBK. This screen allows the prosecutor to review the information from law enforcement, make necessary modifications, and then import into PBK to create (or update) a case in the Karpel system.

← All documents from this meeting