MES 2014R3 P02 (v 5.3.0.2)

Материал из archestra.info
Перейти к: навигация, поиск

MES 2014 R3 Patch 02 Readme

Last revision: 9/21/2018

In This Document

About This Release

Installing the Patch

Known Issue

About This Release

This is a patch release to update the MES Web Portal content and the MES Intelligence Reports of MES 2014 R3. This is to be applied on top of an existing MES 2014 R3 or MES 2014 R3 Patch 01 installation.

There is no change to the operating system, database management system, or product compatibility support with this patch.

The MES 2014 R3 Patch 02 release contains MES 2014 R3 Patch 01 content plus the following updates to the MES Intelligence Reports:

  • Various fixes to the MES 2014 R3 Performance reporting model (see list below)
  • MES Intelligence model deployment performance improvements
  • New Genealogy By Lot report
  • New Genealogy by Work Order report

The MES 2014 R3 Patch 01 release (included in Patch 02) includes the following updates to the MES Web Portal:

  • The Last N Hours filter on the Production Event History grid now supports up to 168 hours (one week) vs 24 hours
  • The Last N Hours filter on the Utilization Event History grid now supports up to 168 hours (one week) vs 24 hours
  • The History grid now supports filtering (e.g., show events greater than 15 minutes)
  • The Last N Hours Reporting Period filter on the Entity Monitor page now supports up to 168 hours (one week) vs 24 hours
  • The Last N Hours Reporting Period filter on the Line Monitor page now supports up to 168 hours (one week) vs 24 hours
  • Hotfixes L00146374 and L00146730 addressing memory leaks are included

The MES 2014 R3 Patch 02 release includes the following major changes to the previous Performance model and reports (these are included in MES 2017):

  • OEE Analysis report calculations for Performance have been fixed.
  • The job batch size, production rate, and production unit of measure have been included in the model to calculate KPIs for OEE for which jobs are not using the default Web Portal values.
  • Issues with Shift times in the shift history dimension and reporting content have been addressed.
  • The Job and Shift History dimensions have been converted to time-defining dimensions so that aaObsolete records are not generated.
  • A job context dimension has been included in addition to the job dimension, to handle the context data for links instead of the job dimension, which changes frequently.
  • Offsets to dimension and measures have been added so that they do not collide with MES hourly tasks and so that dependent dimensions update after non-dependent dimensions.
  • No lock hints have been added to custom queries to avoid database locks.
  • The Production Day calculation and linkage to the system attribute setting has been corrected. Also, the description of this system attribute has been corrected in the MES 2017 versions of the MES Client User Guide and MES Intelligence Reports User Guide.
  • OEE Analysis report aggregation for averaging/summing hourly records up to the shift/day level has been corrected.
  • Duplicate records in reports caused by returning obsolete records from dimensions are now removed.
  • Equipment model and line equipment model separation has been implemented.

For complete information about the updated reports, see the MES 2017 version of the MES Intelligence Reports User Guide.

Note: The enhancements delivered in this patch for the MES Web Portal are not included in the MES 2017 release. Users should not upgrade their MES 2014 R3 Patch 02 system to MES 2017. Please wait for the MES 2017 R2 release, which will support upgrading this patch version.

Installing the Patch

This patch should only be installed on top of an existing MES 2014 R3 or MES 2014 R3 Patch 01 installation that has MES Intelligence Reports.

  1. Stop the MES Service application and the MES Middleware service that is running on the node on which the patch is being installed.
  2. Close the post-install Configurator application if it is open.
  3. Run the file MES2014R3_Patch02_<date>.exe, where <date> is the timestamp in the patch executable file name.

    The patch install tool opens and displays the license agreement.

  4. Accept the license agreement.

    The patch list appears.

  5. Select the patch entry and click Install.

    When the screen showing the patch name preceded by a green check mark appears, the install is complete.

    The patch installs database scripts.

  6. Click Finish to close the install tool.

    The post-install Configurator application opens.

    Note that even though the MES components mentioned in the following steps are shown as already being configured, you must reconfigure them to complete the patch implementation.

  7. Select the MES Database Setup component.
  8. Click Validate.
  9. Make sure the Overwrite and Migrate data options are selected.
  10. Click Configure.
  11. Restart the MES Middleware Host and MES Service either manually or by selecting the DB/MW Communication component and clicking Configure.
  12. If you are using MES Web Portal and Patch 01 has not been previously installed, select the MES Web Portal component and click Configure.

    If MES Web Portal is not installed, the patch will attempt to install it. The install might fail if the MES Web Portal was not previously installed and the prerequisites have not been met.

    If MES Web Portal was previously installed, configuring the MES Web Portal again deploys the updated Web Portal content. As part of the configuration process, existing Web Portal content files are copied to a folder named Web Portal\MES (archive <timestamp>) in the MES application folder, where <timestamp> is the date and time when the MES Web Portal configuration was completed. This saves any customizations that might have been made to Web Portal files. Those customizations will have to be reapplied to the active Web Portal content.

  13. Stop the Intelligence service.
  14. Back up the Intelligence database, as the new model will overwrite the existing database.
  15. Delete both the Intelligence and _Staging_Intelligence databases.
  16. Follow the Intelligence 2014 R3 Hotfix L00148071 instructions (in CD-WonderwareMES\Intelligence Reports\HFL00148071) to apply the that hotfix.
  17. In the post-Install Configurator, configure the Intelligence Server and Data Adapter components.
  18. Manually copy MESIntelligenceModel.xml from CD-WonderwareMES\Intelligence Report to the Intelligence Reports folder within the MES application folder.
  19. Manually copy the Intelligence reports from CD-WonderwareMES\Intelligence Reports\Reports to the Intelligence Reports\Reports folder within the MES application folder.
  20. Manually copy IntelligenceMESViews.sql from CD-WonderwareMES\Intelligence Reports\Scripts to the Intelligence Reports\Scripts folder within the MES application folder.
  21. Run the Intelligence Model Deployment utility to deploy the MES Intelligence model.
  22. In the post-Install Configurator, configure the MES Intelligence Reports component to deploy the SSRS MES Reports to the report server.
  23. If you have applied any MES 2104 R3 hotfixes that modify stored procedures, you must apply them again after installing this patch.

Installing the Patch from a Command Line (Silent Install)

The patch can be installed from a command line.

To view help information for the patch executable file (optional)

  • Run MES2014R3_patch02_<date>.exe with the help parameter /?.

    For example:

    MES2014R3_patch02_<date>.exe /?

    All command options will be displayed.

To generate the response file (required)

  • Run MES2014R3_patch02_<date>.exe with the switches /List and /Filename:"<file path and name>".

    For example:

    MES2014R3_patch02_<date>.exe /List /Filename:“C:\Patch\responseFile.text"

    The response file will be created.

To install the patch

  • Run MES2014R3_patch02_<date>.exe with the switch /Silent and specifying the response file.

    For example:

    MES2014R3_patch02_<date>.exe /Silent “C:\Patch\responseFile.text"

    The patch will be installed.

Known Issue

DateTime values for utilization events will be incorrect in the MES Intelligence Reports when an entity is configured within a site and the site time zone is different from the MES Web Portal time zone used to enter the utilization events.

Copyright © 2018 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us

The Schneider Electric industrial software business and AVEVA have merged to trade as AVEVA Group plc, a UK listed company. The Schneider Electric and Life is On trademarks are owned by Schneider Electric and are being licensed to AVEVA by Schneider Electric.