19-5934 RFP.docx

DOCX document 377 KB Posted

Attached to
EMERGENCY NOTIFICATION SYSTEM (UW-MAD) [19-5934]
Solicitation number
19-5934
Issued by
Dane County, Madison City, Wisconsin

About this file

This is a Request for Proposal (RFP) issued by the University of Wisconsin-Madison Purchasing Services Department on behalf of the UW Police Department for an emergency notification system. The system's primary purpose (Lot 1) is to provide campus administrators a tool to comply with the federal Clery Act by notifying students, faculty, staff, and visitors of emergency situations and crimes through multiple communication channels including email, SMS text, social media (Facebook, Twitter, Instagram), website integration, display boards, VOIP messaging, and the Integrated Public Alert and Warning System (IPAWS). The system must be cloud-based, support approximately 100,000 email addresses and 40,000-60,000 cell phone numbers, and deliver messages within 90 seconds. Lot 2 includes capability to send messages to an estimated 31,000 residents in the immediate area around campus administered by the City of Madison, organized by neighborhood through a registration portal. Lot 3 includes a safety app for students, faculty, and staff with user tracking, test messaging to dispatch, and resource access features. The mandatory Pre-Solicitation Conference was held on September 14, 2018, with the proposal due date of October 16, 2018 at 2:00 PM CDT. Demonstrations were scheduled for October 26, 2019. The contract term is three years from execution with options to renew for two additional one-year periods, automatically extending unless either party provides 30 days written notice.

Pricing shall remain firm for the initial three-year contract term, with any subsequent increases limited to fully documented cost-increase documentation submitted 60 days prior to the next contract term. The cost proposal requires vendors to break down implementation costs, recurring costs, and other costs across ten fiscal years. Implementation costs include the first 30 percent due upon invoice receipt, with the remaining balance due after the University's 30-day testing and approval period. All recurring fees are billed in arrears and payable net 30 days from invoice receipt. The University qualifies for governmental and educational discounts, which must be reflected in unit pricing. All proposal prices must include FOB Destination with delivery charges and risk of loss borne by the contractor. No set-asides or incumbent information are noted in the solicitation. The RFP requires proposals to meet mandatory requirements including U.S.-based service performance and compliance with Section 508 accessibility standards and WCAG 2.0 AA standards. Contractors must maintain commercial general liability insurance of $2,000,000 per occurrence, cyber liability insurance of $2,000,000, and workers' compensation insurance as required by Wisconsin Statutes. Data must be stored in U.S.-based data centers with encryption at rest and in transit, and all University data must be returned or destroyed upon contract termination within 30 days. The scoring matrix allocates 850 technical points across seven evaluation categories (qualifications, mandatory requirements, general requirements, capabilities/functionality, account management, data, and reporting) and 150 cost points for a total possible score of 1,000 points. Only proposals receiving 300 or more technical points will have their cost proposals scored.

View the file

Other files

File Type Posted
19-5934 RFP AMD2.pdf PDF
19-5934 RFP AMD 3.pdf PDF
19-5934 RFP AMD1.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Proposal No. 19-5934

UNIVERSITY OF WISCONSIN

MADISON, WISCONSIN 53715-1218

University of Wisconsin – Madison Request For Proposal

THIS IS NOT AN ORDER

OFFICIAL SEALED

Proposal Number: 19-5934

NO PUBLIC OPENING

Issued Date: 8/30/2018

Due Date: 10/16/2018 2:00 PM CDT Agent:

Questions regarding this proposal – see Section 2.8

For Submittal Instructions & Proposal Response Format – see Section 2.2 and 2.3 Proposal prices and terms shall be firm for sixty (60) days from the date of the proposal to the opening, unless otherwise specified in this Request for Proposal by the UW-Madison Purchasing Services.

If NO BID (check here) ☐ and return.

Emergency Notification System

In signing this bid, we have read and fully understand and agree to all terms, conditions and specifications and acknowledge that the UW-Madison Purchasing Services bid document on file shall be the controlling document for any resulting contract. We certify that we have not, either directly or indirectly, entered into any contract or participated in any collusion or otherwise taken any action in restraint of free competition; that no attempt has been made to induce any other person or firm to submit or not to submit a bid; that this bid has been independently arrived at without collusion with any other bidder, competitor or potential competitor; that this bid has not been knowingly disclosed prior to the opening of bids to any other bidder or competitor; that the stated statement is accurate under penalty of perjury. I certify that the information I have provided in this bid is true and I understand that any false, misleading or missing information may disqualify the bid.

By submitting a bid, the bidder certifies that no relationship exists between the bidder and the University that interferes with fair competition or is a Conflict of Interest, and no relationship exists between such bidder and another person or firm that constitutes a Conflict of Interest. Further, bidder certifies that no employee of the University whose duties relate to this request for bid assisted the bidder in preparing the bid in any way other than in his or her official capacity and scope of employment.

The Bidder certifies by submission of the bid that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation in this transaction by any federal department or agency.

Company Name:

Company Street Address:

Company City, State & Zip:
Date:

Signature:

Type or Print Name:

Title:

Telephone Number: ( )
Fax Number: ( )

Email address:

Fein Number :
DUNS #:

Table of Contents

1.General Information5
1.1.Purpose:5
1.2.Scope:5
1.3.Organization of this Solicitation Document:6
1.4.Definitions:6
1.5.VendorNet Registration:6
1.6.Parking:7
1.7.Reasonable Accommodations:7
2.Preparing and Submitting a Proposal8
2.1.Applicable Dates:8
2.2.Submittal Instructions:8
2.3.Proposal Response Format:9
2.4.Incurring Costs:9
2.5.Pre Solicitation Conference (Mandatory):9
2.6.Oral Presentations, Product Demonstrations and Proposer Location Site Visits (Pre Award):10
2.7.Clarifications and/or Revisions through Designated Contact:10
2.8.Multiple Proposals:10
2.9.Proprietary Information:10
2.10.Appeals Process:11
3.Terms and Conditions of Contract12
3.1.Entire Contract:12
3.2.Contract Administrator:12
3.3.Term of Contract:13
3.4.Orders:13
3.5.Firm Prices:13
3.6.Payment Terms:14
3.7.Invoicing Requirements:14
3.8.F.O.B. Destination:15
3.9.Requirements for Criminal Background Checks:15
3.10.Travel Per Diems:15
3.11.Campus Delivery Requirements:15
3.12.Acceptance and Test (Post Award):16
3.13.Insurance:16
3.14.Activity Reports:16
3.15.Record and Audit:17
3.16.Performance Meetings:17
3.17.Subcontracting:17
3.18.Fair Price Analysis:17
3.19.Severability:17
3.20.Environmentally Friendly (“Green”) Product:17
3.21.Supplier Diversity:17
3.22.Discriminatory Boycotts of Israel:18
3.23.Debarment:18
3.24.Electronic Commerce/Online Ordering:19
3.25.Promotional Materials/Endorsements:19
3.26.Additional Items/Services:19
4.Requirements and Specifications20
4.1.Qualifications and Company History: (100 Points)20
4.2.Mandatory Requirements: (Mandatory)20
4.3.General Requirements: (125 Points)20
4.4.Capabilities/Functionality: (250 Points)21
4.5.Account Management: (175 Points)23
4.6.Data: (125 Points)23
4.7.Reporting: (75 Points)24
5.Evaluation and Award of Contract(s)25
5.1.Proposal Scoring:25
5.2.Scoring Criteria and Method:25
5.3.Best and Final Offers:26
5.4.Contract Award:26
5.5.Notification of Award:26
Attachment A: Vendor Information Form27
Attachment B: Cost Proposal Form29
Attachment C: Client Reference List30
Attachment D: Standard Terms and Conditions31
Attachment E: Hosted (Software as a Service) Rider37
Attachment F: UW-Madison Data Security Terms and Conditions44
Attachment G: Accessibility46
Attachment H: Pre-Solicitation Conference Certification47

1. General Information

1.1. Purpose:

The University of Wisconsin-Madison, hereinafter referred to as the “University”, through its Purchasing Services Department, hereinafter referred to as “Purchasing”, on behalf of the UW Police Department, hereinafter referred to as “UW Police”, requests bids for the purchase of an emergency notification system.

1.2. Scope:

The University of Wisconsin-Madison is soliciting bids for an emergency notification system. The system's primary purpose (Lot 1) is to provide a tool for campus administrators to comply with the federal Clery Act, specifically the notification of emergency situations to students, faculty, staff, and visitors and notice of crimes. The system should also have the capacity to activate key personnel, such as members of the campus's emergency operations center.

The system must utilize common communication channels, including email, SMS text, social media (Facebook, Twitter, and Instagram), website integration, display boards (such as TVs in dining facilities), and Integrated Public Alert and Warning System (IPAWS.) The system should also utilize VOIP messaging and display boards (such as TVs in dining facilities). The system should also have the capacity to utilize emerging or new communication channels. The anticipated population is an estimated 100,000 email addresses and an estimated 40,000-60,000 cell phone numbers. Because of the importance of the notifications that this system will be sending, it is imperative that the notifications be sent quickly. The scoring will favor systems that can be activated and the message sent in under 90 seconds.

The system must be cloud based, data must be stored in US based data centers, utilize the campus' active directory for user authentication, utilize an administrator app for sending of messages, allow for role-based administrator access, utilize groups or lists of individuals, allow for end users to access their profile to add additional contact information while allowing the campus to provide base data (email and cell phone numbers), allow for temporary users to self-register into the system (campus visitors and contractors), and provide a rapid send feature (such as a desktop button).

Lot 2 of the bid should include the capability to send messages to the immediate area around the campus, estimated population is 31,000. These messages will be administered by the City of Madison. The immediate area will be divided into neighborhoods. City of Madison residents living in these neighborhoods should have the ability to register to receive messages specific to their neighborhood(s) of interest via an internet portal.

See Requirements and Specifications (Section 4) and/or Cost Proposal Form (Attachment B) for the minimum acceptable specifications for items/services desired. The estimated item quantities identified on the Cost Proposal Form are for proposal purposes only. The University does not guarantee to purchase any specific quantity or dollar amount. This contract must not be construed as mandatory upon any University campus, State agency or municipality. The University reserves the right to issue separate proposals when deemed in the best interest of the University.

Lot 3 of the bid should include a safety app for students, faculty, and staff that allows for the user to be tracked while walking alone, ability to send test messages to dispatch, and provide resources to the user (such as phone numbers).

The University reserves the right to negotiate with any contracted vendor(s) to establish additional discounts and/or lower prices for products determined to meet the requirements of a University-led initiative to set product standards. Contractor vendor(s) may be asked to provide new, lower prices for these standard products and configurations for a limited, fixed term, to fall within the term of the contract resulting from this Request for Bid/Request for Proposal.

All University of Wisconsin-Madison departments must be eligible to purchase from this contract.

1.3. Organization of this Solicitation Document:

This document is divided into five (5) main sections. The sections also refer to “Attachments” when such organization assists in making this document more fluid. The five (5) main sections are:

Section 1General Information (generally states the intent of the solicitation and submittal instructions)
Section 2Preparing and Submitting a Proposal.
Section 3Terms and Conditions of Contract (contains performance clauses that will become part of any awarded contract).
Section 4Requirements and Specifications (technical and other specifications for the proposal).
Section 5Evaluation and Award of Contract(s) (contains details of the evaluation process).

1.4. Definitions:

The following definitions are used throughout this document:

Agent means UW Madison Purchasing Agent responsible for this Request for Proposal. Full contact information can be found in Section 2.11.

CAP means Common Alerting Protocol Contractor means successful proposer awarded a contract.

DVB means Disabled Veteran-Owned Business.

IPAWS means Integrated Public Alert and Warning System MBE means Minority Business Enterprise.

Proposer means a firm submitting a Proposal in response to this Request for Proposal.

Purchasing card means State credit card.

Purchasing means the Purchasing Services Department in the Division of Business Services responsible for the procurement of goods and services on UW-Madison campus, located at 21 N. Park St., Madison, WI 53715.

RFP means Request for Proposal.
SMS means Short Message Service
State means State of Wisconsin.
University and UW both mean University of Wisconsin-Madison.
UW Police means the UW Police Department.

WBE means Woman-Owned Business Enterprise.

WCAG means Web Content Accessibility Guidelines

1.5. VendorNet Registration:

Registration on the State of Wisconsin’s VendorNet System (http://vendornet.state.wi.us) is available free of charge to all businesses and organizations that want to sell to the state. Refer to Bidder Response: Registration and Sign-in Process for further instructions. Registration allows a vendor to:

1.5.1. Registration for a bidders list for commodities/services that the vendor wants to sell to the state.

1.5.2. Receive an automatic e-mail notification each time a state agency, including the University of Wisconsin System campuses, posts a Request for Bid (RFB) or Request for Proposal (RFP) with an estimated value over $50,000.00 in their designated commodity/service area(s).

1.5.3. Receive an e-mail notification of addendums/amendments relative to the RFB or RFP.

1.5.4. Only vendors registered, with a valid e-mail address, at the time of the RFB or RFP is posted will receive e-mail notifications of addendums/amendments. Vendors who obtain the RFB or RFP from a third party; through the public notice website; or other means assume responsibility for checking for updates to the RFB or RFP.

1.6. Parking:

University parking is very limited. Each Contractor and/or employee(s) shall make their own arrangements for parking through UW Transportation Services (website: http://transportation.wisc.edu/parking/parking.aspx) No additional costs will be allowed for parking fees or violations. Unauthorized vehicles parking in University lots or loading docks without permits will be ticketed and or towed.

1.7. Reasonable Accommodations:

The University will provide reasonable accommodations, including the provision of informational material in an alternative format, for qualified individuals with disabilities upon request.

2. Preparing and Submitting a Proposal

2.1. Applicable Dates:

Date

Event

8/30/2018
Date of Issue of the RFP
9/14/2018
Pre-Solicitation Conference (Mandatory)
9/21/2018
Written Questions Due
9/24/2018
Answers to Questions Sent to Proposers (Estimated)
10/16/2018 – 2:00 PM CDT
RFP Due Date (Local Madison Time)
10/24/2018
Evaluations and Oral Presentations (if needed)

2.2. Submittal Instructions:

PROPOSALS MUST BE DELIVERED TO:

Purchasing Services, 21 N. Park Street, Suite 6101, Madison, WI 53715-1218.

NUMBER OF COPIES TO BE SUBMITTED:

Two (2) Hard copies of the completed proposals, including the signed original, may be mailed, delivered by Proposer, or by a third-party/courier service in a sealed envelope or package with the RFP number on the outside. One (1) Flash Drive Copy of the proposal must also be submitted. Proposal must be received and date/time stamped prior to 2:00 p.m. CDT on the stated proposal due date. Proposals not so date/time stamped shall be considered late. Late proposals shall be rejected.

RETAIN A COPY OF YOUR BID RESPONSE FOR YOUR FILES

If hand delivering to Purchasing Services, please come to 6th Floor Reception Desk in Suite 6101 and call 608-262-1526 for assistance.

Proposals may be dropped off at Purchasing Services, 21 N. Park Street, Suite 6101, Madison, WI 53715-1218, between the hours of 7:00 AM and 4:00 PM prior to the due date and time.

FAXED OR EMAILED RESPONSES WILL NOT BE ACCEPTED.

VENDOR NOTE: FOR THE PURPOSE OF THE RETURN ADDRESS LABEL, IF THE ADDRESS IS THE SAME AS YOUR ADDRESS LISTED ON THE REQUEST FOR PROPOSAL FORM – YOU DO NOT NEED TO FILL OUT THE RETURN ADDRESS LABEL.

RETURN ADDRESS LABEL:

Below is a label that can be taped to the outside of your sealed proposal response. If returning your proposal response by mail or in person, please fill out the information and tape to the outside of your bid package.

OFFICIAL SEALED PROPOSAL

NUMBER: 19-5934

DUE DATE: 10/16/18
TIME: 2:00 PM CDT

SHIP FROM:

VENDOR NAME HERE:

ADDRESS:

SHIP TO:

UNIVERSITY OF WISCONSIN-MADISON

PURCHASING SERVICES

21 N PARK ST, SUITE 6101

MADISON, WI 53715-1218

2.3. Proposal Response Format:

Proposals should be typed and submitted on 8.5 by 11 inch paper and bound securely. The response should be organized and presented in the following order. Each section should be separated by tabs or otherwise clearly marked. The contents within each tab should reference the section or attachment number assigned in the RFP. Failure to submit as indicated may disqualify your proposal.

Tab 1:

· Request for Proposal form signed by an authorized representative of proposing company - Cover Page.

· Vendor Information Form, Attachment A

· Client Reference List, Attachment C Tab 2: Responses to specifications in Section 4. – Specifications (Sections 4.1-4.7) Tab 3: Cost Proposal, Attachment B Tab 4: Accessibility, Attachment G Tab 5: Other

RETAIN A COPY OF YOUR PROPOSAL RESPONSE FOR YOUR FILES

2.4. Incurring Costs:

The State of Wisconsin is not liable for any cost incurred by proposers in replying to this RFP.

2.5. Pre Solicitation Conference (Mandatory):

A Pre Solicitation Conference will be held at 9 am, at University Police Station, 1429 Monroe Street, Madison, WI on 9/14/18 in Room 1006 and 1008. The purpose of this meeting is to respond to questions and to provide any additional instruction to Proposers on the submission of their proposal. Proposal must attend the mandatory Proposer’s Conference in order for their proposal to be considered for an award. Any changes to the proposal as a result of the Proposer’s Conference shall be issued in the form of an Amendment which will be sent to all recipients of the initial RFP. If you think you need accommodations, contact Agent.

2.6. Oral Presentations, Product Demonstrations and Proposer Location Site Visits (Pre Award):

The University at may require oral presentations, product demonstrations and/or proposer location site visits to validate information submitted with the proposals. Failure of a proposer to conduct a presentation on the date scheduled or allow an on-site/proposer site visit may result in rejection of the proposal. These events cannot be used as an opportunity to alter proposals submitted.

Demonstrations will be held October 26, 2019. You will be notified if the UW would like see a demonstration of your product. The invitation will provide the location and time of the meeting.

2.7. Clarifications and/or Revisions through Designated Contact:

All communications and/or questions in regard to this request must be in writing and must reference the proposal number. Proposers are encouraged to e-mail written questions to the Agent. Verbal questions when permitted must be directed to the Agent.

If a Proposer discovers any significant ambiguity, error, conflict, discrepancy, omissions or other deficiency in this RFP, they have five (5) business days after the RFP issue date and time to notify, in writing, the Agent at the address shown below of such error and request modification or clarification of the RFP document.

ADMINISTRATIVE:

Todd Pooler

UW Purchasing

21 N Park St, Suite 6101

Madison, WI 53715-1218

E-mail: todd.pooler@wisc.edu

PHONE (608)263-3224 – FAX 608/262-4467

If a Proposer fails to notify the Purchasing Office of an error in the RFP document which is known to the Proposer, or which must have reasonably been known to the Proposer, then the Proposer shall submit a response at the Proposer’s risk and if awarded a contract, shall not be entitled to additional compensation or time by reason of the error or its later correction.

In the event that it becomes necessary to provide additional clarifying data or information, or to revise any part of this RFP, supplements or revisions will be posted on http://vendornet.state.wi.us and publicnotices.wi.gov.

Any contact with University employees concerning this RFP are prohibited, except as authorized RFP manager during the period from date of release of the RFP until the intent to award is released. Contacting anyone other than the Designated Contacts(s) above may disqualify your RFP.

2.8. Multiple Proposals:

Proposers who wish to submit more than one proposal may do so, provided that each proposal stands alone and independently complies with the instructions, conditions and specifications of the request. If multiple responses are submitted, the University reserves the right to select the most advantageous proposal to the University.

2.9. Proprietary Information:

Any information contained in the Proposer’s response that is proprietary must be detailed separately on form DOA-3027. Marking of the entire response as proprietary will neither be accepted nor honored. The University cannot guarantee that all such material noted remains confidential, particularly if it becomes a significant consideration in contract award. Information will only be kept confidential to the extent allowed by State of Wisconsin Public Disclosure Law (refer to Standard Terms and Conditions, Section 27.0). A copy of the form needed to designate portions of your submission as proprietary can be found at: http://vendornet.state.wi.us/vendornet/doaforms/doa-3027.doc

2.10. Appeals Process:

Any protest of the University's solicitation or intent to award must be based on an alleged violation of the Wisconsin State Statute or a provision of a Wisconsin Administrative Code.

No later than five working days after the date of solicitation or the notice of intent to award is issued by the University, written notice of intent to protest must be received by:

The Office of the Chancellor

The University of Wisconsin-Madison

500 Lincoln Drive

Madison, Wisconsin 53715-1218

With a copy to:

Director of Purchasing Services

University of Wisconsin-System

780 Regent Street, Suite 105

Madison, Wisconsin 53715-1218

The complete protest must be received by the Chancellor and the Director of Purchasing Services no later than ten working days after the date of solicitation or the intent to award is issued. The protest must be in writing. Protesters must make their protests as specific as possible and must specifically identify the Wisconsin State Statute and/or State of Wisconsin Administrative Code provision(s) allegedly violated.

The decision of the University regarding the protest may be appealed to the Secretary of the Department of Administration within five working days after denial by the University, with a copy of such appeal filed with the University.

3. Terms and Conditions of Contract

3.1. Entire Contract:

A contract will be awarded based on the criteria established in this Request for Proposal, including attachments and any amendments issued. The RFP, the proposal response, and written communications incorporated into the contract constitute the entire contract between the parties. The hierarchy of documents in descending order for resolution is as follows:

A. Contract Award Letter B. Original Request for Proposal Number 19-5934 dated, 8/30/2018 including amendments/attachments C. Proposer response to RFP D. Official Purchase Order (when applicable) Any other terms and conditions provided by the Proposer with the proposal or for future transactions against this contract, including but not limited to click on agreements accepted by the Customer; shrink wrapped agreements; or terms submitted with quotations, order acknowledgements, or invoices; will be considered null and void and will not be enforceable by the Contractor unless agreed to in a written amendment signed by the University Purchasing Department. Any exceptions to this RFP should be submitted with your response and alternative language proposed.

Deviations and exceptions from original text, terms, conditions, or specifications shall be described fully, on the bidder's/proposer's letterhead, signed, and attached to the proposal response as an attachment. Each deviation and exception must be identified by the section, page and paragraph to which it applies. In the absence of such statement, the bid/proposal shall be accepted as in strict compliance with all terms, conditions, and specifications and the bidder/proposer shall be held liable.

Submitting a standard Proposer contract or term and condition as a complete substitute or alternative for the language in this solicitation will not be accepted and may result in rejection of the proposal.

The University reserves the right to negotiate contractual terms and conditions or reject the Proposer‘s response and proceed to the next qualified proposer.

3.2. Contract Administrator:

Any correspondence must include reference to Contract number 19-5934 and be sent to the Contract Administrator. The Contractor Administrator is authorized to give the approvals required under this contract on behalf of the University.

A. University The Contract Administrator for the University is:

Todd Pooler

University of Wisconsin-Madison

Purchasing Services

21 N Park St, Suite 6101

Madison, WI 53715-1218

E-mail: todd.pooler@wisc.edu

PHONE (608)263-3224 – FAX 608/262-4467

3.3. Term of Contract:

It is the intent of the University to start the resulting Contract upon successful negotiations. The contract shall be effective on the contract execution date and shall run for three (3) years from that date, with an option to renew for Two (2) additional One (1) year periods.

This contract shall automatically be extended into its fourth and fifth years unless the Contract Administrator is notified in writing by the Contractor; or the Contractor is notified by the Contractor Administrator in writing 30 calendar days prior to expiration of the initial and/or succeeding contract term(s). Contract Termination

3.3.1. The University may terminate the Contract at any time, without cause, by providing 30 days written notice to the Contractor. If the Contract is so terminated, the University is liable only for payments for products provided or services performed, to the extent that any actual direct costs have been incurred by the Contractor pursuant to fulfilling the contract. The University will be obligated to pay such expenses up to the date of the termination.

3.3.2. Shall either party fail to perform under the terms of this Contract; the aggrieved party may notify the other party in writing of such failure and demand that the same be remedied within 30 calendar days. Should the defaulting party fail to remedy the same within said period, the other party shall then have the right to terminate this Contract immediately. Performance failure can be defined but not limited to excessive down time or failure to provide any of the Terms, Conditions or Specifications.

3.3.3. If at any time the Contractor performance threatens the health and/or safety of the University, its staff, students or others who may be on campus, the University has the right to cancel and terminate the Contract without notice.

3.3.4. Failure to maintain the required Certificates of Insurance, Permits and Licenses shall be cause for Contract termination. If the Contractor fails to maintain and keep in force the insurance as provided in Standard Terms and Conditions, Section 22.0, the University has the right to cancel and terminate the Contract without notice.

3.3.5. If at any time a petition in bankruptcy shall be filed against the Contractor and such petition is not dismissed within 90 calendar days, or if a receiver or trustee of Contractor's property is appointed and such appointment is not vacated within 90 calendar days, the University has the right, in addition to any other rights of whatsoever nature that it may have at law or in equity, to terminate this contract by giving 10 calendar days’ notice in writing of such termination.

3.3.6. All notices of performance failure must be submitted in writing to Purchasing, 21 N Park St, Suite 6101, Madison, WI 53715-1218. Purchasing shall be final authority for all performance failure determinations not resolved through the ordering department.

3.4. Orders:

Under this contract, Specific order(s), Contract blanket order(s), or Purchasing Card orders (defined below) may be issued to the Contractor(s).

3.4.1. Specific order(s): issued as one-time orders

3.4.2. Contract blanket order(s): issued for a specified period of time to allow departmental personnel to issue releases against the Contract blanket order(s) as needed.

3.4.3. Purchasing Card order(s): issued as one-time order(s).

3.5. Firm Prices:

Prices remain firm for the initial contract term. Prices established may be lowered due to general market conditions or negotiations between the Contractor and the University.

Prices increase requests proposed after the initial Contract term, along with an updated Price List, must be received by Purchasing in writing 60 calendar days prior to the beginning of the next contract term for acceptance or rejection. Proposed price increases are limited to fully documented cost increases submitted with the request. If Purchasing deems cost increases are not acceptable, it reserves the right to rebid the contract in whole or part.

Price increases must be labeled with the contract number and be submitted in the same format as the original Proposal. Any price increase requested that is not submitted in the proper format may be rejected.

Contractor should promptly notify Purchasing of new or discontinued items.

3.6. Payment Terms:

The University will pay the Contractor based upon the following payment plan.

1) 30% of Vendor’s bid price for implementation of software, net 30 days from the receipt of a valid Invoice.

2) The UW shall have 30 days from the notification by the Vendor that the software is 100% functional to conduct testing of the system. Once approval is given by the UW, Vendor shall submit and invoice for the balance of the implementation fee. UW will pay net 30 days from the receipt of a valid invoice.

3) All other fees will be billed in arrears and will be paid net 30 days from the receipt of a valid invoice.

3.7. Invoicing Requirements:

Invoices for Purchase Orders:

3.7.1. Contractor must agree that all invoices and purchasing card charges shall reflect the prices and discounts established for the items on this contract for all orders placed even though the contract number and/or correct prices may not be referenced on each order.

The University must meet a statutory mandate to pay or reject invoices within 30 days of receipt by University Accounts Payable. Before payment is made, it also must verify that all invoiced charges are correct as per this Contract. Only properly submitted invoices will be officially processed for payment. Prompt payment requires that your invoices be clear and complete in conformity with the instructions below. All invoices must be itemized showing:

· Contractor name

· Remit to address

· Purchase order number

· Release number if given

· Period being billed

· Prices per the Contract

· Any non-reoccurring cost must be itemized to a level that the UW can easily understand what is being billed for.

At the discretion of Purchasing, invoices not reflecting the correct discount or net prices may be short paid or disputed.

The original invoice must be sent to University Accounts Payable, 21 N Park St, Suite 5301, Madison, WI 53715-1218.

Purchasing Card:

Order confirmation shall contain the same detail as listed in Section 3.7.1 and should be sent to the address given at the time of the order is placed.

Any fees charged for use of the University’s purchasing card program are not allowed.

3.8. F.O.B. Destination:

All deliveries shall be FOB Destination. Delivery charges and risk of loss shall be borne by the Contractor. IF any product needs physical delivery, it shall be made by common carrier or Contractor’s truck, with unloading to be performed by the carrier/contractor and carton(s) transported to the interior/ground floor or inside dock at various locations. Proposal prices must include all packing, freight, insurance charges and installation/operation manuals, excluding any import/export costs.

If bidding other than F.O.B. Destination, as stated, F.O.B. point and shipping charges must be identified on the Cost Proposal form. This additional cost will be added to the proposal total and will serve as the basis for determining the award.

Indicate on the Cost Proposal Form the Country of Origin and Shipping Point.

Failure to bid FOB DESTINATION delivery charges and risk of loss borne by the Contractor in proposal price or discount may disqualify your proposal.

In carrying out the scope of this Contract, the Contractor shall be required to perform services on University property. Proposers cost must include all transportation charges.

3.9. Requirements for Criminal Background Checks:

Background Checks of Contractors This contract is contingent upon, Contractor supplying workers who have passed a criminal background check that includes a national criminal background check database demonstrating the worker has no convictions or pending criminal charges that are substantially related to the contracted-for activities or services, including but not limited to, those that would render the worker unsuitable for regular contact with children. Disqualifying convictions or charges include, but are not limited to, sexual offenses, violent offenses, and drug offenses.

If, in the course of providing services to the UW, Contractor (or its employee) observes an incident or threat of child abuse or neglect, or learns of an incident or threat of child abuse or neglect, and the Contractor (or its employee) has reasonable cause to believe that child abuse or neglect has occurred or will occur, Contractor must make a report of that abuse or neglect to law enforcement or to a county social service agency as provided in UW’s Policy on Mandatory Reporting of Child Abuse and Neglect (“the Policy”). If the suspected child abuse or neglect involves an allegation against a UW employee or agent (e.g. student, volunteer, Contractor, etc.), or the incident or threat of child abuse or neglect occurred on the UW campus or during a UW-sponsored activity, the Contractor shall also report to the UW Police Department or UW’s Office for Equity and Diversity.

3.10. Travel Per Diems:

All of the Contractor’s travel and per diem expenses shall be the Contractor’s sole responsibility. Payment to the Contractor by the University shall not include an additional amount for this purpose.

3.11. Campus Delivery Requirements:

3.11.1. Delivery of orders shall be made to the University departments five days per week, Monday through Friday, during normal University business hours.

3.11.2. The University of Wisconsin-Madison no longer permits access to trucks over 30 ft. in length on several designated streets on this campus. The exceptions are trucks necessary for the delivery or pick up of perishable commodities, private construction vehicles, vehicles carrying radioactive materials, and campus service vehicles. For specific policy language, a campus map and restrictions, see the University Transportation Services website at http://transportation.wisc.edu/resources/large_truck.aspx.

3.11.3. This contract requires that Contractor deliver goods to the stated delivery address in accordance with the 30’ truck policy referenced in Section 3.13.2 above. Any unique delivery arrangements must be pre-approved by contacting the ordering department or Material Distribution Services (MDS) at (608) 497-4432. MDS reserves the right to charge Contractor reasonable material handling fees for any deliveries they make for the Contractor.

3.12. Acceptance and Test (Post Award):

Acceptance testing will occur within 30 days after the item/service has been installed. Acceptance testing will be performed by the University and will consist of verification of the specifications and performance requirements.

If the item/service does not meet specification or performance requirements, the Contractor will have 10 days to meet requirements. If after this time period the item/service still does not meet specifications or performance requirements, the Contractor agrees to remove the item and return any payments that may have been made.

Bill Curtis, or his designee, is the only authorized person who can sign an acceptance form. The warranty period will begin following the successful acceptance testing.

3.13. Insurance:

The Contractor shall maintain the following insurance levels:

Vendor Provide Certificate of Insurance demonstrating primary coverage-Workers Compensation (WC): Required for all Contracts NO EXEMPTIONS Commercial General Liability (CGL):

General Aggregate including Products and Completed Operations & Professional Liability $2,000,000 Each Occurrence $1,000,000 Automobile Liability Combined Single Limit $1,000,000 Cyber Liability (including Security & Privacy, PCI-DSS Assessments) * $2,000,000 *This coverage may be provided via a separate policy or under the vendor’s/contractor’s Commercial General Liability (CGL) insurance policy granted the CGL policy does not exclude coverage for cyber breaches/events/liability. Coverage may be provided in any combination of primary and Excess/Umbrella limits totaling the required amounts of coverage.

A certificate of insurance must be provided upon award. The Contractor shall add: “The Board of Regents of the University of Wisconsin System, its officers, employees and agents as an ‘additional insured’ under the commercial general, automobile and Contractor's liability policies." The certificate holder shall be listed as the University of Wisconsin-System Administration or System campus for their respective purchases.

3.14. Activity Reports:

Contractor must be able to report on monthly basis all items/services purchased against this contract during the designated report period, including but not limited to:

· Date of order/release

· Item manufacturer’s name or abbreviation (if applicable)

· Complete item description including catalog, model and/or stock number(s) identical to those stated in proposal

· Prices per the Contract

3.15. Record and Audit:

The Contractor shall establish, maintain, report as needed, and submit upon request records of all transactions conducted under the contract. All records must be kept in accordance with generally accepted accounting procedures. All procedures must be in accordance with federal, State of Wisconsin and local ordinances.

The University shall have the right to audit, review, examine, copy, and transcribe any pertinent records or documents held by the Contractor related to this contract. The Contractor shall retain all applicable documents for a period of not less than five years after the final contract payment is made. The University reserves the right to inspect any facilities used to support this Contract.

3.16. Performance Meetings:

The Account Representative and/or Proposer Contract Administrator must be available to meet as required with the University's Contract Administrator to evaluate contract implementation and performance and to identify continuous improvement.

3.17. Subcontracting:

3.17.1. Any Contract resulting from this proposal shall not be, in whole or in part, subcontracted, assigned, or otherwise transferred to any Subcontractor without prior written approval by Purchasing. Upon request Contractor must provide Subcontractor’s complete contact information including EIN# (TIN#, SS#) and signed W-9 form.

3.17.2. The Contractor shall be directly responsible for any subcontractor's performance and work quality when used by the Contractor to carry out the scope of the job. University reserves the right to assess Contractor damages in excess of the contract amount for Subcontractor’s failure to perform or inability to complete required project milestones.

3.17.3. Subcontractors must abide by all terms and conditions under this Contract.

3.18. Fair Price Analysis:

Purchases made under this contract may require further fair price analysis. The awarded Proposer will be required to provide documentation (i.e. published price list, list of previous buyers, etc.) to allow the University to complete this analysis.

3.19. Severability:

If any provision of this contract shall be, or shall be adjudged to be, unlawful or contrary to public policy, then that provision shall be deemed to be null and separable from the remaining provisions, and shall in no way affect the validity of this contract.

3.20. Environmentally Friendly (“Green”) Product:

Contractors are encouraged to identify products that are made of recycled products, that use environmentally friendly production methods, or that can be recycled at the end of their service life. The UW will make every effort to purchase “Green” products wherever feasible or possible based on individual project needs and funding available.

3.21. Supplier Diversity:

3.21.1. Minority Business Enterprise Program (MBE)

The State of Wisconsin is committed to the promotion of minority business in the state's purchasing program and a goal of placing 5% of its total purchasing dollars with certified minority businesses. Authority for this program is found in ss. 15.107(2), 16.75(4), 16.75(5) and 560.036(2), Wisconsin Statutes. The University of Wisconsin-Madison is committed to the promotion of minority business in the state's purchasing program.

The State of Wisconsin policy provides that Wisconsin Certified minority-owned business enterprises should have the maximum opportunity to participate in the performance of its contracts. The supplier/contractor is strongly urged to use due diligence to further this policy by awarding subcontracts to minority-owned business enterprises or by using such enterprises to provide goods and services incidental to this agreement, with a goal of awarding at least 5% of the contract price to such enterprises.

The Supplier/contractor may be requested to provide information about its purchases from Wisconsin certified MBEs.

A listing of certified minority businesses, as well as the services and commodities they provide, is available from the Department of Administration, Office of the Minority Business Program, 608/267-7806. To view all MBE firms go to https://wisdp.wi.gov/search.aspx select the MBE box and click search.

3.21.2. Woman Owned Business (WBE)

The State of Wisconsin is committed to the promotion of Woman-Owned Businesses as outlined in 560.035, Wisconsin Statutes.

The State of Wisconsin policy provides that Woman-Owned Businesses certified by the Wisconsin Department of Commerce should have the maximum opportunity to participate in the performance of its contracts. The supplier/contractor is strongly urged to use due diligence to further this policy by awarding subcontracts to Woman-Owned Businesses or by using such businesses to provide goods and services incidental to this agreement.

3.21.3. Disabled Veteran Owned Business (DVB)

The State of Wisconsin policy provides that Disabled Veteran-Owned Business Enterprises certified by the Wisconsin Department of Administration should have the maximum opportunity to participate in the performance of its contracts. The supplier/contractor is strongly urged to use due diligence to further this policy by awarding subcontracts to Disabled Veteran-Owned Businesses or by using such enterprises to provide goods and services incidental to this agreement, with a goal of awarding at least 1% of the contract price to such enterprises.

The supplier/contractor may be requested to provide information about its purchases from Wisconsin certified DVBs.

A listing of certified minority businesses, as well as the services and commodities they provide, is available from the Department of Administration, State Supplier Diversity Program, 608/267-9550. To view all DVB firms, go to https://wisdp.wi.gov/search.aspx, select the DVB box, and click search.

3.22. Discriminatory Boycotts of Israel:

Effective October 27, 2017, consistent with 2017 Wisconsin Executive Order 261, contractor agrees it is not engaged in a boycott of the State of Israel and further, contractor will not during the term of the contract engage in a boycott of the State of Israel. State agencies may not execute a contract and reserve the right to terminate an existing contract with a business entity that is not complaint with this provision. This provision applies to all contracts of all values.

3.23. Debarment:

Federal Executive Order (E.O.) 12549 “Debarment“ requires that all contractors receiving individual awards, using federal funds, and all sub recipients certify that the organization and its principals are not debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded by any Federal department or agency from doing business with the Federal Government. By signing this document you certify that your organization and its principals are not debarred. Failure to comply or attempts to edit this language may disqualify your bid. Information on debarment is available at the following websites: www.sam.gov and https://acquisition.gov/browsefar.

3.24. Electronic Commerce/Online Ordering:

Customers of this contract may want to take advantage of electronic ordering and “E-Commerce” opportunities that may be offered by the Contractor. All electronic orders shall receive contract pricing and/or discounts.

3.25. Promotional Materials/Endorsements:

Contractor agrees that they will not use any promotional or marketing material which states expressly or implies that the University endorses either the Contractor or any party related to the Contractor or this Contract.

3.26. Additional Items/Services:

Similar items/services may be added to this Contract provided it was mutually agreeable to both Purchasing Services and the Contractor. Scope of work and pricing (including discounts) must be consistent with the current contract items/services.

4. Requirements and Specifications Requirements that include the word “must” or “shall” describe a mandatory requirement. Failure to meet a mandatory requirement may disqualify your proposal.

Proposer must: 1) indicate agreement on each mandatory requirement and, if requested, describe how the specifications will be met and/or provide additional information, 2) complete any required form(s) and 3) provide a complete and detailed response to any non-mandatory requirement that can be fulfilled. If supplemental materials will be provided, clearly mark all supplements with the corresponding section number.

NOTE: Failure to respond to all items in this section may be deemed as sufficient reason to reject a proposal. Format your response to correspond numerically with items on the Submittal Instruction (see Section 2.3.). Mandatory Requirements

4.1. Qualifications and Company History: (100 Points)

Describe the company's experience and capabilities providing Emergency Alert Notification Systems. Include specific examples of similar scope and complexity.

4.2. Mandatory Requirements: (Mandatory)

4.2.1 Purchased Services – USA Requirement

The State of Wisconsin requires purchased contractual services to be performed in the United States. Some exceptions apply, including procurements subject to the conditions of the World Trade Organization Government Procurement Agreement (WTOGPA) and those listed in (Wis. Stats. 16.705 (1r). Subject to these exceptions, Contractor warrants that the services provided to the University under this contract will be performed in the United States. The inability to perform required services in the United States shall be grounds for disqualifying your proposal for this contract.

4.2.2.Other state universities, campus departments, and agencies must be able to use the contract. Do you agree to this requirement?
4.2.3The system must be cloud based and not require any equipment or software to be installed (except for a quick send feature or administrative smartphone app).
4.2.4Your system must have the ability to manage and send to an estimated 100,000 emails and an estimated 40,000-60,000 cell phone numbers. Please describe how you will comply with this requirement.

4.3. General Requirements: (125 Points)

4.3.1The system should have an administrative software program that could be installed on a computer to minimize data needs (when using cellular connection) and/or provide quicker processing. If you do not have this feature explain how your system will provide the same functionality.
4.3.2The system must be fault tolerant as demonstrated by uptime figures showing continuous operation with downtime at or approaching zero. The system should be run from geographically disparate data centers that allow continuous operation in case of datacenter or infrastructure provider failure (e.g. natural disaster, cyber-attack, widespread DNS outage, etc.). In your response please provide supporting detail of how you compile with this requirement, including how you replicate, your Disaster recovery system, your Hosting infrastructure, etc.
4.3.3The system should demonstrate compliance or a roadmap towards compliance with Section 508. The UW must implement a product that is Section 508 compliant due to federal funding requirements. In your response either provide documentation proving compliance or a roadmap with dates and deliverables of when you will be compliant.
4.3.4The system should be compliant with WCAG 2.0 at an AA level (https://www.state.gov/documents/organization/126552.pdf) accessibility standards to accommodate end users with disabilities. Provide a VPAT demonstrating compliance (https://www.state.gov/documents/organization/126555.pdf). If you are not compliant, please provide a roadmap with dates and deliverables of when you will be compliant.
4.3.5The system should be able to integrate with SAML 2.0 or similar (e.g. OAuth 2.0) single sign-on authentication protocols. Describe your ability to meet this requirement.

4.4. Capabilities/Functionality: (250 Points)

4.4.1The system must be able to send to the following channels: SMS text, email, Facebook, and Twitter. Please explain how you will comply with this requirement.
4.4.2The system must support the Common Alerting Protocol (CAP), including the ability to configure channels that send CAP messages as POST requests to one or more configured HTTP endpoints. Please explain how you system will comply with this requirement.
4.4.3The system must provide one or more ways for web developers to integrate and display emergency messages on websites. Please explain what options and functionality are available.
4.4.4The system must provide access to FEMA's IPAWS system. UW-Madison is authorized to use IPAWS. How will your system comply with this requirement?
4.4.5The system should be able to send to the following channels: Instagram, Snapchat, and other emerging social media channels. Please list the channels that you currently can integrate with and include a roadmap outlining any channels planned for inclusion.
4.4.6The system must be able to integrate with computer desktop pop ups, digital sign boards, and TVs and display the emergency messages. Please describe how your system with comply with this requirement. List any limitations.
4.4.7The system should be able to integrate with building PA systems. Describe your ability to comply with this feature.
4.4.8The system should have the ability to send to all campus VOIP phones and utilize the speaker function and/or display the message. Explain how your system provides this functionality.

This is the start of the file's text. The full file is on GovTribe.

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