Rules /lprAlertConditionRules

The VSP rules service allows users to configure a rule and receive an alert when a license plate event qualifies the rule. There are different rules.

Eagle Eye VSP is configured to a specific plate or to a vehicle list (a group of license plates). It supports different rules, such as:

• Allowed Vehicle
• Denied Vehicle
• Watch Vehicle
• Hotlist
• Unknown Vehicle Alerts
• Number of License Plate Events

After the alert is generated, it is sent to the alert manager service, and the action is performed as it was configured for the rule. Through alert manager integration, VSP supports different alert actions, such as notifications though the web application, emails, messages over Slack, I/O device triggers, and so on.

For the functionality of rules and their parameters to be configured, and example use cases see the following sections.

Allowed Vehicle (lprRuleAccessControlAllow)

Allowed Vehicle rules are configured to receive an alert for a specific plate, or for all plates in a vehicle list that has an access category as allow.

The configured rule can be mapped to a specific plate (RuleMapPlate) or to a specific vehicle list (RuleMapList).

Use Case Example: Generate notifications when authorized employees arrive at the facility for attendance tracking or security verification.

Denied Vehicle (lprRuleAccessControlDeny)

Denied Vehicle rules are configured to receive an alert for a specific plate or for all plates in a vehicle list that has an access category as deny.

The configured rule can be mapped to a specific plate (RuleMapPlate) or to a specific vehicle list (RuleMapList).

Example: It is possible to deny entry to a parking area for a car whose permit has expired, and receive a notification upon its arrival.

Watch Vehicle (lprRuleWatch)

Watch Vehicle is a timebound rule that allows users to track vehicles against a defined time. The Watch Vehicle rule is configured to track vehicles between two vehicle events (between an origin camera and a destination camera which can be the same). A timer is configured and if the vehicle is not detected by the destination camera at the end of the timer, a watch alert is raised.

The Watch Vehicle rule can be configured for a specific plate, a vehicle in a specific vehicle list, or for all vehicles passing between the origin camera and destination camera. Exemptions to tracking could be made if a vehicle in the vehicle list has Vehicle Category (Security Status) marked as exempt.

Examples:

• Parking: Track a vehicle between an entry and an exit and generate an alert if the parking exceeds the allowed time.
• Logistics/Warehouse: Track vehicles between an entry and an exit, and to track if the vehicle is inside a warehouse for more than the defined time.
• Car Service Center: Track vehicles taken out for a test drive and confirm if the vehicle is returned within a specific time window.

Hotlist Vehicle (lprRuleHotlist)

Hotlist Vehicle rules are configured to receive an alert for a specific plate, or for all plates in a vehicle list that has Vehicle Category (Security Status) marked as hotlist.

The configured rule can be mapped to a specific plate (RuleMapPlate) or to a specific vehicle list (RuleMapList).

Examples:

• A multifamily home/HOA: Receive an alert for a payment defaulter as they enter the premises to take action.
• Clubs/Retails/Hospitality: The hotlist can be configured for VIP customers to generate an alert upon their arrival so they can be greeted at the entrance.
• Rental Car/Parking/Dumping Yard: Generate alerts for vehicles that are missing or had been reported as stolen when they appear on the premises.

Number of License Plate Events (lprRuleCountAggr)

The Number of License Plate Events rule is used for monitoring the camera /LPR settings to help alert users in case of any concerns. The Number of License Plate Events rule is configured to be generate alerts if the number of events is greater or lesser than a defined count in a specified time range.

Example: A low number of events might be due to a misaligned or out of focus camera. This rule can generate alerts if the event count goes lower than expected.

Unknown Vehicle Alerts (lprRuleUnlisted)

If you want to receive alerts for vehicles that are not in your approved vehicle lists, you can use Unknown Vehicle Alert rules. This helps identify unauthorized or unknown vehicles entering your premises.

The configured rule can be mapped to a specific vehicle list (RuleMapList) to define which vehicles are considered "known" - any vehicle not in that list will trigger an alert.

Use Cases:

• Security Monitoring: Get alerted when unregistered vehicles enter restricted areas
• Visitor Management: Identify visitors who haven't checked in or registered their vehicles
• Compliance Monitoring: Ensure only authorized vehicles access certain zones
• Suspicious Activity Detection: Monitor for potentially unauthorized vehicle activity

Examples:

• Corporate Campus: Alert security when non-employee vehicles enter the parking garage
• Residential Complex: Notify management of vehicles not belonging to residents or registered guests
• Restricted Facilities: Generate immediate alerts for any vehicle not on the approved access list

VSP Vehicle List /lprVehicleLists

Vehicle List is a group of plates grouped together under a single name for easy management. The vehicle list has an access category and access control schedule for LPR-based access control automation which is integrated with Eagle Eye LPR (with Local ID).

The Vehicle List can be integrated with an external database for its automatic update and management.

The Vehicle List allows users to group vehicles under a list and map to specific cameras and locations.

Vehicle List Parameters

For each vehicle the following information is provided:

Vehicle List Integration

Access Control Automation

Vehicle Lists integrate with Eagle Eye LPR (Local ID) to provide automated access control functionality. The system can automatically grant or deny access based on the vehicle's access type and current schedule settings.

External Database Integration

The Vehicle List system supports integration with external databases for automatic updates and management. This allows for:

• Real-time synchronization of vehicle permissions
• Automated addition and removal of vehicles
• Bulk updates from HR systems or property management platforms
• Integration with third-party access control systems

Camera and Location Mapping

Vehicle Lists can be mapped to specific cameras and locations, allowing for:

• Site-specific access control
• Granular permission management across multiple facilities
• Location-based rule enforcement
• Centralized management with distributed enforcement

Alert Configuration and Management

Alert Manager Integration

After the alert is generated, it is sent to the alert manager service, and the action is performed as it was configured for the rule. Through alert manager integration, VSP supports different alert actions:

Notification Types

• Web Application notifications: Real-time alerts displayed in the VSP interface
• Email Alerts: Customizable email notifications sent to designated recipients
• Slack Integration: Team messaging integration for incident notifications
• I/O Triggers: Physical device activation such as gate controls, barrier systems, or alarm systems

Alert Action Configuration

Each rule can be configured with multiple alert actions to ensure appropriate response based on the rule type and severity:

1. Immediate Actions: Real-time notifications for critical events
2. Escalation Procedures: Progressive alert escalation for unresolved incidents
3. Batch Processing: Scheduled summary reports for non-critical events
4. Integration Actions: API callbacks to external systems for automated responses

Rule Management Best Practices

Performance Optimization

• Camera Targeting: Configure rules for specific cameras to reduce processing overhead
• Confidence Thresholds: Set appropriate plate recognition confidence levels to minimize false positives
• Time Window Optimization: Use appropriate time ranges for Watch Vehicle rules to balance security with system performance

Vehicle List Maintenance

• Regular Cleanup: Implement scheduled removal of expired vehicle entries
• Data Consistency: Maintain standardized user data formats for effective searching
• List Organization: Use meaningful naming conventions and hierarchical structure for vehicle lists

Alert Volume Management

• Notification Channels: Configure appropriate alert methods for different rule types and priorities
• Escalation Procedures: Define clear escalation paths for critical alerts
• Alert Fatigue Prevention: Monitor alert volumes and adjust thresholds to prevent notification overload

Rule Validation and Testing

• Test Environment: Validate rule configuration in non-production environments before deployment
• Performance Monitoring: Regular review of rule effectiveness and false positive rates
• Documentation: Maintain detailed documentation of rule purposes and expected behaviors