Parking provider permit data is saved to Security Center permit entities. You can use
one permit entity to store all permit data, or use a separate permit entity for each parking
provider. You must configure the properties (attributes, delimiters, and so on) of the
permit entity so that Security Center can parse the data and send it to Genetec
Patroller™.
What you should know
You can also merge regular Security Center
static permits with the Pay-by-Plate Sync’s dynamic permits. This allows you to enforce
both permit types by selecting only one permit in Patroller. To merge static and dynamic permits, the
delimiters do not need to match, however, the permits must have the same number of
attributes (not necessarily in the same order).
NOTE: This procedure describes only the
information required to use permits as containers for parking providers’ permit
data.
For more information on how to configure permits in Security Center, see Creating parking permits.
Procedure
-
Configure the permit’s properties as follows:
- Path
- The permit’s source file must be located on a drive that is
accessible by the ALPR Manager and by the Pay-by-Plate Sync plugin
role.
NOTE: If your system is configured for failover, make sure
that permit source files are located on a drive that is
accessible by all potential failover servers. The failover
servers must have both read and write permissions to the
drive.
- Use delimiters
- Turn this ON, and use any type of delimiter
supported by Security Center.
- Attributes
- You must have the attributes Category, PlateState, PlateNumber,
and PermitID in the same order for static permits and in any
order for dynamic permits. If you have any custom attributes, you
can add them after the mandatory attributes are configured. The
maximum number of custom attributes for a static permit is five. You
can also keep the EffectiveDate and ExpiryDate
attributes. If the plugin finds this data in the permit, it will be
supported.
If you are using the
EffectiveDate and
ExpiryDate attributes, note the following:
- These two attributes must always be used together.
- Ensure that the provider you are using supports these
fields.
- We recommend that you use a date time formatter that
specifies Coordinated Universal Time (UTC) time format
such as: yyyy-MM-dd HH:mm:ssZ. Note that
the Z at the end of the formatter indicates that
the time is in UTC and will therefore be correctly
transformed to local time by Patroller.
-
Click Apply.
-
In the Advanced tab, turn on Enable transfer
on modification.
-
Click Apply.
-
Configure which permits are available to be selected in Patroller:
-
Go to ALPR > Roles and
units.
-
Select the ALPR Manager you want to configure.
-
Go to Properties > File
association.
-
If you are merging static permits with Pay-by-Plate Sync dynamic
permits, you can clear those static permits from the list. They do not
need to be displayed separately in Patroller.
-
If you are using permits with permit restrictions applied to them,
select those permits to make sure they are downloaded in Patroller.
For more information on how permit restrictions work,
see Creating permit restrictions.
NOTE: When the system performs a last chance lookup to verify that the
permit has not recently been added to the permit list, it does not
take any active permit restrictions into consideration. Instead, it
only verifies if a valid license plate is found on a permit list.
Any time-based validity properties applied to the permit via a
permit restriction are ignored.
-
Click Apply.
Results
The Security Center permits are configured
to receive permit data from the parking provider.