In this article
Quick Feature Overview
The framework supports both:
- Digital Access IDs → Admission numbers that can be for example, in form of barcodes or QR codes (sent by email or printed).
- Physical Devices → bracelets, cards, or similar devices issued at check-in.
With this, you can scan, assign, erase, and search for access rights directly from the POS and the Activity Host.
POS Commands
Four POS commands are available for this feature available:
-
ACT_ACCESS_SCAN – Scan a digital ticket or device which will perform different behaviors depending if this was triggered on the activity host or on the POS:
- POS: Add the related booking entity to the current transaction.
- Activity Host: Open the related booking entity to view its details.
- ACT_DEVICE_ASSIGN – Assign a booking entity to a physical device.
- ACT_DEVICE_ERASE – Deactivate and clear a physical device from the booking entity.
- ACT_ACCESS_SEARCH – View all details stored on a ticket or device, including access rights.
POS Parameters
- Activity
- Reservation
- Member
- Membership
Notes:
The preceding POS Parameters are valid for the POS Commands SCAN, ASSIGN and ERASE.
This is where you specify the booking entity the POS Command is referring to.
There are plenty of events available to extend or modify this functionality through code. It is possible for example to link entities to a new entity - creating a new POS Parameter.
Activity Device Logs Table
All of the devices that were assigned to a booking entity are listed and kept in this table for traceability and historical purposes.
The table below lists and describes the fields on the Activity Device Logs:
| Field | Description |
|---|---|
| ID | This field states the value of the device identification code. |
| Link Code | This field states the code of the booking entity that was linked to this device. |
| Link Type | This field states the type of booking entity which is linked to this device. |
| Active | This field specifies whether the device is or is not currently in use and assigned to the booking entity defined in the preceding fields. |
How it Works
The AIDC framework manages both digital access IDs (tickets, barcodes, QR codes) and physical devices (bracelets, cards) in a unified way. The work flow typically follows these steps:
-
Scanning
- A customer presents their admission ticket or a device.
- Scanning either opens the linked booking entity (Activity Host) or adds it to the current transaction (POS).
-
Assigning a Device
- At check-in, you can assign a physical device (example: a bracelet) to a reservation, activity, membership, or member.
- The device becomes active and is recorded in the Activity Device Logs for traceability.
-
Using the Device
- While active, the device works like a digital ticket: scanning it retrieves the linked booking entity and applies the action defined by the POS parameter.
-
Erasing a Device
- When the customer checks out or returns the device, it is erased.
- The logs are updated, and the device is marked inactive, ready for reuse.
-
Searching for Access
- At any point, you can search a ticket or device to see what it is linked to and whether it currently grants access.
- This ensures staff can quickly verify entry rights or troubleshoot issues.
Notes and Best Practices
- SCAN, ASSIGN, and ERASE require a POS parameter (Reservation, Activity, Member, Membership).
- ACCESS SEARCH does not require parameters.
- Always Erase devices before reassigning them.
- Use Access Search to confirm whether a ticket or device is valid before granting entry.
- Tickets and devices can be used interchangeably in the framework — the system treats both as access IDs.