Utility Network Operational Manual Innovatec Utility Software System Organization and Requirements Compuware Corp. 08/09/99 11:13 AM Version 0.
Table of Contents 1 Open Issues .................................................................................................................................................. 3 2 Introduction.................................................................................................................................................. 3 3 Primary Requirements................................................................................................................................. 4 3.
Open Issues What type of location information will we use (e.g., lat, long, elevation, pole #) for gateways, relays and meters? What tool will we adopt for network RF planning, and how will we interface the rest of the system to it? Introduction The Enterprise Network and Internet Communications (ENICS) system is a set of software applications that allow either utilities or Innovatec acting as a service bureau to manage and operate an Innovatec communications network.
Primary Requirements Primary requirements are those that ultimately come from the customer or are dictated by the basic nature of the application. Supported Databases For the purposes of this specification, the databases in the system are classified into internal and external databases. Internal databases are those that will be built into a stand alone Innovatec system. External (or legacy) databases are those that are supplied by a particular Innovatec customer or a particular 3rd party application.
Architectural Constraints It shall be possible to distribute user interface, database and server functions over multiple machines. It shall be possible for users to remotely access the interactive utility programs from remote desktop computers. It shall be possible to site the WAN interface hardware on a machine that is physically separate from the machine(s) that host the databases and are generally used for network maintenance and other functions.
Authorization shall be supported by access control lists. It shall be possible to assign permissions on a user by user, utility by utility (for external data distribution) and application by application basis. Thus, a user might be allowed full access to the interactive meter reader, but no access to the network configuration manager. All ENICS applications shall consult the access control list before performing any operation that might be forbidden by the access control list.
address as a legitimate machine that is the target for external data distribution. This cannot be defeated using firewall configuration, since external access for on-demand reads and alarm configuration is necessary. There is currently no effective answer in these specifications for this form of attack. There is no potential for harm to the source utility databases or the Innovatec communications network, however meter data that was set up for external data distribution could be monitored.
Field Service Application ENICS Server IMU (failed or reused) Utility Customer Site Depot Commisioning Tool IMU IMU, Relay, Gateway Utility Depot Factory Factory Commisioning & Test Tool Field Maintainence & Diagnosis Tool Field Maintainence & Diagnosis Tool Relay, Gateway Relay, Gateway (failed or reused) Field Maintainence & Diagnosis Tool Gateway & Relay Pole Locations Figure 2: IMU, Relay and Gateway work flow Gateways and relays will move from the depot to their pole locations.
“Application” Field Service Application Purpose Install, decommission, swap, calibrate, and test meters in the field. The primary users are field service people. Operates on a field service laptop or handheld computer that may be out of communication with the rest of the system for long periods of time. Field Monitoring and Diagnosis Tool Monitors RF traffic. Performs diagnostic tests of meters, relays and gateways.
“Application” Network configuration manager Purpose Configure Innovatec communications network, perform network diagnostics, manage hardware and software versions, support field service operations. The primary users are network maintainers at the utility. Required server functionality View network logically. Supply data relating to characteristics of a communications path. Supply meter and gateway statistics and logged history. Set up service orders Integrate modified service order data into databases.
Supported Autonomous Applications An autonomous application is one that runs without significant user intervention, such as the automatic health monitor. Application Network exerciser Network health monitor ENICS Health Monitor Message Monitor Logged Event Pruner Gateway Logged Event Gatherer Alarm receiver Purpose Test the network software and gateway server, in house. The primary users are developers and testers Determines when an element of the network hasn’t been heard of in some time.
Internal Databases The utility server software shall support access to and maintenance of the following internal databases, independently for each utility supported. The databases referred to in this section are abstract entities introduced for the purposes of requirements analysis and will not necessarily be implemented as databases in the sense of an JDBC (or other protocol) database entity.
Database Logging Authorized users Authorized external data distribution targets. Extern data distribution meter configuration table External data distribution target transaction log Field Service Application Database Application Configuration Database Record Type Notification type record. Typically there’ll be one of these for every notification destination/ destination type. E.g., one for each pager that could be notified that an alarm has arrived.
Permissions Access control permissions (or just permissions) in the ENICS system apply to all applications (including both Java applications and applets) that may be initiated outside of the server environment. Applications that are initiated by and run under the control of the ENICS server environment (such as the network health monitor) do not require access permissions. Access permissions are assigned out of the available options on a user by user basis. Each application has three sets of permissions.
Innovatec Look and Feel Pluggable Look and Feel All enics applications should implement the com.innovatec.plaf.InnovatecLookAndFeel look and feel. import com.innovatec.plaf.InnovatecLookAndFeel;...static{try{UIManager.setLookAndFeel( new InnovatecLookAndFeel() );}catch( Exception e ){}} Colors Foreground/Text Foreground colors should contrast extremely with the background. Since most of our background colors are very light, labels, and text areas will have black foreground colors.
Shortcuts All common commands should have a short cut key strokes, these should be clearly labeled on the menu and or button for that command. The same shortcut key cannot refer to different actions in the application.
Plain Windows Splash Screens A splash screen is a window with no standard window decorations (titlebar, close, minimize, maximize icons) that informs the user that the software is loading and what exactly the program is. A splash screen in ENICS shall consist of the Innovatec logo, an image for the application, the application logo, version, and copyright information. A splash screen should be implemented using com.innovatec.ui.Jsplash.
Menus All commands available should also be made available by menu. As much as possible all menus should have shortcut keys and or mnemonic associated with them. If a menu shares functionality with a button is should share the same label. Status Bar Small bar at the bottom used to convey information to the user. The status bar should be used before a dialog box if at all possible. Error messages should be in Red. Successful completion should be indicated with black. For implementation use com.innovatec.ui.
Change Log Date 5/17/99, Revision 0.2 5/17/99, Revision 0.2 5/17/99, Revision 0.2 5/17/99, Revision 0.2 5/18/99, Revision 0.2 5/18/99, Revision 0.2 5/18/99, Revision 0.2 5/18/99, Revision 0.2 5/18/99, Revision 0.2 5/18/99, Revision 0.2 6/4/99, Revision 0.2 6/4/99, Revision 0.2 6/4/99, Revision 0.2 6/15/99 Revision 0.2 Applications/Subs ystems Affected Description of changes Changed revision number to 0.2 from 0.1.92 Remove action item for authentication of remote redistribution servers.
