Command Center Setup

Security

Advanced Metering Infrastructure (AMI) systems enable powerful grid management capabilities. In addition to sending and receiving meter data, advanced metering and smart grid networks provide remote control and automation of certain distribution system functions to assist utilities with load management, reporting and responding to power outages and monitoring power quality. Ensuring the security of such a system is a top priority.

Because of the current state of the industry and various technologies being deployed, there are no existing uniform security standards for AMI systems. Landis+Gyr is monitoring and participating in the security standards development process currently being conducted by such groups as the AMI Security Task Force (AMI SEC), UtiliSec Advanced Security Acceleration Project (ASAP SG), and the NIST Cybersecurity Coordination Task Group.

The chief concern is ensuring system and network availability while meeting three critical security objectives: Confidentiality, Authentication, and Integrity. By focusing on these objectives, Landis+Gyr is able to effectively manage security risk, while offering a tiered structure of security features to meet the needs of individual utilities.

NOTE: For information on security settings see Landis+Gyr Security Administrators Guide, publication number 98-1035.

Logging into Command Center

Command Center is a secure application that requires users to have unique credentials to log into the software. During the Command Center software installation, one user, with security privileges, is created. This user will be the only person with initial access to the software.

Following is the procedure for logging into Command Center

1.Open an Internet Explorer browser.

2.Enter the assigned Internet address (URL) in the browser’s address bar. The Command Center User Login window will be displayed.

 

 Figure 3 - 1. Command Center User Login Window

3.Type your provided User Name and Password into the spaces provided. The password is case sensitive.

NOTE: After logging in, the user name can be changed by the Administrator and the user can change his/her own password.Passwords are case sensitive and must contain a minimum of 6 characters that consist of at least 1 upper case, 1 lower case and 1 non-alphanumeric character, as well as 1 digit.

4.Click the Login button. The Command Center Message Center tab Home window will be displayed.

 

 Figure 3 - 2. Command Center Message Center Home Page

The purpose of the Message Center is to display Landis+Gyr generated messages, such as new versions of Command Center, or new feature availability. At the bottom of the window, historical log-in information is displayed.

Navigating Command Center

Navigation in Command Center is similar to navigating an Internet web site. Menu tabs and quick select icons allow for ease of navigation.

Menu tabs

Menu options are available for easy access to different functions within Command Center. Each tab will provide a drop down list of sub menu options.

 

 Figure 3 - 3. Command Center Menu Structure

NOTE: The Organization Information setting Menu allows the utility to change the menu layout. The default RF Mesh Command Center layout is MDM.

Quick Select Icons

Quick Select icons, which facilitate navigation, are available in the upper right hand corner. The function of each icon is described in Table 3 - 1.

Initial Command Center Setup

Upon installation of Command Center, the available menu options are limited to Activate License and Organization Information settings. The Security Administrator must activate the license to unlock the Command Center functionality necessary to manage the utility’s RF Mesh solution. Once the license has been activated, additional utility specific settings must be established.

Activate License

The Landis+Gyr licensing program allows customers to purchase additional functionality. A software product license grants you the legal right to run or access a software program. A license agreement governs your use of the licensed software program.

With Landis+Gyr licensing programs, staying current gives your business a technological edge to better respond to customer demands and competitive challenges.

There are three steps required to purchase a software license after you have determined which software program(s) you need:

•Determine the license(s) you need.

•Contact your Landis+Gyr sales representative to purchase the product license key.

•Install the license key in Command Center

1.Click Setup > Activate License.

The Activate License window will be displayed.

 

 Figure 3 - 4. Activate License

NOTE: If expected menu options are not available, it is likely the license has not been purchased or has not been activated.

A list of currently licensed software is displayed.

2.To activate additional software, enter the Activation code provided by Landis+Gyr Sales in the text box.

...or...

Click the Browse button to navigate to the location of the license file supplied to you by Landis+Gyr.

3.Double-click the license file name to add the file name to the license file text box.

4.Click the Activate button to activate the license file or activation code.

Organization Information Settings

The Organization Information settings allow for the establishment of information related to the top-most level of organization structure. Several Organization Information settings must be configured upon initial installation of the software.

1.Click Setup > Organization Information.

The Organization Information window will be displayed. Settings displayed will vary based on license activation.

 

 Figure 3 - 5. Organization Information Window

2.Complete the setup described in the following sections:

•General Settings. See “General Settings” on page 28.

•Readings Settings. See “Readings Settings” on page 31.

•RSS Settings. See“RSS Settings” on page 32.

•Billing Progress Report Settings. See “Billing Progress Report Settings” on page 32.

•Store and Forward Scheduled Gap Detection. See “Store and Forward Scheduled Gap Detection Settings” on page 32.

•Mapping Settings. See “Mapping Settings” on page 33.

•HAN Settings. See “HAN Settings” on page 33.

•Data Extract Settings. See “Data Extract Settings” on page 33.

•Security Settings. See “Security Settings” on page 35.

•Batching Service Settings. See “Batching Service Settings” on page 36.

•Readings Gap Reconciliation Settings. See “Readings Gap Reconciliation Settings” on page 37.

•Event Gap Reconciliation Settings. See See “Event Gap Reconciliation Settings” on page 38.

•Command Specific Settings. See “Command Specific Settings” on page 39.

3.When setup is completed click the Save button.

NOTE: Internet access is required to use the mapping features within Command Center.

NOTE: For information on security settings see “Landis+Gyr Security Administrators Guide” Publication number 98-1035.

Process Settings

The Process Settings function allows the user to control how often Central Server processes occur. The processes are inherent to the normal operation of the Central Server and are rarely modified.

CAUTION: Process Settings should not be modified without assistance by Landis+Gyr.

1.Click Setup > Process Settings.

The Process Settings window will be displayed.

 

 Figure 3 - 6. Process Settings Window

The column headings include the following functions:

•Enable. Select the check box for the appropriate process to enable that function. Clear the check box to disable the function.

•Name. This column displays each function.

•Occurs. This column displays the interval at which each function runs.

•Time/Interval. This column allows the user to select a time for the appropriate function from the corresponding drop-down list.

•Offset Minutes. Offset Minutes. Minutes after the clock-aligned interval, used to set the exact time for the Incremental Daily Reads Extract to run. If this setting is not 0, the extract will run at exactly this number of minutes after the top of the hour, and every interval thereafter.

•Last Run. This column displays the last date and time that each process was run.

•Next Run. This column displays the date and time of the next scheduled process.

•Actions. This column displays a Run Now icon. Click the icon to immediately run the desired process.

•History icon in the Warehouse Update Process row. Click the History icon to view the Process History (Last 30 Days) window. If there are any failed links in the Status column, click the link to view the reason why the task did not run.
The Actions column also displays a Run now icon in most rows. Click the icon to immediately run the desired process.

 

 Figure 3 - 7. Process Settings Window

2.The following processes are displayed for editing. Settings displayed will vary based on license activation.

3.Click the Save button to save any changes.

System Settings

CAUTION: System Settings should not be modified without assistance by Landis+Gyr.

This window is used to adjust system functionality settings.

1.Click Setup > System Settings.

The System Settings window will be displayed.

 

 Figure 3 - 8. System Settings

Enter the following settings:

2.Click the Save button.

Data Streaming

Data Streaming allows near real time readings data transfer from Command Center readings processes to third-party applications utilizing the CIM 2nd Edition standard interface. These readings can be streamed to several external systems. Reading types available for streaming include:

•   Register reads

•Interval Load Profile reads

•On Demand reads (Optional)

The Data Streaming component must be installed using the Centralized Installer. Please see ICMS Installation Add-On: Data Streaming Package Specifics, publication number 98-2622 Rev AA, for installation instructions.

Command Center requires a license for Data Streaming.

1.Enable Data Streaming by selecting Setup > External Integration and then expanding the Integration Suite - Web Based Services accordion.Check the box for Data Streaming Service.

 

 Figure 3 - 9. Enable Data Streaming Service

2.Select Setup > Data Streaming. The Data Streaming Summary page will open.

From this page, Data Streams can be added, edited or deleted.

 

 Figure 3 - 10. Data Streaming Summary

Create a New Data Stream

To create a new Data Stream, do the following:

1.From the Data Streaming Summary page, click New.

2.Enter a Name for the new data stream.

3.Select a Streaming Type from the drop-down list:

•Readings

•Load Profile

4.Enter the Publish URL path.

 

 Figure 3 - 11. Create New Data Stream

5.Select the Data Definitions to stream. Use the > or < symbols to add or remove data definitions. Filter the data definitions options by using the following filters:

•Commodity

•All

•Electric

•Water

•Gas

•Type

•All

•Interval

•Register

•Unit of Measurement

•All

•Amps

•Amp-Hours

•CCF

•CF

•W

•Wh

•VAr

•VArh

•vA

•VAh

•W/VA (Power Factor)

•Volts

•Volts-Hours

•CM

•US GAL

•Time of Use

•All

•Non-TOU

•TOU

6.Click Save or Cancel.

Edit a Data Stream

To edit an existing Data Stream, do the following:

1.From the Data Streaming Summary page, click the Edit (pencil icon) for a data stream. the Create New Data Stream page will open.

 

 Figure 3 - 12. Edit Data Stream

2.Add or remove data definitions as described in “Create a New Data Stream” on page 53.

3.Click Save. A confirmation message will be displayed stating that the Data Stream Saved Successfully.

Delete a Data Stream

To delete an existing Data Stream, do the following:

1.From the Data Streaming Summary page, click the Delete (X icon) for a data stream.

 

 Figure 3 - 13. Delete Data Stream

2.A pop up message will ask Are you sure you would like to delete the data streaming entry.

3.Click OK.

IP Address Support for Endpoints

Command Center supports IP addressability for endpoints. IP has been identified as one of the key protocols that will serve as the foundation to build interoperability within the smart grid.

In reflection of this, the RF Mesh solution has the ability to assign IP addresses to each node in the network (endpoints, Routers, Collectors) as well as supporting IP commands.

Command Center acts as an IP-operations center by managing all IP exchange between external applications (i.e. HP Open View, Advent Net, etc.) and the endpoints. For this purpose, Command Center manages the IP address assignment for each RF node, process all IP requests, and respond to these requests in IP packet structure.

The commands supported by this function are:

•Ping

•SNMP – Get Endpoint Configuration

•SNMP – Get Endpoint Info

NOTE: To take advantage of this feature, access is managed through the Gridstream Integration Suite.

NOTE: To enable this feature go to Setup > System Settings page - enable IP Capability.

NOTE: The IP address assigned to each endpoint will appear on the Endpoint Information Window.

C12.22 Settings

The ANSI C.12.22 standard is supported in Command Center by using Command Center as an ANSI C.12.22 Master Relay and Gateway.

Command Center will assign an ANSI C.12.22 ID (called App Title in the standard language) to each endpoint and will create ANSI C.12.22 extended tables (decades 12 and 13) for each endpoint within the Command Center Database.

This will allow Command Center to process ANSI C.12.22 requests and provide responses using the standard packet format.

The following are the C.12.22 services supported:

•Identification

•Registration

•De-registration

•Read

•Write

•Trace

•Resolve

NOTE: To take advantage of this feature access is managed through the Gridstream Integration Suite.

1.Click Setup > C12.22 Operation > C12.22 Settings to display the C12.22 Settings window.

 

 Figure 3 - 14. C12.22 Settings

a.Master Relay and Gateway Settings.

•Master Relay Aptitle. On first save this field will be locked.

•Gateway Aptitle. On first save this field will be locked.

b.Device Class and ESN.

•Master Relay Electronic Serial Number. On first save this field will be locked.

•Gateway Electronic Serial Number. On first save this field will be locked.

•Node Native Address and Port Number. Node Native Address will be same for Master Relay and Gateway.

c.Gridstream Endpoint Migration Settings.

•Enter Batch Size. This is the number of Endpoints which will be migrated in each interval of schedule. Recommended size is 100000.

d.Notification Cache Settings.

•Notification Retry Interval. Minimum period in minutes following a failed attempt before a next attempt is made to notify a host.

•Notification Retry Count. Maximum number of notification retry attempts following the first unsuccessful notification attempt.

•Notification Timeout Period. Notification Timeout Period in minutes after the last unsuccessful retry that a pending notification can be deleted.

NOTE: Migration process will begin only when an Authentication Host or Notification host is made available to the System.

User Access

A user with Security Administrator permissions is created during the Command Center software installation, and, initially, only this user will have access to Command Center.

NOTE: Landis+Gyr recommends that the utility immediately elect an additional individual with rights to user management.

The User Access function allows the Security Administrator to add or edit customized access roles as well as create users and administer user functions.

Roles

User Roles define the functionality that groups of individuals at the utility will be provided in the Command Center. As a part of the AMI deployment, the utility should determine which individuals will have access to Command Center, and which functions they will need to perform their duties.

NOTE: To view all default user roles, please see the current Landis+Gyr Command Center User Roles and Permissions spreadsheet. Some roles and permissions listed on the spreadsheet and in this document are license specific and may not be available in your version of Command Center.

View Existing Roles

Following is the procedure to view the existing Roles:

1.Select Setup > User Access > Roles.

2.The Roles window will open displaying all existing user roles, shown in Figure 3 - 15. 

 

 Figure 3 - 15. Roles Example

CAUTION: To ensure optimal support from Landis+Gyr, the database is populated with a user role - Landis+Gyr Tech Support - for use by the Landis+Gyr Technical Support team. This role should not be edited or deleted.

The following actions may be performed

•Edit. This function allows for editing an existing role.

•Delete. This function allows for deleting an existing role. If users have been assigned to the role, this option will be unavailable.

NOTE: When a new role is created, or an existing role is modified and the permission is changed, an entry will be made in the User Roles Management Audit Report.

Create User Roles

Seeded roles may be used by the utility, or the utility may choose to define custom roles for its users.

Following is the procedure to create a new Role:

1.Click New. The Role Management window will open, shown in Figure 3 - 16. 

 

 Figure 3 - 16. Role Management

2.Enter a Role name. The role name must be unique to the organization.

3.Click the Edit Description link to add notes to describe the role (optional).

4.Select individual permissions from each of the following:

a.Screen and Menu Permissions

The Screen and Menu Permissions section lists all of the menu options available in Command Center. Select the check-box next to the menu option to allow access for the user role. The top-level can be checked to select all sub-entries. Menu options denoted by a lock, indicate that the user may be provided read only access.

 

 Figure 3 - 17. Screen and Menu Permissions

b.Security Administration Permissions

The Security Administration Permissions section lists all of the menu options available in Command Center. Select the check-box next to the menu options to allow access for the user role.

 

 Figure 3 - 18. Security Administration Permissions

c.RF Collector Command Permissions

All of the available collector commands will be listed in the RF Collector Command Permissions section. Select the check-box next to the collector command to allow access for the user role to execute the command.

 

 Figure 3 - 19. RF Collector Command Permissions

d.RF Endpoint Command Permissions

All of the available Endpoint commands will be listed in the RF Endpoint Command Permissions section. Select the check-box next to the Endpoint command to allow access for the user role to execute the command.

 

 Figure 3 - 20. RF Endpoint Commands Permissions

e.Click External Groups to associate external groups with this role.

 

 Figure 3 - 21. External Groups

NOTE: The Organization Information setting External User Authentication must be enabled to activate this functionality.

To associate external groups with this role:

i.Enter text from the Group name as it is identified in Active Directory.

ii.Select Starts with or Contains.

iii.Click Find.

iv.Choose one or more groups from the list.

v.Click Add Selected Groups.

f.Mobile Admin Tool Permissions

Click Mobile Admin Tool Permissions, shown in Figure 3 - 22, to select the privileges to be granted to users of RadioShop, Endpoint Testing Manager and TechStudio.

 

 Figure 3 - 22. Mobile Admin Tool Permissions

i.RadioShop Access.

•Access Level. Select the level of permission to be granted to users assigned to this role.

•Session Duration. The session duration controls the amount of time a user’s credentials are cached on the local machine. During the session duration the RadioShop user may log into RadioShop without authenticating with Command Center.

•Temporary. 8 hours

•Strict Control. 24 hours

•Tight Control. 10 days

•Normal. 32 days

•Relaxed. 187 days

•No Expiration. Does not require user to periodically login it authenticate.

•MAT Certificate. Select this check-box to grant a MAT certificate for use in communication with devices using Advanced Security configuration. This option will only be displayed if the utility is licensed for Advanced Security.

ii.Endpoint Testing Manager Access.

•Access Level. Select the level of permission to be granted to users assigned to this role. Refer to “Mobile Admin Roles and Permissions” on page 64 for further details.

•Session Duration. The session duration controls the amount of time a user’s credentials are cached on the local machine. During the “session duration” the Endpoint Testing manager user may log into ETM without authenticating with Command Center.

•Temporary. 8 hours

•Strict Control. 24 hours

•Tight Control. 10 days

•Normal. 32 days

•Relaxed. 187 days

•No Expiration. Does not require user to periodically login it authenticate.

•MAT Certificate. Select this check-box to grant a MAT certificate for communication with devices using Advanced Security configuration. This option will only be displayed if the utility is licensed for Advanced Security.

iii.TechStudio Access.

•Access Level. Select Yes to grant login privileges.

•Session Duration. The session duration controls the amount of time a user’s credentials are cached on the local machine.

•Temporary. 8 hours

•Strict Control. 24 hours

•Tight Control. 10 days

•Normal. 32 days

•Relaxed. 187 days

•No Expiration. Does not require user to periodically login it authenticate.

•MAT Certificate. Select this check-box to grant a MAT certificate for communication with devices using Advanced Security configuration. This option will only be displayed if the utility is licensed for Advanced Security.

g.Tools Endpoint Command Permission

Select from available options to control user access to the menus, pages and commands for TechStudio. These options are not enabled by default.

 

 Figure 3 - 23. Tools Endpoint Command Permission

5.Click the Save button to save the role.

Users

The Security Administrator must create a user profile for each individual requiring access to Command Center.

Viewing Existing User

Following is the procedure for viewing existing users in the system:

1.Select Setup > User Access > Users.

2.The Users window will open.

 

 Figure 3 - 24. Users

The Users window displays all active user accounts, and provides the ability to edit a user profile, reset passwords, archive users, and configure new user profiles.

Create a new user profile

Following is the procedure for creating a new user profile:

1.Select Setup > User Access > Users. The Users window will appear, shown previously in Figure 3 - 24.

2.Click New. The User Management window will open, shown in Figure 3 - 25. 

 

 Figure 3 - 25. User Management

Enter all required fields (indicated by an asterisk).

•First Name. Must be one or more alpha characters.

•Last Name. Must be one or more alpha characters.

NOTE: The first name/last name combination must be unique to the organization.

•User Name. The user name is not case sensitive and must not exceed 20 characters.

•E-mail. This field is not required, however, an e-mail address is necessary for users wishing to setup e-mail alerts.

•Password. Enter the user’s password. The minimum number of character allowed is configured in the Organization Information settings. The user’s password must contain one upper case, one lower case, one alphanumeric, as well as one digit.

•Confirm Password. Retype the password.

•Phone. Enter the user’s telephone number (optional)

•Pager. Enter the user’s pager number (optional)

•Notes (optional). Enter any notes associated with the user

•Role Assignments. Select one or more roles to assign to this user.

•Locked Out. By default, when a user attempts to login to Command Center five times with an unrecognized user name or password, the user will be locked out of the system. This setting is applicable to Command Center credentials only.

uSystemSetting: The default number of log-in attempts may be configured in the System Settings “Maximum User Authentication Attempts”

•Show inaccessible menu options. Select this check box to allow users to see menu items that are not part of their role. If selected, when the user logs into Command Center, all menu options will be displayed, but those menu options to which the user has not been granted permissions will be grayed out and unavailable.

•Password Never Expires. Selecting this option allows for over-riding the global Organization Information setting Maximum Password Age. If selected, the user will never be required to change his/her password. This is especially useful for users created for integration to other software, for example GSIS.

•Change Password on Next Login. Selecting this option will cause the user to be required to change their password the next time they login to Command Center. Best practice when first setting up users, would be to force them to change their password on next log-in so that they may select a password only known to them.

•System Owner. When the System Owner check-box is selected all existing tenant groups are automatically assigned.

3.Click the Save button to save the new user.

Archive User

For auditing purposes, inactive users may not be deleted from the system, they must be archived.

Following is the procedure to archive a user:

1.Click the Archive icon for the selected user in the Users window. A windows dialog box will open, asking for confirmation of the archive action.

2.Click OK. The user has now been archived.

Show Archived Users

1.Click the Show Archived Users check box on the User window.

2.The User window will refresh and archived users will appear with a red check mark in the corresponding row under the Archived heading.

NOTE: To un-archive a user, clear the Archived check box within the user’s profile, clear the locked out check box, reassign a role and reset the user’s password.

Reset User Password

When necessary, the Security Administrator (or a user assigned user management privileges) may reset a user’s password:

1.Click the Reset password icon for the selected user in the Users window.

2.Enter the New Password.

3.Re-enter the new password to confirm.

4.Click the Save button to save the changes.

Audit Reports

Audit Reports provide a method to track changes made to Organization Settings, Collector Settings, System Settings, as well as logs of daily activity, user log ins, and when collectors have been archived. Audit Reports will only be displayed for those individuals who have been granted Security Administrator rights.

1.Click Setup > User Access > Audit Reports to display the Audit Reports window.

 

 Figure 3 - 26. Audit Reports

2.Select one of the following reports from the Report Type drop-down list, reports will vary depending on licenses:

a.Daily Activity Report. Displays a description of the activity, the date of the activity, the login user and details of the activity.

 

 Figure 3 - 27. Daily Activity Report

b.Collector Archived Report. The Collector Archived report shows all Collectors that have been archived. Collectors can be archived on the Setup > Collectors page. Collectors can only be archived if there are no associated endpoints.

 

 Figure 3 - 28. Collector Archived Audit Report

c.Collector Settings Change. Displays collector name, setting name, new value, old value, date of change and the login of the user who made the change.

 

 Figure 3 - 29. Collector Settings Change Audit Report

d.Critical Commands. Displays login of user who issued the command, date it was issued, the command that was issued, meter number, endpoint serial number and the collector name.

 

 Figure 3 - 30. Critical Commands Audit Report

e.Data Extract Change > SubReport Type.

•Incr Daily Reads Extract

f.Endpoint Configuration > SubReport Type. Displays the SubReport activity, meter number, endpoint serial number, date the command was issued, the login of the user who issued the command the a detail view of the activity.

•All

•Billing Cycle Added

•Billing Cycle Changed

•Billing Cycle Deleted

•Endpoint Added

•Endpoint Added to Billing Cycle

•Endpoint Archived

•Endpoint Billing Cycle Changed

•Endpoint Changed

•Endpoint Deleted

•Endpoint Removed

•Endpoint Removed from Archive

•Endpoint Removed from Billing Cycle

 

 Figure 3 - 31. Endpoint Configuration Audit Report

g.File Transfer Management Audit Report. This report displays file transfer import operations of DA devices, such as streetlight controllers, by sub report type. The report displays the activity, login user, date, file name and firmware type. Sub Report filters include:

•All

•Transfer File Deleted

•Transfer File Imported

 

 Figure 3 - 32. File Transfer Management Audit Report

h.Group Management > SubReport Type.

The Group Management Audit Report records when devices are moved from one tenant group to another. This report is designed to be used for auditing the following groups in Command Center:

•All

•Collector Groups

•Load Control Groups

•Status Groups

•Endpoint Group Type: Disconnected Groups, Low Signal Quality Groups, Maintenance Groups, Multi Utility Monitoring Groups, Outage Disabled Groups, Permanent Switch Groups, Planned Outage Groups, Quarantine Groups, SIM Management Platform Outage Reporting Groups, Temp Switched Groups, User Defined Groups, Validation Groups, Zero Usage Groups

•Tenant Groups

•User Defined Addressing Groups   

•Virtual Addressing Groups

i.Import Operations > SubReport Type. Displays the login of the user who issued the command, date the command was issued, the SubReport activity type and the name of the .csv file.

•All

•Collector Installation File Imported

•Collector Manufacturer File Imported   

•Customer Information File Imported

•Endpoint ID Ranges Updated

•Mass Archive Endpoints File Imported

•Mass Inventory Endpoints File Imported

•Meter Installation File Imported

•Meter Manufacturing File Imported

•Meter Program Mapping File Imported

•Tool Data Imported

•Update Performance from Tool

 

 Figure 3 - 33. Import Operations Audit Report

j.Login Failures: Invalid Password > SubReport Type. Displays the SubReport Type activity selection, the name of the user who attempted to login with an invalid password.

•All

•CC Invalid Password

•ETM Invalid Password

•GUTS Invalid Password

•RadioShop Invalid Password

 

 Figure 3 - 34. Login Failures: Invalid Password Audit Report

k.Login Failures: Invalid Username > SubReport Type. Displays the SubReport Type activity selection, the name of the user who attempted to login with an invalid username.

•All

•CC Invalid Username

•ETM Invalid Password

•RadioShop Invalid Username

 

 Figure 3 - 35. Login Failures: Invalid Username Audit Report

l.Meter Program Management

The Meter Program Management option allows the user to select to view meter programs that were imported, archived or re-instated.

 

 Figure 3 - 36. Meter Program Management Sub-Reports

•Meter Program Imported Sub-Report

The Meter Program Imported Audit Report, shown below, provides the user a log of Meter Programs that have been imported.

 

 Figure 3 - 37. Meter Program Imported Audit Report

•Meter Program Archived Sub-Report

The Meter Program Archived Audit Report, shown below, provides the user a log of Meter Programs that have been archived.

 

 Figure 3 - 38. Meter Program Archived Audit Report

•Meter Program Reinstated Sub-Report

The Meter Program Reinstated Audit Report, shown below, provides the user a log of Meter Programs that have been reinstated.

 

 Figure 3 - 39. Meter Program Reinstated Audit Report

m.Meter Readings Quality Changed > Sub-Report Type.

The Meter Readings Quality Changed report. Sub-menu reports include Reading Quality Changed to Billable and Reading Quality Changed to Non-Billable.

•All

•Reading Quality Changed to Billable

•Reading Quality Changed to Non-Billable

 

 Figure 3 - 40. Meter Readings Quality Changed Audit Report

n.Organization Settings Change. Displays the name of the activity, the setting name, the date the change was made, the login of the user who changed the setting and a detailed view of the report.

 

 Figure 3 - 41. Organization Settings Change Audit Report

o.Process Settings Change. Displays the name of the activity, the process name, the date the change was made, the login of the user who changed the setting and a detailed view of the report. Sub-reports include:

•All

•Process Settings Disabled

•Process Settings Enabled

•Process Setting Interval Changed

•Process Setting Manually Run

•Remote Connect Halted Process Restarted

•Remote Disconnect Halted Process Restarted

 

 Figure 3 - 42. Process Settings Change Audit Report

p.Security. Displays details for a user action, the date that the action took place, the login information of the person who performed the action and the user ID.

 

 Figure 3 - 43. Security Audit Report

q.System Settings Change. Displays the setting name, the new value of the setting, the old value of the setting, the date the setting was changed and the login of the user who changed the setting.

 

 Figure 3 - 44. System Settings Change Audit Report

r.Tool User Logins. Displays details of when a tool user logged in, the user name and the date the login occurred. Sub-reports include:

•All

•ETM Successful Login

•Maintenance Terminal, (a.k.a. GUTS) Successful Login

•RadioShop Successful Login

 

 Figure 3 - 45. Tool User Logins Audit Report

s.User Account Management. Displays the Sub-Report Type activity selected, user name of the user, the date of the activity, the login of the user who made the change, and details of the action.

•All

•Tenant Group Assigned to User

•Tenant Group Removed From User

•User Archived

•User Changed

•User Created

•User Locked Out

•User Password Reset

•User Reinstated

•User Unlocked

 

 Figure 3 - 46. User Account Management Audit Report

t.User Roles Management. Displays the SubReport Type activity selected, the role name of the user, the date of the activity, the login of the user who made the change and the details of the action.

•All

•User Role Changed

•User Role Created

•User Role Deleted

 

 Figure 3 - 47. User Roles Management Audit Report

u.User Sessions. Displays the user ID, the session action, the name of the user, the session start time, the session end time, the number of days of the session, the session length, terminated by and logtime.

 

 Figure 3 - 48. User Sessions Audit Report

3.Select from the following Device Criteria on which to base the report, if applicable:

•All. Select the All radio button to include all collectors in the report.

...or...

Collector. Select the Collector radio button and then choose a Collector from the drop-down list to include only the selected Collector in the report.

...or...

Meter. Enter the meter number in the Meter field or click the Find a Meter icon and browse to a meter location. This will include only the selected meter in the report.

4.Select from the following User Criteria on which to base the report:

•All. Select the All radio button to include all users in the report.

...or...

User. Select the User radio button and then choose a user from the drop-down list to include only the selected user in the report.

5.Select a Date Range from the following:

•Quick Select. Choose a time frame from the drop-down list

...or...

Start Date. Select a start date by clicking on the Start Date calendar icon, then select an end date by clicking on the End Date calendar.

6.Click OK to display the report.

 

 Figure 3 - 49. Sample Audit Report

7.Click (Figure 3 - 49) to save the report as a.csv file.

Authentication Settings

Command Center users can be authenticated by three different authentication providers:

1.Command Center (Internal) Authentication. This is the current means of authenticating users and relies on credentials stored in the Command Center Central Services database. For system security, the administrator should be the only person that has access to administer roles and their associated permissions. See “Command Center Authentication” on page 76.

2.SAML (Security Assertion Markup Language) Authentication. See “SAML Authentication” on page 78.

3.External User Authentication. Users can log in via their domain user name, also used to log in to Windows, either by entering it directly to Command Center or implicitly by using Internet Explorer while logged on to their Windows desktop. See “External User Authentication” on page 82.

NOTE: When a user logs in to the Command Center, only the menus that the user has access to will be displayed.

NOTE: The administrator should define the various roles and those roles should be assigned immediately after installing Command Center. The system will be seeded with basic roles that may be edited by the administrator if desired.

Command Center Authentication

The administrator will need to establish a user profile for each employee that has access to Command Center. This is also where the roles are assigned for access to the Command Center.

1.Click Setup > User Access > Users to display the Users window.

 

 Figure 3 - 50. Users Window

2.Click the New button to display the User Management window.

 

 Figure 3 - 51. User Management Window

3.At a minimum, the required fields must be filled in.

•First Name. Must be one or more alpha characters.

•Last Name. Must be one or more alpha characters.

NOTE: The first name and last name combination must be unique to the organization.

•User Name. Must be unique to the organization. The user name is not case sensitive. The user name must not exceed 20 characters.

•E-mail. Enter the contact’s e-mail address. This e-mail address is used for sending alerts via the Alert Manager.

•Password. Passwords are case sensitive and must contain a minimum of six characters that consist of at least 1 upper case, 1 lower case and 1 non-alphanumeric character, as well as 1 digit.

•Confirm Password. Retype the entered password.

•Phone. Enter the user’s telephone number. This can be a mobile or land-line telephone number. This field is optional and for informational purposes only.

•Pager. Enter the user’s pager number. This field is optional and for informational purposes only.

•External user name. This is the user name on the Active Directory server.

•Notes. Enter any notes associated with the user.

•Role Assignments. Allows the administrator to assign available role(s) that were created earlier in this chapter to this user.

•Locked Out. This box will be checked when a user has unsuccessfully attempted to log in to the system five times with an unrecognized password. The Locked Out status will be indicated by a red check mark on the Users window.
Only users assigned the “Roles” permission will be able to view and modify the Locked Out check box.
The administrator can re-enable the login by clearing the check box.

•Show inaccessible menu options. Select this check box to allow users to see menu items that aren’t a normal part of their role. The inaccessible menu items are displayed, but grayed-out.

•System Owner. When the System Owner check-box is selected all existing tenant groups are automatically assigned.

4.Click the Save button to save the user.

SAML Authentication

Before SAML Authentication can be enabled, the Security Administrator role will need to be edited.

1.Click Setup > User Access > Roles to display the Roles window.

2.Click the Edit icon for the Security Administrator role.

 

 Figure 3 - 52. Roles

3.On the Role Management page, expand the Security Administration Permissions section.

 

 Figure 3 - 53. Role Management Window

4.Click the Setup>User Access>Authentication Settings box to enable the Authentication Settings function for the Security Administrator role.

5.Click Save.

Enable SAML Authentication Settings

1.Select Setup > User Settings > Authentication Settings to display the Authentication Settings page.

 

 Figure 3 - 54. Authentication Settings

2.Select SAML (Security Assertion Markup Language) from the Authentication Provider drop-down list. Additional fields will be displayed.

 

 Figure 3 - 55. Authentication Settings - Identity Provider

3.Select the Authorization Provider from the drop-down list. Command Center is the default value.

4.Enter the following Identity Provider information:

•Entity ID

•Single Sign On URL

•Certificate Path

•Select the Binding type from the drop-down list.

•HTTP Post (default setting)

•HTTP Redirect

•Log Out URL

•Enable Only SAML Identity Provider check-box. Unchecked by default, check to enable.

NOTE: Once checked and saved, the box cannot be unchecked.

Enter the Command Center User Attribute Mapping information.

•User Name

•First Name

•Last Name

•E-mail

•Phone Number

•External User ID

5.Enter the Service Provider information.

 

 Figure 3 - 56. Service Provider

•Entity ID

•Return URL

•Certificate Path

•Password

6.Enter User Role Mapping information:

 

 Figure 3 - 57. User Role Mapping

a.Enter the Identity Provider Group Attribute Name.

b.Select the Group Attribute Format from the drop-down list.

•FreeText

•ActiveDirectory

7.Click Add new record.

a.Enter a Group Name and select associated Roles from the Role List, click Update.

 

 Figure 3 - 58. Role Mapping

The Group Name will be added to the table of available groups. Multiple groups may be created.

b.Click Edit to make changes to the group.

c.Click Add new record to make an additional group.

8.Click Save.

External User Authentication

Since Active Directory supports user groups, a user's membership in an external group can indicate membership in a Command Center role.

New Installation

When an external user is authenticated for the first time, a new Command Center user can be created automatically if the user has membership in an external Command Center group, i.e., one that belongs to one or more Command Center roles.

Prior Installation

A new Command Center user should not be created when the individual already has a Command Center login. Instead, the individual's external credentials should be linked to their existing login. This resolution of external and Command Center identities can be performed in two ways:

1.Manual Resolution. For each user account that will be externally authenticated, an administrator adds the external identity (e.g., AD domain and user name) to the Command Center user profile. The same external identity may not be added to more than one user account.

2.User-Assisted Resolution. When a user logs in with external credentials that Command Center does not recognize, the user will be offered a list of user names that are not already linked. The user can then:

•Choose one to associate with their external identity. In this case, they must enter the correct password for the selected user.

WARNING: The Command Center web server (where the UI portion is installed) must be a registered server on the active directory domain.

External User Authentication Setup

1.Click Setup > Organization Information to display the Organization Information window.

 

 Figure 3 - 59. Organization Information

2.Enable External User Authentication by selecting the Enabled check-box.

3.Click the Save button.

Add External Integration to Command Center Roles

1.Click Setup > User Access > Roles to display the Roles window.

2.Click the Edit icon for the selected Role to display the Role Management window.

 

 Figure 3 - 60. Role Management Window

3.Check the External Integration check-box to enable.

4.Click the Save button.

Add External Integration to Command Center Roles

1.Click Setup > User Access > Roles to display the Roles window.

2.Click the Edit icon for the selected Role to display the Role Management window.

 

 Figure 3 - 61. Role Management Window

3.Check the External Integration check-box to enable.

4.Click the External Groups bar to display the External Groups search.

 

 Figure 3 - 62. Role Management Window - External Groups

5.Select either the Starts with or Contains radio button, enter a search term, and click the Find button.

6.From the Search Results box (shown below) click to select a group (Control-click to select multiple groups).

 

 Figure 3 - 63. Add Selected Groups

7.Click the Add Selected Groups link to add the selected groups to the Groups In This Role box.

8.Click the Save button.

Change Password

All users are granted the right to change their password. Changing the password is not required, nor forced after a number of days.

NOTE: Command Center will only allow password changes to the Command Center identity, not an external authentication identity. The Change Password window will not be available to users if External Authentication is enabled.

Following is the procedure for changing a user password:

1.Select Setup > Change Password. The Change Password window will open.

2.Enter the Current Password.

3.Enter the New Password.

4.Re-enter the new password to Confirm New Password.

5.Click Save.

Password Management

Multiple Security Settings establish how passwords are managed in Command Center.   Organization Information settings may be viewed and changed by selecting Setup > Organization Information > Security Settings.

 

 Figure 3 - 64. Security Settings

•Minimum Password Length. This setting allows the Security Administrator to specify the minimum number of characters a password may contain. The default value is 6, and may be a value from 6 - 19.

•Maximum Password Age. This setting allows the Security Administrator to establish the frequency at which users must change their password. When a user's password expires the user will be required to change the password, and will not be able to access Command Center until they do so. It is best practice to expire passwords every 30 to 90 days.

NOTE: An over-ride, specifying that a user's password never expires, can be configured for individual users.

•Password History Length. This option allows the Security Administrator to specify mechanism to specify how many unique new passwords must be associated with a user before an old password can be reused. The value must be between 0 and 30 passwords. A value of 0 results in no password check. If the user attempts to reuse a password, the error message You are trying to reuse a password you have used previously. Please select a password that you have not used previously. will be displayed.

•Minimum Password Age. This setting allows the Security Administrator to specify the minimum amount of time, in days, that a user must use a password before they are allowed to change it. If the user attempts to change their password before the Minimum Password Age is reached the error message The minimum time between password changes has not been met. You cannot change your password at this time will be displayed. The default value is 1. The Minimum Password Age must be less than the Maximum Password Age, unless the Maximum Password Age is set to 0, indicating that passwords will never expire. If the Maximum Password Age is set to 0, the Minimum Password Age can be set to any value between 0 and 1000.

•Allow Concurrent Users Sessions. This setting allows the Security Administrator to select whether or not all Command Center users may have either a single or multiple sessions open at one time. By default, this setting is enabled.

End User Options

The following two functions allow the individual user to change their own passwords and set up E-mail alerts.

Change Passwords

The Change Password window allows the individual user to change passwords.

NOTE: Changing passwords is not required and is not forced after a certain number of days.

NOTE: This menu option will not be available if using External Authentication.

1.Click Setup > Change Password.

The Change Password window will be displayed.

 

 Figure 3 - 65. Change Password Window

NOTE: Passwords are case sensitive and must contain a minimum of six characters that consist of at least 1 upper case, 1 lower case and 1 non-alphanumeric character, as well as 1 digit.

2.Type the user’s Current Password.

3.Type the user’s New Password.

4.Retype the user’s new password to Confirm New Password.

5.Click the Save button to save the changes.

E-mail Alerts

The E-mail Alert Manager will allow the Command Center user the ability to select the method and thresholds they wish to utilize for notifications of user definable events.

The E-mail Alert Manager notifies the users of the following category of events:

•Endpoint Status Alerts

•Collector Alerts

•Endpoint Validation Alerts

•Endpoint Alerts

•General Endpoint Alerts

•RF Security Alerts

•System Error Alerts

•Velocity Threshold Alerts

The present method for delivery of alerts include individual e-mail notification.

The system administrator can view and modify user subscriptions but is not able to subscribe other users.

NOTE: Microsoft Internet Information Services (IIS) must be installed on the computer before using the E-mail Alerts module.

WARNING: Once a threshold has been crossed, the user won’t be notified each time the system checks for crossed thresholds. When a count falls beneath a threshold and then crosses it again, a new alert will be triggered.

1.Click Setup > E-mail Alerts.

The E-mail Alerts window will be displayed.

 

 Figure 3 - 66. E-mail Alerts

NOTE: All users that want to set up alerts must first have an e-mail account created.

2.In the E-mail Alerts window, click the New button.

The Select an Alert window will open.

 

 Figure 3 - 67. Select an Alert Page

The Select an Alert window contains the following categories to choose from:

a.Endpoint Status Alerts. Endpoint Status Alerts are issued when the endpoint status changes or if the threshold number of endpoints in a specific status is exceeded. An organization user or a group can subscribe for alerts at an endpoint level, organization level, collector level or by location. Specify the endpoint alert threshold when making a selection other than by meter.

NOTE: When defining thresholds for email alerts for when Endpoints go Lost, meters that are assigned to a Status Group (Planned Outage or Disconnected) will be included in the threshold count, even though the event is suppressed within the user interface.

b.Collector Alerts. Collector Alerts emails are issued when specific events or errors occur for a Collector. Select a Collector, a location, or an organization.

c.Endpoint Validation Alerts. Endpoint Validation email alerts notify when the exceptions specified in the Validation Groups setup by the utility are triggered.

d.Endpoint Alerts. Endpoint Alerts are issued when meter alarm or advisory conditions (events) occur or if the threshold number of alarm or advisory conditions is exceeded.

e.General Endpoint Alerts. General Endpoint email alerts are issued when specific events or errors occur for routers or meters.

f.RF Security Alerts. RF Security Alerts emails will be sent when specific security related events are logged by the system.

g.System Error Alerts. Sends an email when an External Integration Command Error is logged.

h.Velocity Threshold Alerts. The generation of email alerts is used to notify the users when the command velocity threshold is exceeded.

3.Select any alert to open the Alert Filter window to sign up for an email alert.

a.Select the Alert Filter option.

NOTE: Some alerts will have additional filter choices.

 

 Figure 3 - 68. RF Network Device Alerts

•All. To filter the alert by all endpoints.

•Collector. To filter the alert by a Collector.

•Location. To filter the alert by location.

•Meters. To filter the alert by an individual meter. Enter a meter number or click the Find a Meter icon to browse to a meter location.

b.Alert Notification Criteria. Enter an alert threshold. When this threshold is exceeded, an e-mail alert will be sent to the users that signed up for this alert notification. The default threshold is one.

c.Click the Sign Up button to subscribe to this alert. The new alert window will open displaying the newly created alert subscription.

Test E-mail Alerts

To send a test message to the subscribed user’s e-mail address, use the following procedure:

1.Click Setup > E-mail Alerts.

The E-mail Alerts window will be displayed.

 

 Figure 3 - 69. E-mail Alerts Window

2.Click the Edit icon of the desired alert.

3.In the selected Endpoint Status Alert window, click the Test button.

 

 Figure 3 - 70. E-mail Alerts Test

4.Clicking the Test button sends a test message to the user’s e-mail address.

A test message should arrive shortly in the user’s e-mail.

NOTE: The alert will remain in the Alerts window in the Active or Inactive state until the alert is activated or deactivated again or until the user deletes the alert.

Organization Locations

Organization Locations allows the utility to establish the hierarchical organization structure it will need to allow for multiple geographic regions, districts, and offices to be managed by one or more system administrators. Establishing multiple regions will allow the user logged into the system to choose to filter data in order to view only substations, groups, endpoints, etc. that are specific to the user’s own region, district, or office.

The geographic locations can then be chosen by clicking on the Filter icon on most Command Center screens.

NOTE: All Organization Locations are optional. To specify Organization Location Level Names see Organization Information.

If the optional data filtering is desired, follow these instructions to establish the data filtering hierarchy.

1.Click Setup > Organization Locations.

The Organization Locations window will be displayed.

 

 Figure 3 - 71. Organization Locations Window

NOTE: Under the following headings Location Level Names will be referred to by their default settings of Region, District, and Office.

Add Location Level 1 Name

Each region name must be unique to this organization. You can add as many regions to the organization as desired.

1.To add a region, click the Add Region link to display the Region window.

 

 Figure 3 - 72. Region Window

2.Enter a region name in the Name field.

3.Enter an optional region description in the Description field.

4.Click the Save button.

Add Location Level 2 Name

Each District name must be unique to this organization. You can add as many districts to the organization as desired.

1.Click the Add District link to display the District window.

 

 Figure 3 - 73. District Window

2.Select a region from the drop down box.

3.Enter a district name in the Name field.

4.Enter an optional district description in the Description field.

5.Click the Save button.

Add Location Level 3 Name

Each Office name must be unique to this organization. You can add as many offices to the organization as desired.

1.Click the Add Office link to display the Office window.

 

 Figure 3 - 74. Office Window

2.Select a district from the drop-down box.

3.Enter an office name in the Name field.

4.Enter an optional office description in the Description field.

5.Click the Save button.

Archive Settings

Archiving data will enhance the performance of Command Center. This is accomplished by specifying that data older than a user-specified date be archived as a scheduled task.

Data older than the specified date will be archived from the following Command Center functions:

•Error History

•Event History

•Command History

•Readings History

•Raw Reading Packets

•Interval Data History

•User Session History

Landis+Gyr recommends scheduling Archive Settings as a weekly task. It is best run during a period of inactivity (such as a weekend morning).

1.Click Setup > Archive Settings.

The Archive Settings window will be displayed.

 

 Figure 3 - 75. Archive Settings

2.General Settings.

All regions are displayed by default. If you would like to filter the archive by selected regions, click the Filter icon in the upper-right corner of the window.

•Enable Archiving. Select the Enable Archiving check box to enable the archiving function. (Default is off).

•Archive Day. Select any desired day of the week to schedule the archive from the Archive Day drop-down list.

•Archive Time. Select the Archive Time.

•Click to highlight the hour. Click the up or down arrows to change the hour.

•Click to highlight the minutes. Click the up or down arrows to change the minutes.

•Double-click AM or PM, or highlight AM or PM and click the up or down arrows, to toggle between the two selections.

3.Months to Retain.

Select the number of months of data to retain for the listed categories. This means that if you select 12 (the default choice), the last 12 months of data will be retained and the remainder will be archived. The valid choices are any number of months greater than zero.

4.Click the Save button to save your selections and enable archiving.

NOTE: The archived data is saved to the Archive database that was set up during the Command Center installation.

Events Integration

Events Integration provides an interface to communicate alerts, flags and events logged by Command Center to an external software (MDMS, ODS, etc).

Event Extract

The Event Extract allows Alerts, Flags and Events from Command Center to be exported for use in other software programs.

1.Click Setup > Events > Event Extract to display the Scheduled Event Extract window.

 

 Figure 3 - 76. Scheduled Event Extract Window

2.Click the New button to display the new Scheduled Event Extract window.

 

 Figure 3 - 77. New Scheduled Event Extract Window

uOrganization Information Setting: A general setting for the Base Installation Directory is captured during Command Center installation or upgrade.The data extracts in Command Center will use the Base Installation Directory for data extracts in the absence of a directory being specified.

3.Enter an Output File Name.

4.Choose the Output storage for event extract from the drop down

5.Enter or select the Next Event Cut Off Date.

6.Select the Event Types to include in the extract file.

7.Under Schedule select one of the following:

•The Immediately radio button.

...or...

•On specified dates radio button and then specify one or more dates separated by commas or semicolons in the text box. Most standard date formats are acceptable. If you use a date format that includes a comma, separate the dates with a semicolon.

...or...

•To Auto Schedule the Scheduled Read:

i.Select the Recurring radio button and click the calendar icon to select a start date. If you want to change the specified start time, highlight the hour and type a different hour or use the up and down arrows to change the hour. Highlight the minutes and type different minutes or use the up and down arrows to change the minutes. To select AM or PM, click the AM icon to toggle between AM and PM.

ii.Click the Show Recurrence Options link to expand the window to display the recurrence options.

 

 Figure 3 - 78. Recurrence Options

The Recurrence Options window expansion displays the following Scheduled Read options. Click the corresponding radio button to make your selection.

•Do not repeat. The Scheduled Read will occur once.

•Repeat every day. The Scheduled Read will occur daily.

•Repeat every [1-2-3-4] week(s) on Sunday through Saturday. The Scheduled Read can be set to repeat every 1, 2, 3, or 4 weeks on any, or all, of the days of the week.

•Repeat on day [ ] of each month. The Scheduled Read can be set to repeat on the same date of each month. Enter a number from 1 to 31.

•Repeat [ ] day(s) before the end of each month. The Scheduled Read can be set to repeat every month on a specified number of days before the last day of the month.

If you elect to repeat the Scheduled Read, the following two options are also available.

•Repeat until [ ]. The Scheduled Read can be set to repeat until the user specified date by clicking the calendar icon and selecting the end date for the Scheduled Read. To change the end time, highlight the hour and type a different hour. Highlight the minutes and type different minutes. To select AM or PM, click the AM icon to toggle between AM and PM.

•Repeat forever. The Scheduled Read can be set to repeat forever unless or until you change the end date.

8.Click the Save button.

Event Groups

The Event Groups window displays the event groupings seeded in Command Center.

Following is the procedure for viewing the Event Groups:

1.Select Setup > Events > Event Groups to display the Event Groups window shown.

 

 Figure 3 - 79. Event Groups

2.Click the Plus sign adjacent to a folder to view the associated events.

Event Priority

The event priority function allows the utility to create a priority that defines the frequency at which events will be extracted to the external software, for use in configuring event subscriptions.

Following is the procedure for defining event priorities:

1.Click Setup > Events > Event Priority to display the Event Priority Window.

Click the New button to display the Event Priority window.

 

 Figure 3 - 80. Event Priority

2.Enter a Priority Name. This name must be unique to the organization.

3.Select the Enabled check box to immediately enable this event priority.

4.Enter a Description for this priority (optional).

5.Select the desired Notification Frequency from the choices below. This is the frequency at which events assigned to this priority will be written to the extract file.

•Send Event Immediately. Select this option to write the event to the extract file immediately

•Send Events in Groups Every _ Minutes. Select this option to and enter the number of minutes to write events to the extract file at the specified frequency.

6.Click the Save button.

Event Subscriptions

The Events Subscriptions window allows the user to assign events to specific event priorities, created previously, and provide the URL, user name, and password to the subscribing external system.

Following is the procedure for creating a new Event Subscription:

1.Click Setup > Events > Event Subscription to display the Event Subscription window.

Click the New button to display the Event Subscriptions Details window.

 

 Figure 3 - 81. Event Subscription Details

2.Enter the Subscriber Name. The name must be unique to the organization.

3.Select the Enabled check box to enable the subscription.

4.Enter the Notification Address. This must be the complete url to the location of the external software.

5.Notification Username. If required, enter the user name to access the subscribing external system.

6.Password. If required, enter the password to access the subscribing external system.

7.Service Requires Mutual Authentication. If the application is using SSL, this check box must be selected.

8.Basic Authentication. Check this box if the message format is CIM 2nd Edition.

9.Available Events - Event Group.

•Select the desired Event Group from the drop down box, to populate the available events list.

•Select the events to be included in this subscription by highlighting and clicking >>.

•To remove a selected item, highlight the event and click <<

10.Subscribe Events - Priority. Select the desired Event Priority from the drop-down box.

11.Click the Save button.

Firmware

These screens display hardware firmware that is available for installation. You may also use it to import additional firmware and to delete firmware that is no longer in use.

1.Click Setup > Firmware > and select firmware type.

The Firmware window will be displayed.

 

 Figure 3 - 82. Collector Firmware Window

2.Click the Import button to import a new firmware package. The Import Firmware window will be displayed.

 

 Figure 3 - 83. Import Firmware Window

3.Enter the path to the Firmware package file,

...or...

Click the Browse button to navigate to the file.

4.After locating the file, click the Import button to load the firmware into Command Center.

The firmware will be displayed in the Inventory Firmware window.

5.To remove a firmware package, select the check box(es) for any firmware package and click the Delete button.

Import Firmware/DCW .hfz files

DCW, RF endpoint firmware, meter firmware and HAN firmware are provided, as .hfz zip files, with the Command Center installation files. These files should be imported to Command Center for future use in upgrading network devices.

NOTE: Best practice is to upload all of the .hfz files on installation or upgrade of the Command Center software. The files for the firmware versions for all devices deployed in the field must be populated in Command Center.

There are several types of .hfz files, including:

•Collector Code

•Module Firmware

•DCW

•Meter Firmware

•ZigBee

Following is the procedure for uploading Endpoint firmware .hfz files:

1.Select Setup > Firmware > Communication Module.   

The Communication Module Firmware window will open, shown in Figure 3 - 84, displaying a list of the endpoint firmware that are currently available in the Command Center database. When Command Center is installed for the first time this list will be empty.

NOTE: If a firmware is imported before any meter registration for a particular endpoint model has occurred, the Endpoint Model may display No Model. Once an endpoint of this model type has registered in Command Center, the Endpoint Model name will display.

 

 Figure 3 - 84. Communication Module Firmware

2.Click Import. The Import Firmware window will open, shown in Figure 3 - 85.

 

 Figure 3 - 85. Import Firmware

3.Firmware Package File. Enter the path to the RF endpoint firmware hfz file.

...or...

Click Browse to browse to the file location.

4.Click Import. The RF Endpoint Firmware window will open, displaying the new firmware.

NOTE: DCW, ZigBee firmware, Collector firmware, HAN firmware and Meter firmware are also imported in this manner.

Import Small DCW

Import Small DCW into Command Center. Small DCWs (Digital Control Word) are small programs which perform specific actions on the communications module.

1.Click Setup > Import Small DCW.

The Import Small DCW window will be displayed.

 

 Figure 3 - 86. Import Small DCW

2.Enter the path to the Small DCW,

...or...

Use the Browse button to locate the small DCW file.

 

 Figure 3 - 87. Import Small DCW Window

3.Enter a Display name for the small DCW.

4.Enter a Small DCW description.

5.If true, select the check-box for This setting should be selected if the Small DCW invokes the AMR DCW on the device.

6.Click the Import button.

7.To remove a Small DCW, select the check box(es) for any firmware package and click the Delete button.

DCW Error Response Codes

The following DCW Error Response Codes are returned in Command Center:

DCWERR_INVALID_RESPONSE_LENGTH

•   This code is returned when the DCW brings data, usually configuration data, back so that it can process other readings.

•LP config

•Snap read config

•   It can mean several other things. Anything that prevents the DCW from receiving the amount of data that it expects can cause this error, including:

•The password is wrong.

•The meter is not responding.

•The meter is not configured for the type of data that is being requested

•The meter is busy.

•The meter has just been reprogrammed or deployed and it does not yet been running long enough to be able to process the request.

•A meter has to be running a day, at least across midnight, for a self read to be available.

•A meter has to be running at least as long as a push period for LP to work

DCWERR_NO_VALID_BLOCKS

•   This code indicates that the meter has been running long enough to have captured data, i.e. the status tables are populated, but the meter does not have any data for the request.

•Self reads. The self read table is present but reports zero valid entries.

•The LP tables are present but report no active blocks.

•The LP sub-system in the meter is not active.

DCWERR_INVALID_INTERVAL_COUNT

•This code is for LP only.

•It was added for Focus AX meters with metrology version 6.27.

•The meter reports that the number of valid intervals in the current block is greater than the maximum allowed number of intervals in a block.

•The number of valid intervals is stuck and does not increment.

DCWERR_INVALID_INTERVAL_LENGTH

•   Prior to 13X DCWs, the code indicates that the LP interval length is less than five minutes.

•DCW 13.X and above indicates that the LP interval length is 0.

DCWERR_INT_REQUEST_OUT_OF_RANGE

•      All the requested intervals are in the future, i.e. they don't exist in the meter yet.

•All the requested intervals are prior to the LP data in the meter.

•Usually indicates that the start time in the request is bad, but it can also happen during the first few LP pushes until the meter has accumulated enough data.

DCWERR_BLK_REQUEST_OUT_OF_RANGE

•         There are not enough blocks of data to satisfy the request.

DCWERR_LP_NOT_ACTIVE

•            This event is not reported by the current DCWs. The DCW will return DCWERR_NO_VALID_BLOCKS if the set is not active.

DCWERR_INVALID_PARAMETER

•               This code is returned by an S4x when processing on demand reads of decade 20 tables, using the mapped data definition.

•The code indicates that not enough parameters were provided. The DCW expects nine bytes of parameters.

DCWERR_LP_SET_NOT_SUPPORTED

•                  This code is returned when a request asks for a ANSI LP set that is not available on the meter, i.e. asking for ANSI LP Set 4 on a Focus AX would return this error.

DCWERR_PASSTHROUGH_READ_FAILED

•                  This code is returned when a DCW tries to read data from a meter and never receives a response.