EGX300, Com'X 510 and Com'X 200/210

EcoStruxure™ Power Monitoring Expert 9.0

ETL Data Migration Guide
7EN42-0173-00
08/2018
Legal Information
The Schneider Electric brand and any registered trademarks of Schneider Electric Industries SAS
referred to in this guide are the sole property of Schneider Electric SA and its subsidiaries. They
may not be used for any purpose without the owner's permission, given in writing. This guide and its
content are protected, within the meaning of the French intellectual property code (Code de la
propriété intellectuelle français, referred to hereafter as "the Code"), under the laws of copyright
covering texts, drawings and models, as well as by trademark law. You agree not to reproduce,
other than for your own personal, noncommercial use as defined in the Code, all or part of this guide
on any medium whatsoever without Schneider Electric's permission, given in writing. You also
agree not to establish any hypertext links to this guide or its content. Schneider Electric does not
grant any right or license for the personal and noncommercial use of the guide or its content, except
for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are
reserved.

Electrical equipment should be installed, operated, serviced and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of
the use of this material.

As standards, specifications and designs change from time to time, please ask for confirmation of
the information given in this publication.
Safety Information
Important Information
Read these instructions carefully and look at the equipment to become familiar with the
device before trying to install, operate, service or maintain it. The following special
messages may appear throughout this bulletin or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies a procedure.

The addition of either symbol to a "Danger" or "Warning" safety label

indicates that an electrical hazard exists which will result in personal injury if
the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal
injury hazards. Obey all safety messages that follow this symbol to avoid
possible injury or death.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or serious
injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury.

Please Note
Electrical equipment should be installed, operated, serviced and maintained only by qualified
personnel. No responsibility is assumed by Schneider ElectricSiemens Industry for any
consequences arising out of the use of this material.

A qualified person is one who has skills and knowledge related to the construction, installation, and
operation of electrical equipment and has received safety training to recognize and avoid the
hazards involved.
 ETL Data Migration Guide

Contents
Safety Precautions 6
Introduction 7
Additional information 7
Overview 7
Terminology 7
Before you begin 9
For new installations 9
EGX300 device configuration 9
Device Log Export 9
Time Zone Offset 10
Com'X 510 device configuration 10
Folders for CSV and ZIP files 10
Information to collect before you start 10
ETL job upgrade consideration 10
Upgrading previous setup types 11
Installing the EGX300 and Com'X 510 ETL Package 12
Configuring the File Upload Web application 14
Starting the Configuration tool 15
Creating and configuring a new EGX300 ETL job 16
Connections – Define database connections 16
Source Mappings – Define EGX sources 17
File Handling – Specify processing for valid and invalid files 19
Preview Mappings – Review the PME source names 20
Verify the Enable Recorder and Channel Creation setting 20
Start the ETL job and verify data 21
EGX300 to PME ETL user interface 22
Connections 22
Source Mappings 24
File Handling 26
Preview Mappings 27
Appendices 28
Appendix A: Default job settings 28
Appendix B: Supported device types and EGX topics 29
Device types 29
EGX topics 29
Appendix C: Unsupported device types and EGX topics 30
Appendix D: Logging options for ETL jobs 32
Appendix E: Choosing how to run your ETL job 34
Running the ETL job as a Windows Service 34
Running the ETL job as a batch file using Windows Task Scheduler 35
Running the ETL job using the command line 36

Page 4 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide

Appendix F: Modifying an existing ETL job 36

Appendix G: File processing and system resources 36
Appendix H: Importing data from Twido PLCs to existing logical devices 37

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 5

Safety Precautions ETL Data Migration Guide

Safety Precautions
During installation or use of this software, pay attention to all safety messages that occur in the
software and that are included in the documentation. The following safety messages apply to this
software in its entirety.

WARNING
UNINTENDED EQUIPMENT OPERATION
• Do not use the software or devices for critical control or protection applications where human
or equipment safety relies on the operation of the control action.
• Do not use the software to control time-critical functions.
• Do not use the software to control remote equipment without proper access control and status
feedback.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

WARNING
INACCURATE DATA RESULTS
• Do not incorrectly configure the software or the devices.
• Do not base your maintenance or service actions solely on messages and information
displayed by the software.
• Do not rely solely on software messages and reports to determine if the system is functioning
correctly or meeting all applicable standards and requirements.
• Consider the implications of unanticipated transmission delays or failures of communications
links.
Failure to follow these instructions can result in death, serious injury, equipment
damage, or permanent loss of data.

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Use cybersecurity best practices to help prevent unauthorized access to the software.

Failure to follow these instructions can result in death, serious injury, equipment
damage, or permanent loss of data.

Work with facility IT System Administrators to ensure that the system adheres to the site-specific
cybersecurity policies.

Page 6 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Introduction

Introduction
This document explains how to install and configure the necessary applications for migration of
PowerLogic™ EGX300 and Com'X 510 device data to EcoStruxure™ Power Monitoring Expert 9.0.
This document also explains how to start the data upload and verify that the files are being
processed.

This deployment guide covers the EGX300 to EcoStruxure Power Monitoring Configuration tool, the
ETL Engine, and the File Upload web application. Pertinent aspects of the ETL Management tool
are also described.

Additional information
l PowerLogic™ EGX300 Device Configuration Guide, 7EN42-0095-00

l PowerLogic™ Ethernet Gateway EGX300 User Guide, 63230-319-216B4

l Com'X 510 User Manual, fw 3.0. This guide is available on the Exchange Community; regis-
tration is required.

l EcoStruxure™ Power Monitoring Expert 9.0 System Guide

Overview
The ETL Engine is a software application that moves data from one data store to another using plug
ins. The ETL Engine supports moving data between many different data stores. This document
describes how to creating an ETL job that moves log data from EGX300 or Com'X 510 CSV files
into a Power Monitoring Expert database.

Before the ETL Engine can move data, you provide configuration information to describe the where,
what, and how of data migration. The precise details vary from system to system, but typically
include database connection strings, data source information, and frequency of data migration.
Collectively these configuration details are called a job and are stored in an XML file known as a job
file. You use the EGX300 to ION Enterprise Configuration tool to define the job for the ETL Engine to
process.

NOTE: The term ION Enterprise is used in several locations in this document. This is the product
name of previous versions of EcoStruxure Power Monitoring Expert and some references to it still
exist in the configuration tools.

For the EGX300 to Power Monitoring Expert data migration path, many of these configuration
variables are known ahead of time. The Configuration tool was developed to simplify the migration
process.

The Configuration tool supplements the full Tactical Solutions Admin Tool. The Configuration tool
does not fully duplicate the functionality of the Admin Tool. For example, it does not support
Quantity editing or Position Counter viewing.

NOTE: Do not run the Configuration tool and the Tactical Solutions Admin Tool simultaneously.

Terminology
The following terminology is used throughout this document.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 7

Introduction ETL Data Migration Guide

EGX300 To ION Enterprise Configuration tool: An application that allows you to create and
configure ETL jobs that migrate EGX300 CSV log data into a EcoStruxure Power Monitoring Expert
system.

CSV files: Comma-separated value files. Text files that use a comma to separate field values
within each line. EGX300 and Com'X 510 gateways can be configured to export their log data to
CSV files. The ETL Engine reads the CSV files and extracts the device data to be loaded into
Power Monitoring Expert.

ETL Engine: A flexible interoperability tool that transfers data from one data store to another. The
ETL Engine executes ETL jobs that you create and configure.

ETL Job: An ETL job consists of one extract task and one load task. Transform tasks are optional.
An ETL job can also contain multiple transform tasks.

Each ETL job functions as an independent data adapter program and moves data from one data
store to another. ETL jobs are built from lower level building blocks called ETL tasks.

ETL Tasks: There are three types of tasks – extract, transform, and load.

l Extract tasks: Read data from a specific data store or format, and converts it to a common
format that can be understood by other tasks.

l Transform tasks: Transform tasks are optional tasks in an ETL job. They modify data in some
way, and perform operations on the data in the common format. Transform tasks are typically
not associated with any data store.

l Load tasks: Write data to a specific data store or format

Page 8 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Before you begin

Before you begin

For new installations
The EGX300 to ION Enterprise ETL Installer stops the ION Log Inserter Service. To avoid
interrupting data collection, you should start the ION Log Inserter Service between interval
boundaries if your system includes any PC logging. For example, if your system performs 15-
minute interval PC logging, start the ION Log Inserter Service between boundary intervals so that it
is already running when the next 15-minute interval boundary occurs.

NOTICE
LOSS OF DATA
• Do not start the ION Log Inserter Service on an interval boundary if your system includes PC
Logging, otherwise data collection can be interrupted.
• Start the ION Log Inserter Service between interval boundaries.
Failure to follow these instructions can result in a loss of data.

To start the ION Log Inserter Service:

1. Open Windows Services and then locate the ION Log Inserter Service.

2. Right-click ION Log Inserter Service and click Start.

3. Verify that Started appears in the Status column, and then close Windows Services.

EGX300 device configuration

Each EGX300 has a configuration web application that allows you to control how the EGX300
exports and transports logs to CSV files. The CSV files must have correct data for use in
EcoStruxure Power Monitoring Expert.

NOTE: The EGX300 device must be fully configured before you can run ETL jobs to process CSV
files. Refer to the EGX300 Device Configuration Guide for instructions to configure the device.

The following sections highlight the critical parameters you need to set in the device’s web setup
application.

Device Log Export

The settings on the Device Log Export page must be defined to periodically send files to a location
accessible by ETL. If you have chosen to accomplish this using the Transport method of “HTTP,”
you must run the ETL Package installer on a server with Internet Information Services (IIS)
installed. The Power Monitoring Expert application server is the recommended choice.

When configuring Device Log Export, take note of the Schedule parameter. This should be set to
use “Logging Interval.” This knowledge will help you choose the appropriate settings when you are
configuring the ETL job. For example, if the logging interval is set to 15 minutes, you might setup the
ETL job to sleep for 15 minutes between job runs.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 9

Before you begin ETL Data Migration Guide

Time Zone Offset

Each EGX300 device must also be configured with the correct Time Zone Offset on the Date and
Time page. The ETL Engine uses this offset along with the local timestamps in the CSV files to get
the UTC timestamp for each numeric value.

Com'X 510 device configuration

For detailed information on configuring a Com'X 510 device to export and transport logs to CSV
files, refer to the Com'X 510 User Manual.

Folders for CSV and ZIP files

You must create empty folders to store valid and invalid CSV and ZIP files that the ETL Engine will
process. Define one folder for valid files and a separate folder for invalid files. You will later
configure the ETL job to move files to these locations.

Information to collect before you start

Obtain the following details before you start using the EGX300 To ION Enterprise Configuration tool
to define the ETL job.

Database connection strings for ION_Data and ION_Network – Note the server name that
hosts the ION_Data and ION_Network databases. If you plan on using SQL authentication, note
the username and password. If you are using Windows authentication you do not need a username
or password.

EGX300 or Com'X 510 File Directory – The full path of the directory containing the CSV or ZIP
files being exported by the EGX300 or Com'X 510 devices. Note the number of CSV or ZIP files
currently in the EGX300 File Directory.

Valid Directory – The full path of the valid CSV file directory you created.

Invalid Directory – The full path of the invalid CSV file directory you created.

EGX Device Logging Settings – Take note of the settings on the Device Logging page and the
Device Log Export page in the EGX300 web setup application. These settings provide an
approximate frequency of how often new CSV files will be generated and size of each CSV file. The
typical logging interval is 15 minutes.

Com'X 510 Device Logging Settings – Note the Publication settings on the Com'X 510. For more
information, refer to the Publication section in the Com'X 510 User Manual.

EGX Time Zone Offset– Note the Time Zone Offset of each EGX300 device. This will allow you to
choose the correct time zone when configuring the ETL job. All EGX300 devices communicating
with the Power Monitoring Expert system must be in the same time zone.

ETL job upgrade consideration

If you intend to upgrade ETL jobs that you created with the previous version of the EGX300 to ION
Enterprise Configuration utility, see "Verify the Enable Recorder and Channel Creation setting" on
page 20 for additional information.

Page 10 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Before you begin

Upgrading previous setup types

The EGX300 to Power Monitoring Expert ETL Installer gives you the option to choose one of the
following setup types:

l Install EGX300 to ION Enterprise ETL – Complete

l Install EGX300 to ION Enterprise ETL – No Website

l Install EGX300 to ION Enterprise ETL – Website only

For Power Monitoring Expert 9.0 and 8.2, it is assumed that the previous setup type was Install
EGX300 to ION Enterprise ETL – Complete. If that is the case, run the Installer and specify the
same setup type. However, if the previous installation used either the No Website or Website only
setup type, use the Uninstall process in Programs and Features to uninstall the EGX300 to ION
Enterprise ETL program before running the Installer to reinstall one of these setup types.

To determine the previous setup type:

Open Internet Information Services (IIS) Manager, right-click EGXFileUpload, and select
Properties.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 11

Installing the EGX300 and Com'X 510 ETL Package ETL Data Migration Guide

Installing the EGX300 and Com'X 510 ETL Package

The “EGX300 and Com'X 510 ETL Package for Power Monitoring Expert” installer requires specific
information, such as the destination folder for the installed files and the connection information for
the Power Monitoring Expert databases.

1. Run setup.exe to start the installation.

2. Read and agree to the license agreement.

3. On the Gather Information step, choose a Setup Type.

The Setup Type options are:

Install EGX300 to ION Enterprise ETL – Complete. This is the recommended setup type
when installing ETL on the Power Monitoring Expert application server. Choosing this option
will install the full package, including ETL, the job configuration UI, and the web application.

Install EGX300 to ION Enterprise ETL – No Website. This option installs the ETL package
without the web application. This option is useful when installing ETL on a server that does not
have IIS installed.

Install EGX300 to ION Enterprise ETL – Website only. This option installs the web
application without the ETL component. This option is useful when ETL resides on another
server. Under this setup type, the web site would likely be configured to write CSV files to a
share folder that ETL can access.

4. Click Next to continue.

5. Select a destination folder for the files.

6. Click Next.

The installer may notify you that the folder you have selected does not exist and ask for
permission to create the folder.

Page 12 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Installing the EGX300 and Com'X 510 ETL Package

The Check System summary screen appears. All items should be marked with “Success” and
a check mark.

7. Click Next. The Ready to Configure screen appears

8. Review the selections, including the message describing the behavior of the Install button.

9. Once you have verified all selections, click Install to proceed.

Once the installer completes the Copy Files step, it shows the “Configuration Complete” and
“Configuration successful” messages.

10. Click Next to go to the Complete page, which displays a message that the installation com-
pleted successfully.

11. Click Close to exit the installer.

After a successful installation, the following components are installed on your system:

l EGX File Upload web application hosted in IIS. This application receives incoming CSV files
from EGX300 devices via HTTP

l ETL Engine application

l EGX To ION Enterprise Configuration tool

l A new stored procedure in the ION_Data database.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 13

Configuring the File Upload Web application ETL Data Migration Guide

Configuring the File Upload Web application

After completing the installation, configure the EGX File Upload Web application by editing the
HttpFilePost.config file. This web application accepts CSV or ZIP files via HTTP and saves
them to the location specified in the configuration file.

To configure the EGX File Upload Web application:

1. Open Windows Explorer and browse to the folder containing the Web application’s files.

By default, this is C:\Program Files (x86)\Schneider Electric\EGX300 to

EcoStruxure Power Monitoring ETL\EGXFileUpload.

2. Locate the HttpFilePost.config file and then open the file in a text editor such as Win-
dows Notepad.

NOTE: Create a backup copy of this file if desired and move the backup to a separate folder.

3. Fill in a value for the SaveLocation setting. This is the full path to the folder to which the
EGX CSV files will be saved to.

4. If you are using a Com'X 510, change the value of the AllowedFileNameExtensions set-
ting to include zip files. For example, edit the setting to be either of the following:
<AllowedFileNameExtensions>.csv:.txt:.zip</AllowedFileNameExtensio
ns>

or

<AllowedFileNameExtensions>.zip</AllowedFileNameExtensions>

5. Review the values for the remaining settings, which can be left unchanged in the majority of
cases:

DuplicateFileHandlingMethod: Specifies what to do if a file is uploaded that has a

name of a file that already exists in the folder. The following is a list of possible values. The
default and recommended value is Rename.

Ignore Do nothing. Leave the existing file intact and delete the new file.
Overwrite Replace the existing file with the new file.
Rename Rename the new file so that it no longer conflicts with another existing file.

6. Save the HttpFilePost.config file and exit the text editor program. The new settings will
be used automatically on the next POST.

Page 14 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Starting the Configuration tool

Starting the Configuration tool

The EGX300 To ION Enterprise Configuration tool is located in the main ETL folder you chose while
running the ETL Package installer. By default this is:
C:\Program Files\Schneider Electric\EGX300 to Power Monitoring Expert
ETL

1. Double-click EGX300ToIONEConfiguration.exe.

The EGX300 to ION Enterprise Configuration screen opens.

The EGX300 ETL tool contains four sections: Connections, Source Mappings, File
Handling, and Preview Mappings.

2. Navigate among the sections by clicking the section name in the list.

3. Configure the ETL job.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 15

Creating and configuring a new EGX300 ETL job ETL Data Migration Guide

Creating and configuring a new EGX300 ETL job

After completing the installation, proceed with the following steps to create and configure an ETL job
that reads data from CSV files generated by EGX300 devices or ZIP files generated from Com'X
510 devices, and writes that data to a Power Monitoring Expert system.

Connections – Define database connections

1. Click Create New Job to open the New Job dialog.

2. Enter an appropriate name for the ETL job, such as “EGX to PME Job 1.”

3. Click OK.

4. Under Time Between Job Runs, select the appropriate duration.

Refer to the EGX Device Log Export Settings you collected prior to installation to determine
how often new files arrive from the EGX devices.

5. Next to the EGX 300 File Directory box, click the Browse button and select the folder where
the EGX300 devices are exporting the CSV files.

6. Choose either the CSV or ZIP radio button. If reading files from an EGX300, click CSV. If read-
ing files from a Com'X 510, click ZIP.

7. Under ION Enterprise Data Database Connection, click Configure Connection to open the
SQL Server Configuration dialog.

Page 16 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Creating and configuring a new EGX300 ETL job

8. Enter the server, database name, and authentication information for the ION_Data database.

9. Click Test Connection to verify the connection settings.

10. Click OK to return to the main configuration dialog.

11. Under ION Enterprise Network Database Connection, click Configure Connection.

The SQL Server Configuration dialog opens.

12. Enter the server, database name, and authentication information for the ION_Network data-
base.

13. Click Test Connection to verify the connection settings.

14. Click OK to return to the main configuration dialog.

15. On the Connections screen, click Apply.

Source Mappings – Define EGX sources

In Source Mappings you add sources to the configuration, set the source time zone, and edit both
the Power Monitoring Expert group and source names.

NOTE: The EGX300 File Directory must be created before you define the EGX300 or Com'X 510
sources.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 17

Creating and configuring a new EGX300 ETL job ETL Data Migration Guide

1. In the configuration screen, click Source Mappings.

2. From Source Time Zone, select the time zone that matches the UTC offset for the EGX300
or Com'X 510 sources being imported.

NOTE: Review the EGX Time Zone Parameters you collected prior to installation to
determine the time zone offset. You are limited to one time zone per job when editing jobs
using the EGX to ION Enterprise Configuration user interface.

3. Click Add EGX Sources.

The configuration tool performs a lookup of source names in the CSV or ZIP files in the
EGX300 File Directory.

You may be prompted for confirmation to proceed if the configuration tool detects a large
number of files in the input directory.

A status bar indicates the progress of the lookup. All discovered sources appear in the grid.

NOTE: The Configuration tool discovers sources only when CSV files for those sources are
in the EGX300 File Directory. Only devices on the supported device types list will be added
to the job. If sources are added to the EGX300 File Directory after you first run the tool, you
need to rerun it to permit discovery of the new files.

When importing data from a Twido PLC, refer to "Importing data from Twido PLCs to existing
logical devices" on page 37 for instructions on how to cause ETL to automatically discover
existing logical devices associated with the PLCs. These logical devices are configured in
the Power Monitoring Management Console component.

4. In the grid, fill in the ION Enterprise Group values for each EGX source:
a. Select a row in the grid for the source you want to update.

b. Click Edit ION Enterprise Group and enter the new group name in the text box dialog.

An ION Group name can be at most 90 characters in length and contain only alphanumeric
characters or underscores: a-z, A-Z, 0-9, __.

Page 18 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Creating and configuring a new EGX300 ETL job

c. You can set the ION Enterprise Group value for multiple sources at once:

Select multiple rows with Shift-select or Ctrl-select and then click Edit ION Enterprise
Group.

NOTE: This is an important step as it allows you to give each source a unique name. Review
the group names you have chosen after filling them in. To avoid the need to correct source
names after they are created, it is recommended that you define the source names before the
job creates them in Power Monitoring Expert.

Each source follows the convention of Group.Source when it is created in Power

Monitoring Expert.

File Handling – Specify processing for valid and invalid files

In File Handling you can define the way the ETL Engine processes valid files and invalid files at
the end of a job run.

NOTE: Do not disable the file handling feature. File handling is a key feature of the ETL job and is
necessary to ensure proper behavior. The only reason to disable file handling is for troubleshooting
or test scenarios.

To specify processing for valid and invalid files:

1. Click File Handling.

2. Select the Enable Valid File Handling option.

3. In the File Handling Strategy box, select the action to perform. See "File Handling" on page
26 for more information about the options.

NOTE: Any topics that are not on the supported topic list found in "Supported device types
and EGX topics" on page 29 will not be processed by the job. Be aware that if you choose to
delete files as part of your File Handling Strategy the data from these unsupported topics will
be lost. Also consider disk space if you choose to keep the files.

4. In the File Directory box, enter the folder or click the browse button to select the folder.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 19

Creating and configuring a new EGX300 ETL job ETL Data Migration Guide

5. Under File Life Span, select the duration that the tool will keep files in the directory.

6. Select the Enable Invalid File Handling option.

7. Define the settings for the invalid CSV files.

NOTE: Set the File Handling Strategy to “Move” if you want to keep all files that are
marked invalid. This strategy is useful for troubleshooting. It is not usually desirable to delete
invalid files, since you should investigate what caused them to be invalid.

8. Click Apply.

Preview Mappings – Review the PME source names

To review the Power Monitoring Expert source names you have chosen for the devices listed in the
EGX CSV files:

1. Click Preview Mappings.

2. If any names are incorrect, click Source Mapping and change the names as appropriate.

Verify the Enable Recorder and Channel Creation setting

The load task setting for Enable Recorder and Channel Creation should be set to False.

To verify the setting:

1. Open TacticalSolutionsManager.

2. Edit the EGX300 to Power Monitoring Expert job.

3. Click the Tasks tab.

4. Select the load task. It will be one of Power Monitoring Expert Load Task or ION Enter-
prise Load Task V2.

The settings are in the Property grid at the right in the bottom-left pane.

5. Verify that the Enable Recorder and Channel Creation setting is set to False. If it is set to
True, change it to False.

6. Click OK to save your job.

Page 20 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Creating and configuring a new EGX300 ETL job

Start the ETL job and verify data

1. Click Preview Mappings and verify that all settings, including source names and group
names, are correct.

2. Click Connections.

3. Check the Run Job As A Windows Service After Editing option.

NOTE: The default logging options are appropriate for most installations. To customize the
logging options for the ETL job, refer to "Unsupported device types and EGX topics" on page
30.

4. Click OK to save the job. The configuration tool closes and the ETL job starts running as a
Windows service.

The ETL Engine processes the job and begins to move files to the valid folder you specified
above.

You should also be able to view the device data by creating Tabular and Load Profile reports
using the Reports application in the Web Applications component of Power Monitoring Expert.
Refer to the Web Applications online help for instructions about generating and viewing
reports.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 21

EGX300 to PME ETL user interface ETL Data Migration Guide

EGX300 to PME ETL user interface

The EGX300 To ION Enterprise Configuration tool is designed to supplement the full Tactical
Solutions Admin Tool. The Configuration tool does not fully duplicate the functionality of the Admin
Tool. For example, it does not support Quantity editing or Position Counter viewing.

NOTE: Do not run the Configuration tool and the Tactical Solutions Admin Tool simultaneously.

The user interface of the configuration tool contains four sections: Connections, Source
Mappings, File Handling and Preview Mappings. You can navigate among the sections by
clicking the section name in the list.

The following topics add more details about each section of the Configuration tool.

Connections
The Connections section deals with job management, such as where data is coming from and
where it is going.

Job Management
The first thing you should do is create a job file to store the configuration settings. This is done
through the job management controls at the top of the Connections section:

IMAGE

Here you can:

l Create a new job or delete an existing job.

l Select an existing job to edit.

l Set the time between job runs. This corresponds to the length of time between job executions
when the job is run as a Windows Service.

Page 22 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide EGX300 to PME ETL user interface

By default the Windows Service for the job will not be started once the job editing has been
completed. This behavior can be controlled through the check box as shown:

EGX300 Data
Meter data is extracted from CSV files output by the EGX300. Before a job can run successfully,
the CSV drop file location must be specified:

Power Monitoring Expert Data

Meter data is loaded into Power Monitoring Expert databases. Before a job can be run successfully,
you must specify the connection strings to both the ION_Data and ION_Network databases:

Click Configure Connection to open the SQL Server Configuration dialog:

Here you must complete the following settings:

l Server Name: The name of the database server.

l Database Name: The name of the database.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 23

EGX300 to PME ETL user interface ETL Data Migration Guide

l Authentication: Select the method to use. If using SQL Server Authentication, enter the User
Name and the Password.

l Test Connection: Click this to validate the connection string.

NOTE: You should verify the connection string for the ION_Network database and the ION_Data
database before attempting to run the job.

Source Mappings
Source Mappings lets you add sources to the configuration, set the source time zone, and edit the
ION Enterprise group names and source names.

EGX or Com'X Sources

To add EGX sources to the configuration, click Add EGX Sources.

The configuration utility scans the EGX300 CSV File Directory configured in the Connections
section. This directory must be specified prior to clicking Add EGX Sources and CSV files from
the EGX300 device must be present in this directory.

The configuration tool adds sources for all the supported device types it finds and maps any
discovered EGX topics to their Power Monitoring Expert counterparts, if those topics are supported.
The configuration tool also enters suggested ION Source names.

If any ION Group names are missing, you must enter the name for each source prior to saving.

NOTE: The list of supported device types and supported topics are defined in "Supported device
types and EGX topics" on page 29. See "Unsupported device types and EGX topics" on page 30
for information on mapping unsupported devices and topics.

Source Time Zone

This drop down sets the time zone for all the sources contained in the grid.

Page 24 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide EGX300 to PME ETL user interface

Source Mapping Grid

The grid contains a list of all supported EGX sources. The data columns are: MAC Address, EGX
Source Name, Device Type, ION Enterprise Group, and ION Enterprise Source. The left-most
column indicates the status of the row, as follows:

Indicator Meaning
Newly added row

Modified row.

Error in row. All source rows must

have both a valid ION Group and
ION Source Name, and each Group-
Source name combination must be
unique.

When dealing with large mapping sets, you can filter the data by using the filters in the column
headers.

BCPM Devices
For BCPM devices, the configuration tool will automatically setup downstream sources for any
discovered circuits, if the circuits follow the naming convention “Circuit #”.

ION sources created for BCPM circuits have the suffix _1PH_Ch_ appended to their Power
Monitoring Expert source names. The main BCPM source has no suffix appended to its ION source
name.

Only the main BCPM sources are represented in the grid. You can view the linked circuit sources in
the Preview Mappings section.

Power Monitoring Expert Group Names

To edit the Power Monitoring Expert Group Name select one or more rows and click Edit ION
Enterprise Group. The ION Group name will be updated for all selected rows. An ION Group name
can be at most 90 characters in length and contain only alphanumeric characters or underscores: a-
z, A-Z, 0-9, __.

Power Monitoring Expert Source Names

To edit an Power Monitoring Expert Source Name select the desired row in the grid and click Edit
ION Enterprise Source. An ION Source name can be at most 90 characters in length and contain
only alphanumeric characters or underscores: a-z, A-Z, 0-9, __.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 25

EGX300 to PME ETL user interface ETL Data Migration Guide

If the source selected is a BCPM source, the editor updates the main source and the circuits
respectively. When you edit a BCPM source name, an alternative name editor appears showing the
generated main and circuit source names that will be created.

File Handling
During the ETL job run, the ETL Engine attempts to extract data from the EGX CSV files.

If the ETL Engine successfully extracted data without errors, the file is valid. Under normal
operating conditions the vast majority of EGX files should be valid.

If the ETL Engine did not successfully extract data, the file is invalid. Reasons for invalid files
include:

l Structurally invalid files. An alphanumeric character is in a numeric field, or a file contains a

structurally invalid header section.

l The files come from unsupported device types.

In the File Handling section, select the Enable Valid/Invalid File Handling option to force the
ETL Engine to perform additional processing on the files after the job run is complete.

If you enable file handling, the ETL Engine processes the files in the way that you define. Various
options for the File Handling Strategy exist, such as moving files to a specific folder or deleting
files. You can define one method for valid files and a different method for invalid files.

The following table explains the different options for the File Handling Strategy:

Page 26 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide EGX300 to PME ETL user interface

Strategy Description Use this when... But consider...

Files will remain
Files to be archived indefinitely unless
Moves files to the target
indefinitely or to be deleted by a separate
Move directory after ETL is
available for another program. This leads to
done with them.
application. increased disk space
usage.
Permanently deletes the Files to be removed No archived copies of
Delete files when ETL is done from the system the input files are
with them. immediately. retained.
Moves files to the target
directory when ETL is
done with them. ETL
Files to be archived fora Choose the appropriate
Move New Files then deletes all files that
configurable time period file life span for the
and Delete Old Files have been in that
and then deleted. installation.
directory as defined in
the File Life Span
options.

If you choose either “move” option, the ETL Engine can complete the next run more efficiently by
starting at the correct position without having to track too much state information.

Preview Mappings
Preview Mappings lets you inspect the full set of source quantity mappings the ETL job will
process.

The grid organizes the mappings according to the EGX source. If any circuit sources are present,
they are grouped underneath their main source.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 27

Appendices ETL Data Migration Guide

Appendices
Appendix A: Default job settings
Many of the default settings for the Configuration tool are contained in the
EGX300ToIONEDefaultJobSettings.xml configuration file. By changing the settings in this
file you can change the behavior of the configuration tool and ultimately the underlying job.

Setting Description Default

Determines the suffix to
Select True or False
MainSourceSuffix be added to BCPM
from drop-down list.
sources
Determines the suffix to _1PH_Ch_
CircuitSourceSuffix be added to BCPM circuit
sources. ##

The regular expression

used to parse incoming
BCPM circuit names.
Circuit names not
EGX300CircuitRegexExpression \s*Circuit\s* [0-9]+
following this pattern will
not be created as sources
in the Power Monitoring
Expert system.
Determines whether the
job will be run as a
RestartService Windows Service once True
editing has been
completed.
Determines whether the
configuration utility will
map all supported
ForceQuantityMappings False
quantities regardless of
whether they exist in the
source CSV.
List of supported devices.
Devices not on the list will
not be added to the job.
SupportedDeviceTypes
See Appendix B –
"Supported Device Types
and EGX Topics".
List of supported quantity
mappings. Quantities not
on the list will not be
QuantityMappings added to the job. See
Appendix B – "Supported
Device Types and EGX
Topics".

Page 28 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Appendices

Appendix B: Supported device types and EGX topics

Device types
Select the Device and Topic filter check boxes to display the devices on the supported device
types list. These devices will be added to a job configured in the supplemental UI. Device filtering is
done on Device Type ID.

Device Type Name Device Type ID

BCM 154
BCPM Model A 150
BCPM Model A 151
BCPM Model A 151
ION6200 132
PM5350 10
PM700 8
PM9C 9000
Enercept 20
MCM 155
Twido Modular PLC D12/28/44 5002, 5003, 5004

EGX topics
Select the Device and Topic filter check boxes to display the devices on the supported device types
list. These devices will be added to a job configured in the supplemental UI. Device filtering is done
on Device Type ID.

EGX300 Topic ID EGX300 Topic Name ION Measurement Name

1003 Current A Current Phase A
1004 Current B Current Phase B
1005 Current C Current Phase C
Current Phase A Sliding Window
1701 Demand Current A
Demand Delivered
Current Phase B Sliding Window
1702 Demand Current B
Demand Delivered
Current Phase C Sliding Window
1703 Demand Current C
Demand Delivered
1042 Real Power Total (kW) Active Power
Active PowerSliding Window
1731 Demand Real Power
Demand Delivered-Received
Reactive PowerSliding Window
1732 Demand Reactive Power
Demand Delivered – Received
Active Energy Delivered-
1621 Real Energy
Received

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 29

Appendices ETL Data Migration Guide

EGX300 Topic ID EGX300 Topic Name ION Measurement Name

Reactive Energy Delivered-
1625 Reactive Energy
Received
64149 Energy Del (kWh) Active Energy Delivered
Logical Device Output
Measurement configured in
Management Console for the
Weighted Input 0.0 to
20100-20144 following Twido Input Registers
Weighted Input 2.15
(WAGES Input 0 Cumulative
Total to WAGES Input 43
Cumulative Total)

Appendix C: Unsupported device types and EGX topics

If you do not select the Device and Topic filter check boxes in the EGX300 To ION Enterprise
Configuration user interface, any unsupported devices and topics found in the EGX CSV file are
included in the results when you click Add EGX Sources. This appendix describes the steps
required to complete the mapping configuration for unsupported device types and topics.

Terminology in this appendix

Quantity Start Name: The name of the quantity as seen by the extract task. In this case, Quantity
Start Name refers to topic names in the EGX CSV files.

When you edit a job in the Tactical Solutions Admin Tool (TacticalSolutionsManager.exe),
the quantity start name is on the Mappings tab in the bottom-right table. In the Source Quantity
Pairs section, the bottom-right table is labeled Associated Quantities, which contains a Start
Name column.

Quantity End Name: The name of the quantity as seen by the load task. In this case, Quantity End
Name refers to quantity names in Power Monitoring Expert.

When you edit a job in the Tactical Solutions Admin Tool (TacticalSolutionsManager.exe),
the quantity end name is on the Mappings tab in the bottom-right table. In the Source Quantity
Pairs section, the bottom-right table is labeled Associated Quantities, which contains an End
Name column.

Before you Begin

Before you begin, you need the exact names of the quantities in Power Monitoring Expert that you
are targeting. The most precise way to find the names is to open the dbo.Quantity table in the ION_
Data database using SQL Server Management Studio. (The dbo.Quantity table is located in
Databases > ION_Data > Tables in SQL Server Management Studio.) Find the quantity of interest
in the Name column. Copy and paste the names you are targeting into notepad for use later in this
process.

Specifying a Valid Power Monitoring Expert Source and Quantity Name

Complete the following steps to specify multiple Power Monitoring Expert source and quantity
names at a time. See "For Single Source and Quantity Name" on page 31 to specify a single source
and quantity name.

Page 30 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Appendices

For multiple source and quantity names

1. Close the EGX300 to ION Enterprise Configuration utility if it is open.

2. Open the Tactical Solutions Admin Tool (TacticalSolutionsManager.exe) and edit the
job in question

3. Click the Mappings tab.

4. in the bottom-left table, select the source row you want to work with.

The quantities associated with the source are shown in the bottom-right table.

5. Select multiple quantity rows in the bottom-right table.

These are the “parent” rows of the new mapping entries you are creating. (You can select
multiple rows by Ctrl+Click or Shift+Click on the row headers.)

6. Right-click one of the selected quantity rows to open the context menu and click Edit Quant-
ity End Name and Map to New Source.

The Bulk Add Downstream Mappings dialog opens. It shows the original source and quantity
start names. The New Source End Name and the New Quantity End Name are used for
new entries. The instructions at the top of the dialog provide information about its purpose.

7. Enter a value in each row under the New Source End Name column.

This is the source name in Power Monitoring Expert.

8. Enter a value in the Enter New Quantity End Name text box at the bottom of the dialog.

This is the quantity that you are targeting in Power Monitoring Expert.

9. Click OK.

New rows are added to the bottom-left table. These are “downstream” mapping rows that are
identified with an icon of two boxes connected by an arrow in the State field. The start names
in these rows link the child mapping row back to the parent mapping row. The end names
contain the names you entered in the dialog. No changes are required for these rows.

10. Save and run your job.

For Single Source and Quantity Name

1. Repeat steps 1 through 3 under "For multiple source and quantity names" on page 31, above.

2. Select the quantity row in the bottom-right table.

3. Save your work by clicking the Apply button before proceeding.

4. Select a single quantity row in the bottom-right table.

5. Right-click the selected quantity row and select Edit Quantity Name in the menu to open the
Edit Quantity End Name dialog.

NOTE: If a message indicates that there are unsaved mapping records in the job, go back
and proceed from step 2.

6. Determine which of the options Check for this Quantity Under Other Sources and Enforce
Rule: Quantity Names Must Be Unique within Each Source to select, based on the fol-
lowing considerations:

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 31

Appendices ETL Data Migration Guide

For Check for this Quantity Under Other Sources:

If you select this option, the dialog searches for the Quantity Start Name among all of the
sources in the job. It applies the same name change to all quantities with a matching
Quantity Start Name.

If you do not select this option, the dialog applies the Quantity End Name change only to
the selected quantity row. In this case, no other sources receive the quantity end name
change.

For Enforce Rule: Quantity End Names Must Be Unique within Each Source:
If you select this option, the dialog ensures that the same quantity end name appears only
one time within each source to which the rename operation applies.

If you do not select this option, the dialog allows multiple quantities within the same
source to have the same Quantity End Name.

7. Click OK after you select your options.

8. Save and run your job.

Appendix D: Logging options for ETL jobs

Configure Logging Options
The default logging options are appropriate for most installations. This section explains how to
define logging options for ETL jobs by using the ETL Management tool. Review the details in this
section if you want a high degree of control overlogging options. If the default logging options are
appropriate for the customer, you do not need to make changes.

The ETL Management tool is the full ETL User Interface for advanced users. The ETL Management
tool is a plug-in that runs in the Tactical Solutions Manager application.

NOTE: Do not open the ETL Management tool if you already have an ETL job open in the ETL
Configuration tool.

In the ETL Management tool, the Logging tab displays options on how the job will report various
messages such as error messages, warning messages, and trace messages

Task step-in phrase:

1. Click the Connections section.

2. Uncheck the Run Job As A Windows Service After Editing option.

This will prevent the job from running as a service while you set the logging options.

3. Click OK to save the ETL job and close the configuration tool.

4. Open the ETL Management tool by running the TacticalSolutionsManager.exe file in

the main ETL Engine installation folder. The ETL Management tool opens.

5. In the Job tab, select the ETL job that you want to edit, and then click Edit.

6. Select the Logging tab. This tab lists the logging options you can select for the ETL job.

7. Review the logging options and make changes as appropriate. Each option is explained
below.

Page 32 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Appendices

In most cases, the Error Log and Windows Event Log are sufficient and the other logging
features can be ignored. Refer to the following section for details on each logging option.

8. After you configure the logging options, click OK to save the ETL job. This is the quantity that
you are targeting in Power Monitoring Expert.

9. Restart the EGX300 To EcoStruxure Power Monitoring Expert Configuration tool.

10. Select the ETL job you are configuring.

ETL Management Tool – Logging Tab

The following figure shows the Logging tab in the ETL Management tool. This section covers the
Trace Log, Error Log, and Windows Event Log sections of the screen.

Trace Log
The trace log feature is available for any ETL job. When enabled, this feature writes detailed trace
information to the trace.log file. This information includes how many source quantity pairs were
processed during the last run, and a count of data records for each pair.

This feature is designed to help advanced users in troubleshooting scenarios.

Enabling this setting can slow down job performance in some cases. If the job has an extremely
large number of pairs to process, or if you do not require such detailed trace logging, then you can
leave this feature disabled.

The Data Trace Enabled option is useful in troubleshooting scenarios, or when verifying the correct
operation of a recently created ETL job. It does slow down job performance and should be disabled
under normal operating conditions.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 33

Appendices ETL Data Migration Guide

When enabled, the Data Trace feature creates HTML files that show each pair and each data record
processed by the tasks in the ETL job. These HTML files appear in a job-specific sub-folder under
the DataTrace folder. The ETL Engine creates the DataTrace folder automatically in the ETL root
when the feature runs for the first time.

Error Log
ETL jobs report errors during execution to the error.log file. By default, this file is located in the Log
sub-folder under the ETL root folder. You can customize this location for each ETL job.

Multiple ETL jobs can report to the same error.log file. If this is undesired behavior, be sure to give
each ETL job its own error.log file using the settings shown next.

You can also specify other error log settings, such as a maximum log file size.

It is recommended to leave the Error Log feature enabled for all ETL jobs.

Windows Event Log

ETL jobs can also report errors to the Windows Event Log under a specific event log name. Select
the Enabled option to send errors to the Windows Event Log. Enter a different name for the event
log if necessary.

The Windows Event Logging feature is recommended in most cases. The Windows Event Log is a
well known location that many administrators are familiar with outside of ETL.

Of course this decision will come down to the specific needs of the installation, and the users that
will be examining the Windows Event Log on a regular basis. Enable or disable this feature as
appropriate.

Appendix E: Choosing how to run your ETL job

You can run an ETL job by:

l Running the job as a Windows service. This is the default method.

l Running the job as a batch file using Windows Task Scheduler.

l Running the job from the command line.

This section describes how to schedule an existing ETL job to run in an unattended and repeated
fashion, or by running the ETL job from the command line.

Running the ETL job as a Windows Service

This is the default method and is appropriate for most installations. The ETL Administration Tool
provides a built-in way to create a Windows service from the ETL job. The ETL job runs and then
waits for a configurable duration before it runs again. You can define the amount of time between
each run.

Advantages:

l The ETL Administration Tool simplifies setting up the service.

l The ETL service appears in the Windows Services console.

This is desirable in cases where the administrator is already managing other services for related
systems.

Page 34 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Appendices

Disadvantages:

l Very few scheduling features are available. The only configurable option in terms of scheduling
is the sleep time between executions.

l The service does not perform a true periodic execution of the job.

Each single run of the job takes a variable amount of time depending on many factors, such as
how much data it needs to process, or how much activity is taking place on the server during
the job run. The sleep time is fixed. This means that for each run the start time for the job drifts. 
This may be undesirable in situations where you need to be sure that the job starts at a specific
time each day.

Running the ETL job as a service may not be optimal when you have many different ETL jobs. The
service remains in memory even when the underlying job is sleeping.

Running the ETL job as a batch file using Windows Task Scheduler
Create a batch file and use Windows Task Scheduler to schedule when the ETL job runs. The batch
file contains the command line entry to run the job.

Advantage:

l The scheduled task performs a true periodic execution of the job. Windows Task Scheduler
allows you to schedule the job to start at precise times.

Disadvantages:

l It is more difficult to set up than the services option because you must create and test the batch
file before scheduling it. There is currently no built-in feature to create a batch file automatically
for the job.

l You must have a fully configured ETL job that runs successfully. Follow these steps if you want
to run the ETL job using the Windows Task Scheduler.

To create the batch file:

1. Use your favorite text editor and create a command line batch file (.bat) that executes the ETL
job once (using the –SingleRun option).

2. To determine what to put in your batch file:

Try running your ETL job from the command line. Open a command prompt, and change
directories to your ETL Engine’s bin folder.

Optional: View the list of available ETLEngine commands by entering the following:

ETLEngine.exe -?

Run your ETL job once using the following as an example, and substitute your ETL job’s
name:
ETLEngine.exe -SingleRun -job enterjobnamehere

NOTE: Your job name is listed on the Job tab in the ETL Administration Tool.  If your job
name contains spaces, enclose the job name in double quotes on the command line.

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 35

Appendices ETL Data Migration Guide

3. After you determine the correct command line arguments to use, create a batch file containing
the full command.

Schedule that batch file for repeated execution using Windows Task Scheduler. Refer to the
Windows Task Scheduler documentation for details.

Running the ETL job using the command line

The syntax for running an ETL job from a command line is:
ETLEngine.exe [OPTION] -Job JobName

Where OPTION can be one of the following values:

-?, -help Prints a help message and exits.

-SingleRun Performs one single run of processing and exits. 
-Service Registers a specific job as a Windows service.
-UnregService Unregisters the service associated with a specific job.
-WaitSingleRun Useful for debugging only.

Appendix F: Modifying an existing ETL job

You must manually add devices to your ETL job’s Source Mapping section before data from those
devices can be loaded into Power Monitoring Expert.

The same process applies to the following cases:

l Processing CSV files from a new EGX300.

l Processing CSV files from a new serial device added to an existing EGX300.

l Processing data from newly added topics on a device that is known to ETL.

To update an existing ETL job with new devices or topics:

1. Open the EGX300 To Power Monitoring Configuration tool by running EGX300ToIONECon-

figuration.exe.

2. Select your job from the drop down list.

3. Open the Source Mappings section and click Add EGX Sources.

The Configuration tool examines all CSV files in the input directory and adds any new sources
of the supported device type.

All existing mapping information remains intact. The only change will be new mapping
information added.

4. Click Preview Mappings and confirm the new sources or topics are added to the ETL job.

Appendix G: File processing and system resources

It is important to be aware of the approximate total size of new files that are sent to your ETL job’s
EGX300 File Directory in a given time interval, as well as the approximate amount of free space on
the hard drive containing the directory.

For example, if you have configured your ETL job to use a Time Between Job Runs setting of one
day or less, it’s useful to know the total size of one day’s worth of CSV files sent by all EGX300
devices in your system.

Page 36 CONTROLLED DISTRIBUTION 7EN42-0173-00

ETL Data Migration Guide Appendices

The total size of a day’s worth of data can vary depending on how many topics are logged for each
device, and how many devices are connected to each EGX.

The best way to determine the total size in a time interval is to browse to the EGX300 File Directory
and examine the total size using Windows Explorer. Using the example above, do so after at least a
day’s worth of data has been sent to this directory by the EGX300 devices.

Be sure that there is enough free space on the hard drive containing the EGX300 File Directory to
allow for reasonably expected downtime, should someone manually stop the ETL service.
Reasonably expected downtime should be determined by the application engineer deploying the
product based on knowledge of the particular site.

NOTE: It is not recommended behavior to stop the ETL service, but it is good practice to setup
your server to allow for that case.

Also note that all components of the EGX300 to Power Monitoring Expert solution require server
resources (CPU and memory)to operate. The degree to which the components use these resources
can vary depending on the configuration settings you choose, including but not limited to the
following settings: logging frequency, and export frequency on the EGX300 and Time Between Job
Runs and start time in your ETL job.

It is important for the application engineer deploying the system to be aware of other activity on the
server hosting the EGX300 to Power Monitoring Expert ETL software. The application engineer can
use this information to configure the software appropriately and in a way that fits the installation.

Appendix H: Importing data from Twido PLCs to existing logical

devices
ETL is capable of automatically detecting the logical device and output measurements associated
with Twido PLC weighted inputs. It can then import data from CSV files served up by the
associated EGX to those sources and measurements.

To allow for this automatic detection functionality, several prerequisites must be satisfied:

In the Power Monitoring Expert Management Console:

l The EGX that is logging data on behalf of the Twido PLC must be added to Management Con-
sole as a Site. It must be fully configured and given the correct IP address

l The EGX site’s status column should indicate ‘Connected’.

l The Twido PLC must be added to Management Console as a Serial Device on Ethernet Gate-
way site, and it must be fully configured and given the correct Unit ID. Its Site must be set to
the EGX site described above.

l The Twido PLC’s status should indicate ‘Site Available’.

l A logical device is created in Management Console that includes an input register from the
Twido PLC. Refer to Power Monitoring Expert documentation for instructions on how to create
logical devices.

l Each Twido input must be a part of no more than one logical device. The scenario of a Twido
input being part of more than one logical device is not supported in the current version of the
EGX300 ETL package.

In the EGX300 gateway configuration web site:

7EN42-0173-00 CONTROLLED DISTRIBUTION Page 37

Appendices ETL Data Migration Guide

l The Twido PLC must be added to the EGX300’s Device List

l The Twido’s “Weighted Input” topics must be enabled in the EGX300’s Device Logging page.
The recommended practice is to enable all Twido weighted inputs to allow for an easier work-
flow if the logical device configuration changes in the future.

l At least one CSV file containing data for the Twido must have arrived in the EGX300 File Dir-
ectory.

Once those prerequisites have been met, ETL will automatically discover the source and
measurement associated with the Twido inputs that appear in the incoming CSV files.

This automatic discovery happens during the "Source Mappings – Define EGX sources" on page 17
configuration steps.

In the EGX300 To EcoStruxure Power Monitoring Expert Configuration tool, each Twido with a
known logical device association will appear as a single row in the Source Mappings grid. This is
true even if the Twido’s weighted inputs are assigned to multiple different logical devices in
Management Console. The Preview Mappings grid displays a detailed view of each Twido
including:

l The Twido’s weighted inputs with a known logical device association.

l The EGX device and topic identifiers associated with each weighted input.

l The Power Monitoring Expert source and measurement associated with each weighted input.

Page 38 CONTROLLED DISTRIBUTION 7EN42-0173-00

EGX300, Com'X 510 and Com'X 200/210 EcoStruxure™ Power Monitoring Expert 9.0
ETL Data Migration Guide

ION, ION Enterprise, Modbus, PowerLogic, EcoStruxure and

Schneider Electric are either trademarks or registered
trademarks of Schneider Electric in France, the USA and other
countries. Other trademarks used are the property of their
respective owners.
Electrical equipment should be installed, operated, serviced and
maintained only by qualified personnel. No responsibility is
assumed by Schneider Electric for any consequences arising
Schneider Electric out of the use of this material.
35 rue Joseph Monier
92500 Rueil Malmaison - France 7EN42-0173-00
www.schneider-electric.com © 2018 Schneider Electric. All Rights Reserved.