25140 Kinross PPD System - Project Statement.pdf

DTMB-0427 (R 10/22)

PROJECT STATEMENT

STATE OF MICHIGAN

DEPARTMENT OF TECHNOLOGY, MANAGEMENT AND BUDGET

State Facilities Administration

Design and Construction Division 3111 West St. Joseph

Street Lansing, Michigan 48909

FILE NUMBER

472/25140.ABG

PROPOSAL DUE DATE

Thursday, April 10, 2025

CLIENT AGENCY

Michigan Department of Corrections

PROJECT NAME AND LOCATION

Kinross Correctional Facility – Personal Protection Device (PPD) Upgrades PROJECT ADDRESS (if applicable) 4533 W Industrial Park Dr, Kincheloe, MI 49788

CLIENT AGENCY CONTACT

Richard White, whiter12@michigan.gov

TELEPHONE NUMBER

517-242-3599

DTMB - DCD PROJECT DIRECTOR

Alan Goschka, goschkaa@michigan.gov

TELEPHONE NUMBER

517-388-3489

WALK-THROUGH INSPECTION DATE, TIME, AND LOCATION:

Monday, March 31, 2025 at 2:00pm at the Kinross Correctional Facility, 4533 W Industrial Park Dr, Kincheloe, MI 49788. Meeting at the main entrance at the Administration Building.

MANDATORY (Check box if Mandatory)

LEIN CHECK (Dept. of Corrections ONLY) All contractor/vendor representatives attending a Pre-Bid Walk Through Meeting must submit a Vendor/Contractor LEIN Request five business days prior to the meeting date, (See the attached Vendor/Contractor LEIN Request form). Send the LEIN Request form, filled out and signed, by email to Daniel T. Smith & Sharon Frost at email addresses: SmithD76@michigan.gov & FrostS1@michigan.gov .The email “Subject” must include (Facility Name, Project Name, Date & Time of Pre-Bid Walk Through Meeting).

NOTE: An individual is only permitted to represent one bidder at a mandatory walk-through.

PROJECT DESCRIPTION/SERVICES REQUESTED:

The Kinross Correctional Facility is replacing the existing Personal Protection Device (PPD) system throughout the entire facility. The existing system is a Senstar Flare Gen 1 system with the new system to be a Guard 1 PPD system.

The Professional Services Contractor (PSC) is to provide a proposal for Phase 500 Final Design and Phase 600/700 Construction Administration services to field investigate and document the existing system in its entirety, including existing head end unit locations and existing emergency power availability conditions. New IP based head end units are to be installed at existing locations or in new data racks, TBD.

Develop plans/specifications to replace the PPD system, develop an installation plan so that the new system is operational for 30 days prior to shut down and removal of the existing system, submission for plan review, pre-bid walkthrough and evaluation recommendation along with construction administration services.

mailto:whiter12@michigan.gov mailto:goschkaa@michigan.gov mailto:SmithD76@michigan.gov mailto:FrostS1@michigan.gov

The PSC Proposal (Technical and Cost) for all required Professional Architectural and Engineering Services shall be in compliance with the State of Michigan, Department of Technology Management and Budget DTMB Project Statement Form (DMB427), DTMB ISID Billable Rate Professional Services Contract and the DTMB 430 RFP Billable Rate Form (DMB 430) and DTMB Facilities Administration, Design and Construction Division policies and procedures for the development of Contract Bid Documents and Construction Administration. A proposed schedule for design, bidding and construction must be included.

THE PSC PROPOSAL SHALL INCLUDE:

1. All required LARA plan review, permit application preparation, permitting fees, reimbursements, and approvals.

2. Contract Documents utilizing the current State of Michigan, DTMB, Facilities and Business Services Administration, Design and Construction Division and the Master Spec format.

3. Clear documentation of the number of meetings proposed during the design and construction administration phases and indicate whether the meetings are proposed to be on-site, face to face, by telephone, or in specific electronic format.

4. Providing 50% and Final (100%) estimates of construction costs for development plans.

5. Design and construction scheduling. Provide a proposed PSC design schedule. The Agency desires to have the design completed as soon as possible.

6. Submittal of 50% and 90% contract documents for owner review, posting on SIGMA-VSS, Best

Value Bid Evaluation, PSC recommendation of Contract Award, and Contract Administration.

7. Under the Cost Proposal, Section III-2-B Fee with Anticipated Hours and Billing Rate – PSC to breakdown and provide a table for each design phase – Phase 500, Phase 600 and Phase 700.

The PSC shall provide a biweekly progress summary email to the project team, briefly documenting the prior 2-week’s progress by the PSC and display the initial project schedule and current schedule status.

The PSC shall be required to maintain a complete project file of all project documentation including, but not limited to, contract documents, all correspondence, all e-mails, all RFI’s and answers, Field Orders, and telephone communication logs. The project files shall be maintained in an electronic file format and delivered to the DTMB Design and Construction Division with the PSC’s final Payment Request.

Reference Documents

Attachment A – MDOC PPD Specification

Please NOTE:

• Proposal responses MUST be uploaded to SIGMA VSS. Please enter the total cost for all phases as the bid amount.

• Firms are encouraged to combine their technical and cost proposals into one (1) attachment for proposal submission.

• Please remember that attachments can be no larger than 30mb.

• Do not wait until just before the 2:00 p.m. solicitation deadline to submit your proposal response.

SIGMA VSS will not allow a proposal to be submitted after 2:00 p.m., even if a portion of the proposal response has been uploaded.

• If you experience issues or have questions regarding your electronic submission, you must contact the SIGMA Help Desk for assistance prior to the 2:00 p.m., solicitation deadline. You may contact the SIGMA Help Desk by telephone at 517.284.0540 or toll-free at 888.734.9749. You may also email the SIGMA Help Desk at sigma-procurement-helpdesk@michigan.gov

• Please email the Design and Construction Contract Specialists if you are having SIGMA VSS issues. Please include your SIGMA ticket number and any supporting documentation (i.e., screenshots) to Anne Watros (WatrosA@michigan.gov) and Don Klein (KleinD4@michigan.gov).

• You may be asked by our contract specialists to email your proposal. Emailed submissions will require DCD approval and will be handled on a case-by-case basis.

mailto:sigma-procurement-helpdesk@michigan.gov mailto:WatrosA@michigan.gov mailto:KleinD4@michigan.gov

• Approved emailed submissions MUST be received prior to 2:00 p.m. deadline to be considered responsive and responsible.

• Responses should not be emailed to the Project Director.

NIGP CODES

90607, 90678, 91065

DESIRED SCHEDULE OF WORK

Investigation services and design completed Summer 2025, bidding Fall 2025, with construction Winter 2025/2026

ACCEPTING RFP QUESTIONS UNTIL:

Please do not submit online questions via VSS. ALL questions should be emailed to Alan Goschka at goschkaa@michigan.gov address no later than 2:00 p.m., Eastern on Friday, April 4, 2025.

REFERENCE STANDARDS: This project will comply with all codes, standards, regulations, and workers' safety rules that are administered by federal agencies (EPA, OSHA, and DOT), state agencies (DCH, EGLE, DNR, and MIOSHA), and any other local regulations and standards that may apply.

This form is required to be a part of the professional service contract. (Authority: 1984 PA 431) Attachment(s) mailto:goschkaa@michigan.gov

MDOC PPD SPECIFICATION

SECTION 28 5133 – PERSONAL PROTECTION DEVICE SYSTEM (PPD)

PART 1 – GENERAL

1.1 PURPOSE

A. The purpose of this document is to provide a Guide Specifications and Bid Criteria for the design, supply;

installation, commissioning, and associated training for a Personal Protection Device System (PPD) and Man-Down Duress System.

B. Systems by manufacturers other than those listed may submit to be an approved substitution, if approved, not less than two weeks before the scheduled bid date. Alternate manufacturers must include a line-by-line compliance statement based on this specification to be considered.

C. Any deviation from this specification must be submitted as a substitution request for approval prior to procurement and/or implementation.

1.2 RELATED DOCUMENTS

A. SECTION 260500 common work results for Electrical

B. SECTION 260519 low voltage electrical power cables

C. SECTION 260526 grounding and bonding

D. SECTION 260529 hangers and supports.

E. SECTION 260533 raceway and boxes

F. SECTION 260544 sleeves and sleeve seals

G. SECTION 260553 identification for electrical systems

H. SECTION 262726 wiring devices

I. SECTION 270060 underground raceway & structures

J. SECTION 270526 telecommunications grounding

K. SECTION 271100 structured cabling

L. SECTION 272100 network electronics

1.3 SUBMITTALS

A. Product Data: For each type of product indicated.

B. Shop Drawings:

1. Shop Drawings shall be prepared by persons with the following qualifications:

a. Trained and certified by manufacturer in PPD system design.

b. Wiring Diagrams: Detail wiring and differentiate between manufacturer-installed and field-installed wiring. Include diagrams for equipment and for system with all terminals and interconnections identified.

2. UPS: Sizing calculations for minimum of 2-hr power loss.

GoschkaA Text Box Attachment A

472/25140.ABG

Kinross Correctional Facility - PPD Upgrades

3. Delete subparagraph below except for projects where conduit routings are critical but only outlet locations are shown on Contract floor plans. Floor Plans: Indicate all exterior and interior zones. Indicate all receiver locations, types and routing of raceway connections.

4. PPD Characteristics: Indicate the location and type of each receiver. Indicate the coverage areas and corresponding search areas that will correlate with the software graphics.

5. Device Address List: Coordinate with final system programming.

6. System Operation Description: Detailed description for this Project, including method of operation and supervision of each type of circuit and sequence of operations for manually and automatically initiated system inputs and outputs. Manufacturer's standard descriptions for generic systems are not acceptable.

7. Alarm Signaling Service: Equipment rack or console layout, grounding schematic, amplifier power calculation, and single-line connection diagram.

C. Usually delete paragraph and subparagraphs below except for projects where space around air-handling units will be congested. Operating Instructions: For use by Central Control officers and the O&M documents.

D. Operating Instructions: For use by Central Control officers and the O&M documents.

E. Installer Certificates: Signed by manufacturer certifying that installers comply with requirements.

F. Field Test Reports: Indicate and interpret test results for compliance with performance requirements.

G. Maintenance Data: For PPD, include in maintenance manuals specified in Division 01.

H. Include paragraph below where appropriate. See Editing Instruction No. 2 in the Evaluations.

Certificate of Completion: Comply with performance criteria.

1.4 QUALITY ASSURANCE

A. Installer Qualifications: An experienced installer who is an authorized representative of the PPD manufacturer for both installation and maintenance of units required for this Project.

B. Manufacturer Qualifications: A firm experienced in manufacturing systems similar to those indicated for this Project and with a record of successful in-service performance.

C. Source Limitations: Obtain PPD components through one source from a single manufacturer.

D. Compliance with Local Requirements: Comply with applicable building code, local ordinances and regulations, and requirements of authorities having jurisdiction.

1.5 SEQUENCING AND SCHEDULING

A. Existing PPD Equipment: Maintain fully operational until new PPD equipment has been tested and accepted.

B. Equipment Removal: After acceptance of the new PPD, remove existing disconnected PPD equipment and restore damaged surfaces. Offer all removed devices to owner prior to discarding.

1.6 ATTIC STOCK

A. The contractor shall deliver to the facility owner spare system components.

B. For each system component, spares consisting of least one unit or 10% of the number that comprise the system, whichever is greater, shall be provided.

1.7 WARRANTY

A. The product shall be under warranty for a minimum of two years from the date of purchase.

B. The supplier shall make available replacement components, parts or assemblies for a minimum of 10 years from the date of purchase.

1.8 SYSTEM DESCRIPTION

A. Provide a Personal Protection Device System (PPD) with integrated components of the type, size, capacity and characteristics shall be capable of:

1. A duress device system for personal protection.

2. An inmate tracking system for real-time zone-based location (future scope).

3. A task management system for mobile devices (future scope).

4. A well-being check system for documenting required checks and patrols (future scope).

5. An unlimited number of staff personnel or inmates at any time and upon need without degradation to overall functionality or reliability.

6. Support device supervision of all man-down transmitters and network infrastructure devices including automatic trouble alert and notifications, audit trails plus system logs.

7. Deliver staff member & sub-room location data using a minimum of three (3) location technologies & ID logic (RF/IR/LF).

8. Support paging services, display panels, SMS messages, emails, automated PA announcements and warning messages on computer screens.

9. Provide multiple types of location alerts relevant to the specific security incident that can support the simultaneous coordination of multiple response protocols.

10. Automatically collect and store relevant event data for post incident analysis and review.

11. Intuitive, interactive software for managing the life cycle of security incidents as it evolves.

12. Support other safety, security and visibility location-based applications such as: Asset tracking and security, Hands-Free access control, Guard tour monitoring, Temperature Monitoring, Inmate tracking, PREA Alarming, etc.

13. Support integration with external building management and security systems including, but not limited to, CCTV, Access Control and Guard Tour solutions.

14. Deliver distributed local control to ensure that facility personnel remain protected even when network segments or the PPD server are offline.

15. Provide multiple system tags options for duress function, ID badge, asset tracking, critical environment conditions, inmate tracking and well-being, etc.

B. Redundancy

1. The PPD System shall provide a 99.999% level of availability and reliability. Event data reliability, in particular, room location information, shall be explicit and accurate. The following shall be provided as a minimum:

a. Dedicated Fiber Network set-up on the existing fiber infrastructure.

b. Critical network media that makes up the PPD System shall be dedicated and immune to the performance of non-system devices.

c. As necessary, each RS-485 BUS (subnet) that makes up the PPD System shall contain its own power supply with battery backup.

d. The PPD System shall report power supply failures to administrators via text message.

2. Battery Backup

a. Local Controllers that make up the PPD System shall support backup battery functionality recharging circuitry.

3. Distributed Control. The PPD System may be divided into local control areas or subnets as necessary.

a. Each subnet that makes up the PPD System shall be capable of operating independently of a central computer or other control areas.

b. The failure of any subnet that makes up the PPD System should not impact the performance of any other subnet.

c. Each subnet controller that makes up the PPD System shall be capable of setting outputs and displaying alert text messages.

d. Local controllers that make up the PPD System shall communicate with the central server via an Ethernet-based local area network.

e. Two modes of PPD System operation shall be possible:

1 Server-led operation - All alert decisions are performed by the central PPD

Server and backed up by distributed controllers. This may be necessary when complex control scenarios are needed. In the event of a server crash, local controllers shall perform critical functions including button press, exit, and supervision alerts.

2 Controller-led operation - Local Controllers continuously perform alert decisions and feedback on the decision information to a central server for display, logging, and secondary actions. Controllers shall be capable of reporting alert information to a central, IP-based, display panel for the display of alert messages from all controllers on site without the need for a server.

f. Server Recovery - In the event of a server crash all PPD System controller alerts shall be logged locally on the controller and uploaded to the server when the server resumes control.

g. Central Server Redundancy. The PPD Server software shall be provided with full hardware redundancy. The redundancy shall provide for continuous and autonomous synchronization between servers with a downtime of less than 1 minute in the event of a PPD System crash. Switch-over shall be an entirely automated process with no need for manual operation. Consult Guard1 TimeKeeping Systems for failover system suggestions/recommendations prior to implementation.

C. Software Functionality

1. The software shall manage alerts in real time with minimum latency. Alerts shall be displayed to operational personnel within ten seconds or less. The software shall display for each alert:

severity, status, date and time recorded, type, cause, description, and where appropriate, assigned housing zone and zone where alert occurred. The software shall clearly indicate new, active, unacknowledged alerts even when the alert view is not selected.

2. Software shall require acknowledgement of all alerts. Software shall log the user ID of the person acknowledging the alert and the date and time it was acknowledged. Alerts shall remain visible in the alerts list while the alert condition remains active or unacknowledged.

3. Software shall filter alerts displayed on the client alert view by alert status, severity, type, cause and assigned housing zone. Alerts of Emergency severity level shall not be filterable.

The alert display shall clearly indicate that it has been filtered.

4. The severity of all alert types shall be configurable by the customer / end user.

5. The software shall receive and display data in real time with minimum latency.

6. The system shall be capable of expansion to include additional equipment or any of the components described below that were not initially specified.

D. System Operation Alerts. The software shall be fully configurable and provide at minimum the following system alerts:

1. General system. The software shall signal an alert when at least one of the system’s components is not operational.

2. Software component. The software shall signal an alert for each individual software component when that component is not operational. Software components at a minimum shall include agents, services and data maintenance.

3. Hardware device. The software shall signal an alert for each individual Receiver when that device is not operational.

E. Notifications

1. The software shall provide notification capability, via e-mail or SMS for any alert. The software shall send notifications to individuals as configured by the Customer, based on mobile number or e-mail address. The software shall be capable of sending different notifications for different alerts to different individuals or groups.

2. Notifications for alerts shall be based on rules established by the Customer. Software shall provide filtering for notifications based on alert severity, type and cause.

3. The PPD system shall be configurable to open/close system outputs based on alert.

4. The PPD system shall support delivery of pre-defined alert messages to a remote IP port via

TCP/IP.

F. Duress Device System Alerts. The software shall provide at minimum the following alerts for the Duress Device System function:

1. Panic Alert. The software shall signal an alert when the panic button is pressed.

2. Not Vertical / Man Down. The software shall signal an alert when the Duress Device is not in a vertical orientation for a customer- configurable period of time.

3. Removed from Holster. The software shall signal an alert when the Duress Device has been removed from its holster for a customer- configurable period of time.

4. No Motion. The software shall signal an alert when the Duress Device has not detected motion for a customer-configurable period of time.

5. Not Seen. The software shall signal an alert when the Duress Device has not been seen for a customer-configurable period of time.

6. Enter On Duty Mode. The software shall signal an alert when the Non-Rechargeable Duress Device enters On Duty mode.

7. Enter Off Duty Mode. The software shall signal an alert when the Non-Rechargeable Duress Device enters Off Duty mode.

8. Enter Test Mode. The software shall signal an alert when the Non- Rechargeable Duress Device enters Test mode.

9. Exit Test Mode. The software shall signal an alert when the Non- Rechargeable Duress Device exits Test mode and shall display the results of the device self-test.

10. Low Battery. The software shall signal an alert when the battery voltage is low. The Rechargeable Duress Device should be recharged. The Non-Rechargeable Duress Device batteries should be replaced.

11. Very Low Battery. The software shall signal an alert when the battery voltage is very low. The Rechargeable Duress Device should be recharged immediately. The Non-Rechargeable Duress Device batteries should be replaced immediately.

G. Task Management System Alerts. The software shall provide at minimum the following alerts for the Task Management System function (FUTURE SCOPE):

1. Late Well-Being Check. The software shall signal an alert when a required well-being check has not been completed within the required time period.

2. Missed or Incomplete Inspection. The software shall signal an alert when an inspection has not been completed within the required time period.

3. Return from Out Zone. The software shall signal an alert when an inmate has not been recorded as returned from our zone by the scheduled time.

4. Observation. The software shall signal an alert when an observation with alert severity is recorded.

H. Well-being Check Alerts. The software shall provide at minimum the following alerts for the Well Being Check System function (FUTURE SCOPE):

1. Late Well Being Check. The software shall signal an alert when a required well-being check has not been completed within the required time period.

2. Missed or Incomplete Inspection. The software shall signal an alert when an inspection has not been completed within the required time period.

3. Observation. The software shall signal an alert when an observation with alert severity is recorded.

4. Download with Unassigned Buttons - The software shall signal an alert when a PIPE download contains unassigned buttons.

I. System Detail Views

1. Staff – The software shall provide a detailed screen for viewing staff information. The detail screen shall include general information, current status including alerts, position and conditions, and history including alerts, acknowledgments and movements recorded for the staff member. The system shall provide Duress Device and tracking tag commissioning for a staff member via the detail view.

2. Assets - The software shall provide a detailed screen for viewing asset information. The detail screen shall include general information, current status including alerts, position and conditions, and history including alerts, acknowledgments and movements recorded for the asset. The system shall provide tracking tag commissioning for an asset via the detail view.

3. Locations - The software shall provide a detailed screen for viewing location information. The detail screen shall include general information, current status including alerts and conditions, and history including alerts, acknowledgments, checks, observations, annotations for the location.

4. Inmates - The software shall provide a detailed screen for viewing inmate information. The detail screen shall include general information, current status including alerts, position and conditions, and history including alerts, acknowledgments, movements, well- being checks, observations, annotations, handouts, and all other activities recorded for the individual. The system shall provide tracking tag commissioning for an inmate via the detail view.

J. Graphical Interface – Site Plans and Floorplans

1. The graphical interface shall be configured to display one or more site plans of the facility and include a floor plan for each building. Software shall provide the capability to zoom and pan the plan drawings.

2. The software shall display each zone on a map. The software shall clearly indicate the highest alert severity in each zone. The software shall highlight the zone and flash the search area in red if an active emergency alert is in that zone.

3. The software shall display a list of inmates and optionally staff and/or assets in a zone when that zone is selected. The software shall display additional information about an inmate, staff member or asset when the user hovers the cursor over an item in the list. The software shall display a detail view of an inmate, staff member or asset when the user double clicks on an item in the list.

K. Staff / Inmate Count

1. The software shall provide a selectable view for one or more zones. The display shall be filterable by zones. The graphic shall display inmates, officers, optional staff and/or assets in each zone in either a tile or list format. The function shall have the option to display pictures in tiles. The function shall sort tiles or lists by 1) alert severity, 2) alphanumeric by name, 3) alphanumeric by bed or 4) arrival time.

2. The count function shall display general information about inmates, staff and/or assets in the tile or item in the list, including severity alert (if any), late well-being checks and time by which the next check must be completed when the user hovers the cursor over a tile or item in the list. The function shall display a detail view of an inmate, staff member or asset when the user double clicks on a tile or an item in the list.

3. The function shall clearly indicate which inmates in a housing zone are or are not assigned to that housing zone and alert (as configured) the location of inmates that are out of their assigned housing zone. The function shall display the current inmate headcount for the zone, in and out counts, number of staff in the zone, and any active alerts in the zone. The function shall display summary count information and be collapsible by zone.

L. Rule Configuration

1. The software shall support Time-Between rules. Time-Between rules shall specify the maximum time permitted between checks. An alert shall be created if a check does not take place by the end of the time period.

2. The software shall support Period-based rules. Period-based rules shall specify a time period (hours, days) during which inspections must be performed. An alert shall be created at the end of the period if a required inspection is incomplete or does not take place.

3. The software shall support a Validity Period, a time span or date span during with a Time-Between or Period-based rules shall be valid.

4. The software shall support configurable rules that specify the maximum time permitted between checks. An alert shall be created if a check does not take place by the end of the time period.

5. The software shall support schedule-based rules that specify a time period (hours, days) during which inspections must be performed. An alert shall be created at the end of the period if a required inspection is incomplete or does not take place.

6. The software shall support a validation period, a time span or date span during with a time or schedule-based rule shall be valid.

M. Monitor Function. The system shall be capable of monitoring and displaying select data in real-time.

The system shall provide, at minimum, the following monitoring function:

1. By Zone – Monitor movement of all inmates, staff and assets within selected zones.

2. By Inmate – Monitors movement of selected inmates within all zones.

3. By Staff – Monitors movement of selected staff within all zones.

4. By Asset – Monitors movement of selected assets within all zones

5. By Action – Monitors all logged actions. Filterable by source, type and severity.

N. Reporting Function

1. The system shall display report previews on-line.

2. The system shall output reports in multiple formats, including at a minimum, Word, Excel, PowerPoint, PDF, TIFF, MHTML, CSN and XML.

3. The system shall provide reports over a user configured date/time range.

4. The system shall save user configured reports and provide the capability to rerun those reports with date/time ranges automatically adjusted for the current date/time (for example, Daily reports).

O. Reports. The system shall provide, at minimum, the following reports:

1. Well-being – Reports well-being check compliance and exceptions, or exceptions only.

Reports either total time between checks or deviation from rule setting. Report is filterable by inmates, locations, assigned home zones, well-being check rules and observing staff.

2. Location Inspection – Reports location inspection compliance and exceptions, or exceptions only. The report is filterable by locations, zones and location inspection rules.

3. Log – Reports all logged actions. Report is filterable by inmates, staff, assets, locations, zones, activities, handouts, observations, assigned home zones, observing staff, features and alert severities.

4. Contact - Reports inmates, staff and/or assets that were in the same zone at the same time.

Report is filterable by inmates, staff and assets.

5. Movement – Reports movement by inmate, staff and/or assets between zones. Report is filterable by inmates, staff, assets and zones.

6. Movement by Zone – Reports movement of inmates, staff and assets within a selected zone.

Report is filterable by inmates, staff and assets.

7. Zone Occupant - Reports movement by inmate, staff and/or assets within a selected zone.

Report is filterable by inmates, staff and assets.

8. Pipe data – Reports Pipe detail data by Pipe. Report is filterable by Pipes.

9. Pipe download – Reports Pipe Downloads and detail data for select downloads.

P. Inmate Database (FUTURE SCOPE)

1. The software shall be integrated with the Customer’s JMS/OMS. Data shall be imported to the software from a file provided by the vendor of the JMS/OMS. Data shall include the following, or as required by Customer:

a. Inmate Name, Permanent ID, Booking Number, Gender, Date of Birth, Picture, Housing Zone Assignment, Cell/Bed Assignment, Keep Separate from Inmate(s).

b. The software shall be integrated with a customer specific topology file that maintains the relationship between zones, locations and beds.

c. Note: Integration with the Customer's JMS/OMS is optional. Certain features of the software will be unavailable if integration is not implemented.

Q. Inmate Tracking System Alerts. The software shall provide at minimum the following alerts for the Inmate Tracking System component (FUTURE SCOPE):

1. Out of Bounds. The software shall signal an alert when an inmate or asset is out of bounds.

2. Keep Separate. The software shall maintain a list of keep separates, individuals or groups, who must not be in the same zone. The software shall signal an alert when these inmates or groups are in the same zone.

3. Not Seen. The software shall signal an alert when an inmate or asset's tag has not been seen by the system within a customer- defined time period.

4. Tag Removed. The software shall signal an alert when an inmate's tag has detected it is no longer attached.

5. Low Battery. The software shall signal an alert when the inmate or asset's tag battery voltage is low and should be replaced.

6. Very Low Battery. The software shall signal an alert when the inmate or asset's tag battery voltage is very low and should be replaced immediately.

PART 2 – PRODUCT DESCRIPTION

2.1 MANUFACTURER

A. Acceptable Manufacturers:

1. Centrak, Inc. - Elpas PPD

2. TimeKeeping Systems, Inc. – Guard1

2.2 HARDWARE / SOFTWARE

A. The quantities of all system components shall be determined and installed by the Contractor based on the requirement to provide a fully operational PPD Man-Down Duress System as per the intent of the specific application and the MDOC Performance Criteria as recommended by the manufacturer.

2.3 SYSTEM NETWORK

A. The PPD System: server, workstations, and network components that comprise the PPD System will communicate over a 10/100 BASE-T Local Area Network (LAN) utilizing Dynamic or Static TCP/IP protocol.

B. The LAN network shall be configured by the contractor as a dedicated PPD LAN on an existing owner provided fiber infrastructure. Network management and stability shall be the responsibility of the contractor given that the Man-Down Duress System is deemed a life safety PPD System.

2.4 SOFTWARE ENVIRONMENT

A. The system shall support the following minimum installation requirements:

1. Server Operating system.

a. Windows Server 2012 R2

b. Windows Server 2019 or newer (2022 recommended)

c. Windows 10 (64-bit)

d. 2.80 GHz 64-bit 10-thread CPU

e. 32 GB RAM

f. Main Hard drive 100 GB free HDD space

g. Second Hard drive for Archives/Backups-500 GB free HDD space

h. Dual Network Interface Cards

i. Remote access to the Server via the Internet (via WebEx or VPN)

j. 1024x768 monitor

2. SQL Server.

a. SQL Server 2014 with Reporting Services in Native Mode

b. SQL Server 2019 or newer (2022 recommended) with Reporting Services in Native

Mode

c. SQL Server Express 2019 with Reporting Services in Native Mode (Mobile Task

Management and/or Well-being Check only)

3. Client PC Operating System.

a. Windows 7 SP1 (32/64-bit)

b. Windows 10 (64-bit)

c. Windows 11 (64-bit)

4. Client PC Hardware.

a. 2.80 GHz 64-bit 2-core CPU

b. 8 GB RAM

c. 10 GB free HDD space

5. Mobile Device Operating System (Mobile Task Management only – Future scope)

a. Android 6.0 and higher. This is the preferred and recommended mobile device operating system.

b. iOS 10.3.3 and higher

6. Mobile Devices (Mobile Task Management only – Future scope).

a. All Android devices.

b. Cat S41. This is the preferred and recommended mobile device.

c. iPhone 7 or newer

d. iPod Generation 6 or newer

7. Server Hardware for Mobile Task Management and/or Well-being Check only (all requirements must be met – Future scope)

a. 2.80 GHz 64-bit 2-core CPU

b. 8Gb RAM

c. Main hard drive 50Gb free HDD space

d. Second hard drive for archives/backups – 500Gb free HDD space (recommended)

e. Remote access to the Server via internet (via WebEx or VPN)

f. 1024x768 monitor

B. The system shall implement a database optimized for on-line access to real- time data. The system shall implement a data warehouse optimized for access to historical data and for report generation. The system shall implement a data maintenance process that regularly transfers data from the on-line database to the data warehouse.

C. The system shall implement an archive process that transfers data from the data warehouse to an archive file based upon customer configurable settings. The system shall implement an archive restore process that restores an archive file into a temporary database so its historical data can be accessed.

The system shall implement a disaster and recovery process that checks data integrity, rebuilds indexes and backup databases based upon customer configurable settings.

2.5 DURESS DEVICE SYSTEM

A. The Duress Device System shall provide emergency signaling for officers, staff, and visitors within a correctional facility or similar institution.

1. Provide a complete Duress Device System of the type, size, capacity and characteristics described below.

2. Install the system and test all components.

3. Test the RF performance and operational performance of the System to comply with these specifications.

B. The correctional facility does not have a complete personnel database that can be imported into the Personal Protection Device system. All credentials and users shall be created by the contractor and shall be stored on a local server (on-site). The facility shall have the ability to manage and maintain the system locally.

C. Duress Device System Overview

1. The duress device system basis of design is Guard1 – TimeKeeping Systems, Inc.

2. Officers carry a Duress Device, typically in a belt holster, optionally with a lanyard or other means.

3. When the Duress Device panic button is pressed, it is detected by the system and an alert condition exists. The alert is communicated to operational personnel via software. A panic button press is defined as a Primary Alert.

4. The Duress Device supports three Secondary Alerts: Not vertical ("man down"), removed from holster, and no motion. Secondary Alerts can be optionally enabled and their warning times and grace periods configured.

5. The facility is divided into zones, as determined by the customer and the system designer. The facility is instrumented with Receivers in order to implement zone location of the Duress Devices. An Ethernet network supports the transfer of Duress Device information to a server, where software determines the zone location of each device, and manages alerts.

6. The system locates Duress Devices within a zone. Close proximity receivers can be installed for use with Non-Rechargeable Duress Devices where greater accuracy is required. The close proximity receivers transmits its ID at least once every 200 milliseconds. When an alert condition exists the Duress Device receives these transmissions, determines the closest receiver, and forwards its ID to the system software.

7. The Duress Device System shall be provided as one component of an integrated Personal Protection Management System.

D. The Duress Device System shall utilize the following products:

1. Receiver

a. Models. Receiver Models shall include versions for 1) covert mounting or administration areas where abuse is unlikely 2) angle mounting in a hardened case of high impact plastic, 3) flush mounting in a hardened case of high impact plastic,

4) commissioning in a booking or classification environment.

b. Power. All Receiver models shall implement Power over Ethernet. All Receiver models shall accept power from a separate power adapter where Power over Ethernet is not available.

c. Channels. All Receiver models shall contain multiple 2.4 GHz receivers, capable of concurrent reception on multiple channels.

2. Duress Device

a. Provide a quantity of 500 duress devices to be assigned to each staff member.

b. Transmission. All Duress Device models shall implement a 2.4 GHz radio. The Duress

Device shall transmit once per second, 24 hours per day, on multiple channels.

c. Alerts. The Duress Device shall provide a Primary Alert when the panic button is pressed. The Duress Device shall provide Secondary Alerts for not vertical ("man down"), removed from holster, and no motion conditions. Secondary Alert enabled/disabled states and warning times shall be configurable.

d. Transmission During Alert. When an alert condition exists, the Duress Device shall transmit an amplified signal.

e. Low Battery. The Duress Device shall detect Low Battery and Very Low Battery conditions. In Very Low Battery state, the device shall operate on a "best effort" basis.

Panic Alerts shall operate although operation cannot be guaranteed.

f. Duress devices shall be shipped to the facility labeled per the MDOC standards.

g. Transmitter Storage:

1 The devices shall be stored in two (2) PPD cabinets (model DURESS-CAB- 216), provided by Guard1 and installed by the contractor, with a capacity for up to 216 devices.

2 The final installation location of the cabinets shall be determined and coordinated with the facility.

3. Rechargeable Duress Device

a. Recharge cycle. The Rechargeable Duress Device shall be capable of a full recharge in four hours. The Rechargeable Duress Device shall operate for a full twenty-four hours before requiring recharge.

b. Charger. The Duress Device Charger shall be capable of charging up to 6 Duress Devices concurrently. The Duress Device Charger shall mount in a standard 19" rack and multiple chargers can be placed in a single rack depending upon the height and capacity of the rack.

c. Holster. Provide a holster for each Rechargeable Duress Device.

4. Non-Rechargeable Duress Device

a. Batteries. The Non-Rechargeable Duress Device shall use user-replaceable batteries, type CR123A. Normal battery life is approximately eighteen months.

Batteries should be replaced annually.

b. Operation. The Non-Rechargeable Duress Device shall have an On Duty mode, in which Primary Alerts and enabled Secondary Alerts shall be transmitted. The Non- Rechargeable Duress Device shall have an Off Duty mode, in which only Primary (panic button) Alerts shall be transmitted.

c. Test Mode. The Non-Rechargeable Duress Device shall have a test button. When the test button is pressed, the device performs a self-test. Pressing the panic button in Test Mode shall exit to On Duty mode. Pressing the test button while in Test Mode shall exit to Off Duty mode. The results of the test shall be reported by the Non- Rechargeable Duress Device to the system software.

d. Holster. Provide a holster for each Non-Rechargeable Duress Device.

5. Kiosk View. The system software shall provide a custom view showing the results of Non- Rechargeable Duress Device tests, for officers to view test results as they go on or off duty.

a. Close proximity receiver

b. A close proximity receiver can be used with Non- Rechargeable Duress Devices where more precise location is required within a zone.

c. Transmission. The receiver shall transmit a signal at least once every 200 milliseconds. When in an alert condition, the Duress Device shall receive the signal from one or more receivers and shall forward to the system software the ID number of the nearest receiver based on signal strength.

d. Power. The close proximity receiver shall be hardwired, operating from a low-voltage power supply. Battery operation is not permitted.

e. Mounting. The receiver shall mount in a standard single gang junction box.

6. Audible Annunciation

a. Self-contained amplifier and speaker with the ability to store and announce up to five

(5) pre-recorded messages.

b. Speaker shall be capable of 80dB, adjustable.

c. Provide units to be installed in each housing unit, segregation, and/or sleeping showering areas. See Guard1 drawings for quantity and location.

d. Annunciation criteria: The speaker system shall be programmed to announce the pre-recorded messages within the building where the event is occurring. For design purposes, no announcements shall be made throughout the entire facility. All messages shall be considered local events and, therefore, delivered individually to the local building. This criterion shall be coordinated and approved by the facility before programming.

e. The pre-recorded message “opposite gender in the area” shall be announced upon an opposite gender enters in a designated building. MDOC criterion shall be met and coordinated with Guard1 for this announcement.

f. The contractor shall program the annunciation system to allow quiet times at night (sleeping hours), with no audible announcements in the building. The quiet hours need to be coordinated with the facility.

g. Blue lights (PREA requirements) shall remain active even at night time if an opposite gender is identified in the building.

h. Speaker power shall have dedicated power supplies, surge-protected, and on battery backup.

7. Precision Location Tag

a. The Precision Location Tag (PLT) can be used with non-rechargeable duress devices where a more precise location is required within a zone.

b. Transmission. The PLT shall transmit a signal at least once every 200 milliseconds.

When in alert condition, the duress devices shall receive the signal from one or more PLTs and shall forward to the system software the ID number of the nearest PTL based on signal strength.

c. Power. The PLT shall operate from a customer-replaceable battery or from a +4.5V to +24V DC power supply. Power can also be direct feed or fused in-line.

d. Mounting. The PLT shall mount in a standard single-gang junction box.

e. PLT power shall have dedicated power supplies, surge-protected, and on battery backup..

8. Blue Lights (PREA requirements)

a. The contractor shall provide and install blue lights to meet the PREA requirements where indicated in the drawings.

b. The lights shall be installed in single-gang metal boxes per the MDOC standards.

c. The lights shall be installed in a visible location from cells doors, bathrooms doors, showers doors/openings, beds, etc.

d. Ceiling and wall-mounting is acceptable. Follow the drawing instructions for location or submit an RFI for clarification or proposed new location based on field conditions.

e. Blue lights shall be active throughout the day (no requirement for sleeping hours), meeting the MDOC/Guard1’s rules of operation.

2.6 INMATE TRACKING SYSTEM (FUTURE SCOPE)

A. The Inmate Tracking System shall provide real time zone-based location of inmates within a correctional facility or similar institution.

1. The system shall provide the optional capability of tracking assets such as equipment, tools, utensils, or keys.

2. Provide a complete Inmate Tracking System of the type size, capacity and characteristics described below.

3. Install the system and test all components.

4. Test the RF performance and operational performance of the System to comply with these specifications.

B. Inmate Tracking System Overview

1. Inmates wear a Tracking Tag on a wristband. The tag transmits a signal once per second.

2. The facility is divided into zones, as determined by the Customer and the system designer. The facility is instrumented with Receivers, which acquire the signals transmitted by the Tags. An Ethernet network supports the transfer of tag information to a server, where software determines the zone location of each device.

3. The Inmate Tracking System shall be provided as one component of an integrated Real Time Management System.

C. The Inmate Tracking System shall utilize the following products:

1. Receiver

a. Models. Receiver Models shall include versions for 1) covert mounting or administration areas where abuse is unlikely 2) angle mounting in a hardened case of high impact plastic, 3) flush mounting in a hardened case of high impact plastic,

4) commissioning in a booking or classification environment.

b. Power. All Receiver models shall implement Power over Ethernet. All Receiver models shall accept power from a separate power adapter where Power over Ethernet is not available.

c. Channels. All Receiver models shall contain multiple 2.4 GHz receivers, capable of concurrent reception on multiple channels.

2. Wristband Tag

a. Transmission. The Wristband Tag shall implement a 2.4 GHz radio. The Wristband Tag shall transmit once per second, 24 hours per day.

b. Physical. The Tag shall be separate from the wristband. Electronics shall be fully encapsulated. The Tag shall be washable and after an inmate is released, re-usable with a new wristband on a new inmate.

c. Battery. The Tag shall use a primary lithium battery. Battery life shall be a minimum of four years.

d. Removal Detection. The Tag shall have the ability to detect if it has been removed from the inmate. If removed or re- attached, the Tag shall broadcast its status to the system and generate an alert.

3. ID Badge Tag

a. Transmission. The ID Badge Tag shall implement a 2.4 GHz radio. The ID Badge Tag shall transmit once per second, 24 hours per day.

b. Physical. The Tag electronics shall be fully encapsulated. The Tag shall be washable and after an inmate is released, re-usable for a new inmate.

c. Label. The Tag shall implement a destructible label that cannot be removed in one piece.

d. Battery. The Tag shall use a primary lithium battery. Battery life shall be a minimum of two years.

4. Asset Tag

a. Transmission. The Asset Tag shall implement a 2.4 GHz radio. The Asset Tag shall transmit once per second, 24 hours per day.

b. Physical. Electronics shall be fully encapsulated. The Tag shall conform to any number of housing configurations as required by the Customer.

c. Battery. The Tag shall use a primary lithium battery. Battery life shall be a minimum of two years.

2.7 TASK MANAGEMENT SYSTEM (FUTURE SCOPE)

A. The Mobile Task Management System shall automate and provide documentation of repetitive tasks, using mobile devices.

1. Provide and implement a system which meets or exceeds the specifications described below.

B. Task Management System Overview

1. Tasks – including well-being checks, inspections, handouts, activities are created using the system software. The software creates alerts for tasks that have not been completed as required.

2. Officers carry mobile devices running the Mobile Application. The application manages officer logins, task lists, and input necessary to complete the tasks.

C. The Task Management System shall utilize the following products:

1. Mobile Device

a. The system shall use mobile devices approved by or sold by the PPD manufacturer.

The PPD manufacturer shall provide a list of tested devices for compatibility. Vendor warranty shall not apply to untested mobile devices.

b. The system shall use mobile software from the PPD manufacturer.

2. Wall Mount Tag

a. The system shall include a Wall Mount Tag with both NFC and QR code or equivalent.

The Wall Mount Tag shall be manufactured of high- impact plastic.

D. The Task Management System shall implement the following application features and operations.

1. Connection. The application shall connect to the system by any means permitted by the Customer – typically Wi-Fi, but cellular shall also be supported.