Migration Instructions PM 6.0
Migration Instructions PM 6.0
Contents
1 Online Support ................................................................................................................................ 4
2 Overview ......................................................................................................................................... 5
6 Troubleshooting ............................................................................................................................ 35
Click the following link for the list of all FAQs, Hot fixes, and Service Packs:
www.siemens.com/Powermanager/support
In order to protect plants, systems, machines, and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines, and networks. Such systems, machines and components should only be connected
to an enterprise network or the internet if and to the extent such a connection is necessary
and only when appropriate security measures (e.g., firewalls and/or network segmentation)
are in place.
For additional information on industrial security measures that may be implemented, please
visit https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends that product updates are applied as soon as they are
available and that the latest product versions are used. Use of product versions that are no
longer supported, and failure to apply the latest updates may increase customer’s exposure to
cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under https://www.siemens.com/cert.
- Export from powermanager V3.6 HF1: Allows you to select the configurations and the
data to be migrated from powermanager V3.6 HF1 to new powermanager.
NOTE: You should have powermanager V3.6 HF1 to perform the export. Upgrade to
powermanager V3.6 HF1, if you are using an older version of powermanager.
- Import to new powermanager: Allows you to import the exported files from
powermanager V3.6 HF1 to new powermanager.
NOTE: You should have new powermanager to perform the import. Upgrade to new
powermanager if you are using an older version of powermanager.
Migration Rundown:
To save time, we recommend you perform the procedures involved in migration workflow in the
following sequence:
1. Configuration Export
2. Configuration Import
3. Data Export
4. Data Import
new powermanager and powermanager V3.6 HF1 must be available in two different machines to
perform the procedures in the recommended sequence. Refer section Hardware Category
Definitions in System_Description_pm_6.0 document for hardware requirements. Ensure that the
machines involved in the migration process are in the same time zone.
NOTE: To transfer the exported folders from one machine to another, you are recommended to
have USB stick or USB Hard disk.
Below are few important details to be noted before continuing with the migration operation:
• Only server projects can be migrated. If you have an existing client setup, you must setup
the client afresh in new powermanager.
SEM3 ✓ -
SICAM Devices ✓ P850 and P855 will be migrated as PAC5100 and PAC5200
respectively.
Manual -
Measuring Device
Third-party ✓ -
Devices
(XML imported
Third-party Device
types)
• The descriptions of Areas and Sectors are not migrated from powermanager V3.6 HF1 to
new powermanager.
• System and Area level configurations of PAC5100 and PAC5200 device types are
considered for P850 and P855 device type respectively in new powermanager.
• OPC UA/DA and MindSphere configurations are not migrated to new powermanager.
• Manually corrected values are migrated.
• Alarm configuration of 3VLCOM21, PAC1500, GMD and third-party device types (xml
imported device types) will not be migrated. If necessary, reconfigure the alarms after
migration.
Pre-export Checklist:
• Ensure you have sufficient disk space available for the export operation.
• Archive backups of powermanager V3.6 HF1 should be re-mounted if needed for data
export.
• Ensure you take project and data backup before migration.
• Download and unzip the file containing the Migration Tool from the SIOS portal.
• Stop the project and close all powermanager applications and consoles to proceed with
migration.
NOTE: The Powermanager Migration Export tool is available in English and German languages.
The language will be selected by the tool depending on the available operating system. The
language is set to English for all operating systems other than German.
• Enter the Username and Password used to login to powermanager V3.6 HF1 project to
login to the migration tool.
NOTE: You must be a powermanager V3.6 HF1 Admin user to login to the Powermanager
Migration Export tool.
NOTE: We recommend you stop all device communication before proceeding with the export
operation.
Devices Tab
Languages: Allows you to select the description language. This section has the following options:
Language 1: Displays the default language assigned for all descriptions. This field cannot be
changed.
Language 2*: Allows you to select the description languages from the available list of supported
languages. This is a mandatory field.
• By default, all supported devices from the Devices section will be selected.
Devices: Allows you to select the device configurations to be migrated. This section has the
following columns:
Select: Select the checkbox under this section to select the device. All the devices supported for
migration is selected by default. Migration non-supported devices are highlighted in grey and
cannot be selected for migration. Such devices are not migrated even as Third-party devices.
Device Name: Displays the name of the selected device.
Device Type: Displays the device type.
Device Group: Displays the device group.
Area: Displays the area under which the device is available.
Sector: Displays the sector hierarchy under which the device is available.
NOTE: Device passwords are not included in the migration operation. Update the device passwords in
new powermanager after the completion of migration.
• Select Third Party Device XMLs: Allows you to select the required third-party device type XML to be
migrated. This section has the following columns:
Third-Party Device Type: Displays the third-party device type
Number of Devices for the device type: Displays the number of devices of the device type.
Select XML file used for creating the third-party device type: Allows you select the third-party
device type XML files.
Path of XML: Displays the location of the third-party device type XML files.
• Click Save.
NOTE: You must select the XML files for all the third-party devices selected in the Devices section.
• By default, all the Report Templates will be selected. De-select any report templates if
required.
Report Templates: Allows you to select the report templates. This section has the following
columns.
Select: Select the checkbox under this section to select the required report template. All the
report templates are selected by default.
Report Template: Displays the report template name.
Report Type: Displays the report type.
NOTE: 1) Only report templates are migrated and not the generated reports.
2) Migration is not supported for Sankey Report.
3) Only scheduling configuration of the Top 10 report templates is migrated.
4) The Power peak analysis is migrated as a report template.
• Click Save.
Miscellaneous Tab
• Click Save.
Export Tab
• Select the path for the export and complete the configurations export under the Export
Configuration section.
Path: Allows you to select the path to where the files need to be exported to.
Export Configuration: Allows you to complete the complete configurations export.
The file containing the configurations export is available in the above specified folder.
Devices: Allows you to select the devices for which the data must be exported. All the devices
selected in the configuration export are listed here.
Default: Select to export the measurement points that are archived by default when a device is
created in new powermanager.
Example: The measurement points archived by default for a PAC3200 device are active energy
import tariff 1 and cumulated active power import.
Custom: Select to choose measurement points from all the archived measurement points for the
selected device in powermanager V3.6 HF1.
NOTE: Logical devices are not listed for data migration. All the result values are selected for export.
• Select the devices for which the measurement points need to be exported under the Third
Party Devices section.
• Click Save.
Duration Tab
NOTE: The default time duration for the data export is from the selected start time to the time
configuration export is completed.
Duration for Energy Consumption & Power Interval Values: Allows you select the duration for
which the data must be exported for energy consumption and power interval values. This section
has the following options.
Select*: Select the duration for which the data must be exported from this dropdown.
Start time: Displays the start date and time for the selected duration, if the default duration is
selected in the Select* dropdown.
Allows you to select the start time and date, if the custom option is selected in the Select*
dropdown.
Duration for all Other Values: Allows you to select the duration for which the data must be
exported for all other values except energy consumption and power interval values. Default
duration is set to 3 months.
NOTE: Other values data (excluding energy consumption and power interval) can be exported only
for last three months.
Time Based Smoothing: It allows you to reduce the volume of data to be exported.
Smoothing Interval: Select the smoothing interval for time based smoothing. This helps to reduce
the amount of data considered for migration and to reduce the SQL size needed. After the
smoothing interval time has elapsed, the next value will be considered for migration. Any values
during the smoothing interval are discarded.
• Click Save.
Export Tab
• Click Calculate Quick Forecast or Calculate Detailed Forecast to view the SQL storage
analysis needed for new powermanager database.
SQL Storage Forecast Quick Analysis: Provides you a detailed estimate of the required SQL storage
space.
SQL Storge Forecast Detailed Analysis: Provides you a detailed estimate of the required SQL storage
space. This process can take a few minutes to an hour depending on your data.
• Click Data Export in the Data Export section to proceed with the export operation.
Export Data: Displays the path where the data export files are made available.
The file containing the data export is available in the above specified folder.
• Copy the files containing the configuration and data export to the machine with new
powermanager.
Pre-import Checklist:
• During installation of new powermanager, select checkbox Migration (select if you are
migrating from powermanager V3.6 HF1) and click Next.
NOTE: If the checkbox is not selected, Powermanager Migration feature will not be
available after installation.
To add Powermanager Migration feature post installation follow the below steps:
- Launch Powermanager SMC and Navigate to Projects node.
- Click Stop.
- Click Next.
- Click OK.
- Click Next.
- Click Close.
- Click Save.
- Start the project.
• Ensure that you have the required new powermanager license available and activated.
Licensing for powermanager is controlled through a tool called, License Management Utility (LMU).
Once powermanager is installed, the License Management Utility (LMU) is installed on every
system.
Before launching the powermanager client application, you must first enable and manage licenses
for powermanager. Otherwise, only the demo licenses are configured, and you will need to close
the powermanager client application in very short time.
The History Database is created and displays in the SMC tree. This may take a few minutes
depending on the selected database size. When you create a new HDB it gets automatically linked
to the SQL Server. The long term storage is created when the state in the State column in the
Storage table changes to ON.
For additional information, refer to Powermanager Help >Engineering Step-by-Step > Setting Up the
Project > Creating History Infrastructure > Create a New HDB with Long Term Storage.
• Copy the files containing the configuration and data export to the machine with new
powermanager.
• Create the third-party device types, if any.
You must create the third-party device type to be migrated in new powermanager. JSON files for
corresponding third-party device types are created by the migration tool during the configuration
export. These JSON files are available in configuration export folder. You can create third-party
device types using the below steps:
- Select Applications > Powermanager.
The System tab displays.
- Select Third Party Device Type expander and proceed as follows:
▪ In the Open dialog box, select the required JSON file from the location and click Open.
NOTE: Device types like 3VLCOM21 and PAC1500 are supported in powermanager V3.6 HF1 but not
supported in new powermanager. JSON files for these device types are created as a part of the export
operation.
These files are available in path: [Projectname]_Backup_For_Migration(yyyy-mm-dd-
hh.mm)\Configuration\Device\Classic_DeviceType_Jsons.
• Edit the JSON files for the Generic Modbus Device (GMD) types, if any.
A JSON file is created for GMD type by the migration tool during the configuration export. This
JSON file is available in configuration export folder.
Open the JSON file of the GMD type using the powermanager device engineer tool. Perform the
required property configurations and create the new JSON files for corresponding GMD groups.
Consider the below example to create GMD device type JSON files in powermanager device
engineer tool:
- Open JSON file GenericModbusDevice_Classic from configuration export folder in third-party
tool PowermanagerDeviceEngineer.
• Create the devices in new powermanager under Bulk Devices Creation tab:
- In Engineering mode, click Bulk Device Creation.
- Browse .csv file to create devices.
NOTE: A .csv file with the device configurations is created during the export operation. Use this
.csv to create the devices.
These files are available in path: [Projectname]_Backup_For_Migration(yyyy-mm-dd-
hh.mm)\Configuration\Device\BulkDeviceCreation.
30 of 35 Powermanager, Migration Tool
L1V30600299C | Edition 12.2022
- Select the required Device Type from the available dropdown for GMDs.
- Provide the Username and Password for all SEM3 devices.
- Import the JSON files to new powermanager to work with these devices. Refer steps from
section 4.1 Prerequisites for Import > Create the third-party device types to import JSON files
to new powermanager.
- Click Create Devices.
• Switch to Engineering mode and navigate to Migration tab to proceed with the import
operation.
• Select the folder with the migrated files under the Import expander.
Select the folder exported from powermanager V3.6 HF1: Allows you to select the folder with the
configuration or the data export.
Step 1 – Configuration Import: Allows you to import the file containing the configurations.
Username: Enter software account username for new powermanager.
Select path: Select the folder to export the schedule reports.
Step 2 – Data Import: Allows you to import the file containing the data.
Data import could not start User clicks on data 1.Verify if HDB is linked to the
import with incorrect project.
HDB configuration
2.Verify if Siemens GMS HDB service
is running in SMC (system node
>management tab >services
section).
3.Verify if short term and long term
archives/storages are created in
HDB and in ON state.
After performing above
troubleshooting, proceed with data
import.
Migration tab is not available after login Migration EM is not If Migration EM is not installed,
to new powermanager installed or not added in refer section Import to new
the project powermanager.
If migration EM is not added in the
project, click Add to project and add
powermanager migration EM.
Server is not properly running during Migration(import) User should wait till completion of
import in new powermanager running on HDB writer complete migration activity.
manager goes to blocked
state in SMC
The scheduled report file is corrupted User trying to open the In powermanager application re-
generated scheduled save the report definition.
report file