PERMIT-BASED PARKING ENVIRONMENT MANAGEMENT METHOD AND

SYSTEM

Field of the Invention

[001] The present invention relates generally to parking permits, and, more particularly, to a system and method for administering, managing, and monitoring permit-based parking programs.

Background of the Invention

[002] Publicly and privately administered parking programs continually struggle with the seemingly intractable problem of providing parking services for an area having a limited number of parking spaces to an ever increasing number of vehicles. Specifically, there is an increasing effort to manage the problem in residential communities, where cities and towns attempt to provide the local residents with a place to park. This effort generally involves the use of permit-based parking programs.

[003] Permit-based parking programs restrict parking privileges in an attempt to assure residents that the local residents are able to find a place to park their vehicles on a street or in a lot. The goal of such programs is to encourage persons to obtain a permit for parking privileges, or, alternatively, move non-permit holder vehicles, to metered, time-limited, or garage parking. [004] However, such programs are very difficult and expensive to implement and manage. Inefficiencies in the administration of these parking programs and a lack of enforcement of the regulations are rampant problems facing today's parking programs, leading to a significant dilution in the intended benefits.

[005] For example, a small municipality that institutes a permit-based parking program may face the task of issuing from 20,000 to 500,000 permits per year, which requires a complete overhaul of the municipality's existing parking regulation enforcement plan.

[006] While the issuance of permits assists in the institution of parking regulations, use of conventional permits includes many disadvantages. Conventional permits are typically embodied as a sticker that either affixes to a window of the vehicle or a hang-tag that hangs within the vehicle (i.e., from the rear view mirror). However, it is often difficult to determine if a permit is present based on a visual inspection of the vehicle, due to a variety of factors including the presence of tinted windows and/or the arrangement of the vehicle (e.g., angled parking). This creates a significant burden on the individual responsible for inspecting vehicle to determine if the vehicle is legally parked, referred to as a Parking Enforcement Officer (PEO), who must locate and read the permit via a visual inspection of the vehicle.

[007] In addition, conventional permits are frequently stolen or "scalped" (i.e., sold by the authorized permit holder to an unauthorized person). With no efficient means to track the permits administered under a parking program, such misuse is extremely difficult to detect and terminate.

[008] Therefore, there is a need for a method and a system for efficiently and effectively implementing, managing, administering, and monitoring a permit-based parking program.

Summary of the Invention

[009] The above-described problems are addressed and a technical solution is achieved in the art by a system and a method for managing a permit-based parking environment. The "permit-based parking environment" includes a permit management system, one or more RFID

readers, and a number of parking permits each having a unique RF3D tag and tag identifier (e.g., a tag number including a series of alphanumeric characters).

[0010] According to an embodiment of the invention, the permit management system, referred to as the "Permit View" system, provides for the efficient administration, management, and enforcement of the permit-based parking program (herein referred to as the "parking program") which governs the permit-based parking environment.

[0011] According to an embodiment of the present invention, each permit included in the parking program is assigned a unique RFBD tag identifier (e.g., a tag number), which is stored on an RFID tag attached to or embedded in the permit (e.g., in the form of an RFID chip). The

RFID tag identifier is associated with information or data specifically related to that parking permit, including, but not limited to, authorized vehicle data, permit holder data, and parking privilege data (collectively referred to as the "tag data").

[0012] According to an embodiment of the present invention, the Permit View system includes a computer-accessible memory for storing the RFBD tag identifier and associated tag data for each permit maintained by the parking program, to allow for the ongoing management throughout the life of the permit.

[0013] According to an embodiment of the present invention, the one or more parking areas of the permit-based parking environment which are regulated under the parking program, herein referred to as the "zones," are monitored by one or more RFID readers, which may be a handheld device operated by a Parking Enforcement Officer (PEO) or a stationary reader. The

RFID reader scans the parked vehicle, reads the RFID tag, and captures the RFED tag identifier.

To determine if the vehicle is permissibly parked, the RFID reader accesses the computer-

accessible memory of the PermitView system and looks up the tag data associated with the captured RPID tag identifier.

[0014] According to an embodiment of the present invention, the PermitView system provides for an efficient determination of whether or not the scanned vehicle is parked within the privileges associated with the permit. In the event the vehicle is parked in a manner outside the _. scope of parking privileges granted to that permit, an appropriate enforcement action is executed (e.g., issuance of a citation, immobilization, and/or issuance of a warning), and recorded by the PermitView system.

[0015] According to an embodiment of the present invention, the authorized vehicle data

(e.g., the color, make, model, year, plate number, etc.) associated with the scanned RFID identifier is communicated to the RFED reader, for a comparison with the parked vehicle data, to determine if the permit is being used by an authorized vehicle, i.e., a vehicle associated with the permit.

[0016] According to an embodiment of the present invention, the PermitView system may be accessed via a user interface by a number of different users, such as permit holders, permit applicants, parking program managers, PermitView administrators, and the one or more ■' readers.

[0017] According to an embodiment of the present invention, one or more docking stations, adapted for docking one or more handheld RFID readers, may access the PermitView system. The docking stations communicate with the PermitView system for synchronizing the data stored in the system and the data stored on the RFID reader. In addition, one or more stationary RFID readers may connect to the system for data synchronization.

[0018] According to an embodiment of the present invention, newly issued permits are registered in the PermitView system, which acts as a clearing house for all permits managed under the parking program. The PermitView system then tracks and monitors the use of each permit for the life of the permit.

[0019] The PermitView system provides for the effective enforcement of parking regulations, thereby creating a safe and structured parking environment which results in a realization of benefits for the permit holders and the parking program.

Brief Description of the Drawings

[0020] The present invention will be more readily understood from the detailed description of exemplary embodiments presented below considered in conjunction with the attached drawings, of which: [0021] Figure 1 is an illustration of a permit-based parking environment including a permit management system, according to an embodiment of the present invention;

[0022] Figure 2 illustrates an exemplary process for managing a permit-based parking environment, according to an embodiment of the present invention;

[0023] Figure 3 illustrates an exemplary process performed by a permit management system, according to an embodiment of the present invention; and

[0024] Figure 4 illustrates steps according to an exemplary privilege analysis, according to an embodiment of the present invention.

[0025] It is to be understood that the attached drawings are for purposes of illustrating the concepts of the invention and may not be to scale.

Detailed Description of The Invention

[0026] The present invention relates to a method and a system for administering and managing a permit-based parking program. Figure 1 depicts an exemplary permit-based parking environment managed by the methods and systems according to the present invention. A permit- based parking environment includes one or more parking areas or "zones," that are controlled by a parking program. The "parking program" includes the set of rules and regulations which govern parking in the zones of the permit-based parking environment. [0027J According to an embodiment of the present invention, the permit-based parking environment includes a permit management system (herein referred to as the PermitView System 1), one or more RFID Readers 8 for scanning vehicles located in the one or more zones, and one or more parking permits each including a unique RFID tag, (referred to in Figure 1 as RFDD TAG_1, RFE) TAG_2,...and RFID TAG-N, for a parking program having "N" number of permits). One having ordinary skill in the art will appreciate that although the present invention is described as including RFID reader technology, other reading devices and systems may be used in accordance with the invention.

[0028] According to an embodiment of the present invention, the PermitView System 1 is a computer-based system, accessible by one or more users, which includes but is not limited to the following components: a User Interface 20, a Report Generator 30, a Privilege Module 40, and a Permit Database 50. The term "computer" is intended to include any data processing device, such as a desktop computer, a laptop computer, a mainframe computer, a personal digital assistant, a server, a handheld device, or any other device able to process data. Optionally, according to an embodiment of the present invention, the Permit View System 1 may include a Synchronizing Module 60.

[0029] One having ordinary skill in the art will appreciate that the components of the

PermitView System 1 may be located on a single computer, as shown in Figure 1, or on more than one communicatively connected computers. The term "communicatively connected" is intended to include any type of connection, whether wired or wireless, in which data may be communicated. The term "communicatively connected" is intended to include a connection between devices and/or programs within a single computer or between devices and/or programs on separate computers.

[0030] One having ordinary skill in the art will appreciate that at least a portion of the

PermitView System 1 may include human-based components. For example, the User Interface 20 may be a call center or conventional office wherein persons (e.g., permit holders or applicants) may access the PermitView System 1 via a telephone or in-person communication 5Bj as shown in Figure 1.

[0031] The PermitView System 1 may be a computer-executable application or program accessible by a number of user groups, wherein the characteristics of the user group dictate the level, amount, and type of permissible access to the PermitView System 1. According to an embodiment of the present invention, the following primary user groups are defined: permit holders and permit applicants, parking program managers, PermitView administrators, and RFED readers. Each user group accesses the PermitView System 1 via an appropriate User Interface 20, which may be especially adapted and/or configured based on the particular user group, as shown in Figure 1. The User Interface 20 provides user group-specific access to the PermitView System 1, wherein the level of access is customized specifically for each user group. [0032] The 'permit holder/applicant' user group includes all persons having or seeking one or more permits related to one or more zones supervised under the parking program. As

shown in Figure I ₁ the permit holder/applicant user group may access the PermitView System 1 via a permit holder/applicant portal of the User Interface 20 using a computer, herein referred to as a Permit Holder/Applicant Computer 5. One having ordinary skill in the art will appreciate that the permit holder/applicant user group may also access the PermitView System 1 via other means, such as, for example, via a telephone or in-person communication SB, as shown in Figure 1.

[0033] The 'PermitView administrator' user group includes all persons authorized to maintain, manage, monitor, supervise, or otherwise control the PermitView System 1. As shown in Figure 1, the PermitView administrator user group accesses the PermitView System 1 via a PermitView administrator portal of the User Interface 20 using a computer, herein referred to as a PermitView Administrator Computer 6.

[0034] The 'parking program manager' user group includes all persons authorized to maintain, manage, monitor, supervise, or otherwise control the permit-based parking program being managed by the PermitView System 1. As shown in Figure 1, the parking program manager user group accesses the PermitView System 1 via a parking manager portal of the User Interface 20 using a computer, herein referred to as a Parking Manager Computer 7. One having ordinary skill in the art will appreciate that the parking program manager user group may access a call center and/or office-based User Interface 20 via a telephone or in-person communication. [0035] The 'reader' user group includes any device, preferably a RFID device, adapted to scan vehicles, or readable devices enclosed therein, in the one or more zones. As shown in Figure 1, the reader user group accesses the PermitView System 1 via a Reader portal of the User Interface 20 using a communicatively connected Reader 8.

[0036] According to an embodiment of the present invention, the Permit Holder

Computer 5, the Permit View Administrator Computer 6, the Permit Manager Computer 7, and the Reader 8 may each include a Web Browser 5A, 6A, 7A ₃ 8A, respectively, that provides a portal to one or more Web-based networks, such as, for example, a Network/Internet 100. Each Web Browser 5A, 6A ₃ 7A, 8A is communicatively connected to the PermitView System 1 via the Network/Internet 100. One having ordinary skill in the art will appreciate that any Web browser is suitable for use in the present invention, including but not limited to FireFox, Microsoft® Internet Explorer, Netscape, Opera, WebTV®, and Mozilla™. [0037] According to a preferred embodiment, the Reader 8 may be any suitable device or computer capable of reading a RFID tag. The Reader 8 may be a handheld device operated by a PEO ₅ or a stationary device. One having ordinary skill in the art will appreciate that the Readers 8 may be passive, active, or semi-active. The Reader 8 may include one or more software applications or programs (e.g., RFID/Barcode scanning and permit evaluation software such as PermJtFinder, citation writing software, etc.) configured to execute the functions performed the Readers 8, including, but not limited to, data capture, data storage, and scanning activity. Suitable Readers 8 for use with the present invention include, but are not limited to, the Symbol MC9000-G RFK) device. One having ordinary skill in the art will appreciate that the parking permit may include any readable device or means, other than a RFID tag. Accordingly, the Reader 8 may be any device capable of reading the readable device or means that are associated with the parking permit.

[0038] According to an embodiment of the present invention, one or more handheld docking stations 9, adapted for docking one or more handheld Readers 8, may be communicatively connected to the PermitView System 1 via the Network/Internet 100. A

handheld Reader 8 may be docked in the handheld docking station 9 for synchronizing the data stored in the PermitView System 1 with the data stored on the handheld Reader 8. [0039] According to an embodiment of the present invention, the handheld docking station 9 may communicatively connect to the PermitView System 1 via the Synchronization Module 60. The Synchronizing Module 60 maybe a computer-executable module capable of downloading and/or uploading data to and from the one or more Readers 8 docked in the docking station 9. Specifically, the Synchronizing Module 60 may download/upload data including, but not limited to, lists of valid permits, software updates, PEO identification information, a list of scans performed by the PEO, a list of the scan results including any enforcement action taken (Le., issued citations), announcements and alerts for PEOs, a list of malfunction notices (described in greater detail with respect to Figure 2), etc. An exemplary Synchronization Module 60 suitable for use in the present invention is the SQL 2000/CE Synchronization Tool. [0040J According to an embodiment of the present invention, the data stored on the handheld Reader 8 and in the PermitView System 1 may be synchronized in real-time via a wireless connection between the Reader 8 and the PermitView System 1. [0041] According to an embodiment of the present invention, the PermitView System 1 includes a Report Generator 30. The Report Generator 30 is a computer-executable module configured to generate reports relating to the parking program. One having ordinary skill in the art will appreciate that a variety of reports may be generated by the Report Generator 30, said reports including any information related to the parking program which is maintained by the PermitView System 1.

[0042] Exemplary reports which may be generated include, but are not limited to, reports relating to: 1) financial information (e.g., receivables of the parking program; 2) scan results; 3)

PEO-specifϊc reports including PEO performance information (e.g., number of scans, number of warning/notices, number of citations, number of times the PEO failed to take action, etc.); 4) permit holder account information; 5) permit inventory; 6) enforcement action information; 7) parked vehicle data; and 8) tag data.

[0043] The user groups (permit holders/applicants, parking program managers, readers, and/or PermitView administrators) may submit a request for a report to the Report Generator 30 via the User Interface 20. Based on the report request, the Report Generator 30 retrieves the appropriate information from the communicatively connected computer-accessible memory, referred to the Permit Database 50, generates the report, and provides the report to the requesting user group, via the User Interface 20 or the Synchronizing Module 60. The term "computer- accessible memory" is intended to include any computer-accessible data storage device or database, whether volatile or nonvolatile, electronic, optical, or otherwise, including but not limited to, floppy disks, hard disks, CD-ROMs, DVDs ₅ flash memories, ROMs, and RAMs. [0044] One having ordinary skill in the art will appreciate that the Report Generator 30 maybe configured to automatically run reports at one or more specific intervals of time (e.g., hourly, daily, weekly, monthly, yearly, etc.) according to a pre-determined and customizable schedule. For example, the Report Generator 30 may run a daily report detailing each violation that occurred in a particular zone during the previous 24 hour period, and automatically deliver said report to the Parking Program Manager Computer 7 and/or the Reader 8 associated with that zone.

[0045] According to an embodiment of the present invention, the Report Generator 30 may automatically receive report requests from the communicatively connected Synchronizing Module 60, pursuant to a pre-determined schedule. For example, the Synchronizing Module 60

may send a daily request for a report providing permit data updates, for communication with the one or more Readers 8 docked in the Handheld Docking Station 9. [0046] According to an embodiment of the present invention, when the Handheld

Docking Station 9 detects the docking of a Reader 8, it may automatic send a report request to the Synchronizing Module 60. The Synchronizing Module 60 may then send the request to the Report Generator 30 for fulfillment. For example, the Handheld Docking Station 9 may be configured to automatically request a report including updated permit holder information for a particular zone associated with a specific Reader 8, each time that the specific Reader 8 is docked in the Handheld Docking Station 9.

[0047] Figure 2 illustrates an exemplary process flow for monitoring a permit-based parking environment to determine if the vehicle(s) parked therein are permissibly parked. It is to be understood that the schematic representation provided in Figure 2 is exemplary in nature and alternative arrangements are within the scope of the invention.

[0048] In step Sl, a Reader 8 scans a vehicle parked in a permit-based parking zone managed by the PermitView System 1. The Reader 8 scans the vehicle to determine if it includes a parking permit having a valid RFBD tag. One having ordinary skill in the art will appreciate that the permit may be in the form of a sticker affixed to the vehicle or an article hanging within the vehicle. The Reader 8 may be a stationary reader or, as described herein in accordance with an embodiment of the present invention, a handheld reader operated by a PEO. According to an embodiment of the present invention, the RFID Reader 8 is configured to detect and read a permit and corresponding RFID tag from a distance. In addition, one having ordinary skill in the art will appreciate that the Reader 8 may perform the scan while the Reader 8 is in notion.

[0049] In step S2, the Reader 8 determines if a RFE) tag is detected. If no tag is detected, the Reader 8 and/or the PEO determines the reason for the failure to detect a tag, at step S3A.

[0050] During step S3A, if it is determined that the failure to detect a tag is due to an error by the reader operator, i.e., the PEO, the vehicle is scanned again, at step Sl. If the failure to detect a tag is due to reader malfunction, the Reader 8 is repaired or replaced. [0051] Alternatively, during step S3 A, it may be determined that the failure to detect a tag is due to either a tag malfunction or the absence of a tag, In either case, in step S4, the PEO identifies information related to the parked vehicle under review, referred to as the "parked vehicle data," and enters the parked vehicle data into the Reader 8. The parked vehicle data may include, but is not limited to, the following information: 1) the make, model, year, and color of the vehicle; 2) the license plate number of the vehicle; 3) the location of the parked vehicle (e.g., the lot, street, and/or zone); and 4) the date, time, and day of the week of the scan. One having ordinary skill in the art will appreciate that the PEO may enter the parked vehicle data into the Reader 8 using any suitable input means, such as, for example, a keyboard, a keypad, and/or a voice recognition system.

[0052] The parked vehicle data is used to determine if a valid tag is associated with the scanned vehicle, in step S5. For example, if upon visual inspection of the vehicle the PEO determines that no permit/tag is present, or, there is a tag/permit present but the tag is malfunctioning, the license plate number of the vehicle may be looked up in the PermitView System 1 to determine if a valid tag is associated with the vehicle. If so, the PEO may issue a notice or warning to the permit holder concerning the holder's failure to properly display the permit/tag or permit malfunction, in step S5A. According to an embodiment of the present

invention, the PeπnitView System 1 may track the number of such notices issued to a particular permit holder, and, if the number exceeds a certain threshold (i.e., three prior warnings), an appropriate enforcement action may be taken (e.g., the issuance of a citation or immobilization of the vehicle). An enforcement action may include, but is not limited to one or more of the following: 1 ) the issuance of a citation or summons; 2) the issuance of a notice or warning; 3) immobilization of the vehicle (i.e., booting) and/or 4) no action.

[0053] If during step S5 it is determined that no valid tag is associated with the parked vehicle, a determination is made as to the appropriate enforcement action, in. step S8. [0054] Alternatively, if during step S2 a tag is detected, the Reader 8 captures the unique

RFID tag identifier, herein referred to as the "tag number," in step S3B, and identifies the parked vehicle data, in step S4. One having ordinary skill in the art will appreciate that the tag number maybe any length string of alphanumeric characters capable of uniquely identifying the particular permit with which it is associated. According to an embodiment of the present invention, the tag number is stored on the RFID tag embedded in or attached to the permit. [0055] Having captured the RFID tag number and parked vehicle data, the Reader 8 sends this data to the Permit View System 1. Figure 3 illustrates at least a portion of the steps of the permit management process performed by the PermitView System 1. As shown in Figure 3, the PermitView System 1 receives the tag number and parked vehicle data from the Reader 8 via the User Interface 20, in step SI. The information is provided to the Privilege Module 40, which in turn retrieves the tag data associated with the tag number from the Permit Database 50, in step sπ.

[0056] According to an embodiment of the present invention, the "tag data" includes, but is not limited to, the following information: 1) authorized vehicle data; 2) permit holder data;

and/or 3) parking privilege data. The "authorized vehicle data" includes, but is not limited to the make, model, color, year, and/or license plate number of the vehicle or vehicles authorized under a valid permit. The "permit holder data" includes, but is not limited to, the permit holder's name, address, phone number, e-mail address, and/or facsimile number. The "parking privilege data" generally defines the scope of privileges or parking rights held by the permit holder, including, but is not limited to: a) the one or more locations, zones, streets, lots, spaces, or areas the vehicle is permitted to park; b) the term of the permit and/or the permit's expiration date; and/or c) the valid parking time or times (i.e., weekend-only rights; weekday-only rights, seasonal rights, etc.).

[0057] In step SIII, the Privilege Module 40 conducts the privilege analysis, described in detail below with respect to Figure 4. In step SIV, after conducting the privilege analysis, the Privilege Module 40 sends the results of the privilege analysis to the Reader 8. [0058] Returning to the process illustrated in Figure 2, in step S8, if it is determined that there is a violation based on the privilege analysis (see step S7) or, as described above, no valid tag is associated with the parked vehicle (see step S5), a determination is made as to the appropriate enforcement action to be taken. One having ordinary skill in the art will appreciate that the determination as to the appropriate enforcement action may be made by the PermitView System 1 (as part of the privilege analysis), the PEO, or by a parking program manager. [0059] Figure 4 illustrates the steps involved in an exemplary privilege analysis, according to an embodiment of the present invention. Generally, the privilege analysis is performed by the PermitView System 1, and includes, but is not limited to, a comparison of the parked vehicle data to the parking privilege data associated with the permit assigned to the parked vehicle. In step SA, the Privilege Module 40 determines whether or not the parked

vehicle data matches the authorized vehicle data associated with the scanned tag number in the Permit Database 50. If the data does not match, then there is a misuse of the parking permit, and a parking violation has occurred. For each parking violation that occurs, the Permit Database 50 stores information related to the parking violation, referred to as "parking violation data." The parking violation data may include, but is not limited to, the parked vehicle data (i.e., the information related to the violating vehicle); the vehicle owner's information (as derived from the license plate number), the PEO information, the type of enforcement action taken, etc. For example, a permit that has been stolen or illegally transferred to unauthorized vehicle will result in this type of mismatch, and corresponding parking violation. According to an embodiment of the present invention, if a misuse of the permit is detected, the PermitView System 1 may place a temporary hold on the permit, thereby signaling to the PEO(s) that the permit is inactive or invalid.

[0060] Alternatively, the PermitView system 1 may communicate the authorized vehicle data associated with the scanned permit to the Reader 8. Then, based on a visual inspection of the vehicle, the PEO may determine whether or not there is a mismatch between the parked vehicle data and the authorized vehicle data.

[0061] If the data matches, the Privilege Module 40 identifies the parking privilege data

(i.e., the scope of privileges) assigned to the permit, in step SB. According to an embodiment of the present invention, the parking privilege data may be defined in the parking program at the time of issuance of the permit, or at the time of a subsequent update or edit. For example, a permit holder, John Smith, may have a permit which includes parking privileges for zone "C"/ Main Street, Hoboken, New Jersey/ Monday-Friday/ between the hours of 6PM and 7AM. In addition, the same permit may also include privileges allowing John Smith, a student enrolled in

summer classes at Rutgers University, to park his vehicle in campus parking lot "1 Vl zone "H"/ spaces "19-27' V from June 1 ^st through August 15 ^th . Collectively, these parking privileges make up the parking privilege data associated with John Smith's parking permit. [0062] Referring to Figure 4, in step SC, the Privilege Module 40 compares the parked vehicle data with the parking privilege data. Next, in step SD, a determination is made as to whether the vehicle is parked within the scope of the privileges. If not, then it is determined that a parking violation has occurred, and the parking violation data is recorded and stored in the Permit Database 50. One having ordinary skill in the art will appreciate that the parking violation determination may be made by the PermitView System 1, the PEO ₅ or a parking program manager.

[0063] In the example set forth above, assume John Smith's vehicle is parked in parking lot 9/ zone "B"/ space 6 on June 17 ^th . In step SC, this parked vehicle data is compared with the parking privilege data, resulting in a determination that a parking violation has occurred, in step SD. According to an embodiment of the present invention, the Privilege Module 40 communicates the results of the privilege analysis to the Reader 8 for the execution of an appropriate enforcement action. In addition, the parking violation data is stored in the Permit Database 50.

[0064] According to an embodiment of the present invention, the PermitView System 1 may be accessed by both existing and prospective permit holders via the permit holder/applicant portal of the User Interface 20. The User Interface 20 may include an authentication or login screen which prompts existing permit holders to provide login information (e.g., a username and password). One having ordinary skill in the art will appreciate that any suitable authentication system or method may be used in accordance with the present invention, such as, for example,

ASP.Net WebForms-based authentication. A permit holder may access information related to his or her account, and perform a number of account-related tasks, including, but not limited to the following: 1) add/edit/delete/update the authorized vehicle data; 2) add/edit/delete/update the permit data; 3) add/edit/delete/update permit holder data; 4) make bill, renewal, and/or citation payments; and 5) review account information including previously issued warnings/notices and/or citations; etc.

[0065] According to an embodiment of the present invention, a person may access the

PermitView System 1 to submit a new permit application. The new permit application may include, but is not limited to, the permit holder data, the vehicle or vehicles associated with the permit, the requested scope of privileges, a means for payment, and/or the proof required for the issuance of a permit The proof required to obtain a permit may include, but is not limited to proof of residency or eligibility for residential parking privileges (e.g., a utility bill, a driver's license, a real estate tax bill, etc.), proof of employment for employee parking privileges, proof of matriculation for student parking privileges, proof of personal identification (e.g., a driver license, social security card, etc.). According to an embodiment of the invention, this information may be electronically scanned and transmitted to the PermitView System 1 in any suitable file format, such as, for example, a Portable Document Format (PDF). [0066] One having ordinary skill in the art will appreciate that an inventory of available and/or issued permits may be managed, stored, and maintained by the PermitView System 1 in a database, such as, for example, the Permit Database 40. Alternatively, the inventory may be stored in a separate database, referred to as Inventory Database 7B in Figure 1, managed and maintained by the parking program manager, via the Parking Manager Computer 7. According

to this embodiment, new applications may be received by the PeπnitView System 1 and communicated to the Parking Manager Computer 7 for review and evaluation. {0067] According to an embodiment of the present invention, a Permit View administrator may access the PermitView System 1 via the PermitView administrator portal of the User Interface 20. Preferably, an increased or relatively higher level of authentication is required for access via the administrator portal due to the type and amount of access the administrator has to the PermitView System 1.

[0068] According to an embodiment of the present invention, the one or more administrators may access the PermitView System 1 to perform a number of functions, including, but not limited to:l) setting up and administering new parking programs; 2) providing online support; 3) managing user groups; 4) setting parking privilege data in accordance with the parameters of the parking program; 5) managing permit inventory; 6) processing new permit applications; 7) managing warning/notice and citation issuance; 8) defining and providing reports to the user groups; and 9) management of billing and invoicing processes. [0069] According to an embodiment of the present invention, a parking program manager may access the PeπnitView System 1 via the parking program manager portal of the User Interface 20. As compared to the other user groups, the parking program managers require a unique level and type of access to the PermitView System 1. According to an embodiment of the present invention, the one or more administrators may access the PermitView System 1 to perform a number of functions, including, but not limited to: 1) running a variety of reports related to the parking program; 2) setting up and administering new parking programs; 3) updating/editing existing permit holder data; 4) managing permit inventory; and 5) tracking enforcement action information.

[0070] It is to be understood that the exemplary embodiments are merely illustrative of the invention and that many variations of the above-described embodiments may be devised by one skilled in the art without departing from the scope of the invention. It is therefore intended that all such variations be included within the scope of the following claims and their equivalents.