Procurement Services & Supply Chain

---

Procurement Services & Supply Chain REQUEST FOR PROPOSALS For

THE CURATORS OF THE UNIVERSITY OF MISSOURI At UNIVERSITY OF MISSOURI - ST. LOUIS

Managerial and Technological Services Department of Information Technology Services (ITS) Requesting The furnish; delivery; installation; continued maintenance, service, support, training, and compliance with University of Missouri System and UMSL Information Technology Services Policies and Procedures for a Computer Aided Dispatch and Record Management System in the University of Missouri – St. Louis Police Department. RFP # 14-3014-AL-S OPENING DATE: April 30, 2014 TIME: 10:00 AM, CT Prepared by: Digitally signed by Amanda M. La Brier DN: cn=Amanda M. La Brier, o=University of Missouri - System, ou=Procurement Services/Supply Chain, [email protected], c=US Date: 2014.03.19 11:52:34 -05'00'

Amanda M. La Brier Strategic Sourcing Specialist University of Missouri System Supply Chain & Procurement Services One University Boulevard 209 Woods Hall St. Louis, MO 63121

Dated: March 18, 2013 University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 0

Section 1 NOTICE TO RESPONDENTS The University of Missouri Procurement Services requests proposals for providing University, RFP #14-3014AL-S, which will be received by the undersigned at the University of Missouri Procurement Services, One University Boulevard – 209 Woods Hall, St. Louis, Missouri 63121 until 10:00 a.m., CT, Wednesday, April 30, 2014. Proposals will be opened and identified beginning at 10:05 p.m., CT. Specifications and the conditions of proposal together with the printed form on which proposals must be made may be obtained from Amanda M. La Brier, Strategic Sourcing Specialist, One University Boulevard – 209 Woods Hall, St. Louis, Missouri 63121. (314) 516-5368 [email protected]. The University reserves the right to waive any informality in proposals and to reject any or all proposals.

E-MAIL OR FAXED PROPOSAL RESPONSES WILL NOT BE CONSIDERED.

THE CURATORS OF THE UNIVERSITY OF MISSOURI Digitally signed by Amanda M. La Brier DN: cn=Amanda M. La Brier, o=University of Missouri - System, ou=Procurement Services/Supply Chain, [email protected], c=US Date: 2014.03.19 11:52:59 -05'00'

Amanda M. La Brier Strategic Sourcing Specialist University of Missouri System Procurement Services & Supply Chain One University Boulevard 209 Woods Hall St. Louis, MO 63121

Dated: March 18, 2013 University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 1

Section 2 UNIVERSITY OF MISSOURI GENERAL TERMS AND CONDITIONS Instructions to Respondents Request for Proposal A

Furnish and Deliver Delivery must be within the time lines noted after receipt of order and must be F.O.B. St. Louis, MO (domestic) / D.D.P. St. Louis, MO (International).

B.

Payment All bids are to be submitted on the basis of payment by University check, terms Net 30. Payment shall be made within thirty (30) days after receipt of item, acceptance of item, and receipt of invoice, rendered in duplicate to the address listed on the purchase order. Acceptance of items will be upon verification that all items provided meet or exceed the specification of this bid. The University may withhold payment or make deductions as may be necessary to protect the University from loss or damage on account of defective work, claims, damages, or to pay for repair or correction of products/services furnished hereunder. Any different payment terms desired by bidder must be clearly stated and may or may not be accepted by the University. A payment schedule may be negotiated with the successful bidder. If prepayment is required, the Successful Bidder may be required to provide a performance bond or irrevocable letter of credit at no cost to the University for the full amount of prepayment. Any invoicing for under-billing errors which are submitted more than 30 calendar days after the University of Missouri closes funds for any fiscal year (June 30) will not be accepted, paid, or recognized.

C.

Price Prices listed on Bid Form must be all inclusive, including but not limited to, shipping and delivery. Delivery is to be F.O.B. St. Louis, Missouri if shipped from within the United States. If items are imported, delivery is to be D.D.P. Saint Louis, MO and the price is to include all costs, including but not limited to customs, duties, taxes, costs for carriage and transshipment, and delivery to St. Louis, MO. Bidder is responsible for all risks and costs and providing all documentation as required for importing. Contact information for a customs broker accustomed to working with the university is available upon request. Bidder is responsible for any / all costs of customs broker.

Compliance Checklist Meet or Exceed

Does Not Meet

Price Adjustment Pricing for the first year of the contract will remain firm and fixed. If there are escalation costs of doing business then the awarded bidder must provide a written explanation requesting an increase in prices and the University must agree to acceptance of increase.

D.

Bidder Qualifications Bidder must include documentation to show specifications listed below are met or exceeded by brand/model bid. Bid responses received without documentation MAY BE REJECTED. The university may make such reasonable investigations as deemed proper and necessary to determine the ability of the bidder to furnish and deliver the product as described in these specifications, and the Bidder shall furnish to the University all such information and data for this purpose as may be requested. The University further reserves the right to reject any bid if the references and other evidence submitted by, or investigations of, such bidder fails to satisfy the University that such bidder is properly qualified to carry out the obligations of the contract and complete the work contemplated therein. The Bidder shall obtain and maintain in full force and effect all required licenses, permits and authorizations necessary to furnish, delver, and perform services for the University of Missouri – St. Louis. The Bidder shall supply University of MO-St. Louis with evidence of all such licenses, permits and authorizations where applicable. This evidence shall be submitted subsequent to the contract award. All costs associated with any such licenses, permits and authorizations shall have been included by the Contractor in this bid.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 2

E.

Insurance Coverage Successful Bidder must provide a certificate of insurance meeting the University’s requirements as listed below. Coverage to be provided as follows by a carrier with A.M. Best minimum rating of A – XI. Certificate must include NAIC number for each insurer. Coverage: Minimum Limits Insurance (low risk) Contractor agrees to maintain, on a primary basis and at its sole expense, at all times during the life of any resulting contract the following insurance coverages, limits, including endorsements described herein. The requirements contained herein, as well as the University’s review or acceptance of insurance maintained by Contractor is not intended to and shall not in any manner limit or qualify the liabilities or obligations assumed by Contractor under any resulting contract. Coverage to be provided as follows by a carrier with A.M. Best minimum rating of A- VIII. Commercial General Liability Contractor agrees to maintain Commercial General Liability at a limit of not less than $1,000,000 Each Occurrence, $3,000,000 Annual Aggregate. Coverage shall not contain any endorsement(s) excluding nor limiting Product/Completed Operations, Contractual Liability or Cross Liability. Contractor may satisfy the minimum liability limits required for Commercial General Liability or Business Auto Liability under an Umbrella or Excess Liability policy. There is no minimum per occurrence limit of liability under the Umbrella or Excess Liability; however, the Annual Aggregate limit shall not be less than the highest “Each Occurrence” limit for either Commercial General Liability or Business Auto Liability. Contractor agrees to endorse the University as an Additional Insured on the Umbrella or Excess Liability, unless the Certificate of Insurance state the Umbrella or Excess Liability provides coverage on a “Follow-Form” basis. Note: Anyone who serves alcoholic beverages on a University of Missouri Campus must also provide liquor liability coverage. This should be written on an "occurrence basis" and have limits not less than $1,000,000 each claim or each common cause and at least a $1,000,000 aggregate. The insurance carrier, policy number, effective date and limits should be shown on an insurance certificate provided to the University of Missouri. The Curators of the University of Missouri should be named as an Additional Insured on such policy and a copy of the endorsement should be provided along with the certificate of insurance. Business Auto Liability Contractor agrees to maintain Business Automobile Liability at a limit not less than $1,000,000 Each Occurrence. Coverage shall include liability for Owned, Non-Owned & Hired automobiles. In the event Contractor does not own automobiles, Contractor agrees to maintain coverage for Hired & Non-Owned Auto Liability, which may be satisfied by way of endorsement to Workers’ Compensation & Employers Liability Contractor agrees to maintain Workers’ Compensation in accordance with Missouri State Statutes or provide evidence of monopolistic state coverage. Employers Liability with the following limits: $500,000 each accident, disease each employee and disease policy limit. Contract Language The Curators of the University of Missouri, its officers, employees and agents are to be Additional Insured with respect to the project to which these insurance requirements pertain. A certificate of insurance evidencing all coverage required is to be provided at least 10 days prior to the inception date of the contract between the contractor and the University. Contractor/Party is required to maintain coverages as stated and required to notify the University of a Carrier Change or cancellation within 2 business days. The University reserves the right to request a copy of the policy. The University reserves the right to require higher limits on any contract provided notice of such requirement is stated in the request for proposals for such contract. Indemnification The Contractor agrees to defend, indemnify, and save harmless The Curators of the University of Missouri, their Officers, Agents, Employees and Volunteers, from and against all loss or expense

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 3

from any cause of action arising from the Contractor’s operations. The contractor agrees to investigate, handle, respond to and provide defense for and defend against any such liability, claims, and demands at the sole expense of the Contractor or at the option of the University, agrees to pay to or reimburse the University for the Defense Costs incurred by the University in connection with any such liability claims, or demands. The parties hereto understand and agree that the University is relying on, and does not waive or intend to waive by any provision of this Contract, any monetary limitations or any other rights, immunities, and protections provided by the State of Missouri, as from time to time amended, or otherwise available to the University, or its officers, employees, agents or volunteers. Failure to maintain the required insurance in force may be cause for contract termination. In the event the Agency/Service fails to maintain and keep in force the required insurance or to obtain coverage from its subcontractors, the University shall have the right to cancel and terminate the contract without notice.

F.

G.

The insurance required by the provisions of this article is required in the public interest and the University does not assume and liability for acts of the Agency/Service and/or their employees and/or their subcontractors in the performance of this contract. If Bidder has additional terms and condition which must be considered, a copy of the additional terms and conditions must be included with bid response. The terms and conditions must not be in conflict with any terms and conditions or specifications as listed in this request for bids. The request for bids is the controlling agreement with any additional terms submitted being supplementary. Terms submitted will be reviewed by the University’s General Counsel. Both parties must reach agreement on terms and conditions prior to award of a contract. If both parties cannot reach mutual agreement upon terms and conditions, the response may be rejected and the award made to the next low bidder. Working Conditions and Use of Premises The Contractor shall carry out his work in a manner that will not interfere with the normal activities at the site. Contractor's operation, including storage of materials, shall be confined to areas designated by the University's representative. The University will not assume any financial responsibility for materials or equipment stored on job site. The University will provide parking for contractor's service vehicle(s) by temporary permit. Contractor and his employees in other vehicles will be required to compete with the general public for parking space convenient to the work site. All work is to be performed during regular working hours (Monday through Friday, excluding University holidays, 8:00 A.M. - 5:00 P.M.) unless otherwise specified or special permission is granted. The Contractor shall abide by the University's regulations and the University's instructions regarding signs, advertisement, fires, etc., and shall be responsible for repair of damages to buildings and surroundings caused by his employees during work progress. The Contractor is responsible for complete clean-up of all trash and debris

H.

Compliance with Codes Contractor shall execute the work in strict accordance with these specifications and the laws of the State of Missouri. Contractor shall comply with all applicable national and local ordinances or codes excepted as noted.

I.

Examination of Sites Bidders shall personally inspect site of proposed work to fully acquaint themselves with the conditions under which this work is to be performed. No extra compensation will be allowed for anything or matter relating to these conditions of which bidder should have fully informed himself prior to bidding. Such failure to fully inform himself shall not relieve bidder from his obligations with respect to this bid and contract. University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 4

J.

Inspection by University Personnel The University may from time to time make unscheduled inspections of the site. Any deviation from the bid specifications will be called to the Contractor's attention. In the event corrective action or agreement to take corrective action is not forthcoming, the University shall, through the Manager of Campus Procurement Center, notify the Contractor to cease work or the University shall withhold payment until corrective work has been performed.

K.

Workmanship All workmanship shall be first class in all respects, and shall meet the approval of the University's representative. All material and equipment shall be first class as to quality and type designated in these specifications. The work shall be done by skilled tradesmen in the various required crafts. Such tradesmen shall be employed by a firm licensed by the State or Municipality, to perform the specific type work as specified.

L.

Wage Rates The successful bidder will pay workmen wage rates and fringe payments of not less than the prevailing wage rates and fringe payment for workmen preforming work of similar character in the community where construction under the bid takes place, see attachment with prevailing wage rate for St. Louis County, MO.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 5

Section 3 ADDITIONAL INFORMATION A. Website Information http://www.umsystem.edu/apps/fa/procurement/bids/listview_Bids.php

It will be the potential respondent’s responsibility to print out a copy of the specifications found at the above web address and return them in hard copy form as a sealed bid. Proposals are to be submitted in a sealed envelope addressed to Amanda M. La Brier University of Missouri Procurement Services at the above below, and clearly marked in the lower left corner of the envelope, “RFB 14-3014-AL-S” UMSL PD CAD. B. Questions All questions regarding this proposal should be emailed to Amanda M. La Brier at [email protected] at (314) 516-5368. Questions in writing must be submitted to: Amanda M. La Brier University of Missouri Procurement Services & Supply Chain One University Blvd 209 Woods Hall St. Louis, MO 63121

Questions will be addressed until April 18, 2014, 10:00 a.m., CDT. Proposals shall NOT be submitted by fax or email.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 6

Section 4 DETAILED SPECIFICATIONS AND SPECIAL CONDITIONS Request for Proposal: University of Missouri – St. Louis Information Technology Services (ITS) UMSL Police Department (PD) Computer Aided Dispatch/ Record Management System (CAD/RMS) to be: Furnished, delivered, installed, UMSL personnel trained, continually maintained, serviced, supported, and in compliance with University of Missouri System and UMSL Information Technology Policies and Procedures A: INTRODUCTION INFORMATION TECHNOLOGY SERVICES OF UNIVERSITY OF MISSOURI – ST. LOUIS (UMSL) Potential respondents interested in submitting proposals are encouraged to participate in a pre-proposal conference call on Wednesday, March 26, 2014 at 3:00 PM Central Time. The conference call is schedule to last no longer than ninety (90) minutes, and most likely will be shorter. To participate in the conference call, interested parties must call University of Missouri Procurement Services at (314) 516-5368 or by email at [email protected] no later than March 21, 2014 at 3:00 pm to register and to be provided the phone number and conference number. All parties should dial into the conference call as close to the conference time as possible. If participants dialing the toll free number receive a fast busy number signal, the participant should hang up and try again. All participants must clearly state their name, company, phone and fax number or email address when being added to the conference call. This information will be used to send out the meeting notes. Each respondent (company) is requested to place only one (1) call to the conference call number. Multiple representatives may participate either through conference calling within your company before calling the number listed above or by utilizing a speaker phone. This will allow all interested parties the opportunity to participate. Should a participant not be able to connect to the conference call, please call (314) 516-5368 no later than 1:35 pm Central Time to notify University of Missouri Procurement Services of the problem. The pre-proposal conference call will give potential respondents the opportunity to ask questions about the specifications listed within this request for proposals. Potential respondents are encouraged to participate in the pre-proposal conference call but are not required to participate. However, any respondent selected for award of the contract will be required to fulfill the terms of the contract whether or not a representative of their company participated in the pre-proposal conference call. By submitting a response, the respondent agrees that the organization submitting the response fully understands all the required obligations and the scope of the work, and that the organization will not make any claim for cancellation or relief. Notes taken during the pre-proposal conference call will be sent via fax or email to all parties notified by University of Missouri Procurement Services of the Request for Proposals or who participated in the preproposal conference call and for whom University of Missouri – Columbia Campus Procurement has contact information. A copy of these notes will also be available on-line at http://www.umsystem.edu/apps/fa/procurement/bids/listview_Bids.php or by request to (314) 516-5368. The University will attempt to provide a complete review of information discussed during the pre-proposal conference call. However, it is the respondent’s responsibility to make themselves fully aware of the expectation and the conditions under which the work is to be done and these notes do not relieve the respondent of that responsibility. University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 7

The Pre-Proposal Conference Call notes and any subsequent addenda are to be considered the documents of record. Should there be a conflict between a discussion at the Pre-Proposal Conference Call and the written notes or addenda, the written document will prevail. BACKGROUND The University of Missouri – St. Louis (UMSL) seeks an interested firm to furnish, deliver, install, train UMSL ITS and PD personnel, as well as provide maintenance, service, and support a Computer Aided Dispatch (CAD) and Record Management System (RMS) for the UMSL PD that complies with University of Missouri System ITS Policies and Procedures as well as federal collection and reporting mandates to the Clery Act and Title IX as affected by the Violence Against Women Act. The system will serve and support approximately 17,000 UMSL students and 2,500 UMSL faculty and staff on campus, as well as alumni and guests visiting campus and the surrounding community. Competitive proposals will demonstrate previous successes in: • Implementing best practices in CAD/RMS System supply; delivery; installation; training; continued maintenance, service and support in Public University environments. • Management of CAD/RMS Systems in Public University environments. • Identifying operational efficiencies and cost savings. UMSL ITS is requesting qualified respondents to submit proposals to furnish; deliver; install; train UMSL personnel; as well as maintain, service and support a Computer Aided Dispatch (CAD) and Record Management System (RMS) for a contract period to be determined in compliance with University of Missouri System and UMSL ITS policies and procedures. Following RFP award and contract execution anticipated project start date is scheduled for May 31, 2014. ABOUT UMSL: Founded in 1965, University of Missouri – St. Louis (UMSL) is the first public institution of higher education west of the Mississippi River. UMSL is a land grant research university located in St. Louis, Missouri, and a part of the largest University system in the State. UMSL enrolls approximately 17,000 students, and employees over 500 full-time and 1000 part time faculty. Proudly, UMSL employs and is served by over a 1000 full and part-time dedicated staff members. For more information about the University of Missouri – St. Louis campus please visit the website online at http://www.umsl.edu/. UMSL Police Department (PD) was established in 1964, and is a Division of UMSL Institutional Safety. Campus Police is located at One University Boulevard, 44 Campus Police Building, St. Louis, MO 63121-4400. The Campus Police building is adjacent to the North Campus MetroLink stop. The UMSL PD works closely with the campus community, to ensure that UMSL is a safe and pleasant place where people can live, work, and pursue their educational endeavors. UMSL Chief of Police, 24 Commissioned Officers, 4 Dispatchers and departmental staff preserve the peace; maintain order; and expel those persons who violate the rules and regulations prescribed by the Board of Curators of the University of Missouri from UMSL campus buildings and grounds. University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 8

For more information about UMSL PD please visit the department website online at http://safety.umsl.edu/police/.

UMSL Information Technology Services (ITS) is located at One University Boulevard, 451 Express Scripts Hall St. Louis, MO 63121-4400. UMSL ITS provide a wide array of technological services to support teaching, learning, research and administration for students, faculty, and staff at UMSL. UMSL ITS’s 80 staff members, provide services including: voice, video, Internet, and all computing services as well as consultation, programming, training, and operational support. The Priority of UMSL ITS and staff is to ensure that the technical infrastructure works for campus stakeholders. The myriad electronic and mechanical components: wires, optical fiber, switches, connections, servers, operating software, management systems, desktop computers, application software, databases, and other pieces that comprise a modern information infrastructure must work – reliably and cost-effectively. Most important role of ITS at UMSL is to ensure support of technology for learning that assists faculty and students in achieving success. For more Information about UMSL ITS please visit the department website online at http://www.umsl.edu/technology/.

PROJECT DESCRIPTION: UMSL seeks a partner that is able to demonstrate substantial experience in furnishing, delivering, installing, training University personnel, as well as maintaining, servicing and supporting a CAD/RMS System for a public University Police Department that meets public University information technology security processes and procedures. The partner must provide a product that is compatible with current University of Missouri System and UMSL ITS hardware and software, while proposing the best financial arrangement that allows the UMSL to continue to meet budget and quality standards for all of its stakeholders. The proximity to the University of Missouri – St. Louis establishes a significant relationship between UMSL ITS and UMSL PD, and will contribute to the success of this project. The proposed furnish, delivery, install, UMSL personnel training, along with continued maintenance service and support of UMSL PD CAD/RMS will consist of, but not limited to the following: The proposed system will include: • Applicable hardware. • Applicable software. • Continued Maintenance, Service and Support. • Coordinated management with UMSL ITS and PD. • University Staff Training for CAD use. This software will be designed to meet, at a minimum, industry standards.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 9

B: SUBMITTING AN RFP RESPONSE Requirements and Scope The University’s goal is to collaborate with a provider with proven success in CAD/RMS technology that will support its mission and become a partner in developing its product to their maximum potential. It is in the University’s best interest to solicit technology firms that will be able to help build and maintain a high quality service and program that will be operated in a customer focused and financially responsible manner. 1.

Scope and Specifications – UMSL PD CAD/RMS System The scope of work shall include all or part of the following services. Prior to awarding a contract for these services, UMSL reserves the right to modify this scope of work in order to adequately address their needs. The respondent understands that UMSL PD CAD/RMS System shall be furnished, delivered, installed, maintained, serviced and supported and UMSL staff trained on the system for the use and benefit of University of Missouri-St. Louis students, faculty, staff, alumni and guests. The University expects the utmost in professional associations with their contractors. We strive to work together in a harmonious relationship that will result in benefits for the University and Respondent. UMSL is seeking a firm with experience in Computer Aided Dispatch (CAD) and Record Management System (RMS) and software to enter into a five (5) year contracted service agreement to furnish, deliver, install, implement, train UMSL personnel, maintain, service, and support the University CAD/RMS system and software. UMSL is requesting qualified Respondents to submit proposals to furnish, deliver, install, implement, train UMSL personnel, maintain, service, and support a University CAD/RMS system based on the following requirements and evaluation criteria including, but not limited to:

2. Evaluation Criteria From the total information requested below, award shall be made as to the best value to the University. Evaluation of each proposal shall be made based on the following criteria, listed in relative order of importance: • Limiting Criteria • Proposed Solution • Technical Specifications • Computer Aided Dispatch • Case Management • Other Tools • Training and Support Services • Service Activation and Support Requirements • References • Implementation • Vendor Qualifications • Pricing • Service level agreement (SLA) • Desirable Criteria • Information Technology Security • MBE/WBE University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 10

Requirements and Scope. 3. LIMITING CRITERIA A. Proposed Solution 1. The proposed solution must have the ability to enter, save, and modify CAD events using a variety of input methods (short-cut keys, dropdown menus, mouse selections, etc.). 2. The proposed solution must allow for CAD events to be created and saved without location and event type being entered. 3. The proposed solution must automatically generate all date and timestamps for any entries, additions, or modifications of CAD records. These dates and timestamps must be in synchronization with the date and time stamp used with the telephone and voice recording software. 4. The proposed solution must allow for the creation of basic CAD events with no more than 3 (three) keystrokes. 5. The proposed solution must have the ability to add names, vehicles, property, and unknown suspects to the system directly from CAD. 6. The proposed solution must allow an unlimited number of notes to be entered for a CAD event. 7. Minimally, the CAD modules must capture and/or display the following information: a. Display server time in Hours:Minutes:Seconds b. Event creation Date and Time c. Auto-generated Event Number d. User-configurable selection lists for capturing i. Received Via – method the call was received ii. Initial Incident – indicates the type of incident reported iii. Disposition – current status of the event iv. Final Incident e. Incident Priority f. Call Timer alerting dispatch to perform officer safety checks at user-configurable time intervals based on Initial Incident value g. Location based on “Common Name” (i.e. not a specific street address; e.g. Science Building) that is not part of the GEO file h. Location Detail – text field to allow describing exact location i. Location Street Number j. Location Street Name, validated against GEO file k. Location Apt/Suite/Lot number l. Reporting Person Name and Address m. CAD user name entering the event n. Notes area for entering internal information o. Public Information area for entering an event summary for public distribution as well as the Daily Crime log (34 CFR 668.46(F) required by the Clery Act. 8. The proposed solution must allow for entering Open Calls, capturing and/or displaying at a minimum: a. Event Number b. Initial Incident code c. Priority d. Status with “As Of” timestamp e. Elapsed Time since last Status change University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 11

f. Unit Number assigned g. Beat h. Location including Common Name, Street Number, Street Name, Location Detail 9. The proposed solution must allow for the identification of safety hazards for a location and alerts the user if the unit is entering a location that has general safety, known weapons, and/or hazmat concerns. 10. The proposed solution must allow for queries related to reporting persons, premises history, protection orders, warrants, mental or health issues, gang information, sex offenders, vehicle databases for vehicles involved in other incidents/events, etc. These queries must be executable without exiting the CAD system. 11. The proposed solution must allow for the following information to be added/associated with a CAD Event: a. Master Name data, including: multiple addresses, multiple phone numbers, physical description b. Vehicles from a vehicle records database c. Property information from a Property Records database 12. The proposed solution must allow for the following tasks during Case Management: a. Searching/scrolling through existing Case Reports via shortcut key, menu dropdown, toolbar icon, etc. b. Searching for a specific Case Report by Case Number via shortcut key, menu dropdown, toolbar icon, etc. c. Adding/Modifying/Saving Case Reports via shortcut key, menu dropdown, toolbar icon, etc. d. Jumping straight to the last saved Case Report via shortcut key, menu dropdown, toolbar icon, etc. 13. The proposed solution must allow for the ability to add the following information to a Case Report: a. Multiple Vehicles b. Multiple Pictures c. Multiple Businesses d. Multiple Properties e. Chain of Custody and Check Out information for received/recovered property f. Unknown Suspect Description g. Clery/VAWA UCR/NIBRS Review Records h. Racial Profiling 14. The proposed solution must allow for the ability to print a full Case Report, with the following options: a. Display printed report on screen b. Print the report to a local or networked printer c. Save the report as a file to a specific local or network drive d. Select to print the entire report or specific sections of the report 15. The proposed solution must allow for the ability to add, view, search for, edit, and delete Master Name records associated with an individual. 16. The proposed solution must allow supervisors the ability to assign personnel to Investigate, Followup on, and add Supplemental or M.O. Information to a Case Record. 17. The proposed solution must allow for the ability to search/scroll through existing Investigations. 18. The proposed solution must allow for the ability to perform queries/run reports/browse data on CAD records and all Case Management Reports and supplemental information (e.g. Locations, Moving Citations, Vehicles, Property/Evidence, GEO File, Field Interviews, Warrants, Trespasses, Restraining Orders, Crime Analysis, Unknown Suspects) University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 12

19. The proposed solution must allow for the ability to send notifications to user-defined email addresses/lists for incident notification and updates. 20. The proposed solution must maintain an Arrest Log for individuals. 21. Storage and Access Requirements a. The University will be the sole and exclusive owner of its data and contractor agrees not to access or use this data for any purpose unless explicitly agreed to in a separate writing. b. The University must be able to retrieve the data without incurring additional costs. c. University data must be completely segregated from those of contractor’s other customers. d. Contractor agrees to reveal the physical location of the servers that will, or may, store University data and agrees to provide reasonable advance notice if those physical locations change. The University reserves the right to prohibit storage of University data in certain locations/countries and prefers that all data and information remain within the United States. e. The University must be notified immediately of any subpoena or other legal request related to University data. f. Contractor agrees to cooperate and assist the University in responding to any legal request for University data. g. Contractor agrees to identify any third parties, including subcontractors, subcontractors of subcontractors, etc. that will have the ability to access University data and for what purposes. Contractor agrees to conduct reasonable due diligence and security assessments of these third parties and will enter into contracts with these third parties that hold those parties to the same obligations as the vendor’s obligations to the University. h. Contractor agrees to ensure that their employees and approved subcontractors understand, accept and have received appropriate instruction regarding their obligations to handle University data with the proper security. i. University requires that data be maintained and available for the life of the contract plus six months. B. Technical Specifications a. Describe in detail (or provide documentation detailing) the hardware and software technical specifications required by the system, including but not limited to: i. Application development platform ii. Database system and versions (preferred MS SQL Server) iii. Application and Database servers, including OS, memory/CPU requirements, other platform requirements (e.g. .Net, JAVA, etc.) with required versions, if applicable iv. Client OS/Browser/other hardware or software requirements b. Describe in detail (or provide documentation detailing) the technical architecture employed in communicating between the client workstation and the application/database servers, including but not limited to: i. Graphical user interface ii. Network connection requirements c. Describe in detail the upgrade process, including timelines, and how it impacts client workstations as well as server downtimes d. Describe in detail how user permissions are defined and to what level user permissions can be set. e. Describe in detail how the system will be installed inside the UMSL data center. Include any necessary physical security requirements or external connectivity. University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 13

C. Computer Aided Dispatch a. Describe in detail how the proposed solution assigns monitors and tracks the progression of a unit through an incident once dispatched, including color-coding, pop-ups or other alerts, etc. b. Describe in detail how the proposed solution handles Event and Resource Management, including but not limited to: i. Assigning multiple units to a single event ii. How each unit’s times are tracked when assigned to a single event iii. Information stored for open calls, including: 1. Event Number 2. Incident 3. Priority 4. Status 5. Elapsed Time 6. Unit Number 7. Location iv. Sort options for available resources (e.g. sort by Unit Number, Name, Current Location, etc.) v. All options available for updating times (e.g. via shortcut keys, mouse clicks, manually entered, etc.) c. Describe in detail if/how the proposed solution handles Call Stacking, including but not limited to: i. Assigning a single unit to multiple events in sequence ii. Do not allow for a unit to be On Scene for more than one event at a time iii. Notification to dispatcher when the unit has completed one event and is ready for the next iv. Distinguish between stacked calls and other open calls in the open call list d. Describe in detail how the proposed solution handles capturing, reporting, and querying of Reporting Party information, including but not limited to: name, address, and phone number e. Describe in detail how the proposed solution tracks department vehicles, including fuel consumption f. Describe how the proposed CAD solution allows for the generation of Case Numbers for Case Management g. Describe in detail how the proposed solution handles Call Reassignment and Call Cancelling, including but not limited to: i. Reassigning a single unit to a different event while maintaining activities on both events ii. Creating a police information record attached to the CAD event with reassignment date/time and event numbers iii. The original event remains in the open call list until a new unit is assigned iv. Mechanism for cancelling a call (e.g. tool bar icons, shortcut keys, etc.) v. Process that occurs when a call is cancelled (e.g. status is cleared, notes are required to be entered, etc.) h. Describe in detail how the proposed solution allows for querying and reporting CAD record information, including but not limited to: i. Querying on Event Number or Date/Time ii. Querying in a separate window without exiting the CAD module iii. The mechanism for initiating a query or report (e.g. tool bar icon, drop down menu, shortcut keys, etc.) iv. A list or example of all the information included on a complete report of a CAD record i. Describe other features available with the CAD module, including but not limited to: University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 14

v.i. Internal messaging between CAD and RMS users User configurable phonebook/Rolodex for entering names and phone numbers j. Describe how the CAD module contains or integrates with a schedule of available personnel and pulls those specific personnel data to create a shift duty roster as well as the assignment of personnel for the call for service. vi.ii.

D. Case Management a. Describe in detail all information captured and displayed regarding Case Management records, including but not limited to: i. General Information, e.g. Report title, disposition status, approval status, report number, related agency/number, date/time reported, date/time occurred, location, etc. ii. Involved Parties, e.g. name, involvement, prior arrests/referrals, address/phone, ID info (drivers license, SSN, etc.), demographic/physical information (race, height, weight, etc.) iii. Final Disposition, including all notes iv. Dispatch Information, i.e. all associated information from the CAD module v. Narrative, full text description explaining the case, including spell check and font options b. Describe in detail the information captured and displayed for the following Case Management records details: i. Vehicles ii. Pictures iii. Businesses iv. Properties v. Chain of Custody and Check Out information for received/recovered property vi. Unknown Suspect Description vii. UCR/NIBRS Review Records viii. Racial Profiling data as required by RSMo Section 590.650. c. Describe in detail the options available for printing partial vs. full Case Management Reports. d. Describe in detail all information captured and displayed regarding Master Names records and how they are related back to the Case Management record, including but not limited to: i. General Information, e.g. name, ID info (driver’s license, SSN, student id, FBI ID, Finger Print ID, etc.), demographic/physical information (gender, race, ethnicity, etc.) ii. Address, including: type (home, business, college, etc.), number/street, detailed name/description/location (floor, suite, etc.), city/state/zip iii. Phone number, including: type, number, extension iv. Detailed Physical Description v. Any Aliases vi. Field Interview Information vii. Vehicles viii. Prior Arrests ix. Moving/Criminal Citations x. Warrants xi. Trespasses xii. Restraining Orders xiii. Associations xiv. Other Notes xv. Pictures University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 15

e. Describe in detail all information captured and displayed regarding Investigations, including but not limited to: i. General Information, e.g. Case Number, Status (with As Of date/time), Notes, Method for Assignment of an investigation or follow-up, Date Assigned, Assigned To, Closed/Cleared Date/time, Closed/Cleared by, Reason Closed, Review Date, Purge Date, Solvability Factors (list of options to select with Total Solvability Score) ii. Follow-up Information, e.g. Case Number, Date Reported, Unit/Name of officer writing the follow-up (from a selection list), Narrative, Status, Follow-up Start/End Dates/Times iii. Supplements, e.g. Case Number, Date Reported, Unit/Name of officer writing the followup (selected from a list), notes, Supplement Date iv. M.O. Log, e.g. Case Number, Lighting (from selectable list), Type of Structure, Point of Entry, Exit, Number of Suspects, Suspect Actions, Security, Target, Tools Used (including Computers), Under the Influence, Alarm Type, Method of Entry E.

Other Tools a. Describe in detail how queries /searches are executed on CAD records and all Case Management records and supplemental information. Include: i. The mechanism for accessing and navigating through the query/search/reporting tool (e.g. opens in separate window without losing access to the main functions, shortcut keys, menu items, etc.) ii. Any predefined search criteria (e.g. Last 50 Records, Last 8/12/24/48 Hours, etc.) iii. Search Criteria available (e.g. date range, event/case number, names, locations, dispositions, officers, narrative text, case status, report title, related agencies, case disposition, Master Name data (age, race, sex, etc.), etc.) iv. How data is/can be displayed(e.g. tables/grids, graphs, charts, etc.), sorted, grouped v. If/how data can be copied, exported and/or printed and in what file types/formats vi. If/how more detailed data can be viewed for a specific result vii. Any advanced query/search options b. Describe in detail how the Reporting tool functions. Include: i. Any third party reporting tools required (e.g. Crystal Reports, etc.) and whether it needs to be installed on each user’s workstation ii. Search Criteria tools available (e.g. date/time ranges/calendars) iii. Other tools/options (e.g. print, zoom, refresh, scroll through results, etc.) iv. Sharing options for executed reports v. Identify types of administrative/statistical reports available including detailed description of processes used to create appropriate Clery annual reports. This should include any correlation between system setup/configuration and resulting reports. Is there a mechanism for ensuring Clery/VAWA reporting is current with legislative change? c. Describe in detail how the Notification tool functions, including how recipients are selected from a CAD or Case Management record, how/what specific CAD or Case Management information is selected to be sent. d. Describe in detail the Arrest Log features, including how the log is accessed from Case Management tool, how many results are displayed (e.g. 50), if/how the log data can be sorted, search criteria available (e.g. Case Number, Name of arrested party, date range, etc.), how the Name record of the associated individual is accessed from the search result. e. Describe in detail if/how training records for department personnel are captured/managed, including: types of training (classes, scheduled training, permanent training records), how the

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 16

training tool is accessed/navigated (shortcut keys, menu items, etc.), details regarding training (dates, name, description, costs, hours, etc.) f. Describe in detail any mobile technology available with the proposed solution, including detailed hardware and software specifications, installation process, how it interacts with the CAD module, mobile-to-mobile as well as mobile-to-dispatch communication options, etc. g. Describe in detail any Event Tracker functionality available in the proposed solution for special events on campus, including: capturing location, open/close time, primary contact, etc.; maintaining a historical record of past events, creating a new event based on a past event; scheduling multiple/repeating events; etc. h. Describe in detail any Parking enforcement functionality available in the proposed solution, including: provide user-defined parking permits, issuing and tracking of parking tickets, any hand-held device options and how they communicate to the main system, statistical reporting, noting special events that may determine lot closures and/or “no ticket” rules, etc. as well as any review or student court adjunction, fine or discipline. F. Training and Support Services a. Training and support is critical to the University’s successful use of the software to its full potential. The University seeks to utilize the power of the proposed solution quickly and desires a solution with the shortest learning curve and greatest ease of use in order to use the product to its full potential in the shortest time frame possible. Provide training schedule and describe the proposed solution’s training materials, what is included in these materials, how it is delivered both on-site as well as in an online learning environment and to whom it is made available. b. Describe your repository of on-line knowledge bases and documentation, FAQs, and other tools and the technologies used to provide those services. Include your on-line technical support resources (e.g. download center for utilities, maintenance releases, etc.). c. Identify how the proposed solution provides interactive help and ensures learning driven at the point of consumption, including but not limited to user groups and list-serve type peer support. G. Service Activation and Support Requirements a. Describe change management procedures. Specifically address when patches and incremental version upgrades are applied. Describe communications methods to alert the University of upcoming changes. Describe testing procedures before application of patches or upgrades. Describe any recurring schedule for upgrades. b. Describe in a step-by-step format what actions must be accomplished to configure and activate the system. Provide a checklist detailing all tasks. c. The agreement must cover bug reporting by the university and the process for repair. There must be a target timeline offered for all bug fixes identified by the university. d. Describe trouble reporting and escalation procedures. Include a toll-free telephone number or email address to address trouble issues. e. It is important that all problems are resolved promptly within four (4) business hours. Describe your support model and escalation process. Indicate the proposed solution’s ongoing maintenance or service level options available to current clients. Identify problem tracking and resolution reporting, in addition to customer access to those records. Indicate how customer inquiries are handled and the type of support available to current clients for functional and technical assistance.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 17

H. References The University prefers to work with vendors that have extensive experience in higher education. Successful respondent must be tested and proven solid in providing services in this marketplace with large, public institutions supporting enrollments of approximately 17,000+ and multiple academic colleges and schools. Include a list of three (3) references, from institutions of higher education similar to the University of Missouri-St. Louis environment where you have implemented the proposed solution. Provide institution name, contact person, position in the institution, email address, and telephone number. The University reserves the right to contact recipients of respondent’s proposed system and include their responses as part of the evaluation. I.

J.

Implementation a. The University requires a solution that can be implemented smoothly and in a timely and cost efficient approach. Describe your project management methodology for implementation projects. Provide the total number of installations completed using that methodology. b. Submit an estimate of how long implementation is anticipated to take and a typical implementation schedule or model. Describe in full detail how implementation is carried out and what resources will be required from the University. Response must indicate the ability to tailor the proposed solution to the University’s needs. Vendor Qualifications a. Provide a brief statement executive summary of capabilities not to exceed one (1) page. b. Provide a brief history of the organization not to exceed three (3) pages including but not limited to the following: i. Locations ii. Mission statement iii. Company philosophy iv. Brand promise, v. Customer commitments vi. Certifications, personnel vii. Systems and services viii. Management approach and practices ix. Customer service x. Communication, xi. Financials xii. Sustainability practices xiii. Pricing c. Provide a statement summary including years of experience with CAD software not to exceed two (2) pages. d. Provide a statement of company capabilities and years of experience in providing technical support including but not limited to the following: i. Provide the location (domestic and/or international) of technical support and respondent’s ability to provide toll-free technical assistance during normal business hours. ii. Describe in detail the qualifications and years of experience of technical support. e. List any user groups associated with your product(s). f. There must be one vendor point of contact (i.e. account executive) for all issues related to implementation and subsequent service. The point-of-contact may delegate tasks, but must remain directly responsible to the university for delegated tasks. g. Identify the number of respondent’s employees who will be dedicated to the university’s account.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 18

K. Pricing Describe how the proposed solution and services are priced (methodology) and specifically itemize costs for the system application proposed for the initial contract term, including all possible expenses (e.g., license fees [user vs. concurrent, different license levels/roles, permissions per level/role, etc.], implementation and training, documentation, travel, etc.). Outline one-year fees and any annual fees thereafter. Specify any implementation fees and services that are included in the price. The pricing should describe what level of software modification is included to meet the university’s needs during implementation and, if not included, what the cost will be. Additionally, outline your pricing structure for any subsequent renewal years beyond the initial term. What incentives can you offer the University to renew after the initial term? Explain how you will determine proposed price increases and when those price increases take effect. L.

Minority and Business women Enterprises M/WBE a. Respondent must include with their response to this RFP, the M/WBE participation form, filled out in accordance with the percentage of qualified MBE and WBE participation committed to in relation to the total dollar value of the contract regardless of whether the respondent is awarded the contract. All information should be in accordance with section #7 of the General Terms and Conditions. b. Submittals should also include the firm’s M/WBE or Disadvantaged Business certification.

M. Invoicing Management a. RFP consideration will include each firm’s completion of the attached prepared sample invoice to ensure comparative pricing. (Sample invoices and required documents for completion are attached to the end of the RFP 14-3014-AL-S). b. Consideration will be given to vendors providing pricing on completed sample invoice.

The remainder of this page is intentionally left blank

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 19

Requirements and Scope Continued. 4. SERVICE LEVEL AGREEMENT (SLA) a.

SLA Copy 1. Provide a copy of respondent’s standard service level agreement (SLA) for consideration including but not limited to the following: 2. The successful respondent should be prepared to negotiate SLA terms. 3. Describe financial remuneration or other consideration for failure to meet SLA minimums, and the availability of metrics, preferably a report available to both parties after each notification event, including tests. 4. Descript activation and support requirements

b.

Management Procedures 1. Describe change management procedures. Specifically address when patches and incremental version upgrades are applied. The University prefers Thursday (University Health Care best time) or Sunday mornings, although upgrades after normal duty hours (M-F, 7AM to 7PM) are acceptable. 2. Describe communications methods to alert the University of upcoming changes. 3. Describe testing procedures before application of patches or upgrades. Describe any recurring schedule for upgrades.

c.

Configuration and Activation 1. Describe in a step-by-step format what actions must be accomplished to configure and activate the subscription service. Provide a checklist detailing all tasks. The subscription agreement must cover bug reporting by the University and the process for repair. There must be a target timeline offered for all bug fixes identified by the University.

d.

Up and Down time 1. State your uptime and explain any down time you have experienced in the past two years.

e.

Support Model and Escalation Process 1. It is important that all problems are resolved promptly within four (4) business hours. 2. Describe your support model and escalation process. 3. Indicate the proposed solution’s ongoing maintenance or service level options available to current clients. 4. Describe the identification of problems, tracking and resolution reporting, in addition to customer access to those records. 5. Describe how customer inquiries are handled and the type of support available to current clients for functional and technical assistance. 6. Include a toll-free telephone number or e-mail address to address trouble issues.

f.

System Breach 1. Explain procedures if the proposed system’s security is breached.

g.

Disaster Recovery 1. Explain disaster recovery procedures.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 20

h. Data Retrieval 1. Describe in detail the process to retrieve university data at the end of the contract term or in the event we cancel the subscription at an annual anniversary date. Specifically, address procedures, database schema requirements, formats, etc. for the successful export of university data into MS SQL Server or Oracle databases in a form capable of producing Cognos-derived reports and data analyses.

The remainder of this page is intentionally left blank

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 21

Requirements and Scope Continued. 5. DESIRABLE CRITERIA Please provide answers to the following questions. a. Minimum Experience and Knowledge Provide a description of the overall experience and knowledge you will use if engaged to furnish; deliver; install; and continual maintenance, service and support of a CAD System for UMSL ITS and PD that complies with University of Missouri System ITS and UMSL ITS Policies and Procedures as well as Clery, UCR/NIBRS reporting laws.. Include description of the steps necessary to achieve success. In this section, clearly explain how your firm can achieve high levels of efficiency and a recommendation of structure and operations for CAD System Please provide the contact information and client background for three (3) references. Submit references for clients that are most similar to the services being requested by the University. NOTE: Firms that do not provide complete information for references will not be considered (i.e., do not respond if you cannot share references). Respondents must include information that covers the criteria listed below. • Organizational Experience • Stated Commitments • References • Knowledge of CAD System Best • Knowledge of Trends in IT • Knowledge of Local, State and Federal Laws as it Relates to public University IT services and security. b. Management Approach Provide a description of the overall management approach/methodology you will use if engaged to provide CAD System for UMSL ITS and UMSL PD. Describe in particular your approach to furnish; delivery, installation; continued maintenance, service and support of UMSL ITS/ UMSL PD CAD System. You should include the steps used to assess issues and produce a quality product for the University of Missouri. The client relationship management should be discussed (i.e., interaction with UMSL ITS and UMSL PD). In this section, clearly explain how your firm can achieve high levels of efficiency and a recommendation of structure and operations for achieving a successful CAD System. Respondents must include information that covers the criteria listed below. • Attention to Detail • Customer Service • Quality Standards • Communication • Risk • Knowledge Resources and Transfer • Project Management University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 22

c.

Financials Describe how your company derives and creates pricing structures for other clients. Include typical rates. Clearly explain how your firm can decrease costs for production and the recommendations on how those decreases can be achieved. Provide a description of the financial strength of your company. Respondents to include information that covers the criteria listed below. • • •

d.

Communication With any major project the need for open lines of communication is crucial. Describe how your company will stay in contact with UMSL ITS and UMSL PD personnel during the production phase and continued maintenance, service, and support of the CAD System Include in your answer proven successes that your company has experienced with other clients. Responses should include but are not limited to the following: • •

e.

Invoice Management Describe other discounts, scholarship or other amenities within your response. Provide fee structure that corresponds with completed invoice.

Strategies for Communication with UMSL Completeness and Organization of Response

Sustainability In compliance with the State of Missouri Revised Statutes (34.031.1), University of Missouri System is committed to the ideas and principals of environmental improvement, energy efficiency and sustainability with purchasing preference of recycled products made from solid waste, and the elimination of purchase of products made whole or in part of thermoformed or other extruded polystyrene foam manufactured using any fully halogenated chlorofluorocarbon (CFC). Products that utilize recovered materials of a price and quality comparable to products made from virgin materials shall be sought and purchased if their use is technically feasible and, where a bid is required, their price is equal to, or less than, the price of items which are manufactured or produced from virgin materials. Products that would be inferior, violate safety standards or violate product warranties may be excluded. Please provide information relating to sustainability efforts with past and current clients. Include in your answer proven successes for the areas listed below. • Sustainable Practices Utilized. • Sustainable Procurement Emphasized.

f.

Cost Considerations – Price Provide in detail the fee structure for to furnish; deliver; install; provide continual maintenance, service, and support of UMSL CAD System. Firms that do not provide detailed itemized pricing on the completed sample invoice will not be considered.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 23

g.

Preferences In compliance with State of Missouri Revised Statutes (34.031.), University of Missouri System is committed to the ideas and principles to promote the development of an educated, civil, diverse workforce, by maximizing the usage of value driven products and services through a combination of excellence in price and quality; with preference given to products manufactured, mined, produced, or grown by companies in Missouri, or services provided by such companies. In evaluation of proposals, preferences shall be given to products of the mines, forests and quarries of the state of Missouri, and all materials, commodities, products, supplies, provisions and all other articles produced, manufactured, mined, processed or grown within the state of Missouri, provided that: • • • •

They are of a quality suitable and are fit for the purpose intended. They can be secured without additional cost over foreign products or the products of other states. They are found in marketable quantities in the state. The quality is equal or better and delivered price is the same or less.

Preference shall be given to all firms, corporations or individuals doing business as Missouri firms, corporations or individuals. Corporations not incorporated under the laws of Missouri and firms whose members are not residents of the state of Missouri and individuals not residents of the state of Missouri who have and maintain within the state of Missouri a regular place of business shall be deemed "doing business as Missouri firms, corporations or individuals" when consideration is being given to bids for acceptance by the University.

The remainder of this page is intentionally left blank.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 24

Requirements and Scope Continued. 6. SECURITY REQUIREMENTS FOR INFORMAITION TECHNOLOGY As part of the selection process Respondent’s must demonstrate compliance with the security criteria listed in the categories stated on the accompanying “University of Missouri Information Security Requirements” spreadsheet by responding in writing to every statement and question. It is the Respondent’s responsibility to supply sufficient and complete information for a full evaluation of all items in this section, including detailed explanations. Validation of the answers provided by the Respondent may be conducted during the review/assessment process. Any erroneous information could limit the Respondent’s ability to finalize implementation of the proposed solution. Please include any security white papers, technical documents, or policies that are applicable. Failure to provide the necessary information to meet the requirements in this section could lead to disqualification. The University considers security to be an ongoing responsibility and as a result, these information security criteria are subject to additions and changes without warning. When appropriate, the successful vendor will be expected to work in good faith with the University to maintain compliance with new laws and regulations and/or to improve the security of the proposed system.

a.

Data Classification System Vendors are expected to maintain an awareness of the laws and regulations applicable to the use of the proposed solution in a University environment. The University of Missouri reserves the right to periodically audit the hardware and/or software infrastructure to ensure compliance with industry best practices as well as the requirements of the University’s Data Classification System. When applicable, the University of Missouri requires compliance with the Family Educational Rights and Privacy Act (FERPA), Health Insurance Portability and Accountability Act (HIPAA), Gramm-Leach-Bliley Act (GLBA), Payment Card Industry (PCI) specifications and all other applicable state, local and federal laws and regulations. In order to apply security measures in the most appropriate and cost effective manner, data stored electronically must be evaluated and assigned a Data Classification Level (DCL) of 1, 2, 3, or 4. The DCL of the data establishes the extent and type of information security measures that must be implemented and the security requirements set forth are high level requirements that establish the minimum standards necessary for each DCL. Definitions of the DCL’s can be viewed here: http://infosec.missouri.edu/classification/dc-sys-apps.html#other-defs. A post award technical review and assessment is required for all level 3 and 4 system/application implementations. All reviews/assessments shall be prescheduled with the vendor and assessment results will be provided to the departmental representative and to the vendor.

b. Compensating Controls and Descriptions All statements and questions on the spreadsheet are mandatory unless they are not applicable. The Respondent must clearly explain why a given question is not applicable. For all other questions, if a requirement cannot be met, the Respondent still has an opportunity to meet the requirement by the use of compensating controls. In some instances, the University has requested that the Respondent provide a description to accompany their response to a particular statement or question. Descriptions are requested when a “Meets or Exceeds” answer alone could be deceptive without further detail. Compensating controls must be described in full in the appropriate column. When more room is University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 25

needed to fully explain the compensating control or provide a complete description, attachments can be included in the proposal response so long as such attachments are labeled and cross-referenced in the “Comments, Descriptions or Explanations of Compensating Controls” column. In such circumstances, the vendor must provide a full explanation of the compensating control including an explanation of how the control meets the intent of the original question. The University has the sole right to determine if a proposed compensating control is an acceptable solution and if the details provided describe a solution that truly meets or exceeds the University’s needs. c. Information Technology Security Questionnaire. The security questionnaire is not a Limiting Criteria, but a pass/fail from University of Missouri System and UMSL Information Technology Services (ITS). 1. RFP consideration will include each firm’s completion of the attached prepared information technology security questionnaire to ensure public University of Missouri information technology compliance.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 26

Requirements and Scope Continued. 7. UNIVERSITY OF MISSOURI SYSTEM PAYMENT SCHEDULE b. Payment The University reserves the right to withhold a portion of the payment until the software has been fully implemented and training completed. The final invoice will be paid 30 days after user acceptance, as defined by the University. Payment terms shall be mutually agreed upon between the successful respondent and the University prior to contract award. b. Proposed Payment Schedule Contract award with PO issued

30% of total

Installation of solution

30% of total

Software operational in production with University acceptance, including passing a security assessment

40% of total

The remainder of this page is intentionally left blank.

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 27

Requirements and Scope Continued. 8. PROPOSAL CONTENT & REQUIRMENT FOR SUBBMITTING RFP RESPONSE. a. Organization of Proposal Proposals should be organized in this fashion: 1. Letter of Interest 2. Maximum length = 1 page. b. Proposal Section A—Executive Summary Maximum length = 1 pages. 1. Provide a narrative summarizing your response. 2. The summary should include the following information: • Company background in management of printing, publishing and distributing consumer magazines Y • Your understanding of objectives • Clear statement of your companies specialization in the management of printing and distributing consumer publications • Qualifications and experience as it relates to the management of printing and distributing consumer publications including but not limited to: o Similar sized publications o Description of the scope of your proposal

9.

PROPOSAL DELIVERY Proposals are to be submitted in writing, in a sealed envelope, clearly marked in the lower left corner of the envelope, “RFB 14-3014-AL-S” UMSL PD CAD and addressed to: Amanda M. La Brier University of Missouri Procurement Services & Supply Chain One University Blvd 209 Woods Hall St. Louis, MO 63121

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 28

Section 5 KEY DATES AND TIMETABLE The approximate timelines, subject to change, are as follows: Activities Release RFP Registration Deadline for Pre-proposal Conference call. Pre-proposal informational meeting will be by conference call with call-in information to be provided to those who request the information. Informational Walk-Through Site visit if necessary Due date for submission of written questions. Proposer to submit questions in a MS Word document to Amanda M. La Brier [email protected] Last Date for potential responder clarifications. University’s response to questions (Subject to Change) Due Date for Submission (Subject to Change) Interview Period (top bidders) (Subject to Change) Anticipated RFP Award (Subject to Change)

Dates March 19, 2014 March 24, 2014 10:00A.M. CT March 26, 2014 3:00P.M. CT

To be determined during pre-proposal conference call if necessary. April 8, 2014 at 10:00A.M. CT

April 10,2014 April 25, 2013 5:00P.M. CT April 30, 2014 at 10:00A.M. CT May 1st - 8th, 2014 May 9, 2014

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 29

Section 6 Certifying MBE/WBE Agencies MBE/WBEs are those businesses certified as disadvantaged by an approved agency. The Bidder is responsible for obtaining information regarding the certification status of a firm. A list of certified firms may be obtained by contacting the agencies listed below. Any firm listed as disadvantaged by any of the following agencies will be classified as a MBE or WBE by the Owner. St. Louis Development Corporation 1015 Locust St. Louis, MO 63101 314/622-3400; 314/622-3413 (Fax) CONTACT: Minority Business Development Manager Bi-State Development Agency 707 North First Street St. Louis, MO 63102-2595 314/982-1457; 314/982-1558 (Fax) CONTACT: Disadvantaged Business Enterprise Coordinator St. Louis Minority Business Council 308 North 21st St., 7th Floor St. Louis, MO 63101 314/241-1143; 314/241-1073 (Fax) CONTACT: Executive Director U.S. Small Business Administration - St. Louis, MO 8(a) Contractors, Minority Small Business 815 Olive St., Room 242 St. Louis, MO 63101 314/539-6600; 314/539-3785 (Fax) CONTACT: Business Opportunity Specialist Lambert St. Louis International Airport 4610 N. Lindbergh, Suite 240 Bridgeton, MO 63044 314/551-5000; 314/551-5013 (Fax) CONTACT: Program Specialist City of Kansas City, Missouri Human Relations Department, MBE/WBE Division 4th Floor, City Hall Kansas City, MO 64106 816/274-1432; 816/274-1025 (Fax) CONTACT: Minority Business Specialist

816/374-6729; 816/374-6759 (Fax) CONTACT: Business Opportunity Specialist State of Missouri-Office of Administration Division of Design and Construction, Minority Business Development P.O. Box 809, Harry S. Truman State Office Building Room 730, 301 West High Street Jefferson City, MO 65102 573/751-6908; 573/526-3097 (Fax) CONTACT: Minority Contracts Coordinator Missouri Department of Transportation Division of Construction P.O. Box 270 Jefferson City, MO 65102 573/751-6801; 573/526-5640-6555 (Fax) CONTACT: Disadvantaged Business Enterprise Coordinator Illinois Department of Transportation MBE/WBE Certification Section 2300 Dirkes Parkway Springfield, IL 62764 217/782-5490 CONTACT: Certification Manager State of Missouri-Office of Administration Division of Purchasing & Materials Management Minority Purchasing Unit P.O. Box 809 Jefferson City, MO 65102 800/592-6019; 573/751-7276 (Fax) CONTACT: MBE/WBE Certification Coordinator

Kansas City Minority Supplier Council 3017 Main Street, Suite 100 Kansas City, MO 64108-3323 816/931-9672; 816/931-9673 (Fax) CONTACT: Executive Director U.S. Small Business Administration - Kansas City, MO 8(a) Contractors, Minority Small Business 323 W. 8th Street, Suite 501 Kansas City, MO 66105 University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 30

M/WBE PARTICIPATION FORM If proposing MBE/WBE participation, the contractor/supplier must indicate below the percentage of qualified MBE and WBE participation committed to in relation to the total dollar value of the contract regardless of whether the contractor/supplier is awarded one, some, or all of the categories being proposed. Overall the MBE and WBE participation must not be contingent upon award of a specific category, and the contractor/supplier, if awarded a contract, must be able to achieve the stated participation for the resulting contract regardless of the categories awarded or not awarded. The contractor/supplier must be able to achieve the committed to participation stated below for the total value of the awarded contract(s). If the contractor/supplier is a qualified MBE and/or WBE, the contractor/supplier may indicate 100% participation. The University’s MBE participation goal for this bid is 5% The University’s WBE participation goal for this bid is 5% The contractor supplier is committed to the following MBE and WBE participation on this bid: Total MBE Participation _____%

Total WBE Participation_____%

Complete the following table indicating the firms used to meet the participation levels indicated. MBE Firm Name

MBE % of WBE Firm Name Contract

WBE % of Contract

------------THIS FORM MUST BE SUBMITTED WITH THE BID------------See Section 8 Proposal Form Page 3

University of Missouri System Request for Proposal - RFB#14-3014-AL-S: UMSL PD CAD

Page 31

Section 7 SPECIAL CONSIDERATIONS The University of Missouri System Procurement Services request proposals to furnish deliver, install, train UMSL personnel, maintain, service, and support PD CAD/RMS or approved equivalent to the University of Missouri – St. Louis (UMSL) located in St. Louis, Missouri.

A.

Product Information Information Please supply technical data for the CAD/RMS System being offered in the proposal response. The CAD/RMS System must meet or exceed all Federal and or State of Missouri Information Technology applicable safety, security, and standard guidelines, including, but not limited to: “Agencies should develop and implement technical, operational, and policy tools and resources to establish and ensure appropriate security of the technology (including networks and infrastructure) and the data it provides to safeguard against risks of loss, unauthorized access or use, destruction, modification, or unintended or inappropriate disclosure. This principle includes meeting state and federal security mandates (e.g., the FBI’s CJIS Security Policy 1), and having procedures in place to respond if a data breach, loss, compromise, or unauthorized disclosure occurs, including whether, how, and when affected persons will be notified, and remedial and corrective actions to be taken.”2

B.

Product Technical Description Specifications As described in the RFP Limiting Criteria [Section 4 Detailed Specifications and Special Conditions, Part B: Submitting an RFP Response, 3 Limiting Criteria].

1

Federal Bureau of Investigation, Criminal Justice Information Services (CJIS) Security Policy, Version 5.2, August 9, 2013, CJISD ITS DOC 08140 5.2, at http://www.fbi.gov/aboutus/cjis/cjis security policy resource center/view. Accessed December 30, 2013.

2

Additional guidance regarding safeguarding personally identifiable information can be found in the Office of Management and Budget (OMB) Data Breach notification policy (M 0716), at http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2007/m07 16.pdf, and state data breach notification laws available from the National Conference of State Legislatures, at http://www.ncsl.org/research/telecommunicationsand information technology/Security breach notification laws.aspx. Accessed December 30, 2013. University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 32

C. General The University of Missouri-Columbia is greatly interested in information technology security and will perform tests, in information sharing environments when appropriate, to determine University security compliance. The results of these tests will determine if the University continued purchases with vendors. University of Missouri-St. Louis Department of Information Technology Services must approve the CAD software, compatibility, security compliance, implementation, maintenance/service/support agreement prior to awarding the contract for supplied materials and services. At the time of the proposal, the CAD data sheet and sample invoice must be completed and included with the proposal. The log sheet must be signed by a duly authorized officer of the bidding company, one who will guarantee the validity of the information stated. Failure to return the signed data sheet can result in rejection of the proposal. All equipment and software shall conform to the latest revision of all applicable standards. The proposal will be awarded based on the unit with the lowest total ownership cost meeting these specifications. The lead time for delivery may also be included in the bid analysis and may be a factor in the award.

D.

Delivery Shipping 1. Shipping shall be F.O.B. University of Missouri-St. Louis, Department of Information Technology on or before June 15, 2014, with absolutely no delivery later than June 30, 2014. Notice shall be given 48 hours prior to arrival to allow arrangements to be made for receiving. 2. Notice shall be given to the UMSL Department of ITS PMO Manger, Jeff Lovell Contact Name by calling (314) 516-7322 at least 48 hours prior to arrival on site. 3. Ship directly to University of Missouri – St. Louis ITS, One University Boulevard, 451 Express Scripts Hall St. Louis, Missouri 63121 to accept delivery. Attention: ITS, PMO Manager, Jeff Lovell. Do not deliver to any other room. 4. On delivery day, delivery driver should call Jeff Lovell at (314) 516-7322 or second Brian Kuhn at (314) 516 4064 about 30 minutes prior to arrival to ensure someone will be able to accept shipment. 5. Please confirm via email to PMO Manager, Jeff Lovell at [email protected] with estimated ship and delivery dates. 6. Receiving by the University shall be during normal business hours Monday – Friday, 8:00am to 3:00pm.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 33

Section 8 PROPOSAL FORM

(Name of firm or individual proposing)

REQUEST FOR PROPOSALS For

THE CURATORS OF THE UNIVERSITY OF MISSOURI At UNIVERSITY OF MISSOURI - ST. LOUIS

Managerial and Technological Services Department of Information Technology Services (ITS) Requesting The furnish; delivery; installation; continued maintenance, service, support, training, and compliance with University of Missouri System Information Technology Policies and Procedures for a Computer Aided Dispatch System in the University of Missouri – St. Louis Police Department. RFP # 14-3014-AL-S OPENING DATE: April 30, 2014 TIME: 10:00 PM, CT

The undersigned proposes to furnish the following items and/or services at the prices quoted and agrees to perform in accordance with all requirements and specifications contained within this Request for Proposal issued by the University of Missouri. The quantities identified in the Proposal page are estimates only. The quantities may or may not represent the actual quantities encountered on the project. University of Missouri System and UMSL may increase quantities and will expect the firm awarded contract to furnish additional materials, supplies, services and support at the same unit price. University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 1

PROPOSAL FORM PAGE 1

Manufacturer: ______________________________________________________

Project:

______________________________________________________

CAD/RMS CRITERIA Question

1.

2. 3. 4. 5.

6. 7.

Limited Criteria Requirements Please mark whether or not (YES or NO) if the proposed CAD solution for UMSL IT & PD meets each requirement listed below. The proposed solution must have the ability to enter, save, and modify CAD events using a variety of input methods (short-cut keys, dropdown menus, mouse selections, etc.). The proposed solution must allow for CAD events to be created and saved without location and event type being entered. The proposed solution must automatically generate all date and timestamps for any entries, additions, or modifications of CAD records. The proposed solution must allow for the creation of basic CAD events with no more than 3 (three) keystrokes. The proposed solution must have the ability to enter, save, and modify CAD events using a variety of input methods (short-cut keys, dropdown menus, mouse selections, etc.). The proposed solution must have the ability to add names, vehicles, property, and unknown suspects to the system directly from CAD. The proposed solution must allow an unlimited number of notes to be entered for a CAD event.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Yes

No

Page 2

Question

8.

9.

10.

11.

PROPOSAL FORM PAGE 1A Limited Criteria Requirements Please mark whether or not (YES or NO) if the proposed CAD solution for UMSL IT & PD meets each requirement listed below. Minimally, the CAD modules must capture and/or display the following information: a. Display server time in Hours: Minutes: Seconds b. Event creation Date and Time c. Auto-generated Event Number d. User-configurable selection lists for capturing i. Received Via – method the call was received ii. Initial Incident – indicates the type of incident reported iii. Disposition – current status of the event iv. Final Incident e. Incident Priority f. Call Timer alerting dispatch to perform officer safety checks at user-configurable time intervals based on Initial Incident value g. Location based on “Common Name” (i.e. not a specific street address; e.g. Science Building) that is not part of the GEO file h. Location Detail – text field to allow describing exact location i. Location Street Number j. Location Street Name, validated against GEO file k. Location Apt/Suite/Lot number l. Reporting Person Name and Address m. CAD user name entering the event n. Notes area for entering internal information o. Public Information area for entering an event summary for public distribution The proposed solution must allow for entering Open Calls, capturing and/or displaying at a minimum: p. Event Number q. Initial Incident code r. Priority s. Status with “As Of” timestamp t. Elapsed Time since last Status change u. Unit Number assigned v. Beat w. Location including Common Name, Street Number, Street Name, Location Detail The proposed solution must allow for the identification of safety hazards for a location and alerts the user if the unit is entering a location that has general safety, known weapons, and/or hazmat concerns. The proposed solution must allow for queries related to reporting persons, premises history, protection orders, warrants, mental or health issues, gang information, sex offenders, vehicle databases for vehicles involved in other incidents/events, etc. Queries must be executable without exiting CAD system.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Yes

No

Page 3

Question

12.

13.

14.

15.

16. 17.

18.

PROPOSAL FORM PAGE 1B Limited Criteria Requirements Please mark whether or not (YES or NO) if the proposed CAD solution for UMSL IT & PD meets each requirement listed below. The proposed solution must allow for the following information to be added/associated with a CAD Event: x. Master Name data, including: multiple addresses, multiple phone numbers, physical description y. Vehicles from a vehicle records database z. Property information from a Property Records database The proposed solution must allow for the following tasks during Case Management: aa. Searching/scrolling through existing Case Reports via shortcut key, menu dropdown, toolbar icon, etc. bb. Searching for a specific Case Report by Case Number via shortcut key, menu dropdown, toolbar icon, etc. cc. Adding/Modifying/Saving Case Reports via shortcut key, menu dropdown, toolbar icon, etc. dd. Jumping straight to the last saved Case Report via shortcut key, menu dropdown, toolbar icon, etc. The proposed solution must allow for the ability to add the following information to a Case Report: ee. Multiple Vehicles ff. Multiple Pictures gg. Multiple Businesses hh. Multiple Properties ii. Chain of Custody and Check Out information for received/recovered property jj. Unknown Suspect Description kk. UCR/NIBRS Review Records, including: Racial Profiling The proposed solution must allow for the ability to print a full Case Report, with the following options: ll. Display printed report on screen mm. Print the report to a local or networked printer nn. Save the report as a file to a specific local or network drive oo. Select to print the entire report or specific sections of the report The proposed solution must allow for the ability to add, view, search for, edit, and delete Master Name records associated with an individual. The proposed solution must allow supervisors the ability to assign personnel to Investigate, Follow-up on, and add Supplemental or M.O. Information to a Case Record. The proposed solution must allow for the ability to search/scroll through existing Investigations.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Yes

No

Page 4

Question

19.

20. 21. 22.

PROPOSAL FORM PAGE 1C Limited Criteria Requirements Please mark whether or not (YES or NO) if the proposed CAD solution for UMSL IT & PD meets each requirement listed below. The proposed solution must allow for the ability to perform queries/run reports/browse data on CAD records and all Case Management Reports and supplemental information (e.g. Locations, Moving Citations, Vehicles, Property/Evidence, GEO File, Field Interviews, Warrants, Trespasses, Restraining Orders, Crime Analysis, Unknown Suspects) The proposed solution must allow for the ability to send notifications to userdefined email addresses/lists for incident notification and updates. The proposed solution must maintain an Arrest Log for individuals.

Yes

No

Storage and Access Requirements pp. The University will be the sole and exclusive owner of its data and contractor agrees not to access or use this data for any purpose unless explicitly agreed to in a separate writing. qq. The University must be able to retrieve the data without incurring additional costs. rr. University data must be completely segregated from those of contractor’s other customers. ss. Contractor agrees to reveal the physical location of the servers that will, or may, store University data and agrees to provide reasonable advance notice if those physical locations change. The University reserves the right to prohibit storage of University data in certain locations/countries and prefers that all data and information remain within the United States. tt. The University must be notified immediately of any subpoena or other legal request related to University data. uu. Contractor agrees to cooperate and assist the University in responding to any legal request for University data. vv. Contractor agrees to identify any third parties, including subcontractors, subcontractors of subcontractors, etc. that will have the ability to access University data and for what purposes. Contractor agrees to conduct reasonable due diligence and security assessments of these third parties and will enter into contracts with these third parties that hold those parties to the same obligations as the vendor’s obligations to the University. ww. Contractor agrees to ensure that their employees and approved subcontractors understand, accept and have received appropriate instruction regarding their obligations to handle University data with the proper security. xx. University requires that data be maintained and available for the life of the contract plus six months.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 5

PROPOSAL FORM PAGE 1D Proposal Submission will also include a response to all items listed in Section 4, Detailed Specifications and Special Conditions, Requirements and Scope, Sections 3, 4, and 5 above. 3. Evaluation Criteria • Technical Specifications • Computer Aided Dispatch • Case Management • Other Tools • Training and Support Services • Service Activation and Support Requirements • References • Implementation • Vendor Qualifications • Pricing 4. Service level agreement (SLA) 5. Desirable Criteria

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 6

PROPOSAL FORM PAGE 2 COST AND AUTHORIZATIONS

A. Itemized Cost by bidder. Please provide and completed detailed itemized pricing on the attached sample invoice. B. Pricing to be FOB Destination, with all freight charges fully included and prepaid. C. Current Certificate of Insurance to be on file at the UM Procurement Office, meeting coverage and limits per attached sheet where applicable. GRAND TOTAL COST: $___________. Authorized Company Representative: (Please print Name)

Authorized Company Signature: Company Title:

The remainder of this page has been intentionally left blank

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 7

PROPOSAL FORM PAGE 3 M/WBE PARTICIPATION FORM If proposing MBE/WBE participation, the contractor/supplier must indicate below the percentage of qualified MBE and WBE participation committed to in relation to the total dollar value of the contract regardless of whether the contractor/supplier is awarded one, some, or all of the categories being proposed. Overall the MBE and WBE participation must not be contingent upon award of a specific category, and the contractor/supplier, if awarded a contract, must be able to achieve the stated participation for the resulting contract regardless of the categories awarded or not awarded. The contractor/supplier must be able to achieve the committed to participation stated below for the total value of the awarded contract(s). If the contractor/supplier is a qualified MBE and/or WBE, the contractor/supplier may indicate 100% participation. The University’s MBE participation goal for this bid is 5% The University’s WBE participation goal for this bid is 5% The contractor supplier is committed to the following MBE and WBE participation on this bid: Total MBE Participation _____%

Total WBE Participation_____%

Complete the following table indicating the firms used to meet the participation levels indicated. MBE Firm Name

MBE % of WBE Firm Name Contract

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

WBE % of Contract

Page 8

PROPOSAL FORM PAGE 4 University of Missouri Information Security Requirements As part of the selection process vendors must demonstrate compliance with the security criteria listed below by responding in writing to every statement and question in the eight categories. Validation of the answers provided by the vendor may be conducted during the review/audit process. Any erroneous information could limit the vendor's ability to finalize implementation of the proposed solution. Vendors are expected to maintain an awareness of the laws and regulations applicable to the use of the proposed solution in a University environment.

Data Classification Does this solution store and/or transmit any of the following types of restricted and/or highly restricted data? Check all that apply. Health Information (PHI)  Payment Card Industry (PCI)  Gramm-Leach-Bliley Act (GLBA)  Social Security Numbers (SSN)  Federal Educational Rights & Privacy Act (FERPA)  Biometric Data (fingerprints, handprints, etc.)  Employee Evaluations  Intellectual Property  Confidential Research

 Protected

The University assigns data classification levels for all University owned or hosted IT-based systems. This system will have a DCL level of _4_. Security requirements for all DCS levels can be found at: http://infosec.missouri.edu/classification/dcs.html. The University of Missouri reserves the right to periodically audit any or all hardware and/or software infrastructure provided by the vendor to ensure compliance with industry standards and best practices as well as the requirements of the University's DCS. When applicable, the University of Missouri requires compliance with the Health Insurance Portability and Accountability Act (HIPAA), FERPA, GLBA, PCI specifications, and all other applicable state, local and federal laws and regulations. For all level 3 and 4 system/application implementations, a post award technical review and/or assessment is required. All reviews/assessments will be prescheduled with the vendor and assessment results will be provided to the affected University department's representative and to the vendor. The University considers security to be an ongoing responsibility and as a result, these information security criteria are subject to additions and changes without warning. When appropriate, the successful vendor will be expected to work in good faith with the University to maintain compliance with new laws and regulations and/or to improve the security of the proposed system. University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 9

Documentation The vendor should provide security whitepapers, technical documents, or copies of policies as necessary to fully demonstrate compliance with the requirement. Failure to provide the necessary information to meet the requirements in this section could lead to disqualification. Compensating Controls and Descriptions All statements and questions below are mandatory unless they are not applicable. The vendor must clearly explain why a given question is not applicable. For all other questions, if a requirement cannot be met, the vendor still has an opportunity to meet the requirement by the use of compensating controls. Compensating controls must be described in full in the appropriate column. When more room is needed to fully explain the compensating control, attachments can be included in the bid response so long as such attachments are labeled and cross-referenced in the "Comments or Explanations of compensating controls" column. In such circumstances, the vendor must provide a full explanation of the compensating control including an explanation of how the control meets the intent of the original question. The University has the sole right to determine if a proposed compensating control is an acceptable solution.

In some instances, the University has requested that the vendor provide a description to accompany their response to a particular statement or question below. Descriptions are requested when a "Meets or Exceeds" answer alone could be deceptive without further detail. When more room is needed to provide a complete description, attachments can be included in the bid response so long as such attachments are labeled and cross-referenced in the "Comments, Descriptions or Explanations of Compensating Controls" column. The University has the sole right to determine if the details provided describe a solution that truly meets or exceeds the University's needs.

Vendor/Product/Department Information (MUST BE COMPLETED) University Contact(s) Information Vendor Name and Contact Information Product Name and Brief Description

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 10

Requirements

Response or approved compensating control required if product falls within the specified DCS Level: http://infosec.missouri.ed u/classification/dcs.html

Meets

Does Not Meet

Comments, Description of Compensating Control

1. The vendor must acknowledge and agree to allow the University, at its discretion, to inspect/assess all or portions of the proposed solution prior to placing the system into production. The University does not need the vendors "code" to perform such assessments, however, the University will use web application (IBM AppScan, HP WebInspect) and network vulnerability tools (Nessus) in coordination with the vendor's technical team when appropriate. The results of the assessment(s) will be provided to the University customer (i.e., the department) and to the vendor. All

1.a The vendor must agree to remediate high risk security vulnerabilities that are identified by such assessments within a reasonable time frame and at no cost to the University. Medium and low risk vulnerabilities should also be remediated but will be scheduled for remediation based on a mutually agreeable timeframe. (This applies to generally accepted security vulnerabilities within the industry, NOT changes or modifications that would be considered customerrequested improvements or functionality enhancements.) All

2. If the proposed solution will interface with other networks, systems, databases or applications, the vendor MUST provide an architecture document that includes a full network diagram of the environment, illustrates the relationship between the environment and any other relevant networks/systems, and includes a full data flowchart that details where data resides, and any applications that manipulate it. All

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 11

3. Upon selection, details of any third party reviews related to industry or regulatory compliance must be made available for University review. Vendor MUST include third party web application and server vulnerability and/or penetration tests if available. Redacted reports are acceptable.

DCL3 and DCL4

4. Vendor must comply with applicable industry standards and best practices for system administration and application development (i.e. OWASP). Indicate which industry standards are utilized by the vendor. All

5. If applicable, Payment Card Industry - Data Security Standard (PCI-DSS) or Payment Data Security Standard (PA DSS) compliance is required. The vendor can comply with this item if it has attained PCI certification for the overall set of products/services being proposed or by having one or more system implementations that are currently PCI certified. Provide evidence of such certification attached to the response. If available, the vendor must provide a guide for PCI-compliant implementation of their product. DCL4

Network Security 1. The proposed solution must support secure access to privileged University users either through VPN technologies or other secure technologies.

DCL3 and DCL4

Availability 1. Quality Assurance testing for the proposed solution must have been or must be conducted. Such testing must include authentication, authorization, and accounting functions, as well as any other activity designed to validate the functionality, integrity, availability and security of the solution.

All

Authentication, Authorization and Password Security

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 12

Requirements

Response or approved compensating control required if product falls within the specified DCS Level: http://infosec.missouri.ed u/classification/dcs.html

Meets

Does Not Meet

Comments, Description of Compensating Control

1. The vendor must ensure that system and application administrators or anyone having elevated or privileged access to any part of the system, be required to follow strict password complexity and password management policies. Passwords for privileged access must be at least 15 characters and include a combination of letters (upper case and lower case), numbers and symbols. Please provide policies/procedures that govern the vendor's password complexity and password reset requirements. All

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 13

Requirements

2. The University requires that the vendor allow authentication to their system through existing University authentication methods. For on-campus systems, Shibboleth/SAML2.0 (preferred) or Microsoft Active Directory (AD) is required. For vendor-hosted systems, Shibboleth/SAML 2.0 (SP initiated) is required. Vendor must provide their Shibboleth/SAML 2.0 integration documentation. Application Security 1. The database must be segregated from front-end systems (i.e web and application servers.) Please describe how this is accomplished

Response or approved compensating control required if product falls within the specified DCS Level: http://infosec.missouri.ed u/classification/dcs.html

Meets

Does Not Meet

Comments, Description of Compensating Control

DCL2, DCL3 and DCL4

DCL3 and DCL4

Cryptography/Encryption 1. Except for the viewing of static Web pages, the vendor must ensure that all other transmissions to and from the system, including file transfers, authentication mechanisms, end-user and administrator access, etc. are handled via encrypted protocols.

2. Any data stored at rest on a hard drive, on a file server and/or in a database MUST be encrypted or granted an exception by the appropriate Information Security Officer at http://infosec.missouri.edu/admin/iso.html.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

All

DCL4

Page 14

Answer These Additional Questions If The Proposed Solution Will Be Vendor Hosted 1. The vendor must immediately disable all or part of the system functionality should a security issue be identified. 2. The University requires notification of actual or suspected security incidents/breaches within 24 hours of the vendor's first knowledge of such an event.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

All

All

Page 15

Requirements

3. The equipment utilized for services provided to the University must be located in a secure facility using, at a minimum, physical tokens for access. 4. The vendor must provide a listing of individuals by name or by title (if by title, the number of individuals in each title must be provided) that have physical access to the equipment used for the proposed solution.

Response or approved compensating control required if product falls within the specified DCS Level: http://infosec.missouri.ed u/classification/dcs.html

Meets

Does Not Meet

Comments, Description of Compensating Control

All

All

5. The vendor must have written procedures for granting physical access to the facility and ensure that the access is reviewed and updated at least quarterly. Provide a copy of the policy/procedure that governs this activity. All

6. The vendor must acknowledge that it will utilize a hostbased firewall for any systems that are hosted by the vendor for the proposed solution. 7. The proposed solution must be behind a hardware-based firewall to protect and limit access to the system. 8. The vendor must ensure that University of Missouri owned or provided data is segregated and protected from other customers. Please describe how this is accomplished. 9. The vendor must ensure that the hosts comprising infrastructure used by the University of Missouri has been hardened against attack. Please describe how this is accomplished. 10. The University expects non-critical operating system patches to be applied within 30 days of release.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

All

DCL3 and DCL4

All

All

All

Page 16

Requirements

11. The University expects critical system patches to be applied within 15 days. If the 15 day requirement cannot be met, the vendor must clearly indicate how security risks are mitigated until patches can be applied. 12. The vendor must follow separation of duty principles as required by the University's Data Classification System (http://infosec.missouri.edu/classification/dcs.html).

Response or approved compensating control required if product falls within the specified DCS Level: http://infosec.missouri.ed u/classification/dcs.html

Meets

Does Not Meet

Comments, Description of Compensating Control

All

All

13. The vendor must consult with the ISO to determine if integration with an approved centrally managed authentication service (e.g. Active Directory) is necessary DCL2, DCL3 and DCL4

14. Can the vendor consistently (24x7) monitor the application/system/environment for integrity and availability? Describe how and how quickly system issues are responded to by the vendor and how quickly issues will be reported to the University.

All

15. The vendor must have a process to review and update the access list for privileged accounts at least monthly. Please provide copy of the policy or procedure that governs this DCL2 = quarterly; DCL3 and activity. DCL4 = monthly

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 17

PROPOSAL FORM PAGE 5 AUTHORIZED RESPONDENT REPRESENTATION Number of calendar days delivery after receipt of order

Payment Terms

Authorized Signature

Date

Printed Name

Title

Company Name Mailing Address City, State, Zip Phone No.

Federal Employer ID No.

Fax No.

E-Mail Address

Check One:

Individual

Partnership

Corporation

If a corporation, incorporated under the laws of the State of_____________________ This signature sheet must be returned with your proposal.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 18

PROPOSAL FORM PAGE 6 REFERENCES Respondents to provide at least three (3) references that can provide information as to the capabilities, services, performance of respondent in the following format: 1.

Name of Organization _______________________________________________ Address___________________________________________________________ Contact Person _____________________________________________________ Phone Number _____________________________________________________

2.

Name of Organization _______________________________________________ Address___________________________________________________________ Contact Person _____________________________________________________ Phone Number _____________________________________________________

3.

Name of Organization _______________________________________________ Address___________________________________________________________ Contact Person _____________________________________________________ Phone Number ____________________________________________________

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 19

PROPOSAL FORM PAGE 7 STATEMENT OF RESPONDENT'S QUALIFICATIONS (File with Proposal Form in separate envelope appropriately designated.) 1.

Number of years in business:________. If not under present firm name, list previous firm names and types of organizations. _________________________________________________________________________ _________________________________________________________________________

2.

Contracts on hand: (Complete the following schedule.) Amount of Your Contract Per Cent Completed Item Purchaser _________________________________________________________________________ _________________________________________________________________________

3.

General Type of product sold or manufactured _________________________________________________________________________

4.

There has been no default in any contract completed or uncompleted except as noted below: (a) Number of Contracts on which default was made:_________ (b) Description of defaulted contracts and reason therefore: _________________________________________________________________________ _________________________________________________________________________

5.

List banking references: _________________________________________________________________________ _________________________________________________________________________

6.

(a)

Do you have a current confidential financial statement on file with University? Yes/No. (Please Circle)

If not, and you desire, you may file such statement with this proposal, sealed in a separate envelope and appropriately designated. (b)

If not, upon request will you within 3 days file a detailed confidential financial statement? Yes_____ No_____ (check one)

Dated at _______________________________________this________________________day of_______2014.

By:_________________________________ Print

______________________________________

Name of Organization(s)

By:_________________________________ Signature By:___________________________________ Title of Signing Authority University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 20

PROPOSAL FORM PAGE 8

SAMPLE INVOICE

Company Name: Street Address: City, ST ZIP Code: Phone: Fax:

DATE: Quotation valid until: Prepared by:

Comments or special instructions: [Add/remove line items as necessary to indicate what you would be invoicing UMSL for in regard to this proposal] AMOUNT Description ONE TIME COSTS UMSL CAD SYSTEM Software Special Hardware Required Installation Services Training Services User Licenses (by category/level, if applicable) Other Please List

TOTAL

$

-

ON GOING COSTS Software Maintenance Support Services University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 21

Hardware Support/Maintenance User Licenses (by Applicable Category/Level) Other Please List

TOTAL

$

-

If you have any questions concerning this quotation, contact Name, Phone Number, E-mail

THANK YOU FOR YOUR BUSINESS!

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 22

This page was left intentionally blank.

University of Missouri RFB#14-3014-AL-S: UMSL PD CAD

Page 23