MESWeb Portal User Guide

Manufacturing Execution System (MES)
Web Portal
User Guide
Version 6.0
June, 2018
© 2018 AVEVA Group plc or its subsidiaries. All rights reserved.
The Schneider Electric industrial soft ware business and AVEVA have merged to trade as AVEVA Group
plc, a UK listed company. The Schneider Electric and Life is On trademarks are owned by Schneider
Electric and are being licensed to AVEVA by Schneider Electric.
No part of this documentation shall be reproduced, stored in a ret rieval system, or transmitted by any
means, electronic, mechanical, photocopying, rec ording, or otherwise, without the prior written
permission of AVEVA. No liability is assumed with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this documentation, AV EVA assumes no
responsibility for errors or omissions. The information in this documentation is subject to change without
notice and does not represent a commitment on the part of AVEVA. The soft ware described in this
documentation is furnished under a license agreement. This soft ware may be used or copied only in
accordance with the terms of such license agreement.
ArchestrA, Aquis, Avantis, DYNS IM, eDNA, EYESIM, InBatch, InduSoft, InStep, IntelaTrac, InTouch,
PIPEPHASE, PRiSM, PRO/II, PROV IS ION, ROMeo, SIM4ME, SimCentral, SimSci, Skelta,
SmartGlance, Spiral Software, Termis, WindowMaker, WindowViewer, and Wonderware are trademarks
of AVEVA and/or its subsidiaries. An extensive listing of AVEVA trademarks can be found at:
https://sw.aveva.com/legal. All other brands may be trademarks of their respective owners.
Publication date: 6/29/2018
Contact Information
AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 OHB. UK
https://sw.aveva.com/
For information on how to cont act sales, customer training, and technical support, see
https://sw.aveva.com/contact.
MES Web Portal User Guide
Contents
Chapter 1 Getting Started..................................................................................................... 9
Introduction .............................................................................................................................. 9
MES Web Portal Configuration............................................................................................. 9
MES Web Portal Operation .................................................................................................. 9
Installing the MES Web Portal .................................................................................................. 10
Accessing MES Web Portal ..................................................................................................... 10
Closing a MES Web Portal Web Session .................................................................................. 11
Web Browser Support ............................................................................................................. 11
Web Browsers Support ed .................................................................................................. 11
Setting the Web Browser's Preferred Language/Locale for Values and Dates ........................ 11
Requirements for Running Online Help Video Tutorials ........................................................ 12
Navigating in MES Web Portal ................................................................................................. 13
Navigating to the Home Page............................................................................................. 14
Navigating Back ................................................................................................................ 14
Working with Collection Pages ................................................................................................. 15
Filtering Entities on the Entities Collection Page .................................................................. 15
Filtering Work Orders ........................................................................................................ 16
Filtering Item Lists ................................................................................................................... 18
Working with Grids .................................................................................................................. 19
Sorting the Grid by a Column ............................................................................................. 19
Filtering the Grid by a Column ............................................................................................ 19
Filtering a Grid by the Last N Hours of Activity..................................................................... 20
Other Basic Operations ........................................................................................................... 21
Working with the Action Bar ............................................................................................... 21
Trunc ated Information........................................................................................................ 22
Implied Wildcard Characters and Case Sensitivity in Filter Boxes ......................................... 22
Required Entries ............................................................................................................... 23
Responding to Messages .................................................................................................. 23
Information Dat a Refresh ................................................................................................... 23
Chapter 2 MES Web Portal Concepts .............................................................................. 25

Conc epts Overview ................................................................................................................. 25
MES Web Portal User Aut hentication and Privileges ................................................................. 25
User Authentication ........................................................................................................... 25
Using OS Group vs. OS User Sec urity Mode ....................................................................... 25
OS Group Security and Multiple AD Domains ...................................................................... 26
Authentication Checks Performed When a User Logs In ...................................................... 26
Privilege and Access Settings ............................................................................................ 27
Example Roles and Privilege Settings................................................................................. 30
Entities ................................................................................................................................... 31
Version 6.0 3
MES Web Portal User Guide Contents
Entity Capabilities .............................................................................................................. 31

Items and Item Classes ........................................................................................................... 32
Line Management ................................................................................................................... 32
Lines ................................................................................................................................ 32
Parent Entity to a Line ....................................................................................................... 33
Line Layout ....................................................................................................................... 33
Serial and Parallel Entities ........................................................................................... 33
Line Segments ............................................................................................................ 34
Line Positions .............................................................................................................. 34
Entity and Line Guidelines ............................................................................................ 35
Production ........................................................................................................................ 35
Production Rates ......................................................................................................... 35
Line Properties Used to Determine Production Rates ..................................................... 35
Determining a Line’s Performance and Production Amounts ........................................... 36
Bottleneck Entities ....................................................................................................... 36
Determining Bottlenecks Manually or Automatically ....................................................... 36
Automatic Determination of Performance Rates and B ottleneck Entities.......................... 36
Conditions When an Entity’s Production Rate Cannot Be Determined ............................. 37
Determining Comparable Units and Production Rates .................................................... 37
Internal Tracking of Entity Production Rat es .................................................................. 38
Decimal Precision of Item Production Quantities ............................................................ 39
Work Orders and Jobs ....................................................................................................... 39
Work Orders ............................................................................................................... 39
Work Order Status ....................................................................................................... 39
Jobs ........................................................................................................................... 39
Job States................................................................................................................... 40
Work Order and Job Creation in MES Web Portal .......................................................... 40
Work Order Reassignment ........................................................................................... 41
Effects of Work Order Status Changes on Job States .................................................... 42
Line Layout Reconfiguration Guidelines .............................................................................. 43
Guidelines with Work Orders Creat ed from a Line .......................................................... 43
Guidelines with Work Orders Creat ed from a Process .................................................... 43
Line Layout Reconfiguration System Behavior .................................................................... 44
Understanding Batches and Lots for OEE ........................................................................... 44
Utilization ............................................................................................................................... 45
Utilization States ............................................................................................................... 45
Utilization Reasons............................................................................................................ 45
Utilization Reason Groups ................................................................................................. 46
Raw Reason Codes .......................................................................................................... 46
Utilization E vents............................................................................................................... 46
Standard, Minimum, and Maximum Utilization Reason Times ......................................... 46
Maximum Duration ...................................................................................................... 47
Splitting E vents ........................................................................................................... 47
Merging E vents ........................................................................................................... 47
OEE ....................................................................................................................................... 47
A vailability ........................................................................................................................ 48
Quality .............................................................................................................................. 48
Performance ..................................................................................................................... 49
Determining the Line’s OEE Target Values ......................................................................... 49
Chapter 3 MES Web Portal Configuration ....................................................................... 51

Configuration Overview ........................................................................................................... 51
4 Version 6.0
Contents MES Web Portal User Guide
Configuring Utilization States and Reas ons .............................................................................. 51

Configuring Utilization States ............................................................................................. 52
Utilization State Settings .............................................................................................. 53
Configuring Utilization Reason Groups ............................................................................... 54
Configuring Utilization Reasons .......................................................................................... 55
Utilization Reason Settings........................................................................................... 56
Configuring Entities ................................................................................................................. 58
Configuring Entity Basic Information and Capabilities .......................................................... 59
Adding Attributes to the Entity ............................................................................................ 61
Configuring Job Settings .................................................................................................... 62
Configuring Default Utilization Reasons for Standard E vents ................................................ 64
Specifying the Utilization Reasons That Can Be Used wit h an Entity ..................................... 65
Configuring OEE Default Data............................................................................................ 66
Deleting an E ntity .............................................................................................................. 67
Configuring Lines .................................................................................................................... 67
Creating a Line.................................................................................................................. 67
Line Configuration Settings .......................................................................................... 68
Entering a Standard Item (Line Configuration Setting) .................................................... 69
Editing a Line .............................................................................................................. 70
Deleting a Line ............................................................................................................ 70
Configuring a Line’s Lay out ................................................................................................ 70
Sample Line Layout ..................................................................................................... 71
Inserting the Initial Entity .............................................................................................. 72
Inserting an Entity at the Start of a Line ......................................................................... 73
Adding Serial Entities ................................................................................................... 74
Inserting an Entity at the End of a Line .......................................................................... 74
Adding Parallel Entities ................................................................................................ 75
Creating a Segment ..................................................................................................... 76
Moving an Entity in the Layout ...................................................................................... 78
Removing an Entity from a Line .................................................................................... 78
Designating an Entity as the Production Sourc e .................................................................. 78
Manually Designating the Bottleneck Entity ......................................................................... 79
Configuring the Aut omatic Determination of Bottleneck Entities ............................................ 80
Specifying Required Line Configuration Settings............................................................ 80
Making Sure That an Entity Is Not Manually Designated as the Bottleneck ...................... 80
Specifying That the Line’s Entities Can Pot entially Be a Bottleneck ................................. 80
Assigning the Required Capabilities to the Entities in the Line ........................................ 81
Specifying Required Entity OEE Configuration Settings .................................................. 81
Enabling the Entity When in a Running State ................................................................. 81
Assigning Line Access to Users ......................................................................................... 81
Chapter 4 MES Web Portal Operations ........................................................................... 83

Operations Overview............................................................................................................... 83
What Operations Can Be Performed ........................................................................................ 83
Viewing Line Summary Information .......................................................................................... 84
Note Icon in Line Summary Information .............................................................................. 84
Working with Work Orders ....................................................................................................... 85
Creating a Work Order....................................................................................................... 85
Changing a Work Order's Status ........................................................................................ 86
Reassigning a Work Order to Anot her Line ......................................................................... 88
Deleting a Work Order ....................................................................................................... 89
Version 6.0 5
MES Web Portal User Guide Contents
Viewing a Line's Work Order Status ......................................................................................... 89

Viewing Det ailed Job Information ....................................................................................... 91
Production History Grid Column Descriptions ...................................................................... 92
Navigating to the Assigned Line Det ails .............................................................................. 92
Viewing the Status of a Line's Entities ...................................................................................... 92
Entity Tile Functions .......................................................................................................... 93
Viewing Entity Summary Information .................................................................................. 94
Viewing Jobs in an Entity Work Queue ............................................................................... 94
Viewing Bottleneck Information .......................................................................................... 97
Entering Production Quantity for a Running Job ........................................................................ 97
Add Production Quantity Settings ....................................................................................... 98
Reducing Production Quantity .......................................................................................... 100
Starting and Ending Jobs ....................................................................................................... 100
Marking a Job as Complete ................................................................................................... 101
Working with an Entity's Utilization E vents .............................................................................. 102
Viewing an Entity’s Event History ..................................................................................... 102
Entity Current E vent Status .............................................................................................. 102
E vent History Grid Column Descriptions ........................................................................... 103
Adding an E vent .............................................................................................................. 104
Editing an E vent .............................................................................................................. 104
Splitting an E vent ...................................................................................................... 106
Merging an E vent with an Adjacent E vent ................................................................... 108
Monitoring Entity OEE ........................................................................................................... 108
Navigating to an Entity’s Monitor Tab ................................................................................ 109
Scrolling Through Data on the Entity Monitor Tab .............................................................. 109
Setting the Reporting Period ............................................................................................ 109
Viewing Currently Running Jobs ....................................................................................... 110
Viewing Uilization State Information .................................................................................. 111
Viewing KPI Gauges........................................................................................................ 112
Monitoring Line OEE ............................................................................................................. 113
Scrolling Through Data on the Line Monitor Tab ................................................................ 114
Setting the Reporting Period ............................................................................................ 114
Viewing Summary Information for the Period..................................................................... 114
Viewing Work Order Information....................................................................................... 115
Viewing Utilization Counts and Durations .......................................................................... 116
Viewing KPI Measures..................................................................................................... 116
Viewing Item Production for the Period ............................................................................. 117
Appendix A Advanced Concepts ..................................................................................... 119

Determining Comparable Units and Production Rates: Examples ............................................. 119
Line Monitoring and OEE Calculations.................................................................................... 124
Line Structure ................................................................................................................. 125
Entity Properties .............................................................................................................. 125
OEE Use and Bottlenecks................................................................................................ 126
Production Data .............................................................................................................. 126
OEE Calculations ............................................................................................................ 127
Appendix B MES Web Portal URLs ................................................................................ 129

Page URLs ........................................................................................................................... 129
Embedded Controls URLs ..................................................................................................... 130
6 Version 6.0
Contents MES Web Portal User Guide
Index ....................................................................................................................................... 131
Version 6.0 7
C HAPTER 1
Getting Started
In This Chapter
Introduction .................................................................................................................................... 9
Installing the MES Web Portal ....................................................................................................... 10
Accessing MES Web Portal ........................................................................................................... 10
Closing a MES Web Portal Web Session ........................................................................................ 11
Web Browser Support ................................................................................................................... 11
Navigating in MES Web Portal ....................................................................................................... 13
Working with Collection Pages ....................................................................................................... 15
Filtering Item Lists......................................................................................................................... 18
Working with Grids ........................................................................................................................ 19
Other Basic Operations ................................................................................................................. 21
Introduction
The Manufacturing Execution System (MES) Web Portal is a web-based application that provides a user
interface to configure and monitor your plant model and production processes.
MES Web Portal Configuration

The MES Web Portal gives you the ability to configure production lines, work orders, entities, and
utilization states and reasons.
Other configuration tasks can be performed using the MES Client application, which gives you the abi lity
to configure items, operations, processes, specifications, certifications, work orders, jobs, operations
data collection, and quality data collection.
The information configured in MES Web Portal and MES Client is used to convey information to
operators: What do I work on next? How much do I make? It is also used to collect your plant process
information from operators and production equipment on the plant floor. The information collected and
stored from your production processes gives you the informat ion needed to control and improve the
overall operation management and performance of the plant.
MES Web Portal Operation

MES Web Portal is used on the production or shop floor to:
 Monitor the status of a line’s work orders, jobs, and entities
 Change the status of a work order
 Reassign a work order to another line
 Start and stop jobs
 Add or reduce production for a job
 Manage entity events
 Mark a job as complete
Version 6.0 9
MES Web Portal User Guide Getting Started
Other operation tasks can be performed using the MES Operator or through MES application objects by
directly linking MES with shop floor PLCs. Thos e tasks include entering dat a into the system using steps
and specifications, and capturing machine utilization and labor data.
Installing the MES Web Portal

If the MES Web Portal component is selected during the MES installation, the soft ware that supports
MES Web Port al is installed. A fter the installation, the MES Web Port al Configurat or utility must be run to
install the MES Web Portal in Internet Information Services (IIS).
For more information about installing MES Web Portal, see the MES Installation Guide or online help.
Accessing MES Web Portal

You can access the MES Web Portal from a web browser that is running on any machine that has
network access to the MES Web Portal host.
If running HTTP web communications, the default URL is:
http://<serverhostname>/MES/
If running HTTPS web communications for MES Web Portal and you are able to obtain the proper
HTTPS certificat e, the default URL is:
https://<serverhostname>/MES/
Where <serverhostname> is the IP host name of the mac hine on which the MES Web Portal host is
running. However, see your system administrator for the specific URL that is used for your installation of
MES Web Portal.
If you are using the Firefox web browser, you will be prompt ed to ent er your Windows Active Directory
(AD) user account name and password after entering the MES Web Portal URL in your browser. If you
are using the Chrome or Internet Explorer web browser, you will be automatically logged in aft er entering
the MES Web Portal URL.
Note: Organizations determine their own Windows and web application auto -login policies. If you are
experiencing problems with MES Web Portal aut o-login, please contact your IT department.
Once logged in, the MES Web Portal home page appears.
Your access to pages and functions in MES Web Portal depends on the privileges and line and entity
access that have been specified for y ou. For more information about user privileges and access settings,
see the MES Client User Guide or help.
Language Used
The language used in the MES Web Portal brows er session for the text is determined by which MES
Security Mode is being used (as configured in MES Client):
 If OS Group mode is used, the MES system param eter Default language setting is used.
 If OS User mode is used, the Language setting for your MES user account is used.
The display of localized values and dat es is determined by the web browser's language/locale settings.
See Setting the Web Brows er's Preferred Language/Locale for Values and Dates on page 11.
If Privilege and Access Settings Are Changed During a Session
If your privilege or access settings are changed during an MES W eb Portal session, you might see an
insufficient privileges message when you attempt to navigate to or use a function to which you no longer
have privileges or access. Press the F5 key to refresh the browser; the refreshed MES Web Portal
environment will reflect your new privilege and access settings.
10 Version 6.0
Getting Started MES Web Portal User Guide
Note that your privilege settings are cached, and the cache is automatically refreshed every 2 seconds
by default. This refresh rate can be customized for your MES Web Portal host; for modifying the refresh
rate, see the chapter "Configuring the MES Web Port al Host" in the MES Installation Guide or online
help.
Closing a MES Web Portal Web Session

Close the web browser window or tab in which the session is running.
Web Browser Support

The following topics provide information for optimizing MES Web Portal in the supported web browsers.
Web Browsers Supported

The following web browsers are supported for use wit h MES Web Portal. Support was validated for the
web browser versions that were available at the time of the curre nt MES version release or, for Edge,
using the version shown.
 Chrome
 Edge version 38
 Firefox
 Internet Explorer 10, 10 Native, and 11
Note: When running MES Web Portal in some previous releases of Int ernet 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.
Setting the Web Browser's Preferred Language/Locale for Values and

Dates
You can set your web browser's language setting to your preferred language/locale to use in the browser
for values and dates.
The language for the text in the browser is set by your MES us er group or user account language s etting.
To set the preferred language for Chrome
1. Open the Settings page (how to do this varies, depending on the version of Chrome you are using).
2. Click the Show advanced settings link.
3. In the Language s section, click the Language and input settings button.
The Languages dialog box appears.
4. Click Add.
The Add language dialog box appears.
5. In the Language list, select your preferred language, then click OK.
The language is added to the list in the Add language dialog box.
6. Click and drag the preferred language to the top of the list.
7. Click Done to save your changes.
Your preferred language will now be used in the browser.
Version 6.0 11
To set the preferred language for Firefox

1. Open the Options dialog box (how to do this varies, depending on the version of Firefox you are
using).
2. In the Content tab, click the Languages Choose button.
The Languages dialog box appears.
3. In the Select a language to add list, select your preferred language, then click Add.
The language is added to the list.
4. Select the language and click the Move Up button to move the preferred language to the top of the
list.
5. Click OK to save your changes and close the dialog boxes.
To set the preferred language for Internet Explorer
1. On the Tool s menu, click Internet Options.
The Internet Options dialog box appears.
2. Click the Languages button.
The Language Preference dialog box appears.
3. Click the Add button.
The Add Language dialog box appears.
4. Select the preferred language, then click OK.
The language is listed in the Language Preference dialog box.
5. Select the language and click the Move Up button to move the preferred language to the top of the
list.
6. Click OK to save your changes and close the dialog boxes.
Requirements for Running Online Help Video Tutorials

Browsers Supported
The following browsers support running the video tutorials that are included in the online help:
 Chrome, all versions supported by MES Web Portal
 Internet Explorer, all versions supported by MES Web Portal except 9
 Firefox, all versions support ed by MES Web Portal, with the following requirement: To run video
tutorials in Firefox, you must have an MP4 -capable video player such as Windows Media Play er
installed on both the server and client machines, and have a third-party MP4 plug-in installed in
Firefox.
Running MES Web Portal Locally in Windows 2012 or Windows 2012 R2
If you are running an MES Web Portal session using Internet Explorer locally on the same machine on
which the MES Web Portal service is running, and that machine is running Windows Server 2012 or
Windows Server 2012 R2, then you will need to enable the Windows Desktop Experienc e feature to play
the video tutorials in the online help.
1. Open Server Manager.
12 Version 6.0
2. Go to Local Server.
3. On the Manage menu, click Add Roles and Features.
4. In the Add Roles and Features wizard, click Features in the navigation list.
5. In the Feature s list, select the Desktop Experience option.
6. Save your selection.
Navigating in MES Web Portal

A session in MES Web Portal starts on the home page, shown below.
The home page includes a tile for each area of the application:
 Lines
 Entities
 Utilization
 Work orders
Click one of these tiles to navigate to that area.
Version 6.0 13
You can also navigate to these areas from any page in MES Web Portal using the Navigation menu. To
open the menu, click the Navigation menu icon at the upper left.
The Navigation menu appears.
Full navigation instructions are provided in the applicable procedures under MES Web Portal
Configuration on page 51 and MES Web Portal Operations on page 83.
Note: If you click a navigation menu command and receive a message saying that you do not have
sufficient privileges to view that function, your user privileges might have been changed during your
session. To refresh the browser and see to which navigation menu commands you now have access,
press F5.
Navigating to the Home Page

Perform one of the following actions:
 Click the product name on the banner that appears at the top of every page.
 Click the Navigation menu icon at the upper left of any page, then click Home.
Navigating Back
To navigate back to a previous web page in your session, use the web browser's Back button.
14 Version 6.0
Working with Collection Pages

You can interact with objects such as lines, work orders, and entities on collection pages. The objects are
represented by tiles.
You can also filter objects on the Entities and Work Orders collection pages to view only those of interest
to you. See Filtering Entities on the Entities Collection Page on page 15 and Filtering Work Orders on
page 16.
Filtering Entities on the Entities Collection Page

By default, the Entities c ollection page lists all entities in t he system. The entities can be filtered by entity
name or description.
1. In the filter box above the right side of the grid, enter text that matches any portion of the entity
names or descriptions by which you want to filter the list. The filter menu appears.
2. Click Name or Description to specify by which criteria to filter the list. The entity list is filtered
according to your selection.
The filter for the page is saved. It will persist during your session until you change or clear the filter
parameters. The Search icon that appears on the left below the object list indicates that a filter is
active (see the example below).
Version 6.0 15
Note: If the web browser’s "Delete Browsing History on Exit" configuration option is not selected, the
entity filter will be preserved the next time you open a Web Portal browser session.
To clear the filter
 Click the Clear Filter icon.
Filtering Work Orders

By default, the Work Orders collection page lists all work orders in the system that are not in a
Completed state, up to a maximum of 500. Also, a line's Work Order tab lists all work orders assigned to
that line, up to a maximum of 100. The work orders on both these pages can be filtered by work order ID,
item being produced, and status.
If there are more than the maximum number of work orders to be listed, a message on the page or in the
filter dialog box will indic ate this condition. In this case, the most recently created work orders are
retrieved, and they are listed by work order ID. To see other work orders that are not listed, you must
enter or refine the filter criteria.
1. Click the Filter icon at the upper right corner of the page.
The Filter dialog box appears. By default, all work order statuses except Complete are selected.
2. Refine the filter criteria by work order ID, item ID, work order status, and/or line.
For the work order or item ID, enter text that matches any portion of the IDs by which you want to
filter the list.
In the Line list:
o All specifies all work orders, regardless of whether they have been assigned to a line or not.
o Not Defined specifies only those work orders that have not been assigned to a line.
3. Click Apply to leave the Filter dialog box open, or click Close to close the dialog box.
16 Version 6.0
The work order list is filtered and the filter for the page is saved.
The filter will persist during your session until you change or clear the filter parameters. The Search icon
that appears on the left below the object list indicates that a filter is active (see the example below). The
active filter's parameters appear below the Search icon.
Note: If the web browser’s Delete Browsing Hi story on Exit configuration option is not selected, the
work order filter will be preserved the next time you open a Web Portal browser ses sion.
To reset the filter to the default settings
 Click Default in the dialog box or click the Default icon at the upper right corner of the work
order list.
Version 6.0 17
Filtering Item Lists

When assigning items to objects in MES, such as the standard item for a line or entity, you select the item
from a list. To help you find an item to select from a long list, a filter is included, such as the one shown in
the following item selection dialog box.
By default, the list includes all items in the system, up to a maximum of 100. If there are more than 1 00
items to be listed, only the first 100 items sorted alphabetically are listed. A message on the page or in
the filter dialog box will indicate this condition. The item identifier by whic h the items are sorted and
selected for inclusion in the list is the identifier specified by the Item display system parameter (which is
set in MES Client): a combination of the item ID and/or the item description.
To help you identify an item in a long list or to see other items that are not listed, you must enter or re fine
the filter criteria.
To enter or refine the filter criteria and select an item
1. Enter the filter criteria using the Item ID box, Item Description box, and Item Class list.
2. Click the Filter icon to the right of the Item Class list.
The items that match the filter c riteria are listed, and the Filter icon changes to an X clear filter
icon.
3. Select the item and click OK.
Note that the unique filter for each of the item lists in the system persists for your session.
To clear the filter
 Click the X clear filter icon to the right of the Item Class list.
18 Version 6.0
Working with Grids

MES Web Portal includes grids of information, such as the Jobs grid shown below.
You can sort and filter information in the grid based on different columns.
Sorting the Grid by a Column

Click the column heading. The sort icon appears next to the heading label.
Clicking the heading cycles through:

 Ascending order
 Descending order
 Sorting on this column is off
Sorting is supported for one column at a time.
Filtering the Grid by a Column

In the column heading cell, click the Filter icon. The filter panel appears.
There are filter variations for text columns:
Version 6.0 19
Date/time columns:
And true/ false (c heck box) columns:
For text and date/time columns, you can enter up to two filter criteria for the data in the column.
For a text or date/time column
1. Select a condition from one or both of the lists to configure the search. By default, the I s equal to
option is selected.
2. If you are using two filter criteria:
 Select And to filter on results that fulfill both search conditions.
 Select Or to filter on results that fulfill either of the search conditions.
3. Enter the search criteria in the filter boxes.
 If only using one filter criterion, leave the second filter box blank.
4. Click Filter.
Only the entries whose data in the column on which you are filtering match the filter criteria are
included in the grid.
For a true/false column
1. Select the is true or is false option.
2. Click Filter.
Only the entries that match the true (check box selected) or false (check box cleared) condition on
which you are filtering are included in the grid.
Filtering a Grid by the Last N Hours of Activity

By default, entries that occurred in the previous 8 hours are shown in certain grids, such as the Event
Hi story and Production Hi story grids, regardless of the shift. You can change this setting to filter
events from the last 1 to 24 hours.
To change the number of previous hours by which the grid is being filtered
20 Version 6.0
1. In the La st N Hours box above the right side of the grid, enter the number of previous hours on
which to filter the list.
2. Click the Apply Filter icon or button.

This filter will not affect the actual Start Time and Duration of events in the grids so that you can see the
actual data.
Other Basic Operations

The following topics describe ot her basic Web Portal operations.
Working with the Action Bar

Many of the MES Web Portal pages have an action bar that includes command icons.
Click an icon in the action bar to initiate the selected action.

The icons that are available on the action bar will change to indicate what options are available based on
the currently selected object or action being performed.
For example, when a job is running on an entity, the End Job, Add Production, and Reduce
Production icons appear, as shown above.
Version 6.0 21
Truncated Information
If the name of a tile or an entry in a grid is too large to fit, ellipses (...) indicate that it is truncated. To see
the full name in a tile, hover the cursor over it, as shown below. In a grid, widen the column.
If summary information at the top of the page is too large to fit, a chevron appears to indicate that it is
truncated, as shown below. To see the hidden information, click the chevron.
Implied Wildcard Characters and Case Sensitivity in Filter Boxes

Wildcard Characters
Filters are included on several pages and dialog boxes in MES Web P ortal, for example, the Work Order
and Enti ties collection pages and S tandard Item dialog boxes. The filter entry boxes have implied
wildcard characters plac ed before and after your text entry. This causes the list to be filtered by any list
entries that contain your text entry.
For example, if you enter pec, the following list entries would match:
 Feeder - Pec ans

 Pallet - Pecans
 Scale - Pecans
All of the filter boxes, except the Available Entities filter box on the line configuration Layout tab, allow
you to specify a range of characters using square brackets. [a-z] indicates a single alphabetic character,
and [0-9] indicates a single numeric character.
For example, if you enter pallet[0-9], the following list entries would match:
 Pallet1
 Pallet80
However, the following list entries would not match:
 T101- Pallet
 Pallet-100
Case Sensitivity
Text entries in filter boxes are case insensitive, except the Available Entities filter box on the line
configuration Layout tab, which is case sensitive.
22 Version 6.0
Required Entries
Boxes and options that require ent ries are indicated by an asterisk (*) following the box’s or option’s
label.
Responding to Messages
If the system detects a problem as a result of an action you performed, a message bar appears across
the current page. The message can be an error, warning, or informational message.
The message should provide information about the problem and how to correct it. You will not be able to
perform any other task in Web Portal until you acknowledge the message by clicking Close.
Information Data Refresh

By default, information data, such as data displayed in status grids, is refreshed automatically every 60
seconds.
Note the following additional refresh behavior:
 After a refres h, the grid is reset to the first item in the grid.
 The timer for the refresh is reset when scrolling through the grid.
 The automatic refresh is disabled when modifying a record in a grid.
To toggle the Auto Refre sh behavior off and on for those pages that support it
 In the User menu, click Auto Refre sh.
Version 6.0 23
C HAPTER 2
MES Web Portal Concepts
In This Chapter
Conc epts Overview....................................................................................................................... 25
MES Web Portal User Aut hentication and Privileges ....................................................................... 25
Entities......................................................................................................................................... 31
Items and Item Classes ................................................................................................................. 32
Line Management ......................................................................................................................... 32
Utilization ..................................................................................................................................... 45
OEE............................................................................................................................................. 47
Concepts Overview
To use MES Web Portal effectively, it is important to understand basic concepts.
It is recommended that you read through the explanation of these concepts before attempting to
configure or use MES Web Portal.
MES Web Portal User Authentication and Privileges

The following topics include conceptual and configuration information specific to MES Web Portal user
authentication and privileges for MES Web Portal functionality.
User Authentication
The default Security Mode for MES installations is Native mode. However, MES Web Portal requires the
use of your system’s Windows Active Directory (AD) user groups or us er accounts for logging in.
Therefore, to support MES Web Portal users, the Security Mode must be changed to either OS Group or
OS User. Also, AD user groups or users must be added to the MES database using MES Client,
depending on the security mode.
Using OS Group vs. OS User Security Mode

Refer to the following descriptions to help you determine which Security Mode—OS Group or OS
User—to use for MES Web Portal user authentication in your system environment:
 In OS Group mode, the AD groups to which a user belongs are checked and the user’s AD user
account is checked to verify their authentication to log in to an MES Web Portal session. If the user
belongs to an AD group that has also been configured as an OS group in the MES database, then
the user is allowed to open a session. If an MES user account does not already exist for that user,
then one is automatically created. For information about adding AD user groups as OS groups in the
MES databas e, see the MES Client Us er Guide or online help.
 In OS User mode, the user’s AD user account is checked to verify their authentication to log in to an
MES Web Portal session. If the user’s AD user account has also been configured as an OS us er in
the MES dat abase, then the user is allowed to open a session. For information about adding AD user
accounts as OS users in the MES database, see the MES Client User Guide or online help.
Version 6.0 25
MES Web Portal User Guide MES Web Portal Concepts
Note: If you change the security mode, you have to restart the MES Web Portal service in Internet
Information Services (IIS).
OS Group Security and Multiple AD Domains

If your network is configured with multiple Windows AD domains, and you intend to use OS Group
security with MES Web Portal, you must select only Global and Univers al domain groups when
configuring MES groups. This is because MES Web Portal will not authenticate users in local groups if
the system is part of multiple domains.
As an example, say your network has multiple domains and you pick a local domain group to be an MES
group. You configure that group to have access to an entity, to run Operator, and to not allow editing of
entity settings. A user who belongs to that local domain group (and does not belong to any other groups
configured to be an MES group) would be able to log into the entity in MES Operator and perform
operations on that entity. However, the same user would not see the entity in MES Web Portal because
MES Web Portal will not authenticate the user from that domain local group.
You should only select local domain groups if you are sure that your network has only one domain.
Cons ult your net work administrator if you are unsure about whet her your network has multiple dom ains
or if you are unsure about whether a domain group is local, global, or universal.
Authentication Checks Performed When a User Logs In

The following conditions are checked when a user attempts to log in to MES Web Portal:
1. The user’s AD username and password are checked by the web browser.
2. The MES Security Mode must be either OS Group or OS User. If it is MES Native mode, the login will
fail.
3. The user’s AD user group or user account, depending on whether the MES Security Mode is set to
OS Group or OS User, must be mapped t o an MES user group or user account in the MES database.
One or more of the user’s AD user groups can be mapped to MES groups.
4. If OS User mode is being used, the user’s AD user account must map to an MES user account in the
MES databas e.
If OS Group mode is being used and the AD user group maps to at least one MES user group, an
MES user account for the user is automatically added to the MES database.
5. The MES user account must be active. (MES Client includes an Inactive check box option to allow a
user account to be made inactive.)
6. The user has to be a member of at least one MES user group that has at least one privilege setting
assigned to it.
o If no privileges are assigned to any of the MES user groups to which the user belongs, a
message indicating insufficient privileges to use the application appears. The only available
tasks that the user can perform are accessing the online help and logging out.
o If at least one privilege for one of the MES user groups to which the user belongs is set, then
even if that privilege is not related to MES Web Portal functionality, the user will be able to
access the MES Web Portal application. However, only the Work Orders tile will be shown in the
home page and only the Work Order option will appear in the navigation menu.
7. MES licensing is checked. If the appropriate licensing is not available, a licensing message appears
and the user will not have access to the application.
8. Once logged in, the user will see the MES Web Portal pages and functionality as defined by their
MES user groups’ privilege and access settings.
26 Version 6.0
MES Web Portal Concepts MES Web Portal User Guide
Privilege and Access Settings

MES Web Portal uses MES user groups to check for user privileges to perform tasks or view information
and to allow user access to lines and entities. Except for line access, which is set in MES Web Portal, all
MES user group privilege and access settings are set in MES Client.
 Privilege settings allow configuration and operation tasks to be performed, such as creating lines,
entities, utilization states, and utilization reason groups and reasons; assigning work orders to lines;
and changing work order status. These tasks are controlled through the privileges assigned to MES
user groups.
 Access settings allow operation tasks to be performed on a line or entity. This includes viewing and
performing operation tasks related to work orders and jobs, entities, and utilization events. These
tasks are controlled by assigning line or entity access to MES user groups.
A user will inherit all privileges and access that are permitted inclusively in all MES user groups of which
they are a member. So, if a user is a membe r of more than one MES user group and any of those MES
user groups has a particular privilege (for example, May edit lines), the user will have that privilege even
if other user groups of which they are a member do not have that privilege.
The following table describes the privilege and access settings that are available.
Setting Setting Type Where Specified Allows Users to:
May edit lines Configuration MES Client, Create, configure, modify,

in the MES user and delete any lines,
group’s Privileges tab, regardless of line access
Configurator group. settings.
If this privilege is not
assigned, the us er will see
only those lines to which
they have line access. And
for those lines, the user will
not see the line
Configuration tab or
subtabs.
If this privilege is assigned
but the user has not been
assigned access to a line,
the user can configure the
line but will not see the line’s
Work Orders or Entities
tabs. So the user will not be
able to view the line or its
entities and work orders.
Version 6.0 27
Line access Operation MES Web Portal, View lines, including their
in the line’s work orders and entities.
Configuration tab,
Line access is assigned
Line Access subtab.
individually for each line.
If access to a particular line
is not assigned, the user will
be able to see work orders
on the Work Orders
collection page, even if
those work orders are
assigned to that line.
However, any links in MES
Web Portal to that line’s
pages will be disabled.
If a user cannot edit lines
and has not been assigned
access to any lines, they will
not see the Lines tile on the
home page or the Lines
option in the navigation
menu.
May edit entity Configuration MES Client, Create, configure, modify,
settings in the MES user and delete any entities,
group’s Privileges tab, regardless of the us er’s line
Configurator group. access setting for the line to
which an entity is assigned.
If this privilege is not
assigned, the us er will see
only those entities to which
they have been assigned
access. And for those
entities, the user will not see
the entity Configuration
tab or subtabs.
28 Version 6.0
Entity access Operation MES Client, The user will be able to see
in the MES user and perform operation tasks
group’s Entity Acce ss for only those entities that
tab. have been assigned to the
MES user groups of which
the user is a member.
If a user cannot edit entities
and has not been assigned
access to any entities, they
will not see the Enti ties tile
on the home page or the
Enti ties option in the
navigation menu. On the
line Entitie s page, they will
see the entity tiles and
bottleneck information, but
the entity tiles will not
include operation-related
icons.
One exception is that, even
if the user does not have
access to an entity, if that
entity has the Can Store
capability selected, the user
can select that entity in the
To Storage Location list in
the Add Production and
Reduce Production dialog
boxes.
May assign a Operation MES Client, Assign a work order to any
work order to a in the MES user line, regardless of t he user’s
line group’s Privileges tab, line access authorization.
Supervisor group.
If a user cannot assign work
orders to a line, then they
cannot create work orders,
because the line
assignment is required for a
new work order. The user
can edit an existing work
order, but regarding the line
assignment, the user can
only reassign the work order
to no line.
Version 6.0 29
May change Operation MES Client, Change the status of a work

work order state in the MES user order, regardless of the
group’s Privileges tab, user’s line access
Operator group. authorization for the line to
which the work order is
assigned.
If a user cannot change the
status of work orders, then
they cannot create work
orders, because the status
assignment is required for a
new work order. The user
can edit an existing work
order, but cannot change its
status.
May edit Configuration MES Client, Create, configure, modify,
utilization states in the MES user and delete utilization states.
group’s Privileges tab, This privilege applies to
Configurator group. MES Web Portal only.
May edit Configuration MES Client, Create, configure, modify,
utilization in the MES user and delete utilization reason
reasons or group’s Privileges tab, groups and reasons. This
groups Configurator group. privilege applies to MES
Web Portal only.
Typically, the two utilization
edit authorizations are
either both set or not set for
a user group.
If a user has neither of the
two utilization edit
authorizations, they will not
see the Utilization tile on
the home page or the
Utilization option in the
navigation menu. However,
if they have entity access,
they will be able to assign
utilization reasons to events
for those entities.
Example Roles and Privilege Settings

The table below shows suggested privilege settings for the following example MES Web Portal user
roles:
 An Application Engineer who is configuring the system but does not require access to operations
related to lines, work orders, entities, and entity events.
 An Operations Supervisor who needs requires access to all lines, work orders, and entities but no
access to configuration tasks.
 An Operator who requires access to specific lines and entities.
30 Version 6.0
Application Operations
Setting Engineer Supervisor Operator
May edit lines Yes No No

Line access No Yes, to all lines Yes, but only to lines
on which they will
perform tasks
May edit entity Yes No No
settings
Entity access No Yes, to all entities Yes, but only to those
entities on which they
will perform tasks
May assign a work No Yes Optional, depending
order to a line on whether operators
for your site are
allowed to start work
orders
May change work No Yes Optional, depending
order state on whether operators
for your site are
allowed to change
work order status
May edit utilization Yes No No
states
May edit utilization Yes No No
reasons or groups
Entities
Entities are physical assets in the plant whose activity will be tracked by MES and on which information
will be reported.
Entities can be:
 An entire plant
 An area of the plant, such as a production floor or a warehouse
 An organizational group of machines, such as those in a department
 A piece of equipment
 A module that makes up a piec e of equipment
For information about adding and configuring entities, see Configuring Entities on page 58.
Entity Capabilities
Within MES, entities can be assigned one or more capabilities. These capabilities define what activity
can occur at the entity and thus what data will be captured and included in reports. Thes e capabilities
include:
 Scheduling and running jobs
 Having its own shift schedule
Version 6.0 31
 Capt uring machine utilization

 Capt uring labor information
 Tracking OEE (overall equipment effectiveness)
 Receiving, storing, or shipping production items
 Logging data
 Copying folders of program files, documentation, and other files regarding an item’s production
relative to the entity
 Capt uring quality data
Note: With MES 2017, MES Web Portal can be used to configure entity utilization and OEE data capture
only. To configure Operational and Quality data capture, use MES Client.
Items and Item Classes

An item is the basic unit produced or consumed during production. Items can be referred to as a part,
component, piece, and so on in different manufacturing environments.
An item class is a logical grouping of items that share common characteristics, such as physical
properties and whet her they are produced, consumed, or bot h.
Items and item classes are created in MES Client.
It is helpful to understand how item entries are formatted in MES Web Portal:
 The item ent ry format consists of the item class designation followed by a backslash and then the
item designation when both the item class and item designation are displayed on a single line.
 The item class designation is the item class ID and/or item class description, as specified by the Item
class display System parameter.
 The item designation is the item ID and/or item class description, as specified by the Item display
system parameter.
For more information about setting the Item class display and Item display system parameters, see the
MES Client User Guide or online help.
Line Management
Most manufacturers have the concept of a line, whet her it is called a production line, manufacturing line,
or assembly line. On a line, raw materials are converted to finished goods through various process steps
to produce a final product.
Lines can be very simple, such as a linear series of machines and work areas that enhance the value of
the product in an ordered manner with the previous step being completed before the next step can begin.
Other lines can be more complex, with parallel equipment or even parallel segments of multiple piec es of
equipment to increase throughput.
In MES, each entity of a line has a production rate based on the item being processed. As a whole, the
line production rate is limited by the slowest entity or parallel entity segment, referred to as the
bottleneck.
The following topics explain the main concepts of the MES implementation of line management.
Lines
In MES Web Portal, a line is an ordered set of entities that models a production line, manufacturing line,
or assembly line. A line is ordered in the sense that each ent ity in the line is related to at least one ot her
entity in the line in a directed way that indicates the flow of product.
32 Version 6.0
All of the entities in the line must have the following conditions:
 Ability to schedule jobs, run jobs, capture utilization, and trac k OEE (overall equipment
effectiveness)
 Not be allowed to have more than one Job Exec (that is, it cannot have more than one job running at
a time)
 Have an OEE production rate defined
 Not be a member of another line
 Not be the parent entity of the line
The following diagram is a model for an example line that produces bags of mixed nuts.
For information about creating and configuring lines in MES Web Portal, see Configuring Lines on page
67.
Parent Entity to a Line

A line is not an entity itself. It is assigned to a parent entity, from which it inherits its shift schedule. The
parent entity to a line is typically a location, such as a plant site, or an organization. Such an entity can be
the parent entity to more than one line.
Entities that serve as the parent entities to lines can schedule shifts. The entities in the line can inherit
their shifts from the line’s parent entity.
Line Layout
Your physical line can be modeled using the line layout tools available in MES Web Portal. See
Configuring a Line’s Layout on page 70.
When configuring a line lay out, it is important to understand several layout -relat ed concepts:
 Serial and parallel entities
 Line segments
 Line positions
There are also some important guidelines about entities and lines that you should be aware of, explained
in the topics that follow.
Serial and Parallel Entities

A line consists of a combination of serial and, optionally, parallel entities.
Version 6.0 33
Parallel entities refer to a set of two or more entities that are at the same position in a production line.
Each parallel entity can receive material from the same set of entities immediately before it in the
production line or line segment, and can send mat erial to the same set of entities immediately after it in
the production line or line segment.
Serial entities do not have any other entities at the same position in the production line or line segment.
Line Segments
A line segment is a subset of the entities in a line that acts as a line unto itself.
Line segments can consist of a combination of serial and parallel entities.
Line segments that are parallel with each other must contain the same number of entities. The
corresponding entities in the parallel segments use the same line positions.
Line Positions
Parallel entities or entities that are at the same position in parallel line segments are said to be at the
same line position within the line. Which entities are at a particular line position is considered when
determining the line’s production rat e and bottleneck entity. For example, if an entity is designated as the
bottleneck, all entities at the same line position are considered bottleneck entities.
34 Version 6.0
The following diagram indicates the line positions for an example line.
Entity and Line Guidelines

 An entity can be the parent entity of more than one line.
 An entity can be placed in a given line only once, not at multiple positions.
 The same entity cannot be both a member of a line and a parent of a line.
 An entity cannot be the member of more than one line.
Production
To understand how a line's production rate and bottleneck entity are determined, you should be familiar
with the following related concepts:
 The various types of production rates that are used by the system
 The types of completion times and how they are calculat ed
 How line properties are used to determine production rates
 How the line's production bottleneck entity is determined
 How entity production rates are tracked internally
Production Rates
The expected production rate for a given entity is the estimated production rate for the job running on the
entity. This is also referred to as the standard production rat e, as it is the rate that is set by the time
standard for the job. The ex pected rate can default to the standard rate defined for the entity if a rate is
not defined for the job.
The actual production rate is the rate derived by dividing the total production (good and reject) by the
amount of time that the entity was in a running state for the job.
Line Properties Used to Determine Production Rates

The following line properties must be defined to support the determination of the line’s production rates.
Standard Item
The standard item that is being produced on the line.
Version 6.0 35
Batch Size
The standard batch size used when producing items on the line. The default is 1.
Production Unit of Measure
The standard production rate unit of measure for items produced on the line. The default is
hours/batch.
Determining a Line’s Performance and Production Amounts

A line’s performanc e amount is the amount of production (good and rejects) at the line’s bott leneck entity
(see Bottleneck Entities on page 36). If the line’s bottleneck is a set of parallel entities, the performance
amount for the line will be the sum of the performance amounts of the parallel entities. Rejects from
entities upstream from the bottleneck entity/entities are not included in the performance amount.
A line’s production amount is the amount of production (good and rejects) to be reported to resource
planning systems, such as an enterprise resource planning (ERP ) system. It is based on the amount of
production at the entity defined as the line’s production source, which is usually the last entity in the line.
If there are other entities at the same line position as the entity that is defined as the production source,
the production amount will be the sum of the production of all entities at that line position.
Bottleneck Entities
A bottleneck entity is identified for each line to determine the line’s performance rate. The bottleneck
entity line position is the entity or set of parallel entities in a line that have the lowest expected produc tion
rate, and thus limit the rate at which the entire line can produc e items.
The entity production rate can vary by whether a job is running or not and by which job is running.
Therefore, the bottleneck is not necessarily a fixed entity or line position, but can be determined
programmatically (either by MES Web Portal or by MES Stateless API c alls) given the c urrent production
situation.
The production rate for a set of parallel entities is determined by adding the appropriate production rates
of each eligible entity (that is, entities that are not disabled or that can be bottlenecks) and converting
them to a common unit of measure (see Line Configuration Settings on page 68). The production rate of
the bottleneck entity, or parallel entities, is used as the line's production rate, and the performance
amount of the bottleneck entity, or parallel entities, is used as the line's performance amount.
Determining Bottlenecks Manually or Automatically

The bottleneck entity can be det ermined in the following ways:
 Manually, by specifying a speci fic entity as the bottleneck entity when configuring the line. In this
case, the specified entity is always used to set the line's performance amount. Note that, if there is
more than one entity at the same line position as the manually -designat ed entity, the performance
amount comes from all of the entities at that line position. See Manually Designating the Bottleneck
Entity on page 79.
 Automatically, by not specifying a specific entity as the bottleneck entity when configuring the line,
but by specifying which entities can be the bottleneck. In this case, the bottleneck entity will be
determined by the system’s evaluation of entity performance rat es for the entities that have been
designated as "Can be a bottleneck." See Configuring the Automatic Determination of Bottleneck
Entities on page 80.
Automatic Determination of Performance Rates and Bottleneck Entities

The following behavior governs the aut omatic determination of entity performance rates and which
entities are bottlenecks.
 All entities at the line position with the lowest production rate are designated as the bottleneck
entities.
36 Version 6.0
 If entities at different line positions have the same lowest performance rat e for the line, the entity (or
set of parallel entities) closest to the end of the line is designated as the bottleneck entity.
 The production rat e for a set of parallel entities is the sum of the production rate of all of the parallel
entities that are enabled. This is true whether the entities are in a standalone set of parallel entities or
are in parallel line segments and at the same line position. Note that there must be a path of enabled
entities through the line or line segment.
 For an entity to be considered a bottleneck, it has to be configured as capable of being a bottleneck.
 If an entity does not have a utilization reason (meaning a utilization event was never set for the entity,
perhaps because the entity was just created), then that entity is considered for the bottlenec k
calculation. However, if the entity has a utilization reason, then the current utilization reason for that
entity must have its Is Entity enabled when this Reason applies? setting selected to consider that
entity for the bottleneck calculation; otherwise, it will not be considered.
 To compare production rates between entities at different line positions, the line’s and entities’
production units of measure, batch sizes, and standard items are used to convert the rates to
comparable units. This comparison, and thus the determination of the bottleneck entity, can only be
performed if item production rates can be converted to comparable units.
 If an entity is running multiple jobs, the lowest production rate of all of those jobs is used for the
entity's production rate value when calculating the line's performance rate.
 If an entity is not running any jobs, the next job that will be running on it is used in the performance
rate calculation. The next job is determined by looking at the next upstream work order on the line
that has a job for this entity. If there are no jobs for the entity in any upstream work orders, then the
standard production rat e defined for the entity is used (see Configuring Entities on page 58).
Conditions When an Entity’s Production Rate Cannot Be Determined

If the production rate for an entity cannot be determined, then the line’s performance rate and bottleneck
entity cannot be determined. Examples of this condition are:
 An entity on which no job is running, there is no upstream job source for the rate, and a default rat e
has not been defined for the entity.
 A job is running on an entity that produc es an item that is different than the default standard item
configured for a line and there is no conversion factor between the different units of measure of these
two items.
Determining Comparable Units and Production Rates

The expected production rat e for a given entity is primarily the estimated production rate of the job
running on the entity. To compare the production rates among the entities in a line, the rates have to be
converted into comparable units. This involves the production unit of measure (UOM), the batch size,
and the UOM for each standard item.
The estimated production rate can be expressed as hours, minutes, or seconds per batch, or batches per
hour, minute, or second, as defined by the entity’s production unit of measure.
As an example of the production rates for different entities being defined differently, one machine can be
running at 20 batches per minute with a batch size of 5 and for which the item is a 64-oz bottle. Another
machine might be making 30 batches of 20-oz bottles per hour with a batch size of 2.
 The production UOM and batch size factors can be handled by converting all rates to a common
production UOM and batch size.
 For the item UOM conversion, the native production UOM of the item is used to convert to the native
production UOM of another item. In the case of converting a 64 -bottle to a 20-oz bottle UOM, the
conversion factor to convert "64-oz bottle" to "20-oz bottle" would be 3.2, assuming that the
operation's duration is proportional to the volume of the container.
Version 6.0 37
When the item being produced by an operation is different than the items being produced at the
upstream operations, there might not be a direct UOM conversion defined bet ween the UOMs of items in
successive operations. In this case, you need to define the UOM conversions in MES Client. For
example, if an 8-count carton (with a certain item ID) holds 8 64-oz bottles, a unit-of-measure conversion
factor of 8 must defined between "each" or "8 -ct" (the unit of measure of the carton) and "64-oz bottle".
There will always be a standard item being produced on the line whose UOM is used as the reference
UOM. If a standard item for the line is defined, then its UOM will be used as the UOM to which all
production rates for the individual entities are converted. If a standard item for the line is not defined, the
UOM of the first item encountered when doing the production rate conversion calculation will be used as
the standard to which all other UOMs are converted. The UOMs of all items being produced in the line
must be able to be convert ed to the standard item's UOM.
Internal Tracking of Entity Production Rates

The estimated production rate for an entity is updated whenever any of the following events occur on the
entity and the production rate has changed. When automatic determination of the bottleneck is being
used, any time that an entity’s production rate is updated, a reevaluation of the line’s bottleneck is
performed. The bottleneck information is displayed in the header area of every line page in MES Web
Portal.
 A job is started on the entity and the new job's production rate is different than the entity’s previous
production rate.
 A job is ended on the entity and the entity's projected production rate is different than that of the job
that was ended. The projected production rate is determined by the next job that is expected to be
run on that entity if one of the following events occurs:
o A job starting on an upstream entity from that entity, where neither that entity nor any between it
and the upstream entity where the job is being started are running any jobs.
o A job ending on an upstream entity from that entity, where neither that entity nor any bet ween it
and the upstream entity where the job is being ended are running any jobs.
 A change in the production rate of a job running on the entity. Note that this can be a change in the
job's production rate unit of measure, batch size, or the item being produced, as well as a change in
the job’s production rate value itself. (In MES Client, the UOM, batch size, or item being produced
cannot be changed while a job is running on the entity. When using the Stateless API, the item being
produced cannot be changed while a job is running on the entity.)
 A change in the production rate of a job that is running on an upstream entity from the entity, where
neither that entity nor any bet ween it and t he upstream entity where t he job's production rate is being
changed are running any jobs.
 A change in the default production rate of an entity if neither that entity nor any upstream entities
from it are running any jobs. This would occur if one or more of the following parameters are changed
for the entity: the standard item, the batch size, or the production unit of measure. See Configuring
Entities on page 58.
 The entity is disabled by choosing a utilization reason for it that indicates that it is disabled (that is, a
utilization reason for which the Entity Enabled flag is false) when the previously chosen utilization
reason indicated that it was enabled. In this case, its production rate would go to 0.
 The entity is enabled by choosing a utilization reas on for it that indicates that it is enabled (that is, a
utilization reason for which the Entity Enabled flag is true) when the previously chosen utilization
reason indicated that it was disabled. In this case, its production rate would probably change from 0
to some other value.
38 Version 6.0
Decimal Precision of Item Production Quantities

The number of decimals used for item production quantities display ed in MES Web P ortal is based on the
item's Num Decimals parameter. However, for good production (not rejected production), if the Num
Decimals parameter is 0, then the number of decimals is based on the system parameter Maximum
number of decimals for good piece part entries. For information about setting these parameters, see the
MES Client User Guide or online help.
Work Orders and Jobs

Production rates are calculated as jobs are executed according to work orders.
To track the progress of job execution, it is helpful to understand work order status and job states.
Work Orders
A work order represents a request for some quantity of an item to be produced. A work order is uniquely
identified by its ID number. Onc e completed, a work order is not intended to be execut ed again.
For line management, work orders can be created and assigned to lines in MES Web Portal. Work orders
can also be submitted to MES from an external system, such as a manufacturing resource planning
(MRP ) or enterprise resource planning (E RP) system, or created in MES Client. The work orders are
assigned to specific production lines.
To be executed, the work order must comprise a set of jobs that represent the complete set of operations
required to manufacture that product from ingredients or components. Thes e ingredients or components
may have been purchased or manufactured as the result of a previous work order. Creating a work order
in MES Web Portal and assigning it to a line also creates the necessary jobs for all entities associated
with the line. Unlike work orders created using MES Client and worked using MES Operator, there is no
correlation to a process and therefore no conc ept of a bill of material in MES Web Portal. There is the
produced item of the work order and the quantities (starting and required).
Work Order Status

A work order has a status that is determined by the status of its member jobs. Job states are described in
Job States on page 40.
You can also manually change work order's status. See Changing a Work Order's Status on page 86.
The status of the work order is derived bas ed on the first condition that satisfies the following order:
1. If there is a job running, the work order status is Running.
2. If all the jobs are completed or canceled, the work order status is Complete.
3. If there is any one on-hold job, then the work order status is On Hold.
4. If there is any one suspended job, then the work order status is Suspended.
5. If there is any one ready job, then the work order status is Ready.
6. If none of the above conditions are true, the work status is New.
Jobs
A job represents an instance of an operation for a given work order that is intended to be performed at a
given entity. A job can include a list of steps or procedures that are execut ed to perform t hat operation. In
turn, a work order consists of a set of jobs that are executed to produce an item.
Within the MES databas e, a job is characterized by a unique combination of work order ID, operation,
and internal sequence number.
Jobs are execut ed on entities. Jobs can be controlled by:
Version 6.0 39
 Starting an existing job on the entity

 Pausing or ending a job that is running on the entity
The recording of job execution data for an entity can be performed by an Operations Capability Object
(OCO) instance. In the MES Web Portal, a production operat or can manually start a new job or end a job
(see Starting and Ending Jobs on page 100).
Job States
New
The job is scheduled to be run but is not yet ready to start because upstream work needs to be done
first, unless the job is for a first operation of a work order. When a new work order is assigned to a
line, a job is created for eac h entity on the line with a status of New.
Ready
The job is ready to start; all of the requirements for running the job h ave been met.
Running
The job is currently running on an entity.
On Hold
The job has been paused indefinitely, typically because of some problem such as material or
machine issues.
Suspended
The job has been temporarily paused, typically in favor of another more import ant job.
Canceled
The job has been permanently stopped before being completed; a record of it is still maintained in the
MES databas e.
Complete
The job has finished.
Work Order and Job Creation in MES Web Portal

When a work order is created and assigned to a line, a job is created for each entity in the line. Within the
work order, each job is uniquely identified as follows:
 An operation ID is assigned, starting at 1 and incremented for each position in the line layout.
 A sequence number is assigned, starting at 0 for each parallel entity at a given location or each
unique segment in the line and incremented according to the entity name or segment order in the
line, respectively.
40 Version 6.0
The following diagram illustrates the operation ID and sequence number assignments for jobs in a line
with two segments.
Note that, for work orders created in MES Web Portal, no BOM information is associated with the work
order assigned to a line, except for the produced item itself. It is assumed that for these work orders, the
material consumed is the same as that produced, and in the same amounts.
For information about how to creat e a work order and assign it t o a line, see Creating a Work Order on
page 85.
Work Order Reassignment

In certain situations, it is necessary to reassign a work order to another line. This could happen when one
line has equipment failure and the work order has to be moved to another line for immediate completion.
Work orders can be reassigned even if some units have already been produced against the work order.
When reassigning a work order, its ID and the item being produced cannot be changed. For how to
reassign a work order, see Reassigning a Work Order to Another Line on page 88.
Note: Only work orders created from a line can be reassigned. Work orders created from a process are
not shown in MES Web Portal.
A work order can be reassigned to another line if its status is New, Ready, Suspended, or On Hold.
A running work order, which means it has at least one job running, cannot be reassigned to another line.
The running work order must first be stopped by:
 Changing its status to Suspended or On Hold, or
 Stopping or completing any of its running jobs
Reassigning a work order to another line has the following results:
 All the existing jobs are deleted and new jobs are created according to the entity configuration of the
new line. To ensure job record uniqueness, the sequence numbers for the new jobs wi ll start with the
sequence number that follows the highest sequence number used for any previously existing jobs in
the work order.
 Any existing production dat a for the work order is retained.
 The starting quantity defaults to the quantity remaining. The quantity remaining is the difference
between the original starting quantity and the total good quantity produced in any job for this work
order that ran on the line's production entity, and any entities in parallel with the production entity,
plus the reject quantities produced in these jobs or any jobs upstream from them.
Version 6.0 41
 The required quantity defaults to the original required quantity less any good quantity or 0, whichever
is greater. The quantity produced is the total of any good quantity produced in any job for this work
order that ran on the line's production entity plus any entities in parallel with the production entity.
 The produced and rejected quantities show the totals for the reassigned work order when a different
line is selected. These totals do not include production from lines to whic h the work order was
previously assigned. Each time the work order is reassigned these totals are reset to 0, because the
starting and required quantities are being updated to just the remaining amounts for the work order
on its new line.
 The starting and required quantities are updated based on the production that has already been
reported for the work order, to reflect just the amounts that need to be produced on the new line.
Note that starting and required quantities are based on the production at the line's production entity.
For example, say there are t hree entities in series in a line and a work order for 1,000 units. When the
work order is suspended to be reassigned, 10 units were rejected at an entity upst ream from the
production entity, and the production entity for the line has processed 380 units. When the work
order is reassigned to another line, the starting quantities for all three entities will be 610, regardless
of how many units the other two entities had processed before the work order was suspended.
Note: In some situations where scrap quantities have been reported, the calculations of starting quantity
and required quantity will result in a starting quantity that is less than the required quanti ty, which is not
permitted. These jobs cannot be reassigned to another job until either the job is updated through
methods outside MES Web Portal or the job is completed.
Effects of Work Order Status Changes on Job States

 Changing the status of a work order to New will set the state of all its jobs to New. This is allowed only
if no production quantities have been recorded for any jobs in the work order.
 When the status of a work order is changed from New or Suspended to Ready, the state of all of its
jobs that are not Complete or Canceled will be changed to Ready if the system setting Ready all new
jobs of a work order together has been selected. If this system setting has not been selected, then
only the jobs that are not Complete or Canceled and that are not preceded by a job with a state ot her
than Complete or Canceled will be changed to Ready.
 When the status of a work order is changed from On Hold to Ready, the state of all of its jobs that are
On Hold will be changed to Ready.
 When the status of a work order is changed from In Progress to Ready, all of the running jobs are
paused and their states are set to Ready.
 When the status of a work order is changed from Complete to Ready, the state of all of its jobs that
are Canceled will be changed to Ready, and the state of all of its jobs that are Complete and have no
production quantities recorded will also be changed to Ready.
 If the work order is assigned to a line that is configured to allow only one work order to run at a time,
when the status of a work order is changed from Ready to In Progress, the state of all of its jobs that
are Ready will be set to Running. If the line is configured to allow for more than one work order to
run at a time, the Ready jobs that are closest to the first jobs will be set to Running.
Changing the status of a work order from a status of other than Ready to In P rogress will do what first
readying the work order and then changing it to In Progress does.
All running jobs from ot her work orders will be sus pended on the entities where this work order's jobs
are being started if not doing so would cause the maximum number of job positions to be exceeded.
In addition, if the line is allowed to run only one work order, all running jobs from the other work order
will be suspended, even if no job for the work order being started will be started on entities where the
other work order is running, so that the limitation on the line's not being allowed to run more than one
work order is observed. For the case of a shared entity that can run more than one job, only jobs of
work orders from the same line as the work order being s et to In Progress will be suspended.
42 Version 6.0
 When the status of a work order is changed from any other status to Complete, the state of all of its
jobs that are not Canceled will be set to Complete unless this would violate minimum or maximum
consumption requirements. If it would, then the status change to Complete will not occur. Note that
there is no ot her check (for example, that anything at all has been made) on the appropriat eness of
this action.
 When the status of a work order is changed from any other status to Suspended, the state of all of
its jobs that are not Complet e or Canceled will be set to Suspended.
 When the status of a work order is changed from any other status to On Hold, the state of all of its
jobs that are not Complete or Canceled will be set to On Hold.
 When the status of a work order is changed to Canceled, the state of all of the work order's jobs that
are not Complete will be set to Canceled.
Line Layout Reconfiguration Guidelines

A line's layout can be rec onfigured, even if work orders are assigned to it. See E diting a Line on page 70.
The following topics describe the guidelines under which a line with assigned work orders can be
reconfigured. Note that the guidelines are different for work orders created from a line vs. work orders
created from a process.
Guidelines with Work Orders Created from a Line

You can reconfigure a line that has work orders created from a line queued to it within the following
guidelines:
 You must have line editing privileges. This is assigned using the May edit lines Configurator privilege
setting in MES Client.
 All work orders on the line must have a status of New, Ready, Suspended, or On Hold.
 If a work order is currently running, which means it has at least one job running, it must be stopped
by:
o Changing its status to Suspended or On Hold (see Changing a Work Order's Status on page 86),
or
o Stopping, canceling, or completing any running jobs. Jobs can be stopped or completed in MES
Web Portal (see Starting and Ending Jobs on page 100), but can only be canceled using MES
Client.
 For Suspended or On Hold work orders, the calculated starting quantity must be equal to or greater
than the required quantity.
Guidelines with Work Orders Created from a Process

In addition to being created in MES Web Portal, work orders can also be created from a process. These
work orders are either creat ed from a proc ess defined in MES Client or import ed into the system using
Supply Chain Connector.
Note: Work orders that are created from a process and assigned to a line will not be shown in the Work
Order collection page.
You can rec onfigure a line that has work orders created from a process assigned to it within the following
guidelines:
 You must have line editing privileges. This is assigned using the May edit lines Configurator privilege
setting in MES Client.
Version 6.0 43
 All work orders on the line that were created from a process must have a status of Complete.
 If a work order is currently running, which means it has at least one job running, it must be stopped by
completing or canceling any running jobs. Jobs can be completed in MES Web Portal (see Starting
and Ending Jobs on page 100), but can only be canceled using MES Client:
 Changes can only be made to entities that have completed or canceled jobs. Any running jobs must
be manually removed using MES Client. Changes to entities include the following:
o Removing an entity from the line
o Changing an entity's input percentage or the input percent age to the first entity in its segment
o Moving an entity to a new segment.
 If an entity is added to the line, jobs for the entity must be manually created for all work orders
already queued to that line that are expected to be run while the added entities are pres ent. This
includes deleting existing job routes that "span" the added entities (that is, the route runs from an
entity preceding the added entity to an entity following the added entity) and adding new job routes
that account for the new jobs. Failure to do this will mean that, for work orders created from a
process, there will be no jobs to execute on the newly -added entities when already-queued work
orders are run.
Line Layout Reconfiguration System Behavior

Reconfiguring a line's layout essentially reassigns all the work orders created from the line as it existed
prior to the modification to the same line as it exists after the modific ation. This means that the old jobs
are completed and new jobs are creat ed, even for entities in the line that were not directly involved with
the change.
Thus, if a work order is partially run on the line, and then the line is modified and the work order is
restarted, the work order will be running a different set of jobs than it was previously. The item quantities
will reflect only the amount of work remaining when the line was modified. Also, if a work order is queued
to the line with a non-zero required quantity and the The required quantity must be produc ed to end a job
setting is selected for any of the line’s entities, at least that much good production will need to have been
recorded at those entities for that work order or modifying the line will not be allowed.
Understanding Batches and Lots for OEE

It is important to understand the difference between batches and lots so that your OEE results are within
expected ranges.
 A lot is generally used to uniquely identify a group of consumed or produced items for tracking
purposes.
 A batch is an amount of product that is processed simultaneously. A batch is used to determine the
standard production time for a given amount of product. Standard production times are expressed
either in time per batch, or batches per time.
For example, assume that you want to track all of the cookies that are baked during a shift as a group,
and that you want to det ermine the cookie production’s OEE. A unique lot number can be assigned to the
group of cookies produced during the shift. But the lot size has nothing to do with the OEE calculation.
That calculation would be based on the batch size and the batch production rate. If a batch size is 100
cookies and it takes 20 minutes to bak e a batch of cookies, then up to 24 batches of cookies could be
baked during an 8-hour shift, or a maximum of 2,400 cookies in a lot.
Also, note that the amount of production might not be an integral number of batches. This is because the
standard production time for a batch will be constant, regardless of whether the batch ac tually includes
the maximum number of items for the batch. For example, if the oven capacity, and thus a batch, is 100
cookies, it takes as long to bake 90 cookies as it does to bake 100. The performance component of OEE
factors in t his nonlinear behavior. So, for OEE to be reported accurately, it is important that the batch size
be set according to the way production actually occurs.
44 Version 6.0
The number of decimals used for batch sizes displayed in MES Web Portal is based on the system
parameter Maximum number of decimals for batch size entry. For information about setting this
parameter, see the MES Client User Guide or online help.
Utilization
An entity’s utilization is tracked when an associated Utilization Capability Object (UCO) or production
operator enters events, such as when the entity is running a job or when the entity is down for repairs or
maintenance.
At all times, an entity will have a reason assigned to it. The reason can be assigned by an operator
manually or determined directly from a UCO by input/output (I/O) automatically. The reason will assign a
utilization state. Based on the configuration of the utilization state, the event as classified by the reason
will contribute to either the Performance or A vail ability component of OEE, or the time will be excluded
from the OEE calculation entirely.
It is important to understand that "event" does not refer to an isolated occurrence of something at the
entity. All utilization events for an entity form a contiguous series from the time the entity was configured
as being capable of capturing utilization to the present. In other words, one sort of event or another is
always occurring at the entity.
An operator adds an event by selecting a utilization reason for t he entity. The utilization reason specifies:
 The state of the entity
 A reason for that state
Operators might have to make adjustments to events that have already been entered so that they
represent actual entity activity. These adjustments include:
 Reclassifying an event by selecting a different utilization reason
 Splitting an event into two events
 Merging two adjacent events
 Modifying an event’s start or end time
 Modifying the comment ent ered about an event
Utilization States
To support utilization tracking, entities are considered to be in utilization states, such as Running, Idle,
Down, or Maintenance.
During system configuration, utilization states are assigned to utilization reasons. Therefore, an entity’s
state is defined when a utilization reason is assigned to an entity’s event.
For information about configuring utilization states, see Configuring Utilization States on page 52.
Utilization Reasons
Utilization reasons describe the current condition of an entity and associate eac h reason with a utilization
state. A reason group is a category of reasons. For ex ample, the reason Bottle Jam can belong to the
reason group Bottle Descrambler Down, and results in a Downtime utilization state. On the production
floor, a reason can be selected by a PLC, an input/out put (I/O) connection to a devic e, or an operator.
The utilization reasons that operators can assign to events during production are created during system
configuration. For a list of the configuration settings, see Utilization Reas on Settings on page 56.
For information about configuring utilization reasons, see Configuring Utilization Reasons on page 55.
Version 6.0 45
Utilization Reason Groups

To help production operators navigate a large list of utilization reasons, reasons can be assigned to
utilization reason groups during system configuration.
The reason groups are displayed as folder nodes in the reason list.
It is helpful to understand the difference between utilization states and utilization reason groups. While
both terms represent an aggregation of utilization reasons, states are sets of reasons that imply
something about the physical situation of the entity, with res pect to the way it is operating or not
operating. Utilization reason groups are strictly a navigational aid for lists of utilization reasons in the user
interface.
For information about configuring utilization reason groups, see Configuring Utilization Reason Groups
on page 54.
Raw Reason Codes

Machine utilization raw reason codes can be sent directly from an entity to MES (for example, via a
UCO). Depending on how the raw reason code is configured in the UCO or in MES Client, it will create a
new utilization event in the MES database, using the utilization reason to which the raw reason code was
mapped.
If a raw reason code that is not configured for the entity is received, the Unknown Reas on utilization
reason, which is configurable in MES Web Portal, is used.
Utilization Events
A utilization event indicates the current operational state of the entity. An entity is always considered to
be in a utilization event. The events that are typically of interest are those that indicate that the e ntity is
down or when it is idle when it should be running.
If so configured, the system can set an entity’s event automatically based on changes in the operational
state of the entity.
Production operat ors can also manually change the event that an entity is in when the condition or state
of the entity changes. When changing to a new event, the operat or assigns a utilization reason to the
new event. The reason specifies the entity’s utilization state and the reason for that state. For example,
the utilization reasons Running - Normal Speed, Running - High Speed, and Running - Low Speed all
indicate a utilization state of Running. However, each reason indicates a running speed.
Standard, Minimum, and Maximum Utilization Reason Times

When configuring a utilization reas on, the Standard, Minimum, and Maximum Times can be specified for
it. These times can be displayed in MES Web Portal and in utilization reports to indicate expected times
that an entity can be in the utilization reason.
46 Version 6.0
Maximum Duration
When configuring a utilization reason, a Maximum Duration can be specified for a utilization reason. This
value can be used to do one of the following:
 Specify how long an entity can be in the utilization reason before the condition is considered Severe.
For example, a plant might consider an entity that is undergoing maintenance for longer t han 2 hours
to be in a Severe condition. If so, the Maintenance utilization reason would have its Maxi mum
Duration set for 2 hours.
The state of the Severe flag for an entity event is shown in the Event Hi story grid.
 Specify how long an entity can be in the utilization reason before it is changed to a new reason. For
example, you might want a machine that is in the Jammed utilization reas on for more than 5 minutes
to automatically switch to the Requires Mechanic Assistance reason.
Splitting Events
An event can be split into two events, so that one of them can be assigned a different utilization reason.
For example, if it was discovered that an entity had actually been down for a portion of a Running event,
the Running event can be split.
For information about how to split events, see Splitting an Event on page 106.
Merging Events
Adjacent utilization events for the same entity can be merged if it is determined that the events actually
represent one event.
To merge two events for an entity, all of the following conditions must be true:
 The events are contiguous. This is, no other events have occurred bet ween the two events.
 The events have the same utilization reason.
 The events are in the same shift.
 The comments for the events are the same.
or
The comments for the events are different but one of the options for the system parameter How to
handle comments when merging utilization events that allows events with different comments to be
merged has been selected. (This system parameter is configured in MES Client, in the Operator
group of the General Parameters module. )
 The raw reason codes for the events are the same.
or
The raw reason codes for the events are different but one of the options for the system parameter
How t o handle raw reas on codes when merging utilization events that allows events with different
raw reas on codes to be merged has been selected. (This system parameter is configured in MES
Client, in the Operator group of the General Parameters module.)
For information about how to merge events, see Merging an Event with an Adjacent Event on page 108.
OEE
The efficiency calculation implemented in the MES is based on the industry standard OEE (Overall
Equipment Effectiveness) efficiency methodology.
OEE is determined as follows:
Version 6.0 47
OEE = Availability x Quality x Performance

OEE as implemented by MES is described in the following topics.
Availability
The availability component of OEE measures a system's availability during the scheduled operation time
for a given time period, based on the following equation:
A vailability = Runtime / Net Operating Time
Entity Availability
In MES, a line’s availability is based on the availability of the line’s bottleneck entities during the given
time period.
To support the determination of entity availability, utilization events are applied to each entity. A
utilization event indic ates the current operational state of the entity. Utilization events can be applied
automatically based on an entity's default utilization settings (see Configuring Default Utilization
Reas ons for Standard Events on page 64) or manually by an operator.
The component of a utilization event that is used to determine entity availability is OEE Use. Each
utilization event, via its utilization reason and that reason’s assigned utilization state, is assigned an OEE
Use value of Runtime, Downtime, or Neither. MES bases the calculation of an entity’s availability by
summarizing the duration of its Runtime and Downtime events in the given time period for eac h OEE
Use. E vents with an OEE Use value of Neither are not included in the calculation.
So for MES, an entity’s availability is:
Entity Availability = Runtime / (Runtime + Downtime)
Line Availability
To determine a line’s availability, the system considers the Runtime and Downtime events for any entities
that were designated as bottleneck entities during the given time period. This includes all entities at a
bottleneck entity position in the line. Only those portions of the events that fall within the time frame in
which the entities were designat ed as a bottleneck entity are included.
So, a line’s availability is:
Line A vailability = Bottleneck Entities Runtime / (Bottleneck Entities Runtime + Bottleneck Entities
Downtime)
Quality
The quality efficiency component of OEE measures a system's output quality while producing units
during a given interval.
Quality = Good Output / Total Out put
Entity Quality
In MES, entity quality is:
Quality = Good Production / (Good Production + Rejected Production)
where only production at the entity is considered.
Line Quality
In MES, line quality is:
Quality = Good Production / (Good Production + Rejected Production)
Good production counts for a line are capt ured at the line's production entity (or entities, if there is more
than one entity at that line position). Rejected counts are captured at the production entity and any
upstream entities during the given time period.
48 Version 6.0
The production counts are normalized to the line’s unit of measurement (UOM) before calculating the
quality metrics. Therefore, if the UOM of the production item is different than the UOM of the line’s item,
a conversion factor from the production item to the line’s item must be defined in the system. An error is
returned if no conversion factor exists to convert the production counts to the line’s UOM.
Performance
The performanc e efficiency component of OEE measures a system's ability to produce at the target
production rate:
Performance = Total Output / Target Output
Entity Performance
In MES, an entity's performance during a time period is based solely on the production reported on the
entity only while the entity is in a Runtime utilization state. If multiple work orders are run during the
period, producing different items with different unit of measures, the performance calculation is based
purely on item production counts with no effort to convert units of measure.
Line Performance
In MES, the performance component of OEE for a line focus es on the Runtime events during a given
time period. The system compares the total output as measured by production transactions during the
time period to the output that would be expected if the entity or entities were producing at the target
production rate while in the Runtime state.
A line’s performance is:
Performance = Actual Production Count / Expected Production Count
Where:
 Actual Production Count is the total number of good units produced on the production entity during
the given time period, plus the reject units produced on t he production entity and all entit ies upstream
to the production entity. All counts are converted to the unit of measure (UOM) of the line's standard
item.
 Expected Production Count is calculated using the following equation:
Expected Production Count = Duration of the Bottleneck Entities During Runtime x Default Entity
Production Rates (in batches) x Default Entity Batch Size
If the bottleneck entity is in parallel with other entities in the same line position, then all the entities at that
position in the line will be considered. Only durations for which the utilization event’s Is entity enabled
when this reason applies? s etting is true are included in the calculation. The actual production counts are
determined in the same way the production counts are determined for quality (see Quality on page 48).
Determining the Line’s OEE Target Values

A line’s OEE target values are set as part of the line configuration (see Creating a Line on page 67 and
Line Configuration Settings on page 68). Target values are displayed in the KPI gauges on the line’s
Monitor tab.
Version 6.0 49
C HAPTER 3
MES Web Portal Configuration
In This Chapter
Configuration Overview ................................................................................................................. 51
Configuring Utilization States and Reas ons .................................................................................... 51
Configuring Entities ....................................................................................................................... 58
Configuring Lines .......................................................................................................................... 67
Configuration Overview
You can create and configure the following components that are used in MES Web Port al:
 Utilization states, reason groups, and reas ons (see Configuring Utilization States and Reas ons on
page 51)
 Entities (see Configuring Entities on page 58)
 Lines (see Configuring Lines on page 67)
 Work orders (see Creating a Work Order on page 85)
Access to each of the configuration pages starts at the Home page, shown below. The proc edures in the
topics referenced in the previous bullet list provide det ailed steps for navigating to the appropriate
configuration pages.
Note that, because utilization states and reasons are specified for entities, and entities need to exist in
the system to create lines, the suggested order for configuring components is:
1. Configure utilization states, reason groups, and reasons that will be used with the entities.
2. Configure the entities that will be used in the lines.
3. Configure the lines.
4. Create work orders.
Configuring Utilization States and Reasons

To implement entity utilization tracking, you must configure utilization states, reason groups, and
reasons.
For conceptual information about utilization states and reasons, see Utilization on page 45.
Version 6.0 51
MES Web Portal User Guide MES Web Portal Configuration
Configuring Utilization States

To add a utilization state
1. On the home page, click the Utilization tile. The Utilization page appears.
2. Click the States tab.
3. Click the Add State icon. A new state entry is added to the grid.
4. Enter the state’s configuration settings. See Utilization State Settings on page 53.
5. To save the settings, click the Save icon in the action bar.
To edit a utilization state
 In the grid on the State s tab, modify the state’s configuration settings. To s ave the changes, click the
Save icon in the action bar.

To delete a utilization state
 In the grid on the States tab, click the state entry to select it and then click the Delete icon in
the action bar.
A utilization state that is linked to a utilization reason cannot be deleted. You must first link the utiliza tion
reason to another utilization state before attempting to delete it.
Unsaved Change s Indicator and Behavior
If you make changes to a state's setting, the unsaved state of the setting is indicated by a red hash mark
in the upper left corner of the field, as shown below.
52 Version 6.0
MES Web Portal Configuration MES Web Portal User Guide
You can make changes to more than one setting and to more than one record before deciding to save
them all. You can also delete utilization states without affecting the unsaved state of other setting
changes.
Utilization State Settings

Each utilization reason is assigned a corresponding utilization state. In addition to the state's description
and background color, the utilization state includes utilization default settings. These default settings can
then be applied to the utilization reason when it is being added or edited.
Utilization State
Required. The unique name for the state.
Color
The state's background color in the user inte rface. A color is assigned by default, which can be
changed. Enter the color's hex code or name.
Priority
A default setting for the utilization reas on's priority, which is used to determine the reason for a line
that has two or more bottleneck entities with differing reasons. The reason with the
highest-numbered priority value is used as the line’s utilization reason.
The default is 1. A value must be entered, and 0 is not allowed. If 0 entered, the value defaults to 1.
OEE Use: Runtime
If selected, specifies that an event with this utilization reason counts toward runtime. Runtime events
contribut e to the calculation of A vailability and Performance.
OEE Use: Downtime
If selected, specifies that an event with this utilization reason counts toward downtime. Downtime
events contribut e to the calculation of A vailability.
OEE Use: Neither
If selected, specifies that an event with this utilization reason does not count toward runtime or
downtime. Therefore, this utilization reason time is excluded from the calculation of OEE.
Cost As
A default setting for the utilization reas on’s Cost As setting, which is used to determine whether an
event with this utilization reason is to be costed as fixed time, variable time, or neither.
Failure
A default setting for the utilization reas on’s Failure flag. If selected, specifies that any time that the
entity spends in t he utilization reason is considered failure time. Failure time is used in the calculation
of Mean Time Between Failures (MTBF) and Mean Time to Repair (MTTR).
Enti ty Enabled
A default setting for the utilization reas on’s Entity Enabled flag. If selected, specifies that any entity
with this reason is enabled for production. If an entity is in a disabled state, then its production rat e is
not used in the calculation of the bottleneck line position.
Maximum Duration
A default setting for the utilization reas on’s Maximum Duration value. Specifies the maximum
duration, in seconds, that is used with setting a Severe flag or with the New Reason parameter.
o If the New Reason functionality is not being used (that is, there is no ent ry in the New Reason
column) and the maximum duration is exceeded, the reason is marked as being Severe and the
event is considered to be in a severe condition. The Severe flag is typically used with downtime
events.
o If the New Reason functionality is being used (that is, there is an entry in the New Reason
column) and the maximum duration is exceeded, the utilization reason for the entity is changed
to the new reason specified in the New Reason column.
Version 6.0 53
A value of 0 is not allowed. If 0 ent ered, the value defaults to 1.

If Maximum Duration is not being used, leave this field blank, which disables the feature.
New Reason
A default setting for the utilization reason’s New Reason entry. The utilization reas on that this reason
should change to when the maximum duration is exceeded.
For example, if a Jam condition exceeds a maximum duration of 5 minutes, then the entity woul d
change to the new reason Mechanic Assistance Required. Note that this has the same effect as
manually entering a new reason of Mechanic Assistance at the 5-minut e mark. The new reason
(Mechanic Assistance Required) starts at that time, and the Jam utiliz ation event ends at that time.
However, because utilization is only updated once a minute, the actual transition may be up to 59
seconds after the maximum duration of the original event (Jam in this example) was reached.
This setting is not available unless a value is entered for Maximum Duration.
Standard Time
A default setting for the utilization reas on’s Standard Time value. The standard amount of time, in
minutes, that an entity is expected to be in this utilization reason.
Entered values are rounded to two decimal places.
Minimum Time
A default setting for the utilization reas on’s Minimum Time value. The minimum amount of time, in
Maximum Time
A default setting for the utilization reas on’s Maximum Time value. The maximum amount of time, in
Setup Time
A default setting for the utilization reas on’s Setup Time flag. If selected, specifies that an event wit h
this utilization reason counts toward setup time.
Teardown Time
A default setting for the utilization reas on’s Teardown Time flag. If selected, specifies that an event
with this utilization reas on counts toward teardown time.
Category 1–4
Default settings for the utilization reason’s category entries. Specifies a user-defined entry that
describes a category.
Configuring Utilization Reason Groups

Utilization reason groups are used to organize utilization reas ons. Therefore, during configuration,
utilization reasons are added to reason groups.
To create a grouping hierarchy, a utilization reason group can be created in a another utilization reason
group. There can be up to 10 levels of groups.
To add a utilization reason group
1. On the home page, click the Utilization tile. The Utilization page appears and the Reasons &
Groups tab should load by default.
2. Add the reason group:
 To add a reason group at the highest level of the reason group hierarchy, in the Rea sons &
Groups tab, select the Utilization node in the tree.
54 Version 6.0
 To add a reason group as a child to an existing reason group, select the existing reason group in
the tree.
3. Click the Add Group icon. The Group Info pane appears.
4. Enter the reason group’s configuration settings:

a. In the De scription box, type the name of the reason group.
b. Optionally, in the Spare boxes, type custom data.
5. To save the settings, click Save. The new reason group appears in the tree.
To edit a utilization reason group
1. On the Rea sons & Groups tab, select the reason group.
The Group Info pane appears.
2. Make your changes, then click Save to save them.
To delete a utilization reason group
 On the Rea sons & Groups tab, select the reason group and then click the Delete icon. A
confirmation message appears.
To delet e a reason group that contains other reason groups, you must first delete the reason groups it
contains.
All reasons in a reason group are delet ed when the group is deleted.
Configuring Utilization Reasons

To add a utilization reason
1. On the home page, click the Utilization tile. The Utilization page appears and the Reasons &
Groups tab should load by default.
2. On the Rea sons & Groups tab, select the reason group with which the reason should be
associated.
Version 6.0 55
Note: Reasons must be associated wit h a reason group. However, reasons cannot be directly
associated to the Utilization node at the top of the tree, as that node is not a reason group. Only
reason groups can be created directly under the Utilization node.
3. Click the Add Reason icon. The Reason Info panel appears.
4. Enter the reason’s configuration settings. See Utilization Reason Settings on page 56.
 To apply the default reason settings defined for the currently selected utilization state, click
Apply Defaults.
5. To save the settings, click Save.
To edit a utilization reason
 On the Rea sons & Groups tab, select the reason. The Reason Info pane appears. Make your
changes, then click Save to save them.
To delete a utilization reason
 On the Rea sons & Groups tab, select the reason and then click the Delete icon. A
confirmation message appears.
Utilization Reason Settings

Description
The unique description for the reas on.
56 Version 6.0
Utilization State
The state with which the utilization reason is associated.
Priority for line utilization
Used to determine the reason for a line that has two or more bottleneck entities with differing
reasons. The reason with the highest-numbered priority value is used as the line’s utilization reason.
The default is 1. A value must be entered, and 0 is not allowed. If 0 entered, the value defaults to 1.
Is entity enabled when this reason applies?
If selected, specifies that any entity with this reason is enabled for production.
Failure
If selected, specifies that any time that the entity spends in the utilization reason is considered failure
time. Failure time is used in the calculation of Mean Time Between Failures (MTBF) and Mean Time
to Repair (MTTR).
Maximum Duration
Specifies the maximum duration, in seconds, that is used with setting a Severe flag or with the New
Reas on parameter.
o If the New Reason functionality is not being used (that is, there is no ent ry in the New Reason
column) and the maximum duration is exceeded, the reason is marked as being Severe and the
event is considered to be in a severe condition. The Severe flag is typically used with downtime
events.
o If the New Reason functionality is being used (that is, there is an entry in the New Reason
column) and the maximum duration is exceeded, the utilization reason for the entity is changed
to the new reason specified in the New Reason column.
A value of 0 is not allowed. If 0 ent ered, the value defaults to 1.

If Maximum Duration is not being used, leave this field blank, which disables the feature.
New Reason
The utilization reason that this reason should change to when the maximum duration is exceeded.
For example, if a Jam condition exceeds a maximum duration of 5 minutes, then the entity would
change to the new reason Mechanic Assistance Required.
If you are using the Maximum Duration setting to set a Severe flag, then leave this setting blank.
This setting is not available unless a value is entered for Maximum Duration.
Standard Time
The standard amount of time, in minutes, that an entity is expected to be in this utilization reason.
Minimum Time
The minimum amount of time, in minutes, that an entity is expected to be in this utilization reason.
Maximum Time
The maximum amount of time, in minutes, that an entity is expected to be in this utilizat ion reason.
OEE Use: Runtime
If selected, specifies that an event with this utilization reason counts toward runtime. Runtime events
contribut e to the calculation of A vailability and Performance.
OEE Use: Downtime
If selected, specifies that an event with this utilization reason counts toward downtime. Downtime
events contribut e to the calculation of A vailability.
Version 6.0 57
OEE Use: Neither

If selected, specifies that an event with this utilization reason does not count toward runtime or
downtime. Therefore, this utilization reason time is excluded from the calculation of OEE.
Scheduling Use: Setup Time
If selected, specifies that an event with this utilization reason counts toward setup time.
Scheduling Use: Teardown Time
If selected, specifies that an event with this utilization reason counts toward teardown time.
Categorization: Category 1–4
Specifies a user-defined entry that describes a category.
Note: These category entries are currently not integrated with MES Cat egory definitions.
Cost As: Fixed Time

If selected, specifies that an event with this utilization reason is costed as fixed time.
Cost As: Variable Time
If selected, specifies that an event with this utilization reason is costed as variable time.
Cost As: Neither
If selected, specifies that an event with this utilization reason is not costed as fixed time or variable
time.
Configuring Entities
To add an entity
1. On the home page, click the Entitie s tile.
The Entitie s page appears.
2. Click the Add Entity icon. The General configuration tab appears.
3. On the configuration tabs, enter the entity’s configuration settings.

4. To save the settings, click Save.
58 Version 6.0
Initially, the page has two tabs, General and Attribute s, on which you specify general settings and add
attributes to the entity. As you select the entity’s capabilities, additional tabs appear:
 If the entity can run jobs, you configure job settings on the Job tab.
 If utilization data can be captured for the entity, you configure utilization settings on the Utilization
and Allowable Reasons tabs.
 If OEE data can be tracked for the entity, you configure OEE settings on the OEE tab.
Configuring Entity Basic Information and Capabilities
On the General tab, you specify:

 Basic information about the entity
 The entity’s capabilities
Note: If an entity is a member of a line, then its Can Run Jobs, Can Capture Util, and Can Track OEE
capability options cannot be cleared. If you attempt to clear any of these options, an error message will
appear.
The General entity settings are:

Name
Required. The entity name. The name must be unique within a given site.
Description
A description of the entity.
Identical Job Execs
The number of jobs that can be run simultaneously on the entity.
A value of 0 (the default) or 1 indicates that only one job can run at a time.
Note: For entities that are in a line, MES currently allows only one job to be running at a time.
Ent spare fields

Can be used to specify custom general information about the entity.
Version 6.0 59
Can Schedule Jobs

The entity can have jobs scheduled to it.
Select this option if the entity is a member of a line.
This option is useful when jobs are initially scheduled to a parent entity (for example, from an E RP
download of a work order) and then the running entity (which has the Can Run Jobs capability) is a
child of the parent and set by the plant person.
Can Run Jobs
The entity can run jobs.
This capability is required so that the individual jobs for a specific entity that are associated to the
work order running on the line can be started and complet ed.
Can Capture Util
The entity can capture utilization data.
This capability is required because the production rate calculation for determining a line’s bottleneck
uses the entity's utilization reason to det ermine whether an entity is enabled and so should be used
in the rate calculation.
Can Capture Labor
The entity can capture labor data.
Can Track OEE
The entity can capture OEE statistics.
This capability is required because it allows for a default production rate to be assigned to the entity.
The production rate is used in the calculation that determines a line's bottleneck when no job is
running on the entity and the next one cannot be inferred.
Can Schedule Shifts
The entity has its own shift schedule and will not inherit shifts from any parent.
Select this option if the entity will be the parent entity of a line, unless shift inf ormation for the line is
inherited from an entity above the line's parent entity in the entity hierarchy.
Do not select this option if shifts for this entity are managed at a higher-level entity within the entity
hierarchy.
Can Store
The entity can serve as a storage location.
Can Log Data
The entity can log data to one of the data log t ables defined separately. This option is not required for
Quality data collection.
Can Ship
The entity can serve as a shipment location.
Can Receive
The entity can serve as a location that can rec eive materials.
Can Copy Folders
Copies of files in a folder (program files, documentation, and other files regarding an item’ s
production relative to the entity) can be made specifically for this entity.
Can Capture QM Data
The entity can have QM Samples generat ed for it and record results.
60 Version 6.0
Adding Attributes to the Entity

Attributes provide a way to assign additional properties to an entity, which can then be tracked in the
MES databas e, entered by or displayed for operators, and included in reports. For example, entity
attributes could be:
 Location (example attribute value: Aisle 6)
 Capacity (example attribute value: 5000 gal)
 Processing capability (example attribute value: Max. Temp. 500C)
 Manufacturer (example attribute value: Acme Nuclear Reactors Ltd.)
 Maintenance information (example attribut e value: Align monthly)
Attributes must be defined using MES Client before they can be added to an entity in MES Web Portal.
To add an attribute to an entity
1. On the Attribute s tab, click the Add Attribute icon. A new attribute row is added to the grid.
2. In the Attribute column, select the attribute.

3. In the Value column, enter the value of the attribute. Depending on the attribute selected, this entry
can be selected from a list, picked from a Date/ Time control, or manually typed.
4. Enter not es in the Note s column.
The Value and Note s columns behave as follows:
 If the attribut e is configured for a value only, a value must be entered and notes cannot be entered.
 If the attribut e is configured for notes only, notes must be ent ered and a value cannot be ent ered.
 If the attribut e is configured for a value and not es, entering a value or notes is optional.
To remove an attribute from the entity
 Click the attribute entry’s Delete button. A confirmation message appears.
Version 6.0 61
Configuring Job Settings
If the entity can run jobs, you specify the following job -related settings for the entity on the Job tab.
Default production reason
The default production reason that will be entered for the entity, unless a user overrides it with a
production reason in the Add Production dialog box.
Default consumption reason
The default consumption reason that will be entered for the entity, unless a user overrides it with a
consumption reason in the Add Consumption dialog box.
Note: This setting is currently not used in MES Web Port al.
Start next sequence for current W/O and operation

Specifies how the next sequence in the current work order starts.
o Manually: An operator must start the next sequence.
o When previous done: The next sequence number within a work order starts aut omatically. This
requires multiple jobs having the same work order and operation but different sequence
numbers queued at the entity. Otherwise, the next job must be started manually.
Start next job

Specifies how the next job starts.
o Manually: An operator must start the next job when a running job is completed.
o As soon as ready: The next job that is ready in the entity’s queue starts automatically aft er a
running job is completed. Otherwise, the next job must be started manually.
62 Version 6.0
End job
Specifies what ends a job.
o Manually: An operator must change the job status to Completed when a running job is
completed.
o When quantity done meets required quantity: The job status is changed to Completed when
the required item quantity is produced.
Show both item class and entity reasons

Select the check box to show item class reasons and the entity production and consumption reasons
for the jobs.
The required quantity must be produced to end a job
Select the check box to ensure that the required quantity is produced before the job is marked
Complete.
Run without operator
Clear the check box to ensure that an operator must remain logged on while a job is runnin g. By
default, no operator must be logged on while a job is running.
Note: This setting does not currently apply to MES Web Portal.
Suppress 'Start Some Quantity' prompt

Specifies whether a dialog box should appear for entering start quantities for a job that is being split.
If this check box is selected, the dialog box does not appear and, by default, the value of the start
quantity is 1. If the Allow zero quantity split check box is selected, the value of start quantity is 0 by
default.
Note: This setting does not currently apply to MES Web Portal.
Job_Exec Spare fields

Can be used to specify custom information about the entity's capability to run jobs.
Version 6.0 63
Configuring Default Utilization Reasons for Standard Events
If utilization data can be captured for the entity, you can optionally specify default utilization reasons on
the Utilization tab for the following actions:
 When the job starts
 When the job ends
 When a shift starts
 When a shift ends
 When a raw reason code that has not been configured for the entity is received (that is, if utilization is
coming from a UCO)
You can also enter:
 A value for the Target Util %. This value appears on the KPI A vailability gauge as the target
percentage of availability that the entity should achieve. See Viewing KPI Gauges.
 Custom utilization information using the Spare boxes.
64 Version 6.0
Specifying the Utilization Reasons That Can Be Used with an Entity
If utilization data can be captured for the entity, you specify the utilization reasons that can be used with
the entity on the Allowable Reasons tab. At runtime, when an operator manually adds a new utilization
event for an entity, the list of reason groups and reasons will be limited to the selected allowable reasons.
Note that if no reasons are specified for an entity, all reasons are available to be selected for it. It is not
possible to have no allowable reasons for an entity that can collect utilization, if there are any reasons at
all configured.
To specify allowable reasons
 Select the reason groups or individual reasons in the Allowable Reasons tree.
Version 6.0 65
Configuring OEE Default Data
If OEE data can be captured for the entity, you specify the entity’s OEE data default settings, described
below, on the OEE tab.
For an explanation of how these settings are used, see Production on page 35.
Default Production Rate
Required. The default production rate for the entity.
Note: The default production rate must be greater than 0. An ent ry of 0 will cause an error.
Default Production UOM

The default unit of meas ure for the production rat e. The default is hours/batch.
Default Batch Size
If using batches during production, ent er the default batch size. The default is 1.
Note: The batch size cannot be 0. If 0 is entered, it is automatically changed to the default value 1.
This setting is used when determining the line’s production rate. For additional information about how
batch size affects OEE results, see Understanding Batches and Lots for OEE on page 44.
The decimal place resolution of the batch size is controlled by the s ystem paramet er Maximum
number of decimals for batch entry. For information about setting this parameter, see t he MES Client
User Guide or online help.
66 Version 6.0
Default Standard Item

The default standard item that is used for the entity when the system is determining a comparable
production rate unit of measure for the different entities in the line.
To select a standard item from a list of available items, click Configure and then click the item.
Note: To filter the item list in the item selection dialog box, see Filtering Item Lists on page 18.
Target OEE %, Target Perf %, Target Qual %

The target setpoints for KPI OEE, Performance, and Quality. These values are indicated on the KPI
gauges by a tick mark at the outer edge of the gauge's color band. See Viewing KPI Gauges on page
112.
Deleting an Entity
1. On the home page, click the Entitie s tile. The Entitie s page appears.
2. To filter the entities list, see Filtering Entities on the Entities Collection Page on page 15.
3. Click the entity to be deleted. The entity’s page appears.
4. Click the Configuration tab.
5. Click the Delete icon. A confirmation message appears.
Note: If an entity is either the manually -designated bottleneck entity or the production source of a line,
that entity cannot be deleted.
Configuring Lines
When configuring lines, you can:
 Create a line (see Creating a Line on page 67)
 Configure a line's settings (see Line Configuration Settings on page 68)
 Configure a line's entity layout (see Configuring a Line’s Layout on page 70)
 Manually designate a line's bottleneck entity, or configure the automatic determination of a line's
bottleneck entity (see Manually Designating the Bottleneck Entity on page 79 and Configuring the
Automatic Determination of Bottleneck Entities on page 80)
 Delet e a line (see Deleting a Line on page 70)
 Assign line access to users (see Assigning Line Access to Users on page 81)
Creating a Line
1. On the home page, click the Lines tile. The Collection tab of the Line s page appears.
Version 6.0 67
2. Click the Add Line icon. The Add Line page appears.
3. Enter the line’s configuration settings. See Line Configuration Settings on page 68.
4. To save the settings, click Save. The line Configuration tabs appear.
Line Configuration Settings

Name
Required. The unique name for the line.
Labor Load (people)
The number of people required to run the line.
Note: This value is stored in the MES database but is not currently used.
Maximum Work Orders

Required. Maximum number of simultaneous work orders permitted on the line. The default is 1.
68 Version 6.0
This setting affects how jobs are handled when starting a work order on a line. When Maximum Work
Orders is 1, starting a work order will attempt to start all of its jobs at once. Unless the system
parameter Ready all new jobs of a work order together in MES Client is set to Yes, only the first job(s)
of a new work order will initially be ready, and this will not work. Therefore the Ready all new jobs of
a work order together parameter must be set to Yes when there are lines having Maximum Work
Orders set to 1.
Standard Item
The standard item that is being produced on the line.
This setting is used to derive a common unit of measure for item production when determining the
line’s production rate. It is also the default item for work orders created for this line.
To enter the standard item, see Entering a Standard Item (Line Configuration Setting) on page 69.
Batch Size
Required. The standard batch size used when producing items on the line. The default is 1.
Note: The batch size cannot be 0. If 0 is entered, it is automatically changed to the default value 1.
This setting is used when determining the line’s production rate. For additional information about how
batch size affects OEE results, see Understanding Batches and Lots for OEE on page 44.
The decimal place resolution of the batch size is controlled by the system paramet er Maximum
number of decimals for batch entry. For information about setting this parameter, see t he MES Client
User Guide or help.
Production Unit of Measure
The standard production rate unit of measure for items produced on the line. Th e default is
hours/batch.
This setting is used to derive a common unit of measure for item production when determining the
line’s production rate.
Parent Entity for Scheduling
The entity that is the parent of the line and from which the line and its entities inherit their shift
schedules.
Only entities that can schedule shifts or their descendants, which inherit the capability to schedule
shifts, are included in the list. Entities that are members of a line are not included in the list.
Line Spare 1–4
Boxes for entering custom information about the line.
Target OEE %, Target Perf %, Target Util %, Target Qual %
The target setpoints for KPI OEE, Performance, Utilization, and Quality for the line. These values are
indicated on the KPI gauges on the line’s Monitor tab by a tick mark at the outer edge of the gauge's
color band. See Viewing KPI Measures on page 116.
Values must be from 0 to 100.
Entering a Standard Item (Line Configuration Setting)

1. On the Add Line page, click Configure. The Standard Items dialog box appears.
2. To filter the list, see Filtering Item Lists on page 18.
3. Select the standard item.
4. Click OK.
For an explanation of how the item designation is derived, see Items and Item Classes on page 32.
Version 6.0 69
Editing a Line
Note: You cannot edit a line if a work order is currently running on it. For more information, see
Guidelines with Work Orders Creat ed from a Line on page 43.
1. On the home page, click the Lines tile. The Lines collection page appears.
2. Click the line you want to edit. The Work Orders tab appears.
3. Go to the Configuration tab to edit the line’s configuration settings (see Line Configuration Settings
on page 68), layout (see Configuring a Line’s Layout on page 70), or user group access (see
Assigning Line Access to Users on page 81).
For information about what happens to work orders and jobs when a line's layout is reconfigured, see
Line Layout Reconfiguration System Behavior on page 44.
Deleting a Line
Note: Deleting a line does not delete the entities that are members of the line.
Note: You cannot delete a line if a work order is currently running on it.
2. Click the line that you want to delet e. The Work Orders tab appears.
3. Go to the Configuration tab.
4. Click the Delete icon. A confirmation message appears.
Configuring a Line’s Layout

For conceptual information about lines and line layout, see Lines on page 32 and Line Layout on page
33.
1. Load the line for configuration either by creating the line (see Creating a Line on page 67) or
loading the line to edit it (see Editing a Line on page 70).
2. Click the line configuration Layout tab.
3. Optionally, use the filter box at the top of the Available Entities list to filter the list of entities.
The filter ent ry will persist when you leave and ret urn to this page. To clear the filter, click X.
4. Drag the entities in the Available Entitie s list onto the layout model. For an example layout and
description of the layout components, see Sample Line Layout on page 71. For examples of how to
add entities for various layout configurations, see the other topics in this s ection.
Note: A line with more than 50 line positions is not supported for calculating bad counts.
5. To save the layout, click Save.
70 Version 6.0
If you navigate away from the Layout tab, any changes that you made since last performing a Save
operation will be discarded.
Entities can be added to a layout according to the following guidelines:
 Only entities that have the following capabilities and settings can be added to a layout: can run jobs,
can capture utilization, can track OEE, have an OEE production rate defined, and have no more t han
one Job Exec (that is, it cannot have more than one job running at a time).
 A line’s parent entity cannot be added.
 An entity that is already a member of the layout cannot be added again.
Only entities that meet these guidelines will be included in the Available Entitie s list.
Note: An entity that is already a member of another line should not be added to a line. That is, an entity
should not be a member of multiple lines.
Sample Line Layout

The following figure shows a sample line layout and identifies layout tools and line components.
Entities available to be added to the lay out

Box on which to drop an entity at the start of the line
Box on which to drop an entity in parallel with entities above the box
Example of parallel entities
Example of line segments
Example of serial entities
Box on which to drop an entity at the end of the line
The list of available entities is determined by the following guidelines:
 Only entities that have the following capabilities and settings are included in the list: can run jobs, can
capture utilization, can track OEE, have an OEE production rate defined, and have no more than one
Job Exec (that is, it cannot have more than one job running at a time).
 The line’s parent entity and any entities that are already in the line layout are not listed.
Version 6.0 71
Inserting the Initial Entity

Drag an entity from the Available Entities list to the Drop Entity Here box.
The entity is added to the layout.
72 Version 6.0
Inserting an Entity at the Start of a Line

Drag an entity from the Available Entities list to the Add to Start box.
The entity is added to the start of the layout.
Version 6.0 73
Adding Serial Entities

Drag an entity from the Available Entities list to the entity that will precede it in the line.
The entity is added to the layout following the entity it was dropped on.
Inserting an Entity at the End of a Line

Drag an entity from the Available Entities list to the Add to End box.
74 Version 6.0
The entity is added to the end of the layout.
Adding Parallel Entities

Drag an entity from the Available Entities list to an Add in Parallel box.
The entity is added to the layout in parallel with ot her entities.
Parallel entities are listed in alphabetical order.
Version 6.0 75
Creating a Segment
Segments are parallel subpaths in the line. So you must first set up entities that are in parallel. When
creating parallel subpaths in a line, each subpath must contain the same number of entities.
1. Create a parallel structure that includes each of the entities that are at the start of the line segments.
2. Drag an entity from the Available Entities list to the parallel entity that it should follow in the line
segment.
76 Version 6.0
The entity is added to the line segment.
3. Drag another entity from the Available Entities list to the other initial parallel entity in the line
segment.
Version 6.0 77
The entity is added to that line segment.
4. Continue adding entities to each line segment as needed by dragging the new entity and dropping it
on the last entity in the line segment.
To add an additional line segment in parallel with the others, drag an entity to the Add in Parallel
box below the line segments. This will start another line segment to which you can add its entities.
Segments are ordered alphabetically according to the entities at the first position of the segments.
Therefore, changing the first entity in a segment could cause the segments to be reordered.
Moving an Entity in the Layout

Drag the entity to an Add box or to another entity.
Removing an Entity from a Line

Removing an entity does not delete the entity from the system. It only removes it from the current line.
1. Click the entity to be removed.
A menu appears.
2. In the menu, click Remove Selection.
Designating an Entity as the Production Source

You can designat e the entity in the line from which the line's production amount is to be derived. This
means that the good count comes from the designated entity's line position and the bad count comes
from the designated entity's line position and all preceding entities. Only one entity in the line can be
designated as the source of the line’s production amount. If no entity is specifically designat ed as the
production source, then the entity or entities in the last line position of the line are considered as the
production source for the line.
78 Version 6.0
If you select a parallel entity or an entity in a line segment, the production amount will include the items
produced by all entities at that entity’s line position.
To designate an entity as the production source
1. Click the entity to be designated as the production amount source for the line. A menu appears.
2. In the menu, click Set as the Source of Production Counts.
That entity is indicated to be the production source.
To remove the production source

 Perform one of the following actions:
 Select another entity as the production source.
 In the entity menu, click Unset a s the Source of Production Counts.
Manually Designating the Bottleneck Entity

You can manually designate the entity in the line that will be considered the line’s bottleneck entity. If the
designated entity is in parallel with other entities at the same line position, then all entities at that line
position are considered to be bottleneck entities. Only one line position can have entities that are
designated as the bottleneck entities.
Note: E ven if an entity is manually designated as the bottleneck entity, if it is not in a utilization reason
code that enables it, nothing will be returned when the system is queried for which entity is the
bottleneck. See Enabling the Entity When in a Running State on page 81.
To designate an entity as the bottleneck

1. Click the entity to be designated as the bottleneck entity for the line. A menu appears.
2. In the menu, click Is the Bottleneck.
3. That entity is indicated to be the bottleneck entity.
Note: When an entity is manually designated as the bottleneck entity, the Can be the Bottleneck setting
is removed from all of the other entities to which it was assigned. Also, the I s the Bottleneck setting is
removed if it was previously assigned to another entity.
Version 6.0 79
To remove the bottleneck designation from the entity

 Select another entity as the bottleneck.
 In the entity menu, click Is Not the Bottleneck.
Configuring the Automatic Determination of Bottleneck Entities

To ensure that the automatic determination of a line’s bottleneck entity can be performed properly, the
line and the line’s entities must be configured as follows.
Note: If the production rate for an entity cannot be det ermined, then the line’s performance rate and
bottleneck entity cannot be determined. Examples of this condition is an entity on which no job is running,
there is no upstream job source for the rate, and a default rate has not been defined for the entity.
Specifying Required Line Configuration Settings

Each of the following line configuration settings must have entries:
 Standard Item
 Batch Size
 Production Unit of Measure
These values are used to determine a common unit of measure for the item being produced by the line.
For more information, see Line Configuration Settings on page 68.
Making Sure That an Entity Is Not Manually Designated as the Bottleneck

If an entity in the line has been designat ed as the bottleneck, you must remove this designation. See
Manually Designating the Bottleneck Entity on page 79.
Specifying That the Line’s Entities Can Potentially Be a Bottleneck

Each of the entities in the line must be specified as potentially being a bottleneck.
To specify that an entity can potentially be a bottleneck
1. In the line’s Layout tab, click the entity.
A menu appears.
2. In the menu, click Can be the Bottleneck.
That entity can now potentially be the bottleneck entity.
To remove the designation that the entity can be the bottleneck designation
 In the entity menu, click Cannot Be the Bottleneck.
80 Version 6.0
Assigning the Required Capabilities to the Entities in the Line

All of the entities in the line must have the following capabilities:
 Can Schedule Jobs
 Can Run Jobs
 Can Capture Utilization
 Can Track OEE (because the entity’s default production rate is specified in its OEE settings)
See Configuring Entity Basic Information and Capabilities on page 59.
Specifying Required Entity OEE Configuration Settings

Each of the entities in the line must have entries for the following settings:
 Default Production Rate
 Default Batch Size
 Default Standard Item
These values are us ed to determine the entity’s production rate if it is not currently running a job and
there are no jobs for this entity in any upstream work orders.
See Configuring OEE Default Data on page 66.
Enabling the Entity When in a Running State

If an entity is disabled and it is the only entity in that line position, then a production rate for it will not be
determined. Therefore, the line’s production rate and bottleneck entity cannot be determined. For this
reason, make sure that, for utilization reasons that will be used when the entity is producing items, the Is
entity enabled when this reason applies? check box is selected. See Configuring Utilization Reasons
on page 55.
Assigning Line Access to Users

To interact with work orders and jobs that are running on a line, users must be assigned access to the
line. Access is assigned at the user group level. For information about configuring MES user groups and
assigning us ers to them, see the MES Client User Guide or help.
Version 6.0 81
To assign line access to user groups

1. On the Line s collection page, click the line, click the Configuration tab, and then click the Line
Acce ss t ab. The MES user groups are listed in the tab.
2. Select the check boxes for the user groups who require access to the line.
Note: Anytime you change line access settings, press F5 to refresh the browser so that the proper line
tabs are displayed to reflect your changes.
82 Version 6.0
C HAPTER 4
MES Web Portal Operations
In This Chapter
Operations Overview .................................................................................................................... 83
What Operations Can Be Performed .............................................................................................. 83
Viewing Line Summary Information ................................................................................................ 84
Working with Work Orders ............................................................................................................. 85
Viewing a Line's Work Order Status ............................................................................................... 89
Viewing the Status of a Line's Entities ............................................................................................ 92
Entering Production Quantity for a Running Job .............................................................................. 97
Starting and Ending Jobs ............................................................................................................ 100
Marking a Job as Complete ......................................................................................................... 101
Working with an Entity's Utilization E vents .................................................................................... 102
Monitoring Entity OEE ................................................................................................................. 108
Monitoring Line OEE ................................................................................................................... 113
Operations Overview
You can ent er transactional data to the system through the various pages of the MES Web Portal.
Depending on your privileges and line access permissions, you can create work orders, transact against
the work orders and jobs wit hin the work order, view line and entity status, enter and modify downtime
events, and complete jobs.
A typical workflow, whic h could involve more than one user, is:
1. Create a work order on a line. (If the work order comes from an external system such as an ERP, t he
work order can be assigned to a line.)
2. Move a work order from one line to anot her line if, for example, an equipment failure occurs or work
priority has changed.
3. Start a work order and/or the jobs within the work order.
4. Add and/or reduce production for a job running on an entity.
5. Add, split, or modify equipment downtime events on an entity.
6. Complete a job running on an entity.
What Operations Can Be Performed

Operators and ot her MES Web Portal users can view status information about:
 Work orders (see Viewing a Line's Work Order Status on page 89)
 A line’s bottleneck entity (Viewing Bottleneck Information on page 97)
 Jobs that are in an entity's work queue (see Viewing Jobs in an Entity Work Queue on page 94 and
Viewing Det ailed Job Information on page 91)
 Production (see Ent ering Production Quantity for a Running Job on page 97)
 Entities (see Viewing the Status of a Line's Entities on page 92)
Version 6.0 83
MES Web Portal User Guide MES Web Portal Operations
 Utilization events (see Viewing an Entit y’s Event History on page 102)
Operators can also:
 Start and end jobs (see Starting and Ending Jobs on page 100)
 Add or reduce production for a job (see Entering Production Quantity for a Running Job on page 97
and Reducing Production Quantity on page 100)
 Mark jobs as complete (see Mark ing a Job as Complete on page 101)
 Add, merge, or split an entity’s events (see Work ing with an Entity's Utilization Events on page 102)
Access to viewing information or performing operations starts at the Home page, shown below. The
procedures in the topics referenced in the previous bullet list provide det ailed steps for navigating to the
appropriate pages.
Viewing Line Summary Information
A line's pages include the following summary information at the upper right of the page:
 The line's default production rate.
 The line's default batch size.
 The line's standard item, if one has been specified.
 The line's bottleneck entity, if one can be determined. If you have permission to edit entities or you
have been assigned access to the entity, the entity name will be a hyperlink that will navigate to the
entity's detail page.
 If a job is currently running on the line, the current utilization reason.
Note Icon in Line Summary Information

If any of the data reported in the line summary information cannot be determined by the system, then a
Note icon will appear in that block of information, as shown below.
84 Version 6.0
MES Web Portal Operations MES Web Portal User Guide
To see the reason why the data could not be determined, hover the cursor over the message icon. A tool
tip appears with an explanation of the issue.
Working with Work Orders

You can create work orders and assign them to a line.
Creating a work order in MES Web Portal and assigning it to a line also creates the necessary data entry
jobs for all entities associated with the line. Unlike work orders created using MES Client and worked
using MES Operator, there is no correlation to a proc ess and therefore no concept of a bill of material.
There is only the produc ed item of the work order and the quantities (starting and required).
Once created, you can change the status of a work order (for example, from Ready to Running; see
Changing a Work Order's Status on page 86). You can also reassign a work order to another line (s ee
Reassigning a Work Order to Anot her Line on page 88).
Creating a Work Order

To create a work order and assign it to a line
1. On the Work Order collections page or on the line's Work Orders tab, click the Add
Work Order icon in the action bar.
The Create Work Order for a Line dialog box appears.
2. Specify the parameters for the work order:
Version 6.0 85
Work Order ID
The work order ID uniquely identifies the work order in the system.
Item
The item that is being produced for the work order. Click the Configure button to display the list of
items from which to choose.
To filter the item list in the item selection dialog box, see Filtering Item Lists on page 18.
If you created the work order from the line's Work Orders tab, the line's standard item is selected by
default.
Starting Quantity
The starting quantity is the quantity that the work order is expected to produce if there is no rejected
production (t hat is, if all production is good).
The value entered here sets the starting quantity of each of the jobs at the first entity position of the
line. If there is more than one entity at the first line position, the starting quantity is equally divided
among the jobs. The starting quantities for each downstream job in t he line is calculated using this
starting quantity and taking into account the good and rejected production reported for upstream
jobs.
The number of decimal places are set according to the selected item. The maximum value that can
be ent ered is 999,999.
While the unit of measure (UOM) for items being produced at line positions might be different,
starting quantities on MES Web Portal pages are always shown in the UOM specified for the line.
Required Quantity
The required quantity is the quantity of the line's items that are required by the work order.
The value entered here sets the quantity required to be produced by the line’s designated production
position.
If the The required quantity must be produced to end a job job setting is being used for entities in the
line, the required quantities for each upstream and downstream job in the line is determined using
the required quantity entered here at each line position and dividing it equally among the entities at
each position.
The number of decimal places are set according to the selected item. The maximum value that can
be ent ered is 999,999.
While the UOM for items being produced at line positions might be different, remaining quantities on
MES Web Portal pages are always shown in the UOM specified for the line.
Line
The line to which this work order will be assigned.
If you are adding the work order with the line's Work Orders tab displayed, the line is automatically
selected and cannot be changed.
Status
The work order status. When creating a work order, the status defaults to New and cannot be
changed.
3. When you are finished specifying the work order details, click Save.
The work order is added to the list of work orders that are assigned to the line.
Changing a Work Order's Status

You can change a work order's status. For example, to start running a work order, you would change its
status from Ready to Running.
86 Version 6.0
For the effects of changing a work order's status on the state's of the work order's jobs, see Effects of
Work Order Status Changes on Job States on page 42.
To change the status of a work order
1. Initiate the change from one of the followi ng web pages:
 On the Work Order collections page or on a line's Work Orders tab, click the Edit Work
Order icon on the tile of the work order you want to edit.
 On the work order's detail page, click the Edi t Work Order icon in the action bar.
The Edit Work Order dialog box appears.
2. Select the desired status in the Status list.

After selecting a different status, the Apply and Save buttons appear in the dialog box.
3. Click Save.
Note the following restrictions when changing a work order's status:
 You cannot change the status from Completed to Suspended, Canceled, or On Hold.
 You cannot change the status to New if there is any production recorded against any of the jobs in
the work order.
 You cannot change the status from Completed to Ready or Running if all the jobs have production
reported for them.
Version 6.0 87
Reassigning a Work Order to Another Line

In certain situations, it is necessary to reassign a work order to another line. This could happen when one
line has equipment failure and the work order has to be moved to another line for immediate completion.
The system allows for reassigning work orders that are not running to another line even if there have
been some units already produced against the work order.
When reassigning a work order, all the existing jobs are deleted and new jobs are created. Existing
production data is retained. For additional background information about reassigning a line, refer to Work
Order Reassignment on page 41.
To reassign a work order to another line
1. Initiate the change from one of the following web pages:
 On the Work Order collections page or on a line's Work Orders tab, click the Edit Work
Order icon on the tile of the work order you want to edit.
 On the work order's detail page, click the Edi t Work Order icon in the action bar.
The Edit Work Order dialog box appears.
2. Select New in the Status list.

You can also select Ready, Suspended, or Onhold, but then you have to click Apply to make the
line list available.
3. In the line list, select the line to which to reassign the work order.
The starting and required quantities are updated based on the production that has already been
reported for the work order, to reflect just the amounts that need to be produced on the new line.
Also, the work order status is automatically changed to New.
88 Version 6.0
4. Modify the start and required item quantities for the work on the new line as needed.
5. Click Apply or Save. The work order is moved to the collection page of the line to which you
reassigned it.
Deleting a Work Order

If a work order has any status except Running, it can be deleted.
To delete a work order
 On the work order's details page, click the Delete icon. A confirmation message appears.
Work Order Deletion Behavior
If you delete a work order, the work order and its jobs are deleted from the database. However, any
production that has been entered for the work order is not delet ed. Production history is maintained as it
might be required, for example, for rec all purposes.
Therefore, if a work order that had production reported against it is deleted, its production will still be
included in the Total Production Count on the line Monitor page, even though it will not be included in the
Word Orders in Period list.
Also, if a new work order is using the same work order ID as a deleted work order, any production that
was reported against the old deleted work order will be associated with the new work order. For this
reason, unless you are reinstating a work order that was deleted by mistake, you should avoid reusing
work order IDs of delet ed work orders.
To remove all information associated with a work order, including related production history, use the
Purge function in MES Client instead of the Delet e function described here.
Viewing a Line's Work Order Status

To view a work order’s status
2. Click the line whose work order you want to track.
Version 6.0 89
The line's Work Orders tab appears, listing all of the work orders that are assigned to the line.
The work order tiles shown in this tab includes summary quantity data about the work order and the
work order status. They also include a Progre ss chart, which shows:
(Qty Produc ed + Qty Rejected)/Qty Required
3. To view more detailed tracking information, click the work order tile.
The work order’s detail page appears. This page includes summary information about the work order
at the top of the page, and a Jobs grid below that lists all of the jobs in the work order.
From this page, you can:

 View detailed information about each job by clicking the job's Operation ID or S equenc e Number link.
See Viewing Detailed Job Information on page 91.
 Navigate to the entity on which a job is running or scheduled to be run by clicking the link in the
Running On or Scheduled To column.
 Navigate to the line to which the work order is assigned by clicking the Line Assignment link in the
summary information.
90 Version 6.0
Work Order Status Not Able to Be Shown

For work orders created from a process, if a unit of meas ure (UOM) conversion has not been defi ned
between any of the items created by the work order's jobs and the item made by the work order, status
information will not appear on the work order tile. Instead a message appears that indicates that the work
order status cannot be determined due to UOM conversion issue.
In the Units of Measure module in MES Client, make sure that a UOM conversion exists between each
item being produced by the work order's jobs and the item being produced by the work order.
Viewing Detailed Job Information

To view detailed information about a job
In the Jobs grid on the work order’s detail page, click the job’s Operation or Sequence Number link. The
job’s detail page appears.
The page includes Job Detail information, and the Production Hi story grid.
In the Job Detail information:
 The job's required quantity is determined using the required quantity entered for the line's designated
production position.
 The job's remaining quantity is the starting quantity at this production position minus the production
(good and rejected) that has been reported at this production position.
 The job's starting quantity is calculated from the work order's starting quantity minus any good or
rejected production that has occurred at upstream jobs.
 If t here is more than one entity at this position, the job required, remaining, and starting quantities are
equally divided among the jobs at this position.
 While the unit of measure (UOM) for items being produced at line positions might be different, item
quantities on MES Web Portal pages are always shown in the UOM specified for the line.
For a description of the Production Hi story grid columns, see Production History Grid Column
Descriptions on page 92.
From the job’s detail page, you can also:
 Navigate to the entity’s Utilization tab by clicking the Entity link in the Job Detail area.
 Add production quantity to a job by clicking the Add Production icon on the action bar. See Entering
Production Quantity for a Running Job on page 97.
 Reduce the production of one of the job’s quantity entries by clicking the Reduce Production icon
on the action bar. See Reducing Production Quantity on page 100.
Version 6.0 91
Production History Grid Column Descriptions

Created Date
The date and time that the production was recorded if the system settings Maint ain distinct good
production records and Maintain distinct reject production records are selected (in MES Client).
Otherwise, this is the date and time that production is first rec orded.
By default, the grid is sorted by descending created date.
Shift
The shift during which the item was produced.
Quantity
The quantity of the produced item that was added.
UOM
The unit of measure for the item that was produced.
Item Reason
The reason that was assigned to this production of the item.
Navigating to the Assigned Line Details

To navigate back to the line details from the work order’s detail page
 Click the Line Assignment link on the work order detail page.
Viewing the Status of a Line's Entities

1. On the home page, click the Lines tile.
The Line s collection page appears.
2. Click the line whose entity status you want to track.
The Work Orders tab of the line’s page appears.
92 Version 6.0
3. Click the Entitie s tab.
The Enti ties tab includes a tile for eac h entity in the line. If the entity has an active job, the job information
is displayed on the tile. Also, the color of the banner at the bottom of the tile indicates the entity’s current
utilization state.
Entity Tile Functions
Each entity tile includes icons and a link for:

Adding an event. See Editing an Event on page 104.
Navigating to the work order whose job is currently running on the entity.
Marking the job as Complete. See Mark ing a Job as Complete on page 101.
Adding production. See Entering Production Quantity for a Running Job on page 97.
You can also navigate to the entity’s detail page by clicking the entity tile.
Version 6.0 93
Viewing Entity Summary Information
The entity detail page includes the following summary information at the upper right of the page:
 The entity's default batch size.
 The entity's default production rate.
 The entity's standard item, if one has been specified.
 If the entity is assigned to a line, the name of the line. If you have permission to edit lines or you have
been assigned access to the line, the line name will be a hyperlink that will navigate to the line's detail
page.
 If a job is currently running on the entity, the ID of the job's work order. The work order ID is a
hyperlink that navigates to the work order's detail page.
Viewing Jobs in an Entity Work Queue

To view the jobs in an entity's work queue
1. Display the entity's detail page using one of the following methods:
 On the home page, click the Entitie s tile, then click the tile of the entity whose jobs you want to
view.
 Navigate to the entity tile via the Line s tile (see Viewing the Status of a Line's Entities on page
92) and click the entity tile.
The entity’s detail page appears.
2. Click the Work Queue tab.
Tiles for each job in the entity's work queue are listed on the left.
The job tile shows the operation, item quantity information related to the job, and the current state of
the job.
3. To view a job’s details and production history, click the job tile.
94 Version 6.0
The Job Detail information and Production Hi story grid appear.
In the Job Detail information:

 The job's required quantity is determined using the required quantity entered for the line's designated
production position.
 The job's remaining quantity is the starting quantity at this production position minus the production
(good and rejected) that has been reported at this production position.
 The job's starting quantity is calculated from the work order's starting quantity minus any good or
rejected production that has occurred at upstream jobs.
 If t here is more than one entity at this position, the job required, remaining, and starting quantities are
equally divided among the jobs at this position.
 While the unit of measure (UOM) for items being produced at line positions might be different, item
quantities on MES Web Portal pages are always shown in the UOM specified for the line.
For a description of the Production Hi story grid columns, see Production History Grid Column
Descriptions on page 92.
Filtering the Jobs Queue
You can filter the list of tiles in the Job Queue.
1. Click the Filter icon at the upper right corner of the Job Queue list.
Version 6.0 95
The Filter dialog box appears.
2. Enter the filter criteria and click Filter.
Note: Clicking Default restores the filter default settings.
The Job Queue list is filtered and the filter for the page is saved.
Other Operations
From the Work Queue tab, you can also:
 Navigate to the entity’s Utilization tab and other entity tabs by clicking the Entity link in the Job
Detail area.
 Add production quantity to a job by clicking the Add Production icon on the action bar. See Entering
Production Quantity for a Running Job on page 97.
 Reduce the production of one of the job’s quantity entries by clicking the Reduce Production icon
on the action bar. See Reducing Production Quantity on page 100.
 End the job by clicking the End Job icon on the action bar. See Starting and Ending Jobs on page
100.
96 Version 6.0
Viewing Bottleneck Information

A line's bottleneck information is displayed at the top of its line pages, as shown below. In addition, the
entity that is the bottleneck is indicat ed by the Bottleneck icon on its tile on the line's Entities tab. If
there are parallel entities at the bottleneck position, each entity will include the icon.
If the bottleneck cannot be determined by the system, then a Note indicator appears in the Bottleneck
position of the line summary information, as shown below.
To see why the bottleneck cannot be determined, hover the cursor over the message icon. A tool tip
appears that explains the issue.
Entering Production Quantity for a Running Job

As items are being produced by a currently running job on an entity, you can enter the production
quantity.
To add a production quantity
1. Navigate to the job:
Version 6.0 97
 Navigate to the Entitie s tab of the line of which the entity is a member (see Viewing the Status of
a Line's Entities on page 92) and click the Add Production icon on the entity’s tile, to the
right of the Quantity information.
 Navigate to the job’s det ail page from the work order's detail page (see Viewing Detailed Job
Information on page 91) and click the Add Production icon on the action bar.
 Navigate to the job's detail page from the entity’s Work Queue tab (see Viewing Jobs in an
Entity Work Queue on page 94) and click the Add Production icon on the action
bar.
The Add Production dialog box appears.
2. Enter the production quantity and the corresponding production information. See Add Production
Quantity Settings on page 98.
3. To save the entries, click Add Production.

The production amount shown for the job is updated. Also, the new production is added as an entry
in the Production Hi story grid (see Viewing Detailed Job Information on page 91 or Viewing Jobs in
an Entity Work Queue on page 94).
Add Production Quantity Settings

The Add Production dialog box includes the following settings.
Production Type
The type of production being added.
98 Version 6.0
Good production is added to the quantity produced. Rejected production is added to the quantity
rejected. These quantities are used to determine the quality component of OEE.
The selected production type affects the set of reasons available in the Production Reason list.
Quantity
The amount of produced items to add.
Production Reason
The reason assigned to this production of the item.
Item ID
The unique ID of the item bei ng produced.
The list will include multiple items if the job can produce items in addition to the standard item, such
as substitutes or byproducts.
If you select another item ID, the Item Description selection is updated accordingly.
Item Description
The description of the item being produced.
The list will include multiple items if the job can produce items in addition to the standard item, such
as substitutes or byproducts.
If you select another item description, the Item ID selection is updat ed accordingly.
Lot Number
The lot number for the item being produced.
This can only be set if, in MES Client, the May create new lots option has been selected for the job
bill of mat erial (B OM) for the selected item.
To Storage Location
The storage entity to which items produced by this entity are sent.
This can only be set if, in MES Client, the May choose alternate inventory location option has
been selected for the job BOM for the selected item.
Created At
The date and time when the quantity was added:
o Current Time: The current date and time is used.
o Earlier in Current Shift: Use the calendar and time widgets to enter the earlier time when the
quantity was produced.
Note: If "No Shift" is displayed with this choice, there is no current shift. For example, if there are
no shifts over the weekend, the shift description used to specify time on Saturday or Sunday is
"No Shift".
o During the Previous Shift: Use the calendar and time widgets to enter the time in the previous
shift when the quantity was produced.
Note: If the entity does not have a shift schedule, then this list is unavailable because there are
no current or previous shifts. Production will be added using the current time.
Unless both of the system settings Maintain distinct good production rec ords and Maintain distinct
reject production records are selected (in MES Client ), the Created At data and time for production
with the same production reason, item, lot, and storage location will always be the first t ime an entry
for that production was recorded.
Version 6.0 99
Reducing Production Quantity

You can reduce production quantity from a quantity entry made for an entity and job.
To reduce the amount of production quantity from a quantity entry
1. Display one of the Production Hi story grids in the system using one of the following methods:
 Navigate to the job’s Information tab from the work order's detail page (see Viewing Detailed
Job Information on page 91).
 Navigate to the Job Detail panel from the entity’s Work Queue tab (see Viewing Jobs in an
Entity Work Queue on page 94).
2. In the Production Hi story grid, select the production record to reduce and click the
Reduce Production icon on the action bar.
The Reduce Production dialog box appears. You can check the information in this dialog box to
make sure that you are reducing the quantity of the correct item.
3. In the Quantity box, enter the amount by which to reduce the quantity.
The reduced quantity cannot exceed the current quantity, which is displayed to the right of the box.
4. To reduce the quantity, click Reduce Production.
Starting and Ending Jobs

You can start and end a job. Note that ending the job is the same as marking it as Complete.
To start or end a job on an entity
1. Display the job using one of the following methods:
 Navigate to the job’s Information tab from the work order detail page (see Viewing Detailed Job
Information on page 91).
 Navigate to the Job Detail panel from the entity’s Work Queue tab (see Viewing Jobs in an
Entity Work Queue on page 94).
100 Version 6.0

If the job is not running, a Start Job icon appears in the page’s action bar. If the job is running, an
End Job icon appears.
2. Click the Start or End Job icon.
Marking a Job as Complete

When the job on the entity is finished, you can mark it as Complete. Note that marking a job as Complete
is the same as ending the job.
To mark a job as Complete
1. Navigate to the line’s Entitie s tab:
a. On the home page, click the Lines tile.
b. Click the line of which the entity is a member.
c. Click the Entitie s tab.
2. On the entity tile, click the Complete icon.
3. A confirmation message appears. Information about the job that is currently running on the entity is
included, such as the work order ID, operation ID, and sequence number.
4. Review the c urrently running job information in the message to verify that this is the job that you want
to mark as Complete.
Version 6.0 101

5. To confirm marking the job Complete, click OK. The state of the job changes from Running to
Complete.
Working with an Entity's Utilization Events

You can view an entity’s event history (see Viewing an Entity’s Event History on page 102).
You can also:
 Add events (see Adding an Event on page 104)
 Edit events (see Editing an Event on page 104)
 Split events (see Splitting an E vent on page 106)
 Merge events (see Merging an Event with an Adjacent Event on page 108)
Viewing an Entity’s Event History

1. On the home page, click the Entitie s tile. The Entitie s page appears.
2. To filter the entities list, see Filtering Entities on the Entities Collection Page on page 15.
3. Click the entity tile.
That entity’s page appears.
4. Click the Utilization Events tab.
The Utilization Events tab includes the entity’s current event status and the Event Hi story grid (see
Entity Current Event Status on page 102 and Event History Grid Column Descriptions on page 103).
Work Order ID Not Appearing for an Event

The MES Service minut ely task updates the duration and job information for utilization events every
minute. However, if a job is started and stopped (paused or completed) within the minute bet ween the
updates, the job information is lost (because the MES Service sees the job duration as 0 and assumes it
did not occur).
If this occurs, the work order ID for the utilization event in the Event Hi story grid will be blank.
Entity Current Event Status

The following current event status information appears at the top of the entity Utilization tab.
Current State
The utilization state associated with the current utilization reason.
102 Version 6.0

Current Reason
The utilization reason assigned to the current event.
Duration
The duration of the current event.
Standard Time
The standard amount of time that the entity is expected to be in this utilization reason.
Percent of Standard Time
A bar that indicat es the perc entage of the event duration relative to the standard time for the
utilization reason. The bar is green if the standard time, if defined, has not been exceeded. If the
defined standard time is exceeded, the bar turns red.
This information is not available if the standard time for the utilization reason has not been specified.
Event History Grid Column Descriptions

Work Order ID
The ID of the work order that was running during this event. If more than one work order ran during
this event, only one of their IDs is displayed.
Note: The MES Service minutely task updates the duration and job information for utilization events
every minute. However, if a job is started and stopped (paused or completed) within the minute
between the updates, the job information is lost. If this occurs, the work order ID for the utilization
event will be blank.
Start Time
The start time of the event. For events that started before the current shift, this is the actual start time
and not the start of the shift.
Utilization State
The utilization state associated with the current utilization reason. The utilization state det ermines
the color associated with the utilization reason.
Reason Group
The reason group of the current utilization reason.
Reason Description
The utilization reason assigned to the event.
End Time
The end time of the event.
Duration
The total duration of the event. For events that started before the current shift, this is the actual
duration and not just the duration from the start of the shift.
Severe
Indicates whether the event’s Severe flag has been set. The Severe flag is set if the duration of the
event has exceeded that utilization reason’s maximum duration setting, indic ating that the entity
condition is severe.
Standard Time
The standard amount of time that an event is expected to be in the utilization reason.
Shift
The shift during which the event occurred.
Comments
Comments entered by the operator about the event.
Version 6.0 103

Adding an Event
You can add an event to an entity to indicate that its operating condition has changed.
To add an event
1. Navigate to the entity’s Utilization tab (see Viewing an Entity’s Event History on page 102).
2. Click the New Event icon on the action bar. The New Event dialog appears. The reasons
that can be used with this entity are displayed in the utilization reason tree (see Specifying the
Utilization Reasons That Can Be Used with an Entity on page 65).
3. Select the reason for the event from the tree.
 You can expand all of the reason groups for a given reas on group in the tree. Select the reason
group, then click the expand icon (highlighted below) that appears above the tree.
 You can use the filter box above the tree to filter the reasons that are listed. Enter the filter crit eria
and press the Enter key. To clear the filter, click the X icon.
 You can navigate the reason groups and reasons in the utilization reason tree using the arrow
keys. Select the currently highlighted reason by pressing the Enter key.
After selecting a reason, the Comments box appears.
4. Optionally, enter a comment about the new event.

5. Click OK. The event is added to the Event Hi story grid.
When a new event is added, the previous event is ended.
Editing an Event
You can edit an existing event for an entity.
To edit an event
1. Navigate to the entity’s Utilization tab (see Viewing an Entity’s Event History on page 102).
104 Version 6.0

2. In the Event Hi story grid on the Utilization tab, select the event and then click the Edit
Event icon on the action bar. The Edit Event dialog box appears.
3. To save your changes, click the Save button.

In the Edit Event dialog box, you can:
 Reclassify the event by changing the reason in the Utilization Reason tree. All utilization reasons
are shown in this tree.
 You can expand all of the reason groups for a given reason group in the Utilization Reason
tree. Select the reason group, then click the expand icon (highlighted below) that appears above
the tree.
 You can use the filter box above the tree to filter the reasons that are listed. Enter the filter crit eria
and press the Enter key. To clear the filter, click the X icon.
 You can navigate the reason groups and reasons in the Utilization Reason tree using the arrow
keys. Select the currently highlighted reason by pressing the Enter key.
 Split the event (see Splitting an Event on page 106).
 Merge the event with an adjacent event (see Merging an Event wit h an A djacent Event on page 108).
 Modify the event’s comments.
Version 6.0 105

Splitting an Event
You can split an event so that the new event is added either before or after the event that is being split.
To split an event
1. In the Edit Event dialog box, click either Split Next or Split Previous.
2. Reclassify one of the split events by selecting that event and then changing the reas on in the
Utilization Reason tree. All utilization reasons are shown in this tree.
Splitting an event has the following effects:
 For Split Previous, the new event’s start time will be the source event’s start time.
 For Split Next, the new event’s end time will be the sourc e event’s end time.
 The new event will default to the same reason and comment as the source event.
 The duration of both events will default to half the original duration of the source event.
To change the durations of the split events
 If Split Next was chosen, select the new next event, and use the hour, minutes, and seconds
buttons in the Event Start cont rol to change its start time. Note that the end time of the new
previous event will change as well, matching the new start time of the next event.
106 Version 6.0

 If Split Previous was chosen, select the new previous event, and use the hour, minutes, and
seconds buttons in Event End control to change its end time. Note that the start time of the new
next event will change as well, matching the new end time of the previous event.
The hours (-h, h) or minutes (-m, m) buttons might not appear in the Event Start or Event End
controls, depending on the duration of the event. For example, in the previous screens the hours
buttons do no appear because the duration of the original event is less than an hour.
To understand how changing an event’s start and end time works, consider the time changes to an event
as shown in the following diagram.
Version 6.0 107

Merging an Event with an Adjacent Event

If you determine that an event is actually a continuation of the event before or after it, you can merge the
two events by making their utilization reasons match.
To merge an event with an adjacent event
 In the Edit Event dialog box, select the reason that matches the next or previous event. The events
will be merged when the event is saved. The duration of the merged event will equal the duration of
the two source events, as shown in the following diagram.
The system might be configured such that the comments of the events being merged must match to
allow t he merge to occur. If this is the case, edit the comment so that it matches the comment of t he ot her
event.
The system might also be configured such that the raw reason codes of the events being merged must
match to allow the merge to occur. For a complete explanation of the restrictions regarding when events
can be merged, see Merging Events on page 47.
Note: This merging of events with the same reasons (and comments and raw reason codes, potentially)
means that if a utilization reason is split, and nothing about it is changed, the new event will aut omatically
be merged with the event from which it was split when saved. So, it will appear as if the splitt ing did not
happen. To avoid this, when splitting the event, you should change the reason (or possibly the
comments) of the new event before saving it.
Monitoring Entity OEE

An entity's OEE information is displayed on the entity's Monitor tab.
108 Version 6.0

The Monitor tab includes the following reporting areas:

 Reporting Period
 Currently Running Jobs
 Utilization Counts or Durations
 KPI
The dat a on the Moni tor tab is refreshed according the Auto Refresh rate (if the Aut o Refresh setting is
selected; see Information Data Refresh) or if the reporting period is changed.
Navigating to an Entity’s Monitor Tab

The entity’s performance information appears on its Monitor tab.
You can navigate to the Monitor tab in the following ways:
If you know that the entity is running jobs in the current shift
 On the Entitie s collection page, click the entity tile, then click the Monitor tab.
If you know that a work order is running
1. On the Work Orders collection page, click the work order tile. The work order's detail page appears.
The entities that are running jobs are listed in the Running On column of the Job grid.
2. Click the entity name link to open the entity, then click the Monitor tab.
If you know that a line is actively running work orders
1. On the Line s collection page, click the line tile.
2. Perform one of the following actions:
 On the Work Orders tab, click the tile of the work order of interest and proceed as desc ribed
above for "If you know that a work order is running".
 On the Entitie s tab, click the entity of interest and then click the Monitor tab.
Scrolling Through Data on the Entity Monitor Tab

If there is more data than can fit in either the Currently Running Jobs or KPI panels, use the scroll arrows
that appear to scroll through the data.
Setting the Reporting Period

To set the reporting period for the OEE information displayed in the Monitor tab
 Click the Reporting Period filter box and select the reporting period.
Version 6.0 109

The available periods are:

 This Hour.
 Last N Hours. If you select this option, enter the number of hours (from 1 to 24) in the accompanying
box and press the Enter key. Entering 1 hour here is equivalent to the This Hour time period. The
entry defaults to 1 or to the value saved in cache if one was saved.
 Current Shift.
 Previous Shift.
 Current Day.
 Yesterday.
If you change the reporting period, the content on the Monitor tab updates to reflect the dat a for that
reporting period.
Viewing Currently Running Jobs
Each currently running job appears in the Currently Running Jobs panel. This allows you to see the
production counts that were used to determine the Quality KPI measure.
Each job ent ry includes the following information:
 The ID of the job's work order
 The ID of the job's operation
 The total production count for the job, and the Good and Rejected production counts in parentheses
To view additional job information
 Click anywhere on the job entry.
The additional job information appears. It includes a work order ID link to the job's work order and an
operation ID link to the job details page.
110 Version 6.0

Viewing Uilization State Information

You can view eit her the counts or duration of an entity's utilization states, reason groups, or reasons on
the Counts/Duration Pareto graph.
The graph is refreshed whenever a change in the utilization state, reason group, or reas on is det ected for
the entity from the MES database.
To toggle between the two viewing modes
 Click the graph’s Show Duration/Show Counts button.
To drill down into the count or duration information
 Click a bar in the graph.
The drill-down sequence of information is:
1. Utilization states (the initial display, shown above)
2. Reas on groups for the selected utilization state:
Version 6.0 111

3. Reas ons for the selected reason group:
To move back up in the drill-down sequence
 Click the Back icon to the left of the graph title.
Viewing KPI Gauges

The KPI gauges indicate the OEE, Performance, A vailability, and Quality measures for the entity.
The gauges are driven by the following calculations:

 OEE = Performance x Availability x Quality
 Performance = Total Production Count / Predicted Count for the Entity
where Total Production Count = Good Production Count + Rejected Production Count
 Availability = Entity Runtime / Entity Available Time
 Quality = Good Production Count / Total Production Count
where Total Production Count = Good Production Count + Rejected Production Count
For more information about how the gauge data is determined, see the topics in OEE on page 47.
The gauges include the following status indicators:
 Three zones—red, yellow, and green—to indicate the relative status of the KPI measurement.
Note: For the current release, the zone values are fixed at 20% and 80%.
 A tick mark at the outer edge of the gauge's color band that points to the target value for that
measurement type as configured for the entity. To configure the target values for an entity, see
Configuring Default Utilization Reasons for Standard Events on page 64 and Configuring OEE
Default Data on page 66.
 The pointer that indicates the current value.
112 Version 6.0

 A text readout of the current value. Note that the pointer will never go beyond 100%. However, if the
measurement exceeds 100%, the actual value will be display ed in this text readout.
If there is no OEE-related data for the selected time period, then Performance, A vailability, and Quality
will be 100%, and so OEE will be 100%. If the OEE metrics are actually 0, then OEE will be 0.
Monitoring Line OEE

A line’s OEE information is displayed on the line’s Monitor tab.
The Monitor tab includes the following reporting areas:

 Reporting Period
 Period Summary
 Work Orders in Period
 Utilization Counts or Durations
 KPI
 Item Production for Period
The dat a on the Moni tor tab is refreshed according the Auto Refresh rate (if the Aut o Refresh setting is
selected; see Information Data Refresh) or if the reporting period is changed.
Version 6.0 113

Scrolling Through Data on the Line Monitor Tab

If there is more data than can fit in either the Work Orders in Period, KPI, or Item Production for Period
panels, use the scroll arrows that appear to scroll through the data.
Setting the Reporting Period

To set the reporting period for the OEE information displayed in the Monitor tab
 Click the Reporting Period filter box and select the reporting period.
The available periods are:

 This Hour.
 Last N Hours. If you select this option, enter the number of hours (from 1 to 24) in the accompanying
box and press the Enter key. Entering 1 hour here is equivalent to the This Hour time period. The
entry defaults to 1 or to the value saved in cache if one was saved.
 Current Shift
 Previous Shift
 Current Day
 Yesterday
If you change the reporting period, the content on the Monitor tab updates to reflect the dat a for that
reporting period.
Viewing Summary Information for the Period
The Period Summary panel includes the following information.

Production Source s
The entities on the line that are currently configured as the production count sources. Clicking an
entity name will navigate you to the entity’s Configuration tab. For how the line’s production source
entity is specified, see Designating an Entity as the Production Source on page 78.
114 Version 6.0

Utilization Sources
The entities that were utilization data sources during the selected time period. If more than one entity
is shown, they are display ed in time order of when the entity first appeared as a bottleneck in the time
period.
Clicking an entity name will navigate you t o the entity’s Configuration tab. For an explanation of how
the entities are determined to be utilization data sources, see Availability on page 48.
Total Production Count
The line’s total production count for the selected time period. The Good and Rejected production
counts are shown in parent heses. For an explanation of how the Good and Rejected production
counts are determined, see Quality on page 48.
The entities shown as production and utilization sources are listed in the order in which they were
bottlenecks for the line during the selected time period.
Viewing Work Order Information
Each work order that produced items during the selected time period appears in the Work Orders in
Period panel. If a work order produced no items or only rejected items, it will not be listed.
Each work order entry includes the following information.
 The work order ID
 The total production count in the time period, with the Good and Rejected production counts in
parentheses
To view additional work order information
 Click anywhere on the work order entry.
The additional work order information appears. It includes a work order ID link to the work order's
page.
Version 6.0 115

Viewing Utilization Counts and Durations
On the Utilization Counts/Duration Pareto graph, you can view either the counts or duration of the
utilization states, reason groups, or reas ons for the bottleneck entities in the line that were used for OEE
calculations.
Note that if there are parallel entities involved in a bottleneck position during the selected time period,
then the sum of the durations for all the events will be greater than the time period duration.
Also, events for an entity that are immediately adjacent to the period during whic h that entity was a
bottleneck for the line are included in the graph of event counts. However, thes e events do not cont ribute
any time to the graph of event durations because they do not actually extend into that period. So if an
entity that is changing into or out of a utilization reason and is disabled causes the bottleneck to move to
or from that entity’s position on the line, that utilization event will be counted even if no additional time for
it is added to the duration for its state, group, or reason.
To toggle between the two viewing modes
 Click the graph’s Show Duration/Show Counts button.
To drill down into the count or duration information
 Click a bar in the graph.
The drill-down sequence of information is:
1. Utilization states (the initial display, shown above)
2. Reas on groups for the selected utilization state
3. Reas ons for the selected reason group
To move back up in the drill-down sequence
 Click the Back icon to the left of the graph title.
Viewing KPI Measures

The KPI gauges indicate the OEE, Performance, A vailability, and Quality measures for the line.
The gauges are driven by the following calculations:
116 Version 6.0

 OEE = Performance x Availability x Quality

 Availability = Bottleneck Entities Runtime / Bottleneck Entities Available Time
where Bottleneck Entities Available Time = Bottleneck Entities Runtime + Bottleneck Entities
Downtime
 Quality = Good Production Count / Total Production Count
where Total Production Count = Good Production Count + Rejected Production Count for the line
based on the production entity and all upstream entities
 Performance = Total Production Count / Predicted Count for Bottleneck Entities
where Total Production Count = Good Production Count + Rejected Production Count for the line
based on the production entity and all upstream entities
For more information about how the gauge data is determined, see the topics in OEE on page 47.
The gauges include the following status indicators:
 Three zones—red, yellow, and green—to indicate the relative status of the KPI measurement.
Note: For the current release, the zone boundaries are fixed at 20% and 80%.
 A tick mark at the outer edge of the gauge's color band that points to the target value for that
measurement type for the line. For more information, see Determining the Line’s OEE Target
Values.
 The pointer that indicates the current value.
 A text readout of the current value. Note that the pointer will never go beyond 100%. However, if the
measurement exceeds 100%, the actual value will be displayed in this text readout.
 Icons that indicat e the data source calculation that drives the gauge.
If there is no OEE-related data for the selected time period, then Performance, A vailability, and Quality
will be 100%, and so OEE will be 100%. If the OEE metrics are actually 0, then OEE will be 0.
Viewing Item Production for the Period
Each item that was produc ed on the line during the selected time period appears in t he Item Production
for Period panel. This allows you to see the item counts that were used to determine the Quality KPI
measure.
Each item entry includes the following information:
 The item ID and item description
 The total production count for the item, and the Good and Rejected production counts in parentheses
Version 6.0 117

A PPENDIX A
Advanced Concepts
In This Appendix
Determining Comparable Units and Production Rates: Examples ................................................... 119
Line Monitoring and OEE Calculations ......................................................................................... 124
Determining Comparable Units and Production Rates:

Examples
The examples in this topic show how comparable units are determined for production rate calculations
when the entities on the line can produc e different items for a work order.
These examples do not apply to work orders created in MES Web Portal. All of the jobs that are running
for work orders created in MES Web Port al will produce the same item at each entity.
The line for these examples is set up as follows:
The entities in the line have following default rates and standard items.
Default Production
Enti ty Rate Production UOM Standard Item
Washer 1.2 batches/minute Bottle of C
Filler 1 15 seconds/batch Bottle of C
Filler 2 15 seconds/batch Bottle of C
Capper 1 1.5 seconds/batch Bottle of C
Capper 2 1.5 seconds/batch Bottle of C
Cart oner 1.2 seconds/batch Cart on of C
Palletizer 1.1 minutes/batch Pallet of C
The entity production UOMs are as follows:
Version 6.0 119

MES Web Portal User Guide Ad vanced Concepts
Item Production UOM
Bottle of A 16 oz. bottle
Cart on of A 6 pack of 16 oz. bottles
Pallet of A pallet of 192 16 oz. bottles
Bottle of B 32 oz. bottle
Cart on of B 6 pack of 32 oz. bottles
Pallet of B pallet of 108 32 oz. bottles
Bottle of C 64 oz. bottle
Cart on of C 4 pack of 64 oz. bottles
Pallet of C pallet of 64 64 oz. bottles
UOM conversions are defined in MES Client. The general procedure for creating the UOM conversions
for a line is:
1. Create all of the required UOMs.
2. Identify the UOM that will be used for the item that is defined as the standard item for the line.
3. Create conversion factors for each UOM so that all items can be specified in the UOM of the
standard item.
For instructions about creating UOMs and defining UOM conversion factors, see the Units of Measure
chapter in the MES Client User Guide or help.
For the example line, the UOM conversion factors listed in the following table would be used. Note that
the conversions shown in italics do not need to be defined for the sake of thes e examples, but are shown
to illustrate how some of the rest of the conversions are obtained.
From UOM To UOM Factor
16 oz. bottle 6 pack of 16 oz. bottles .16667
6 pack of 16 oz. bottles pallet of 192 16 oz. bottles .03125
16 oz. bottle pallet of 192 16 oz. bottles .00521
pallet of 192 16 oz. bottles 6 pack of 16 oz. bottles 32
pallet of 192 16 oz. bottles 16 oz. bottle 192
6 pack of 16 oz. bottles 16 oz. bottle 6
120 Version 6.0

Ad vanced Concepts MES Web Portal User Guide
16 oz. bottle 32 oz. bottle .5
32 oz. bottle 16 oz. bottle 2
6 pack of 16 oz. bottles 6 pack of 32 oz. bottles .5
6 pack of 32 oz. bottles 6 pack of 16 oz. bottles 2
4 pack of 64 oz. bottles 6 pack of 16 oz. bottles 2.6667
4 pack of 64 oz. bottles 6 pack of 32 oz. bottles 1.3333
6 pack of 16 oz. bottles 64 oz. bottle 1.5
pallet of 192 16 oz. bottles pallet of 108 32 oz. bottles .88889
pallet of 108 32 oz. bottles pallet of 192 16 oz. bottles 1.125
Version 6.0 121

Assume that there is one work order A1 running on the entire line when no entities are disabled, with the
following jobs, items, and production rate information.
Batch
Enti ty Operation Item Made Est. Prod. Rate Prod. UOM Size
Washer Washing Bottle of A 2 batches/minute 100
Filler 1 Filling Bottle of A 5 seconds/batch 8
Filler 2 Filling Bottle of A 5 seconds/batch 8
Capper 1 Capping Bottle of A 0.6 seconds/batch 1
Capper 2 Capping Bottle of A 0.6 seconds/batch 1
Cart oner Filling Cartons Cart on of A 1.5 seconds/batch 1
Palletizer Palletizing Pallet of A 0.9 minutes/batch 1
If the line's production UOM is batches per minute, where the batch size is 1, but there is no standard
item for the line so that the item made in the job running on the first entity is used, the rates at each entity
will be as follows:
Production Rate in Bottles of

Enti ty A per Minute
Washer 200
Filler 1 96
Filler 2 96
Capper 1 100
Capper 2 100
Cart oner 240
122 Version 6.0

Production Rate in Bottles of

Enti ty A per Minute
Washer 200
Palletizer 213
Since the sum of the fillers at the second position is 192, and the sum of the two cappers at the third
position is 200, the slowest position on the line is the second. Thus, assuming all entities can be part of
the bottleneck, the line's bottleneck comprises the two fillers, and the line's performance rate is 192
bottles of A per minute.
As work order A1 progresses, a point will be reached where its first jobs are done. If the jobs for work
order A1 are completed on the washer, both fillers, and capper 1, and there is no other work order's jobs
started yet on any of these entities, the rates at these entities will be set to their default values. Since no
job is running at the first entity and the default item produced by it is bottles of C, all the rates will be
expressed in terms of bottles of C.
Enti ty Production Rate in Bottles of C per Minute
Washer 120 (from default for the washer)
Filler 1 32 (from default for Filler 1)
Filler 2 32 (from default for Filler 2)
Capper 1 40 (from default for Capper 1)

Capper 2 25 (from work order A1)
Cart oner 60 (from work order A1)
Palletizer 53.25 (from work order A1)
position is 65, the slowest position on the line is the fifth. Thus, assuming all entities can be part of the
bottleneck, the line's bottleneck is the palletizer, and the line's performance rate is 53.25 bottles of C per
minute.
Continuing the example, as work order A1 progressed, another work order, B1, is assigned to the line
and is started. If the jobs for work order A1 reach the same point as above (t hat is, completed on the
washer, both fillers, and capper 1), and the jobs for work order B1 are as follows:
Est. Prod.
Enti ty Operation Item Made Rate Prod. UOM Batch Size
Washer Washing Bottle of B 1.5 batches/minute 100
Filler 1 Filling Bottle of B 8 seconds/batch 8
Filler 2 Filling Bottle of B 8 seconds/batch 8
Capper 1 Capping Bottle of B 1.2 seconds/batch 1
Capper 2 Capping Bottle of B 1.2 seconds/batch 1
Version 6.0 123

Est. Prod.
Enti ty Operation Item Made Rate Prod. UOM Batch Size
Washer Washing Bottle of B 1.5 batches/minute 100
Cart oner Filling Cartons Cart on of B 1.6 seconds/batch 1
Palletizer Palletizing Pallet of B 0.8 minutes/batch 1
Then once t he jobs for the washer and filler 1 are start ed, the operations for filler2 and capper1 from work
order B1 will be used to determine the rates at those entities even though they are not yet running,
because of the jobs being run at the upstream entities (the washer and filler1 respectively). So since the
item produced by the first entity is now bottles of B, all the rates will be expressed in terms of bottles of B.
Enti ty Production Rate in Bottles of B per Minute
Washer 150 (from work order B1)
Filler 1 60 (from work order B1)
Filler 2 60 (inferred from work order B1)
Capper 1 50 (inferred from work order B1)

Capper 2 50 (from work order A1)
Cart oner 120 (from work order A1)
Palletizer 106.5 (from work order A1)
position is 100, the slowest position on the line is the third. Thus assumi ng all entities can be part of the
bottleneck, the line's bottleneck comprises the two cappers, and the line’s performance rate is 100
bottles of B per minute.
Line Monitoring and OEE Calculations

This example demonstrates how the OEE calculations for line monitoring are performed.
124 Version 6.0

Line Structure
The entities in the example line are shown in the following diagram.
Entity Properties
In the example line, the production entity is the Packer.
The values for the production-relat ed properties are listed in the following table.
Default
Enti ty Production Rate Production UOM Batch Size
Grinder 3.5 batches/sec 1

Filler1 1.1 batches/sec 1
Sleever1 2 batches/sec 1
Sleever2 2 batches/sec 1
Packer 3 batches/sec 1
In this example, the UOMs of the default items configured for the entities in this line are exactly the same
as the UOM of the standard item configured for the line. Therefore, no conversion factors are used in the
examples to convert the units.
Version 6.0 125

OEE Use and Bottlenecks

The following time chart shows the OEE Use durations for the utilization events that are pertinent to the
OEE calculations. It also shows which entities were bottlenecks and for what time periods (for example,
the Packer was the bottleneck entity from 6 to 7 am).
Note the following about the chart:

 Bottleneck time periods that are pertinent to OEE calculations are shown in dark gray with the label
"Bottleneck."
 Bottleneck time periods that are not pertinent to OEE calculations are shown in li ght er gray with the
label "BN-Not in OEE." For example, Filler1 was considered as a bottleneck entity from 7 to 8 am.
However, it had an OEE Us e designation of Neither (that is, not in Runtime or Downtime), so it was
not included in OEE calculations during this time period.
 Filler3 is not considered as a bottleneck entity when the other two Filler entities are bec ause it is
configured to not be enabled during Downtime. The same is true for Sleever2.
Production Data
The following table shows the Good and Rejected production for eac h entity, by the hour.
Production
Enti ty Type 6-7 am 7-8 am 8-9 am 9-10 am 10-11 am 11-12 pm
Grinder Good 11,500 4,100 4,100 10,500 8,000 7,100

Reject 0 25 50 0 100 0
Filler1 Good 3,750 0 3,960 3,950 0 2,400
Reject 0 0 40 0 0 0
Filler2 Good 3,750 3,980 0 3,750 3,900 2,400
Reject 0 20 0 0 60 0
Filler3 Good 3,700 0 0 3,200 3,900 2,400
Reject 0 0 0 0 60 0
Sleever1 Good 5,500 1,920 2,000 5,450 7,200 7,200
126 Version 6.0

Production
Enti ty Type 6-7 am 7-8 am 8-9 am 9-10 am 10-11 am 11-12 pm
Reject 0 40 20 0 40 0
Sleever2 Good 5,500 1,920 2,000 5,450 0 0
Reject 0 40 20 0 0 0
Packer Good 10,800 4,000 3,900 10,800 7,350 7,200
Reject 0 10 50 0 20 0
OEE Calculations
The OEE metrics for the time period from 6 am to 12 pm are calculated as follows.
Line Availability
Line A vailability = Bottleneck Entities Runtime / (Bottleneck Entities Runtime + Bottleneck

Entities Downtime)
= ((Packer Runtime 6 am –7 am) + (Filler1 Runtime 7 am –9 am) +
(Filler2 Runtime 7 am–9 am) + (Packer Runtime 9 am–10 am) +
(Sleever1 Runtime 10 am –12 pm)) /
((Runtime Total + (Filler2 Downtime 8 am –9 am))
= (3,600 + 3,600 + 3,600 + 3,600 + 5,400) / (19,800 + 3,600)
= 19,800 / 23,400
= 0.84615 (84.62%)
Quality
Quality = Packer Good Production / ( Packer Good P roduction + Rejected

Production at All Entities)
= 44,050 / (44,050 + 595)
= 0.98667 (98.67%)
Performance
Performance = Actual Production Count / Expected Production Count for Bottleneck

Entities
= Actual Production Count /
((Packer Expected Production 6 am–7 am) +
(Filler1 Expected Production 7 am–9 am) +
(Filler2 Expected Production 7 am–9 am) +
(Packer Expected Production 9 am –10 am) +
(Sleever1 Expected Production 10 am–12 pm))
Calculating the expected production count for each entity when it was a bottleneck entity by using the
following equation:
Entity Expected = Entity Production Rate x Runtime Duration (in seconds) x Entity Default
Performance Batch Size
Yields the following:
Version 6.0 127

Performance = 44,645 / ((3 x 3,600 x 1) + (1.1 x 3,600 x 1) + (1.1 x 3,600 x 1) +

(3 x 3,600 x 1) + (2 x 5,400 x 1))
= 44,645 / 40,320
= 1.10727 (110.73%)
OEE
OEE = A vailability x Quality x Performance

= 0.84615 x 0.98667 x 1.1073
= 0.9244 (92.44% )
128 Version 6.0

A PPENDIX B
MES Web Portal URLs
In This Appendix
Page URLs................................................................................................................................. 129
Embedded Controls URLs ........................................................................................................... 130
Page URLs
The URLs for the MES Web Portal pages are listed below.
Home
http://<web_portal_server>/mes/
Enti ties
http://<web_portal_server>/mes/#/entities/
Enti ty
http://<web_portal_server>/mes/#entity/<entID>/
Enti ty > Utilization Events tab
http://<web_portal_server>/mes/#entity/<entID>/utilization
Enti ty > Work Queue tab
http://<web_portal_server>/mes/#entity/<entID>/workQueue
Enti ty > Monitor tab
http://<web_portal_server>/mes/#entity/<entID>/monit or
Enti ty > Configuration tab
http://<web_portal_server>/mes/#entity/<entID>/configuration
Lines
http://<web_portal_server>/mes/#lines/
Line
http://<web_portal_server>/mes/#line/<lineID>/
Line > Work Order tab
http://<web_portal_server>/mes/#line/<lineID>/workOrders
Line > Entities tab
http://<web_portal_server>/mes/#line/<lineID>/entities
Line > Monitor tab
http://<web_portal_server>/mes/#line/<lineID>/monitor
Line > Configuration tab
http://<web_portal_server>/mes/#line/<lineID>/configuration
Utilization
http://<web_portal_server>/mes/#/utilization/
Utilization > Reasons & Groups tab
http://<web_portal_server>/mes/#utilization/reasonsGroups
Version 6.0 129

MES Web Portal User Guide MES Web Portal URLs
Utilization > States tab

http://<web_portal_server>/mes/#utilization/states
Work Orders
http://<web_portal_server>/mes/#/workOrders/
Work Order
http://<web_portal_server>/mes/#workOrder?wo_id=<woID>
Work Order > Job
http://<web_portal_server>/mes/#job?wo_id=<woID>&op_id=<opID>&seq_no=<seqNo>
The parameters to pass are represented by:
<web_portal_server>
The name of the server on which MES Web Port al is running.
<entID>
The ID number of the entity whose page or tab is being displayed.
<lineId>
The ID number of the line whose page or tab is being displayed.
<woID>
The ID number of the work order whose page is being displayed.
<woID>, <opID>, <seqNo>
The work order ID, operation ID, and sequence number of the job whose page is being display ed.
Embedded Controls URLs

Cert ain MES Web Portal controls can be embedded in another web application without the surrounding
web page layout elements. These controls and their URLs are listed below.
Enti ty Monitor
http://<web_portal_server>/mes/noChrome.cshtml#common/ entity/monitor/monitor?entID=<ent ID>
Enti ty Utilization
http://<web_portal_server>/mes/noChrome.cshtml#common/ entity/utilization/ut ilization?entID=<ent
ID>
Enti ty Work Queue
http://<web_portal_server>/mes/noChrome.cshtml#common/ entity/workQueue/workQueueHost?en
tID=<ent ID>
Line Layout
http://<web_portal_server>/mes/noChrome.cshtml#common/line/configuration/layout/editor?lineID=
<lineID>
Line Monitor
http://<web_portal_server>/mes/noChrome.cshtml#common/line/monitor/monitor?lineID=<lineID>
The parameters to pass are represented by:
<entID>
The ID number of the entity to associate to the control.
<lineId>
The ID number of the line to associate to the control.
130 Version 6.0

Index
versions supported • 11
A closing a session • 11
access settings • 27 collection pages • 15
suggested settings by user roles • 30 filtering entities • 15
action bar • 21 filtering work orders • 16
asterisk, meaning of • 23 comparable units and production rates • 37
Auto Refresh • 23
examples • 119
auto-login • 10
configuration
A vailability (OEE)
overview • 9
calculation of • 48
B E
entities
batches and lots, OEE • 44
bottleneck entities adding • 58
description • 36 Allowable Reasons tab, configuration • 65
determining manually • 36 allowable reasons, specifying • 65
determining programmatically by the Attributes tab, configuration • 61

system • 36 attributes, adding • 61
information, viewing • 97 basic information settings • 59
bottleneck entities, configuring automatic bottleneck information, viewing • 97
determination of • 80 bottleneck, definition • 36
entity • 81
capabilities • 31
entity Can Be the Bottlneck setting,
capabilities settings • 58, 81
selecting • 80
conditions required to be in a line • 32
entity required capabilities • 81
current utilization event status, viewing •
entity, enabling when in the Running
102
utilization state • 81
definition • 31
line configuration settings, required • 80
deleting • 67
line entites can be the bottleneck, enabling •
E vent History grid column descriptions • 103
80
filering on the Collection page • 15
manual designation, removing • 80
General tab, configuration • 58
guidelines, in a line • 35
C
job settings • 62
Chrome • 11
Job tab, configuration • 62
language used • 10
locale used for values and dates • 11 KPI, monitoring • 108
Version 6.0 131

MES Web Portal User Guide Index
Monitor tab • 109 filtering by last N hours of activity • 20

OEE default dat a, specifying • 66, 81 sorting by column • 19
OEE tab, configuration • 66 guidelines
parallel • 33 creating work orders from a process • 43
parent entity of a line • 33 entities and lines • 35
position in a line • 34 recreating work orders from a line • 43
production rate, automatic determination of

• 36 I
serial • 33 installing
status, viewing • 92 overview • 10
tile functions • 93 Internet Explorer
utilization event history, viewing • 102 language used • 10
utilization event, adding • 104 locale used for values and dates • 11
utilization event, editing • 104 versions supported • 11

item classes • 32
utilization event, splitting • 106
items
utilization events, merging • 108
definition • 32
utilization reasons, specifying for standard
filtering item lists • 18
events • 64
quantities, decimal precision of • 39
Utilization tab, configuration • 64
work queue, viewing jobs in • 94
E vent History grid column descriptions • 103 J
jobs
creation • 40
F
filtering definition • 39
case sensitivity of entries • 22 ending • 100
entities on the entities Collection page • 15 entity job settings • 62
grds by the last N hours of activity • 20 information, viewing • 91, 92
grid by a column • 19 line, running on • 110
items in item lists • 18 marking as complete • 101
wildcard characters, implied • 22 production quantity, entering • 97
work orders on the work orders Collection starting • 100

page • 16 states • 40
Firefox states, effect of work order status changes •
language used • 10 42
locale used for values and dates • 11 viewing in entity workqueue • 94
versions supported • 11
K
G KPI
grids • 19 guages, working wit h • 112, 116
filtering by a column • 19 monitoring • 108, 116
132 Version 6.0

Index MES Web Portal User Guide
shift on which data is based • 109, 114 entity status, viewing • 92

example • 32
L KPI measures • 116
language used in web brows er • 10 layout • 33
layout, line • 33 layout reconfiguration, system behavior • 44
reconfiguration guidelines • 43 navigating to, from the work order • 92
reconfiguration, system behavior • 44 OEE, monitoring • 113, 124
liine management • 32
parallel entities • 33
line configuration • 67
parent entity • 33
bottleneck entity automatic determination,
configuring • 80 performance, determining • 36
bottleneck entity, manually designating • 79 production amounts, determining • 36, 117
entity Can Be the Bottlneck setting, production rate and bottleneck entity • 36
selecting • 80 production rates • 35
line layout • 70 production rates, line properties used to
production source entity, designating • 78 determine • 35
settings • 68, 80 reassigning a work order • 41
standard item • 69 segments • 34

line layout serial entities • 33
configuring • 70 summary information • 84
end of a line, inserting entity at • 74 user access, assigning • 81
entity, moving in the layout • 78 work order job informaiton, viewing • 91, 92
entity, removing • 78 locale used for values and dates • 11
lots and OEE • 44
initial entity, inserting • 72
parallel enties, adding • 75
sample • 71
M
MES Native user authentication mode • 25
segment, creating • 76
MES Web Portal
serial entites, adding • 74
accessing • 10
start of a line, inserting entity at • 73
configuration overview • 51
lines
installing • 10
bottleneck entity • 36, 80
language used • 10
bottleneck information, viewing • 97
navigating • 13
comparable units and production rates • 37
operations overview • 83
creating • 67
operations that can be performed • 83
definition • 32
session, closing • 11
deleting • 70
URL • 10
editing • 70
web browsers supported • 11
entity guidelines • 35
messages, system • 23
entity positions • 34
entity required conditions • 32
Version 6.0 133

MES Web Portal User Guide Index
line properties used to determine • 35

N production rate and bottleneck entity • 36
Native user mode, MES • 25 production rate determination, examples •
navigating 119
home page, to the • 14 production rate for entity, automatice
Navigation menu icon • 13 determination of • 36
production rates • 35
O quantity settings • 98
OEE (Overall Equipment Effectiveness) removing • 100
A vailability • 48 when a rate cannot be determined • 37
batches and lots • 44 prvileges • 10
calculations • 127 insufficient privileges message • 10
default data for an entity, specifying • 66 settings cached • 10
line configuration settings • 66
line, exampe calculations for • 124 Q
monitoring for the line • 113 Quality (OEE)
overview • 47 calculation of • 48
Performance, calculations • 49
Quality • 48 R
target values, setting • 49 raw reas on codes • 46
operation refres h behavior, displayed information • 23
required ent ries • 23
overview • 9
operation ID • 40
OS Group security mode • 25 S
multiple AD domains • 26 screen text truncated • 22
OS User security mode • 25 segments, line • 34
sequence number • 40
serial entities • 33
P session, closing • 11
parallel entities • 33
states
Performance (OEE)
job • 40
calculation of • 49 status
performance, determining for a line • 36
work order • 39
positions, entities in a line • 34
production
adding • 97 T
comparable units • 37 truncated information • 22
comparable units, examples • 119

determining amounts for a line • 36 U
URL, MES Web Portal • 10
internal tracking of • 38
user access
item quantities, decimal precision of • 39
auto-login • 10
134 Version 6.0

Index MES Web Portal User Guide
lines • 81 configuring • 55, 81

refres h after settings change • 10 default reasons for standard events, by
user aut hentication • 25 entity • 64
checks performed during login • 26 entity, specifying allowable reasons for • 65
MES Native Mode • 25 overview • 45
OS Group security mode • 25 settings • 56
OS Group security mode and multiple A D utilization raw reason codes • 46
domains • 26 utilization states
OS User security mode • 25 configuring • 52
Windows Active Directory (AD) • 25 overview • 45
user privileges settings • 53
settings • 27 viewing information on • 111, 116
settings, suggested by user roles • 30
user roles • 30
utilization • 45
W
web browsers supported • 11
raw reas on codes • 46 wildcard characters • 22
utilization events
Windows Active Directory user groups and
adding • 104 users • 25
counts and durations, monitoring • 108 work orders
counts and durations, Paret o graph • 111 created from a line, guidelines • 43
default utilization reasons for standard created from a process, guidelines • 43
events • 64 creating • 85
editing • 104 definition • 39
entity current event status • 102 effect of status changes on job states • 42
entity event history, viewing • 102 filtering on the work order Collection page •
entity events, working with • 102 16
entity Monitor tab, navigating to • 109 job creation • 40
E vent History grid column descriptions • 103 job information, viewing • 91, 92
Maximum Duration setting • 46 production history grid, column descriptions
Maxmum Time setting • 46 • 92
merging • 47 reassigning to a different line • 41, 88
Minimum Time setting • 46 status • 39
overview • 46 status, changing • 86
Severe flag • 47 viewing status • 89
splitting • 47, 106 working with • 85
Standard Time setting • 46

utilization reason groups
configuring • 54
overview • 46
utilization reasons
Version 6.0 135

MESWeb Portal User Guide

Uploaded by

Copyright:

Available Formats

MESWeb Portal User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MESWeb Portal User Guide

Uploaded by

Copyright:

Available Formats

Manufacturing Execution System (MES)

Chapter 2 MES Web Portal Concepts .............................................................................. 25

Entity Capabilities .............................................................................................................. 31

Chapter 3 MES Web Portal Configuration ....................................................................... 51

Configuring Utilization States and Reas ons .............................................................................. 51

Chapter 4 MES Web Portal Operations ........................................................................... 83

Viewing a Line's Work Order Status ......................................................................................... 89

Appendix A Advanced Concepts ..................................................................................... 119

Appendix B MES Web Portal URLs ................................................................................ 129

Index ....................................................................................................................................... 131

MES Web Portal Configuration

MES Web Portal Operation

Installing the MES Web Portal

Accessing MES Web Portal

Closing a MES Web Portal Web Session

Web Browser Support

Web Browsers Supported

Setting the Web Browser's Preferred Language/Locale for Values and

To set the preferred language for Firefox

Requirements for Running Online Help Video Tutorials

6. Save your selection.

Navigating in MES Web Portal

The Navigation menu appears.

Navigating to the Home Page

Working with Collection Pages

Filtering Entities on the Entities Collection Page

To clear the filter

 Click the Clear Filter icon.

Filtering Work Orders

To reset the filter to the default settings

Filtering Item Lists

Working with Grids

Sorting the Grid by a Column

Clicking the heading cycles through:

Filtering the Grid by a Column

And true/ false (c heck box) columns:

Filtering a Grid by the Last N Hours of Activity

2. Click the Apply Filter icon or button.

Other Basic Operations

Working with the Action Bar

Click an icon in the action bar to initiate the selected action.

Implied Wildcard Characters and Case Sensitivity in Filter Boxes

 Feeder - Pec ans

Information Data Refresh

MES Web Portal User Authentication and Privileges

Using OS Group vs. OS User Security Mode

OS Group Security and Multiple AD Domains

Authentication Checks Performed When a User Logs In

Privilege and Access Settings

Setting Setting Type Where Specified Allows Users to:

May edit lines Configuration MES Client, Create, configure, modify,

Setting Setting Type Where Specified Allows Users to:

Setting Setting Type Where Specified Allows Users to:

Setting Setting Type Where Specified Allows Users to:

May change Operation MES Client, Change the status of a work

Example Roles and Privilege Settings

May edit lines Yes No No

 Capt uring machine utilization

Items and Item Classes