RFP Amendment 2.pdf

PDF 269 KB Posted

Attached to
Request for Proposals - Criminal Case Intake and Disposition Portal
Solicitation number
Not on record
Issued by
Alaska

About this file

This is Amendment 2 to a Request for Proposals issued by the State of Alaska Department of Law Criminal Division for the Criminal Case Intake and Disposition Portal (RFP #2026-0300-0290). The amendment provides clarification and responses to inquiries submitted by offerors regarding system integration requirements, API availability, evidence management functionality, and operational procedures. Key clarifications include that the Department of Law's Case Management System supports bidirectional data exchange through APIs or vendor-supported integration tools, though the department cannot represent capabilities across all 40+ law enforcement agencies statewide using various systems and vendors. The portal is designed primarily to facilitate submission of initial case referral information rather than transfer of digital evidence, which will continue through existing processes outside the portal. Users require the ability to upload and submit documents but need only sufficient display information such as file names or attachment lists to verify uploads. Law enforcement users may add referred charges within a reasonable timeframe after initial submission, with the system alerting the Department of Law to enable manual entry if direct integration is unavailable. All criminal referrals and filings, including direct-filed cases, require an Alaska Tracking Number and are entered into the Department of Law's Case Management System.

The amendment addresses technical infrastructure, noting that the Department of Law's Case Management System and Digital Evidence Management System are hosted in Azure Government Cloud within Prosecutor by Karpel and Axon's tenants. API access to the Department of Law's systems will be made available to the successful contractor as necessary, though vendors seeking access to law enforcement agencies' APIs must work directly with those agencies and bear any associated costs. The amendment confirms that no API integration between the portal and the Department of Law's Digital Evidence Management System is anticipated as part of this project. Questions regarding the amendment should be directed to Jedediah Smith, Procurement Officer, at (907) 465-4337 or jed.smith@alaska.gov.

View the file

Other files

File Type Posted
Standard Contract Form with draft Appendices.pdf PDF
RFP Amendment 1.pdf PDF
Submittal Forms B - F.docx DOCX document
Submittal Form A - Scoring Matrix Criminal.xlsx XLSX spreadsheet
Submittal_Form_G_SOALAW_Cost_Proposal.xlsx XLSX spreadsheet
RFP 2026-0300-0290.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

STATE OF ALASKA

Department of Law Criminal Division

Criminal Case Intake and Disposition Portal (CCID)

RFP #2026-0300-0290

Amendment #2 August 6, 2026

This Amendment is being issued for informational purposes only. This document does not need to be returned with your proposal.

Important Note to Offerors: This amendment is to provide clarification and answers to a number of questions submitted regarding this RFP. Please see the list of questions below, and the official responses by the Department of Law.

Please contact me if you have any questions.

Name: Jedediah Smith Title: Procurement Officer Phone: (907) 465-4337 Email: jed.smith@alaska.gov or 03procurement@alaska.gov mailto:jed.smith@alaska.gov mailto:03procurement@alaska.gov

Questions and Responses:

1. Do the CMS and DEMS systems (for all LEAs and LAW) have API or vendor-supported tools available for the Portal to support bi-directional information integration? Figures 8 & 9, pages 19 & 20, figure 12 page 27.

Response: LAW’s CMS supports bi-directional data exchange through APIs or vendor-supported integration tools. LAW cannot represent whether every LEA uses a records management system or digital evidence management system that supports bi-directional integration. There are more than 40 LEAs statewide using a variety of systems and vendors, and those capabilities vary by agency. See also response to question 2.

2. Will those API’s be made available to the winning vendor? If so, is there a cost to the winning vendor associated with the API access?

Response: To the extent LAW controls access to its own APIs, LAW intends to make them available to the successful contractor as necessary to support the portal solution. However, at this point, LAW does not have open access to PbK’s API – any vendor and LAW would need to work with PbK to obtain access and build an integration.

If an LEA’s participation requires licensing fees, vendor costs, or other expenses associated with access to that LEA’s APIs or systems, those costs are the responsibility of the participating LEA or vendor and are not the responsibility of LAW or the portal solution.

3. It appears that the Dept of Law has it’s own DEMS as it appears so from figure 12 on page 27. How should evidence sharing work with the new Portal? Is there an API available as in question 2?

Response: At this time, the portal is not expected to integrate directly with LAW's Digital Evidence Management System (DEMS). The primary purpose of the portal is to facilitate the submission of initial case referral information, not the transfer of digital evidence. For purposes of this answer, digital evidence is defined as any evidence other than documents (e.g. .pdfs, Word documents etc.). LAW expects that the LEA may desire and should have the capacity to include the defendant’s APSIN history and the charging document with the initial referral. By contrast, we do not expect the LEA to send LAW videos, images etc. through the portal. Digital evidence will continue to be exchanged outside the portal using existing processes. Accordingly, no API integration between the portal and LAW's DEMS is anticipated as part of this project.

4. Do users need to be able to view (not just submit) documents and evidence in the portal? Reference B. Law

Enforcement Referral Functionality, page 32, "Attachments".

Response: Users only need the ability to upload and submit documents through the portal. They do not need the ability to view the contents of uploaded documents after submission. However, the portal should display sufficient information (such as file names or attachment lists) so users can verify which files have been uploaded.

5. Where are the Dept of Law CMS and DEMS hosted? Figure 12, page 27.

Response: Azure Government Cloud within PbK and Axon’s tenants.

6. Will LEA users be able to edit data in the portal after original referral submission? If so, do those changes need to be pushed to CMS? What restrictions should there be for updates? Reference B. Law Enforcement Referral Functionality, page 32.

Response: Yes. LEA users should be able to add referred charges within a reasonable time after they are submitted to LAW. It would be acceptable to LAW to create a window of time when that action is available. The system must provide a means to alert LAW to the change and an opportunity to add it manually to our CMS if there is no direct integration.

7. How will direct filed cases be handled in the new portal process? Do they get an ATN and if so, how is it assigned? Do direct-filed cases go into CMS? Page 23, E. How cases are referred: charged/direct filed vs referral.

Response: All criminal referrals and criminal filings, including direct-filed cases, require an Alaska Tracking Number (ATN). Under the current process, an LEA obtains an ATN by completing a paper CCID form at the time of direct filing (when the LEA charges the case with the court). The court will not accept a criminal filing without an ATN. Direct-filed cases are entered into LAW's CMS in the same manner as other criminal referrals.

File details come from the government source that posted it. Updated .