Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue If a SmartX Server is using External Log Storage how often are new trend log data and events sent to the TimescaleDB? Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When a SmartX server is using External Log Storage many of the trend logs and all new event records are sent to a TimescaleDB for storage. Resolution New event records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them. Some records as "Edit" and "Comment" are sent immediately. New trend log records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them.

Issue WorkPlace Tech 5.8.x, 5.9.x, and 5.10x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, and 5.10x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, and 5.10.x? Resolution Microsoft Windows WorkPlace Tech Tool release 5.8 through 5.8.6 is certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool release 5.9.1 to 5.9.4 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool release 5.8 through 5.8.6 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio Office 365 Subscription Plans Note: Workplace Tech Tool 5.10.0 and future releases will require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow instructions in the article link for security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. Following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016,(.msi install) Visio 2019 is not supported in 5.9.4 or EBO versions.  Visio 2019 is supported when using Workplace Tech 5.10 only. Visio 2013, 2016, 2019 (subscription "Click to Run", Plan 1 or 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run" , Plan 1 or 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Security Bulletin MS-16-70 Visio 2010 32 bit KB3114872       Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020       Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan1 or 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1 , 2002 SP1 5.0 2002 SP1 , 2003 SP1 5.1 2002 SP1 , 2003 SP1 5.2 2002 SP2 , 2003 SP1 or SP2 5.3 2002 SP2 , 2003 SP1 or SP2 5.4 2002 SP2 , 2003 SP1 or SP2 5.5 2002 SP2 , 2003 SP1 or SP2 5.6 2002 SP 2 , 2003 SP1 or  SP2 5.7 2003 SP3 , 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3 , 2007 SP1 or SP2 , 2010 SP1 5.8.6 2007 SP1 or SP2 , 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 2016, 2019, Office (Visio) 365 Subscription Plans ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue Sigma parallel port dongle or USB dongle upgrade to software license Product Line Satchwell Sigma Environment Sigma version 4.08 Cause It is becoming increasingly harder to purchase computers with parallel ports. With the increase use of virtual computer operating systems USB ports may not be available either. ∴ A different type of Sigma licensing will be required. Resolution Product Support Services (PSS) can arrange for an upgrade from your existing parallel port or USB type Sigma dongle to an SBO/EBO software license entitlement for Sigma 4.0.8. Sites running Sigma 4.07 or older do not support software licensing and would need to be upgraded to Sigma version 4.08.57 or later to include the software option. Sigma Software license type availability is documented on page 8 in the Sigma 4.08 release note. For engineers using Sigma 4.08: The StruxureWare Building Operation Evaluation License, available from the Schneider Electric Download Center, will unlock the Sigma 4.08 for testing etc for the period of the Evaluation License (maximum 3 months or until the expiry of the downloaded license).   For customer sites using Sigma 4.08: To reduce the Sigma system downtime, currently PSS operate on a trust basis and provide the software license in advance. PSS require you to send the old Sigma dongle back to the PSS representative that is assisting you with your license upgrade. This should be completed within 30 days of receiving your software license. Once you receive the software license entitlement for Sigma. Install the SBO License Server version 1.6 or later. (it is recommended that the latest available version of the SBO License Server compatible with the computer's operating system is used). Procedure: Download the Sigma Dongle Replacement - Required Data 2020 form. Complete the cells that are highlighted/filled in blue. Open a case with PSS. Supply the completed spreadsheet. PSS will escalate a Sigma transitions site for the software license. If the site is a stand-a-lone Sigma site, PSS will need to get approval from the regional category manager before escalating for the software license. Note: If your current Sigma dongle contains Remote Alarm Manager licensing, Remote Alarm Manager does not support the EBO license server option. The USB dongle can still be used or a TAC license server type license can be used instead of the dongle. To install the software licensing option for Sigma 4.08: - Stop the Sigma server service. Install SBO/EBO License Administrator. Add your entitlement to the SBO/EBO License Server. Start the Sigma server service. Sigma should now be licensed.

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue The MVB actuator is no longer available from Schneider Electric Replacing a Controlli S300 Actuator Product Line Field Devices Environment VMB valves MVB actuators S300 actuator Cause Only the actuator requires replacing but the MVB is no longer available from Schneider Electric. Resolution Note: The MVB actuators are still manufactured by Controlli, but not distributed by Schneider Electric. Use the AG52 valve linkage kit 880-0129-000. For the Controlli MVB22, MVB26 and MVB28 or S300 replace with the MV15B-230 actuator For the Controlli MVB46 replace with the MV15B-24 actuator For the Controlli MVB32, MVB52 and MVB56 replace with the M800 880-0310-030 actuator If a D36 auxiliary switch was fitted in the  the MVB actuator or if the auxiliary switch was used in the S300 actuator then the following auxiliary switch packs can be used: M800, use the 880-0104-000 kit or order the M800-S2 880-0311-030 actuator which includes 2 auxiliary switches. MV15B-24/230, use the 880-0469-000 kit. Note: if the valve also requires replacing see VSB, VSB..F, VMB, VMB..F Schneider Electric replacement valves.

Issue Sigma controllers that have been cold started do not recover correctly. Product Line EcoStruxure Building Operation, Sigma Environment Sigma Server Building Operation Enterprise Server Cause Having imported a Sigma database into the Sigma Interface on the Enterprise Server, and following a controller cold start, Sigma controllers fail to fully recover. The controller correctly receives the Backup server number, but fails to request the data from the Sigma Server. Resolution This issue is resolved as follows; Data Import the Sigma Data. Stop and restart the Enterprise Server using the Software Administrator Cold start a controller to confirm that it fully recovers. Note: A  restart of the Enterprise Server will be required again if any new additional controllers are to be added to the Enterprise Server. This workaround only works for ARM7 controllers, for V53 devices, the Sigma 4.08 (3.46.79) Hot Fix is available on the Download Centre and needs to be installed at the Sigma Server machine. Note; this hotfix is a separate item to any other Sigma hotfix and the correct Sigma Transition Tool version needs to be installed.

Issue When trying to launch the Energy Expert Integration Utility (formerly the Power Manger Integration Utility) the following error is given. Product Line EcoStruxure Building Operation Environment Energy Expert Power Manager for SmartStruxure Integration Utility Cause This error message can be the result of different causes. Check the IntegrationUtility.log file found in the same location as the Integration Utility for more information.  Example of Integration Utility Log error: ERROR: Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "IntegrationUtility.Shell", name = "(none)". Exception occurred while: Calling constructor IntegrationUtility.Pme.Services.PmeUserDataStore(). Exception is: ConfigurationProviderException - Could not locate a connection string provider. Resolution NOTE: If you have already downloaded the software, you must first delete the folder you unzipped before doing the process below.  Unblock the Zip file The first thing that MUST be done after downloading the Power Manager software from the Exchange is to unblock the zip file. Right click on the zip file and select Properties. Under the General tab, towards the bottom click Unblock. Click Apply and close the properties window.  You can now unzip the software and use it as normal.  Compatible .Net Framework Versions Different versions of the Power Manager / Energy Expert Integration Utility require certain versions of Microsoft .Net Framework. Note: Having multiple versions of .Net Framework installed may cause issues.    Pease refer to the Energy Expert Compatibility Matrix for further detail.

Issue When mapping the EcoStruxure Building Operation (EBO) Trend Logs to EcoStruxure Energy Expert, not all trend logs are visible in the ETL Tool 'Load Sources'. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Energy Expert Cause The EBO user credentials entered into ETL for connect to the EBO Database must have access to BOTH the trend log itself, and the point which the trend log is logging. Resolution Edit the EBO user which the ETL is using to connect to EBO and give a minimum of Read Only access to both the Trend Log in question and the Point being logged  and then in the ETL re-run 'Load Sources'.  The additional points which were missing before should now be available for mapping

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as 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 EcoStruxure Energy Expert 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 EE. 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 StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert 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 EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) 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. EE 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 EcoStruxure Energy Expert (EE) 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 EE 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 your web server address and port as needed) 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 EE 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 Manager 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. 

Issue When attempting to access the dashboard URL via the web browser or in SBO Workstation, the following message is displayed. Product Line EcoStruxure Building Operation, EcoStruxure Energy Expert Environment Power Manager 1.2 and newer Power Manager Expert 8.1 and newer Building Operation Workstation Cause A Power Manager 1.2 or newer system running a permanent license allows the user to a log into the Management Console, manual authentication URL, and through the EWS interface in SmartStruxure Workstation. After upgrading to the latest version of Power Manager this access no longer works. The Ports match in License Manager and FlexNet and this site has previously worked. The cause to this issue is that the URL being used has changed starting in PME 8.1. Resolution This issue is due to a change made in the dashboards URL starting in Power Manager 1.2 / Power Manager Expert 8.1. The URL needs to be changed by replacing "Web" with "Dashboards" in the URL found in the EWS link settings or when logging in directly with a web browser.    Example: http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fWeb%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324... http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fDashboards%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324...   Also in the newer versions of Power Manager, there is a limit regarding what can be accessed in PME when using a Power Manager license. In Power Manager 1.2 and on you can access: /Reporter /Dashboards /Trends /HierarchyManager /RateEditor and use the integration toolkit to get into SBO if necessary. Power Manager is now known as EcoStruxure Energy Expert.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue Duplicated SFE Short Form Edit graphics Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Sigma Cause A duplicated set of Short Form Edit graphics are created but are in a different language appear along side the original SFE graphics when using Data Import with a Sigma transition into EBO The example below shows the original DataImport was completed in English, the second DataImport was completed in Danish. Resolution Before a Sigma DataImport is undertaken, ensure that the correct language is set in EBO. Delete the Sigma Interface, set the correct language and start the transition again. Note: By deleting the Sigma Interface, this will delete all the SFE graphic links on the objects and a clean set of SFE graphics will be created on all the objects.

Issue Is it possible to include the Comments field from Extended Logs into Report Server Reports? Product Line EcoStruxure Building Operation Environment Building Operation Reports Server Cause Regardless of the new Reporting Features in EcoStruxure Building operation (EBO) 3.2, users of existing systems up to and including EBO 3.1 are asking if it is possible to include the Comments field in Extended Logs within the Enterprise Sever to enhance the data in RS Reports? Resolution Extended Log Comments within the ES are not available to Report Server reports today and given the move to new Reporting Features now available in EBO 3.2 it is unlikely that an Enhancement Request for such a feature would be implemented quickly. Therefore, the suggestion here would be to migrate the Extended Logs to External Storage via TimeScaleDB where all the Extended Log data (including the comments) can be freely manipulated by 3rd party Reporting Products.

Issue Following a successful configuration of the Continuum Transition Tool (CTT) it has been noted that some ongoing changes in Continuum do not seem to then be migrated through to the Security Expert database. Product Line Andover Continuum Security Expert Environment Continuum Transition Tool Security Expert Data Sync Cause It would appear that on occasion, some changes made to Continuum Areas after the initial CTT Transition is completed, fail to be exported from the Continuum DB by the CTT in its periodic update, This can be verified by examining the actual CSV output and seeing that certain known changes to Areas  are simply not present.  The actual Security Expert Data Sync is working correctly but if the changes are not exported by the CTT then they cannot then be imported by the Data Sync Service Resolution Although this is not currently resolved, it is documented as a limitation of the Andover Continuum System. Page 21 of the Transition Guide Security Expert - Continuum Database - Transition Quick Start Guide states that the Last Changed field of an Area object is only updated if the object is edited in a specific way. Since the CTT uses the Last Change field to decide what new object changes need to be exported, this legacy issue in Continuum directly affects the update to Security Expert if the changes are not made as advised above.

Issue There can be confusion on the differences between EcoStruxure Energy Expert (formerly Power Manager) and EcoStruxure Power Monitoring Expert (PME)  Product Line EcoStruxure Building Operation, Other Environment EcoStruxure EcoStruxure Energy Expert (formerly Power Manager) EcoStruxure Power Monitoring Expert (PME) Cause Power Monitoring Expert (PME) is a long-established product in the Schneider Power (EMS) offer and so its place in the market is well known and its support path is very clear. Energy Expert is a much newer offering that intentionally sits nearer to EcoStruxure Building Operation (EBO) in the BMS community, while still remaining an EMS product and so its place in the market and support path is more easily confused. Resolution Definitions   EcoStruxurePower Monitoring Expert (PME) Schneider Electric's supervisory software dedicated to power monitoring that enables you to maximize operational efficiency, optimize your power distribution system, and improve bottom-line performance   EcoStruxure Building Operation (EBO)  Schneider Electric's premier building management system (BMS) providing integrated monitoring, control, and management of energy, lighting, HVAC, and fire safety.   Energy Expert for EcoStruxure                                                             Designed to offer Power Monitoring Expert (PME) features to new and existing EcoStruxure Building Operation (EBO) projects, giving extra capabilities to manage power utilization in a BMS environment.   It utilizes EcoStruxure Web Services (EWS) to be able it to share data between the two EcoStruxure software platforms. (EBO and EE) and applications such as the ETL Tool and the Integration Utility in the integration process.   EcoStruxure Web Services (EWS) The Schneider Electric standard for sharing data among various Schneider software platforms to facilitate the creation of EcoStruxure Solutions. Based on conventional Web Services technology (SOAP, WSDL)   ETL Tool The function of the ETL is to extract select historical data (Trend logs) from EBO, and load that data into the Energy Expert SQL database for use in Dashboard and Reports etc.   Integration Utility The function of the Integration Utility is to export Energy Expert Dashboards, Reports and Alarms for import into EBO to enhance its Power Offer to the customer   Product Support Path: PME, Energy Expert, ETL and the Integration Utility are are all fundamentally Power Products and so should always be raised through your local Product Support Team (via your Customer Care Center (CCC)) under an EMS commercial reference. However in cases where an Energy Expert project needs specific assistance with the EBO side of the integration then a BMS commercial reference should be used instead.