Glossary and key concepts

Contents

1. General
    1.1 User / Profile
    1.2 Organisation (Owner vs. Tenant)
    1.3 Lease agreement
    1.4 Portail visiteurs
    1.5 Visitor

2. Configuration du parking
    2.1 Parking lot
    2.2 Spot
    2.3 Group (of spots)
    2.4 Timetable
    2.5 Community

3. Access control
    3.1 Access strategy
    3.2 Access policy
    3.3 Access right
    3.4 Access methods
    3.5 Grace period
    3.6 Access Sequence Enforcement (ASE)
    3.7 No re‑entry

4. Dashboard tabs
    4.1 Parking Management Console & Organisation Management Console
    4.2 Control Room
    4.3 Access Log
    4.4 Reservations List
   
   

 

The glossary is divided into the following categories:

1. General: Generic Izix terms.

2. Parking setup: Terms related to the parking facility to better represent the physical reality of the car park in the Izix system.

3. Access control: The selective restriction of access to a car park according to predefined conditions, including terms related to managing and supervising the flow of people and vehicles.

4. Dashboard tabs: The Izix interface includes different types of information; this section gives an overview of the main tabs and their purpose

1. General

User / Profile

• • A user’s membership as part of an organisation. A user can have several profiles, one per organisation; each profile has its own roles and attributes, such as phone numbers, email addresses and vehicles.

  • Depending on the role, the user has limited permissions to access Izix and configure the account.

  • The parking administrator has full access to the Izix interface and can manage all profiles and access rights.

Organisation (Owner vs. Tenant)

• • A legal entity (company, association) that owns, uses or operates a car park in the Izix system.

  • An organisation that owns a car park is called the owner.

    • An owner who rents out their car park becomes the landlord.

  • An organisation that uses a car park owned by another organisation is called the tenant.

Lease agreement

• • A lease agreement is a contract between two organisations, in which one organisation (the landlord) delegates the usage rights of its spots (or a subset of them) to another organisation (the tenant).

  • Once an organisation has rights over a spot, it can sublet it again; in this way, usage rights can be transferred (subletting), which means the landlord is not always the owner of the car park.

Visitor portal

• • The visitor portal is a parking reservation website (URL) intended for visitors of the organisation and tailored to its needs. The customised portal offers visitors a modern and smooth registration process.

Visitor

• • A visitor is a user with temporary access to the car park; they must be invited by the organisation.

  • Visitors do not have access to the Izix app, but they can be granted access via any available method, including the remote control represented as a URL

2. Parking setup

Parking lot

• • A single place within a car park where a vehicle (car, motorbike, bike, etc.) can park; it cannot be subdivided further.

Spot

• • A single place within a car park where a vehicle (car, motorbike, bike, etc.) can park; it cannot be subdivided further.

Group (of spots)

• • A group is a virtual subdivision of spots belonging to the same organisation / tenant within a car park; being virtual, it does not correspond to a physical separation.

  • The organisation / tenant uses a group to limit the use of its spots when certain conditions are met (for example, spots with chargers reserved for electric vehicles).

Timetable

• • A schedule representing the availability of the car park, the lease agreement or the access policy. By default, a timetable is 24/7, but it is fully configurable.

Community

• • A community is a group of organisations that share access rights to a certain number of spots.

  • Through a community, capacity usage is optimised and unused capacity is shared with other organisations

3. Access control

Access strategy

• • An access strategy is a specific type of planning that allows the user to legitimately access the car park.

  • Users can only use strategies allowed by their organisation (for example, selected staff with a guaranteed spot vs. employees who book manually).

  • Depending on the chosen strategy, the impact on parking occupancy and on the ability to enter changes; the aim is to regulate access according to each user’s needs.

Access policy

• • An access policy is the combination of an access strategy with a specific timetable, possible costs and a group.

  • The policy is assigned to a profile or a vehicle, which becomes the beneficiary; each policy can have a different strategy (FCFS, booking, preferential, etc.).

Access right

• • A configured access policy can be assigned to a user, thus becoming an access right.

  • A user without access rights cannot enter the car park.

Access methods

Method used to identify the user at the barrier and grant (or deny) them access to the car park. Izix offers three main methods: ANPR, app and code (+ URL for visitors).

• • ANPR – Automatic Number Plate Recognition: Method based on a camera that recognises the licence plate and automatically opens the barrier; it requires the licence plate to be registered in the profile.

  • App (remote control): Authenticated users have an “open barrier” button in the mobile app.

  • Code (keypad): Input device that allows access via a personal code.

  • URL: Only for visitors; they open the barrier via a URL received by email.

Grace period

• • Additional time before or after a planned entry / exit during which the user can access or leave the car park.

  • The grace period is unique to each organisation and applies to all its access strategies except visitor bookings.

  • It applies to ANPR accesses but not to openings via remote control from the app.

Access Sequence Enforcement (ASE)

• • ASE checks that a user cannot reopen a barrier in the same direction after having passed through it.

  • The barrier will not open via any method (app, ANPR, code) if the last recorded opening was already in that direction.

  • This option is not enabled by default; it can be enabled from the back end. Contact your Account Manager for more information.

No re‑entry

• • Automatic closing of the reservation when the user leaves the car park.

4. Dashboard tabs

Parking Management Console & Organisation Management Console

• • The Parking Management Console is used to monitor the flow of people and vehicles on a daily basis and to perform actions that allow access.

  • The Organisation Management Console is used to configure parking‑specific settings or to modify the organisation‑wide configuration.

Control Room

• • Real‑time list of car park accesses, with additional controls so that a security guard can grant manual access.

Access Log

• • Contains the barrier opening records from the last 4 months together with explanations of the reasons for access or denial.

Reservations List

• • Shows all planned reservations (preferential, user bookings, visits) and completed FCFS sessions from the last 4 months.

  • Reflects the theoretical planning and thus the allocation of spots; bookings for users and visits can be created directly from this list.