FACSIMILE TRANSMISSION COVER LETTER

Report as inappropriate Your report has been received

Shared by: hedongchenchen

Tags

FACSIMILE TRANSMISSION, COVER SHEET, cover page, the Court, FAX NUMBER, Cover Letter, Superior Court, Filing fee, Legal Forms, Telephone Number

Stats

views:: 3
posted:: 8/18/2011
language:: English
pages:: 41

Public Domain

Document Sample

VENDOR NET TRANSMISSION COVER LETTER

DATE: July 20, 2010

When using Vendor Net, you may submit your proposal through one of the following options: U.S. mail, hand-
delivery, fax or e-mail. Refer to “SUBMITTAL INSTRUCTIONS”. Regardless of the option used, your proposal
must be received and time stamped in by Purchasing Services, 21 N Park St, Suite 6101, Madison, WI 53715-
1218, prior to 2:00 PM on the proposal due date to be considered on time. Proposals not so stamped shall be
considered late. Late proposals shall be rejected.

If you have any questions concerning these instructions, please contact the University of Wisconsin-Madison
Purchasing Services (Bid Processing) at (608) 262-6121.

PURCHASING SERVICES
University of Wisconsin-Madison  21 N Park St, Suite 6101 Madison, WI 53715-1218
608/262-6121  (Fax) 608/262-4467  www.bussvc.wisc.edu  bids@bussvc.wisc.edu
A REQUEST FOR PROPOSAL (RFP)

RFP #11-5270

AGENT: Charlie Simonson at (608) 265-0656 / FAX: (608) 262-4467

E MAIL: csimonson@fpm.wisc.edu

If NO BID (check here) and return.

UNIVERSITY OF WISCONSIN – Madison

ACCESS AND REVENUE CONTROL HARDWARE AND SOFTWARE

Issued by:
STATE OF WISCONSIN
UNIVERSITY OF WISCONSIN - MADISON
PURCHASING SERVICES

Issue Date: July 20, 2010

NO PUBLIC OPENING
Proposals must be submitted by
August 9, 2010 - No later than 2:00 p.m. CDT
NOTE TO PROPOSERS: Written questions due July 27, 2010. Site Visit is
scheduled for July 29, 2010. See Section 2.2 for details.

NOTE: This is a COMPLETE REBID of 11-5259.

COMPANY NAME: _________________________________________________________________________________________________

A completed and signed proposal response must be received and date/time stamped in by UW-Madison Purchasing
Services prior to 2:00 p.m. CDT on the stated proposal due date to be considered. Proposals not so date/time stamped
in shall be considered late. Late proposals shall be rejected. We have supplied you with a pre-addressed return
label. Please fill in your vendor name and address on the return label to help us identify this transaction. Please use
one of the options below for return of your proposal.

MAILING:
Original and (# of copies) (#) copies of mailed proposals must be received at Purchasing Services, 21 N. Park Street,
Suite 6101, Madison, WI 53715-1218, prior to 2:00 p.m. CDT on the stated proposal due date.

HAND DELIVERY:
Original and (# of copies) (#) copies of hand-delivered proposals may be delivered by vendor or third-party/courier
service. Proposals must be received at Purchasing Services, 21 N. Park Street, Suite 6101, Madison, WI 53715-1218,
prior to 2:00 p.m. CDT on the stated proposal due date.

FAXING:
For your faxed proposal to be considered valid by UW-Madison Purchasing Services:
1. A complete copy of the entire transmitted response must be received at Purchasing Services prior to 2:00 p.m.
CDT on the stated proposal due date. FAX: (608) 262-4467 (AVAILABLE 24 HOURS A DAY).

2. Original and (FIVE copies) (5) copies to be delivered (via hand delivery, mail or courier) within one (1) business day
after the stated proposal due date must be received at Purchasing Services, 21 N. Park Street, Suite 6101, Madison, WI
53715-1218.

E-MAILING:
For your e-mailed proposal to be considered valid by UW-Madison Purchasing Services:
1. Send a complete copy of the entire response prior to 2:00 p.m. CDT on the stated proposal due date via e-mail to:
bids@bussvc.wisc.edu. Submitting a proposal to any other e-mail address than bids@bussvc.wisc.edu does not
constitute receipt of a valid proposal by Purchasing Services.

Prior to the proposal deadline, proposer is responsible for confirming that their e-mailed proposal response has been
successfully received. Proof of transmission doesn't constitute proof of receipt. The original e-mail submission must be
supported by the last page of Section 6 “RFP Checklist and Submittal Page”. This page must be signed and returned via
fax (608-262-4467) and must be received prior to 2:00 p.m. CDT on the proposal stated due date.

RETURN ADDRESS LABEL:


OFFICIAL SEALED PROPOSAL
NUMBER: 11-5270
DUE DATE: 07/01/10 TIME: 2:00 PM CDT
NO PUBLIC OPENING
INSERT
VENDOR NAME HERE: ______________________________________
ADDRESS: ________________________________________________
________________________________________________
________________________________________________

UNIVERSITY OF WISCONSIN-MADISON
PURCHASING SERVICES
21 N PARK ST, SUITE 6101
MADISON, WI 53715-1218
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270

TABLE OF CONTENTS
PAGE(S)
Section #1: General Information 1-4
1.1 Purpose
1.2 Organization of this Solicitation Document
1.3 Definitions
1.4 Incurring Costs
1.5 Affirmative Action
1.6 Wisconsin Sales and Use Tax Registration
1.7 Debarment
1.8 VendorNet
1.9 Electronic Commerce/Online Ordering
1.10 Campus Delivery Requirements
1.11 Parking
1.12 Smoking Free Environment
1.13 Promotional Materials
1.14 Energy Star

Section #2: RFP Process Instructions 5-6
2.1 Applicable Dates
2.2 Proposer Site Visit
2.3 Clarifications and/or Revisions through Designated Contact
2.4 Preparing the Proposal
2.5 Conflict of Interest
2.6 Multiple Proposals
2.7 Oral Presentations and Site Visits
2.8 Proprietary Information
2.9 Reasonable Accommodations

Section #3: Performance and Contract Requirements 7-11
3.1 Contract Terms and Conditions
3.2 Scope
3.3 Term of Contract
3.4 Firm Prices
3.5 Payment Terms
3.6 Invoicing Requirements
3.7 Acceptance and Testing
3.8 Title And Shipping Terms
3.8.1 F.O.B. Destination Freight Prepaid Included and Installed for the INITIAL TWO INSTALLATIONS
3.8.2 F.O.B. Destination, Freight Prepaid and Allowed (vendor responsible for freight costs)for Subsequent Orders
For Repair Parts
3.8.3 Country of Original and Custom Duty Costs
3.9 Insurance
3.10 Travel Per Diems
3.11 Contract Termination
3.12 Eligible Purchasers
3.13 Fair Price Analysis
3.14 Subcontractors
3.15 Executed Contract to Constitute Entire Contract
3.16 Severability
3.17 Environmentally Friendly (“Green”) Product

Section #4: Requirements of All Proposals 12-13

Section #5: Evaluation and Award of Contract(s) 14
5.1 Proposal Scoring
5.2 Scoring Criteria and Method
5.3 Best and Final Offers
5.4 Contract Award
5.5 Notification of Award

Section #6: RFP Checklist and Submittal Page 15-17
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270

TABLE OF CONTENTS

PAGE(S)

Attachment A – Mandatory Specifications 18-19
Attachment B – Desired and Value Added Specifications 20-26
Attachment C – Cost Proposal Form 27-28
Attachment D – Client Reference List 29
Attachment E – Supplier Diversity, Minority Business Enterprise (MBE) Program Commitment 30
Attachment F – Standard Terms and Conditions 31-35
Attachment G - Certification of Site Visit 36
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 1 OF 36

Section #1: General Information
Requirements that include the word "must" or "shall” describe a mandatory requirement. All specifications are defined as
mandatory minimum requirements unless otherwise stated. If no proposer is able to comply with a given specification or
mandatory requirement, Purchasing reserves the right to delete that specification or mandatory requirement. FAILURE TO
MEET A MANDATORY REQUIREMENT MAY DISQUALIFY YOUR PROPOSAL. This Proposal document and the
awarded proposer’s (Contractor’s) response information shall become the Contract.

1.1 Purpose
The University of Wisconsin-Madison, hereinafter referred to as the “University”, through its Purchasing Services
Department, hereinafter referred to as “Purchasing”, is requesting proposals for Facilities Planning and
Management Transportation Services, hereinafter referred to as “FP&M”, for the purchase of integrated parking
gate access and revenue control hardware and electronic systems.

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.

The purposes of this request for proposal are:

1. Purchase replacement access and revenue control systems at three University parking structures,
2. Purchase an initial access and revenue control systems at one University parking structure,
3. Purchase parking and transportation services management software that is fully integrated with gates, ticket
dispensers and payment systems, and
4. Establish a contract for potential future access and revenue control systems at existing and/or new parking
facilities.

The scope of this project includes complete replacement of any existing gate access and revenue control systems
(hardware, software and electronic control system components) and the installation of new gate systems where
none currently exist. The awarded Contractor shall be responsible for designing, providing and installing the gate
system components, start-up operations and repair services, and on-going training and technical support.

UW-Madison Parking Structure Equipment Upgrade Possibilities

Lot # Physical Stall Count Lot Enforcement Type Entry Columns Exit Columns

6 LL 95 one 36”X72” booth 1 1
6 UL 98 one 52”X76” booth 1 1
7 410 two 74”X109” booths 2 2
one 72”X108” booth, one
17 859
66”X90” and an office 2 2
20 220 one 65”X90” booth 1 1
23 44 N/A 1 1
27 80 under construction 1 1
29 344 office, no booths 2 2
36 463 N/A 1 1
38 146 N/A 1 1
41 173 N/A 0 0
46 747 two 72”X48” booths 2 2
76 1283 N/A 2 2
79 227 N/A 1 1
80 182 under construction 1 1
83 299 one 66”X90” booth 1 2
95 227 N/A 1 1
Totals 5897 21 22
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 2 OF 36

The supplied hardware and electronic components will replace the current equipment at Lot 17, Lot 20, and Lot 83.
New hardware and electronic components will be installed in Lot 76 where none exist. In addition, the supplied
software will provide centrally managed access and revenue control at Lot 17, 20, 76 and 83. Potentially, similar
hardware and software will be installed at other campus parking facilities during the next five years. Equipment
installation must take place while maintaining normal operating hours and functions. The current hours of operation
are Monday-Sunday from 7:00 am-10:00 pm.

The goals of the new system are: reliability, integrated revenue management, integrated access controls, increased
fraud prevention, and extensibility to manage other transportation service programs such as employee parking
permits, parking enforcement, special events, accounts receivable, and interface with University payroll services.
Distributed gate access and revenue controls must be centrally administered through access and revenue control
software. Distributed gate access controls must be accessible and controllable from the central office location even
while distributed access and revenue control is maintained. Payment architecture should use a central cashiering
pay-on-exit model where appropriate but may also use pay stations and cashless validations. Gate access and
revenue controls must include the capability of using generic Class 1 Generation 2 UHF Air Interface Protocol
Standard (“GEN 2”) readers and tags developed by the University.

The University anticipates a single-vendor solution but the University may choose to make multiple awards. The
awarded contractor or contractors must be able to provide detailed system design, planning, implementation, project
management, oversight, training, support and maintenance for all hardware and software as per specifications.

For more information about University Transportation Services go to their website http://www2.fpm.wisc.edu/trans/

1.2 Organization of this Solicitation Document
This document is divided into Six main sections. The sections also refer to “Attachments” when such organization
assists in making this document more fluid. The six main sections are:

Section 1 General Information (generally states the intent of the solicitation)
Section 2 Instructions to Proposers (contains Information on the proposal process)
Section 3 Performance and Contract Requirements (contains performance clauses that will become part of any
awarded contract).
Section 4 Requirements of All Proposals (contains all information Proposers must submit as part of their
proposal).
Section 5 Evaluation (contains detail on the evaluation of proposals)
Section 6 Checklist and Signature Page (contains check-off list)

1.3 Definitions
The following definitions are used throughout the Special Conditions of Proposal:

Agent means UW Madison Purchasing Agent responsible for this Request for Proposal. Full contact information
can be found in Section 2.3.
Contractor means successful proposer awarded the proposal.
Department means UW Madison Facilities Planning and Management Transportation Services, hereinafter referred
to as “FP&M”,
MBE means Minority Business Enterprise.
Purchasing card means State credit card.
Proposer means a firm submitting a Proposal in response to this Request for Proposal.
RFP means Request for Proposal.
State means State of Wisconsin.
University means University of Wisconsin-Madison.

1.4 Incurring Costs
The State of Wisconsin is not liable for any cost incurred by proposers in replying to this RFP.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 3 OF 36

1.5 Affirmative Action
As a State agency, the University requires contractors issued any purchase order exceeding $25,000.00 to provide
an Affirmative Action Plan. Failure to comply appropriately with these requirements may lead to your company
being banned from doing business with any agency of the State of Wisconsin. Additionally, failure to comply
with this requirement may result in termination of this contract and withholding of payment. On the Requirements of
All Proposals form please provide the requested information.

For additional information see section 17.0 of the Standard Terms and Conditions
(http://www.bussvc.wisc.edu/purch/stdterms1.html). Some exceptions may apply. FAQ info is available at:
http://www.bussvc.wisc.edu/purch/VendorInfo/AffAction/AffirActionInfo.html. Instructions for completing a plan are
available upon request.

1.6 Wisconsin Sales and Use Tax Registration
No award can be made to a vendor who is not in compliance with Sec. 77.66 of the Wisconsin State Statutes
(vendornet.state.wi.us/vendornet/wocc/certtax.asp) relating to sales and use tax certification.

If you have not established a certification for Collection of Sale and Use Tax status with the Wisconsin Department
of Revenue, the University and any other state agency can not issue any purchase orders to your firm. For
additional information see http://www.dor.state.wi.us/html/vendlaw.html

1.7 Debarment
Federal Executive Order (E.O.) 12549 “Debarment“ requires that all contractors receiving individual awards, using
federal funds, and all subrecipients 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. As a part of this proposal document there is debarment language
and a signature block for you to self certify your debarment status on the Requirements of All Proposals form.
Failure to supply this information may disqualify your proposal. Information on debarment is available at the
following websites: www.epls.gov and https://www.acquisition.gov/far/.

1.8 VendorNet
The State of Wisconsin has implemented a registration service on an internet system called “VendorNet” to
enable vendors to receive notice of all official sealed proposals (over $25,000.00) as solicited by all state
agencies.

To obtain information on the state’s bidder registration, please visit the VendorNet Web site at
http://vendornet.state.wi.us or call the VendorNet Information Center (1-800-482-7813). In the Madison area,
please call 264-7898.

1.9 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. If electronic ordering methods are used, the following conditions will apply:

The terms of this RFP will take precedence over any auxiliary or ancillary contract that may be accepted by any
employee of the University or State. Any terms, conditions, clauses or specifications that are not consistent with the
terms, conditions, or specifications of the RFP will be considered null and void and will not be enforceable by the
contractor unless agreed to in a written amendment format signed by the Contract Administrator. These contracts
include, at a minimum, “Wrap Around”, “Click and Wrap”, Electronic Commerce contracts, auxiliary or ancillary
service contracts, or any other additional contracts that further define or add additional service elements to the
master contract.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 4 OF 36

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

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://www2.fpm.wisc.edu/trans/policy_large_truck.asp

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

1.11 Parking
University parking is very limited. Each Contractor and/or employee(s) shall make their own arrangements for
parking through UW Transportation Services at 610 N. Walnut Street, WARF Building Room #120, Madison, WI
53726 (608) 263-6667. 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.12 Smoke-Free Environment
All University buildings are smoke-free buildings.

1.13 Promotional Materials
Contractor agrees to not use promotional or marketing material which states expressly or by fair implication that the
University endorses either the Contractor or any sponsor of such material.

1.14 Energy Star
The State encourages the use of equipment which meets the Environmental Protection Agency (EPA) Energy Star
requirements. The Energy Star Program is a voluntary contract between an Original Equipment Manufacturer
(OEM) and the EPA. It is not mandatory that every device offered meet Energy Star requirements but the bulk of
the product line should be energy efficient.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 5 OF 36

Section #2: RFP Process Instructions
2.1 Applicable Dates

Date Event

July 20, 2010 Date of Issue of the RFP

July 27, 2010 Written questions due

July 29, 2010 – 10:00 AM Proposer Site Visit

August 9, 2010 -- 2:00 PM RFP Due Date (Local Madison Time)

2.2 Proposer Site Visit
Proposer must visit the job site prior to submitting a proposal to assure themselves and the University that they
fully understand all requirements of the project. The mandatory site visit will be on July 29, 2010 at 10:00 a.m.
Please call Charlie Simonson at (608) 265-0656 to confirm your attendance at the site visit. The location for
the site visit is at 610 N. Walnut Street, Room #124, Madison, WI 53726. Failure to attend a mandatory site
visit will disqualify your proposal.

2.3 Clarifications and/or Revisions through Designated Contact
All communications and/or questions in regard to this request must be in writing and proposers are encouraged to
FAX or 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, omission, or other deficiency in this
RFP, they have five (5) business days prior to the RFP due date to notify, in writing, the Agent at the address shown
below of such error and request modification or clarification of the RFP document. All written questions will be
responded to in writing and provided to all proposers.

Charlene M. Simonson, Purchasing Manager
Facilities Planning & Management Purchasing Office
Room 101C Service Building
1217 University Ave., Madison, WI 53706-1589
Phone: 608-265-0656 / Fax: 608-262-0568
Email: csimonson@fpm.wisc.edu

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 provided to all recipients of this initial RFP.

2.4 Preparing the Proposal
To be considered, Proposers must respond to each of the requirements listed in Section #4 and per the attached
Submittal Instructions. Responses should be formatted to correspond numerically to the requirements listed in
Section #4.

2.5 Conflict of Interest
By submitting a proposal, the proposer certifies that no relationship exists between the proposer and the University
that interferes with fair competition or is a conflict of interest, and no relationship exists between such proposer and
another person or firm that constitutes a conflict of interest that is adverse to the University.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 6 OF 36

2.6 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.7 Oral Presentations and Site Visits
The University, at its sole discretion, may require oral presentations and/or site visits to supplement the proposals.
Failure of a proposer to conduct a presentation on the date scheduled may result in rejection of the proposal. Oral
presentations cannot be used as an opportunity to alter the proposals.

2.8 Proprietary Information
Any information contained in the Bidder’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.9 Reasonable Accommodations
University will provide reasonable accommodations, including the provision of informational material in an alternative
format, for qualified individuals with disabilities upon request. If you think you need accommodations for your site
visit, contact Charlie Simonson at (608) 265-0656.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 7 OF 36

Section #3: Performance and Contract Requirements
3.1 Contract Terms and Conditions
A contract will be awarded based on the criteria established in this RFP. The terms and conditions of the contract
will minimally contain:

3.1.1 The minimum contract requirements identified in this Section #3.
3.1.2 The Proposer’s commitments identified in their responses to Section #4.
3.1.3 The University Standard Terms and Conditions of Contract as provided in Attachment F.
3.1.4 A contract will be awarded based on the criteria established in this RFP. The Specifications, Special and
Standard Terms and Conditions, Attachments to the proposal document, Proposer response and any UW
Madison Purchase Order will become the Contract between the University and the Contractor. Proposer
must accept these Specifications, Special and Standard Terms and Conditions or submit detailed and
defined exceptions along with proposed alternative or additional language for each exception.

Submitting a standard Proposer Contract as a complete substitute or alternative for the language in this
solicitation will not be accepted and may result in rejection of the Proposer’s 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 Scope
The scope of this RFP includes complete replacement of any existing gate access and revenue control systems
(hardware, software and electronic control system components) and the installation of new gate systems where
none currently exist. The awarded Contractor shall be responsible for designing, providing and installing the gate
system components, start-up operations and repair services, and on-going training and technical support.

UW-Madison Parking Structure Equipment Upgrade Possibilities

Lot # Physical Stall Count Lot Enforcement Type Entry Columns Exit Columns

See Attachments A and B for complete specifications.

3.3 Term of Contract
The contract effective date shall commence upon the successfully negotiated signed contract of the successful
proposer as required in this RFP. The initial contract term shall be for one year from the contract effective date
with the option of four one year renewal periods.

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

It is the intent of the University to start the resulting Contract upon successful negotiations.

3.4 Firm Prices
Prices must remain firm for one year from the date of the signed contract. Prices established may be lowered due to
general market conditions.

Price increase requests proposed after the initial Contract term must be received by Purchasing in writing 60
calendar days prior to the effective date of proposed increase 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. Acceptance of the price increases shall be
in the form of an amendment to the contract publication.

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.

3.5 Payment Terms
The University will pay the Contractor at each phase in accordance with milestones and achievements and as
accepted by the University.

Contractor may submit a progress payment plan but in any case, payment will only be made for work performed and
such payment plan shall not exceed amounts indicated below:

Signing of Contract - 10%
Identified Milestones for work accomplished - 40%
Delivery – 20%
Final Acceptance as defined in this Section 3: Balance of Payment due
3UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 9 OF 36

3.6 Invoicing Requirements
Invoices for Purchase Orders:
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
 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

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

Invoices for Purchasing Card: Invoices shall contain the same detail as listed in Section 3.6 and
mailed to the billing address given at the time of the order is placed.

2. Final payment may not be made until the item is operating according to specifications and has been
accepted by the University.

3.7 Acceptance and Testing
Acceptance testing will occur within 90 after the equipment has been installed at each location. Acceptance testing
will be performed by the University and will consist of verification of the specifications and performance
requirements.

If the equipment does not meet specification or performance requirements, the contractor will have 15 days to meet
requirements. If after this time period the equipment still does not meet specifications or performance
requirements, the contractor may be asked and contractor agrees to remove the equipment and return any
payments that may have been made.

The director of Transportation Services, or the director's designee, is the only authorized person who can sign an
acceptance test form. The warranty period will begin following the successful acceptance testing.

3.8 Title and Shipping Terms
3.8.1 F.O.B. Destination Freight Prepaid Included and Installed for the INITIAL TWO INSTALLATIONS
Gate equipment and systems are to be installed at Lot 17 and Lot 20 on the University campus (actual
address to be provided upon award) F.O.B. DESTINATION FREIGHT PREPAID INCLUDED AND
INSTALLED. Proposal prices must include all packing, freight, insurance, set-up, instruction and operation
manual charges. Items must be set in place in an area designated by University personnel, demonstrated
to be in operating condition, and approved by University personnel. All debris must be removed from the
University premises and properly disposed of by the contractor. Upon installation all operating instructions,
operating and maintenance manuals, must be furnished to the University personnel identified on the
purchase order.

The Contractor is required to maintain insurance in compliance with "Standard Terms and Conditions 22.0
Insurance."

Failure to bid FOB DESTINATION FREIGHT PREPAID INCLUDED AND INSTALLED in price may
disqualify your Proposal.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 10 OF 36

3.8.2 F.O.B. Destination, Freight Prepaid and Allowed (vendor responsible for freight costs)for
Subsequent Orders For Repair Parts
Delivery will be made by common carrier or proposer's truck, with unloading to be performed by the
carrier/proposer 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.

Failure to bid F.O.B. DESTINATION, FREIGHT PREPAID AND ALLOWED in Proposal price or discount
may disqualify your Proposal.

3.8.3 Country of Original and Custom Duty Costs
(CFR/CPT) - DDU Delivered Duty Unpaid. Proposers must include costs from proposers door to port of
destination and local delivery charges. The University will be responsible for all United States duty fees,
port of entry documentation fees, custom clearance, tax, etc., if applicable.

NOTE: Awarded contractor must use the University's contracted customs broker identified on the purchase
order.

Please indicate on the Bidder Response Sheet the Country of Origin and Shipping Point.

3.9 Insurance
The Contractor shall maintain insurance levels as required in STANDARD TERMS AND CONDITIONS, SECTION
22.0. A certificate of insurance must be provided upon request and provided on an annual basis.

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.

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 Contract Termination
After the initial term of the Contract, the University may terminate the Contract at any time, without cause, by
providing 45 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 contracted proposer pursuant to fulfilling the contract. The University will be obligated to pay such expenses
to date of the termination.

Contract Termination may occur for the following reason: Shall either party fail to perform under the terms of this
Contract; the aggrieved party may notify the other party in writing via certified mail 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 as but not limited to failure to provide any of the conditions of the Specifications or Special Conditions of
Proposal.

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 #22 of the
University's Standard Terms and Conditions, the University has the right to cancel and terminate the Contract
without notice.

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 inequity, to terminate this contract by giving 90 calendar days notice in writing of such
termination.

If at any time the contractor performance threatens the health and/or safety of the University, the University has the
right to cancel and terminate the Contract without notice.

All notices of performance failure shall be submitted in writing to Purchasing, 21 N Park St, Suite 6101, Madison WI
53715-1218. Purchasing will be the final authority for all grievances not resolved through the Department.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 11 OF 36

3.12 Eligible Purchasers
All University of Wisconsin-Madison campus locations, other U.W. System campuses, State of Wisconsin agencies,
and Wisconsin municipalities may be eligible if offered from the proposer to purchase from this contract. Proposers
are to state on the RFP Checklist whether they will agree to provide items to these other locations.

A Wisconsin municipality is defined by Wisconsin Statute 16.70(8) to include counties, cities, villages, towns, school
boards, sewage, drainage, vocational, technical and adult education districts, and other bodies with the power to
award public contracts.

This contract must not be construed as mandatory upon any University campus, State agency or municipality. The
University reserves the right to issue a separate Proposal when deemed in the best interest of the University.

3.13 Fair Price Analysis
Purchases made under this proposal may require further fair price analysis. Prior to award, the awarded
contractor 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.14 Subcontractors
3.14.1 Any Contract resulting from this proposal shall not be, in whole or in part, subcontracted, assigned, or
otherwise transferred to any other Contractor without prior written approval by Purchasing.

3.14.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.

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

3.14.4 If subcontractors are to be used, the Contractor must clearly explain their participation.

3.15 Executed Contract to Constitute Entire Contract
The University's Request for Proposal, the proposal responses, written communications and this 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 11-5270, dated July 20, 2010 including amendments/attachments
C. Proposer response to RFP
D. Official Purchase Order (when applicable)

3.16 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.17 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.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 12 OF 36

Section #4: Requirements of All Proposals

NOTE: Failure to respond to all items in this section may be deemed as sufficient reason to reject any proposal.
Please format your response to correspond numerically with items listed below.

4.1 Proposers must complete the RFP Checklist and Submittal Page in Section #6 of this RFP, and sign in ink.
(Mandatory Response) (0 points available)

4.2 Proposers must complete the Mandatory Specifications Form provided in Attachment A.
(Mandatory Response) (0 points available)

4.3 Desired and Value Added Specifications as provided in Attachment B.
(Mandatory Response) (1500 points available)

4.4 Proposer must complete the Cost Proposal Form provided in Attachment C.
(Mandatory Response) (400 points available)

4.5 Proposer must complete the Client Reference List provided in Attachment D.
(Mandatory Response) (100 points available)

4.6 Proposer must complete the Supplier Diversity, Minority Business Enterprise (MBE) Program Commitment provided in
Attachment E.
(Mandatory Response) (0 points available)

Proposer must provide contact information for the following:

NAME PHONE NUMBER FAX NUMBER
Contract Renewal/ _________________ _______________ _____________
Cancellation/Problems
Invoice Information _________________ _______________ _____________

Ordering/Expediting _________________ _______________ _____________

MINORITY REPORTING: PHONE NUMBER FAX NUMBER
Contact Name: __________________________ _______________ ___________
Address: __________________________
__________________________
__________________________
E-mail: __________________________

AFFIRMATIVE ACTION: PHONE NUMBER FAX NUMBER
Contact Name: __________________________ _______________ ___________
Address: __________________________
__________________________
__________________________
__________________________

4.7 Proposer must complete the Certification of Site Visit provided in Attachment G.
(Mandatory Response) (0 points available)
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 13 OF 36

Provide responses to the following:

 Do you have the capability of putting the University’s specific pricing on a WEB site that is accessible to
University Purchasers through a unique logon ID?

 If yes, does your Website provide a means of on-line ordering with our specific pricing being applied
automatically?

 If yes, does your Order System accept Purchasing Cards for payment?

 If yes, does your Order System provide a self-service means for the customer to track their order via Internet?
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 14 OF 36

Section #5: Evaluation and Award of Contract(s)

5.1 Proposal Scoring
Proposals meeting mandatory requirements will be reviewed by an evaluation committee and scored against the
stated criteria. The committee may, at its sole discretion, review references, request oral presentations, and
conduct an on-site visit and use the results in scoring the proposals. Proposals from certified Minority Business
Enterprises may have points weighted by a factor of 1.00 to 1.05 to provide up to a five percent (5%) preference to
these businesses. The evaluation committee's scoring will be tabulated and proposals ranked based on the
numerical scores calculated.

5.2 Scoring Criteria and Method
For each response required of the Proposer in Section #4, the points provided in parentheses represents the total
possible points available for each response. The responses will be evaluated based on the relative merits to the
needs of the State of Wisconsin (rather than relative to competing Proposer’s responses). The proposals will be
scored and ranked independently by each committee member and the resulting scores will be averaged to
determine the highest scoring proposal.

Cost Proposal Scoring
5.2.1 The lowest priced proposal will receive 100% of the allotted cost points. All other proposals will be scored
using the formula as follows:

Lowest Proposed Cost
(constant) __ X Maximum evaluation points given to cost = SCORE
Other Proposer's Cost
(varies according to proposal being scored)

Calculation of points awarded to subsequent proposals will use the lowest dollar proposal amount as a
constant numerator and the dollar amount of the firm being scored as the denominator. This result will
always be less than one. The result is then multiplied by the number of points given to the cost section of
the RFP.

5.2.2 For all other non-pricing related responses, points will be awarded relative to the needs of the State of
Wisconsin, as solely determined by the evaluation committee members.

5.3 Best and Final Offers
At the sole discretion of the University, the highest scoring Proposer or Proposers may be requested to submit a
Best and Final Offer in order to further clarify the deliverables, contract language, or costs presented in the
Proposer’s RFP. If Best and Final Offers are requested, they will be evaluated against the stated criteria, scored
and ranked. There is no obligation on the part of the University to request Best and Final Offers from any or all of
the Proposers responding to the RFP.

5.4 Contract Award
The contract will be awarded to the highest scoring Proposer providing contract negotiations are successful.

5.5 Notification of Award
All proposers who respond to this RFP will be notified in writing of the University's award of contract(s) as a result of
this RFP. After notification by Purchasing of the notice of award file copies of proposals will be available for public
inspection. Proposers must schedule document inspection with the Contract Administrator responsible for
managing this RFP.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 15 OF 36

Section #6: RFP Checklist and Submittal Page
6.1 Proposer has responded to all items in Section # 4,” Requirements of All Proposals”. ___________(Initial)

6.2 In accordance with Wisconsin Statutes 16.75(3m), 16.752 and 560.035(1)(c), please indicate below if you are a
Wisconsin Certified minority business (MBE), work center (WC) or woman owned business (WBE) (see websites:
http://www.commerce.state.wi.us/bd/BD-MinorityandWomen.html or
http://stateuseprogram.wi.gov/section.asp?linkid=1424&locid=65 ).

____ Minority (MBE) ____ Work Center (WC) ____ Woman Owned Business (WBE) ___ Not applicable
(If no answer is indicated above, we will assume that you are none of the above when making the award.)

6.3 Pursuant to Public Law 95-507, indicate which of the following classifications apply to your organization. All
vendors are considered Large Business unless otherwise indicated (see website: www.sba.gov/). (Check √ all that
apply.)

____________ LARGE BUSINESS (LG)
____________ SMALL BUSINESS (SB)
____________ VETERAN OWNED SMALL BUSINESS (VOSB)
____________ SERVICE DISABLED VETERAN OWNED SMALL BUSINESS (SDVOSB)
____________ HISTORICALLY UNDER UTILIZED BUSINESS ZONE (HUBZONE)
____________ SMALL DISADVANTAGED BUSINESS (SDB)
____________ WOMAN-OWNED SMALL BUSINESS (WOSB)

6.4 MINORITY BUSINESS PARTICIPATION: As a mandatory component of this proposal, you must complete the
“Supplier Diversity, Minority Business Enterprise (MBE) Program Commitment” form that is a part of this document.

I have reviewed and completed the ““Supplier Diversity, Minority Business Enterprise (MBE) Program Commitment”.

____________ YES ____________ NO

6.5 In preparing this RFP, this Proposer has not been assisted by any current or former employee of the State of
Wisconsin whose duties relate to this RFP and who was assisting in other than his or her official capacity. Neither
does such a person or any member of his or her immediate family have any financial interest in the outcome of this
RFP. ____________(Initial)

6.6 AMERICAN MADE: Wisconsin Statutes S. 16.754, directs the state to purchase materials which are
manufactured to the greatest extent in the United States when all other factors are substantially equal.
“Substantially equal” means when proposals are tied or proposal scores are equal. Indicate whether the material
covered in your proposal were manufactured in whole or in substantial part within the United States, or the majority
of the component parts thereof were manufactured in whole or in substantial part in the United States.

____________ YES ____________ NO ____________ UNKNOWN

6.7 ELIGIBLE PURCHASERS
Proposer agrees to make the terms of the resulting contract available on a convenience use basis for other UW-
System Campuses and to other State Agencies, municipalities, and school districts if awarded a contract.

____________ YES ____________ NO
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 16 OF 36

6.8 CONTRACT ADMINISTRATOR
Any correspondence, price lists or other documents must include reference to Contract number 11-5270 and be
sent to the Contract Administrator. The Contract Administrators are authorized to give the approvals required
under this contract on behalf of the University.

A. University
The Contract Administrator for the University is:

Day- to-day operations for the University will be handled by:

Tom Woznick, Booth Operations Supervisor
Facilities Planning & Management Transportation Services
Room #124 WARF Building
610 N Walnut Street, Madison, WI 53726
PHONE 608-890-0427 – FAX 608-265-3424
EMAIL twoznick@fpm.wisc.edu

B. Contractor
Contractor must provide knowledgeable individuals, acceptable to the University, who will provide the
following administrative support functions:

The Contract Administrator for the Contractor who is authorized to give the approvals required under this
Contract is:

_______________________________________ (Name)
_______________________________________ (Company)
_______________________________________ (Address)
_______________________________________ (Address)
PHONE ________________ -- FAX ________________
EMAIL _________________________________________

A Contract Administrator to act with full authority on the Contractor’s behalf in all matters pertaining to the
University.

Day- to-day operations for the Contractor will be handled by:

The Proposer certifies by submission of the proposal 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. ___________ (Initial)

In signing this proposal, we have read and fully understand and agree to all terms, conditions and specifications
and acknowledge that the University Purchasing Services proposal document on file shall be controlling. 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 proposal; that this proposal has been independently arrived at without
collusion with any other proposer, competitor or potential competitor; that this proposal has not been knowingly
disclosed prior to the opening of proposals to any other proposer or competitor; that the above stated statement is
accurate under penalty of perjury.

___________________________________________________________________________________
Name and Title of Signing Officer (print)

___________________________________________________________________________________
Company Name and Address

_______________________ _____________________ __________________
Telephone Fax Number Tax I.D. Number

_____________________________________________________________ __________________
Signature Date
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 18 OF 36

ATTACHMENT A – MANDATORY SPECIFICATIONS

Proposer MUST respond "YES" or "NO" by checking the appropriate box on each of the following Mandatory Specifications
or your Proposal will not be considered. Proposer should provide on an attached sheet a detailed description of how
your firm's parking ramp access and revenue control system meets each mandatory requirement listed below, clearly
identified by the specification number. Proposer should provide an explanation for any "NO" responses. The University will
be the sole judge of equivalency.

DOES
NOT
MEETS MEET
MANDATORY SPECIFICATION SPECIFI- SPECIFI-
SPECIFI- CATION CATION
CATION
NUMBER YES NO
4.2.1 The proposed equipment and software must permit University staff with the
appropriate authorizations to monitor all installed devices, view activity (entry &
exit), open gates, close gates, view counts and have complete control of the
 
system operation from a standard personal computer equipped with access to the
internet. This capability is in addition to any proposed fee computers that are part
of the supplied equipment.
4.2.2 The proposed equipment and software must provide central credit card
processing from workstations, fee computers, exit stations and Pay on Foot (POF)  
stations without requiring separate, dedicated telephone connections.
4.2.3 The proposed equipment and software must provide for on-line and real time
 
communication with the University’s ARC system.
4.2.4 The proposed equipment and software must have a way of accounting for the
number of vehicles within the parking facility.
4.2.5 The proposed equipment and software must be able to restrict vehicle entry to the
facility based on capacity, type of parking (visitor, contract or annual permit, guest  
list), date (day) and time.
4.2.6 The proposed equipment and software must include the capability of producing
and processing “bulk” validations (coupons printed at one time for later distribution
to parking customers whose parking fees are reduced or eliminated by use of the
coupon).
4.2.7 The proposed equipment and software must have the capability to sort and
 
itemize charges for the parking validation providers.
4.2.8 All field programmable functions of the proposed system must also be
programmable from a standard personal computer, from any fee computer, and  
from any workstation that is part of the access and revenue control system.
4.2.9 The proposed equipment and software must be capable of both individual and
bulk validation which allows parking validation by either dedicated validation
devices or by a standard web browser. Each of these validation methods must  
provide the ARC system with the information necessary to process the validated
parking through selected exit gates.
4.2.10 Any proposed equipment that is located outside of a staff occupied space must be
suitable for use in a temperature range from -10 to 110 degrees Fahrenheit and in  
environments that are dusty, wet, and greater than 75% relative humidity.
4.2.11 Proposed Pay on Foot stations when connected to the University’s ARC system
must accept credit cards, debit cards, US bill and US coin payments. The  
proposed system must provide customers with change for cash transactions.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 19 OF 36

DOES
NOT
SPECIFI- MEETS MEET
CATION MANDATORY SPECIFICATION SPECIFI- SPECIFI-
NUMBER CATION CATION

YES NO
4.2.12 Credit and debit card authorizations of the proposed system must be immediate
(10 seconds or less) more than 90% of the time for all installed credit and debit  
card readers.
4.2.13 The proposed exit readers must read parking receipts (e.g. entrance tickets and
validation encodings, coupons, articles, and credentials), credit cards, and debit  
cards through the same slot.
4.2.14 The proposed servers must operate from behind the University’s firewall.
4.2.15 Provider warrants that, for the life of the contract, processing transactions shall be
compliant with banking standards established by Payment Card Industry (PCI)  
Data Security Standards.
4.2.16 The proposer must agree to provide the University with access (ability to
purchase) for OEM repair parts and all system hardware components for a  
minimum of five (5) years after installation.
4.2.17 The proposer must agree to provide the University with availability of training in
repairs and maintenance for all system hardware components for a minimum of  
five (5) years after installation.
4.2.18 All exits must be equipped with readers and gates controlled by the proposed
 
software system.
4.2.19 The proposed equipment and software must include the capability for two-way
voice over the internet (VoIP) communication between Transportation Services
 
staff at office workstations and fee computers and every entry gate, exit gate, and
pay station.
4.2.20 The system must comply with all provisions of American National Standards
Institute (ANSI) A117.1-2003. Standard for Accessible and Usable Buildings and  
Facilities.
4.2.21 The system must use Oracle 10gR2 or newer as the system database for
 
customization and maintainability by University IT staffs.
4.2.22 The system must operate in a MS Windows environment consisting of Server
2003 R2 or newer and IIS 6.0 or newer for customization and maintainability by  
University IT staffs.
4.2.23 The system must comply with all applicable codes (building, electrical, access,
 
etc.) and regulations.
4.2.24 Did a representative from your company attend the mandatory site visit on July 29,
 
2010?
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 20 OF 36

ATTACHMENT B – DESIRED AND VALUE ADDED SPECIFICATIONS

4.3 DESIRED AND VALUE ADDED SPECIFICATIONS
Your Proposal response should include a narrative addressing each item listed below. Proposer should submit on
an attached sheet, clearly identified by the specification number, a detailed explanation of your proposed parking
access and revenue control equipment for each Desired Specification, or any exceptions or variations.

Please format your response to correspond numerically with items listed below for each of the following
specifications. The University will be the sole judge of equivalency.

4.3.1 SYSTEM ARCHITECTURE
Describe the overall system architecture for hardware and software in Lot 17, Lot 20, Lot 76, Lot 83 and Home
Office at 610 Walnut Street, Madison, WI. Use diagrams and/or photographs to supplement narrative. Your
proposal should show each parking location as well as how all the locations are centrally administered and
controlled. Describe your proposed architecture as it related to all component pieces listed in 4.3.1.1 through
4.3.1.3.

The system architecture should also show how future installations purchased under this proposal will be integrated
into the overall architecture. Possible future locations are Lots 7, 23, 29, 36, 38, 41, 46, 95.

The University desires at least one camera per combined entrance/exit location to remotely observe that gate
equipment is functioning, vehicles are present or not, and provide evidence in the event equipment is misused. The
cameras should connect to the existing video management/storage system at the home office location. Describe
the system’s capability to add additional cameras at current and future locations.

4.3.1.1 Entry Lanes
1. Passes/Permits/Gates/Readers
2. Hourly Tickets/Ticket Dispensers
3. Loops/Counters/Payment Equipment
4. Cameras/Communication Equipment/Network

4.3.1.2 Cashiering and Control Stations
1. Location of Pay Stations/Central Cashiering
2. Validation methods, Payment methods/Receipts
3. Damaged/Lost/Unreadable tickets
4. Central Hub/Network/Voice and Data Equipment
a. Financial Control Capability
b. Reporting Capability
c. Administration (Security and Validation)
d. Compatibility with existing campus security (Andover Continuum at Lot 38 and Lot 95)
5. Equipment Maintenance and upgrades
6. Supplemental Payment Systems if available

4.3.1.3 Exit Lanes
1. Passes/Permits/Gates/Readers Payments
2. Loops/Counters/Payment Equipment/Receipts
3. Pass back controls
4. Cameras/Communication Equipment/Network

4.3.2 HARDWARE
For each numbered section of your Proposal your response for the following components should include
manufacturer and model numbers of the components. Attach technical specifications for the components
to your response. For each numbered section below, your response should include manufacturer and
model numbers of the components listed. State whether the components are generic or proprietary.
Format your response to correspond numerically with each of the following specifications.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 21 OF 36

4.3.2.1 Entry Lane Equipment at each location
Describe the components of the entry stations in the proposed system which may generate and/or receive
tickets, passes, and permits. The entry lane components must include a Class 1 Generation 2 UHF Air
Interface Protocol Standard reader capable of reading low cost generic RFID tags or a Gen 1 RFID reader.
The University desires a central cashier model or fully automated method of operation. Your proposal
should clearly state whether existing booths will be retained or abandoned, if a new cashier location will be
provided, and how any new cashier locations will be designed, constructed, and commissioned. The
University is not responsible for modifying infrastructure unless clearly identified in the proposal and
included in the cost proposal.

1. Vehicle Detection System
a. Describe the testing of all existing loops for integrity. Describe any contingency pricing.
b. Describe in detail any new vehicle detection equipment that is proposed.
c. Describe how motorcycles are or are not detected.

2. Describe the ticket dispensing equipment and how it is integrated with the rest of the system.
3. Describe the gates and how they are integrated with the rest of the system.
4. Describe how operator and customer mistakes and errors are handled.
5. Describe communication and display equipment, such as variable message signage and voice
messaging, intercoms, and cameras that are part of your proposal.
6. Describe the ability to raise and lower gates using a mobile phone, personal computer, and hardware
switch.

4.3.2.2 Cashier and Control Stations
Describe the office or booth space that is proposed. For the items listed below, describe the office
equipment and hardware components for your proposed system as well as any security and environmental
requirements for each location. The current environment includes staffed booths at Lots 17, 20, and 83 but
the University prefers a central cashier model. Describe the office equipment and hardware components for
your proposed system as well as any security and environmental requirements for each location. Your
proposal should clearly state whether existing booths will be retained or abandoned, if a new cashier
location will be provided, and how any new cashier locations will be designed, constructed, and
commissioned. The University is not responsible for building or modifying infrastructure unless clearly
identified in the proposal and included in the cost proposal.

1. Central Hub/Network Voice & Data
a. Server(s) (must be behind University firewalls)
Describe the server or servers required for your proposed system. Include information on
hardware (disk, memory, CPU, etc.), and software (operating systems, etc.) requirements.
What components do you propose to run on the server(s)? NOTE: We intend for this system
to run on servers owned and maintained by the University that are behind a University
firewall (See Mandatory Specification 4.2.13)
b. Workstations. Describe the workstations required for this solution. What hardware (disk,
memory, CPU, etc.), operating systems, etc. are required? What components run on each
workstation?
c. Network. Describe your proposed network devices and the industry standard protocols that will
be used. Describe any network requirements including devices that the University must supply.
d. Security. Describe any security devices/techniques supported by this solution. For example,
are network communications encrypted? Are fingerprint readers supported? NOTE: Describe
any network security requirements including devices that the University must supply.
2. Payment Systems
a. Any Staffed Office with Cash Register
b. Any Pay On Foot stations
Describe the components of the Pay on Foot customer payment stations in your system.
c. Any Pay from Vehicle stations
Describe the components of the stations for customer payment from vehicles in your system.
Include validated parking as means of payment.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 22 OF 36

4.3.2.3 Exit Lane Equipment at Each Location
Describe the components of the exit stations in your system that receive tickets and credit cards. The exit
stations should also receipts. The exit lane components must include a Class 1 Generation 2 UHF Air
Interface Protocol Standard reader capable of reading low cost generic RFID tags.

The University desires a central cashier model. Your proposal should clearly state whether existing booths
will be retained or abandoned, if a new cashier location will be provided, and how any new cashier locations
will be designed, constructed, and commissioned. The University is not responsible for modifying
infrastructure unless clearly identified in the proposal and included in the cost proposal. As applicable,
describe how your proposed system will process and/or address:

1. Vehicle Detection System
a. Describe testing of all existing loops for integrity
b. Contingency pricing for new loops
c. Describe any new vehicle detection equipment.
d. Describe exit lane safety features
2. Passes/Permits/Gates/Readers Payments
3. Payment Equipment/Receipt printers
4. Pass back controls
5. Cameras/Communication Equipment/Network
6. Describe the ability to raise and lower gates using a mobile phone, personal computer, and hardware
switch.

4.3.3 SOFTWARE AND DATA MANAGEMENT
For each numbered section 4.3.3.1 through 4.3.3.3 of your Proposal response, describe the specifications of the
system you propose to provide to the University with respect to the following. Format your response to
correspond numerically with each of the following specifications.

4.3.3.1 Data Repository Architecture
1. Describe the architecture of the data repository for the proposed system.
2. Data must be transferred from the University’s PowerPark system to the proposed system. Describe
how the transfer will occur and how data integrity will be assured.

4.3.3.2 Data Security
Describe your proposed system’s security architecture, including the level of granularity at which security
can be applied. Include what sensitive data (see the following for a definition of sensitive data:
https://wiki.doit.wisc.edu/confluence/display/POLICY/Sensitive+Info ; sensitive data includes, ssn; driver
license no; financial account numbers; DNA profile; Unique biometric data; protected health information) are
stored and whether or not information is encrypted. Describe your proposed system’s user interfaces. Is
the interface a thick client or web based? If both, how do they differ? Describe methods used to secure the
web client. If there are any fees for the data security in your proposed system, the fees must be in the cost
proposal or the data security must be provided at no cost.

4.3.3.3 For each of the following bullets, describe how your system functions to provide a means to share
information from and with external sources.
Data Sharing capabilities:
 Ability to support SOAP and XML.
 ODBC requirements.
 API’s and the functions provided with them.
 What databases are compatible with your product?
 Ability to directly access the data repository.
 Capabilities to import and export data.
 How data imports and exports affect the normal operation of your proposed system.
 Ability for users to access selected data without having to log in to the system and without additional
licensing required.
 Ability to add and modify additional tables and fields to data repository and have them accessible via
the interface and graphics engine.
 Ability to allow BASS-IT applications development staff to write Microsoft .NET applications that
integrate with your system.
 Ability to accept “smart” or declining balance cards
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 23 OF 36

 Ability to add funds to smart cards at pay stations or card readers.
 How does third party integration, for example, an in-house web application, affect service levels
provided by your support staff and the product?

rd
Ability to integrate with 3 party cards such as the University’s WISCARD, bus pass, or a cashier
station that provides declining balance cards (gift cards).

4.3.3.4 Report capabilities. Describe and provide examples of the proposed system’s ability to:
• produce standard reports.
• produce reports within the application in an industry-acceptable format.
• create, save and modify reports with a reusable library of reports available for authorized users, and
modify parameters.
• alias report fields so that end users can see columns represented in their own terms.
• define report formats.
• allow end users to run their own reports via a web page.

4.3.3.5 Query capabilities. Describe and provide examples of the proposed system’s ability to:
• produce standard queries.
• query data using wildcards in any or all descriptive fields.
• query on any field in the data repository from any point in the system and save the query to a library.
• perform ad hoc queries on data using multiple complex search criteria, Boolean logic, and multiple
sorting criteria.
• save and store queries and their result sets.
• export result sets in standard formats.
• query data within this system and also data imported from other systems.
• present data in graphical form using graphs and charts.

4.3.3.6 Describe how the proposed system could be used to manage annual parking permits, payroll deduction for
employees, spaces assigned to categories of users (visitors, employees, students, special events, etc.),
hangtag inventories, access cards, and all methods of payment for parking.

4.3.3.7 Describe how the proposed system could be used to manage parking enforcement, citations, citation
appeals, citation hearings, citation payments, scofflaws, past due citation collections, towing, suspension of
vehicle registration, and integration with the Wisconsin Department of Transportation, Division of Motor
Vehicles system of vehicle registration.

4.3.3.8 Describe how user accounts (individuals) are linked to vehicles, parking privileges (permits), citations,
citation appeals, parking locations (a surface lot or structure), bus pass, bicycle locker, community car
account, pay-by-phone account, carpool, vanpool, or other alternative-to-parking program service.

4.3.3.9 Describe parking management operations that cannot be performed through the proposed software user
interface and must be performed on the proposed hardware system.

4.3.3.10 Describe operations that cannot be performed through the proposed hardware user interface and must
be performed by the proposed software system.

4.3.3.11 Describe the interface and communication protocols between your proposed hardware and software.

4.3.4 STARTUP TRAINING AND SUPPORT
In this section of your Proposal response, describe how you propose provide training and/or support. Please format
your response to correspond numerically with the following:

4.3.4.1 Startup Assistance and Planning
 Describe your startup training and support
 Does your firm provide all startup assistance?
 How is startup assistance initiated?
 How long will it take for a response to startup assistance request?
 How are startup assistance calls tracked?
 The University is supported by an Information Technology (IT) department. How do you propose to
coordinate startup assistance training and ongoing support provided by the IT department?
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 24 OF 36

 Describe the extent to which University staff can perform service on your proposed system, both
during startup and during warranty periods.
 All fees for startup assistance must be included in the cost proposal section or the assistance must
be provided at no additional cost.

4.3.4.2 System Administration Startup Assistance. Describe all the system administration needs of the proposed
parking ramp access and revenue control software and hardware. How and where will University staff be
trained to administer the system during startup? All fees for system administration startup assistance must
be included in the cost proposal or the assistance must be provided at no additional cost.

4.3.4.3 Job and Report Scheduling Assistance. Describe how the proposed system supports scheduled jobs and
reports. How will staff be trained to use scheduled jobs and reports during startup?

4.3.4.4 Information Backup and Retrieval Assistance. Describe, for each of the following bullets, how staff will be
trained to accomplish backup, retrieval and restore.
 Automatic backup at pre-set times and dates.
 Ability to recover or retrieve data and get it back into the system.
 Ability to recover from a catastrophic database loss.

4.3.4.5 Event/Audit Logging Assistance. Describe how University staff will be trained to use and report the
proposed system’s event/audit logs. Include training on reports for equipment category types, severity
levels, granularity of logging, ability to change logging levels on the fly, and other relevant information about
event/audit logging in the proposed system.

Your proposed equipment should have the ability to raise the entry/exit gates manually and remotely using a
standard personal computer equipped with an internet connection and web browser. Vending a gate
manually and remotely should be system recorded events.

4.3.5 ON-GOING SUPPORT
In this numbered section of your Proposal response describe how you will ensure that Facilities, Planning &
Management (FP&M) technicians and electricians are able to service all the components of your proposed system.
Describe how you will provide both onsite and remote support. Please format your response to the above to
correspond numerically with items listed below for each of the above specifications. Any costs for on-
going support must be in the cost proposal or the support must be provided at no additional cost.

4.3.5.1 Describe to what extent service requirements for components of the system can be performed by University
personnel both during and after warranty periods.
 Identify software and hardware components that will not be serviceable by UW personnel.
 Describe how equipment maintenance and upgrades will occur.

4.3.5.2 Describe for each of the following bullets, your company’s ability to provide support and upgrades for:
 System administration components and configuration
 Troubleshooting and diagnostic techniques and tools
 Access to an on-line knowledge base of common problems and solutions
 Handling of future US currency bills and coins
 Who installs patches, upgrades and new firmware versions – the customer or the vendor
 How is the patch/upgrade process initiated?
 How is training provided for patches, upgrades and new firmware versions?

4.3.5.3 Describe backward compatibility of future software and hardware installations.

4.3.5.4 Software Licensing
If your system includes software licenses, describe how your product is licensed and the increments in
which additional licenses may be added. For example, are additional licenses required for twenty (20) new
(additional) users? Include a copy of any software license agreements that you would expect the University
to sign.

4.3.5.5 Software Support
List the software support plan you are proposing for the proposed system. Describe if the proposed system
has the ability for support representatives to communicate with the system remotely for troubleshooting
purposes.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 25 OF 36

4.3.5.6 Software Training
Describe your comprehensive training plan to meet the conversion, implementation, operation, system
administration, and development needs as they relate to the proposed system. Detail specific courses
required, duration, location and a tentative schedule for each course.

4.3.5.7 Software Upgrades
Describe, for each of the following bullets, your policy and practices on software upgrades and patches with
respect to:
 Frequency of upgrades.
 Response time for bug fixes.
 Ability to download patches and upgrades from the web.
 System enhancements and feature capabilities.
 Keeping system current with evolving hardware standards and operating systems.
 Migrating existing system settings and data.
 System disruption caused by upgrades.
 Small patches for bug fixes in lieu of major upgrades.
 Backward compatibility with hardware.

4.3.6 WARRANTIES
In this numbered section of your Proposal response describe the warranty coverage, including time periods, of the
system you propose to provide. A minimum warranty of one year from a successful acceptance test for hardware,
firmware, and software is required. Describe in detail any extended warranties. If there are any fees for the
extended warranties, the fees must be in the cost proposal or the extended warranty must be provided at no cost.

4.3.7 EXTENSIBILITY
In this section of your proposal describe how the software and hardware proposed for Lots 17, 20, 76, and 83 could
be extended to other campus parking facilities and to additional parking management functions and features. If
there are any costs for providing extensibility the fees must be in the cost proposal or the ability to extend the
system to other campus locations must be provided at no cost.

4.3.7.1 Extend to other locations
 How would equipment needs be determined and designed?
 What would be the design and installation costs?
 How will the potential installations be scheduled?
 If infrastructure improvements (e.g., concrete, electrical, data, booths, etc.) are needed, how will these be
defined and coordinated with the access and revenue control equipment installations?
 Will future installations be substantially the same and compatible with the equipment you are currently
proposing for Lots 17, 20, 76, and 83?
 The University currently uses Andover Continuum access controls at Lots 38 and 95 for building security.
Describe how your proposed solution will or will not be compatible with the University’s Andover Continuum
system. Can the proposed parking system use University issued ID cards for parking access?
 Is there a limit to the kinds and number of components that can be added to your proposed system before
network infrastructure improvements are needed?
 What are the component prices for extending parking access and revenue control to other UW Madison
campus locations? Provide a detailed price list.
 Describe how the proposed system can use mobile phones, telephones, any computer connected to the
internet, smart phones, and hardware switches.

4.3.7.2 Extend to additional parking management features
The University may choose to phase implementation of some system features. For example, the University
may choose to implement only the access and revenue control features in the first year and wait until
subsequent years to implement additional parking management features such as citation management, bus
pass management, and event management. Describe how the proposed system functions and features
can be implemented in phases or stages. Any additional costs for implementing software features in
phases must be in the cost proposal or a phased implementation must be provided at no cost.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 26 OF 36

4.3.8 DELIVERY AND IMPLEMENTATION
The UW-Madison desires the Parking Ramp Access and Revenue Control system to be fully operational in
Lots 76, 17, 20, and 83 by June 1, 2011. Installation should be sequenced in the above order. In this numbered
section of your Proposal response describe the delivery, implementation, and payment schedule of the system you
propose to provide. Explain the proposed schedule in detail and include at least the following milestones: Detailed
Requirements Complete, Approved Design Complete, Approved Implementation Plan Complete, Lot 76 Installation
Start, Lot 76 Commissioning, Lot 17 Installation Start, Lot 17 Commissioning, Lot 20 Installation Start, Lot 20
Commissioning, Lot 83 Installation Start, Lot 83 Commissioning, and Substantial Completion. If you are unable to
meet the proposed implementation deadline of June 1, 2011, please provide an alternative schedule.
UNIVERSITY OF WISCONSIN PROPOSAL NO.: 11-5270
MADISON, WISCONSIN 53715-1218 PAGE 27 OF 36

ATTACHMENT C – COST PROPOSAL FORM

4.4 COST PROPOSAL SUBMISSION
Submit Attachment C: Cost Proposal, with attached description sheet(s) requested, in a separate sealed
envelope labeled: RFP 11-5270 COST PROPOSAL. NOTE: Proposer must fill out the Cost Proposal in this
EXACT format without any edits or additions, or Cost Proposal will be considered non-responsive.