Schindler Lift Interface

Overview

This guide explains how to configure the Schindler Lift Interface on the Integriti system. This high-level (HL) integration provides user management, floor control, lift calls, and live event reporting between Integriti and the Schindler HLI (High-Level Interface).

The Schindler integration uses three TCP/IP connections to the SchindlerID server:

• DB Interface (TCP 4040) — Communications Handler for Schindler user synchronization.
• Live Reporting (TCP 6060) — Communications Handler for receiving live lift events into Integriti review.
• PORT Interface (TCP 5050) — Communications Task for lift allocations, Free/Secure, and Call By Profile.

This integration has been tested against SchindlerID v1.2.357.1 through v1.3.367.1.

Important: User records should not be created in the Schindler lift system. All user management must be done through Integriti after the Communications Handler has been configured and communications are established.

Supported Card Data Types

• PACS data — secure physical access control system data (Wiegand data). Recommended.
• CSN — the serial number of a credential (not recommended).
• Other — mixed or non-standard data available via custom enhancement.

All options allow for a maximum of 3 credentials per user. Since v19, Integriti supports sending up to 3 different card technologies using the Schindler Card Codec custom enhancement.

Prerequisites

• Integriti System Designer with installer-level access.
• Schindler Port Lookup table (IP addresses and port information from the 3rd party).
• License 996933 — Elevator Management Integration (Lift HLI) for user sync and live floor reporting.
• License 996023 — Elevator Management System HLI (Lift EMS) Smart Card license on the Security Controller nominated for the Schindler interface (for Free/Secure, Call By Profile, Direct Call, Call By ID).
• Schindler Card Codec custom enhancement imported (see Step 1).
• SchindlerID server IP addresses and port information (typically TCP 4040, 5050, 6060).

Step-by-Step

1. Import the Schindler Card Codec

1. In Integriti, click File > Import.
2. Browse to C:\Program Files\Inner Range\Integriti Pro\Resources\Helpers.
3. Select Schindler Card Codec.irentities and click Open.
4. In the Import Entities from XML window, click Import.
5. Click Close once the import finishes.

The Card Codec should only be programmed by Inner Range. Contact Inner Range Technical Support if other card technologies are purchased for Schindler Terminals.

2. Create the Schindler Communications Handler

6. In Integriti System Designer, open the Communications panel from the Design tab.
7. Click the Add New button to create a new communications handler.
8. Give the handler a name (e.g., “Schindler HLI”) and add any necessary notes.
9. Choose a Handler Type of Schindler Integration.

3. Configure User Synchronization Settings

10. Expand Schindler User Synchronization Settings.
11. Set Enabled to enable user synchronization between Integriti and Schindler.
12. Enter the Port number (typically 4040 for the database interface).
13. Leave the Time-based settings as-is (Connection Timeout, Message Time Frame, Reconnection Pace Time).
14. Set Reconnection Limit Count to -1 (never stop trying to reconnect).
15. Set Heartbeat Period to 160000ms (default).
16. Leave the Person ID Prefix as-is.
17. Leave Visualize Empty Names checked (substitutes blank last names with ’.’ for easier Schindler searching).
18. Choose a User ID Mapping Scheme:
    • Legacy — {Prefix}{UserNumber} (assuming global users).
    • With Partition — {Prefix}{Partition}.{Number}.
19. Select the Mode for user synchronization.
20. Leave Inverted Data Bits Arrangement unchecked unless advised.
21. Set Schindler Version to v1.3+.

4. Configure Custom Fields

22. Expand Schindler Custom Fields Settings.
23. For each custom field, select an existing field or click New to create one. The integration pre-populates the Name, Field Type, Item Type, and Category Name. Click Save to accept.

Custom Field	Item Type	Field Type	Required?	Purpose
Is Schindler User	User	Editable Drop Down Box / Check Box	Yes	Marks a user as a Schindler lift user.
Profile Name	User	Text	Yes	CASE SENSITIVE — must match the Schindler profile name exactly.
Badge #1 Field	User	Text	Yes	18-character formatted card data for Schindler (e.g., 1fff8ec400f9ff12e0).
Badge #2 Field	User	Text	No	Second credential (18-character string).
Badge #3 Field	User	Text	No	Third credential (18-character string).
Schindler User Destination Floor	User	Entity Link (Lift Floor)	Recommended	Used by review logging and auto-destination.
Schindler Floor ID	Lift Floor	Text	Recommended	Schindler floor identifier for live reporting and auto-destination.
Schindler Zone ID	Lift Floor	Text	Recommended	Schindler zone identifier for auto-destination.
User Email Address	User	Text	No	User email synced to Schindler.
Hide User Names	User	Check Box	No	Hides user names from Schindler DB.
Company	User	Text	No	User’s company.
Enterprise	User	Text	No	User’s enterprise.
Department	User	Text	No	User’s department.

If Schindler Floor ID and Destination Floor custom fields are not configured, review data will report numbers instead of floor names, and the Auto-Destination feature will not work.

5. Configure Live Reporting (Logger)

24. Expand Schindler Logger Connection Settings.
25. Check the Enabled option to enable Schindler live reporting.
26. Set Port to 6060 (default; change if different).
27. Set Heartbeat Timeout (sec) to 120.
28. Leave other Time-based settings as-is.
29. Leave Disable User State Change on Allocation and Disable User State Change on Access unticked (Integriti updates user states on successful events by default).
30. Leave User ID XML Attribute Name blank unless advised by Inner Range Technical Support.

6. Configure Host Connection

31. Expand Configuration.
32. Enter the Host Name (IP address or host name of the SchindlerID server).
33. Optionally enable Debug Logging for troubleshooting (recommended for debug only).
34. Set Auto-Destination Boarding Floor if desired — when a user presents their card at this floor’s terminal, they are taken to their default (home) floor instead of using their Schindler Profile.

7. Create Lift Floors

35. Open the Lifts tab, then click the Lift Floors entity list.
36. Click Add New to create a Lift Floor.
37. Give the Lift Floor a name matching the physical floor.
38. Expand the Schindler section.
39. Enter the matching Schindler Floor ID from the Schindler Port Lookup table.
40. Enter the Schindler Zone ID if using auto-destination.
41. Set the Software HLI Handler to the Schindler Communications Handler.
42. Save and close.
43. Repeat steps 36–42 for all remaining floors.

8. Configure User Settings

44. Once the Communications Handler, Lift Floors, and Lift Cars are configured, open each Schindler user.
45. Set the following custom fields for each user:
    • Is Schindler User — check/enable.
    • Profile Name — enter the exact Schindler profile name (CASE SENSITIVE).
    • Badge #1 Field — 18-character formatted card data.
    • Badge #2 / #3 Fields — optional additional credentials.
    • Schindler User Destination Floor — select the user’s home floor.

9. Configure the EMS Communications Task (Free/Secure and Call By Profile)

46. Open the Communications panel from the Design tab.
47. Click Add New to create a new Communications Task.
48. Change the EMS Protocol to Schindler PORT.
49. Leave the User Prefix as-is.
50. Enter the IP address of the SchindlerID server configured for the PORT interface.
51. Enter the TCP port number 5050.
52. Save and close.

10. Configure EMS Lift Cars for Free/Secure

53. Navigate to the Lifts tab.
54. Click Add New to create a Lift Car entity.
55. Name the Lift Car after the physical floor (e.g., “Lobby”, “Level 1”).
56. Under Lift Configuration:
    • Lift Mode: High Level / EMS.
    • Lift Type: Entry Door.
    • Lift Floors: select only the corresponding Lift Floor entity.
57. Under High Level:
    • EMS Type: Car Panel.
    • Lift Group: select the Lift Group containing all floors.
    • EMS Lift ID: the Terminal ID from the Schindler Port Lookup table.
    • EMS Floor Number: set to the corresponding Lift Floor entity.
58. Save and close.
59. Use Named Actions (Secure/Free) on the Lift Car entity to control access to Schindler floors.

11. Configure Call By Profile (Optional)

60. Create a Lift Floor List entity.
61. Name the Lift Floor List to match the Schindler Profile name exactly.
62. Optionally add floor(s) to the Floor List.
63. Create or modify a Permission Group and add the Lift Floor List.
64. Assign the Permission Group to the user(s) as the Primary Permission Group.
65. Create a Lift Car entity for the Call By Profile terminal:
    • Lift Mode: High Level / EMS.
    • Lift Type: Entry Door.
    • Lift Floors: all accessible floors.
66. Under High Level:
    • EMS Type: Destination Panel.
    • Lift Group: the Lift Group containing all floors.
    • EMS Lift ID: the Terminal ID from the Schindler Port Lookup table.
67. When a valid credential is presented at the reader, the name of the Lift Floor List in the user’s Primary Permission Group is sent to Schindler as the Call By Profile.

Verification

• After saving the Communications Handler, check its status for a successful connection to the SchindlerID server.
• In Integriti review, verify Schindler events appear: Allocation events, Access Successful/Access Failed events, Car Availability events, and User Sync events.
• Present a test user’s credential at a Schindler terminal — an Allocation or Access event should appear in Integriti review with the user’s name and floor transition.
• Test Free/Secure Named Actions on a Lift Car — verify floors are released and secured.
• For Call By Profile, present a credential at the configured reader and verify the correct Schindler Profile is sent.
• Verify user synchronization: check the Integriti logs for “Successfully updated Schindler user” messages.

Troubleshooting

Problem	Resolution
Communications Handler not connecting	Verify the Host Name (IP address) is correct. Check network connectivity between the Integriti server and SchindlerID server on TCP ports 4040, 5050, and 6060.
Users not syncing to Schindler	Verify Schindler User Synchronization Settings are enabled. Ensure users have the Is Schindler User field checked and a valid Profile Name set (CASE SENSITIVE — must match Schindler profile exactly).
Review shows numbers instead of floor names	The Schindler Floor ID custom field is not configured on Lift Floors, or the Schindler User Destination Floor custom field is not set on users. Populate both fields with values matching the Schindler Port Lookup table.
Auto-Destination not working	Ensure the Auto-Destination Boarding Floor is set in the Communications Handler Configuration. Verify Schindler User Destination Floor and Schindler Zone ID custom fields are populated.
Card data not recognized by Schindler	Verify Badge #1 Field contains exactly 18 characters. Ensure the Schindler Card Codec has been imported. Check that Inverted Data Bits Arrangement is set correctly (consult Inner Range Technical Support).
Call By Profile not working	Ensure the Lift Floor List name matches the Schindler Profile name exactly. Verify the Permission Group with the Floor List is assigned as the user’s Primary Permission Group.
Free/Secure not responding	Verify the EMS Communications Task is configured with Schindler PORT protocol, correct IP address, and TCP port 5050. Check that the Lift Car EMS Type is set to Car Panel.
CSN cards not working	CSN is not recommended for Schindler. Ensure the user’s Card has the CSN property populated with hexadecimal data. PACS data (Wiegand) is the preferred method.

Related Pages

• UniBus 16 Floor Lift Interface
• IAC Overview
• ISC
• Integriti System Configuration
• Integriti Communication Handlers
• Integriti Comms Tasks Automation