Installation and Operation Manual
Contents 1 Introduction... 1 1.1 Requirements... 1 2 Authentication... 2 3 Installation... 3 3.1 Description of LED Indications... 3 3.2 Internal Inputs and Outputs... 3 3.3 Error Relay Output... 4 3.4 Unlicensed Mode... 4 3.5 Configurations to make the AMS Receive Pagings from A-bus... 4 4 AMS Home... 5 4.1 AMS Functions... 5 4.2 ELISE Functions... 6 5 Client Administration... 7 6 Presentation on the Alarm Management Client... 8 6.1 AMC Alarm Status Window... 8 6.2 Editing Translation Tables from the AMC... 8 6.3 Communication between AMS and AMC... 9 6.3.1 Creating a Presentation... 10 6.3.2 Taking care of a Presentation Response... 10 6.3.3 Detecting Communication Error between AMS and AMC... 10 7 Related Documents... 11 Appendix A: Services... 12 Appendix B: Installation... 13 Appendix C: Document History... 15
1 Introduction The AMS is an Alarm Management Server based on the ELISE hardware. It can be programmed to take care of alarms and other events from the system. An event consists of a set of elements that contain data. The information that the AMS receives, for example from the System 900 A-bus, is converted to an internal communication protocol before it is handled. The engine in the AMS is the Event Handler, that recognizes an incoming event and executes actions accordingly. Which actions that are executed depend on the data in the incoming event and the system configuration. For more information of the Event Handler, see Programming Guide, Event Handler, TD 92329GB. System 900 Other systems Event Handler AMS Presentation Server AMC AMC Block Event Handler database Block Configuration database Configuration Interface 1. Figure Figure 1. Communication between the Event Handler, the databases, the configuration, and presentation clients. 1.1 Requirements Ethernet (10baseT or 100baseT 1 ) Microsoft Internet Explorer 5.0 or later (needed for installation, administration and configuration) 1.To be able to connect a 100baseT Ethernet the hardware ELISE2 is required. 1
2 Authentication All administration and configuration of the AMS is done from a web browser. In order to access the pages a user name and password have to be given. IMPORTANT: The default passwords have to be changed, else anyone with knowledge of the password and IP address can access the administration and configuration pages and make changes. There are five different users in the AMS; admin, sysadmin, user, loguser, and ftpuser. User name Default password Application admin changeme Administration and simple troubleshooting, configuration of the Event Handler, and view, delete and download log. sysadmin setmeup Administration and advanced troubleshooting, configuration of the Event Handler, and view, delete and download log. user password Configuration of the Event Handler, and view, delete and download log. loguser password View, delete and download log. ftpuser changemetoo Upload/download files to/from the AMS. The tasks for the users user, loguser, and ftpuser are described later in this document. 2
1 8 1 8 Installation and Operation Manual 3 Installation This chapter is a complement to Installation Guide, ELISE2, TD 92232GB. If the first version of the ELISE hardware is used, see Appendix B for installation instructions. 3.1 Description of LED Indications There are a number of LEDs on ELISE that indicate the status of the software, see figure 2. These indications are software dependent and are presented in this chapter. For information regarding indications by other LEDs, see the ELISE Installation Guide. SW4 LED2 LED3 LED4 LED5 LED1 J1 SW2 LED2 LED5 BAT1 SW3 IC1 6 J22 J2 5 J16 1 IC24 1 J9 J10 J11 S3 J12 J6 LED6 LED7 4 1 2 J14 J15 J4 1 6 J16 J7 J8 J11 J12 J13 J20 J5 J6 1 2 J14 S4 1 2 J24 S5 1 4 1 4 S1 S2 2. Figure Figure 2. Location of the LEDs indicating the status of the AMS LED # LED status Indication LED2 ON Paging waiting in queue to A-bus OFF No pagings in queue. LED5 ON The AMS applications are up and running. OFF Problems when starting the applications, check the log files on the AMS Administration web page for more information. 3.2 Internal Inputs and Outputs The AMS has two internal inputs and two open-collector outputs (J16, see figure 2 above), that can be triggered and activated in the configuration. 3
3.3 Error Relay Output The error relay output (J14) can be used to supervise if the AMS is operating. When the AMS starts, the error relay operates. The error relay releases when the AMS is shutting down or rebooting. If the error relay output opens or closes on actual relay status depends on how the jumper J15 is set, see Installation Guide, ELISE2, TD 92232GB. 3.4 Unlicensed Mode When needed, the AMS can be started in unlicensed mode. How to set the AMS in different operation modes is described in the ELISE Installation Guide. The AMS will have full functionality for 2 hours in unlicensed mode. After that, the AMS needs to be restarted either physically from the unit or from the AMS administration web page. How to set the AMS in unlicensed mode is described in Installation Guide, ELISE2, TD 92232GB. 3.5 Configurations to make the AMS Receive Pagings from A-bus The AMS can receive pagings that are sent on the A-bus. 1 Configure the Central Unit in System 900 to distribute pagings to the AMS. 4
4 AMS Home This page will be opened when the AMS IP address is entered in the web browser address field. 3. Figure Figure 3. AMS and ELISE functions Different users have access to the AMS and Elise functions. If the same person should work with both, two browsers can be used to avoid log on every time one wants to switch between the different pages. 4.1 AMS Functions With AMS functions, the Event Handler can be configured, an overview of existing configuration can be shown, administration of the database can be done, and log files with information about the configuration and executed actions viewed. The user name to log in to the AMS functions is user and the password is password. Note: It is recommended to change the password. The password can be changed on the following page http:/xxx.xxx.xxx.xxx/admin/public/user_chpass.shtml, where xxx... is the AMS IP address. Event Handler On this page you can configure; triggers, actions, add or delete elements etc. See description in the Programming Guide, Event Handler, TD 92329GB for details. Overview A printable listing of current configuration. It is possible to follow the flow of the configuration by clicking the links in the listing. 5
Admin Database In Admin Database, the contents of the Configuration and Block databases can be updated, restored, and backed up. See 5 Client Administration on page 7 for more information. View log All changes in the configuration of the AMS are written to the log. It is also possible to write information to the log, for example when a trigger is activated. For more information about the log file and its content, see the chapter Event Log File in the Programming Guide Event Handler, TD 92329GB. Admin Client The configuration of the Alarm Management Client (AMC) can be backed up and restored. See 5 Client Administration on page 7 for more information. 4.2 ELISE Functions Administrate With ELISE Functions the network and system setup of the AMS can be administrated. It is also on these pages that the passwords for different users are changed. 6
5 Client Administration The configuration of the AMC can be backed up and restored from the client administration page. Locations and users are backed up separately. For locations, all maps that are connected to each location code are saved. For users, all user settings are saved. It is also possible to return to original user settings, the factory user settings. Translation tables are backed up together with the AMS configuration. The Alarm History in the AMC can be cleared from the Client Administration. 7
6 Presentation on the Alarm Management Client This chapter describes the connection between the AMS and the Alarm Management Client (AMC). 6.1 AMC Alarm Status Window Below, it is described which information from the blocks in the AMS that will be shown in the AMC Alarm Status window. AMC Information AMS Block and Element Time: [out]presentation/alarm/:time Alarm Type: [out]presentation/alarm/:description* Name: [out]presentation/:identity* Number: [out]presentation/identity number Location: [out]presentation/alarm/:location{1}/ Description* Time Since Location: [out]presentation/alarm/:location{1}/time Previous Location: [out]presentation/alarm/:location{2}/ Description* Time Since Previous Location: [out]presentation/alarm/:location{2}/time Subject: [out]presentation/message/:subject Body: [out]presentation/message/:body *These values have to be translated in the AMS to display correctly. Translations that have to be done in the AMS in order to display the information correctly in the AMC. The destination element is the one specified above. AMC Information AMS Block and Element Translation Table Alarm Type [in]alarm/:type Alarm types Name [in]alarm/delivery/source address/user Alarm units Location [in]alarm/:location{1}/code Location descriptions Previous Location [in]alarm/:location{2}/code Location descriptions 6.2 Editing Translation Tables from the AMC It is possible to edit the Translation Tables for Alarm Units, Alarm Types, and Locations from the AMC. To be able to do this the Translation Tables in the AMS have to have predefined names: Translation Table name Alarm units Alarm types Location descriptions What to translate Alarm units Alarm types Location codes 8
6.3 Communication between AMS and AMC A Presentation Server is one of the parts of the AMS. The Presentation Server controls all communication with the presentation clients (AMC). The Event Handler has to be configured to send information to the server, and also to confirm the actions taken in the AMC (acknowledge and reset of alarms). When the server gets the presentation block from the Event Handler, it notifies the client that there are new information to display. When the server receives an acknowledge or reset request from the client, it sends a presentation response block to the Event Handler. When the Event Handler receives the response, it sends an updated presentation to the server. The server notifies the client that there are new information to display. Event Handler Presentation Server Client Presentation Notification Presentation Response Acknowledge Request Presentation (updated) Notification Presentation Response Reset Request Presentation (updated) Notification 4. Figure Figure 4. Communication flow between the Event Handler, Presentation Server, and Presentation Client. 9
6.3.1 Creating a Presentation The Presentation block includes the identity of the alarm sender, an Alarm block, and an Interactive Message block. On an incoming alarm, the easiest way is to copy the complete block [in]alarm to [out]presentation/alarm. Then make the translations needed, see 6.1 AMC Alarm Status Window on page 8 for more information. Add an acknowledge response alternative to the Interactive Message. See Appendix A in the Programming Guide, Event Handler, TD 92329GB for a detailed explanation. 6.3.2 Taking care of a Presentation Response The acknowledge and reset request from the AMC is sent in an Presentation Response block. Identify the response and send an updated Presentation block to the AMC. See Appendix A in the Programming Guide, Event Handler, TD 92329GB for a detailed description, and also how to acknowledge or reset the presentation from a Pocket Unit. 6.3.3 Detecting Communication Error between AMS and AMC If the AMS detects that the connection to an AMC is lost, an Application Log Report block will be sent to the Event Handler. The block will have the following content: Element name Application name Level Code Application specific/type Application specific/data Application specific/information text Element value PresentationServer 3 (Error) 3 (Lost communication to subsystem) 2 (AMS Status Code) LostClient Information about which user that was logged on to the client that was lost. 10
7 Related Documents Data Sheet, Alarm Management Server Data Sheet, Alarm Management Client Installation Guide, ELISE (first version of ELISE hardware) Installation Guide, ELISE2 Installation and Operation Manual, Alarm Management Client Programming Guide, Event Handler TD 92046GB TD 92144GB TD 92020GB TD 92232GB TD 92145GB TD 92329GB 11
Appendix A: Services S900 This service should be used for External Interfaces that send blocks to System 900. PresentationServer DECT This service should be used for External Interfaces that send blocks to the Alarm Management Client (AMC). This service should be used for External Interfaces that send blocks to the Integrated Message Server within the Ascom 9d System. EventHandler IO This service should be used by other modules that addresses the AMS over the LAN. This service should be used by the External Interfaces that are used when activating the AMS outputs. 12
Appendix B: Installation This chapter refers to the first version of the ELISE hardware and is a complement to its ELISE Installation Guide, see also Installation Guide, ELISE (first version of ELISE hardware), TD 92020GB. Description of LED Indications There are a number of LEDs on ELISE that indicate the status of the software, see figure 5. These indications are software dependent and are presented in this chapter. For information regarding indications by other LEDs, see the ELISE Installation Guide. LED05 LED01 LED08 S02 LED14 J09 LED05 IC12 LED15 LED16 1 B S04 SW01 LED14 LED02 LED03 Compact Flash J14 J08 2 SW02 J07 1 S01 J08 1 2 A B LED04 S07 J01 S08 J02 ETH S05 S06 J06 232 900 900 J03 J04 J05 1 1 1 6 6 4 5. Figure Figure 5. Location of the LEDs indicating the status of the AMS LED # LED status Indication LED05 ON The AMS applications are up and running. OFF Problems when starting the applications, check the log files on the AMS Administration web page for more information. LED06 - Not used by the AMS LED07 - Not used by the AMS LED08 - Not used by the AMS 13
Internal Inputs and Outputs The AMS has two internal inputs and two open-collector outputs (J04), that can be triggered and activated in the configuration. Error Relay Output The error relay output (J08) can be used to supervise if the AMS is operating. When the AMS starts, the error relay operates. The error relay releases when the AMS is shutting down or rebooting. Unlicensed Mode When needed, the AMS can be started in unlicensed mode. How to set the AMS in different operation modes is described in the ELISE Installation Guide. The AMS will have full functionality for 2 hours in unlicensed mode. After that, the AMS needs to be restarted either physically from the unit or from the AMS administration web page. Configurations to make the AMS Receive Pagings from A-bus The AMS can receive pagings that are sent on the A-bus. 1 Configure the Central Unit in System 900 to distribute pagings to the AMS. 14
Appendix C: Document History C.1 Version A: Upgrade from 3.00 to 3.10, December 2002 New chapter with information about authentication, see 2 Authentication on page 2 for more information. How the log is displayed can be customized, see the chapter Event Log File in the Programming Guide Event Handler, TD 92329GB for more information. Possibility to clear Alarm History in the AMC, see 5 Client Administration on page 7 for more information. Correction of alarm types in the Alarm block, see Appendix B in the Programming Guide, Event Handler, TD 92329GB for more information. Added information about how the AMS is addressed over the LAN, see Appendix A in the Programming Guide, Event Handler, TD 92329GB for more information. C.2 Version B: Upgrade from 3.10 to 3.20, July 2003 Licence information moved from this document to the ELISE Installation Guide. New parameter in the User Log, see the chapter Customizing the View of the Log in the Programming Guide Event Handler, TD 92329GB. Possibility to make a selection of elements with a new type of Element Assignment, see Element Assignments for an Event Trigger in the Programming Guide, Event Handler, TD 92329GB. Full support for combined locations from base stations and DECT beacons, see Appendix B, Location Data in the Programming Guide, Event Handler, TD 92329GB. Possibility to handle Battery warning from Pocket Units, see Appendix B, Application Log Report, in the Programming Guide, Event Handler, TD 92329GB. C.3 Version C: Upgrade from 3.20 to 3.21, September 2003 Possibility to add a selection of elements to another existing selection, see Element Assignments for an Event Trigger in the Programming Guide, Event Handler, TD 92329GB. As the changes from version B to C in this document was minor and also due to the fact that version B never was published in the Technical Reference Library, the change bars indicates all changes that have been made since version A. 15
C.4 Version D: Upgrade from 3.21 to 4.00 (3.30), October 2003 Installation instructions for the ELISE hardware released autumn 2003, see 3 Installation on page 3. Installations instructions for the old hardware is moved to Appendix B. Possibility to trigger activation on AMS internal inputs and to activate AMS internal outputs, see Appendix B, Input Activity and Output Activity in the Programming Guide, Event Handler, TD 92329GB. Please note that there has been a protocol change in the Input Activity block, which makes it necessary to update existing configurations for Input Activity before they can be activated. A user defined external interface for the internal outputs has been added to the default database, see External Interfaces in the Programming Guide, Event Handler, TD 92329GB for more information. Possibility to initiate conference calls and speech monitoring, see Appendix B, Call Setup in the Programming Guide, Event Handler, TD 92329GB. Possibility to receive availability information for Pocket Units, see Appendix B, Availability Blocks in the Programming Guide, Event Handler, TD 92329GB. C.5 Version E: Upgrade from 4.00 to 5.01, June 2004 This version of the AMS is the first that supports the Enhanced System Services (ESS). The AMS clock can be synchronised with an NTP server, for example ESS. Special location alarms are reported as a single Location Data block instead of an Alarm block (implemented in AMS 4.00 but added to the documentation in this release). See Appendix B, Alarm and Location Data in the Programming Guide, Event Handler, TD 92329GB for more information. It is possible to make a numeric evaluation of the definition string before it is written to the source element, see Assignments in the Programming Guide, Event Handler, TD 92329GB for more information. Use of the Unite Name Server (UNS) has been implemented. The set up of the UNS is made in the AMS administration pages. Default External Interfaces that are used for message delivery has been changed to use the UNS by default. It is also possible to create User Defined External Interfaces that uses the UNS. See External Interfaces in the Programming Guide, Event Handler, TD 92329GB for more information. Increased possibility to select which statuses that should be requested when a block has been transmitted, and also to specify number of times the AMS should try to transmit the block. See External Interfaces in the Programming Guide, Event Handler, TD 92329GB for more information. The Application Log Report block has been redesigned. This means that for example the Pocket Unit address of a unit that reports battery warning is reported differently. Lost AMC clients and System 900 module status are reported in two different ways; as before in the Data element and in the new Code element. See Appendix B, Application Log Report in the Programming Guide, Event Handler, TD 92329GB for more information. The AMS can from this version control the communication on the A-bus. 16
C.6 Version F: Upgrade from 5.01 to 5.10, December 2005 The Configuration of the Event Handler is removed from this document into a separate document, Programming Guide, Event Handler, TD 92329GB. In the Programming Guide, Event Handler, TD 92329GB, the chapter Definition, a new combobox with predefined values for elements appears for some of the destination elements. In the Programming Guide, Event Handler, TD 92329GB, the chapter Activation for an Event Trigger, a new combobox Comparison type has been added. In the Programming Guide, Event Handler, TD 92329GB, the Appendix B Addressing Blocks, and additional information has been added in; Destination Address, Source Address, Exclude Address, Sender Address, Status Address and Application Address. In the Programming Guide, Event Handler, TD 92329GB, a new block has been added in the Appendix B, Token Data Blocks. C.7 Version G: Upgrade from 5.10 to 5.20, Mars 2006 The chapter 5 Database Administration and the chapter 6 AMS Log File has been removed from this document. The information is now in the Programming Guide, Event Handler, TD 92329GB. The AMS Log File has also been renamed it is now called Event Log File. C.8 Version H: Upgrade from 5.20 to 5.50, 22 December 2010 No AMS functionality changes. 17