Schedule A, Attachment 2- Prisoner Services Business Specifications Worksheet v2.docx

DOCX document 303 KB Posted

Attached to
MDOC Inmate Network, Applications & Services RFS
Solicitation number
RFP-171-250000002079-4
Issued by
Alger County, Michigan

About this file

This document is a Business Specifications Worksheet for the Michigan Department of Corrections (MDOC) seeking a comprehensive prisoner services technology solution. The solicitation covers multiple integrated digital services including electronic deposits and release debit cards, multimedia services, prisoner telephone systems, video visitation, messaging platforms, educational services, document repositories, store services, and electronic law library access. The proposed solution requires a sophisticated, secure technology platform that enables communication, entertainment, educational, and administrative functions for prisoners while maintaining strict security protocols, monitoring capabilities, and administrative controls for MDOC staff.

The technology solution must interface with existing MDOC systems, provide multilingual support, ensure data privacy and security, and offer advanced reporting and intelligence gathering capabilities. Key requirements include role-based access control, comprehensive logging, preventing prisoner-to-prisoner communications, supporting ADA compliance, and enabling MDOC staff to manage and restrict various system functionalities. The contractor will be responsible for implementing, maintaining, and supporting the entire ecosystem of digital services, with specific performance metrics, response times, and service level agreements. The solution must also provide mechanisms for refunds, data export, and integration with existing intelligence and offender management systems, with potential future expansions into additional operational support functions.

View the file

Other files

Show all 18

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

SCHEDULE A, ATTACHMENT 2: PRISONER SERVICES BUSINESS SPECIFICATIONS WORKSHEET

Instructions for Completing the Business Specifications Worksheet

Contractor must respond to each business Specification on how they will meet the requirements below for each system or service it is bidding on. Contractor must not alter the document. The Business Specifications Worksheet contains columns and is defined as follows:

Column A: Business Specification number.

NOTE:

· The “Required” section of the Business Specifications Worksheet lists items that the State requires to be part of the Solution. “Required” items will be evaluated and scored upon per the State evaluation process.

· The “Optional” section of the Business Specifications Worksheet lists items that are not required at the time of the solicitation but may be desired by the State in the future. Such “Optional” items will be evaluated and used in a best value award recommendation Column B: Business Specification description.

Column C: Contractor must indicate how it will comply with the business Specification. Contractor must enter “Y” to one of the following:

Current Capability – This capability is available in the proposed Solution with no additional configuration or cost

· Requires Configuration – This capability can be met through Contractor-supported changes to existing settings and application options as part of the initial implementation at no additional cost (e.g., setting naming conventions, creating user-defined fields).

· Customizations to Software Required – The requirement can be met through Contractor modifying the underlying source code, which can be completed as part of the initial implementation.

· Future Enhancement – This capability is a planned enhancement to the base software and will be available within the next 12 months of contract execution at no additional cost.

· Not Available – This capability is not currently available, and a future enhancement is not planned.

NOTE: Configuration is referred to as a change to the Solution that must be completed by the awarded Contractor prior to Go-Live but allows an IT or non-IT end user to maintain or modify thereafter (i.e. no source code or structural data model changes occurring).

Customization is referred to a modification to the Solution's underlying source code, which can be completed as part of the initial implementation. All configuration changes or customization modifications made during the term of the awarded contract must be forward-compatible with future releases and be fully supported by the awarded Contractor without additional costs.

Contractor must understand that customizations (i.e. changes made to the underlying source code of the Solution) may not be considered and may impact the evaluation of the Contractor's proposal.

Column D: The Contractor must also fully disclose how they will meet the requirements in their proposal response. This column is for Contractor to describe how they will deliver the business Specification and if the Contractor proposes configurations or customizations, the Contractor must explain the details of the impacted risk that may be caused if configured or customized to meet the business Specification. Description must be no more than 250 words for each business Specification.

Contents

SCHEDULE A – TABLE 1 – BUSINESS SPECIFICATION WORKSHEET1
General Requirements for Service (GEN)4
Requirements Electronic Deposits and Release Debit Cards (EDRC)12
Requirements Multimedia Services (MS)18
Requirements Intelligence Analysis (IA)25
Requirements Prisoner Telephone System (TS)29
Requirements Prisoner Video Visitation (VV)36
Requirements Requests and Messaging (ME)43
Requirements Educational Services (ES)50
Requirements Document Repository (DR)54
Requirements Store Services (SS)55
Requirements Electronic Law Library (ELL)57
Requirements Future Considerations (FC)61

General Requirements for Service (GEN) This section pertains to any services provided under any resulting contract.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

GEN 1.0
Services and equipment must be compliant with all telecommunications industry standards including but not limited to FCC, MPSC, IEEE, and BICSI.
GEN 2.0
All information systems must implement role-based access control.
GEN 3.0
All information systems must log all user activity for the life of the contract.

Note: This data must be made available to MDOC upon request or at regular MDOC approved intervals.

GEN 4.0
Contractor must comply with all SOM requests for penetration testing.
GEN 5.0
Contractor must provide a Single Point of Contact (SPOC) for each solution.
GEN 6.0
Applications and systems must not allow for “Prisoner-to-Prisoner” communications and unauthorized connections.
GEN 7.0
Contractor must provide all available options for MDOC staff to view the prisoner entered data.
GEN 8.0
Applications and systems must not allow users to navigate to applications or other areas of the internet that have not been approved for use.
GEN 9.0
Contractor with MDOC must complete a “pilot” at one or two locations to ensure functionality, compatibility, and reliability before installing infrastructure and/or services at the rest of MDOC’s locations.
GEN 10.0
All applications must allow for managed access using User Directory and/or Mobile Device Management (MDM) utilities.
GEN 11.0
All Prisoner-facing applications and systems must allow MDOC administrators to restrict access to applications and device as needed at MDOC’s discretion, in some cases based on User Directory associations.

Examples:

· Disable data transfer on tablet USB port

· Disable Settings on device Operating System

· Disable messaging application for Prisoners labeled as “High Risk” in User Directory application

GEN 12.0
Contractor must assist with development of procedures for MDOC to request logs, changes, support, or other services/actions.
GEN 13.0
Contractor must provide support for non-urgent inquiries within the timeframes defined in the SLA
GEN 14.0
The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA.
GEN 15.0
Contractor must work with SOM to develop Service Level Agreements (SLA’s) for responses/resolution of issues with varying degrees of criticality and impact, including (but not limited to):

· Response timeliness

· Escalations

· Processing Times

· Repairs

· Quotes

GEN 16.0
Contractor must ensure any scheduled maintenance on provided services occurs only during MDOC-approved maintenance windows.
GEN 17.0
Existing Services: Store Services (SS), CETN and Electronic Law Library (ELL) will need to be integrated into a will need to integrate to an MDOC approved MDM solution
GEN 18.0
Any new services such as Messaging (ME) both General Requests (GR) and Medical Requests (MR), Document Repository (DR), Multimedia Services (MS), Video Visitation (VV) and Telephone Services (TS) services will need to integrate to an MDOC approved MDM solution
GEN 19.0
If provided applications and/or services can be interfaced with using an API or web services integration, Contractor must indicate this, along with any restrictions on usage (rate-limits, associated costs, etc.).
GEN 20.0
If a Contractor needs to visit an MDOC facility, Contractor must complete required paperwork/approvals to do so (LEIN clearance).
GEN 21.0
All applications and services must meet or exceed agreed upon SLA’s related to uptime.
GEN 22.0
Each Application must have the ability to detect when it is not on an approved network and disable accessand notify/report.
GEN 23.0
Contractor must offer a support Solution through which Prisoners can submit requests for assistance.

Note: Resolving non-hardware issues i.e. software configuration, access, networking, etc.) via written instruction

GEN 24.0
Contractor must provide any customer data (ex: who is depositing funds or money for video visits, and how much) associated with the purchase of services for the inmate. This includes address information, transaction information, contact information, etc.

Note: This information must be provided as a report and via a interface with MDOC intelligence application.

GEN 25.0
The applications must store all user entered data and allow MDOC access to it.
GEN 26.0
All service providers must provide an option for purchased media content to be available in a non-proprietary format.

Requirements Electronic Deposits and Release Debit Cards (EDRC) MDOC is seeking a solution to provide a method for friends and family of MDOC Prisoners to deposit funds into a prisoners account through online and mail. If there is any money remaining in the account upon the Prisoner’s release from an MDOC facility, the system must have functionality to deposit the remaining funds onto a payment/debit card issued in the Prisoner’s name.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

EDRC 1.0
Contractor must supply debit release cards at no cost to MDOC
EDRC 2.0
System must include a public-facing web interface where individuals can deposit money into Prisoner accounts
EDRC 3.0
Contractor must offer a support solution through which Prisoners can submit requests for assistance.

Note: Resolving non-hardware issues i.e. software configuration, access, networking, etc.) via written instruction

EDRC 4.0
System must interface with MDOC accounting system
EDRC 5.0
Service must provide a loadable zero balance debit cards to Prisoners upon release from an MDOC facility
EDRC 6.0
System must provide reporting tools,

Note: Including but not limited to; user activity and transaction history reports.

EDRC 7.0
System must work with MDOC-approved mobile devices.
EDRC 8.0
Contractor must be able to restrict friends or family members depositing funds to Prisoners as requested/required by MDOC.
EDRC 9.0
Contractor must provide any forms for drop box deposits and any other forms or marketing tools to promote the service to the public at no cost to the State. These forms must be available at each facility, along with a printable version available on the Contractor’s website and the MDOC’s website. Contractor must provide the MDOC an electronic copy of the form to be downloaded onto the MDOC’s website.
EDRC 10.0
All services must provide multiple language options. All options/services must, at a minimum, include English and Spanish. Per MDOC’s request, additional languages can be added.
EDRC 11.0
Contractor must have a secure web-based solution to allow MDOC to view all user activity (Prisoners and associated friends/family accessing this service), and all transaction history.
EDRC 12.0
System must give MDOC the ability to determine the maximum amount allowed per deposit
EDRC 13.0
System must allow deposits to Prisoner’s accounts 24/7/365

Note: Funds must deposit (Via interface with offender accounting system) in account by next calendar day.

EDRC 14.0
System must allow MDOC staff to load debit cards with Prisoner funds upon parole or discharge at all correctional facilities/virtual prisons using a web-based interface
EDRC 15.0
System must allow deposits from Prisoners transferred from other agencies
EDRC 16.0
Service must provide MDOC staff the ability to view, hold or restrict deposits before they are submitted to the MDOC accounting system.
EDRC 17.0
System must allow debit cardholders to access their account information nationwide 24/7/365
EDRC 18.0
The cards provided must have no minimum load amount and must allow the Prisoners to convert the card for banking purposes later if the Prisoner elects to do so

Note: Prisoner must be able to use card without fees for 60 days upon release.

EDRC 19.0
Service must have the ability to export data in a format that allows MDOC to import the data into their intelligence application.
EDRC 20.0
System must require filling out data fields to deposit funds including but not limited to; relation to prisoner, phone number, offender ID#.

Note: The relation to prisoner field includes Grandparent, Parent, Stepparent, Spouse, Mother-in-law, Father-in-law, Child, Stepchild, Grandchild, Sibling, Stepbrother, Stepsister, Aunt, Uncle, Friend, Prisoner Advocacy Group, Legal Correspondent.

OPTIONAL

EDRC 21.0
System may provide alternative deposit solutions on-site such as ATM’s, kiosks, etc. for public users to deposit funds into Prisoner accounts.

Note:

Requirements Multimedia Services (MS)

Digital Media - A multimedia ordering and playback Solution that provides entertainment options for offenders, such as music, movies, shows, podcasts, etc. MDOC must be able to review and restrict specific products prior to availability for purchase. In addition, prisoners need the ability to create a document (word processing) and then have the ability to print their created document.

· Note: This will require Web Services integration to the Corrections Offender Management System (COMS), managed by A-T-G.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

MS 1.0
Solution must allow the downloading of digital media/entertainment onto devices.

Note: MDOC will consider streaming as a method to access content. If the delivery method is as efficient as downloading.

MS 2.0
System must provide eBooks, audio books, magazines, and podcasts, etc.

Note: Content should include but not limited to; Health, Mental Health, Nutrition, Life Skills, Physical Fitness, meditation, and behavioral health.

MS 3.0
System must provide access to music as described in 1.0
MS 4.0
System must provide access to games as described in 1.0
MS 5.0
System must provide access to movies and shows as described in 1.0
MS 6.0
System must restrict downloads/access to any media per MDOC discretion
MS 7.0
Service must have the ability to export data in a format that allows MDOC to import the data into their intelligence application.
MS 8.0
System must interface with MDOC’s offender accounting system
MS 9.0
System must allow MDOC staff to monitor downloads/usage of media on devices
MS 10.0
System must work with MDOC-approved mobile devices
MS 11.0
Contractor must offer a support solution through which Prisoners can submit requests for assistance.

Note: Resolving non-hardware issues i.e. software configuration, access, networking, etc.) via written instruction

MS 12.0
System must prohibit Prisoners from accessing any media outside of the MDOC-approved catalog
MS 13.0
System must provide advanced reporting tools, including user activity logs and transaction history.
MS 14.0
System must provide MDOC staff access to review all media content.
MS 15.0
Service must have the ability to allow offenders to purchase approved media content.
MS 16.0
If media was previously purchased by any MDOC Prisoner and the purchased media was later found to be inappropriate and blocked by MDOC, the media must be removed from the Prisoner’s device/account and a full credit for the media must be provided to the Prisoner at the Contractor’s expense.
MS 17.0
The system must offer a minimum of 1 million song titles available for purchase.
MS 18.0
The media catalog must be searchable by artist, and genre to include descriptions of artists and must be able to be browsed.
MS 19.0
For media purchases, application must allow for a preview before purchase.
MS 20.0
The system must provide the Prisoner with an account transaction history and account balance from the Prisoner accounting system to include at least the last 25 transactions and media account balance. This feature must be able to be turned off if not approved for use by MDOC.
MS 21.0
The system must not allow Prisoners to share content.
MS 22.0
System must have the ability to play educational, religious material, games, or other media as approved by MDOC.
MS 23.0
Contractor must provide a mechanism to refund incorrect charges to a Prisoner’s account.
MS 24.0
Contractor must provide refund/return detail and must provide refunds within two business days of notification and verification of returns.
MS 25.0
Contractor must accept returns and provide refunds if a Prisoner paroles from the MDOC, discharges, or dies.
MS 26.0
Contractor must work with existing service providers to migrate media content purchased.
MS 27.0
Contractor must provide software (i.e., media players) allowing the offender to play migrated media content.
MS 28.0
Contractor must provide storage for migrated media content.
MS 29.0
Contractor must provide a document creation process within their solution that has limited functionality and must be controlled by MDOC.
MS 30.0
Prisoners must be able to print their created document to create physical copies. Printing functionality must be controlled by MDOC
MS 31.0
MDOC staff must be able to view all prisoner created documents and the solution must be able to prevent unapproved communication between prisoners.
MS 32.0
Solution must have Closed Captioning functionality for all media/entertainment content provided as part of the MS solution.

OPTIONAL

MS 2933.0
System may provide movies available for group viewing, Contractor will be responsible for procuring public performance agreements
MS 3034.0
Movie, game, and music services may be available via monthly subscription
MS 3135.0
Service provider must work with MDOC on incentive options for purchased media content that will not be migrated.
MS 3236.0
The system may allow Prisoners to listen to FM radio with pre-set station capabilities and must allow MDOC to block any stations that are deemed inappropriate.
MS 3337.0
System may allow MDOC to request to add various types of media to be made available to Prisoners.

Requirements Intelligence Analysis (IA) MDOC is seeking a Solution that will provide the ability to gather and export data across prisoner services such as but not limited to financials, phone calls, messaging etc. in a form that is supported by our current Intelligence Application. The Solution must interface with current web based and local information systems and must have the ability to link, sort, filter, generate, export reports across multiple data sets. Solution must provide advanced reporting tools that allow for complex querying, in addition to audit tracing. Solution will allow for configurable permissions across various roles that will be determined by MDOC. Contractor will provide acknowledgment and support for critical issues within 1 hour for critical issues and 24 hours for non-critical issues as well as a summary of findings upon the closing of issues. Maintenance, compliance, and updates will be the responsibility of the Contractor.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

IA 1.0
Solution must gather data from all Prisoner services, including but not limited to: Financial transaction history, phone calls, and messaging.
IA 2.0
Service must have the ability to export/import data in a format that allows MDOC to export/import the data into the intelligence application.
IA 3.0
Solution must be able to interface with existing and future web services to gather information for analysis.
IA 4.0
Solution must be able to generate and export reports indicating relationships between data sets.
IA 5.0
System must provide advanced reporting tools, including user activity logs and transaction history.
IA 6.0
Solution must include a “link analysis” interface to visually show relationships, with an easy-to-interpret interface.
IA 7.0
Link analysis tool must visually indicate frequency/volume of interactions
IA 8.0
Solution must allow MDOC users to filter for data using any data points contained within the system.
IA 9.0
Solution must allow MDOC to run complex queries against available data sets.
IA 10.0
Solution must allow MDOC to configure user permissions for varying access levels for data of Prisoners, other MDOC personnel, etc.
IA 11.0
Contractor must respond to/acknowledge non-critical issues within 24 hours.
IA 12.0
Solution must be able to store data in a way that is “Consumable” by MDOC. In DB such as Azure etc.

OPTIONAL

IA 13.0
User accounts within the system may be configurable using Active Directory roles/groups.
IA 14.0
Contractor may have a robust API and may provide web services integration documentation.

Requirements Prisoner Telephone System (TS) The MDOC is required by State law (MCL 791.270) and Administrative Rule 791.6638 to provide telephone service to Prisoners. The MDOC has special security requirements and has a prime objective of controlling Prisoner telephone usage and limiting the use of the telephone system for fraudulent activity. The telephone calls are monitored for public safety, security and to prevent fraudulent activity.

The Contractor will be responsible for furnishing and maintaining a softphone telephone service for use in all present and future Correctional Facilities that will allow MDOC Prisoners to complete auto-collect local, debit through disbursement, long-distance and international calls, and/or pre-paid local, long-distance, and international calls from the MDOC Correctional Facilities. The solution must include a statewide phone system, any necessary telephone equipment, the ability to monitor and record equipment and services, and other ancillary services to be determined. The system must also provide a security-controlled environment; allowing and disallowing calls to specific telephone numbers; recording, monitoring, and playback capabilities; verification of calls against the LIDB system; detection of three-way calls; and interfacing with the chosen MDOC intelligence-gathering application to aid investigators.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

TS 1.0
System must only allow for outbound calls
TS 2.0
System must notify call recipients that the call is coming from a Prisoner within an MDOC facility and allow for the recipient to decline the call
TS 3.0
System must be capable of recording certain calls based on the call type. MDOC staff must be able to mark calls as confidential.
TS 4.0
System must provide advanced reporting tools, including user activity logs and transaction history.
TS 5.0
System must be capable of associating a call type to a phone number
TS 6.0
System must comply with FCC regulations.
TS 7.0
System must limit the number of contacts available for Prisoners for an MDOC-specified length of time
TS 8.0
System must be capable of allowing certain telephone numbers to be free of charge when called

Note: Certain MDOC staff need access to create/maintain these lists

TS 9.0
System must interface with MDOC existing intelligence gathering software
TS 10.0
System must only allow phone calls during determined MDOC windows
TS 11.0
System must be capable of restricting Prisoner usage based on security needs
TS 12.0
System must be compatible with MDOC-approved wireless devices
TS 13.0
System must be capable of restricting software access when the device is connected to an unapproved network
TS 14.0
System must have a way to restrict video calls or telephone calls to only MDOC-approved areas within the facilities

Note: e.g., detect device connection type i.e. Local Area Network (LAN) or Wireless restrict software functionality based on connection

TS 15.0
System must provide MDOC required reports including but not limited to logs of individual user activities and investigative analysis reporting
TS 16.0
System must not allow MDOC Prisoners to call other MDOC Prisoners
TS 17.0
The system must have the functionality to allow certain staff to disable all Prisoners from completing phone call’s both system wide and by facility

Note: This includes scheduled and unscheduled time periods

TS 18.0
Copper wire/analog telephones must be made available for Prisoner use in the facility yards
TS 19.0
System must have web-based administrative portal for MDOC staff to access
TS 20.0
System must verify the identity of the Prisoner who is making the phone call via voice biometric or other option
TS 21.0
System must detect calls to notify MDOC staff if a different person joins the call from either/both the outgoing and receiving ends of the call
TS 22.0
System must be able to identify and prevent 3-way calling
TS 23.0
Contractor must offer ADA-Compliant software that allows Prisoners to read transcripts of conversation in real time
TS 24.0
Contractor must offer sign language interpretating for video calls when required by Prisoners or call recipients
TS 25.0
Any shared devices/infrastructure within common areas must follow ADA regulations
TS 26.0
Contractor must retain call logs and recordings for the life of the contract plus 5 years
TS 27.0
System must allow metadata for all communications to be transferred to MDOC or next Contractor at end of contract per MDOC direction
TS 28.0
Contractor must provide a mechanism to refund incorrect charges to a Prisoner’s account, along with details surrounding the return.
TS 29.0
Contractor must have sufficient data redundancy for data related to the system
TS 30.0
Contractor must provide a solution with multiple language options, including at a minimum both English and Spanish options.
TS 31.0
System/application must provide phone account balance to Prisoners upon request
TS 32.0
System must allow MDOC to block calls/numbers as deemed necessary for security purposes
TS 33.0
System must have a direct connect visitation platform initiated by the Prisoner caller for ADA video calls.
TS 34.0
Prisoners must have ability to use their telephone account after transferring funds from their Prisoner Accounting System account to pay for call services.
TS 35.0
Friends and family of a prisoner must have the ability to deposit funds in the prisoner’s telephone account for the purpose of calling their number only.
TS 36.0
System must interface with MDOC-approved intelligence gathering application, and/or allow MDOC to export user activity data into an MDOC-approved intelligence gathering application.
TS 37.0
Ability to create a link that approved law enforcement entities can access multiple phone calls.

OPTIONAL

TS 38.0
Service provider may use a Michigan-based customer service.

Note: This is preferred.

TS 39.0
Service provider may include foreign language call translation and call transcription

Requirements Prisoner Video Visitation (VV) MDOC seeks a Prisoner Visitation Solution that allows family and pre-authorized contacts to schedule visitation, both in-person and virtually. The video visits will happen in defined spaces within MDOC facilities and only pre-approved visitors will be authorized to join video visitation calls. The system must also provide a solution for scheduling for video and in-person visitations.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

VV 1.0
System must record and allow for live monitoring of video visits
VV 2.0
Video visits must only happen in pre-approved areas within MDOC facilities
VV 3.0
System must provide a public-facing web portal where Prisoner contacts and family can schedule/request video and in-person visits
VV 4.0
System must provide an administration side of the web portal for MDOC staff to open visitation windows and monitor video visits in real time and recording of those visitations will need to be available to the appropriate staff.
VV 5.0
Administration portal must allow MDOC staff to deny visitation requests at MDOC discretion based on policy.
VV 6.0
System must provide advanced reporting tools, including user activity logs and transaction history.
VV 7.0
System must include reporting but not limited to; by inmate, visitor, number of visits, who had visits, who hasn’t had visits, restrictions per inmate, facility, date, race, duration, etc.
VV 8.0
Administration portal must allow MDOC staff to assign approved contacts to individual Prisoners
VV 9.0
System must allow MDOC to set schedules for video visits and in-person visits by facility
VV 10.0
System must allow approved visitors to schedule video and in-person visits
VV 11.0
System must allow MDOC staff to intervene at any time during a video visit. System must allow MDOC staff to end video visit if an action is not permitted.
VV 12.0
System must allow MDOC to review all recorded video visits.
VV 13.0
System must allow MDOC to review all visit schedule history.
VV 14.0
System must provide Intel reporting and search capability.
VV 15.0
System must have a process to approve/deny prisoner/visitor relationships for scheduling (Approved visitor list).
VV 16.0
System must remove visitor list for offender upon parole, discharge, or death.
VV 17.0
System must allow MDOC to set quotas on the number of visits, based on security level/classification and day of the week. For both video and in-person visits
VV 18.0
System must allow MDOC to place restrictions on prisoners and visitors in compliance with MDOC policy. System must track types of restrictions. System must allow for notes on restriction
VV 19.0
System must have a refund and quota reset process for video visits that did not occur or are interrupted due to interruption in Contractor services and/or MDOC operational processes.
VV 20.0
System must have ability to log video and voice quality.
VV 21.0
System must have the ability to schedule Professional visits. Visits that do not count toward quotas and video visits are not monitored/recorded (audio).
VV 22.0
System must blur background for prisoner video visitation.
VV 23.0
System must comply with all applicable MDOC visiting standards, policies, and operating procedures.
VV 24.0
System must allow for video or data to be exported
VV 25.0
System must limit all video visits to MDOC-specified lengths of time
VV 26.0
Data will be managed by Contractor
VV 27.0
Contractor must provide the option to Integrate to the MDOC “Prisoner mgt system”

Web Service/API

VV 28.0
Appropriate staff to have permission to restrict Visitation either from in Person or video
VV 29.0
System must interface with MDOC-approved intelligence gathering application, and/or allow MDOC to export user activity data into an MDOC-approved intelligence gathering application.
VV30.0
Contractor must provide the ability for approved MDOC staff to create a link of selected video visits for law enforcement to be able to access.
VV31.0
Video Visit services must include closed captioning functions for all video calls.
VV 32.0
The Contractor shall provide telephone reception quality equal to the highest level of toll quality offered to the general public and shall meet telecommunication industry standards for service quality. call and video quality must meet requirements necessary for calls and videos to be admissible in court of law. For Audio Quality/Clarity, the following requirements should be met:

a. Format: Use a lossless or high-quality format such as WAV or FLAC. Compressed formats like MP3 may degrade quality and raise questions about authenticity.

b. Sample Rate: Minimum of 44.1 kHz (CD quality) or higher (e.g., 48 kHz or 96 kHz).

c. Bit Depth: At least 16-bit, preferably 24-bit.

d. Signal-to-Noise Ratio (SNR): Ensure a high SNR (low background noise) to make voices or critical sounds distinguishable.

e. Mono vs. Stereo: Stereo is preferred if the recording captures spatial information (e.g., multiple speakers), but mono may suffice for single-source recordings.

f. Embedded Metadata: The audio file should include metadata such as recording date, time, device used, and location (if available).

g. Original Device Information: Retain details about the recording device (e.g., model, firmware version, and settings).

h. Timestamping: Use a device that automatically embeds accurate timestamps or synchronize with a trusted time source (e.g., GPS or NTP).

For Video Visitation Quality/Clarity, the following requirements should be met:

a. Resolution: Higher resolution (e.g., 1080p, 4K) is preferred to ensure details like faces, license plates, or actions are clearly visible. Low-resolution videos (e.g., 480p or below) may be challenged if critical details are unclear.

b. Frame Rate: A frame rate of at least 24–30 frames per second (fps) is ideal for smooth motion capture. Lower frame rates (e.g., 15 fps) may miss critical moments or appear choppy.

c. Compression: Use minimal compression to preserve detail. Highly compressed formats (e.g., low-bitrate MP4) may degrade quality, making it harder to discern details. Formats like H.264 or H.265 are common but should be high-bitrate.

d. Lighting and Focus: The video should be well-lit and in focus to clearly depict the scene. Night vision or low-light capabilities may be necessary for footage recorded in poor lighting conditions.

e. File Format: Use widely accepted, non-proprietary formats like MP4, AVI, or MOV to ensure compatibility with court playback systems. Avoid obscure or heavily edited formats.

f. Embedded Metadata: The video file should include metadata such as recording date, time, device used, and location (if available).

VV 33.0
Specific voice metrics must include but are not limited to:

a. Mean Opinion Score (MOS)

b. Jitter

c. Latency

d. Packet loss, and

e. codecs used.

VV 34.0
Specific video metrics include but are not limited to:

a. Bit rate

b. Resolution

c. Frame rate

d. Codec

e. Buffer fill time

f. Lag length

g. VMAF or SSIM at a minimum.

VV 35.0
The Contractor awarded phone and video services would be responsible for measuring and recording voice and video quality and providing the data via reports as requested by MDOC.

OPTIONAL

VV 36.0
Ability to override the scheduling platform to allow one time visits (video and in-person).

Requirements Requests and Messaging (ME) MDOC seeks a contained messaging platform for Prisoners in MDOC Correctional Facilities to communicated with registered contacts. The platform must be self-contained and require registration by the public.

Friends & Family Messaging - A messaging service to allow electronic communications between offenders and approved contacts outside of facilities (public-facing).

Electronic Requests - An electronic replacement of the manual paper process to facilitate certain requests to staff (e.g. Grievances, information requests, forms, etc.,). MDOC currently receives thousands of requests from offenders each month. This application could also be used to deliver announcements from MDOC staff to offenders.

· Note: This will require Web Services integration to the Corrections Offender Management System (COMS), managed by A-T-G.

Messaging (ME) between MDOC staff and Prisoner individual groups and facility by location.

General Requests (GR) allows Prisoners to submit digital form to MDOC group based on facility by location.

Medical Requests (MR) allows Prisoners to submit medical digital form to MDOC group based on facility by location.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

ME 1.0
System must interface with MDOC-approved intelligence gathering application, and/or allow MDOC to export user activity data into an MDOC-approved intelligence gathering application.
ME 2.0
System must allow for MDOC staff to send messages to individual or multiple Prisoners

Note: The system must NOT send messages using DOC staff work email and must have the ability to mask staff identity.

ME 3.0
System must work with MDOC-approved mobile devices
ME 4.0
System must provide advanced reporting tools, including user activity logs and transaction history.
ME 5.0
System must prevent Prisoners from messaging unauthorized recipients.

System must prevent users from sending messages outside the system.

ME 6.0
System must allow Prisoners to send messages only to approved users/accounts that have been approved to receive messages from the Prisoner
ME 7.0
System must interface with Mobile Device Management and Active Directory solutions (or similar) to allow administrators to manage user access and define allowable actions within the system.
ME 8.0
System must allow MDOC staff to access Prisoner message history

Note: This access must be for all facilities.

ME 9.0
System must retain messages for the life of the contract.
ME 10.0
System must block attachments of certain types, as defined by MDOC
ME 11.0
System must allow for MDOC staff to add attachments.
ME 12.0
System must not allow Prisoner-to-Prisoner communication.
ME 13.0
System must encrypt all data at rest and in transit using a FIPS 140-2 compliant module
ME 14.0
System must include administrative tools allowing MDOC staff to search for requests by Prisoner, Location, content, resolution status, or other attributes.
ME 15.0
System must allow MDOC administrators to create reports on statistics for request submissions, resolution status, or other attributes.
ME 16.0
System must provide a word processing software allowing certain users to create templates for messaging responses.
ME 17.0
Contractor must offer a support solution through which Prisoners can submit requests for assistance.

Note: Resolving non-hardware issues i.e. software configuration, access, networking, etc.) via written instruction

ME 18.0
System must include the functionality to map data elements to fields on the template, pre-populating data
ME 19.0
System must allow Prisoners to send and receive messages to/from approved external users
ME 20.0
System must alert public users that any conversations will not be private and that MDOC will have access to all conversations

Note: This is done through a website

ME 21.0
System must allow external users to register an account within the system.

Note: External users must have an account to send and receive messages

ME 22.0
System must automatically prompt MDOC for review of a communication if specific characters, words, or phrases are detected.
ME 23.0
System must allow MDOC admin users to access conversations within the system as needed
ME 24.0
System must allow MDOC to search all conversations for instances of specified words or phrases.
ME 25.0
System must allow MDOC to flag Prisoners, requiring all messages to and/or from that Prisoner to be reviewed prior to delivery, with the ability to approve or deny that communication.
ME 26.0
System must allow for an informal communication individual or group staff and Prisoner.

General Requests

GR 1.0
System must allow MDOC administrators to create additional templates

Note: Prisoner must have the ability to access the template, complete the template and submit the template to specific staff

GR 2.0
The templates must have the ability to route to correct facility based on need.
GR 3.0
The templates must prepopulate certain fields based on available data
GR 4.0
The templates must include the functionality to define a request type
GR 5.0
Contractor must assist with integrations to new or existing services and applications as needed.
GR 6.0
System must allow Prisoner to enter the details of their request in a “free form” text box.

Medical Requests (MR)

MR 1.0
System must allow Prisoners to submit a medical request via electronic template
MR 2.0
The templates must prepopulate certain fields based on available data
MR 3.0
System must require Prisoners to select one or more Request Types (among “Health Record Copies,” “Medication Refill,” “Medical,” “Dental,” “Optometry,” “Mental Health”)
MR 4.0
System must require Prisoners to select only one Urgency level (either “Urgent” or “Non-Urgent”)
MR 5.0
System must allow Prisoner to enter the details of their request in a “free form” text box.
MR 6.0
System must require Prisoner to confirm truthfulness/accuracy of request details before finalizing the request
MR 7.0
System must be able to interface with existing MDOC utilities via web services- deliver request information to MDOC, and deliver MDOC responses to Prisoner

Requirements Educational Services (ES)

The MDOC is focused on providing educational opportunities and content to those that are incarcerated. Having access to this content in a digital format will increase engagement and the number of users that can access materials to expand knowledge while developing employment skills, soft skills, and digital skills. The MDOC has worked with outside contractors to develop a new educational network, which hosts Google Classroom and other programs to modernize educational offerings within the MDOC. While this was an important step, access and learning is still limited by having to be in a classroom on a hardwired device. It is important (both for students and to maximize existing investments), to provide those that are incarcerated with access to this network, as well as other educational programs and materials on a secure Wi-Fi platform that can be accessed throughout the facilities on appropriate devices for learning.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

REQUIRED

ES 1.0
The Vendor must provide a web browser that meets the requirements of Schedule A (Statement of Work) Section 9.(Chrome or IE).

Note: Prisoner would use the web browser to connect to Corrections Education Technology Network (CETN). This would give them access to all available education services for that Prisoner.

ES 2.0
The contractor must provide an array of library titles focusing on special education, disabilities, treatment, and vocational courses

Note: Included but not limited to. (i.e. literacy, English as a Second Language (ESL), GED, college preparation, cognitive therapy, parenting skills, interview skills, workplace readiness, and soft/life skills training).

ES 3.0
The primary language must be English, in addition to other languages that may be available.
ES 4.0
Content may be updated, by the Contractor.

However, the Contractor must submit any material revisions, deletions, or additions to the content to the State Program Manager or designee at least seven (7) calendar days prior to making changes. Approval for changes must be in writing. If the State does not approve the changes to the content, the Contractor will not change the content.

ES 5.0
Contractor must maintain sufficient licenses for all content to allow the State unlimited access to

the content.

ES 6.0
Contractor must provide the necessary software and hardware that is required for the educational services
ES 7.0
The Contractor must provide the functionality that would allow MDOC staff to perform the following: Create/manage prisoner accounts, investigate prisoner activity, review available content, Manage prisoner progress (i.e. managing certificates)
ES 8.0
Contractor must provide support for services.
ES 9.0
Contractor must provide entertainment incentive content.
ES 10.0
Contractor must supply educational transcript of offenders completed courses.

OPTIONAL

ES 11.0
The Contractor may provide subscription education-based offerings

Requirements Document Repository (DR) The goal is to share information with the prison population about rules, policies and programing. Document Repositories can be location specific and read only documents for prisoners to access.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

Required

DR 1.0
The system must be able to allow staff to upload documents and video files to a common repository i.e pdf, jpeg, all file types
DR 2.0
System must allow MDOC the ability to create, delete, assign permissions to document libraries.

Requirements Store Services (SS) MDOC has a current contract for Prisoner Commissary Services with Keefe Commissary Network LLC. With the new prisoner network and device/tablet that will be awarded via this RFS, MDOC prisoners need the ability to enter their store orders and view their prior order from the awarded device/tablet via an interface to the prisoner store system.The Prisoner store or “Commissary” is an existing MDOC service with access to the solution via a Contractor managed kiosk that allows prisoners to purchase personal items.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

Required

SS 1.0
System needs to integrate with the current commissary provider and services.
SS 2.0
Contractor must work with future commissary contractors to interface solution to the prisoner tablet/device.

OPTIONAL

SS 3.0
Ability to enter store orders.
SS 4.0
Ability to see current balance of funds available to prisoner.
SS 5.0
Ability to see previous orders places by prisoner.
SS 6.0
Ability to see order status.

Requirements Electronic Law Library (ELL) Give the prisoner access to view the Electronic Law Library.

ELL Integration – The Statehas a current contract for an Electronic Law Library system (currently Lexis Nexis). The ELL needs to be accessed by Prisoners on a device that is proposed as part of the prisoner services solution of this RFS.MDOC Prisoners need to have the ability to access this service via the awarded device/tablet, as well as make requests (kites) from this device to the Librarians for forms and physical copies.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

Required

ELL 1.0
The ELL System on the CETN network needs to integrate with the tablet/device awarded via this RFS.
ELL 2.0
The integration/interface to the ELL shall not limit any functionality of the ELL.

OPTIONAL

ELL 3.0
The state prefers a solution that allows access to MDOC’s ELL by prisoners incarcerated in other institutions other than MDOC facilities. (Example: MDOC prisoners in Federal Custody).

Requirements Future Considerations (FC)

Depending upon the ability of the Contractor to provide the appropriate services once the initial scope is met, the project scope may be expanded to include functionality not currently within scope of this Contract if such additional scope increases the overall value to the State. Such follow-on work may occur after initial implementation.

A
B
C
D
Business Specification Number
Business Specification
Current Capability
Requires Configuration
Requires Customization
Future Enhancement
Not Available
Contractor must explain how they will deliver the business Specification. Explain the details of any configuration/customization and the impacted risk that may be caused if configured or customized to meet the business specification.

Optional

FC 1.0
Future Functionality Considerations:

1. Financial management

2. Personnel support

3. Operations support

4. Data analytics

5. Business intelligence

6. Research and planning

7. Warehouse ordering and inventory

8. Prisoner-related functionality:

· Alert system for hearing impaired

· Prisoner and Jurisdiction time computation

· Money deposits

· Electronic devices

· Vending machine card encoding

FC 2.0
Contractor may provide access to Department policies and guidelines.
FC 3.0
Contractor may provide access to Library circulation- Software
FC 4.0
System allows prisoners to view entire ELL catalog.

Note: Catalog from all facilities.

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