City of Lawrence Parking Management - Parking Management Functionality
Subsystem Description
The Parking Management Subsystem (PMS) provides electronic monitoring and management of parking facilities. It supports a Field-Vehicle Communications link to the Vehicle Subsystem that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. This portion of the subsystem functionality must be located in the parking facility where it can monitor, classify, and share information with customers and their vehicles. The subsystem also interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region. Note that the latter functionality may be located in a back office, remote from the parking facility.
Functional Area: Parking Data Collection
Collection and storage of parking management information. For use by operations personnel or data archives in the region.
| ID | Requirement | Status |
|---|---|---|
| 1 | The parking element shall collect parking management data including lot usage and charging information. | Long-term |
| 2 | The parking element shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data. | Long-term |
| 3 | The parking element shall receive and respond to requests from ITS Archives for either a catalog of the parking management data or for the data itself. | Long-term |
| 4 | The parking element shall be able to produce sample products of the data available. | Long-term |
Functional Area: Parking Electronic Payment
Parking payment collection using in-vehicle equipment (tags) or contact or proximity traveler cards used for electronic payment. Includes field elements and back-office functionality.
| ID | Requirement | Status |
|---|---|---|
| 1 | The parking element shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable features, etc.). | Existing |
| 2 | The parking element shall read data from the traveler card / payment instrument carried on-board the vehicle or by the traveler. | Existing |
| 3 | The parking element shall provide an interface to the driver informing them of the success or failure of the financial transaction. This may involve a request for the driver to pull aside so the operator can resolve an issue. | Existing |
| 4 | The parking element shall collect data on payment violations and send the data, including images of the violator and the vehicle registration data obtained from the Department of Motor Vehicles (DMV) office, to the appropriate enforcement agency. | Existing |
| 5 | The parking element shall manage the parking lot charges, considering such factors as location, vehicle types, and times of day. | Existing |
| 6 | The parking element shall process the financial requests and manage an interface to a Financial Institution. | Existing |
| 7 | The parking element shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments. | Existing |
| 8 | The parking element shall process requests for parking lot charges to be paid in advance. | Existing |
| 10 | The parking element shall maintain a list of invalid traveler credit identities. | Existing |
Functional Area: Parking Management
Monitor vehicles and current parking availability within parking facilities. Use driver information systems (e.g., DMS) to provide parking availability and other parking facility information to drivers. Support local traffic control coordination around the parking facility.
| ID | Requirement | Status |
|---|---|---|
| 1 | The parking element shall maintain parking lot information including static information such as hours of operation, rates, location, entrance locations, capacity, type, and constraints; as well as dynamic information such as current state of the lot, occupancy, arrival rates, and departure rates. | Existing |
| 3 | The parking element shall manage local dynamic message signs that display messages to travelers such as the parking lot state, number of spaces available, location of entrances, and current charges. | Existing |
| 4 | The parking element shall provide the capability to detect, count, and classify vehicles at entrances, exits, and designated locations within a parking facility. | Existing |