Check the "Contract Updates for the Week"

PARKING RAMP ACCESS AND REVENUE CONTROL SYSTEM
(contract last updated 03/27/2013)

SCOPE: Contract for the Facilities Planning and Management Transportation Services (FP&M) for parking ramp access and revenue control system.

The purpose is to purchase replacement equipment for University parking Lot 75, and establish a contract for potential future purchases for existing or new parking facilities to include other campus parking facilities, for which there are no final plans at this time.  The scope of the Lot 75 project includes complete replacement of the existing access and revenue control system, both hardware and control system components.  Contractor shall be responsible for providing and installing the system components and for providing repair service, training and technical support for the system throughout the contract period.
CONTRACT # DESCRIPTION
09-5012 PARKING RAMP ACCESS AND REVENUE CONTROL SYSTEM
CONTRACT ORIGIN: ADDITIONAL INFORMATION:
UW-Madison
Purchasing Services
21 N Park St, Ste 6101
Madison, WI 53715-1218 		UW-Madison users contact:
Andy Richardson
(608) 890-2422 / FAX (608) 262-4467
arichardson@bussvc.wisc.edu
 

Non-UW-Madison users contact: Vendor Representative
COOPERATIVE PURCHASING: YES
CONTRACT TERM: September 15, 2008 through September 14, 2009, with automatic renewal extensions to September 14, 2014, unless amended, cancelled or rebid.
Manufacturer: SkiData
Vendor(s)
081406
Don Harstad Co
7103 Hwy 65 NE
Fridley  MN  55432
     
Sales Representative: PHONE # FAX #
Dan Stublaski 763-571-5660 763-571-5943
E-mail dstublaski@donharstad.com
  PHONE # FAX #
Ordering/Expediting: 763-571-5660 763-571-5943
Invoice Information: 763-571-5660 763-571-5943
Supplier Diversity Reporting: 763-571-5660 763-571-5943
Website:www.donharstad.com
Commodity Code 155-53
285-36
550-38
550-90
Federal Employee ID # (FEIN) 41-1336603
F.O.B. SHIPPING COSTS, ON SITE SERVICE AND CUSTOMS REQUIREMENTS
Terms: N/30
Invoicing: Invoices shall reflect contract pricing.
Warranty: The warranty period shall commence upon successful acceptance testing.
Pricing Information:

See below

ITEM DESCRIPTION
TOTAL PRICE
    
4.6.1 Total cost for all equipment and hardware needed for operation Parking Ramp Access and Revenue Control System.
$359,534.00
   
4.6.2 Total cost for all software licensing and/or one time charges for all programs.
$74,571.00
   
4.6.3 Installation, support and software maintenance through initial 1-year contract term.
$49,990.00
   
       
   
4.6.4
Annual Support and Software Maintenance for year 2
Annual Support and Software Maintenance for year 3
Annual Support and Software Maintenance for year 4
Annual Support and Software Maintenance for year 5
Annual Support and Software Maintenance for contract years 2 through 5
   
$16,560.00
$17,885.00
$19,315.00
$20,668.00
$74,428.00
   
ITEM DESCRIPTION
TOTAL PRICE
4.6.5 Total cost for all training through initial 1-year contract term.
$5,400.00
4.6.6 Other pricing not requested
Contact vendor
Spec number SPECIFICATION DESCRIPTION
4.5.1 The system must permit Transportation Services staff with the appropriate authorizations to monitor all devices, view activity, access system events, control gates, view counts and have complete control from any workstation or fee computer on the parking equipment network.
4.5.2 The system must provide real-time central credit card processing from fee computers, exit stations and Pay on Foot (POF) stations without requiring separate telephone line connections.
4.5.3 The system must be microprocessor based.
4.5.4 The system must provide for on-line communications.
4.5.5 The system must have a way of accounting for the number of vehicles within the parking facility and have programming capability to restrict vehicle entry to the facility based on capacity.
4.5.6 The system 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.  System must have the capability to charge provider for the parking validations they authorize for customers.
4.5.7 All field programmable functions of the system must be programmable from the central facility computer or from any fee computer or workstation on the parking revenue control network.
4.5.8 The system must be compatible with an individual and bulk validation system which currently allows validation by either a validator, which imprints a bar code on the ticket, or a web browser.  Both of these methods must provide the system with the information necessary to process the validation through the payment stations and exit gates.
4.5.9 All system components that are located outside of a staff occupied space must be suitable for use in a temperature range from -25 to 105 degrees Fahrenheit and in dusty, wet or high humidity conditions.  Barrier -25 - +113F / ENT Column -22 - $113F – Contractor supplies additional heaters for entrance columns.
4.5.10 Pay on Foot stations incorporated into the system must accept credit cards, debit cards and cash payments and provide customers with change for cash transactions.
4.5.11 Readers must read all parking tickets, credit cards, debit cards, and validation coupons through the same slot.
4.5.12 All payment services included in the system must be compliant with Payment Card Industry Data Security Standards.
4.5.13 Proposal must include access to repair parts and availability of training in repairs and maintenance for all system components.
4.5.14 The system must include RFID proximity card readers and the capability to produce proximity cards which permit parking facility entry and exit.
4.5.15 The system must include the capability for two-way voice communication between each entry gate, exit gate, pay station and Transportation Services staff by mobile device.
4.5.16 The system and equipment must work with the current vehicle detection system or a new vehicle detection system must be installed.
4.5.17 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.5.18 The system must comply with all applicable codes.
DESIRED SPECIFICATIONS
4.6 Desired Specifications
  4.6.1 System architecture and overview
    4.6.1.1 Entry Lanes    
    4.6.1.2 Offices    
      1. Booths    
      2. Central Hub/Network Voice & Data    
        a. Financial Capability    
        b. Reporting Capability    
        c. Administration (Security and Validation)    
      3. Maintenance and upgrades    
      4. Payment Systems    
    4.6.1.3 Exit Lanes    
      1. Validation    
      2. Payment    
  4.6.2 Hardware      
    4.6.2.1 Entry Lanes    
      Components of the entry stations in your system, which generates and receive tickets, receipts, and include a proximity card reader.
      1. Vehicle Detection System    
        a. Testing of all existing loops for integrity, including contingency pricing for each loop.
        b. New vehicle detection equipment    
      2. Ticket dispensing equipment and how it is integrated with the rest of the system
      3. Gate and access control equipment and how it is integrated with the rest of the system.
      4. Operator and customer mistakes and errors.
      5. Communication and display messages, such as variable message signage
    4.6.2.2 Offices    
      1. Booths    
        Hardware components for the booths for the system.    
      2. Central Hub/Network Voice & Data    
        a. Server(s)
          Server or servers required for the system.  Information on hardware (disk, memory, CPU, etc.), and software (operating systems, etc.) requirements.  What vendor components run on each server?
          *We intend for this system to run on servers owned and maintained by Facilities, Planning and Management (FP&M), UW-Madison.
        b. Workstations
          Workstations required for this solution.  What hardware (disk, memory, CPU, etc.), operating systems, etc. are required?  What vendor components run on each workstation?
        c. Network
          Network hardware requirements.  Are industry standard protocols and devices used?
        d. Security
          Security devices/techniques supported by this solution.  For example, are network communications encrypted?  Are fingerprint readers supported?
      3. Maintenance and upgrades    
        a. Hardware Training
          Company’s ability to provide training for:
         
  • System administration, configuration and installation
  • Troubleshooting and diagnostic techniques and tools 
  • Access to on-line knowledge base of common problems
        b. Hardware Warranty
          Warranty for all hardware components included in the system and include a copy of warranty document
      4. Payment Systems    
        a. Pay On Foot stations
          Components of the Pay on Foot customer payment stations in your system.
        b. Pay from Vehicle stations
          Components of the stations for customer payment from vehicles in your system.
    4.6.2.3 Exit Lanes    
      Components of the exit stations in your system, which should receive tickets, provide receipts, and include a proximity card reader.  System will process and/or address.
      1. Vehicle Detection System    
        a. Testing of all existing loops for integrity, including contingency pricing for each loop.
        b. New vehicle detection equipment
      2. Validations
      3. Payments
      4. Operator and customer mistakes and errors
      5. Communication and display messages, such as variable message signage
  4.6.3 Information Technology specifications
    In each numbered section description of the specifications of the system provided to the University
      1. Data Repository Architecture    
        Architecture of data repository for the system.    
      2. Data Security    
        System’s security architecture, including the level of granularity at which security can be applied. Sensitive data (for example, credit card numbers) are stored and whether or not information is encrypted
      3. Data Sharing
       

Description of how the system functions to provide a means to share information from and with external sources.

  • 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 applications that integrate with your system.
  • Ability to accept SMART or declining balance cards
  • How does third party integration, for example, an in-house web application, affect service levels provided by your support staff and the product?
      4. Data Conversion
        Company’s migration plan for all data from identified existing systems to the system.  The conversion and migration plan may include separately priced software and services, but these should be clearly itemized.  At its option, the University may choose to utilize any or all portions of the Contractor's plan, or it may opt to do all data conversion and migration independently
    4.6.3.1 Entry Lanes    
      Components of the exit stations in your system, which should receive tickets, provide receipts, and include a proximity card reader.  System will process and/or address.
      1. Input/Network Voice & Data    
      2. Storage    
      3. Output    
      4. Admin/Management    
    4.6.3.2 Offices    
      1. Input/Network Voice & Data    
      2. Storage    
      3. Output    
      4. Admin/Management    
    4.6.3.3 Exit Lanes    
      1. Input/Network Voice & Data    
      2. Storage    
      3. Output    
      4. Admin/Management    
  4.6.4 Software Specifications
      1. User Data Interfaces    
        System’s user interfaces.  Is the interface a thick client or web based?  If both, how do they differ?
      2. System Administration Interface    
        System’s interface for console operation and system administration.  If the interface is web based, describe how the look and feel of the web client is similar to the operator workstation interface and the methods used to secure the web client.
      3. Interface Security
        System’s security architecture.  Level of granularity supported.  Support for encrypting communications with external service providers (for example, credit card processors).
      4. Customizing Software
       
  • Ability for BASS-IT staff and Transportation Services staff to customize the software to take into account business and validation rules.
  • Ability to add user-defined fields to or associated with records.  Such fields should be searchable with validation rules applied to them.  Values contained in them should appear in pick lists or drop down lists.
  • Ability to store NULL values.
  • Ability to define fields within the application.  For example, if labels are not intuitive, more information should be available with cursor movement.
  • Ability to provide customized graphical user interface for web end users.
  • Explain how pass back features work.
      5. Past, Near-Real-Time and Future Information/Audit Trail
       

System’s capability to store past and future data.

  • Ability to store an audit trail, including user ID’s, of all edits to data.
  • Ability to store and retrieve up to five years worth of data using snapshots and an activity log.
  • Ability to view and use new information immediately (NRT – Near Real Time).
      6. Queries and Reports
       

Report capabilities:

  • Ability to produce standard reports.
  • Ability to produce reports within the application in an industry-acceptable format.
  • Ability to create, save and modify reports with a reusable library of reports available for authorized users, including an option for modifiable parameters.
  • Ability to alias report fields so that end users can see columns represented in their own terms.
  • Ability to define report formats.
  • Ability for end users to run their own reports via a web page.
  • Provide samples.

Query capabilities:

  • Ability to produce standard queries.
  • Ability to query data using wildcards in any or all descriptive fields.
  • Ability to query on any field in the data repository from any point in the system and save the query to a library.
  • Ability to perform ad hoc queries on data using multiple complex search criteria, Boolean logic, and multiple sorting criteria.
  • Ability to save and store queries and their result sets.
  • Ability to export result sets in standard formats.
  • Ability to query data within this system and also data imported from other systems.
  • Ability to present data in graphical form using graphs and charts.
    4.6.4.1 Entry Lanes    
      1. Operating System    
      2. Licensing    
      3. Upgrades    
      4. Compatibility    
      5. Capabilities    
    4.6.4.2 Offices    
      1. Operating System    
      2. Licensing    
      3. Upgrades    
      4. Compatibility    
      5. Capabilities    
    4.6.4.3 Exit Lanes    
      1. Operating System    
      2. Licensing    
      3. Upgrades    
      4. Compatibility    
      5. Capabilities    
  4.6.5 Training
      1. Support Model    
       
  • Support model. 
  • Does your firm provide all support? 
  • How is the support process initiated?
  • How long will it take for a response to support requests? 
  • How are calls tracked? 
  • If the customer is supported by an Information Technology department, how do you propose splitting support responsibilities? 
  • Extent to which University Information Technology staff can perform service requirements, both during and after warranty periods.
      2. Software Support
       
  • Software support plan for the proposed system. 
  • System has the ability for support representatives to communicate with the system remotely for troubleshooting purposes.
      3. Software Training
       
  • Comprehensive training plan to meet the conversion, implementation, operation, system administration, and development needs as they relate to software components of your proposed system.
  • Specific courses required, duration, location and a tentative schedule for each course.
      4. Software Upgrades
       
  • 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.
  • Who installs patches, upgrades and new software versions – the customer or the vendor?  How is the patch/upgrade process initiated?
  • How is training provided for patches, upgrades and new software versions?
      5. Software Installation Pre-Implementation Planning
       

Pre-implementation planning sessions to discuss implementation options and to devise and adopt a strategy for the successful implementation of the proposed system.

Topics to be covered may include, but are not restricted to, software installation, training of software users and system administrators, data conversion, and a step-by-step strategy for the transition from the current system to the new system.  Identification of current practices, policies, and procedures which will have to be abandoned or adjusted in the transition to the new system, as well as new procedures which will need to be adopted.
      6. Software Setup and Installation
        Contractor’s ability to provide support and assistance with your system software installation and setup.
      7. System Administration Specifications
        System administration specifications of the parking ramp access and revenue control system provided to the University.
      8. User/Password Administration
       
  • Parking ramp access and revenue control system accomplishes and organizes passwords and user ID’s. 
  • Software login procedure and how the passwords (and login, if applicable) are configured and administered in your system. 
  • Integration with Windows
  • Active Directory to provide single sign-on capability. 
  • Where are user ID’s and passwords stored? 
  • Are passwords encrypted? 
  • Ability to create and disable default user ID’s and passwords
      9. Scheduling
        System supports scheduled jobs.
      10. Information Backup and Retrieval
       
  • 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.
      11. System Administration Activity
        System administration activity specific to your system to keep it functioning.
      12. Event Logging
       

System logs system events, including category types, severity levels, granularity of logging, ability to change logging levels on the fly, and other relevant information about event logging in your system.

The system should have the ability to raise the entry/exit gates remotely and this should be a recordable event within the system
    4.6.5.1 Entry Lanes    
      1. Who, What, When, Where, How (Timelines, Deadlines)
      2. Scenarios    
      3. On-going    
    4.6.5.2 Offices    
      1. Who, What, When, Where, How (Timelines, Deadlines)
      2. Scenarios    
      3. On-going    
    4.6.5.3 Exit Lanes    
      1. Who, What, When, Where, How (Timelines, Deadlines)
      2. Scenarios    
      3. On-going    
    4.6.5.4 Staff Qualifications    
      1. Training Demonstrations
  4.6.6 UW-Madison Involvement
    Facilities, Planning & Managements (FP&M) computer support and electricians are able to service the components of the network and system architecture as desired by Transportation Services.
      1. Service requirements for software and hardware components of the system can be performed by University personnel from Information Technology and Physical Plant units, both during and after warranty periods
      2. Software and hardware components that will not be serviceable by UW personnel.
    4.6.6.1 Entry Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.6.2 Offices    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.6.3 Exit Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
  4.6.7 Warranties
    Warranty coverage, including time periods, of the system you propose to provide.
    4.6.7.1 Entry Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.7.2 Offices    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.7.3 Exit Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
  4.6.8 Delivery and Implementation
    4.6.8.1 Entry Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.8.2 Offices    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    
    4.6.8.3 Exit Lanes    
      1. Electrical    
      2. Mechanical    
      3. Information Technology    
      4. Access    
      5. Security    

Revision History
(3/27/13): added Manufacturer represented:  SkiData for Don Harstad Co.
link to top of document