Last revision: Thursday, September 3, 2020
This document contains important information about AVEVA™ Manufacturing Execution System (MES) 2020 (version 6.2). 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.
MES 2020 includes the following new features and enhancements.
MES Web API
The MES Middleware now hosts the MES Web API and System Management Services provides the authentication. This is a considerable change from the prior Web API, which relied on IIS. For details, see the MES Installation Guide as this change requires modifications to the existing applications developed against the MES Web API.
All existing V1 and V2 endpoints are not modified in respect to parameters to pass to it; however, the connection to the Web API is new.
Note: The new MES Web API contains endpoints that send any XML commands to MES Middleware. This functionality replaces the Fact Web Access interface and is more secure. This is the last release to support Fact Web Access so convert any usage of Fact Web Access to the new MES Middleware Web API.
MES Web Portal Updates
The MES Web Portal includes the following updates:
MES Intelligence Reporting Updates
MES Client Updates
MES Client now includes additional content from MES Web Portal:
The following system parameters for purging and archiving data are no longer used:
MES API Updates
The MES Stateless API has added the following:
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 installation, upgrading, and configuration of System Management Server.
MES Client User Guide and Help
Updated content to cover the new and updated modules for the changes in this release.
MES Stateless API Reference Help
Updated content to cover API changes described above in "MES API Updates."
MES Intelligence Reports User Guide
Updated content to cover the change described above in "MES Intelligence Reporting Update."
MES Web API Reference
Updated and added endpoints for the changes in this release.
MES Web Portal User Guide and Help
Updated content to cover changes described above in "MES Web Portal Updates."
This section describes the hardware, software, and operating system requirements to install the MES 2020 software.
For the most current compatibility information, see the Technology Matrix page.
The following are the recommended hardware requirements for nodes on which MES 2020 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).
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 |
Links to Microsoft Operating System Requirements |
|
Windows Server 2012 R2 |
64-bit |
Standard or Datacenter |
|
Windows Server 2016 |
64-bit |
Standard or Datacenter |
|
Windows Server 2019 |
64-bit |
Standard or Datacenter |
|
Windows 8.1 |
64-bit |
Professional or Enterprise |
|
Windows 10 (version 1607 or later for .NET 4.7.2) |
64-bit |
Professional or Enterprise |
|
This section lists the AVEVA and other third-party software requirements to install MES 2020:
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 2020 release:
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: Internet Explorer and Microsoft Edge releases prior to Edge Chromium version have a memory leak and are not recommended. Update your browser to Edge Chromium.
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.
Supported Microsoft SQL Server Versions
Microsoft SQL Server Version |
Type |
Service Pack |
|
2014 |
64-bit |
Express, Standard, or Enterprise Edition |
SP3 |
2016 |
64-bit |
Express, Standard, or Enterprise Edition |
SP2 |
2017 |
64-bit |
Express, Standard, or Enterprise Edition |
N/A |
2019 |
64-bit |
Express, Standard, or Enterprise Edition |
N/A |
Requirements
Recommendations
The following table lists the operating systems that are supported and can be installed on computers that run MES 2020.
Operating Systems |
Type |
Version |
MES Features |
|||||
Client |
Database |
Middleware |
MES Web Portal Service |
Reports Components |
||||
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 Server 2019 |
64-bit |
Standard or Datacenter |
none |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server |
64-bit |
Core |
1803/1903 |
No |
No |
No |
No |
No |
Windows 8.1 |
64-bit |
Professional or Enterprise |
none |
Yes |
Yes 1 |
Yes 1 |
No |
Yes |
Windows 10 |
64-bit |
Professional or Enterprise |
1607 (Anniversary Update) or later for .NET 4.7.2 |
Yes |
Yes 1 |
Yes 1 |
No |
Yes |
1 Indicates that it is supported for sales and demo purposes only, not for production systems.
The MES 2020 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, see 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.
The MES 2020 software runs on the following non-English operating systems:
The corresponding language versions of Microsoft SQL server are used, where applicable.
Exception white list entries and firewall ports specific to MES applications are not needed with MES 2020. HTTP or SQL Server firewall ports that are required by MES applications are opened by default on Windows or by installing SQL Server.
The port numbers that MES is using are listed in the following table:
Component |
Port |
Changeable? |
||
|
HTTP |
HTTPS |
HTTP |
HTTPS |
MES Middleware Proxy |
80 |
443 |
Y |
N |
MES Middleware Web API |
|
|
Y |
N |
MES Web Portal |
|
|
N |
Y |
System Management Server |
N/A |
|
N |
Y |
MES 2020 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 page.
Component |
Version |
Compatibility |
Co-existence |
|---|---|---|---|
InTouch® |
2017 U3, 2020 |
Y |
Y |
Application Server |
2017 U3, 2020 |
Y |
Y |
System Platform |
2017 U3, 2020 |
Y |
Y |
Operations Management Interface (OMI) |
2017 U3, 2020 |
Y1 |
Y |
Historian Server |
2017 U3, 2020 |
N/A |
Y |
Historian Client |
2017 U3, 2020 |
N/A |
Y |
Batch Management |
2017 Update 1 |
N/A |
Y |
Batch Management |
2020 |
N/A |
Y |
QI Analyst™ |
8.0 SP4 |
N/A |
Y |
Intelligence |
2017 Update 12 |
Y |
Y |
Enterprise Integration |
2020 |
Y |
Y |
Recipe Management |
2017 Update 2 |
N/A |
Y |
Workflow Management |
2019, 2019 Update 1 |
Y |
Y |
AVEVA™ Work Tasks |
2020 |
Y |
Y |
Skelta™ BPM Connector/Extensions for MES |
6.33 |
N |
N |
Workflow Management Connector/Extensions for MES |
6.44 |
N |
N |
Workflow Management Connector/Extensions for MES |
6.55 |
Y |
Y |
Work Tasks Connector/Extension for MES |
6.66 |
Y |
Y |
1OMI 2017 U3 does not support .NET controls and therefore cannot contain any of the MES .NET controls for visualization. Starting with OMI 2020, external .NET controls can be imported as OMI Apps, which includes the MES .NET controls.
2The version of Intelligence included with MES has different OS and SQL Server version support. Check the Technology Matrix page for the latest updates to Intelligence OS and SQL Server support..
3This version of Skelta BPM Connector/Extension for MES works with MES 2017 R2 and Skelta BPM 2017 or Skelta BPM 2017 R2 (Update 1 and 2).
4This version of Workflow Management Connector/Extension for MES works with MES 2017 R2 and Workflow Management 2019.
5This version of Workflow Management Connector/Extension for MES works with MES 2020 and Workflow Management 2019 and 2019 Update 1.
6This version of Work Tasks Connector/Extension for MES works with MES 2020 and Work Tasks 2020.
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.
Upgrading from the following MES versions is supported:
To upgrade from an earlier version, you must 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 from versions prior to 6.0 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.
In MES version 6.0 and 6.1, the database structure has views that include the same columns as the tables prior to MES version 6.0 so that legacy queries will not break. However, the data will be slightly different as there are no longer extra records during shift changes.
In MES 2020 (version 6.2), an additional link table is added, and the views are updated to use this new table. The migration populates this new link table, so migrations from 6.0 and 6.1 to version 6.2 also take significant time.
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.
Note: You can only perform a database Restore from an archive that was created with the version of MES that you are currently running. Restores using an archive from a previous version of MES are not supported and might fail.
For more information on upgrading, see the MES Installation Guide and online help.
This section describes important resolved issues in MES 2020, listed by their Change Request number.
L00105873 |
Add option to set the display order of item reason groups and item reasons. |
L00146910 |
JobExec.AddProd() Method not handling value of 0 forbyproduct_bom_pos correctly. |
L00148370 |
Error when checking the "Always log on to these Entities", and the "ALL" radio buttons on the entity login screen. |
L00149049 |
Editing an MES Object to remove a dynamic attribute such as decreasing the "Number of Simultaneous Jobs That Can Run On This Entity" on the OCO and then deploying the MES object (without undeploying it) generates errors in the log. Fixed in System Platform 2020. |
L00149834 |
Configuring a BOM using MES Client with the BOM item having update_inv TRUE sets update_inv in bom_item_oper_link to false. |
L00150310 |
Viewing an entity's KPIs on a node with the MES middleware/Web Portal having a different timezone from the entity's site timezone returns incorrect KPIs on the Entity Monitor page. |
L00150416 |
An entity configured to get "Utilization Data from" a different entity does not work when viewing the Monitor tab of the entity in the MES Portal. It does work elsewhere. |
L00150438 |
Passing empty for the required WorkOrder ID parameter to the API aaMES.Prod.aaWO.Delete method will delete ALL work orders from the database. |
L00150831 |
Inventory transfer to an entity with "multiple lots/items stored here become indistinguishable" generates error when location is empty. |
L00150908 |
Inefficiencies in the DoAutoShiftChanges stored procedure. |
L00150925 |
Line performance calculation should use JOB’s 'est_prod_rate' and not the bottleneck entity OEE_EXEC.def_prod_rate. |
L00150964 |
Line Monitor page doesn't show the correct utilization details when an entity gets its utilization source from a different entity. |
L00151027 |
With the API AddProdPostExec method, you can reduce more than the produced amount, resulting in an incorrect total production reported. |
L00151127 |
After a shift change, the wrong duration is shown in MES Web Portal for the current event. |
L00151475 |
Backflushing for substitutes doesn't retrieve the substitute item's settings and instead uses the job BOM item's settings. |
L00151788 |
MES does not maintain distinct consumption records when enabled in system attributes for consumption being made from entities configured for "indistinguishable lots" and having multiple lots at the entity. |
L00151799 |
Supply Chain Connector time-based schedules are not triggering for one hour after clock change in October. |
L00151823 |
When starting a job and sending in a null job position, the Middleware is converting it to 0 before calling stored procedure rather than sending the null so that the stored procedure will get the next available job position. |
L00152173 |
When a new person logs into the InTouch window using OS security, the button bar disappears from the Sample Viewer control. |
L00152245 |
When cloning a BOM in MES Client, MES Client hangs for certain items and no BOM created. |
L00152271 |
Improve MES Intelligence reports query performance on shift and utilization views |
L00152314 |
MES Client Job Queue allows you to change the job state of a running job in the properties pane, which should not be allowed (the grid does not allow for a change). |
L00152502 |
Creating a work order results in a duplicate entry in the Job_Bom table with incorrect bom_pos value because creation of the new BOM version of a parent item is not correctly setting/removing produced item flags. |
L00152505 |
It takes more than 5 minutes to add a BOM version with the API FactMES.EnProd.BomVersion.Add() method. |
L00152574 |
Configuring additional result attributes in SRO object after deployment results in runtime errors when the "preserve runtime changes” option is enabled. Request HF L00154286 for AOT 4.0. |
L00152677 |
When logging in to MES Client on a Web Server, the following error is received: External component has thrown an exception. |
L00152693 |
Ensure qm_spec_id and char_id are required parameters for QMSpecCharLink.UpdateSpecific. |
L00152727 |
HF 152505 for 5.2: It takes more than 5 minutes to add a BOM version with the API FactMES.EnProd.BomVersion.Add() method. |
L00152761 |
Slow performance of creating a work order from a process when many operations exist on the process. |
L00152811 |
Using LOCALHOST when configuring the MES Middleware generates licensing issues on second Middleware. Issue fixed by resolving LOCALHOST to server name during configuration. |
L00152841 |
When a new user logs in with the API, the button bar disappears from the Sample Viewer control. |
L00152991 |
MES middleware will fail to acquire a license after fail-over of SQL Mirroring node. |
L00153015 |
More than 9 parameters in an error message from the database are not handled properly. |
L00153037 |
Job Start and Shift frequencies do not generate all the characteristics defined depending on the alphabetical ordering of multiple active QM Specifications. |
L00153048 |
For the MES Middleware and Middleware Proxy Configuration components in the post-install Configuration utility, the components are shown as not configured and values are not saved after an upgrade. The values must be re-entered after an upgrade. |
L00153137 |
Domain name resolution issue while configuring MES Middleware on a remote node for "NT SERVICE\WCFHostService". |
L00153281 |
Less than the total consumed quantity is being decremented when consuming from indistinguishable lot storage units. |
L00153358 |
Wrong date time compare in SA Item Cons GetConsByFiltr for shift times. |
L00153446 |
The MTBF report includes a row for the last failure event which has no subsequent event and the calculation uses the time period in the calculation. |
L00153475 |
HF L00152841 for MES 6.1: When a new person logs in with the API, the button bar disappears from the Sample Viewer control. |
L00153497 |
Samples for calendar and shift frequency with offset not getting created at shift change. |
L00153499 |
Reduce Inventory (ReduceInv API) doesn't log sublot_id to item_transfer table. |
L00153699 |
Using the MES API in a 64-bit VS application fails to connect to the MES Middleware. |
L00153711 |
Issue with fn_GetEntityID, where it can retrieve incorrect entity ID when same entity name exists in multiple sites. |
L00153800 |
Pausing a job does not change the utilization code to what is configured for Job End Reason Code. |
L00153806 |
User name with an apostrophe cannot log into MES Client. |
L00153808 |
Upgrade from 4.5 to 6.0 and the database migration fails after a few minutes in a DB with distinct production and consumption records enabled and wanting to aggregate. |
L00153809 |
Work Order Job BOM records getting generated with the wrong BOM version - not using the default BOM Version. |
L00153810 |
Problem with daylight saving where the shift history shows the wrong start and end local time for the shift transition. UTC times are correct. |
L00153970 |
HF L00153699 for MES 6.1: Using the MES API in a 64 bit VS application fails to connect to the MES Middleware. |
L00153983 |
The "Verify Process" operation fails with the error "Some of the operations have more BOM being consumed at the operation than available in the BOM" error, even if the quantities are correct. |
L00154001 |
The JobExec.StartJob (sp_U_Job_Exec_StartBatchJobs) does not always return consistent message when supplying incorrect values to start a job. |
L00154012 |
Reduce Inventory (ReduceInv API) doesn't log grade_cd and status_cd to item_transfer table. |
L00154165 |
When multiple parent entity records exist, the default parent entity shown in MES Client is incorrectly shown from ent_link table instead of ent table. |
L00154191 |
Slow performance in Quality.Result.Add() call when validating control rules. Hotfix provides overload to pass in ValidateControlRules parameter. |
L00154416 |
row_id columns in MESDB tables are int32, which can run out after many years. Fixed tables db_deleted_log, shift_to_go, and job_spec to use BigInt |
L00154526 |
With item specific UOM conversions between the line standard item UOM and the job item UOM, the Web portal is showing an error that UOM conversion doesn't exist. |
L00154527 |
Job Start frequency generates extra samples for an entity with multiple job positions. A sample is created for each running job on the entity when only one should be created. |
L00154651 |
Poor Query Performance when saving QM sample results. |
L00154725 |
Cannot set the Job states to ready unless the first operation is set to Running instead of Ready, this then allows the remaining operations to be set to Ready. |
L00154802 |
Float rounding issue when decreasing production quantity. |
L00154870 |
With millions of records, the initial population of the Intelligence Data Model used by the MES reports is failing because of timeouts. |
L00154882 |
Web Portal times out on the Entity monitor currently running Jobs feature. |
L00154903 |
HF L00154527 for 5.2: Job Start frequency generates extra samples for an entity with multiple job positions. A sample is created for each running job on the entity when only one should be created. |
L00154918 |
With 100,000 utilization reasons, opening utilization configuration in MES Client takes 20 minutes. |
L00154963 |
Float rounding issue when reclassifying production quantity. |
L00155100 |
HF L00155116 for MES 6.1: Util_history records are getting deleted after some time because of deadlocks. |
L00155116 |
The “job_hour_history” table should have no rows where runtime=0 and downtime=0 and idletime=0. |
L00155117 |
sp_U_Job_Hour_History_RefreshQtysAndTimes is deadlocking at shift end when multiple equipments (10) complete their job. |
L00155143 |
When setting up an entity to be able to run two jobs at the same time (Identical Job Execs = 2) the parameter “The required quantity must be produced to end a job” is only updated for job_pos 0. |
L00155182 |
Job_event table is missing item_id for job state changes other than Running. |
L00155350 |
MES 2017 util_log view doesn't break up events by shift as the previous version did. |
L00155365 |
JobExec.EndJob API method and overloads are not using the checkCerts parameter when provided. |
L00155424 |
Adding inventory with sp_I_Item_Inv_Add, the uom_id is not logged in item_transfer table. |
L00155427 |
SplitJob() API does not copy the SPARE fields to the newly created job. |
L00155446 |
When inserting an event in the past where the event time falls in standard time and event end falls in daylight savings time, the correct UTC time is recorded, but the local time is off by an hour. |
L00155629 |
Long additive shift exceptions from one entity are affecting shift_to_go data for other entities. |
L00155663 |
Util history records a duplicate reason for the scenario of suspend one job, start another job (new reason), followed by end the first job. |
L00155689 |
MES Client crashes when there is an attribute with data type 12. |
L00155694 |
aaMES.Prod.aaJobExec.AddProdPostExec does not store rmLotNo and rmSubLotNo. |
L00155697 |
MES 2017 job_util_log_link view doesn't break up events by shift as the previous version did. |
L00155701 |
Duplicate records appear in some reports when the line configuration is changed such as the production source entity. |
L00155838 |
AddProdPostExec() API call fails after migration from 2014 R2 to 2017 R2 for jobs running (prior to upgrade) on entities that do not have utilization capability. |
L00155956 |
StorageExec.MoveInventory method's last edit at parameter is not getting parsed properly in other languages. |
L00155986 |
Web Portal can't select standard item for Entity OEE or Line when item display as "item desc". |
L00156044 |
Job Summary Control is not loading data when switching to a different window and back again. |
L00156299 |
If AVEVA License Manager is already installed, then we cannot change the destination folder. |
L00156677 |
MES Middleware Service Configuration issue across domains |
L00156681 |
When Loading the Job queue form in MDM, it takes many seconds for the data to show up in the grid because sp_SA_Job_GetJobQueueByFilter is slow. |
L00156870 |
MES Service creates duplicate tz_offset records causing error in the conversion to utc of dates after the time change from DST to Standard. |
L00157024 |
Transferring inventory between two entities that are marked for indistinguishable and the target entity has no inventory, generates error of not having a common unit. |
L00157070 |
The utilization timeline report does not show full 24 hours time line in one day when select "ALL" in the shift filter. |
L00157366 |
Cannot migrate MES 3.4 database to MES 6.1. |
L00157534 |
MES Web API JobBom does not take into account the parameter bomPos. |
L00157586 |
The Performance calculationperformed in the Web Portal is NOT excluding items produced as a “byproduct”. |
L00157752 |
HF L00153699 for MES 5.2: Using the MES API in a 64-bit VS application fails to connect to the MES Middleware. |
L00158468 |
Refresh of UtilGrid takes 11 seconds on a Production System. |
L00158762 |
MES Web Portal Line Monitor page not subtracting reduced production for short time periods. |
L00158855 |
Calls to JobExec.ChangeJobStates MES Activity returning error message when initialize variables/start command is clicked. |
L00159062 |
Jobs running for over a month take a long time to end and can time out. |
L00159221 |
HF L00158855 for MES 6.1: Calls to JobExec.ChangeJobStates MESActivity returning error message when initialize variables/start command is clicked. |
L00159262 |
HF L00159062 for MES 6.1: Jobs running for over a month take along time to end and can time out. |
This section describes important known issues in MES 2020, and in System Platform that affect MES.
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. |
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 of the Operator following a fresh install fails with an error dialog that states Unable to load DLL 'PEGRP32C.DLL'. This is an intermittent issue that can be resolved by rebooting the machine after installation. |
L00152573 |
Creating an instance of a Sample Recording Object (SRO) logs unhandled errors when there is a default area defined. The workaround is to not have a default area or to ignore the messages. |
L00155839 |
Memory Leak in IE 11 / MS Edge when staying on a collection page such as line collection or work order collection. This is a Microsoft known issue and is addressed in the Chromium version of Edge. |
L00157474 |
Incorrect timestamp values recorded to job_event table when recording backflush consumption. |
L00157709 |
Setting 'Log storage entity changes' is not logging changes to spare_intX to storage_ent_transfer table. |
L00158991 |
Prod.Sublot.Rename does not work when there is inventory |
L00159022 |
Using PEM attributes in the OCO objects to report production/consumption for the same jobs on different entities at the same time then cannot stop second job |
L00159144 |
Users are unable to log in to MES Client when one of the OS groups to which the user belongs is deleted. |
L00159359 |
Pausing / suspending a job from MES Client Job Queue does not update certain fields in job and job_history tables. |
L00159500 |
OCO Job attributes stuck in initializing state after reboot. |
L00159604 |
MES Client APR will crash if an archive job is created and then the system parameter for the Archive Root Directory is changed. |
L00159669 |
Selecting an entity class in MES client, the attributes are not updated. |
L00159775 |
Changing the utilization event for an entity that has been in the same state for over a month takes over a minute. |
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. |
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 ArchestrA 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. |
L00144202 |
After failover, selecting an OCO object with PEM enabled in the Object Viewer logs many 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. |
L00153087 |
SampleViewer .NET control does not honor RequireEntityLogOn property when used in an InTouch Frame window. Request InTouch Hotfix L00153571 for InTouch 2017 Update 2 to be released for your version of InTouch. |
L00158082 |
Importing of the MES folder may generate a warning during the import and log a message that it was unable to find referenced file system.windows.forms. No action is needed and the controls will work. |
L00158123 |
The following 4 properties of the imported OMI apps cannot be saved in the OMI configuration:
|
Defect 1304624 |
Unable to change License Server Name in Configurator with SP2020 and Intelligence 2017 U1 installed and configured on same node. Workaround is to update "C:\ProgramData\AVEVA\Licensing\ServerConfig.xml" file manually. |
Defect 1345502 |
Undeploying a platform in System Platform 2017 U3 SP1 may generate a warning message of “Failed to shutdown platform”. This is a consequence of upgrading to PCS 4.4.6 and its increased security checks. To correct the error, add the ArchestrA user to the ASBSolution windows group. This issue does not exist with System Platform 2020. |
The MES 2020 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 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 V1 Reference online help
Provides information about using the MES Web API V1 to develop custom applications.
MES Web API V3 Reference online help
Provides information about using the MES Web API V3 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 Help
Provides online information about MES Supervisor, Operator, and Data Editor.
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 2020 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.
|
Copyright © 2020 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |