INTERVALLMONATE - Detailed description

Overview

Parameter:INTERVALLMONATE
Category: ParkingSpaceManagement
Default value: 2
Product: eTASK.ParkingSpaceManagement

What does this parameter do?

Determines the time intervals (in months) at which employees with active parking authorization are automatically prompted to review their registered license plate numbers and update them if necessary. This regular review ensures that the license plate numbers stored in the system are always up to date and can be used correctly during parking lot inspections.

What is this parameter used for?

• Automatic license plate validation at defined intervals

• Ensuring up-to-date vehicle data for active parking authorizations

• Prevention of incorrect license plates during parking lot inspections

• Workflow-driven reminders to employees to update their data

• Quality assurance in the parking management process

• Compliance with internal parking policies

• Reduction of manual follow-ups through automated verification cycles

Technical Details (for Administrators)

Format: Integer as a string
Default value: 2

Valid values:

• 1 to 12 = Number of months between automatic attribute checks

• Recommended range: 2 to 6 months

Important notes:

• The workflow automatically jumps to an intermediate step for license plate verification

• Applies only to parking authorizations with the status "Parking authorization active"

• Employees must confirm or update the license plate

• The cycle restarts with every new or updated parking authorization

• Intervals that are too short can lead to frequent interruptions

• Intervals that are too long increase the risk of outdated data

• This parameter works in conjunction with the parking management workflow

Interaction with other parameters:

• INTERVAL_DAYS: Defines the number of days after which the workflow automatically returns to the "Parking Permit Active" status if there is no response

When should you change this value?

Leave the value at 2 (default) if:

• Vehicle changes occur relatively frequently

• There are high requirements for data timeliness

• Parking lot inspections are conducted regularly

• Security-related reasons require current license plate numbers

• The default configuration is sufficient for most organizations

Increase the value to 3–6 if:

• Vehicle changes are rare

• Employees should be bothered less frequently

• Administrative burden needs to be reduced

• Stable, long-term vehicle use is common

• Quarterly or semi-annual inspections are sufficient

Set value to 12 (annual inspection) if:

• Minimal workflow disruption is desired

• Vehicle usage is very stable

• Annual compliance checks are sufficient

• There is low monitoring frequency for parking spaces

Important Notes

1. Automatic workflow activation
   The workflow automatically transitions to an intermediate step once the interval has expired. Employees receive a prompt to check the license plate and must actively respond.

2. No retroactive application
   The change to the parameter only affects new intervals. Cycles already in progress are not recalculated or adjusted.

3. Combination with INTERVALLTAGE
   After receiving the prompt, employees have a certain number of days to respond (defined by INTERVALLTAGE). If there is no response, the system automatically resets the parking authorization to "active."

4. Impact on user experience
   Too frequent checks can be perceived as disruptive. Find a balance between data quality and user experience.

5. Multiple flags allowed
   Employees can store up to 5 flags. All must be confirmed or updated during each check.

6. Workflow status dependency
   The parameter is only effective if the parking authorization has the status "Parking authorization active." No automatic check occurs for other status values.

Security

Does changing this parameter affect security?

No, changing this parameter has no impact on security.

Practical example

Initial situation: A company with 500 employees operates a parking management system with 300 parking spaces. The parking spaces are in high demand and are allocated via workflow. Illegal parking occurs regularly because employees do not update their license plate numbers when they change vehicles. The security team reports that, during inspections, unregistered vehicles are frequently found in assigned spaces.

Configuration: INTERVALLMONATE was set to 12. The administrator changes the value to 3 months.

After the change:

• Every 3 months, employees are automatically prompted to verify their license plate

• The workflow displays a clear prompt in the portal

• Employees confirm their license plates or enter new ones

• Incidents of illegal parking are reduced by 75%

• The security team has up-to-date data for parking lot inspections

• Higher satisfaction among employees with assigned parking spaces

Result: Significantly improved data quality without unduly inconveniencing employees. Quarterly checks are frequent enough to ensure up-to-date data, but infrequent enough not to be perceived as disruptive.

Alternative scenarios:

Scenario A - Company car pool:

• INTERVAL MONTHS set to 1

• Company cars are rotated among employees on a monthly basis

• License plates change frequently

• Monthly check ensures that current assignments are up to date

Scenario B - Long-term parking permits:

• INTERVAL MONTHS set to 6

• Stable workforce with personal vehicles

• Very low turnover rate for license plates

• Semi-annual checks are sufficient, reducing administrative burden

Recommended setting

For standard installations:2(months)

Reason:

• Strikes a balance between data freshness and user-friendliness

• Captures typical vehicle changes in a timely manner

• Does not disrupt the daily workflow too frequently

• Complies with best practices in parking management

• Enables timely updates in case of changes

Recommendations by environment:

• Standard office environment: 2-3 (quarterly for a good balance)

• Stable long-term use: 4-6 (semi-annually for minor changes)

• Minimal administrative effort: 12 (annually, only under very stable conditions)

Important: Consider the frequency of vehicle changes in your organization. For leased vehicles with a 2–3-year term, an interval of 2–3 months is optimal. For personal vehicles, longer intervals may be sufficient.

Tip: Monitor the response rate for license plate checks during the first few months. If many employees do not make any changes, the interval can be extended. If changes are frequent, it should be shortened. Combine this parameter with clear communication about the importance of up-to-date license plate data.