Schedule A, Attachment 1- Network Managed Services Business Specifications Worksheet.docx
DOCX document 102 KB Posted
- Attached to
- MDOC Inmate Network, Applications & Services RFS
- Solicitation number
- RFP-171-250000002079-2
- Issued by
- Alger County, Michigan
About this file
This document is a Network Managed Services Business Specifications Worksheet from the Michigan Department of Corrections (MDOC) and Department of Technology, Management, and Budget (DTMB), outlining comprehensive technical requirements for a prisoner device and network management solution. The solicitation seeks a contractor to provide network security, device management, identity access management, internet service, and network maintenance services across approximately 30 correctional facilities throughout Michigan. The solution must include mobile device management, network monitoring, security controls, device support, and connectivity services for prisoner-assigned devices, with specific requirements for device functionality, security, remote management, and technical support.
The procurement involves providing networked devices and infrastructure services for prisoner use, with detailed specifications around device capabilities, security protocols, and management systems. The solution must comply with state cybersecurity policies, support multiple device types and operating systems, and include features like remote device locking, location tracking, application control, and comprehensive logging and auditing capabilities. While specific pricing details are not provided in the document, the requirements suggest a complex, multi-year contract with potential for ongoing service and technology upgrades. The solution must provide 24/7 support, maintain robust security measures, and integrate with existing MDOC systems while allowing granular administrative control over device and network access.
View the file
Other files
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 1: NETWORK MANAGED 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
| Contents | 3 |
| Requirements Network Security and Monitoring (NSM) | 5 |
| Requirements Device Management (DM) | 15 |
| Requirements Identity Access Management (IAM) | 19 |
| Requirements Prisoner Device Support (PDS) | 25 |
| Requirements Prisoner Handheld Devices and Peripherals (PD) | 28 |
| Requirements Internet Service Provider (ISP) | 31 |
| Requirements Network Management & Maintenance (NMM) | 35 |
| Facility Locations | 41 |
Requirements Network Security and Monitoring (NSM)
Network Security- The vendor network and the SOM managed “offender” Wi-Fi network will be physically connected via a SOM managed firewall at each MDOC location. The vendor must provide specific network, protocol and port requirements for connecting vendor managed Wi-Fi connected devices to the vendor network. Solution must be compliant with all network security requirements as indicated in DTMB Policy 1345.00.05 (ENTERPRISE WIRELESS LOCAL AREA NETWORK (WLAN) STANDARD) and must comply with all other applicable DTMB policies.
The Contractor will be responsible for participating through completion of the State’s Security Accreditation Process and achieving Authority to Operate before cutover to production. The Security Accreditation Process includes a framework-based, questionnaire-driven security assessment and automated scans. Contractor must remediate any identified vulnerabilities at the Contractors expense unless otherwise waived in writing by the State. Contractor must work closely with DTMB and the Michigan Cyber Security (MCS) team to document the security assessment in the State’s Governance, Risk and Compliance (GRC) tool, which is currently Lockpath Keylight software.
| 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
| NSM 1.0 |
| The Contractor must install and manage Dynamic Host Configuration Protocol (DHCP), Proxy, routing, Domain Name Services (DNS), physical infrastructure and services at each facility. |
Note: This infrastructure must be installed on-site at each serviced facility to prevent unauthorized traffic leaving approved network parameter.
| NSM 2.0 |
| Contractor must configure Dynamic Host Configuration Protocol (DHCP) service to only provide DHCP leases to sanctioned (allow listed) devices. |
| NSM 3.0 |
| The Contractor must provide a network monitoring, detect, alert, locate and disable solution. |
Note: Solution must monitor traffic/services for performance, availability, and security. It must be able to detect and alert when network outages performance degradation, security incidents, and suspicious activity events occur.
| NSM 4.0 |
| The Contractor must follow SOM reporting and incident response procedures for all network outages, performance issues, and security incidents. |
| NSM 5.0 |
| The Contractor network and the SOM managed Wi-Fi infrastructure must be physically connected via a SOM managed firewall at each MDOC location. Contractor must provide connectivity details for applications security controls the Contractor would install and manage. |
| NSM 6.0 |
| Contractor must allow certain users to modify an allowed device list. |
Note: MDOC must approve the functionality.
| NSM 7.0 |
| Contractor managed DHCP service must be compatible with MDM solutions to allow for management of access to network services and applications. |
| NSM 8.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
| NSM 9.0 |
| The Contractor must provide access to an electronic gateway (or similar means) to the Contractors real-time network monitoring information, which must include (but is not limited to): |
· Service Level Agreement (SLA) metrics
· Circuit and device utilization
· NetFlow data
· Simple Network Management Protocol (SNMP) Events.
· Packet Loss
· Jitter
· Latency Metrics
· Unauthorized access logs
· Ability to generate reports using the above data/metrics
| NSM 10.0 |
| Contractor must participate in SOM incident response processes and must work with MDOC to develop and provide SLA’s for offered services. |
| NSM 11.0 |
| Contractor must notify designated MDOC personnel when an access or security incident is detected. |
| NSM 12.0 |
| Contractor must engage in standard SOM Michigan Security Accreditation process (MiSAP) to receive Authority to Operate (ATO) prior to “go-live.” |
Note: This includes the initial MiSAP and the required 3-year renewals
| NSM 13.0 |
| Contractor must provide time synchronization services to ensure accurate log timestamping. |
| NSM 14.0 |
| Contractor must monitor network activity for unauthorized traffic, and alert upon detection. |
Note: This includes but is not limited to unauthorized access to the internet, social media, video conferencing, texting etc.
| NSM 15.0 |
| Contractor must complete a full penetration testing assessment performed by a third party. |
Note: Contractor must remediate or address all vulnerabilities or concerns resulting from this assessment.
| NSM 16.0 |
| The Penetration testing must be completed at regular intervals. |
Note: Intervals must be approved by MDOC.
| NSM 17.0 |
| Contractor must provide auditing that includes but is not limited to; Successful user login, failed user login attempts, account lockouts due to failed attempts, user logout, and user session timeout (forced logout). |
| NSM 18.0 |
| The Contractor must implement and maintain compliance with FIPS 140-2 certified systems and encryption algorithms. |
| NSM 19.0 |
| The log size must be configurable and be of sufficient capacity (read: minimum size must be able to store data for ~30,000 untrusted users for 3 years to prevent the data from being overwritten to mask intrusion attempts or to impose any denial-of-service. |
| NSM 20.0 |
| Each device must have a unique identifier tracible by the network. |
| NSM 21.0 |
| The Contractor must use Web Application Firewalls (WAF) |
| NSM 22.0 |
| The Contractor must use an Intrusion Detection System (IDS) and Intrusion Prevention System (IPS) |
| NSM 23.0 |
| The Contractor may deploy the use of Virtual Private Network (VPN) |
| NSM 24.0 |
| The Contractor must provide Audit logs that include but not limited to the following: |
· Audit logs must be un-editable.
· Audit log capturing all data modifications.
· Audit Log for the security system for access, privacy, security controls, and audit functionalities if not built in.
· Maintain an audit log for all Prisoner Employee and Prisoner user and group activity and changes.
· Ability to run reports.
| NSM 25.0 |
| Contractor must disclose past incidents of security breaches, including descriptions, impacts, and mitigations. |
Note: Public companies must legally disclose and private companies do not have to.
| NSM 26.0 |
| The Contractor must provide a method of keylogging and be responsible for monitoring and reporting on the key log sessions. Logs must be maintained for a minimum of 3 years. |
| NSM 27.0 |
| Contractor must provide Behavioral Analytics to detect and analyze the way the systems are being used. Also, be able to act as defined by MDOC on the results of the detected behavior. |
| NSM 28.0 |
| Deploy real-time monitoring systems to log all user actions, including login attempts, file accesses, and data transfers. This information is used to build audit trails and facilitate forensic analysis. |
| NSM 29.0 |
| Set up automated controls that can isolate compromised segments, lock down user accounts, and notify security personnel immediately upon detecting any breach attempts. |
OPTIONAL
| NSM 30.0 |
| Contractor may be able to work with ISP and SOM in configuring static IP assignment upon request from SOM. |
| NSM 31.0 |
| Contractor may provide a “geo-location” solution, using Wi-Fi signal strength to determine approximate physical location of connected devices. |
NSM 32.0
NSM 33.0
Requirements Device Management (DM) Application Management - Enables the Contractor to manage MDOC approved applications, including software distribution, patch management, and license compliance. The solution should interface with Identity Management tools and MDM utilities, providing the ability to deploy applications to appropriate user groups, monitor application usage, and report on license compliance.
Asset and Endpoint Management - enables the vendor to manage Wi-Fi enabled mobile devices used in this service offering. The solution shall provide the ability to remotely lock and wipe devices, alert on suspicious activity, log and monitor usage, enforce security policies, and distribute applications. The vendor must be able to provide logs upon request to MDOC personnel and DTMB MiSOC personnel. The solution should support device provisioning, monitoring, and troubleshooting. Only the assigned user (offender) should be able to access their own device, and MDOC staff must have access to all devices. The solution must comply with all applicable DTMB policies.
| 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
| DM 1.0 |
| The Contractor must be responsible for the management and support of all Prisoner devices. |
| DM 2.0 |
| The Contractor must provide a Mobile Device Management (MDM) solution, including but not limited to: |
· Device provisioning
· Remote device wiping
· Automatic Device Enrollment (ADE)
· Mobile Threat Defense (MTD)
· Remote device locking
· Monitoring and alerts upon detection of suspicious activity
· User activity logging and monitoring
· Enforce security policies
· Application distribution
· Management of functionality for physical and wireless interfaces (Wi-Fi, Bluetooth, etc.).
| DM 3.0 |
| The Contractor must support device provisioning, remote update capabilities, monitoring and troubleshooting. |
| DM 4.0 |
| The MDM software must detect if the device is connected to an unapproved network. |
Note: Detection must include functionality to lock, disable and shutdown the device. We must have the ability to enable the device remotely
| DM 5.0 |
| The Contractor must assist with the development of procedures for MDOC to request logs, manage emergency changes, and assist with physical extraction of devices for forensic purposes. Configure applications distributed through MDM, and other associated workflows. |
| DM 6.0 |
| The Contractor must provide a solution to extract all data from the device (a.k.a. “data dump”), including (but not limited to): |
· Stored Credentials
· Configuration settings
· Log’s and other meta data
| DM 7.0 |
| The Contractor must provide a Single Point of Contact (SPOC) for all communications to/from MDOC. |
| DM 8.0 |
| The Contractor must provide regular support hours for inquiries, and requests. |
| DM 9.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
| DM 10.0 |
| The Contractor must provide a remote access solution to allow administrators to remotely access a Prisoner device to monitor activity in real-time and act on the device |
Note: This must not allow a Prisoner to ‘reject’ an administrator’s attempt to remotely access the device.
The contractor must provide the ability to turn on camera, video and microphone at MDOC’s discretion.
| DM 11.0 |
| The Contractor must provide for MDOC the ability to remotely track device’s location statistics. Note: Ability to track and locate device |
| DM 12.0 |
| Contractor must provide tamper resistance and reporting. |
Note: Device must report when it detects that it’s been manipulated so the device can be automatically disabled.
| DM 13.0 |
| The system must have the ability to shut down devices that are not current. |
OPTIONAL
DM 14.0
Requirements Identity Access Management (IAM) Identity and Access Management - provide a Solution that enables the Contractor to manage user accounts, including user directory services, access control, and authentication. The solution will provide to administrators the ability to manage user profiles, reset passwords, and monitor user activity.
| 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
| IAM 1.0 |
| The Contractor must provide an identity / access management solution that enables administrators to manage end users (i.e., Prisoners), including but not limited to, user accounts, access control, and authentication. |
| IAM 2.0 |
| The Contractor must allow administrators to perform functions including but not limited to: |
· Create, manage, and delete user profiles (including groups, tags, and other account attributes)
· Create, manage, and delete user groups (including assigned users, tags, and other attributes)
· Reset user passwords
· Monitor user activity
| IAM 3.0 |
| The Contractor must allow administrators to allow, restrict, or deny access to applications, websites, and functionalities of external systems via API, web services, and/or other authentication/monitoring methods. |
| IAM 4.0 |
| The Contractor must allow administrators to apply modifications in masse (apply a change to multiple accounts with one action). |
| IAM 5.0 |
| The Contractor must assist with providing or developing documentation on how to use all functions available to MDOC within the offered solution- account creation, rights management, etc. |
| IAM 6.0 |
| The Contractor must provide API/web services documentation for all offered solutions |
| IAM 7.0 |
| The Contractor must offer on-premises management or cloud management of identity/access management services, clearly indicating service availability and support structures. |
Note: Cloud management services must be accessed via secure portal.
| IAM 8.0 |
| The Contractor must store logs for all changes made to accounts, groups, or other objects within the system indefinitely (36 months post contract), including but not limited to: |
· Account making the change
· Time and date of change
· Actions taken
· Affected profiles/groups
| IAM 9.0 |
| The Contractor must store activity logs for all accounts indefinitely (36 months post contract), with the following included but not limited to: |
· Activity (website accessed, application opened, file opened, etc.)
· Time and Date
· User Account
· Device Name
| IAM 10.0 |
| The Contractor must provide regular support hours for inquiries, and requests. |
Note: MDOC must approve the support model.
| IAM 11.0 |
| The Contractor must respond to inquiries/support requests within the timeframes defined in the SLA. |
The Contractor must work with MDOC to develop SLA’s and support structures for emergency and escalated requests- this will take place prior to contract award to ensure all expectations are clear.
| IAM 12.0 |
| The Contractor must include the following attributes to user accounts (but not limited to): |
· Full Name
· MDOC Number
· Cell Assignment
· Location (Facility)
· Group Memberships
· Tags
· Notes
· Assigned device name/tag
| IAM 13.0 |
| The Contractor must include the functionality to restrict profiles for use on specified devices. |
Note: No Prisoner account should be able to log into a device that isn’t assigned to that Prisoner. This must be done via biometrics.
| IAM 14.0 |
| The Contractors solution must be compatible with devices running on various Operating Systems. |
| IAM 15.0 |
| The Contractor must include backup/restoration services in the event of an outage/data loss. |
| IAM 16.0 |
| The contractor must integrate with MDOC’s Offender Management System for offender demographic and other data as required |
| IAM 17.0 |
| Specified MDOC staff must have remote access. |
OPTIONAL
| IAM 18.0 |
| The Contractor may develop a process where certain staff can request changes to Prisoner account attributes. |
| IAM 19.0 |
| The Contractor may fulfill Prisoner account within the timeframes defined in the SLA. |
| IAM 20.0 |
| The solution may be compatible with various devices, including but not limited to tablets running Android or iOS . |
Requirements Prisoner Device Support (PDS) Prisoner Device Support - Provide a Solution that enables the Contractor to manage and support prisoner devices. The Solution will provide to administrators the ability to manage user profiles, reset passwords, and monitor user activity. This support includes but is not limited to the operating system, hardware, firmware (i.e security and OS patches) and the application that resides on the device.
| 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
| IDS 1.0 |
| The 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.).
| IDS 2.0 |
| The Contractor must provide the ability for assigned MDOC staff to review all communication between Prisoner and the Contractor. |
| IDS 3.0 |
| The Contractor must interface with a Mobile Device Management (MDM) solution, such that user and device properties can be automatically associated to support requests |
| IDS 4.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
| IDS 5.0 |
| The Contractor must allow certain staff to submit support requests on a Prisoner’s behalf. |
Note: No Prisoners should be able to submit requests for another Prisoner or device besides their own assigned device.
| IDS 6.0 |
| The Contractor must familiarize themselves with all warranties relating to devices covered under this service. |
| IDS 7.0 |
| The Contractor must work with MDOC to develop procedures through which support requests would be submitted. |
| IDS 8.0 |
| The Contractor staff that require entry to an MDOC correctional facility must satisfactorily complete all requirements (e.g., training, LEIN background checks, etc.) |
| IDS 9.0 |
| The Contractor must include in their support model a method to process warranty related issues. This must be included in the support model. |
Note: This includes assisting (through support) with devices needing (offsite repairs), that require documentation, in-warranty requirements, out-of-warranty requirements, additional parts, delay, etc.)
| IDS 10.0 |
| The Contractor must comply with all Service Level Agreements (SLA’s). |
| IDS 11.0 |
| The Contractor must provide a Single Point of Contact (SPOC) for the device support solution and associated processes. |
| IDS 12.0 |
| The Contractor must be able to provide the support needed to resolve reported issues. |
Note: This includes from the initial support request analysis through resolution.
| IDS 13.0 |
| Contractor must be responsible for the repair of the devices. |
| IDS 14.0 |
| The Contractor must provide (as-needed) documentation to assist with resolution of common errors. |
| IDS 15.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
OPTIONAL
IDS 16.0
Requirements Prisoner Handheld Devices and Peripherals (PD) Prisoner Handheld Devices and Peripherals - Provide a Solution that provides a variety of devices so that MDOC can decide which devices are applicable for which prisoners.
| 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
| PD 1.0 |
| Contractor must offer various devices with a minimum screen size of 10 inches. |
Note: Devices with a larger screen size may be allowed for specific Prisoner population subsets (e.g. Education, security level, etc.).
Note: Devices include but are not limited to tablets and laptops.
| PD 2.0 |
| Contractor must include device options without Wi-Fi Direct connect functionality. |
| PD 3.0 |
| The Contractor must demonstrate how the device is tamper resistant and how the device disables itself from being used. |
| PD 4.0 |
| The Contractor must offer a solution (e.g. docking station) for software that MDOC would require physical connection to the network to function. |
| PD 5.0 |
| The devices must include or be compatible with an external keyboard. |
Note: Keyboard specifications must be assessed and approved by MDOC.
| PD 6.0 |
| The Contractor must offer “rugged” devices with improved durability and shock resistance. |
Note: The Contractor may include “water resistant” as a feature.
| PD 7.0 |
| The Contractor must include a feature of the device detecting unapproved traffic and disabling the device. |
| PD 8.0 |
| Offered devices must be compatible with Mobile Device Management (MDM) solutions: |
Note: Including but not limited to (remote locking, wiping, and locating) tablets as a part of the security solution.
| PD 9.0 |
| Contractor must offer a comprehensive warranty with replacement options for damaged devices. |
| PD 10.0 |
| The Contractor must include the functionality to disable specific applications and services as needed. |
| PD 11.0 |
| The Contractor must include the functionality to add or remove specific applications and services as needed. |
| PD 12.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
OPTIONAL
| PD 13.0 |
| Offered device may be compatible with an external track pad and/or mouse peripheral, either built in or through an adapter or docking station. |
| PD 14.0 |
| Offered device must allow an imaging (or similar) deployment solution, such that administrators can deploy tablets with preset configurations, applications, permissions, etc. |
Requirements Internet Service Provider (ISP) Internet Service Provider - Provide a Solution that gives a reasonable expectation of service of internet connectivity at each facility.
| 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
| ISP 1.0 |
| The Contractor must, provide network connectivity access services to each MDOC correctional facility throughout the State. |
| ISP 2.0 |
| The Contractor must identify a single point-of-contact for any issues and/or inquiries related to data services provided to these facilities (including but not limited to downtime, requests of logs/reports, upgrades, downgrades, addition or removal of service, etc.) |
| ISP 3.0 |
| The Contractor must develop and manage installation and removal of equipment. |
Note: This must include any steps required to get subcontracted installers approved to access MDOC correctional facilities
| ISP 4.0 |
| Services and equipment must be compliant with all telecommunications industry standards including, (FCC, MPSC, IEEE, and BICSI). |
| ISP 5.0 |
| The Contractor must provide upwards of a 120% capacity in overutilization. |
Note: This is in regard to all approved MDOC applications and services.
| ISP 6.0 |
| The Contractor must be able to provide: |
· Current data network capacity
· Expansion capacity
· Capacity limits
· CPE equipment required for each speed and/or type of service
| ISP 7.0 |
| The Contractor must monitor, report and alert on usage statistics monthly for review by the State in relation to throughput consistency, availability, and latency |
| ISP 8.0 |
| The Contractor must accept problem reporting by phone and email. |
| ISP 9.0 |
| The Contractor must provide procedures for problem resolution of any contractor equipment and infrastructure. |
| ISP 10.0 |
| The Contractor must plan, coordinate, and perform maintenance on network services equipment during a maintenance window approved by MDOC. |
| ISP 11.0 |
| The Contractor equipment must be in accordance with the most recent requirements of the National Electrical Code, EIA/TIA standards, state and local codes, ordinances and regulations of any other governing body-having jurisdiction. |
| ISP 12.0 |
| The Contractor must designate a Single Point of Contact (SPOC) that MDOC can work with through the life of the contract. |
| ISP 13.0 |
| MDOC must be notified of price adjustments at least 30 days prior to changes. |
[should be standard language available for pricing adjustments for RFS, prefer to use Standard language]
| ISP 14.0 |
| Provide Monthly cost reports for network services in Excel spreadsheet formats. |
All one-time and recurring charges must be identified.
| ISP 15.0 |
| The Contractor must allow administrators to perform functions including but not limited to: |
Allow access, restrict access, or deny access to applications, websites, and functionalities of external systems via API, web services, and/or other authentication/monitoring methods.
OPTIONAL
| ISP 16.0 |
| The Contractor may provide static IP reservation services for each serviced facility |
Requirements Network Management & Maintenance (NMM) Network Monitoring – This includes the monitoring the network for performance, availability, and security. The Solution will be able to detect and alert on network outages, performance degradation, and security breaches. The Contractor will be expected to follow SOM reporting procedures for all network outages, performance degradation, and security breaches. The Contractor will monitor bandwidth usage and identify potential bottlenecks. The Contractor will be expected to provide bandwidth utilization reports and activity logs upon request, and some logs will need to be sent to State of Michigan cybersecurity personnel at regularly scheduled intervals.
Network Services - Including coordination with the ISP(s), troubleshooting and resolving service issues, planning and coordinating service upgrades/modifications as-needed or requested by MDOC, notifying impacted users of outages (planned/unplanned/emergency/etc.), and providing status updates of ongoing efforts within the scope of providing these internet services. These services would need to be managed for all MDOC correctional facilities within the State. The Solution must comply with all applicable DTMB policies.
Network Performance - The Contractor will be able to measure and report on common performance metrics (latency, jitter, wan circuit utilization, etc.), and provide these reports both upon request and at regular intervals to MDOC personnel, DTMB Agency Services, and DTMB Security Operations. The solution must comply with all applicable DTMB policies.
| A |
| B |
| C |
| D |
| Business Specification Number |
| Business Specification |
| Current Capability |
| Requires Configuration |
| Requires Customization |
| Future Enhancement |
| Not Available |
| Contractor must explain how they Must 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
| NMM 1.0 |
| Contractor must provide and manage network and infrastructure services as part of the solution. |
Note: Contractor will need to work with DTMB on a network layer handoff. Services include but not limited to DHCP, DNS etc.
Note 2: DTMB Must provide the vendor with applicable SSID’s
| NMM 2.0 |
| The Contractor must provide network maintenance services that include routine maintenance, upgrades, and repairs. |
| NMM 3.0 |
| The Contractor must ensure that the network is operating at peak performance. |
| NMM 4.0 |
| All Contractor supplied computer hardware and software will be kept current and on platforms or versions supported by the respective manufacturers and/or |
software vendors.
| NMM 5.0 |
| The Contractor must provide a Single Point of Contact (SPOC) for all support and maintenance-related issues for services contracted. |
| NMM 6.0 |
| The Contractor must ensure scheduled maintenance is completed during MDOC approved maintenance windows. |
| NMM 7.0 |
| The Contractor must have multiple methods for MDOC to contact e.g. direct email, phone |
Note: The Contractor must provide 24/7 support for critical issues.
| NMM 8.0 |
| The Contractor must perform full backups on a weekly basis and incremental daily backups. All copies of system data, including backups must remain within the continental U.S. |
| NMM 9.0 |
| The Contractor must conduct an annual failover test that will adequately |
demonstrate the Contractor’s ability to recover the system and transfer of operations to a failover site.
| NMM 10.0 |
| The Contractor must maintain and provide copies of a recommended failover plan |
for use when the system becomes unusable.
| NMM 11.0 |
| The Contractor with input from the State, will create and maintain a test plan for conducting an annual failover test. The State will approve the test plan annually. |
| NMM 12.0 |
| The Contractor must provide an annual plan that identifies all planned hardware and |
system software upgrades. Key elements include an executive summary, hardware strategy (including server strategy, storage strategy, tape strategy, connectivity strategy, router environment, and network security strategy), and software strategy (including OS, DBMS, and independent software contractor product considerations).
| NMM 13.0 |
| The Contractor must provide operational and technical service, and assistance to restore and operate all system hardware. |
| NMM 14.0 |
| The Contractor supplied computer hardware and software must be kept current and on platforms or versions supported by the respective manufacturers and/or software vendors. |
| NMM 15.0 |
| The Contractor must provide the State with 90-calendar day notice of its intent to upgrade, enhance, or otherwise modify the existing production environment of the new system. |
| NMM 16.0 |
| The Contractor must be capable of restoring from backups that allow the recovery of the Contractor managed infrastructure. |
| NMM 17.0 |
| The Contractor must maintain and provide copies of a recommended failover plan for use when the system becomes unusable. |
| NMM 18.0 |
| The Contractor must create, review, and update a failover plan annually (or more often, if needed), including a review of recovery configurations to ensure there is adequate capacity to meet the requirements of the State in the event of an unscheduled outage. The State will approve the initial plan and each annual update. |
| NMM 19.0 |
| The recovery site must be on a different power grid and must be in a different geographic location (within the U.S.) than the active site. (It is the State’s preference that the recovery site be a minimum distance of ten (10) miles from the active site.) |
| NMM 20.0 |
| The Contractor, with input from the State, will create and maintain a test plan for conducting an annual failover test. The State will approve the test plan annually. |
| NMM 21.0 |
| The Contractor must provide operational and technical service, and assistance to restore and operate all implemented modules of the new system. |
| NMM 22.0 |
| The Contractor must respond to emergency inquiries/support requests within the timeframes defined in the SLA. |
| NMM 23.0 |
| The Contractor must interface to the State’s wide area network and provide capacity planning data for and needed growth in WAN capacity to MDOC sites. |
OPTIONAL
NMM 24.0
Facility Locations
HANDLON
CORRECTIONAL FACILITY
1728 BLUEWATER HWY, IONIA, MI 48846
WOMEN'S HURON VALLEY
CORRECTIONAL FACILITY
3201 BEMIS RD., YPSILANTI, MI 4819
BARAGA CORRECTIONAL FACILITY
13924 WADAGA RD, BARAGA, MI 49908
COOPER STREET CORRECTIONAL FACILITY
3100 COOPER ST, JACKSON, MI 49201
SAGINAW
CORRECTIONAL FACILITY
9625 Pierce Rd, Freeland, MI 48625
OAKS CORRECTIONAL FACILITY
1500 Caberfae Highway Manistee, MI 49660-9200
PARNALL CORR. FACILITY
1780 E. Parnall Jackson, MI 49201-7138
THUMB CORRECTIONAL FACILITY
3225 John Conley Drive Lapeer, MI 48446
BELLAMY CREEK CORR. FACILITY
1727 W. Bluewater Hwy.
Ionia, MI 48846
IONIA CORRECTIONAL FACILITY
1576 W. Bluewater Highway Ionia, MI 48846
GUS HARRISON CORR FACILITY
2727 E. Beecher Street Adrian, MI 49221
ALGER CORRECTIONAL FACILITY
N6141 Industrial Park Drive Munising, MI 49862
CARSON CITY CORR. FACILITY
10274 Boyer Road Carson City, MI 48811
CENTRAL MICHIGAN CORR. FACILITY
320 N. Hubbard St. Louis, MI 48880
CHIPPEWA CORR. FACILITY
4269 West M-80 Kincheloe, MI 49784
LAKELAND CORR FACILITY
141 First Street Coldwater, MI 49036
MUSKEGON CORR. FACILITY
2400 South Sheridan Dr.
Muskegon, MI 49442
CHARLES E. EGELER RECEPTION
3855 Cooper Street Jackson, MI 49201
G. ROBERT COTTON CORR FACILITY
3500 N. Elm Road Jackson, MI 49201
EARNEST C. BROOKS CORR. FACILITY
2500 S. Sheridan Road Muskegon Heights, MI 49444
MACOMB CORR. FACILITY
34625 26 Mile Road Lenox Township, MI 48048
MARQUETTE BRANCH PRISON
1960 U.S. 41 South Marquette, MI 49855
NEWBERRY CORR. FACILITY
13747 E. County Road 428 Newberry, MI 49868
ST LOUIS CORR. FACILITY
8585 N. Croswell Road St. Louis, MI 48880
KINROSS CORR FACILITY
4533 W. Industrial Park Drive Kincheloe, MI 49788
WOODLAND CENTER CORR. FACILITY
9036 E. M-36 Whitmore Lake, MI 48189
File details come from the government source that posted it. Updated .