HomeMy WebLinkAboutCC Resolution 11189 (Purchase Parking Access & Revenue Control Systems)RESOLUTION NO. 11189
RESOLUTION OF THE CITY COUNCIL OF THE CITY OF SAN
RAFAEL AUTHORIZING THE CITY MANAGER TO ENTER INTO
A CONTRACT WITH SENTRY CONTROL SYSTEMS, INC., IN A
FORM TO BE APPROVED BY THE CITY ATTORNEY, FOR THE
PURCHASE OF PARKING ACCESS AND REVENUE CONTROL
SYSTEMS IN AN AMOUNT NOT TO EXCEED $450,000.
WHEREAS, on the 15th day of July, 2002, pursuant to Resolution 11133, the City
Council did grant permission to contract for the purchase of parking access and revenue control
systems by use of Competitive Negotiation, pursuant to San Rafael Municipal Code section
2.55.200; and:
WHEREAS, on the 18th day of July, 2002, pursuant to due and legal notice published in
a manner provided by law, inviting sealed proposals for the equipment hereinafter mentioned, the
Parking Services Manager of the City of San Rafael did publicly open, examine and record all
sealed proposals for furnishing the following equipment:
PARKING ACCESS AND REVENUE CONTROL SYSTEMS - BID NO. 00-00
in accordance with the specifications therefore on file in the office of said City Clerk; and
WHEREAS, Sentry Control Systems, Inc., has been ranked by the Staff Parking
Equipment Replacement Committee as the most qualified and responsive vendor, based upon the
evaluation criteria communicated to the vendors; and staff recommends the contract for the
purchase of this equipment be awarded to said vendor.
NOW, THEREFORE, IT IS HEREBY RESOLVED by the City Council of the City of
San Rafael that the City Manager is authorized to enter into a contract, in a form to be approved
by the City Attorney, with Sentry Control Systems, Inc., for purchase of Parking Access And
Revenue Control Systems for use in the off-street parking garages in San Rafael, in a total
amount not to exceed $450,000.
I, JEANNE M. LEONCINI, City Clerk of the City of San Rafael, hereby certify that the
foregoing Resolution was duly and regularly introduced and adopted at a regular meeting of the
City Council of said City held on Monday, October 21, 2002, by the following vote, to wit:
AYES: COUNCILMEMBERS: Cohen, Heller, Phillips and Mayor Boro
NOES: COUNCILMEMBERS: None
ABSENT: COUNCILMEMBERS: Miller
JEIA M.
A. M. .
LEONCINI, City Cleric
AGREEMENT FOR PARKING ACCESS
AND REVENUE CONTROL EQUIPMENT
This Agreement is made and entered into this 28th day of March 2003, by and between the
CITY OF SAN RAFAEL (hereinafter "CITY"), and Sentry Control Systems, Inc., (hereinafter
"CONTRACTOR').
WHEREAS, the City of San Rafael intends to replace the Parking Access and Revenue
Control Equipment in the City's parking garage facilities; and
WHEREAS, the City Council of the City of San Rafael has granted authority to the City
Manager, by the passing of Resolution 11189 on the 21St day of October, 2002, to contract for the
purchase of this equipment; and
WHEREAS, the Parking Services Division has selected Sentry Control Systems, Inc. to
provide said equipment and service.
NOW, THEREFORE, the parties hereby agree as follows:
A. CITY. The City Manager shall be the representative of the CITY for all purposes
under this Agreement. The Parking Services Manager is hereby designated the PROJECT
MANAGER for the CITY, and said PROJECT MANAGER shall supervise all aspects of the
progress and execution of this Agreement.
B. CONTRACTOR. CONTRACTOR shall assign a single PROJECT DIRECTOR
to have overall responsibility for the progress and execution of this Agreement for
CONTRACTOR. Timothy Flanagan is hereby designated as the PROJECT DIRECTOR for
CONTRACTOR. Should circumstances or conditions subsequent to the execution of this
Agreement require a substitute PROJECT DIRECTOR for any reason, the CONTRACTOR shall
notify the CITY within ten (10) business days of the substitution.
CONTRACTOR shall provide all materials, services, and equipment as set forth in the
RFP for the purchase of Parking Access and Revenue Control Systems, RFP 00-00, dated June 12,
2002, as modified to incorporate the agreed upon modifications to the specifications, as described
in Exhibit "A" attached and incorporated herein, with such options, additions, eliminations and
discounts, as described in Exhibit "B" attached and incorporated herein, as may be selected by the
CITY at its sole discretion.
CONTRACTOR also shall open within one hundred and eighty (180) days of the date of
this agreement and thereafter maintain during the term of this agreement, a service center within
seventy-five (75) miles of the City of San Rafael. CONTRACTOR shall employ at such service
center one or more full-time employees with expertise in maintenance and upkeep of the equipment
and materials purchased under this Agreement, and shall stock at such service center an on-time
inventory of parts and replacements necessary for maintenance of such equipment and materials.
CONTRACTOR shall provide CITY with the address and telephone number for such service
center and the names of the employees there employed. If at any time the CONTRACTOR
breaches this service center obligation, the parties agree that the CITY shall be entitled to
liquidated damages in the amount of $50,000. The existence of this liquidated damages remedy
shall not affect in any way the CONTRACTOR'S warranty obligations under this Agreement.
CONTRACTOR shall furnish a Performance Bond in an amount of 100% of the total cost
of the Contract amount prior to beginning any work, or receiving any compensation and no later
than April 15, 2003.
In consideration of the CONTRACTOR's performance of the duties provided in paragraph
2, the CITY shall pay compensation in an amount not to exceed $450,000.00 for the purchase of
units in a quantity to be determined at the sole discretion of the City, in the amounts as specified in
the City of San Rafael Proposal and described in Exhibit `B" the attached hereto and incorporated
herein.
For the full performance of the services described herein by CONTRACTOR, CITY shall
pay CONTRACTOR a fee in an amount not to exceed $450,000.00, and pursuant to resolution
11189.
Payment will be made based on a percentage of the total contract agreed upon by both
parties which has been completed and accepted by the CITY, and upon receipt by PROJECT
MANAGER of an itemized invoice submitted by CONTRACTOR.
Except as terminated as provided in Paragraph 6, the term of this Agreement shall continue
from the date of this Agreement until forty-eight (48) months following the City's written
acceptance of the equipment and materials as being in conformance with the specification described
in Section IV of Exhibit "A" attached hereto.
A. Cause. Either party may terminate this Agreement for cause upon fifteen (15) days
written notice mailed or personally delivered to the other party, and the notified party's failure to
2
cure or correct the cause of the termination, to the reasonable satisfaction of the party giving such
notice, within such fifteen (15) day time period.
B. Effect of Termination. Upon receipt of notice of termination, neither party shall
incur additional obligations under any provision of this Agreement without the prior written consent
of the other.
C. Return of Documents. Upon termination, any and all CITY documents or
materials provided to CONTRACTOR and any and all of CONTRACTOR's documents and
materials prepared for or relating to the performance of its duties under this Agreement, shall be
delivered to CITY as soon as possible, but not later than thirty
(30) days after termination.
The written documents and materials prepared by the CONTRACTOR in connection with
the performance of its duties under this Agreement, shall be the sole property of CITY. CITY may
use said property for any purpose, including projects not contemplated by this Agreement.
Upon reasonable notice, CONTRACTOR shall make available to CITY, or its agent, for
inspection and audit, all documents and materials maintained by CONTRACTOR in connection
with its performance of its duties under this Agreement. CONTRACTOR shall fully cooperate
with CITY or its agent in any such audit or inspection.
The parties agree that they shall not assign or transfer any interest in this Agreement nor the
performance of any of their respective obligations hereunder, without the prior written consent of
the other party, and any attempt to so assign this Agreement or any rights, duties or obligations
arising hereunder shall be void and of no effect.
A. During the teen of this Agreement, CONTRACTOR shall maintain, at no expense
to CITY, the following insurance policies:
1. A comprehensive general liability insurance policy in the minimum amount
of one million ($1,000,000) dollars per occurrence for death, bodily injury, personal injury, or
property damage;
2. An automobile liability (owned, non -owned, and hired vehicles) insurance
policy in the minimum amount of one million ($1,000,000) dollars per occurrence;
3. If any licensed professional performs any of the services required to be
performed under this Agreement, a professional liability insurance policy in the minimum amount
of one million $1,000,000) dollars to cover any claims arising out of the CONTRACTOR's
performance of services under this Agreement.
B. The insurance coverage required of the CONTRACTOR by section 9. A., shall
also meet the following requirements:
1. The insurance shall be primary with respect to any insurance or coverage
maintained by CITY and shall not call upon CITY's insurance or coverage for any contribution;
2. Except for professional liability insurance, the insurance policies shall be
endorsed for contractual liability and personal injury;
3. Except for professional liability insurance, the insurance policies shall be
specifically endorsed to include the CITY, its officers, agents, employees, and volunteers, as
additionally named insureds under the policies.
4. CONTRACTOR shall provide to City's Risk Manager, (a) Certificates of
Insurance evidencing the insurance coverage required herein, and (b) specific endorsements naming
CITY, its officers, agents, employees, and volunteers, as additional named insureds under the
policies.
S. The insurance policies shall provide that the insurance carrier shall not
cancel, terminate or otherwise modify the terms and conditions of said insurance policies except
upon thirty (30) days written notice to City's Risk Manager.
6. If the insurance is written on a Claims Made Form, then, following
termination of this Agreement, said insurance coverage shall survive for a period of not less than
five years;
7. The insurance policies shall provide for a retroactive date of placement
coinciding with the effective date of this Agreement;
8. The insurance shall be approved as to form and sufficiency by PROJECT
MANAGER and the City Attorney.
C. If it employs any person, CONTRACTOR shall maintain worker's compensation
and employer's liability insurance, as required by the State Labor Code and other applicable laws
and regulations, and as necessary to protect both CONTRACTOR and CITY against all liability
for injuries to CONTRACTOR's officers and employees.
D. Any deductibles or self-insured retentions in CONTRACTOR's insurance policies
must be declared to and approved by the City's Risk Manager and the City Attorney. At CITY's
4
option, the deductibles or self-insured retentions with respect to CITY shall be reduced or
eliminated to CITY's satisfaction, or CONTRACTOR shall procure a bond guaranteeing payment
of losses and related investigations, claims administration, attorney's fees and defense expenses.
1►1� u1►11 � ►
CONTRACTOR shall indemnify, release, defend and hold harmless CITY, its officers,
agents, employees, and volunteers, against any claim, demand, suit, judgment, loss, liability or
expense of any kind, including attorney's fees and administrative costs, arising out of or resulting in
any way, in whole or in part, from any acts or omissions, intentional or negligent, of
CONTRACTOR or CONTRACTOR'S officers, agents and employees in the performance of
their duties and obligations under this Agreement."
� ► • ►It i lull► : • ►
CONTRACTOR shall not discriminate, in any way, against any person on the basis of age,
sex, race, color, religion, ancestry, national origin or disability in connection with or related to the
performance of its duties and obligations under this Agreement.
13. (':DTyT IAMCF. WTTH AT J, TAWS.
CONTRACTOR shall observe and comply with all applicable federal, state and local laws,
ordinances, codes and regulations, in the performance of its duties and obligations under this
Agreement. CONTRACTOR shall perform all services under this Agreement in accordance with
these laws, ordinances, codes and regulations. CONTRACTOR shall release, defend, indemnify
and hold harmless CITY, its officers, agents and employees from any and all damages, liabilities,
penalties, fines and all other consequences from any noncompliance or violation of any laws,
ordinances, codes or regulations.
14. NO THMD PARTY -RENF.FI TARTF.S.
CITY and CONTRACTOR do not intend, by any provision of this Agreement, to create in
any third party, any benefit or right owed by one party, under the terms and conditions of this
Agreement, to the other party.
15. NOTICES.
All notices and other communications required or permitted to be given under this
Agreement, including any notice of change of address, shall be in writing and given by personal
delivery, or deposited with the United States Postal Service, postage prepaid, addressed to the
parties intended to be notified. Notice shall be deemed given as of the date of personal delivery, or
if mailed, upon the date of deposit with the United States Postal Service. Notice shall be given as
follows:
5
TO CITY: Chad Lynn
Parking Services Manager
City of San Rafael
1400 Fifth Ave. (P.O. Box 151560)
San Rafael, CA 944915-1560
TO CONTRACTOR: Tim Flanagan
Sentry Control Systems, Inc.
9842 Glenoaks Blvd.
Sun Valley, Ca 91352
1►1� ►11 ►1191,01YI •
For the purposes, and for the duration, of this Agreement, CONTRACTOR, its officers,
agents and employees shall act in the capacity of an Independent Contractor, and not as employees
of the CITY. CONTRACTOR and CITY expressly intend and agree that the status of
CONTRACTOR, its officers, agents and employees be that of an Independent Contractor and not
that of an employee of CITY.
►11 1:• 810INDENWik
A. The terms and conditions of this Agreement, all exhibits attached, and all
documents expressly incorporated by reference, represent the entire Agreement of the parties with
respect to the subject matter of this Agreement.
B. This written Agreement shall supersede any and all prior agreements, oral or
written, regarding the subject matter between the CONTRACTOR and the CITY.
C. No other agreement, promise or statement, written or oral, relating to the subject
matter of this Agreement, shall be valid or binding, except by way of a written amendment to this
Agreement.
D. The terms and conditions of this Agreement shall not be altered or modified except
by a written amendment to this Agreement signed by the CONTRACTOR and the CITY.
E. If any conflicts arise between the terms and conditions of this Agreement, and the
terms and conditions of the attached exhibits or the documents expressly incorporated by reference,
the terms and conditions of this Agreement shall control.
T
CONTRACTOR agrees that CITY may deduct from any payment due to
CONTRACTOR under this Agreement, any monies which CONTRACTOR owes CITY under
any ordinance, agreement, contract or resolution for any unpaid taxes, fees, licenses, assessments,
unpaid checks or other amounts.
The waiver by either party of any breach or violation of any term, covenant or condition of
this Agreement, or of any ordinance, law or regulation, shall not be deemed to be a waiver of any
other term, covenant, condition, ordinance, law or regulation, or of any subsequent breach or
violation of the same or other term, covenant, condition, ordinance, law or regulation. The
subsequent acceptance by either party of any fee, performance, or other consideration which may
become due or owing under this Agreement, shall not be deemed to be a waiver of any preceding
breach or violation by the other party of any term, condition, covenant of this Agreement or any
applicable law, ordinance or regulation.
f •. ►It r r • : ►1
The prevailing party in any action brought to enforce the terms and conditions of this
Agreement, or arising out of the performance of this Agreement, may recover its reasonable costs
(including claims administration) and attorney's fees expended in connection with such action.
CONTRACTOR shall obtain and maintain during the duration of this Agreement, a CITY
business license as required by the San Rafael Municipal Code. CONTRACTOR shall pay any
and all state and federal taxes and any other applicable taxes. CONTRACTOR's taxpayer
identification number is 33-0311403, and CONTRACTOR certifies under penalty of perjury that
said taxpayer identification number is correct.
7
The laws of the State of California shall govern this Agreement.
IN WITNESS WHEREOF, the parties have executed this Agreement as of the day, month
and year first above written.
CITY OF SAN RAFAEL
ROD GOULD, City Manager
ATTEST:
JLVANNE M. LEON , City Clerk
APPROVED AS TO FORM:
?���`�
GARY T. RAGGHIANTI, City Attorney
II19cr
1.1
CONTRACTOR
By: -54;—L
Name:
Title: C� U
(Revised 6/99)
Title: Revenue Control and Parkina Management Eubment
Exhibit "A"
CITY OF SAN RAFAEL
PARKING SERVICES DIVISION
1400 FIFTH AVE❑SAN RAFAEL, CALIFORNIA
94901 0(415) 485-3070
LEGAL NOTICE - BIDS WANTED
BID NO. 00-00
Sealed proposals are requested on the list of materials, supplies, equipment or services set
forth herein, subject to all conditions outlined in the Bid Document, including:
SECTION I: REQUEST FOR BIDS
SECTION II: GENERAL INFORMATION AND INSTRUCTIONS
SECTION III: AGREEMENT
SECTION IV: DETAIL SPECIFICATIONS
SECTION V: BID FORM
***(IF YOU CHOOSE NOT TO BID, PLEASE COMPLETE ONLY THE "NO BID"
PAGE IN SECTION 10'
Sealed proposals will be received only at the Office of the Citv Manaaer, 1400 Fifth Ave, San
Rafael, Ca 94901 until 2:00 p.m. local time, on the dates hereinafter stated at which time they
will be opened and publicly read for furnishing the materials, supplies, equipment or services or
for supplying the materials, and/or providing labor for the repair, construction or improvement
as the case may be, as indicated by the items hereunder listed and in accordance with the
applicable specifications.
Date of Request:
Bid Number:
SECTION I - REQUEST FOR BID
June 12, 2002
Item Description: Parking Revenue Control and Facility Management Equipment
Bid Opening: July 10, 2002 at 2:00 pm
AMMENDED to July 18, 2002 at 2:00 pm
All bids must be delivered by the specified opening time of the bid. Bids arriving after the
specified hour will not be accepted. Mailed bids, which are delivered after the specified hour
will not be considered regardless of postmarked time on the envelope. All bids must be in
writing and must contain an original signature by an authorized officer of the firm - Electronic
bids (telephone, FAX, etc.) are NOT acceptable.
BID DEPOSIT - NONE REQUIRED WITH THIS BID
Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parking Manaaement Eubment
PERFORMANCE BOND AND PAYMENT BOND - NONE REQUIRED WITH THIS BID
2 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Management Eubment
CITY OF SAN RAFAEL
SECTION II - GENERAL INFORMATION AND INSTRUCTION
1. Bidders are advised to become familiar with all conditions, instructions and
specifications governing this bid. Once the award has been made, a failure to have
read all the conditions, instructions and specifications of this contract shall not be cause
to alter the original contract or for vendor to request additional compensation.
2. Bidders agree to defend and save the City from and against all demands, claims, suits,
costs, expenses, damages and adjustments based on any infringement of any patent
relating to goods specified in this contract.
3. Successful bidder shall not assign the contract, or subcontract the whole or any part of
the contract without written consent of the City. Such consent shall neither relieve the
bidder from his obligation nor change the terms of the contract.
4. The City shall have the right to inspect any material specified herein. Equipment,
supplies or services that fail to comply with the specifications herein regarding design,
material or workmanship are subject to rejection at the option of the City. Any materials
rejected shall be removed from the premises of the City at the expense of the vendor.
5. Bidder shall state the nature and period of any warranty or guarantee. Manufacturer's
specifications shall be submitted with the bid and shall be considered a part of this
contract where such specifications meet the minimum of the City specifications.
6. Each bidder shall submit in full this completed original BID DOCUMENT and all
necessary catalogues, descriptive literature, etc., needed to fully describe the materials
or work they propose to furnish.
7. Bidders shall state the delivery date for commodities in terms of calendar days after
notification of award. Where the contract calls for performance of labor, the bidder shall
also state the number of calendar days required for completion after notification of
award.
8. Cash discounts shall be considered in the evaluation of the bids, except that payment
periods of less than thirty (30) days will not be considered in award of this bid. Where
cash discounts are offered, the discount date shall begin with the invoice date or
delivery date to the City, whichever is later.
9. Alternative financing options shall be considered in the evaluation of the bids. All
proposed financing proposals and terms shall end with the City as the sole owner of the
products.
10. Upon the award of the bid to the successful bidder, if insurance is required by the terms
of this bid, the City will require evidence of such coverage be furnished within fourteen
(14) days of notification of bid award. The amounts and tvnes of coverage will be
specified in Section III of this bid. All insurance forms must be in a format
acceptable to the City.
3 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkino Manaaement EuiDment
11. The Contractor agrees to indemnify, defend and hold harmless the City, City Council
and each member thereof, and every officer, and employee of the City, from any liability
or financial loss including, without limitation, attorneys fees and costs, arising in any
manner whatsoever from any intentional, reckless, negligent, or otherwise wrongful acts,
errors or omissions of Contractor, or any person employed by Contractor, including
agents and independent contractors, in the performance of this agreement.
12. Every supplier of materials and services and all contractors doing business with the City
shall be an "Equal Opportunity Employer" as defined by Section 2000 (E) of Chapter 21,
Title 42 of the United States Code Annotated and Federal Executive Orders #11375,
and as such shall not discriminate against any other person by reason of race, creed,
color, religion, age, sex or physical or mental handicaps with respect to the hiring,
application for employment, tenure, terms or conditions or employment of any person.
13. The successful bidder agrees to obtain and/or maintain a proper City business license
when working for or within the territorial limits of the City.
14. Prices quoted herein must be firm for a period of not less than ninety (90) days after
date of bid opening.
15. Bids calling for other than a "lump sum" total bid may be awarded by single item, by
groups of items, or as a whole, as the City deems to be in the best interest of the City.
16. The City will be the sole and exclusive judge of quality, compliance with bid
specifications or any other matter pertaining to this bid. The City reserves the exclusive
right to award this bid in any manner it deems to be in the best interest of the City.
17. Quantities specified in Section IV are approximate only, the City reserves the right,
within the period for delivery to increase or decrease the quantity ordered and upon
mutual agreement after the period specified for delivery, order additional quantities of
items bid.
18. Contractor shall cooperate with the City in all matters relating to taxation and the
collection of taxes. It is the policy of the City to self -accrue use tax associated with its
own purchases. The City requests that its contractors self -accrue their use tax, when
applicable, and report the use tax to the State Board of Equalization with a City -
assigned permit number. The City's own use tax which is self -accrued by the City will
be remitted to the State of California pursuant to the City's permit with the State Board
of Equalization."
19. The submittals will be evaluated based on the ablility to meet the specifications,
serviceability, functionality, price, and financing options. The most qualified and
responsive proposals (minimum of three (3)) will be selected for contract negotiation.
Negotiations will be conducted individually with each qualified supplier and a committee
to be determined by the City. All elements of the negotiation process shall be
documented by the project manager. Responsible offers shall be accorded fair and
equal treatment with respect to opportunity for discussion and revision of proposals, and
such revisions may be permitted after submission in writing and prior to award for the
purpose of obtaining the best final offer.
4 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Management Euinment
20. Estimated tmeline for the award of this bid will be as follows:
• RFP Response by July 10, 2002.
• Bid review, interviews and negotiations by July 25, 2002.
• Site visits and bid award by August 2, 2002.
• Shop drawings for new facility construction by August 23, 2002.
• Installation/Retrofit of 3`d & A St. garage TBD.
• Installation of 3`d and C St. garage, TBD by General Contractor.
21. For any questions or site visits regarding this bid, please contact Chad Lynn, Parking
Services Manager at 415.485.3070.
22. Please submit five (5) identical copies of your response to this RFP.
5 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkino Manaaement Eubment
SECTION III —AGREEMENT
CITY OF SAN RAFAEL
SECTION III - AGREEMENT FOR PARKING ACCESS AND REVENUE CONTROL
EQUIPMENT
..� .��■ R
r .. .
_ w
_ _ .. _ - _ .ter ■ r.
- - -
r
� r
. \ Llj&Gfe6Gf 'r'�t4. r party may termigate this - Agreement withOui}__Ga-ure UPGRn
thirty (30) days wFitteR RE)tiGe mailed eF PeFSGRally de!WeFed to the ether
Q. C'auma. ■ itli��efm4iatez.TT& Agreeme4 far rra se i,ngr. fiiftdays written netiGe mailed er- pemenally delivered to the ether party, and the �,r,n
V ,fci`!`1 r?
period.
C. E `-_\h. Upgri W MiPRtign neither party shall
of the other,
C.
,
Fnatffiais prepared fGF OF Felatirig to the peFfE)FmaRce of its cluties under this t, ahcll be
C_jPl;1'RrPH to CITY as soeR as possible, but not h. n thirty .
T QWNEoculo QF DC)GU ENTc
Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Management Euioment
The t
the peFfeFmaRGe ef its duties URdeF this AgFeemeRt, shall be the sole PFGpeFty ef CITY. CITY may
Upon FeaseRable notiee, CONTRACTOR shz;ll rcke available to CITY, eF its agent, f'eF
with ks peFfGFmaRGe ef-its duties undeF this AgFeement. GONTPACTO peFate with
CITY GF SUGh audit
E. AiTIGNABI ITv
T
ad` the ocr
'Z Of Re effeGt.
?. INSURANCE.
A D n the term of this A,
to -CITY, the €el4ewiS incercnse policies: -
1. A sempr minimum cmauM
death,of one Fnoll;en ($4,000,000) dollars per OGGUFFeRGe fGF
bedily nal
propeFty
?. An-autemc!�!c KLifi s) ir,LAm4Ge
3. 1`
I 0. !RSUFaRE;e pe!iGy OR the Fniwnum amount
,
Lir;uing out of the CONTRACTOR's
W. ., &211 2139
Fneet the following FeqLJiFeFnents-.
1. Tha ;neUFanGe shall be grin -wry with respeGt tG any iRSUFaRGe GF coverage
rr,&M�n 'i ingirmse OF eeyemeo fer aRy ^antri!1Aia
3 Gr^���cncl livl:iUy irw6:rcnce;-#c inuurcese peki3a ohall be
cticl `atilit�^d perscnal injw
3. EXGept fGF pFefessiGRal liability iRSUFaRce, the insuFaRGe policies shall be
CC v Risk A
7 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parking Manaaement Euiament
the PO!iGies:
E. Th, insyFaRGe p0kies shall provide that the iRSUFaRGe raFrier Jticll n9t
GaPGelr
UPGR thirty (30) days witteR RGtiGe to City's Risk ManageF.
I�'— , Geis wtteR on a C!cimc Made FOFFn, then,
teHninat;OR of this Agreement, said insuranGe GoveFage shall suFvive fGF a peFied Gf RGt less thaR
€v"ear-
�e,eiri for troaGtiye ate of nla Gement
'. T��-;r�edr�r�e-�e4iev�� •hsll Fra.,-,o,--aTG��� asa�,crc,c•nTcrrc
GGiAdcling with the effeGtWe date of this AgFeernef#j
8. Ths i.
MANAGER and the Gity Attemey.
C. If it 1
and pleyir'3 lijki'
SQir%t all k2bility feF
'• inurc^.p^'�e
must be deelaFed to and appFOved by the Gity's Risk ManageF and the Gity A#GFRey. At G!
eI;min•cted t„ r'ITY c c -ti
,
of le o and related investigations slcims r4,dminiStr.•.tien attorney's fees and defenses ovonncne
E. IR'. -
CC' ,
agvntC, amY I , aScin3t eny—ria,m, demand,suit, judgmeRt, Incv, nliability 0expense ef any r,
' Ct1, diming `��,t of or rest ltT�inn
t T�
iR whole or in ti.rt, #Fam cny aGtS GF GMiGSiGRG, '
9. .
10runnel IANGE WITH AI 1 I Alec
r ccc o ct�-,T
CCtNT-Rq ith cll 2W!4Gable- .,&l, cWt
AgFeemeRt. CONTRACTOR chell pc 1 rm all `anti3nn t rURdeFThi-_A�nQcr�oGmrrGnt in .Si3awdaMe with
these laws, EwdiRaRees, c;edes and regulatiens. CONTRACTOR shall Felease, defeRd, iRdempgy
CITY, , ageRts and employees from aRy and all damages, bilitiCS
Exhibit "A"
Revenue Control and Parking Management Equipment ,
Parking Equipment Specifications
For
The City of San Rafael, California
12
Revenue Control and Parking Management Equipment
Table of Contents
1. GENERAL INFORMATION...........................................................................................................................14
CURRENT CONDITION: THE CITY OF SAN RAFAEL HAS A PARKING SYSTEM CONTAINING 7 METERED SURFACE LOTS, 2
METERED STRUCTURED FACILITIES, 792 ON -STREET METERED SPACES AND ONE OFF-STREET FULLY CONTROLLED
FACILITY. THE CITY IS CURRENTLY IN THE PROCESS OF CONSTRUCTING A SECOND OFF-STREET STRUCTURED PARKING
FACILITY. CONSTRUCTION WILL START IN THE EARLY PART OF 2003, WEATHER PERMITTING .................................. 14
1.2.
GENERAL DESCRIPTION: THIS RFP IS FOR A FULLY AUTOMATED PARKING REVENUE CONTROL SYSTEM TO BE
INSTALLED IN BOTH THE EXISTING FACILITY AND THE PROPOSED NEW PARKING FACILITY .........................................
14
1.3.
INCLUSIONS: .................................................................................................................................................
14
1.4.
LIST OF ABBREVIATIONS...............................................................................................................................
14
1.5.
SYSTEM DESCRIPTION & OVERVIEW.............................................................................................................
16
1.6.
RATES..................................................................................................... ERROR! BOOKMARK NOT DEFINED.
1.7.
TYPICAL DEDICATED TICKET ENTRY............................................................................................................
17
1.8.
EXCEPTION TICKET ENTRY...........................................................................................................................
18
1.9.
TYPICAL DEDICATED AV-I/PC ENTRY...........................................................................................................
18
1.10.
EXCEPTION AV-1/PC ENTRY......................................................................................................................
20
1.11.
REVERSIBLE ENTRANCE LANE............................................................ ERROR! BOOKMARK NOT DEFINED.
1.12.
CENTRAL CASHIERING OVERVIEW............................................................................................................
20
1.13.
TYPICAL DEDICATED TICKETED EXIT.......................................................................................................
20
1.14.
EXCEPTION TICKET EXIT...........................................................................................................................
22
1.15.
TYPICAL DEDICATED AI/PC EXIT..........................................................................................................
22
1.16.
EXCEPTION AV-1/PC EXIT.........................................................................................................................
23
1.17.
REVERSIBLE EXIT LANE......................................................................ERROR! BOOKMARK NOT DEFINED.
1.18,
TYPES OF COUNTS.....................................................................................................................................
23
1.19.
CAPACITY.................................................................................................................................................
25
1.20.
QUALIFICATIONS.......................................................................................................................................
26
1.21.
ELECTRICAL DEVICES...............................................................................................................................
26
1.22.
SUBMITTALS.............................................................................................................................................
27
1.23.
RESPONSIBILITIES OF CONTRACTOR..........................................................................................................
28
1.24.
WIRING.....................................................................................................................................................
30
1.25.
PROJECT RECORD DOCUMENTS................................................................................................................
30
1.26.
WARRANTY & SERVICE REQUIREMENTS..................................................................................................
30
1.27.
WARRANTY RESPONSE TIME....................................................................................................................
30
1.28.
PERFORMANCE OF WARRANTY REPAIRS...................................................................................................
31
1.29.
MANNER OF CONDUCT DURING ORIGINAL WARRANTY PERIOD..............................................................
31
1.30.
LIMITATIONS OF WARRANTY....................................................................................................................
32
2. PRODUCTS........................................................................................................................................................34
2.1. MANUFACTURERS.........................................................................................................................................34
2.2. TYPES & QUANTITIES OF EQUIPMENT TO BE PROVIDED................................................................................ 34
2.3. PERFORMANCE SPECIFICATIONS.................................................................................................................... 36
3. SYSTEM INTRODUCTION............................................................................................................................. 54
3.1. GENERAL......................................................................................................................................................54
3.2. THE PRIMARY GOALS OF THE ON-LINE SYSTEMS ARE AS FOLLOWS: .............................................................. 54
3.3. SYSTEM GENERAL REQUIREMENTS...............................................................................................................54
3.4. REVENUE SYSTEM: GENERAL REQUIREMENTS............................................................................................. 57
4. EXECUTION......................................................................................................................................................76
4.1. GENERAL...................................................................................................................................................... 76
4.2. EXHIBITS.................................................................................................ERROR! BOOKMARK NOT DEFINED.
13' Exhibit "A"
Revenue Control and Parking Management Equipment
1. GENERAL INFORMATION
Current Condition: The City of San Rafael has a parking system containing 7 metered surface
lots, 2 metered structured facilities, 792 on -street metered spaces and one off-street fully
controlled facility. The City is currently in the process of constructing a second off-street
structured parking facility. Construction will start in the early part of 2003, weather
permitting.
1.1.1. Existing Facility: The existing facility is located on the southern half of the block
bordered by 3rd and 4th Streets to the North and South and A and B Streets to the
East and West. This facility has 396 total parking spaces, 35 of which are located in
the southwest section of the first floor in an area that is currently outside of the
existing controlled parking area. In the future this area will remain outside of the
controlled parking area. The remainder of the facility is controlled by traditional
parking gates, ticket dispenser, card readers, and cashiered exit.
1.1.2. Planned New Controlled Off -Street Facility: The City of San Rafael is currently
constructing a new 400 space parking facility located on the southern half of the block
bordered by 3rd and 4th street to the south and north and B and C Street to the East
and West.
U. General Description: This RFP is for a fully automated Parking Revenue Control System
to be installed in both the existing facility and the proposed new parking facility.
1.3. Inclusions:
Incorporate into the work materials and equipment conforming to the applicable specifications,
codes and standards and complying with the size, make, type, design, quality, capacity and
performance shown or specified, unless otherwise specifically approved in writing by the CITY
and Engineer.
1.4. List of Abbreviations
1.4.1. ACS Access Control System
1.4.2. ANSI American National Standards Institute
1.4.3. AVI Automatic Vehicle Identification (Transponder activated monthly parking
access)
1.4.4. CITY City of San Rafael
14 Exhibit "A"
Revenue Control and Parking Management Equipment
1.4.5. CCF
Central Cashiering Facility
1.4.6. CMS
Changeable Message Sign
1.4.7. Consultant
The Parking Network
1.4.8. DL
Detector Loop
1.4.9. Engineer Engineers Design Group
1.4.10.
EN Entrance or Entry
1.4.11.
EV Exit Verifier
1.4.12.
FMS Facility Management System (PC Hardware & Software)
1.4.13.
GC General Contractor
1.4.14.
ID Identification
1.4.15.
LC Local Controllers
1.4.16.
LN Lane
1.4.17.
NEMANational Electrical Manufacturing Association
1.4.18.
PC Proximity Card
1.4.19.
POF Pay On Foot
1.4.20.
PARCS Parking Access, Revenue, and Count System
1.4.21.
PC Personal Computer
1.4.22.
PIN Personal Identification Number
1.4.23.
Proposer You, also "Contractor"
1.4.24.
RCS Revenue Control System
1.4.25.
TD Ticket Dispenser
1.4.26.
UPS Uninterruptable Power Supply
1.4.27.
VMS Variable Message Sign
15 Exhibit "A"
Revenue Control and Parking Management Equipment
1.4.28. Vend A gate open command, typically a momentary closure of a normally
open dry contact, from a ticket dispenser, card reader, etc.
1.4.29. Work All efforts described herein or implied relating to providing a
complete working PARCS system during installation, testing, final acceptance,
warranty, and extended warranty as applicable.
1.5. System Description & Overview
1.5.1. General: The existing parking facility is a 396 space parking facility serving the
central business district of the City of San Rafael. The purpose of this document is to
provide the specifications for the removal and replacement of the existing parking
cash control system with a fully automated on-line FMS using central cashiering,
ANUPC and automated pay stations as the primary exiting methods. The new facility
is a planned 400 space parking facility serving the central business district of the City
of San Rafael. The facility will be located on the southern half of the block where the
surface lot known as lot #11 is currently located.
1.5.2. Configurations
1.5.2.1. Existing Facility, `B" Street Access
1.5.2.1.1. Lane 1: Entry only for ticket and monthly parkers
1.5.2.1.2. Lane 2: Exit only for ticket and monthly parkers
1.5.2.2. Existing Facility, "A" Street Access
1.5.2.2.1. Lane 3: Entry only for ticket and monthly parkers.
1.5.2.2.2. Lane 4: Exit only for ticket and monthly parkers
1.5.2.2.3. Lane 5: The Central Cashiering Office
1.5.2.3. New Facility, "B" Street Access
1.5.2.3.1. Lane 6: Entry only for ticket and monthly parkers
1.5.2.3.2. Lane 7: Exit only for ticket and monthly parkers
1.5.2.3.3. Lane 8: Exit only for ticket and monthly parkers
1.5.2.3.4. Lane 11: The Central Cashiering Office
1.5.2.4. New Facility "C" Street Access
16 Exhibit "A"
Revenue Control and Parking Management Equipment
1.5.2.4.1. Lane 9: Entry only for ticket and monthly parkers
1.5.2.4.2. Lane 10: Reversible entry and exit for ticket and monthly
parkers
1.6. Rates
1.6.1. To Be Determined
1.6.2. Please note that the above rate structure and validations for these facilities shall be
programmed into the fee computers and FMS at installation.
1.7. Typical Dedicated Ticket Entry
1.7.1. Patrons without other means of access, such as AV-1/PC, shall approach the entrance
lane, passing over a TD arming loop "A" embedded in the pavement. No Entry
Stations shall be active without an interlocking detector/loop array requiring vehicle
presence.
1.7.2. All lanes shall be demarcated by Lane Status Indicator lights mounted above the
lanes. For the dedicated entrance lane, an illuminated green arrow on a black
background shall always be displayed below and outside the array. An illuminated
red "X" on a black background shall always be displayed above and inside the array.
SENTRY CONTROL SYSTEMS, INC. - Only reversible lanes shall have Lane Status
Indicator lights inounted above the lanes. These lights shall meet all applicable
specifications contained herein.
CITY OF SAN RAFAEL — ACCEPTED
1.7.3. The TD shall dispense a ticket for the patron only upon pressing the pushbutton on
the face of the TD.
1.7.4. All tickets issued shall contain information including the time/date of entrance, TD
number, lane identification, electronic ticket number, and rate code shall be encoded
on the magnetic stripe or machine printed barcode ticket and imprinted in "person
readable" ink. At least 3/4" of ticket stock shall extend beyond the throat of the TD to
allow patron visual access and enough of the edge of the ticket to grasp it and pull it
from the throat
1.7.5. As the ticket is cut or burst from the ticket fan fold and is dispensed into the throat,
an alarm shall sound and an audio prompt shall be capable, at a minimum, of
replaying the following message, recorded on site: "Welcome to the "City of San
Rafael!" "Please take your ticket and Pay before you exit."
SENTRY CONTROL SYSTEMS, INC. - No alarin sounded tivith ticket issue
17 Exhibit "A"
Reuenue Control and Parking Management Equipment
CITY Of SAN RAFAEL -- ACCEPTED
1.7.6. When the patron takes the ticket from the throat as offered, a vend signal shall be
sent to open a barrier gate, allowing the patron to proceed into the facility. As the
patron crosses over the "B" loop, the gate shall close and the system shall reset itself
for the next transaction
1.7.7. The FMS shall add a differential count of one to "Tickets in Facility", "Total
Facility", and shall add the electronic ticket number to the ticket database to
accommodate the ticket tracking features of the FMS. Additional totalizing counts
related to revenue control shall be tallied as well, as described in the succeeding
sections below.
1.7.8. Contractor shall be required to achieve a 99.5% device cycle success rate by
completing the above steps, excepting cases of patron or employee error or
malfeasance.
1.8. Exception Ticket Entry
1.8.1. If the patron fails to take the ticket in a certain amount of time, which shall be user-
settable, the ticket shall be retracted, voided in the FMS, and vaulted separately in the
TD.
1.8.2. If the patron backs out of the lane with the ticket, therefore failing to cross over the
"B" loop, the ticket shall be voided in the FMS. Should a customer attempt to use a
voided ticket at one of the exit stations the exit verifier will return the ticket to the
customer and by voice and visual display instruct the customer to repark and proceed
to the cashier office
SENTRY CONTROL SYSTEMS, INC. —No voice announcement for Bad Tickets
CITY OF SAN RAFAEL ACCEPTED
1.8.3. Either of the above conditions shall activate an alarm in the FMS, located in the
CCF, allowing parking management to utilize intercoms (included in this package)
mounted on the TD to assess the situation and communicate with the patron.
1.9. Typical Dedicated AA /PC Entry
1.9.1. Patrons shall pass over an Entry Station anning loop "A" embedded in the
pavement. No Entry Stations shall be active without an interlocking detector/loop
array requiring vehicle presence.
1.9.2. AVVPC access shall be accomplished by use of a transponder mounted in a vehicle
and registered in the FMS. It is Contractor's responsibility to insure that all AV41PC
system components deployed are compatible with the City's system.
18 Exhibit "A"
Reuenue Control and Parking Management Equipment
1.9.3. Those patrons that have arranged for AAI/PC parking privileges in exchange for a
fixed monthly fee will be issued "AVVPC " ID tags which shall be fixed to the inside
of the vehicle windshield at a location determined by the manufacture. If the patron
has a vehicle that is determined to have a compatibility problem with inside mounted
transponders the vendor must provide an external mount solution. The external
mount must have mounting capabilities that would deter theft.
1.9.4. As the patron enters the entry lane, the "AVI/PC " transponder and reader shall read
the ID tag automatically, and shall immediately pass the ID information, via a
standard weigand or ASCII data transmission protocol, to the new on-line access
control system supplied by the Contractor.
1.9.5. Patr-ens with a properly fneunted and registered tr-anspender- shall pass thfeugh th
"read field" ef the AV! tfanspender- meunted eve -the . Patrons with a PC tag
shall present the card within 6" of the PC reader. It is Contractor's responsibility to
insure a minimum 99% read capability is achieved (assuming the patron has properly
installed and registered their transponder) that:
1.9.6. The transponder is properly positioned to receive signals from vehicles in the lane
or the patron presents the PC within the maufactures maximum read distance; and
1.9.7. The transponder does not "crosstalk", interfere with, or otherwise pick up stray
signals from adjacent lanes
1.9.8. The AVVPC transponder shall poll the FMS for information regarding the patron's
status, including, but not limited to whether the transponder has been properly issued
and registered. The on-line access control system shall verify that the ID tag is up to
date and in proper anti-passback sequence, and shall issue a command to raise the
entry gate.
1.9.9. All accesses granted shall be recorded in the FMS and such records shall contain
information including the transponder number, time/date of entrance, device number,
lane identification, and rate code.
1.9.10. When the patron's transponder has been successfully read, a vend signal
shall be sent to open a barrier gate, allowing the patron to proceed into the facility.
As the patron crosses over the "C" loop, the gate shall close and the system shall reset
itself for the next transaction
1.9.11. The FMS shall add a differential count of one to "Cards in Facility", "Total
Facility", and shall add the electronic transponder number to the card database to
accommodate the card usage tracking features of the FMS. Additional totalizing
counts related to revenue control shall be tallied as well, as described in the
succeeding sections below.
1.9 Exhibit "A"
Revenue Control and Parking Management Equipment
1.10. Exception "V: C Entry
10.1. If the transponder is not read by the reader and no vend signal is sent to
open the gate, the patron shall be required to take a ticket.
1.10.2. If the transponder is read, but is not registered in the system, the patron shall
be required to take a ticket.
1.10.3. If the transponder is read, but is either out of cycle (each "in" transaction
must be followed by an "out"), not authorized due to insufficient funds in the patron's
debit account, or has been reported lost or stolen, parking management shall have the
option of either allowing entry via "soft antipassback" or denying the patron access
and requiring the patron to take a ticket. In the event of soft antipassback, an alarm
shall sound in the FMS, allowing personnel to interact with the patron via the
intercoms (included in this package) linking the lane to the CCF. The exception shall
be logged in a separate transaction log for management follow-up.
SENTRY CONTROL SYSTEMS, INC. — Skidata will deny the patron access during an
antipassback violation. This is often referred to as "hard antipassback. " Skidata does not
allow access via "soft antipassback. "
CITY OF SAN X4F.4EL ACCEPTED.
1.11. INTENTIONALLY LEFT BLANK
1.12. Central Cashiering Overview
1.12.1. General Description: Upon entry, patron receives a mag -stripe encoded or
bar coded ticket from the TD and proceeds to designated parking areas. Upon exit,
the patron approaches the CCF located at the A St pedestrian entrance of the 3rd and A
St garage, and the B St. pedestrian entrance of the 3rd & C St garage, presents ticket to
a cashier who processes transaction in the fee computers provided by Contractor.
Upon completion of transaction, patron receives an encoded ticket that will activate
the gate and allow patron to leave within a pre -determined time frame (for example:
10 minutes).
1.13. Typical Dedicated Ticketed Exit
1.13.1. Patrons without other means of access, such as the AV-1/PC transponder,
shall approach the entrance lane
1.13.2. All lanes shall be demarcated by Lane Status Indicator lights mounted
above the lanes. For the dedicated exit lane, an illuminated red "X" on a black
background shall always be displayed below and outside the array. An illuminated
green arrow on a black background shall always be displayed above and inside the
array.
26 Exhibit "A°
Revenue Control and Parking Management Equipment
SENTRY CONTROL SYSTEMS, INC. - Only reversible lanes shall have Lane Status
Indicator lights mounted above the lanes. These lights shall meet all applicable
specifications contained herein.
CITY OF SAN RAFAEL -A CCEPIED
1.13.3. Patrons shall pass over an Exit Station arming loop "A" embedded in the
pavement. No Exit Stations shall be active without an interlocking detector/loop
array requiring vehicle presence.
1.13.4. Signage and a painted "STOP" bar on the pavement shall direct the patron to
halt in front of the Exit Station (signage and "STOP" bar to be provided by others).
Signage on the front of the device shall clearly indicate the desired sequence of
events, including the location of insertion of the parking ticket that has been
processed by the CCF and is within the prescribed grace time.
1.13.5. As the ticket is inserted, the encoded information on the ticket shall be read
and processed on-line with the FMS; however, the Exit Station shall be capable of
recognizing and processing such information locally, in case of on-line system failure.
Successful transactions will cause an alarm to sound and an audio prompt shall be
capable, at a minimum, of replaying the following message, recorded on site:
"Thank You for Parking With The City of San Rafael!"
SENTRY CONTROL SYSTEMS, INC. - No alarm
CITY OF SAN RAFAEL ACCEPTED
1.13.6. The Exit Station shall allow three attempts to process a transaction before
reverting to Exception mode.
1.13.7. When the transaction has been processed successfully, a vend signal shall be
sent to open a barrier gate, allowing the patron to exit the facility. As the patron
crosses over the "B" loop, the gate shall close and the system shall reset itself for the
next transaction
1.13.8. The FMS shall subtract a differential count of one to "Tickets in Facility",
"Total Facility", and shall add the electronic ticket number to the ticket database to
accommodate the ticket tracking features of the FMS. Additional totalizing counts
related to revenue control shall be tallied as well, as described in the succeeding
sections below.
1.13.9. Contractor shall be required to achieve a 99.5% device cycle success rate by
completing the above steps, excepting cases of patron or employee error or
malfeasance.
21 Exhibit "A"
Revenue control and Parking Management Equipment
1.14. Exception Ticket Exit
1.14.1. General
1.14.1.1. In the event a patron's ticket fails to activate the gate and allow egress in the
"Typical" fashion described above, the parking system provided by Contractor
shall provide the following options for processing these transactions:
1.14.1.1.1. Remote Release
1.14.1.1.1.1. Remote release may be achieved when a Parking
Attendant communicates with the patron via the intercoms
(included in this package) between devices and utilizes the
FMS software to open the gate and release the patron.
1.14.1.1.1.2. The FMS software provided must support this
practice to allow remote vending of gates and provide separate
documentation of all such releases in an exception report that
can be accessed by parking management.
1.14.1.1.2. Return to CCF
1.14.1.1.2.1.1.1. Contact the CCF by the intercom so that an
attendant can be dispatched to the lane to assist in
completing the transaction.
1.15. Typical Dedicated AVI/PC Exit
1.15.1. As the patron exits the facility via the designated exit lane, the "A-VI/PC "
transponder and reader shall read the ID tag automatically, and shall immediately pass
the ID information, via a standard weigand or ASCII data transmission protocol, to
the access control system supplied by the Contractor.
1.15.2. The access control system shall verify that the ID tag is up to date and in
proper anti-passback sequence, and shall issue a command to raise the exit gate.
1.15.3. Once the gate arm is raised, the patron shall drive forward, and the gate arm
shall lower once the patron has cleared the gate reset detection loop buried in the
drive surface.
15.4. More detailed transaction descriptions, exception events and system
monitoring and reporting options are described more fully in subsequent sections of
this document.
1.15.5. Other actions are as described above in the "Typical Dedicated AALI/PC
Entry" section
22 Exhibit "A"
Revenue Control and Parking Management Equipment
1.16. Exception AI/PC Exit
1.16.1. General
1.16.1.1. In the event a patron's AVI/PC tag should fail to activate agate and allow
exit in the proper sequence, patron shall default into the Exception procedure
described for Exception Ticket Exits above.
1.17. Capacity Monitoring & Count Functions
1.17.1.1. General
1.17.1.2. Demand for space may, at times, exceed supply. Therefore, it is important
to maintain an ongoing capability to quickly and automatically assess the
number of available spaces at any given time. This information must be readily
available to parking management and to patrons, via messaging options.
1.17.1.3. Knowledge of real-time capacity is a tool that the City parking management
can utilize to maximize use of the deck, avoid inconvenience to patrons and
potential patrons, and reduce the possibility of gridlock and backup.
1.17.1.4. The count system will be oriented toward internal capacity and measuring
deck activity in terms of ingress and egress. A central PC with the appropriate
FMS software will be installed (in the CCF near the station entrance, however,
the City may choose to locate the central PC off-site in the City Parking
Management Office.
1.17.1.5. Contractor shall, in advance of the installation, submit a proposed count
matrix to Consultant for review. This Count Matrix shall describe the various
counts, to what loop or device the count is tied, and how the count is rolled up or
related to other counts in the facilities.
1.18. Types of Counts
1.18.1. There are two types of counts that shall be monitored:
1.18.1.1. Differential Occupancy
1.18.1.1.1. The primary use of Differential Occupancy counts at both
decks is for the purpose of facility management and messaging
options chosen by the City. The capability to perform these types of
counts accurately will be critical to the success of the parking
program.
1.18.1.1.2. Differential occupancy is defined as the number of vehicles
23 Exhibit "A"
Revenue Control and Parking Management Equipment
occupying a particular area, zone, or facility in a given period of
time. These counts are calculated by the central PC, which monitors
all activity in "real time", that is, as it actually happens with no delay
for device buffering or scheduled intermittent transmission. The
count is generated by adding the number of vehicles that have
crossed an entrance loop into the area, zone, or facility and
subtracting those that have departed by crossing over an exit loop
from that same area, zone, or facility.
1.18.1.1.3. The resulting count shall be compared by the central PC to a
pre-set occupancy count that is derived from a physical count of the
total number of spaces within the given area, zone, or facility. This
pre-set count is initially calculated by multiplying 95% times the
actual number of spaces (this number shall be user adjustable and
may change upon the City's operational field experience).
1.18.1.1.4. Setting a threshold allows for error and also takes into
account a phenomenon known as "practical capacity" in which
patrons believe the facility is full when there are so few spaces that it
is difficult or impossible to find them quickly and easily. It also
allows for errors in the counting system that might over represent
available spaces.
1.18.1.1.5. The "practical capacity" pre-set count threshold and the
actual differential count in any zone, queue, or facility area shall be
resettable by an authorized user of the system, and be password
protected.
1.18.1.1.6. When the real time occupancy count matches the pre-set
practical capacity count, the facility is "full" and the FMS software
shall be capable of causing messages to change on applicable VMS
and CMS. Sign change shall be accomplished either by direct
control (in the case of VMS) or by communication in an industry
standard format acceptable to the City.
1.18.1.1.7. Likewise, the FMS software shall be capable of controlling
all attached devices, enabling devices such as ticket dispensers to
turn off, while allowing others, such as card access devices, to
remain on, in any combination. The FMS software shall be capable
of accomplishing this remotely, from the CCF, either automatically
per a pre -ordained programming or manually via appropriate
password entry into the FMS.
1.18.1.1.8. The FMS Reporting System shall be capable of generating
reports on Differential Counts by user -selected criteria, including at
a minimum, time, date, and zone, queue, or facility. These reports
shall be viewable on screen or capable of being printed.
24 Exhibit "A"
Revenue Control and Parking Management Equipment
1.18.1.2. Totalizing Entry/Exit
1.18.1.2.1. The primary use of Totalizing Entry/Exit counts is for the
purpose of revenue and access control. A secondary function allows
management to plan for staffing, equipment maintenance, cleaning
and other functions by providing information as to which entrances
and exits are most heavily used and when. The capability to perform
these types of counts accurately will be critical to the success of the
parking program at both decks.
1.18.1.2.2. Totalizing counts are defined as those counts sensed by a
detector/loop array that adds a count of one to a non-resettable
counter for a particular lane
1.18.1.2.3. Totalizing counts monitor activity over a certain loop or sets
of loops within an queue, zone, or facility area. They shall work
independently of, but may be installed in tandem with, Differential
Occupancy counts to produce information useful to management.
Totalizing counts indicate the total number of vehicles that entered
or exited at a certain time or within a given time frame. Parameters
of inquiry can be set via a central PC.
1.18.1.2.4. The FMS Reporting System shall be capable of generating
reports on Totalizing Counts by user -selected criteria, including at a
minimum, time, date, and zone, queue, or facility. Additionally,
these counts shall utilize directional and sequence logic to provide
counts for specific activities, such as counting vehicles traversing
"in" through and exit lane, or counting as "one" the successful
completion of a sequence of activities, such as "Arming Loop
activation + Device Vend + Gate Cycle + Closing Loop activation
I". These reports shall be viewable on screen or capable of being
printed.
1.18.1.2.5. Totalizing counts shall not be resettable under any
circumstances like occupancy counts, which may increase or
decrease as occupancy within the area, zone, or facility changes.
Therefore, totalizing counts sequentially ascend ad infinitum.
1.19. Information Streams to be Monitored
1.19.1. Capacity
1.19.1.1. Counts, as described above, will be made of all vehicles entering and
exiting the deck. These counts will be collated and analyzed by a central PC and
compared to facility occupancy. When maximum occupancy has been reached,
the central PC will automatically (or manually, as an option) trigger changes to
the "FULL" signs installed at the facility entrance.
25 Exhibit "A"
Revenue Control and Parking Management Equipment
1.19.2. Internal Counting
1.19.2.1. Internal counting shall be Facility -wide differential counts only, broken out
by device type used for access (TOTAL IN - TICKET IN - CARD IN). Counts
shall be used to drive "FULL" signs (included in this package) via the FMS. All
counts shall be taken from closing loop activity in each lane located at each entry
and exit plaza.
1.20. Qualifications
1.20.1. Manufacturer
1.20.1.1. Company specializing in manufacturing the Products specified in this
section shall have a minimum five years documented experience.
1.20.1.2. Manufacturer shall have current version of each primary component
currently operating successfully in three or more parking facilities of similar size
and activity.
1.20.2. Installer
1.20.2.1. Company specializing in performing the work of this specification with
minimum three years documented experience and is approved by manufacturer.
1.20.3. References
20.3.1. Document the experience and qualifications of the Contractor,
Manufacturer(s) and Installer(s) of each primary component listed in the Bid.
Include the three most recently installed, complete projects which are similar in
magnitude, complexity, and dollar value. Please provide address and phone
number for each.
1.21. Quality Assurance
1.21.1. Installation Observations
1.21.1.1. PARCS installation work may be observed by City, Consultant, Engineer,
General Contractor, and/or Quality Assurance personnel at any time during
progress of Work.
1.21.2. Electrical Devices
1.21.2.1. Devices installed within the PARCS shall be UL listed. Factory installed
wiring system shall bear UL classification label certifying compliance with the
National Electric Code, most recent edition.
26 Exhibit "A"
Reuenue Control and Parking Management Equipment
1.21.3. Authorized Manufacturer's Representative
1.21.3.1. Contractor and/or Installer shall present evidence of training and
certification by the Manufacturer of each product to install, test, operate, and
service the product and will insure that no factory warranties are voided by
improper or unauthorized actions by Contractor and/or Installer.
1.22. Submittals
1.22.1. Acceptable Format
1.22.1.1. Submit in approved format as approved by the engineer.
1.22.1.1.1. Bid Submissions
1.22.1.1.2. Proposer shall submit the following with the bid:
1.22.1.1.2.1. Qualifications: List the experience and qualifications
of the Contractor, Manufacturer(s) and Installer(s) of each
primary component listed in with the Bid. Each submittal shall
include the three most recently installed, complete projects
which are similar in magnitude, complexity, and dollar value.
Information shall include names, locations, contacts, telephone
numbers, date of installation, number of spaces in facility and
general description of types and quantities of equipment.
SENTRY CONTROL SYSTEA:GS, INC. As stated i►► qucilificatio►►s
listed in the response to hid PA RCS 00-00 on July 18, 2002
CITY OF SAN RAFAEL _ACCEPTED
1.22.1.1.2.2. Product Data: List the manufacturer of each primary
component of the system and provide cut sheets and/or data on
operating equipment, characteristics and limitations, operating
temperature ranges, and all related information.
1.22.1.1.2.3. Samples: Submit two samples of ticket discard,
illustrating size, coding method, and ticket handling.
1.22.1.1.2.4. List of sub -contractors: Identify the nature of the
work that will be performed by each. Successful Proposer
shall be required to submit evidence of Waiver of Lien prior to
final payment, if subcontractors are used.
1.22.1.1.2.5. Scheduling: Submit schedule showing Proposer's
timing for shop drawings, fabrication, delivery, installation,
testing, training and substantial completion. Milestones shall
also include special project requirements related to
coordination with work by others and phasing. Pricing for
equipment and installation submitted with this document must
be available to the owners for a period of six months. All
27 Exhibit "A"
Revenue Control and Parking Management Equipment
scheduling and timing is at the discretion of the General
Contractor.
1.23. Responsibilities of Contractor
1.23.1. Accept Sole Responsibility
1.23.1.1. It is the selected PARCS contractor's sole responsibility to provide all
products, services, wiring, and installation necessary for a complete and
functioning PARCS system.
1.23.1.2. Provide the Parking Control System equipment and software as defined by
and implied by the Contract Documents and generally accepted industry
standards.
1.23.1.3. Provide all equipment, software, components and materials to comply with
the functional system requirements of the Contract Documents.
1.23.1.4. Provide Labor, Equipment, and Materials Necessary to Deliver a Complete
System
1.23.1.5. Provide all necessary labor, equipment and construction materials to install
the Parking Control System to comply with the functional system specifications
as defined by the Contract Documents.
23.1.6. Provide all necessary labor, equipment and materials to maintain and
guarantee the Parking Control System to comply with the Contract Documents.
1.23.1.7. Provide all necessary labor, materials and facility to train personnel in the
use, maintenance and management of the Parking Control System to comply
with referenced industry standards the Contract Documents.
1.23.1.8. Provide all necessary labor and equipment to protect, transport, and store
the equipment and materials removed and provided under the Contract
Documents.
1.23.1.9. Provide all necessary project supervision, coordination, and inspection,
including clean-up, punch list, and corrections, to comply with industry
standards and the Contract Documents.
1.23.1.10.Meet Testing Requirements
1.23.1.11.Certify manufacturer's assurances of quality according to any cut sheets or
product detail supplied, as relates to types of materials used, manufacturing
means and methods, and suitability of purpose.
�8 Exhibit "A"
Revenue Control and Parking Management Equipment
1.23.1.12. Provide all necessary functional demonstrations and acceptance testing to
comply with the functional specifications as defined by the Contract Documents.
1.23.1.13.Make available two (2) persons on call for a minimum of five ( 5 ) business
days to assist in and witness testing of the system.
1.23.2. Meet Regulatory Requirements
1.23.2.1. Products requiring electrical connection shall be listed and classified by
Underwriters' Laboratories, Inc., as suitable for the purpose specified and
indicated.
1.23.2.2. Adherence to applicable portions of state and local building codes is the
responsibility of the Contractor. Conform to applicable codes, if any, for paint
finishes on equipment, markings on gate arms, etc.
1.23.2.3. The contractor shall be responsible for permits, special engineering,
calculations, or architectural -type drawings, if any, required by code.
1.23.3. Provision and Review of Plans, Drawings, and Specifications
1.23.3.1. Provide all necessary engineering, drawings and submittals to comply with
the Contract Documents.
23.3.2. Verify that field measurements are as instructed by manufacturer and are as
designated in any plans, drawings, and specifications provided by City or
Engineer.
1.23.3.3. Be certain that all functional requirements, as described herein, can be met
with equipment specified and provided.
1.23.4. Coordination
1.23.4.1. Coordinate work with others under provisions of City Guidelines.
1.23.4.2. Coordinate with others the placement of equipment frames and anchors,
bollards, and concrete islands.
1.23.4.3. Coordinate with others the placement of conduit and accessories and the
power wiring to operating equipment and provide for support activities.
23.4.4. City may choose to have GC and Engineer prepare plans, drawings, and
install certain PARCS products referenced herein. Contractor shall coordinate
and advice GC and Engineer on these and related matters.
29 Exhibit "A"
Reuenue Control and Parking Management Equipment
1.24. Wiring
1.24.1. Provide, install, and test all necessary device control wiring and
communications wiring to equipment provided in this contract and equipment to be
installed by others.
1.24.2. Terminate and properly connectorize all communications cabling.
1.24.3. Provide all incidental conduit and wiring which is needed for total system
performance but which was not noted on Contract Documents. There shall be no
additional cost to City for these incidental items.
1.25. Project Record Documents
1.25.1. Submit under provisions of the general conditions of the contract
documents.
1.25.2. Record actual locations of concealed conduit and disconnects.
1.25.3. Forward Documentation
1.25.4. Provide City with a 4 mil reproducible set of drawings and a CAD file
stored on machine readable media in AutoCAD 12.0 (or higher) format showing any
modifications or clarifications not present on original Contract Drawings including
the actual equipment field wiring diagram and electrical circuitry and service
schematics.
1.26. Warranty & Service Requirements
1.26.1. General
1.26.1.1. PARCS contractor shall warrant equipment and installation for a period of
two (2) years from the date of final acceptance as described in Part 3 at no cost
to City.
1.26.1.2. At the completion of the one (1) year maintenance and guarantee period
and/or any Extended Warranty period, Contractor shall insure that all of the
Parking Control System equipment shall be operating within the original
operational specifications of the Contract Documents and the manufacturer's
equipment specifications.
1.26.2. Warranty Response Time
1.26.2.1. Following installation, during the testing phases, Contractor shall make
available one (1) full time qualified technician on call for immediate response at
30 Exhibit "A"
Reuenue Control and Parking Management Equipment
all times during regular business hours, Monday through Friday, for a period of
thirty (30) days.
1.26.2.2. Warranty response shall be provided seven (7) days per week, twelve (12)
hours per day (6AM-6PM), including New Year's Day, Memorial Day,
Independence Day, Labor Day, Thanksgiving Day, and Christmas Day.
Response time from initiation of trouble call to on-site presence of qualified
technician must not exceed four (4) hours for trouble calls placed from 6AM-
6PM and eight (8) hours for trouble calls placed during other hours and the
holidays of New Year's Day, Memorial Day, Independence Day, Labor Day,
Thanksgiving Day, and Christmas Day. Contractor shall insure calls received
after the close of business are forwarded to an on -duty technician or manager for
prompt dispatch of service.
1.26.3. Performance of Warranty Repairs
1.26.3.1. Contractor shall maintain an "on-time" inventory of parts to effect
immediate repairs of specified equipment.
1.26.3.2. Contractor shall repair or replace all defective or damaged items delivered
under this specification by the end of calendar day following day on which
notice was given by City or its agent.
1.26.3.3. Contractor shall maintain a staff of qualified technical personnel authorized
by the specified equipment's respective manufacturers to perform warranty work
as allowed by the factory.
1.26.3.4. If Contractor is not available within the above prescribed response times,
CITY may effect repairs. Contractor shall then reimburse CITY for parts and
labor necessary to correct deficiencies as defined within warranty clause and
time. Contractor shall pre -qualify appropriate CITY personnel to effect repairs,
as described in Part 3, and identify the types of repair each trained individual is
qualified to perform after training of owner personnel. Such qualified action by
CITY shall not void any warranties.
1.26.3.5. Contractor may elect to have any replaced item returned to manufacturer at
no additional expense to CITY.
1.26.4. Manner of Conduct During Original Warranty Period
1.26.4.1. Contractor shall ensure that all maintenance is provided sufficiently to
maintain the equipment in like new condition until completion of the two (2)
year manufacturer's warranty period for parts and labor.
1.26.4.2. Contractor shall check-in with the CITY's representative immediately upon
arriving at the parking facilities and prior to performing any work.
31 Exhibit "A"
Reuenue Control and Parking Management Equipment
1.26.4.3. Preventive maintenance services shall be scheduled in advance with CITY
during the performance of the initial installation, and during the two (2) year
guarantee period.
1.26.4.4. Contractor shall submit a copy of a work order detailing the service
performed to CITY immediately following completion of each maintenance or
preventive service call.
26.4.5. Each work order shall detail arrival time, departure time, service performed,
parts required, and the servicing technicians name and signature. The work
order shall be authorized by CITY.
26.4.6. Contractor shall provide sequentially numbered work orders exclusively
prepared for the Work. Copies of the work orders shall be inserted in the
maintenance log book.
1.26.4.7. Contractor shall maintain a log listing all work orders and detailing all of
the preventive maintenance and repairs made during the performance of the
Work and prior to final acceptance.
1.26.4.8. Contractor shall maintain a log listing all work orders and detailing all of
the preventive maintenance and repairs made during the two (2) year contract
guarantee period.
1.26.4.9. Contractor shall maintain the log on each parking control device, software
module and communication device.
1.26.4.10.Format of the log shall be of two primary divided sections for the
acceptance period and the two (2) year contract guarantee period.
1.26.4.11.The log book shall contain the history of maintenance and repair activities,
the duration, and cause and cure for all malfunctions.
1.26.4.12.The log book shall be turned over to the CITY's representative at the
completion of the Contract period.
1.26.4.13.Preventive maintenance provided by the contractor shall consist of
examination of all installed equipment at least once every month by the
Contractor's service personnel, and necessary adjustment, lubrication, and
cleaning of parts.
1.26.5. Limitations of Warranty
1.26.5.1. Warranty shall not cover acts of vandalism, damage caused by third party,
or natural phenomena. Warranty shall not cover damage caused during
maintenance actions by untrained/unapproved CITY Personnel.
32 Exhibit "A"
Revenue Control and Parking Management Equipment
1.26.5.2. The City may, at it's sole discretion discontinue any future or extended
service/maintenance contracts at anytime. If at some future date the City wishes
to reinstate the service/maintenance contract the vendor must do so without back
charging to the point the contract was terminated. The price for the contract will
remain as quoted, but only through the original termination date.
32 Exhibit "A"
Revenue Control and Parking Management Equipment .'
2. PRODUCTS
2.1. Manufacturers
2.1.1. Sourcing of Revenue Control Products
2.1.1.1. To ensure reliability, serviceability, and quality, it is the CITY'S preference
the entire RCS shall be provided by one manufacturer. The RCS includes mag
stripe or barcode ticket dispensers, reader/writers, fee computers, fee displays,
full signs, but does not include , intercoms, (included in this package) items to
be fabricated, AVI/PC monthly parking system. Any communications
equipment or software required for the system shall be provided by a
manufacturer that provides full compatibility with the parking equipment. This
shall ensure that service and support of the equipment may be carried out in a
timely manner and will ensure that one party shall be responsible for that service
and support.
2.1.1.2. If all components of PARCS are not from same manufacturer, Contractor
shall be responsible for the performance of these components, as they relate to
the proper functioning of system as required herein.
2.1.1.3. Certification: It is mandatory that contractor provide as a part of this
submittal evidence of Certification as an approved and fully certified contractor
and installer of each of the manufactures represented in their response.
2.2. Types & Quantities of Equipment to be Provided
(See attached Exhibits for placement location, lane naming, and other detail)
(See next page for types and quantities detail)
2.2.1. Equipment List
34
Revenue Control and Parking Management Equipment
Description
r
r
r
r
r
r
r
c-
r
r
r
> y
co
cn
co
to
cn
(D
to
co
co
co
rD
�
N
W
-P
C11
ON
-1
Oo
�0
�
�-
�.
O
Parking Gate
1
1
1
1
1
1
1
1
1
I I
9
Mag stripe or bar code
1
1
1
I 1
1
read/write TM
11
I
I
16
Lot Full Sign Pole &
1
1
I
(1
I
Hdware
11
I
I
I
14
Fee Computer
I
I
I l
I
I
I
I
I
I l I
I I
2
Mag Stripe or bar code
I
Ticket Validator
Electronic Fee
I
I
I l
I
Indicator
I
I
11
I
I
12
Credit Card Interface
I
I
II
1 2
I
I
I
I
2 1
I
1 4
Ticket Vault
I
I
I
I
1
1
I
I
I
1 1 I
I I
1 2
Communications Kit
11
1 1
1 1
11
, 1
1
1 1
11
11
1
1 1 I
I I
11
Exit Verifier
I
11
1
'
I
11
I
1
1
14
ag ripe or bar code
readerwrit(
Pay Station (POF)
I
I
I
2
I
I
I
I
1 2 I
I I
1 4
PAq/PC Reader
1 1
1
1
1 1
I
11
1 1
11
1 1
1 1
f I
I I
1 9
AV! Tr-anspender-1
I
I
I
I
I
I I
I I} I}97-5
Extermal Mount AV!
Tr-anspender-
-2-5
215
Orr Proximity Cars
Pentium P
D�n+e�
I
I
I
I
I
I
I
I
I
I
I
I I
I I
I 1 2000 1 2000
I I
B/W hase_
PC Communications
I
I
I
11
I
I
1
Kit
I
I
1
11
13
Access Software
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I 1 1
11 1
Accounts Receivable
I
I
I
I
I
I
I I
Software
I
I
I
I 11
11
Revenue Management
I
I
I
I
1
Software
I
I
I
I I
I 11
Ticket Tracking
1
1
Software
License Plate
Inventory Software
Facility Management
I
1
Software Server
I
I
I
I
I
I 11
Debit Control Software
I
I
I
I
I
I I
I
I
I I l
11
Intercom Station
1
1 1
1 1
11
I
11
1
1 1 1
1
1 1
I I
I I
9
10 Station IntercomI
I
I
I
11
I
3
Master
I
I
11
I 11
Directional Lights
1 4
1-2
12
1 2
1
1 2
12
12
2
1 4
I I
1 20 8 1
Lane Controler
1 1
1 1
1 1
1 1
1
1 1
1 1
1 1
1
1 1'
I
I I
1 9
Note: The City will supply the PC, monitor,
and printer.
We want
to keep this server
consistant
with the City Standard.
35
Reuenue Control and Parking Management Equipment
2.3. Performance Specifications
2.3.1. General
2.3.1.1. All exterior equipment including equipment located inside the garage but
exposed to the elements shall be of non -corrosive materials such as galvanized
steel, stainless steel or heavy-duty aluminum.
2.3.1.2. All exterior equipment including equipment located inside the garage but
exposed to the elements as described above shall be primed and factory -painted
with powdercoated or baked on acrylic enamel. Color to be selected by CITY or
Engineer. If no color is chosen by CITY or Engineer all equipment shall be
provided in white.
SENTRY CONTROL SYSTEMS, INC. - Cannot specify color
CITY OF SAN R4F 4EL -.4 CCEPTED
2.3.1.3. All communicating devices shall be provided with Communications
isolators and manufacturer's recommended lightning and surge suppression.
2.3.1.4. Contractor shall confirm quantity of vehicle detectors and loops required for
system and determine detector loop sizes
2.3.1.5. Contractor shall famish two sets of keys to each piece of lockable
equipment and two sets of master keys which shall open all locks. Cash drawers
shall be uniquely keyed from each other. Identically -keyed locks shall not be
placed in service elsewhere in the San Francisco Bay Area.
SENTRY CONTROL SYSTEMS, INC. - One key supplied per device. No ntaster key
exists.
CtTY OF SAN RAF_ 1 F,L - ACCEPTED.
2.3.2. Mag Stripe or Bar Code Ticket Dispensers
2.3.2.1. Dispenser Operational Cycle
2.3.2.1.1. The ticket dispenser (manually operated) shall be designed
to issue fan -folded or magazine contained time/date stamped
"person readable" ticket when a vehicle arms the device loop
detector in the proper sequence and the motorist pushes a "ticket
issue" button on the faceplate of the dispenser.
2.3.2.1.2. Ticket shall be presented conveniently to patron without
opening car door or touching metal part of dispenser.
36 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.2.1.3. Dispenser shall imprint in person -readable ink and
magnetically encode ticket with dispenser number, fee structure or
number to be used at exit, `In' time and date. Ticket shall be cut or
burst upon issue.
2.3.2.1.4. If the barcode option is chosen, the barcode shall include
dispenser #, fee structure, or number to be used at exit, "In time &
date".
2.3.2.1.5. Include printed "Please Take Ticket" & "Pay Before
Exit"sign at location visible from vehicle. If dispenser offers other
visual or auditory cues (as required in this document), such as
programmable voice packages, please describe.
2.3.2.1.6. When ticket has been removed, unit shall produce a vend
signal to raise the parking gate. An audible alert shall sound until
ticket is removed from throat of dispenser. Unit shall be capable of
processing a ticket in less than 2 seconds after push-button is
activated.
SENTRY CONTROL SYSTEMS, INC. — No alarm. Ticket issuing speed is
3 seconds.
CITY OF SAN RAFAEL —ACCEPTED
2.3.2.1.7. When facility is full as determined manually or
automatically from the Facility Count Enclosure, the dispenser shall
be capable of being at user option, to automatically disable/re-enable
or remotely disabled and re -enabled from the CCF (or other location
designated by CITY).
2.3.2.2. Cabinet
2.3.2.2.1. Construction shall feature weather tight seams, flush access
doors and panels, tamper proof hardware, and weather tight gaskets.
Conceal mounting bolts inside units.
2.3.2.2.2. The cabinet shall be properly gasketed and designed for
all-weather use. A thermostatically controlled heater shall be
provided, thermally insulated to permit heater to maintain cabinet
temperature to equipment operating minimum.
2.3.2.2.3. If the ticket dispenser has multiple doors, designed to permit
ticket loading from one side and electronic/programming on the
other, then each door shall be separately key coded. All dispensers
shall be keyed alike.
37 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.2.2.4. An intercom substation shall be internally mounted within
the faceplate and within convenient reach of the motorist. A
push -to -call button and sign shall be required. Unit to be compatible
to base station.
2.3.2.3. Ticket Capacity & Loading
2.3.2.3.1. Minimum 4000 ticket capacity shall be provided. This may
be accomplished by providing a 2000 ticket load capacity and a 2000
ticket inventory.
2.3.2.3.2. Include low ticket indicator light and automatic shut down
when empty. Low ticket alarm/message sent to FMS.
SENTRY CONTROL SYSTEMS, INC. — No low -ticket indicator. We
provide alarm on the control center screen of monitoring software.
CITY OF SAN RAFAEL ACCEPTED
2.3.2.4. Dispenser Mechanism
2.3.2.4.1. Provide a user -programmable LCD operational status and
message display.
2.3.2.4.2. Unit shall be Microprocessor controlled with 12 hour
AM/PM time clock and emergency battery backup.
2.3.2.4.3. Controller Mechanism shall be self-contained, with plug in
modules, easily replaceable by user.
2.3.2.5. Electrical & Communications Requirements
2.3.2.5.1. Equip dispenser with thermal circuit breaker, on/off switch,
grounded convenience outlet, built-in service light, and
thermostatically controlled minimum 500 Watt electric heater.
SENTRY CONTROL SYSTEMS, INC. Outlet not available
CITY OF SAN RAF_?1 EL ACCEPTED
2.3.2.5.2. The ticket dispenser shall function on-line in real time
communications with a central PC or control unit.
2.3.2.5.3. All necessary electronic communication devices, firmware,
and electrical connection components that are necessary for this
device to function within the overall system shall be provided.
38 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.3. Parking Gates
2.3.3.1. Gate shall be capable of on-line or off-line communications and possess
directional logic and multi -mode functionality. Gates shall have a buffer
capacity of at least three simultaneous vend inputs and can sequentially process
each vend without lowering and raising gate.
2.3.3.2. Cabinet shall:
2.3.3.2.1. Be made of minimum 14 gage galvanized steel or non-
ferrous metal
2.3.3.2.2. Possess weather tight seams and be thermally insulated to
permit heater to maintain cabinet temperature to equipment
operating minimum.
2.3.3.2.3. Have flush access doors and panels, tamper proof hardware,
and weather tight gaskets.
2.3.3.2.4. Feature mounting bolts concealed inside units.
2.3.3.2.5. Contain thermostatically controlled heating unit to insure
operation at minus 30 degrees F.
2.3.3.2.6. Be primed and painted with enamel, per CITY'S selection,
or white.
2.3.3.3. Arm Control shall feature:
2.3.3.3.1. Mechanism to raise and lower arm by instant reversing
electric motor, enclosed speed reducer operated by self contained,
plug-in replaceable controller.
2.3.3.3.2. Design mechanism shall be equipped with slip clutch to
prevent breakage if arm is forced and to permit manual operation if
required. Arm movement to stop and start at reduced speed.
Components of cadmium coated steel.
2.3.3.3.3. Arm Clamp shall be made of cast metal with quick change
clamp and hub bracket, to permit rapid replacement of arm without
fitting or drilling.
2.3.3.3.4. The height of the gate arm shall be 30 inches from floor
level when in down position.
2.3.3.4. Electrical Components shall include:
39 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.3.4.1. Power board shall be self-contained, plug-in type, with
replaceable components.
2.3.3.4.2. Wiring for control units, zinc plated connection box,
grounded convenience outlet, switch for automatic or manual
operation, switch to disconnect power unit, thermostatically
controlled minimum 250 Watt heater strip, and thermal protection
disconnect for motor.
2.3.3.4.3. 115 volt, 60 cycle power supply and shall not draw more
than l 1 amperes surge power. The gate housing shall contain enough
room to locate detectors and other electrical components.
2.3.3.4.4. A motor rated at a minimum 1/3 horsepower. The gate
motor shall be equipped with a thermal overload circuit breaker. In
addition, all motor relays and solenoid power shall be provided with
a circuit breaker.
2.3.3.4.5. Separate momentary contact closures for the count control,
monitoring and future software system upgrades and applications.
2.3.3.5. Safety Features for Gate Arm
2.3.3.5.1. Articulating arm shall have internal counterbalance, with
safety rubber bottom edge.
2.3.3.5.2. Each gate shall be equipped with aluminum or breakaway
gate arm and finish painted in diagonal warning stripes or safety
yellow.
SENTRY CONTROL SYSTEMS, INC. — Fiberglass arra
CITY OF SAN RAFAEL —ACCEPTED
2.3.3.5.3. Each gate shall have an automatic arm reversing switch and
sensory unit which will insure that the gate arm will automatically
reverse its direction should an object be struck by the gate arm
during its descent. The arm will remain in the open position until
automatically reset by a variable control with a time range of 2 to 60
seconds and display an alarm at the FMS.
2.3.4. Traffic Loops
2.3.4.1. Loops shall be installed cut -in to paved surface of traffic lane.
2.3.4.2. Contractor shall adjust location of traffic loop to avoid saw cutting of
concrete reinforcing and shall not saw -cut without the approval of CITY's
40 Exhibit "A"
Revenue Control and Parking Management Equipment
Engineer. Sawcutting is limited to 1/4" wide by 3/4" deep. If conflicts arise,
contractor shall resolve the issues with the CITY's Engineer.
2.3.4.3. Cut -ins shall measure approximately 2' by 6' placed in saw cuts 1/4" wide
and 3/4" deep.
2.3.4.4. Cut -ins shall be completely sealed after installation with sealant approved
by parking gate and detector/loop array manufacturer.
2.3.4.5. Loops shall be comprised of a minimum of three turns of 16 -gage unspliced
single conductor wire.
2.3.4.6. Loop leads shall be conduit -contained, where possible and limited to no
more than 100 feet with a minimum four twist per foot.
2.3.5. Vehicle Detectors
2.3.5.1. The Loop Detector shall be a solid state electronic device with fully
self -tuning and self scanning features provided. Unit shall feature modular plug-
in construction.
2.3.5.2. It shall have a minimum of three switch selectable operating frequencies and
provide an LED to indicate vehicle presence.
2.3.5.3. Unit shall be capable of detecting vehicles tailgating at a minimum distance
of 6" apart.
2.3.5.4. An internal sensitivity switch shall be provided. Sensitivity shall be
maintained automatically regardless of environmental conditions.
2.3.5.5. The Loop Detector shall be integrated into the overall vehicle count control
system. The detector shall be of sufficient speed and reliability to permit
accurate operation of the system.
2.3.5.6. Detectors shall be intelligent and capable of directional logic for different
gate operations.
2.3.6. Lane Controllers
2.3.6.1. General
2.3.6.1.1. Lane/Port Controllers shall be a microprocessor based
communication device which provides the ability to interface access,
revenue, and count functions for a given lane, zone, or area and
allow full, two way communications between a lane, its individual
devices, and interconnected FMS software.
41 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.6.2. Features
2.3.6.2.1. Total compatibility with all devices and FMS software
2.3.6.2.2. Integrated Count functions, including illegal forwards,
tailgates, tickets, monthlies, and backouts, all with directional logic
2.3.6.2.3. Storing and buffering of device inputs and sequential
processing of successive vend inputs
2.3.6.2.4. LED indicator lights to display unit status
2.3.6.2.5. Full communications and testing from FMS for each
attached device
2.3.6.2.6. Status messaging and alarm generation capabilities in
conjunction with FMS, including gate up too long, back out with and
without ticket, ticket in throat, and gate arm rebound
2.3.6.2.7. Real time communications, including resetting loops,
turning signs on/off, raising/lowering gates, and enabling/disabling
devices.
2.3.7. Intercom Systems
2.3.7.1. Master Stations - An Intercom Master Station shall be installed in each of
the CCF (Parking Management Office. The Intercom Master Stations shall have
the following features:
2.3.7.1.1. Desk top use.
2.3.7.1.2. Selective call up to 10 stations simultaneously, for 10
Station Masters
2.3.7.1.3. Talk handset
2.3.7.1.4. Exclusive master to master communications
2.3.7.1.5. Minimum 10 station capacity
2.3.7.1.6. Monitor any substation
2.3.7.1.7. Telephone interconnect capability to other Master Station.
2.3.7.1.8. Have the ability to forward intercom communications to a
cell phone or landline.
42 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.7.1.9. Temporary Privacy that will allow Master to temporarily
disconnect any or all stations for private conversation.
2.3.7.1.10. Call Annunciator lights for Station Selection, indicates
which station has called.
2.3.7.2. Substations
2.3.7.2.1. Intercom Substations shall be installed at all ticket
dispensers, room key readers, and exit Stations (or lag time readers).
The Intercom Substations shall have the following features:
2.3.7.2.2. ADA -compliant.
2.3.7.2.3. Weather -resistant.
2.3.7.2.4. Flush mounted with a stainless steel faceplate.
2.3.7.2.5. Minimum of simplex (push -to -talk) communication.
2.3.8. Full Sign
2.3.8.1. Contractor shall provide a pedestal -mounted full sign, locations subject to
CITY approval.
2.3.8.2. At the "A" and "B" Street entrances for the Existing Facility and at the "B"
and "C" Street entrances for the New Facility. The "Full Sign" shall be mounted
on islands # 1,2,3 & 5, turned at an angle to face customers before they enter the
plaza.
2.3.8.3. Sign shall be capable of activation automatically or manually from the FMS.
2.3.8.4. Enclosure shall be weather-proof NEMA -Type IV or equivalent with a
built-in sun shield. Finishes shall match other PARCS equipment supplied by
Contractor.
2.3.8.5. Display shall be flashing 4" letters minimum.
2.3.9. Fee Computers (Cash Registers)
2.3.9.1. General
2.3.9.1.1. The Fee Computer shall be an operator -oriented, high speed
terminal for use in machine-readable revenue control processing
applications. Fee Computer shall be capable of processing a
transaction in less than five seconds.
43 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.9.1.2. The revenue terminals shall be on-line communications with
a central PC unit tied via hard wire. The Fee Computer must also be
capable of being linked to a remote site via telephone modem, or
network connection.
2.3.9.1.3. The Fee Computer terminal shall contain a microcomputer,
consisting of a microprocessor with associated program and data
storage areas. All other parts of the terminal shall operate as a unit
and be connected directly to the microprocessor. All control and data
movements shall be handled by the instructions of the program
storage area. The control programs in the program storage area shall
be stored in a Read Only Memory (ROM). The instructions shall be
in hardware and although they may be used by the microprocessor,
they shall not be alterable. The data storage area shall be in a
Random Access Memory (RAM). It shall store the audit totals and
shall be continuously updated.
2.3.9.1.4. All units provided shall be identical and contain the
firmware necessary for this project's requirements.
2.3.9.2. The fee computer shall have the following features, functions and
components:
2.3.9.2.1. Calculate parking fee using machine readable tickets and
built-in processing capability. The fee computer cannot be connected
to a controller or another computer for the purpose of performing
machine readable ticket read functions. The fee computer and ticket
dispenser must provide machine readable functions on a continuous
off-line basis. The fee computer system shall read and decode the
ticket upon insertion during the exit process.
2.3.9.2.2. Capacity to have rate structures including but not limited to;
2.3.9.2.3. Variable rates (6 rates minimum)
2.3.9.2.4. Fixed rates (4 rates minimum)
2.3.9.2.5. Zones or Blocks within each rate (3 minimum)
2.3.9.2.6. Discount Keys configured to dollars, time or percent (25
merchant -type accounts minimum)
2.3.9.2.7. Compute and display change to cashier. An alpha- numeric
display shall be used by the fee computer to communicate
information and instructions to the cashier.
44 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.9.2.8. Dual cash drawer system
SENTRY CONTROL SYSTEMS, INC. — Only one cash dralver is
available
CITY OF SAN RAFAEL -ACCEPTED
2.3.9.2.9. An electronically -activated cash drawer shall be contained
within each exit fee computer.
2.3.9.2.10. The units are opened by continuous duty solenoids activated
by a signal from the cashier terminal.
2.3.9.2.11. Requires double cash drawer firmware.
2.3.9.2.12. Separately locked and an integral part of the Fee Computer
Unit
2.3.9.2.13. Calculate sales and use taxes
2.3.9.2.14. Provide programmable options for:
2.3.9.2.14.1. Drawer operation
2.3.9.2.14.2. Printer failure
2.3.9.2.15. Fee computer shall be capable of programming options for
the processing, identifying, and posting to reports the following
transactions:
2.3.9.2.15.1. Cashier Shift Report - all activity by a single cashier,
including time card and revenue by shift
2.3.9.2.15.2. Lane Activity - all cashier activity for that lane with
buried non -resectable grand totals
2.3.9.2.15.3. Duration Statistics - cars parked by time period
2.3.9.2.15.4. Revenue Statistics - revenue by time period, rate
structures, merchant account,
2.3.9.2.15.5. Sales and Use Tax reports
2.3.9.2.16. Fee computer shall be capable of programming options for
the processing, identifying, and posting to reports the following
unusual transactions:
45 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.9.2.16.1.
Lost ticket, utilizing a color coded exception ticket
2.3.9.2.16.2.
Mutilated ticket, requiring manual entry of data
2.3.9.2.16.3.
Insufficient funds, requiring a debit feature
2.3.9.2.16.4.
Clear, No Sale key count
2.3.9.2.16.5.
Stolen tickets identified by management
2.3.9.2.16.6.
15 different non -revenue transactions, such as
employees or emergency vehicles
2.3.9.2.16.7.
Voided or canceled transactions
2.3.9.2.17. Real Time Clock - Each Fee Computer shall be equipped
with a real time clock implemented as a portion of the
microcomputer to accommodate the following time -related
functions:
2.3.9.2.17.1. Grace period - extra time allowed at no charge for
exiting
2.3.9.2.17.2. Complimentary time, such as no parking space,
incorrect entry into lot.
2.3.9.2.17.3. Grace or lag time allowed for duration of exit from
location where ticket was validated.
2.3.9.2.17.4. Programmable time formats (AM/FM vs.military,
dd/mm/yy formats, etc.)
SENTRY CONTROL SYSTEMS, INC. - Only military time display.
SENTRY CONTROL SYSTEMS, INC - Based on the Meetin- of
916/0' the system delivered to San Rafael will be capable of meeting
this specification, as it will have programmable time_formats as
stated herein.
CITY OF SAN RAFAEL - ACCEPTED.
2.3.9.2.17.5. The clock shall be accurate to better -than -two
minutes per month, and used to keep track of month, day,
hours, minutes, and seconds for calculating fees and recording
current time on exit transactions.
2.3.9.2.17.6. The Time & Date information is to be updated via the
keyboard by supervisory personnel only with the use of
Supervisor keys or FMS. Fee computer will automatically
adjust for changes in month, Daylight Savings Time, and leap
year.
2.3.9.2.18. Audio Alarm - The Fee Computer shall be equipped with a
microcomputer controlled audio alarm. The alarm shall be activated
by the terminal whenever an improper situation is detected to attract
the attendant's attention to the display for further instructions.
2.3.9.2.19. Power Supply - Power Reserve for Power Failure. The
battery shall maintain and protect the clock, data entries and stored
programs for 72 hours during power outage. When power is
restored, the starting time and the end of power failure period shall
be printed on the journal tape. The following system requirements
46 Exhibit "A"
Revenue Control and Parking Management Equipment
are expected:
2.3.9.2.19.1.
2.3.9.2.19.2.
40C)
2.3.9.2.19.3.
2.3.9.2.19.4.
Power source - AC 120 V + 50/60 Hz.
Ambient condition Temperature: 14F - 104F (-I OC -
Humidity: 10% - 90% (RH) (No water condensation)
Contractor shall provide and install PC -grade quality
uninterruptible power supply (UPS) with built-in surge
suppression for fee computers.
2.3.9.2.20. Cashier and Supervisory Identification shall be
accomplished via special keys or PIN which are kept in the fee
computer where two digit identification numbers can be entered by
the cashier(s) on duty. Supervisory and management keys or PIN are
required for obtaining report information. The identification number
data bank shall accommodate 99 different cashier/supervisor I.D.
numbers. The fee computer shall not be functional unless an
authorized ID # is entered.
2.3.9.2.21. Lock down plate shall be provided to cover validator, power
supply and fee computer cables to prevent tampering.
2.3.9.2.22. Printer Options to be provided:
2.3.9.2.22.1. User -programmable receipt printer shall be separately
locked and an integral part of the Fee Computer System.
Receipt to include out time, date, fee charged, transaction #,
lane # or cashier ID, and facility name.
2.3.9.2.22.2. User -programmable journal printer shall record
details of all transactions. (Daily shift Report for each cashier
accessible by separate key or PIN.) (24 hour Grand Total
Report accessible by separate key or PIN.) Journal shall be
separately locked and an integral part of the Fee Computer
System.
2.3.9.2.23. Fee Display
2.3.9.2.23.1. The Fee Indicator shall contain electrically
illuminated numerals that are 2-1/2" high minimum. It shall
display to the customer the parking fee and the change due.
SENTRY CONTROL SYSTEMS, INC. - Character Size on the fee
indicator is'/o of an inch.
CITY OF SAN RAFAEL - ACCEPTED
2.3.9.2.23.2. Between transactions the Fee Indicator operates in
blank mode.
SENTRY CONTROL SYSTEMS, INC. -Idle mode shows time
instead of blanks.
CITY OF SAN RAFAEL ACCEPTED
2.3.9.2.23.3. The Fee Indicator shall be packaged for all weather
outdoor use with a NEMA Type IV enclosure (or equivalent)
47 Exhibit "A"
Revenue Control and Parking Management Equipment
finished to match other PARCS equipment in color, style, and
durability. The lighted display digits shall be tilted and placed
in a compartment that is mounted in the CCF window facing
the patron.
SENTRY CONTROL SYSTEMS, INC. - Indoor unit. Can be
packaged for outdoor use if required but specification is for indoor
use.
CITY OF SAN RAFAEL - Specification is for outdoor use under
cover. It is understood that this machine will function in a parking
f teility that is open to the elements, and may reside close to an open
air entrancelexit exposed to rain, wind-borne dust, etc. All
materials needed to meat the specification listed herein shall be
supplied by SENTRY CONTROL SYSTEMS, INC. at no additional
cost to the CITY. This unit is expected to function under these
conditions and in compliance with the specifications listed herein.
SEN7RYCONTROL SYSTEMS, INC. - ACCEPTED
2.3.9.2.23.4. The Fee Indicator is hardware connected, and is
mounted internally to the cashier counter and is sealed in place
with no cable visible from the interior or exterior of the cashier
booth.
2.3.9.2.24. All electrical connections shall be tamper -proof within one
inch rigid conduit.
2.3.9.2.25. Locking Ticket Vault
2.3.9.2.25.1. Tickets processed through the fee computer shall be
transported via an internal track mechanism into a locking
ticket vault inaccessible to the cashier.
2.3.9.2.25.2. Vault provided shall have a capacity of at least 1000
tickets
2.3.9.2.25.3. A stacker or other device shall be provided to channel
the tickets into the vault to assure they are stacked in
transaction ring order, with the first ticket processed on the
bottom and the last ticket processed on top.
SENTRY CONTROL SYSTEMS, INC. - No locking ticket vault available
CITY OF SANR4FAEI_ - -ICCF.PTF.D
2.3.9.2.26. Mag Stripe/Barcode Reader for Fee Computer
48 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.9.2.26.1. Reader shall decode data magnetically or barcode
printed in Interleaved 2 of 5 symbology encoded on patron
tickets and be compatible with fee computer provided.
2.3.9.2.26.2. Unit shall be capable of operating off-line or on-line,
in conjunction with fee computer, with a central PC.
2.3.9.2.26.3. Data to be provided and decoded includes Lot #,
ticket dispenser #, rate key, ticket issue #, year/month/day, time
of issuance, store account #.
2.3.9.2.26.4. Operation: Ticket shall be inserted into validator and
fee computer total key shall cause reader to validate ticket with
and deposit ticket in locked vault. Fee computer shall then
issue vend signal to raise gate.
2.3.9.2.26.5. Printing: Ticket shall be imprinted with person -
readable type including transaction #, cashier ID, rate applied,
net fee, exit/entry time.
2.3.9.2.26.6. Types of media accepted:
2.3.9.2.26.6.1. Tickets issued from Manufacturer's Ticket Dispensers
2.3.9.2.26.6.2. Service or Discount Tickets
2.3.9.2.26.6.3. Prepaid Tickets
2.3.9.2.26.6.4. Store number (01-127) encoded on entry ticket by
portable encoders
2.3.9.2.26.6.5. Standard Credit Cards
2.3.9.2.26.6.6. All types of media accepted as defined in
Manufacturer's Proprietary Format Specification
2.3.9.2.26.6.7. Magnetic Specifications
2.3.9.2.26.6.7.1. Mag Stripe Placement: Conforms to ISO
Track specifications.
2.3.9.2.26.6.7.2. Refer to Manufacturer's Standard Ticket
Specifications, if any, for location
2.3.9.2.26.6.7.3. Mag Stripe Coercivity:
2.3.9.2.26.6.7.3.1. 300 orsted to 650 orsted
2.3.9.2.26.6.7.4. Mag Head:
2.3.9.2.26.6.7.4.1. 0.240" (6.096 mm) width write head
centered on ISO track 11
2.3.9.2.26.6.7.4.2. 0.060" (1.524 mm) width read head
centered on ISO track 11.
2.3.9.2.26.6.8. To allow reading of credit cards.
2.3.9.2.26.6.8.1. Mag Encoding Density:
2.3.9.2.26.6.8.1.1. 110 BPI only
2.3.9.2.26.6.8.1.2. Mag Encoding Format:
2.3.9.2.26.6.9. Data is recorded twice on the magnetic stripe
2.3.9.2.26.6.10. A format may be defined in Manufacturer's
Proprietary Format Specification
2.3.9.2.26.6.11. Barcode specifications
2.3.9.2.26.6.11.1. Software configured to use transient barcode
tickets and barcode system tickets
49 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.9.2.27. Uninterruptible Power Supply
2.3.9.2.27.1. Provide backup power for fee computer and count
system for a period of not less than two hours.
2.3.9.2.27.2. Back-up unit shall have lightning and surge
suppression built in
2.3.9.2.27.3. Back-up unit shall contain a rechargeable battery
system which maintains a minimum of 90% of full charge at
all times
2.3.9.2.28. Surge Suppressors
2.3.9.2.28.1. Unit shall be capable of suppressing a surge of up to
1800 joules without system damage
2.3.9.2.28.2. Unit's manufacturer shall offer a warranty on
equipment damaged by lightning when device is attached to a
maximum of $25,000.
2.3.10. Mag Stripe/Barcode Auto Exit System (EV)
2.3.10.1. EV system shall accept a mag stripeBarcode ticket and allow patron exit
within programmable parameters. Unit shall be operable either on-line or off-
line.
2.3.10.2. System shall be capable of determining if ticket data as programmed by
controller is valid and will vend gate if all parameters are satisfied.
2.3.10.3. Parameters shall include:
2.3.10.3.1. Ticket valid for facility
2.3.10.3.2. Ticket has been paid
2.3.10.3.3. Ticket that has been directly encoded or bar coded with
validation.
2.3.10.3.4. Ticket is accompanied with a machine readable validaiton.
2.3.10.3.5. Ticket is accompanied by a credit card for payment.
2.3.10.3.6. Ticket has not exceeded grace time allowed
2.3.10.3.7. Invalid tickets not meeting all the above parameters shall be
returned to the patron with either programmable visual and/or audio
instruction.
2.3.10.3.8. Invalid tickets shall not vend exit gate.
50 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.10.3.9. Grace or lag time shall be programmable from a minimum
of 0 up to 99 minutes.
2.3.10.3.10. System shall include any programmer needed to set user
preferences and to provide reports on system activities.
2.3.10.3.11. Customers exiting within the "Rate Structure" defined grace
period will be allowed exit without having their ticket processed at
the CCF or POF stations.
2.3.10.4. Lane Status Indicators
2.3.10.4.1. Signs shall be approved by Consultant
2.3.10.4.2. Incandescent illuminated message enclosures shall be
pedestal -mounted by the Contractor in the following locations and
manner:
2.3.10.4.3. Existing Facility (See Attached Drawings)
2.3.10.4.4. New Facility (See Attached Drawings)
2.3.10.4.5. Unit shall feature:
2.3.10.4.6. Duranodic bronze finish
2.3.10.4.7. Galvanized Steel Cabinet
2.3.10.4.8. Aluminum Raceways
2.3.10.4.9. Maintenance -free operation
2.3.10.4.10. Lettering visible from 100 feet.
2.3.10.4.11. Unbreakable Lexan message panel
2.3.10.4.12. High Output Incandescent Traffic Bulbs.
2.3.10.4.13. Galvanized steel or extruded aluminum cabinet
2.3.10.4.14. Louvered sunscreen for visibility
2.3.11. POF Machine at CCF
2.3.11.1. Unit shall feature:
51 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.11.1.1. Accept Dollar Bills from $1.00 to $20.00 for payment
2.3.11.1.1.1.
Provide change in coin only to include $1.00 coin.
2.3.11.1.1.2.
Programmable variable rate structure
2.3.11.1.1.3.
Self -replenishing change fund
2.3.11.1.1.4.
Printed receipt
2.3.11.1.1.5.
Locking cash drawer
2.3.11.1.1.6.
Download transaction reports
2.3.11.1.1.7.
Machine readable mag strip/Barcode reader for ticket
transactions
2.3.11.1.1.8.
Unit shall be on-line with the PARCS
2.3.11.1.1.9.
Compute parking fee
2.3.11.1.1.10.
Accept Validations
2.3.11.1.1.11.
Accept Credit Card or Debit Card or other similar
cash value
card
2.3.12. On -Line Facility Management System
2.3.12.1. Specify the minimum requirements of the PC and components needed for
the specifications of the contract documents.
2.3.12.2. System Components
52 Exhibit "A"
Revenue Control and Parking Management Equipment
2.3.12.2.1.1. Existing Facility:
2.3.12.2.1.1.1. One Fee Computer and 2 POF Units, two entrance
lane UO devices and two exit lane UO devices.
2.3.12.2.1.2. New Facility:
2.3.12.2.1.2.1. One Fee Computer and 2 POF unit, four entrance
lane UO devices and two exit lane UO devices.
2.3.12.2.1.3. AV4/PC readers in each entrance and exit lane.
2.3.12.2.1.4. A laser or color inkjet jet printer with 4KB or greater
buffer and a parallel interface, with a minimum 300 DPI
resolution at a rate in excess of 4 pages per minute for text..
2.3.12.2.1.5. Computer requirements may vary among individual
FMS software modules. This also applies to local or wide area
network system configurations. However, the selected
Contractor shall provide hardware, software, and firmware
suitable to operate each station's FMS in either a "stand-alone"
mode or, at CITY's option, networked with a Central
Management System compatible with the FMS hardware,
software, and firmware.
2.3.12.2.1.6. ODBC database (SQL format preferable) for the
purpose of exportating data into Crystal Reports for the
purpose of building custom reporting.
2.3.12.2.1.6.1. Provide access to the configuration of data tables for
the purpose of outsourcing the custom report development.
2.3.12.2.1.7. Option pricing for the ability of the A/R system to
integrate with the City Finance system. (See section 4.2.3 for
attached specifications.
53 Exhibit "A"
Reuenue Control and Parking Management Equipment
3. SYSTEM INTRODUCTION
3.1. General
3.1.1. The On -Line System shall provide for two way communications and reporting to
and from all devices including ticket dispensers, gates, central cashiering stations, exit
stations, "AAWC" Readers and parking lanes installed under this contract.
3.2. The primary goals of the On -Line Systems are as follows:
3.2.1. Enhance customer service by improving response time to changing operational
conditions.
3.2.2. Provide a higher level of audit control for the parking operation by monitoring,
accumulating, storing, and time and date stamping selected device, lane, and parking
facility transaction and exception event activity.
3.2.3. Furnish management with the statistical transaction and report data required to
effectively manage a modem, state-of-the-art parking operation.
3.2.4. Provide consolidated, historical data for future analysis and planning purposes.
3.2.5. Supply the centralized monitoring tools required by a Central Cashiering Parking
Operation.
3.3. System General Requirements
3.3.1. The contractor shall provide an integrated software system that operates on a single
personal computer or personal computer network.
3.3.2. All software functions, programs, and reports shall be menu driven, utilizing a
generally accepted, PC industry, standard user interface.
3.3.3. The contractor shall provide a conversion utility program to export all created
reports and the stored transaction data stream into a fixed field length, flat ASCII,
comma or space delimited format suitable for importation into an off-the-shelf
spreadsheet program, such as MS Excel.
3.3.4. Contractor shall provide the instructions, tools and utilities necessary to
demonstrate this import routine during acceptance testing.
54 Exhibit "A"
Revenue Control and Parking Management Equipment
3.3.5. Contractor shall provide, at no additional cost, any software revisions, updates and
standard enhancements to the standard software product, or to the options supplied to
meet the requirements of this contract, which are released during the warranty period
of the system.
3.3.6. After the initial warranty period, software patches and fixes are to be provided at no
additional cost to the City.
3.3.7. Any such software revisions, updates and enhancements and related documentation
shall be supplied within sixty (60) days of the revisions implementation to the
standard product line.
3.3.8. All alarm conditions generated by the parking control system shall be capable of
generating an audible tone and displaying on the central computer monitor
independent of, and without interruption to, the current system user function.
3.3.9. As an example, if the user is working on the creation of a lengthy report or
programming option, any alarms conditions must be displayed to the user, in a
separate window or dedicated screen area, in real time without interrupting the user's
current function.
3.3.10. The software system shall be capable of handling a 100% expansion in
terms of the number of devices, lanes monitored and controlled.
3.3.10.1. It is recognized that additional hardware, such as gates, ticket dispensers and
even some communications related components, may be required at an
additional cost for a 100% expansion of the parking system. It is the intent of
this provision to insure that the software system itself will not require
replacement or upgrade to handle the additional devices, lanes and facilities.
3.3.11. The system shall provide for the following minimum data retention:
3.3.11.1. Transaction detail for 90 days;
3.3.11.2. Summarized shift and daily reports for 1 year;
3.3.12. Contractor shall provide a utility for downloading (storing) of historical
transaction and summary report data onto a portable media, such as floppy discs, tape
or CD-ROM.
3.3.13. Contractor shall also provide a utility for uploading and analysis of
historical data back onto the system without compromising the current data integrity.
3.3.14. All report printouts shall have column and row headings in either full
English, or clear abbreviations of English.
55 Exhibit "A"
Revenue Control and Parking Management Equipment
3.3.15. System Security: Passwords
3.3.15.1. Password security shall be provided for each of the following functions,
independently:
3.3.15.1.1. Responding to alarm conditions;
3.3.15.1.2. Printing or viewing of transaction data and/or reports;
3.3.15.1.3. Accessing or editing any device programming;
3.3.15.1.4. Accessing or editing system configuration parameters;
3.3.15.1.5. Accessing system user database and passwords;
3.3.15.1.6. System security passwords shall be configurable by an
authorized system user only.
3.3.15.1.7. All password security shall have a corresponding record file,
and shall create an audit trail of each user's use of the central
computer software system.
3.3.15.2. System Security: Data Integrity
3.3.15.2.1. Under no circumstances shall the stored raw transaction
detail, summarized report audit data or non-resettable audit numbers
generated by the parking devices be available for editing using the
system application program.
3.3.15.2.2. Any over -ring or under -ring transactions or summary totals
that may require adjustments shall be addressed by the addition of
adjusting journal entries or other additional records, which shall be
viewed as a separate line items in addition to the original raw data.
3.3.15.2.3. Any raw data files that may be stored in industry standard
DOS/ASCII or standard PC Windows or Database formats as part of
the system application software shall be encrypted to prevent casual
user manipulation.
3.3.15.2.4. It shall not be possible to simply power up the central
system, interrupt a "batch" program boot sequence with the keyboard
(using standard Ctrl/Break keystrokes) and edit the audit data using a
widely available text editor or database application program.
3.3.15.2.5. Credit Card transactions from the POS terminals shall be
stored in an encrypted format and transmitted to the credit
56 Exhibit "A"
Revenue Control and Parking Management Equipment
processing agency in an encrypted format.
3.3.15.2.6. Notwithstanding all of the above, it is recognized that no
computer system is totally secure, and that each level of security
comes at a price to the end user. It is the intent of this section to
provide, at minimum, a first level of security only, to prevent a
casual PC novice from hacking his or her way into the audit data.
3.3.15.3. System Security -System Activity Logs
3.3.15.3.1. The software shall provide an activity log of all user sign on
and sign off activity on the system.
3.3.15.3.2. User acknowledgments of system generated alarms shall
also be maintained in the system activity logs.
3.3.15.3.3. All system activity log entries shall include a time and date
stamp, along with the system number and user ID.
3.4. Revenue System: General Requirements
3.4.1. The On -Line Revenue System includes all system related communications utilities,
functions and reports that pertain to the Ticket Dispensers, Central Cashiering
Stations and Exit Station Devices.
3.4.2. Revenue System: Device Monitoring & Control
3.4.2.1. The Revenue System shall be capable of programming the Ticket
Dispensers, Central Cashiering Stations and Exit Station Device parameters
from the central computer.
3.4.2.2. The system shall also provide a utility to automatically update selected
devices at pre-programmed times and dates.
3.4.2.3. The central computer shall be capable of testing all rate structure
programming, using "what if' entry ticket data, to insure that the rate
programming is correct prior to downloading the new rate structures to the
payment terminals.
3.4.2.4. The revenue control software system shall be capable of updating and
synchronizing the internal clocks of the Ticket Dispensers, Central Cashiering
Stations and Exit Station Devices from the central computer.
3.4.2.5. The system shall also provide a utility to automatically update all or selected
devices with the current time and date at pre-programmed times and dates.
57 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.2.6. It shall be possible to close a shift, daily or other tour of duty cycle of a
payment terminal from the on-line revenue system computer.
3.4.2.7. The system shall also provide a utility to automatically close, store and reset
accumulators of the tour of duty cycles for all or selected devices at pre-
programmed times and dates.
3.4.2.8. The following exception revenue transactions shall be displayed as alarm
messages in real time on the central computer screen:
3.4.2.9. Ticket Dispenser Generated Alarms:
3.4.2.10. Back Out With Ticket (Stolen Ticket);
3.4.2.11. Back Out Without Ticket (Abandoned Ticket);
3.4.2.12. Ticket Jam;
3.4.2.13. Low Tickets;
3.4.2.14. Test/ Maintenance Ticket Pulled;
3.4.2.15. Ticket ID number changed;
3.4.2.16. Central Cashier Alarms:
3.4.2.17. Back Out Ticket (Stolen Ticket) presented for processing;
3.4.2.18. Maintenance or canceled ticket presented for processing;
3.4.2.19. Credit Card Denied;
3.4.2.20. Manual entry (mutilated, or unreadable) ticket;
3.4.2.21. Lost Ticket;
3.4.2.22. Exit Station Alarms to include auto gate reverse
3.4.2.23. Exit Grace Time Expired;
3.4.2.24. Unprocessed Entry Ticket inserted as an exit pass;
3.4.2.25. Transaction Reporting
3.4.2.25.1. The on-line revenue control system shall maintain a
58 Exhibit "A"
Revenue Control and Parking Management Equipment
historical database of all payment terminal transaction history,
generated by the Central Cashiering Stations, one record for each
transaction processed, each record to include the following fields, at
a minimum:
3.4.2.25.2. Consecutive, minimum four (4) digit unique transaction
number, traceable to the payment terminal's sequential audit trail;
3.4.2.26. Payment Terminal Identification Number
3.4.2.27. Central Cashier Identification Number (If any)
3.4.2.28. Date and Time of Transaction;
3.4.2.29. Rate Structure Identification Code to include code for monthly parking rates
3.4.2.30. Amount of Transaction up to $9,999.99
3.4.2.31. Validation Identification Code (If Any)
3.4.2.32. Discount or Validation Amount
3.4.2.33. Payment Method (Cash, Credit Card Type)
3.4.2.34. Short Money (A/R) Amount (If any);
3.4.2.35. Exception Transaction Codes (Manual, Lost, Etc)
3.4.2.36. Unique Ticket ID Number
3.4.2.37. The on-line revenue control system shall maintain a historical database of
all Exit Station Transaction detail data, including incomplete transaction detail
created by attempts to exit with an expired pass, etc. Each record shall include
the following fields, at a minimum:
3.4.2.37.1. Consecutive, minimum four (4) digit unique transaction
number, traceable to the Exit Station terminal's sequential audit trail;
3.4.2.37.2. Unique Exit Station ID #;
3.4.2.37.3. Date & Time of Exit;
3.4.2.37.4. Exception event code, if any (lag time exceeded,
unprocessed entry ticket attempted at exit, etc);
3.4.2.37.5. Unique Ticket Number, traceable back to the ticket
59 Exhibit "A"
Revenue Control and Parking Management Equipment
dispenser from which the ticket was issued.
3.4.2.37.6. Amount of fee forgiven, if gate opened centrally or by
authorized cashier ID Card;
3.4.2.37.7. The on-line revenue control system shall provide a query
tool enabling the user to search the various transaction databases for
records matching a specific set of field variables as may be defined
by the user. For example, the query tool shall allow the user to print
a list of all transactions that match all of but not limited to the
following criteria:
3.4.2.37.8. All tickets processed for payment, at any payment terminal
or central cashiering station;
3.4.2.37.9. All tickets processed for payment from May 1 -May 3;
3.4.2.37.10. All tickets over $ 6.00;
3.4.2.37.11. All tickets discounted for a series or single validation;
3.4.2.37.12. All tickets issued in Lane 1;
3.4.2.37.13. Under the above example, the query tool would only list
those tickets that matched all of the above criteria.
3.4.2.37.14. Using the query tool, it shall also be possible to print a
complete transaction history for a single ticket, by simply requesting
all records that match the unique ticket identifier field. The ticket
issue location, time and date, payment history at the payment
terminals and Exit Station data shall then be printed, providing the
user with a quick history for any ticket. In addition to the obvious
audit control value of this ticket history, customer service will be
greatly enhanced by providing the capability to quickly access the
above data to handle customer requests for assistance.
3.4.3. Revenue System: Audit and Statistical Reports
3.4.3.1. Available Data Set
3.4.3.1.1. The Revenue System shall store and print all individual Exit
Station and Central Cashier Audit and Statistical Reports as defined
elsewhere in this specification;
3.4.3.1.2. Any and all audit reports generated locally from either the
Central Cashiering Terminals, POF stations or Exit Station
60 Exhibit "A"
Revenue Control and Parking Management Equipment
Terminals (including amounts "forgiven" by central user as
described elsewhere in this specification) shall be transmitted
automatically to the Revenue System and stored for future retrieval.
3.4.3.1.3. It shall also be possible to transmit the Shift, Daily and Non-
Resettable audit reports to the on-line Revenue Control System from
the payment terminals without printing the reports locally.
3.4.3.1.4. Finally, it shall be possible to generate shift and daily
reports from the on-line revenue reporting system.
3.4.4. Consolidated Report Generation
3.4.4.1. The Revenue System shall have the capability of combining the data from
the collected shift and daily audit reports into a single consolidated report, based
on user defined criteria, including, but certainly not limited to:
3.4.4.2. Selected Payment Terminals (#1 only, #1 & #3 only, etc ... All);
3.4.4.3. Selected Report Date Ranges (From -To);
3.4.4.4. Selected Report Time Ranges (From -To);
3.4.4.5. Selected Cashier ID #;
3.4.4.6. All reports shall include the following information in the report header:
3.4.4.7. Time and date of the report;
3.4.4.8. ID of the person taking the report;
3.4.4.9. All search criteria from which the report was created;
3.4.4.10. Consolidated reports shall contain the same data fields from which the
individual reports were created;
3.4.4.11. Consolidated reports shall be available for all reports created at the
individual terminals, including:
3.4.4.11.1. Shift ("Z") and Daily ("ZZ") Reports;
3.4.4.11.2. Validation Reports;
3.4.4.11.3. Duration of stay reports;
3.4.4.11.4. Exit Statistics reports;
61 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.5. Count & Monitoring System General
3.4.5.1. The count, control and monitoring system shall provide real time and
historical information of all defined event counts, occupancy reports and
equipment status, alarms and activities occurring at each parking facility.
3.4.5.2. The count, control and monitoring system shall capture data and generate
reports on a continuous basis. The system shall monitor predefined alarm
conditions and take the actions defined when any alarm condition is activated.
3.4.5.3. The count, control and monitoring system shall perform three (3) primary
functions:
3.4.5.4. EVENT COUNTERS: Produce device, lane and facility event counters,
sufficient to provide a reliable audit trail, which increment as real world events
occur.
3.4.5.5. STATUS AND ALARM INDICATORS: Display device, lane and facility
status and alarms based upon predefined characteristics to allow monitoring of
the events in real time as the status is occurring.
3.4.5.6. DIFFERENTIAL COUNT SYSTEM: Display facility occupancy (or spaces
available) for the various patron groups and control full signs and other devices
based upon a pre-programmed set of conditions.
3.4.5.7. Count & Monitoring System Operational
3.4.5.7.1. The count, control and monitoring system shall provide
Event Counters and shall record the following events on separate
totalizers including but not limited to the following:
3.4.5.7.2. Ticket Entry Lane:
3.4.5.7.3. Barrier gate closing loop count
3.4.5.7.4. Legal tickets issued
3.4.5.7.5. Manual, or test, tickets issued
3.4.5.7.6. Backouts without ticket
3.4.5.7.7. Backouts with ticket;
3.4.5.7.8. Illegal Entry
3.4.5.7.9. Legal forward counts;
62 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.5.7.10.
Manual gate raise;
3.4.5.7.11.
Ticket Exit Lane:
3.4.5.7.12.
Barrier gate closing loop count
3.4.5.7.13.
Gate open (vend) signal;
3.4.5.7.14.
Manual gate raise
3.4.5.7.15. Illegal exit
3.4.5.8. The count, control and monitoring system shall provide status (s) and alarm
(a) messages. Status Messages shall be displayed on the screen only, at a
minimum. Alarm messages shall be displayed on the screen, with a short
audible tone, be logged on the printer and stored on the hard disc in a separate
file with a time and date stamp documenting where and when the alarm occurred
and which system user acknowledged the alarm condition.
3.4.5.9. Ticket Entry Lane status (s) and alarm (a) messages shall include the
following:
3.4.5.9.1. Barrier gate open / closed
3.4.5.9.2. Ticket in throat
3.4.5.9.3. Low tickets
3.4.5.9.4. Vehicle on ticket dispenser loop A
3.4.5.9.5. Vehicle on barrier gate closing loop B
3.4.5.9.6. Backout without ticket
3.4.5.9.7.
Backout with ticket
3.4.5.9.8.
Illegal entry
3.4.5.9.9.
Illegal exit
3.4.5.9.10.
Manual gate raise
3.4.5.10. Ticket Exit Lane status and alarm messages shall include the following:
3.4.5.10.1. Barrier gate open / closed
63 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.5.10.2. Vehicle on Exit Station loop A
3.4.5.10.3. Vehicle on Exit Station closing loop
3.4.5.10.4. Car On Loop Too Long
3.4.5.10.5. Illegal exit
3.4.5.10.6. Manual gate raise
3.4.5.10.7. Gate Up Too Long
3.4.5.11. The count, control and monitoring system shall create a short audible tone
for all alarm conditions. The short audible tone shall repeat, at intervals to be
adjusted by an authorized use of the system, until acknowledged by the central
system user.
3.4.5.12. Status Indicators shall display events as they occur on the central computer
monitor screen. While it may not be possible to display all events in all lanes
simultaneously, it shall be possible to display all selected exception events as
alarm messages.
3.4.5.13. Differential Count System
3.4.5.13.1. Total Spaces Available
3.4.5.13.2. Ticket Spaces In Area
3.4.5.13.3. Access Tag Spaces In Area
3.4.5.13.4. At each parking entry lane a count of one (1) is to be
subtracted from the total spaces available in the associated parking
facility each time a vehicle enters through the lane or into a counting
queue.
3.4.5.13.5. At each parking exit lane a count of one (1) is to be added to
the total spaces available in the associated parking facility each time
a vehicle exits through the lane or out of a counting queue.
3.4.5.13.6. The entry and exit counts shall also be applied to either the
transient or monthly differential counter dependant on the device
used for access or egress.
3.4.5.13.7. Once (0) ticket spaces are available for a specific facility,
the differential count software system shall be capable of either
64 Exhibit "A"
Revenue Control and Parking Management Equipment
automatically or manually transmitting a parking area close signal
to:
3.4.5.13.8. Disable the ticket dispenser
3.4.5.13.9. Illuminate the "Full" sign(s) for that facility;
3.4.5.13.10. Once one (1) or more ticket spaces are available, the
differential count software system shall be capable or automatically
or manually transmitting a parking area open signal to:
3.4.5.13.11. Enable the ticket dispenser(s) for that facility;
3.4.5.13.12. Turn off the "Full' sign(s) for that facility;
3.4.5.13.13. The differential count software system shall incorporate
anti -coincidence logic to prevent the loss of simultaneously
occurring counts.
3.4.5.13.14. The differential count software system shall be capable of
maintaining two (2) separate counts where one shall provide "Full'
sign enable and the second shall provide "Full' sign disable, in the
event that separate thresholds are to be set by the authorized system
user.
3.4.5.13.15. Each counter value shall be independently programmable by
an authorized system user.
3.4.5.14. Count & Monitoring System Reporting
3.4.5.14.1. Available Data Set
3.4.5.15. The count and monitoring system shall maintain a historical data base of
event accumulators by hour of the day by facility and drive lane.
SENTRY CONTROL SYSTEMS, INC. - Counts reported by hourly increments.
CITY OF SAN RAFAEL -A CCEPTED
3.4.5.16. The count, control and monitoring system shall maintain a historical data
base of alarm events, to include the time and date of the event, the location
(device number or lane ID) of the event and the ID of the central system user that
acknowledged the event.
65 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.5.17. The count, control and monitoring system shall maintain a historical data
base of peak vehicle occupancy by facility and patron type by hour of the day for
each day of system operation.
3.4.5.18. Activity reports by drive lane. The database shall produce a report that
defines the peak vehicle capacities by hour of the day for each parking lane:
3.4.5.19. Ticket Entry Peak Activity Report
3.4.5.19.1. Parking Area Identification;
3.4.5.19.2. Identification Number of Personnel taking the report;
3.4.5.19.3. Date and Time of report;
3.4.5.19.4. Date and Time of period start;
3.4.5.19.5. Date and Time of period close;
3.4.5.19.6. Number of peak ticket transactions by hourly time
increments;
3.4.5.19.7. Number of monthly transactions by hourly time increments;
3.4.5.20. Ticket Exit Peak Activity Report
3.4.5.20.1. Parking Area Identification;
3.4.5.20.2. Identification Number of Personnel taking the report;
3.4.5.20.3. Date and Time of report;
3.4.5.20.4. Date and Time of period start;
3.4.5.20.5. Date and Time of period close;
3.4.5.20.6. Number of peak ticket transactions by hourly time
increments;
3.4.5.20.7. Number of monthly transactions by hourly time increments;
3.4.5.21. The Count & Monitoring System shall produce a report that displays the
alarm event activities as selected by the user from the various alarm conditions
stored on disc. Each report shall include:
3.4.5.21.1. Parking Facility / Lane and/or Device ID
66 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.5.21.2. Identification Number of Personnel taking the report
3.4.5.21.3. Date and Time of report
3.4.5.21.4. Date and Time of period start
3.4.5.21.5. Date and Time of period close
3.4.5.21.6. Date and Time Alarm Event Occurred
3.4.5.21.7. Search parameters under which report was designed
3.4.5.21.8. Description of each alarm event
3.4.5.21.9. ID of system user acknowledging each event
3.4.5.22. The Count & Monitoring System shall produce a report that displays the
occupancy levels of the various facilities by patron type (transient and monthly),
by hour for each day. The report shall include:
3.4.5.22.1.
3.4.5.22.2.
3.4.5.22.3.
3.4.5.22.4.
3.4.5.22.5.
Parking Facility Identification
Identification Number of Personnel taking the report
Date and Time of report
Date and Time of period start
Date and Time of period close
3.4.5.22.6. Number of transient vehicles in the facility by hourly time
increments
3.4.5.22.7. Number of monthly vehicles in the facility by hourly time
increments;
3.4.6. Access Control System General
3.4.6.1. The On -Line Access Control System shall provide real time and historical
information of the "A/PC " ID Tag Database and Transaction event activities
occurring at each parking facility.
3.4.6.2. The Access Control System shall capture data and generate reports on a
continuous basis. The system shall monitor predefined alarm conditions and
take the actions defined when any alarm condition is activated.
67 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.7. Access Control System Operational
3.4.7.1. The on-line access software system shall maintain a data base of all access
tag holders. Database fields shall include the following:
3.4.7.1.1. Tag ID #
3.4.7.1.2.
Name
3.4.7.1.3.
Address
3.4.7.1.4.
Phone 1
3.4.7.1.5.
Phone 2
3.4.7.1.6.
License Number 1
3.4.7.1.7.
Vehicle Make, Model, Year, Color 1
3.4.7.1.8.
License Number 2
3.4.7.1.9.
Vehicle Make, Model, Year, Color 2
3.4.7.1.10.
Employer
3.4.7.1.11.
Card Group Number(s)
3.4.7.1.12.
Payment Status
3.4.7.1.13.
Payment Expiration Date
3.4.7.1.14.
Amount of Last Payment Posted
3.4.7.1.15. Issue Date
3.4.7.1.16. Assigned Parking Facility(s) or valid Reader Interface
Terminal ID #'s.
3.4.7.1.17. E-mail address
3.4.7.1.18. It shall be possible for an authorized system user to access
the above record by keying in the Name, Tag ID # or License Plate #
as a search identifier, If only one of either the name, tag or license
plate data are known to the user, it shall still be possible to access
the entire record.
68 Exhibit "A"
Revenue Control and Padang Management Equipment
3.4.7.1.19. Each use of an "AVWC " tag in a parking lane shall create
a tag transaction event record, which shall be recorded on the system
hard disc for report purposes.
3.4.7.1.20. Each record shall include the following fields:
3.4.7.1.21. Reader Interface Terminal Identification Number
3.4.7.1.22. Date and Time of the Event
3.4.7.1.23. Access Tag Number
3.4.7.1.24. Event Description, including:
3.4.7.1.25. Entry, or Exit Granted
3.4.7.1.26. Exception Events, to include:
3.4.7.1.27. Passback Violation (Soft Granted, or Hard Attempted)
3.4.7.1.28. Time Zone Violation Attempted
3.4.7.1.29. No Vehicle (arming)
3.4.7.1.30. Invalid Tag
3.4.7.1.31. Payment Expired
3.4.7.1.32. Sequential Tag Transaction Number
3.4.7.1.33. The authorized user shall have the capability of selecting
whether to print all real time tag transaction events (including every
legal entry and exit), or to print real time exception events only.
3.4.7.1.34. The Access Control System shall include a payment
expiration feature, capable of automatically disabling a tag for use in
the facilities once the monthly payment period has elapsed, unless a
subsequent payment for the current month has been posted.
3.4.7.1.35. The Access Control System shall include the following
Lease Matrix models.
69 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.7.1.35.1. Limit the number of cards issued to a master tenant.
(If the master tenant is allowed no more than 50 cards, the
system will not allow, without supervisor authorization, cards
above the 50 card threshold to be added to the Master tenant
account.
3.4.7.1.35.2. Charge the master tenant for a number of cards but
allow the master tenant to possess additional cards for the
following usages;
3.4.7.1.35.2.1. The master tenant may have only a predetermined
number of cards in the facility at any given time. All cards
over the predetermined limit would be denied access.
3.4.7.1.35.2.2. The master tenant may have only a predetermined
number of cards in the facility at any given time. All cards
entering over the predetermined limit would be charged
and billed to the master tenant through the A/R system a
fee that would be user settable per the existing rate
structure, a flat fee or a fee structure discounted from the
posted rate structure.
3.4.7.2. Access Control System Reporting
3.4.7.2.1. "AV-1/PC " Tag Database Reports
70 Exhibit "A"
Reuenue Control and Parking Management Equipment
3.4.7.2.1.1. The system shall be capable of producing a report of
active tags sorted by any one or more of the following fields:
3.4.7.2.1.1.1. Starting & Ending Tag ID #
3.4.7.2.1.1.2. Starting & Ending Last Name
3.4.7.2.1.1.3. Starting & Ending License Number 1
3.4.7.2.1.1.4. Starting & Ending Employer
3.4.7.2.1.1.5. Starting & Ending Card Group Number(s)
3.4.7.2.1.1.6. Assigned Parking Facility(s) or valid Reader Interface
Terminal ID #'s
3.4.7.2.1.1.7. Tag Activity Reports
3.4.7.2.1.1.8. The on-line revenue control system shall provide a
query tool enabling the user to search the tag transaction
database for records matching a specific set of field
variables as may be defined by the user.
3.4.7.2.1.1.9. For example, the query tool shall allow the user to
print a list of all transactions that match all of but not
limited to the following criteria:
3.4.7.2. 1. 1.10. All tags attempting to violate passback requirements;
3.4.7.2.1.1.11. All tags attempting to exit from the "C" Street Exit
Only
3.4.7.2.1.1.12. All Activity from May 1, (year) through May 15,
(year).
3.4.7.2.1.1.13. Under the above example, the query tool would only
list those tag events that matched all of the above criteria.
3.4.7.2.1.1.14. Using the query tool, it shall also be possible to print
a complete transaction history for a single tag within a
specified date range, by simply requesting all records that
match the unique tag identifier field.
3.4.7.2.1.1.15. In addition to the obvious audit control value of this
ticket history, customer service will be greatly enhanced by
providing the capability to quickly access the above data to
handle customer requests for assistance.
3.4.7.2.1.1.16. The Access Control System shall print a report on
demand, and automatically at a user specified time each
day, that identifies the quantity of access tag patrons parked
in each parking facility based on the anti-passback status
("IN") of the tags. The primary purpose of this report is to
provide the user with an auditable number that can be used
to assist with the reconciliation of tickets to vehicle
inventory.
3.4.7.2.1.1.17. Because the count & monitoring system number is
adjustable by the user, this requirement cannot be met by
the count & monitoring system.
3.4.7.2.2. Credit Card On File Functions
3.4.7.2.2.1. The Credit Card On File software module shall be a
Windows-based program that must work in conjunction with
71 Exhibit "A"
Revenue Control and Parking Management Equipment
the Card Access software module provided by Contractor. The
software shall be the latest available, non -beta version.
3.4.7.2.2.2. All information shall be stored in a Microsoft Access
Database file format on the computer hard disk with built-in
exporting utility to transfer to a variety of software packages.
User-friendly interactive color graphics and contact -sensitive
help shall ease software operation.
3.4.7.2.2.3. All credit card information shall be stored and
transmitted in an encrypted format.
3.4.7.2.2.4. Credit Card On File Functions
3.4.7.2.2.4.1. General
3.4.7.2.2.4.1.1. Parking management shall have the capability
provided by the FMS software as described above to
link access cards, including "AV4/PC" type vehicle -
mounted transponder, to a credit card placed on file
by agreement between parking management and
patrons.
3.4.7.2.2.4.1.1.1. Types of Transactions
3.4.7.2.2.4.1.1.2. The credit card may be charged for parking
fees per the programmed rate structure on:
72 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.7.2.2.4.1.1.3. "Pay-as-you-go" basis - Each charge that is
incurred is individually authorized via the FMS
software, credit card on file module, and credit card
clearing house firmware/software.
3.4.7.2.2.4.1.1.4. "Pay-as-you-go", Batched basis - Each charge
that is incurred is grouped with other charges and
authorized at a pre-set time of day or at the
conclusion of a cashier shift via the FMS software,
credit card on file module, and credit card clearing
house firmware/software.
3.4.7.2.2.4.1.1.5. "Decrementing" basis - Each charge that is
incurred is individually authorized via the FMS
software, credit card on file module, and credit card
clearing house firmware/software. At setup of the
patron's account the system shall be capable of
manual entry and processing of necessary credit card
and patron data. Renewals of the account may be
accomplished on either and automatic or manual
basis, at the option of parking management. The
amount charged is set up as a debit to the patron's
account which is drawn down by successive patron
transactions according to the prevailing fee schedule.
3.4.7.2.2.4.1.1.6. This function shall have at least the following
attributes:
3.4.7.2.2.4.1.1.7. The initial amount to be debited to the
decrement account shall be user settable, for example
$60.
3.4.7.2.2.4.1.1.8. Each paid transaction will draw down the
amount in the patron's account within the FMS
software per the prevailing fee schedule. The amount
drawn down shall not be a separate credit card
authorization transaction, but shall be credited to the
account and transferred to, and recognized by, the
Revenue System as a credit card payment.
3.4.7.2.2.4.1.1.9. The system shall be capable of accepting a
lower threshold at which the account may be
automatically and/or manually refreshed, at parking
management's option.
3.4.7.2.2.4.1.1.10. When a lower threshold is reached, for
example $20, the system shall automatically refresh
the account by requesting authorization to charge $40
to the credit card account when the amount in the
account falls below $20. The charge shall be a
"signature on file" transaction, if allowed. If
successful, the patron's decrement account balance
shall be brought up automatically to $60.
73 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.7.2.2.4.1.1.11. If the credit card authorization is denied for
any reason, the FMS system shall continue to allow
the patron to enter and exit the facility until the
amount in the decrement account is insufficient to
allow the next transaction. When this occurs, the
transponder or card associated with the credit card
shall be denied exit from the facility and the patron
shall return to the central cashier via a bail out or
escape lane for a manual re -authorization of the
account or cash settlement of any balance due.
3.4.7.2.2.4.1.1.12. Authorization Threshold Setting
3.4.7.2.2.4.1.1.13. The FMS software and/or credit card clearing
house firmware/software shall have the capability of
providing a threshold below which signature is not
required on an individual credit card receipt and the
transaction is batched with others for group
processing at the end of a programmable time period,
such as daily or at the end of a shift.
3.4.7.3. Traffic Controllers
3.4.7.3.1. Incandescent illuminated message enclosures shall be
mounted by the Contractor in the following locations:
3.4.7.3.2. Pendant -mounted above Dedicated Entrance and Exit
Lanes, and Reversible Lane.
3.4.7.3.3. Message shall be green (OPEN) or red (CLOSED),
selectively illuminated via a switch, automatically keyed as follows:
3.4.7.3.4. Unit above Dedicated Entrance Lane # 1, 3, 6, 7 & 9 below
entry plaza shall be OPEN at all times, unless entry gate is locked in
the down position.
3.4.7.3.5. Unit above Reversible Entry Lane #10 above entry plaza
shall be OPEN when the dispenser is active
3.4.7.3.6. Unit above Reversible Exit Lane # 10 shall be CLOSED
when Ticket Dispenser is active, OPEN when Ticket Dispenser is
inactive.
3.4.7.3.7. Unit above Dedicated Exit Lane # 2,4 & 8 below entry plaza
shall be OPEN at all times, unless entry gate is locked in the down
position.
74 Exhibit "A"
Revenue Control and Parking Management Equipment
3.4.7.3.7.1.
3.4.7.3.7.2.
3.4.7.3.7.3.
3.4.7.3.7.4.
3.4.7.3.7.5.
3.4.7.3.7.6.
3.4.7.3.7.7.
3.4.7.3.7.8.
3.4.7.3.7.9.
3.4.7.3.7.10.
3.4.7.4. Consumables
Unit shall feature:
Duranodic bronze finish
Galvanized Steel Cabinet
Aluminum Raceways
Maintenance -free operation
Lettering visible from 100 feet.
Unbreakable Lexan message panel
High Output Incandescent Traffic Bulbs.
Galvanized steel or extruded aluminum cabinet
Louvered sunscreen for visibility
3.4.7.4.1. Contractor shall furnish the following operating stock items
prior to commencement of operational testing as described in Part 3.
Contractor must provide samples for CITY approval prior to final
order of any item that is custom printed. Actual size of tickets and
ACS card shall be selected by the manufacturer. The color and art
work of tickets must be approved by CITY. CITY will provide
camera-ready art work for logos.
3.4.7.4.2. 100;000 tiek, is p .,t GFFV'sspeEifieatier3s
3.4.7.4.3. 1 Gallon Gear Reducer Oil
3.4.7.4.4. (2) Gate Arms
3.4.7.4.5. 10 Rolls receipt paper
3.4:7.46, 1P75 AVT Tags /Generie) n 25 external mount A Vi Tags
O \ / � IVIIlI�l 1 ♦ Tags
e - 2000 PCtags
3.4.7.4.7. 5 printer ribbons
3.4.7.5. Communications between Facilities
3.4.7.5.1. City will provide trenching under "B" Street and provide
conduit for the purpose of installing fiber optic cable used for the
purpose of communicating with the CCF located in the parking
office of the New Facility.
75 Exhibit "A"
Reuenue Control and Parking Management Equipment L
4. EXECUTION
4.1. General
4.1.1. Meetings
4.1.1.1. Contractor shall meet with CITY and CITY's designated representatives
within 30 days of contract award to verify all details of PARCS system specified
herein and any approved substitutions. Meet with Electrical Contractor, before
any rough -in work begins, to review building plans as they relate to PARCS
equipment, to explain details or precautions necessary to assure that all parking
and revenue control equipment will work properly, and to determine that all
required conduits and wiring are properly laid out. Contractor shall be available
to attend additional work -in -progress meetings during the installation, testing,
inspection, and acceptance phases as required.
4.1.2. Submittals
4.1.2.1. Provide those responsible for related work with shop drawings showing
required locations of conduits, anchor bolts, blockouts and other information
required to properly perform related work by the date spcified in the timeline.
4.1.3. Project Site Conditions
4.1.3.1. General
4.1.3.1.1. Contractor shall deliver or cause to be delivered equipment
to site or to bonded location packaged to prevent damage and
marked for easy identification.
4.1.3.1.2. If delivered to site, Contractor shall store equipment in
original containers in clean, dry location designated by General
Contractor and/or CITY and shall replace damaged materials at no
cost to CITY.
4.1.3.1.3. PARCS components shall be installed under and operate
dependably within environmental conditions indigenous to the
facility location in the city and state in which the PARCS is
installed. Contractor shall inspect site and provide equipment which
is suitable for site conditions and install same according to
manufacturer's specifications.
4.1.4. Electrical Requirements
76
Revenue Control and Parking Management Equipment
4.1.4.1. All equipment shall be properly grounded.
4.1.4.2. CITY will not provide back-up emergency power at site.
4.1.4.3. CITY will provide "clean" power which for the purposes of this Project
shall be defined as 115 VAC +/- 10% and 60 Hz from circuits dedicated to the
PARCS. Contractor shall provide any additional power conditioning required for
the operation of the system as described herein.
4.1.5. Installation
4.1.5.1. General
4.1.5.1.1. Install PARCS in accordance with manufacturer's
recommendations and approved Shop Drawings, as follows:
4.1.5.1.1.1. Pull all low voltage control wire and cable.
4.1.5.1.1.2. Hook-up all low voltage control wire and cable.
4.1.5.1.1.3. Mount in place all equipment.
4.1.5.1.1.4. Install all vehicle detector loops.
4.1.6. Provide complete system
4.1.6.1. Contractor shall be responsible for supplying and installing all control and
communication wiring and Contractor supplied equipment and its interfacing
and interconnection with CITY supplied equipment. The Contractor shall
authorize and accept responsibility for application of power to the equipment
and initiation of operation, be responsible for running all initial diagnostics and
system generation programs necessary to provide complete working system.
4.1.7. Training & Customized Setup
4.1.7.1. General
4.1.7.1.1. Contractor shall deliver system complete and customized
for CITY's use appropriate to that described above. Contractor shall,
prior to final system installation and configuration review with
CITY and Consultant proposed customization of user software
interfaces, count and reporting matrices, and other customized
applications, interfaces, or products.
4.1.7.1.2. PARCS manufacturer and/or Contractor shall provide 5
days of on-site training by factory personnel to instruct the user on
the software programming and operation of the system and to assist
in programming setup and troubleshooting as needed. The
contractor must also include an additional 5 days of training as
follow-up to be completed between the 60th day and 90th day after
77 Exhibit "A"
Revenue Control and Parking Management Equipment
the initial training period is completed. Additionally the contractor
must provide for a maximum of one hour per week of telephone
assistance during the first year of the initial warranty period.
Telephone assistance must be available to the City through a toll free
number.
4.1.7.1.3. In addition, PARCS manufacturer and/or Contractor shall
provide 5 days of on-site training on the service and maintenance of
the equipment and system and to assist in programming setup and
troubleshooting as needed.
4.1.7.1.4. Training shall include at least all of the following:
78 Exhibit "A"
Revenue Control and Parking Management Equipment
4.1.7.1.4.1.
4.1.7.1.4.2.
4.1.7.1.4.3.
4.1.7.1.4.4.
4.1.7.1.4.5.
4.1.7.1.4.6.
4.1.7.1.4.7.
4.1.7.1.4.8.
4.1.7.1.4.9.
4.1.7.1.4.10.
4.1.7.1.4.11.
4.1.7.1.4.12.
4.1.7.1.4.13.
Comprehensive Overview of All Equipment
Operational Theory
General Review of System Documentation
Performance of Basic Tasks
Repair Procedures
Trouble Shooting Techniques
Problem Isolation
System Diagnostics
Spare Parts Inventory
Preventive Maintenance and Service Requirements
Contractor Contacts for Technical Service
Service and Trouble Report Logs
Manuals detailing the above shall be provided by
Contractor.
4.1.7.1.4.14. Contractor shall submit copy of the training class
attendance logs, signed by the CITY's personnel, prior to
receiving final system acceptance.
4.1.7.1.4.15. User Groups
4.1.7.1.4.16. Cashiers shall be trained to:
4.1.7.1.4.17. Operate the cashier terminal. Operation of the cashier
terminal shall include the ability to process normal and
exception transactions, and to understand any and all system
messages provided by the cashier terminal.
4.1.7.1.4.18. Perform troubleshooting techniques to correct
common exit equipment problems, such as resetting a gate that
has failed to cycle properly.
4.1.7.1.4.19. Maintenance personnel shall be trained to:
4.1.7.1.4.20. Perform all the above.
4.1.7.1.4.21. Provide primary maintenance on all major
components of the system.
4.1.7.1.4.22. Replenish all system supplies.
4.1.7.1.4.23. Clear ticket and other paper jams.
4.1.7.1.4.24.
Reset the system after a power failure.
4.1.7.1.4.25.
Replace internal elements such as circuit boards
4.1.7.1.4.26.
Lubricate and clean internal components.
4.1.7.1.4.27.
Remove and replace gate arms and adjust gate arm
travel.
4.1.7.1.4.28.
Repair/replace gate hardware such as cotter pins,
articulating
arms, etc.
4.1.7.1.4.29.
Be certified by the contractor to perform routine
maintenance.
4.1.7.1.4.30.
Supervisors shall be trained to:
4.1.7.1.4.31.
Perform all the above.
4.1.7.1.4.32. Understand any and all system messages provided by
the FMS, including but not limited to alarm messages,
indications of attempts to compromise the PARCS and
79 Exhibit "A"
Revenue Control and Parking Management Equipment
explanations of atypical lane activity displayed by the count
system and revenue control system.
4.1.7.1.4.33. Be able to correlate tickets issued with vehicles
present, time parked with revenue generated through fee
computer.
4.1.7.1.4.34. Be able to understand the purpose and data contained
within any and all reports produced by the FMS.
4.1.7.1.4.35. Be able to program the FMS.
4.1.7.1.4.36. Be able to process exception transactions occurring at
exits.
4.2. Exhibits
4.2.1. Exhibit A — Specifications for Importing InForum Journal Entry Transacitons
4.2.2. Exhibit B — Equipment Location for 3 d and A St. Parking Garage
4.2.3. Exhibit C — Equipment Location for 3`d and A St. Parking Garage
4.2.4. Exhibit D — Specifications for Reversible Lane Options
80 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parking Management Eubment
SECTION V - BID FORM
(Must be completed by Vendor)
Please complete the following table for any exceptions to the product specifications.
Spec # Description Proposed Mitigation
The undersigned proposes to furnish all materials, supplies, equipment or services set forth
herein subject to all conditions outlined in the Bid Document, including the general instructions
and information to bidders, at prices indicated below:
Bid Proposal for the above: $
Purchases to be made at the option of the City:
The following items may be purchased at the option of City in any quantity, greater or
lesser than stated in this document. If there is a Minimum Purchase Requirement for
the specific price please state it in the appropriate column.
Description
Price Per
Unit
Additional equipment for reversible land configuration for xxxxxxxxx
Lane 1
Additional equipment for reversible land configuration for xxxxxxxxx
Lane 9
Integration for exportation to EDEN system for monthly xxxxxxxxx
customer A/R information
Total Options Bids
Total Minimum
Price Unit
Purch
Req.
Xxxxxxxxx
Xxxxxxxxx
81 Exhibit "A"
-ritle: Revenue Control and Parkino Management Eubment
Bid Proposal + Options: $
Payment Terms
Exceptions or Deviations attached YES NO
Financing options attached YES
Company Name
Taxpayer ID Number
Address
Designated Project Manager
Person submitting bid
Print Name
Signature
NO
Telephone
Title
BID NO. 00-00
F.O.B.
All prices of the bid shall be F.O.B. destination San Rafael, California; and delivery to any point
within San Rafael shall be without additional charge.
TAX
All bid proposals shall be exclusive of tax; City staff will compute all tax involved when
applicable.
ACCEPTANCE OF PROPOSAL
The City reserves the right to accept or reject any and all bids and reserves the right to waive
technicalities where such action best serves the interests of the City. The manufacturer of the
proposed materials or equipment may be required to acknowledge by written conformation that
the minimum requirements of the specifications are included in the Bidder's proposal before the
award of the bid.
EXCEPTIONS
Any bidder's exceptions to these terms or conditions or deviations from the written
specifications shall be shown in writing in the exceptions table provided as part of this bid form.
However, such exceptions or deviations may result in bid rejection.
$2 Exhibit "A"
Title: Revenue Control and Parkino Management Eubment BID NO. 00-00
AFTER THE ACCEPTANCE AND AWARD OF THE BID BY THE CITY COUNCIL UPON
RECEIPT OF A WRITTEN PURCHASE ORDER EXECUTED BY A PROPER OFFICER OF
THE CITY, THIS RFP AND CONTRACTOR'S PROPOSAL (EXHIBIT "A") WILL CONSTITUTE
THE LEGAL CONTRACT BETWEEN THE CITY AND THE SUCCESSFUL BIDDER.
83 Exhibit "A"
Title: Revenue Control and Parkino Manaaement Eubment BID NO. 00-00
If your response is "NO BID", please explain below:
COMPANY NAME:
ADDRESS:
CITY, STATE, ZIP CODE:
TELEPHONE NUMBER:
BY:
Print Name Signature
Title Date
PLEASE RETURN TO:
CITY OF SAN RAFAEL
OFFICE OF THE CITY MANAGER
1400 Fifth Ave
SAN RAFAEL, CA 94901
84 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parking Management Euioment
EXHIBIT "A"
Specifications for Importing InFourm Journal Entry Transacations
It is the desire of the City to import/export Accounts Receivable information in both line
item and agragate totals from the City's Accounts Receivable system to the selected
FMS. Please read the following specifications and check the appropriate box in the
SECTION V of the Bid Form.
EDEN
=systems
Svecifications for Importing InForum Gold Journal Entry Transactions
Introduction
In many InForum Gold installations there is a need to
"feed" the General Ledger module from other data sources
that are outside the scope of InForum Gold; these foreign
data sources may be cash receipting (till) sub -systems, tax
collection systems, and court payment systems, among
others. The InForum Gold General Ledger module
provides the ability to import journal entries from an
external source into the general ledger.
This document describes an import file interface and
accompanying InForum Gold import program that allows
journal entry transactions from foreign data sources to be
imported into the General Ledger. The import interface
essentially replaces the entry portion of the source
document. All of the data validation operations performed
at the edit and post stages will still be applied to the
imported data. This ensures that the agency has an
85 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkino Manaqement Euipment
opportunity to correct invalid data from the foreign data
source prior to actual posting to the General Ledger.
Import File Format
The General Ledger import file, like all import files in
InForum Gold, should conform to the following
specifications.
• ASCII character content: the data in the import files
must contain only printable ASCII characters.
Control characters, non -printable characters, or
"packed" data fields are not allowed.
• One record per line: each line of the import file
constitutes a single record, or row, in the database.
Lines must be terminated with the newline
character (ASCII value 14).
• Fields separated by delimiter character. fields
(columns) within the record (row) are separated by
a delimiter character. The default delimiter
character is the I ("pipe") character, but a different
delimiter can be specified when executing the
import program. Use a delimiter character that is
sufficiently "strange" that it will not appear in field
data (the tilde, backslash and caret characters are
typically good delimiters). The last field of the
import record must be terminated with a delimiter
character, immediately followed by the newline
record terminator.
• Fixed or variable lenqth: the records in an import file
can be fixed length or variable length. Fixed length
86 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkino Management Euioment
records contain fields that are the same length
across all records (fields are padded with trailing
spaces to the field size). Variable length records
contain fields that are only as wide as the data
requires (there are no trailing spaces between field
data and delimiter characters).
The import file name must be located in a suitable
directory and have appropriate permissions such that
is readable by the user executing the import program.
Also, the import file must be writeable by the import
program, as the import filename is either renamed
with a ".done" extension, or copied to a file with a
".done" extension and emptied, at the end of the
import process.
Data Field Tvpes
Each record in the import file contains one or more
data fields, each separated by delimiter characters.
Data fields within the record are of a specified data
type; there are format and value restrictions for each
of the supported data types, as outlined below.
Character
■ Format: Alphanumeric printable characters. Case translation (forced upper -
or forced lower-case) will be performed by import program.
• Restrictions: Less than or equal to specified length. Excess characters are
truncated.
Smallint
■ Format: Numeric characters (0-9) and optional leading sign indicator (+ or
Positive sign (+) is assumed if specific sign indicator is not present.
■ Restrictions: Values within the range -32,767 to +32,767. Out of range
values result in import errors.
87 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Manaaement Eubment
Integer
■ Format: Numeric characters (0-9) and optional leading sign indicator (+ or
Positive sign is assumed if specific sign indicator is not present.
■ Restrictions: Values within the range -2,147,483,647 to +2,147,483,647. Out
of range values result in import errors.
Decimal
Date
■ Format. Numeric characters (0-9), optional leading sign indicator (+ or -), and
decimal point indicator (.). Positive sign is assumed if specific sign indicator
is not present. Decimal fields are stated in terms of precision (total number
of digits) and scale (fields to the right of the decimal point). For example,
decimal (14,2) means 12 digits to the left, and 2 digits to the right, of the
decimal point. The decimal point is optional (assumes zeros to the right of
the decimal point). If fewer digits are provided after the decimal point than
specified for the field, trailing zeros are assumed.
■ Restrictions: Values within the range determined by the field specification.
For example, decimal (14,2) can have 12 or fewer digits to the left of the
imported (or implied) decimal point and 2 or fewer digits to the right of the
decimal point. Out of range values result in import errors.
■ Format: Dates can be imported in the following formats: mm/dd/yy,
mm/dd/yyyy, mm-dd-yy, mm-dd-yyyy. If 2 -digit year format is used, the
century defaults to 1900. For example, 01/15/95 means January 25, 1995.
■ Restrictions: Invalid dates (for example, 12/32/95) result in import errors.
Data fields with null values (the lack of a value) are
specified with adjacent delimiter characters for variable
length import files, or with a series of space characters
between delimiters for fixed length import files.
Import File Specification
This section describes the specific fields of a General
Ledger journal entry import file.
An InForum Gold general journal document is a header -
detail document. That is, the header area of the document
provides basic information about the journal entry (the
transaction date, the reference, the document group, etc.),
88 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parking Manaciement Eubment
while the detail area of the document provides line -item
information for the journal entry (ledger account number,
item description, amount, debit/credit). Each record of the
import file contains both header and detail journal entry
fields. Records within the import file will be grouped into
InForum Gold journal entry documents based on the
equivalence of the header fields; each record that shares
common header fields (document reference, group, date,
etc.) will be grouped onto a single document.
The specification of each field includes its order within an
import file record, the data type of the field, the mapping of
the field to the InForum Gold journal entry input screen
label, a description of the contents of the field, whether the
field requires a value, and the allowable values for the field
(above and beyond any data type restrictions noted in the
preceding section). Value restrictions may be sensitive to
other field values, and will be so noted. A non -required
field may have value restrictions, but the restrictions only
apply if a value (as opposed to null) is specified.
If a specific field within an import record is blank (spaces)
or null, it will be populated with a default value during the
import process. Default values for non -required fields will
be specified at the time of import.
89 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Manaaement Euioment
:. '.liie d
tL�rat w '-'i�v, ,'i: h.; :r:x �e ,`sl'Y %:r,; "r'•" Suit
.... -^�,rk ` :t-'4 �`'i3�r's ,De"s�Hptt! I . ...... SUN
�s'7�•Y.
1 char(10)
Doc Source
The document source
N
Must be one of the GL
code for the journal
document source codes
entry document
defined in InForurn Gold
(determines summary
transaction behavior)
2 char(9)
Ref #
The reference number
Y
None
for the journal entry
3 char(40)
Description
The journal entry
N
None
header description (the
description of the
journal entry document
as a whole)
4 char(10)
Group
The posting group for
N
None
this journal entry
5 smallint
Fiscal Year
The fiscal year that the
N
If blank, will be determined by
journal entry applies to
date
6 date
Date
The journal entry
Y
Must match the fiscal year
document date
according to agency period
structure
7 smallint
Period
Accounting period if this
N
Null for standard
journal entry is posted
transactions; a defined
to an opening or closing
opening period or closing
period
period
8 char(1)
EOP
End of period reversing
Y
Y = document automatically
Reverse?
entry
reversed in succeeding
accounting period; N =
document not reversed
9 char(1)
Summarize?
Should the document
Y
Y = document automatically
automatically
summarizes to balance
summarize to balance
sheet; N = document
sheet accounts
contains valid balance sheet
according to the
summary transactions
document source code,
or does the document
contain both originating
and valid (balanced)
balance sheet line
items?
10 char(1)
Account type
The type of account that
Y
E = expenditure
is used on the journal
R = revenue
entry line item
B = balance sheet
11 char(44)
Account
The formatted account
Y
Must be a valid account
Number
number that is used on
number for the specified
the journal entry line
account type; must be in the
item
displayed format (correct
number of levels, separator,
etc.) for the account type and
fiscal year of the document
12 char(30)
Description
Description specific to
N
None
the journal entry line
item
90 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Manaaement Euioment
Field ,Dant°
Qrder flow
0 ,�. 01
Mesa 0404 p . .Req 1Gafue res#rtcitop
13 decimal (14,2)
Amount
The amount of the
Y
None
journal entry line item
signs not allowed (+) or (-)
14 char(1)
Debit/Credit
Whether the account
N
D = Debit the account
should be debited or
C = Credit the account
credited for this line
Blank = D/C determined by
item
account type and sign of line
item amount
15 char(1)
Summary
Is this line item an
N
Only relevant if Summarize?
originating line item or a
= N (blank otherwise)
summary line item?
O = Originating line
S = Summary line
16 char(1)
Job Costing
If the item contains job
N
Blank = no job cost numbers
Flag
costing numbers, what
for line item
type?
E (or J) = Expense
F (or G) = Funding
17 char(32)
Costing
The formatted job-
N
Must be a valid job -
Number
costing/grant-
costing/grant -accounting
accounting number
number for the specified job
used on the journal
cost type; must be in the
entry line -item
displayed format (correct
number of levels, separator,
etc.) for the fiscal year of the
document
What follows is a sample journal entry import file. It
consists of five records, each with the fields described in
the preceding table. Due to page width limitations, each
line has been broken after the document description field;
in an actual import file, the arbitrary line breaks would not
occur.
adjjrnallA]-127731EXPENDITURE TO REVENUE TRANSFER
lfinancell995112/01/19951INlYIE1011.14.514.230.31021Transfer to
revenue1500.0 DIIII
adjjrnallAJ-127731EXPENDITURE TO REVENUE TRANSFER
Ifinancell995112/01/199511N1YIR1011.316.430.001From computer supplies
expense1500.01c1111
adjjrnallAJ-22711FICA ADJUSTMENTS FOR 10/05/95 PAYROLL
Ifinancel1995110/20/19951ININIEI011.11.511.600.2101IFica expense
adjustment1100.01DIOIJ1999/999/9991
adjjrnallAJ-22711FICA ADJUSTMENTS FOR 10/05/95 PAYROLL
Ifinancel1995110/20/19951ININIBI011.292.2001Adjust expense control1100.01Dlslll
adjjrnallAJ-22711FICA ADJUSTMENTS FOR 10/05/95 PAYROLL
Ifinancell995110/20/199511NINIBI011.111.1001Adjust cash balancel100.01clslll
91 Exhibit "A"
BID NO. 00-00
Title; Revenue Control and Parkina Manaaement Eubment
The five records of this sample file will translate into two
journal entry documents. The first two lines comprise the
first document (containing two line items), and the last
three lines comprise the second document (containing
three line items). These five records are translated into
two documents because of the equivalency of the "header"
fields -- the first two lines each have equivalent values for
document source, document reference, document group
and so on.
Importinq a file containinq both Subsidiary Ledqer and Balance Sheet rows
The import program in Gold splits large journal entries into
multiple journal entries. Splitting journals on imports
improves readability and performance in most cases. The
number of rows imported before a break occurs is
controlled by the GL system preference importmaxrows.
The default is set at 190 rows.
If you are importing journal entries with both subsidiary
ledger account lines (revenue and/or expenditure
accounts) and balance sheet account lines, balance sheet
debits and credits may not be equal on split journal entries.
Even though the sum of imported balance sheet debits
and credits is equal, journal entries that are split every 190
lines may not be split at points where all journal entries
contain equal balance sheet debits and credits. To
accommodate this issue, set the value on importmaxrows
sufficiently high so the import program does not split
journal entries.
92 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkina Manaoement Eubment
If you are importing only subsidiary account lines, the GL
import document source code makes sure that balance
sheet debits and credits are always equal. Any arbitrary
split should be acceptable.
93 Exhibit "A"
BID No. 00-00
Title: Revenue Control and Parking Manaoement Eubment
M Lall-lba-M
E.
94 Exhibit "A"
BID NO. 00-00
Title: Revenue Control and Parkinq Manaaement Euiament
95 Exhibit "A"
BID NO. 00-00
Title Revenue Control and Parkinq Manaaement Eubment
€) # ..T "C"
Equipment SpeGifir-ations fGF Reversible Lanes
96 Exhibit "A"
Parking Access and Revenue Control System Fee Agreement
Between the City of San Rafael and Sentry Control Systems
Exhibit "B"
Base Bid
Options
Reversable Lane 1
Reversable Lane 9
POF Stations
EDEN Integration
Additions
Note Dispenser
Multi -Read Head Exit Verifiers
Multi -Read Head Exit Verifiers
Multi -Read Head POF Station
Multi -Read Head POF Station
Multi -Read Head Entrance
Multi -Read Head Entrance
Eliminations/Discounts
AVI
Central Cashiering Booth
UPS System
Tickets/Smart Gate/Lot Full
Directional Lighting
POF Discount
Preformance Bond
$250,000 Bond
Fund Control
Transaction Fee
$ 542,117.00
$ 11,900.00
$ 11, 900.00
$ 49,665.00
$ 3,590.00
$ 30, 776.00
$ 851.00
$ 3,065.00
$ 681.00
$ 2,452.00
$ 681.00
$ 2,452.00
$ (112,884.00)
$ (16,901.00)
$ (19,192.00)
$ (7,171.00)
$ (6,087.00)
$ (60,000.00)
$ 5,000.00
$ 2,750.00
$ 7.50
Exhibit "B"