MES 2012 (v 4.5)

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

Wonderware MES 2012 (Version 4.5) Readme

Last revision: 08/23/2012

About This Readme

This document contains important information about Wonderware® MES 2012 (version 4.5) software. This Readme documents the system requirements, known issues, resolved issues, and changes, if any, to the MES 2012 (version 4.5) software documentation included on this CD.

Readme files from previous releases of Wonderware MES are posted to the Wonderware Developer Network at http://wdn.wonderware.com/Downloads.

Wonderware MES 4.5 Release Notes

About This Release - Wonderware MES 4.5

Wonderware MES 4.5 offers the following new features and enhancements:

  • Categories: An extension for creating categories, which are used to group items.
  • Characteristics: An extension for defining variable and attribute characteristics.
  • QM Specifications: An extension for defining quality management specifications in the context of an item, entity, and/or a process and operation. A quality management specification is associated to a sample plan and contains a list of characteristics and a set of control rules.
  • Sample Plans: An extension for defining sample plans, which are a collection of sample plan frequencies and a naming pattern for samples.
  • Sample Plan Frequencies: An extension defining sample plan frequencies, which will be used to determine when samples are collected.
  • Sample Recording Object: A new ArchestrA object used for automatic or semi-automatic collection of sample data.
  • Sample Viewer .NET Control: Displays a grid that shows past samples, current samples, and future samples. The sample viewer is also used to enter new sample data and edit existing sample data.
  • SPC Chart .NET Control: Displays the SPC chart. This control supports ten different chart types that can be configured per instance of the control.
  • Quality Summary and Statistics Report: Provides an overview of the run rule violations, and out of spec conditions sorted by equipment and/or product. It also provides a summary of the statistics such as percent out of spec, count of alarms, average Cpk for a characteristic filtered by entity class, entity, item class, item, and/or process and operation.
  • Measurement Details Report: Provides the list of individual measurements for a characteristic filtered by entity class, entity, item class, item, and/or processes and operation. It also includes one or more SPC charts.
  • Enhancement to the MES Service: MES Service is updated to generate and ready samples based on sample plan frequencies.
  • Enhancement to the MES Middleware: MES Middleware is updated to validate the sample data against run rules when the data is entered.

< top of document >

System Requirements - Wonderware MES 4.5

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

Hardware Requirements

The following are the recommended hardware requirements to install Wonderware MES 4.5.

Middleware or Database Server

  • Computer with dual core processor with 2 gigahertz (GHz) or faster clock speed, or single core processor with 3 GHz or faster clock speed Dual core processor recommended for optimal performance.
  • 2 gigabytes (GB) or more of RAM. (1 GB minimum supported; may limit performance of some features)

Manager Web Application Server

  • Computer with 2 GHz or faster processor clock speed.
  • 1 GB RAM or higher.

All Systems (Client Applications)

  • 30 GB of available disk space
  • Super VGA (1024 x 768) or higher resolution video adapter and monitor
  • CD-ROM or DVD drive
  • Keyboard
  • Mouse or compatible pointing device

Note: The Microsoft Windows Vista operating system imposes hardware requirements that exceed the minimum requirements for Wonderware MES 3.5. If you intend to run selected components of the Wonderware MES version 4.0 with Windows Vista, see the following Microsoft Web site for hardware requirements: www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.aspx.

Minimum Hardware Requirements

See your specific Microsoft operating system hardware requirements for details.

Operating Systems Type Service Pack
Level
Link to Microsoft Operating System Requirements
Windows Server 2003 R2 32-bit only Standard or Enterprise SP2 http://technet.microsoft.com/en-us/windowsserver/bb430827.aspx#EIC
Windows Server 2008 32-bit & 64-bit Standard or Enterprise none, SP1, SP2 http://technet.microsoft.com/en-us/windowsserver/bb414778
Windows Server 2008 R2 32-bit & 64-bit Standard or Enterprise none, SP1 http://technet.microsoft.com/en-us/library/dd578335(v=ws.10)
Windows Vista 32-bit & 64-bit Business none, SP1 http://windows.microsoft.com/en-us/windows-vista/products/system-requirements
Windows XP 32-bit only Professional SP3 http://www.microsoft.com/windowsxp/sysreqs/pro.mspx
Windows 7 32-bit & 64-bit Professional or Enterprise none, SP1 http://windows.microsoft.com/en-us/windows7/products/system-requirements

Note: Depending on complexity and size of your database server, 30 GB or more of available disk space is recommended. Your database hard disk space should be enough to support the storage and performance requirements for your particular deployment.

Software Requirements

This section lists the Wonderware and other third-party software requirements to install the Wonderware MES 4.5 software:

  • Microsoft .NET Framework 3.5 SP1. If this version of the .NET Framework is not installed on the computer, the Wonderware MES installation automatically installs the .NET Framework.
  • The Entity Model Builder feature requires ArchestrA Integrated Development Environment (ArchestrA IDE).
  • The Wonderware Information Server Integration feature requires Wonderware Information Server version 4.0 or later. For more information, see Wonderware MES Reports in Wonderware Information Server Guide.

Database Requirements

Microsoft SQL Server

Version Type Service Pack
Level
Notes
Microsoft SQL Server 2008 (with clustering) 32-bit & 64-bit Standard or Enterprise Edition none, SP1, SP2, SP3 See notes 1, 2 & 3
Microsoft SQL Server 2008 R2 (with clustering) 32-bit & 64-bit Standard or Enterprise Edition none, SP1 See notes 1, 2 & 3
Microsoft SQL Server 2012 32-bit & 64-bit Standard or Enterprise Edition none See notes 1, 2 & 3

Oracle Database

Version
Type
Bit
Notes
Oracle Components (recommended versions)
Client
Data Access
Components
Data Provider
for .NET
Provider
for OLE DB
Objects
for OLE
Services For Microsoft
Transaction Server
Oracle Database 10g Release 2 Standard or Enterprise Edition 32-bit & 64-bit
See note 4
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
Oracle Database 10g Release 2 Standard Edition One 32-bit & 64-bit
See note 4
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
10.2.0.5
Oracle Database 11g Release 2 Standard or Enterprise Edition 32-bit & 64-bit
See note 4
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3
Oracle Database 11g Release 2 Standard Edition One 32-bit & 64-bit
See note 4
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3
11.2.0.3

Notes:

  1. SQL Server should be configured for TCP/IP for local and remote connections. If you use SQL Server, make sure it is installed using a case-insensitive collation.
  2. Microsoft Distributed Transaction Coordinator and IIS 6.0 or later.
  3. MESDB using multiple languages requires AL32UTF8 Unicode character set installed on your server.
  4. The MESDB Configuration Utility requires the Oracle Client installation to configure an Oracle database. SQLPlus must be available.

Note: The Gage_Config table and all of the tables with names starting with “SPC_” except for the SPC_Rule table will be deprecated in a future release.

Using Wonderware MES with Oracle on a Non-English Operating System

When you install Oracle on a supported non-English operating system:

    1. Install with the default CodePage appropriate to the language of the operating system. For example: CL8MSWIN1251 for Russian, WE8MSWIN1252 for French.
    2. Run Regedit.
    3. Go to HKEY_LOCAL_MACHINE|SOFTWARE|ORACLE and look for the key under Oracle for the Oracle Home. Depending on the Oracle version, the wording of this may be different.
    4. Select the NLS_LANG option (LANGUAGE_TERRITORY.CHARACTERSET) associated with this Oracle Home key. Edit the CHARACTERSET to AL32UTF8 so that NLS_LANG option is RUSSIAN_RUSSIA.AL32UTF8.
    5. Install MES as normal.

If you are using a non-English Oracle 11g environment and are saving changes in the MES Client (or any code using the MES API), the 'String was not recognized as a valid DateTime' error occurs.

To fix the issue:

    1. Run Regedit.
    2. Go to HKEY_LOCAL_MACHINE|SOFTWARE|ORACLE and look for the key under Oracle for the Oracle Home key. Depending on the Oracle version, the wording of this may be different.
    3. Right-click the key, point to New and then click String Value.
    4. For the new string value, set the Name to: NLS_DATE_FORMAT
    5. Double-click the new string value and set the Value data to: yyyy-mm-dd hh24:mi:ss

Installing Wonderware MES with an Oracle 64-bit Database

Wonderware MES can connect to and use a 64-bit Oracle 11gR2 (11.2.0.3) database server for better performance. MES clients and applications will need 32-bit Oracle client components in order to connect.

For the Oracle server, you need to install the 64-bit Oracle database server and 32-bit Oracle 11gR2 (11.2.0.3) client. For the MES client, it will need the 32-bit Oracle client and Oracle Data Access Components (ODAC 11.2.0.3) in order to connect the database server.

The following outlines the procedure to set up MES for a 64-bit Oracle database server.

Installing the MES Database on the server

    1. Create the Oracle Database using the 64-bit Oracle Database installation setup. Additional databases can be set up using Oracle’s Database Configuration Assistant (DBCA).
    2. After installing the database, ensure that the listener is up and running for the database that is created.
    3. Start the Oracle Enterprise Manager for the database, so that you can ensure that the instance is up and running and that you can monitor and tune your database.
    4. Install the Oracle 32-bit client, with the Administrator options.
    5. Using the client’s Oracle Net Manager, create a network service name for database.
    6. Test the connection to Oracle database using tnsping and SQL*Plus.
    7. Install MES Database Setup utility.
    8. Create the MES user, tablespace, and schema using the Database Setup utility by entering the net service name and the schema owner and password. The tablespaces, schema, and schema objects will be created by the utility. You will need the password for the SYSTEM user to create the tablespace and schema.

Connecting MES Client to the MES 64-bit Oracle database

    1. If necessary, install the 32-bit Oracle client and create a network service name for the database.
    2. Install the Oracle Database Access Components (ODAC).
    3. Install the MES Client and other components.
    4. Configure the Oracle database using Wonderware MES Database Connection Editor.
      • The Data Source refers to the Oracle network service name.
      • The User Id refers to the schema owner.
      • The Database Password refers to the schema owner password.

      Test the connection and ensure that you can connect successfully. Save the settings.

    5. Restart the MES Middleware and the MES service.
    6. Open MES Client and connect.

Operating System Requirements

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

Operating Systems
Type
Service Pack
Level
Wonderware MES Features
Client
Components
Database
Middleware
Factory
Connector
Manager
Wonderware
Information Server
Windows Server 2003 R2 32-bit only Standard or Enterprise SP2
Yes
Yes
Yes
Yes
Yes
Yes
Windows Server 2008 32-bit & 64-bit Standard or Enterprise none, SP1, SP2
Yes
Yes
Yes
Yes
Yes
Yes
Windows Server 2008 R2 32-bit & 64-bit Standard or Enterprise none, SP1
Yes
Yes
Yes
Yes
Yes
Yes
Windows Vista 32-bit & 64-bit Business none, SP1, SP2
Yes
Yes 1
Yes 1
Yes 1
No
No
Windows XP 32-bit only Professional SP3
Yes
Yes 1
Yes 1
Yes 1
Yes
No
Windows 7 32-bit & 64-bit Professional or Enterprise none, SP1
Yes
Yes 1
Yes 1
Yes 1
Yes
Yes

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

Windows Server 2003 Requirement

If Windows Powershell 2.0 and WinRM 2.0 are installed in Windows Server 2003, Wonderware MES FactWebAccess and Manager Application pools and the default web site will not be created during the Wonderware MES installation. To avoid this issue, uninstall Windows Powershell 2.0 and WinRM 2.0 prior to the Wonderware MES installation.

Support for VMware

Wonderware MES 4.5 software supports the following VMware platforms*:

  • ESX 3.5
  • ESX 4.0
  • ESX 4.1
  • ESXi 4.1
  • ESXi 5.0

* - Does not include support for Failover, Redundancy, and Live Migration.

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

Wonderware MES 4.5 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.

Wonderware MES Firewall Exceptions List

The following table lists the port name and corresponding port numbers that must be added in the Windows Firewall exceptions list for Wonderware MES 4.5.

Port Name Port Number
Port 5413 5413
SQL TCP 1433 1433
SQL Server Browser 1434 1434
HTTP 80 80
TCP 8099 8099

The list of application names that must be added in the Windows Firewall exceptions list for Wonderware MES 4.5 is as follows:

  • DANSrv.exe
  • OpcEnum.exe
  • Microsoft SQL Server
  • Microsoft Distributed Transaction Coordinator (MSDTC)
  • dllhost.exe

< top of document >

Product Compatibility - Wonderware MES 4.5

The Wonderware MES 4.5 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.

    Component Version Compatibility Co-existence
    Wonderware® InTouch® 10.1 SP3, 10.5 P01 Y Y
    Wonderware® Application Server 3.1 SP3, 3.5 P01 Y Y
    Wonderware® Historian Server 10.0, 10.0 SP1 Y Y
    Wonderware® Historian Client 10.0 SP1, 10.0 SP2 Y Y
    Wonderware® Information Server 4.0 SP1, 4.5 Y Y
    Wonderware® InBatch™ 9.0 SP2, 9.5 Y Y
    Wonderware® QI Analyst™ 8.0 SP2 Y Y
    Wonderware® SCADAlarm™ 6.0 SP2 P01 Y Y
    Wonderware® Intelligence 1.5 Y Y

ArchestrA® Workflow 2012 is compatible and can coexist with Wonderware MES 2012. Note that the ArchestrA Workflow provided integration with Wonderware MES 4.0 does not work with Wonderware MES 2012. An update to the integration components will be posted on the Software Downloads site (https://wdn.wonderware.com/sites/WDN/Pages/Downloads/Software.aspx) as soon as they are available.

< top of document >

Licensing - Wonderware MES 4.5

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

Quinn-Curtis SPC Chart Control:

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

< top of document >

Upgrading from a Previous Version - Wonderware MES 4.5

The upgrade from Factelligence 3.4 (Sidus 1), Factelligence 3.5 (Sidus 2), and Wonderware MES 4.0, 4.0 SP1, and 4.0 SP2 is supported. To upgrade from a version earlier than Factelligence 3.4, you need to first uninstall the previous version and then install the new version.

The MES Database Configuration utility delivered with this project 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 Factelligence database may not be supported by the utility and may prevent migration.

For more information on upgrading, see the Wonderware MES Installation Guide.

< top of document >

Resolved Issues - Previous Versions

This section describes important resolved issues in Wonderware MES 4.5 and provides an updated list of resolved issues in Wonderware MES 4.0 SP2.

Wonderware MES 4.5

L00118939: SR 35312045: In MES Client, you cannot save dynamic routing code for a job.
L00119376: You cannot read or update BOM specification value for float data type. The value is always displayed as 0.0.
L00119516: SR 34211354: You cannot view the defined steps for an operation in MES Client, on an Oracle database.
L00119738: SR 103123880: In Steps control, the lot numbers are displayed incorrectly.
L00119816: The time zone offset is not adjusted correctly for daylight saving change in Eastern Europe.
L00119997: If you add a new job to an existing work order, the job BOM WIP flag is recorded incorrectly for the item BOM.
L00120153: SR 103124759: The Inventory is not transferred if you apply CR L00118989. If the source location has more than 1 material, the correct value is not transferred for each lot.
L00120384: SR 35312083: Executing a large import schedule fails and causes the MES middleware to become unresponsive.
L00120602: SR 34211377: If you attempt to logon to an already logged on entity, the system is not responding in a timely manner.
L00120705: SR 103124489: In MES Operator, BOM and Genealogy tabs are disabled.
L00120919: SR 103125245: Starting a paused job intermittently raises a unique key violation error.
L00121021: If sublots are used, Inventory transactions intermittently fail.
L00121119: SR 15712528: If multiple jobs are running on the same entity, duplicate event records are displayed in the "Production Event Summary by Utilization Reason Group" report.
L00121142: SR 41510452: When you upgrade from Operations 3.5 to MES 4.0 SP2, custom SQL cannot be executed through ExecuteBatchXMLCmds.
L00121178: If you update an item specification, the system is not responding in a timely manner.

Wonderware MES 4.0 SP2

L00105462: SR 103118227 (Hot Fix 2040): In Oracle, changing Item State or Item Grade for an Item Reason gives an error and the MES Client crashes.
L00107812: In sp_I_Item_Prod_Split stored procedure, the update statement for the item_prod table does not work because it compares sublot_no parameter with @new_lot_no parameter.
L00108072: Adding a record from SCC to data_log_16 table or data_log_48 table gives an error because all the columns are not passed.
L00108993: SR 103119817 (Hot Fix 2251): In Oracle, an inventory location with less than 1 Item is rounded off to zero and deleted from the database.
L00109296: Installing HF 1142 causes CWOFP to overwrite other work orders created from different BOM versions.
L00109347/
L00110496: In Supervisor, you cannot change the value of Quantity to less than 1 if BOM position is 1.
L00109348/
L00116878: SR 35311765 (Hot Fix 2289): You cannot write PEM attributes to the Data_log_48 table, if there are more than 22 attributes defined.
L00109354: SR 38710166 (Hot Fix 2291): Labor Usage records show the incorrect Shift ID based on the Labor Start Time value.
L00109380: SR 19911603 (Hot Fix 2295): You cannot change Quantity in the configure Operation BOM for a second Item used in the process.
L00109425: In Supervisor, adding the same Item with a different Number and Quantity gives an error.
L00109593: Transferring all the entities from Entity Model Builder to MES takes hours.
L00109638/
L00112752: SR 103120110 (Hot Fix 2306): Middleware is not connecting if SQL Server takes more than a minute to start. The retry parameter is hardcoded to 1 minute and cannot be changed.
L00109966/
L00120522: SR 35311779 (Hot Fix 2505): When creating a Work Order for an Item that has a multi-level BOM an error message appears - "Conversion failed when converting the varchar value to '7e' to data type".
L00109996: Curent Labor fields must display the current labor record, not the first labor record.
L00110206: SR 103120223 (Hot Fix 2427): Issues with stability and usage of the "Transaction Control" in the API.
L00110262: Using Lot Attributes tab gives errors because update takes long time.
L00110335: SR 103119658 (Hot Fix 2356): You cannot reduce inventory after the item is produced.
L00110543: SR 103120586 (Hot Fix 2382): In MES Client when you split a job and change the end time of the job created from the split, the change is not reflected.
L00110584: Database migration utility fails with larger database and gives an error message - "Timeout expired".
L00110618: SR 103120516 (Hot Fix 2373): You cannot Clone/Delete a certified process. The system must reflect the settings for the general parameters when you copy a certified process.
L00110760/
L00111412: SR 103120720 (Hot Fix 2385): When multiple entities are logged on to Utilization control, the control refreshes on a new event for any of the logged entities, and not just for the current entity.
L00110959: You cannot login to the Manager Reports module of MES, if OS Security enabled.
L00111035: SR 40211128 (Hot Fix 2398): FactMES.Client.Common.Items.GetItems() returns all items based only on item class, without considering produced parameter and consumed parameter.
L00111097: SR 103120721(Hot Fix 2426): Work Order purging issues because of change in the format of the Date field supported by UCO and OCO.
L00111103: SR 19911640 (Hot Fix 2406): Issue while updating BOM Version with Supply Chain Connector when multiple BOMs are checked for the Item at an Operation.
L00111189: SR 38710200 (Hot Fix 2410): When opening the Labor Usage tab in DataEditor, a warning message appears warning that the record count being returned will exceed 2000. However, when you click Continue only 3 records are returned.
L00111210: SR 103120849 (Hot Fix 2418): You cannot reconnect to the UCO, if the Database/Middleware server is rebooted.
L00111214/
L00119586: SR 35311811 (Hot Fix 2412): Using Auto Login and OS Security does not allow you to access the Process or the Work Queue screens.
L00111319/
L00118419: SR 35311790 (Hot Fix 2419): If the sort criterion uses a Reason Group, the Counts/Duration control takes about a minute to return. If the sort criterion uses only a Reason, and not a Reason Group, the control populates in seconds.
L00111354: SR 103120925 (Hot Fix 2422): You cannot enter negative values for floating point data type in Detail Specification dialog box.
L00111592: SR 103120218 (Hot Fix 2434): Factelligence / MES Service takes too long to complete the Minutely tasks when the database is large.
L00111597: SR 103121035 (Hot Fix 2436): Issue in Operator Utilization Grid when the filter is set. It does not filter by the Status in the grid.
L00111741: SR 103120867 (Hot Fix 2445): The .NET client controls give an error if you close and open them again. Over time, InTouch needs to be restarted as it becomes increasingly slower.
L00111751: SR 40211349 (Hot Fix 2443): Cannot enter Work Order Notes, Job Notes, or Item Notes from MES Operator with Touch Screen.
L00111753: SR 40211350 (Hot Fix 2444): The Data Log tab in Operator has no popup keyboard / Touch Screen capability.
L00111787: If current data uses site field, upgrading from Factelligence 3.4 to Wonderware MES 4.0 gives an error.
L00111808: SR 42010020 (Hot Fix 2451): The MES Reports have errors in dates when the Regional Setting is not "en-US".
L00111906: (Hot Fix 2468): While trying to stop a Job, an error message appears - "Difference of two datetime columns caused overflow at runtime".
L00111968: (Hot Fix 2462): When a Labor Usage record extends from one shift to the next, the record should be split, creating one record for each shift.
L00112030: SR38710189: Issue with high CPU consumption when running with several thin client sessions that are idling at 10% CPU, and when the total CPU load overloads the terminal server.
L00112583: SR 19911635 (Hot Fix 2486): Issue trying to configure OS Users on a domain with the name ending in .COM.
L00112730: When UCO has more than 270 raw reason codes defined, Entity Model Builder takes a very long time and never syncs with MES database.
L00112799: SR 40211602 (Hot Fix 2502): When using a "Pending Reason" and then selecting a Final Reason, the four Category fields in the util_log are not set correctly.
L00113059: SR 40211672 (Hot Fix 2513): Issue with rounding when using decimals for Production Quantities. The values are not displayed correctly in the Supervisor Queue's Quantity Produced column.
L00113493: SR 15712234: When a Work Order with Required Quantity greater than 2264420 is created from the Supply Chain Connector (SCC), the SCC Schedule fails with an exception. When a Work Order with Required Quantity greater than 2264420 is updated from the SCC, the SCC Schedule succeeds.
L00113503: SR 103121599: Issue with the API's Transaction Control returning Middleware errors.
L00113543: Issue with the MES Client when an Entity's Job property "Must require Quantity be produced to end job" is not selected. All the Production records are recorded as "No Shift" even though Shifts are being used.
L00113598: The Manager reports display the following message at the end of the page -"Evaluation copy, contact datadynamics.com for more information."
L00114030: SR 40211733: Trying to complete a Job fails when using Job-based Login parameter.
L00114329: SR 103121443: OS User and OS Group security cannot login to any clients on the system without stopping and starting the Middleware.
L00114513: SR 103121540: An error in the Task Scheduling of the Wonderware MES Service causes the periodic calculations to execute only every other period.
L00114646: SR 37112125: The Steps Control can throw the error message - "The specified row was not found in the database", while navigating through the Steps too quickly.
L00114711: SR 40211890: The MES Client is allowing changes to be saved against a "running" Job in the Work Orders and Jobs module.
L00114745: Exporting Reports using Supply Chain Connector fails. An error message appears - "Err No: 449, Desc: Argument not optional, Source: FIBR".
L00115048/
L00116362: SR 40211862: After migrating from Factelligence 3.4 to Wonderware MES 4.0, the General Parameters in MES Client are not accessible.
L00115090: SR 15712283: In the Operator Utilization tab or the Utilization Grid Control, the "last_edit_by" for all visible existing records is overwritten with the current User, when a reason is updated for a single selected row.
L00115257: SR 40211987: Even when Export Schedule in Supply Chain Connector for "Every N Minutes" is defined with 10 minutes duration, the schedule is executed every minute.
L00115260/
L00116156: SR 40211896: Using the “UPDATE” option for “If Row Exists” for a Supply Chain Connector Import Schedule (job_bom) gives an error message - "the row cannot be updated because it is running or completed" when the Job is "New".
L00115301: Issue with the MES Client’s Work Orders and Jobs window when a Job State is changed and then saved. Critical data in the Job table such as run_ent_id, act_start_time_local, act_finish_time_local, and act_finish_time_utc is lost.
L00115407/
L00115577/
L00115839/
L00115914: Issue with having to link a rework Process to at least one Item.
L00115544: SR 40211893: Error after clearing the Entity filter for the Work Queue in the MES Client.
L00115545: SR 103122186: The Queue Control does not enforce the "May change operators queue display" User Privilege.
L00115574: SR 40211941: The issue, "the specified row cannot be the current row because it is not visible", is raised in Operator after saving the grid's configuration selecting "Include Filter Row".
L00115584: SR 38710239: Issue with invalid error when executing FactMES.API.EnProd.ItemInv.Add.
L00115946: SR 40212095/40212100: Folder or Inventory Controls can crash when used with the ArchestrA Client Toolkit application, if the Folders Control is not the control that processes the Entity Login.
L00115988: SR 40212082: The Labor Control can give an error message - "object reference not set to a valid instance of an object" when multiple users try to logon to the same Entity in the same workstation.
L00116373: SR 17133491: Reason Codes defined in the MES Client using the Greek character set are not displayed correctly in the UCO.
L00116591: SR 40211871: A "DB Connection String" is now required at MES 4.0 on the Trigger tab or Transport tab, of a Supply Chain Connector Import Schedule.
L00116640: SR 103122568: Supervisor does not enable the "Save" button after deleting customer's Contact Information.
L00116761: SR 40212232: Inventory Control gives errors after logging out and logging back in, with Hotfixes L00115946 and L00115988 installed.
L00116832: SR 40212250: The default language is not used for OS group security.
L00116866: SR 35311950: When viewing the Job Route for a Work Order, the Job Routes for all Work Orders with the same Process appear in the grid.
L00116878: SR 35311765 (Hot Fix 2289): You cannot write PEM attributes to the Data_log_48 table, if there are more than 22 attributes defined.
L00116890: SR 15712308: Linking seventy or more Operations for a Process in "Route Map" is taking more than 30 minutes.
L00116916: SR 15712307: When you execute "Insert Standard Operation" for a Process, after insertion, the description is always updated with Operation ID.
L00116973: SR 40212301: Issue with MES about how downstream job's qty_at_start are updated for a work order when a job is completed.
L00116974: Issue when using Steps within an Operation. The Steps cannot be started due to the Middleware indicating that the Steps are already started. The Steps cannot be completed due to the same issue.
L00117038: SR 31310008: The MES Reports have errors in dates when the Regional Setting is not "en-US".
L00117110: When the Queue Control is first initialized the buttons are not correct.
L00117112: Cannot import the OCO into a system migrated from MES 4.0.
L00117289/
L00117351/
L00117372: SR 42410018: Issue with the Work Queue Control when the control is initialized with the highlighted row and selected row not synchronized.
L00117337: MES Client crashes when selecting an Operation in a process. When the same process and operation are viewed in Order Management, MES Client does not crash.
L00117338: Performance issue with MES Client’s Order Management when adding a new Operation to a Work Order and selecting the "Can Schedule To" and "Schedule To".
L00117388: SR 40212312: An unhandled exception is raised in the MES 4.0 SP1 Folders Control.
L00117592/
L00117953: After installing Hot Fix 2426, using the Archive, Purge and Restore, the Restore fails and the error message appears - "Unable to insert <DD/MM/YYYY HH:MM:SS> into last_edit column. Type waited?? is DateTime".
L00117595: SR 37112298: Stateless API call Prod.Lot.Rename raises foreign key errors when trying to rename Serialized Lots.
L00117630: Dynamic routing Work Order does not enable the "Must Consume from WIP" option in the Job BOM for BOM position 0 in first operation.
L00117663: When "Shipping Inventory" in Supervisor, the Date/Time for the transfer is shown incorrectly. It shows the time when the Item was received, and not the time when the Item was transferred.
L00117768: When cloning a Work Order with a Dynamic Route configured, the Rework Code is NULL in the cloned Work Order.
L00117851: Issue when cloning a Work Order that the Start Quantity is not written correctly in the Job table.
L00117896: SR 19911784: Stateless API call Prod.SubLot.Rename raises foreign key errors when trying to rename Serialized Sublots.
L00117931: SR 103123146: Items with the same value for Minimum and Maximum Quantities in the BOM do not consume correctly.
L00118044: When OCO is configured for Storage and the Entity already has a Storage Type defined using the MES Client, the Storage Type is set to NULL when the Entity Model Builder (EMB) is run from IDE.
L00118062: SR 103123434: When calling FactMES.API.Prod.JobExec.AddConsDirect, irrespective of the value passed for the UserID parameter, the method always derives the UserID from the "sessn" table based on the SessionID parameter passed.
L00118073: Issue with Supervisor's Inventory functionality that the Expiry Date adds the GMT time zone offset to the local time.
L00118175: SR 103123272: If the Utilization Reason is "Downtime" or "Idle" during a shift change, the UCO Current Performance and the Utilization Percentages do not match the OEEKPI Control values.
L00118410/
L00118450: SR 35311992: Steps that are superseded and have the "Enter Data" check box selected do not see the data entered for the new Step.
L00118417: SR 42010020 (Hot Fix 2451): The MES Reports have errors in dates when the Regional Setting is not "en-US".
L00118418: SR 41310027: Triggering an OCO PEM instance against a Job that does not have the default Production Rate causes the current Job to end and a new Job to be incorrectly Created and Started.
L00118491: SR 35312002: When there are a large number of Utilization Reasons, editing or adding a Utilization Reason and updating the database is taking 3 - 4 minutes.
L00118499: SR 43110125: Enabling "Distinct Consumption Records" has no effect when consuming from a Entity with Storage and Indistinguishable Lots.
L00118671: The Spare fields are not recorded in the database if the Item is transferred or shipped.
L00118833: SR 27810523: When starting/restarting multiple Work Orders from MES Operator, attempts to start the Job cause errors.
L00118908: SR 103123233: When a "Reset" command is triggered on the OCO with Redundant Application Engines and there is a switch over, the "Reset" command shows Busy after the new master engine is up and running.
L00118945: With Hot Fix L00118671 installed, if the Item is Transferred or Shipped, then UOM_ID, Sublot, and Expiry Date are not recorded in the new record.
L00118955: When using Dynamic Routing, sending more reworked Items to an Entity, where non-running Jobs for the same Work Order are queued, causes the Required and Started Quantities for all Jobs in the Work Order to be updated.
L00118968: SR 103123991: Datalog values of type Logical do not appear in the correct order in the Datalog Control and cannot be toggled reliably, and sometimes cannot be toggled at all. Also, Datetime Datalog values only accept date and not time.
L00118989: SR 103123921: When Consuming from an Indistinguishable Lot with a quantity that is more than the available quantity and if that Entity allows for negative inventory, the Middleware records an incorrect Quantity in Inventory.
L00119025: In the MES Client, an Operation can be configured so that two Items are set to be produced at an Operation, but only one Item should be allowed to be set as produced.
L00119111: When creating a Work Order for an Obsolete Item, a non-descriptive error is returned by the Middleware.
L00119268: A Specification of type "Float" currently has an upper limit value of 99,999.00.
L00119272: In Supply Chain Connector, when creating a Work Order (with Process) the Release Time Local and UTC, and Required Finish Time Local and UTC do not get populated in the database when importing from an XML file.
L00119361: SR 103123146: Items with the same value for Minimum and Maximum Quantities in the BOM do not consume correctly. After implementing the Hot Fix of L00117931, the same error message is raised in a different scenario.
L00119641: In Supervisor, the grid used for defining specifications is not refreshed when entity selection changes.
L00120241: The XML command ExecuteBatchXMLCmds changed its behavior for the Job.UpdateSpecific object between 3.5 and 4.0.

< top of document >

Known Issues - Wonderware MES 4.5

This section describes important known issues in Wonderware MES version 4.5.

L00115018:

The controls support only a 32-bit development environment and not a 64-bit development environment. A control developed in a 32-bit development environment can run in a 64-bit environment.

L00120213:

After you uninstall MES 4.5, the ‘ArchestrA License Server’ Services cannot be started.

L00120324:

The strings in the MES Client are not translated correctly when the default language is Russian in RU OS.

Steps to resolve this issue are as follows:

  1. When you install Oracle, install with the CodePage CL8MSWIN1251.
  2. Run Regedit and go to HKEY_LOCAL_MACHINE|SOFTWARE|ORACLE. Look for the key under Oracle for the Oracle Home (depending on the Oracle version, the wording of this may be different). Select the NLS_LANG option (LANGUAGE_TERRITORY.CHARACTERSET) associated with this Oracle home key. Edit the CHARACTERSET to AL32UTF8 so that NLS_LANG option is RUSSIAN_RUSSIA.AL32UTF8.
  3. Install the MES Server component on the Server node and install the MES Client component on the Client node.
  4. Start the Middleware and MES Service on the Server node.
  5. Start the MES Client on the Client node.

L00121507:

In an MES system topology, if the Galaxy Repository (GR) node does not have any MES components installed on it, you will get errors after you import/upgrade the MES .NET controls because the FactMES.Client.middlewareAccess is not installed.

To resolve this, install the Operator module on the GR node so that the FactMES.Client.middlewareAccess is installed. This will resolve the validation errors for the .NET controls.

L00121661:

Unable to deploy 100 Sample Recording Object (SRO) instances to a WinPlatform.

To resolve this issue, a system should not have more than 50 SRO instances deployed per WinPlatform. Additional instances must be deployed to another WinPlatform (not just to another AppEngine on the same WinPlatform).

L00122112:

Unable to migrate the MES database from the MES 4.0 and 4.0 SP1 versions to MES 2012 on a node where SQL Server is installed as a Network Account.

The issue is that the SQL Server account must have privileges to write to the local computers's hard drive to create the database backup file. To resolve this issue, either choose an option other than backup during the database setup, or change the SQL Server account to one that can write to the local drive.

L00122345:

Multiple sample results are recorded when the characteristic's maximum sample size is left as "null" and is not specified.

To solve this issue, set the maximum sample size to the required value.

L00122362:

Sample Recording Object – Scalability limit.

Loss of sample results may occur with a total system sample collection rate above 200 samples per minute. For example: With 20 concurrent SRO instances configured for 20 entities, at 10 characteristics each, collecting samples every minute, the total system rate is 200 samples per minute.

Refer to the Sample Recording Object user's guide for additional information on limitations with the object. The object contains unavailable fields in this release, which are documented in the user's guide.

Refer to the Wonderware MES .NET Programmer's Guide for limitations on the SPC Chart control. There are specific combinations of chart types, number of results within the sample set, and control limit calculation options that are not supported.

Binary and Counted Attribute Characteristics are not evaluated for control rule violations. This may be added in a future release.

The MES Quality Detail Report requires additional configuration to the SQL Server Reporting Services policy file for the report to load the SPC Chart control. Follow the instructions provided in the Reporting Services Security Configuration.txt file that is located in the \Reporting Services folder.

< top of document >

Known Issues–Wonderware MES 4.5 Documentation

In the MES Stateless API Reference Help, the filter strings are not being shown correctly. Use the following substitutions within the filter strings as they appear in the Help:

  • !MISSING PHRASE ' = $$
  • '!!MISSING PHRASE ' = $$$$
  • '! = $$
  • !MISSING PHRASE ''! = $$$$

For example, the following text:

An example of an empty processFilters string is shown below.

!MISSING PHRASE '$PROCESS_ID='!!MISSING PHRASE 'OPER_ID='!!MISSING PHRASE 'ENTITY='!!MISSING PHRASE 'PROCESS_LEVEL='!!MISSING PHRASE 'PROCESS_STATUS='!!MISSING PHRASE 'CREATOR='!!MISSING PHRASE 'APPROVER='!!MISSING PHRASE 'LASTEDITOR='!!MISSING PHRASE 'CHECKEDOUTBY='! !MISSING PHRASE 'SHOW_STEPS='!!MISSING PHRASE 'SHOW_SPECS='!!MISSING PHRASE '('!!MISSING PHRASE '8001='!!MISSING PHRASE '8002='!!MISSING PHRASE ')'!!MISSING PHRASE 'ICF:'!!MISSING PHRASE 'ITEM_CLASS_DESC='!!MISSING PHRASE 'CONSUMED='!!MISSING PHRASE 'OBSOLETE='!!MISSING PHRASE '('!!MISSING PHRASE '4003='!!MISSING PHRASE '8144='! !MISSING PHRASE '4001='!!MISSING PHRASE '4002='!!MISSING PHRASE '4003='!!MISSING PHRASE '8147='!!MISSING PHRASE ')'!!MISSING PHRASE 'IF:'!!MISSING PHRASE 'ITEM_DESC='!!MISSING PHRASE 'UNITS='!!MISSING PHRASE 'TEMPLATE='!!MISSING PHRASE 'LIFETIME='!!MISSING PHRASE 'UNIT_COST='!!MISSING PHRASE 'OBSOLETE='!!MISSING PHRASE 'NUM_DECIMALS='! !MISSING PHRASE '('!!MISSING PHRASE '1002='!!MISSING PHRASE '1003='!!MISSING PHRASE '1004='!!MISSING PHRASE '1005='!!MISSING PHRASE '1006='!!MISSING PHRASE '1001='!!MISSING PHRASE '8068='!!MISSING PHRASE ')'!

Should appear as:

An example of an empty processFilters string is shown below.

$$$PROCESS_ID=$$$$OPER_ID=$$$$ENTITY=$$$$PROCESS_LEVEL=$$$$PROCESS_STATUS=$$$$CREATOR=$$$$APPROVER=$$$$LASTEDITOR=$$$$CHECKEDOUTBY=$$

$$SHOW_STEPS=$$$$SHOW_SPECS=$$$$($$$$8001=$$$$8002=$$$$)$$$$ICF:$$$$ITEM_CLASS_DESC=$$$$CONSUMED=$$$$OBSOLETE=$$$$($$$$4003=$$$$8144=$$

$$4001=$$$$4002=$$$$4003=$$$$8147=$$$$)$$$$IF:$$$$ITEM_DESC=$$$$UNITS=$$$$TEMPLATE=$$$$LIFETIME=$$$$UNIT_COST=$$$$OBSOLETE=$$$$NUM_DECIMALS=$$

$$($$$$1002=$$$$1003=$$$$1004=$$$$1005=$$$$1006=$$$$1001=$$$$8068=$$$$)$$

As a second example, the following text:

item_id=!MISSING PHRASE ''!item_desc=!MISSING PHRASE ''!item_class_id=!MISSING PHRASE ''!item_class_desc=!MISSING PHRASE ''!lot_no=!MISSING PHRASE ''!grade_cd =!MISSING PHRASE ''!status_cd=!MISSING PHRASE ''!expiry_date=!MISSING PHRASE ''!wo_id=!MISSING PHRASE ''!oper_id=!MISSING PHRASE ''!seq_no=!MISSING PHRASE ''!serial_no=!MISSING PHRASE ''!serialized_items=$$

Should appear as:

item_id=$$$$item_desc=$$$$item_class_id=$$$$item_class_desc=$$$$lot_no=$$$$grade_cd

=$$$$status_cd=$$$$expiry_date=$$$$wo_id=$$$$oper_id=$$$$seq_no=$$$$serial_no=$$$$serialized_items=$$

As a third example, the following text:

The jobFilters filter parameter contains a series of filter types and filters. For all filterOption values except for 103, each filter type and filter is surrounded by ‘!MISSING PHRASE '’ in the string. A filter type precedes each set of filters corresponding to that type.

For example, for the job filters, the format would be:

'!1,2,3,4,5,6,7!MISSING PHRASE ''!CANCELLED=0!MISSING PHRASE ''!COMPLETED=0!MISSING PHRASE ''!WO_ID=!MISSING PHRASE ''!OPER_ID=!MISSING PHRASE ''!SEQ_NO=!MISSING PHRASE ''!ITEM_ID=!MISSING PHRASE ''!ITEM_DESC=!MISSING PHRASE ''!FIRST_JOB=0!MISSING PHRASE '

Should appear as:

The jobFilters filter parameter contains a series of filter types and filters. For all filterOption values except for 103, each filter type and filter is surrounded by ‘$$’ in the string. A filter type precedes each set of filters corresponding to that type.

For example, for the job filters, the format would be:

$$1,2,3,4,5,6,7$$$$CANCELLED=0$$$$COMPLETED=0$$$$WO_ID=$$$$OPER_ID=$$$$SEQ_NO=$$$$ITEM_ID=$$$$ITEM_DESC=$$$$FIRST_JOB=0$$

< top of document >

Wonderware MES 4.5 Documentation

The Wonderware MES 4.5 documentation set includes the following:

  • Object Help - Provides information about run-time behavior, configuration, and run-time attributes of UCO, OCO and SRO objects.
  • Operation Capability Object User's Guide - Provides information about installing, configuring, and using the Operations Capability Object.
  • ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation.
  • Sample Recording Object User's Guide - Provides information about installing, configuring, and using the Sample Recording Object to collect and store values for samples.
  • Utilization Capability Object User's Guide - Provides information about installing, configuring, and using the Utilization Capability Object to collect equipment performance data.
  • Wonderware MES .NET Controls Programmer's Guide - Provides information about integrating the Wonderware MES .NET controls into ArchestrA automation objects.
  • Wonderware MES Client Guide - Provides information about customizing and maintaining the plant floor information.
  • Wonderware MES Configurator User's Guide - Provides information about customizing and maintaining the Wonderware MES system.
  • Wonderware MES DataEditor - Provides information about inserting and modifying data in the Wonderware MES Database.
  • Wonderware MES Entity Model Builder User's Guide - Provides information about creating entities from the ArchestrA equipment model.
  • Wonderware MES Installation Guide - Provides information about installing Wonderware MES applications.
  • Wonderware MES Manager - Provides information about managing and viewing status tables and running reports on the data generated by the Wonderware MES system.
  • Wonderware MES Operator User's Guide - Provides information about executing processes at the plant floor.
  • Wonderware MES Report Designer - Provides information about creating and configuring custom reports.
  • Wonderware MES Reports in Wonderware Information Server - Provides information about viewing Wonderware MES reports with either the Reporting Services feature or the Table Weaver feature of Wonderware Information Server.
  • Wonderware MES Service Guide - Provides information about the MES Service utility which performs various tasks in the MES System.
  • Wonderware MES Stateful API Reference - Provides information about using Stateful API within the ArchestrA IDE to develop and customize ArchestrA scripts.
  • Wonderware MES Stateless API Reference - Provides information about using Stateless API within the ArchestrA IDE to develop and customize ArchestrA scripts.
  • Wonderware MES Supervisor User's Guide - Provides information about coordinating and overseeing the daily activity of the plant floor.
  • Wonderware MES Web Access User’s Guide - Provides information about using web access methods that allow MES Middleware calls to the MES database.
  • Wonderware PEM Migration Utility User's Guide - Provides information about migrating the existing PEM templates to the OCO template.

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

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

After installing Adobe Reader, double-click on 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 Wonderware MES 4.5 installation instructions are located in the root folder of the Wonderware MES 4.5 installation CD as an online Help file. You can view these instructions by clicking Help as you start the Wonderware MES 4.5 installation procedure.

< top of document >

© 2012 Invensys Systems, Inc. All Rights Reserved.