TK Elevator
Controller for EOX Products
See Details
| Attribute | Description | MC5 | MAX | XPU | Intercoms | Frequency | Estimated volume | Storage location | Data retention |
|---|---|---|---|---|---|---|---|---|---|
| Capacity | The lift's capacity in kg. | YES | No information | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Car Call | When you are inside an elevator and press a button to go to a specific floor. | YES | NO | NO | When an elevator call happens | Based on system usage | Azure Cloud | indefinitly | |
| CarType | Defines whether the car is a single, double deck, or twin car. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| ContractSpeed | Operation mode / status. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| ControllerDescription | Helpful information describing what elevator this is. Is mainly for the technician and not for machine learning. | NO | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| ControllerNumber | A unique number for the elevator. For TAC, this will be the controller’s job number. This number might be the ERP ID for some elevators. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| ControllerType | This denotes the type of elevator connected. E.g. TAC20, TAC32, E.COR, etc. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| CurrentPosition | The current position in mm. The value is reported to the core (application) in specific bluebox API calls (e.g. after a trip is finished). | YES | NO | NO | When the elevator moves or by request (TCM) | Based on system usage | Azure Cloud | indefinitly | |
| Destination Calls | When you walk up to a kiosk, select the floor you want to go to, and the kiosk tells you which elevator to ride. | YES | NO | NO | When an elevator call happens | Based on system usage | Azure Cloud | indefinitly | |
| Digital Position | The digital position of the elevator inside the shaft. | YES | NO | NO | When the elevator moves or by request (TCM) | Based on system usage | Azure Cloud | indefinitly | |
| Door Movement | A door movement describes the opening or closing of a car door with its starting point, end point, and motion cause. | YES | NO | NO | When the door moves | Based on system usage | Azure Cloud | indefinitly | |
| Elevator Floor | The different levels at which the elevator stops. They are numbered from 0 on the lowest floor of the elevator upwards. Note that floor 0 might not be at ground level. Also, note the difference between the floor label (usually 1, 2, 3.... starting at the ground floor) and the floor number. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| ElevatorType | The type of this elevator. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| EmergencyPower | Indicates whether the emergency power is on or off. | YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | |
| Error Codes | Error codes provided by the controller. | YES | NO | NO | When error occur | Based on system usage | Azure Cloud | indefinitly | |
| FirefighterMode | 1. Describes which phase of the figherfighter mode the elevator is in. The firefighter mode is either in - a. off, b. Phase1: transition from normal operation to fire/smoke/fire/heat has been detected (or the detection is set to true due to a test); passengers are transported to the main floor of egress, c. Phase 2: firefighters use a special key, so they can use the elevator to access the building floors, if the elevator is usable. |
YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | |
| FireSmoke | Indicates whether the elevator has detected a fire or smoke. Typically they come down to the lobby and park with open doors. Newer lifts can also perform an evacuation action in this mode and avoid the floors where fire has been detected and evacuate all other floors to the lobby. | YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | |
| GeneralShutdown | Indicates whether the elevator can be used or not. | YES | NO | NO | When there is a shutdown error | Based on system usage | Azure Cloud | indefinitly | |
| GroupName | The name of the group as perceived from the controller. This helps the cloud to perform some sanity checks on manual group configuration. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| Hall Call | When you walk up to the elevator and press the down button signifying that you want to go down. | YES | NO | NO | When a call happens | Based on system usage | Azure Cloud | indefinitly | |
| HallCallsInhibited | Indicates whether the elevator can answer hall calls or not (e.g. technician is working on the elevator, fire in the building → hall calls are disabled). | YES | NO | NO | When it's happening | Based on system usage | Azure Cloud | indefinitly | |
| HasResidentMechanic | True if this elevator has a resident mechanic. | YES | NO | NO | Masterdata - Could be provided by the user in GTA | Based on system usage | Azure Cloud | indefinitly | |
| IndependentOperation | Indicates whether this elevator operates as part of a group or independent. elevator is only answering car calls (not answering to any hall calls or destination calls). | YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | |
| Inspection | 1. Inspection describes a mode of operation, where someone (service person) is working on the elevator. Is set to true if someone is working on the elevator. 2. The inspection mode can be set manually from different locations for one elevator: a. machine room, b. in the car, c. on top of the car. |
YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | |
| Load | The lift's actual load in percent. Due to sensor misalignments or overload conditions, this value can easily exceed the expected range of 0-100 % in both directions. | YES | NO | NO | When the load is updated and the elevator is stopped | Based on system usage | Azure Cloud | indefinitly | |
| NumberOfCarsInGroup | The number of cars within the group the elevator is in, as perceived from the elevator, not the group controller. This number can help the cloud to perform sanity checks on the manual group configuration. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| NumberOfStops | Can be derived on cloud side based on the number of associated stops. | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | |
| Operation Modes | The operation mode is defined in the CPC. The CPC reports the operation mode as an integer value (can be different for all the different CPCs). THe cloud has a mapping table to decide which operation mode the elevator is in. | YES | NO | NO | When elevator updates is mode | Based on system usage | Azure Cloud | indefinitly | |
| OverloadThreshold | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | ||
| Recall | YES | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly | ||
| SoftwareVersion | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | ||
| TravelHeight | YES | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly | ||
| Trips | YES | NO | NO | When a trip happens | Based on system usage | Azure Cloud | indefinitly | ||
| Alarm Activation Signal | Must trigger a two-way voice communication with a remote assistance center. | NO | YES | Initiated by a passenger pressing the emergency button | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Lift Identification Data | Ensures the remote center knows which lift is calling. | NO | YES | When connecting to call center | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Intercom id | SIP id of intercom related to elevator. | NO | YES | Unique identifier for a intercom installed in an elevator | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Call Status Information | Duration of the call and whether it was terminated properly. | NO | YES | Confirmation that the call was successfully connected | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Voice and data as SIP/ RTP data | Voice and data stream to the IP. | NO | YES | During routine (every 72 hours) and active emergency call | 1x every 3 days and baed on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Battery Status | Alerts if battery is low or faulty (especially during test calls). | NO | NO | Real-time monitoring and reporting of battery health in case of not compliance | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Fault or Error Codes | If any part of the system fails (e.g., $G module, speaker, microphone), a fault signal must be sent to the monitoring center. | NO | YES | On failure detection | Based on system usage | Country specific call Center backend | Depends on country call center backend policy | ||
| Test Call Confirmation | Every 72 hours, a routine test call must be made using the same method as a real emergency call (e.g., GSM voice channel). The system must log and confirm that the test was successful. | NO | YES | Every 72 hours | 1x every 3 days | Azure Cloud & Call Center backend | "Azure Cloud: ""@Jens Call Center backend: depends on country call center backend policy" |
||
| Trapped passenger release | In case of rescue opperation, notification to the call center that the entrapment has been solved. | NO | YES | when initiated by service men onsite | Based on system usage | Azure Cloud | |||
| Heartbeat | The keep alive signal sent by the devices. | YES | YES | YES | 1x per hour | Azure Cloud | |||
| DES Alerts | Alerts coming from DES Devices to notify the cloud and country backend on specific conditions. | YES | YES | Based on specific scenarios of the devices | Azure Cloud | ||||
| IoT Hub Connection | Information whether the device is connected or not with IoT Hub (Azure). | YES | NO | NO | Depends on connections and disconnections w/ cloud | Azure Cloud | |||
| Transmission Mode | The transmission mode of MAX (batch, real-time, live). | YES | NO | NO | 2x a day | 2x/day | Azure Cloud | ||
| Remote Update and Remote Configuration Events* |
Aggregated category that includes all event notifications related to firmware updates, configuration downloads, installation outcomes, verification results, cancellations, and system reboots. | Event‑based | Event‑based | Azure Cloud | |||||
| * This category represents consolidated data — up to 26 individual categories — and detailed breakdowns can be provided upon request. | |||||||||
| DeviceConfigUpdated | When the device is running with a new Configuration File. | YES | YES | Based on configuration changes | Azure Cloud | ||||
| DeviceStart | When the device has just completed a device start up (from initial power up or reboot anytime after installation). | YES | YES | Based on device power cycle (not very often - updates, power failures, etc) | Azure Cloud | ||||
| Heartbeat | When the device is reporting its scheduled Heartbeat Alert (I'm Alive). | YES | YES | By default once per hour | Azure Cloud | ||||
| Status | "Id": 65536125 == Status. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536125, this means that EN81-28:2018 In-Cabin IP Intercom is reporting its current operational status. The EN81-28:2018 In-Cabin IP Intercom shall also set the value of the "Cid" field to the current operational status (the "Co" field shall remain set to "Device" as defined at the beginning of this subsection). The possible operational status values are as follows: | NO | YES | Azure Cloud | |||||
| ParameterMissing | "Id": 65536126 == ParameterMissing. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536126, this means that EN81-28:2018 In-Cabin IP Intercom has detected that an expected parameter is missing in the Configuration File. For this alert, the EN81-28:2018 In-Cabin IP Intercom shall set the "Cid" value to "${parameter_name}". For example, if the missing parameter name is "Remote_Update_Time", this alert will have the following values: | YES | On failure | Azure Cloud | |||||
| RemoteUpdateServiceFailure | "Id": 65536127 == RemoteUpdate ServiceFailure. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536127, this means that EN81-28:2018 In-Cabin IP Intercom failed to connect to the Remote Update Service or the query to the Remote Update Service failed. The triggering action for this event is found in the separate file: “REQ 071 - In-Cabin Intercom - Remote Update Activity Diagram.png”. For this alert, the EN81-28:2018 In-Cabin IP Intercom shall set the "Cid" value to the http response code (400 or 500 series response codes) or the return value from the Remote Update Service (“ERROR”, “BUSY”). For example, if the http response code is "404", this alert will have the following values: | YES | On failure | Azure Cloud | |||||
| RemoteConfigServiceFailure | "Id": 65536128 == RemoteConfig ServiceFailure. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536128, this means that EN81-28:2018 In-Cabin IP Intercom failed to connect to the Remote Update Service. For this alert, the EN81-28:2018 In-Cabin IP Intercom shall set the "Cid" value to the http response code (400 or 500 series response codes) or the return value from the Remote Config Service. For example, if the http response code is "404", this alert will have the following values: | YES | On failure | Azure Cloud | |||||
| SSLCheckFailure | "Id": 65536129 == SSLCheckFailure. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536129, this means that the EN81-28:2018 In-Cabin IP Intercom either failed to connect to the SSL Cert Check Service, or it failed to contact the provided Download URLs, or some later error was detected when parsing the downloaded files. For this alert, the EN81-28:2018 In-Cabin IP Intercom shall set the "Cid" value to the http response code (400 or 500 series response codes). For example, if the http response code is "404", this alert will have the following values: | YES | On failure | Azure Cloud | |||||
| SSLCertificateUpdated | "Id": 65536153 == SSLCertificateUpdated. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536153, this means that the EN81-28:2018 In-Cabin IP Intercom has successfully retrieved the check URIs from the SSL Certificate Service, downloaded the corresponding Certificate and Key Files, parsed and put the new SSL Certificate and Key into operation. | YES | When SSL cert is updated, ~once per year | Azure Cloud | |||||
| PhonebookUpdated | "Id": 65536156 == If the EN81-28:2018 MR/MRL IP Intercom successfully downloads and parses a new Phonebook File from the Phonebook Download Service, the EN81-28:2018 MR/MRL IP Intercom shall send an alert to the MAX Gateway with the "Id" value set to 65536156 (PhonebookUpdated). | YES | When phonebook is updated (e.g. when dialers are provisioned to the system) | Azure Cloud | |||||
| PhonebookCheckFailure | "Id": 65536157 == If the EN81-28:2018 MR/MRL IP Intercom attempts to contact the Phonebook Download Service and the connection fails, or parsing the downloaded file fails, the EN81-28:2018 MR/MRL IP Intercom shall send an alert to the MAX Gateway with the "Id" value set to 65536157 (PhonebookCheckFailure) and the "Cid" value to the HTTP response code. | YES | On failure | Azure Cloud | |||||
| YesButtonPermActive | "Id":65536160 == When the Yes button input is found to be continuously Active for more time than the value of the parameter "Chat_Button_Permanent_ Activation_Time", this shall be considered a permanent activation failure of the Yes button input and the XPU shall send an alert to the MAX Gateway with the "Id" value set to 65536160 (YesButtonPermActive). | YES | When the yes button gets stucked while pressed | Azure Cloud | |||||
| YesButtonPermActiveRecovery | "Id":65536161 == When a permanent activation failure of the Yes button input is detected, the failed state of the Yes button shall be persisted in non-volatile memory by the XPU until the Yes button input has returned to the Inactive condition, at which time the XPU shall "clear" the permanent activation failure state from non-volatile memory and send an alert to the MAX Gateway with the "Id" value set to 65536161 (YesButtonPerm ActiveRecovery). | YES | When the yes button recovers from the stuck situation | Azure Cloud | |||||
| NoButtonPermActive | "Id":65536162 == When the No button input is found to be continuously Active for more time than the value of the parameter "Chat_Button_Permanent_ Activation_Time", this shall be considered a permanent activation failure of the No button input and the XPU shall send an alert to the MAX Gateway with the "Id" value set to 65536162 (NoButtonPermActive). | YES | When the no button gets stucked while pressed | Azure Cloud | |||||
| NoButtonPermActiveRecovery | "Id":65536163 == When a permanent activation failure of the No button input is detected, the failed state of the No button shall be persisted in non-volatile memory by the XPU until the No button input has returned to the Inactive condition, at which time the XPU shall "clear" the permanent activation failure state from non-volatile memory and send an alert to the MAX Gateway with the "Id" value set to 65536163 (NoButtonPerm ActiveRecovery). | YES | When the no button recovers from the stuck situation | Azure Cloud | |||||
| ChatSessionActivated | "id": 65536164 == A Chat Session may only be activated by the following method: | YES | When chat starts | Azure Cloud | |||||
| ChatSessionDeactivated | "Id": 65536165 == While a Chat Session is active, if the XPU receives a message from the In-Cabin Intercom via the ICIPI to XPU Signalling Service (see Section 7.6.4 ICIPI to XPU Signalling Service of this document for details) with "Command":" DeactivateChat", the XPU shall do the following: | YES | When chat is deactivated | Azure Cloud | |||||
| VideoActivated | "Id": 65536166 == While a Chat Session is active, when the XPU receives a message from the In-Cabin Intercom via the ICIPI to XPU Signalling Service (see Section 7.6.4 ICIPI to XPU Signalling Service of this document for details) with "Command":" ActivateCamera", the XPU shall activate the video camera, connect the video feed to the DES Platform Chat/Video Service chat room, and the XPU shall send an alert to the MAX Gateway with the "Id" value set to 65536166 (VideoActivated). | YES | When video starts | Azure Cloud | |||||
| VideoDeactivated | "Id": 65536167 == While a Chat Session is active, if the XPU receives a message from the In-Cabin Intercom via the ICIPI to XPU Signalling Service (see Section 7.6.4 ICIPI to XPU Signalling Service of this document for details) with "Command":" DeactivateChat", the XPU shall do the following: | YES | When video is deactivated | Azure Cloud | |||||
| ChatInactiveInvalidVideo ActivationCommand |
"Id": 65536168 == While there is no currently active Chat Session, it shall not be possible to activate the collection of video from the cabin. If a Chat Session is not Active and the XPU receives a message from the In-Cabin Intercom via the ICIPI to XPU Signalling Service with "Command":" ActivateCamera", the XPU shall ignore this command and it shall send an alert to the MAX Gateway with the "Id" value set to 65536168 (ChatInactiveInvalidVideo ActivationCommand). | YES | On failure | Azure Cloud | |||||
| YesButtonActive | "Id": 65536169 == While a Chat session is active, in addition to sending text messages to the DES Platform Chat/Video Service the XPU shall send Alerts to the MAX Gateway: | YES | When the yes button is pressed during chat | Azure Cloud | |||||
| YesButtonInactive | "Id": 65536170 == While a Chat session is active, in addition to sending text messages to the DES Platform Chat/Video Service the XPU shall send Alerts to the MAX Gateway: | YES | When the yes button is released during chat | Azure Cloud | |||||
| NoButtonActive | "Id": 65536171 == While a Chat session is active, in addition to sending text messages to the DES Platform Chat/Video Service the XPU shall send Alerts to the MAX Gateway: | YES | When the no button is pressed during chat | Azure Cloud | |||||
| NoButtonInactive | "Id": 65536172 == While a Chat session is active, in addition to sending text messages to the DES Platform Chat/Video Service the XPU shall send Alerts to the MAX Gateway: | YES | When the no button is released during chat | Azure Cloud | |||||
| CanCommGain | "Id": 65536173 == CanCommGain. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536173, this means that stable and successful CAN communications has been established. | YES | When recovering from CAN failure | Azure Cloud | |||||
| CanCommLoss | "Id": 65536174 == CanCommLoss. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536174, this means that stable and successful CAN communications has been lost. | YES | On failure | Azure Cloud | |||||
| RemoteUpdateTriggered Reboot |
"Id": 65536178 =. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536178, this means that EN81-28:2018 In-Cabin IP Intercom received a trigger from the Remote Update Service to reboot. In this case, the Remote Update Service will not provide a firmware version for update and the EN81-28:2018 In-Cabin IP Intercom shall reboot as soon as possible (if there is no currently active voice connection). | YES | During update | Azure Cloud | |||||
| AudioLibraryCatalogMissing | "Id": 65536182 == If the parameter "Voice_Announcements" ==TRUE (see Section 7.9 Cabin Display in this requirements document for more details), the two following conditions must also be TRUE: | YES | On failure | Azure Cloud | |||||
| InvalidPrimaryAnnouncement Language |
"Id": 65536183 == InvalidPrimary AnnouncementLanguage. If the parameter "Voice_Announcements" ==TRUE, the device shall check if the primary language config is set to a valid value when the device starts and any time the primary language config changes. If the language is not valid then the device shall send this alert. The language is not valid if it is set to NULL or an empty string. If this alert is sent, then the AnnouncementAudio FilesMissing alert should not be sent. | YES | On failure |
Azure Cloud | |||||
| PerformingFactoryReset | "Id": 65536186 == PerformingFactoryReset. When the EN81-28:2018 In-Cabin IP Intercom sends an Alert to the MAX Gateway with the "Id"==65536186, this means that EN81-28:2018 In-Cabin IP Intercom received a trigger via the ICIPI Command Service to perform a Factory Reset and the intercom will now perform that task. Once this Alert is sent, the Intercom should shortly stop functioning normally and revert to its Pre-Registered state. | YES | On factory reset (during device decomissioning) | Azure Cloud | |||||
| AudioLibraryDirectoryMissing | "Id": 65536187 == AudioLibrary DirectoryMissing. When the device starts up and when the audio library config changes, the XPU should check if the audio library directory exists. If it does not, it should trigger this alert to be sent. If this alert is sent, no other library related alert should be sent to avoid redundancy. These library related alerts consist of AudioLibraryNotSet, PrimaryAnnouncement LanguageDirectoryMissing, SecondaryAnnouncement LanguageDirectoryMissing, LocalAnnouncement LanguageDirectoryMissing, and AnnouncementAudio FilesMissing. | YES | On failure | Azure Cloud | |||||
| AnnouncementAudioFilesMissing | "Id": 65536188 == Announcement AudioFilesMissing. If the parameter "Voice_Announcements"==TRUE, upon receiving the first command from the controller to play a voice announcement after start up or after an audio library change or after a language config change, the device shall check if the audio file for the specified language is available. If the audio files is not available, the device shall send this alert. The alert shall not be resent unless the conditions above are met again after an audio library change or after a language config change. | YES | On failure | Azure Cloud | |||||
| InvalidSecondaryAnnouncement Language |
"Id": 65536189 == InvalidSecondary AnnouncementLanguage. If the parameter "Voice_Announcements"==TRUE, upon receiving the first command from the controller to play a secondary language voice announcement after start up or after the secondary language config changes, the device shall check if the secondary language config is valid. If the language is not valid, the device shall send this alert. The language is not valid if it is set to NULL or an empty string. The alert shall not be resent unless the conditions above are met again after a secondary language config update. | YES | On failure | Azure Cloud | |||||
| InvalidLocalAnnouncement Language |
"Id": 65536190 == InvalidLocal AnnouncementLanguage. If the parameter "Voice_Announcements" ==TRUE, upon receiving the first command from the controller to play a local language voice announcement after start up or after the local language config changes, the device shall check if the local language config is valid. If the language is not valid, the device shall send this alert. The language is not valid if it is set to NULL or an empty string. The alert shall not be resent unless the conditions above are met again after a local language config update. | YES | On failure | Azure Cloud | |||||
| RemoteUpdateDailyLimit | YES | On failure | Azure Cloud | ||||||
| RemoteConfigurationDailyLimit | YES | On failure | Azure Cloud | ||||||
| SSLCertDailyLimit | YES | On failure | Azure Cloud | ||||||
| XPUBIPISignalFailure | YES | On failure | Azure Cloud | ||||||
| PhonebookDownloadStarted | YES | Azure Cloud | |||||||
| PhonebookInstallAborted | YES | Azure Cloud | |||||||
| PhonebookDownloadTimeout | YES | Azure Cloud | |||||||
| PhonebookInvalid | YES | Azure Cloud | |||||||
| PhonebookDownloadCmpleted | YES | Azure Cloud | |||||||
| SSLCheckDownloadStarted | YES | Azure Cloud | |||||||
| SSLCertificateInstallAborted | YES | Azure Cloud | |||||||
| SSLCheckDownloadTimeout | YES | Azure Cloud | |||||||
| SSLCheckInvalidCertificates | YES | Azure Cloud | |||||||
| SSLCheckDownloadCompleted | YES | Azure Cloud | |||||||
| RemoteUpdateCanceledFire | The Remote Firmware Update Process has been canceled due to an active Fire Mode. | YES | On failure | Azure Cloud | |||||
| RemoteConfigCanceledFire | The Remote Configuration Process has been canceled due to an active Fire Mode. | YES | On failure | Azure Cloud | |||||
| FireFighterModeActive | Either the Phase 1 or the Phase 2 of the EN81-72 Firefighter mode has become active. | YES | On fire event | Azure Cloud | |||||
| FireFighterModeInactive | Both Phase 1 and Phase 2 of the EN81-72 Firefighter mode has become inactive. | YES | On fire event | Azure Cloud | |||||
| OutgoingDesktopPhone CallStarted |
An Outgoing Desktop Phone Call has been triggered and the Intercom is dialing the Conference Bridge. | YES | On desktop phone call | Azure Cloud | |||||
| OutgoingDesktopPhone CallAnswered |
An Outgoing Desktop Phone Call has been answered by the Conference Bridge. | YES | On desktop phone call | Azure Cloud | |||||
| OutgoingDesktopPhone CallNoAnswer |
The Conference Bridge has not responded to an Outgoing Desktop Phone Call and the Intercom has timed out and given up and hung up the call. | YES | On desktop phone call failure | Azure Cloud | |||||
| OutgoingDesktopPhone CallEnded |
An active Outgoing Desktop Phone Call was terminated normally (with a SIP BYE). | YES | At the of a desktop phone call | Azure Cloud | |||||
| OutgoingDesktopPhone CallException |
An active Outgoing Desktop Phone Call was terminated due to an abnormal condition (network, SIP, etc). | YES | On desktop phone call failure | Azure Cloud | |||||
| OutgoingDesktopPhone CallTimeout |
An active Outgoing Desktop Phone Call was terminated due to device timeout. | YES | On desktop phone call failure | Azure Cloud | |||||
| OutgoingFireFighters CallStarted |
An Outgoing FireFighters Call has been triggered and the Intercom is dialing the Conference Bridge. | YES | On fire event | Azure Cloud | |||||
| OutgoingFireFighters CallAnswered |
An Outgoing FireFighters Call has been answered by the Conference Bridge. | YES | On fire event | Azure Cloud | |||||
| OutgoingFireFighters CallNoAnswer |
The Conference Bridge has not responded to an Outgoing FireFighters Call and the Intercom has timed out and given up and hung up the call. | YES | On fire event failure | Azure Cloud | |||||
| OutgoingFireFighters CallEnded |
An active Outgoing FireFighters Call was terminated normally (with a SIP BYE). | YES | At the end of a fire event | Azure Cloud | |||||
| OutgoingFireFighters CallException |
An active Outgoing FireFighters Call was terminated due to an abnormal condition (network, SIP, etc). | YES | On fire event failure | Azure Cloud | |||||
| FactoryResetDelayed | The device has received a FactoryReset command from MAX via the Command Service and the command is being delayed for various reasons (Emergency Call state=="active", Fire State=="active", etc). | YES | Azure Cloud | ||||||
| CameraMissing | The camera associated with the device was determined to be unreachable. | YES | On failure | Azure Cloud | |||||
| CameraError | A camera error occurs that prevents the starting or continued running of the camera. | YES | On failure | Azure Cloud | |||||
| InvalidDisplayFeature ForScreenSize |
Indicates an enabled display setting was not able to be rendered because the feature is not compatible with the current display size (e.g. Next_Landing_Indicator_Enabled =true but display size is 7" would trigger this alert because Next_Landing_Indicator_Enabled =true is only compatible with 10.1" screens). | YES | When there's a configuration mismatch | Azure Cloud | |||||
| ContentWidgetSizeMismatch | Indicates there is a mismatch between a screen size parameter within the system and the actual screen size. Currently this is only used when the Widget Board configuration screen size does not match the actual screen size. | YES | When there's a configuration mismatch | Azure Cloud | |||||
| NdcConfigUpdateRejected | "Id": 65536277 == NdcConfigUpdateRejected. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536277, this means that a requested non-digital connectivity (NDC) config update was rejected. At this time, the only reason for an NDC config update rejection is when the request is submitted after the device is already provisioned. After the device is provisioned, only remote updates through the cloud config update service are allowed. | YES | On failure | Azure Cloud | |||||
| NdgcControllerVersion Incompatible |
"Id": 65536279 == NdgcController VersionIncompatible. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536279, this means that the controller version is not compatible with the nDGC application. | YES | On start up if the system is badly configured | Azure Cloud | |||||
| NdgcInactive | "Id": 65536280 == NdgcInactive. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536280, this means that the nDGC application did not transition out of the INACTIVE state within some timeout period upon start up. | YES | On start up | Azure Cloud | |||||
| NdgcCommunicationError | "Id": 65536281 == NdgcCommunicationError. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536281, this means that an attempt to communicate with the local nDGC application failed. | YES | On failure | Azure Cloud | |||||
| NdgcPrepareForReboot Timeout |
"Id": 65536282 == NdgcPrepareFor RebootTimeout. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536282, this means that the nDGC application prepare for reboot process timed out and that a reboot will proceed without a ready for reboot confirmation from nDGC. | YES | On failure | Azure Cloud | |||||
| NdgcUnknownStatus | "Id": 65536283 == NdgcUnknownStatus. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536283, this means that the nDGC application provided an unknown status in response to the get status request. When this occurs, this indicates some nDGC coordination process (e.g. initialization monitoring, prepare for reboot, etc.) was unable to complete. | YES | On failure | Azure Cloud | |||||
| SdCardMountFailed | "Id": 65536284 == SdCardMountFailed. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536284, this means that an installed SD card was detected, but it failed to mount during the device boot up process. | YES | On failure | Azure Cloud | |||||
| SdCardMissing | "Id": 65536285 == SdCardMissing. When the XPU sends an Alert to the MAX Gateway with the "Id"==65536285, this means that an installed SD card was not detected. | YES | On failure | Azure Cloud | |||||
| WidgetBoardClientUpdated | When the XPU sends an Alert with the "Id"==65536286, this means that the WidgetBoard Client component was updated successfully after receiving a "setContents" Push Command. | YES | ~once each 3 months | Azure Cloud | |||||
| WidgetBoardClientUpdate Failed |
When the XPU sends an Alert with the "Id"==65536287, this means that the WidgetBoard Client component failed to update after receiving a "SetContents" Push Command. | YES | On failure | Azure Cloud | |||||
| WidgetBoardConfigUpdated | When the XPU sends an Alert with the "Id"==65536288, this means that the WidgetBoard Client content configuration was updated successfully after receiving a "SetContentConfiguration" Push Command. | YES | When widget board client config is updated, at most 12 times a day | Azure Cloud | |||||
| WidgetBoardConfigInvalid | When the XPU sends an Alert with the "Id"==65536289, this means that the WidgetBoard Client content configuration was detected to be incompatible or broken after an XPU restart. | YES | On failure | Azure Cloud | |||||
| WidgetBoardConfigUpdate Rejected |
When the XPU sends an Alert with the "Id"==65536290, this means that the WidgetBoard Client content configuration was rejected by the WB client after receiving a "SetContentConfiguration" Push Command. | YES | On failure | Azure Cloud | |||||
| ScreenshotCaptureFailure | When the XPU sends an Alert with the "Id"==65536291, this means that a screenshot capture attempt failed after receiving a TakeScreenshot Push Command. | YES | Never - feature not currently supported in the cloud | Azure Cloud | |||||
| ScreenshotUploadFailure | When the XPU sends an Alert with the "Id"==65536292, this means that a screenshot capture was successful but failed to be uploaded to the cloud after receiving a TakeScreenshot Push Command. | YES | Never - feature not currently supported in the cloud | Azure Cloud | |||||
| ScreenshotUploadSuccess | When the XPU sends an Alert with the "Id"==65536293, this means that a screenshot capture and upload was successful after receiving a TakeScreenshot Push Command. | YES | Never - feature not currently supported in the cloud | Azure Cloud | |||||
| CameraLightWardenNotActive | When the XPU sends an Alert with the "Id"==65536294, this means that the EstablishCameraLight WardenReference Push Command was received but cannot be handled because the camera light warden application is disabled due to the Camera_Light_ Warden_Enabled parameter being set to false. | YES | When there's a configuration mismatch | Azure Cloud | |||||
| CameraLightWardenInvalid ReferenceValue |
When the XPU sends an Alert with the "Id"==65536295, this means that the EstablishCameraLight WardenReference Push Command was received but the reference value provided in the push command payload was invalid (out of range, wrong format, etc). | YES | On bad configuration | Azure Cloud | |||||
| CameraLightWardenReference ImageCaptureFailure |
When the XPU sends an Alert with the "Id"==65536296, this means that the camera light warden image reference establishment procedure failed. | YES | On failure | Azure Cloud | |||||
| CameraLightWardenReference ImageCaptureSuccess |
When the XPU sends an Alert with the "Id"==65536297,this means that the camera light warden image reference establishment procedure succeeded. The lux reference value used during the process shall be included in the "Cid" field of the alert. | YES | Once in a device lifecycle | Azure Cloud | |||||
| CameraLightWarden OperationalFailure |
When the XPU sends an Alert with the "Id"==65536298, this means that the device fail to perform regular operation (e.g. failed to acquire a measurement). | YES | On failure | Azure Cloud | |||||
| CameraLightWardenReference ImageNotEstablished |
When the XPU sends an Alert with the "Id"==65536299, this means that during the camera light warden application initialization process there is no reference picture available and thus the refence images are not established. | YES | On failure | Azure Cloud | |||||
| CameraLightWardenReference ImageCaptureRejectedEmergency |
When the XPU sends an Alert with the "Id"==65536300, this means that the EstablishCameraLight WardenReference Push Command was received but cannot be handled because the camera is currently in use due to an active emergency. | YES | On failure | Azure Cloud | |||||
| CameraLightWardenCabin LightDefective |
When the XPU sends an Alert with the "Id"==65536301, this means that the lux measurement is below the defined threshold long enough to be considered a defect. | YES | On failure | Azure Cloud | |||||
| CameraLightWardenCabin LightOK |
When the XPU sends an Alert with the "Id"==65536302, this means that, in case a CameraLightWardenCabin LightDefective was issued before, but the lux measurement is now above the defined threshold long enough to assume the defect was resolved. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| CameraLightWardenCabin LightMonitorDefective |
When the XPU sends an Alert with the "Id"==65536303, this means something is causing the monitor to not function properly (e.g. missing camera, exception, process failure, etc). | YES | On failure | Azure Cloud | |||||
| CameraLightWardenCabin LightMonitorOK |
When the XPU sends an Alert with the "Id"==65536304, this means in case a CameraLightWardenCabin LightMonitorDefective was issued before, but the application was able to recover itself and it is back to normal operation. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| WidgetBoardClientUpdate RejectedEmCall |
When the XPU sends an Alert with the "Id"==65536305, this means a widget board client update request triggered by the SetContents push command request was rejected due to an active emergency call. | YES | On failure | Azure Cloud | |||||
| WidgetBoardClientUpdate RejectedFire |
When the XPU sends an Alert with the "Id"==65536306, this means a widget board client update request triggered by the SetContents push command request was rejected due to an active fire. | YES | On failure | Azure Cloud | |||||
| WidgetBoardConfigUpdate RejectedEmCall |
When the XPU sends an Alert with the "Id"==65536307, this means a widget board client update request triggered by the SetContentConfiguration push command request was rejected due to an active emergency call. | YES | On failure | Azure Cloud | |||||
| WidgetBoardConfigUpdate RejectedFire |
When the XPU sends an Alert with the "Id"==65536308, this means a widget board client update request triggered by the SetContentConfiguration push command request was rejected due to an active fire. | YES | On failure | Azure Cloud | |||||
| LogsPackingFailure | When the XPU sends an Alert with the "Id"==65536309, this means that a Submit*Logs push command was received, but the logs failed to be retrieved/bundled/packed for upload. | YES | On failure | Azure Cloud | |||||
| LogsUploadFailure | When the XPU sends an Alert with the "Id"==65536310, this means that a Submit*Logs push command was received and the logs were successfully prepared to be uploaded, but some error occurred during the upload process. | YES | On failure | Azure Cloud | |||||
| ControllerRequestedUnset SecondaryLanguageToPlay |
Controller requested for XPU to play an audio using secondary language, but the device doesn't have such language set. | YES | When there's a mismatch between GCSW and XPU configs | Azure Cloud | |||||
| AudioLibraryNotSet | On startup or upon audio library change, if the parameter "Voice_Announcements" ==TRUE and the audio library directory is present, the device shall check the Audio_Library_Number config parameter. If its value is NULL, this alert shall be sent. This alert shall not be resent unless the conditions are met again after the audio library is changed. If this alert is sent, the PrimaryAnnouncement LanguageDirectoryMissing, SecondaryAnnouncement LanguageDirectoryMissing, LocalAnnouncementLanguage DirectoryMissing, AnnouncementAudio FileMissing, and AudioLibraryDirectoryMissing alerts should not be sent to avoid redundancy. | YES | Due to bad configuration | Azure Cloud | |||||
| PrimaryAnnouncement LanguageDirectoryMissing |
On startup, upon audio library change, or upon primary announcement language config change, if the parameter "Voice_Announcements" ==TRUE and the primary announcement language config is not NULL, the device shall check if the specified language directory in the audio library exists. If it does not exist, this alert shall be sent. If this alert is sent, the AnnouncementAudio FileMissing alert should not be sent to avoid redundancy. | YES | Worst case scenario once in a device life cycle | Azure Cloud | |||||
| SecondaryAnnouncement LanguageDirectoryMissing |
On startup, upon audio library change, or upon secondary announcement language config change, if the parameter "Voice_Announcements" ==TRUE and the secondary announcement language config is not NULL, the device shall check if the specified language directory in the audio library exists. If it does not exist, this alert shall be sent. If this alert is sent, the AnnouncementAudio FileMissing alert should not be sent to avoid redundancy. | YES | Worst case scenario once in a device life cycle | Azure Cloud | |||||
| LocalAnnouncement LanguageDirectoryMissing |
On startup, upon audio library change, or upon local announcement language config change, if the parameter "Voice_Announcements"==TRUE and the local announcement language config is not NULL, the device shall check if the specified language directory in the audio library exists. If it does not exist, this alert shall be sent. If this alert is sent, the Announcement AudioFileMissing alert should not be sent to avoid redundancy. | YES | Never - local lang not currently being used | Azure Cloud | |||||
| AnnouncementAudio CouldNotBePlayed |
If the parameter "Voice_Announcements" ==TRUE, upon receiving the first command from the controller to play a voice announcement after start up or after the audio library changes or after the language config changes, the device will attempt to play the announcement with the specified language. If the specified audio file is available in the audio library, but the announcement fails to play for any reason (e.g. corrupted), then the device shall send this alert. The alert shall not be resent unless conditions are met again after the audio library changes or after the language config changes. | YES | On failure | Azure Cloud | |||||
| DiskUsageWarning | When storage usage goes above a specified threshold. | YES | On failure | Azure Cloud | |||||
| DiskUsageCritical | When storage usage goes above a specified critical threshold. | YES | On failure | Azure Cloud | |||||
| DiskUsageOk | When storage usage is below the specified threshold. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| SDCardUsageWarning | When storage usage goes above a specified threshold. | YES | On failure | Azure Cloud | |||||
| SDCardUsageCritical | When storage usage goes above a specified critical threshold. | YES | On failure | Azure Cloud | |||||
| SDCardUsageOk | When storage usage is below the specified threshold. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| RAMUsageWarning | When RAM usage goes above a specified threshold. | YES | On failure | Azure Cloud | |||||
| RAMUsageCritical | When RAM usage goes above a specified critical threshold. | YES | On failure | Azure Cloud | |||||
| RAMUsageOk | When RAM usage is below the specified threshold. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| CPUUsageWarning | When CPU usage goes above a specified threshold. | YES | On failure | Azure Cloud | |||||
| CPUUsageCritical | When CPU usage goes above a specified critical threshold. | YES | On failure | Azure Cloud | |||||
| CPUUsageOk | When CPU usage is below the specified threshold. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| TemperatureWarning | When temperature goes above a specified threshold. | YES | On failure | Azure Cloud | |||||
| TemperatureCritical | When temperature goes above a specified critical threshold. | YES | On failure | Azure Cloud | |||||
| TemperatureOk | When temperature is below the specified threshold. | YES | On start up or once device recovers from failure | Azure Cloud | |||||
| TemperatureSensorFailure | When there's a failure on the temperature sensor. | YES | On failure | Azure Cloud | |||||
| AudioLibraryUpdateStarted | When the device starts to update its audio library. | YES | During provisioning, once each 7 days | Azure Cloud | |||||
| AudioLibraryUpdateSuccess | When the audio library is successfully updated. | YES | ~Once a year | Azure Cloud | |||||
| AudioLibraryUpdateFailed | When the audio library update process fails. | YES | On failure | Azure Cloud | |||||
| AudioLibraryUpToDate | When the audio library is already up to date. | YES | When library is up to date, ~once each 7 days | Azure Cloud | |||||
| RemoteFilesUpdateDaily Limit |
When the remote files service limit has been reached | YES | On failure | Azure Cloud | |||||
| RemoteFilesUpdate CanceledEmCall |
When the remote files service is canceled due to an emergency call. | YES | On failure | Azure Cloud | |||||
| RemoteFilesUpdate CanceledFire |
When the remote files service is canceled due to a fire event. | YES | On failure | Azure Cloud | |||||
| RemoteFilesUpdate CanceledPower |
When the remote files service is canceled due to a power event. | YES | On failure | Azure Cloud | |||||
| RemoteFilesUpdate Timeout |
When the remote files serivce times out. | YES | On failure | Azure Cloud | |||||
| SSLCertificateExpiring | Indicates the SSL certificates obtained during provisioning are within 14 days of expiring. The device should automatically try to update the certificates every day until successful and will send this alert along with the expiration time represented in Unix time within the "Cid" field. | YES | Worst case scenario once in a year | Azure Cloud | |||||
| ArtificialVisionInvalidROI | Indicates that configuration specifying artificial vision's region of interest is either missing (empty string) or invalid (missing entries). | YES | On bad configuration, once per start up | Azure Cloud | |||||
| DeviceRootfsCompromised | Indicates that the device's active rootfs partition has been compromised (unauthorized modification). The device cannot recover itself and action must be taken. | YES | When system integrity has been compromised | Azure Cloud | |||||
| SDCardCompromised | Indicates that the SD card data has been "compromised". Since there's no way to compare the contents of the SD card data (as they are not previously known), by compromised it is meant that there's data in the SD card that shouldn't be there and will be deleted. Deleted data is informed in the "Cid" field. | YES | When system integrity has been compromised | Azure Cloud | |||||
| DataPartitionCompromised | Indicates that the data partition data has been "compromised". Since there's no way to compare the contents of the data partition (as they are not previously known), by compromised it is meant that there's data in the data partition that shouldn't be there and will be deleted. Deleted data is informed in the "Cid" field. | YES | When system integrity has been compromised | Azure Cloud | |||||
| DeviceProcessesCompromised | Indicates that the device is running unknown/unauthorized processes. Processes will be killed. Killed processes are informed in the "Cid" field. | YES | When system integrity has been compromised | Azure Cloud | |||||
| SSLAutoRenewalStarted | Indicates the current SSL Certificate has expired or will expire within the next 14 days and the device has triggered the process to contact the Remote SSL Certificate Service to check for a new certificate. | YES | Worst case scenario once in a year | Azure Cloud | |||||
| SSLAdHocCheckStarted | Indicates the device has received the CheckSSL via the ad hoc command interface and has triggered the process to contact the Remote SSL Certificate Service to check for a new certificate. | YES | Ad-hoc | Azure Cloud | |||||
| SSLCheckConfigTimeout | Indicates the device has downloaded the new certificate and key but failed to put the certificate and key into operation before the "Certificate_Configuration_Time_Limit" expired. | YES | On failure | Azure Cloud | |||||
| Model | The hardware model name. | YES | On device start up | Azure Cloud | |||||
| Serial Number | The hardware serial number. | YES | On device start up | Azure Cloud | |||||
| Type | Device type. | YES | On device start up | Azure Cloud | |||||
| Regulatory Code | The regulatory code the device was provisioned under. | YES | On device start up | Azure Cloud | |||||
| Device Vendor | The hardware vendor. | YES | On device start up | Azure Cloud | |||||
| Firmware Version | The firmware version. Note that during firmware version initialization, the firmware version retrieval blocks until no firmware update is in progress or a timeout occurs. | YES | On device start up or on firmware update, ~once each 3 months | Azure Cloud | |||||
| GALC Version | Global audio library catalog version. If the data file does not exist, the version is set to "not available". If the data file exists but the version is not provided, the version is set to "1.0.0". | YES | NO | On device start up | Azure Cloud | ||||
| nDGC Version | nDGC application version obtained via the nDGC HTTP server /version method. | YES | NO | On device start up | Azure Cloud | ||||
| Widget Board Client Version | Widget board client version obtained via the WidgetBoard D-Bus interface WidgetBoardVersions property. | YES | NO | On device start up and on widget board updates, ~once each 3 months | Azure Cloud | ||||
| Widget Board Config ID | Widget board client version obtained via the WidgetBoard D-Bus interface WidgetBoardVersions property. | YES | NO | On device start up and on widget board configuration changes (up to 12x a day?) | Azure Cloud | ||||
Data Specifications Non-EOX Products
Controller for Non-EOX Products
See Details
| Attribute | Description | TCM | CMC3 | Other CMCs | MAX Fusion | Frequency | Estimated volume | Storage location | Data retention |
|---|---|---|---|---|---|---|---|---|---|
| Capacity | The lift's capacity in kg. | YES |
NO | YES | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Car Call | When you are inside an elevator and press a button to go to a specific floor. | YES | NO | YES | YES | When an elevator call happens | Based on system usage | Azure Cloud | indefinitly |
| CarType | Defines whether the car is a single, double deck, or twin car. | NO | NO | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| ContractSpeed | The contract speed in millimeters per second. | YES | NO | YES | YES | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| ControllerDescription | Helpful information describing what elevator this is. Is mainly for the technician and not for machine learning. | NO | NO | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| ControllerNumber | A unique number for the elevator. For TAC, this will be the controller’s job number. This number might be the ERP ID for some elevators. | YES | NO | NO | YES | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| ControllerType | This denotes the type of elevator connected. E.g. TAC20, TAC32, E.COR, etc. | YES | YES | YES | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| CurrentPosition | The current position in mm. The value is reported to the core (application) in specific bluebox API calls (e.g. after a trip is finished) | YES | NO | YES/NO | YES | When the elevator moves or by request (TCM) | Based on system usage | Azure Cloud | indefinitly |
| Destination Calls | When you walk up to a kiosk, select the floor you want to go to, and the kiosk tells you which elevator to ride. | YES | NO | NO | NO | When an elevator call happens | Based on system usage | Azure Cloud | indefinitly |
| Digital Position | The digital position of the elevator inside the shaft. | YES | NO | YES/NO | YES | When the elevator moves or by request (TCM) | Based on system usage | Azure Cloud | indefinitly |
| Door Movement | A door movement describes the opening or closing of a car door with its starting point, end point, and motion cause. | YES | YES | YES | YES | When the door moves | Based on system usage | Azure Cloud | indefinitly |
| Elevator Floor | The different levels at which the elevator stops. They are numbered from 0 on the lowest floor of the elevator upwards. Note that floor 0 might not be at ground level. Also, note the difference between the floor label (usually 1, 2, 3.... starting at the ground floor) and the floor number. | YES | YES | YES | YES | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| ElevatorType | The type of this elevator. | NO | NO | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| EmergencyPower | Indicates whether the emergency power is on or off. | YES | NO | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| Error Codes | Error codes provided by the controller. | YES | YES | YES | NO | When error occur | Based on system usage | Azure Cloud | indefinitly |
| FirefighterMode | 1. Describes which phase of the figherfighter mode the elevator is in. The firefighter mode is either in - a. off, b. Phase 1: transition from normal operation to fire/smoke/fire/heat has been detected (or the detection is set to true due to a test); passengers are transported to the main floor of egress, c. Phase 2: firefighters use a special key, so they can use the elevator to access the building floors, if the elevator is usable. | NO | NO | NO | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| FireSmoke | Indicates whether the elevator has detected a fire or smoke. Typically they come down to the lobby and park with open doors. Newer lifts can also perform an evacuation action in this mode and avoid the floors where fire has been detected and evacuate all other floors to the lobby. | YES | YES | YES | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| GeneralShutdown | Indicates whether the elevator can be used or not. | YES | YES | YES | NO | When there is a shutdown error | Based on system usage | Azure Cloud | indefinitly |
| GroupName | The name of the group as perceived from the controller. This helps the cloud to perform some sanity checks on manual group configuration. | NO | NO | NO | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Hall Call | When you walk up to the elevator and press the down button signifying that you want to go down. | YES | NO | YES | NO | When a call happens | Based on system usage | Azure Cloud | indefinitly |
| HallCallsInhibited | Indicates whether the elevator can answer hall calls or not (e.g. technician is working on the elevator, fire in the building → hall calls are disabled). | YES | NO | NO | NO | When it's happening | Based on system usage | Azure Cloud | indefinitly |
| HasResidentMechanic | True if this elevator has a resident mechanic. | NO | Masterdata - Could be provided by the user in GTA | Based on system usage | Azure Cloud | indefinitly | |||
| IndependentOperation | Indicates whether this elevator operates as part of a group or independent. elevator is only answering car calls (not answering to any hall calls or destination calls) | YES | YES | YES | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| Inspection | 1. Inspection describes a mode of operation, where someone (service person) is working on the elevator. Is set to true if someone is working on the elevator. 2. The inspection mode can be set manually from different locations for one elevator: a. machine room, b. in the car, c. on top of the car |
YES | YES | YES | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| Load | The lift's actual load in percent. Due to sensor misalignments or overload conditions, this value can easily exceed the expected range of 0-100 % in both directions. | YES | NO | YES/NO | NO | When the load is updated and the elevator is stopped | Based on system usage | Azure Cloud | indefinitly |
| NumberOfCarsInGroup | The number of cars within the group the elevator is in, as perceived from the elevator, not the group controller. This number can help the cloud to perform sanity checks on the manual group configuration. | YES | NO | YES | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| NumberOfStops | Can be derived on cloud side based on the number of associated stops. | YES | YES | YES | YES | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Operation Modes | The operation mode is defined in the CPC. The CPC reports the operation mode as an integer value (can be different for all the different CPCs). THe cloud has a mapping table to decide which operation mode the elevator is in. | YES | YES | YES | YES | When elevator updates is mode | Based on system usage | Azure Cloud | indefinitly |
| OverloadThreshold | The threshold for the overload condition in percent. This can vary depending on elevator type and/or regulatory requirements. | YES | YES | YES | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Recall | The recall identifies a specific kind of inspection mode. | YES | YES | YES | NO | When it's under this mode | Based on system usage | Azure Cloud | indefinitly |
| SoftwareVersion | The software version of the elevator control system. | YES | YES | YES | NO | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| TravelHeight | The travel height as derived from the associated floors. | YES | NO | YES/NO | YES | On MAX startup | Average 1x a month | Azure Cloud | indefinitly |
| Trips | A trip is any time that the car is moving. This can be a full trip between two floors, or a re-level. A trip is signified as starting when the drive’s run signal goes high. The trip ends when the drive’s run signal goes low. A re-level is defined as a trip that starts and ends at the same floor. | YES | YES | YES | YES | When a trip happens | Based on system usage | Azure Cloud | indefinitly |
| Alarm Activation Signal | Must trigger a two-way voice communication with a remote assistance center. | YES | Initiated by a passenger pressing the emergency button. | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Lift Identification Data | Ensures the remote center knows which lift is calling. | YES | When connecting to call center | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Call center dial no. | No. of call center or ID to dial to. | YES | Unique identifier for the call center when connecting to lift | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Call Status Information | Duration of the call and whether it was terminated properly. | YES | Confirmation that the call was successfully connected | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Voice and data as SIP/ RTP data | Voice and data stream to the IP PBX call center. | YES | During routine (every 72 hours) and active emergency call | 1x every 3 days and baed on system usage | Based on system usage | Depends on country call center backend policy | |||
| Battery Status | Alerts if battery is low or faulty (especially during test calls). | YES | Real-time monitoring and reporting of battery health in case of not compliance | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Fault or Error Codes | If any part of the system fails (e.g., $G module, speaker, microphone), a fault signal must be sent to the monitoring center. | YES | On failure detection | Based on system usage | Based on system usage | Depends on country call center backend policy | |||
| Test Call Confirmation | Every 72 hours, a routine test call must be made using the same method as a real emergency call (e.g., GSM voice channel). The system must log and confirm that the test was successful. | YES | Every 72 hours | 1x every 3 days | Azure Cloud & Call Center backend | "Azure Cloud: ""@Jens Call Center backend: depends on country call center backend policy" |
|||
| Trapped passenger release | In case of rescue opperation, notification to the call center that the entrapment has been solved. | YES | When initiated by service men onsite | Based on system usage | Azure Cloud | ||||
| Heartbeat | The keep alive signal sent by the devices. | YES | 1x per hour | 24x/day | Azure Cloud | ||||
| DES Alerts | Alerts coming from DES Devices to notify the cloud and country backend on specific conditions. | YES | Based on specific scenarios of the devices | Based on system usage | Azure Cloud | ||||
| IoT Hub Connection | Information whether the device is connected or not with IoT Hub (Azure). | YES | Depends on connections and disconnections w/ cloud | Based on device-cloud connection stability | Azure Cloud | ||||
| Transmission Mode | The transmission mode of MAX (batch, real-time, live). | YES | 2x a day | 2x/day | Azure Cloud | ||||
| Acceleration values | Accleration --> vibration during door and car movements. | YES | Every run | Based on system usage | Azure Cloud | indefinitly |
Data Specifications Global Escalator Controller (GEC)
Controller for Escalator Products
See Details
| Attribute | Description | Frequency | Estimated volume | Storage location | Data retention |
|---|---|---|---|---|---|
| Error log | Errors detected by the controller, last 2300. | Once error is detected | Daily | Local memory | Until memory is full |
| Parameter | Configuration loaded in the controller. | Once parameter are changed | Based on usage | Local memory | Overwritten on change |
| Event log | Register for the last 200 events detected. | Based on usage | Based on usage | Local memory | Until memory is full |
| Braking distance | Last 50 braking distance measurements. | Each time escalator stops | Based on usage | Local memory | Until memory is full |
| People Counter | Last 60 days. | Each 5 minutes | Hourly | Local memory | Until memory is full |
| Warning log | Last 50 warning detected by the controller. | Each time a warning is detected | Based on usage | Local memory | Until memory is full |
| Scheduled configuration | Specific times for scheduled operation. | Daily | Daily | Local memory | Overwritten on change |
| Statistics | Number of faults, stops, startings, hours running up, down, high speed, low speed… | Continously | Based on usage | Local memory | Overwritten on change |
| Operation mode | Last operation mode detected. | Once Op Mode is changed | Based on usage | Local memory | Overwritten on change |
Data Specifications for MAX Monitoring by Insight
Controller for MAX Monitoring by Insight
See Details
| Asset | Attribute | Description | Frequency | Estimated volume | Storage location | Data retention |
|---|---|---|---|---|---|---|
| Elevator | Car Call | When you are inside an elevator and press a button to go to a specific floor. | When an elevator call happens | Based on system usage | Cloud or local server | 1 year |
| Elevator | ControllerDescription | Helpful information describing what elevator this is. Is mainly for the technician and not for machine learning. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | ControllerNumber | A unique number for the elevator. For TAC, this will be the controller’s job number. This number might be the ERP ID for some elevators. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | ControllerType | This denotes the type of elevator connected. E.g. TAC20, TAC32, E.COR, etc. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | CurrentPosition | The current position in mm. The value is reported to the core (application) in specific bluebox API calls (e.g. after a trip is finished) | When the elevator moves or by request | Based on system usage | Cloud or local server | 1 year |
| Elevator | Destination Calls | When you walk up to a kiosk, select the floor you want to go to, and the kiosk tells you which elevator to ride. | When an elevator call happens | Based on system usage | Cloud or local server | 1 year |
| Elevator | Direction | Indicates if Elevator is moving upwards or downwards | When Elevator changes the direction | Based on system usage | Cloud or local server | 1 year |
| Elevator | Door Movement | A door movement describes the opening or closing of a car door with its starting point, end point, and motion cause. | When the door moves | Based on system usage | Cloud or local server | 1 year |
| Elevator | Elevator Floor | The different levels at which the elevator stops. They are numbered from 0 on the lowest floor of the elevator upwards. Note that floor 0 might not be at ground level. Also, note the difference between the floor label (usually 1, 2, 3.... starting at the ground floor) and the floor number. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | ElevatorType | The type of this elevator. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | EmergencyPower | Indicates whether the emergency power is on or off. | When it's under this mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | Error Codes | Error codes provided by the controller. | When error occur | Based on system usage | Cloud or local server | 1 year |
| Elevator | FirefighterMode | 1. Describes which phase of the figherfighter mode the elevator is in. The firefighter mode is either in - a. off, b. Phase 1: transition from normal operation to fire/smoke/fire/heat has been detected (or the detection is set to true due to a test); passengers are transported to the main floor of egress, c. Phase 2: firefighters use a special key, so they can use the elevator to access the building floors, if the elevator is usable | When it's under this mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | FireSmoke | Indicates whether the elevator has detected a fire or smoke. Typically they come down to the lobby and park with open doors. Newer lifts can also perform an evacuation action in this mode and avoid the floors where fire has been detected and evacuate all other floors to the lobby. | When it's under this mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | GeneralShutdown | Indicates whether the elevator can be used or not. | When there is a shutdown error | Based on system usage | Cloud or local server | 1 year |
| Elevator | GroupName | The name of the group as perceived from the controller. This helps the cloud to perform some sanity checks on manual group configuration. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | Hall Call | When you walk up to the elevator and press the down button signifying that you want to go down. | When a call happens | Based on system usage | Cloud or local server | 1 year |
| Elevator | HallCallsInhibited | Indicates whether the elevator can answer hall calls or not (e.g. technician is working on the elevator, fire in the building → hall calls are disabled). | When it's happening | Based on system usage | Cloud or local server | 1 year |
| Elevator | IndependentOperation | Indicates whether this elevator operates as part of a group or independent. elevator is only answering car calls (not answering to any hall calls or destination calls) | When it's under this mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | Inspection | 1. Inspection describes a mode of operation, where someone (service person) is working on the elevator. Is set to true if someone is working on the elevator. 2. The inspection mode can be set manually from different locations for one elevator: a. machine room, b. in the car, c. on top of the car. | When it's under this mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | Load | The lift's actual load in percent. Due to sensor misalignments or overload conditions, this value can easily exceed the expected range of 0-100 % in both directions. | When the load is updated | Based on system usage | Cloud or local server | 1 year |
| Elevator | NumberOfCarsInGroup | The number of cars within the group the elevator is in, as perceived from the elevator, not the group controller. This number can help the cloud to perform sanity checks on the manual group configuration. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | NumberOfStops | Can be derived on cloud side based on the number of associated stops. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Elevator | Operation Modes | The operation mode is defined in the CPC. The CPC reports the operation mode as an integer value (can be different for all the different CPCs). THe cloud has a mapping table to decide which operation mode the elevator is in. | When elevator updates is mode | Based on system usage | Cloud or local server | 1 year |
| Elevator | OverloadThreshold | The threshold for the overload condition in percent. This can vary depending on elevator type and/or regulatory requirements. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Both | SoftwareVersion | The software version of the elevator/escalator control system. | On startup | Average 1x a month | Cloud or local server | 1 year |
| Escalator | Escalator operation mode | Operation mode selected in the escalator. | When operation mode changes | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator direction | Direction of movement. | When direction changes | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator fault code | Fault/error codes detected. | When a new fault is detected | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator events | Any escalator event (switch to run up, down, stopped…) | When a new event is detected | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator statistics | Time in running, time stopped… | Hourly on average | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator people counter | People detected in escalator. | Each 5 minutes | Based on system usage | Cloud or local server | 1 year |
| Escalator | Escalator controller type | Type of escalator controller. | On startup | 1 month | Cloud or local server | 1 year |
| Both | Video recording | video captured by the cameras. | Continuously | Based on system usage | Local server | 1 month |
Data Specifications for HME MAX Stairlift
Controller for HME MAX Stairlift
See Details
| Entity | Tag | Description/Comment | MAX V2 | MHI | Frequency | Estimated volume | Storage location | Data retention |
|---|---|---|---|---|---|---|---|---|
| JY Armrest | JY - LEFT | Joystick left activation | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY - RIGHT | Joystick right activation | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | ES | Emergency stop button status | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | EL | Emergency lowering button status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | ARMREST-POSITION A | Armrest position A status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | ARMREST-POSITION B | Armrest position B status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | ARMREST-LOCK | Armrest lock pin status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | SEATBELT | Seatbelt status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | REMOTE ID | Remote control identifier | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | REMOTE BUTTON1 | Remote control button 1 status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | REMOTE BUTTON2 | Remote control button 2 status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | REMOTE BATTERY | Remote control battery level | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | AB_SW_ID_VERSION | Integer value of SW version (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | AB_SW_ID_RELEASE | Decimal value of SW version (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | AB_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_SW_ID_VERSION | Integer value of SW version (Joystick Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_SW_ID_RELEASE | Decimal value of SW version (Joystick Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Joystick Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_AB_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_AB_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_AB_SW_BULID_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_AB_HW_ID_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_SW_BULID_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| JY Armrest | JY_HW_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board |
SEATFB | Seat folding button status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | FOOTFB | Footrest folding button status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | KEYLS | Key-lock status switch | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | ARMREST-POSITION A | Armrest position A status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | ARMREST-POSITION B | Armrest position B status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | ARMREST-LOCK | Armrest lock status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | SEATBELT | Seatbelt status | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | AB_SW_ID_VERSION | Integer value of SW version (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | AB_SW_ID_RELEASE | Decimal value of SW version (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | AB_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Armrest Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_SW_ID_VERSION | Integer value of SW version (Option Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_SW_ID_RELEASE | Decimal value of SW version (Option Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Option Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_AB_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_AB_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_AB_SW_BULID_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_AB_HW_ID_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_SW_BUILD_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Option board | OPT_HW_ID_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_SW_ID_VERSION | Integer value of SW version (Folding Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_SW_ID_RELEASE | Decimal value of SW version (Folding Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Folding Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_SW_BUILD_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Folding board | FB_HW_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | FOLDFOOT | Footrest fold command | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | UFOLDFOOT | Footrest unfold command | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | FOLDING STOP | Folding stop command | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | DEVICE TYPE | C&P, REP, ATT and C&P + REP | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | COUNTRYCODE | Country of installation | YES | NO | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_SW_ID_VERSION | Integer value of SW version (Control Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_SW_ID_RELEASE | Decimal value of SW version (Control Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_HW_ID_VERSION | HW version, measured on Revision ID Voltage (Control Board) | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_SW_MAJOR_VERSION | Major software version of the module | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_SW_MINOR_VERSION | Minor software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_SW_BUILD_VERSION | Build software version of the module | YES | NO | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | CB_HW_VERSION | HW version of the PCB | YES | YES | On start up | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | S-code | Source code of fault code | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | C-code | Warning code | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | F-code | Fault code | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | U-code | User error code | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Operating seconds | The total amount of seconds the stairlift has been awake | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Drive seconds | The total amount of seconds the stairlift has driven | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Number of starts | The amount of times the stairlift has started driving | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Next Position Number | The number of the Position that the stairlift is driving to/last drove to, can become obsolete when current position is send | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Next Position Type | The type of Position that the stairlift is driving to/last drove to (1 = halt, 2 = park) | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | Stairlift Direction | The direction in which the stairlift is driving (1 = up, 2 = down) | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
| Control board | STATUS | Lift equipment status | YES | YES | Real-time state change | Based on usage | Azure Cloud | During service contract else 1 year |
