Central Signal Control System - RFP - Final.docx

STATE OF MICHIGAN

Department of Technology, Management and Budget Procurement

Request For Proposal 190000001433 Central Signal Control System

Solicitation Manager Name: Christopher Martin Telephone Number: 517-643-2833 DTMB-Procurement Telephone Number 1-855-MI-PURCH (1-855-647-8724) E-Mail Address: martinc20@michigan.gov

This is a Request for Proposal (RFP) for Central Signal Control System to manage and communicate with Traffic Signals across the State.

Anticipated Timeline Issue Date

4/19/2019

Anticipated Date State Will Post Answers to Bidder Questions

5/10/2019

Anticipated Contract Begin Date

9/1/2019

*A proposal received at 3:00:01 p.m. ET is considered late.

The information in this document is subject to change. Check www.michigan.gov/SIGMAVSS for the current information.

Request For Proposal No. 190000001433 Central Signal Control System

PROPOSAL INSTRUCTIONS

1. RESPONSE PREPARATION. The State recommends reading all RFP materials prior to preparing a proposal, particularly these Proposal Instructions and the Bidder Information Exhibits. Bidders must follow these Proposal Instructions and provide a complete response to the items indicated in the table below. References and links to websites or external sources may not be used in lieu of providing the information requested in the RFP within the proposal. Include the Bidder’s company name in the header of all documents submitted with your proposal.

RFP Structure and List of RFP Documentation

2. CONTACT INFORMATION FOR THE STATE. The sole point of contact for the State concerning this RFP is listed on the Cover Page. Contacting any other State personnel, agent, consultant, or representative about this RFP may result in Bidder disqualification.

3. QUESTIONS. Bidder questions about this RFP must be emailed to the Solicitation Manager no later than the time and date specified on the Cover Page. In the interest of transparency, only written questions are accepted. Answers to questions will be posted on www.michigan.gov/SIGMAVSS. Submit questions using the format below; a Microsoft Excel format or similar is suggested.

Bidders should submit their questions using the following format:

4. MODIFICATIONS TO RFP. The State may modify the RFP at any time. Changes will be posted on www.michigan.gov/SIGMAVSS. This is the only method by which the RFP may be modified. The posted changes will automatically revise the original RFP.

5. DELIVERY OF PROPOSAL.

The Bidder must submit its proposal, all attachments, and any modifications or withdrawals electronically through www.michigan.gov/SIGMAVSS. The price proposal should be saved separately from all other proposal documents. The Bidder should provide the documents in a modifiable form (e.g., Microsoft Word or Excel), but has the option to also provide copies of any documents in a non-modifiable form (e.g., PDF). Bidder’s failure to submit a proposal as required may result in disqualification of such proposal. The proposal and attachments must be fully uploaded and submitted prior to the due date identified above. Do not wait until the last minute to submit the bid, as the SIGMA VSS system requires the creation of an account and entry of certain information, in addition to uploading and submitting the materials. The SIGMA VSS system will not allow a proposal to be submitted after the due date and time identified above.

Questions on how to submit information or how to navigate in the SIGMA VSS system can be answered by calling (888) 734-9749.

Bidder’s proposal should include the following information:

· Executive Summary - Top level summary of the most important aspects of the proposal, containing a concise description of the proposed Solution. Requested limitation: 2 pages.

· Table of Contents

· Proposed Solution - description clearly identifying and detailing the proposed Solution, and any processes, methodologies, and resources required by the system as defined in the scope of work. The following items should be included:

· Understanding of scope of services

· Project Management approach and ability to meet Exhibit A – Project Scope

· Requirement Responses - Completed Exhibit A, Table 1 Business Specification Worksheet

· High-level System Architecture and Design Plan (detailed plan to be prepared, submitted and approved once contracted)

· High-level Implementation Plan (detailed plan to be prepared, submitted and approved once contracted)

· Suggestions for innovative and other strategic approaches for cost efficiencies, deployment, testing, and training that would benefit the state.

· Any assumptions used in the preparation of the RFP response, if applicable.

· QA/QC Approach – Provide a QA/QC plan.

· Resume Templates for Key Personnel – Completed Exhibit A, Attachment 1 Resume Templates

· Vendor Information – Completed Exhibit B – Vendor Questions Worksheet

· Company and Team Qualification – including the following information:

· Three project references that closely match the scope of services being requested.

· Organizational chart identifying team make up and key personnel roles. This should include a summary of list of suppliers, subcontractors, and any other third-parties the Bidder plans to use, including a description of their role on the project.

· Detailed list of accomplishments on a same and/or similar type and scale of the scope of services being requested.

· Price proposal (Exhibit C) including Schedule C – Licensing Agreement

· Confidential Treatment Form

· Revisions, as-needed, to the following items:

· Schedule A - Contract Terms

· Schedule B - Maintenance and Support

· Schedule E – Service Level Agreement

· Schedule F – Data Security Requirements

· Schedule G – Disaster Recovery Plan

· Schedule H – Acceptance Testing

· Schedule I – Terms for On-Site Hardware

6. MANDATORY MINIMUM REQUIREMENTS. To avoid disqualification, the Bidder must provide documentation to support the following:

Minimum Requirements

The Solution must be compatible with controllers using the NTCIP 1202 v02 Center-to-Field (C2F) communications protocol and have the scalability to meet future NTCIP standards as they are approved (e.g., NTCIP 1202 v03 is currently under development).

Only those proposals that meet the mandatory minimum requirements will be considered for evaluation.

7. EVALUATION PROCESS. If all mandatory minimum requirements are met, The State will evaluate each proposal based on the following factors:

Proposals receiving 80 or more evaluation points will have pricing evaluated and be considered for award.

The State may utilize all Bidder information, without regard to a proposal’s technical score, to determine fair market value for goods or services sought. The State is not obligated to accept the lowest price proposal. If applicable, the State’s evaluation will include consideration of a Bidder’s qualified disabled veteran (QDV) status under MCL 18.1261(8). Additional information on the QDV preference is available at: http://michigan.gov/micontractconnect/0,4541,7-225-48677-123519--,00.html.

The State strongly encourages strict adherence to the Contract Terms. The State reserves the right to deem a bid non-responsive for failure to accept the Contract Terms. Nevertheless, the Bidder may submit proposed changes to the Contract Terms in track changes (i.e., visible edits) with an explanation of the Bidder’s need for each proposed change. Failure to include track changes with an explanation of the Bidder’s need for the proposed change constitutes the Bidder’s acceptance of the Contract Terms. General statements, such as that the Bidder reserves the right to negotiate the Contract Terms, may be considered non-responsive.

The State may, but is not required to, conduct an on-site visit to tour and inspect the Bidder's facilities, require an oral presentation of the Bidder's proposal, attend a proof of concept meeting, conduct interviews with Bidders, conduct system trial at MDOT facility using Bidder supplied computer and system suitable for MDOT testing, or request additional price concessions at any point during the evaluation process.

The State may deduct points or reject a proposal if the Bidder fails to demonstrate to the State’s satisfaction the viability or functionality of the goods or services at the proof of concept meeting, on-site visit tour, oral presentations, demonstrations, system trial, or during Bidder interviews.

8. NOTICE OF DEFICIENCY. The State reserves the right to issue a Notice of Deficiency to Bidders if the State determines after the proposal deadline that a portion of the RFP was deficient, unclear, or ambiguous. Failure to respond to a Notice of Deficiency timely may be cause for disqualification.

9. CLARIFICATION REQUEST. The State reserves the right to issue a Clarification Request to a Bidder to clarify its proposal if the State determines the proposal is not clear. Failure to respond to a Clarification Request timely may be cause for disqualification.

10. RESERVATIONS. The State reserves the right to:

a. Disqualify a Bidder for failure to follow these instructions.

b. Discontinue the RFP process at any time for any or no reason. The issuance of an RFP, your preparation and submission of a proposal, and the State’s subsequent receipt and evaluation of your proposal does not commit the State to award a contract to you or anyone, even if all the requirements in the RFP are met.

c. Consider late proposals if: (i) no other proposals are received; (ii) no complete proposals are received; (iii) the State received complete proposals, but the proposals did not meet mandatory minimum requirements or technical criteria; or (iv) the award process fails to result in an award.

d. Consider an otherwise disqualified proposal, if no other proposals are received.

e. Disqualify a proposal based on: (i) information provided by the Bidder in response to this RFP; (2) the Bidder’s failure to complete registration on www.michigan.gov/SIGMAVSS; or (3) if it is determined that a Bidder purposely or willfully submitted false or misleading information in response to the RFP.

f. Consider prior performance with the State in making its award decision.

g. Consider overall economic impact to the State when evaluating proposal pricing and in the final award recommendation. This includes but is not limited to considering principal place of performance, number of Michigan citizens employed or potentially employed, dollars paid to Michigan residents, Michigan capital investments, job creation, tax revenue implications, and economically disadvantaged businesses.

h. Consider total-cost-of-ownership factors (e.g., transition and training costs) when evaluating proposal pricing and in the final award recommendation.

i. Refuse to award a contract to any Bidder that has failed to pay State taxes or has outstanding debt with the State.

j. Enter into negotiations with one or more Bidders on price, terms, technical requirements, or other deliverables.

k. Award multiple, optional-use contracts, or award by Contract Activity.

l. Evaluate the proposal outside the scope identified in the Evaluation Process Section, if the State receives only one proposal.

11. AWARD RECOMMENDATION. The contract will be awarded to the responsive and responsible Bidder who offers the best value to the State, as determined by the State. Best value will be determined by the Bidder meeting the minimum point threshold and offering the best combination of the factors stated in the Evaluation Process Section, and price, as demonstrated by the proposal. The State will post a Notice of Recommendation for Award on www.michigan.gov/SIGMAVSS.

12. STATE ADMINISTRATIVE BOARD. Contracts in excess of $500,000 require approval by the State Administrative Board. The State Administrative Board’s decision is final; however, its approval does not constitute a contract. The award process is not complete until the awarded contractor receives a contract fully executed by all parties.

13. DEBRIEF MEETINGS AND PROTEST. The State will post a Notice of Recommendation for Award, which will provide instructions on how to request a debrief meeting.

If you wish to initiate a protest of the award, you must submit your written protest electronically at BidProtest-DTMB@michigan.gov no later than 3:00 p.m. Eastern, 5 business days after posting the Notice of Recommendation for Award on SIGMA VSS, or by 3:00 p.m. Eastern, the next business day if that date falls on a state holiday or weekend. The State reserves the right to adjust this timing and will publish any change on the SIGMA VSS system.

Additional information about the protest process is available at www.michigan.gov/micontractconnect under the “Programs and Policies” link.

14. GENERAL PROPOSAL CONDITIONS. The State will not be liable for any costs, expenses, or damages incurred by a Bidder participating in this solicitation. The Bidder agrees that its proposal will be considered an offer to do business with the State in accordance with its proposal, including the Contract Terms, and that its proposal will be irrevocable and binding for a period of 180 calendar days from date of submission. If a contract is awarded to the Bidder, the State may, at its option, incorporate any part of the Bidder’s proposal into a contract. This RFP is not an offer to enter into a contract. This RFP may not provide a complete statement of the State’s environment or contain all matters upon which agreement must be reached. Other than verified trade secrets, proposals submitted via www.michigan.gov/SIGMAVSS are the State’s property.

15. CONFIDENTIAL TREATMENT FORM AND THE FREEDOM OF INFORMATION ACT. All portions of the bidder’s proposal and resulting contract are subject to disclosure as required under Michigan’s Freedom of Information Act (FOIA), MCL 15.231, et seq. However, some information may be exempt from disclosure. Under MCL 18.1261(13)(b), records containing “a trade secret as defined under section 2 of the uniform trade secrets act, 1998 PA 448, MCL 445.1902,” are exempt from disclosure under FOIA. In addition, “financial or proprietary information” submitted with a bidder’s proposal is exempt from disclosure under FOIA. A bidder’s failure to comply with this Section is grounds for rejecting a bidder’s proposal as non-responsive. As a part of its proposal, each bidder must follow the procedure below.

A. SUBMIT A COMPLETED “CONFIDENTIAL TREATMENT FORM” (CT FORM) WITH YOUR BID. Completion and submission of the CT Form is required regardless of whether the bidder seeks confidential treatment of information. Failure to submit a completed CT Form may be cause for disqualification from the solicitation process.

(a) Complete and sign Section 1 of the CT Form if the bidder does NOT request confidential treatment of information contained in its proposal; or

(b) Complete and sign Section 2 of the CT Form if the bidder requests confidential treatment of certain information. Bidder must also submit a “Public Copy” of the proposal with the trade secret, financial, and proprietary information redacted and clearly labeled as the “Public Copy.”

B. FOIA REQUESTS. If a FOIA request is made for a bidder’s proposal, the Public Copy may be distributed to the public along with the bidder’s CT Form. The CT Form is a public document and serves as an explanation for the redactions to the Public Copy. Do not put any trade secret, financial, or proprietary information in the CT Form. Do not redact the CT Form itself.

C. NO ADVICE. The State will not advise a bidder as to the nature or content of documents entitled to protection from disclosure under FOIA or other laws, as to the interpretation of such laws, or as to the definition of trade secret or financial or proprietary information. Nothing contained in this provision will modify or amend requirements and obligations imposed on the State by FOIA or other applicable law.

D. FAILURE TO REQUEST CONFIDENTIAL TREATMENT. Failure to request material be treated as confidential as specified herein relieves the State, its agencies, and personnel from any responsibility for maintaining material in confidence.

E. Bids containing a request to maintain an entire proposal as confidential may be rejected as non-responsive. Bidders may not request confidential treatment with respect to resumes, pricing, and marketing materials. The State reserves the right to determine whether material designated as exempt by a bidder falls under MCL 18.1261 or other applicable FOIA exemptions. If a FOIA request is made for materials that the bidder has identified as trade secret, financial, or proprietary information, the State has the final authority to determine whether the materials are exempt from disclosure under FOIA.

F. Bidder forever releases the State, its departments, subdivisions, officers, and employees from all claims, rights, actions, demands, damages, liabilities, expenses and fees, which arise out of or relate to the disclosure of all or a portion of bidder’s proposal submitted under this RFP. Bidder must defend, indemnify and hold the State, its departments, subdivisions, officers, and employees harmless, without limitation, from and against all actions, claims, losses, liabilities, damages, costs, attorney fees, and expenses (including those required to establish the right to indemnification), arising out of or relating to any FOIA request, including potential litigation and appeals, related to the portion of bidder’s proposal submitted under this RFP that bidder has identified as a trade secret, or financial or proprietary information. The State will notify bidder in writing if indemnification is sought. The State is entitled to: (i) regular updates on proceeding status; (ii) participate in the defense of the proceeding; (iii) employ its own counsel; and to (iv) retain control of the defense, or any portion thereof, if the State deems necessary. Bidder will not, without the State’s written consent (not to be unreasonably withheld), settle, compromise, or consent to the entry of any judgment in or otherwise seek to terminate any claim, action, or proceeding. If a State employee, official, or law is involved or challenged, the State may control the defense of that portion of the claim. Any litigation activity on behalf of the State, or any of its subdivisions under this Section, must be coordinated with the Department of Attorney General. An attorney designated to represent the State may not do so until approved by the Michigan Attorney General and appointed as a Special Assistant Attorney General.

CONFIDENTIAL TREATMENT FORM (CT FORM)

INSTRUCTIONS. Complete either Section 1 or Section 2 of this CT Form and sign where indicated. This CT Form must be signed by the individual who signed the bidder’s proposal. A completed CT Form must be submitted with your proposal, regardless of whether your proposal contains confidential information. Failure to submit a completed CT Form with your bid is grounds for rejecting the proposal as non-responsive. See Section 16 of the Proposal Instructions for additional information.

Section 1. Confidential Treatment Is Not Requested

This section must be completed, signed, and submitted with the proposal if bidder does not request confidential treatment of any material contained in the proposal.

By signing below, the bidder affirms that confidential treatment of material contained in the proposal is not requested.

[Printed Name] [Title] [Company]

Section 2. Confidential Treatment Is Requested

The section must be completed, signed, and submitted with the proposal if bidder requests confidential treatment of any material contained in the proposal. Submission of a completed CT Form is required to request confidential treatment.

Provide the information in the table below. Bidder may add rows or additional pages using the same format shown in the table. Bidder must specifically identify the information to be protected as confidential and state the reasons why protection is necessary. The CT Form will not be considered fully complete unless, for each confidentiality request, the bidder: (1) identifies whether the material is a trade secret (TS), financial information (FI), or proprietary information (PI); (2) explains the specific legal grounds that support treatment of the material as TS, FI, or PI; and (3) provides the contact information for the person at bidder’s organization authorized to respond to inquiries by the State concerning the material. Bidders must not simply cite to an applicable act or case name; rather, bidders must provide a complete justification as to how the material falls within the scope of an applicable act or relevant case law.

STATE OF MICHIGAN

CONFIDENTIAL TREATMENT FORM (CT FORM)

By signing below, the bidder affirms that confidential treatment of material contained in its proposal is requested and has attached to this form a redacted “Public Copy” of the bidder’s proposal.

[Printed Name] [Title] [Company]

Central Signal Control System

EXHIBIT A

PROJECT SCOPE

This Exhibit identifies the anticipated requirements of any Contract resulting from this RFP.

The Bidder must respond to each Section, requirement or question, and explain how it will fulfill each requirement. Attach any supplemental information and appropriately reference within your response.

Contractor refers to a Bidder responding to this RFP. Contractor and Bidder are referred to interchangeably throughout these documents.

1. DEFINITIONS

The following terms have the meanings set forth below. All initial capitalized terms that are not defined below shall have the respective meanings given to them in Section 1 of the Contract Terms. “Solution” means the software (Commercial-Off-the-Shelf (COTS) or a Software as a Service (SaaS)) and Hardware (includes but is not limited to cellular modems) CU install, and Signalized Intersection Integration that the State is seeking under this RFP.

1. BACKGROUND

The Michigan Department of Transportation (MDOT) has identified the need to implement a central signal control system (CSCS) to provide the ability to remotely manage and monitor traffic signals and optimize operations and maintenance (O&M) procedures. MDOT recently developed a competitive controller unit (CU) specification based on the NEMA Advanced Transportation Controller (ATC) type to meet current operational and future connected vehicle needs. MDOT’s current NEMA ATC Special Provision (SP) allows for the use of the following two CUs, which provide functionality that meets or exceeds operational characteristics as described in NEMA TS-2-2016, including National Transportation Communications for ITS Protocol (NTCIP):

· Siemens m60 NEMA ATC loaded with Siemen’s SEPAC controller firmware version 5 over Linux using NTCIP communications.

· Econolite Cobalt NEMA ATC loaded with Econolite’s EOS controller firmware version 03.01.28 over NTCIP communications.

A critical element of the CSCS is to function seamlessly with both controllers. Therefore, the CSCS must be integrated with all the features of the two controllers/firmware listed in MDOT’s NEMA ATC SP. Integration must include all the base features available through NTCIP or other open protocols/data object definitions (e.g., NTCIP 1202 mandatory objects) as well as all vendor-specific features available through vendor-specific Management Information Bases (MIBs). All functionality that is available locally at the controller must also be available remotely through the Software.

Following Bidder selection and contract award, MDOT will provide and make available to the Bidder the MIBs of the two controllers listed above. The MIBs will be made available in industry standard electronic and Portable Document Format (PDF) formats to allow for custom integration into the CSCS software to provide all controller functionality via remote software application.

MDOT’s Traffic Signals Unit currently has remote monitoring and management capability to approximately 16% (500) of its nearly 3,200 traffic signals through a workstation using Siemens TACTICS software. Access to this workstation located in Lansing, Michigan will be made available to the selected Bidder to support the data migration and implementation of the CSCS.

Due to budget constraints, the CSCS deployment will be phased over several years. MDOT has obligated funding for Phase 1, which includes the CSCS deployment and integration of 280 traffic signal locations. Future phases are planned to occur following Phase 1, but funding has not been allocated, as identified in the below table. Therefore, this RFP is requesting costs for Phase 1 to be included in a base bid price. This RFP is also requesting costs for the future expansion that may be authorized as funding becomes available. See Exhibit C – Pricing. Pricing for future expansion items will be valid for the duration of this contract, and MDOT is under no obligation to authorize any of the future expansion items.

Approximately 1,498 MDOT owned and local agency operated and maintained signals Dependent on future funding and local agency participation

This RFP defines the services, hardware, software, and integration for the CSCS. MDOT will procure traffic signal CUs for the Bidder to configure, install, and integrate. This RFP will procure the following items as defined herein:

· Traffic signal controller unit (CU) setup, testing and installation (CU provided by MDOT)

· Center to field communications equipment, setup, installation, and testing (cellular modem)

· CSCS software installation and testing

· Signalized intersection implementation in CSCS

· Software warranty, support, maintenance, and troubleshooting

Phase 1 intersection locations are provided in Exhibit G – Phase 1 Intersections. All signals within an identified common group must be deployed together to avoid negatively impacting traffic operations. Exhibit G – Phase 1 Intersections identifies the 16 signals (5%) that must be prioritized as the first deployment group.

1. PURPOSE

The State is seeking either externally hosted or on-premise Software as part of the Solution. Bidder may provide proposals for COTS (externally hosted or on-premise) or SaaS (collectively, “Software”). Bidder may provide a proposal with COTS and SaaS if both options can be provided by the Bidder. If locally hosted at a State of Michigan facility the hardware (severs, firewalls, switches) will be purchased by the State of Michigan per requirements provided by the Bidder. SaaS

As roadway technology continues to advance at an unprecedented pace, MDOT’s traffic signal system requires an investment to overhaul the aging signal system and prepare for the future of traffic signal management. The ability to remotely manage and control traffic signals is the nucleus to provide the enhanced capabilities to optimize traffic signal operations, improve safety, provide quick and effective responses to disruptive incidents, reduce system maintenance costs, and prepare for future traffic management (i.e. performance metrics, connected vehicles, and adaptive traffic signal timings). MDOT has established the following goals for the CSCS:

· Increase the efficiency of Michigan’s roadways

· Provide active and remote traffic signal monitoring

· Improve safety, enhance reliability, and reduce congestion

· Streamline the management of a critical asset

· DOT staff responsibilities

· Arterial performance

· Prepare for the future of traffic signal management

· Provide interoperability with controller specification

· Adaptive timings, signal priority, multi-modal

· Active traffic management and integrated corridor management

· Provide structure for future connected vehicle operations

· Bring MDOT up to a level of service and functionality compared to peer states

3. Legacy Controller Firmware Compatibility The Solution must provide full remote, functionality with the 280 Phase 1 CUs loaded with Siemens and Econolite ATC firmwares listed in the Background and as described Exhibit A – Table 1 – Business Specification Worksheet. In addition, the Bidder must describe their Solution's compatibility/functionality with legacy equipment in the following table:

M60/SEPAC v5

M50/SEPAC v4

M50/SEPAC v3

1. CONTRACT TERM

The contract overall term is expected to be 5 years with 5, 1-year options

1. SPECIFIC STANDARDS

IT Policies, Standards and Procedures (PSP) Bidders are advised that the State has methods, policies, standards and procedures that have been developed over the years. Contractors are expected to provide proposals that conform to State IT policies and standards. All services and products provided as a result of this RFP must comply with all applicable State IT policies and standards. Contractor is required to review all applicable links provided below and state compliance in their response.

Public IT Policies, Standards and Procedures (PSP):

https://www.michigan.gov/dtmb/0,5552,7-358-82547_56579_56755---,00.html

Note: Not all applicable PSP's are available publicly. Controlled PSP's applicable to the RFP are available after signing and returning to the State the required Nondisclosure Agreement (NDA) agreement. Failure to return a signed NDA may be grounds for disqualification.

Acceptable Use Policy To the extent that Contractor has access to the State’s computer system, Contractor must comply with the State’s Acceptable Use Policy, see https://www.michigan.gov/documents/dtmb/1340.00.01_Acceptable_Use_of_Information_Technology_Standard_458958_7.pdf. All Contractor Personnel will be required, in writing, to agree to the State’s Acceptable Use Policy before accessing the State’s system. The State reserves the right to terminate Contractor’s access to the State’s system if a violation occurs.

Mobile Responsiveness It is preferred that the Bidder’s Solution utilize responsive design practices to ensure the application is accessible via a mobile device. Bidders must provide a list of all mobile devices that are compatible with the Solution. Additionally, Bidder must provide list of features that can be performed via a mobile device.

ADA Compliance The State is required to comply with the Americans with Disabilities Act of 1990 (ADA), and has adopted a formal policy regarding accessibility requirements for websites and software applications. The State is requiring that Bidder’s proposed Solution, where relevant, to level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.0. Bidder may consider, where relevant, the W3C’s Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) for non-web software and content. The State may require that Bidder complete a Voluntary Product Accessibility Template for WCAG 2.0 (WCAG 2.0 VPAT) or other comparable document for the proposed Solution. http://www.michigan.gov/documents/dmb/1650.00_209567_7.pdf?20151026134621

Bidder must acknowledge their agreement with this section and provide details for how they will meet the requirements.

1. USER TYPE AND CAPACITY

Bidder must be able to meet the expected number of concurrent Users. Bidder must explain how it will be able to support the expected number of concurrent Users. Bidder must also explain whether the Solution can scale up or down without affecting performance.

Bidder must meet the total expected number of signals in Phase 1 Bidder must be able to scale up or down to accommodate future phases and maximum capacity without affecting performance. Bidder must explain how the Solution can scale up to or down without affecting performance.

Bidder must provide details regarding latency response time for (i.e., Generate Page Load, standardized reporting, ad hoc reporting). The Bidder must identify what network connectivity or equipment the State must have to meet the expected latency response time.

1. ACCESS CONTROL AND AUDIT

The Bidder’s Solution must integrate with the State’s IT Identity and Access Management (IAM) environment as described in the State of Michigan Digital Strategy (http://www.michigan.gov/dtmb/0,5552,7-150-56345_56351_69611-336646--,00.html), which consist of:

1. MILogin/Michigan Identity, Credential, and Access Management (MICAM)

a. An enterprise single sign-on and identity management solution based on IBM’s Identity and Access Management products including, IBM Security Identity Manager (ISIM), IBM Security Access Manager for Web (ISAM), IBM Tivoli Federated Identity Manager (TFIM), IBM Security Access Manager for Mobile (ISAMM), and IBM DataPower, which enables the State to establish, manage, and authenticate user identities for the State’s Information Technology (IT) systems.

2. MILogin Identity Federation

a. Allows federated single sign-on (SSO) for business partners, as well as citizen-based applications.

3. MILogin Multi Factor Authentication (MFA, based on system data classification requirements)

a. Required for those applications where data classification is Confidential and Restricted as defined by the 1340.00 Michigan Information Technology Information Security standard (i.e. the proposed Solution must comply with PHI, PCI, CJIS, IRS, and other standards).

4. MILogin Identity Proofing Services (based on system data classification requirements)

a. A system that verifies individual’s identities before the State allows access to its IT system. This service is based on “life history” or transaction information aggregated from public and proprietary data sources. A leading credit bureau provides this service.

To integrate with the SOM MILogin solution, the Bidder’s Solution must support HTTP Headers based SSO, or SAML, or OAuth or OpenID interfaces for the SSO purposes.

The Solution must support Federal Information Processing Standards (FIPS)/National Institute of Standards and Technology (NIST) compliant multi-factor authentication for privileged/administrative or other identified access.

1. DATA RETENTION

The Bidder must explain how the Solution will collect and archive data elements such as historic and current traffic timing parameters, system events, alerts, user activity, and high-resolution and/or detector data.

1. SECURITY

The Bidder must provide a description of the Solution's approach to providing security functionality.

Externally Hosted The Solution will be storing sensitive data.

Bidder must review the Data Security requirements set forth in Schedule F – Data Security Requirements to the Contract Terms. Bidder must note any exceptions to the security requirements by redlining Schedule F – Data Security Requirements.

Bidder must describe how it will comply with the following and provide supporting evidence as part of their proposal:

· Must provide a GovCloud Solution that is hosted in a FedRAMP authorized facility and maintain an annual SSAE 16 SOC 2 Type 2 audit based on NIST SP 800-53 moderate controls.

· Must be encrypted in transit and at rest using FIPS certified modules with AES 128 bit or higher encryption.

· Must have FIPS/NIST compliant multi-factor authentication for privileged/administrative access or other identified access.

· Must remain compliant with The Federal Information Security Modernization Act of 2014 (FISMA) and the NIST Special Publication 800-53 (most recent version) MOD controls using minimum control values as established in the applicable SOM PSP’s.

On-Premise Bidder is responsible for establishing and maintaining a data privacy and information security program, including physical, technical, administrative, and organizational safeguards, that is designed to: (a) ensure the security and confidentiality of the State Data; (b) protect against any anticipated threats or hazards to the security or integrity of the State Data; (c) protect against unauthorized disclosure, access to, or use of the State Data; (d) ensure the proper disposal of State Data; and (e) ensure that all Contractor personnel comply with all of the foregoing. In no case will the safeguards of Contractor’s data privacy and information security program be less stringent than the safeguards used by the State, and Contractor must at all times comply with all applicable State IT policies and standards, of which publicly available ones are located at http://www.michigan.gov/dtmb/0,4568,7-150-56355_56579_56755---,00.html.

Bidder must acknowledge their agreement with this section and provide details for how they will meet the requirements.

1. END USER OPERATING ENVIRONMENT

The SOM hosting environment is X86 VMware, IBM Power VM and Oracle VM, with supporting enterprise storage monitoring and management.

If the Solution includes a web browser-based application, the software must run under commonly used web browsers. At a minimum the software must support Internet Explorer v9 or higher, Chrome v36 or higher, Firefox v31 or higher, and Safari v5.1 or higher both under the Windows and iOS operating systems.

If the Solution includes a stand-alone, desktop application, the software must run under the most recent Windows operating system and be backward compatible to at least Windows 7.

Solution must support remote access through secure communications connection, such as VPN.

Bidder must support the current and future State standard environments at no additional cost to the State.

Bidder must:

· Describe the optimal technical environment based on the environment choices set forth above.

· Describe any State system access requirements that are necessary for the Bidder to perform its obligations on a timely basis, including but not limited to, physical or remote access to State networks, servers, or individual workstations.

· Describe if it can comply with the current environment and how it intends to comply with any future changes to the user environment. And if not, describe what end user operating environment its Solution supports.

· Describe if it can support the original environment throughout the term of the contract.

· Describe how it communicates changes to its roadmaps.

· Identify any plug-ins necessary for the proposed Solution to meet the system requirements of this request.

· Describe how customers collaborate with your organization in the decision-making process for upgrades, maintenance, and change control.

1. SOFTWARE

Bidder must provide a detailed description of the Software to be provided under the resulting Contract including, but not limited to, a detailed description of the proposed Software (name, type, version, release number, etc.), its functionality, optional add-on modules, Contractor’s services and the Software’s ability to be rapidly configured or scaled as the State’s business or technical demands change. If Bidder is using any open source or third-party products in connection with the proposed Software, the Bidder must identify these separately in its proposal (including identifying any associated cost in Exhibit C - Pricing).

Bidder must describe the approach and Solution ability to seamlessly function with the two controllers listed in Section 2 of this exhibit which includes providing remote access to all controller features. Bidder is encouraged to provide project examples of other successful deployments integrating vendor-specific controller features through vendor-specific MIBs.

Bidder must include a License Agreement for the Software, and label as Schedule C – License Agreement in its bid proposal. Bidder should refer to Exhibit C – Pricing with respect to proposing a perpetual license versus term-based license. The License Agreement should only include licensing terms and should not include any terms that conflict with the Contract Terms (e.g. payment terms). Bidder’s License Agreement should include full use of the Software by the State’s Authorized Users, and there should not be any separate end-user license agreement required or included with Bidder’s proposal.

For third-party products that are being proposed as part of the overall Solution, Bidder must include any end-user license agreements that will be required to access and use such products.

12. HARDWARE

Bidder must provide a detailed description of the proposed Hardware to be provided under the resulting Contract including, but not limited to, a detailed description of the cellular modem that will be used to establish communications from CU and the Solution managed field ethernet switch (may be authorized at a future date), and any other Hardware provided to operate the Solution. Contractor’s services and the Hardware ability to be configured and deployed must meet the State’s requirements.

1. SOLUTION REQUIREMENTS

Bidder must fully answer each section in this Exhibit A - Project Scope and complete the attached Exhibit A - Table 1 Business Specification Worksheet.

Bidder must explain the proposed approach to validate each requirement to ensure that the Solution meets the specifications set forth in this RFP.

Bidder must detail any configuration changes or customization modifications that will need to be made to the Solution to meet the specifications set forth in Exhibit A - Table 1 Business Specification Worksheet and where applicable in each section of this RFP.

Configuration is referred to as a change to the Solution that must be completed by the awarded Bidder 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 modifications occurring).

Customization is referred to a modification to the Software’s underlying source code, which can be completed as part of the initial implementation.

All configurations or customizations made during the term of the awarded contract must be forward-compatible with future releases and be fully supported by the awarded Bidder without additional costs.

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

1. INTEGRATION

The Solution must be integrated with controller units (CU) installed in the field via remote communications connection provided by cellular modems. Contractor is responsible to program, configure, test and install MDOT-furnished CU’s and integrate the corresponding intersection in the Software as defined in Exhibit D – CU Requirements. Contractor is responsible to furnish, configure, install, integrate, and test cellular modems as defined in Exhibit E – Cellular Modem Requirements.

1. MIGRATION

Bidder must review the Migration Data Sample the State has provided and explain how the Bidder will migrate the data. Data migration includes programming MDOT-furnished CU with existing intersection timing parameters to provide the required traffic signal control operation in accordance with the Michigan Manual on Uniform Traffic Control Devices (MMUTCD). MDOT will provide the existing signal timing parameters in pdf format. The Bidder may collect electronic versions of databases from in-service CU in the field at no additional cost to MDOT (see Exhibit D – CU Requirements for traffic signal cabinet access restrictions). The Bidder is responsible for any labor and equipment required for programming the new CU.

1. TESTING SERVICES AND ACCEPTANCE

Bidder must review Section 12. Pre-Delivery Testing and Section 13. Acceptance Testing- and the Schedules referenced in Section 13, of the Contract Terms.

Bidder must review Schedule H – Acceptance Testing which includes System Acceptance and Testing requirements (i.e. Acceptance Test Plan, Confirmation Testing, Local Device Assembly Test, Final System Test, Burn-in Test).

17. IMPLEMENTATION

Bidder must include a high-level…