Appendices_F,_G,_and_H_Final.xlsx

XLSX spreadsheet 41 KB Posted

Attached to
Incarcerated Person Communication Services (IPCS)
Solicitation number
2000018655
Issued by
Minnesota

About this file

This document comprises three appendices (F, G, and H) from the Minnesota Department of Corrections (DOC) and Department of Information Technology Services (MNIT) Request for Proposal for an Incarcerated Person Communication Services (IPCS) platform. The RFP solicits a comprehensive, integrated electronic services and communications platform for all 11 Minnesota DOC facilities, requiring vendors to respond to detailed functional requirements, responsibility matrices, and accessibility conformance standards. Phase A (voice cutover) targets completion by December 1, 2027, encompassing site surveys, cabling installation, approximately 4,000 wireless access points (including 250 relocations), approximately 900 wall-mounted phones, and approximately 127 TRS/VRS accessibility stations across all facilities. Phase B (portable device deployment) targets November 1, 2028, requiring staged implementation beginning June 2027 and delivery of one assigned electronic device per incarcerated person. The RFP mandates full compliance with Section 508 and WCAG 2.1 Level AA accessibility standards, with remediation timelines not exceeding 180 days post-contract execution for any gaps.

Appendix F establishes a RACI (Responsibility, Accountability, Consultation, Informed) matrix defining roles across the contractor, DOC, MNIT, and RECS (Responsible Custodian of Facilities) for 61 activities spanning infrastructure deployment, system integrations, ongoing operations, support, and data ownership. Appendix G requires vendors to address 137 critical and ideal requirements organized into 17 categories (A through Q), with mandatory compliance assessments, proposal cross-references, and exception documentation for evaluation as part of Tier 1 technical scoring. Appendix H mandates submission of a completed VPAT 2.5 INT (Voluntary Product Accessibility Template) prepared or validated by an external accessibility testing organization, covering all proposed software, hardware, and websites. All voice services must comply with Minnesota Statute 241.252 (no-cost calling) and the Martha Wright-Reed Just and Reasonable Communications Act (47 U.S.C. § 262), with rates capped under FCC 23-111. The platform must support encrypted data transmission, redundancy for major components, and 99.5% monthly uptime, with 24/7/365 dedicated service desk support and response times ranging from 30 minutes (Priority 1) to 1 calendar day (Priority 4). All data and communications records remain DOC property with minimum 7-year retention in exportable formats, and the vendor must provide transition-out plans no later than 180 days before contract expiration.

View the file

Other files

File Type Posted
Appendix_L_Prevailing_Wage_County_Rate_Information.pdf PDF
Appendix_I_Definitions_FINAL.docx DOCX document
Incarcerated_Person_Communication_Services_(IPCS).pdf PDF
Appendix_J_Security_Questionnaire.docx DOCX document
Appendices_A,_B_and_D.docx DOCX document
Appendix_C_-_Cost_Proposal_FINAL.xlsx XLSX spreadsheet
Appendix_K_DOC_Facility_Site_Visit_Application.doc DOC document
State_of_Minnesota_Sample_Contract_FINAL.docx DOCX document
MNIT_RFP_FINAL.docx DOCX document
Appendix_E_Scope_of_Work_Overview_FINAL.docx DOCX document

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

Instructions

MINNESOTA DEPARTMENT OF CORRECTIONS | Electronic Services and Communications Platform RFP
Appendices F, G, and H | Vendor Submission Package
PURPOSE OF THIS WORKBOOK
This workbook is part of your proposal. Complete Appendix F (Responsibility Matrix), Appendix G (Requirements Matrix), and Appendix H (Accessibility), and submit all three tabs with your response, as required by RFP Section 4. Appendix G captures the detailed functional requirements supporting Appendix E, so your responses here should be consistent with the technical narrative you provide there.
SOURCE DOCUMENTS
Each requirement cites where it comes from: "Appendix E Sec." for the Scope of Work Overview, or "RFP Sec." for the main solicitation. Use these citations to review the full requirement language before you respond.
OTHER APPENDICES
This workbook does not include Appendix A (Responder Declarations), Appendix B (Exceptions), Appendix C (Cost Proposal), Appendix D (Responder Forms), or Appendix I (Definitions).
HOW TO COMPLETE EACH TAB
Appendix F (RACI): Review the pre-populated Contractor role for each activity and identify any proposed exceptions or assumptions in the Notes column. DOC will confirm or adjust all columns during negotiation.
Appendix G (Requirements): Respond to every requirement — do not leave rows blank. Select your compliance status in column E, cite the page/section of your proposal that addresses it in column F, and note any exceptions in column G. Appendix G is evaluated as part of the Tier 1 technical evaluation.
Appendix H (Accessibility): Respond to every requirement — do not leave rows blank. Select your conformance status in column D, describe any known gaps in column E, cite your VPAT 2.5 INT in column F, and commit to a remediation timeline (maximum 180 days after contract execution) in column G. Appendix H is evaluated separately under Accessibility.
STATUS CODES
Appendix F (RACI)
P = Primary, S = Shared/Support, A = Approval Required, I = Informed, — = Not Applicable
Appendix G (Compliance Status)
✅ Fully Meets, ⚠ Partially Meets, ❌ Does Not Meet, 🔄 Future Roadmap (provide timeframe in column G)
Appendix H (Conformance Status)
S = Supports, PS = Partially Supports, NS = Does Not Support, NA = Not Applicable, NC = Not Checked
BEFORE YOU SUBMIT
Respond to every row in Appendix F, G, and H. Incomplete responses that materially deviate from the required format and content may be rejected as non-responsive. Submit this workbook in .xlsx format. Do not password-protect or lock cells, and do not alter column structure, row order, or headers.

Appendix F - RACI

MINNESOTA DEPARTMENT OF CORRECTIONS | Electronic Services and Communications Platform RFP
APPENDIX F | Responsibility Matrix (RACI)
Review the pre-populated Contractor role for each activity and identify any proposed exceptions or assumptions in the Notes column. DOC will confirm or adjust all columns during negotiation.
Responder Legal Name: ________________________________________________ Date Submitted: _______________
#Activity / DeliverableContractorDOCMNITRECSJoint /
SharedNotes / AssumptionsAppendix E

Sec. Reference

PHASE A — VOICE CUTOVER | Target: December 1, 2027 (all 11 facilities)
1.1Site surveys and design validation — all 11 facilitiesPASSRECS approves access sequencingAppendix E Sec. 1
1.2Cabling, conduit, and pathway installationPIIARECS construction approval required; installed infrastructure becomes DOC property upon acceptanceAppendix E Sec. 1
1.3MNIT wireless access point procurement (~4,000 APs, incl. ~250 relocated)——P—MNIT-furnished and managed; contractor mounts only. ~250 relocated AP figure per RFP Sec. 2.RFP Sec. 2 / Appendix E Sec. 1
1.4Wireless access point physical mountingPIA—Contractor installs; MNIT configures network sideAppendix E Sec. 1
1.5Network closet terminations and connections——P—MNIT scope onlyAppendix E Sec. 1
1.6Network configuration, segmentation, and security settings——P—MNIT scope onlyAppendix E Sec. 1
1.7Wireless assessment to voice-grade coverage (-65 dBm RSSI or stronger)PIS—Includes adding/adjusting AP locations after activationRFP Sec. 1.3 / Appendix E Sec. 1
1.8Network testing and commissioning—IP—SMNIT performs network testing and commissioning; DOC retains final facility go-live approval.Appendix E Sec. 1
1.9Wall-mounted phone supply and installation (~900 units)PIIARECS construction approval requiredAppendix E Sec. 1, Sec. 5
1.10TRS/VRS accessibility station supply and installation (~127 units)PIIARECS construction approval requiredAppendix E Sec. 1, Sec. 5
1.11Voice system platform configurationPAS—DOC approval before activationAppendix E Sec. 7
1.12Voice system testing and voice cutoverPAS—SNo lapse in required phone access during transitionRFP Sec. 1.3
1.13As-built documentation delivery to DOCPA—IDigital format, within 30 calendar days of State acceptance at each facility; floor plans/CAD and network diagramsAppendix E Sec. 1
1.14Incumbent vendor coordination for transition-inPSI—SEngagement no later than 90 days before cutoverAppendix E Sec. 14
1.15Joint troubleshooting runbook submissionPAS—SEscalation contacts/roles, triage procedures, fault-domain determination, documentation requirementsRFP Sec. 4
1.16Facility acceptance and defect classification for go-livePA——SCritical/Major/Minor classification; Major resolved within 30 days, Minor within 90 days; go-live approval rests solely with DOCRFP Sec. 4
1.17Training plan for DOC administrators, facility users, investigators, and technical staffPA——RFP Sec. 4
1.18Account for CIP program schedule and operational requirementsPS——MCF-Togo and MCF-Willow River (Challenge Incarceration Program)RFP Sec. 2
PHASE B — PORTABLE DEVICE DEPLOYMENT | Target: November 1, 2028 (concurrent with or following voice cutover)
2.1Device procurement, staging, and enrollmentPI——Appendix E Sec. 4
2.2Biometric enrollment of incarcerated persons (if biometric proposed)PS——DOC staff facilitate facility access; equity testing/disclosure requiredAppendix E Sec. 4
2.3Device assignment and initial distributionPS——Appendix E Sec. 4
2.4Messaging system activation and configurationPAI—DOC approval before activationAppendix E Sec. 8
2.5Media and content library activationPA——DOC content approval required prior to go-liveAppendix E Sec. 10
2.6Education and reentry platform activationPA——Appendix E Sec. 11
2.7Shared kiosk supply, installation, and configurationPAIARECS approval for mounting workAppendix E Sec. 5
2.8Facility acceptance testingPAS—SDOC issues final go-live approval; contractor cannot self-declare readyRFP Sec. 4
2.9Post-go-live stabilization monitoringPSS—Appendix E Sec. 16
SYSTEM INTEGRATIONS
3.1CACTAS (Cashless Commissary and Trust Fund Accounting System) integrationPSS—SMNIT provides API access and environmentAppendix E Sec. 12, Sec. 15
3.2Offender Management System (OMS) integrationPSS—SAppendix E Sec. 15
3.3User identity sync — enrollment, transfer, restriction, releasePAS—Near real-time propagation requiredAppendix E Sec. 15
3.4DOC administrative account provisioning and role managementPA——Appendix E Sec. 15
3.5Reporting and export handoff configurationPAS—Appendix E Sec. 15
3.6Subcontractor performance management and accountabilityPI——Prime vendor manages subcontractor role and performanceRFP Sec. 4
ONGOING OPERATIONS
4.1Platform uptime monitoring and availability managementPIS—MNIT monitors network layer; contractor monitors application layerAppendix E Sec. 2, Sec. 16
4.2Security patch management — critical/high patches within 30 days, standard within 90 daysPA——Appendix E Sec. 16
4.3Device spare inventory maintenance (minimum 10% per facility)PA——Appendix E Sec. 4
4.4Device replacement logistics and repairPI——Replacement within 2 calendar days; 1 day where on-site spare existsAppendix E Sec. 16
4.5Network performance monitoring—IP—MNIT responsible for network-layer performanceAppendix E Sec. 2
4.6Joint troubleshooting — application vs. network degradationPIP—SPer joint runbook (see Phase A, item 1.15)RFP Sec. 4
4.7Content governance and prohibited content removalPA——DOC initiates; contractor executes without delayAppendix E Sec. 10
4.8Remote camera disable (device / housing unit / facility-wide)PA——No physical possession or vendor intervention requiredAppendix E Sec. 13
4.9AI monitoring model changes — prior written DOC approval requiredPA——30-day advance notice required before any model or threshold changeAppendix E Sec. 13
4.10Biometric authentication equity testing and demographic-disparity disclosurePA——Required if biometric authentication is proposedAppendix E Sec. 4
4.11Non-contact visitation monitoring parity with voice communication controlsPA——Recording, playback, keyword search, administrative reviewAppendix E Sec. 9
4.12DOC approval required before offering any optional paid service—A——Only where legally permissible and specifically approved by DOCRFP Sec. 1.1
SUPPORT
5.1Dedicated correctional service desk (24/7/365, incl. holidays)PI——Separate line from general consumer supportAppendix E Sec. 16
5.2Priority 1 incident response (30-min acknowledgment / 4-hr resolution)PIS—MNIT engaged for network-layer issuesAppendix E Sec. 16
5.3Priority 2 incident response (2-hr acknowledgment / 8-hr resolution)PIS—Appendix E Sec. 16
5.4Priority 3 / Priority 4 incident responsePI——P3: 4-hr response / 3-calendar-day resolution. P4: response within 1 calendar dayAppendix E Sec. 16
5.5Accommodation and TRS-related support requests treated as Priority 1PI——ASL interpreters, alternative formats, any TRS-related needAppendix E Sec. 16
5.6On-site field support and hardware repairPI——Appendix E Sec. 16
5.7Reportable service event notification and post-incident reportingPA——>10% of devices at one facility down >30 min = reportable; root-cause notice within 24 hrs; post-incident report within 5 calendar daysAppendix E Sec. 16
5.8Annual downtime summary reportingPA——Within 30 calendar days of each contract year endAppendix E Sec. 16
DATA OWNERSHIP AND TRANSITION
6.1Scheduled automated data exportPI——DOC-designated operational dataAppendix E Sec. 14
6.2On-demand data exportPA——Executed within timeframe agreed with DOCAppendix E Sec. 14
6.3System configuration documentationPA——Maintained current and available throughout program termAppendix E Sec. 14
6.4Transition-out plan submission (180 days before expiry)PA——SCovers data export, config docs, equipment removal, continued operation through final dayAppendix E Sec. 14
6.5Successor vendor / DOC technical cooperation during transitionPA——SEngagement no later than 90 days before cutover; no service disruption used as leverageAppendix E Sec. 14
6.6Data retention (minimum 7 years from date of creation)PI——Or longer if required by law or directed by DOC in writingAppendix E Sec. 14
6.7Refund determination and execution at contract closeoutPA——Covers eligible media/service balancesAppendix E Sec. 14

Appendix G - Requirements

MINNESOTA DEPARTMENT OF CORRECTIONS | Electronic Services and Communications Platform RFP
APPENDIX G | Functional Requirements and Specifications Matrix
For each requirement, select a compliance status from the dropdown (column E). Enter your proposal page/section reference in column F. Add exceptions or clarifications in column G. Column H is reserved for DOC evaluator use — do not edit.
Responder Legal Name: ________________________________________________ Date Submitted: _______________
Req #Requirement SummaryTypeRFP Sec. / App E Sec.Compliance Status
(select from list)Proposal Page /
Section ReferenceClarifying Notes / ExceptionsDOC Score

(Internal Only)

A. INFRASTRUCTURE DEPLOYMENT AND OWNERSHIP
A.1Design installation approach and site-specific sequencing for all 11 facilitiesCriticalRFP 4 / App E 1DOC Use Only
A.2Install required network cabling, conduit, pathways, supports, and associated materialsCriticalApp E 1DOC Use Only
A.3Coordinate facility access with RECS, DOC facility leadership, and MNIT; comply with security restrictionsCriticalApp E 1DOC Use Only
A.4Mount MNIT-furnished wireless access points in approved locations (~4,000 APs, incl. ~250 relocated)CriticalRFP 2 / App E 1DOC Use Only
A.5Define minimum connectivity requirements per facility (bandwidth, latency, redundancy)CriticalRFP 4 / App E 1DOC Use Only
A.6Perform post-activation wireless assessment to voice-grade coverage of -65 dBm RSSI or strongerCriticalRFP 1.3 / App E 1DOC Use Only
A.7Provide as-built documentation (digital, incl. floor plans/CAD and network diagrams) within 30 calendar days of State acceptance at each facilityCriticalApp E 1DOC Use Only
A.8Provide a dedicated vendor project manager as the named point of accountability to DOCCriticalApp E 1DOC Use Only
A.9Submit project plan, risk mitigation plan, communications plan, and governance plan prior to implementation kickoffCriticalApp E 1DOC Use Only
A.10Identify and provide any additional hardware required beyond MNIT-furnished access pointsCriticalApp E 1DOC Use Only
A.11Confirm required phone access will not lapse during transition, cutover, replacement, maintenance, or outage responseCriticalRFP 1.3, 4DOC Use Only
A.12Complete full, uninterrupted voice cutover across all 11 facilities by December 1, 2027 (Phase A)CriticalRFP 1.2, 1.3DOC Use Only
A.13Begin staged portable device implementation June 2027 and complete statewide deployment by November 1, 2028 (Phase B)CriticalRFP 1.2, 1.3DOC Use Only
A.14Submit joint troubleshooting runbook covering escalation contacts/roles, triage procedures, fault-domain determination, and documentation requirementsCriticalRFP 4DOC Use Only
A.15Classify implementation defects as Critical (blocks go-live), Major (resolved within 30 days of go-live), or Minor (tracked and resolved within 90 days); no facility goes live with an unresolved Critical defectCriticalRFP 4DOC Use Only
A.16Provide a training plan for DOC administrators, facility users, investigators, and technical staffCriticalRFP 4DOC Use Only
A.17Convey ownership to DOC upon installation of vendor-furnished cabling and pathway infrastructureCriticalRFP 1.1 / App E 1DOC Use Only
A.18Account for Challenge Incarceration Program (CIP) schedules and operational requirements at MCF-Togo and MCF-Willow River in deployment and service delivery plansCriticalRFP 2DOC Use Only
B. SYSTEM ARCHITECTURE AND HOSTING ENVIRONMENT
B.1Support encrypted data transmission in transit and protection of data at restCriticalApp E 2DOC Use Only
B.2Provide redundancy for major application components (voice, messaging, video visitation, device management, admin dashboard)CriticalApp E 2DOC Use Only
B.3Identify and disclose single points of failure in the proposalCriticalApp E 2DOC Use Only
B.4Maintain documented failover, disaster recovery, backup, and planned-maintenance practicesCriticalApp E 2DOC Use Only
B.5Support scaling for peak activity across facilitiesCriticalApp E 2DOC Use Only
B.6Separate and secure administrative functions from end-user functionsCriticalApp E 2DOC Use Only
B.7Support logging and traceability for administrative actions, security events, and user activityCriticalApp E 2DOC Use Only
B.8Describe system architecture in full detail: hosted components, geographic location, interdependencies, authentication flows, integration touchpoints, limitationsCriticalRFP 4 / App E 2DOC Use Only
C. INTEGRATED PLATFORM OVERVIEW
C.1Present platform as an integrated suite (or tightly integrated components), not siloed productsCriticalApp E 3DOC Use Only
C.2Apply consistent identities, contact controls, suspension logic, logging, permissions, and rule enforcement across modulesCriticalApp E 3DOC Use Only
C.3Integrate assigned device access, shared kiosk/fixed-station access, voice, messaging, video visitation, media/content, education/reentry, financial tools, admin notices, monitoring/reporting, and accessibility settingsCriticalApp E 3DOC Use Only
C.4Offer optional paid services only where legally permissible and specifically approved by DOCCriticalRFP 1.1DOC Use Only
D. ELECTRONIC DEVICE PLATFORM REQUIREMENTS
D.1Provide one assigned electronic device per incarcerated person as primary personal access pointCriticalApp E 4DOC Use Only
D.2Identify brand, model, and operating system of each device proposedCriticalRFP 4 / App E 4DOC Use Only
D.3Require two-factor authentication on devicesCriticalApp E 4DOC Use Only
D.4If biometric authentication is proposed, demonstrate equitable performance across demographic groups (incl. darker skin tones) and disclose known error rates/disparitiesCriticalRFP 4 / App E 4DOC Use Only
D.5Ensure biometric authentication can be disabled per-device or per-user by authorized DOC staff without vendor interventionCriticalApp E 4DOC Use Only
D.6Describe authentication flow for routine use, reassignment, recovery, transfer, suspension, restriction, and releaseCriticalRFP 4 / App E 4DOC Use Only
D.7Bear all device replacement costs; no charge for device damage may be assessed to the incarcerated personCriticalApp E 4DOC Use Only
D.8Describe replacement timeline and intake-to-return workflow for damaged devicesCriticalRFP 4 / App E 4DOC Use Only
D.9Provide regulatory-mandated device/successor-product transitions at no additional cost to DOCCriticalRFP 4 / App E 4DOC Use Only
D.10Support administrative search of device content without the person's cooperation, and remote deletion without physical possessionCriticalApp E 4DOC Use Only
D.11Auto-delete attachments from portable device when parent message is deleted by authorized staffCriticalApp E 4DOC Use Only
D.12Maintain spare inventory equal to at least 10% of deployed assigned devices per facilityCriticalApp E 4DOC Use Only
D.13Provide packaging/prepaid shipping (or equivalent) for malfunctioning units, and non-disruptive update proceduresCriticalApp E 4DOC Use Only
D.14Display: minimum 7-inch screen, scratch-resistant glass or equivalentCriticalApp E 4DOC Use Only
D.15Processor: sufficient capability to support simultaneous voice calling, video visitation, messaging, and media playback without degradation under normal operating conditionsCriticalApp E 4DOC Use Only
D.16Storage: minimum 32 GB, with at least 1 GB reserved for DOC-loaded materialsCriticalApp E 4DOC Use Only
D.17Battery: minimum 8 hours active use under mixed-use conditionsCriticalApp E 4DOC Use Only
D.18Durability: meet or exceed MIL-STD-810 or DOC-approved equivalent; tamper/disassembly/contraband-concealment resistantCriticalApp E 4DOC Use Only
D.19Wireless: Wi-Fi only, compatible with MNIT-furnished AP environment; no cellular, Bluetooth, or other unapproved interfacesCriticalApp E 4DOC Use Only
D.20Front-facing camera and microphone for video visitation; rear camera disabled or absent unless DOC-approvedCriticalApp E 4DOC Use Only
D.21Disclose OS version, update cadence, and end-of-support timeline; no deployment on end-of-support OS without written DOC approval and remediation planCriticalApp E 4DOC Use Only
D.22Support standard OS-level accessibility features (screen readers, display scaling, closed captioning, assistive touch) without vendor disabling themCriticalApp E 4DOC Use Only
E. SHARED KIOSKS AND FIXED COMMUNICATION STATIONS
E.1Support a hybrid endpoint environment: assigned devices, shared kiosks/fixed stations, wall-mounted phones, TRS/VRS stationsCriticalApp E 5DOC Use Only
E.2Provide approximately 900 wall-mounted phones across DOC facilitiesCriticalApp E 5DOC Use Only
E.3Provide approximately 127 TRS/VRS accessibility communication stations across DOC facilitiesCriticalApp E 5DOC Use Only
E.4Support voice calling, video visitation access, accessibility workflows, and other approved functions at fixed endpointsCriticalApp E 5DOC Use Only
E.5Be correctional-grade: appropriate mounting, tamper resistance, monitoring, session controls, physical/digital accessibility compatibilityCriticalApp E 5DOC Use Only
F. DEVICE MANAGEMENT AND ADMINISTRATIVE CONTROL PLATFORM
F.1Provide centralized device management/admin control platform for the full device and endpoint fleetCriticalApp E 6DOC Use Only
F.2Enable routine configuration, status review, restrictions, and scheduling without vendor interventionCriticalApp E 6DOC Use Only
F.3Provide dashboards/reports: distribution/assignment status, utilization, failure/replacement rates, firmware/software version status, restriction/suspension historyCriticalApp E 6DOC Use Only
F.4Maintain a complete, tamper-evident audit log of admin actions (remote lock/disable/reset, content removal), accessible without vendor interventionCriticalApp E 6DOC Use Only
F.5Allow authorized DOC staff to control device-based voice calling by facility, housing unit, classification, program status, or individual, without vendor interventionCriticalApp E 6DOC Use Only
F.6Support device enrollment/assignment; status tracking (active, spare, lost, damaged, restricted, in-repair, decommissioned)CriticalApp E 6DOC Use Only
F.7Support remote lock, remote disable, remote reset, and other emergency admin controlsCriticalApp E 6DOC Use Only
F.8Control applications, content availability, communication permissions, and service permissionsCriticalApp E 6DOC Use Only
F.9Provide visibility into device/endpoint activity, last contact, health, and operational statusCriticalApp E 6DOC Use Only
F.10Support group-based and individual rule assignment by facility, housing unit, classification, program status, and userCriticalApp E 6DOC Use Only
G. VOICE COMMUNICATION SYSTEM REQUIREMENTS
G.1Voice calls provided at no charge to incarcerated persons and call recipients, per Minn. Stat. § 241.252CriticalRFP 2 / App E 7DOC Use Only
G.2Comply with the Martha Wright-Reed Just and Reasonable Communications Act (47 U.S.C. § 262) and FCC implementing rules (47 C.F.R. Part 64, Subpart MM), including applicable rate caps under FCC 23-111 and successor ordersCriticalRFP 2DOC Use Only
G.3No rate, fee, surcharge, or ancillary charge may exceed the applicable FCC cap for the call or service typeCriticalRFP 2DOC Use Only
G.4Provide prompts/announcements in English, Spanish, Somali, and Mandarin at minimum; support additional languages (≥50 speakers) within 180 days of DOC's population reportCriticalApp E 7DOC Use Only
G.5Provide secure, correctional-grade telephone hardware; single-line security-style telephones where required by security levelCriticalApp E 7DOC Use Only
G.6Ensure telephones comply with 47 C.F.R. §§ 68.316 and 68.317 and the TIA-4953 standard, where applicableCriticalApp E 7DOC Use Only
G.7Maintain fraud-prevention capabilities; support anti-fraud and anti-three-way-call controlsCriticalApp E 7DOC Use Only
G.8Operate on digital/VoIP infrastructure; support TTY accessibility via digital-to-analog conversion (no POTS line availability assumed)CriticalApp E 7DOC Use Only
G.9Require voice-activated account access or equivalent voice biometric function; use continuous voice detection with notice before disconnecting on unauthorized speakerCriticalApp E 7DOC Use Only
G.10Provide call announcements identifying the call as originating from a Minnesota correctional facilityCriticalApp E 7DOC Use Only
G.11Allow called parties to accept, reject, or block calls; support global/individual number blocking (area code/exchange blocking, ≥25,000 entries)CriticalApp E 7DOC Use Only
G.12Record a reason code and editable notes for blocked numbers; maintain contact allow lists fully configurable by DOCCriticalApp E 7DOC Use Only
G.13Support configurable call limits by individual, classification, housing unit, or facilityCriticalApp E 7DOC Use Only
G.14Ensure restrictions follow the incarcerated person during intra-agency transfer in near real timeCriticalApp E 7DOC Use Only
G.15Allow incarcerated persons to reset PINs without DOC staff involvementCriticalApp E 7DOC Use Only
H. ELECTRONIC MESSAGING SYSTEM REQUIREMENTS
H.1Provide secure messaging with contact-approval rules, restrictions, suspensions, monitoring, printing, retention, and admin handling controlled by DOCCriticalApp E 8DOC Use Only
H.2Support routine staff-to-incarcerated-person operational/administrative messaging, separate from legal/protected communicationsCriticalApp E 8DOC Use Only
H.3Allow incarcerated persons to view incoming messages and compose outgoing messages from their assigned devicesCriticalApp E 8DOC Use Only
H.4Restrict ordinary messages to text only — no embedded images or unauthorized attachmentsCriticalApp E 8DOC Use Only
H.5Ensure all messages are printable, with headers including date and current facility locationCriticalApp E 8DOC Use Only
H.6Allow authorized staff to print incoming messages by user, living unit, or dateCriticalApp E 8DOC Use Only
H.7Require external users to initiate contact by searching for the incarcerated person by name or Incarcerated Person IdentifierCriticalApp E 8DOC Use Only
H.8Support hiding protected incarcerated persons from general public search queriesCriticalApp E 8DOC Use Only
H.9Allow photo attachments (JPEG/PNG) and short video attachments (≤30 seconds, if enabled), subject to DOC content governanceCriticalApp E 8DOC Use Only
H.10Restrict messaging to approved contacts; support spam/account blocking as directed by DOCCriticalApp E 8DOC Use Only
H.11Support attachment deletion when associated messages are deleted by authorized staffCriticalApp E 8DOC Use Only
H.12Support review, printing, export, retention, and monitoring of incoming/outgoing messages, with audit loggingCriticalApp E 8DOC Use Only
I. VIDEO VISITATION SYSTEM REQUIREMENTS
I.1Provide secure, scheduled video visitation with DOC-controlled scheduling, approval, restriction, and cancellation rulesCriticalApp E 9DOC Use Only
I.2Support separate, administratively distinct workflows for legal/court-related/protected video communications; AI monitoring not applied to these sessionsCriticalApp E 9DOC Use Only
I.3Support non-contact visitation monitoring that replicates voice-communication controls (recording, playback, keyword search, admin review) where approved by DOCCriticalApp E 9DOC Use Only
I.4Disclose any in-person visitation scheduling capability (request submission, approval workflow, slot/capacity management, notifications) — preferred but not mandatory; kept separate from protected-visitation access controlsIdealApp E 9DOC Use Only
I.5Support video visits via assigned personal devices and via kiosk/fixed-station endpointsCriticalApp E 9DOC Use Only
I.6Target minimum 720p video (incarcerated-person side) and 480p (external-user side) under standard broadband conditionsCriticalApp E 9DOC Use Only
I.7Provide refund/credit/remediation for paid-visit cancellation, outage, or quality failure through no fault of the userCriticalApp E 9DOC Use Only
I.8Provide web-based access for external users; require acceptance of DOC-approved terms and conditionsCriticalApp E 9DOC Use Only
I.9Allow DOC to restrict availability by facility, living unit, endpoint type, or individual; allow staff to cancel any scheduled visitCriticalApp E 9DOC Use Only
I.10Automatically notify users of suspensions, start/end dates, and reasonsCriticalApp E 9DOC Use Only
J. DIGITAL MEDIA AND CONTENT SERVICES REQUIREMENTS
J.1MusicCriticalApp E 10DOC Use Only
J.2Books and eBooksCriticalApp E 10DOC Use Only
J.3MoviesCriticalApp E 10DOC Use Only
J.4Television programsCriticalApp E 10DOC Use Only
J.5GamesCriticalApp E 10DOC Use Only
J.6ApplicationsCriticalApp E 10DOC Use Only
J.7Audiobooks, podcasts, internet radio, and news or sports feedsCriticalApp E 10DOC Use Only
J.8Fully disclose pricing structure, charged party, and financial treatment for each media offeringCriticalApp E 10DOC Use Only
J.9Ensure no bundle recovers cost for voice or other services that must be provided at no charge under lawCriticalApp E 10DOC Use Only
J.10Provide only DOC-approved content (contraband/prohibited-content policy compliant) and applicable industry ratingsCriticalApp E 10DOC Use Only
J.11Allow DOC to review, approve, report, restrict, and remove content, and control availability by facility/user groupCriticalApp E 10DOC Use Only
K. EDUCATION, PROGRAMMING, REENTRY, AND DIGITAL SERVICES
K.1DOC-facilitated assessments — no user-facing chargeCriticalApp E 11DOC Use Only
K.2Applications for department programs or services — no user-facing chargeCriticalApp E 11DOC Use Only
K.3Grievances and requests — no user-facing chargeCriticalApp E 11DOC Use Only
K.4Medical requests and healthcare-request submission access — no user-facing chargeCriticalApp E 11DOC Use Only
K.5Behavioral health requests — no user-facing chargeCriticalApp E 11DOC Use Only
K.6Legal library access — no user-facing chargeCriticalApp E 11DOC Use Only
K.7Staff notices and facility communications — no user-facing chargeCriticalApp E 11DOC Use Only
K.8Account balance and transaction history, where applicable — no user-facing chargeCriticalApp E 11DOC Use Only
K.9High school equivalency diploma / secondary or postsecondary educational content (may be user-charged)IdealApp E 11DOC Use Only
K.10Coursework modules and digital textbooks (may be user-charged)IdealApp E 11DOC Use Only
K.11Cognitive behavioral programming (may be user-charged)IdealApp E 11DOC Use Only
K.12Substance use education (may be user-charged)IdealApp E 11DOC Use Only
K.13Self-guided mental health and well-being programming (may be user-charged)IdealApp E 11DOC Use Only
K.14Other rehabilitative programming options (may be user-charged)IdealApp E 11DOC Use Only
K.15Job readiness and employment resources, such as CareerEdge and CareerOneStop (may be user-charged)IdealApp E 11DOC Use Only
K.16Financial literacy resources (may be user-charged)IdealApp E 11DOC Use Only
K.17Housing resource information (may be user-charged)IdealApp E 11DOC Use Only
K.18Community reintegration resources or online resource repositories (may be user-charged)IdealApp E 11DOC Use Only
K.19Reentry planning or goal-setting resources (may be user-charged)IdealApp E 11DOC Use Only
L. FINANCIAL SERVICES AND ACCOUNT ACCESS FUNCTIONS
L.1Describe integration with CACTAS: available functions, administrative-only functions, and adaptability if DOC changes trust-account systemsCriticalRFP 4 / App E 12DOC Use Only
L.2If offering money-transfer/funding/release-card services, identify all fees, surcharges, processor fees, and settlement/commission arrangementsCriticalApp E 12DOC Use Only
L.3Provide account balance review, transaction history review, and electronic receipts for purchases/chargesCriticalApp E 12DOC Use Only
L.4Provide release-card issuance or related release support functions where applicableIdealApp E 12DOC Use Only
M. SECURITY, MONITORING, INTELLIGENCE, AND INVESTIGATIVE TOOLS
M.1Allow authorized staff to retain, access, search, filter, export, and manage operational records without vendor interventionCriticalApp E 13DOC Use Only
M.2Call recording and playbackCriticalApp E 13DOC Use Only
M.3Messaging review and exportCriticalApp E 13DOC Use Only
M.4Video visitation monitoring where approved by DOCCriticalApp E 13DOC Use Only
M.5Device activity logsCriticalApp E 13DOC Use Only
M.6Role-based access to monitoring functionsCriticalApp E 13DOC Use Only
M.7Keyword and phrase search within messages and other reviewable contentCriticalApp E 13DOC Use Only
M.8Communication pattern and relationship analysisCriticalApp E 13DOC Use Only
M.9Ability to identify high-volume or unusual contact patternsCriticalApp E 13DOC Use Only
M.10Historical record retrieval by person, contact, date range, facility, housing unit, or other relevant filterCriticalApp E 13DOC Use Only
M.11Export of records for investigative or legal use with chain-of-access loggingCriticalApp E 13DOC Use Only
M.12Allow authorized DOC staff to remotely disable the front-facing camera on any assigned device — individually, by housing unit, or facility-wide — without physical possession or vendor interventionCriticalApp E 13DOC Use Only
M.13AI monitoring: human review required before any consequential action based on an AI-generated alert, score, or recommendationCriticalApp E 13DOC Use Only
M.14AI monitoring: plain-language explainability of outputs, inputs, and alert thresholds; no black-box systems without prior written DOC approvalCriticalApp E 13DOC Use Only
M.15AI monitoring: disclose known bias/accuracy limitations, error rates, and demographic disparitiesCriticalApp E 13DOC Use Only
M.16AI monitoring: excluded from legal, privileged, or otherwise protected communicationsCriticalApp E 13DOC Use Only
M.17AI monitoring: 30-day advance notice of any material model/algorithm/threshold change, with DOC approval rightCriticalApp E 13DOC Use Only
M.18AI monitoring: maintain complete, DOC-reviewable audit log of all AI-generated alerts, flags, and risk scoresCriticalApp E 13DOC Use Only
N. DATA OWNERSHIP, RECORDS ACCESS, AND TRANSITION REQUIREMENTS
N.1All communications data and platform-generated records remain DOC property; vendor claims no ownership interestCriticalApp E 14DOC Use Only
N.2Describe data retention architecture, default retention periods, and format/structure of historical usage data available to DOCCriticalRFP 4 / App E 14DOC Use Only
N.3Retain all data categories for a minimum of 7 years from date of creation, or longer if required by law or directed by DOC in writingCriticalApp E 14DOC Use Only
N.4Retain data in exportable, searchable formats usable without proprietary vendor toolsCriticalApp E 14DOC Use Only
N.5Support both on-demand and scheduled/automated export in standard, reasonably usable formatsCriticalApp E 14DOC Use Only
N.6Cooperate fully with incumbent vendor during transition-in and successor vendor/DOC during transition-outCriticalApp E 14DOC Use Only
N.7Engage with DOC and any incumbent vendor no later than 90 days before planned cutoverCriticalApp E 14DOC Use Only
N.8Provide a written transition-out plan (data export, configuration documentation, equipment removal, continued operation through final day) no later than 180 days before program expirationCriticalApp E 14DOC Use Only
N.9Support refund determination and refund execution for eligible balances at contract closeoutCriticalApp E 14DOC Use Only
O. SYSTEM INTEGRATION REQUIREMENTS
O.1Integrate with CACTAS or successor trust-account systemCriticalApp E 15DOC Use Only
O.2Integrate with Offender Management System (OMS) or comparable inmate records databaseCriticalApp E 15DOC Use Only
O.3Support user identity creation, update, transfer, restriction, and release handlingCriticalApp E 15DOC Use Only
O.4Support facility and housing-unit location awareness for communications controlsCriticalApp E 15DOC Use Only
O.5Support trust-account balance, transaction-history, and approved account-access data flowsCriticalApp E 15DOC Use Only
O.6Support DOC administrative account creation and role managementCriticalApp E 15DOC Use Only
O.7Provide reporting/export handoff points and MNIT handoff points for network connectivity, troubleshooting, and shared operational supportCriticalApp E 15DOC Use Only
O.8For each required integration, describe purpose, dependencies, timing, error handling, and fallback/manual proceduresCriticalApp E 15DOC Use Only
P. SUPPORT AND SERVICE LEVELS
P.1Provide a dedicated service desk reachable 24/7/365 including holidays, with a separate line for DOC facility staffCriticalApp E 16DOC Use Only
P.2Priority 1 (Critical): 30-minute response / 4-hour resolution for complete loss of voice, video, or platform access affecting a facility or multiple housing unitsCriticalApp E 16DOC Use Only
P.3Priority 2 (High): 2-hour response / 8-hour resolution for significant degradation of a core function affecting a housing unit or defined user groupCriticalApp E 16DOC Use Only
P.4Priority 3 (Standard): 4-hour response / 3-calendar-day resolution for degraded functionality with available workaroundsCriticalApp E 16DOC Use Only
P.5Priority 4 (Low): response within 1 calendar day for general inquiries/configuration assistanceCriticalApp E 16DOC Use Only
P.6Treat accommodation requests (ASL interpreters, alternative formats) and any TRS-related support need as Priority 1 regardless of underlying requestCriticalApp E 16DOC Use Only
P.7Immediately begin remote triage upon incident declaration, regardless of on-site response timing; provide on-site response within 4 hours (P1) / 8 hours (P2) when remote resolution is not achievableCriticalApp E 16DOC Use Only
P.8Ensure critical notices and status pages are accessible/compatible with assistive technologies (screen readers, switch devices)CriticalApp E 16DOC Use Only
P.9Provide a proposed SLA covering network performance, device performance, and support availability/response times, meeting or exceeding these minimumsCriticalApp E 16DOC Use Only
P.10Platform availability: 99.5% uptime measured monthly, excluding approved scheduled maintenanceCriticalApp E 16DOC Use Only
P.11Unplanned downtime affecting >10% of assigned devices at a single facility for >30 consecutive minutes is a reportable service event; written root-cause notification within 24 hoursCriticalApp E 16DOC Use Only
P.12Provide a written post-incident report within 5 calendar days of any reportable service event (downtime, root cause, affected users/facilities, corrective actions)CriticalApp E 16DOC Use Only
P.13Provide device replacement within 2 calendar days of confirmed malfunction (1 calendar day where on-site spare inventory exists)CriticalApp E 16DOC Use Only
P.14Provide at least 5 calendar days written notice before any scheduled maintenance window affecting availabilityCriticalApp E 16DOC Use Only
P.15Apply critical/high security patches within 30 days of release; standard updates within 90 daysCriticalApp E 16DOC Use Only
P.16Provide an annual downtime summary report within 30 calendar days of each contract year endCriticalApp E 16DOC Use Only
Q. DATA SECURITY AND COMPLIANCE
Q.1Perform all storage and processing of information within the borders of the United States, including work by subcontractors at all levelsCriticalRFP 6DOC Use Only
Q.2Comply with GovRAMP cloud security requirements per Sample Contract Exhibit A, Supplement 1, clause 1.20 (contracts involving High Risk Data)CriticalRFP 6DOC Use Only
Q.3Ensure no contract term is inconsistent with the Minnesota Government Data Practices Act (Minn. Stat. Ch. 13)CriticalRFP 6DOC Use Only

Appendix H - Accessibility

MINNESOTA DEPARTMENT OF CORRECTIONS | Electronic Services and Communications Platform RFP
APPENDIX H | Accessibility Conformance and Assistive Services Response
Select conformance status from the dropdown (column D). Describe known gaps in column E. Reference your VPAT 2.5 INT in column F. Commit to a remediation timeline (not to exceed 180 days after contract execution) in column G. Column H is reserved for DOC evaluator use — do not edit.
Responder Legal Name: ________________________________________________ Date Submitted: _______________
#Component / FunctionStandard / RequirementConformance
StatusKnown Gaps or LimitationsVPAT 2.5 INT
ReferenceRemediation Timeline
(max 180 days post-execution)DOC Notes

(Internal Only)

PROGRAM-WIDE CONFORMANCE (Appendix E Sec. 3; RFP Sec. 4)
A.1All platform components accessible to incarcerated persons, external users, or DOC staff conform to WCAG 2.1 Level AA and Section 508WCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.2Completed VPAT® 2.5 INT (Nov 2023), prepared or validated by an external accessibility testing organization, submitted for all proposed software, hardware, and websites, with Section 508 and WCAG 2.1 A/AA sections completed. If the VPAT itself has not been third-party prepared or validated, submit an independent third-party certification or attestation of accessibility testing and compliance level, or a third-party summary report of findings (including identified issues, severity ratings, and remediation status), in addition to the Responder-completed VPAT.WCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.3Where full conformance is not currently achievable, specific unmet criteria identified with a remediation timeline not to exceed 180 days after contract executionWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.4Accessibility documentation dated within the past 12–24 months, reflecting the proposed product/service version, with sufficient detail for independent verification of testing scope and methodologyWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.5Staff/contractor knowledge and skills for creating accessible digital technology describedWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.6Accessibility strategy, tools, design process, testing, and ongoing validation approach describedWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
A.7Third-party applications integrated with the platform disclosed where full accessibility conformance cannot be confirmed, with a remediation or alternative-access planWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
ASSIGNED DEVICES (Appendix E Sec. 4)
B.1Standard OS-level accessibility features (screen readers, display scaling, closed captioning, assistive touch) supported and not disabled by vendor platform or device management controlsWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
B.2Accessible authentication path available for users unable to use biometric authentication, while satisfying required authentication controlsWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
SHARED KIOSKS AND FIXED COMMUNICATION STATIONS (Appendix E Sec. 5)
B.3Kiosks and fixed stations are correctional-grade with physical and digital accessibility compatibility appropriate to secure deploymentWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
B.4Wall-mounted phones and TRS/VRS accessibility stations support accessible physical and audio accessWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
ELECTRONIC MESSAGING (Appendix E Sec. 8)
C.1Messaging platform (assigned device and admin side) conforms to WCAG 2.1 AA / Section 508WCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
VIDEO VISITATION (Appendix E Sec. 9)
D.1Video visitation platform conforms to WCAG 2.1 AA / Section 508; supports accessible scheduling and notificationWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
D.2Non-contact visitation monitoring and controls remain accessible and consistent with platform-wide conformanceWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
DEVICE MANAGEMENT AND ADMINISTRATIVE INTERFACES (Appendix E Sec. 6)
E.1DOC administrative portal (device management, reporting, monitoring) conforms to WCAG 2.1 AA / Section 508WCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
SUPPORT AND SERVICE LEVELS (Appendix E Sec. 16)
F.1Critical notices and status pages accessible and compatible with assistive technologies, including screen readers and switch devicesWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only
F.2Accommodation requests (e.g., ASL interpreters, alternative formats) and any TRS-related support need treated as Priority 1 regardless of the underlying requestWCAG 2.1 Level AA; Section 508 (29 U.S.C. § 794d; 36 CFR Part 1194); MN Digital Accessibility StandardDOC Use Only

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