OpenComms Nform Software GUIDE SPECIFICATION for Network Alarm Management Software 1.0 GENERAL 1.1. SUMMARY The Alarm Management Software shall centrally monitor multiple distributed devices using the customer's existing network infrastructure. The monitored devices shall be capable of transmitting alarm notifications to the central management system using SNMP traps. The centralized management system shall receive traps from these monitored devices and display the alarm notification in a graphical user interface, which shall enable the user to centrally manage the alarm(s). Alarm management shall include alarm processing, local alarm receipt notification such as generating an audible alarm, and notification to remote users. The software shall provide secure access to the viewer interface and will be capable of operating and managing alarms without the viewer running. The viewer interface shall enable the user to build a custom defined navigation tree, which will allow the end user to logically group distributed devices in the centralized viewer interface. The custom defined navigation tree will also provide support for custom graphics. Configuration of the devices and graphics defined in the custom navigation tree shall be through a drag and drop interface, enabling the user to efficiently build logical organizational groupings of devices. The software shall support tiered levels of access, limiting authenticated users access to configuration information. 1.2. STANDARDS 1.2.1.SNMPv1 1.2.2.TCP/IPv4 1.3. SYSTEM DESCRIPTION 1.3.1.Operating System Support: The network alarm management software shall be compatible with the latest versions of Windows NT server and workstation, Windows 2000 server and workstation, and Windows XP Professional 1.3.2.Minimum Operating System Requirements: The computer system on which the automated shutdown software is installed must meet the following minimum requirements; support for TCP/IP, DNS, and the computer must be physically connected to the network. 1.3.3.Network Alarm Management Software Architecture: The software shall support a front-end graphical interface and a background process, which shall monitor all specified network connected equipment 1.3.3.1. Front-end Graphical Interface: The front-end graphical interface, or Viewer, will enable the user to centrally view distributed device status information, configure alarm and event notifications, configure the device navigation interface, integrate with HTML viewers, manage and log events, and authenticate user access. 1.3.3.2. Background Process: The software will run a background process, which will operate independent of the front-end viewer and will communicate to the managed devices through a network connection. 1.3.4.Centralized Management: The application will run on a computer connected to the network on which the managed devices are communicating. All managed devices shall report device status information to this computer system for centralized event and notification management. All distributed devices shall be viewable from the computer running the centralized application. 1.3.5.Device Navigation Interface: This application will support a navigational interface, which shall enable the user to logically define the layout of the managed devices. This navigational interface will allow the user to connect to any managed device and view status and event conditions. SL-28083 10/03 1.3.5.1. Security: The navigational interface shall provide authenticated user access, presenting a user with a login screen from which a user must be authenticated before allowing access to any product functionality. 1.3.5.1.1. Authenticated Access: The application shall support authenticated access for two user types. 1.3.5.1.1.1. Administrator: A user who logs in as an Administrator shall receive full access to the application, including all configuration capabilities. 1.3.5.1.1.2. Power User: A user who logs in as a Power User shall receive access rights to view devices and manage alarms. All configuration capabilities will be disabled for the Power User. 1.3.5.1.2. Auto Logoff: The application shall support the ability to automatically log a connected user off the system, locking the user out of the application. The user will be required to authenticate to the application to re-establish access to the viewer interface 1.3.5.1.2.1. User configured logoff timer: A user configurable timer will enable the Administrator to set the amount of idle time that will lock a user out of the application. 1.3.5.2. Navigation Tree: The application shall provide an interface that will enable the user to view all monitored devices in a logical, user defined structure. Every monitored device will have a status viewing interface available from the defined structure, as well as alarm management from each device. 1.3.5.2.1. Custom Device Navigation: The application will allow the user to design and build a custom, user defined navigational interface. 1.3.5.2.1.1. Navigation Builder: The monitoring application will allow the user to add, remove, and move managed devices and graphics within, and from the user built navigational tree interface. 1.3.5.2.1.2. Custom Graphics: Custom designed, HTML graphics will be supported in the user built navigational tree interface. 1.3.5.2.2. Device Status Monitoring Interface: From the navigation interface, users will be able to select a device and launch a view of the current device status 1.3.5.2.2.1. HTML Page: Any managed device that supports an HTML interface will be capable of being viewed through the navigation interface in its native HTML format. 1.3.5.2.2.1.1. Full Screen Browser Interface: The application Viewer will allow the user to view HTML images in full screen mode. 1.3.5.2.2.2. SNMP Only Page: Monitored devices that only support an SNMP communication interface shall be presented in the Viewer as a data table, showing SNMP variable data requested from the device and the values collected during the most recent poll. 1.3.5.2.2.2.1. SNMP Device Configuration: The viewer shall support an interface which will enable the user to configure readwrite SNMP variables available on managed devices. 1.3.5.2.2.2.2. Data Definition: The application shall be capable of displaying SNMP variable description information through the application viewer. 1.3.5.3. Alarm Management: The application shall be able to receive SNMP traps from multiple managed devices over the network. SNMP traps received by the application will be logged as alarms and presented to the user through the viewer interface. Event actions and management can be performed by the end user on logged alarms. 1.3.5.3.1. Date/Time Generation: All logged alarms shall be date and time stamped upon receipt. 1.3.5.3.2. Address: The IP address of the device that generated the SNMP trap will be stored with the logged alarm. SL-28083 10/03 1.3.5.3.3. Name: The name of the device that generated the SNMP trap will be stored with the logged alarm. 1.3.5.3.4. Alarm Message: A user configurable text message will be stored with the logged alarm. 1.3.5.4. Alarm Status Management: The application will enable all logged alarm messages to be managed by the end user. Management action on alarms shall include alarm acknowledgement, deletion, and adding comments to specific alarm messages. 1.3.5.4.1. Acknowledge Alarm: A user initiated action to acknowledge receipt of an alarm shall be supported by the application. 1.3.5.4.2. Delete Alarm: A user initiated action to delete an acknowledged alarm shall be supported by the application. 1.3.5.4.3. Multiple Alarm Management: The application shall support the acknowledgement and deletion of multiple alarms at the same time. 1.3.5.4.4. User Defined Color Scheme: Alarm shall be able to be color- coded based on the status of the alarm. 1.3.5.4.5. Alarm Silence Button: The application shall be able to notify a local user through the default OS notification sound that a new alarm has been added. The viewer interface will allow the user to silence this alarm when enabled. 1.3.5.5. Add/View Alarm Comments: Each alarm shall support the addition of comments to the alarm record. 1.3.5.5.1. Add comments to an alarm: The viewer will provide an interface which will allow the user to add comments to an alarm record. 1.3.5.5.2. Modify Alarm Comments: The application will allow the user to view, edit, or delete existing comments tied to an alarm record. 1.3.6.Notification: The application shall support notification actions, which shall be based on managed device events. 1.3.6.1. Event Action(s): The application shall allow the user to configure actions, which will be executed upon the receipt of the event. 1.3.6.1.1. Configuration: All actions shall be configurable independent of the defined events. 1.3.6.1.2. Assignment: The application will allow the user to map configured actions to specific events on specific managed devices. 1.3.6.1.3. Advanced Management: The user shall be able to configure events for active alarms and the alarm cleared event, or only for the active alarm condition. 1.3.6.2. Local Alarm Notification: When the user is connected to the application through the Viewer interface, local notifications shall be available to alert the user of new alarm conditions. 1.3.6.2.1. Default PC system beep upon alarm receipt: The user will be able to configure the application to execute the default PC system sound upon receipt of a new alarm. 1.3.6.2.2. Launch audible sound file: The user will be able to configure the application to execute a user defined audible sound file upon receipt of a new alarm. 1.3.6.2.3. Propagate viewer to application foreground: The user will be able to configure the application to propagate the application viewer to the foreground of the operating system desktop upon receipt of a new alarm. 1.3.6.2.4. Task bar notification: The user will be able to configure the application to notify a user of a new alarm condition by blinking the task bar icon when the Viewer is minimized. 1.3.6.2.5. Command Action: The user will be able to configure the application to execute a command file upon receipt of a new alarm. Command action shall be configurable by device and event. SL-28083 10/03 1.3.6.3. Remote Alarm Notification: The application will allow the user to configure notification actions through e-mail that will be executed upon receipt of new alarms as defined by the user. Remote alarm notifications shall execute without requiring the application Viewer to be running. 1.3.6.3.1. E-mail: The user will be able to configure the application to send email notifications to specified users upon receipt of a new alarm. E-mail actions shall be configurable by device and event. 1.3.6.4. Third-party application alarm monitoring: The application shall support monitoring third-party devices through open standard protocols, such as SNMP. 1.3.6.4.1. File Write Action: The application shall allow received alarms to be written to a file in comma-delimited format, which shall be exportable into a third-party application for analysis. File write actions shall be configurable by device and event. 1.3.7.Device Management: Monitored devices shall be manageable through the application Viewer interface. Management options shall consist of alarm management, device configuration, and status polling. 1.3.7.1. SNMP alarm management: Monitored devices shall be configured to send alarm notifications to the application. Management of alarms and alarm notifications shall be configured through the Viewer interface. The user will be able to acknowledge new alarms, delete alarms, and add comments to alarms. The user will also be able to configure notifications, which shall be executed upon receipt of defined alarms. 1.3.7.1.1. Multiple Alarms: The user shall be able to manage multiple alarms at the same time. 1.3.7.2. Device Configuration: The application shall allow the user to perform SNMP Set operations on monitored devices that allow SNMP write capabilities by the application. 1.3.7.3. Device Status Polling: The application shall support device status polling which will actively poll each monitored device and upon detection of communication loss or active alarm state, present a visual notification to the user in the Viewer interface. 1.3.8. License Key Management: The application shall provide an interface, which will allow the user to manage installed licenses, permitting control over the number of devices the application can monitor. 1.3.8.1. Installation Wizard: The installation and management of license keys shall be a user friendly, wizard based application that will lead the user through the management process. 1.3.8.2. Display Installed License Information: The application shall be able to display the number of installed license keys, number of devices capable of being supported by the application, and the number of devices currently monitored. 1.3.9.System Logging: The application will track and log all system activity when the program services are running. The logged system activity shall be stored on the computer system as text files for review and analysis. SL-28083 10/03