Submittal Form A - Scoring Matrix Criminal.xlsx
XLSX spreadsheet 30 KB Posted
- Solicitation number
- Not on record
- Issued by
- Alaska
About this file
This is a Submittal Form A Scoring Matrix for a Request for Proposals issued by the State of Alaska, Department of Law for the design, implementation, hosting, and support of a secure, web-based, bidirectional Criminal Case Intake and Disposition portal (RFP 2026-0300-0290). The RFP seeks qualified vendors to develop a system capable of managing criminal case intake and disposition processes. Proposals must be submitted by email to 03procurement@alaska.gov no later than 2:00 p.m. on August 14, 2026. The submittal form serves as an evaluation tool for scoring vendor proposals against defined criteria, enabling the procurement team to assess and compare qualified bidders on standardized metrics.
The scoring matrix contained within this form establishes the evaluation framework that will be applied to all responsive proposals received. This document is essential for ensuring transparent and consistent evaluation of all submissions against predetermined scoring categories and weightings. Interested vendors should reference the complete RFP 2026-0300-0290 and accompanying submittal forms for detailed requirements, technical specifications, pricing instructions, and other submission requirements. Questions regarding the procurement process should be directed to 03procurement@alaska.gov or by calling 907-465-4337.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP Amendment 2.pdf | ||
| Standard Contract Form with draft Appendices.pdf | ||
| RFP Amendment 1.pdf | ||
| Submittal Forms B - F.docx | DOCX document | |
| Submittal_Form_G_SOALAW_Cost_Proposal.xlsx | XLSX spreadsheet | |
| RFP 2026-0300-0290.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
Sheet1
| Req ID | Purpose | Requirements: | Overall Priority: | Demonstration Priority: | Score Weight: | Offeror's Response: | ||||
| OpenAI: Vendor to indicate extent of fit: Fully Meets / Partially Meets / Does Not Meet / Future Roadmap / Not Applicable. | Delivery Method | |||||||||
| OpenAI: Identify whether requirement is met via standard configuration, workflow/rules, report, integration, custom development, third-party component, or process/service. | Gap / Comments: | |||||||||
| OpenAI: Use this column to explain gaps, assumptions, dependencies, or implementation considerations. | Acceptance Notes: | Eval Score (0-5) | Weighted Score | Max Score | Fit % | Max Score Possible: | 440 | |||
| CJIS-001 | CJIS Requirements. Must comply with federal and state guidelines. | Integrate with Microsoft Active Directory or equivalent State identity directory (Azure/Entra AD) services for State Employee authentication | High | Required | 5 | Offeror's Score: | 0 | |||
| CJIS-002 | CJIS Requirements. Must comply with federal and state guidelines. | Vendor must demonstrate operational experience hosting CJIS-regulated criminal justice systems in production environments. | High | 5 | ||||||
| CJIS-003 | CJIS Requirements. Must comply with federal and state guidelines. | Vendor personnel accessing criminal justice information must meet CJIS personnel security requirements. | High | 5 | ||||||
| CJIS-004 | CJIS Requirements. Must comply with federal and state guidelines. | System architecture must support CJIS audit logging and retention requirements. | High | 5 | ||||||
| CJIS-005 | CJIS Requirements. Must comply with federal and state guidelines. | Vendor must document CJIS incident response procedures. | High | 5 | ||||||
| CJIS-006 | CJIS Requirements. Must comply with federal and state guidelines. | Vendor should demonstrate prior prosecutor-office or law-enforcement intake portal implementations. | High | 5 | ||||||
| CJIS-007 | CJIS Requirements. Must comply with federal and state guidelines. | Vendor must demonstrate CJIS-compliant disaster recovery and continuity capabilities. | High | 5 | ||||||
| CJIS-008 | CJIS Requirements. Must comply with federal and state guidelines. | Provide encryption in transit and at rest for all State data and backups using industry-standard, FIPS-validated cryptography, including HIPAA-grade encryption (AES-256 for data at rest and TLS 1.2 or higher for data in transit), appropriate for standard, CJIS, PII, and PHI data. | High | 5 | ||||||
| CJIS-009 | CJIS Requirements. Must comply with federal and state guidelines. | Provide as a cloud-based solution hosted exclusively in U.S.-based data centers and fully aligned with NIST 800-53 and AWS GovCloud controls. All application components and primary data must reside in the offeror's U.S. cloud environment, with geography of primary and backup sites disclosed. | High | 5 | ||||||
| CJIS-010 | CJIS Requirements. Must comply with federal and state guidelines. | Must provide configurable session‑management controls, including State‑defined timeouts, idle‑session detection with automatic termination, and forced‑logout capabilities. | High | 5 | ||||||
| UPTIME-001 | Uptime, continuity, and mission-critical availabiilty | Vendor must provide guaranteed uptime SLA appropriate for 24/7 law enforcement operations. Uptime must be 99.95% excluding scheduled maintenance. | High | 5 | ||||||
| UPTIME-002 | Uptime, continuity, and mission-critical availabiilty | System must support disaster recovery and geographic redundancy. | High | 5 | ||||||
| UPTIME-003 | Uptime, continuity, and mission-critical availabiilty | Vendor must provide documented continuity procedures for statewide outages. | High | 5 | ||||||
| UPTIME-004 | Uptime, continuity, and mission-critical availabiilty | System must support emergency/manual CCID processing during outages. | High | 5 | ||||||
| UPTIME-005 | Uptime, continuity, and mission-critical availabiilty | Vendor should provide near real-time system health monitoring and alerting. | Medium | 4 | ||||||
| LOWB-001 | Low Bandwidth Operation | System must function effectively in low-bandwidth rural environments. Defined as environments of download speeds of 2 Mbps and upload speeds of 2 Mbps. | High | 5 | ||||||
| LOWB-002 | Low Bandwidth Operation | System must support resumable uploads/downloads. | High | 5 | ||||||
| LOWB-003 | Low Bandwidth Operation | System must support intermittent connectivity without data corruption. | High | 5 | ||||||
| LOWB-004 | Low Bandwidth Operation | System should provide bandwidth-optimized document and evidence handling. | Medium | 4 | ||||||
| LOWB-005 | Low Bandwidth Operation | System should support offline drafting or queued submission workflows. | Medium | 4 | ||||||
| MUNI-001 | Municipal Access | Support secure municipal prosecutor access to jurisdiction-specific ATN records. | High | 5 | ||||||
| MUNI-002 | Municipal Access | Restrict municipal access based on agency/jurisdiction permissions. | High | 5 | ||||||
| MUNI-003 | Municipal Access | Allow municipal prosecutors to track referral status and dispositions without requiring direct system integration. | High | 5 | ||||||
| MUNI-004 | Municipal Access | Support manual and offline access, including the ability to batch print for offline use. | High | 5 | ||||||
| MUNI-005 | Municipal Access | Support configurable external agency visibility rules. | Medium | 4 | ||||||
| DISPO-001 | Disposition Feedback | Automatically transmit disposition information to referring LEAs. | High | 5 | ||||||
| DISPO-002 | Disposition Feedback | Support configurable disposition status notifications and workflows. | High | 5 | ||||||
| DISPO-003 | Disposition Feedback | Provide evidence retention guidance to referring agencies. | High | 5 | ||||||
| DISPO-004 | Disposition Feedback | Support structured declination reason tracking and communication. | High | 5 | ||||||
| DISPO-005 | Disposition Feedback | Provide near real-time disposition synchronization. | Medium | 4 | ||||||
| DISPO-006 | Disposition Feedback | Support configurable disposition audit reporting. | Medium | 4 | ||||||
| INT-001 | Integration with Agency Partners and CMS | Support vendor-supported bidirectional APIs for LEA RMS integration. | High | 5 | ||||||
| INT-002 | Integration with Agency Partners and CMS | Support standards-based vendor-agnostic integration architecture. | High | 5 | ||||||
| INT-003 | Integration with Agency Partners and CMS | Support automated synchronization between portal and CMS. | High | 5 | ||||||
| INT-004 | Integration with Agency Partners and CMS | Support future integration expansion without significant redesign. | High | 5 | ||||||
| INT-005 | Integration with Agency Partners and CMS | Support scalable, industry‑standard APIs and integration methods to accommodate high‑volume data exchange without degrading performance. | High | 5 | ||||||
| INT-006 | Integration with Agency Partners and CMS | Provide API-based or equivalent interoperability architecture suitable for key case details (e.g. defendant's name, referral agency) | High | 5 | ||||||
| INT-007 | Integration with Agency Partners and CMS | Assist with completing the required Department of Administration, Office of Information Technology, Security Plan. | High | 5 | ||||||
| INT-008 | Integration with Agency Partners and CMS | Support field matching API to enable the creation of new cases following portal submissions. | High | 3 | ||||||
| INT-009 | Integration with Agency Partners and CMS | Support secure DEMS integration workflows. | Medium | 4 | ||||||
| INT-010 | Integration with Agency Partners and CMS | Support integration with court system - CourtView. | Low | 3 | ||||||
| ATN-001 | Arrest Tracking Number Generation | System must integrate legacy alogrithim to prevent duplication. ATN #s can never repeat. | High | Required | 5 | |||||
| ATN-002 | Arrest Tracking Number Generation | System must support configurable check-digit validation or equivalent error-detection mechanism. | High | Required | 5 | |||||
| ATN-003 | Arrest Tracking Number Generation | System must support offline/manual ATN issuance with later synchronization and collision prevention. | High | Required | 5 | |||||
| ATN-004 | Arrest Tracking Number Generation | System must generate globally unique ATNs that never repeat. | High | Required | 5 | |||||
| ATN-005 | Arrest Tracking Number Generation | ATNs must be randomly generated and non-sequential. | High | Required | 5 | |||||
| ATN-006 | Arrest Tracking Number Generation | Provide functional parity with the desktop platform, guaranteeing consistent performance, usability, and compliance in all work environments, including remote and field operations. | High | 5 | ||||||
| ATN-007 | Arrest Tracking Number Generation | System should support configurable ATN formatting rules and auditing. | Medium | Required | 4 | |||||
| IMP-001 | Implementation | Vendor must provide phased implementation methodology minimizing operational disruption. | High | 5 | ||||||
| IMP-002 | Implementation | Vendor must support staged agency onboarding. | High | 5 | ||||||
| IMP-003 | Implementation | Vendor must provide rollback/contingency planning. | High | 5 | ||||||
| IMP-004 | Implementation | Vendor should provide pilot implementation options. | Medium | 4 | ||||||
| IMP-005 | Implementation | Vendor should provide transition support and hypercare services. | Medium | 4 | ||||||
| IMP-006 | Implementation | Allow export of State-owned data in a usable format during the term and on transition or termination. | High | 5 | ||||||
| REP-001 | Reporting Functionality | Provide referral volume reporting by agency, office, and case type. | Low | 3 | ||||||
| REP-002 | Reporting Functionality | Provide screening timeline and disposition analytics. | Low | 3 | ||||||
| REP-003 | Reporting Functionality | Provide case aging dashboards for intake and screening. | Low | 3 | ||||||
| REP-004 | Reporting Functionality | Support legislative and executive reporting exports. | Low | 3 | ||||||
| REP-005 | Reporting Functionality | Provide comparative district and agency performance analytics. | Low | 3 | ||||||
| REP-006 | Reporting Functionality | Provide compatability with PowerBI reporting software for creation of in-house reports. | Low | 3 | ||||||
| FUNC-001 | Portal Functionality | Support automatic population of related fields and records so that entering data once updates all corresponding fields across the system. | High | 5 | ||||||
| FUNC-002 | Portal Functionality | Support consistent use of the State of Alaska's official time zone for all displayed and record dates and times, including timestamps, workflows, notifications, and audit trails, across all modules and devices | High | 5 | ||||||
| FUNC-004 | Portal Functionality | Provide real-time monitoring and notification to system administrators of errors, API failures, latency, background tasks, and system availability. | High | 5 | ||||||
| FUNC-005 | Portal Functionality | Provide real‑time monitoring and notification to system administrators of hosted storage consumption, storage‑growth trends, capacity thresholds, and nearing‑limit conditions for all storage components (e.g., file storage, database storage, object storage, and backups). | High | 5 | ||||||
| FUNC-006 | Portal Functionality | Support automated email notification of new submissions to associated Division office. | High | 5 | ||||||
| FUNC-006 | Portal Functionality | Support document transmission for associated case referrals. | High | 5 | ||||||
| FUNC-007 | Portal Functionality | Support creation of customizable fields on CCID (e.g. defendant's identifying information, referred criminal charges, referring agency, date of offense, check boxes for other relevant details such as domestic violence offense, location of the offense, date of arrest/citation, victim identifying information, LEA report numbers) | High | 5 | ||||||
| FUNC-008 | Portal Functionality | Support creation of pre-populated Alaska statutes, including statutory citation, class and level of offense. | High | 5 | ||||||
| FUNC-009 | Portal Functionality | Support multiple charges per referral. | High | 5 | ||||||
| FUNC-010 | Portal Functionality | Support copying of details to a co-defendant's referral. | High | 5 | ||||||
| ACCESS-001 | Accessibility and Administration | Support SSO and MFA compatible with State identity standards. | High | 5 | ||||||
| ACCESS-002 | Accessibility and Administration | Provide and manage user identites for 3rd party Law-Enforcement and other organizations as well as tie into the SOA Microsoft Ecosystem for SOA users | High | 5 | ||||||
| ACCESS-003 | Accessibility and Administration | Ensure all integrated systems exchange date and time values using consistent time-zone standards. | High | 5 | ||||||
| ACCESS-004 | Accessibility and Administration | Allow system administrators to add and manage security groups without vendor development. | High | 5 | ||||||
| ACCESS-005 | Accessibility and Administration | Support office based access restrictions. | High | 5 | ||||||
| ACCESS-009 | Accessibility and Administration | Allow system administrators to configure retention rules, schedules, workflows, and expectations without vendor intervention. | High | 5 | ||||||
| ACCESS-010 | Accessibility and Administration | Allow role-based user functionality (e.g. for prosecutors, paralegals, LOAs, supervisors, admins, victims, and LEAs) | High | 5 | ||||||
| ACCESS-011 | Accessibility and Administration | Support conflict-case restricted acccess controls | High | 5 | ||||||
| ACCESS-012 | Accessibility and Administration | Support offline access with synchronization upon reconnection. | High | 5 | ||||||
| ACCESS-013 | Accessibility and Administration | Maintain complete auditability of all retention and disposition decisions, including timestamps, role-based users, workflow history, and applied rules. | High | 5 | ||||||
| ACCESS-014 | Accessibility and Administration | Support agency-based restrictions. | High | 5 | ||||||
| ACCESS-015 | Accessibility and Administration | Support permission types such as full control, modify, read, write, and comparable rights appropriate to the platform. | High | 5 | ||||||
| ACCESS-016 | Accessibility and Administration | Allow system administrators to create, modify, update, or supersede retention schedules and rules, including criteria, cutoff events, durations, and disposition actions. | Medium | 4 | ||||||
| ACCESS-017 | Accessibility and Administration | Allow authorized users to purge or retire records in accordance with policy while preserving referential integrity and auditability. | Medium | 4 | ||||||
| ACCESS-018 | Accessibility and Administration | Provide configurable quick links for accessing frequently used resources directly from the system interface (e.g., Courtview, State Employee Directory, VINElink). | Low | 3 | ||||||
| SCA-001 | Scalability | Provide a modular, cloud‑native architecture that supports scalable deployment and separation of components. | High | 5 | ||||||
| SCA-002 | Scalability | Support dynamic resource scaling to maintain consistent performance and high availability under variable workloads. | High | 5 | ||||||
| SCA-003 | Scalability | Support horizontal and vertical scalability to accommodate increasing user loads, data volumes, and functional complexity. | High | 5 | ||||||
| SCA-004 | Scalability | Support statewide multi-office usage and concurrency at a scale appropriate for the Criminal Division as well as all LEA's in Alaska. | High | 5 | ||||||
| SCA-005 | Scalability | Support scalable audit logging that maintains traceability and performance as usage, data volume, and configuration activity increases | High | 5 | ||||||
| SCA-006 | Scalability | Support secure, scalable data synchronization across modules and external systems without compromising performance. | High | 5 | ||||||
| DEV-001 | Development | Provide comprehensive documentation of the development process, including regular progress reports to project leads | High | 5 | ||||||
| DEV-001 | Development | Provide appropriate environments for configuration, testing, training, and production use. | High | 5 | ||||||
| DEV-001 | Development | Document inbound and outbound integrations, field mappings, dependencies, error handling, and operational support points. | High | 5 | ||||||
| WF-001 | Workflow Automation | Ability to route referrals automatically based on originating LEA, geography, offense type, or configurable rules. | High | 5 | ||||||
| WF-002 | Workflow Automation | Track referral status throughout case lifecycle and provide near real-time feedback to referring agency. | Medium | 4 | ||||||
| WF-003 | Workflow Automation | Automated notifications triggered by status changes. | Low | 3 | ||||||
| WF-004 | Workflow Automation | Provide confirmation of referral receipt to LEA. | Low | 3 | ||||||
| WF-005 | Workflow Automation | Display screening status to authorized external users. | Medium | 4 |
File details come from the government source that posted it. Updated .