MES 2017 (v 6.0)

About This Readme

This document contains important information about Manufacturing Execution System (MES) 2017 (version 6.0). This Readme documents the system requirements, known issues, resolved issues, and changes, if any, to the MES user documentation.

Readme files from previous releases of MES are posted to the Product Hub page of the Knowledge and Support Center. Once on the Product Hub page, you can use the filter to list the MES documents, which include the Readme files. To access the Knowledge and Support Center, start at the Contact Page and click through the Customer Support links.

About This Release

MES 2017 includes the following new features and enhancements.

MES Performance Database Redesign

Three key tables for capturing MES Performance data have been redesigned:

Util_Log is replaced with Util_History
Job_Util_Log_Link is replaced with Job_History
Tpm_Stat is replaced with Job_Hour_History

When upgrading from an MES version 5.3 or earlier database to the 6.0 version, a migration process is performed. It includes:

Moving all the existing data in these three tables to the new table structure. The existing tables will be renamed to Util_Log_Deprecated, Job_Util_Log_Link_Deprecated, and Tpm_Stat_Deprecated. These tables can be deleted once the database has been successfully migrated and the end user is satisfied the data is accurate.
Creating views with the same name as the previous tables (Util_Log, Job_Util_Log_Link, and Tpm_Stat). These views return the same data as the prior tables to ensure reports and custom queries continue to function.
Merging some records together in the new schema and rebuilding the new Job_Hour_History table in case of any inconsistencies. Once the migration is complete, it is very likely that there will be a different number of records in the new tables versus the prior tables.
Migrating any existing Archive/Purge/Restore jobs that used the previous tables to use the new tables.

With the new design, utilization events are not split by the system at shift and day boundaries. This also permits splitting of events that span multiple shifts and days.

Also, the Job_Hour_History table will only have records up to 3 hours in the past.

MES Reporting

MES Operations and MES Quality reports against the MES reporting database—powered by Intelligence—are included in this release. The Information Server-based reports are still included in this release but will be removed in the next release.

The MES Performance reports have also been modified in this release.

The underlying Intelligence reporting model has been updated for all reports and is only compatible with Intelligence 2014 R3. Please check the Knowledge and Support Center site for an updated reporting model for Intelligence 2017 and updated MES reports that will be posted after the MES 2017 release.

The following major changes have been made to the previous Performance model and reports:

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 in the MES Client Guide and MES Intelligence Reports Guide has been corrected.
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 more details, see the updated MES Intelligence Reports Guide.

MES Quality SPC Chart Enhancement

The underlying SPC Chart control is updated to a new version. The MES media also includes a JavaScript version of the SPC Chart control for use in building web applications.

The updated control includes new user interface elements for toggling on/off the various sections of the chart and a new zoom window in place of the scroll bar. The chart control now supports indication of Ignored samples, control limit zone coloring, and different symbols for alarm points. Additional changes have been added for how the system handles missing results and asymmetric control limits.

MES Attributes, Specification Description, and Unit of Measure Conversion Spares

MES Attributes have been added for shifts and sublots in this release. Attributes of type list now support custom ordering of the elements in the list. The API for querying attribute values now includes an overload for querying by attribute description in addition to the attribute ID.
Specifications now have an optional description added to them. The specification descriptions are available to see throughout MES Client.
Unit of measure conversions now include the four standard spare fields.

MES API Modifications

In support of the upcoming MES model-driven application content, the MES Web API has been modified and documented. As the previous versions of the MES Web API were not documented, there might be some breaking changes in this version of the MES Web API as some Web API parameter naming has changed. Please refer to the new MES Web API Reference Manual for more details.

The MES Stateless API also had numerous changes to add support for some new MES Web API calls and support for the other new features in this release. The following additions have been made:

Util.UtilHistory and Prod.JobHistory Classes for Utilization Changes

These should be used for new installations and new features. All existing APIs continue to function, but might not perform optimally.

Prod.ItemProd.Update and UpdateSpecific Methods

New overloads were added that include a createdAtUtc parameter for easier modification of historical production records.

Prod.JobExec.AddProdPostExec Method

A new overload was added that includes a createdAtUtc parameter for easier insertion of historical production records.

Util.UtilExec.GetAll and GetByKey Methods

New overloads were added that include a parameter to recalculate the current utilization value.

Prod.OEEExec.GetAll and GetByKey Methods

New overloads were added that include a parameter to recalculate current performance, quality, and OEE values.

Prod.JobExec.StartJob, StartJobAsync, EndJob, EndJobAsync, PauseJob, and PauseJobAsync Methods

New overloads were added that include parameters to specify event time in UTC.

Core.Ent.PrepareProductionAttributesByEntName Method

New overloads were added that include parameters to specify event time in UTC.

EnProd.Spec, JobSpec, StdOperEntSpec, OperEntSpec, OperItemSpec, and BOMItemOperSpec Classes

New overloads were added that include parameters to specify specification descriptions.

Core.AttrSet Class

New overloads were added that include parameters for setting and retrieving the display sequence of list attributes.

Prod.UOMConv Class

New overloads were added that include parameters for setting and retrieving spare fields.

Core.EntAttr, Core.LineAttr, Core.ShiftAttr, Prod.ItemAttr, Prod.ItemClassAttr, Prod.JobAttr, Prod.LotAttr, Prod.OperAttr, Prod.ProcessAttr, Prod.StdOperAttr, Prod.SublotAttr, Prod.WOAttr, Quality.ResultAttr, and Quality.SampleAttr Classes

New overloads were added that include parameters for retrieving attribute values by name.

Core.ShiftAttr Class

This new class was added to support shift attributes.

Core.Ent.Update Method

This method now allows for NULL parent entity and site parameters.

Prod.Job.GetJobQueueByFilter Method

A new overload was added to return parent entities.

Prod.WO.GetByFilter Method

A new overload was added that has a parameter for retrieving work orders from a process.

Prod.ItemProcessLink.GetAll and GetByKey Methods

Additional columns were added to the returned dataset.

EnProd.JobBOM.GetJobBOMData Method

Additional columns were added to the returned dataset, and the method now accepts NULL for the sequence number parameter.

MES Uses Activated Licensing

With this release, MES now uses the activation-based licensing.

The number of feature lines has been reduced and will be reflected in the License Manager application.
The MES middleware continues to manage the licensing of features.
License counts are additive in this release, so it is possible to use a 20-entity count and a 5-entity count functional license to enable 25 entities.
The number of MES middlewares is also enforced in this release.

Updated Documentation

Significant content updates to the MES user documentation are summarized below.

MES Installation Guide and Help

Updated content to cover changes to the License Manager and to the installation and configuration of the MES Intelligence Reports.

MES Client User Guide and Help

Updated database maintenance content to reflect the MES Performance database redesign.
Updated and added content relative to the addition of MES attributes, specification descriptions, and Unit of Measure Conversion spare fields.

MES Stateless API Reference Help

Updated content to cover API changes described above in "MES API Modifications."

MES .NET Controls Developer Guide

Updated content to cover the SPC Chart control enhancements described above in "MES Quality SPC Chart Enhancement."

MES Intelligence Reports User Guide

Updated content to cover the MES Intelligence model and the new reports described above in "MES Reporting."

MES Web API Reference

New document to describe the MES Web API calls.

MES Configurator User Guide

Removed content related to configuring departments and categories for users and user groups (these tasks are now performed in MES Client).

MES Data Editor User Guide

Revised content for the Utilization tab.

MES Middleware Extensibility Hooks Reference

Added a table that summarizes the stored procedure changes related to the MES Performance database redesign.

Related Topics

System Requirements

This section describes the hardware, software, and operating system requirements to install the MES 2017 software.

For the most current compatibility information, see the Technology Matrix, which is available in the Knowledge and Support Center. To access the Knowledge and Support Center, start at the Contact Page and click through the Customer Support links.

Hardware Requirements

The following are the recommended hardware requirements for nodes on which MES 2017 components will be installed.

The hardware requirements that are described in the following topics are based on the minimal requirements for running MES components. Additional minimum hardware might be required based on the version of Windows being used on a node (see Minimum Hardware Requirements for Supported Windows Versions).

Middleware or Database Server

Computer with dual core processor with 2 GHz or faster clock speed, or single core processor with 3 GHz or faster clock speed. Multi-core processor recommended for optimal performance.
8 GB or more of RAM recommended, 4 GB of RAM minimum.
300-GB Disk with RAID support for data. The amount of disk space necessary depends on the frequency of data collected (number of work orders, operations, production quantities, etc.) and the amount of data kept online in the production database.
Depending on complexity and size of the database server, 30 GB or more of available disk space is recommended. The database hard disk space should be enough to support the storage and performance requirements for your particular deployment.

MES Web Application Server

Computer with 2 GHz or faster processor clock speed.
8 GB or more of RAM recommended, 4 GB of RAM minimum.

All Systems (Client Applications)

30 GB (minimum) hard drive
Super VGA (1024 x 768) or higher resolution video adapter and monitor
CD-ROM or DVD drive, or access to a network share or portable media device that contains the installation files
Keyboard
Mouse or compatible pointing device

Minimum Hardware Requirements for Supported Windows Versions

The following additional minimum hardware might be required based on the version of Windows being used.

See your specific Microsoft operating system hardware requirements for details.


Operating Systems		Type	Service Pack Level	Links to Microsoft Operating System Requirements
Windows Server 2012	64-bit	Standard or Datacenter	none	Windows Server 2012 main docs page
Windows Server 2012 R2	64-bit	Standard or Datacenter	none	Windows Server 2012 main docs page
Windows Server 2016	64-bit	Standard or Datacenter	none	Windows Server 2016: System Requirements
Windows 8.1	32-bit & 64-bit	Professional or Enterprise	none	Windows 8.1 Enterprise: System Requirements
Windows 10	32-bit & 64-bit	Professional or Enterprise	none	Windows 10 Enterprise System Requirements

Software Requirements

This section lists the Aveva and other third-party software requirements to install MES 2017:

Microsoft .NET Framework 4.5.1 is required for all components except MES Intelligence Reports, as Intelligence requires .NET Framework 4.5.2. If the required version of .NET Framework is not installed, it will be installed during the MES installation.
If installing MES Web Portal, the following are required:
- Microsoft Internet Information Services 7.5.
- Microsoft Web Deploy tool.
- MES Web Portal is compatible with version 8.0.3 of newtonsoft.json.dll.
If installing MES application objects, the following are required:
- The Entity Model Builder feature requires ArchestrA Integrated Development Environment (ArchestrA IDE).
- The Utilization Capability Object (UCO) and Operations Capability Object (OCO) require Microsoft Message Queue for their asynchronous calls.
- The UCO cannot be deployed/co-exist onto the same platform with any other application object that uses a version of the newtonsoft.json.dll that is not from version 6.0.1 to 6.0.8. Otherwise, a Could not load file or assembly error message will be generated.

Web Browsers Supported for MES Web Portal Client

The MES Web Portal client has been validated with the following web browsers, using the web browser versions that were available at the time of the MES 2017 release or, for Edge, using the version shown:

Chrome
Edge version 38
Firefox
Internet Explorer 10, 10 Native, and 11

It is expected that the MES Web Portal client will operate properly with subsequent releases of Chrome, Edge, and Firefox browsers. However, if any MES Web Portal features do not function due to changes in a new release of Chrome, Edge, or Firefox, customers will be notified by a Technical Alert when we are made aware of the issue.

Note: When running MES Web Portal in some previous releases of Internet Explorer 11, there is a browser issue that can cause filter boxes on a page to not display correctly (for example, the filter box might be covered by a tile). To prevent this, make sure that a recent release of Internet Explorer 11 (more recent than 11.0.9600.17280) is installed.

Note: Demo videos in the MES Web Portal help will not run in standard Firefox. To run demo videos in Firefox, you must have an MP4-capable video player such as Windows Media Player installed on both the server and client machines, or have a third-party MP4 plug-in installed in Firefox.

Database Requirements

Supported Microsoft SQL Server Versions


Microsoft SQL Server Version		Type	Service Pack Level
2012	32-bit & 64-bit	Express, Standard, or Enterprise Edition	SP4
2014	32-bit & 64-bit	Express, Standard, or Enterprise Edition	SP2
2016	64-bit	Express, Standard, or Enterprise Edition	SP2
2017	64-bit	Express, Standard, or Enterprise Edition

Requirements

The MES 2017 release requires SQL Server 2012 or greater as it makes use of SQL functionality added in that release.
SQL Server should be configured for TCP/IP for local connections. SQL Server should also be configured for TCP/IP for remote connections if servers that require access to the MES database, such as the MES middleware server or the Reports server, are on remote machines. If you use SQL Server, make sure it is installed using a case-insensitive collation.
Microsoft Distributed Transaction Coordinator and IIS 6.0 or later.
MES Database using multiple languages requires AL32UTF8 Unicode character set installed on your server.

Recommendations

For proper database maintenance, use an SQL Enterprise version due to the availability of online indexing capability.

Operating System Requirements

The following table lists the operating systems that are supported and can be installed on computers that run MES 2017.


Operating Systems		Type	Service Pack Level	MES Features
Operating Systems		Type	Service Pack Level	Client Components	Database	Middleware	MES Web Portal Service	Reports Components
Windows Server 2012	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows Server 2012 R2	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows Server 2016	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows 8.1	32-bit & 64-bit	Professional or Enterprise	none	Yes	Yes ¹	Yes ¹	No	Yes
Windows 10	32-bit & 64-bit	Professional or Enterprise	none	Yes	Yes ¹	Yes ¹	No	Yes

¹ Indicates that it is supported for sales and demo purposes only, not for production systems.

Support for Virtual Environments and High Availability

The MES 2017 software can be run in virtual environments to support High Availability for Live Migration and Failover. Implementing High Availability can be performed using VMware technology or Microsoft Hyper-V technology.

For information about implementing MES in a virtual environment, refer to the ArchestrA System Platform Virtual Implementation Guide and the MES Virtual Implementation Guide.

For specific information on VMware product compatibility, go to http://www.vmware.com/resources/compatibility/search.php.

Support for Non-English Versions of Operating Systems

The MES 2017 software runs on the following non-English operating systems:

French
German
Japanese
Simplified Chinese
Russian
Spanish

The corresponding language versions of Microsoft SQL server are used, where applicable.

MES Firewall Exceptions List and Firewall Ports

Exception white list entries and firewall ports specific to MES applications are not needed with MES 2017. HTTP or SQL Server firewall ports that are required by MES applications are opened by default on Windows or by installing SQL Server.

Product Compatibility

MES 2017 is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

For the most current compatibility information, see the Technology Matrix, which is available in the Knowledge and Support Center. To access the Knowledge and Support Center, start at the Contact Page and click through the Customer Support links.

Component	Version	Compatibility	Co-existence
InTouch^®	2014 R2, 2017	Y	Y
Application Server	2014 R2, 2017	Y	Y
System Platform	2014 R2, 2017	Y	Y
Operations Management Interface (OMI)	2017	N¹	Y
Historian Server	2014 R2, 2017	N/A	Y
Historian Client	2014 R2, 2017	N/A	Y
Information Server	2014 R2	Y	Y
InBatch™	2014 R3	N/A	Y
QI Analyst™	8.0 SP4	N/A	Y
Intelligence	2014 R2	N	Y
Intelligence	2014 R3	Y	Y
Intelligence	2017²	N	Y
Wonderware Enterprise Integrator	2014 R3	N	N
Enterprise Integration	2017	Y	Y
Recipe Manager Plus	2014 R3, 2017	N/A	Y
Skelta™ BPM Workflow Management	2014 R2 SP2 P01	N	Y
Skelta™ BPM Workflow Management	2017	Y	Y
Skelta™ BPM Workflow Management	2017 R2	Y	Y
Skelta™ BPM Connector/Extensions for MES	5.3³	N	N
Skelta™ BPM Connector/Extensions for MES	5.5⁴	N	N
Skelta™ BPM Connector/Extensions for MES	6.0⁵	Y	Y
Skelta™ BPM Connector/Extensions for MES	6.2⁶	Y	Y

¹OMI 2017, 2017 Update1, and 2017 Update2 do not support .NET controls and therefore cannot contain any of the MES .NET controls for visualization. Starting with OMI 2017 Update2, external libraries can be used in the scripting environment, which includes the wrapped MES Stateful and Stateless API libraries.

²Check the Knowledge and Support Center for an updated model file. To access the Knowledge and Support Center, start at the Contact Page and click through the Customer Support links.

³This version of Skelta BPM Connector/Extension for MES works with MES 2014 R3 and Skelta BPM 2014 R2 SP2 P01.

⁴This version of Skelta BPM Connector/Extension for MES works with MES 2014 R3 and Skelta BPM 2017.

⁵This version of Skelta BPM Connector/Extension for MES works with MES 2017 and Skelta BPM 2017.

⁶This version of Skelta BPM Connector/Extension for MES works with MES 2017 and Skelta BPM 2017 R2.

Related Topics

Licensing

The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws and is used by MES under license from Microsoft.

Quinn-Curtis SPC Chart Control:

The use of the QCSPCChart and QCChart2D WPF, .NET, and JavaScript controls require the purchase of an Advanced Dev Studio or MES Quality license.

Related Topics

Upgrading from a Previous Version to MES 2017

The upgrade from MES version 4.0 (all service packs and patches), 4.5 (including P1), 5.0 (including SP1 and R2), and 5.3 is supported. To upgrade from an earlier version, you need to first uninstall the previous version and then install the new version.

The MES Database Setup component in the post-install Configurator application supports migration of databases from version 3.1 and later. To migrate from versions earlier than 3.1, you must first update the database to version 3.1. Custom modifications to any version of the MES database might not be supported by the utility and might prevent migration.

The MES database upgrade to this version will take significantly longer than previous upgrades as the utilization data must be migrated to the new schema. Databases with multiple millions of records in the Util_Log, Job_Util_Log_Link, and Item_Prod tables will take on the order of hours to migrate. Prior to migration, the post-install Configurator application will provide a rough estimate of the time required.

Note: If an existing database has custom indexes or keys that reference MES core tables, the database migration will fail. Prior to upgrading, drop any custom indexes and keys. They can be added back after the database migration is complete.

For more information on upgrading, see the MES Installation Guide and online help.

Related Topics

Resolved Issues

This section describes important resolved issues in MES 2017, listed by their Change Request number.


L00120369		The LogonEntList() method of Stateful API FactMES.Client.Common.User class logs a user on when the user is not certified.
L00130286		SPC Chart and Sample Viewer controls do not resize if contained in a graphic that was shown dynamically using the function call in Application Server ShowGraphic or the Show Symbol animation.
L00134990		During a shift change, the events in the util_log table have the wrong duration or negative duration with the UCO writing events at the same time.
L00142497		Negative and 0 duration entries in util_log.
L00142614		With the stored procedure sp_I_Item_Prod_AddProdPostExec, production counts do not get properly added to the tpm_stat table.
L00143615		No error occurs when the consumed quantity is more than maximum value configured for the BOM item.
L00143769		HF 134990 for 5.0 SP1: During a shift change, the events in the util_log table have the wrong duration or negative duration with the UCO writing events at the same time.
L00143866		When editing events associated to a job that spans a shift change, the stored procedure sp_U_Job_Exec_AdjustJobDur can delete records in job_util_log_link seeming randomly based on how SQL returns data.
L00143902		Issue after installing HF 143576: The reason group is not getting updated when the reason code changes.
L00143981		When running a Restore, it aborts due to system out of memory and issues with conversion from nvarchar to float.
L00144003		A project-specific build of the Process Editor control for Workflow forms and Skelta BPM 2014 R2 SP2 P01 Connector for MES 4.6 included the Web API calls in the MES 2017 release.
L00144226		The stored procedure sp_i_item_inv_add does not convert the UOM before checking if there is negative inventory.
L00144237		MES Client APR does not have the option to purge the table Storage_Ent_Transfer.
L00144252		Restoring MES Quality data from an archive results in the error: Cannot perform '=' operation on System.String and System.Int32.
L00144413		Archive and Purge jobs abort with System Out Of Memory Exception when large amounts of data are involved.
L00144486		When editing an item in a grid in MES Client, the right-click menu shows a separator through the options.
L00144586		Shift schedule calculation is wrong when the database is set on British English date format because the first day of the week is Monday instead of U.S. expectation of Sunday.
L00144608		Auto-logon using ArchestrA Group Security does not work for all MES .NET client controls in InTouch.
L00144688		Auto-logon using ArchestrA Group Security does not work for all MES .NET client controls in InTouch.
L00144714		Circular Reason groups cause 100% CPU in MES Web Portal. The fix will not allow a circular reference, but the existing database will have to be repaired manually in the table.
L00144751		Cursor is not closed in the stored procedure sp_BOM_Item_Oper_Link_Chk.
L00144775		Closing a PO that has run for several days with many events will time out and take more than 9 minutes to complete.
L00144901		Auto-logon using ArchestrA Group Security does not work for all MES .NET client controls in InTouch.
L00144951		OCO subscription to update current attributes does not reconnect after loss of communication with the middleware.
L00144966		HF 144775 for 4.5: Closing a PO that has run for several days with many events will time out and take more than 9 minutes to complete.
L00144968		Starting two jobs on different job positions simultaneously deletes the job_util_log_link record on the first job position.
L00145026		The API TransferAndUpdateInv() method will return without any error if some parameters are passed incorrectly.
L00145038		Occasional OS login failures (configuration and run time) in multi-domain environments. Switch to a different Microsoft call for user authentication/verification based on Microsoft recommendation.
L00145042		After a shift change and auto-logoff, the Sample Viewer control tries to update the grid with no records and causes an error.
L00145255		CR 145038 for 5.2: OS group login taking 7 to 10 seconds to login.
L00145345		Merge hotfix L00145038 and L00143753 as the fix is in the same files.
L00145444		The OCO fails to reconnect after rebooting the MES database server.
L00145564		The sample_result (Pending, OOS, GOOD) does not update for "not monitored" characteristics.
L00145638		The SID field in the grp_name table is not being populated by MES Client when adding OS Groups.
L00145681		CR 145038 for 5.3: OS group login taking 7 to 10 seconds to login.
L00145683		If SQL Server or the MES middleware is not available during a deploy, the UCO does not pick up the entity ID and does not recover.
L00145710		Occasionally, sample status is not resulting in Complete; it continues to stay as In Progress.
L00145716		An exception can occur on subsequent API calls when an open transaction is allowed to time out (calling startTransaction with no Commit or Rollback).
L00145745		The Ent.Update() method does not accept NULL for parentEntId and site parameters, while Ent.UpdateSpecific() does.
L00145747		The stored procedure sp_S_job_exec_VerifyProcess is using floats on a calculation that results in an error in BOM quantities at operations.
L00145968		HF 145745 for 5.3: The Ent.Update() method does not accept NULL for parentEntId and site parameters, while Ent.UpdateSpecific() does.
L00145977		Related to HF 145444: OCO and UCO objects are not recovering after an MES database SQL Server failure.
L00146064		Issue with HF 127323: The hour_start_utc can be incorrect in the TPM_stat table when calling the stored procedure sp_I_Item_Prod_AddProdPostExec with a historical shift.
L00146188		A user not linked to a certification can authorize the certification.
L00146214		An OCO PEM error occurs when attempting to generate a new genealogy ID.
L00146219		HF 144751 for 5.2: Cursor is not closed in the stored procedure sp_BOM_Item_Oper_Link_Chk.
L00146272		HF 145716 for 5.3: An exception can occur on subsequent API calls when an open transaction is allowed to time out (calling startTransaction with no Commit or Rollback).
L00146333		There are no lot numbers in Supervisor shipment lots. Get the error There are no lots available to ship.
L00146374		MES Web Portal consumes memory that will not be released for the WO page.
L00146382		The API ExecSP() method throws an error for the DateTime parameter in the EN-GB (English - Great Britain) locale.
L00146403		A value that is the same as the LSL gives a warning as an out-of-spec condition.
L00146451		When set to Chinese, standard operations generate the following error: Unable to cast object of type"StepGroupAndSteps.DataModel.StandardOperationStepModel"to type"FactMES.Clients.CommonLibrary.DataModel.Prod.OperationStepDataModelBase"
L00146493		HF 146382 for 5.3: The API ExecSP() method throws an error for the DateTime parameter in the EN-GB (English - Great Britain) locale.
L00146627		HF 144751 for 5.3: Cursor is not closed in the stored procedure sp_BOM_Item_Oper_Link_Chk.
L00146628		Combine HF 145710 and 145564 into one HF for MES 5.3.
L00146730		MES Web Portal consumes memory that will not be released for pages in addition to the WO page.
L00146752		MES Service is randomly not generating calendar QM samples during a shift change.
L00147052		The MES OEE Analysis Intelligence report does not calculate the performance correctly.
L00147085		Any Client PC on which software is run that communicates with MES via the MES middleware must also match the dd/MM/yyyy regional setting. Some calls will fail if they do not match.
L00147115		After applying a filter at the entity level in MES Client, it takes around 10-15 minutes to display the entities.
L00147135		The Import scheduler of SCC does not provide an error when it cannot access the file directory with the MES middleware account.
L00147219		The MES stored procedure SetRawReasonByName is taking long time to complete execution and it is resulting in many transactions getting suspended.
L00147341		Cannot view the Work Order Management page due to a server timeout.
L00147378		Cannot switch the job state in MES Operator when the number of job routes is more than 100.
L00147644		HF 145710 for 5.0.1: Occasionally, sample status is not resulting in Complete; it continues to stay as In Progress.
L00147696		The qty_per_parent_item column is rounded off in the job_bom_step table.
L00147697		HF 147696 for 5.3: The qty_per_parent_item column is rounded off in the job_bom_step table.
L00147796		When trying to delete an item with many BOM versions to be produced (BOM POS 0) from the MES Client Process tab, the item does not get deleted and you see time-out errors to the MES database in the SMC.
L00147986		The region_id W.Australia standard time only has a year 2007 to 2009 record in the tz_offset table when selecting the time zone (UTC+08:00)Perth.
L00148023		HF 143866 for 5.3: When editing events associated to a job that spans a shift change, the stored procedure sp_U_Job_Exec_AdjustJobDur can delete records in the job_util_log_link table seeming randomly based on how SQL returns data.
L00148208		Shifts are not created in MES (version 4.6 Nestle) due to a deadlock on the stored procedure sp_U_Util_Log_UpdAllDurations.
L00148233		HF 143866 for 5.2: When editing events associated to a job that spans a shift change, the stored procedure sp_U_Job_Exec_AdjustJobDur can delete records in the job_util_log_link table seeming randomly based on how SQL returns data.
L00148348		Rerelease of HF 147986: The region_id W.Australia standard time only has a year 2007 to 2009 record in the tz_offset table when selecting the time zone (UTC+08:00)Perth.
L00148409		CR 147115 for 5.3: After applying a filter at the entity level in MES Client, it takes around 10-15 minutes to display the entities.
L00148493	The DB/MW Communication configuration component attempts to create the SQL user while using the machine name instead of configured service user.
L00148802		HF 145564 for 5.0.1: The sample_result (Pending, OOS, GOOD) does not update for "not monitored" characteristics.
L00148933		Locking OCO PEM attributes at the template causes an error when the object is deployed.
L00149149		Undeploy/deploy of OCO causes rolling counters to improperly increment, resulting in excessive, invalid item production
L00149168		CR 147115 for 5.2: After applying filter at entity level in MES Client, it takes around 10-15 minutes to display the entities.
L00149223		HF 145564 for 5.3: sample_result (Pending, OOS, GOOD) doesn't update for "not monitored" characteristics.
L00149373		Incorrect event time calculated when calling aaMES.Util.aaUtilLog.AdjustDuration and aaMES.Util.aaUtilExec.SetReason, which use sp_U_Util_Log_AdjustDuration.
L00149390		HF 145747 for 5.2: The stored procedure sp_S_job_exec_VerifyProcess is using floats on a calculation that results in an error in BOM quantities at operations.
L00149392		HF 145747 for 5.3: The stored procedure sp_S_job_exec_VerifyProcess is using floats on a calculation that results in an error in BOM quantities at operations.
L00149480		Unable to configure Middleware with SQL Server on remote node and non-default port.

Related Topics

Known Issues

This section describes important known issues in MES 2017, and in System Platform that affect MES.

License Viewer Shortcut Does Not Open After Uninstall

When uninstalling a software component that uses the ArchestrA.lic file with other components still installed, the shortcut to the License Viewer application (aaLicView.exe) might no longer work. This is more likely to happen when uninstalling MES 2014 R3 or when uninstalling any Aveva component from a non-default install path. This issue can be resolved by modifying the shortcut location manually or by running a repair on any of the remaining Aveva software components.

MES Client Performance Affected by Skelta 2017 R2 on the Same Node

If Skelta 2017 R2 is installed on the same node as MES Client, there will be a noticeable slowdown in MES Client due to listening for trace messages.

MES Intelligence Reports: Detection of Utilization Event Deletion or Modification

The MES Intelligence Reports model cannot detect utilization event deletion or duration modification. The Intelligence service is dependent upon a detection method for notification of changes to records. The MES model uses the last_edit_at field in the MES database for its detection method. When a utilization event is deleted by modifying an existing event's duration or inserting a new event to cover an existing event, there is no option to notify the Intelligence Service. Similarly, if an event's duration is changed but not its start time, the last_edit_at column is not modified since the duration is not stored in the new Util_History table, resulting in no notification to the Intelligence Service.

Known Issues for MES

The following table lists the known open change requests for MES, listed by their change request number.

L00131983	Trying to start a job on more than one machine causes an error inserting into the prod_rate_history table on very specific scenarios.
L00132902	If multiple items to be produced in a process have a common sub-item to be produced in BOM #1 and BOM #2, then every time that common sub-item is marked as "Set as Produced Item" on BOM #1 for an operation, the same sub-item will be marked as produced on that operation for BOM #2.
L00133800	The date/time control on the entity configuration Attributes tab in MES Web Portal is enabled only after the third click in Internet Explorer 11 when used for the first time.
L00135404	With the OS language set to Russian, the Entity OEE targets set in MES Client will generate a validation error but still save correctly.
L00137118	During migration of the MES database from MES version 4.5 SP1 to 5.0 SP1, there is an error associated to conflict with check constraint CK_Sample_Size. MES 2014 (version 5.0) and above prohibit this invalid configuration. The user must correct the bad data in the database and then run the migration again.
L00143414	Launching MES Operator following a fresh install fails with the error Unable to load DLL 'PEGRP32C.DLL'. This is an intermittent issue that can be resolved by rebooting the machine after installation.
L00148162	Production counts stop during a shift change in system with many records and custom indices
L00148429	Samples are generated even after a job is paused.
L00148433	Work orders and items produced overlap on the Monitor page if the screen is not maximized.
L00148750	Cannot login to the MES Web Portal for OS Group-based security in specific scenarios.
L00148781	End job frequency creates samples for previously completed jobs.
L00148797	API Item_Prod and Item_Cons queries validate the user_id parameter passed and will not return all requested rows.
L00148823	The API ItemInv.Add() method incorrectly merges lots and generates an error when using sublots.
L00148962	Creating a new BOM version takes a very long time when many BOM versions exist.
L00149173	Stored procedure SP_U_Item incorrectly declares the max_sublot_size and max_order_size as an integer when SP_I_Item and the Item table have the fields set as Float.
L00149287	With end job and production count frequencies enabled, when multiple entities have jobs running and end job occurs before any production count samples are readied, future production count samples are not getting cleaned up.
L00149518	Shift exceptions are being missed when configured during the same shift.
L00149795	Unable to configure MES middleware if the fully qualified domain name differs from the pre-Windows 2000 domain name.

Known Issues for System Platform and Common Components That Affect MES

The following table lists the known open change requests for System Platform that affect MES, listed by their change request number.

L00117794	Tooltip text on the MES Button Bar .NET Control buttons is not shown when running the control in InTouch. This is an InTouch issue.
L00136956	For Wonderware System Platform 2014 R2 (but not earlier versions), in the OCO, the Attributes tab does not show the Properties window on the right side. To correct the issue, click the Filter icon to show the filter and then click it again to collapse the filter. After this the Properties window displays. Customers can also request Hotfix 139108 for Wonderware System Platform 2014 R2 Patch 01 or Hotfix 141524 for Wonderware System Platform 2014 R2 SP1. This is fixed in System Platform 2017.
L00138837	AppEngine can crash due to the calls made to the FactMES API DLLs even when using try/catch. Specific to Nullable data types. Will not be fixed in Application Server, so recommendation is to continue using the wrapped MES API DLLs in Application server scripting.
L00140001	On an OS using a comma separator instead of a period separator for numbers, when the ArchectrA IDE is first opened, the MES objects will display the period separator instead of the comma separator. If you open another editor, the MES objects will display correctly. This is an ArchestrA IDE issue.
L00140616	Dynamic attributes deletion doesn’t propagate in Wonderware System Platform 2014 R2 SP1. This impacts the OCO production and consumption counters and the SRO characteristic attributes. This is fixed in System Platform 2017. For System Platform 2014 R2 Patch 01 can request hotfix 138741
L00144202	After failover, selecting an OCO object with PEM enabled in the Object Viewer logs a error messages from the BaseRuntimeComponentServer component when reading a PEM extended attribute's data type property. This can be corrected by restarting the hosting engine of the object.

Related Topics

http://get.adobe.com/reader/

The MES 2017 documentation set includes the following:

MES Deployment Guide

Provides guidance on deploying a MES solution.

MES Virtual Environment Implementation Guide

Provides information to assist with implementing MES in a virtualized environment.

ReadMe

Provides information about software and hardware requirements, known issues, licensing, and documentation.

MES Installation Guide and online help

Provides information about installing MES applications.

MES Client User Guide and online help

Provides information about customizing and maintaining the plant floor information.

MES Configurator User Guide

Provides information about customizing and maintaining the MES system.

MES Dynamic Routing User Guide

Provides information required to set up dynamic routing of operations through a process defined in MES.

MES Middleware Extensibility Hooks Reference

Provides information about how to use middleware extensibility hooks to perform custom actions before or after a specific middleware event is executed.

MES .NET Controls Developer Guide

Provides information about the properties and methods of the MES .NET controls for use in custom applications and ArchestrA graphics.

MES Application Object (OCO, UCO, SRO) Help

Provides information about run-time behavior, configuration, and run-time attributes of UCO, OCO, and SRO application objects. This help is accessed from the Object Editor Help menu in the ArchestrA IDE.

Operation Capability Object (OCO) User Guide

Provides information about installing, configuring, and using the Operations Capability Object to track production transactions against equipment.

Sample Recording Object (SRO) User Guide

Provides information about installing, configuring, and using the Sample Recording Object to collect and store values for samples.

Utilization Capability Object (UCO) User Guide

Provides information about installing, configuring, and using the Utilization Capability Object to collect equipment performance data.

MES Entity Model Builder User Guide

Provides information about creating entities from the ArchestrA equipment model.

MES Stateless API Reference online help

Provides information about using the Stateless API within the ArchestrA IDE to develop and customize ArchestrA scripts.

MES Stateful API Reference online help

Provides information about using the Stateful API within the ArchestrA IDE to develop and customize ArchestrA scripts.

MES Web API Reference online help

Provides information about using the Web API to develop custom applications.

MES Operator User Guide

Provides information about executing production processes at the plant floor using the Operator application.

MES Web Portal User Guide and online help

Provides information about using the web browser-based MES Web Portal to customize and maintain the MES system and execute jobs at the plant floor.

MES Service User Guide

Provides information about how to use the MES Service utility to perform regularly scheduled tasks in the MES system.

MES Supervisor User Guide

Provides information about coordinating and overseeing the daily activity of the plant floor.

MES Intelligence Reports User Guide

Provides information about viewing MES Intelligence Reports.

MES Reports in Information Server User Guide

Provides information about viewing MES Reports for Information Server with either the Reporting Services feature or the Table Weaver feature of Information Server.

MES Help

Provides online information about MES Configurator, Supervisor, Operator, and Data Editor, and MES Reports in Information Server.

MES Data Editor User Guide

Provides information about inserting and modifying data in the MES database.

MES Web Access User Guide

Provides information about using web access methods that allow MES middleware calls to the MES database.

The MES 2017 product library includes a set of Portable Document Files (PDFs) located in the Docs folder in the MES installation folder. You need Adobe Reader installed on your computer to view the MES documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

After installing Adobe Reader, double-click a PDF file to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.

The MES installation instructions are located in the root folder of the MES installation folder as a PDF file and an online help file. You can view these instructions by clicking Help as you start the MES installation procedure.

Related Topics