Power Manager for SmartStruxure: Best Practices

Issue

There are some best practices and tips that can be used to save engineering time when setting up a Power Manger for SmartStruxure system.

To find out the difference between Power Manager and Power Monitoring Expert (PME) see Lessons Learned Article #18121.

Product Line

SmartStruxure Solution

Environment

  • StruxureWare Building Operation
  • Workstation
  • Power Manager
  • Power Monitoring Expert
  • ETL
  • Integration Tool

Cause

The following topics should be considered before and during the implementation of the Power Manager for SmartStruxure offering to achieve the cleanest and most effective database. 

 

For more information outside of this Lessons Learned article including update rate, IT considerations, software compatibility, server specification, hard drive space, etc; see the Power Manger for SmartStruxure Solution - Design Guide.

For more information outside of this Lessons Learned article including the actual install of the software and how to use the software, see the Power Manager for SmartStruxure Solution - Integration Manual

For more information regarding Power Monitoring Expert please visit the Solutions Expert Community. Here you can find documentation, content, and additional help. 

Resolution

Start by reading through the documentation found on The Exchange Extranet especially the Deploy Power Manager for SmartStruxure Solution in a Day document. 

Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange.


General

  • Always install the Power Manager software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator
  • Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to PME. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process. 
  • See Article #18672 for information on how to improve the scan time of the ETL load sources function. 

 


SQL Server

  • It is not recommended to install Power Monitoring Expert (PME) on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills.
  • The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.

 


Selecting Between Architecture 1 and 2

The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement.

Most of the Schneider Electric meters and circuit breakers are fully supported by PME. This means that PME has built-in drivers to utilize the full function of the device and the required commission time is minimized. For more information on the differences between architecture 1 and 2 see the Power Manager for SmartStruxure Solution - Design Guide.

 


Architecture 1: Logging data in StruxureWare Building Operation (SBO)

  • It is recommended to use interval trend logs to log the raw data coming in from the meters. 
  • The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. Power Manger dashboards and reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into Power Monitoring Expert (PME) as it can be calculated later based off of the 15 minute trend log value. 
  • If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to Power Manager to avoid the lagging between Extended Trendlogs and Trendlogs. 

 


ETL

  • StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs.
  • For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with :) in the settings.
  • For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True.
  • The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name. 
     
  • The Target Measurement field is very important to set correctly as it will not bring the data over to PME correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manger for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use.