Otis Compass Elevator Integration Guide

Transcription

1 Otis Compass Elevator Integration Guide November 2015

2 SATEON Otis Compass Elevator Integration Guide Issue 2.0, released November 2015 Disclaimer Copyright 2015, Grosvenor Technology. All rights reserved. SATEON and the SATEON logo are trademarks or registered trademarks of Grosvenor Technology. All other brands, names, or trademarks appearing in this document are acknowledged as the trademarks of their respective owners. No part of this document may be reproduced in any form or by any means for any purpose without the written permission of Grosvenor Technology. Whilst we make every effort to ensure the accuracy of our publications, Grosvenor Technology assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. SATEON 2 Issue 2.0

3 Contents Preface... 5 About the Otis Compass Elevator interface... 5 About this guide... 5 Related documents... 6 Technical support... 6 Introduction... 7 Overview of the integration... 8 Key functionality... 9 Prerequisites... 9 Specific concepts Elevator Controllers and Terminals Designation of destinations Operational modes Levels of service Segmentation Setting up and licensing the Otis Compass Elevator interface Installing the elevator interface New installations Existing installations What is installed Licensing the Otis Compass Elevator integration Configuring the Otis Compass Elevator interface Configuring Service Settings Segmentation Levels of service Setting up readers and groups Setting up the elements of the elevator system within Sateon Configuring the Destination System SATEON 3 Issue 2.0

4 Configuring Destination Groups Configuring specific Destinations Configuring specific Destination Terminals Other configuration Access permissions Personnel attributes Monitoring activity Elevator interface events reported in Sateon Destination Group Events Destination Terminal Events Monitoring the Otis elevator elements Checking logs SATEON 4 Issue 2.0

5 Preface This document provides information on the Sateon Otis Compass Elevator interface, which provides an interface between Sateon and an Otis Compass Elevator system. The integration has been documented for Sateon Release 2.9: it may not include changes incorporated in later versions of the software. Representations of screens are shown for illustration only: there may be some differences in the screens you see, depending on the operating system and the computer configuration. Date of latest update: November About the Otis Compass Elevator interface SATEON is a powerful yet easy-to-use browser-based access control system that allows users to manage and monitor physical access to sites. It integrates access control, alarm and incident monitoring and comprehensive reporting facilities. The Otis Compass Elevator interface allows information to be passed between the Sateon system and the Otis Compass destination dispatch elevator system, in order to control which destinations within a building each individual can use and to report events back to Sateon. This interface is supported in Sateon Release 2.7 and above. About this guide This document provides information on setting up and monitoring the Otis Compass Elevator interface. It assumes familiarity with Sateon. It is aimed at installers and system managers who are responsible for setting up and configuring interfaces to third-party systems. SATEON 5 Issue 2.0

6 Note: This guide does not provide information on any configuration of the Otis Compass Elevator system that may be necessary. This guide includes the following information: Section 1 Introduction. This section provides an overview of the integration and introduces the Otis Compass concepts. Section 2 Installing up and licensing the Otis Compass Elevator interface. This section explains how to install the Otis Compass Elevator module and upgrade the Sateon licence. Section 3 Configuring the Otis Compass Elevator interface. This section covers setting up the Sateon system to communicate with the Otis Compass system. Section 4 Monitoring activity. This section explains how to view Otis interface events within the Sateon interface and ensure everything is working correctly. Related documents The following Sateon documents may also be useful: The SATEON Installation Guide. This guide explains how to install Sateon, including details of software prerequisites and licensing. The SATEON Personnel Module Guide. Explains how to set up the people who will use the system and the tokens they use to gain access to the site. The SATEON Access Control Guide. Explains how to set up the data in the access control module of SATEON which includes access permissions, time patterns, areas and system hardware. The SATEON Control Centre Guide. Explains the Sateon Control Centre, which allows security staff to view and monitor events, to deal with reported incidents and to manage or control specific elements of the system. The SATEON Event Configuration Guide. Details how to set up the way in which system events are reported, tagged and used within the system. Technical support For further assistance with Sateon, please contact Grosvenor Technology Technical Support as follows: (EMEA): (US): (APAC): Website: ac-support@grosvenortechnology.com ac-ussupport@grosvenortechnology.com apacsupport@grosvenortechnology.com SATEON 6 Issue 2.0

7 Section 1 Introduction This section provides an overview of the Otis Compass Elevator interface and introduces some of the system concepts. For a summary of the Otis Compass Elevator panel interface, see Overview of the integration on page 8. For an explanation of the various elements of the Otis system and terms used, see Specific concepts on page 10. SATEON 7 Issue 2.0

8 Overview of the integration Otis Compass is a destination dispatch elevator system which is designed to manage and control the use of multiple elevators in high-traffic locations. Integration requires a separate, licensable Sateon module which manages communication between the Otis elevator system and the main Sateon access control system. The interface between the Otis Compass Elevator system and the Sateon system is illustrated in the diagram below: In the Otis Compass system, elevator passengers request their destination at a terminal in the lobby, using touch-screens or keypads. The information is forwarded to the controller that manages the bank of elevators. The controller then sends an elevator car to the appropriate floor to collect the passenger, and the terminal display directs the passenger to the designated car. The overall effect is to manage the flow of traffic and reduce waiting and travel times. When the Otis system is integrated with Sateon, passengers use their tokens at readers adjacent to each terminal. Information in the Sateon database defines which destinations they are permitted so their access to certain floors can be controlled. For example, if a person has access to floors only, these will be the only ones selectable. SATEON 8 Issue 2.0

9 It is possible to configure the Otis system to use PIN Entry rather than token reads. When this is supported, the user enters a token number at a keypad rather than using a reader. Note: This is not the same as the use of PINs within Sateon, which requires a PIN to be entered at an attached keypad in addition to a token read, for added security. Error messages are displayed on the terminal screens if the person selects a floor they do not have access to. Note that in some systems there are destination request terminals in one or more elevator cars, for example this may be the case in the goods elevator. Key functionality The Otis interface module within Sateon includes the following functionality: It enables personnel access via elevators to be to be controlled. Access is defined by destinations which may be a floor (such as Floor 15), or where there are two sets of doors on the elevator by floor and side (such as Floor 20, Rear). It enables Sateon to provide access control information to each terminal. It enables a Sateon system user to view the status of each elevator controller and terminal in the system, for example to check if a device is offline. It supports the reporting of elevator-based events within the Sateon Control Centre. It supports segmentation, which is used to define the access of multiple tenants occupying the same building. It supports the provision of different levels of service to passengers based on information contained in the Sateon database. For example, a wheelchair user could be given more time to access the elevator. Prerequisites The only Otis Compass protocol version that is supported is V2.0. The computer that hosts the Sateon Elevator Service requires a network card specifically for the Otis Compass interface. The IP address, subnet and default gateway must be correctly set up. IP Address Subnet Default Gateway: Note that there may be a requirement to put in a static route for this card. Also be aware some network card drivers do not support the old multicast IGMP V2 protocol required by the Otis Compass system. SATEON 9 Issue 2.0

10 The Otis Compass Elevator module is licensed separately. If necessary, an upgraded licence file needs to be installed. For details, see Licensing the Otis Compass Elevator integration on page 17. Specific concepts Some of the specific concepts within the Otis system and the way they are implemented in Sateon are outlined here. For full details, see the Otis Compass documentation. Elevator Controllers and Terminals Passengers request their destination floor at a touchscreen or keypad terminal positioned in each lobby or elevator car. This is known as a Destination Entry Computer (DEC). Note that a DEC is capable of operating with or without Sateon integration and it will always check that Sateon is running; if for any reason Sateon is not running it will operate independently. The DEC sends data to the appropriate controller that manages the bank of elevators. This is known as a Destination Entry Server (DES). The DES sends the appropriate elevator to the required floor to collect the passenger. Note that some Otis Compass systems may include a Destination Entry Redirector (DER) which supports terminals throughout the building. A DER connects to all elevator groups and allows DECs at a common entry point in the building to accept destination requests for any floor in the building. Within Sateon, each DEC is configured as a Destination Terminal. Each DES/DER is configured as a Destination Group. Designation of destinations The Otis Compass system distinguishes between Allowed floors and Authorised floors. An Allowed floor is accessible to all elevator users. The user s credentials do not need to be checked. For example, if the 15th floor in a building is the cafeteria, defining it as an Allowed floor will permit all staff to access it from any other floor without checking access permissions. Access to an Authorised floor requires credentials to be checked. In the case of the Sateon integration the person will need access to the specified reader group that controls access to the floor. The Otis Compass system also has the concept of a Default floor. This means that passengers with valid credentials at a specific terminal are always sent to a specific floor, rather than needing to select a destination. Within Sateon, you can link a destination terminal with a reader group that identifies the default floor. Default floors are not used in all modes (see Operational modes on page 11). SATEON 10 Issue 2.0

11 If the elevator has doors on both sides these can be defined as separate destinations. For example, the system could be set up so that members of the R&D department are permitted to access Floor 8, Front and Rear exits, while someone in Accounts is allowed to access Floor 8, Front exit only. Operational modes Each terminal (DEC) on the system can be set to operate in one of four modes, as described below. For more information, consult the Otis documentation. Mode 1 Default Floor only In this mode, all passengers with valid credentials are automatically sent to a Default floor. The person will be required to present their token to the reader but will not need to select a destination floor on the terminal. As long as access is permitted, Sateon informs the Otis system of the default floor and the appropriate elevator will be sent to pick the person up. Mode 2 Access to Authorised Floors In this mode, all destinations are defined as Authorised floors and require credentials to be checked. The person will be required to present the token to the reader and if they have valid access, Sateon informs the Otis system of the floors permitted for this person. The person can then select a destination floor on the terminal, and an elevator will be sent to pick the person up. Mode 3 User Entry of Destination Floor In this mode, some destinations are defined as Authorised floors (requiring credentials) and some are defined as Allowed floors (credentials not required). The passenger selects a destination floor at the terminal. If the floor selected is an Allowed floor, further authorisation is not required, and an elevator is dispatched to pick the person up. If the floor selected requires authorisation, the person will then be asked to present their token at the reader and Sateon will check their access rights. If the person has access to the selected floor, an elevator is dispatched to pick the person up and they are directed to the appropriate elevator. Mode 4 Default Floor or User Entry of Destination Floor In this mode, passengers with valid credentials are sent to a Default floor, but they may override this default and select an alternative destination. The person presents their token to the reader and Sateon checks their access rights. If they have valid access, Sateon informs the Otis system of the default floor and the elevator will be sent to pick the person up. Within a certain time period (defined within the Otis system) the person can choose an alternative destination. Sateon checks the person s access rights: if the person has access to the selected alternative floor, they are directed to the appropriate elevator. SATEON 11 Issue 2.0

12 Note: In all cases if credentials are required and access is not permitted, an Access Denied message will be sent to the DEC. In situations where destination selection and valid credentials are required, the passenger may present their token first or may select a destination first. The Otis Compass system operates in Mode 3 by default. Modes are defined within a Destination Terminal record; see Configuring specific Destination Terminals on page 26. Levels of service The controllers can also offer different levels of service to passengers based on access information held in the Sateon database. A high-privilege user may be allocated the nearest available elevator and be guaranteed a direct service to their floor; a visionimpaired person may receive voice commands, while a user with restricted mobility may be provided with extended door-opening times. Within the Otis Compass system this information is held as a bitmap field that has flags set to mark information about personnel, such as a person with a disability, a VIP, or someone susceptible to vertigo. Within Sateon this is managed by the use of personnel attributes, which are mapped on to the Otis Compass flags by means of Sateon service settings. For details, see Configuring Service Settings on page 20. Segmentation In the Otis Compass system, segmentation is a means of managing multiple tenants occupying the same building. It provides a way of directing passengers to different elevator cars based on their segment membership: allowing travel within a segment while preventing travel between segments. For example, Company A could lease Floors 4, 5 and 6 (Segment 1), and Company B could lease Floors 7, 8 and 9 (Segment 2). Using segmentation, passengers working for company A would not be assigned to cars that serve the floors of company B and vice versa. Segmentation is known within the Otis Compass system as the Compass Inter-floor Matrix (CIM). Within Sateon, if segmentation is used, it needs to be enabled by means of a Sateon service setting. (See Configuring Service Settings on page 20.) The segments that a destination is part of are defined within a Destination record; see Configuring specific Destinations on page 25. SATEON 12 Issue 2.0

13 Section 2 Setting up and licensing the Otis Compass Elevator interface This section explains how to install the Otis Compass Elevator interface module and upgrade the licence file. For details of installation, see Installing the elevator interface on page 14. For information about licensing, see Licensing the Otis Compass Elevator integration on page 17. SATEON 13 Issue 2.0

14 Installing the elevator interface The Otis Compass Elevator interface module requires a specific database and service; these may not be installed by default. Note: To install optional features, you must use the advanced installer, Sateon Installer.msi. The one-step installer cannot be used. Brief instructions are given here; for full details, see the SATEON Installation Guide. Note: The elevator service and database are generic and can support integrations with different elevator systems. However, they can only be used when an appropriate licence is present. New installations For a new installation you need to run a customised installation to ensure that the elevator options are selected. To ensure the elevator options are included 1. On the release media, navigate to..\installer\sateon\ and run SATEON installer.msi. 2. On the first screen, press Next. 3. After reading the Licence Agreement, select the checkbox to accept the agreement and click Next. The following dialog appears: 4. Click the Customise button. SATEON 14 Issue 2.0

15 5. On the Destination Folder dialog, accept the default or click Change to select an alternative location. 6. Click Next. The Custom Setup dialog appears. In the tree structure, only the databases and services required for core functionality are selected by default. Expand the structure and select the Elevators Database within SATEON Databases and the Elevators Service within SATEON Services. 7. Click Next and continue to follow instructions on the dialogs. 8. Click Install to begin the installation, then when it is completed, click Finish. Existing installations For an existing installation you will need to re-run the installer to add the elevator options. To add the elevator options to an existing installation 1. On the release media, navigate to \Installer\Sateon\ and run SATEON installer.msi. 2. On the first screen, press Next. SATEON 15 Issue 2.0

16 3. Choose Change. 4. In the tree structure, select the features to be installed. Expand the structure and select the Elevators Database within SATEON Databases and the Elevators Service within SATEON Services. Note: When adding features to an existing installation, you must ensure all the options that are already installed are selected, including the services and databases. If you do not do this, the existing features will be removed. 5. Click Next. SATEON 16 Issue 2.0

17 6. Follow the instructions on the dialogs, ensuring you provide exactly the same settings as when Sateon was first installed. 7. Click Change to begin the installation, then when it is completed, click Finish. Note: For multi-tier installations, ensure the service and database are installed on the appropriate servers. What is installed The elements installed are as follows: The Elevators database. The Elevators service and associated executables. These are installed in the default location (C:\Program Files\Grosvenor Technology Ltd (x86)\sateon\services) unless another has been specified. The service should start automatically following installation. If necessary, you can manage it from the Control Panel > Administrative Tools > Services dialog. The Elevator service logs all its activities, enabling you to examine events as they occur and diagnose problems. See Checking logs on page 33. Licensing the Otis Compass Elevator integration The Otis Compass Elevator integration is a separately licensed Sateon feature. For a new installation you need to ensure that the licence includes support for the Otis Compass Elevator interface. If you have added Otis Compass Elevator support to an existing installation, you will need an updated licence file. You can add a new or updated licence from the System Configuration > System Administration > Licensing page within Sateon. For full details on how to add a licence file, see the SATEON Installation Guide. SATEON 17 Issue 2.0

18 For a new installation the licence needs to be validated within 30 days for Sateon to continue to work. Note: If you do not have a valid licence file yet, contact Grosvenor Technical Support as soon as possible. Support for the Otis Compass Elevator Interface is indicated on the Licencing page: SATEON 18 Issue 2.0

19 Section 3 Configuring the Otis Compass Elevator interface This section explains how you need to set up the Sateon system to communicate with the Otis Compass system. For details of the settings that control the Elevators service, see Configuring Service Settings on page 20. For information about configuring readers, see Setting up readers and groups on page 21. For information about setting up the elements of the elevator system, see Setting up the elements of the elevator system on page 22. For other data that needs to be set up, see Other configuration on page 29. SATEON 19 Issue 2.0

20 Configuring Service Settings Service Settings within Sateon define a number of configuration parameters that control the way that particular features work. Usually these are set up correctly when the system is installed and do not need to be amended. A number of these service settings are required for the Otis Compass Elevator integration, and should be set up under the guidance of an Otis engineer and Grosvenor Technology support staff. To view service settings, select System Configuration > System Administration > Service Settings. The settings that are applicable to the Otis Compass Elevator are those in the elevator > Otis hierachy: Segmentation The segmentation enabled setting is used to control segmentation support (CIM). See Segmentation on page 12 for details. By default this setting is turned off; select the checkbox to switch it on. (Note that you also need to set up the segments that each destination is part of: see Configuring specific Destinations on page 25.) Levels of service The userattribute settings are used to map Sateon personnel attributes to Otis Type Descriptor flags which can be used to provide different levels of service. See Levels of service on page 12 for details. SATEON 20 Issue 2.0

21 The default mappings are as follows: Sateon Personnel Attribute Blind or partially sighted Wheelchair or impaired mobility Vertigo VIP Otis Type Descriptor TD02 TD02 TD08 TD04 For specific details of how the descriptors are used in your Otis Compass system, consult the Otis engineer. Additional attributes can be mapped if required, but note that these must be set in the form of GUIDs. Note: When any service settings are changed, you must restart the Elevators Service from the Control Panel > Administrative Tools > Services dialog. Setting up readers and groups We recommend that the readers, reader groups and access groups required by the Otis Compass system are set up before configuring the elements of the elevator system. You need to ensure the following are set up: The readers that are associated with each DEC and the reader groups that they are members of. A reader group for each destination floor. For example: SATEON 21 Issue 2.0

22 Access groups with permissions for the specified reader groups. Access can be restricted by time schedule if required. Setting up the elements of the elevator system within Sateon The various elements of the Otis Compass system need to be configured within Sateon as elements of the Destination Framework within Access Control. This is a generic way of configuring integrations with elevator systems and other destination-based systems within Sateon. It is configured differently for each type of system. For the Otis Compass Elevator system you need to set up the following: A Destination System identifying the Otis Compass system. A Destination Group record for each of the controllers within the Otis Compass system: the Destination Entry Servers (and Destination Entry Redirectors, if used). A Destination record for each potential destination in the elevator system, each floor and if supported, each side. A Destination Terminal record for each terminal (DEC) in the elevator system. Note: Assistance may be required from the Otis engineer. Because the Destination Framework features are generic, Sateon performs very little validation of the input, and in most cases it is vital that data is configured exactly as detailed here. SATEON 22 Issue 2.0

23 Configuring the Destination System Within Sateon, you need to set up a Destination System to identify the Otis Compass Elevator system. To set up the destination system 1. Choose Access Control > Action/Group Management. 2. Choose Destination Systems and click the Create button: 3. On the Basic tab, enter the following fields: Description Interface System Configuration Comms Engine Name of the elevator system; this can be anything but ensure it allows you to easily identify the Otis system. This must be Otis Compass. (Note that this value is case sensitive and must be entered exactly as indicated.) Not used; leave blank. Choose the Comms Engine that the relevant readers are controlled by. 4. Click Save. Configuring Destination Groups Once the Destination System is set up, you need to set up Destination Groups to identify the control elements of the Otis system. You need to create a Destination Group for each Destination Entry Server and each Destination Entry Redirector, if used. All elevators within a Destination Group serve the same destinations. SATEON 23 Issue 2.0

24 To set up a destination group 1. Choose Access Control > Action/Group Management. 2. Choose Destination Groups and click the Create button: 3. On the Basic tab, enter the following fields: Description Group Designation Group Configuration Destination System Name of the new destination group; this can be anything, but ensure it is something that helps you identify it. For a DES, this must be the identifying DES number which will be a number between 1 and 8. For a DER, this must be the identifying DER number which will be a two-digit number in the form 10, 20, 30 and so on. Leave this blank. For example, a DEC record may be set up as follows: Choose the previously defined Destination System. For a DER, the record may be set up as follows: SATEON 24 Issue 2.0

25 4. Click Save. Configuring specific Destinations You need to set up a Destination record for each destination served by an elevator group. Generally each floor is a destination. However if the elevator has front and rear doors in use on a particular floor, then a separate Destination record is required for each. To set up the destination 1. Choose Access Control > Action/Group Management. 2. Choose Destinations and click the Create button: 3. On the Basic tab, enter the following fields: Description Destination Group Reader Group Default Destination Reader Group Floor Designation Side Designation Destination Configuration Name of the destination; ensure this clearly identifies the destination. Choose the Destination Group that identifies the appropriate Controller. Select the reader group that defines access to this floor. This does not need to be set if this destination is Allowed (accessible to everyone without authorisation). This is used when passengers are directed to a particular default destination. Select the appropriate reader group that defines access to the default destination. This only needs to be set for Mode 1 or Mode 4, which use the concept of a default destination. Enter a number to identify the floor. The Ground floor is indicated by 0. Indicate whether the front or rear doors are used: F for the front door, R for the rear door. Leave blank unless this elevator system uses segmentation (CIM). If segmentation is used, define the segments the floor belongs to, for example Segment = 2. Use a format such as Segment = 1 2 to specify that this floor is a member of more than one segment. SATEON 25 Issue 2.0

26 4. Click Save. Configuring specific Destination Terminals You need to set up a Destination Terminal record for each terminal (DEC) in the elevator system. Each terminal is associated with the controller that manages it. To set up the destination terminal 1. Choose Access Control > Action/Group Management. 2. Choose Destination Terminals and click the Add button: 3. On the Basic tab, enter the following fields: Description Destination Group Reader Floor Designation Terminal Designation Terminal Configuration Name of the terminal/dec; ensure this clearly identifies the terminal. Choose the Destination Group that identifies the controller/des that manages this terminal. Choose the reader that is associated with this terminal/dec. A number signifying the floor that this terminal is situated on. Note that the Ground Floor is 0. Specify the IP address of the terminal. This field is used to set the DEC operational mode and enable PIN entry. SATEON 26 Issue 2.0

27 To specify a mode, use the format: Mode = n For example, Mode = 4 sets the DEC to use mode 4. Note: Mode 3 is the default and will apply if no mode is specifically set. To specify that PIN entry is to be used by the Otis Compass system, use the format: PinEntry = true Note: PinEntry in this context refers to entering a token number at a keypad rather than a reader; it is not the same as the Sateon Token + PIN feature which requires personnel to enter a PIN at a keypad in addition to their token being read in order to gain access. If you enter both a Mode and a PinEntry setting in the Terminal Configuration field, they must be separated by a comma. The following example shows Terminal Configuration separated by a comma: SATEON 27 Issue 2.0

28 4. If your configuration supports Allowed Destinations floors that are permitted without authorisation or presentation of a token choose the Allowed Destinations tab. Select any floors that are to be permitted without assigned permissions. 5. Click Save. SATEON 28 Issue 2.0

29 Other configuration Access permissions Personnel need to be granted the correct access permissions so that they can access the floors and readers they need. Ensure that personnel are granted appropriate access to the readers/reader groups associated with the elevator terminals (DECs). Ensure that personnel are granted appropriate access to the reader groups for each destination floor that they are permitted to access. Personnel attributes Ensure that where appropriate, you have set up specific attributes for personnel such as sight limitations or impaired mobility. These attributes are mapped to flags in the Otis system to ensure that the correct service is provided, for example a vision-impaired person may receive voice commands. This information is set on the Personnel record: SATEON 29 Issue 2.0

30 Note: By default no Type Descriptor is mapped for personnel with the Deaf or hard of hearing attribute, although this can be configured manually if required. See Configuring Service Settings on page20. SATEON 30 Issue 2.0

31 Section 4 Monitoring activity This section explains how to monitor the Otis Compass Elevator operation and ensure that everything is working correctly. For a list of events raised by the Event Gateway, see Elevator interface events reported in Sateon on page 32. For details of viewing and managing information about Event Gateway interfaces, see Monitoring the Otis elevator elements on page 33. For information about monitoring logs in case of problems during operation, see Checking logs on page 33. SATEON 31 Issue 2.0

32 Elevator interface events reported in Sateon Once the system is configured and in use you will see events reported on the Control Centre page. This information includes the destination requested by the user and the elevator car that is assigned. For example, if a person s token is valid and they select a valid floor, events may appear as follows: Note that the Valid Read and Valid Destination messages may in the reverse order if the person selects a destination before their token read. If the attempt fails because the person selects a floor that they do not have access to, events as follows may appear: Destination Group Events Events that may be raised on a Destination Group are as follows: Event Destination Valid Read Destination Invalid Read Explanation Indicates that a valid token read has occurred at the elevator. Indicates that an invalid token read has occurred at the elevator. Note that there will also be reader events associated with the specific reader. Destination Terminal Events Events that may be raised on a Destination Terminal are as follows: Valid Destination Event Explanation Indicates that the destination selected is permitted for this person. SATEON 32 Issue 2.0

33 Invalid Destination Event Explanation Indicates that the destination selected is not permitted for this person. The messages returned from the Otis Elevator system may include additional information. Note that you can configure the Sateon system to report any of the events raised from the Otis system in order to flag any issues. For example, if the remote system was disconnected, you could configure the notification system to send an to an engineer, or you configure an event to be reported as an incident. See the Event Configuration Guide for more information. Monitoring the Otis elevator elements Destination Groups (representing DES/DER devices) and Destination Terminals (representing DEC devices) will appear in the Devices section of the Control Centre in Sateon. If the Otis Compass and Sateon are communicating correctly you should expect the State property of all devices to be Connected. Configuration errors can prevent successful communication between the Otis Compass Elevator system and Sateon. Therefore when the interface is first set up, and if any changes are made, we advise that you check the Control Centre page to ensure connection is made correctly. Checking logs In the case of problems during operation, such as data not being imported, we recommend that you check the Elevator Service logs. You can configure and monitor the logs using the SATEON Real-Time Diagnostics Tool. This utility is generally installed as part of a standard Sateon installation and is located in the..grosvenor Technology Ltd/SATEON/Utilities folder. SATEON 33 Issue 2.0

34 To set up logging using the Real-Time Diagnostics tool 1. Locate and open the SATEON Real Time Diagnostics (by default installed in Program Files (x86) Grosvenor Technology Ltd > SATEON > Utilities). 2. In the Sources pane, select the checkbox for the Elevator service: 3. In Event Options, select checkboxes against options that allow more detailed logging: Enable Debug Channels Enable Verbose Messages Enable Raw Exceptions Select if you want detailed debug messages. Select if you want verbose logging (more detailed messages). Select this if you want to display exceptions raised by Sateon. 4. Once options are set, events will appear in the main screen as they occur. When you select a specific message, more information will appear in the pane at the bottom of the page. Note: Once any issues are resolved, you can clear the Debug and Verbose checkboxes if you no longer need this level of reporting. You can also monitor messages using the Windows Event Viewer (Control Panel > System and Security > Administrative Tools). For full details, see the SATEON Administration Guide. SATEON 34 Issue 2.0