A. General. Signing on to Server shall be accomplished only by personnel with an authorized card, the scope of the functions and capabilities of which shall be determined by the security level of the card used to sign on with.
1. Cards can be linked, and defined only by personnel signed on to the system with a sign on card assigned to the administrator security level. Internally, no two cards shall have the same number.
2. The system shall be able to utilize insertion cards, proximity cards, AVI tags, or a combination thereof with no difference in processing.
3. Insertion cards shall not be magnetic nor affected by magnetic fields.
B. Linking. The system shall contain "cold start sign on" cards that are internally hard-coded in the system software so they cannot be inadvertently de-linked, rendered ineffective, or otherwise removed from the system.
1. All other cards or credentials shall be linked only with a single, unique number;
2. The system shall not allow two cards to be simultaneously linked with the same number.
3. The administrator shall be able to disable or remove a card from the system without having the physical card.
4. In the event a card is lost, the administrator shall be able to link a new card as the same number as the lost card. Such action shall destroy neither the static information contained in the card file (name, address, paid status, etc.) nor the historical data used to review past activity for that card.
5. When card "A" is linked with the same number as card "B", card "B" shall be rendered useless and will be considered as "foreign" if an attempt is made to use it.
6. The system shall prevent linking an already linked card as a different number without first delinking the known card to prevent inadvertent mistakes.
7. System shall automatically broadcast the linking activity information to all satellite sites to eliminate having to link the card on each remote system.
C. Programming
1. The administrator shall be able to define non-cold start cards capable of signing on, including assigning a sign-on cypher code.
2. The administrator shall have the ability to assign security levels to sign-on cards to:
a. Restrict functions by commands (link, deactivate, remote open, etc.),
b. To restrict access to specific files (card file, terminal devices, house accounts, etc.),
c. To restrict the ability to view and/or update specific fields within a record (home address, debit balance, bank card number, etc.).
3. The administrator shall be able to define employee cards for use by:
a. Attendants
b. Cashiers
c. Roving Cashiers
d. Prepay attendants
e. Employees exempt from monthly payment
4. The administrator shall be able to define cards with respect to
a. Time zone
b. Area group
c. Home garage/lot
d. Defined group or house account
e. Payment status
f. Payment amount
g. Expiration time and date
h. Credit or debit balance
i. Department
j. Suite
k. Requirements to nest
l. Card feature (time zone violator, credit, debit, limit by house account, etc.).
D. Reporting. Operation of this parking facility shall be to the highest standards of fiscal accountability. Accordingly, the following requirements will identify the role the revenue control system shall provide in achieving the necessary accountability.
1. Software accountability: The software that operates the key revenue control elements including, but not limited to, the fee calculating registers and the revenue reporting computer(s) shall be unalterable in the field by any person, including any person who may have access through a phone line.
2. The entire system shall be completely impervious to any software virus
3. The system shall report hourly, on hard copy, and on the system hard drive, which software release is running in the field. The manufacturer shall certify that any change in the software will be accompanied by a change in the release version number of the software.
4. The manufacturer (supplier) shall certify that there are no means by which its employees (or others) can change any data on the system except through the normal, auditable, methods of:
a. Signing on (using card and cipher) with the proper level of authorization
b. Using the system as a user and causing a printed record and an electronic record on the system disc log.
E. Protection of critical data.
1. The Software: The system software shall reside in EPROM.
a. There shall be no ability to load software into the system from the fixed disc, the removable disc, a phone line or any other means.
b. This lack of ability shall be absolute. The process of performing such function shall not exist. It is not sufficient to turn them off.
c. There shall be no "back door" access to the software.
2. The Memory: The main memory of the system is volatile. No critical data shall be supported in this memory even if battery is backed up. This includes transaction numbers, etc. All critical data shall reside on the system's fixed disc. This data falls into three categories:
a. Category A refers to site data. The site data shall include:
1) The name and address of the location.
2) The date the disc was formatted and loaded with this data in the manufacturers factory.
3) The serial number of the system.
4) There shall be no ability to load or change this data in the field or tamper with it in anyway.
b. Category B refers to financial data collected by the system. There shall be no ability to change this data in the field except as a result of legitimate customer transactions.
1) Such changes shall be controlled by the operational software warranted by the manufacturer as complying with this requirement.
2) There shall be no ability to reload this data nor to reformat this portion of the disc in the field.
3) It shall not be possible to dynamically allocate this space, but shall at all times be located in a known fixed area.
4) Such control shall be "hard coded" into the system and shall not be able to be modified in the field.
c. Category C refers to the system parameters (rates etc.) customer files and other data. The owner shall be able to change this information as needed under the normal security procedures built into the system.
F. Reporting unusual events: Unusual events shall be printed as they occur (on continuous fan fold paper) and, along with all other events, logged as they occur to the electronic log where they shall be available for review, either on-demand and immediate, or at some point in the future. It shall not be possible to disable or alter this information in any way. Events classified as unusual shall include but not be limited to:
1. Every transaction at the register where the ticket was not read and processed by the system as a normal valid ticket, such as a manually or locally issued ticket
2. Every ticket that was issued as a back-out ticket, not taken, or manual.
3. Every time the gate is opened manually.
4. Every time a car drives through a gate where the arm is open or missing.
5. Every time a gate is opened remotely. In this case the card number and name of the employee shall also be recorded.
6. Every transaction cancelled by the cashier. The system shall allow a search of such events and show the event, the ticket number, the cashier, the register and details of the ticket (time/date of issue etc) as well as the next transaction at that register.
7. Every attempt by a monthly customer to use a card out of sequence (in passback). The system shall concurrently report and record details of the previous time the card was used.
G. Reporting Functionality: The system shall
1. Be able to create and generate reports of static information:
2. Run the report(s) on demand,
3. Start the report(s) automatically by day and/or time
4. Using up to three selection criteria on any data element.
5. Print any data elements,
6. Clear or change any data element of records selected
H. PC-based Data Management Computers: The system shall hand-off an ASCII text string of all transaction data for general analysis using standard Windows-based applications such as MS Excel, Access, FoxPro and Word.
I. General System Capabilities: Manufacturer's standard software shall be compatible with the existing security access control system and provide automatic facility monitoring, supervision, and remote control of parking control equipment from one or more locations. The system shall:
1. Perform rates calculation with up to 16 rate schedules
2. Have a database of card user data including, but not limited to the following fields:
a. Last name, first name, middle name
b. Title
c. Department
d. Company name
e. E-mail address
f. Address, city, state, zip
g. Office phone and extension
h. Automobile #1 make, color, license and state
i. Automobile #2 make, color, license and state
j. Suite
k. Employee number
l. House account, uses, charges
m. Debit card number, balance today, month-to-date, year-to-date
n. Debit card time balance today, month-to-date, year-to-date
o. Opening balance
p. Bank credit card number and expiration date
q. Used today parking
r. This month payment status
s. Next month payment status
t. Parking time zone
u. Parking area group
v. Cash or credit violator
w. Security time zone
x. Security area group
y. Elevator group/floor
z. Parking feature set
aa. Security feature set
bb. Last use time, date and location
cc. Last entry time date and location
dd. Last exit time, date and location
ee. Original entry time, date and location
ff. Nesting card
gg. Remarks
3. Automatically report an access control card's last use on passback event
4. Maintain a 25-year non-clearable daily system summary of all financial transactions.
5. With the ability to review historical activity of a minimum of three million events.
6. Review all activity on demand by multiple search keys
7. Review one activity or a range of past card activities
8. Recover printout data printer off, paper out or malfunction
9. List device malfunctions for diagnostics, and preventative maintenance,
10. Review by day, month, and year and by day, employee, terminal, merchant
11. Review card violator revenue collection for limit and time zone
12. Review by both occupancy and time restrictions with the ability to calculate outside limits reports and collection of fees
J. General Future Capabilities: The City of Camden expects a minimum of seven years (preferably ten) system life from this software hardware and lane equipment acquisition. Although not required at this time, the system must be able to perform the following revenue management functions that may be needed with this ascribed time:
1. Read and fully integrate license plate information with a high accuracy rate:
a. Capture, optically read and store the license plate number on entry and exit within the same amount of time it takes to read an access control card or to vend a ticket, or 1.5 seconds, which ever is less
1) Upon contract card presentation on entry or exit, the verification with stored license plate data shall occur within the above timeframe to vend the gate
2) Upon visitor ticket vend license plate data shall be assigned to the ticket taken upon entry and matched to ticket presented upon exit for transaction completion.
b. Report automatically and on demand:
1) All outstanding tickets with associated license plates and length of stay information
2) All contract card in the garage with associated license plates and length of stay information
c. Search and find specific license plate by full plate or possible wild card numbers
d. Ability to prevent unauthorized vehicles, regardless of validity of card, from entering a secure garage or area.
2. Nest tickets where visitors are compelled to use lesser desirable areas of parking facility by the incentive of a lower rate that will be automatically calculated when the transient parker follows the rules of arriving and leaving the area within the user-definable allotted time.
3. Assign and track a select group of two or more contract card holders to a carpool reward system to track and report the number of days the card holders carpooled for the month.
4. Permit alternate traffic and lane configurations to include:
a. Central Cashiering of transient tickets
b. Pay-on-foot stations
View Brochure PDF
Back