Skip to main content

Elevator Integration

The integration of ACCELERO with elevator systems enables the advance call of elevators and the triggering of button panels to release specific floors, providing a smooth and secure experience for users.

Licensing Requirement

This feature requires the elevator integration module enabled in the license. See Licensing.

Overview​

The elevator integration offers two main features:

FeatureDescriptionWhen to Use
Advance CallThe system calls the elevator automatically after authorized access and tells the user which elevator to useBuildings with multiple elevators and centralized control
Button Panel ReleaseThe system releases specific buttons on the elevator panel, allowing the user to access only authorized floorsIndividual elevators or systems without advance call
Transparent Operation

The entire process happens transparently for the user - simply present the identifier at the barrier and follow the instructions (if there is an advance call) or enter the elevator and press the floor button.

Architecture​

Required Components​

  1. Elevator system with an integration interface
  2. ACCELERO/Elevators Gateway (IONGRADE product)
  3. ACCELERO Server with the module enabled
  4. Communication network between the gateway and the systems
Specific Gateway

There are several gateway models, each developed for a specific elevator system model, including the Cobalt gateway.

Consult IONGRADE to identify the correct gateway for the elevator system installed in your building.

Network Topology​

Recommendation: The gateway should be on the same physical network as the elevator server (if there is one).

[Person] → [ACCELERO Controller] → [ACCELERO Server]
                                              ↓
                                        [Gateway]
                                              ↓
                                    [Elevator System]
                                              ↓
                                        [Elevators]

Fundamental Concepts​

Advance Call vs Button Panel Release​

Advance Call​

How it works:

  1. The person presents the identifier at the barrier
  2. The system authorizes access
  3. The system identifies the destination floor
  4. The system sends a command to the elevator system
  5. The elevator system indicates which elevator to use (on its own terminal)
  6. The person heads to the indicated elevator
  7. The elevator is waiting and goes directly to the floor

Characteristics:

  • More efficient in large buildings
  • Requires a compatible elevator system
  • Reduces waiting time
  • Improves flow during peak hours

Button Panel Release​

How it works:

  1. The person presents the identifier at the barrier
  2. The system authorizes access
  3. The person enters the elevator
  4. The system sends a command to release the buttons of authorized floors
  5. The person presses the button of the desired floor (among those released)
  6. The elevator takes them to the selected floor

Characteristics:

  • Works with any compatible elevator
  • The user has control over which floor to visit
  • Allows multiple floors per person
  • Simple and intuitive
Choosing the Mode

The choice between advance call and button panel release depends on:

  • Available infrastructure (installed elevator system)
  • Usage profile (flow of people, peak hours)
  • Cost-benefit of the implementation

Determining the Destination Floor​

The system automatically identifies the destination floor based on the type of person who is accessing:

For Visitors​

Destination floor: The "Floor" field of the company associated with the event/visit

Example:

Visitor: João Silva
Event: Visit to the company ABC Advocacia (Floor 12)
Result: Destination = Floor 12

For Non-Visitors (Employees, Residents, etc.)​

Destination floor: The "Default floor" field of the person's registration

Example:

Person: Maria Santos (Employee)
Default floor: 8
Result: Destination = Floor 8
Prior Configuration

For correct operation:

  • Companies must have the "Floor" field filled in correctly
  • Fixed people must have the "Default floor" field configured

See Companies and People.

Multiple Floors (Button Panel Release)​

For button panel release, it is possible to configure multiple floors separated by commas:

Examples:

Company: Multi-Floor Office
Floor: 5,6,7
Result: Buttons 5, 6, and 7 released
Person: João (Caretaker)
Default floor: 1,2,3,4,5,6,7,8,9,10
Result: All buttons released
Operational Flexibility

Multiple floors are useful for:

  • Companies that occupy several floors
  • Maintenance employees with broad access
  • Managers who move between departments

Configuration in ACCELERO​

Controllers/Channels​

Path: Settings > Controllers > [Select Controller] > Channels

For each channel (barrier) that should trigger elevators, configure:

FieldDescription
Enable elevator integrationEnables elevator integration (advance call) for accesses performed on this channel
Access delay for advance call (ms)Time in milliseconds of delay in releasing the barrier after authorization.
Allows the user to see/confirm information on the terminal before release.
Value 0 = no delay
GatewayCommunication gateway that should be triggered for advance call/button panel release
Origin floorPhysical floor where the barrier is located.
Important: Must be identical to the floor registered in the elevator system
Origin Floor

The "Origin floor" field is critical for advance call:

  • It must correspond exactly to the floor configured in the elevator system
  • If configured incorrectly, the elevator may not be called correctly
  • Example: if the barrier is on the ground floor and the system calls it "T", configure "T" (not "0")
Access Delay

Use of the delay:

  • 0ms: Immediate release (common use)
  • 2000-5000ms: Allows the user to confirm which elevator to use on the terminal before the turnstile releases

Useful in places where the user needs time to read information before passing through.

TODO: Add Screenshot

Include a screenshot of the channel configuration screen showing the elevator integration fields.

See Controllers for complete controller and channel configuration.

Companies​

Path: Settings > Companies > [Select Company]

FieldDescription
FloorPhysical floor of the company for elevator integration purposes.
For button panel release, it can contain multiple floors separated by commas (e.g., "5,6,7")
Consistency

Make sure the floor numbering used in ACCELERO is consistent with the elevator system's numbering:

  • If the elevator calls the ground floor "T", use "T"
  • If it uses "0", use "0"
  • If it uses "Basement", use "Basement"
TODO: Add Screenshot

Include a screenshot of the company registration screen showing the "Floor" field.

See Companies for complete configuration.

People​

Path: People > [Select Person] > General Data tab

FieldDescription
Default floorDefault floor of the person for elevator advance call purposes.
Used when the person is NOT a visitor.
For button panel release, it can contain multiple floors separated by commas
When It Is Used

The "Default floor" field is only used when the person accesses outside a visit context (event).

  • Employee entering to work → uses "Default floor"
  • Resident entering home → uses "Default floor"
  • Visitor with an active event → uses the "Floor" of the event's company
TODO: Add Screenshot

Include a screenshot of the person registration screen showing the "Default floor" field.

See People for complete configuration.

Operation Flow​

Advance Call​

Scenario: Employee arriving to work

  1. Presenting the identifier:

    • Maria presents her card at the reception reader (ground floor)

  2. Access authorization:

    • The system checks the access rules
    • Access authorized ✓

  3. Destination determination:

    • Maria is not a visitor → uses the "Default floor" from the registration
    • Default floor: 8

  4. Communication with the elevator system:

    • The gateway sends: origin=T, destination=8
    • The elevator system processes it

  5. Information to the user:

    • The elevator system terminal shows: "Elevator 3"
    • Maria heads to Elevator 3

  6. Barrier release:

    • If delay=0: immediate release
    • If delay>0: waits for the delay, then releases

  7. Elevator waiting:

    • Elevator 3 is already on the ground floor waiting
    • Maria enters
    • The elevator goes directly to floor 8

Button Panel Release​

Scenario: Visitor with a meeting on multiple floors

  1. Presenting the identifier:

    • João presents a QRCode at the reception reader

  2. Access authorization:

    • The system checks the access rules
    • Access authorized ✓

  3. Destination determination:

    • João is a visitor with an event for company XYZ
    • Company XYZ - Floor: 5,6,7

  4. Barrier release:

    • The turnstile releases

  5. João enters the elevator:

    • Elevator without a prior command

  6. Communication with the elevator system:

    • The gateway sends a command: release buttons 5, 6, 7

  7. João selects the floor:

    • Buttons 5, 6, and 7 are released
    • Other buttons blocked
    • João presses button 5
    • The elevator goes to floor 5
Multiple Visits

If João needs to go to floors 6 and 7 later, he can use the elevator again and the buttons will be released throughout the entire event period.

Common Use Cases​

Corporate Building with Multiple Companies​

Challenge: Visitors should go only to the floor of the company they are visiting.

Solution:

  • Configure "Floor" in each company's registration
  • Use advance call to direct visitors
  • Employees with "Default floor" configured

Result:

  • Visitor of company X → the elevator takes them only to the floor of X
  • Visitor of company Y → the elevator takes them only to the floor of Y
  • Employee → goes to their work floor

Residential Condominium​

Challenge: Each resident should access only their floor. Visitors only the floor of the visited resident.

Solution:

  • Residents with "Default floor" = their apartment
  • Visitors: event linked to the "company" (unit) with the floor configured
  • Button panel release (since a resident may have visited someone and need to return)

Result:

  • Resident 501: accesses only floor 5
  • Visitor of 801: accesses only floor 8
  • Security/caretaker with multiple floors

Multi-Floor Company​

Challenge: The company occupies floors 10, 11, and 12. Employees need to move between all of them.

Solution:

  • Employees with "Default floor" = "10,11,12"
  • Button panel release mode

Result:

  • The employee can access any of the three floors
  • Visitors from other companies cannot

Delivery Person/Service Contractor​

Challenge: The delivery person needs to access the service elevator hall, not the social one.

Solution:

  • DELIVERY category with an access policy for a specific area
  • Configure the controller/channel of the service area with elevator integration
  • Create an event for the delivery with the destination company/floor

Result:

  • The delivery person accesses the service barrier
  • The system calls the service elevator
  • Takes them to the correct floor
  • Has no access to the social elevators

Best Practices​

Planning​

  1. Define the network topology:

    • Gateway on the same network as the elevator system
    • Priority traffic if necessary
    • Network redundancy if critical

  2. Choose the operation mode:

    • Advance call for large buildings
    • Button panel release for flexibility
    • Consider the building's usage profile

  3. Standardize the floor numbering:

    • Consistency between ACCELERO and the elevator system
    • Document the adopted convention (T, 0, Basement, etc.)

  4. Configure floors before releasing the system:

    • All companies with "Floor" filled in
    • Employees with "Default floor" configured
    • Test before operation

Operation​

  1. Train users:

    • Explain how the advance call works
    • Guide them on which elevator to use
    • Instruct them on button panel release

  2. Monitor special events:

    • Events with many simultaneous visitors
    • Configure appropriate access policies
    • Consider the entry/exit flow

  3. Register visitors correctly:

    • Always associate the event with the correct company/unit
    • Verify that the company has a floor configured
    • Confirm the validity period

  4. Use the appropriate delay:

    • 0ms for fast flow
    • 2-5s if the user needs to read information

Maintenance​

  1. Check communication:

    • Gateway ↔ ACCELERO
    • Gateway ↔ Elevator system
    • Test calls periodically

  2. Update registrations:

    • When a company changes floors
    • When an employee changes department/floor
    • When there are changes in the building

  3. Configuration backup:

    • Elevator gateway
    • Elevator system settings
    • Floor mapping

  4. Have a contingency plan:

    • What to do if the integration fails?
    • Manual access to the elevators?
    • Emergency procedures

Troubleshooting​

Elevator is not called​

Possible causes:

  • Gateway without communication
  • Incorrect origin floor
  • Destination floor not configured
  • The elevator system does not recognize the command

Solution:

  1. Check the gateway communication
  2. Confirm the channel's "Origin floor"
  3. Check the "Default floor" or the company's "Floor"
  4. Consult the elevator system logs
  5. Test the command manually

Elevator called to the wrong floor​

Possible cause:

  • Incorrect floor configuration

Solution:

  1. Check that the channel's "Origin floor" is correct
  2. Check that the "Destination floor" (default or company) is correct
  3. Confirm the floor numbering in the elevator system
  4. Correct inconsistencies

Buttons are not released (button panel)​

Possible causes:

  • Gateway without communication
  • Command not sent
  • The elevator system did not receive it

Solution:

  1. Check the gateway communication
  2. Confirm that the channel has a gateway configured
  3. Check the communication logs
  4. Test the command manually

Multiple floors do not work​

Possible cause:

  • Incorrect format (commas, spaces)

Solution:

  1. Use only commas without spaces: "5,6,7" ✓
  2. Do not use: "5, 6, 7" ✗
  3. Do not use: "5;6;7" ✗
  4. Re-save the registration after correction

Visitor cannot access​

Possible causes:

  • The event's company without a floor configured
  • The event is not active

Solution:

  1. Check that the event is active
  2. Confirm that the company associated with the event has "Floor" filled in
  3. Test access outside the elevator context first

Integration with Other Modules​

Events​

Relationship: Visitors use the "Floor" of the event's company

Important:

  • Always associate the event with the correct company
  • The company must have a floor configured
  • See Events

Companies​

Relationship: The "Floor" field defines the destination for visitors

Important:

  • Keep floors updated
  • Use commas for multiple floors
  • See Companies

People​

Relationship: The "Default floor" field defines the destination for non-visitors

Important:

  • Configure it for all employees/residents
  • Update it when there are changes
  • See People

Areas and Controllers​

Relationship: Controllers/channels execute the calls

Important:

  • Configure the correct gateway per channel
  • The origin floor must be correct
  • See Controllers

Next Steps​