OpcenterEXDS UserManual

Opcenter Execution Discrete 4.
User Manual
07/2021
PL20210504131482743
Guidelines
This manual contains notes of varying importance that should be read with care; i.e.:
Important:
Highlights key information on handling the product, the product itself or to a particular part of the documentation.
Note: Provides supplementary information regarding handling the product, the product itself or a specific part of
the documentation.
Trademarks
All names identified by ® are registered trademarks of Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes
could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Security information
Siemens provides products and solutions with industrial security functions that support the secure operation of
plants, systems, machines and networks. In order to protect plants, systems, machines and networks against
cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems,
machines and components should only be connected to the enterprise network or the internet if and to the extent
necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into account. For more
information about industrial security, please visit https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly
recommends to apply product updates as soon as available and to always use the latest product versions. Use of
product versions that are no longer supported, and failure to apply latest updates may increase customer’s
exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under https://
www.siemens.com/industrialsecurity.
Siemens AG PL20210504131482743 Copyright © Siemens AG 2021

Digital Industries 20210726_115346 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of Contents
1 Basic Know-How Before Getting Started.........................................................12
1.1 Apps and Extension Apps included in the Discrete Solution ............................................... 13
1.2 Managing Multi-Plant Support .............................................................................................. 19
1.3 Speeding Up Operator Landing Page Loading through Task Customization..................... 21
2 Quick Start to Using Opcenter Execution Discrete..........................................23
3 How to Configure the Production Environment..............................................24
3.1 Applying General Configuration Settings ............................................................................. 24
3.1.1 Engineering Configuration Settings.................................................................................................................... 25
3.1.2 Runtime Configuration Settings.......................................................................................................................... 27
3.1.3 Additive Manufacturing Configuration Settings................................................................................................. 31
3.1.4 Integration Configuration Settings ..................................................................................................................... 32
3.1.5 E-mail Configuration Settings ............................................................................................................................. 33
3.1.6 CLM Integration Configuration Settings ............................................................................................................. 34
3.1.7 Certification Configuration Settings ................................................................................................................... 35
3.2 How to Define the Plant Structure ........................................................................................ 37
3.2.1 Creating Equipment Configurations ................................................................................................................... 37
3.2.2 How to Design the Equipment Hierarchy ........................................................................................................... 39
3.3 Configuring Identifier Templates .......................................................................................... 40
3.4 Configuring Reasons .............................................................................................................. 43
3.5 How to Configure Tool Definitions ........................................................................................ 43
3.6 Configuring Substrates .......................................................................................................... 47
3.7 Configuring Custom Logistic Classes .................................................................................... 48
3.8 Configuring Buffer Definitions............................................................................................... 49
3.9 How to Configure Materials ................................................................................................... 50
3.9.1 How to Configure Material Classes, Suppliers and Functional Codes............................................................... 52
3.9.2 Creating a Material from Scratch ........................................................................................................................ 53
3.9.3 Copying a Material ............................................................................................................................................... 55
3.9.4 Creating a Revision of a Material ......................................................................................................................... 55
3.9.5 Associating Documents with a Material.............................................................................................................. 56
3.9.6 Associating a Template with a Material .............................................................................................................. 56
3.9.7 Associating Suppliers with a Material ................................................................................................................. 56
3.9.8 How to Configure Bill of Materials....................................................................................................................... 57
3.10 Configuring Powder Materials ............................................................................................... 59
Opcenter Execution Discrete 4.2 - User Manual iii

3.11 How to Configure Container Types ....................................................................................... 60
3.12 How to Configure Operation/Step Categories...................................................................... 62
3.13 How to Manage Catalogs ....................................................................................................... 65
3.13.1 How to Manage the Process Catalog................................................................................................................... 66
3.13.2 How to Manage the Operation Catalog............................................................................................................... 67
3.13.3 How to Manage the Step Catalog ........................................................................................................................ 70
3.14 How to Configure Plugins ...................................................................................................... 72
3.15 How To Configure 3D Printers ............................................................................................... 73
3.16 How to Configure Failures ..................................................................................................... 74
3.17 Configuring Rework Codes .................................................................................................... 76
3.18 Configuring Non-Productive Activities ................................................................................. 77
3.19 How to Configure Print Job Files........................................................................................... 78
3.19.1 Importing Print Job Files ..................................................................................................................................... 78
3.19.2 Creating Print Job Files Manually........................................................................................................................ 79
3.19.3 Finalizing the Print Job File Configuration ......................................................................................................... 80
3.20 Importing and Mapping CNC Packages ................................................................................ 81
3.21 Configuring Work Operations................................................................................................ 83
3.22 How to Configure Custom Non-Conformance Lifecycles .................................................... 86
3.22.1 Creating a Non-Conformance Lifecycle .............................................................................................................. 87
3.22.2 Creating a Non-Conformance Status .................................................................................................................. 88
3.22.3 Configuring a Transition ...................................................................................................................................... 88
3.22.4 Associating States with Behaviors ...................................................................................................................... 89
3.22.5 Associating Transitions with User Roles and E-mail Addresses ........................................................................ 89
3.23 Configuring Custom Interlocking Checks ............................................................................. 90
3.24 Configuring Custom Result Types ......................................................................................... 92
3.25 Linking Items to Buffer Definitions........................................................................................ 93
3.26 How to Configure Setpoints .................................................................................................. 94
3.27 How to Configure Barcode Rules .......................................................................................... 96
3.27.1 Creating Barcode Rules ....................................................................................................................................... 96
3.27.2 Creating Rule Parts .............................................................................................................................................. 97
3.27.3 Associating a Barcode Rule with a Material........................................................................................................ 98
3.27.4 Associating a Barcode Rule with a Functional Code .......................................................................................... 99
3.27.5 Viewing Barcode History...................................................................................................................................... 99
3.28 How to Configure Line Side Positions................................................................................. 100
iv Opcenter Execution Discrete 4.2 - User Manual

3.29 How to Configure Qualification Criteria.............................................................................. 102
4 How to Create and Prepare Human Resources and Their Capabilities........106
4.1 Configuring Skills ................................................................................................................. 106
4.2 Configuring Certifications.................................................................................................... 107
4.3 How to Create and Prepare Teams ..................................................................................... 109
5 How to Configure the Production Processes.................................................111
5.1 How to Manage As Planned BOPs and Processes............................................................... 111
5.1.1 Creating As Planned BOPs and Processes ........................................................................................................ 112
5.1.2 Linking Processes to As Planned BOPs ............................................................................................................. 113
5.1.3 Cloning an As Planned BOP ............................................................................................................................... 114
5.1.4 Evolving an As Planned BOP.............................................................................................................................. 114
5.1.5 Creating a Revision of a Process........................................................................................................................ 114
5.1.6 Completing an As Planned BOP ........................................................................................................................ 115
5.2 How to Manage Master Plans and Processes...................................................................... 115
5.2.1 Creating Master Plans and Processes ............................................................................................................... 115
5.2.2 Linking Processes to Master Plans .................................................................................................................... 117
5.2.3 Completing Master Plans................................................................................................................................... 117
5.3 Creating a Sub-Process........................................................................................................ 118
5.4 Creating a Process Operation.............................................................................................. 120
5.5 Defining Dependencies between Process Operations ....................................................... 122
5.6 Defining Groups of Alternative Process Operations........................................................... 124
5.7 Associating Items to Process Operations ........................................................................... 125
5.7.1 Associating Machines to Process Operations ................................................................................................... 126
5.7.2 Associating Materials to Process Operations ................................................................................................... 128
5.7.3 Associating Tools to Process Operations.......................................................................................................... 131
5.7.4 Linking Documents to Process Operations ...................................................................................................... 131
5.7.5 Associating Work Instructions to Process Operations ..................................................................................... 132
5.7.6 Associating Skills to Process Operations .......................................................................................................... 133
5.7.7 Linking Interlocking Checks to Process Operations......................................................................................... 134
5.7.7.1 Role of Work Order Production Type for the DocumentsUploaded Interlocking Check................................ 135
5.7.8 Linking Inspection Definitions to Process Operations ..................................................................................... 136
5.7.9 Associating Qualification Criteria to Process Operations ................................................................................ 137
5.7.10 Associating Powders to Process Operations .................................................................................................... 138
5.7.11 Linking Human Resources to Process Operations ........................................................................................... 138
5.7.12 Linking Material Parameters to Automation Node Instance Parameters ....................................................... 139
Opcenter Execution Discrete 4.2 - User Manual v

5.7.13 Linking Data Collection Parameters to Automation Node Instance Parameters ........................................... 140
5.7.14 Linking Tool Definition Parameters to Automation Node Instance Parameters ............................................ 140
5.7.15 Linking Setpoint Variables to Automation Node Parameters.......................................................................... 141
5.8 Creating a Process Step ....................................................................................................... 142
5.9 Defining Dependencies between Process Steps ................................................................ 144
5.10 Associating Items to Process Steps..................................................................................... 144
5.10.1 Associating Materials to Process Steps............................................................................................................. 145
5.10.2 Associating Tools to Process Steps ................................................................................................................... 148
5.10.3 Linking Documents to Process Steps................................................................................................................ 148
5.10.4 Associating Work Instructions to Process Steps............................................................................................... 149
5.10.5 Associating Skills to Process Steps ................................................................................................................... 149
5.10.6 Linking Interlocking Checks to Process Steps .................................................................................................. 150
5.10.7 Linking Inspection Definitions to Process Steps .............................................................................................. 151
5.10.8 Linking Human Resources to Process Steps..................................................................................................... 152
6 How to Configure and Manage Output Messages .........................................154

6.1 Creating Output Message Destinations .............................................................................. 154
6.2 Creating Output Message Definitions ................................................................................. 155
6.3 Configuring Output Message Sections................................................................................ 156
7 How to Prepare Production Execution ..........................................................158
7.1 How to Create and Prepare Material Tracking Units.......................................................... 158
7.1.1 Splitting Material Tracking Units....................................................................................................................... 160
7.1.2 Changing Material Tracking Unit Codes............................................................................................................ 161
7.2 Creating Powder Material Batches...................................................................................... 162
7.3 Creating Tools ...................................................................................................................... 163
7.4 Creating Substrates ............................................................................................................. 166
7.5 How to Create and Prepare Buffers..................................................................................... 167
7.6 How to Create and Prepare Containers .............................................................................. 169
7.6.1 Associating the Container to a Work Order ...................................................................................................... 172
7.7 How to Create and Prepare Work Orders for Production Execution ................................. 172
7.7.1 Creating a Work Order ....................................................................................................................................... 172
7.7.1.1 Creating a Work Order from a Process.............................................................................................................. 173
7.7.1.2 Creating a Work Order Manually ....................................................................................................................... 175
7.7.1.3 Creating Work Orders from an As Planned BOP ............................................................................................... 178
7.7.1.4 Creating a Work Order from a Work Order Header........................................................................................... 179
vi Opcenter Execution Discrete 4.2 - User Manual

7.7.1.5 Creating a Work Order from a Master Plan ....................................................................................................... 182
7.7.1.6 Creating a Work Order from a Master Plan with Qualification Criteria ........................................................... 185
7.7.2 Completing Work Order Configuration ............................................................................................................. 188
7.7.2.1 How to Create Work Order Operations ............................................................................................................. 189
7.7.2.2 Defining Dependencies between Work Order Operations ............................................................................... 196
7.7.2.3 Defining Groups of Alternative Work Order Operations................................................................................... 199
7.7.2.4 Creating Work Order Steps manually................................................................................................................ 200
7.7.2.5 Defining Dependencies between Work Order Steps ........................................................................................ 201
7.7.2.6 Associating Items to Work Order Operations ................................................................................................... 202
7.7.2.7 Associating Items to Work Order Steps............................................................................................................. 213
7.7.2.8 Associating Users to Work Order Operations ................................................................................................... 221
7.7.3 Scheduling a Work Order................................................................................................................................... 222
7.7.4 Releasing a Work Order ..................................................................................................................................... 224
7.7.5 Pre-Transferring Print Job Files to 3D Printers................................................................................................. 225
7.7.6 Editing Released Work Orders Before Execution.............................................................................................. 225
7.7.7 Splitting a Work Order ....................................................................................................................................... 226
7.7.8 Performing Pre-Kitting for Work Orders ........................................................................................................... 227
7.8 How to Create and Prepare Execution Groups for Production Execution ........................ 229
7.8.1 Creating an Execution Group............................................................................................................................. 229
7.8.2 Linking Work Order Operations to an Execution Group................................................................................... 230
7.8.3 Updating Execution Group Phases.................................................................................................................... 232
7.8.4 Linking Print Job Files to Execution Group Phases.......................................................................................... 233
7.8.5 Linking Work Instructions to Execution Group Phases .................................................................................... 234
7.8.6 Associating Powders to Execution Group Phases ............................................................................................ 235
7.8.7 Scheduling an Execution Group ........................................................................................................................ 236
7.8.8 Releasing an Execution Group........................................................................................................................... 236
8 How to Execute Work Orders..........................................................................238

8.1 Navigation of the Operator Landing Page during Production Execution ......................... 239
8.1.1 Joining and Leaving Teams at Runtime............................................................................................................ 243
8.1.2 Runtime Behavior in case of Dependencies between different Work Orders ................................................. 244
8.1.3 Managing Automatically Executed Work Order Operations ............................................................................ 245
8.2 Previewing Work Order Operations, Work Order Steps and Execution Groups................ 247
8.3 Previewing Document Files ................................................................................................. 248
8.4 Loading Containers.............................................................................................................. 249
8.5 Starting Work Order Operations.......................................................................................... 251
8.5.1 Special Cases and Constraints When Starting a Work Order Operation ......................................................... 254
Opcenter Execution Discrete 4.2 - User Manual vii

8.6 Managing Work Order Operations....................................................................................... 256
8.6.1 Managing Tasks for Work Order Operation or Step Progression..................................................................... 258
8.6.1.1 How to Manage Work Instructions .................................................................................................................... 260
8.6.1.2 Using Tools ......................................................................................................................................................... 262
8.6.1.3 Using Substrates ................................................................................................................................................ 263
8.6.1.4 Consuming or Assembling Material Tracking Units ......................................................................................... 264
8.6.1.5 How to Manage Quality Inspections ................................................................................................................. 272
8.6.1.6 Transferring Print Job Files to 3D Printers........................................................................................................ 275
8.6.1.7 Transferring CNC Programs to Machines.......................................................................................................... 277
8.6.1.8 Producing Material Tracking Units at Runtime ................................................................................................ 278
8.6.1.9 How to Manage Powder Material Batches ........................................................................................................ 280
8.6.2 Changing Serial Numbers during Production................................................................................................... 283
8.6.3 Skipping Work Order Operations ...................................................................................................................... 285
8.6.4 Adding Documents to Work Order Operations at Runtime ............................................................................. 285
8.6.5 Adding Notes to Work Order Operations at Runtime....................................................................................... 286
8.6.6 Aborting Work Orders ........................................................................................................................................ 287
8.6.7 Placing Work Orders on Hold ............................................................................................................................ 288
8.6.8 Placing Work Order Operations on Future Hold............................................................................................... 288
8.6.9 Placing Workcenters and Machines on Hold .................................................................................................... 289
8.6.10 Managing Work Order Updates ......................................................................................................................... 289
8.6.11 Disassembling Material Tracking Units............................................................................................................. 290
8.6.12 Pausing and Resuming Work Order Operations............................................................................................... 291
8.6.12.1 Special Case: Performing an Administrative Pause ......................................................................................... 292
8.6.13 Closing Flexible Work Orders............................................................................................................................. 293
8.7 Completing Work Order Operations ................................................................................... 294
8.8 Unloading Containers .......................................................................................................... 296
8.9 How to Manage Additive Manufacturing-related Activities ............................................... 297
8.9.1 Performing Substrate Treatment...................................................................................................................... 298
8.9.2 Reducing Substrate Thickness .......................................................................................................................... 298
8.9.3 Maintaining Substrates...................................................................................................................................... 299
8.9.4 Loading Powder Material Batches into 3D Printers.......................................................................................... 300
8.9.5 Recycling Powder Material Batches .................................................................................................................. 300
8.9.6 Mixing Powder Material Batches ....................................................................................................................... 302
9 How to Execute Production on Execution Groups ........................................306

9.1 Navigation of the Execution Group Working Environment at Runtime ............................ 306
9.1.1 Operations Available in the Bottom Bar ........................................................................................................... 307
viii Opcenter Execution Discrete 4.2 - User Manual

9.2 How to Prepare Execution Groups during Production Execution ..................................... 308
9.2.1 Creating an Execution Group On The Fly .......................................................................................................... 308
9.2.2 Linking Work Order Operations to an Existing Execution Group..................................................................... 309
9.3 Starting Execution Groups................................................................................................... 310
9.4 Consuming Materials of type Additive from an Execution Group...................................... 311
9.5 How to Manage Work Instructions for Execution Group Phases ....................................... 311
9.6 Pausing and Resuming Execution Groups .......................................................................... 313
9.7 Completing Execution Groups............................................................................................. 314
10 How to Execute Production in Offline Mode..................................................315
11 How to Manage Non-Conformances ..............................................................317
11.1 Declaring Quality Non-Conformances during Production................................................. 318
11.2 Declaring Quality Non-Conformances on Work Order Operations ................................... 320
11.3 Declaring Non-Conformances of type Quality on Production Entities ............................. 322
11.4 Declaring Change Non-Conformances................................................................................ 325
11.5 Example of a Repeat Operation Change Non-Conformance ............................................. 328
12 How to Manage Buffer Replenishment and Transport Operations ..............330
12.1 How to Configure Handling Units........................................................................................ 330
12.2 Declaring Logistic Requests................................................................................................. 331
12.3 Accepting Logistic Requests................................................................................................ 333
12.4 Executing Transport Operations ......................................................................................... 334
12.5 How to Unload Handling Units............................................................................................ 335
13 How to Manage Non-Productive Activities ....................................................336
13.1 Managing Non-Productive Activities from the Users page ................................................ 336
13.2 Managing Non-Productive Activities from the Operator Landing Page ............................ 337
13.3 Managing Non-Productive Activities from the Notification Bar ........................................ 338
14 How to Handle Notifications ..........................................................................339
14.1 Handling Note Notifications ................................................................................................ 340
14.2 Handling Work Order Notifications..................................................................................... 341
14.3 Handling Process Notifications ........................................................................................... 342
14.4 Handling Change Non-Conformances ................................................................................ 342
14.5 Handling Buy-Off Notifications ........................................................................................... 347
14.6 Handling Quality Non-Conformances................................................................................. 348
Opcenter Execution Discrete 4.2 - User Manual ix

15 How to Monitor and Tweak Production Execution .......................................352
15.1 Viewing Work Order Progress .............................................................................................. 352
15.2 Viewing Work Order Genealogy........................................................................................... 353
15.3 Displaying Historical Data ................................................................................................... 356
15.4 Tracking Additional Actions ................................................................................................ 360
15.5 Monitoring Work Order Operations in Execution on a Workcenter or Machine................ 361
15.6 Associating Additional Users to Work Order Operations ................................................... 362
15.7 Updating the Labor Time..................................................................................................... 363
15.8 Viewing and Amending the Results of a Material Tracking Unit ........................................ 363
15.9 Displaying Powder Genealogy............................................................................................. 365
15.10 Tracking Non-Conformance Histories ................................................................................ 366
15.11 Monitoring and Managing Output Messages at Runtime................................................... 367
15.12 Monitoring and Managing Kanban Calls ............................................................................. 368
16 How to Integrate Opcenter Execution Discrete with Other Systems ...........370
16.1 How to Benefit from Integration with Siemens Opcenter APS .......................................... 370
16.1.1 Scheduling Work Orders/Work Order Operations from Opcenter APS ........................................................... 370
16.1.2 Verifying the Download of Scheduled Work Orders/Work Order Operations to Opcenter Execution
Discrete............................................................................................................................................................... 371
16.2 How to Benefit from Integration with DNC Systems .......................................................... 372
17 Deprecated Functionalities ............................................................................373
17.1 Configuring Defects (Deprecated)....................................................................................... 373
17.2 Configuring 3D Printers (Deprecated)................................................................................. 375
17.3 Configuring Powder Materials (Deprecated) ...................................................................... 375
17.4 Creating Powder Material Batches (Deprecated) ............................................................... 376
17.5 Recycling Powder Material Batches (Deprecated) ............................................................. 378
17.6 Mixing Powder Material Batches (Deprecated) .................................................................. 378
17.7 Displaying Powder Genealogy (Deprecated) ...................................................................... 382
x Opcenter Execution Discrete 4.2 - User Manual

ID OpcenterEXDS_UserManual
Title User Manual
Product Title Opcenter Execution Discrete
Version Title 4.2
Product Version OpcenterEXDS_4.2.0.0
Category Runtime
Summary Provides detailed information on how to use the Opcenter

Execution Discrete web user interface.
Audience Operator, Supervisor, Support Engineer
Revision PL20210504131482743
State Published
Author Siemens AG
Language en-US
Opcenter Execution Discrete 4.2 - User Manual 11

Basic Know-How Before Getting Started
1 Basic Know-How Before Getting Started

Before you start using the Solutions released by Opcenter Execution Discrete, here are the essentials to familiarizing
with the application, performing basic operations and taking advantage of certain Apps.
 This Manual provides detailed information on how to work within the UI Applications installed with the
product without specifying which App or Extension App provides each functionality. The same procedures
can be used as a reference also for custom solutions, provided that their UI Applications include the UI
modules and screens of the Apps or Extension Apps related to each functionality.
Released Solutions
Opcenter Execution Discrete includes the installation of the following Solutions:
• U4DM, dedicated to the management of Discrete functionalities in a complex production environment that may
include also Additive Manufacturing activities. It includes the Siemens_SIT_UADM UI Application.
• DS4AM, dedicated to the management of small production environments focused on Additive Manufacturing
activities. It includes the Siemens_OPC_EXDS_AM UI Application.
The operations to be performed in the UI Applications provided by both Solutions are described in the current
manual.
Accessing the Applications

1. Access the login page clicking the Opcenter Execution Discrete shortcut.
 The direct paths of the Applications are:

• http://<hostname>/sit-ui/runtime/U4DM.Siemens_SIT_UADM
• http://<hostname>/sit-ui/runtime/DS4AM.Siemens_OPC_EXDS_AM
2. Log in to the Opcenter EX DS web page in either of the following ways:

• Insert the credentials of a valid user and click Sign In.
• Click Use your current Windows session to Log In to access the application with the current user
credentials.
The Home Page

The Home page represents your starting point for familiarizing with the product. It contains all available tiles for
accessing the numerous pages containing the available functionalities. To facilitate navigation within the Home
Page, these tiles have been grouped on the basis of the type of functionalities they offer:
• Production Coordination: tiles for assisting Production Coordinators in monitoring production inside their
plant and work in progress, as well as for verifying data acquired during production.
• Shopfloor Execution: tiles for assisting Operators in their tasks on the shopfloor during execution in regard to
work order progress and history, logistics, additive manufacturing, etc.
• Product and Production Configuration: tiles for creating and configuring entities representing the essential
engineering elements that come into play to execute production.
• System Configuration: tiles related to basic functionalities as configuration keys, log management or template
configuration.
The Home Page comes provided with four dedicated navigation cards representing the aforementioned tile groups:
clicking the card of your choice allows you to jump directly to the tile group containing the tile you require, and
then clicking each tile allows you to jump to the related page. Unlike the home page, all other pages contain a
sidebar displaying icons that correspond to the aforementioned tile groups, thus allowing you to easily access each
12 Opcenter Execution Discrete 4.2 - User Manual

Apps and Extension Apps included in the Discrete Solution
page without returning to the home page. All procedures contained in this manual describe how to access the UI
Application pages from the sidebar, but you can also start from the home page searching for the related tile name.
 If desired, this standard layout can be modified according to your needs: for example, it is possible to
create custom navigation cards or move tiles from one category to another of your preference. For
information on these customizations, see Configuring the UI Application Menu in the Opcenter Execution
Foundation Development and Configuration Guide.
In addition, to facilitate navigation, you can focus solely on certain tiles that satisfy your needs by using the Search
filter provided at the top of the Home page: if you enter a text in the Search filter, only those tiles containing it in
their label will be displayed, according to the tile group to which they belong.
Selecting and searching for elements

All pages come provided with both a Smart Filter and a dynamic Search. Fields that accept elements of a list as
input offer both a dynamic filter and a Browse button, which opens a dedicated search window.
On pages that display elements in tile format, you can access the element details in the following ways:
• selecting the tile and clicking Open.

• clicking on the upper-right corner of the tile.
Applying User Preferences

User Preferences can be used to customize the look and feel of your UI in intuitive ways. You can customize the
current view by setting User Preferences. Click the button to choose the column visibility, column order, and
tile property visibility. You can specify the properties you want to show, and their sequence. For more information,
see Setting User Preferences in the Opcenter Execution Foundation Development and Configuration Guide, and
Opcenter Execution Foundation Apps Overview in the Opcenter Execution Foundation User Manual.
Import and Export of Data from the Runtime Database

If the system is properly configured, in several screens you can click Export to download selected entities and
instances from the database. The data can be subsequently modified and eventually imported on the same or
another production machine. For details, refer to the How To Export and Import Data section in the Opcenter
Execution Foundation User Manual.
1.1 Apps and Extension Apps included in the Discrete Solution

The Opcenter Execution Discrete Solutions include the installation of a set of Apps and Extension Apps either
specific to Discrete manufacturing or provided by the underlying platform. The following sections list them
providing an overview of the related functionalities.
Opcenter Execution Discrete Apps

Name Provided Functionalities U4DM DS4AM

Solution Solution
AppU4DM Core functionalities for managing

production execution in Discrete
manufacturing context.
BoP Bill of Processes, Catalogs and

Master Plan management
MaterialTraceability Material consumption tracing.
FunctionalCode Functional Code management.
OutputMessage Output Message management.
QualifCriteria Qualification Criteria management.
Kanban Kanban Call and Line Side Position

management.
AMMaterialRemoteInt Integration between microservices

used for Additive Manufacturing and
services used for Discrete
production.
AMMaterialInt Synchronization of Materials used in

Additive Manufacturing with those
used in Discrete production.
AMEquipmentInt Synchronization of Equipment used

in Additive Manufacturing with those
AMEquipmentRemoteInt Integration between Equipment used

in Additive Manufacturing and those
AMPowderRtRemoteInt Integration between runtime

functionalities of Additive
Manufacturing and those of Discrete
production.
DSAMRemoteInt Integration between services used

for Discrete production and
microservices used for Additive
Manufacturing.


Solution Solution
MaterialAMRemoteInt Integration between Materials used

in Discrete production and those
used in Additive Manufacturing.
PrintJobFile 3D Printing Management.
PowderMgt Powder Management.
EquipmentAMInt Synchronization of Equipment used

in Discrete production with those
used in Additive Manufacturing.
PluginMgt Management of Plugins handling

requests.
PJFPluginMgt Integration between Print Job Files

and Plugins.
RtAMPowderRemoteInt Integration between Materials used

in Discrete production and those
used in Additive Manufacturing at
runtime.
RuntimeAMPowderInt Integration between Powders used in

Discrete production and those used
in Additive Manufacturing, in regard
to runtime functionalities.
PjfRtRemoteInt Integration of Print Job File runtime

management between Additive
Manufacturing and Discrete
production.
RtPJFInt Synchronization of runtime 3D

printing operations between Additive
Manufacturing and Discrete
production.
Opcenter Execution Discrete Extension Apps


Solution Solution
BOPPJF Management of Print Job Files linked to

Bill of Process Operations. It extends the
BoP App.
BoPQC Bill of Process Management (it adds the

possibility of associating Qualification
Criteria to Process Operations). It
extends the BoP App.
DSBPFlow Creation of a default set of

Tasks specific for Discrete
manufacturing. It extends the Opcenter
EX FN BPFlow App.
If necessary you can choose to remove
unnecessary tasks thus speeding up the
Operator Landing page loading.
DSContainer Configuration and management of

production execution on Containers. It
extends the Opcenter EX FN Material
App.
DSMaterial Material Management in Discrete

manufacturing context. It extends
the Opcenter EX FN Material App.
DSResult Result management on Material

Tracking Units and Work Order
Operations. It extends the Opcenter EX
FN Material App.
DSWorkInstruction Work Instruction Management in

Discrete manufacturing context. It
extends the Opcenter EX FN Work
Instruction App.
MaterialMTR Barcode management. It extends

MatTrcCNF Barcode management (it adds the

Default Barcode Rule configuration
key). Extends the
MaterialTraceability App.


Solution Solution
FuncCodeMTR Functional Code management (it adds

the possibility of associating Barcode
Rules to Functional Codes). Extends the
FunctionalCode App.
AppU4DMAM Powder loading management at

runtime for Work Orders and Execution
Groups in additive manufacturing
context. It extends the AppU4DM App.
AppU4DMPJF Print Job File assignment to Work Order

Operations in additive manufacturing
context. It extends the AppU4DM App.
BoPAM Powder loading management at

runtime for Bill of Processes in additive
the BoP App.
MaterialAMInt Material Management in additive

Printer3DPowderInt Integration between 3D Printers and

Powders in additive manufacturing
context. Extends the PrintJobFile App.
PrintJobFileEquipInt Integration between Equipment used in

Discrete production and 3D Printers
used in Additive Manufacturing. Extends
the PrintJobFile App.
PowderMgtRuntime Extends Powder management runtime

functionalities and contains the logic
necessary to perform specific checks on
Discrete production entities. It extends
the PowderMgt App.
Opcenter Execution Foundation Apps


Solution Solution
ApplicationLog Logging and viewing application messages

such as Errors and Warnings for any
Functional Block, App or Extension App in
runtime environment.
Automation Automation Node management.
BPFlow Process Definition management.
DataSegregation Segregation Tag management.

See Note following this table for details.
Defect Failure management.
Equipment Equipment management.
Label Label management.

See Note following this table for details.
Material Material management.
Personnel Person management.

If you want your system to provide Multi-
Plant Support, you must explicitly install the
DataSegregation App (see Note following
this table) and then integrate it with the
Personnel App.
Reference Unit of Measure and Entity Lifecycle

management.
Signals Signal Rule management
System Base entities and functionalities

management. This App is mandatory in any
Manufacturing Solution.
Task Task management.

Managing Multi-Plant Support

Solution Solution
WorkInstruction Work Instruction management.
Barcode Barcode management.
Audit Trail Audit Trail management.
 The Opcenter Execution Foundation Label App is not included by default in the Opcenter EX DS Solutions,
but after installing and configuring it, in the Operator Landing page, as well as in other screens in various
contexts, it is possible to click the icon to manually trigger the printout of specific labels (containing
barcodes, text or images) for particular entities.
Also, the Opcenter Execution Foundation DataSegregation App is not included by default in the Opcenter
EX DS Solutions. To take advantage of its functionalities, it must be explicitly installed and configured: it is
then possible to click the icon to assign segregation tags to specific entities. Should you want your
system to provide Multi-Plant Support, this requires that the DataSegregation App be then integrated
with the Personnel App.
For more information, see Integrating Opcenter Execution Foundation Apps in the Opcenter EX DS Solution in
the Opcenter EX DS Installation and Configuration Manual.
Opcenter Execution Foundation Extension Apps

Solution Solution
OPCUAConnect Integration of the Equipment data model with

the Automation Gateway functionalities. It
extends the Equipment App.
WITask Inspection Definition management at runtime. It

extends the WorkInstruction App.
1.2 Managing Multi-Plant Support

 This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.
Multi-Plant Support comes in handy when you want to limit data visibility in a more targeted manner, simplifying
the content of the screens displayed to users. This possibility is feasible in the production environment, as well as in
the production process, for a number of entities.
The multi-plant support can be managed for all entity types.

Managing Multi-Plant Support
For those users who intend to take advantage of the Multi-Plant Support functionality offered by Opcenter
Execution Discrete in relation to various entities (for example, Materials), a dedicated Assigned Tags pop-up can be
accessed via the Segregation Tags button on the bottom bar. From this pop-up, the currently-logged user can
select one or more among his associated tags to filter data visibility according to his specific needs.
In particular, in runtime, the selections made by the user affect what is displayed in the Work Orders page, as well
as in the Operator Landing Page: for more information, see Creating a Work Order.
Prerequisites
• The Opcenter Execution Foundation Data Segregation App has been appropriately installed and configured.
• The Opcenter Execution Foundation Personnel App has been appropriately configured.
• Data Segregation tags have already been created using the Opcenter Execution Foundation Data Segregation
App and then associated via the Opcenter Execution Foundation Personnel App with the user (referred to as
Person in Opcenter Execution Foundation) who is creating the entities for which multi-plant support can be
managed.
Target User
Users with the Product Engineer and Production Coordinator role can perform this action.
In certain cases, when the entities for which multi-plant support can be managed are created on-the-fly, users with
the Operator role can perform this action.
Procedure
1. Operating on the header bar, click the Segregation Tags button: this opens a pop-up listing all the Data
Segregation tags associated with the currently-logged user.
2. Select those tags that you want to be associated with the entity you are creating.
3. Proceed to create the entity of interest.
Result
Data Segregation tags associated with various entities are displayed:
• in a dedicated column, when entities are displayed in grid mode;
• in the lower part of each tile, when entities are displayed as medium or large tiles (see the following image for
an example).
To change the associated tags, click the icon and, in the Tags Management panel, do the following:
• To assign segregation tags to the selected entity, click .

• To unassign segregation tags from the selected entity, click .

Speeding Up Operator Landing Page Loading through Task Customization
1.3 Speeding Up Operator Landing Page Loading through Task

Customization
Opcenter Execution Discrete comes provided with a pre-defined set of Tasks related to material consumption, Print
Job File management, quality inspection, etc.. This pre-defined set of Tasks forms a Process Definition which is
released by default by Opcenter Execution Foundation and is known as UADMProcessDefinition. When operating
in Runtime, all of the Tasks provided by UADMProcessDefinition are available for use, as they are all loaded into
your system.
Given that your system might not need all of the Tasks available (for example, if you are not working in an Additive
Manufacturing context, you will not require the Task for Print Job File management), you can tailor the contents of
the default UADMProcessDefinition to your needs. By limiting the content of your default UADMProcessDefinition
to one or a sub-set of the available Tasks offered by default, the Operator Landing Page is loaded more quickly.
For more information, see How to Manage Process Definitions in the Opcenter Execution Foundation User Manual.
 Remember that Process Definitions work in synergy with what are known as Operation/Step Categories,
which require appropriate configuration in order to function properly: for more information, see How to
Configure Operation/Step Categories.
Target User
Product Engineer
Procedure
1. Operating in the Home page, click the Process Definitions tile.
2. Select UADMProcessDefinition and then click Copy Revision in the sidebar on the right: this opens the
Copy Revision dialog.
3. Enter values for Id and New Revision and click Save: the copy of the Revision is now listed as a Process
Definition in the Process Definitions page.
4. Select the Process Definition you have just made.

5. Click Open the flow editor for the selected process definition in the sidebar on the right: the flow editor
opens, displaying the complete set of Tasks making up the original default UADMProcessDefinition.
6. Operating in the flow editor, click each Task that you want to eliminate: a broken-line border is displayed
surrounding the Task.
7. On the broken-line border, click the Delete icon on the horizontal icon bar at the top of the flow editor: the
selected Task is removed.
8. Repeat step 6 for each of the remaining Tasks that you want to remove.
 You can leave a single Task, or a combination of Tasks inside the Process Definition you are editing,
according to your needs.
9. Click Save in the sidebar on the right: the selected Process Definition now contains solely those Tasks of
your preference.
10. Click Set Current in the sidebar on the right and then click Yes.
11. Click Set Executable in the sidebar on the right and then click Yes.

Quick Start to Using Opcenter Execution Discrete
2 Quick Start to Using Opcenter Execution Discrete

Here is a general outline of the main macro-steps that must be executed in order to use Opcenter Execution
Discrete properly and to full advantage.
Keep in mind that:
• not all users can perform all the operations cited: before attempting to perform the operation(s) making up a
macro-step, check that you possess the appropriate user rights to do so.
• some operations are not available in the Siemens_OPC_EXDS_AM UI Application.
 Integration with Other Systems

If you intend to use Opcenter EX DS in integration contexts, before proceeding with the Workflow below,
see How to Integrate Opcenter Execution Discrete with Other Systems for dedicated information.
Prerequisites
• The shortcut containing the URL to the Opcenter EX DS web user interface has been copied from the desktop of
the production machine (where the shortcut has been created by the Opcenter EX DS configuration tool)
to the desktop of the web client machine. The URL in the shortcut's properties has been modified, changing the
machine name accordingly.
Note SSL connections are also supported.
• The hosts file, available in %windir%\System32\drivers\etc, maps the production machine hostname to the IP
address.
Workflow
1. Configure the production environment.
2. Create and prepare Human Resources and their capabilities.
3. Configure the production processes.
4. Prepare production execution.
5. Execute Work Orders.
6. (optional) Execute production on Execution Groups.
7. Manage Non-Conformances.
8. Monitor (and, if necessary, tweak) production execution.
Additional Operations
• Manage Buffer replenishment and transport operations.
• Manage Non-Productive Activities.
• Handle Notifications.
• Execute production in Offline mode.
• Configure and manage Output Messages.

How to Configure the Production Environment
Applying General Configuration Settings
3 How to Configure the Production Environment

Before configuring the production processes you want to manage, you must properly configure the system, defining
the structure of the plant in which the production processes will take place, and then configuring a set of basic
entities that will be used to model the production activities.
Workflow
1. Perform General Configurations.
2. Define the Plant Structure.
3. Configure the Identifier Templates.
4. Configure the Reasons.
5. Configure the Tool Definitions.
6. (for Additive Manufacturing) Configure the Substrates.
7. (optional) Configure the Custom Logistic Classes.
8. Configure Buffer Definitions.
9. Configure the Materials.
10. (for Additive Manufacturing) Configure Powder Materials.
11. Configure Container Types.
12. Configure Operation/Step Categories.
13. Manage Catalogs.
14. (for Additive Manufacturing) Configure Plugins.
15. (for Additive Manufacturing) Configure 3D Printers.
16. Configure Failures.
17. Configure the Rework Codes.
18. Configure Non-Productive Activities
19. (for Additive Manufacturing) Configure Print Job Files.
20. (for DNC Integration) Import and Map CNC Packages.
21. Configure Work Operations.
22. Configure Custom Non-Conformance Lifecycles.
23. Configure Custom Interlocking Checks.
24. (optional) Configuring Custom Result Types.
25. Associate Items with Buffer Definitions.
26. Configure Setpoints.
27. Configure the Barcode Rules.
28. Configure Line Side Positions.
29. Configure Qualification Criteria.
3.1 Applying General Configuration Settings

The system provides a dedicated page for accessing the general parameters that you must set to pre-configure the
system before starting to work with it.
The parameters are grouped by logical functionality.
Target User
Users with the Product Engineer role can perform this action.
Procedure
1. Click System Configuration > Configuration Keys in the sidebar.
2. Select one of the following tabs and set the relative parameters according to your needs:

• Engineering
• Runtime
• Additive Manufacturing
• Integrations
• E-Mail
• CLM Integration
• Certifications
3. Click Save.
3.1.1 Engineering Configuration Settings

The following General Configuration Settings are related to Engineering functionalities.
Configuration Key Description
Enable automatic Work Order Header Defines how the system must manage the Work Order Headers.
merge
Possible values:
• NO: Work Order Headers are not automatically merged
with As Planned BOPs (default behavior).
• DEFAULT: a Work Order Header is automatically merged
with a downloaded As Planned BOP. The generated Work
Order is then released for production according to the
setting of the Enable automatic Work Order Header
release configuration key.
• CUSTOM: Reserved for custom project implementations.
Note This configuration key is not available in
the Siemens_OPC_EXDS_AM UI Application.
Enable automatic Work Order Header Defines how the system must manage the release of Work
release Orders generated from Work Order Headers that have been
automatically merged with downloaded As Planned BOPs.
Possible values:
• NO: Work Orders are not automatically released for
production.
• DEFAULT: Work Orders are automatically released for
production (default behavior).
Non-Conformance Lifecycle for Machine Identifier of the Lifecycle used for Quality Non-
Conformances associated with Machines.
The default value corresponds to the Lifecycle provided by the
system. If you configured a custom Non-Conformance
Lifecycle, you can insert its identifier here.

Non-Conformance Lifecycle for Material Identifier of the Lifecycle used for Quality Non-
Tracking Unit Conformances associated with Material Tracking Units.
Non-Conformance Lifecycle for Tool Identifier of the Lifecycle used for Quality Non-
Conformances associated with Tools.
Non-Conformance Lifecycle for Work Order Identifier of the Lifecycle used for Quality Non-Conformances
associated with Work Order Operations.
Non-Conformance on Defect or Failure Used to change the behavior of the system when creating Non-
Conformances on Machines, Material Tracking Units, Tools and
Work Order Operations.
• Defect: This is the default setting. You will be prompted to
select Defects and Defect Groups.
• Failure: You will be prompted to select custom Failures
and Sub-Failures.
Save Quick Search If the check-box is selected, the system saves the last search
criteria used and proposes it to the user when a new search is
performed.

Use Latest Version of As Planned BOP (Used in case of integration with Teamcenter Manufacturing)
Defines how the system must behave if some changes have
been made on the As Planned BOP in terms of Material, Tool
Definition, Operations or Steps.
Possible values:
• NO: Out-Of-Date As Planned BOPs can be used to generate
Work Orders (default behavior).
• DEFAULT: The system verifies if an out-of-date version of
the As Planned BOP is available in Opcenter Execution
Discrete and, in this case, requests that the entire structure
be downloaded from Teamcenter Manufacturing.
3.1.2 Runtime Configuration Settings

The following General Configuration Settings are related to Runtime functionalities.
Auto-Consume Batch Materials This configuration key defines the behavior of the Auto-
Consume Batch Materials toggle in the Operator Landing page.
If this check-box is selected, automatic generation and
consumption of batch materials is enabled by default for the
whole production.
You can disable it centrally using the configuration key or you
can use the toggle in the Operator Landing page to disable it
only for the Work Order Operation in execution.
Global automatic Non-Conformance close If the check-box is selected, whenever a Non-Conformance is set
upon Scrap to Scrap and is associated with one of the following entities:
• Work Orders
• Tools
• Material Tracking Units
• Equipment
thereby causing the entity to be scrapped, the system
automatically closes all the other Non-Conformances associated
with the entity.
Default Barcode Rule The default Barcode rule to be used to validate the Material if
there are no rules set.

Result Management Selecting a value from this list determines:

• Whether Result management is enabled or not.
• The default value that is set for what is displayed in the
Complete Work Order Operation Options panel.
Possible values:
• OFF: Result management is disabled.
• OK: Result management is enabled: in this case, OK is
selected as the default value for the Result column displayed
in the Complete Work Order Operation Options panel.
• NOK: Result management is enabled: in this case, NOK is
selected as the default value for the Result column displayed
in the Complete Work Order Operation Options panel.
• N/A: Result management is enabled: in this case, no default
value is selected for the Result column displayed in the
Complete Work Order Operation Options panel.
 Once Result management has been enabled, if the

Result Types provided by default in Opcenter Execution
Discrete do not satisfy your needs, you can configure
custom Result Types.

Complete Serial Number(s) without (Only for Serialized and FlexibleSerialized production types) If
pausing others this check-box is selected, only the selected Serial Numbers will
be completed for a specific Work Order Operation, while the
remaining Serial Numbers remain active along with the Work
Order Operation. Otherwise, the remaining Serial Numbers will
be paused.

Result Strategy Management The Result Strategy Management key works in combination
with the Result Management key.
Selecting a value from this list makes it possible to determine the
corrective actions to be adopted by default when result
management is enabled.
Possible values:
• Repeat (default): The failed Work Order Operation will be re-
executed for the Batches or Serial Numbers (MTUs) involved
and then re-evaluated by the Shop-Floor Operator to
determine whether this second attempt was completed
successfully or not. Should the Result still be deemed NOK,
the process of re-execution and re-evaluation will be re-
iterated until the Result is deemed OK.
• N/A: Although it is still possible to declare a Result, no
consequent strategy (corrective action) will be adopted.
Auto-Select First Document If the check-box is selected, when Documents are previewed
from the Operator Landing page, the focus is set on the first
document in the list and its content is also loaded.
Automatic Redirect to details If the check-box is selected, the system automatically displays
the Work Order Operation details, after it has been started.
Check Data Collection If the check-box is selected, whenever a Work Order Operation
associated with Work Instructions is completed, the system
automatically checks that all the Work Instructions have been
completed.
Check Material Consumption If the check-box is selected, Work Order Operations can be
completed only when all required Materials have been
assembled. For Materials to be produced (where the Material
Specification is of type CoProduct or ByProduct), the Work
Order Operation can be completed only when all the Materials
have been produced.

Complete Work Order Operation by Used for configuring Workcenters and/or Machines so that the
Different User Work Order Operations pending on those pieces of Equipment
can be completed also by Users who did not start them.
Possible values:
• YES: If this option is selected, the Work Order Operation can be
completed by any User, even if the User did not start the Work
Order Operation.
• YES with standard behavior: If this option is selected, the
entire Work Order Operation cannot be completed by the User
who started it. A User who did not start the Work Order
Operation can complete it.
• NO: If this option is selected, the Work Order Operation must be
completed by the User who started it.
Create Mat. on Custom Mat. Spec. Type If the check box is selected, in those cases in which the Material
Consumption Tracking Units to be consumed are Custom Material
Specification Types and no such Serial Numbers or Batch IDs are
available for material consumption, the required Material
Tracking Units of the Custom Material Specification Types can be
created on-the fly.
Show Execution Groups in Operator If the check-box is selected, Execution Groups, in addition to the
Landing page Work Order Operations, will be displayed in the Operator
Landing page.
Use Web Workers for data retrieval If this check-box is selected, data in the Operator Landing page
is retrieved in an asynchronous manner (by using Web Workers).
In this modality, the Busy indicator is not displayed while data is
being loaded.
Filter by Users assigned to Work Order If this check-box is selected, the Operator Landing page applies
Operations a filter on the Work Order Operations according to the logged
User.
If the check-box is not selected, the Work Order Operations will
not be filtered by User.

Filter WOOps by logged User and show If this check-box is selected, the Operator Landing page displays
free WOOps by default the Work Order Operations assigned to the logged
User, as well as any Work Order Operations that are not assigned
to any user. If no Work Order Operations have been assigned to
the logged User, then only those Work Order Operations that are
not assigned (that is, the ones that are free) will be shown.
If the check-box is not selected, the Operator Landing page
displays only the Work Order Operations assigned to the logged
User.
PCD Refresh Interval Refresh time (in seconds) of the Production Coordinator
Dashboard.
Refresh Time WIP Refresh time (in seconds) of the Work Order Work in
Progress page.
Show Users having appropriate skills If this check box is selected, the Production Coordinator
Dashboard displays only the Work Order Operations associated
to users with the appropriate skills.
Show only Work Order Operation ready to If the check-box is selected, when the Operator selects a Work
be started Order in the Operator Landing page, the system displays only
those Work Order Operations that can be executed.
3.1.3 Additive Manufacturing Configuration Settings

The following General Configuration Settings are related to Additive Manufacturing functionalities.
Configuration Description
Key
Check Powder Select the check-box if you want the system to validate the value of Current recycle count
Material against that of Maximum Recycle Count. Current recycle count represents the number of
Recycle Count times a recycle operation is performed on a Powder Material batch. With each recycle
operation, the system increments the value of Current recycle count. By selecting this check
box, the system is configured to validate that Current recycle count does not become greater
than Maximum Recycle Count.
Edit Print Job Used for managing and editing values of a specific Print Job File.
File
Select the check-box to enable the editing of the Print Job File details inherited from the CAM
system.

Key
Auto Print Job Select the check-box to manage Additive Manufacturing operations without importing Print
File Job Files locally.
Clear the check-box to manage Additive Manufacturing operations with Print Job Files
imported locally through a dedicated plugin. This is the default behavior.
Check If you select this check box, the system validates the thickness of the Substrate against the
Substrate minimum thickness threshold. If the Substrate's thickness decreases below the threshold
Thickness value that has been set while configuring the Substrate, the Substrate's status is set to On
Hold and it is not available for production.
Note This configuration key is not available in the Siemens_OPC_EXDS_AM UI Application.
Check If you select this check box, the system will validate the treatment count value. If the
Substrate treatment count value rises above the maximum treatment count threshold that has been set
Treatment while configuring the Substrate, the Substrate's status is set to On Hold, and it is not available
Count for production.
3.1.4 Integration Configuration Settings

The following General Configuration Settings are related to Integration functionalities.
Keys
Enable APS Select the check box to enable integration with Opcenter APS.
Integration
Enable DNC Select the check-box to enable integration with DNC systems.
Integration
Enable Select the checkbox to enable integration with any external system, for example Opcenter
External Quality. Integration is enabled via web using the URL indicated in the External System
System URL configuration key.
Integration
External URL of the external system. Any fixed parameter can be passed in the URL: for example,
System URL www.XYZ.com?parametername=parametervalue

Keys
Enable When integration with Opcenter APS is enabled and this check box is selected, receiving a
Unscheduling Work Order Operation with either Estimated Start Time or Estimated End Time fields set to
null from Opcenter APS causes both these fields to be set to null in the corresponding Work
Order Operation in Opcenter EX DS. The Preferred Equipment information is also cleared. This
allows the Work Order Operation to be eventually scheduled again later.
Percentage Type a value (expressed in percentage of the Operation Duration) that represents the
for APS maximum allowed delta between the estimated start time and the actual start time (and the
estimated end time and the actual end time) of a Work Order Operation. If this percentage is
exceeded, this value is considered significant and Opcenter APS receives a dedicated alert in
merit. You can take this into account for your calculations, if desired.
Operation Indicate any Work Order Operation status (for example, Active, Complete) that you want to
Status exclude from scheduling inside Opcenter APS.
excluded
from
Scheduling
DNC Plugin Identifier of the plugin used to import, transfer and preview CNC Packages and their content.
This parameter is meaningful only if the Enable DNC Integration check-box is selected.
Plugin Path Physical path of the DNC plugin file.

This parameter is meaningful only if the Enable DNC Integration check-box is selected.
3.1.5 E-mail Configuration Settings

 The E-Mail tab is not available in the Siemens_OPC_EXDS_AM UI Application.
The following General Configuration Settings are related to the configuration of the server that must be used to
send e-mail notifications whenever a Transition of Quality Non-Conformances occurs. E-mails will be sent to any e-
mail address that has been properly configured within the corresponding Transition.
 Before starting with the configuration of these keys, verify that the Enable secure application data
support for users and groups check-box is selected from the UMC Home page > Account Policies >
Advanced tab.

Sender of Non-Conformance E-Mail The e-mail address from which e-mail notifications are sent. For
example, if your SMTP server is smtp.acme.com, an example of
the e-mail address is admin@acme.com.
Text for Non-Conformance e-mail The customized message contained in the e-mail notification that
message is sent by the SMTP server. In addition to the message, the SMTP
server also appends the following details about a Non-
Conformance:
• NId
• Non-Conformance Lifecycle
• Work Order
• Work Order Operation
• Equipment
• Tools.
SMTP server host The SMTP server that the system uses for sending e-mail
notifications for Non-Conformances. For example,
smtp.acme.com.
SMTPS (implicit SSL) Selecting this check box indicates that the Simple Mail Transfer
Protocol Secure (SMTPS) protocol is used to secure e-mail
communication at the transport layer. If you select this check
box, the default value of SMTP server port will be 587. If you do
not select this check box, the default value of SMTP server port
will be 25.
SMTP server port The port that the SMTP server uses to send e-mails. If this key is
left blank, the default value will be 25, provided that the SMTPS
(implicit SSL) check box is not selected. Instead, if the SMTPS
(implicit SSL) check box has been selected, the default value for
SMTP server port will be 587.
Password for SMTP authentication The password for the SMTP account.
Username for SMTP authentication The username for the SMTP account from which e-mail
notifications are sent.
SMTP over TLS (explicit SSL) Selecting this check box indicates that the SMTP server uses
Secure Sockets Layer (SSL) protocol for e-mail communication.
3.1.6 CLM Integration Configuration Settings

 The CLM Integration tab is not available in the Siemens_OPC_EXDS_AM UI Application.
The following General Configuration Settings are related to the integration of Opcenter Execution Discrete
with Teamcenter Manufacturing within the context of Closed-Loop Manufacturing (CLM).

 Before starting with the configuration of these keys, verify that the Enable secure application data
support for users and groups check-box is selected from the UMC Home page > Account Policies >
Advanced tab.
Enable CLM Integration Selecting this check-box enables the integration for Teamcenter
Manufacturing, ERP and PLM.
Integration Password The password of the user logged into the Teamcenter Manufacturing
platform.
Integration User The name of the user logged into the Teamcenter Manufacturing
platform.
Event Notification Web Service Opcenter Execution Discrete uses this URL to notify events to external
URL systems like Teamcenter Manufacturing and SAP.
Issue Report Web Service URL When users change the status of the Non-Conformance to “Escalate for
engineering review”, Opcenter Execution Discrete uses this URL to submit
the Non-Conformance information for engineering review.
ERP WO Confirmation Web Opcenter Execution Discrete uses this URL to submit Work Order
Service URL complete notifications.
Note Do not configure this key, if you want to be notified in regard to
Work Order Operation completion.
ERP WOOp Confirmation Web Opcenter Execution Discrete uses this URL to submit Work Order
Service URL Operation complete notifications.
Note Do not configure this key, if you want to be notified in regard to
Work Order completion.
AsPlannedBOP Opcenter Execution Discrete uses this URL to request a BOP skeleton for a
Transfer Service URL specific product and process configuration.
Update WO from Generic System Opcenter Execution Discrete uses this URL to request a BOP skeleton for a
Web Service URL specific product and process configuration.
Note Use this configuration key only in the case of custom developments.
3.1.7 Certification Configuration Settings

 The Certification tab is not available in the Siemens_OPC_EXDS_AM UI Application.

The following General Configuration Settings are related to Certifications.
Certification Management Used for defining how the certifications must be verified at
runtime. Possible values:
• AND: The system checks for valid certification for both
Materials and Equipment Type. When this value is selected,
The User who starts, pauses or completes a Work Order
Operation must possess a valid certification for the Final
Material produced by the Work Order and a valid certification
for the Machine used by the Work Order Operation.
Furthermore, the Skills owned by the User, if required, are
checked according to the value of the Validate Certifications
according to Skills key.
• OR: The system checks for valid certification for Materials or
Equipment Type. When this value is selected, the User who
starts, pauses or completes a Work Order Operation must
possess a valid certification for the Final Material produced by
the Work Order or a valid certification for the Machine used by
the Work Order Operation. Furthermore, the Skills owned by
the User, if required, are checked according to the value of the
Validate Certifications according to Skills key.
• NO: The system does not check for any certification.
Consequently, Skills are not checked.
Validate Certifications according to Used to configure how the system must evaluate the Skills
Skills associated with a Certification.
• NO: The system validates the Certification regardless of the
associated Skills.
• OR: The system validates the Certification if at least one of the
associated Skills is verified.
• AND: The system validates the Certification only if all
associated Skills are verified.
Enable Certification Skill Level Filter Used to configure how the system validates the level of the Skills
associated with the Certification.
This key is meaningful only if the value of the
Validate Certifications according to Skills key is set to OR/AND.
• NO: The system does not check the skill level.
• EQUAL: The Certification is valid when it includes a Skill with
level equal to the Skill level required by a Work Order
Operation.
• EQUAL OR GREATER THAN: The Certification is valid when it
includes a Skill with level greater than or equal to the Skill level
required by a Work Order Operation.

How to Define the Plant Structure
3.2 How to Define the Plant Structure

The first step in the configuration of the production environment is the definition of the plant structure, in which
you create a virtual representation of the plant by creating a set of Equipment and organizing them within a
hierarchical structure.
The procedure below indicates the steps required for the creation of a Plant structure. Complex configurations are
possible, for more information, see Equipment App in the Opcenter Execution Foundation User Manual.
If you decide to arrange Equipment Configurations in a Hierarchy, you should follow the recommended
configuration as described in section Business Plant Model: Equipment Levels and Machines of the Opcenter
Execution Discrete Product Overview. This configuration guides you in the association of the Machine to be used at
runtime during Work Order Configuration, by filtering out those that are not related to the linked Site.
Following situations are possible:
• One Hierarchy designed according to the recommended configuration: filter is applied and only the Machines
related to the linked Enterprise/Site will be listed.
• No Hierarchy, but flat Equipment Configurations are available: no filter is applied and you can associated any
Machine of your choice
• More than one Hierarchy having the same Equipment Configurations of type Enterprise/Site: no filter is applied
and you can associated any Machine of your choice.
Target User
Users with the Production Coordinator or Product Engineer role can perform this action.
Workflow
1. Create Equipment Configurations.
2. (Optional) Configure the Equipment Hierarchy.
3.2.1 Creating Equipment Configurations

While defining the Plant structure, the first step is to create the entities that hierarchically represent the pieces of
physical Equipment. Each piece of Equipment is an Equipment Configuration. All Equipment Configurations may be
then organized in an Equipment Hierarchy to represent your plant.
If anomalies or defects are discovered on existing Machines, it is possible to declare Quality Non-Conformances on
them, either by an Operator at runtime or by a Production Coordinator.
Equipment Configurations can also be associated to Automation Node Instances, to benefit from the integration
with the Shop-Floor, for example for the semi-automatic acquisition of values or for driving the execution behavior
for Tools and Materials.
For more information on Automation Nodes, see How to Manage Automation Nodes of the Opcenter Execution
Foundation User Manual..
For more information on how to associate Equipment Configurations to Automation Node Instances see section
How to Configure the Association between Equipment and Automation Gateway of the Opcenter Execution Foundation
User Manual
The procedure below provides step by step instructions on how to create all Equipment the production plant
consists of, including 3D Printers that, in addition, can also be created from the 3D Printers page.
Procedure
1. Click Product and Production Configuration > Equipment Configurations in the sidebar.

2. Click Add Equipment Configuration.

3. Set the following parameters:
Parameter Description
Id The unique identifier assigned to the Equipment Configuration. Once

the Equipment Configuration is created, the Id value cannot be modified.
Name (Optional) The name assigned to the Equipment Configuration.
Description (Optional) Additional information on the Equipment Configuration.
Equipment (Optional) The Equipment Type to be used to define the Equipment Configuration content.
Type Once the Equipment Configuration is created, the Equipment Type value cannot be
modified. If the parameter is not selected, the system automatically uses the Equipment
Type that is currently set as default, and if the default Equipment Type does not exist, the
system creates an empty Equipment Configuration.
 If you are configuring a Machine, select the UADM Equipment Type, to

automatically assign the default properties to the Equipment Configuration. The
UADM Equipment Type also provides the UADMEquipmentLifecycle state
machine.
Level The position of the Equipment Configuration in the hierarchy. According to the selected
parent Equipment, either all or a subset of the following options are displayed:
• Enterprise, the upper level, it represents the entire company.
• Site, may be a physical plant or a factory owned by the company.
• Area, may be a sector within a factory.
• WorkCenter, may represent a Workcenter and is focused on a specific type of
production.
• ProcessCell, may represent a Workcenter and is focused on a specific type of
production.
• ProductionLine, may represent an assembly line.
• StorageZone,
• WorkUnit
• Unit, may represent a workstation where a single operation is performed (for
example, door stamping in a car manufacturing plant).
• WorkCell,
• StorageUnit,
• ProductionUnit,
4. Click Save.
5. Repeat steps 2-4 for each piece of Equipment to be added to your plant.
6. In case of Equipment Configurations mapped to the Unit level, if you have associated the UADM Equipment
Type, click the Properties tab, to configure the following default properties according to your needs:
Is3DPrinter If the value is set to True, the piece of Equipment represents a 3D

Printer to be used in Additive Manufacturing.

AMMachine Identifier of the 3D Printer in the external system that generated

the Print Job File.
(only if Is3DPrinter is True)
Note This parameter can also be set while configuring the 3D
Printers.
TransferPlugin The name of the Plugin that manages the Print Job File transfer.
Note This parameter can also be set while configuring the 3D
(only if Is3DPrinter is True)
Printers.
EnabledForCompleteByDifferentUser If the value is set to True, the Work Order Operations assigned to
this piece of equipment can be completed by a user differing from
the user who started them, according to the selected option for
the Complete Work Order Operation by Different
User configuration key.
Lockable If the value is set to True, the Equipment associated with a Work
Order Operation will be marked as Locked during the execution
of the Operation and will be unavailable for concurrent use.
Equipment that has been locked can be unlocked manually. From
the State Machine tab of the Equipment Management page,
change the Equipment status clicking the Set Equipment Status
button and setting the Status Transition Verb parameter to

from Busy to Ready.
 Equipment of Unit level does not inherit the setting of

this parameter from its Workcenter parent Equipment.
3.2.2 How to Design the Equipment Hierarchy

Once created, the Equipment Configurations may be arranged in a Hierarchy in order to be used in production.
Workflow
1. Create the Equipment Hierarchy.
2. Configure the Equipment Hierarchy.
Creating the Equipment Hierarchy

1. Click Product and Production Configuration > Equipment Hierarchy Configurations in the sidebar.
2. Click Add Equipment Hierarchy Configuration and set the following parameters:
Id The unique identifier assigned to the Equipment Hierarchy. Once

the Equipment Hierarchy is created, the Id value cannot be modified.

Configuring Identifier Templates
Name (Optional) The name assigned to the Equipment Hierarchy.
Description (Optional) Additional information on the Equipment Hierarchy.

3. Click Save.
Configuring the Equipment Hierarchy

1. In the Equipment Hierarchy Configurations page, select the previously created Equipment Hierarchy from the
list on the left.
2. Do either of the following:
• If the Equipment Hierarchy is empty, click Add Node in the toolbar.
• If the Equipment Hierarchy already contains Equipment, select the node below which you want to add
other Equipment.
3. Select the Equipment of interest.
4. Click Save.
5. The selected Equipment are displayed as a flat list below the previously selected node (or at root level if no node
had been selected): organize the Equipment hierarchically dragging and dropping them to the proper position.
When you move a node, also the underlying nodes are automatically moved.
3.3 Configuring Identifier Templates

Each entity within the system is characterized by a unique identifier: you are prompted to define it while configuring
the items involved in your production processes.
In addition, during the configuration of specific entities (Serial Numbers, Material Batches and Work Orders), you
can choose to either insert this identifier manually or generate it automatically according to a predefined template.
The definition of an Identifier Template consists of two phases, which can be performed at different times. In the
first phase, you create the template, but, at this point, it is simply a container that cannot be used to generate
unique identifiers. The final structure of the identifiers is defined during the second phase in which you specify the
sequence of text chunks (called Template Blocks) to be used to form the identifier.
Once defined, an Identifier Template cannot be renamed, but you can modify the Template Blocks it contains at
any time.
Accessing the Working Environment

To access the Identifier Templates page, click System Configuration > Identifier Templates in the sidebar.
Target User
Workflow
1. Create the Identifier Template.
2. Configure the Identifier Structure.
Creating the Identifier Template

1. Click Create a New Template.

Template Type One of the following:

• WorkOrderNId, to create a Template for Work Order
Identifiers.
• SerialNumber, to create a Template for Serial Number
Identifiers.
• MaterialBatchId, to create a Template for Material Batch
Identifiers.
Identifier A meaningful name to be used to identify the Template. Once saved,

this parameter can no longer be modified.
3. Click Create.
Configuring the Identifier Structure

Perform these operations to configure each Block to be used to form the Identifier Template:
1. Select the Identifier Template and click Open.

2. Click Begin Editing.
3. Click Add.

Block Type Define the type of information the Block will display by selecting one of
the following options:
• Order NId: The unique identifier of the Work Order currently
being executed. This block does not apply to the Work Order
template.
• Material NId: The unique identifier of the Material currently
being produced.
• Year: The current year (Local Time). If you select the Extended
year check box, the year is expressed with four digits;
otherwise, it is expressed with two digits.
• Month: The current month (Local Time). If you select the Zero
padding check box, single-digit values are always expressed
with a trailing zero.
• Day: The current day (Local Time). If you select the Zero
• Hour: The current hour (Local Time). If you select the Zero
• Minute: The current minute (Local Time). If you select
the Zero padding check box, single-digit values are always
expressed with a trailing zero.
• Second: The current second (Local Time). If you select
the Zero padding check box, single-digit values are always
expressed with a trailing zero.
• Millisecond: The current millisecond (Local Time). If you
select the Zero padding check box, values are always
expressed with three digits, with the addition of trailing
zeroes, if necessary.
• Incremental: A numerical value that increases whenever an
identifier is generated. After selecting this option, specify the
number of digits in the No. digits edit box, and then the value
immediately following the current one in the Next value edit
box. In addition, if you select the Zero padding check box, the
values are always expressed with the same number of digits,
with the addition of adding trailing zeroes, if necessary.
 Mandatory field. Its position within the sequence of

the template is not fixed.
• Separator: A custom text to be inserted in the Value edit box.

This block, unlike the others, can be specified multiple times,
with different values.
Sequence A number that identifies the position of the Block inside the Template.
Once a block has been saved, you can change its position within the
Template, by simply selecting it and then clicking the Edit button.
5. Click Save.

Configuring Reasons
6. Click Close Editing Session.
3.4 Configuring Reasons

Before starting the production execution, you must configure a set of Reasons, which will be used at runtime by the
operator, in case the execution of a Work Order Operation is stopped and the action must be justified.
Target User
Procedure
1. Click System Configuration > Reasons in the sidebar.
2. In the Reason page, click Create.
Reason A description of the Reason, for which the operator stops the Work
Order Operation at runtime.
Type Select one of the following options:

• Hold, the Reason can be selected setting a Work Order in
Hold status.
• FutureHold, the Reason can be selected setting a Work
Order in Future Hold status.
• Pause, the Reason can be selected pausing a Work Order
Operation.
• Skip, the Reason can be selected when skipping a Work
Order Operation at runtime.
Workcenter If you have selected the Pause option from the Type drop-down list
box, select the relative Workcenter.
4. Click Create.
3.5 How to Configure Tool Definitions

A Tool Definition represents the type of Tool involved in production. While configuring the production environment,
you can create Tool Definitions, on the basis of which Tools will be created at runtime.
Depending on your needs, through appropriate configuration, you can create two types of Tool Definitions:
• Tool Definitions for creating tools in general (Tools),
• Tool Definitions for creating specific tools known as Substrates, which are peculiar to Additive Manufacturing.
At runtime, you can instantiate Tools and Substrates from their respective Tool Definitions. Both Tool Definition
types are configured from the Tool Definitions page. The procedures involved in configuring Tool Definitions for
creating Tools in general is described in the following section. For information on setting parameters for Tool
Definitions to be used to generate Substrates, see Configuring Substrates.

How to Configure Tool Definitions
Regardless of whether the Tool Definition you are configuring is to be used to create generic Tools or Substrates,
you can:
• update a Tool Definition to modify details, such as its name and description.
• delete a Tool Definition, provided that it is not associated with a Work Order Operation or a Step.
You can associate previously configured Automation Node Types to the Tool Definitions, in order to automatically
acquire the data of the related Tools at runtime. This operation is necessary if you want to use Setpoints
(alternatively you can associate Automation Node Instances directly with the Tools). For detailed information
on Automation Node Types, see the Opcenter Execution Foundation User Manual.
Workflow
1. Create a Tool Definition in one of the following ways:
• From Scratch
• Creating a Revision of a Tool Definition
• Copying a Tool Definition
2. Associate Automation Node Types to the Tool Definition. (This functionality is not available in
the Siemens_OPC_EXDS_AM UI Application.)
3. Display compatible Setpoints. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)

To access the Tool Definitions page, click Product and Production Configuration > Tool Definitions in the
sidebar.
Target User
Users with the Product Engineer role can perform this procedure.
Creating a Tool Definition from Scratch

1. In the Tool Definitions page, click Create.
2. Set the following general parameters according to your needs:
Natural Identifier Unique identifier to be assigned to the Tool Definition. Once

saved, this parameter can no longer be modified.
Revision Identifier of the Tool Definition's Revision.
Name Name of the Tool Definition.
Description Useful information about the Tool Definition.
Consumable If this check box is selected, the Tools instanced from this
Tool Definition will be marked as "consumable" in the
Operator Landing page, to remind the User to insert the ID
of the Tool instance used during the execution of the Work
Order Operation.

Substrate Selecting this check box indicates that the Tool Definition
being configured will generate a Substrate when it is
instantiated. Substrates are specialized tools that are used
for 3D printing.
Logistic Class Identifier Allows you to logically group similar Tool Definitions for
logistic purposes (for example: transportation, packaging).
Either select a Logistic Class from the list or click the
button to create a new one. For more information on
Logistic Classes, see Configuring custom Logistic Classes.
Volume UoM Unit of Measure related to the Volume of the Tool Definition.
Note This value cannot be changed, if a Tool is instantiated
from the Tool Definition.
Volume Value indicating the unitary volume of the Tool Definition.

For example: for a Tool Definition with UoM= unit , the
Volume is related to a single unit, if UoM = m3 , the Volume is
related to one m3.
Note This value cannot be changed, if the Tool Definition is
linked to a Buffer Definition.
Weight UoM Unit of Measure related to the Weight of the Tool Definition.
Note This value cannot be changed, if a Tool is instantiated
from the Tool Definition.
Weight Value indicating the unitary weight of the Tool Definition.

For example: for a Tool Definition with UoM= unit , the
weight is related to a single unit, if UoM = Kg, the Weight is
related to one Kg.
Note This value cannot be changed, if the Tool Definition is
linked to a Buffer Definition.
Max. Usage Count The maximum number of times a Tool can be used. Every
time a Tool is used, the Usage Counter value is incremented
by 1. If the Usage Counter value becomes greater than the
maximum allowed times a Tool can be used, the Tool status
is set to OnHold, and it is not available for production.
Max. Duration Time (days, hours, minutes, The maximum duration for which a Tool can be used. The
seconds) system monitors the duration of Tool usage. If the usage
duration exceeds this value, the Tool status is set to
OnHold, and it is not available for production.

Expiration Date The expiration date and time of a Tool. Upon reaching this
date, the system sets the Tool status to OnHold, and it is not
available for production.
Lockable If this check box is selected, the Tools instantiated from this
Tool Definition will be locked when used in a Work Order
Operation, thereby making them unavailable for concurrent
use elsewhere.
3. (Only if you intend to use the Tool Definition being created to instantiate a Substrate, with Substrate selected in
the previous step) Set the parameters specific to Substrates.
4. Click Save.
Creating a Revision of a Tool Definition

1. In the Tool Definitions page, select the Tool Definition for which you want to create a new revision.
2. Click Create > Revision: the system automatically increases the revision identifier.
3. If necessary, select the new Tool Definition displayed in the Tool Definitions page and click the button to
modify the name and description of the Tool Definition: the changes are automatically applied to all Tool
revisions.
Copying a Tool Definition

1. In the Tool Definitions page, select the Tool Definition to be copied.
2. Click Create > Copy.
3. Insert a Unique Identifier to be assigned to the new Tool Definition you want to create (Identifier edit box) and
then modify the other parameters as you like (for details, see Creating a Tool Definition from Scratch).
4. Click Create to confirm the operation and return to the Tool Definitions page.
Associating Automation Node Types to Tool Definitions

1. In the Tool Definitions page, select the Tool Definition to be associated with one or more Automation Node
Types and click Open.
2. In the Automation Node Types tab click Link.
3. Select the Automation Node Types to be added and click Save.
 To unlink the Automation Node Type from the Tool Definition, select the association and then click .
Displaying Compatible Setpoints

Perform the following operations to access the list of Setpoints declared compatible with a Tool Definition:
1. In the Tool Definitions page, select the Tool Definition of interest and click Open.
2. Click the Setpoints tab.

Configuring Substrates
3.6 Configuring Substrates

Substrates are considered as a special type of Tool peculiar to Additive Manufacturing and instantiated at runtime
from a Tool Definition that requires specific configuration.
Your starting point remains the procedure for configuring a Tool Definition from scratch, but you must set
additional parameters if the Tool Definition you are configuring is intended for instantiating a Substrate.
The parameters specific to Substrates include minimum thickness, maximum treatment count allowed, current
thickness, and so forth: these parameters can be updated as needed.
In addition, you must associate compatible machines with Substrates. Compatible machines within the context of
Substrates are 3D printers that you previously configured.
 It is possible to force a Substrate to undergo a state transition that differs from what is described in its
lifecycle. For information on states and lifecycles, see the Opcenter Execution Discrete Product Overview.
Target User
Procedure
1. In the Tool Definitions page, click Create.
2. Set the general parameters as described in Configuring a Tool Definition from scratch, taking care to
select the Substrate check box.
3. Set the following additional parameters specific to Substrates:
Min. Thickness Warning (mm) The minimum thickness that a Substrate must have. If the
current thickness of a Substrate falls below this value, the
status of the Substrate is set to Warning Available. The
Substrate is still available for production, but with a warning.
Min. Thickness Hold (mm) If the thickness of a Substrate continues to fall below Min
Thickness Warning, the Min Thickness Hold value represents
the minimum thickness value that the Substrate must have in
order to be available for production. If the current thickness of
a Substrate falls below this value, the Substrate status is set
to OnHold, and it is not available for production. This value is
always less than Min Thickness Warning.
Automatic Thickness Decrease Selecting this check box indicates that you can reduce the
thickness of the substrate by using the one-step Substrate
thickness reduction option. If you do not select this check
box, the Substrate thickness must be set manually. For more
information, see Performing Substrate Treatment.
Amount Set for Automatic Thickness If you selected Automatic Thickness Decrease, this is the
Decrease (mm) value by which thickness is reduced every time you reduce the
thickness of a Substrate. For more information, see
Performing Substrate Treatment.

Configuring Custom Logistic Classes
Max. Treatment Count Warning The maximum number of treatments that a Substrate can
undergo without a warning. If the current treatment count
rises above this value, the Substrate's status is set to Warning
Available, but is still available for production.
Max. Treatment Count Hold If the number of treatments that a Substrate undergoes
continues to rise above Max Treatment Count Warning, the
Max Treatment Count Hold value represents the maximum
number of treatments this Substrate can continue to undergo
until the Substrate becomes no longer available for
production. If the current treatment count rises above this
value, the Substrate's status is set to OnHold, and it is no
longer available for production. This value is always greater
than Max Treatment Count Warning.
Max. Usage Count The maximum number of times a Substrate can be used.
Every time a Substrate is used, the Usage Counter value is
incremented by 1 and if it becomes greater than the
maximum allowed times a Substrate can be used, the
Substrate's status is set to OnHold, and it is no longer
Max. Duration Time (days, hours, The maximum duration for which a Substrate can be used.
minutes, seconds) The system monitors the duration of Substrate usage. If the
usage duration exceeds this value, the substrate status is set
to OnHold, and it is no longer available for production.
4. Click Save.
Adding Compatible Machines

1. In the Tool Definitions page, select the Tool Definition for Substrates to which you want to add a compatible
machine.
2. Click Open.
3. In the Compatible Machines tab, click Add and then select either of the following:
• Machine Definition, if the Substrate must be associated with any Machine belonging to a specific class.
• Machine, if the Substrate must be associated with a specific Machine.
4. In the Add Compatible Machine dialog, select the compatible machines (3D printers) that you want to add, and
click Save.
3.7 Configuring Custom Logistic Classes

A Logistic Class groups together similar Materials or Tool Definitions for transportation. For example, Logistic Class
"Burner Pipes" groups together all burner pipes that are produced in the same Plant and need to be transported.
Opcenter EX DS comes with a predefined default Logistic Class, but it is possible to create custom Logistic Classes
tailored to your needs.

Configuring Buffer Definitions
Through the Opcenter EX DS UI, you can only create and view custom Logistic Classes. Logistic classes cannot be
edited or deleted.
Once defined Logistic Classes can selected while configuring Materials and Tool Definitions.
Target User
Procedure
1. Click the Logistic Classes tile in the homepage.
2. On the Create Logistic Class page, click the Create button.
3. Enter the NId and the Name for the Logistic Class to be created.
4. Click Save.
3.8 Configuring Buffer Definitions

If your manufacturing model uses Intra-Plant Logistics (IPL), prior to starting production execution, you must
configure the Buffer Definitions (that is, the abstract representations of areas or accessories dedicated to item
storage).
It will then be necessary for you to instantiate the actual Buffers you need from their respective Buffer Definitions,
so that these Buffers can be used in runtime.
You can configure a Buffer Definition by adopting one of the following methods:
• Creating a Buffer Definition from scratch: this method permits creating a totally new Buffer Definition.
• Creating a Revision of an existing Buffer Definition: this method permits a differentiation of a Buffer Definition
while maintaining its basic characteristics.
It is then possible to link items to a Buffer Definition so to establish logical constraints on it.

To access the Buffer Definitions page, click Product and Production Configuration > Buffer Definitions in
the sidebar.
Target User
Creating a Buffer Definition from Scratch

1. In the Buffer Definitions page, click Create.

How to Configure Materials
Identifier Unique identifier to be assigned to the Buffer Definition. Once saved, this parameter can
no longer be modified.
Name Name of the Buffer Definition.
Description (Optional) Useful information about the Buffer Definition.
Revision Revision to be assigned to the Buffer Definition.
Capacity Type Select one of the following values:

• Quantity
• Weight
• Volume
Indicates the type of capacity to be used by the Buffer Definition and, consequently, how
the stored items must be measured.
UoM The Unit of Measure to be assigned to the Buffer Definition.
 The Units of Measure presented for selection will be solely those the UoM
Category of which is congruent with the Capacity Type of the Buffer Definition
you are creating.
Max. Value Maximum quantity, weight or volume (according to te selected capacity type, of items
storable by the Buffer Definition).
Is Valid If this check box is selected, the Buffer Definition is valid and can be used for instantiating
actual Buffers. If the check box is not selected, the Buffer Definition cannot be used to
instantiate Buffers (for example, because its definition is still incomplete, or because the
current Revision can no longer be used and a new one needs to be created).
3. Click Create.
Creating a Revision of a Buffer Definition

1. In the Buffer Definitions page, select the Buffer Definition for which you want to create a new Revision.
2. Click Revision.
3.9 How to Configure Materials

Prior to starting production execution, you must configure which types of materials will be involved in the
production processes.
Depending on your needs, through appropriate configuration, you can create two types of Materials:
• Materials for creating Material Tracking Units in general;
• Materials peculiar to Additive Manufacturing (known as Powder Materials) for creating specific Material Tracking
Units known as Powder Material Batches.

 If you are operating in Additive Manufacturing contexts, in addition to this page, see also Configuring
Powder Materials for specific details on particular parameter settings for Powder Materials.
Once created, existing Materials can be modified when desired ( ).

At runtime, you can instantiate Material Tracking Units and Powder Material Batches from their respective
Materials.
You can choose from among three ways to begin configuring a Material:
• Creating a Material from scratch.
• Copying an existing Material.
• Creating a Revision of an existing Material.
You can then associate one or more of the following items with the Material you are configuring:
• a set of Documents to provide useful information about the Material itself.
• Templates.
Likewise, while you are configuring your Material, you can create a Bill of Materials (BoM) to provide the list of raw
Materials for it.
 It is not possible to delete Materials, if they are associated with other entities.
The procedures involved in configuring Materials for creating Material Tracking Units in general are described
below.
Preliminary Operations
• Create Material Classes
• Create Suppliers (optional). This functionality is not available in the Siemens_OPC_EXDS_AM UI Application..
• Create Functional Codes (optional). This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application..

To access the Materials page, click Product and Production Configuration > Materials in the sidebar.
Target User
Workflow
1. Depending on your needs and the extent to which you intend to configure a Material, execute the most
appropriate of the following actions:
• Create a Material from scratch.
• Copy an existing Material.
• Create a Revision of an existing Material.
2. (optional) Associate Documents with the Material.
3. (optional) Associate Templates with the Material.
4. (optional) Associate Suppliers with the Material. .This functionality is not available in
5. (optional) Create a Bill of Materials (BoM) to provide the list of raw Materials for it.

3.9.1 How to Configure Material Classes, Suppliers and Functional Codes

Before creating Materials, you need to configure a series of items to be associated with them which are:
• Material Classes, which represent groupings of Materials for a definite purpose and which must be defined in
order to logically organize Materials,
• Suppliers, which are the external vendors that provide them,
• Functional Codes, which are unique names used to group Materials specifying their functionality or class (for
example, Insulation, Electronics, Hardware and so on).
Available Operations
• Creating Material Classes.
• Creating Suppliers. (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Creating Functional Codes. (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
Creating Material Classes

1. Click Product and Production Configuration > Material Classes in the sidebar.
2. In the Material Classes page, click .
Identifier Unique identifier of the Material Class.
Name Unique user-friendly name to be used to identify the Material Class.
Description (Optional) Useful information on the Material Class.
4. Click Save.
Creating Suppliers
1. Click Product and Production Configuration > Suppliers in the sidebar.
2. In the Suppliers page, click .
Identifier Unique identifier of the Supplier.
Name Unique user-friendly name to be used to identify the Supplier.
Description (Optional) Useful information on the Supplier.

4. Click Save.
Creating Functional Codes

1. Click Product and Production Configuration > Functional Codes in the sidebar.
2. In the Functional Codes page, click .

Identifier Unique identifier of the Functional Code.
Name Unique user-friendly name to be used to identify the Functional

Code.
Description (Optional) Useful information on the Functional Code.

4. Click Save.
3.9.2 Creating a Material from Scratch

By adopting this method to configure a Material, you can set its basic parameters: any associations (a set of
Documents and/or a Template associated with the Material being configured) can be made either immediately or at
a later date.
Procedure
1. In the Materials page, click Add > New Material.
Identifier Unique identifier to be assigned to the Material. Once saved, this

parameter can no longer be modified.
Revision Revision of the Material. Initially, this parameter is blank: it will

be automatically filled upon creating a new Revision.
Name Name of the Material.
Description Useful information about the Material.
Unit of Measure The Unit of Measure to be assigned to the Material. Default is

UNIT (U).
Use Default Template If the check box is selected, the Material will be created using a
default Template.
Template The Template to be used for the creation of the Material. If you
have selected Use Default Template, this field will be disabled.
Serial Number Profile (not available if If the check box is selected, the material is managed through a
Material Class is set to AMPowder) Serial Number and not through a Batch.

First Article Inspection If the check box is selected, when the material is used for the first
time in production, it will require a First Article Inspection.
 Additional custom business logic is necessary to enable

this functionality at runtime.
Logistic Class Identifier Allows you to logically group similar Materials for logistic
purposes (for example: transportation, packaging). Either select
a Logistic Class from the list or click the button to create a
new one. For more information on Logistic Classes,
see Configuring custom Logistic Classes.
Traceable If the check box is selected, the actual Serial Numbers generated
from this Material will be logged so that they can be checked
against production engineering specifications.
Note Regardless of this setting, the Serial Numbers are always
included in the As Built reports.
Material Class Allows you to logically group Materials.
 For Additive Manufacturing, select Material

Class AMPowder, which is provided by Opcenter
Execution Discrete to permit configuring a Powder
Material.
Functional Code Identifier of the Functional Code of the Material.
Volume Unit of Measure Unit of Measure related to the Volume of the Material.
Note This value cannot be changed, if a Material Tracking Unit is
instantiated from the Material.
Volume Value Value indicating the unitary volume of the Material. For example,
for a Material with UoM= unit , the Volume is related to a single
unit; if UoM = m , the Volume is related to one m.
Note This value cannot be changed, if the Material is linked to a
Buffer Definition.
Weight Unit of Measure Unit of Measure related to the Weight of the Material.
Note This value cannot be changed, if a Material Tracking Unit is
instantiated from the Material.

Weight Value Value indicating the unitary weight of the Material. For example,
for a Material with UoM= unit , the weight is related to a single
unit; if UoM = m , the Weight is related to one m.
Note This value cannot be changed, if the Material is linked to a
Buffer Definition.
Barcode Rule The Barcode Rule to be associated to the Material.
Enable Automatic Consumption Determines how Batch Consumption must be managed at

runtime:
• If not selected, a new batch is created on the fly
(standard mode).
• If selected, more batches can be created with the
same Batch Id until a given quantity is reached.
Max. Consumption Quantity (Enabled only if Enable Automatic Consumption is selected)

The maximum quantity that can be consumed re-creating the
same Batch Id. If empty, the same Batch Id will be created more
than once with no limitation.
3. (Only if you intend to use the Material being created to instantiate a Powder Material Batch,
with AMPowder selected as Material Class in the previous step) Set the parameters specific to Powder Materials.
4. Click Save.
3.9.3 Copying a Material

By adopting this method to configure a Material, the new Material will inherit any existing associations with a set of
Documents and/or with a Template, if present. However, you can remove such associations and add new ones,
according to your needs.
Procedure
1. In the Materials page, select the Material to be copied and click Open Material.
2. Click Copy Material Revision.
3. Insert a Unique Identifier to be assigned to the new Material you want to create (New Unique Identifier edit
box) and then modify the other parameters as you like (see Creating a Material from Scratch).
4. Click Save.
3.9.4 Creating a Revision of a Material

When configuring a Material, if you intend to make considerable changes (such as adding and/or removing
associated Documents or changing its associated Template), this method is to be preferred over modifying an
existing Material.
Procedure
1. In the Materials page, select the Material for which you want to create a new revision.
2. Click New Material Revision.

3. Insert the new revision value and click Save.

4. Select the new Material which is displayed in the Materials page and click the button to modify the
Material parameters.
5. If necessary, modify any associations with Documents and/or with a Template.
3.9.5 Associating Documents with a Material

1. Select a Material in the Materials page and click Open Material.
2. Click the Document tab.
3. Click Link.
4. If the Document to be associated is not displayed in the list, click Import and then browse the file of interest.
5. Select the Document to be associated with the Material and then click Add.
6. To access a preview of the Document contents, click the Document Viewer tab.
3.9.6 Associating a Template with a Material

Prerequisites
You have created and configured an Identifier Template.
Procedure
2. Click the Template tab.
3. Click Add Template: the Add Template panel opens.
4. Select an Identifier Template of the appropriate type to associate with the Material you are configuring and click
Select.
5. Click Save: the association between the Template and the Material has been established.
It is possible to remove an association between a Template and a Material, by clicking the Template tab, selecting
the Template and then clicking .
3.9.7 Associating Suppliers with a Material

Prerequisites
You have created and configured Suppliers to be associated to the Material.
Procedure
2. Click the Suppliers tab.
3. Click Link.
4. Select the Supplier to be associated with the Material and then click Link.

 To unlink previously associated Suppliers, select the Supplier and click Unlink.
3.9.8 How to Configure Bill of Materials

A Bill of Materials (BoM) is a list of raw materials and related quantities required to manufacture a final product. As
such, a BoM can be associated with a Material that identifies a Final Product.
BoMs must be populated with BoM Items, which form the list of Materials to be consumed. These Materials can be
linked to other BoMs as well.
BoMs can be grouped together on the basis of how the user wants their BoM Items contained therein to be
consumed.
You can see the structure of a configured BoM from the BoM Tree tab. This is useful especially in the case of
complex BoMs, in which, for example, sub-BoMs are nested.
Once defined, the status of the BoM must be changed to Released. Once released, the BoM can no longer be
modified.
Changing the status of a BoM to Obsolete renders it no longer valid for use.
Depending on the type of Bill of Materials released, the system's behavior will vary in regard to execution:
• Released standard BoMs that identify a Final Material can be associated with Work Orders during Work Order
configuration and enabled for usage: in this case, once released, the Work Order will be executed taking into
consideration the raw Materials indicated in the BoM.
 BoMs cannot be deleted, if they are associated with Work Orders.

Also, the status of a BoM can be changed to Obsolete only if its associated Work Order is not in one of the
following states:
• New
• Queue
• Pause
• Active
• Pending
• ReadyForScheduling
• Hold
• Rework
• Verified.
Target User
Prerequisites
A Material exists and it identifies a Material to be produced.
Workflow
1. Create a BoM.
2. Configure the BoM by adding BoM Items.
3. Release the BoM.

Creating BoMs
1. In the Materials page, select the Material for which you want to create an appropriate BoM that satisfies your
needs and click Open Material.
2. Click the BoM tab, and then click .
Identifier Unique identifier assigned to the BoM.
Version Version of the BoM.
Name Name of the BoM. Note: If a name is not defined, by default, the
BoM Identifier will be used as the BoM's Name.
Description Additional useful information on the BoM.
Priority A number determining the order in which the BoM is displayed. Note: In
case the Priority is not defined, and the user is creating the first BoM,
the Priority must be set as 0 (highest one).
Valid from Date and time from when the BoM is valid.
Valid to Date and time until when the BoM is valid. After this date, the BoM is no
longer available.
Quantity The quantity of BoMs.

4. Click Save. The BoM is created in Edit status.
Adding BoM Items from a Material

1. In the BoM tab, select the BoM to be configured and open it .
2. In the BoM Items tab, click .
Identifier Unique identifier to be assigned to the BoM Item.
Material Select the Material from the list. It must be related to a Material to be
consumed.
Quantity (Optional) The quantity required for the BoM Item. If not provided, the
default value is 1.

Configuring Powder Materials
Group Type The following Group types are available:

• No selection: default group type (also referred to as the
"Normal part" group type).
• Alternative: Only one Material to be consumed and
belonging to the Alternative group must be totally
consumed among those proposed belonging to the
Alternative group.
Select Default Alternative if you want to use the default
Material.
Note If Group Type is Alternative, you must specify
Group Id and Options.
• Selected Fit: The total resulting from the sum of the
partial consumed quantities of all the Selected Fit
Materials to be consumed must be equal to the quantity of
the Selected Fit Material to be consumed with the highest
quantity.
Note Only one Selected Fit group of Materials to be
consumed is permitted for a single BoM.
• Range Parts: At least one Range Part Material to be
consumed must be partially consumed.
Logical Position The coordinates of the BoM Item position inside the BoM.
4. Click Save. A BoM Item is created and assigned to the BoM.
5. Repeat steps 2-4 for any other Material to be used to populate the BoM.
Releasing BoMs
1. In the BoM tab, select the BoM to be released.
2. Click Release.
3.10 Configuring Powder Materials

Powder Materials represent a type of Material peculiar to Additive Manufacturing and from which Powder Batches
are instantiated at runtime.
Powder Materials are configured through a dedicated page that, while displayed in Table mode, shows for all
configured items the Is Invalid parameter: if the check box is selected, it indicates that there are misalignments
between the Powder and its corresponding Material.

To access the Powders page, click Product and Production Configuration > Powders in the sidebar.
Target User
Procedure
1. In the Powders page, click .

How to Configure Container Types

Identifier Identifier to be assigned to the Powder Material. Once saved, this

Revision Revision to be assigned to the Powder Material.
Unique Identifier (Optional) Unique identifier of the Powder Material. If not inserted, it
is automatically filled with Identifier and Revision values separated
by an underscore.
Name (Optional) Name to be assigned to the Powder Material.
Description (Optional) Useful additional information on the Powder Material.
Unit of Measure Unit of Measure to be associated with the Powder Material.
Min. Quantity (Optional) Minimum Quantity allowed for the Powder Material Batch.
If the quantity of the Powder Material Batch falls below this value, the
status of the Powder Material Batch is set to Quarantine, thus
making it unavailable for production.
Max. Recycle Count (Optional) The maximum number of times a Powder Material Batch
can be recycled. If the number of times the Powder Material Batch
has been recycled exceeds this value, the status of the Powder
Material Batch is set to Spent, thus making it no longer available for
production.
3. Click Add.
3.11 How to Configure Container Types

Container Types are templates that can be associated to a Material Tracking Unit Aggregate that you want to use as
Containers.
Container Types are objects that are used as templates and are associated to one or more Materials. Container
types are optional, and should be configured only if necessary. They are useful in case you need to configure
multiple Containers with same, or similar, characteristics.
Through Container Types you can define:
• If the Container can be used just once or multiple times.
• Which Materials you want to declare compatible with the Containers.
• A set of documents useful for the Container use or maintenance.
All these characteristics will be automatically inherited by all Containers based on a specific Container Type but,
except for documents, they can be adapted Container by Container (for example existing compatible Materials can
be removed and new ones can be linked or the reusable property can be changed.

How to Configure Container Types
Target User

To access the Container Type page, select the Container Types tile in the home page.
Workflow
1. Create a Container Type
2. Associate Materials to the Container Type
3. Associate Documents to the Container Type
Creating a Container Type

1. In the Container Type page, click Create.
Identifier Unique identifier to be assigned to the Container Type. Once

Name Name of the Container Type.
Description Useful additional information about the Container Type.
Is Reusable If this checkbox is selected, Containers created using this

Container Type can be reused. By default, this checkbox is
selected.
Compatible Material Select the Material to be associated to the Container Type. You
can use this option to instantly associate the Container Type to a
particular Material. Additional Materials can also be linked to the
Container Type using the Link Material option.
3. Click Create.
Associating Materials to a Container Type

1. In the Container Type page, select the Container Type for which you want to associate additional Materials, and
then click Open.
2. Click the Materials tab, and click Link Material.
3. Select the required Materials to be linked and specify the Maximum Quantity.
4. Click Link.
 • To unlink an associated Material, select the Material and click Unlink.

• The specified Maximum Quantity value of a compatible material can also be edited using the Edit
Max Quantity icon.

How to Configure Operation/Step Categories
Associating Documents to a Container Type

1. In the Container Type page, select the Container Type for which you want to associate the Document, and
then click Open.
2. Click the Documents tab.
3. Click Link.
4. If the Document to be associated is not displayed in the list, click Import and browse to the file of interest.
5. Select the Document to be associated to the Container Type and then click Add Document.
 To unlink an associated Document, select the Document and click Unlink.
3.12 How to Configure Operation/Step Categories

Operation/Step Categories can be used to classify Process Operations, Work Order Operations, Process Steps and
Work Order Steps according to their purpose or execution context (for example, "Manual Assembly", "Automatic
Assembly", "Additive Manufacturing", "Traceability").
Furthermore, in conjunction with the Opcenter Execution Foundation Business Process Flow App, you can
associate Operation/Step Categories to Process Definitions, so that, providing dedicated custom business logic, the
workflows represented by the Process Definitions are automatically triggered at runtime when, for example, the
Work Order Operation (or Work Order Step) is started.
Operation/Step Categories can also be used to configure the system so that, thanks to dedicated business logic,
runtime screens are automatically displayed on the basis of Work Order Operation/Work Order Step context (that is,
their Machines and Material Tracking Units).
The product provides a pre-configured Operation/Step Category, named Default. This Operation/Step category is
associated to a default Process Definition, the UADMProcessDefinition, which contains the configuration of the
workflows to trigger runtime Tasks related to:
• Material Consumption
• Tool Usage
• Work Instructions
• Quality Inspection
• Print Job Files
• Part Programs
• Material Production.
In addition, for additive manufacturing contexts, the product provides the pre-configured Operation/Step Category
Setup3DPrinter. This Operation/Step category is associated to the default Process Definition
3DPrinterSetupProcessDefinition which contains the configuration of the workflows to trigger runtime Tasks
dedicated to the loading of Powder into the 3D Printer.
For more information on these runtime tasks, see Managing Tasks for Work Order Operation or Step Progression.
 It is possible to customize the default UADMProcessDefinition by eliminating those runtime Tasks that
you do not require: the end result is a more streamlined loading of the Operator Landing Page. For more
information, see Speeding Up Operator Landing Page Loading through Task Customization.
In addition to the default Operation/Step Category, it is also possible to create and configure your own Operation/
Step Categories to satisfy your specific needs. Once created, Operation/Step Categories can be associated to at

least one Process Definition. By also linking one or more Machines and/or Materials, the association between
Operation/Step Category and Process Definition can be made more restrictive.
If no Machines or Materials are associated, no additional restriction is applied: in this case, the association
between Operation/Step Category and Process Definition is considered valid for all Machines and Materials
available in the system.
You can link Interlocking Checks to Operation/Step Categories. At runtime, if no Interlocking Checks are linked to
the started or completed Work Order Operation, but the Work Order Operation itself has been classified with a
specific Operation category, the execution of the Interlocking Check is triggered. Likewise, if no Interlocking Checks
are linked to Work Order Steps, but the Step is classified with a specific Step category, and to this category you have
linked an Interlocking Check, it is executed at runtime.
To be used at runtime, associations must be activated.
Relying on custom business logic and according to your project's specific requirements, the system will then
execute workflows (that is, Work Processes, which are the runtime instantiations of Process Definitions) triggered
for the Work Order Operations / Work Order Steps to which specific Operation/Step Category - Process Definition
associations have been established.
 Only Operation/Step Categories that are not involved in an association can be deleted.
Target User
Users with the Product Engineer, Production Coordinator or MPP role can perform this procedure.
Prerequisites
At least one Process Definition has been created using the Opcenter Execution Foundation Business Process Flow
App.
 For more information on how to configure Process Definitions using the Business Process Flow App, see
the Opcenter Execution Foundation User Manual.

To access the Operation/Step Categories page, click Product and Production Configuration > Operation/
Step Categories in the sidebar.
Workflow
1. Create an Operation/Step Category.
2. Associate one or more Process Definitions, optionally restricted to specific Machines/Materials.
3. (Optional) Set the association to Serialized behavior (a Work Process will be associated to each Serial Number
produced by the Work Order).
4. (Optional and not available in the Siemens_OPC_EXDS_AM UI Application). Link Interlocking Checks to the
Operation/Step Category.
5. Activate the Association.
Creating Operation/Step Categories

1. In the Operation/Step Categories page, click Create.

Identifier Unique identifier to be assigned to the Operation/Step Category. Once

Name Name of the Operation/Step Category.
Description Useful information about the Operation/Step Category.

3. Click Save.
Associating Operation/Step Categories to Process Definitions

1. In the Operation/Step Categories page, select the Operation/Step Category you want to associate to one or
more Process Definitions and click Open: the Operation/Step Category Details page is displayed.
2. Click the Associations tab.
3. Click Create.
4. In the Create Associations page, operating in the Process Definitions accordion, select the tile(s) representing
the Process Definition(s) of interest.
5. (Optional) If you want to restrict the association(s) being created to certain Machines and/or Materials,
operating in the Machines and/or Materials accordions, select the tile(s) representing the Machine(s) and/or
Material(s) according to your needs.
6. Click Save.
 If you delete a Process Definition from the Opcenter Execution Foundation Business Process Flow App, all
involved associations are deleted as well.
Setting the association to Serialized behavior

By default, the association created between an Operation/Step Category and a Process Definition will assume the
following behavior: a single Work Process will be instantiated for the entire Work Order Operation, given a specific
context (that is, Machine).
If you want to set Serialized behavior for the association that has just been created, click the Set Serialized
icon on the right side bar to associate a single Work Process for each Serial Number produced by the Work Order.
To remove this behavior and return to the default setting, click the Unset Serialized icon.
This setting is visible in the Serialized column of the Association tab.
Linking Interlocking Checks to the Operation/Step Category

1. In the Operation/Step Categories page, select the Operation/Step Category you want to link to one or more
Interlocking Checks and click Open: the Operation/Step Category Details page is displayed.
2. Click the Interlocking Checks tab.
3. Click Link.
4. In the Link Interlocking Check pane, select the Interlocking Check to be linked.
5. Define the following Interlocking Check properties (type and link):

How to Manage Catalogs
Property Description
Inbound If this check box is selected, the custom Interlocking Check will
trigger the start of the related Work Order Operation, once all
conditions required by the check are satisfied.
Outbound If this check box is selected, the custom Interlocking Check will
trigger the completion of the related Work Order Operation, once all
Operation-relevant If this check box is selected, it will be possible to link the Interlocking
Check only to Process or Work Order Operations.
Step-relevant If this check box is selected, it will be possible to link the Interlocking
Check only to Process or Work Order Steps.
 The definition of type (Inbound/Outbound) and link (Operation-relevant/Step-relevant) is

mandatory.
6. In the Associated Interlocking Check Parameters area, select a parameter and then click Set Parameter
Values.
7. In the Set Parameter Values pane, insert or update values for the parameters. If the parameter foresees
multiple values (that is, Is List is selected), it will be possible to define more than one value for the parameter.
8. Click Set. The tile indicates the values have been set for the parameter.
9. Click Add.
 Once linked, Interlocking Checks cannot be deleted. To delete Interlocking Checks, they must be first
unlinked from the Operation/Step Category.
Activating Associations
 To activate the association, it is necessary that the Machine-Material pair involved in the association must
not already have been used in another association that is already activated.
In the Associations tab, select the association to be activated and click Activate on the right side bar.
 If you want to deactivate an active association, select the association to be deactivated and then click the
Deactivate icon on the right side bar.
3.13 How to Manage Catalogs

Opcenter Execution Discrete includes Catalogs, that is, repositories of abstract production entities that can be
instanced and combined together to create actual Work Orders.

When an entity is created "on the fly" (for example, a Process Operation created during the creation of a Process) it
is automatically included in the corresponding Catalog and can be re-used later. Conversely, it is possible to create
directly entities in the Catalog.
You can manage Catalogs for Processes, Operations and Steps.
A Catalog includes all the Revisions of an entity. It is possible to revise the entities from their corresponding Catalog.
Target User
• How to Manage the Process Catalog
• How to Manage the Operation Catalog
• How to Manage the Step Catalog.
3.13.1 How to Manage the Process Catalog

A Process Catalog is a repository of Processes.
When a Process is created from the Catalog, it is "unlinked", that is, not yet used in an actual production process. It
is also not linked to neither an As Planned BOP nor a Master Plan.
Working in the Process Catalog page, you can:
• create a Process
• create a revision of an existing Process
Revisions of existing Processes are typically created to apply some minor modifications to them. When a Process is
created for the first time, the Revision indicates A as value. This value is incremented (with B, C and so on) while
creating Revisions of it.
You can also revise Processes from the As Planned BOPs and Processes page: new Revisions are automatically
added to the Process Catalog.
Creating a Process
1. Click Product and Production Configuration > Process Catalog in the sidebar.
2. Click Create > Manually: the Create Process panel is opened.
Identifier Unique identifier to be assigned to the Process. Once saved, this

Name Name of the Process.
Description Useful information about the Process.
Plant Either the Enterprise or the Site where the Process execution will
take place, to be selected among those created from the
Equipment Configurations page.

Final Material The Final Material that will be produced by the Process. If no Final
Material exists, you can create a new Material. The Final Material
field can be left blank: if a Final Material is not specified at this time,
it will be required when creating a Work Order from this Process. This
allows you to create a generic Process which can be used to produce
different Materials.
Quantity (Enabled and mandatory only if you have selected a Final Material)
The default quantity of the Material that will be produced by the
Process.
Min. Quantity (Enabled only if you have selected a Final Material) The minimum
quantity of the Final Material to be produced by the Process.
Max. Quantity (Enabled only if you have selected a Final Material) The maximum
4. Click Create.
Revising a Process
1. Click Product and Production Configuration > Process Catalog in the sidebar.
2. Select a Process and click Create > Revision.
3.13.2 How to Manage the Operation Catalog

An Operation Catalog is a repository of Process Operations.
When a Process Operation is created from the Catalog, differently from when it is created inside a Process, it is
"unlinked", that is, not yet used in an actual production process and not belonging to a Process included in an As
Planned BOP or Master Plan.
Working in the Operation Catalog page, you can:
• Create a Process Operation
• Create a Revision of a Process Operation.
• Associate Documents to a Process Operation
• Associate Work Instructions to a Process Operation
• Associate Skills to a Process Operation. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)
Revisions of existing Process Operations are typically created to apply some minor modifications to them. When a
Process Operation is created for the first time, the Revision indicates A as value. This value is incremented (with B, C
and so on) while creating Revisions of it.
Process Operations can be enriched with Documents, Work Instructions and Skills, provided that they are available
in the system.
 If you want to delete a Process Operation, you must first unlink the Process Operation from the Process it
is linked to, if any. If you try to delete multiple Process Operations at once and only some of them are
linked to Processes, only those unlinked are actually deleted.

Creating a Process Operation

1. Click Product and Production Configuration > Operation Catalog in the sidebar.
2. Click Create > Manually: the Create Operation panel is opened.
Identifier The unique identifier to be assigned to the Operation. Once saved, this parameter can no
longer be modified.
Revision Identifier of the Operation's revision.
Name The name of the Operation.
Description Useful information about the Operation.
Estimated Estimated duration of the Operation's execution. It is expressed in hours, minutes, seconds.
Duration
(hours,
minutes,
seconds)
Required Deprecated.
Inspection
Role
Required If a Certification name is specified, the Operation can be started, paused or completed only
Certification by an Operator owning the specified Certification.
If the field is left blank, no Certification is required to execute the Operation.
Work To define how the Operation must behave at runtime, select one of the configured Work
Operation Operations.
Operation/ Operation/Step Category to be assigned to the Operation.

Step
Category  If no value is selected for this parameter, the default Operation/Step Category
provided in Opcenter EX DS will be assigned.
Electronic If the check box is selected, the operator credentials are validated at the time of starting a
Signature Work Order Operation. The validation ensures that only authorized operators start Work
Start Order Operations.
Electronic If the check box is selected, the operator credentials are validated at the time of pausing a
Signature Work Order Operation. The validation ensures that only authorized operators pause Work
Pause Order Operations.
Electronic If the check box is selected, the operator credentials are validated at the time of completing
Signature a Work Order Operation. The validation ensures that only authorized operators complete
Complete Work Order Operations.

4. Click Create.
Revising a Process Operation

2. Select a Process Operation and click Create > Revision.
Associating Documents to a Process Operation

2. Select the required Process Operation and then click Open.
4. Click Link.
5. If the Document to be associated with the Process Operation is not displayed in the list, click Import and select
the file of interest.
6. Select the Document from the list and click Link.
Associating Work Instructions to a Process Operation

3. Click the Work Instructions tab.
4. Click Link.
5. Select the Work Instruction Association Type:
• Operation: the Work Instruction will be associated with the whole Process Operation;
• Serial Number: the Work Instruction will be associated with all the Serial Numbers produced by the
Process Operation;
• Serial Number On Demand: the Work Instruction will be associated only to some Serial Numbers
produced by the Process Operation. The Operator will select at runtime the exact list of Serial Numbers
to be associated.
6. Select the Work Instruction to be associated and click either of the following:
• Link, to only associate the Work Instruction to that specific Process Operation in the Catalog.
• Link and Propagate, to associate the Work Instruction to all Process Operations created from that
specific Operation in the Catalog.
 Similarly, when you unlink a Work Instruction from a Process Operation, you can decide to unlink it only
from that Process Operation in the Catalog you are currently managing, or you can unlink and propagate
the removal to all Process Operations created from the same source Operation in the Catalog.
Associating Skills to a Process Operation

3. Click the Skills tab.
4. Click Link.
5. In the Level field, type the required level of the Skill to be associated with the Process Operation.
 According to the Enable Certification Skill Level Filter configuration key, the Level can either be the
exact or the minimum value required to authorize the Process Operation execution.

6. Select one or more Skills from the list and click Link.
3.13.3 How to Manage the Step Catalog

A Step Catalog is a repository of Process Steps.
When a Process Step is created from the Catalog, differently from when it is created inside a Process Operation, it is
"unlinked", that is, not yet used in an actual production process and not belonging to a Process Operation included
in an As Planned BOP.
Working in the Step Catalog page, you can:
• Create a Process Step
• Create a Revision of a Process Step
• Associate Documents to a Process Step
• Associate Work Instructions to a Process Step
• Associate Skills to a Process Step (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.).
Process Steps can be enriched with Documents, Work Instructions and Skills, provided that they are available in the
system.
Revisions of existing Process Steps are typically created to apply some minor modifications to them. When a
Process Step is created for the first time, the Revision indicates A as value. This value is incremented (with B, C and
so on) while creating Revisions of it.
 • Process Steps can also be revised in the Steps page, and new Revisions are automatically added to the
Catalog.
• Process Steps already linked to Process Operations cannot be deleted. To delete them, they must be
first unlinked.
Creating a Process Step

1. Click Product and Production Configuration > Step Catalog in the sidebar.
2. Click Create > Manually: the Create Step panel is opened.
Identifier The unique identifier to be assigned to the Process Step. Once

Name The name of the Process Step.
Description Useful information about the Process Step.
Operation/Step Category Operation/Step Category to be assigned to the Process Step you

are creating.
 If no value is selected for this parameter, the default

Operation/Step Category provided in Opcenter EX
DS will be assigned.

Electronic Signature Complete If the check box is selected, the operator credentials are validated
at the time of completing a Work Order Operation. The validation
ensures that only authorized operators complete Work Order
Operations.
Estimated Duration Hours Estimated duration, in hours, of the Process Step execution.
This value will be aggregated with estimated duration in Minutes
and Seconds to form a unique estimated duration displayed in
the following formats: d.hh:mm:ss or hh:mm:ss.
Estimated Duration Minutes Estimated duration, in minutes, of the Process Step execution.
Estimated Duration Seconds Estimated duration, in seconds, of the Process Step execution.
4. Click Create to confirm the operation.
Revising a Process Step

2. Select a Process Step and click Create > Revision.
Associating Documents to a Process Step

2. Select the required Step and then click Open.
4. Click Link.
5. Select the Document from the list and click Link.
Associating Work Instructions to a Process Step

3. Click the Work Instructions tab.
4. Click Link.
5. Select the Work Instruction Association Type:
Process Operation;
to be associated.
6. Select the Work Instruction to be associated and click Link.
Associating Skills to a Process Step


How to Configure Plugins

3. Click the Skills tab.
4. Click Link.
5. In the Level edit box, type the required level of the Skill to be associated with the Process Step.
 According to the Enable Certification Skill Level Filter configuration key, the Level can either be the
exact or the minimum value required to authorize the Process Step execution.
6. Select one or more Skills from the list and click Link.
3.14 How to Configure Plugins

To successfully complete Additive Manufacturing operations, you need to define the required Plugins. The system
provides by default the following Plugin Types to be used to configure the Plugins you need:
• Import, dedicated to import metadata related to Print Job Files from the external CAM system that generated
them.
• Transfer, dedicated to transfer Print Job Files to the proper 3D Printer. To be properly used at runtime, while
configuring 3D Printers, they must be associated with the 3D Printer for which they will manage the Print Job
File transfer.
• PrinterConn, dedicated to pre-transfer the intermediate Print Job Files to 3D Printers and then to use at
runtime the final Print Job Files generated by the 3D Printers.
Plugins are grouped by Types to easily identify the environment in which they must be used and the action they can
perform.
Prerequisite
A custom plugin has been created by system integrators. For more information see How to Develop a Print Job File
Repository Plugin and How to Develop a Print Job File Transfer Plugin in the Opcenter Execution Discrete Extensibility
Guide.
Workflow
1. Creating a Plugin Type.
2. Creating a Plugin.
Creating a Plugin Type

1. Select Product and Production Configuration > Plugin Types in the sidebar.
2. In the Plugin Types page, click the Add Plugin Type button.
Parameter Name
Action The action the Plugin can perform.
Context Label to be used to identify the technology that characterizes the

Plugins belonging to the Plugin Type (for example, AM).
Description Useful information on the Plugin Type.

4. Click Add.

How To Configure 3D Printers
Creating a Plugin
1. Select Product and Production Configuration > Plugins in the sidebar.
2. In the Plugins page, click the Add Plugin button.
Parameter Name
Identifier The unique identifier assigned to the Plugin. Once the Plugin is created,
it cannot be modified.
Name The name assigned to the Plugin.
Path The physical path of the Plugin file.
Type The Plugin Type identifying the action the Plugin can perform and the
context in which it can be used, by default:
• Import
• Transfer
• PrinterConn
Once the Plugin is created, it cannot be modified.
4. Click Add.
3.15 How To Configure 3D Printers

3D Printers represent the Equipment dedicated to printing Work Order Operations and consequently they are
essentials in an Additive Manufacturing scenario.
Optionally they can be based on templates, called 3D Printer Types.
Before being used, they must be associated to both the 3D Printer, belonging to an external system, that generated
the Print Job File to be used and to the plugin dedicated to the Print Job File transfer.
3D Printers can be configured together with other Equipment while defining the Equipment Configurations making
up the plant, or later through a dedicated page, as described below.
Regardless of how they have been created, it may be necessary to fine-tune them at any time according to the
production needs, for example because a new transfer plugin must be used, simply selecting them in the 3D
Printers page and click the Edit 3D Printer button.
Both 3D Printers and 3D Printer Types are configured through dedicated pages that, while displayed in Table mode,
show for all configured items the Is Invalid parameter: if the check box is selected, it indicates that there are
misalignments between the 3D Printer or Printer Type, and its corresponding Equipment.
Workflow
1. (Optional) Creating 3D Printer Types.
2. Creating 3D Printers.
Creating 3D Printer Types

1. Select Product and Production Configuration > 3D Printer Types in the sidebar.

How to Configure Failures
2. In the 3D Printer Types page, click the Add button.

Parameter Name
Identifier The unique identifier assigned to the 3D Printer Type. Once the 3D
Printer Type is created, it cannot be modified.
Name The name assigned to the 3D Printer Type.
Description Useful information on the 3D Printer Type.
Transfer Plugin The Plugin that manages the Print Job File transfer.
4. Click Add.
Creating 3D Printers
1. Select Product and Production Configuration > 3D Printers in the sidebar
2. In the 3D Printers page, click the Add button.
Parameter Name
Identifier The unique identifier assigned to the 3D Printer. Once the 3D

Printer is created, it cannot be modified.
Name The name assigned to the 3D Printer.
Description Useful information on the 3D Printer.
AM Machine The identifier of the 3D Printer in the external system that

generated the Print Job File.
Transfer Plugin The Plugin that manages the Print Job File transfer.
3D Printer Type The 3D Printer Type to be used as template for the 3D Printer.
Is Pre-Transfer Enabled Select the check box if the 3D Printer requires files to be
transferred in advance in order to be properly processed.
4. Click Add.
3.16 How to Configure Failures

 Opcenter Execution Foundation provides the possibility to configure Failures, and Opcenter Execution
Discrete extends this functionality allowing you to associate Failures to specific parts of the configured
production plant. As some of the configurations required by Opcenter Execution Foundation (for example
Quality Action management) are not relevant or applicable in this production context, the current
documentation does not mention them. Only involved parameters, buttons and tabs are mentioned.

How to Configure Failures
Different types of problems can occur during the various phases of the production process. To properly manage and
notify them it is important to define a catalog of possible Failures, if necessary organizing them hierarchically into
more specific Sub-Failures.
Once created, Failures can be enriched with attachments that provide additional details, and must the be
associated with specific plant parts thus becoming available only to operators working on specific workstations.
While configuring Failures keep in mind that Sub-Failures cannot be directly associated with any equipment, even if
at runtime the operator will be able to browse them starting from the related root Failure and that Failures
associated with a plant node are automatically inherited by all underlying nodes.
Target User

To access the Failures page, click Product and Production Configuration > Failures in the sidebar.
Workflow
1. Create Failures.
2. (Optional) Create Sub-Failures.
3. (Optional) Associate Attachments to Failures.
4. Associating Failures to Equipment.
Creating Failures
1. In the Failures page, click .
Attribute Description
Id The unique identifier to be assigned to the Failure. Once the Failure is created, the Id
value cannot be modified.
It cannot contain the following special characters: & (ampersand), ' (quote), #
(hashtag), " (double quotes), + (plus), : (colon).
Revision The revision associated to the Failure.

Once the Failure is created, it cannot be modified.
Name (Optional) The name assigned to the Failure.
Description (Optional) Additional useful information on the Failure.

3. Click Save.
Creating Sub-Failures
1. In the Failures page, select a Failure and click .
2. Click the Sub-Failures tab.
3. Click and set the following parameters:

Configuring Rework Codes
Id The unique identifier to be assigned to the Sub-Failure. Once the Sub-

Failure is created, it cannot be modified.
It cannot contain the following special characters: & (ampersand), '
(quote), # (hashtag), " (double quotes), + (plus).
Revision The revision associated to the Sub-Failure.

Once the Sub-Failure is created, it cannot be modified.
Name (Optional) The name assigned to the Sub-Failure.
Description (Optional) Additional useful information on the Sub-Failure.

4. Click Save.
Associating Attachments to Failures

1. In the Failures page select a Failure, click and then click the Attachments tab.
2. Click .
Id The unique identifier to be assigned to the Attachment.

Once the Attachment is created, it cannot be modified.
Name (Optional) The name of the Attachment.
Description (Optional) Additional useful information on the Attachment.
File The document to be attached. You can browse text files, videos and images.
Icon The icon that will be assigned to the attachment.

4. Click Save.
Associating Failures to Equipment

1. In the Failures page select a Failure, click and then click the Equipment tab.
2. Click .
3. Click and select the item of interest.
4. Click Select.
5. Click Save.
3.17 Configuring Rework Codes

A Rework Code represents an association between a Process, which has been defined to rework an item, a Defect
(or a group of Defects) previously defined, one or more Failures (and Sub-Failures) and a Final Material.

Configuring Non-Productive Activities
During production, whenever the Operator opens a Non-Conformance on an item, the system takes into account
the defect that has been found and the Material that the Operation is going to produce, and provides the user with
the list of possible rework Processes to be performed to rectify the problem encountered.
Procedure
1. Click the Rework Codes tile in the homepage.
2. Depending on the configuration key, a Rework Code can be created for a Defect Type, Defect Group or a
Failure. Click either of the following in the Rework Codes page:
• Create > Defect Type/Failures, to define a Rework Code for a set of Defect Types or Failure/Sub-
Failure.
• Create > Defect Group/Failures to define a Rework Code for a set of Defect Groups or Failure/Sub-
Failure.
3. From the drop-down list box, select the item of interest (either a Defect Type, Defect Group or a Failure).
4. Click the Select Materials button.
5. Select the Materials to be associated with the Rework Code and then click Add.
6. Click the Select Processes button.
7. Select the Processes to be associated with the Rework Code and then click Add.
 Only Processes included in an As Planned BOP can be associated with a Rework Code.
8. Click Create.
3.18 Configuring Non-Productive Activities

Before starting the production execution, you can define a set of Non-Productive Activities. Users will then be able
to declare the start of one or more of them and the system will track the activities and the time spent on them.
Target User
Users with the Product Engineer or the Production Supervisor roles can perform this operation.
Procedure
1. To access the Non-Productive Activities page, click System Configuration > Non-Productive Activities in
the sidebar.
2. In the Non-Productive Activities page, click Create.
Identifier (Mandatory) Unique Identifier of the Non-Productive Activity.
Description (Optional) Additional information on the Non-Productive Activity you

are creating.
4. Click Create.

How to Configure Print Job Files
3.19 How to Configure Print Job Files

In Additive Manufacturing (3D Printing) production, Print Job Files provide detailed instructions on how the
products to be manufactured must be 3D-printed.
Print Job Files are usually generated in a dedicated external CAM system and are specific to printer brands, models
and types, but in case of need it is also possible to generate them manually within the system.
Once imported or created, you can associate Print Job Files to Materials to be produced and 3D Printers to be used
to produce those Materials.
Prerequisites
• At least one 3D Printer has been defined.
• The 3D Printer has been configured to manage the Print Job File transfer.

To access the Print Job Files page, click Product and Production Configuration > Print Job Files in the
sidebar.
Workflow
• Import Print Job Files
• Create Print Job Files Manually
2. Finalize the configuration of the imported Print Job Files.
3. To access the list of operations performed on the Print Job File, select it in the Print Job Files page, click
Open and the click the History tab.
3.19.1 Importing Print Job Files

Print Job Files can be imported in the system in two ways:
• Full Import: the system requests information about all Print Job Files available in the external system. Existing
Print Job Files are deleted and eventually overwritten, except those with the Runtime Only attribute.
• Delta Import: Only variations from the previously-imported list are processed. It is up to the plug-in or the
external system to implement the logic about how to define which Print Job Files are new or updated. Print Job
Files with the Runtime Only attribute are not overwritten.
Prerequisite
A plugin to be used to import Print Job Files has been defined.
Procedure
1. Click Product and Production Configuration > Print Job Files in the sidebar.
2. In the Print Job Files page, do either of the following:
• Click Import > Full Import to perform a Full Import.
• Click Import > Delta Import to perform a Delta Import.
3. From the dedicated screen that is displayed, select one or more tiles representing those CAM systems from
which the Print Job Files are to be imported and click Import.

Result
The Print Job Files present in the selected CAM systems are analyzed and then related metadata are imported in the
system, in accordance with the type of Import that has been selected. Existing Print Job Files with the Runtime
Only attribute are not deleted or overwritten.
3.19.2 Creating Print Job Files Manually

Print Job Files are usually generated in an external CAM system and then they are imported into Opcenter Execution
Discrete, but in case of need it is also possible to create them manually within the system.
Procedure
1. Click Product and Production Configuration > Print Job Files in the sidebar.
2. In the Print Job Files page, click the Add Print Job File button.
Identifier External Identifier of the system repository that stores the

Print Job File binaries and related information.
File Name Name of the Print Job File (including extension).
Source Identifier of the system repository.
Build Tray Layout Information regarding the piece's position in the build tray.
Estimated Build Process Duration in Hours Estimated time necessary to generate the Print Job File or
modify it in hours.
Estimated Build Process Duration in Estimated time necessary to generate the Print Job File or
Minutes modify it in minutes.
Estimated Build Process Duration in Estimated time necessary to generate the Print Job File or
Seconds modify it in seconds.
Estimated Material Consumption Quantity Estimated consumption of raw material to fulfill the Print
Job File.
Estimated Material Consumption UoM Unit of Measure of the raw material.
Max. Produced Height Maximum product height in millimeters.
Serializable Product If the check box is selected, the product requires Serial
Numbers.
Test Bars If the check box is selected, the Print Job File includes test
bars.

Serializable Test Bars If the check box is selected, the Test Bars require Serial
Numbers.
Test Bar Number The amount of required Test Bars.
Estimated Print Duration in Hours Estimated time necessary to execute the 3D Print Job in
hours.
Estimated Print Duration in Minutes Estimated time necessary to execute the 3D Print Job in
minutes.
Estimated Print Duration in Seconds Estimated time necessary to execute the 3D Print Job in
seconds.
Production Printer The external 3D Printer.
Product Serial Number Management The status of the association between product and Serial
Numbers:
• None, Serial Numbers are not required.
• Pending, Serial Numbers have not yet been
assigned.
• Assigned, Serial Numbers have been assigned.
Test Bar Serial Number Management The status of the association between test bars and Serial
Numbers:
• None, Serial Numbers are not required.
• Pending, Serial Numbers have not yet been
assigned.
• Assigned, Serial Numbers have been assigned.
File Path Path of the Print Job File.
Can be Pre-Transferred Select the check box if the Print Job File must be used by a
3D Printer that requires in input an intermediate file to be
processed to generate the final Print Job File.
4. Click Add.
3.19.3 Finalizing the Print Job File Configuration

Once a Print Job File has been either imported or created manually, it may be necessary that you tweak the file in
question in order to satisfy your needs.
It is also possible to:
• associate one or more Materials to be produced.
• associate one or more 3D printer types.
• associate one or more 3D printers.
In addition, if the Edit Print Job File configuration key is enabled, it is possible to edit the Print Job File details
provided by the external CAM system.

Importing and Mapping CNC Packages
Procedure
1. In the Print Job Files page, select the Print Job File that contains the instructions to be used for printing and
click Open: the Print Job File Details page is displayed.
2. To edit the Print Job File, click Edit Print Job File and modify the details of the Print Job File shown in the
Details tab: then click Save.
3. If necessary, select the most appropriate tab(s) from those listed below and finalize the selected Print Job File's
configuration as follows:
Select tab ... If you want to....
3D Printer Types Associate one or more 3D Printer Types.
Click Link, make your selection and then click Save. Click
Unlink to remove the association.
3D Printers Associate one or more 3D Printers.
Products Associate one or more Materials to be produced, also specifying

their quantity.
 If a Print Job File is associated to a Work Order Operation, the Work Order tab appears on the Print
Job File Details page. After the Work Order Operation is started, the Work Order tab is populated
with the details of the Work Order to which the Print Job File is associated. If the Work Order that is
associated to the Print Job File is of type Serialized or FullySerialized, the Serial Number tab also
appears on the Print Job File Details page after the Work Order is started. This tab displays Work
Order details such as Serial Number, Material, Machine.
3.20 Importing and Mapping CNC Packages

When using DNC Integration, the following operations must be performed:
• Import a set of CNC Packages, which include CNC Artifacts (either documents or CNC Programs).
• Link the DNC Machines to the Opcenter EX DS Machines.
• Associate Products with CNC items (Packages, Programs or Artifacts).
CNC Packages can be imported in two ways:
• Full import: All references in the DNC system are processed. Current associations with Machines and Products
are kept, if they are still meaningful after the new Import operation.
• Delta import: Only variations from the previously-imported list are processed. If the list was previously
imported, it is updated.

Importing and Mapping CNC Packages
The exact functionalities of the delta import procedure depend on the features of the custom plugin. For example, a
plugin might support only delta imports of new program references, or it might also allow the deletion of existing
ones. Refer to the documentation of the specific plugin for further details.
After importing and mapping CNC Packages, it will be possible to transfer them to CNC Machines.
Prerequisites
• A valid DNC software interface (any generic system or a custom one) is installed and configured.
• DNC Integration must have been enabled and configured in the Configuration Keys > Integrations page.
Importing CNC Packages

1. Click Product and Production Configuration > DNC in the sidebar.
2. In the DNC page, click either of the following:
• Import > Full Import to perform a full import;

• Import > Delta Import to perform a delta import.
Linking DNC Machines to Opcenter EX DS Machines

1. Click Product and Production Configuration > DNC Machines in the sidebar.
2. In the DNC Machines page, select a DNC Machine and click Link.
3. In the Link Equipment panel, select an Equipment to be linked to the DNC Machine and click Save.
Associating Products to CNC Items

To associate Products with... Do the following
CNC Packages 1. In the Product and Production

Configuration > DNC page, select a CNC Package and click
Open.
2. Select the Products tab.
3. Click Add Products.
4. In the Add Products page do either of the following:
• Select the Manage Hierarchy check box to associate
the Product also with all CNC Programs and Artifacts
contained in the Package, if any.
• Clear the check box to associate the Product only
with the Package.
5. In the Material field, select a Product to be associated with
the CNC Package.
6. Click Save.

Configuring Work Operations
To associate Products with... Do the following
CNC Programs 1. In the Product and Production

Open.
2. Select the Part Programs/Artifacts tab.
3. Select a CNC Program and click Open.
6. In the Add Products page do either of the following:
• Select the Manage Hierarchy check box to associate
the Product also with all Artifacts contained in the
Program, if any.
• Clear the check box to associate the Product only
with the Program.
7. In the Material field, select a Product to be associated with
the CNC Program.
8. Click Save.
CNC Artifacts 1. In the Product and Production

Open.
2. Select the Part Programs/Artifacts tab.
• If the desired Artifact is directly contained in the
Package, select it.
• If the desired Artifact is contained in a Program,
select the container Program, click Open and
select the Artifact in the Artifacts tab.
4. Click Open.
7. In the Add Products page, select a Product to be associated
with the CNC Artifact and click Save.
3.21 Configuring Work Operations

Before configuring your production processes, you can define a set of items known as Work Operations, which are
to be associated with Work Order Operations in order to define their behavior at runtime (for example, the
possibility of automatic start and completion of a Work Order).
The system provides you with a set of predefined Work Operations, which you can both modify and delete:
• Standard
• Dynamic
• Machining
• Additive (specific to additive manufacturing contexts)
• SetUp3DPrinter (specific to additive manufacturing contexts)

In addition, you can also create new Work Operations either from scratch or copying and then customizing the
existing ones.

To access the Work Operations page, click Product and Production Configuration > Work Operation
Management in the sidebar.
You can create a Work Operation in either of the following ways:
• From Scratch
• Copying an existing Work Operation
Creating a Work Operation from Scratch

1. In the Work Operations page, click Create > Manually.
Identifier Unique identifier to be assigned to the Work Operation. Once saved,

Only One Active Only one Work Order Operation can be active among those belonging
to the same Work Order.
Auto-Complete The Work Order Operation is automatically completed after it has

been started. Auto-Complete operations are usually brief operations
that do not require a distinction between the Start and the Complete
phase.
 • This parameter must be set to permit automatic

Complete by an active User or an active Machine
(or Workcenter).
• It is possible to set both Auto-Start and Auto-
Complete at the same time, as they are not
mutually exclusive.

Auto-Start The Work Order Operation is automatically started when a preceding

Work Order Operation (according to the dependency schema) has
been started (for AfterStart dependency) or completed (for AfterEnd
dependency).
 • This parameter must be set to permit automatic

Start by an active User or an active Machine (or
Workcenter).
• If an automatic Start by an active User or
Machine is foreseen, there must be no other
Work Order Operations of the same type queued
on the same Machine.
• It is possible to set both Auto-Start and Auto-
Complete at the same time, as they are not
mutually exclusive.
CNC The Work Order Operation will be executed on a numerical control

machine and it will require a part program package.
Machine Auto-Complete For future use - The Work Order Operation can only be automatically
completed by a machine, and not manually by an Operator.
Machine Auto-Start For future use - The Work Order Operation can only be automatically
started by a machine, and not manually by an Operator.
Machine Auto-Pause For future use - The Work Order Operation can only be automatically
paused by a machine, and not manually by an Operator.
Milestone The Work Order Operation is considered important from a

manufacturing standpoint.
Optional The Operator can choose not to start the Work Order Operation.
 In the case of Serialized and TransferBatch production

types, the Operator can also choose to execute the optional
Work Order Operation partially.
Additive Manufacturing If selected, the Work Operation is used in 3D printing processes. A

single Print Job File can be associated with this operation by
associating it with a 3D printer.
Can be skipped If selected, the execution of the Work Order Operation can be
intentionally skipped at runtime by clicking the related button. This
activity is traced in the system, along with the name of the Operator
who skipped the Operation and the timestamp.

How to Configure Custom Non-Conformance Lifecycles
Load AM Powder If selected, the Work Order Operation is used in 3D printing

processes. The Powder must be loaded into the associated 3D
Printer.
Lock AM Powder Batch If selected, the Work Order Operation is used in 3D printing
processes. The Powder Batch is locked at the start of a printing
operation, so that its status changes to Busy and no actions can be
performed on it until the printing operation is finished and the Batch
becomes available again.
3. Click Create.
Copying a Work Operation

1. In the Work Operations page, select the Work Operation to be copied.
2. Click Create > Copy.
3. Change the Unique Identifier of the Work Operation and then modify the other parameters as you like (see
Creating a Work Operation from Scratch).
4. Click Create.
3.22 How to Configure Custom Non-Conformance Lifecycles

A Non-Conformance Lifecycle represents the states that a Non-Conformance assumes in relation to the activities or
tasks it may undergo: creation, modification, completion, in addition to other possibilities.
Opcenter EX DS supports two default Non-Conformance Lifecycles which are applicable to Quality Non-
Conformances, respectively associated to Work Order Operations and Machines/Tools/Material Tracking Units.
Additionally, there exists the possibility of creating custom Quality Non-Conformances Lifecycles. Once created,
you must configure transitions for the lifecycle states and you can also associate the states with particular
behaviors. You can later change status-transition associations, or add more transitions to the lifecycle, provided
that you did not select this lifecycle for your Opcenter Execution Discrete setup.
 For more information on using State Machines to manage entity lifecycles, see section How to Manage
Entity Lifecycles with State Machines in the Opcenter Execution Foundation User Manual.

To access the Non-Conformance Lifecycles page, click System Configuration > Non-Conformance
Lifecycles in the sidebar.
Target User
Users with the Product Engineer role can perform this operation.
Workflow
1. Create a Non-Conformance Lifecycle.
2. (Optional) Create a Non-Conformance Lifecycle Status.
3. Configure a Transition.

4. (Optional) Associate States with Behaviors.

5. Associate Transitions with User Roles and E-mails. (This functionality is not available in
the Siemens_OPC_EXDS_AM UI Application..)
6. Select the newly-created Non-Conformance Lifecycle from the Engineering Configuration Keys page. Once
selected, this Non-Conformance Lifecycle, or its associated states and transitions cannot be edited.
3.22.1 Creating a Non-Conformance Lifecycle

This procedure describes how to create and configure a custom Non-Conformance Lifecycle. At the time of creating
a Non-Conformance Lifecycle, you must select an initial status from a set of existing system-defined and custom-
defined Non-Conformance Lifecycle States. You can also modify an existing Non-Conformance Lifecycle.
 Name, description and initial status of the default Non-Conformance Lifecycle of type Change cannot be
modified. However, it is possible to configure its Transitions.
Procedure
1. In the Non-Conformance Lifecycles page, click Create.
Identifier Unique identifier to be assigned to the Non-Conformance Lifecycle to

be created. Once saved, this parameter can no longer be modified.
Name Name of the Non-Conformance Lifecycle to be created.
Description Useful information about the Non-Conformance Lifecycle to be

created.
Initial Status From the list of system-defined or custom-created states, the initial
status that you want to assign to the Non-Conformance Lifecycle you
are creating. This value is mandatory.
(Optional) To create a new Non-Conformance Lifecycle Status instead
of using an existing one, click to provide Identifier, Name, and
Description for the new status.
3. Click Save.
Result
The Non-Conformance Lifecycle is created, but it can be used only after completing its configuration. To complete
configuration, configure one or more Transitions for this Non-Conformance Lifecycle, and associate these
Transitions with User Roles.
 After selecting this Non-Conformance Lifecycle for your Opcenter Execution Discrete setup from the
Engineering Configuration Keys page, you cannot add or update associated Transitions.

3.22.2 Creating a Non-Conformance Status

At the time of configuring a Quality Non-Conformance Lifecycle, you can either select the Initial Status value from
a list of available states, or choose to create a new one. However, Opcenter Execution Discrete also supports a
stand-alone method for creating states. This means that you can choose to create states separately, before or after
configuring lifecycles. The states thus created are added to a library of states that are either system-defined, or
were created earlier. These states can then be assigned to one or more Transitions and associated with particular
behaviors, or set as Initial Status at the time of creating a Non-Conformance Lifecycle.
Procedure
1. In the Non-Conformance Lifecycles page, click the button. The Non-Conformance Lifecycle Status page
is displayed.
2. Click Add.
3. In the Create New Status page, set the following parameters:
ID Unique identifier to be assigned to the Non-Conformance Lifecycle

Status to be created. Once set, this field cannot be changed.
Name Name of the Non-Conformance Lifecycle Status to be created.
Description Useful information about the Non-Conformance Lifecycle Status to be

created.
4. Click Save.
3.22.3 Configuring a Transition

This procedure describes how to create a Transition for a custom Non-Conformance Lifecycle. A transition starts
when a condition (for example, Status is Open) is identified, and undergoes completion when the status changes
due to actions or activities performed (for example, upon discarding a Non-Conformance, the Status changes to
Scrap). Transitions, unlike states, are closely tied to the Non-Conformance Lifecycle with which they are associated.
This means that you can only create Transitions in relation to a Non-Conformance Lifecycle, and not separately.
Each Transition must be unique, it is not possible to create two Transitions with the same name. At the time of its
creation, you must associate an initial status and a final status that represent the beginning and the completion of
the transition respectively.
Procedure
1. In the Non-Conformance Lifecycles page, select the Non-Conformance to which you want to add a transition.
2. Click Open.
3. In the Non-Conformance Details page, click the Transitions tab.
4. Click Add.
Name Unique name to be used to identify the Transition.
Description Useful information about the newly-created Transition.

From The initial status that the Non-Conformance must assume. This
represents the start of the transition.
To The status that the Non-Conformance changes to, after an operation

or task has been completed. This represents the completion of the
transition.
6. Click Save.
3.22.4 Associating States with Behaviors

You can associate Non-Conformance States, both system defined and custom, with specific behaviors according to
your needs. In detail, you can choose to which of the States making up the custom Non-Conformance Lifecycle you
want to associate the following behaviors:
• Is Frozen: this behavior causes the state to be frozen (set aside) whenever the entity associated with the custom
Quality Non-Conformance is frozen (suspended).
• Is Scrapped: this behavior causes the state to be scrapped whenever the entity associated with the custom
Quality Non-Conformance is scrapped.
• Is Closed Ok: this behavior causes the state to be the final one whenever the entity associated with the custom
Quality Non-Conformance is scrapped, due to the Non-Conformance itself being set to Scrap.
Prerequisites
To be able to associate the behaviors, you must first configure a Transition between two States.
Procedure
1. In the Non-Conformance Lifecycles page, select a Non-Conformance and click Open.
2. In the Non-Conformance Details page, click the Status Properties tab.
3. Select the State you want to associate with a behavior and click Edit.
4. In the Edit Status panel, flag one or more of the available behaviors according to your needs and click Save.
3.22.5 Associating Transitions with User Roles and E-mail Addresses

User Roles are assigned for performing tasks or activities pertaining to the Transition, and acknowledging the
occurrence of a Transition. After you associate User Roles to acknowledge the completion of a Transition, the
relevant users receive system-generated notification e-mails containing details about the Transition. Assigning a
Transition to User Roles ensures that only users with relevant authorization can perform those activities or tasks
related to the Transition.
Prerequisite
The SMTP server parameters that Opcenter Execution Discrete uses for sending e-mails have been set.
Procedure

Configuring Custom Interlocking Checks
1. In the Non-Conformance Lifecycles page, select the Non-Conformance Lifecycle, the Transitions of which you
want to associate with User Roles.
2. Click Open.
3. In the Non-Conformance Details page, click the Transitions tab.
4. Select the Transition to which you want to assign User Roles and click the button.
5. On the Configure Action panel, click those User Roles that you want to assign from the Unassigned Role(s) list.
The User Roles you select appear under the Assigned Role(s) list.
 To remove a previously-assigned User Role, click the assigned User Role. The selected User Role
appears under the Unassigned Role(s) list.
6. Click Save.
7. To assign User Roles for receiving Transition occurrence e-mails, click the button.
8. On the Configure Notification page, type the e-mail addresses to which notifications must be sent in the E-mail
box, using a comma as a separator between two consecutive entries.
9. Click . The e-mail addresses that you assigned appear under the Assigned E-mail(s) list.
 To remove a previously-assigned e-mail address, click the assigned e-mail address in the Assigned E-
mail(s) list.
10. Click Save.
3.23 Configuring Custom Interlocking Checks

In addition to the standard Inbound and Outbound Interlocking Checks, Opcenter EX DS allows you to configure
custom Inbound and Outbound Interlocking Checks, according to your needs.
 Additional custom business logic is necessary to use these checks at runtime. Each custom Interlocking
Check must necessarily be connected to the Orchestrator command of the corresponding type (Outbound
Orchestrator or Inbound Orchestrator) in order to be handled.
Finally, to be used at runtime, custom Interlocking Checks must be linked to Process Operations, Process
Steps, Work Order Operations and Work Order Steps.
Standard Interlocking Checks, indicated as STANDARD, are listed in the Interlocking Checks page, but cannot be
modified, whereas custom Interlocking Checks, indicated as CUSTOM, can be modified or deleted in terms of
details and parameters.

To access the Interlocking Checks page, click Product and Production Configuration > Interlocking
Checks in the sidebar.
Target User

Configuring Custom Interlocking Checks
Prerequisites
A custom Interlocking Check is available in your system. For more information on how to implement it, see section
How to Develop Custom Interlocking Checks of the Opcenter Execution Discrete Extensibility Guide.
Procedure
1. In the Interlocking Checks page, click Create.
2. Set the following parameters according to your needs:
Identifier Unique identifier to be assigned to the custom Interlocking Check.

Once saved, this parameter can no longer be modified.
Name Name of the custom Interlocking Check.
Description Useful information about the custom Interlocking Check.
Operation-relevant If this check box is selected, the Interlocking Check will be linkable
only to Process or Work Order Operations.
Step-relevant If this check box is selected, the Interlocking Check will be linkable
only to Process or Work Order Steps.
3. Click Create.
4. In the Interlocking Checks page, open the Interlocking Check you have created and switch to the Parameters
tab.
5. Click Interlocking Check Parameters.
Identifier Unique identifier to be assigned to the custom Interlocking Check

parameter. Once saved, this parameter can no longer be modified.
Name Name of the custom Interlocking Check parameter.

Configuring Custom Result Types
Data Type Data Type of the Interlocking Check parameter. Accepted types:
• string
• int
• smallint
• tinyint
• bigint
• decimal
• timespan
• datetime
• guid
• bool
Mandatory If selected, this parameter is mandatory for the Interlocking Check.
Is List If selected, the parameter can accept a list of values.

7. Click Create.
3.24 Configuring Custom Result Types

Custom Result Types come in handy when you want to make a clear distinction between what is to be considered a
positive or negative Result in a given context compared to others: for example, if you want to declare a negative
Result for an MTU for what concerns consumption, and the standards for the same MTU are more stringent for what
concerns assembly, you can configure Result Types "NOK for Consumption" and "NOK for Assembly" to satisfy your
needs.
Target User
Users with the Product Engineer or Production Coordinator role can perform this action.
Procedure
1. Operating in the Home Page, click the Result Types tile.
2. In the Result Types page, click the Create Result Type icon.
3. In the Create Result Type panel, in field Result Value, type a meaningful name that you want to assign to the
custom Result Type you are creating: once saved, this name cannot be modified.
4. Select the isDefault checkbox if you want the custom Result Type you are creating to be used as the default for
Result management.
5. Select the Is NOk checkbox if you want the custom Result Type you are creating to be used to represent a
negative Result.
6. Click the Create button.
7. If not already enabled, set the Result Management configuration key.

Linking Items to Buffer Definitions
 • The settings of both standard and custom Result Types can be updated by clicking : however, the
Is NOk checkbox can be changed only if the selected Result Type has not already been associated to a
Result.
• Only custom Result Types can be deleted, provided that they have not already been linked to a Result.
3.25 Linking Items to Buffer Definitions

You can link a Buffer Definition previously created to specific Engineering entities. In this manner, you can establish
logistic constraints on Buffer Definitions and, by extension, on the Buffers that will be instantiated from them. For
example, you can declare that a specific Buffer Definition is able to transport or store only a maximum quantity of a
specific Material, or only items belonging to a specific Logistic Class, and so on.
When a Buffer Definition is instantiated, its links are instantiated in the same manner to the corresponding Runtime
entities, but they can be overriden, if necessary.
You can link the following entities to a Buffer Definition:
• Tool Definitions
• Materials
• Logistic Classes
Target User
Procedure
1. Click Product and Production Configuration > Buffer Definitions in the sidebar..
2. In the Buffer Definitions page, select the Buffer Definition that you want to link to a particular entity and click
Open.
3. Select the tab corresponding to the desired item type:
• Materials
• Tool Definitions
• Logistic Classes
4. Click .
5. Set the following parameters for the entity to be linked to the Buffer Definition:
Min. Value Minimum quantity, according to the selected Unit of Measure.
Threshold Value Quantity that, when reached, triggers an automatic

replenishment of the container.
Target Value Quantity that is to be reached when an automatic replenishment

of the container occurs.
Max. Value Maximum quantity, according to the selected Unit of Measure.

How to Configure Setpoints
UoM Unit of Measure to be adopted.

6. Select one or more entities to be linked to the Buffer Definition and click Add.
 Existing links between entities and a Buffer Definition can be unlinked by selecting the linked entity
from the list and clicking .
3.26 How to Configure Setpoints

Setpoints are used to drive the behavior of a specific Machine or Tool at runtime, thereby eliminating the need for
the Shop Floor Operator to perform manual adjustments.
Once created, Setpoints are merely empty containers and in order to function, they must be filled with one or more
variables and then must be declared compatible with a set of Machines or Tools. The compatibility can be declared
for a set of Machines/Tools (using the related Definition) or for a single item. When a Setpoint is declared
compatible with a Machine/Tool Definition, the behavior is automatically inherited by all related Machines and
Tools (both those already existing and those that will be created). Consequently, when the compatibility with a
Definition is removed, the system automatically removes the compatibility between the involved Setpoint and all
items generated from that Definition.
Since Setpoint variables contain the values to be transferred at runtime, during Process Operation configuration it
will be necessary to map them to the related Automation Node Parameters.
Only released Setpoints will be available to be used at runtime.
Example
If a certain Machine must reach a specific temperature before it can be used to execute a Work Order Operation, the
Setpoint to be linked to that Machine must contain a variable for the temperature, the value of which is equal to
that specific temperature.
At runtime, the value of the Setpoint will be transferred to the Machine, that is linked to the Automation Layer and
must reach that temperature value prior to being used automatically.

To access the Setpoints page, select the Setpoints tile in the home page.
Target User
Workflow
1. Create a Setpoint.
2. Add Variables to the Setpoint.
3. Release the Setpoint.
4. Link the Setpoint to the entities of interest, thus declaring their compatibility.

How to Configure Setpoints
Creating Setpoints
1. In the Setpoints page, click Create.
Identifier The unique Identifier of the Setpoint. Once saved it cannot be

changed anymore.
Name The name of the Setpoint.
Description Useful information about the Setpoint.

3. Click Create.
Adding Variables to a Setpoint

1. Select the Setpoint in the Setpoints page and then click Open.
2. In the Variables tab, click Create.
Identifier The unique Identifier of the variable. Once saved it cannot be

changed anymore.
Name The name of the variable.
Description Useful information about the variable.
Data Type The data type of the variable that will be mapped to an Automation
Node Parameter.
Editable If this check-box is selected, it will be possible to modify the value of

the variable at runtime.
Default Values The default value (or values) of the variable. This parameter is not
available if Data Type is set to DateTime.
4. Click Save.
Releasing Setpoints
1. In the Setpoint tab, select the Setpoint to be released.
2. Click Release.
Linking a Setpoint to an Entity

1. Select the Setpoint of interest in the Setpoints page and then click Open.
2. Click one of the following tabs:
• Machine, to link the Setpoint to a specific Machine (represented by an Equipment of Unit Level).

How to Configure Barcode Rules
• Machine Definition, to link the Setpoint to all Machines that have been or will be generated from a
specific Equipment Type (of Unit Level).
• Tools, to link the Setpoint to a specific Tool.
• Tool Definitions, to link the Setpoint to all Tools that have been or will be generated from a specific Tool
Definition.
3. Click . Select one or more of the entities that you want to link to the currently-selected Setpoint.
4. (Optional) If you intend to link more than one Setpoint to the entity of your choice, select the Is Default check-
box to set the currently-selected Setpoint as the default for the selected entity.
5. Click Add.
 If necessary, any entity that has been linked to a Setpoint can be unlinked from it by selecting its
corresponding tile and then clicking .
Result
The items that have been set as compatible with a Setpoint are listed in the related tab of the Setpoints page, and
in case of Tool Definitions and Tools, within the Setpoints tab of the Tool Definitions page and Tools page.
3.27 How to Configure Barcode Rules

Opcenter Execution Discrete provides you with the possibility of configuring Barcode Rules which make it possible
to validate a Barcode string against a specific, configurable rule.
Barcode Rules can be configured with Rule Parts in the SerialNumber/BatchId and Material combination, and a
regular expression which is used to validate the Barcode string.
To validate the barcodes at runtime, the Barcode Rules can be associated with either the Material or the Functional
Code of the Material. Default barcode rules can also be configured using a dedicated configuration key.
In addition, it is possible to view the History of each Barcode reading executed at runtime to easily know which ones
are valid or not.
For information on further functionalities provided by Opcenter Execution Foundation, refer to the Barcode App
documentation in the Opcenter EX FN User Manual.
Workflow
1. Create Barcode Rules.
2. Add Rule Parts.
3. (Optional) Associate a Barcode Rule with a Material.
4. (Optional and not available in the Siemens_OPC_EXDS_AM UI Application) Associate a Barcode Rule with a
Functional Code.
5. View Barcode History.
3.27.1 Creating Barcode Rules

Barcode Rules are empty containers to which one or more Rule Parts can be added according to your needs.
Procedure
1. Click the Barcode Rules tile.
2. In the Barcode Rules page, click .
3. Set the required attributes:

Identifier The identifier assigned to the Barcode Rule. Once the Rule is created,
the Identifier value cannot be modified.
Name The name assigned to the Barcode Rule.
Description (Optional) Additional information on the Barcode Rule.

4. Click Save.
3.27.2 Creating Rule Parts

After creating a Barcode Rule, you must add one or more Rule Parts which will make up the final Rule. Each Rule
Part is defined by a regular expression which will be used to validate the received Barcode string at runtime.
Procedure
1. In the Barcode Rules page, select a Barcode Rule.
2. Click the Rule Parts tab.
3. Click and set the required attributes:
Identifier The identifier assigned to the Rule Part. Once the Rule Part is created,
the Identifier value cannot be modified.
Name The name assigned to the Rule Part.
Description (Optional) Additional information on the Rule Part.
Item Type (Optional) Represents the item which must be considered in the
Barcode Rule.
The product offers two predefined item types which is used for
traceability at runtime:
• PartNumber - The identifier of the Material associated with
the barcode rule.
• SerialNumber - The identifier of the Material Tracking Unit
associated with the barcode rule.
Prefix (Optional) Represents the prefix to be included in the regular

expression. For example: SN for Serial Number.

Expression Represents the regular expression which will be used to validate the
received Barcode string.
For example:
\d{2} which means that the matching Barcode must contain two
numbers.
The following characters are currently not supported:
• \r
• \n
• \t
The expression will be generated with boundaries (\b) at the beginning
and at the end.
Suffix (Optional) Represents the suffix to be included in the regular

expression. For example: 00. The Barcode provided must end with the
numerals 00.
4. Click Save.
Example
Here below an example of the same Barcode matching or not matching the regular expression defined in the Rule:
Barcode Regular Expression Result
SN12NSPN12NP \bSN\d{2}NSPN\d{2}NP\b True
SN123NSPN1234NP \bSN\d{2}NSPN\d{5}NP\b False
Result
In the Overview tab of the Barcode Rules page, if you add more than one Rule Parts to your Barcode Rule, it is
possible to view the sum of all the regular expressions in the Expression field.
3.27.3 Associating a Barcode Rule with a Material

Once Barcode Rules are created, they can be associated with Materials and retrieved at runtime. Barcode Rules can
also be associated with the Functional Code of a Material.
At runtime, when a string is received from a Barcode reader, the rule is automatically retrieved from the Material or
alternatively from the Functional Code of the Material.
A default rule can also be configured using the Default Barcode Rule configuration key. If set, the default rule is
retrieved when no such rules are found associated with the Material or the Functional Code of the Material.
At runtime, the Barcode received for consumption is scanned and the MTU can be consumed once the Barcode is
successfully validated.
Procedure
1. In the Materials page, to associate the Barcode Rule with the Material either:

• click the button to create a new Material, setting also the Barcode Rule parameter.
• click the button to open an existing Material and then click the button to edit and set
the Barcode Rule parameter.
2. Click Save.
3. If necessary, to remove existing associations, select the Material of interest, click and then click the
Unlink Barcode Rule icon.
3.27.4 Associating a Barcode Rule with a Functional Code

Barcode Rules can also be associated with Functional Codes. In this way, whenever a Barcode string is received at
runtime, if a Barcode Rule has not been set for the Material, the system retrieves the rule to validate the Barcode
from the corresponding Functional Code.
Procedure
1. In the Functional Codes page, select the Functional Code of interest and click .
2. In the Overview tab, click and then select the Barcode Rule to be linked to the Functional Code.
3. If necessary, to remove existing associations, click the button.
3.27.5 Viewing Barcode History

The Barcode History page tracks the outcome of each Barcode reading executed at runtime, indicating also if the
Barcode string is valid and matches the Rule.
Procedure
1. Open the Barcode History page. The system displays the following details:
Barcode The identifier of the Barcode.
Validated On Timestamp indicating when the Barcode string has been

validated.
Rule Identifier The identifier of the Rule used to validate the Barcode.
Expression The regular expression used to validate the Barcode string.
Is Valid Flag indicating if the Barcode is valid or not, which means if it

matches the Rule or not.
User The user who performs the operation.
Created On Timestamp of the History log creation.

How to Configure Line Side Positions
Last Updated On Timestamp of the History log last update.
3.28 How to Configure Line Side Positions

Line Side Positions are abstract representations of specific areas or accessories allocated to store Materials. They
contain Bins, which represent a logical unit of measure indicating how the Material is stored, and which are used to
replenish them.
Line Side Positions can be managed automatically or manually. For those Line Side Positions which are managed
automatically, thresholds must be configured to define priorities and values.
In the Line Side Positions page, you can:
• create new Line Side Positions,
• modify Line Side Positions previously created ( button), except for their Id, and the associated Material and
Workplace if the Line Side Position has been released at least once,
• delete Line Side Positions that are no more necessary ( button),
• release Line Side Positions ( button). In case of automatically managed Line Side Positions, there must be at
least one Threshold associated.
Each time the Threshold reaches or falls below the configured value, a Kanban Call is automatically sent to the
Warehouse to request a replenishment, equal to the Bins maximum capacity for the Bin Standard Quantity. If there
are more than one Thresholds associated, the system selects the one with the highest priority. The call is performed
using a Kanban Output Message.
At runtime, it is possible to manage released Line Side Positions and the related Kanban Calls, from the Line Side
Positions Monitoring page.
For additional information, please refer to the Line Side Positions and the Kanban Calls pages in the Opcenter
Execution Discrete Product Overview.
Target User

To access the Line Side Positions page, click Material Runtime > Line Side Positions in the sidebar.
Workflow
1. Create Line Side Positions.
2. Configure Thresholds for automatic Kanban Calls.
Creating Line Side Positions

1. In the Line Side Positions page, click .

How to Configure Line Side Positions
Identifier The unique identifier of the Line Side Position.
Name (Optional) The name to be assigned to the Line Side Position.
Description (Optional) Useful additional information on the Line Side Position.
Material The Material to be stored in the Line Side Position.
Workplace The Workcenter or Unit to be associated with the Line Side Position.
Material A released Message Definition associated with a Kanban Output Message, to be selected
Source from the entity picker.
Only manual (Optional) If selected, indicates that the decreasing of the Material quantity and related
Kanban call Kanban Call will be managed manually at runtime.
Bins to be (Optional, available if Only manual Kanban call is selected) The number of Bins which
requested can be requested for the Line Side Position, in case of manual Kanban call.
Maximum Bins (Not available if Only manual Kanban call is selected) The maximum capacity of the Line
Capacity Side Position, expressed in Bins.
Bin Standard The Unit of Measure of the Bin Standard Quantity. It is automatically filled with the Unit
Qty (UoM) of Measure of the Material selected before.
Bin Standard (Not available if Only manual Kanban call is selected) Value representing the capacity of
Qty (Value) a single Bin, therefore how many pieces the Bin must contain.
Start Quantity (Optional, not available if Only manual Kanban call is selected ) The start quantity of
Materials a Line Side Position contains. If not specified, it is automatically calculated as
the maximum quantity of the Material that the Line Side Position can contain. For
example, if the Maximum Bins Capacity is 5 and the Bin Standard Quantity is 2, then the
start quantity is 10.
BoM (Not available if the flag Only manual Kanban call has been set.) Defines how the
Consumption Materials inside the Material Specification must be consumed, thus automatically
Type decreasing, each time the production item exits the Workplace. Possible Values are:
• Percentage (default)
• FixedQuantity
• Fraction
For example, in case you have 4 wheels, you can choose to consume 50 % in the
Workplace associated with the Line Side Position you are creating, and the other 50 % in
another Workplace associated with a different Line Side Position.

How to Configure Qualification Criteria
BoM (Not available if the flag Only manual Kanban call has been set.) The value associated
Consumption with the Material consumption.
Value
Note If the BoM Consumption Type is set to Percentage, the whole quantity is
consumed regardless of the value set in this field.
3. Click Save.
Configuring Thresholds for automatic Kanban Calls

1. In the Line Side Positions page, select a Line Side Position (whose checkbox Only manual Kanban Call has not
been selected) and click .
2. Click the Thresholds tab.
3. Click the button and then set the following parameters:
Priority Indicates the Threshold priority. Priority and Value are strictly
connected to one another. If the Value is 5, then the Priority is
also 5 (which means that it is lower). If the Value is 1, then the Priority is
1, which means that it is higher.
Value Indicates the Threshold value. You cannot insert for example a Value 10
with Priority 2, because there could exist another Threshold with a
lower value having therefore a higher priority.
4. Click Save.
3.29 How to Configure Qualification Criteria

Qualification Criteria represent a set of rules that, once configured, can be associated with Process Operations and
applied to the Master Plan from which the Work Order is generated, to select and use at runtime only those
Operations deemed necessary.
In the Qualification Criteria page, you can:
• create new Qualification Criteria,
• modify Qualification Criteria previously created ( button), except for their Id,
• delete Qualification Criteria that are no more necessary ( button), provided that they are not already linked
to an Operation of a released Process.
• lock Qualification Criteria previously created ( button), so that they cannot be modified anymore.
Once created, Qualification Criteria are empty containers for which rules must be configured.
The product comes provided with a set of predefined entities with their respective properties and values, for which
it is possible to configure filter clauses using logical operators, to create the logical expression representing the final
rule.
In addition, different Qualification Criteria can also be combined to produce more complex rules.

If the Production Resolution common component has been properly configured during the Opcenter Execution
Discrete installation, Qualification Criteria can be filtered and validated. For additional information refer to the
Configuring the Production Resolution Common Component page in the Opcenter Execution Discrete Installation and
Configuration Manual.
For additional information on Qualification Criteria, refer to the Qualification Criteria page in the Opcenter Execution
Discrete Product Overview.
Should it be necessary to extend the entities provided for configuring custom filter clauses, refer to How to
Implement Custom Filters for Qualification Criteria page in the Opcenter Execution Discrete Extensibility Guide.
Target User
User with the Product Engineer role can perform this procedure.

To access the Qualification Criteria page, click Product and Production Configuration > Qualification
Criteria in the sidebar.
Workflow
1. Create the Qualification Criteria.
2. Configure the Filter Clauses.
Creating Qualification Criteria

1. In the Qualification Criteria page, click the button.
Id The unique identifier of the Qualification Criteria.
Name (Optional) The name to be assigned to the Qualification Criteria.
Description (Optional) Useful additional information on the Qualification

Criteria.
3. Click Save.
Configuring Filter Clauses

1. In the Qualification Criteria page, click the Filter Clauses tab.
2. Click > Add New Clause and then set the following parameters:
Entity The entity for which you want to set the clause. Possible values are:
• Qualification Criteria: to create more complex rules combining
different Qualification Criteria.
• Work Order
• Material

Property According to the entity selected in the previous step, the system displays a
series of properties. In detail:
Qualification Criteria: Id
The identifier of the selected Qualification Criteria must be different from
the one for which you are configuring the filter clause.
Work Order:
• Final Product
• Plant
• Priority
• Due Date
• Creation Date
Material: Functional Code
Operator In the drop-down menu, the system displays a list of predefined logical
operators, to be selected according to your needs:
• =
• !=
These operators permit the inclusion (in the first case) or exclusion (in the
second case) of certain elements making up the final rule, according to the
entity and property you have selected in the previous steps.
In addition, the following logical operators are specific to Creation Date
and Due Date:
• <
• >
• <=
• >=
 If you have selected the Qualification Criteria entity in step 1, this

field is automatically disabled.
Value The value to be assigned to the Property field chosen before, to be selected
with the entity picker (or date picker in case of Due Date and Creation
Date), except for the Priority value, where you can type a value of your
choice.
3. (Optional) To have a preview of the rule before saving it, click the Preview button. The rule is displayed in the
Rule Preview area.
4. Click to save the clause.
5. (Optional) To create another filter clause to be combined with the one already set, click > Add New
Clause and select the logical operator And/Or (disabled when only one clause is created). Insert the required
parameters as described in step 2 and click .
6. (Optional) To create more complex rules, after having created two or more set of clauses (following the
procedures described in steps 2-5), flag them to create a group of clauses and click . In the Rule Preview,
the grouped clauses are included in brackets.

 Filter Clauses previously created can be removed by clicking the button.
Result
In the Overview tab of the Qualification Criteria page, under the Rule area, it is possible to view both short and
extended form of the rule previously created and saved. If you have created only one rule, both Rule and Extended
Rule display the same expression.
If more Qualification Criteria are combined, it is possible to view their details in the Extended Rule.

How to Create and Prepare Human Resources and Their Capabilities
Configuring Skills
4 How to Create and Prepare Human Resources and Their

Capabilities
For reasons of security, as well as to allocate the best possible workforce for achieving successful production
targets, it must be established who can perform certain actions within a production plant and what specific
certified knowledge or know-how (known as Skills) these individuals must possess in order to carry out their
activities in the best possible manner. Those users who do not possess the appropriate Certificates attesting that
they have undergone sufficient training to perform delicate tasks must be inhibited from doing so.
In Opcenter EX DS, the term Human Resources is used to cover these aspects: the Human Resources of a production
plant are its Users, each of whom possesses certain Skills and certain Certifications attesting his/her personal
capabilities.
In some cases, it may be a good idea to form Teams of individuals who have the same or similar Skills and
Certificates to:
• speed up execution;
• have a pool of interchangeable users available for certain tasks or who work together to complete a specific job.
Target User
Users with the Product Engineer or Production Coordinator role can perform this procedure.
Workflow
1. Configure Skills.
2. Configure Certifications.
3. (optional) Create and prepare Teams.
4.1 Configuring Skills

Before starting the production execution, you can optionally configure a set of Skills. A Skill represents a specific
requirement which subsequently can either be directly associated with Process Operations and/or Work Order
Operations or assigned to specific Users through Certifications.
Target User
Procedure
1. Click Product and Production Configuration > Skills in the sidebar.
2. In the Skills page, click Create.

Configuring Certifications
Identifier Unique Identifier for the Skill.
Name Name of the Skill.
Description (Optional) Description of the Skill
Color (Optional) Color to be associated with the Skill. The color will be
displayed in the Production Coordinator Dashboard.
4. Click Save.
4.2 Configuring Certifications

To properly configure the production environment, you must set restrictions on the access of specific users to
certain functionalities, so that only solely qualified Users are allowed to perform certain actions, according to their
Roles and their knowledge.
Permissions are configured through an entity called Certification, which can be associated both with users and
roles. In addition, it is also possible to associate the Certification with:
• Final Materials of the Work Orders.
• Workcenter where the production occurs.
• Machines to be used in the production.
• Skills required to perform specific Work Order Operations.

To access the Certifications page, click Product and Production Configuration > Certifications in the
sidebar.
Target User
Users who possess the Product Engineer role can perform this operation.
Workflow
1. Create a Certification.
2. Add or link items to the Certification.
Creating a Certification
1. In the Certifications page, click Create.
Identifier Unique identifier to be assigned to the Certification. Once saved, this


Configuring Certifications
Name Name to be assigned to the Certification.
Description Useful information about the Certification to be created.

3. Click Create.
Adding or Linking Items to a Certification

1. In the Certifications page, select a Certification and click Open.
2. If you want to add one or more Materials and/or Workcenters to a Certification, select the tab of interest
according to your needs:
Tab Description
Materials The Users/User Roles linked to this Certification can manage Work
Orders that produce one or more Final Materials that you will specify
herein.
Workcenters The Users/User Roles linked to this Certification can manage Work Order
Operations that are executed on one or more Workcenters that you will
specify herein.
and then click Add: this opens a dedicated panel.

3. Select the item(s) to be added to the Certification and then click the Add button.
4. If you want to link Equipment Types, Skills, Users and/or Roles to the Certification, select the tab of interest
according to your needs:
Tab Description
Equipment Types The Users/User Roles linked to this Certification can manage Work
Order Operations that are executed with one or more Equipment
Types that you will specify herein.
Skills The Users/User Roles linked to this Certification can manage Work
Order Operations only when they possess one or more Skills that you
will specify herein.
Users Selected Users are authorized to execute certain operations. After

selecting one or more Users of interest, set an expiration date for the
link.
Roles Selected User Roles are authorized to execute certain operations.

After selecting one or more User Roles of interest, set an expiration
date for the link.
and then click Link: this opens a dedicated panel.

5. Select the item(s) to be linked to the Certification and then click the Link button.

How to Create and Prepare Teams
4.3 How to Create and Prepare Teams

Teams are groups of Users that can be created to perform production operations together: a single Team member
can start/pause/complete Work Order Operations on behalf of the entire Team.
Target User
Users with the Product Engineer or the Production Coordinator roles can perform this operation.

To access the Teams page, click Production Coordination > Teams in the sidebar.
Workflow
1. Create a Team.
2. (optional) Link Skills to the Team so that only those Users who possess these Skills (optionally, specifying a
minimum Skill level) may join the Team at runtime.
3. Add members (Users) to a Team.
Creating Teams
1. In the Teams page, click Create.
Identifier Unique identifier to be assigned to the Team. Once saved, this

Name The name of the Team. The field is mandatory.
Description Optional Description for the Team.
Max. Number of Users If a number is entered, the Team will allow only that maximum
number of Users.
If the field is left empty, the Team will have no limitations on the
number of Users.
3. Click Create.
 • Empty Teams (that is, without members) can be deleted by selecting them and clicking Delete.
• When editing existing Teams, you can change the Max. Number of Users field only for empty Teams.
Linking Skills to Teams
 Linking Skills is permitted only when a Team is empty.

How to Create and Prepare Teams
1. In the Teams page, select a Team and click Open.

2. Click the Skills tab: any Skills currently linked to the selected Team will be displayed.
3. Click Link: this calls up the Link Team Skill panel.
4. (optional) In the Level field, insert the minimum required Skill level.
5. In the Skill field, click : from the Select Skill panel, select one or more Skills to be linked to the Team.
6. Click Link.
If you want to unlink a Skill from a Team, select one or more Skills and click Unlink.
Adding Users to Teams
 Only those Users who possess Skills that match those required by the Team can be added to it.
1. In the Teams page, select a Team and click Open.

2. Click the Users tab: any Users currently belonging to the selected Team will be displayed.
3. Click Add, select one or more Users and click Associate.
If you want to remove a User from the Team, select the User and click Remove.

How to Configure the Production Processes
How to Manage As Planned BOPs and Processes
5 How to Configure the Production Processes

To use Opcenter Execution Discrete to manage your production, you can define one or more As Planned BOPs (Bills
of Processes) or Master Plans mapping all activities that must be performed to start and complete the production
execution within the plant.
As Planned BoPs contain the specific structure, as well as the exact combination of data to be used to generate a
specific Work Order for producing a specific product.
Master Plans contain the structure and all the possible combinations of data for producing a generic product.
For more information, see sections As Planned BOPs, Master Plans, Processes, Operations and Steps in the Opcenter
Execution Discrete Product Overview.
Target User
Workflow
1. Create either an As Planned BOP or a Master Plan.
• Create the Subprocesses (not applicable for Master Plans)
• Create the Operations.
3. If you have created Subprocesses at step 2, create the Operations.
4. Define Dependencies between Operations.
5. Define Groups of Alternative Process Operations (not applicable for Master Plans and not available in the
Siemens_OPC_EXDS_AM UI Application)
6. Associate Items with Operations.
7. Create the Steps.
8. Define Dependencies between Steps.
9. Associate Items to Steps.
5.1 How to Manage As Planned BOPs and Processes

As Planned BOPs are structures containing one or more Processes hierarchically grouped together to define the
execution of a specific manufacturing activity. An As Planned BOP contains one Process, called Root Process. The
Root Process can contain other Processes, called Subprocesses, or Process Operations.
For more information on the hierarchical structure of an As Planned BOP, see section As Planned BOPs, Master
Plans, Processes, Operations and Steps of the Opcenter Execution Discrete Product Overview.
To create an As Planned BOP, you must contextually specify its Root Process, which can be created manually "on
the fly" or chosen from the Process Catalog.
To edit an existing As Planned BOP, you can add a Process inside its structure. Again, the Process can be created
manually or chosen from the Catalog.
An As Planned BOP can be:
• Cloned: this operation creates a copy of the structure and gives a completely new baseline identifier to the
clone, effectively separating it from the original structure.
• Evolved: this operation revises the As Planned BOP, incrementing its baseline identifier but keeping a link (the
Plant BOP Identifier parameter) with the original structure.
If the Root Process of an As Planned BOP contains only Operations (that is, there are no Subprocesses), it is also
possible to create a new Revision of the Process.

Actual Work Orders can then be created by instantiating:

• an entire As Planned BOP. In this case, this particular instantiation will produce as many Work Orders as there
are leaf Processes contained in the As Planned BOP.
• a leaf Process inside an As Planned BOP. In this case, a single Work Order is created.

To access the As Planned BOPs and Processes page, click Product and Production Configuration > As
Planned BOPs and Processes in the sidebar.
You can perform the following operations:
• Creating As Planned BOPs and Processes
• Linking Processes to As Planned BOPs
• Cloning an existing As Planned BOP
• Evolving an existing As Planned BOP
• Creating a new Revision of a Process
• Completing an As Planned BOP
5.1.1 Creating As Planned BOPs and Processes

This procedure allows you to create a new Process and link it to:
• a new As Planned BOP: the newly created Process becomes the Root Process of the As Planned BOP.
• an existing As Planned BOP: the newly created Process becomes a Sub-Process of an existing Process without
Operations, inside the As Planned BOP.
When a new Process is created, it is automatically added to the Process Catalog.
When a new As Planned BOP is created, its Completed status is set to false. You need to complete the As Planned
BOP to make it available for the creation of Work Orders.
Procedure
1. In the As Planned BOPs and Processes page, click .
As Planned BOP To create a new As Planned BOP, click and then insert the
required identifiers in the Plant BOP Identifier and Baseline edit
boxes.
To add the Process to an existing As Planned BOP, either type the
baseline ID of the As Planned Bop or click and select the As
Planned BOP from the list.
Parent Process (Visible and mandatory only if you have selected an existing As
Planned BOP) Identifier of the parent Process. This field appears and
can be populated only if in the As Planned BOP field you choose an
existing BOP and this BOP already contains Processes.

Identifier Unique identifier to be assigned to the Process. Once saved, this

Name Name of the Process.
Description Useful information about the Process.
Revision Identifier of the Process's revision.
Plant Either the Enterprise or Site where the Process execution will take
place, to be selected among those created from the Equipment
page.
Material exists, you can create a new Material. The Final Material field
can be left blank: if a Final Material is not specified at this time, it will
be required when creating a Work Order from this Process. This allows
you to create a generic Process which can be used to produce
Sequence A number determining the order in which the Process will be

executed.
Process.
5.1.2 Linking Processes to As Planned BOPs

This procedure allows you to link an existing Process previously added to the Process Catalog to:
• a new As Planned BOP: the Process becomes the Root Process of the As Planned BOP
• an existing As Planned BOP: the Process becomes a Sub-Process of an existing Process without Operations,
inside the As Planned BOP.
When a new As Planned BOP is created, its Completed status is set to false. You need to complete the As Planned
BOP to make it available for the creation of Work Orders.
Procedure
1. In the As Planned BOPs and Processes page, click Link Process to Baseline.

Baseline The baseline ID of the As Planned BOP to which the Process belongs.
To create a new As Planned BOP, click and then insert an

identifier in the Process BOP Identifier and the Baseline edit box.
To add the Process to an existing As Planned BOP, either type the
baseline ID of the As Planned Bop or click and select the As
Planned BOP from the list.
Parent Process Identifier of the parent Process. This field appears and can be
populated only if in the Baseline field you choose an existing BOP
and this BOP already contains Processes.
Process Name Identifier of the Process to link to the As Planned BOP.

3. Click Link.
5.1.3 Cloning an As Planned BOP

This procedure allows you to create a clone of an existing As Planned BOP. Contrary to the evolving operation, the
cloning operation creates a copy of the As Planned BOP with a completely new baseline identifier.
Procedure
1. In the As Planned BOPs and Processes page, select the As Planned BOP to be cloned.
2. Click Clone As Planned BOP.
3. In the Clone As Planned BOP page, insert the new Plant BOP Identifier of the cloned As Planned BOP in
the Plant BOP Identifier field
4. Insert the new Baseline Identifier in the Baseline ID field.
5. Click Save.
5.1.4 Evolving an As Planned BOP

This procedure allows you to create an evolution of an existing As Planned BOP. Contrary to the cloning operation,
the evolution increments automatically the Baseline Identifier of the As Planned BOP, keeping a link with the
original structure (the Plant BOP Identifier parameter).
It is necessary to perform this operation while creating a new revision of a Process in order to be able to update the
Work Orders generated from the linked As Planned BOP.
Procedure
1. In the As Planned BOPs and Processes page, select the Process to be evolved.
2. Click Evolve As Planned BOP.
5.1.5 Creating a Revision of a Process

This procedure allows you to create a new Revision of a Process. You can revise only Processes containing Process
Operations, not Processes containing Subprocesses.

How to Manage Master Plans and Processes
 A Process can also be revised from the Process Catalog page.
Procedure
1. In the As Planned BOPs and Processes page, select the Process for which you want to create a new revision.
2. Click Create > Revision: the new Process is displayed in the Processes page and a notification is sent to the
subscribed users, if any.
5.1.6 Completing an As Planned BOP

When an As Planned BOP is created, either creating a Root Process manually or adding it from the Process Catalog,
its Completed status is initially set to false and therefore the As Planned BOP is not yet available for the creation of
Work Orders (either from a Process or from an As Planned BOP).
You need to complete the As Planned BOP before using it.
Procedure
1. In the As Planned BOPs and Processes page, select the As Planned BOP to be completed.
2. Click Open.
3. Click Complete and confirm the operation.
5.2 How to Manage Master Plans and Processes

Master Plans are structures containing one root Process and one or more Process Operations to define the
execution of a specific manufacturing activity.
For more information on the hierarchical structure of a Master Plan, see section As Planned BOPs, Master Plans,
Processes, Operations and Steps of the Opcenter Execution Discrete Product Overview.
To create a Master Plan, you must contextually specify its Root Process, which can be created "on the fly" or chosen
from the Process Catalog.
Once the Master Plan is configured along with all the required production combinations, it is necessary to complete
it.

To access the Master Plan and Processes page, click Product and Production Configuration > Master Plans
and Processes in the sidebar.
You can perform the following operations:
• Creating Master Plans and Processes
• Linking Processes to Master Plans
• Completing Master Plans
5.2.1 Creating Master Plans and Processes

This procedure allows you to create a new Process and link it to:

• a new Master Plan: the newly created Process becomes the Root Process of the Master Plan.
• an existing Master Plan: the newly created Process becomes a Sub-Process of an existing Process without
Operations, inside the Master Plan.
When a new Process is created, it is automatically added to the Process Catalog.
When a new Master Plan is created, its Completed status is set to false. You need to complete the Master Plan to
make it available for the creation of Work Orders.
Procedure
1. In the Processes and Master Plans page, click Create.
Master Plan Identifier of the Master Plan.

To add an existing Master Plan, either type the ID of the Master Plan
or click and select the Master Plan from the list.
To create a new Master Plan click and insert values for the
Identifier, Correlation Identifier and Unique Identifier parameters.
In addition, select Is Specialized, if you want to restrict the kind of
specifications, (such as Tools, Machines, Work Instructions and
Materials) configurable for the Master Plan.
Identifier Unique identifier to be assigned to the root Process. Once saved, this
Name Name of the root Process.
Description Useful information about the root Process.
Revision The Revision (version) to be assigned to the root Process.
Plant Either the Enterprise or Site where the Process execution will take
place, to be selected among those created from the Equipment
Configurations page.
Material exists, you can create a new Material. The Final Material
field can be left blank: if a Final Material is not specified at this time,
it will be required when creating a Work Order from this Process. This
allows you to create a generic Process which can be used to produce
Sequence A number determining the order in which the Process will be

executed.
Process.

5.2.2 Linking Processes to Master Plans

This procedure allows you to link an existing Process to:
• a new Master Plan: the Process becomes the Root Process of the Master Plan
• an existing Master Plan: the Process becomes a Sub-Process of an existing Process without Operations, inside
the Master Plan.
Existing Processes are picked from the Process Catalog.
When a new Master Plan is created, its Completed status is set to false. You need to complete the Master Plan to
make it available for the creation of Work Orders.
Procedure
1. In the Processes and Master Plans page, click Link Process to Master Plan.
Master Plan The Identifier of the Master Plan to which the Process is to be linked.
To add the Process to an existing Master Plan, either type the Identifier
of the Master Plan or click and select the Master Plan from the list.
To create a new Master Plan click and then insert the required
parameters. In addition, select Is Specialized, if you want to restrict
the kind of specifications, (such as Tools, Machines, Work Instructions
and Materials) configurable for the Master Plan.
Process Name Name of the Process to be linked to the Master Plan.

3. Click Link.
5.2.3 Completing Master Plans

When a Master Plan is created, its Completed status is initially set to false and therefore the Master Plan is not yet
available for the creation of Work Orders.
Before using the Master Plan for production, it is necessary to complete it.
Procedure
1. In the Processes and Master Plans page, select the Master Plan to be completed.

Creating a Sub-Process
2. Click and confirm the operation.
5.3 Creating a Sub-Process

Each Process can be divided into Sub-Processes.
Once created the Sub-Process is identified by a minimal set of parameters and you must properly configure it,
before using it in your production processes. The configuration process, which can also be performed at a later
time, consists of creating Sub-Processes or Operations within the Sub-Process itself in order to detail the activities
to be performed.
In addition, you can modify existing Sub-Processes when you want ( ) but, if you want to modify the Sub-Process
considerably, for example adding and/or removing Operations and Sub-Processes, you are strongly recommended
to create a new revision of the Sub-Process and then to modify it instead of modifying the existing one.
Sub-Processes are created within a Process, but if necessary you can choose to use them also in other Processes
simply creating a link to them. After performing this operation, a copy of the original Sub-Process is created within
the other Process and, in case of changes, the system will notify the user that they will be applied also to the
original Sub-Process.
Target User
Prerequisite
The parent Process does not contain any Operation.

1. Do one of the following:
• If you have just created and opened a Process, go to step 2.
• If the Process for which you want to define the Sub-Process has been previously created and closed, or if
you have just created a new revision of an existing Process, select it in the Processes page and click
Edit.
2. Click the Sub-Processes tab.
Workflow
1. Create a Sub-Process in either of the following ways:
• From scratch
• Creating a new Revision of an existing Sub-Process
2. If you want to use the Sub-Process in multiple production processes, create a link from the new Sub-Process to
another Process/Sub-Process.
Creating a Sub-Process from Scratch

1. In the Sub-Processes tab, click Create > Manually.
Identifier Unique identifier to be assigned to the Sub-Process. Once saved, this


Creating a Sub-Process
Name Name of the Sub-Process.
Description Useful information about the Sub-Process.
Sequence A number determining the order in which the Sub-Processes

included in the same Process will be executed.
Plant Either the Equipment or Site where the Sub-Process execution will
take place, to be selected among those created from the Equipment
page.
Final Material The Final Material which will be produced by the Sub-Process. If no
Final Material exists, you can create a new Material.
The default quantity of the Material which will be produced by the
Sub-Process.
quantity of the Final Material to be produced by the Sub-Process.
quantity of the Final Material to be produced by the Sub-Process.
3. Click Create.
 You can also create a Sub- Process during the creation of a new Process, setting the Parent Process field
properly.
Creating a Sub-Process Revision

1. In the Sub-Processes tab, select the Sub-Process for which you want to create a new revision.
2. Click Create > Revision.
3. Select the new Sub-Process which is displayed in the Sub-Processes tab and click Edit to:
• modify the Sub-Process parameters.
• modify the Sub-Processes or Operations contained in the Sub-Process.
• change the dependencies between the Operations contained in the Sub-Process.
Linking a Sub-Process to another Process/Sub-Process

1. In the Sub-Processes tab, select the Sub-Process you want to link to another Process/Sub-Process.
2. Click Link Process.
3. Select the Process or Sub-Process in which you want to use the selected Sub-Process.
4. Click Save.
 You can unlink a Sub-Process from a Process or another Sub-Process, by selecting the Sub-Process and by
clicking Unlink. After this disassociation, the system changes the Sub-Process to a Process.

5.4 Creating a Process Operation

Processes, as well as Sub-Processes (in those cases where present), can act as containers for Process Operations,
which will be instantiated as Work Order Operations at runtime to concur to the production of a specific Product.
You can create a new Process Operation from scratch setting a minimal set of parameters: before using it in your
production processes, you must configure the Process Operation properly. The configuration process, which can
also be performed at a later time, consists in creating Process Steps within the Process Operation in order to detail
the activities to be performed. In addition, during the configuration phase, you can also associate the Process
Operations with a set of items in order to provide additional information relative to their execution (for example,
the involved Materials or Tools).
You can modify existing Process Operations when you want ( ). However, if you want to modify the Process
Operation considerably (for example, by associating it with new Machines or changing its dependencies), you are
strongly recommended to create a new revision of the Process Operation and then to modify it, rather than
modifying the existing one.
Process Operations are created within a Process/Sub-Process, but, if necessary, you can choose to use them also in
other Processes/Sub-Processes simply by creating a link to them. After performing this operation, a link to the
original Process Operation is created within the other Process/Sub-Process and, in case of changes, the system
notifies the user that modifications will be applied also to the original Process Operation.
This action cannot be performed if the parent Process already contains at least a Sub-Process.
Target User

1. Click Product and Production Configuration > Processes.
• If you want to create a Process Operation within a Process, select the Process in the Process
Management page and click Details.
• If you want to create a Process Operation within a Sub-Process, open the parent Process, select the Sub-
Process of interest in the Sub-Processes tab and then click Details.
3. Click the Operations tab.
Workflow
1. Create a Process Operation in one of the following ways:
• From scratch
• Creating a new Revision of an existing Process Operation
2. If you want to use the Process Operation in multiple production processes, create a link from the Process
Operation to another Process/Sub-Process.
Creating a Process Operation from Scratch

1. In the Operations tab, click Create > Manually.

Identifier The unique identifier to be assigned to the Process Operation.

Name The name of the Process Operation.
Sequence A number determining a hypothetical execution order of the

Process Operations included in the same Process/Sub-process. It
will be used by the system to automatically create dependencies
with other Process Operations, if you select the Create
Dependency check box displayed below.
Description Useful information about the Process Operation.
Estimated Duration Estimated duration of the execution of the Work Order Operation
generated from the Process Operation. This value is expressed in
hours, minutes, seconds.
Required Inspection Role Deprecated.
Required Certification If a Certification name is specified, the Work Order Operation

generated from the Process Operation can be started, paused or
completed only by an Operator owning the specified
Certification.
If the field is left blank, no Certification is required to execute the
Work Order Operation generated from the Process Operation.
Work Operation To define how the Work Order Operation generated from the
Process Operation must behave at runtime, select one of the
configured Work Operations.
Operation/Step Category Operation/Step Category to be assigned to the Process

Operation.
 The value set for this parameter will be inherited by the

Work Order Operation generated from the Process
Operation you are creating.
If no value is selected for this parameter, the default
Operation/Step Category provided in Opcenter EX DS
will be assigned.
Electronic Signature Start If the check box is selected, the operator credentials are
validated at the time of starting a Work Order Operation. The
validation ensures that only authorized operators start Work
Order Operations.

Defining Dependencies between Process Operations
Electronic Signature Pause If the check box is selected, the operator credentials are
validated at the time of pausing a Work Order Operation. The
validation ensures that only authorized operators pause Work
Order Operations.
Electronic Signature Complete If the check box is selected, the operator credentials are
validated at the time of completing a Work Order Operation. The
validation ensures that only authorized operators complete Work
Order Operations.
Collect Document If the check box is selected, at runtime it will be possible to

associate documents with the Work Order Operation generated
from the Process Operation.
Dependency Type Select one of the following options to specify which type of
Dependency you want to create for the current Process
Operation:
• After End: The destination Process Operation can
start only after the source Process Operation is
started.
• After Start: The destination Process Operation can
start only after the source Process Operation has
ended.
3. Click Create.
Creating a Process Operation Revision

1. In the Operations tab, select the Process Operation for which you want to create a new Revision.
2. Click Create > Revision.
3. Select the new Process Operation displayed in the Operations tab and click Edit to modify its parameters,
define dependencies between Process Operations, create Process Steps within the Process
Operation or associate items to the Process Operation itself.
Linking a Process Operation to another Process/Sub-process

1. In the Operations tab, click Create > Link.
2. In the Process box, select the Process or Sub-process with which you want to link a Process Operation.
3. In the Operation box, select a Process Operation that you want to link to the Process or Sub-process.
4. Click Save.
5.5 Defining Dependencies between Process Operations

You can define if the system must execute the Operations you have created within a Process (or a Sub-Process) in a
specific order, setting dependencies among them.
Then, while editing an Operation ( in the Operations tab) you can click the Dependencies tab to display the list
of dependencies in which the current Operation is involved, and you can remove the unnecessary Dependencies.

Defining Dependencies between Process Operations
Target User
Workflow
1. Create a Dependency.
2. Customize the Dependency Graph.
Creating Dependencies between Operations

1. In the Operations tab, select the Operation the execution of which will influence the execution of another
Operation.
2. Click Add Dependency.
From Operation The Operation that influences the execution of the other Operation.
To Operation The Operation the execution of which is influenced by the

execution of the previously-selected Operation.
Dependency Type Select one of the following:

• AfterEnd: The Operation selected from the To
Operation drop-down list box can start only after the
first Operation is completed.
• AfterStart: The Operation selected from the To
Operation drop-down list box can start only after the
first Operation has started.
4. Click Save.
 You can also create dependencies during the creation of an Operation, both from scratch and by copying it
from an existing one, selecting the Create Dependency check box.
Customizing the Operation Dependency Graph

After creating Dependencies between the Operations contained in a Process/Sub-Process as described above, click
the Operation Dependencies tab: the system displays a graphical representation of the existing dependencies. If
necessary, perform the following operations to customize the Operation Dependency Graph:
• To change the size of the graph, click to the left or right of the Zoom slide.
• To display the entire graph on a single page, click Auto Fit.
• To display a window containing a preview of the entire graph, click Pan and Zoom, and then
• Move the display box to pan the graph.
• Click the lower right corner of the display box to resize the graph.

Defining Groups of Alternative Process Operations
5.6 Defining Groups of Alternative Process Operations

Alternative Process Operations can be adopted in place of the Process Operations that have already been defined
as part of your main execution flow for a specific Process.
 • A Process Operation cannot belong to different groups of Alternative Process Operations.

• The Process Operations making up a group must belong to the same Process.
For more information, see Alternative Process Operations in the Opcenter Execution Discrete Product Overview.
Target User
Prerequisites
• At least three Process Operations have been defined.
• The Process Operations are in sequence and one is configured as predecessor of all the others.
Procedure
1. Operating in the Processes page, select the Process for which you want to create a group of Alternative Process
Operations and click Open.
2. Click the Alternative Operations tab.
3. In the top-right corner, click Add Group.
4. In the Add Alternative Operation Group panel, configure the following parameters:
Name Name to be assigned to the Group of alternative Process

Operations.
Parent Operation The Process Operation configured as predecessor in the

execution flow.
5. Select all those Process Operations (at least two) that you want to be added to the group.
6. Set one of the aforementioned Process Operations as the preferred one: click the star icon next to your
choice.
 This preference setting can be changed, according to your needs. See the section below for details.
7. Click Add.
 Groups of Alternative Process Operations can be inherited only by Work Orders with
either Serialized or Full Quantity Production Type.
Changing the preference setting on Alternative Process Operations

Associating Items to Process Operations
Over time, you may find that you want to change your preference of one Alternative Process Operation in favor of
another: being able to change the preference setting allows you to adopt the solution that is best fit to satisfy your
production needs.
1. Operating in the Process Detail page, click the Alternative Operations tab: this displays the available
Alternative Groups for the current Process.
2. Select the Alternative Group for which you want to change the preferred Alternative Process Operation and then
click : this opens the Edit Alternative Operation Group panel.
3. From among the Alternative Process Operations displayed for the selected Alternative Group, select the one
that you want to set as your preference by clicking on the star icon next to it and then click Save.
5.7 Associating Items to Process Operations

You can create an association between the Process Operations your production process consists of and specific
resources. In this manner, you can establish the various specifications regarding which machinery, know-how and
materials are necessary to producing a specific Product, as well as providing Operators with additional instructions
to help them perform their tasks, if necessary.
When a Process Operation is instantiated to create a Work Order Operation, associations are instantiated as well.
Target User

1. Click Product and Production Configuration > As Planned BOPs and Processes in the sidebar.
2. Select the Process to which the desired Process Operation belongs and click Open.
4. Select the desired Process Operation and click Open.
Available Actions
You can provide Process Operations with:
• Machines
• Materials
• Tools
• Documents
• Skills (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Interlocking Checks (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Quality Inspections
• Qualification Criteria (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Powders
• Human Resources (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
In addition, you can:
• link Material Parameters with Automation Node Instance Parameters (This functionality is not available in
• link Data Collection Parameters to Automation Node Instance Parameters (This functionality is not available in

• link Tool Definition Parameters to Automation Node Instance Parameters (This functionality is not available in
• link Setpoint Variables to Automation Node Parameters (This functionality is not available in
• create Process Steps.
5.7.1 Associating Machines to Process Operations

This procedure allows you to specify where the Process Operation can be executed and which Machines can be
used to execute the Process Operation.
Target User
Procedure
1. Open the desired Process Operation and then click the Machines tab.
2. Click Create and then proceed as follows:
If the Work Operation Select one of the following options Set the following
associated with parameters
the selected Process
Operation
had the AM parameter selected Add 3D Printer, if the Process Operation • Printer, the
must be executed name of the 3D
on a specific 3D Printer. Printer.
• Print Job File,
the program the
3D Printer
requires to
determine how
to print items
tridimensionally.
(Optional, see
note below)
Add 3D Printer Type, if the Process • Printer Type,

Operation the name of the
can be executed using any 3D Printer 3D Printer Type.
belonging to a specific type. • Print Job File,
the program the
3D Printer
requires to
determine how
to print items
tridimensionally.
(Optional, see
note below)

the selected Process
Operation
Add Unit, if the Process Operation must • Unit, the name

be executed of the Machine.
had not the AM parameter
only on a specific Machine. • Part Program,
selected
the identifier of a
Part Program
that must be
downloaded to
the machine,
when the
Process
Operation is
started.
(Only if the Work
Operation
associated to
this Process
Operation had
the CNC
parameter set)
Note If the Machine is linked
to an Automation Node
Instance, you can link the
related Parameters to Data
Collections, Tool
Definitions, and Materials,
so that the values will be
automatically collected
from the field at runtime.
Add Equipment Type, if the Process Equipment Type, the

Operation Equipment Type that you
can be executed using any Machine want to select for this
belonging to a specific class. machine instance.
Add WorkCenter, if the Process WorkCenter, the name of

Operation the Workcenter.
must be executed in a specific place.

 In case of Process Operations dedicated to 3D printing, the Print Job File field can be left blank and
then set at a later time:
• in this tab, by selecting the 3D Printer or 3D Printer Type and then clicking Link Print Job
File;
• if the Print Job File is a template (that is, the Print Job File must have Product to Be
Serialized set to True and Product Serial Number Management set to Pending) and the Work
Order is either of the Serialized or Full Serialized type, you can associate it with Serial
Numbers to create one or more Runtime Print Job Files.
• at runtime, before transferring the Print Job File to the 3D Printer.
3. Click Add.
5.7.2 Associating Materials to Process Operations

This procedure allows you to define an association between a Process Operation and the Materials that it will
consume or assemble.
Target User
Procedure
1. Open the desired Process Operation and then click the Materials tab.
2. Click .
Material The Material to be consumed or assembled during the Process

Operation. If the associated Work Operation is of type Additive
Manufacturing, select a Material of type AMPowder. Upon selecting,
Material Specification Type is set to Additive in read-only mode.
Logical Position Any kind of reference about where the component must be placed or
assembled in the final product.

Material Specification Type The Specification Type to which the Material to be

consumed\assembled or produced during the Operation's execution
belongs. How you set this parameter will affect one of the following:
• The manner in which the Material in question will be
consumed, in relation to its initial quantity (input Material
Specification Types).
• The output quantity to be produced, in relation to the
Material's quantity (output Material Specification Types).
Possible values for Input Material Specification Types
• Alternative: Only one Material among those proposed
must be consumed. This Material will be consumed in full.
Note By selecting this Material Specification Type,
the Group additional parameter is displayed, allowing
you to create a logical grouping of alternative Materials.
• AsRequired: The quantity to be consumed for each
Material can range from zero to the total quantity of each
Material, meaning that the consumption of the Material in
question can span from not being consumed in any
extent to being consumed in full.
• AutoConsume: Material for which it is necessary to trace
the consumption regardless of the involved Batch or
Serial Number.
• Disassemble: Setting this Material Specification Type
affects how disassembly is performed: if a compound
Material resulting from an assembly of Materials is
successively disassembled, all those Materials set
to Normal Part with the same ID relative to the
completed Work Order Operations belonging to the same
Work Order will be disassembled (dismantled) from the
compound Material.
• NormalPart: Default value. The entire quantity of the
Material must be consumed.
• RangeParts: The portion (partial quantity) of the Material
to be consumed can range from greater than zero to the
total quantity of the Material itself.
• Reference: This Material is not directly consumed or
assembled, but is used as a reference for other activities
performed in Work Order Operations.
• SelectedFit: The total part quantity for the selected
range must be equal to the maximum quantity of one of
the parts.

• Additive: Adopted specifically for Additive Manufacturing
powders. The quantity of the Material to be consumed
can range from greater than zero to the total quantity of
the Material. The quantity can also be updated to more
than the suggested quantity from the Operator Landing
page. However, once mixed (combined), the quantity that
has been introduced can no longer be separated, either in
full or in part, from the Powder Material Batch resulting
from the execution of the Operation.
• TrackLoadedAMPowder: Adopted specifically for
Additive Manufacturing powders. The quantity of the
Powder Material consumed during a printing operation is
tracked, after the operation has been completed,
rescaling the quantity of the Powder Batch (loaded into
the 3D Printer) used to print the parts for which
consumption must be tracked.
Possible values for Output Material Specification Types
• CoProduct: To be selected when you intentionally want
more than one distinct product to be produced from the
same Material during the execution of the same
Operation. The quantity to be produced can range from
zero to the total quantity of each Material.
• ByProduct: To be selected when, in addition to a distinct
product to be produced from the same Material, during
the execution of the same Operation, there
will inevitably be also a resulting by-product (derivative)
that may or may not be further processed to produce
something else. The quantity to be produced can range
from zero to the total quantity of each Material.
 Custom Material Specification Types

System Integrators can create custom Material
Specification Types for determining Material consumption/
assembly modalities that differ from those illustrated above
and are peculiar to specific needs, focusing either on the
quantity of the Material to be consumed (input) or the
quantity of Material to be produced (output).
Group If the Material Specification Type is set to Alternative, use this

parameter to create a logical grouping of alternative Materials.
Quantity The quantity of Material to be consumed during the Process

Operation. After setting this parameter, select the proper Unit of
Measure from the drop-down list on the right. If a Material of type
AMPowder is selected, only those units that are applicable for
Powder Material batches are available in the drop-down list.

Alternative Selected If the Material Specification Type is set to Alternative, select this
check box to define which Material must be displayed by default to
the Operator among those contained in the same Group.
4. Click Add.
5.7.3 Associating Tools to Process Operations

This procedure allows you to define an association between a Process Operation and the Tools that will be used to
execute it.
Target User
Procedure
1. Open the desired Process Operation and then click the Tools tab.
2. Click Create.
Tool Definition The type of Tool to be used to perform the Process Operation.
Select one among those you have created. If the associated Work
Operation is of type Additive Manufacturing, you can also
associate a Tool Definition of type AM Substrate, indicating that
the Tool is a Substrate. It is possible to have a Process Operation
of type Additive Manufacturing, having both Substrates and
regular Tools associated with it.
Usage Number The number of times the Tool is used to perform the current
Process Operation.
4. Click Create.
5.7.4 Linking Documents to Process Operations

This procedure allows you to establish a link between a Process Operation and a set of Documents that can be
useful to the Operator who will manage the corresponding Work Order Operation at runtime. For example, it could
be useful to provide the user with an image of the involved items in order to allow him to easily identify them before
executing the Work Order Operation. Such documents, added at the engineering phase, are displayed under the
Documents tab. Additionally, if the Operator links documents to a Work Order Operation at runtime, these
documents are also displayed under the Documents tab.
In addition, to further support the Operator, you can also associate detailed Work Instructions to the Process
Operation.
Target User

Procedure
1. Open the desired Process Operation and then click the Documents tab.
2. Click Catalogs.
3. In the Operation Details screen, click the Documents tab.
4. Click Link.
 If the Link icon is not displayed, click the Process Operation in the left panel.
5. If the Document to be linked to the Process Operation is not displayed in the list, click Import and select the
file of interest.
6. Select the Document of interest from the list and click the Link button.
 If Multi-Plant Support is enabled, tags currently enabled for the logged User are applied to the imported
Documents.
5.7.5 Associating Work Instructions to Process Operations

This procedure allows you to define an association between a Process Operation and Work Instructions that are
used by Operators at runtime to get detailed instructions about how to perform specific tasks on the product.
Operators can also use Work Instructions to collect runtime data during production execution. To discriminate if a
Work Instruction is to be used for data collection or for providing instructions, the Work Instruction Steps must be
configured as Acknowledge or DataCollection type. For more information about Work Instructions, see the Work
Instruction App in the Opcenter Execution Foundation User Manual.
Work Instructions can be associated with both Process Operations and Process Steps.
When you unlink a Work Instruction, it is only unlinked from the Process Operation without impacting any related
Operation available in the Operation Catalog.
Target User
Prerequisite
A Work Instruction to be associated with the Process Operation is available.
Procedure
1. Open the desired Process Operation and then click the Work Instructions tab.
• Click Catalog and in the In the Operation Details screen, click the Work Instructions tab then click
Link Work Instruction.
• Click Link Work Instruction.

 • If you link a Work Instruction to a Process Operation working from the Operation
Catalog page, the Work Instruction will be inherited by all new Process Operations
picked from that Operation in the Catalog and by the existing Operation provided that
the Work Instruction has been propagated.
• If you link a Work Instruction directly to a specific Process Operation, only new Work
Order Operations that will be instantiated from that specific Process Operation will
inherit the linked Work Instruction.
3. In the Link Work Instruction panel, select one Work Instruction Association Type among the following
options:
Process Operation (only for Serialized, FullSerialized and FlexibleSerialized Work Orders);
to be associated.
4. Select the Work Instruction of interest and click Link.
5.7.6 Associating Skills to Process Operations

Skills are specific requirement which can be associated to Process Operations, Work Order Operations, Process
Steps and/or Work Order Steps, and which allows a more granular way to control their execution.
Target User
Prerequisite
At least one Skill has been previously created.
Procedure
1. Open the desired Process Operation and then click the Skills tab.
2. Click Catalog.
3. In the Operation Details screen, click the Skills tab.
4. Click Add.
5. In the Level edit box, type the required level of the Skill to be associated to the Process Operation.
Note According to the Enable Certification Skill Level Filter configuration key, the Level can either be the
exact or the minimum value required to authorize the Process Operation execution.
6. Select one or more Skills from the list and click Add.
 If multiple Skills are selected at the same time, they are all associated with the same Level. If you need to
associate Skills with different Levels, you need to associate them individually.

5.7.7 Linking Interlocking Checks to Process Operations

Interlocking Checks (both of Standard and Custom type) can be linked to Process Operations to verify whether one
or more conditions have been satisfied at runtime prior to starting or completing the instantiated Work Order
Operation.
If the outcome of all these checks is successful, the execution of the Work Order Operation will either be started
(Inbound Interlocking Checks satisfied) or completed (Outbound Interlocking Checks satisfied).
The following table lists the Interlocking Checks provided by default by Opcenter EX DS.
For more information, see section Interlocking Checks of the Opcenter EX DS Product Overview.
Name Description
AllPartsAssembled Verifies that all components have been assembled on the Work Order
Operation (as well as on its Work Order Steps, where present), according
to the Material Specifications or BoMs.
• For Serialized Work Orders, the check is specific to the Serial
Numbers to be completed.
• For TransferBatch Work Orders, the check is specific to the quantity
to be completed.
AllStepsAssembled Verifies that all the Steps belonging to the active Work Order Operation
have been completed.
DocumentsUploaded Verifies how many documents have been uploaded in relation to the
current Work Order Operation as a whole (that is, in relation to the Work
Order Operation and its Work Order Steps, if present). This interlocking
check is performed against the Min. doc # parameter: if the number of
uploaded Documents falls below the value set for this parameter, the
check's outcome is considered unsuccessful.
A distinction is made for the various Production Types available for Work
Orders: for details, see Role of Work Order Production Type for
the DocumentsUploaded Interlocking Check.
Target User
Prerequisite
The Interlocking Check to be linked is configured as Operation-relevant.
Procedure
1. Open the desired Process Operation and then click the Interlocking Checks tab.
2. Click Link.

3. In the Link Interlocking Check pane, select the Interlocking Check to be linked: if you have selected a standard
Interlocking Check, go to step 5.
4. (only for custom Interlocking Checks) In the Define Interlocking Check Type area, select at least one of the
following Interlocking Types:
Interlocking Type Description
Values.
6. In the Set Parameter Values pane, insert or update values for the parameters. If the parameter foresees more
values (that is, Is List is selected), it will be possible to define more than one value for the parameter.
8. Click Add.
unlinked.
5.7.7.1 Role of Work Order Production Type for the DocumentsUploaded

Interlocking Check
The Production Type of the Work Order to which the current Work Order Operation belongs plays an important role
in how the DocumentsUploaded Interlocking Check is executed and how its outcome is to be considered. In all
cases, this Interlocking Check is performed against the Min. doc # parameter.
If the Work Order Then ...

belongs to
Production
Type...
Serialized The Min. doc # parameter is checked for each of the Material Tracking Units (Serial
Numbers) that is being completed: it is sufficient that the minimum number of Documents
not be uploaded for one of the Serial Numbers for the outcome of the check to be
considered unsuccessful as a whole.
FullQuantity The Min. doc # parameter is checked on the batch of the Final Material as a whole.
FullSerialized The Min. doc # parameter is checked on the specified list of the Material Tracking Units
(Serial Numbers) that is being completed: it is sufficient that the minimum number of
Documents not be uploaded for one of the Serial Numbers for the outcome of the check to
be considered unsuccessful as a whole.

If the Work Order Then ...

belongs to
Production
Type...
TransferBatch The Min. doc # parameter is checked on the batch of the Final Material, with the possibility
of only a portion of the batch being consumed at a time. In this case, each time that a
portion of the batch is consumed, the check is performed to see whether the minimum
number of Documents has been reached: if the minimum number of Documents has been
reached at the first partial consumption of the batch, then it is not necessary for any
Document to be uploaded at the successive partial consumptions of the batch in
question. In any case, the sum of the Documents uploaded for each partial consumption of
the batch must not be less than the value set for Min. doc #.
Here are two examples for TransferBatch: we have a Batch of Final Material with initial
Batch quantity = 10 and parameter Min doc # = 10.
Example 1
First partial consumption of batch = 5 with 10 Documents uploaded
The remaining portion of batch to be consumed = 5 with 0 Documents yet to be uploaded
Second partial consumption of batch = 5 with 0 Documents uploaded
Total Documents uploaded = 10 + 0 = 10 Documents uploaded for the batch as a whole.
The outcome of the Interlocking Check is successful.

Example 2
First partial consumption of batch = 5 with 5 Documents uploaded
The remaining portion of batch to be consumed = 5 with 5 Documents yet to be uploaded
Remainder consumed as follows:

Second partial consumption of batch = 1 with 2 Documents uploaded
Third partial consumption of batch = 4 with 3 Documents uploaded
Total Documents uploaded = 5 + 2 + 3 = 10 Documents uploaded for the batch as a whole.
The outcome of the Interlocking Check is successful.
5.7.8 Linking Inspection Definitions to Process Operations

Inspection Definitions are used to configure Quality Inspections to be carried out at runtime.
They represent how a certain measurement (that is, a Quality Characteristic) has to be collected at runtime in terms
of frequency and sample size.
Measurements can be related to Attributive, Variable or Visual Characteristics.
The results of the measurements at runtime, collected for the Inspection Definitions, can be used to perform
Statistical Process Control (SPC) calculations.
Quality Inspections can also be used specifically to perform Buy-Off activities (that are, explicit approvals or
rejections of individual produced Material Tracking Units).
Finally, Quality Inspections can be configured to be executed on each piece produced (100 Percent) or
automatically triggered according to a specified interval of produced items (Part Based).

 • Part Based Quality Inspections are only supported for

Serialized, FullSerialized, FlexibleSerialized and FullQuantity production types.
• In case of Alternative Paths having more than one Work Order Operation, the Quality Inspection cannot
be associated to the first Operation of the alternative path. If the alternative path contains only one
Work Order Operation, then the Quality Inspection task must be associated to the Work Order
Operation closing the Alternative path.
Inspection Definitions are managed via the Opcenter Execution Foundation Work Instruction App.
Target User
Prerequisite
• An Inspection Definition (derived from Attributive, Variable or Visual Quality Characteristic) is available in the
system.
• (For Buy-Off only) The Inspection Definition to be linked to the Process Operation must:
• point to the Buy-Off Quality Characteristic
• have an Electronic Signature scenario configured with the users or user roles entitled to approve or
reject the produced MTUs.
• If the Work Order Operation also contains Steps, it is recommended that you link the
AllStepsCompleted Interlocking Check to avoid that the Work Order Steps are set to NotExecuted once
a Buy-Off request is accepted for the Work Order Operation.
• (For Part Based Inspections only) The Inspection Definition to be linked to the Process Operation must have the
Frequency set to Part Based.
Procedure
1. Open the desired Process Operation and then click the Quality Inspections tab.
2. Click Link.
3. Select the Inspection Definition to be associated.
4. (For Part Based Inspections only) Select a reference operation to be used by the system to recognize when to
start the inspection, according to the configured interval of produced items.
5. Click LINK.
 • If you want to unlink the linked Inspection Definition revision, click Unlink.
• You can link multiple Inspection Definitions to a Process Operation, but only one revision of the
selected Inspection Definition can be linked.
5.7.9 Associating Qualification Criteria to Process Operations

Qualification Criteria can be associated to Process Operations, so that specific rules can be applied during the
creation of the Work Order, to include and perform at runtime only those operations deemed necessary.
Procedure
1. Open the desired Process Operation and, in the Details tab, click the button visible in the right sidebar.

2. From the entity picker, select the Qualification Criteria to be associated with the Process Operation and click
Save.
 You can remove existing associations by clicking the button.
5.7.10 Associating Powders to Process Operations

This procedure allows you to specify which Powder must be loaded into the 3D Printers associated to the Process
Operation.
Target User
Users with the Product Engineer Role can perform this action.
Prerequisite
The Work Operation type must be Setup3DPrinter (which has the property Load AM Powder set to true).
Procedure
1. Open the desired Process Operation and then click the AM Powders tab.
2. Click . In the Set Powder pane, the upper area displays the list of 3D Printers associated with the Process
Operation.
3. Set the following parameters in the lower area:
Powder The Powder to be loaded into the 3D Printer. Select one

among those you have created.
Min. Quantity (Optional) The minimum quantity which must be loaded into
the 3D Printer.
Enable Mandatory Check (Optional) If this checkbox is selected, you can choose
whether to enable the mandatory check at runtime only on
the Quantity, only on the Batch or both:
• Powder Quantity: a check is performed at runtime
on the Powder Batch quantity.
• Powder Batch: a check is performed at runtime on
the Powder Batch identifier.
4. Click Set.
5.7.11 Linking Human Resources to Process Operations

Linking Human Resources to Process Operations allows you to specify how many users with specific Certifications
are required to start the execution of a specific Work Order Operation.

Once the Human Resource is linked to the Process Operation, it is possible to remove the association ( button)
or to modify the number of users that are required to possess each Certification ( button).
Target User
Prerequisite
A Certification is available in the system.
Procedure
1. Open the desired Process Operation and then click the Human Resources tab.
2. Click Link.
3. Select one or more Certifications to be associated.
4. In the Number of Users area specify, for each Certification, the number of required users.
5. Click Link.
5.7.12 Linking Material Parameters to Automation Node Instance

Parameters
Once created and associated to the Process Operation/Step, Material Parameters can be linked to Automation
Node Instance Parameters.
At runtime, the Operator will be able to decide whether to automatically retrieve the values coming from the field or
enter them manually.
The parameters that can be acquired from the field are related to the:
• Serial Number or Batch ID of the Material to be consumed.
• Quantity to be consumed.
Prerequisites
• The target machine for the Process Operation is linked to an Automation Node Instance.
• Materials have been associated to the involved Process Operation/Step.
Target User
Procedure
1. Open the Process Operation in edit mode and then click the Machines tab.
2. Select the Machine of interest and click .
3. In the Automation Node Instance Parameters page, select the parameter to be linked.
4. Click the Materials tab.
5. Click Link.
6. In the Link Node Instance Parameter to Material panel, do the following:

• select the Material from the upper pane.

• select the parameter to be linked to the selected Material from the lower pane.
7. Click Link.
5.7.13 Linking Data Collection Parameters to Automation Node Instance

Parameters
You can create and associate Data Collection Parameters to the Process Operation/Step. You can then link these
Data Collection Parameters to the Automation Node Instance Parameters. At runtime, the Operator can decide
whether to automatically retrieve the values coming from the field or enter them manually.
Prerequisites
• Data Collections have been associated to the involved Process Operation/Step.
Target User
Procedure
3. In the Automation Node Instance Parameter assigned to Machine page, select the parameter to be linked to
the Data Collection parameter and click Link.
 The same Automation Node Instance Parameter can be linked to different Data Collections.
4. Select either an Operation Data Collection parameter or a Step Data Collection parameter and click Link. The
linked parameter is listed in the Linked Data Collection Parameters section.
5. Repeat steps 2-4 to make further associations.
 To unlink the parameter from the Automation Node Instance Parameter, click the parameter and then
click Unlink.
5.7.14 Linking Tool Definition Parameters to Automation Node Instance

Parameters
Once created and associated with the Process Operation or Step, Tool Definition Parameters can be linked to the
Automation Node Instance Parameters.

At runtime, the Operator can decide whether to automatically retrieve the values coming from the field or enter
them manually.
The parameters that can be acquired from the field are related to the:
• identifier of the Tool Definition
• duration time
• usage count.
Prerequisites
• Tool Definitions have been associated with the involved Process Operation/Step.
Target User
Procedure
3. In the Automation Node Instance Parameter Association page, select the parameter to be linked.
4. Click the Tools tab.
5. Click Link.
6. In the Link Tool Definitions to Automation Node Instance Parameter page, do the following:
• select the Tool Definition from the Select Tool Definitions to Link pane.
• select the parameter to be linked to the selected Tool Definition from the Select Tool Definition
Parameter to Link pane.
7. Click Link.
 To unlink a Tool Definition Parameter from an Automation Node Instance Parameter, click the parameter
and then click Unlink.
5.7.15 Linking Setpoint Variables to Automation Node Parameters

To be properly used at runtime to transmit data to the field, the variables of Setpoint that have been previously
declared compatible with Machines and Tools, must be linked to Automation Node Parameters.
Prerequisites to use Setpoints at Runtime

Only released Setpoints will be available to be used at runtime. In addition, to properly manage Setpoints, it is
necessary that:
• the Opcenter Execution Foundation Automation Gateway and Signal Apps, and the OPCUAConnect extension
App are included in the solution.
• the Automation Gateway has been enabled while configuring Opcenter Execution Foundation.
• Automation Node Parameters have been:
• configured and approved.
• associated with Machine Definitions, Machines, Tool Definitions or Tools during their configuration.

• OnTransmitEquipmentSetPointSignalRule and OnTransmitToolSetPointSignalRule Signal Rules have been

imported, approved and deployed.
For detailed information, see the Opcenter Execution Foundation User Manual.
Target User
Linking Setpoint Variables involving Tools

1. Open the Process Operation in edit mode and then click the Tools tab.
2. Select the Tool of interest and click .
3. In the Automation Node Instance Parameters page, select the Automation Node Type Parameter from the
upper table.
4. In the Setpoint Variables tab, click .
5. Select the Setpoint of interest and then the Variable to be linked to the Automation Node Type Parameter.
6. Click Link.
 You can unlink a Setpoint variable from an Automation Node Type parameter by selecting the variable and
clicking .
Linking Setpoint Variables involving Machines

2. Select the Machine of interest and then click .
3. In the Automation Node Instance Parameters page,
4. Select the Automation Node Type Parameter from the upper table.
5. In the Setpoint Variables tab, click .
6. Select the Setpoint of interest and then the Variable to be linked to the Automation Node Type Parameter.
7. Click Link.
5.8 Creating a Process Step

If necessary, each Process Operation can be split into a set of Process Steps.
You can create a new Process Step from scratch setting its parameters one by one, or alternatively, you can select
an existing Step from the Step Catalog and link it to the current Process Operation.
After creating some Process Steps, you can define the dependencies among them.
Target User

• If you have just created and opened a Process Operation, go to step 2.
• If f you want to create a Process Step within a Process Operation that has been previously created, select
the Process Operation in the Operations tab and click Edit.
2. Click the Steps tab.

1. Create a Process Step in one of the following ways:
• From scratch
• Linking an existing Step from the Step Catalog.
Creating a Process Step from Scratch

1. In the Steps tab, click Create > Manually.
Identifier The unique identifier to be assigned to the Process Step. Once

Name The name of the Process Step.
Description Useful information about the Process Step.
Sequence A number determining the order in which the Steps included in

the same Operation will be executed.
Step Category Step Category to be assigned to the Process Step you are creating.

Step Category provided in Opcenter EX DS will be
assigned.
Electronic Signature Complete If the check box is selected, the operator credentials are validated
at the time of completing the instantiated Work Order Operation.
The validation ensures that only authorized operators complete
Estimated Duration Hours Estimated duration, in hours, of the Work Order Step execution.
Estimated Duration Minutes Estimated duration, in minutes, of the Work Order Step execution.
Estimated Duration Seconds Estimated duration, in seconds, of the Work Order Step execution.
To Be Collected Document If the check box is selected, at runtime it will be possible to

associate documents with the Work Order Step.
Linking an existing Step from the Step Catalog

Defining Dependencies between Process Steps
1. In the Steps tab, click Link Step To Operation.

2. Select the Step that you want to link to the current Process Operation.
3. Insert the required Sequence number.
4. Click Save.
5.9 Defining Dependencies between Process Steps

After defining some Process Steps, you can set the dependencies among them.
 Unlike those between Process Operations, dependencies between Process Steps can only belong to
the After End type.
Target User
Procedure
1. In the Steps tab, click Details.
2. Select the tab Dependencies.
4. In the From and To fields, set the Steps linked by the Dependency.
5. Click Save.
5.10 Associating Items to Process Steps

You can create an association between the Process Steps involved in your production process, and specific
resources. In this manner, you can establish the various specifications regarding which machinery, know-how, and
materials are necessary to produce a specific Product, as well as providing Operators with additional instructions to
help them perform their tasks, if necessary.
Target User

1. Click Product and Production Configuration > As Planned BOPs and Processes in the sidebar.
2. Select the Process to which the desired Process Step belongs and click Open.
4. Select the Process Operation to which the desired Process Step belongs and click Open.
6. Select the desired Process Step and click Open.
Available Actions
You can provide Process Steps with:
• Materials
• Tools
• Documents

Associating Items to Process Steps
5.10.1 Associating Materials to Process Steps

This procedure allows you to define an association between a Process Step and the Materials that it will consume or
assemble.
Target User
Procedure
1. Open the desired Process Step and then click the Materials tab.
2. Click .
Material The Material to be consumed or assembled during the Process Step.

If you select a Material of type Additive Manufacturing, Material
Specification Type is set to Additive in read-only mode, indicating
that this is a Powder Material.


consumed\assembled or produced during the execution of the Step
belongs. How you set this parameter will affect one of the following:
the Group additional parameter is displayed allowing you
to create a logical grouping of alternative Materials.
• AsRequired: The quantity to be consumed for each
Serial Number.
completed Steps related to the completed
Operations belonging to the same Work Order will be
disassembled (dismantled) from the compound Material.
• NormalPart: Default value. The entire quantity of the
• RangeParts: The portion (partial quantity) of the Material
to be consumed can range from greater than zero to the
total quantity of the Material itself.
• SelectedFit: The total part quantity for the selected
the parts.

from the execution of the Step.
• CoProduct: To be selected when you intentionally want
same Material during the execution of the same Step. The
quantity to be produced can range from zero to the total
quantity of each Material.
• ByProduct: To be selected when, in addition to a distinct
the execution of the same Step, there will inevitably be
also a resulting by-product (derivative) that may or may
not be further processed to produce something else. The


Quantity The Quantity of Material to be consumed during the Process Step.

After setting this parameter, select the appropriate Unit of Measure
from the drop-down list on the right. If a Material of type AMPowder
is selected, only those units that are applicable for powder batches
are available in the drop-down list.
UoM The unit of measure of the Material being linked to the Process Step.

4. Click Add.
5.10.2 Associating Tools to Process Steps

This procedure allows you to define an association between a Process Step and the Tools that will be used to
execute it.
Target User
Procedure
1. Open the desired Process Step and then click the Tools tab.
2. Click Create.
Tool Definition The type of Tool to be used to perform the Process Step. Select
one among those you have created.
Usage Number How many times the Tool must be used to perform the current
Process Step.
4. Click Create.
5.10.3 Linking Documents to Process Steps

This procedure allows you to establish a link between a Process Step and one or more Documents that can be
useful to the Operator who will manage the instantiated Work Operation Step at runtime.
For example, it could be useful to provide the user with an image of the items involved in order to allow him or her
to easily identify them before the assembly.
In addition, to further support the operator, you can also associate detailed work instructions to the Process Step.
Target User
Procedure
1. Open the desired Process Step and then click the Documents tab.
2. Click Catalog.
3. In the Step Details screen, click the Documents tab.
4. Click Link.
 If the Link icon is not displayed, click the Process Operation in the left panel.
5. If the Document to be linked to the Process Step is not displayed in the list, click the Import button
and select the file of interest.

6. Select the Document of interest from the list and click Add.
 If Multi-Plant Support is enabled, tags currently enabled for the logged User are applied to the
imported Documents.
5.10.4 Associating Work Instructions to Process Steps

This procedure allows you to define an association between a Process Step and Work Instructions that are used by
Operators at runtime to get detailed instructions about how to perform specific tasks on the product. Operators can
also use Work Instructions to collect runtime data during production execution. To discriminate if a Work
Instruction is to be used for data collection or for providing instructions, the Work Instruction Steps must be
configured as Acknowledge or DataCollection type. For more information about Work Instructions, see the Work
Instruction App in the Opcenter Execution Foundation User Manual.
Work Instructions can be associated also with Process Operations.
Target User
Prerequisite
A Work Instruction to be associated with the Process Steps is available.
Procedure
1. Open the desired Process Step and then click the Documents tab.
2. Click Catalog.
3. In the Step Details screen, click the Work Instructions tab.
4. Click Link.
5. From the Add Instruction Definition page, select the Work Instruction Association Type:
Process Operation (only for Serialized, FullSerialized and FlexibleSerialized Work Orders);
to be associated.
6. Select the form of interest from the list and click Link.
5.10.5 Associating Skills to Process Steps

Target User

Prerequisite
Procedure
1. Open the desired Process Step and then click the Skills tab.
2. Click Catalog.
3. In the Process Details screen, click the Skills tab.
4. Click Add.
exact or the minimum value required to authorize the Process Step execution.
5.10.6 Linking Interlocking Checks to Process Steps

Interlocking Checks (both of Standard and Custom type) can be linked to Process Steps to verify whether one or
more conditions have been satisfied at runtime prior to starting or completing the instantiated Work Order Step.
If the outcome of all these checks is successful, the execution of the Work Order Step will either be started
For more information, see section Interlocking Checks of the Opcenter Execution Discrete Product Overview.
Name Description
Step, according to the Material Specifications or BoMs.
• For TransferBatch Work Orders, the check is specific to the
quantity to be completed.
AllStepsCompleted Verifies that all the Steps belonging to the active Work Order
Operation have been completed.

Name Description
current Work Order Step. This Interlocking Check is performed against
the Min. doc # parameter: if the number of uploaded Documents falls
below the value set for this parameter, the check's outcome is
considered unsuccessful.
A distinction is made for the various Production Types available for
Work Orders: for details, see Role of Work Order Production Type for
Target User
Prerequisite
The Interlocking Check to be linked is configured as Step-relevant.
Procedure
1. Open the desired Process Step and then click the Interlocking Checks tab.
2. Click Link.
3. In the Add Interlocking Check page, select the Interlocking Check to be linked: if you have selected a standard
4. (Only for custom Interlocking Checks) Define at least one of the following Interlocking Types:
INBOUND If this check box is selected, the custom Interlocking Check will
OUTBOUND If this check box is selected, the custom Interlocking Check will
5. In the Associated Interlocking Check Parameters pane, select a parameter and then click Set Parameter
Values.
8. Click Add.
unlinked.
5.10.7 Linking Inspection Definitions to Process Steps


Measurements can be related to Attributive, Variable or Visual Quality Characteristics.
Target User
Prerequisite
system.
• (For Buy-Off only) The Inspection Definition to be linked to the Process Step must:
Procedure
1. Open the desired Process Step and then click the Quality Inspections tab.
2. Click Link.
3. Select the Inspection Definition to be associated and click LINK.
• You can link multiple Inspection Definitions to a Process Step, but only one revision of the
5.10.8 Linking Human Resources to Process Steps

Linking Human Resources to Process Steps allows you to specify how many users with specific Certifications are
required to start the execution of a specific Work Order Step.
Once the Human Resource is linked to the Process Operation, it is possible to remove the association ( button)
or to modify the number of users that are required to possess each Certification ( button).
Target User
Prerequisite

Procedure
1. Open the desired Process Step and then click the Human Resources tab.
2. Click Link.
5. Click Link.

How to Configure and Manage Output Messages
Creating Output Message Destinations
6 How to Configure and Manage Output Messages

Output Messages can be used to send information related to Work Orders and Work Order Operations.
Messages in the standard XML format can be downloaded from the Work Orders page or for the selected Work
Order Operation from the Operations tab, depending on the level of information required.
For each Output Message, you must configure the following items:
• Destination, which is used to properly route the message, both to internal and external systems.
• Definitions, to properly configure the structure of the Output Message that will be generated and sent.
• Sections, containing information related to the different production entities, and which can be enabled or not
for each Definition.
Target User
Users with the following roles can perform this procedure:
• Users with the Production Coordinator or Product Engineer role can perform this action.
Workflow
1. Create Output Message Destinations
2. Create Output Message Definitions.
3. Configure Output Message Sections.
6.1 Creating Output Message Destinations

Output Message Destinations must be configured to properly route the Message to internal or, in case of integration
with Opcenter Connect MOM, external systems.
For additional information on how to send Output Messages to external destinations, refer to the How to Send
Output Messages to Opcenter Connect MOM section in the Opcenter Execution Discrete Installation and Configuration
Guide.
From the Output Message Destinations page you can:
• create new Output Message Destinations,
• modify Output Message Destinations that have been previously created, except for their Id
• delete Output Message Destinations that are no more required.
 If a Message Destination is already associated with a Message Definition, it cannot be deleted.

To access the Output Message Destinations page, click Product and Production Configuration > Output
Message Destinations in the sidebar.
Procedure
1. In the Output Message Destinations page, click the button.

Creating Output Message Definitions
Identifier The unique identifier of the Output Message Destination.
Name (Optional) The unique user-friendly name to be used to identify

the Output Message Destination.
Description (Optional) Useful additional information on the Output Message

Destination.
Use Message Broker By selecting this flag, the Output Message will be sent to an
external destination using Opcenter Connect MOM .
Broker Message Type Available only if you have flagged the Use Message Broker check
box. The Message Type should be the same Message Type that
will be used by Opcenter Connect MOM, in case of external
destinations. This field must be specified, otherwise the Message
will not be recognized.
Broker Adapter Name Available only if you have flagged the Use Message Broker check
box. The Adapter Name should be the same Adapter Name that
will be used by Opcenter Connect MOM, in case of external
destinations. This field must be specified, otherwise the Message
will not be recognized.
3. Click Save.
6.2 Creating Output Message Definitions

Output Message Definitions enable you to configure the following parameters for each Output Message:
• Message Type
• Message Destination, to be used to properly route the Message to internal or, in case of integration
with Opcenter Connect MOM, external systems.
From the Output Message Definitions page you can:
• create new Output Message Definitions.
• modify Output Message Definitions previously created (except for the Id).
• delete Output Message Definitions that are no more necessary.
• release Output Message Definitions. Output Messages can be sent only when the associated Message Definition
is released.
• enable or disable the optional Sections for each Output Message Definition, provided that the Output Message
Definition is not released.
 If an Output Message Definition is released it cannot be deleted.

Configuring Output Message Sections
To access the Output Message Destinations page, click Product and Production Configuration > Output
Message Destinations in the sidebar.
Prerequisites
You have created an Output Message Destination.
Procedure
1. In the Output Message Definitions page, click the button.
Identifier (Mandatory) Unique identifier of the Output Message Definition.
Use Default Revision If this check box is selected, the Output Message Definition will
be created using the default Revision.
Revision The Revision (version) to be associated with the Output Message

Definition. If you have flagged Use Default Revision, this field
will be disabled.
Name The name to be assigned to the Output Message Definition.
Description Useful additional information on the Output Message Definition.
Message Type (Mandatory) Represents the type of Output Message. Possible

Values are:
• Work Order Output Message
• WO Operation Output Message
Destination Identifier (Mandatory) The Destination to be associated with the Output

Message.
Advanced Settings Clicking on this section, a field is displayed, where you can select
the Numbering Pattern provided by default for the Message
Type ID. If you don't specify a Numbering Pattern, the default
one WorkOrder-OutputMessage will be used.
3. Click Save.
6.3 Configuring Output Message Sections

Output Message Sections can be enabled according to the type of Message you intend to use. They contain
information on the production entity to which they refer.
The product releases a set of predefined Sections, but additional Sections can be configured according to your
production needs.
Some Sections are mandatory, while others are optional and you can decide not to configure them. In the detail the
Sections are:

Configuring Output Message Sections
• Work Order Section (Mandatory)

• Material
• Tool
• Skill
• Human Resources
• Users
For additional information on Output Message Sections and what they contain, refer to the Output Messages page
in the Opcenter Execution Discrete Product Overview.
In addition to the standard Output Message Sections, custom Message Sections can also be configured. For
additional information on how to configure custom Output Message Sections, refer to the Custom Output Message
Sections page in the Opcenter Execution Discrete Extensibility Guide.
Procedure
1. In the Output Message Definitions page, select an Output Message Definition and click
2. Click the Sections tab.
3. Flag one or more Sections to be associated with the Output Message Definition according to your needs, and
click the button. A confirmation message appears, click Yes.
 • To disable one or more Sections, remove the flag from the Sections you want to disable, and click the
button.
• Mandatory Sections cannot be disabled.

How to Prepare Production Execution
How to Create and Prepare Material Tracking Units
7 How to Prepare Production Execution

Production execution requires that some groundwork be done: you will need to create and prepare certain runtime
entities (some of which differ, if Additive Manufacturing is involved, for example) and your Work Orders first.
Workflow
1. Create the following Runtime entities used in production execution:
• Powder Material Batches (specific to Additive Manufacturing)
• Tools
• Substrates (specific to Additive Manufacturing)
• Buffers (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Containers (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.).
2. Create and prepare Work Orders.
3. (Optional) Create and prepare Execution Groups.
7.1 How to Create and Prepare Material Tracking Units

To properly start production execution, you must instantiate the Material Tracking Units (MTUs) consumed or
produced during the Work Order's execution. MTUs are created from their abstract representations (Materials)
defined while configuring the production environment.
 Opcenter Execution Discrete extends the Material Tracking Units configuration functionality provided
by Opcenter Execution Foundation, tailoring it to the Discrete production processes. As some of the
operations required to configure general Material Tracking Units are not relevant or applicable in the
Discrete context, the current documentation only provides information on steps necessary for the
configuration of Discrete MTUs. Only involved parameters, buttons and tabs are mentioned.
Once you have created an MTU, it is possible to associate one or more Documents to it to provide the Operator with
additional relevant information during both engineering and runtime.
If the required Material Tracking Units involved in the production process are insufficient (and therefore, must be
replenished) or not in condition (and thus must be replaced) to permit the continuation of manufacturing activities,
users can manage buffer replenishment and transport operations within the Plant by declaring a specific Logistic
Request.
If anomalies or defects are discovered on existing Material Tracking Units, it is possible to declare Quality Non-
Conformances on them, either by an Operator at runtime or by a Production Coordinator.
Target User
Users with either the Production Coordinator or Product Engineer role can perform this operation.
Workflow
1. Create a Material Tracking Unit.
2. (Optional) Link one or more Documents to the MTU.
Creating a Material Tracking Unit

1. Click the Material Tracking Units tile in the home page.
2. In the Material Tracking Units page, click .

Id The unique identifier assigned to the Material Tracking Unit. Once the Material Tracking
Unit is created, the Id value cannot be modified.
Name (Optional) The name assigned to the Material Tracking Unit.
Code Type (Optional) The type of Code assigned to the Material Tracking Unit. The possible values are:
• Batch Id: identifies a batch object,
• Serial Number Code: identifies a serializable object.
Code The Batch Id or Serial Number assigned to the Material Tracking Unit.
Description (Optional) Additional information on the Material Tracking Unit.
Material (Optional) The Material you want to associate with the Material Tracking Unit.
Material (Optional) The Material revision associated with the Material Tracking Unit. If you have
Revision selected Use Current Revision, this field will be disabled.
Material (Optional) This field is already selected when a specific Material revision is chosen and only
Unique one Unique identifier exists; otherwise, a Unique identifier must be selected in the list of the
Identifier available ones. If you have selected Use Current Revision, this field will be disabled.
Use Current If selected, the Material Tracking Unit will be created using the current Material revision.
Revision
Unit of (Optional) The Unit of Measure you want to associate with the Material Tracking Unit.
Measure
Value (Optional) The Unit of Measure value. If a Unit of Measure has been selected, the value must
be inserted.
State (Optional) The State Machine associated with the Material Tracking Unit.
Machine
Equipment The Equipment you want to associate with the Material Tracking Unit.
Weight Unit Unit of Measure related to the weight of the Material Tracking Unit.
of Measure
Weight Value indicating the unitary weight of the Material Tracking Unit. For example, for a Material
Value Tracking Unit with UoM= unit , the weight is related to a single unit; if UoM = m , the weight is
related to one m.
Volume Unit of Measure related to the volume of the Material Tracking Unit.
Unit of
Measure

Volume Value indicating the unitary volume of the Material Tracking Unit. For example, for a Material
Value Tracking Unit with UoM= unit , the volume is related to a single unit; if UoM = m , the volume
is related to one m.
4. Click Create.
Linking Documents with a Material Tracking Unit

1. In the Material Tracking Units page, select a Material Tracking Unit and click Open.
3. Click Link.
4. If the Document to be linked is not displayed in the list, click Import and then browse the file of interest.
5. Select the Document and then click Link.
Result
The MTU is created. At this point, if necessary, you can:
• Split a Material Tracking Unit.
• Change a Material Tracking Unit Code.
• Add the MTU to one or more Buffers, operating from the Buffers page: as a consequence, the Buffer tab will be
populated.
You can trace activities such as creation and modification that are performed on MTUs. To do this, open an MTU of
your interest, and click the History tab. Any Material Traceability activities can be viewed by clicking the
Traceability History tab.
 Material Tracking Units and Results

If Result management and Result Strategy management have been enabled, operating within the Results
tab, it is possible to view the Results declared for the selected MTU being produced, as well as their history.
For more information, see Viewing and Amending the Results of a Material Tracking Unit.
7.1.1 Splitting Material Tracking Units

Batch-type Material Tracking Units can be split into smaller quantities before being consumed during production
execution. These smaller quantities can then be used by different Work Orders.
The split can be performed by indicating a specific target quantity to be applied to a single new Material Tracking
Unit.
 Effects of a Split on Entities related to Material Tracking Units

• When a split involving a Material Tracking Unit to which one or more Documents have been associated
is performed, the same Documents will be automatically associated to the resulting Batches.
• When a Material Tracking Unit is totally split, it will be automatically removed from the Buffer
containing it. The resulting target MTUs will be automatically placed in the same Buffer that contained
the source MTU from which they were split.

Prerequisite
• The Material Tracking Unit to be split is not in Scrap status.
• No Non-Conformances are open/active on the Material Tracking Unit.
Target User
Users with Operator, Production Coordinator or Product Engineer role can perform this action.
Procedure
1. In the Material Tracking Units page, select the Material Tracking Unit to be split and click Open.
2. Click Split Material Tracking Unit.
3. In the Split Material Batch panel, set the following parameters and click Preview:
Split Type The criteria to be used to split the Material Tracking Unit. Set by
default to Partial: a new Material Tracking Unit is created with
the specified quantity and the system automatically creates
another Material Tracking Unit having the remaining quantity.
Quantity to be used for Split Indicates the value by which the Material Tracking Unit will be
split.
UoM Unit of Measure to be used for the target Material Tracking Unit .
Note The Unit of Measure must belong to the same Unit of
Measure family of the parent one.
4. Click Split.
Result
The resulting Material Tracking Unit is displayed in the Material Tracking Units page and can be:
• consumed
• assembled
• recycled, in case of Powder Material Batches.
 These actions are no longer possible for the parent Material Tracking Unit.
7.1.2 Changing Material Tracking Unit Codes

You can automatically regenerate the Batch ID or Serial Number assigned to a Material Tracking Unit, starting from
the template associated with the related Material.
Prerequisite
An Identifier template has been created and associated with the Material.
Procedure

Creating Powder Material Batches
1. In the Material Tracking Units tab, select the Material Tracking Unit of interest.
2. Click the Generate and Associate button: the system automatically sets the Code field to the newly
generated value.
7.2 Creating Powder Material Batches

Powder Material Batches are a special type of Material Tracking Units specific to Additive Manufacturing. They
represent the raw material to be used for a 3D printing operation and are instantiated from a special type of
Material known as Powder Material.
Powder Material Batches are configured through a dedicated page called Powder Batches, that while displayed in
Table mode, shows for all configured items the Is Invalid parameter: if the check box is selected, it indicates that
there are misalignments between the Powder Batch and its corresponding Material Tracking Unit.
If necessary, when editing Powder Material Batches ( button), it is possible to select the Estimated Quantity
checkbox, to indicate that the Quantity value is an estimation (for example because, since the Batch creation, other
actions have been performed, such as mixing). Therefore, before performing further actions on the Batch, its exact
quantity must be verified by weighing it. A dedicated indicator ( ) is visible in the Batch's tile to show that the
checkbox has been selected and thus the quantity must be verified.
Powder Batches can be managed also from the: Powder Genealogy, Powder Batch Mixing, Powder Recycle and 3D
Printers pages.
As other batch-type MTUs, existing Powder Material Batches can be split into smaller batches or, conversely, mixed
to create greater ones.
 In certain contexts (for example, when recycling Powder Material Batches), you can force a Powder
Material batch to transition to any state, even if contrary to what is standard behavior regarding its
lifecycle.
Target User
Procedure
1. In the Powder Batches page, click .
Identifier Unique identifier to be assigned to the Powder Batch. Once saved,

Name (Optional) Name to be assigned to the Powder Batch.
Description (Optional) Useful additional information on the Powder Batch.
Code Batch ID to be assigned to the Powder Batch.
Unit of Measure (Optional) Unit of Measure to be assigned to the Powder Batch.

Creating Tools
Quantity (Optional) Value indicating the quantity of the Powder Batch.
Powder Identifier Powder Material to be associated with the Powder Batch.
Recycle Count (Optional) The actual number of times that the Powder Batch is
recycled.
Max. Recycle Count (Optional) Maximum number of times a Powder Batch can be
recycled.
The first time a powder batch is created, its Recycle Count is set to
zero. Thereafter, following each recycle, this value is incremented.
If the incremented value becomes greater than the Max. Recycle
Count, the status of the powder batch is set to Spent, and the
powder batch is not available for production. The value of this
parameter is inherited from its corresponding Powder, but can be
superseded, if necessary.
Min. Quantity UoM (Optional) Identifier of the minimum quantity Unit of Measure.
Min. Quantity (Optional) Minimum quantity allowed for the Powder Batch.
If the powder batch quantity falls below this value, the status of the
powder batch is set to Quarantine, and the powder batch is not
available for production. The value of this parameter is inherited
from its corresponding Powder, but can be overridden, if necessary.
3. Click Add.
Result
The Powder Batch is created. You can trace activities that are performed on Powder Batches (for example their
creation or a change of status) by opening a Powder Batch of your interest and clicking the History tab. The details
include: the user who performed the action, the date and time when the action was performed, information on the
mixed quantity, on the quantity lost during mixing and on the recycle count.
7.3 Creating Tools

Tools are equipment used to transform raw material into final items during the execution of a Work Order
Operation.
Depending on your needs, thanks to appropriate configuration of their respective Tool Definitions, you can create
two types of Tools:
• generic tools (Tools),
• specialized tools used in conjunction with 3D printers in Additive Manufacturing (Substrates).
The procedure for creating Tools in general is described below: for information on setting parameters for
Substrates, see Creating Substrates.
Both Tools and Substrates are instantiated from the Tools page.

Creating Tools
You can associate previously configured Automation Node Instances to the Tools, in order to automatically acquire
the data of the Tool to be used at runtime. This operation is mandatory if you want to use Setpoints, unless
Automation Node Types have been already associated with the related Tool Definition. For detailed information
on Automation Node Instances, see the Opcenter Execution Foundation User Manual.

To access the Tools page, click Shopfloor Execution > Tools in the sidebar.
Target User
Procedure
1. In the Tools page, click Create.
Identifier Unique identifier to be assigned to the Tool. Once saved,

Name Name of the Tool.
Description Useful information about the Tool.
Tool Definition The Tool Definition to be instantiated to configure the Tool.

Either select an option from the list or create a new Tool
Definition, by clicking and inserting the required
parameters for the Tool Definition that you want to create.
Lockable If this check box is selected, the Tool will be locked when
used in a Work Order Operation, thereby making it
unavailable for concurrent use elsewhere.
For more information, see Locked Tools.
Max. Usage Counter The maximum number of times a Tool can be used. Each
time a Tool is used, the Usage Counter value is incremented
by 1. If the Usage Counter value becomes greater or equal
than the maximum allowed times a Tool can be used, the
Tool's status is set to OnHold, and it is no longer available
for production.
Max. Duration Time (days, hours, minutes, The maximum duration for which a Tool can be used. The
seconds) system monitors the duration of Tool usage. If the usage
duration exceeds this value, the Tool's status is set to
OnHold, and it is no longer available for production.

Creating Tools
Expiration Date The expiration date and time of a Tool. Upon reaching this
date, the system sets the Tool's status to OnHold, and it is
no longer available for production.
3. (Only if you have selected a Tool Definition of the AM Substrate type to create a Substrate) Set the parameters
specific to Substrates.
4. Click Create.
Operations Available for Both Tools and Substrates

Regardless of whether you are creating a generic Tool or Substrate, you can:
• update Tools and Substrates, using the Edit button to modify their details, such as its name and
description.
• delete Tools and Substrates, using the Delete button, provided that they are currently not in use.
• perform maintenance activities on the Tool, using the Tool Maintenance button and update the usage
counter, locked status, usage duration and the expiration date.
• declare Non-Conformances of type Quality on Tools, using the Add Defects button, if anomalies or defects
are discovered on existing Tools either by an Operator at runtime or by a Production Coordinator.
Locked Tools
Tools that have been locked cannot be edited, except in the case in which tool maintenance is required. Once a
specific Tool is locked, it can be used only on the same Work Order Operation, by the same User and on the same
machine.
However, in serialized production, it can be used to produce different Serial Numbers, provided they belong to the
same Work Order Operation. Also, a locked Tool is automatically unlocked whenever the user completes or pauses
the execution of the Serial Number for which the locked Tool is being used or upon completing the related Work
Order Step.
Associating Automation Node Instances to Tools
1. In the Tools page, select the Tool to be associated with one or more Automation Node Instances and click
Open.
2. In the Automation Node Instances tab, click .
Select the items to be added and click Save.
 To unlink the Automation Node Instance from the Tool , select the association and then click .
Displaying Compatible Setpoints

Creating Substrates
Perform the following operations to access the list of Setpoints declared compatible with a Tool:
1. In the Tools page, select the Tool of interest and click Open.
2. Click the Setpoints tab.
7.4 Creating Substrates

In addition to generic Tools, Opcenter Execution Discrete supports a special type of Tool specific to Additive
Manufacturing known as a Substrate. Substrates are build plates that are used in conjunction with 3D printers to
build tri-dimensional final items.
Your starting point remains the procedure for instantiating a Tool, but you must set additional parameters if the
Tool you are creating is to be used as a Substrate. These extra parameters include minimum thickness, maximum
treatment count allowed, current thickness, and so forth.
In addition, you must associate the Substrate with 3D printers, if this association has not already been defined
previously (that is, when the Tool Definition used as the basis for creating the Substrate was configured).
Substrates are created solely from the Tools page, but can be managed from the Substrates page.
If anomalies or defects are discovered on existing Substrates, it is possible to declare Non-Conformances of
type Quality on them, either by an Operator at runtime or by a Production Coordinator.
Target User
Procedure
1. Click Shopfloor Execution > Tools in the sidebar.
2. In the Tools page, click Create.
3. Set the general parameters as described in Creating Tools, taking care to select a Tool Definition of
the Substrate type.
4. Set the following additional parameters specific to Substrates:
Current Thickness The current thickness value of the Substrate.
Min. Thickness Warning The minimum thickness that a Substrate must have. If the current
thickness of a Substrate falls below this value, the status of the
Substrate is set to Warning Available. The Substrate is still
available for production, but with a warning.
Min. Thickness Hold If the minimum thickness value is less than this Min Thickness Hold
value, the Substrate can no longer be used in production, and its
status is set to OnHold.
Automatic Thickness Decrease Selecting this check box indicates that you can reduce the
thickness of the Substrate by using the one-step Substrate
thickness reduction option. If you do not select this check box, the
Substrate's thickness must be set manually. For more information,
see Performing Substrate Treatment.

How to Create and Prepare Buffers
Amount Set for Automatic Thickness If you have decided to reduce the Substrate thickness in automatic
Decrease mode (Automatic Thickness Decrease), this value represents the
thickness by which the Substrate must be reduced each time. For
more information, see Performing Substrate Treatment.
Max. Treatment Count Warning The maximum number of treatments that a Substrate can undergo
without a warning. If the current treatment count rises above this
value, the Substrate's status is set to Warning Available, but is still
Max. Treatment Count Hold If the number of treatments that a Substrate undergoes continues
to rise above Max. Treatment Count Warning, the Max.
Treatment Count Hold value represents the maximum number of
treatments this Substrate can continue to undergo until the
Substrate will no longer be available for production. If the current
treatment count rises above this value, the Substrate's status is set
to OnHold, and it is no longer available for production. This value
is always greater than Max. Treatment Count Warning.
5. Click Save.
Associating a Substrate with 3D Printers
 If the Tool Definition you selected was associated with compatible machines, the newly-created Substrate
inherits this association. However, you can associate or remove some 3D printers, provided that the status
of the Substrate is Available or Warning Available.
1. In the Tools page, select the Substrate that you want to associate with 3D printers.
2. Click Open.
3. Click the Compatible Machines tab.
4. Click Add.
5. From the list of 3D printers, select the 3D printers that you want to associate with this Substrate, and click Add.
7.5 How to Create and Prepare Buffers

A Buffer is an actual area or accessory allocated to store Material Tracking Units either for storage and/or transport.
Target User
Users with the Production Coordinator role can perform this operation.
Prerequisites
At least one Buffer Definition has been created and set to Valid.

How to Create and Prepare Buffers

To access the Buffers page, click Shopfloor Execution > Buffers in the sidebar.
Workflow
1. Create a Buffer.
2. Change the status of the Buffer.
3. Add Material Tracking Units to the Buffer.
Creating Buffers
1. In the Buffers page, click Create Buffer.
Identifier Unique identifier to be assigned to the Buffer. Once saved, this

Name Name of the Buffer.
Description Useful information about the Buffer.
Status Current state of the Buffer. Select one of the following status:
• In Work: The Buffer is created but not ready to be
used.
• Released: The Buffer is ready to be used. You can then
add MTUs to the Buffer.
• Invalid: The Buffer is no longer required.
Buffer Definition The Buffer Definition to be instantiated to configure the Buffer.

Select an option from the list.
Workcenter/Machine The Workcenter or Machine where the Buffer is located.
Valid From Date and time from when the Buffer is valid.
Valid To Date and time until when the buffer is valid. After this date, the
Buffer is no longer available.
3. Click Create.
Changing the Buffer Status

1. In the Buffers page, select the Buffer for which you want to change the status, and click Change Buffer Status
.
2. Select the status of interest from the list.
3. Click Save.

How to Create and Prepare Containers
Adding Material Tracking Units to the Buffer

Adding MTUs to the Buffers depends on the configuration of the Buffer Definition for that Buffer. Each buffer can
hold only those specific MTUs belonging to certain Materials and/or Logistic Classes which have been added to the
Buffer Definitions.
1. In the Buffers page, select the Buffer for which you want to add Material Tracking Units, and then click .
2. Click the Material tab, and then click Link Materials.
3. Select the Material Tracking Unit, and then click Add.
 While the MTU is added to the Buffer, an error is displayed if the value of the MTU:
• exceeds the maximum value mentioned in the Buffer Definition.
• is less than the minimum value mentioned in the Material.
• is more than the maximum value mentioned in the Material.
 The Material tab displays the Material Tracking Units currently added to the Buffer. In the Buffer tab of
the Shopfloor Execution > Material Tracking Units page, you can display the Buffer to which a
Material Tracking Unit belongs.
7.6 How to Create and Prepare Containers

In Opcenter Execution Discrete, Material Tracking Unit Aggregates can be configured as Containers, and like MTUAs
can also store Material Tracking Units (both to be consumed and produced MTUs).
 Opcenter Execution Foundation provides the possibility to configure Material Tracking Unit Aggregates,
and Opcenter Execution Discrete extends this functionality allowing you to define Containers as specific
types of Material Tracking Unit Aggregates. As some of the operations required to configure general
Material Tracking Unit Aggregates are not relevant or applicable in the Discrete context, the current
documentation only provides information on steps necessary for the configuration of Discrete Containers.
Only involved parameters, buttons and tabs are mentioned.
For information on the functionalities provided by Opcenter Execution Foundation, refer to the Material App
documentation in the Opcenter EX FN User Manual.
Materials can either be associated to a Container, when a Container is created from scratch or can be inherited from
the linked Container Type. Usually Containers are loaded at runtime, but it is also possible to pre-load them with
specific Material Tracking Units during the configuration phase.
When pre-loading the Materials:
• If compatible Materials have been defined, you can select MTUs only from those Materials.
• If compatible Materials have not been defined, you can select any MTU.
In both cases, after loading the first MTU, it will be possible to load only other MTUs that belongs to the same
Material, until the Container is fully unloaded.

Once the Containers are linked or loaded with the Material Tracking Units they are then associated to Work Orders
and executed through Work Order Operations and/or Work Order Steps. While configuring, one Container can be
associated to one Work Order only, but multiple Containers can be utilized to complete the Work Order Operation.
Containers with associated Container Types also display the documents that are linked to the Container Type.
These documents can be viewed from the Document Viewer tab.
Target User
Users with the Product Engineer and Product Coordinator role can perform this action.

To access the Material Tracking Unit Aggregates or Containers page, select the Material Tracking Unit
Aggregates and Containers tile.
Containers can be easily identified in tile mode by the icon displayed within the tile, and in grid mode by the
selected check box displayed in the Is Container column.
Workflow
1. Create a Container.
2. Define Compatible Materials.
3. (Optional) Preload the Container.
4. (Optional) Associate the Container to a Work Order.
Creating a Container
1. In the Material Tracking Unit Aggregates or Containers page, click Add Material Tracking Unit
Aggregate.
2. Set the required attributes:
Id The unique identifier that will be assigned to the Container. Once

the Container is created, this value cannot be modified.
Name (Optional) The name to be assigned to the Container.
Description (Optional) Additional information on the Container.
Equipment Set n/a if the Equipment details are unavailable.
Is Container Select this checkbox to configure the item you are creating as a
Container.
Container Type (Optional) The Container Type you want to associate to the
Container.
Is Reusable (Optional) If this checkbox is selected, the Container you are

creating can be reused at runtime after unloading.
Source Equipment (Optional) Select the Source Location of the Container.

Target Equipment (Optional) Select the Target Location of the Container.

3. Click Save.
Defining Compatible Materials

1. In the Material Tracking Unit Aggregates or Containers page, select the required Container and click
Open.
2. Select the Materials tab and click Link Material icon.
3. Set the following parameters on the Link Material panel.
Parameter Name
Compatible Material Select the Material from the list.
Max Quantity The maximum quantity of the Material that can be loaded
inside the Container.
The system displays the Materials linked to the Container Type if the Container is associated to a Container
Type. The Materials tab is auto-populated with the linked Material details. Here, additional Materials can
further be linked to the Container.
4. Click Link.
 • To remove the linked Material , select the Material and click Unlink Material. Only those
Materials without Material Tracking Units linked to a Container can be unlinked from the
Container.
• The specified Maximum Quantity value of a compatible material can also be edited using the
Edit Max Quantity icon.
Click the Link Material icon again, to link more compatible Materials.
Pre-loading the Container

1. In the Material Tracking Unit Aggregates or Containers page, select the required Container and click
Open.
2. Select the Material Tracking Units tab and click the Link Material Tracking Unit icon.
3. Select one or more Material Tracking Units to be consumed or produced and click Link.
 • The icon indicates that the Material Tracking Units to be consumed or produced are valid
for the Work Order to which the Container is associated.
• To remove the linked Material Tracking Units, select the Material Tracking Units and click
Unlink Material Tracking Unit.
• If a Container is not associated to a Container Type, the Materials tab is empty, and Materials
(and subsequently, MTUs) can be linked using the Link icon. If additional MTUs are
required to be linked, only those MTUs associated to Material that was already linked can be
linked here.

How to Create and Prepare Work Orders for Production Execution
7.6.1 Associating the Container to a Work Order

1. In the Material Tracking Unit Aggregates or Containers page, select the required Container and click to
open the Material Tracking Unit Aggregates or Containers page.
2. In the Overview tab, click the Associate Container to Work Order icon and select the desired Work Order
from the Associate Container to Work Order panel.
 • Only one Work Order can be associated to a Container. To unlink the associated Work Order,
click Unlink.
• Containers cannot be associated to a Work Order that is in the Aborted, Completed, Verified or
Scrapped status
Actions performed on a Container such as creation of the Container, loading, unloading, transitions through the
states, etc. can be traced from the History tab. Open the Container of your interest, and click the History tab.
Additionally, the activity history of Containers associated to Work Orders is logged in the As Built report of the
Work Order. Select the Work Order of interest and click As Built Order.
7.7 How to Create and Prepare Work Orders for Production

Execution
The starting point in the execution of the production process is the creation and configuration of the Work Orders
including the Operations to be performed to produce the final product. After a Work Order is configured or updated,
it must be released for production in order to become effective. If necessary, released Work Orders can then be split
into sub-parts.

To access the Work Orders page, click Production Coordination > Work Orders in the sidebar.
Workflow
1. Create a Work Order.
2. Complete the Work Order Configuration.
3. (Optional) Schedule a Work Order.
4. Release a Work Order.
5. (Optional and only for Additive Manufacturing) Pre-Transfer Print Job Files.
At the end of this workflow, the Work Order is ready to be executed.
• Edit a released Work Order.
• Split a Work Order.
• Perform pre-kitting for Work Orders.
7.7.1 Creating a Work Order

You can create a Work Order:
• from a Process: typically done for standard manufacturing operations;

• manually: especially useful in the case of one-shot productions or exceptions;

• from an As Planned BOP: this operation typically creates several Work Orders at the same time, related to the
same engineering activity;
• creating a Work Order Header and then merging it with a Process: especially useful to track production requests
from an ERP system. (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• creating a Work Order from a Master Plan: creates Work Orders based on the structure defined in the Master
Plan.
• from a Master Plan with Qualification Criteria: creates Work Orders only with the operations deemed necessary,
applying Qualification Criteria rules. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)
 Inheritance of Data Segregation tags

Regardless of which of the aforementioned cases is adopted for Work Order creation, if Data Segregation
tags have been associated to the user creating the Work Orders to permit Multi-Plant support, the
generated Work Orders will inherit solely those tags that he has selected (among those tags that are
associated to him) via the Associated Tags pop-up provided via the Segregation Tags button on the
header bar.
In runtime, on the basis of the Data Segregation tags selected in the Associated Tags pop-up by the user,
the content displayed in the Work Orders page, as well as in the Operator Landing Page, will vary. In
detail:
• The Work Orders page will display only those Work Order instances created with the same Data
Segregation tags as those currently selected by the user.
• The Operator Landing Page will display only those Work Order Operation instances that belong to
Work Orders created with the same Data Segregation tags as those currently selected by the user.
 Inheritance involving Alternative Groups

Alternative Groups of a Parent Process will be inherited when you create a Work Order:
• from a Process that contains Alternative Groups of Process Operations.
• from an As Planned BOP that contains Processes with Alternative Groups.
• by first creating a Work Order Header and then merging it with a Process containing Alternative
Groups.
Target User
 A Work Order can be deleted selecting it and clicking Delete. A Work Order cannot be deleted if it
contains Work Order Operations with dependencies towards Work Order Operations either in state Open
or Future Hold belonging to another Work Order.
7.7.1.1 Creating a Work Order from a Process

This procedure allows you to create a Work Order from a Process previously created.
When you use a Process to create the Work Order, the Material is inherited by the Work Order: the system does not
allow you to create a new Material at this time.
The Work Order is created in status Edit.

Target User
Users with the Production Coordinator role can perform this action.
Prerequisite
You must have created at least one Process.
Procedure
1. In the Work Orders page, click Create > From Process.
2. In the As Planned BOP field, insert the Baseline Identifier of the As Planned BOP containing the source Process.
You can either type it directly or click and select the As Planned BOP from the list.
Process The Process with which you want to associate the Work Order. This
field is displayed only if there are multiple sub-processes inside the
As Planned BOP otherwise, the Root Process is automatically
selected.
Identifier Unique identifier of the Work Order. Either type it manually or click
the Generate button to automatically create it according to a
predefined template.
Production Type (Appears only after selecting a Process)

• Serialized - Indicates that at the time of Work Order
creation, serial numbers representing the number of
items that the Work Order is expected to produce, must
be associated with the Work Order. Available only if the
selected Process produces serialized Materials.
• FullQuantity - Indicates that the next Work Order
Operation can start only after the entire quantity of the
previous Work Order Operation has been produced.
• FullSerialized - Indicates that the Work Order will
produce multiple Material Tracking Units of the same
type, and each of them will be assigned with a serial
number. Available only if the selected Process produces
serialized Materials.
• TransferBatch - Indicates that the next Work Order
Operation can start after a portion of the entire material
batch is completed. The remaining portion can be
moved to a successive Work Order Operation.
• FlexibleBatch - Indicates that the Work Order created is
a flexible batch and the user can modify the quantity to
be produced based on the plant conditions (status of the
equipment, end of shifts, and so on).
• FlexibleSerialized - Indicates that the Work Order is
created stepwise and is flexible. The user can modify the
quantity to be produced based on the plant conditions
(status of the equipment, end of shifts, and so on).

Quantity The quantity of material that the Work Order is expected to

produce.
Plant Either the Enterprise of Site where the Work Order is expected to be
executed. If the Plant had been specified during the creation of the
Process, it is inherited from the Process itself and cannot be
modified. Otherwise, the Plant must be specified at this time.
Planned Target Quantity (Only if the Production Batch is FlexibleBatch

or FlexibleSerialized) The quantity of material that the Work Order
is expected to produce.
 In the case of FlexibleSerialized, the Planned Target

Quantity is optional.
ERP Order Identifier of the related ERP order, if applicable.
Batch ID (Only if Production Type is set to FullQuantity or TransferBatch)

The unique identifier of the Material Batch that the Work Order is
expected to produce. Either type it manually or click
Priority A number identifying the order of execution of the Work Orders.
Product The Material Tracking Units that this Work Order is expected to
produce.
If the Product had been specified during the creation of the Process,
it is inherited from the Process itself, but can be edited if necessary.
You can select an existing Material and associate it with this Work
Order. In alternative, use the button to create a new Material.
For more information, see creating a Material.
Due Date The date by which the Work Order must be completed.
Estimated Start Time The date and time when the Work Order execution is expected to
start.
Estimated End Time The date and time when the Work Order execution is expected to
end.
4. Click Create.
7.7.1.2 Creating a Work Order Manually

This procedure allows you to create a Work Order manually.

When you create a Work Order manually, you need not associate it with a Process, thereby requiring a manual
association with a Material. You can use an existing Material or create a new Material for the Work Order.
Target User
Prerequisite
You must have created at least a Material.
Procedure
1. In the Work Orders page, click Create > Manually.
Identifier Unique identifier of the Work Order. Either type it manually or click
Name The name of the Work Order
Sequence A number that indicates the order in which the Work Order will be
hypothetically executed. This applies if the Work Order belongs to a
series of Work Orders that share the same ERP ID, Initial Quantity
and Material to be produced.
 Successive Work Orders of the same series may be

released for execution even if the first Work Order in the
sequence has not been completed. To prevent this
behavior, you can define dependencies between Work
Order Operations belonging to different Work Orders.
produce.

Production Type (Appears only after selecting a Product)

Operation can start only after the current Work Order
Operation including an entire material batch is
completed.
be produced based on the requirement.
batch is completed. The remaining part can be moved
to a successive Work Order Operation
creation, serial numbers codes representing the
number of items that the Work Order is expected to
produce, must be associated with the Work Order.
Available only if the property Serial Number Profile of
the selected Product is true.
number. Available only if the property Serial Number
Profile of the selected Product is true.
• FlexibleSerialized - Indicates that the Work Order
produces serialized items. After the Work Order
creation, the user can modify the quantity of the Work
Order to be produced based on the requirement.
Planned Target Quantity ( Only if the production Type is FlexibleBatch) The quantity of
material that the Work Order is expected to produce.

produce.
Plant Either the Enterprise of the Site where the Work Order is expected
to be executed.

start.

end.
Notes Additional useful information relative to the Work Order.

3. Click Create.
7.7.1.3 Creating Work Orders from an As Planned BOP

This procedure allows you to create Work Orders from an As Planned BOP (Bill of Process) previously created. The
procedure creates one Work Order per Sub-process belonging to the As Planned BOP.
Creating Work Orders from an As Planned BOP requires a detailed description of operations required to assemble or
produce a part or product (Bill of Process, also called BOP) from which the Work Orders can inherit specifications
such as Operations. Work Orders created using BOPs produce Material Tracking Units that are the resultants of one
or more Operations defined in the BOP.
Any Operation belonging to any of the Processes making up the As Planned BOP can contain Materials.
 Multi-Plant Support via Data Segregation tags

In the presence of Multi-Plant support, one Work Order will be created for each Sub-process belonging to
the As Planned BOP. However, any tags associated to the Sub-processes will be ignored, regardless of
whether they coincide or not with those selected by (or, in any case, associated to) the user.
The Work Orders are created in status Edit.
 Once created, the system automatically assigns a sequence number to the Work Order. This number
indicates the order in which the Work Order will be hypothetically executed. This applies if the Work Order
belongs to a series of Work Orders that, originating from an As Planned BOP, may share the same ERP ID,
Initial Quantity and Material to be produced.
Note Successive Work Orders of the same series may be released for execution even if the first Work Order
in the sequence has not been completed. To prevent this behavior, you can define dependencies between
Work Order Operations belonging to different Work Orders.
Target User
Prerequisites
• You must have created at least one As Planned BOP.
• The As Planned BOP must be completed.
Procedure
1. In the Work Orders page, click Create > As Planned.

As Planned BOP The As Planned BOP using which you want to create the Work Orders.
You can either type it directly or click and select the As Planned BOP
from the list. Note Only completed As Planned BOPs can be selected.
Note Depending on how the system has been configured, you can
generate Work Orders from the latest version of the As Planned BOP or
from out-of-date versions.
Production Type • Serialized - Indicates that at the time of Work Order creation,
serial numbers codes representing the number of items that
the Work Order is expected to produce, must be associated
with the Work Order.
• FullQuantity - Indicates that the next Work Order Operation
can start only after the current Work Order Operation
including an entire material batch is completed.
• FullSerialized - Indicates that the Work Order will produce
multiple Material Tracking Units of the same type, and each
of them will be assigned with a serial number.
batch is completed. The remaining portion can be moved to a
successive Work Order Operation.
• FlexibleBatch - Indicates that the Work Order created is a
flexible batch and the user can modify the quantity to be
produced based on the requirement.
• FlexibleSerialized - Indicates that the Work Order produces
serialized items. After the Work Order creation, the user can
modify the quantity of the Work Order to be produced based
on the requirement.
ERP Order Identifier of the related ERP order.
Plant Either the Enterprise or the Site where the Work Order is expected to be
executed. This field is displayed only if the Plant had not If the Plant had
been specified during the creation of the Process, it is inherited from the
Process itself and cannot be modified. Otherwise, the Plant must be
specified at this time.
3. Click Create.
7.7.1.4 Creating a Work Order from a Work Order Header
This procedure allows you to:

• create a Work Order Header, without creating Work Order Operations. This is useful, for example, to
immediately track production requests from ERP but being able to complete the details at a later time.

• merge a Work Order Header with a Process previously created. In case of integration with Teamcenter
Manufacturing, the Process will be downloaded from Teamcenter while creating the Work Order Header.
The Work Order Header is created in status Pending. It will be available for release only after the merge operation.
Target User
Prerequisite
You must have created at least one Process.
Creating a Work Order Header

1. In the Work Orders page, click Create > Header.
Identifier Unique identifier of the Work Order. Either type it manually or

click the Generate button to automatically create it according
to a predefined template.
Name The name of the Work Order.

produce.
Plant Either the Enterprise or the Site where the Work Order is
expected to be executed.
Product The material that the Work Order is expected to produce.

Production Type (Appears only after selecting a Product)

• FullQuantity - Indicates that the next operation can
start only after the current operation including an
entire material batch is completed.
• TransferBatch - Indicates that the next operation
can start after a portion of the entire material batch
is completed. The remaining part can be moved to a
subsequent operation.
creation, serial numbers codes representing the
number of items that the work order is expected to
produce, must be associated with the Work Order.
Available only if the property Serial Number
Profile of the selected Product is true.
produce multiple Material Tracking Units of the
same type, and each of them will be assigned with a
serial number. Available only if the property Serial
Number Profile of the selected Product is true.
• FlexibleBatch - Indicates that the Work Order being
created is a flexible batch and the user can modify
the quantity to be produced based on the
requirement.
• FlexibleSerialized - Indicates that the Work Order
being created will produce serialized items. After
the Work Order creation, the user can modify the
quantity of the Work Order to be produced based
on the requirement. Available only if the
property Serial Number Profile of the selected
Product is true.
Batch ID (Only if Production Type is set

to FullQuantity, TransferBatch or FlexibleBatch) The unique
identifier of the Material Batch that the Work Order is expected
to produce. Either type it manually or click
Request Teamcenter As Planned BoP (Only in case of integration with Teamcenter Manufacturing) If
resolution this check-box is selected, additional parameters must be
entered and the As Planned BOP is retrieved from Teamcenter
according to the specified Routing ID, Product ID and
Configuration Parameter.
Teamcenter Routing ID ID of the Process available in Teamcenter.
Teamcenter Target Product ID ID of the Final Material in Teamcenter.

Teamcenter Configuration Parameter String containing parameters used to uniquely identify the As
Planned BOP in Teamcenter. Example: {\\\"EffectivityUnit\\\":\
\\"1\\\",\\\"EffectivityParams\\\":[{\\\"Name\\\": \\\"ID\\\", \\
\"Value\\\": \\\"50076677\\\"}]}.
Estimated Start Time The date and time when the Work Order execution is expected
to start.
Estimated End Time The date and time when the Work Order execution is expected
to end.
Notes Additional useful information relative to the Work Order.
Priority A number identifying the order of execution of the Work

Orders.
3. Click Create.
Merging a Work Order Header with a Process

1. In the Work Orders page, select a Work Order in Pending status.
2. Click Merge.
3. In the Merge Work Order page, set the following parameters:
Process The Process which you want to merge with the Work Order Header.
If a Final Material had been specified while creating the Work Order
Header, you can select the Process only from those with the same
Final Material.
start.
end.

4. Click Merge. The Work Order is set in Edit status.
7.7.1.5 Creating a Work Order from a Master Plan

This procedure allows you to create a Work Order from a Master Plan.

When you use a Master Plan to create a Work Order, the Material to be consumed is inherited from the selected
Master Plan. The Work Order is created in status Released.
Target User
Prerequisite
• You must have created at least one completed Master Plan.
• The Unique Identifier parameter must be set for the selected Master Plan.
Procedure
1. In the Work Orders page, click Create > From Master Plan.
2. In the Master Plan step of the wizard, insert the Identifier of the Master Plan. You can either type it directly or
click and select the Master Plan from the list.
Master Plan Identifier of the Master Plan with which you want to associate the
Work Order.
Identifier Identifier of the Work Order. Either type it manually or click


Production Type (Appears only after selecting a Master Plan)

selected Master Plan produces serialized Materials.
number. Available only if the selected Master Plan
produces serialized Materials.

produce.
Master Plan, it is inherited from the Master Plan itself and cannot be
Planned Target Quantity (Only if the Production Batch

is FlexibleBatch or FlexibleSerialized) The quantity of material
that the Work Order is expected to produce.
In the case of FlexibleSerialized, the Planned Target Quantity is
optional.


produce.
If the Product had been specified during the creation of the Master
Plan, it is inherited from the Master Plan itself, but can be edited if
necessary.
start.
end.
4. Click Next.
5. In the Materials step of the wizard, select the Materials to be consumed and click the Create button.
7.7.1.6 Creating a Work Order from a Master Plan with Qualification Criteria
This procedure allows you to create a Work Order from a Master Plan applying Qualification Criteria rules, so that
operations with valid Qualification Criteria are added to the Work Order at the moment of its creation, to perform
only those operations which are deemed necessary to the correct execution of the Work Order.
More specifically, during the creation of the Work Order:
• Operations associated to valid Qualification Criteria are added to the Work Order
• Operations associated to Qualification Criteria which are not considered valid are not added to the Work Order
• Operations which have not been associated to Qualification Criteria are added to the Work Order.
If there are dependencies between Operations, if an Operation is removed, the new dependency is automatically
inherited by the Operations which precede and the Operations which follow the one that has been removed.
If no Operations associated to valid Qualification Criteria are found, the Work Order is not created.

Target User
Prerequisite
• You must have created at least one completed Master Plan.
• Qualification Criteria have been associated to Process Operations.
• To validate Qualification Criteria, the Production Resolution Common Component has been properly configured
as indicated in Configuring the Production Resolution Common Component page in the Opcenter Execution
Discrete Installation and Configuration Manual.
Procedure
1. In the Work Orders page, click Create > From Master Plan with QC.
2. In the Master Plan step of the wizard, insert the Identifier of the Master Plan. You can either type it directly or
click and select the Master Plan from the list.
Master Plan Identifier of the Master Plan with which you want to associate the
Work Order.
Identifier Identifier of the Work Order. Either type it manually or click


Production Type (Appears only after selecting a Master Plan)

number. Available only if the selected Master Plan
produces serialized Materials.
selected Master Plan produces serialized Materials.

produce.
Planned Target Quantity (Only if the Production Batch

is FlexibleBatch or FlexibleSerialized) The quantity of material
that the Work Order is expected to produce.
In the case of FlexibleSerialized, the Planned Target Quantity is
optional.
Master Plan, it is inherited from the Master Plan itself and cannot be

Batch ID (Only if Production Type is set to FullQuantity, TransferBatch or

FlexibleBatch) The unique identifier of the Material Batch that the
Work Order is expected to produce. Either type it manually or click
Priority (Optional) A number identifying the order of execution of the Work

Orders.
produce.
If the Product had been specified during the creation of the Master
Plan, it is inherited from the Master Plan itself, but can be edited if
necessary.
start.
end.
4. Click Create.
7.7.2 Completing Work Order Configuration

After creating a Work Order or a Work Order Header, you can complete and/or edit its configuration.
Once the Work Order has been configured, it will then be necessary to release it to permit its use in runtime.
 If a BoM is configured to be used, the following restrictions apply:

• If a Change Non-Conformance is opened, the system will not allow you to specify a different Material to
be consumed, using the Add Part option.
• If a Change Non-Conformance is opened, the system will not allow you to specify an Operation using
the Add Operation option, if Materials are already specified for the Operation that you want to add.
Target User
Users with the Production Coordinator role can perform this procedure.
Prerequisites
• Work Orders in the Aborted, Complete and Active status cannot be edited.

Procedure
1. Select the Work Order in the Work Orders page.
2. Click Edit and then, if necessary, change the main Work Order parameters. If you want to use a BoM, select
the Use BoM check-box and, from the BoM field, select a BoM that is appropriate for the Final Material to be
produced. Only one BoM can be selected.
 Plant settings can be edited only when the Work Order is in the Edit status.
3. Click to open the Work Order.

4. Click the Operation details tab and, if necessary, edit the existing Work Order Operations and/or create new
ones.
Note This step is not available if you are configuring a Work Order Header.
5. Click the Work Order Operation Dependencies tab to check the Operation dependencies and if necessary, edit
them. For more information, see Defining Dependencies between Work Order Operations.
6. (Only for Serialized Work Orders) Click the Serial Numbers tab and click the Associate Serial Numbers button:
the system displays the list of Serial Numbers that have been created for the Final Material, either select an
option from the list or, if you have configured a proper Identifier Template, click the Generate and associate
button to create a new one.
7. If necessary, edit the items associated to the Work Order Operations or add new ones.
8. (Only for Serialized and Full Quantity Work Orders) Click the Alternative Operations tab to create groups of
Operations that can be executed in alternative to the Work Order Operations defined at step 4.
9. If necessary, edit the Work Order Steps or add new ones, eventually defining dependencies among them.
10. If necessary, edit the items associated to the Work Order Steps or add new ones.
11. If necessary, associate Containers with the Work Order: the associated Containers are displayed in the
Containers tab.
• Release the Work Order, if you want the configured Work Order to be available for execution.
• Click the button to change its status to ReadyForScheduling, if you want to notify that the Work
Order configuration can no longer be changed (provided the Work Order does not belong to the
FlexibleBatch or FlexibleSerialized production type), and that the Work Order can be scheduled.
 In the case of FlexibleBatch and FlexibleSerialized Work Orders, it is always possible to make
changes to their configuration (for example, their Due Date), even while production is in
progress.
7.7.2.1 How to Create Work Order Operations

You can modify a Work Order in Edit status, not only changing its parameters, but if necessary also removing
Operations ( ), adding new ones or modifying the existing ( ).
Work Order Operations can be created:
• manually
• instantiating Process Operations previously created.
• instantiating Master Plan Operations downloaded from Teamcenter Manufacturing.
Prerequisite
The Work Order is in status Edit.


Do one of the following:
• If you have just created and opened a Work Order, click the Operation details tab.
• If the Work Order that you want to configure has been previously created and closed, select it in the Work
Orders page and click Edit.
• Creating Work Order Operations Manually
• Creating Work Order Operations from Process Operations
• Creating Work Order Operations from Master Plan Operations.
7.7.2.1.1 Creating Work Order Operations Manually

In a typical manufacturing cycle, Work Order Operations are automatically created from their corresponding
Process Operations when a Work Order is instantiated from its Process. It is also possible to create them manually,
for example when the Work Order to which they belong has also been created manually.
Procedure
1. In the Operations tab of the Work Orders page, click Create > Manually.
Identifier The unique identifier to be assigned to the Work Order

Operation. Once saved, this parameter can no longer be
modified.
Name The name of the Work Order Operation.

Work Order Operations included in the same Work Order. It will
be used by the system to automatically create dependencies
with other Work Order Operations, if you select the Create
Description Useful information about the Work Order Operation.
Required Inspection Role Deprecated.
Required Certification If a Certification name is specified, the Work Order Operation

can be started, paused or completed only by an Operator
owning the specified Certification.
If the field is left blank, no Certification is required to execute the
Work Order Operation.
Priority A number identifying the order of execution of the Work Order

Operation.

validated at the time of starting a Work Order. The validation
ensures that only authorized operators start Work Orders.
validated at the time of pausing a Work Order. The validation
ensures that only authorized operators pause Work Orders.
validated at the time of completing a Work Order. The validation
ensures that only authorized operators complete Work Orders.

associate documents with the Work Order Operation.
Dependency you want to create for the current Work Order
Operation:
• AfterEnd: The destination Work Order Operation can
be started only after the source Operation has been
completed.
• AfterStart: The destination Work Order Operation
can be started only after the source Operation has
been started.
Work Operation To define how the Work Order Operation must behave at
runtime, select one of the configured Work Operations. If you
select a Work Operation of type Additive Manufacturing, you
can associate this Work Order Operation with either a Substrate
or a Powder Material.
The default Work Operation is Standard. To create a Dynamic
Work Order Operation (that is a Work Order Operation whose
quantity can be changed at runtime until the Supervisor marks
it as Complete), the Production Type of the Work Order must
be either FlexibleBatch or FlexibleSerialized.
Operation/ Step Category Operation/Step Category to be assigned to the Work Order

Operation you are creating.

Operation/Step Category provided in Opcenter EX
DS will be assigned.
Estimated Duration The estimated duration of the Work Order Operation's

execution. It is expressed in hours, minutes, seconds.

Estimated Start Time The date and time when the Work Order Operation's execution
is expected to start.
Estimated End Time The date and time when the Work Order Operation's execution
is expected to end.
3. Click Create.
7.7.2.1.2 Creating Work Order Operations from Process Operations

When you create Work Order Operations from Process Operations, you inherit the configuration of the Process
Operation.
 If you are creating a Work Order Operation from a Process Operation, and Interlocking Checks have been
associated to the Process Operation, these Interlocking Checks will not be inherited by the corresponding
If you intend to use them, you must associate these Interlocking Checks to the Work Order Operation
manually.
Prerequisite
A Process, including one or more Operations is available in the system.
Procedure
1. In the Operations tab, click Create > From Process Operation.

modified.

As Planned BOP Baseline Identifier of the As Planned BOP containing the source
Process.
Process The source Process containing the Process Operation to be

instantiated.

Operation The Process Operation to be instantiated

It is possible to set a value for this parameter provided that you
have already selected a parent Process (Process).
 If a specific Operation/ Step Category has been assigned

to the Process Operation you select, this Operation/
Step Category will be inherited by the Work Order
Operation resulting from the Process Operation's
instantiation.
Otherwise, if no Operation/Step Category has been
assigned to the Process Operation you select, the
default Operation/Step Category provided in Opcenter
Execution Discrete will be inherited.
Estimated Start Time The date and time when the Work Order Operation's execution is
expected to start.
Estimated End Time The date and time when the Work Order Operation's execution is
expected to end.

Operation:
• After End: The destination Work Order Operation can
be started only after the source Work Order Operation
has been completed.
• After Start: The destination Work Order
Operation can be started only after the source Work
Order Operation has been started.

Estimated Duration The estimated duration of the Work Order Operation's execution.
It is expressed in hours, minutes, seconds.
3. Click Create.
7.7.2.1.3 Creating Work Order Operations from Master Plan Operations

When you create Work Order Operations from Master Plan Operations, you inherit the configuration of the Master
Plan Operation.
Prerequisites
• You have integrated Opcenter Execution Discrete with Teamcenter Manufacturing.
• A Master Plan, including Operations, has been downloaded to Opcenter Execution Discrete and listed in the
Master Plan page accessible from the home page.
Procedure
1. In the Operations tab, click Create > From Master Plan Operation.

modified.

Master Plan The Master Plan containing the Operation to be instantiated.
Process The source Process containing the Operation to be instantiated.

Operation The Master Plan Operation to be instantiated

It is possible to set a value for this parameter provided that you
have already selected a parent Process (Process).
 If a specific Operation/ Step Category has been assigned

to the Process Operation you select, this Operation/
Step Category will be inherited by the Work Order
Operation resulting from the Operation's instantiation.
Otherwise, if no Operation/Step Category has been
assigned to the Operation you select, the default
Operation/Step Category provided in Opcenter
Execution Discrete will be inherited.
Estimated Start Time The date and time when the Work Order Operation's execution is
expected to start.
Estimated End Time The date and time when the Work Order Operation's execution is
expected to end.

Operation:
• After End: The destination Work Order Operation can
be started only after the source Work Order Operation
has been completed.
• After Start: The destination Work Order Operation
can be started only after the source Work Order
Operation has been started.
Estimated Duration The estimated duration of the Work Order Operation's execution.

3. Click Create.
7.7.2.2 Defining Dependencies between Work Order Operations

Dependencies between Work Order Operations can be inherited from the corresponding dependencies between
Process Operations if the Work Order to which they belong is created from a Process. In this case, it is possible to
edit existing Dependencies and/or add new ones.
In alternative, Dependencies can be created manually if the Work Order and its Work Order Operations are in turn
created manually.
It is possible to create Dependencies between Work Order Operations belonging to the same Work Order or to
different Work Orders.
Dependencies can be displayed in a graph which can be customized as required.
Constraints
Do not use Optional Work Order Operation at the end of the routing, since they will be skipped by the system.
For any other constraint related to the management of Work Order Operations inside a routing see below.
Target User
Creating Dependencies between Work Order Operations

1. In the home page, click Work Orders .
2. Select a Work Order in one of the following states:
• Edit
• New
• ReadyForScheduling
• Queue
• Pause
• Hold
3. Click .
4. Click the Operations tab. The page displays those Work Order Operations that:
• are currently in state Open.
• were previously in state Open and are currently in state Future Hold
 To display the state, hover over the button in the Work Order Operation tile.
5. Select the Work Order Operation of interest and click Add Dependency.
 You can also create dependencies between Work Order Operations belonging to the same Work Order
during the creation of an Operation, selecting the Create Dependency check box.

Source Work Order The Work Order containing the Work Order Operation from which
the Dependency originates. By default, it is the currently-selected
Work Order.
Note When a different Work Order is selected in this field, the
currently-selected Work Order is set in the Destination Work Order
field: the Dependency that is being defined must involve the
currently-selected Work Order either as the source, the destination,
or both.
From Work Order Operation The Work Order Operation that influences the execution of the other
Work Order Operation. It is possible to choose among the Work
Order Operations belonging to the Work Order selected in the
Source Work Order field.
Destination Work Order The Work Order containing the Work Order Operation to (in) which
the Dependency ends (terminates). By default, it is the currently-
selected Work Order.
Note When a different Work Order is selected in this field, the
currently-selected Work Order is set in the Source Work Order field:
the Dependency that is being defined must involve the currently-
selected Work Order either as the source, the destination, or both.
To Work Order Operation The Work Order Operation the execution of which is influenced by
the execution of the previously-selected Work Order Operation. It is
possible to choose among the Work Order Operations belonging to
the Work Order selected in the Destination Work Order field.
Dependency Type Select one of the following:

• After End: The Operation selected from the To Work
Order Operation list can start only after the first Work
Order Operation is completed.
• After Start: The Work Order Operation selected from the
To Work Order Operation list can start only after the first
Work Order Operation has started.
Note
• In case of Work Orders with TransferBatch Production
Type, the dependencies between its Work Order
Operations must all be of type AfterEnd. Otherwise, you
will not be able to release the Work Order.
• In case of dependencies between Work Orders
Operations belonging to different Work Orders, the
runtime behavior is driven by the source Work Order
Operation. If the required conditions are not satisfied, the
Operator will not be able to proceed with production
execution. For more information, see Runtime Behavior
in case of Dependencies between different Work Orders.

Partial
 This parameter is enabled only if:
• Source Work Order is of type Serialized or
TransferBatch.
• Destination Work Order is different from
Source Work Order.
• Dependency Type is of type After End.
If this check box is selected, the Dependency is fulfilled when the

source Work Order Operation is completed by at least one piece
(either one Serial Number for a Serialized Work Order or one Batch
item for a TransferBatch Work Order).
If this check box is not selected, the Dependency is fulfilled when the
source Work Order Operation is completed in full (that is, either all
Serial Numbers for a Serialized Work Order or all Batch items for a
TransferBatch Work Order have been completed).
7. Click Save.
Customizing the Operation Dependency Graph

After creating Dependencies between the Operations contained in a Work Order as described above, click the Work
Order Operation Dependencies tab: the system displays a graphical representation of the existing dependencies.
In particular:
• Work Order Operations belonging to the current Work Order are displayed in blue.
• Work Order Operations belonging to different Work Orders are displayed in different colors (a specific color for
each Work Order).
• The dependencies are represented as arrows and their type is indicated near the arrow itself:
• After Start
• After End
• Partial After End: for After End dependencies from/to a different Work Order created with the Wait for
full completion parameter set to false.
If necessary, perform the following operations to customize the Operation Dependency Graph:
Constraints for Adding or Deleting Work Order Operations in a Routing

• Work Order Operations in a routing can only be deleted if all the related dependencies are removed and the
Work Order Operation is isolated (i.e. OutOfRoute).
• Work Order Operations can be removed from a routing only if the related predecessor and successor Work Order
Operations are in Open or Future Hold status. This is valid also for Optional Work Order Operations (i.e. having
Optional Work Operation type).
• New Work Order Operations can be added to an existing routing only if the required predecessor and successor
Work Order Operations are not dependent from each other.

• Dependencies can be removed from the page, while deleting the Work Order Operations from a routing requires
additional custom implementations in order to call the proper command. Also, to deleted Work Order
Operations from a routing, the CheckWOStatusOnDeleteWorkOrderOperation pre-check must be disabled
from Opcenter Execution Foundation Solution Studio.
• New Work Order Operations can be added to an existing routing even if the Work Order is already in execution,
provided that all the previous constraints are satisfied and you have implemented custom additional code in
order to call the proper command.
7.7.2.3 Defining Groups of Alternative Work Order Operations
Alternative Work Order Operations can be executed in place of the main execution flow configured for a specific
Work Order by setting dependencies between the Work Order Operations.
 • Groups of Alternative Work Order Operations can be defined only for Work Orders that belong to either
the Serialized or Full Quantity Production Type.
• A Work Order Operation cannot belong to different groups of Alternative Work Order Operations.
• The Work Order Operations making up a group must belong to the same Work Order.
For more information, see Alternative Work Order Operations in the Opcenter Execution Discrete Product Overview.
Target User
Prerequisite
• The Production Type of the involved Work Order is either Serialized or Full Quantity.
• You have defined at least three Work Order Operations.
• The Work Order Operations are in sequence and one is configured as predecessor of all the others.
Procedure
1. Open the Work Order in edit mode and then click the Alternative Operations tab.
2. In the top-right corner, click Add Group.
3. In the Add Alternative Operation Group panel, configure the following parameters:
Name Name to be assigned to the Group of alternative Work Order

Operations.
Parent Operation The Work Order Operation configured as predecessor in the execution
flow.
4. Click Add.
5. Set one of the listed Work Order Operations as the preferred one: click the star icon next to your choice.
 This preference setting can be changed according to your needs. See the section below for details.
6. Select all the Work Order Operations to be added to the group and click Add.

Changing the preference setting on Alternative Work Order Operations

Over time, you may find that you want to change your preference from one Alternative Work Order Operation in
favor of another: being able to change the preference setting allows you to adopt the solution that is best fit to
satisfy your production needs.
 Changing your preference from one Alternative Work Order Operation to another is permitted, provided
that the Work Order is not already in use.
1. Operating in the Work Order Detail page, click the Alternative Operations tab: this displays the available
Alternative Groups for the current Work Order.
2. Select the Alternative Group for which you want to change the preferred Alternative Work Order Operation and
then click : this opens the Edit Alternative Operation Group panel.
3. From among the Alternative Work Order Operations displayed for the selected Alternative Group, select the one
that you want to set as your new preference by clicking on the star icon next to it and then click Save.
7.7.2.4 Creating Work Order Steps manually

In a typical manufacturing cycle, Work Order Steps are automatically created from their corresponding Process
Steps when a Work Order is instantiated from its Process. It is also possible to create them manually, for example
when the Work Order to which they belong has also been created manually.
Target User
Procedure
1. In the Work Orders page, select the desired Work Order and click Open.
2. In the Operations tab, select the desired Work Order Operation and click Open.
4. Click Create > Create Step Manually.
Identifier The unique identifier to be assigned to the Work Order Step.

Name The name of the Work Order Step.
Description Useful information about the Work Order Step.
Sequence A number determining the order in which the Work Order Steps
included in the same Work Order Operation will be executed.

Step Category The Step Category to be associated to the Work Order Step being
created. It is used to implement custom behavior (for example,
plant-specific ways to execute the Work Order Step).

Step Category provided in Opcenter EX DS will be
assigned.
validated at the time of completing the instantiated Work Order
Operation. The validation ensures that only authorized operators
complete Work Order Operations.
Estimated Duration Hours Estimated duration, in hours, of the Work Order Step execution.
Estimated Duration Minutes Estimated duration, in minutes, of the Work Order Step
execution.
Estimated Duration Seconds Estimated duration, in seconds, of the Work Order Step
execution.
To Be Collected Document If the check box is selected, at runtime it will be possible to

associate documents with the Work Order Step.
6. Click Create.
7.7.2.5 Defining Dependencies between Work Order Steps

After defining some Work Order Steps, you can set the dependencies among them.
 Unlike those between Work Order Operations, dependencies between Work Order Steps can only belong
to the After End type.
Target User
Procedure
1. In the Steps tab, click Open.
2. Select the tab Dependencies.
4. In the From and To fields, set the Steps linked by the Dependency.

5. Click Save.
7.7.2.6 Associating Items to Work Order Operations

In a typical manufacturing cycle, resources like Machines, Materials and Tools are associated to Process Operations,
then automatically copied to the corresponding Work Order Operations when they are instantiated. It is also
possible to perform this procedure directly on Work Order Operations, for example to edit existing associations or
because the Work Order has been created manually.
Target User

1. Click Production Coordination > Work Orders in the sidebar.
2. Select the Work Order to which the desired Work Order Operation belongs and click Open.
3. Click the Operation Details tab.
4. Select the desired Work Order Operation and click Open.
Available Actions
You can provide Work Order Operations with:
• Machines
• Materials
• Tools
• Documents
• Powders
7.7.2.6.1 Associating Machines to Work Order Operations

This procedure allows you to specify where the Work Order Operation can be executed and the Machines which can
be used to execute the Work Order Operation.
If more than one Machine is associated with a Work Order Operation in status New, Partial or Open, you can specify
a preferred Machine by selecting it and clicking .
Target User
Procedure
1. Open the desired Work Order Operation and then click the Machines tab.
2. Click Create and then proceed as follows:

the selected Work Order
Operation
had the AM parameter selected Add 3D Printer, if the Work Order • Printer, the
Operation must be executed name of the 3D
on a specific 3D Printer. Printer.
• Print Job File,
the program the
3D Printer
requires to
determine how
to print items
tridimensionally.
(Optional, see
note below)
Add 3D Printer Type, if the Work • Printer Type,

Order Operation the name of the
can be executed using any 3D Printer 3D Printer Type.
belonging to a specific type. • Print Job File,
the program the
3D Printer
requires to
determine how
to print items
tridimensionally.
(Optional, see
note below)
Add Unit, if the Work Order Operation • Unit, the name

must be executed of the Machine.
had not the AM parameter
only on a specific Machine. • Part Program,
selected
the identifier of a
Part Program
that must be
downloaded to
the machine,
when the Work
Order Operation
is started.
(Only if the Work
Operation
associated to
this Work Order
Operation had
the CNC
parameter set)

the selected Work Order
Operation
Add Equipment Type, if the Work Equipment Type, the

Order Operation Equipment Type that you
can be executed using any Machine want to select for this
belonging to a specific class. machine instance.
Add WorkCenter, if the Work WorkCenter, the name of

Order Operation the Workcenter.
must be executed in a specific place.
 In case of Work Order Operations dedicated to 3D printing, the Print Job File field can be left blank
and then set at a later time:
• in this tab, by selecting the 3D Printer or 3D Printer Type and then clicking Link Print Job
File;
• if the Print Job File is a template (that is, the Print Job File must have Product to Be
Serialized set to True and Product Serial Number Management set to Pending) and the Work
Order is either of the Serialized or Full Serialized type, you can associate it with Serial
Numbers to create one or more Runtime Print Job Files.
• at runtime, before transferring the Print Job File to the 3D Printer.
3. Click Add.
7.7.2.6.2 Associating Materials to Work Order Operations

This procedure allows you to define an association between a Work Order Operation and the Material that it will
consume/assemble or produce.
Target User
Procedure
1. Open the desired Work Order Operation and then click the Materials tab.
2. Click .
Material If the associated Work Operation is of type Additive Manufacturing,

select a Material of type AMPowder. Upon selecting, Material
Specification Type is set to Additive in read-only mode.


consumed\assembled or produced during the Work Order
Operation's execution belongs. How you set this parameter will
affect one of the following:
Material's quantity. (output Material Specification Types).
the Group additional parameter is displayed as
mandatory, allowing you to create a logical grouping of
alternative Materials.
• As Required: The quantity to be consumed for each
Serial Number.
completed Work Order Operations belonging to the same
Work Order will be disassembled (dismantled) from the
compound Material.
• Normal Part: Default value. The entire quantity of the
• Range Parts: The portion (partial quantity) of the
Material to be consumed can range from greater than
zero to the total quantity of the Material itself.
• Selected Fit: The total part quantity for the selected
the parts.

from the execution of the Operation.
• Co-Product: To be selected when you intentionally want
same Material during the execution of the same
Operation. The quantity to be produced can range from
zero to the total quantity of each Material.
• By-Product: To be selected when, in addition to a distinct
the execution of the same Operation, there
will inevitably be also a resulting by-product (derivative)
that may or may not be further processed to produce
something else. The quantity to be produced can range
from zero to the total quantity of each Material.

Quantity The quantity of the Material to be consumed during the Work

Order Operation. After setting this parameter, select the appropriate
Unit of Measure from the drop-down list on the right. If a Material of
type AMPowder is selected, only those units that are applicable for
powder batches are available in the drop-down list.
Alternative Selected If the Material Specification Type is set to Alternative, select the
check box to define which Material must be displayed by default to
the Operator among those contained in the same Group.
4. Click Add.

7.7.2.6.3 Associating Tools to Work Order Operations

This procedure allows you to define an association between a Work Order Operation and the Tools that will be used
to execute it.
Target User
Procedure
1. Open the desired Work Order Operation and then click the Tools tab.
2. Click .
Tool Definition Name The type of Tool to be used to perform the Work
Order Operation. Select one among those you have created. If
the associated Work Operation is of type Additive
Manufacturing, you can also associate a Tool Definition of type
AM Substrate, indicating that the Tool is a Substrate. It is
possible to have a Process Operation of type Additive
Manufacturing, having both Substrates and regular Tools
associated with it.
Usage Number The number of times the Tool is used to perform the current
4. Click Create.
7.7.2.6.4 Associating Documents to Work Order Operations

This procedure allows you to define an association between a Work Order Operation and a set of Documents which
can be useful to the Operator that will execute the Work Order Operation. For example, it could be useful to provide
the user with an image of the involved items in order to allow him or her to easily identify them before executing the
Work Order Operation. Such documents, added at the engineering phase, are displayed under the Documents tab.
Additionally, if the Operator adds documents to a Work Order Operation at runtime, these documents are also
displayed under the Documents tab.
In addition, to further support the Operator, you can also associate detailed Work Instructions to the Work
Order Operation.
Target User
Procedure
1. Open the desired Work Order Operation and then click the Documents tab.
2. Click Link.
3. If the Document to be associated with the Work Order Operation is not displayed in the list, click
Import and select the file of interest.
4. Select the Document of interest from the list and click Link.

 If Multi-Plant Support is enabled, tags currently enabled for the logged User are applied to the imported
Documents.
7.7.2.6.5 Associating Work Instructions to Work Order Operations

Work Instructions are used by Operators at runtime to get detailed instructions about carrying specific tasks on the
product. Work Instructions are also used to collect data during production execution. To discriminate if a Work
configured as Acknowledge or DataCollection type.
For more information about Work Instructions, see the Work Instruction App in the Opcenter Execution Foundation
User Manual.
Work Instructions can be associated with both Work Order Operations and Work Order Steps.
Target User
Prerequisite
A Work Instruction to be associated with the Work Order Operation is available.
Procedure
1. Open the desired Work Order Operation and then click the Work Instructions tab.
2. In the top-right corner, click Link Work Instruction.
3. Select one of the following options from the Work Instruction Association Type drop-down list box:
• Operation: the Work Instruction will be associated with the whole Work Order Operation;
• SerialNumber: the Work Instruction will be associated with all the Serial Numbers produced by the Work
Order Operation (only for Serialized, FullSerialized and FlexibleSerialized Work Orders);
• SerialNumberOnDemand: the Work Instruction will be associated only to some Serial Numbers
produced by the Work Order Operation. The Operator will select at runtime the exact list of Serial
Numbers to be associated (only for Serialized, FullSerialized and FlexibleSerialized Work Orders).
4. Select the file to be associated with the Work Order Operation and then click Link.
 If the Work Instruction is linked to an Automation Node Instance, you can link the related Parameters.
The Automation Node Variable tab fetches the values of these parameters and displays them in a tree
view.
7.7.2.6.6 Associating Skills to Work Order Operations
Target User

Prerequisite
Procedure
1. Open the desired Work Order Operation and then click the Skills tab.
2. Click Add.
3. In the Level edit box, type the required level of the Skill to be associated to the Work Order Operation.
exact or the minimum value required to authorize the Work Order Operation execution.
7.7.2.6.7 Linking Interlocking Checks to Work Order Operations
Both Standard and Custom Interlocking Checks can be linked to Work Order Operations to verify whether one or
more conditions have been satisfied at runtime prior to starting or completing them.
If the outcome of all these checks is successful, the execution of the Work Order Operation will either be started
 Interlocking Checks linked to Work Order Operations configured with Auto-Start and Auto-Complete
behavior will not be executed.
Name Description
AllPartsAssembled Verifies whether all parts have been assembled as expected

according to the Material Specifications or BoMs.
AllStepsCompleted Verifies whether all Steps of a Work Order Operation have been
completed.
DocumentsUploaded Verifies how many Documents have been uploaded in relation to

the current Work Order Operation.
Target User
Prerequisite
The Interlocking Check to be linked is configured as Operation-relevant.

Procedure
1. Open the desired Work Order Operation and then click the Interlocking Checks tab.
2. Click Link.
3. In the Link Interlocking Check pane, select the Interlocking Check to be linked: if you have selected a standard
4. (only for custom Interlocking Checks) In the Define Interlocking Check Type area, select at least one of the
following Interlocking Types:
Values.
8. Click Link.
unlinked.
Keep in mind that you cannot unlink Interlocking Checks from Work Order Operations if:
• The Work Order Operation is in Aborted, Complete or Not Executed status.
• The Work Order to which the Work Order Operation belongs is in Aborted, Complete, Scrap, Split
or Verified status.
7.7.2.6.8 Linking Inspection Definitions to Work Order Operations

Likewise to Process Operations, you can associate Inspection Definitions to Work Order Operations.
Finally, Quality Inspections can be configured to be executed on each piece produced (100 Percent) or
automatically triggered according to a specified interval of produced items (Part Based).

 • Part Based Quality Inspections are only supported for

Serialized, FullSerialized, FlexibleSerialized and FullQuantity production types.
• In case of Alternative Paths having more than one Work Order Operation, the Quality Inspection cannot
be associated to the first Operation of the alternative path. If the alternative path contains only one
Work Order Operation, then the Quality Inspection task must be associated to the Work Order
Operation closing the Alternative path.
Target User
Prerequisite
system.
• (For Buy-Off only) The Inspection Definition to be linked to the Work Order Operation must:
• If the Work Order Operation also contains Steps, it is recommended that you link the
AllStepsCompleted Interlocking Check to avoid that the Work Order Steps are set to NotExecuted once
a Buy-Off request is accepted for the Work Order Operation.
• (For Part Based Inspections only) The Inspection Definition to be linked to the Process Operation must have the
Frequency set to Part Based.
Procedure
1. Open the desired Work Order Operation and then click the Quality Inspections tab.
2. Click Link.
3. Select one or more Inspection Definitions to be associated.
4. (For Part Based Inspections only) Select a reference operation to be used by the system to recognize when to
start the inspection, according to the configured interval of produced items.
5. Click Link.
• You can link multiple Inspection Definitions to a Work Order Operation, but only one revision of
the selected Inspection Definition can be linked.
7.7.2.6.9 Linking Human Resources to Work Order Operations

Linking Human Resources to Process Operations
Likewise to Process Operations, you can associate Human Resources to Work Order Operations.
Human Resources are used to specify how many users with specific Certifications are required to start the execution
of a specific Work Order Operation.
Once the Human Resource is linked to the Work Order Operation, it is possible to remove the association (
button) or to modify the number of users that are required to possess each Certification ( button).

Target User
Prerequisite
Procedure
1. Open the desired Work Order Operation and then click the Human Resources tab.
2. Click Link.
5. Click Link.
7.7.2.6.10 Associating Powders to Work Order Operations

This procedure allows you to specify which Powder must be loaded into the 3D Printers associated to the Work
Order Operation.
Target User
Users with the Product Engineer Role can perform this action.
Prerequisites
• The status of the Work Order Operation is one of the following: Edit, Hold, or Aborted.
• The Work Operation type must be Setup3DPrinter (which has the property Load AM Powder set to true).
Procedure
1. Open the desired Work Order Operation and then click the AM Powders tab.
2. Click . The upper area of the Set Powder pane displays the list of 3D Printers associated with the Process
Operation.

the 3D Printer.
4. Click Set.

7.7.2.7 Associating Items to Work Order Steps

In a typical manufacturing cycle, resources like Machines, Materials and Tools are associated to Process Steps, then
automatically copied to the corresponding Work Order Steps when they are instantiated. It is also possible to
perform this procedure directly on Work Order Steps, for example to edit existing associations or because the Work
Order has been created manually.
Target User

2. Select the Work Order to which the desired Work Order Step belongs and click Open.
3. Click the Operation Details tab.
4. Select the Work Order Operation to which the desired Work Order Step belongs and click Open.
6. Select the desired Work Order Step and click Open.
Available Actions
You can provide Work Order Steps with:
• Materials
• Tools
• Documents
7.7.2.7.1 Associating Materials to Work Order Steps

This procedure allows you to define an association between a Work Order Step and the Materials that it will
consume or assemble.
Target User
Procedure
1. Open the desired Work Order Step and then click the Materials tab.
2. Click .

Material The Material to be consumed or assembled during the Work

Order Step. If you select a Material of type Additive Manufacturing,
Material Specification Type is set to Additive in read-only mode,
indicating that this is a Powder Material.


consumed\assembled or produced during the Work Order Step's
execution belongs. How you set this parameter will affect one of the
following:
the Group additional parameter is displayed allowing you
to create a logical grouping of alternative Materials.
• As Required: The quantity to be consumed for each
Serial Number.
completed Steps related to the completed
Operations belonging to the same Work Order will be
disassembled (dismantled) from the compound Material.
• Normal Part: Default value. The entire quantity of the
• Range Parts: The portion (partial quantity) of the
Material to be consumed can range from greater than
zero to the total quantity of the Material itself.
• Selected Fit: The total part quantity for the selected
the parts.

from the execution of the Step.
• Co-Product: To be selected when you intentionally want
same Material during the execution of the same Step. The
• By-Product: To be selected when, in addition to a distinct
the execution of the same Step, there will inevitably be
also a resulting by-product (derivative) that may or may
not be further processed to produce something else. The


Quantity The Quantity of Material to be consumed during the Work

Order Step. After setting this parameter, select the appropriate Unit
of Measure from the drop-down list on the right. If a Material of type
AMPowder is selected, only those units that are applicable for
powder batches are available in the drop-down list.
4. Click Add.

7.7.2.7.2 Associating Tools to Work Order Steps

This procedure allows you to define an association between a Work Order Step and the Tools that will be used to
execute it.
Target User
Procedure
1. Open the desired Work Order Step and then click the Tools tab.
2. Click Create.
Tool Definition The type of Tool to be used to perform the Work Order Step.
Select one among those you have created.
Usage Number How many times the Tool must be used to perform the current
Work Order Step.
4. Click Create.
7.7.2.7.3 Associating Documents to Work Order Steps

This procedure allows you to define an association between a Work Order Step and one or more Documents which
can be useful to the Operator who will execute the Work Operation Step.
For example, it could be useful to provide the user with an image of the items involved in order to allow him or her
to easily identify them before the assembly.
In addition, to further support the operator, you can also associate detailed work instructions to the Work
Order Step.
Target User
Procedure
1. Open the desired Work Order Step and then click the Documents tab.
2. Click Link.
3. If the Document to be associated with the Work Order Step is not displayed in the list, click
Import and select the file of interest.
4. Select the Document of interest from the list and click Link.
7.7.2.7.4 Associating Work Instructions to Work Order Steps

Work Instructions are used by Operators at runtime to get detailed instructions about carrying specific tasks on the
product. Work Instructions are also used to collect data during production execution. To discriminate if a Work
configured as Acknowledge or DataCollection type.

They can be associated also with Work Order Operations.

User Manual.
Target User
Prerequisite
A Work Instruction to be associated with the Work Order Steps is available.
Procedure
1. Open the desired Work Order Step and then click the Work Instructions tab.
2. In the top-right corner, click Link Work Instruction.
3. If the Work Instruction is used to collect Data, select one of the following options from the Work Instruction
Association Type drop-down list box:
• Operation: the Work Instruction will be associated with the whole Work Order Operation;
• SerialNumber: the Work Instruction will be associated with all the Serial Numbers produced by the Work
• SerialNumberOnDemand: the Work Instruction will be associated only to some Serial Numbers
produced by the Work Order Operation. The Operator will select at runtime the exact list of Serial
Numbers to be associated (only for Serialized, FullSerialized and FlexibleSerialized Work Orders).
4. Click Link.
7.7.2.7.5 Associating Skills to Work Order Steps
Target User
Prerequisite
Procedure
1. Open the desired Work Order Step and then click the Skills tab.
2. In the top-right corner, click Link.
exact or the minimum value required to authorize the Work Order Step execution.
4. Select one or more Skills from the list.

 If multiple Skills are selected at the same time, they are all associated with the same Level. If you need
to associate Skills with different Levels, you need to associate them individually.
5. Click Create.
7.7.2.7.6 Linking Interlocking Checks to Work Order Steps
Interlocking Checks (both of Standard and Custom type) can be linked to Work Order Steps to verify whether one or
more conditions have been satisfied at runtime prior to starting or completing them.
If the outcome of all these checks is successful, the execution of the Work Order Step will either be started
For more information, see the section Interlocking Checks of the Opcenter Execution Discrete Product Overview. The
following table lists the Interlocking Checks provided by default by Opcenter EX DS.
Name Description
Step, according to the Material Specifications.
• For TransferBatch Work Orders, the check is specific to the
quantity to be completed.
AllStepsCompleted Verifies that all the Steps belonging to the active Work Order
Operation have been completed.
current Work Order Step. This Interlocking Check is performed against
the Min. doc # parameter: if the number of uploaded Documents falls
below the value set for this parameter, the check's outcome is
considered unsuccessful.
A distinction is made for the various Production Types available for
Work Orders: for details, see Role of Work Order Production Type for
Target User
Prerequisite
The Interlocking Check to be linked is configured as Step-relevant.
Procedure

1. Open the desired Work Order Step and then click the Interlocking Checks tab.
2. Click Link.
3. In the Link Interlocking Check page, select the Interlocking Check to be linked: if you have selected a standard
4. (only for custom Interlocking Checks) Define at least one of the following Interlocking Types:
INBOUND If this check box is selected, the custom Interlocking Check will
trigger the start of the related Work Order Step, once all conditions
required by the check are satisfied.
OUTBOUND If this check box is selected, the custom Interlocking Check will
trigger the completion of the related Work Order Step, once all
5. In the Associated Interlocking Check Parameters pane, select a parameter and then click Set Parameter
Values.
8. Click Link.
unlinked.
Keep in mind that you cannot unlink Interlocking Checks from Work Order Steps if:
• The Work Order Operation containing the Step is in Aborted, Complete or Not Executed status.
• The Work Order to which the Work Order Operation containing the Step belongs is in Aborted,
Complete, Scrap, Split or Verified status.
7.7.2.7.7 Linking Inspection Definitions to Work Order Steps

Likewise to Process Steps, you can associate Inspection Definitions to Work Order Steps.
Inspection Definitions are used to configure Quality Inspections to be carried out at runtime. They represent how a
certain measurement (that is, a Quality Characteristic) has to be collected at runtime in terms of frequency and
sample size.
Measurements can be related to Attributive, Variable or Visual Quality Characteristics. The results of the
measurements at runtime, collected for the Inspection Definitions, can be used to perform Statistical Process
Control (SPC) calculations.
Target User
Prerequisite

system.
• (For Buy-Off only) The Inspection Definition to be linked to the Work Order Step must:
Procedure
1. Open the desired Work Order Step and then click the Quality Inspections tab.
2. Click Link.
3. Select one or more Inspection Definitions to be associated and click LINK.
• You can link multiple Inspection Definitions to a Work Order Step, but only one revision of the
7.7.2.7.8 Linking Human Resources to Work Order Steps

Likewise to Process Operations, you can associate Human Resources to Work Order Steps.
Human Resources are used to specify how many users with specific Certifications are required to start the execution
of a specific Work Order Step.
Once the Human Resource is linked to the Work Order Step, it is possible to remove the association ( button) or
to modify the number of users that are required to possess each Certification ( button).
Target User
Prerequisite
Procedure
1. Open the desired Work Order Step and then click the Human Resources tab.
2. Click Link.
5. Click Link.
7.7.2.8 Associating Users to Work Order Operations

Once created, Work Order Operations are automatically associated to the same items to which the source
Operations are associated. In addition to changing these associations according to your needs, you can also
associate Users to Work Order Operations in order to define who is allowed to manage them at runtime.
Target User

Prerequisite
The status of the Work Order Operation is one of the following: Open, Partial, Active or Future Hold.
Procedure
2. Select a Work Order and then click .
3. In the Operation Details tab, select the Work Order Operation of interest and then click .
4. In the Users tab, click Link User to Work Order Operation.
5. In the Add User Association panel, select the users you want to associate to the Work Order Operation
according to the required Skills and their presence within the plant and then click Save.
6. To remove a User association, select one or more Users and click Unlink User from Work Order Operation.
7.7.3 Scheduling a Work Order

When the Work Order configuration is completed but the Work Order cannot be released yet, it is set in
ReadyForScheduling status and, if properly configured, the system sends a notification to the Production
Coordinator who can proceed with the Work Order scheduling.
This operation may consist of two subsequent phases:
1. Defining estimated due date, start time and end time at Work Order level, editing the Work Order from the Work
Orders page. This phase is optional and is intended to provide indications to correctly plan the execution of the
associated Work Order Operations.
2. Setting scheduling details for each Work Order Operation in either of the following environments:
• Production Coordinator Dashboard as described below. From this page, you can also monitor and
tweak production execution later.
• Sequencer, in case of integration with Opcenter APS.
 Scheduling of FlexibleBatch and FlexibleSerialized Work Orders

• If you are a Production Coordinator, it is possible to schedule a FlexibleBatch (or FlexibleSerialized)
Work Order, even if there are no ProducedMaterialItems associated to it or they do not match with the
Work Order's target quantity.
• It is possible to set a planned target quantity for a flexible Work Order so that it is possible to schedule
the Work Order based on an estimated target quantity.
Prerequisite
The Work Order is not in a final status (for example Complete or Scrap).
Target User
Procedure
1. Click the Production Coordinator Dashboard tile in the home page.
2. Select the Workcenter or Machine where the Work Order Operations are planned to be executed and click
Open: the system displays the list of associated Operations, showing them graphically on a time table if their
execution has been scheduled.

 The content of Production Coordinator Dashboard is periodically refreshed at a predefined frequency.

You can pause the refresh clicking on Disable countdown, then resuming it clicking on Resume
countdown.
3. Click the button to select one or more sets of Work Order Operations that you want to display:
Option Resulting Display
Active Operations Work Order Operations in Active status.
Ready Operations Work Order Operations in Open status that are ready to
be executed.
Open Operations Work Order Operations in Open status.
Complete Operations Work Order Operations in Complete status.
Partial Operations Work Order Operations in Partial status.
 Clicking on the button you can set additional filters on specific Work Orders, Materials or date/time
ranges.
4. Select the Work Order Operation that you want to reschedule and then click the following buttons according to
your needs:
Click... If you want to...
Set the Machine as the preferred Machine for the Work Order Operation.
 This option is available only if you have selected a Machine (and not
a Workcenter) and when the Work Order Operation is in the New,
Partial or Open status.
Set or modify the estimated start and end time of the Work Order Operation.
Note If the estimated start and end time of a Work Order Operation is already
set, it appears as a graphical bar. You can drag the bar and/or resize it to
modify the time range.
Assign the Work Order Operation to another workstation.
Release a Work Order, if not already released.

Click... If you want to...
Set in ReadyForScheduling status the Work Order to which the Work Order
Operation belongs. The button is displayed only if the Work Order is in
Edit status.
Insert a note relative to the Work Order Operation to be acknowledged

before its execution.
7.7.4 Releasing a Work Order

When the Work Order configuration is completed, you can release it for production.
Prerequisite
The Work Order is in Edit or ReadyForScheduling status.
Target User
Procedure
1. In the Work Orders page, select the Work Order that you want to release.
2. Click the button to release the Work Order.
3. Click OK to confirm the operation: the system changes the Work Order status to New and, if properly
configured, a notification is displayed in the notification bar to inform the Operator that the Work Order can be
executed.
 In alternative, you can release Work Orders also from the Production Coordinator Dashboard.
Result
The Work Order is released. If the Work Order you released has associated Work Order Operations of type Additive
Manufacturing, then the following scenarios are applicable:
Work Order Type Print Job file Quantity Expected Scenario
Any Greater than Work Order Quantity Work Order is released with a warning
Any Equal to Work Order Quantity Work Order is released successfully
TransferBatch, or Less than Work Order Quantity Work Order is released successfully
Serialized
FullQuantity or Less than Work Order Quantity The system displays an error, and the Work
FullSerialized Order is not released

7.7.5 Pre-Transferring Print Job Files to 3D Printers

Specific 3D Printers associated with Work Order Operation of type Additive, may need to receive the Print Job Files
in advance, in order to properly process them and to generate the final Print Job Files to be used for the printing.
Since the processing of the Print Job File usually requires a huge amount of time, the transfer should be performed
as soon as possible, for example when the Work Order configuration is completed.
Target User
Prerequisites
• The AMPlugInPrinterConn Plugin ot type PrinterConn has been configured.
• A 3D Printer that requires an intermediate Print Job File (Is Pre-Transfer Enabled parameter selected) has been
associated to both the Work Order and the AMPlugInPrinterConn plugin (through the Transfer Plugin
parameter).
• An intermediate Print Job File (Can be Pre-Transferred parameter selected) is compatible with both the 3D
Printer and the final Material of the Work Order (with the appropriate quantity).
Procedure
1. In the Work Orders page, select the Work Order whose Print Job Files must pre-transfer to the 3D Printer.
2. Click the Pre-Transfer button.
3. Select a 3D Printer among those that require preliminary Print Job Files to be processed.
4. Select the Print Job Files to be pre-transferred.
5. Click Transfer.
7.7.6 Editing Released Work Orders Before Execution

Generally speaking, during normal manufacturing workflows, once a Work Order has been released, it is usually not
necessary to edit it prior to its execution. However, in exceptional cases, the Production Coordinator and/or the
Product Engineer might want to edit the main Work Order parameters (for example, the quantity of Final Material or
the list of Serial Numbers to be produced). Before performing this operation it is necessary to reset the Work Order
status to Edit and then, after making the changes, the Work Order must be released again. Instead, at any time, it is
possible to modify the items making up the Work Order (for example, its Work Order Operations and any related
dependencies) without changing the status of the released Work Order.
Prerequisite
The Work Order is in New status.
Target User
Users with the Production Coordinator or the Product Engineer roles can perform this action.
Procedure
1. In the Work Orders page, select the Work Order that you want to edit.
2. Click Change Status To Edit.
3. Click Yes to confirm the operation: the system changes the Work Order's status to Edit.
4. Select the Work Order again and click Edit to edit it.

 Edited Work Orders must be released again before their execution.
7.7.7 Splitting a Work Order

You might encounter a scenario where a Work Order might need to be repeated, or altered. Sometimes, engineering
issues might be discovered in the process for which production will require subsequent rearrangement. A Work
Order might be too large, and you may need to break it down into numerous Work Orders while retaining the
configuration of the original Work Order. For scenarios such as these, you can split a Work Order.
 When a Work Order that produces a Material Tracking Unit (that is, a Batch) to which one or more
Documents have been associated is split, the new Work Orders resulting from the split will produce in turn
Batches that will automatically be associated to the same Documents associated to the Batch produced by
the original Work Order.
Prerequisite
The Work Order has been released.
Target User
Procedure
1. In the Work Orders page, select a Work Order and then click Split.

Type The criteria to be used to split the Work Order. Select one of the
following options:
• Size, the original Work Order is split into new Work Orders
of the size value specified in Split Quantity. For example,
if you set Split Quantity to 4, an original Work Order of
size 10 will be split into three Work Orders, two of size 4,
and one of size 2 respectively.
• Number, the Work Order will be split into as many Work
Orders of equal size as possible as represented by the
value of Split Quantity. The remainder size value, if any,
will represent another Work Order. For example, if you set
Split Quantity to 3, an original Work Order of size 10 will
be split into three equal-sized Work Orders of size 3 each,
and another Work Order of size 1.
• Copy, the original Work Order will be copied, but with a
size that matches the Split Quantity value. In the
example above, if you set Type to Copy, and Split
Quantity to 2, the original Work Order of size 10 will be
copied; however, the size of the new Work Order will be
set to 2, while the original Work Order will now have size
8.
Quantity The system automatically calculates the quantity of each Work Order
as described above but, if necessary, you can modify the values
manually according to your needs, provided that the sum of the
inserted values corresponds to the quantity of the original Work
Order.
Split Quantity Indicates the value with which a Work Order will be split.
3. The fields New Work Order display the identifiers of the Work Order that will be generated. You can either:
• accept the proposed identifiers;
• modify them manually;
• generate them according to their predefined template (if any) clicking Generate.
4. Click Split.
 When Work Orders are split by type Copy, existing Non-Conformances, if any, are automatically inherited
after the splitting operation.
7.7.8 Performing Pre-Kitting for Work Orders

Work Order pre-kitting permits reserving the Serial Numbers or Batches and their respective quantities that are
required for an assembly order. You can operate from the Work Order Pre-Kitting page to set the MTUs (with their
respective quantities) that will be automatically presented to the operator in assembly operations.
When performing pre-kitting, depending whether the Material to be consumed is a Serial Number or a Batch, it is
possible to reserve either of the following for each Work Order Operation (or Work Order Step):
• a single Serial Number (for serialized Materials)
• more than one Batch (for Materials that are Batches).

The icon indicates that pre-kitting (either in full or in part) has already been performed on the Material Tracking
Unit to which it refers.
 Partial Pre-Kitting
Should you want to pre-kit a quantity of a Material Tracking Unit that exceeds the quantity that is currently
available, in this case, the pre-kitting will be performed, but it will be considered a partial pre-kitting, as
the required quantity is not totally satisfied. For example, if the quantity you want to pre-kit is 10 and the
Material Tracking Unit has a quantity equal to 6, then the entire quantity of the MTU is pre-kitted, but a
remainder of 4 is yet to be satisfied.
Constraints
Pre-Kitting is not permitted for Work Order Operations (as well as Work Order Steps) that:
• belong to a Work Order that is in status Scrap, Hold or Aborted.
• belong to a Work Order of TransferBatch or FlexibleBatch production type.
Depending on the Material to be consumed, the elements that are to be reserved must be either all Serial Numbers
or all Batches.
For Material Tracking Units with the Enable Automatic Consumption flag set to True, the quantity that you want to
pre-kit must be equal to or less than the value set for Max. Consumption Quantity.
Target User
Procedure
1. Click Production Coordination > Work Order Pre-Kitting in the sidebar: the Work Order Pre-
Kitting screen displays all the Work Orders for which pre-kitting is allowed.
2. Select the Work Order for which you want to reserve Serial Numbers or Batches (with their respective quantities)
and click Open.
3. Select the Material for which you want to reserve the related MTU required by the Work Order Operation (or
Work Order Step) to produce the Final Material and click Pre-Kit: the Pre-Kit Serial Numbers/
Batches panel is displayed, which presents all the Materials that must be produced by the selected Work Order.
 If desired, if you click on the History tab that is displayed, it is possible to view the history of all pre-
kitting performed on the various MTUs to be produced related to the selected Work Order.
4. For each Material to be produced, reserve a Serial Number or one or more Batches as follows:
• In the Serial Number / Batch Id edit box, either:
• Click , select the Serial Number or Batch you want to reserve and then click Select: the edit
box is filled with your selection.
• Type either the desired Serial Number or Batch manually: if the Serial Number or Batch you enter
manually does not yet exist in the system, it will be created once you click Pre-Kit.
5. (If the Material you want to reserve is a Batch) In Quantity, enter the quantity (portion) you want to reserve of
the total quantity of the Batch you selected in the previous step.
6. Select the Validate check box, if you want the pre-kitted Serial Number/Batch to be validated prior to its
consumption when executing a Work Order Operation or Work Order Step at runtime.

How to Create and Prepare Execution Groups for Production Execution
7. If you want to reserve additional Batches for the same Material to be produced, click Add Serial Number /
Batch Id to be Pre-Kitted and repeat steps 4 thru 6.
8. Click Pre-Kit: the Serial Number or the multiple Batches you have specified in the previous steps will be
reserved for the Work Order Operation (or Work Order Step).
 Pre-kitting History
Operating from the Work Order Pre-kitting Details screen, it is possible to view the history of any pre-
kitting operations performed on a certain Work Order: simply select the Work Order of interest and then
select the History tab. If no pre-kitting operations have been performed, the tab in question will display no
data.
7.8 How to Create and Prepare Execution Groups for Production

Execution
Execution Groups are sets of previously created Work Order Operations (belonging to either the same Work Order or
to different Work Orders) that are grouped to be executed together at runtime on the same Equipment.
The purpose of Execution Groups is to both maximize productivity and minimize Equipment downtime, thereby
allowing the Machines to work at full capacity.
Managing Execution Groups involves several actions: some of them can be performed both during the Engineering
and the Runtime phases, while others are reserved only for a specific phase.
 Production Execution involving Execution Groups

Production execution follows a distinct workflow when Execution Groups are involved: see dedicated
section How to Execute Production on Execution Groups for details.
Accessing the Work Environment

To access the Execution Groups page, click Production Coordination > Execution Groups in the sidebar.
Workflow
1. Create an Execution Group.
2. Link Work Order Operations to an Execution Group.
3. (Optional) Update Execution Group Phases: this includes scheduling Execution Group Phases manually.
4. (Feasible only in Additive Manufacturing - Optional) Link Print Job Files to Execution Group Phases.
5. (Optional) Link Work Instructions to Execution Group Phases.
6. (Optional) Associate Powders to Execution Group Phases.
7. (Optional) Schedule an Execution Group.
8. Release an Execution Group.
9. (Optional) Display the details of the actions performed on the Execution Group (History tab).
7.8.1 Creating an Execution Group

This procedure allows you to create an Execution Group, to which you can later link Work Order Operations
grouped together to be executed on the same Equipment.

Target User
Procedure
1. In the Execution Groups page, click Create.
Identifier Unique Identifier of the Execution Group.
Name The name of the Execution Group.
Description Useful information about the Execution Group.
Estimated Duration Estimated duration necessary to execute the Execution

Group.
Estimated Start Time The date and time when the Execution Group is expected to
start.
Estimated End Time The date and time when the Execution Group is expected to
end.
3. Click Save.
Result
The new Execution Group is displayed in the page, and you can complete its configuration by linking Work Order
Operations to it.
7.8.2 Linking Work Order Operations to an Execution Group

This procedure allows you to link Work Order Operations to an Execution Group previously created. Once grouped
together, the Work Order Operations can be later executed together on the same Equipment.
 Work Order Operations (and the Work Orders to which they belong) cannot be deleted if they are linked to
an Execution Group.
It is possible to set various filters to select the Work Order Operations to be included in an Execution Group. For
example, when including Work Order Operations that belong to the same Work Order, it is possible to select a range
of sequence numbers.
 Unlinking Work Order Operations from an Execution Group

Unlinking at least one Work Order Operation belonging to a specific Work Order from an Execution Group
automatically unlinks all the other Work Order Operations (and not just the selected ones) belonging to
the same Work Order. Partial unlinking is not supported.

Prerequisites
All the Work Order Operations that are to be linked to • have at least one common Machine on which they
an Execution Group must..... can be executed within the same Execution Group
Phase.
• use Tools belonging to the same Tool Definitions, if
any.
• consume Material Tracking Units belonging to the
same Materials, if any.
• require the same Skill and Skill Levels, if any.
• have a dependency on the next Work Order
Operation.
• belong to a Work Order with Production Type that
differs from FlexibleSerialized and FlexibleBatch.
The Work Operations associated to the Work Order • Not possess any of the following attributes:
Operations must... • Milestone
• Optional
• Only One Active
• Auto-Start
• Auto-Complete
• Machine Auto-Start
• Machine Auto-Complete
• Machine Auto-Pause
• Can be skipped.
• Quality Only
• Dynamic.
The Execution Groups to which you want to link the Have not yet been released.
selected Work Order Operations must....
Target User
Procedure
1. In the Execution Groups page, select the Execution Group to which you want to link Work Order Operations and
click Open.
2. Click the Operations tab. The upper panel displays the Work Order Operations currently linked to the selected
Execution Group. Select a Work Order Operation to display in the lower panel the Material Tracking Units
produced by the Work Order to which the Work Order Operation belongs.
3. Click Link.
4. In the Link Operations to Execution Group panel, select one or more Work Order Operations to be linked to the
selected Execution Group.

 • When multiple Work Order Operations belonging to the same Work Order and linked by linear
dependencies are selected, one Execution Group Phase is automatically created for each Work
Order Operation involved. Execution Group Phases can later be edited if needed, or in case of
Additive Manufacturing Print Job Files can be linked to Execution Groups Phases, however, it
will not be possible to add other Work Order Operations with different Execution Group Phases
to the same Execution Group.
• Work Order Operations that are already linked to another Execution Group can be selected only
if the other Execution Group has been completed.
• When multiple Work Order Operations are linked to an Execution Group Phase, the Estimated
Duration of the Execution Group Phase can be optionally configured to be equal to the value of
the Work Order Operation where Estimated Duration value is the highest.
5. (Optional) For selected Work Order Operations belonging to Serialized or TransferBatch Production Types, the
related quantities of Serial Numbers and/or Batch Items to be produced are displayed in the Select Quantity
table. For each of these Work Order Operations, type the quantity to be produced by the Execution Group.
6. Click Link.
 The Execution Groups tab on the Work Orders page displays the Execution Groups currently linked to any
of the Work Order Operations belonging to the selected Work Order. Select an Execution Group and click
Open.
7.8.3 Updating Execution Group Phases

When Work Order Operations are linked to an Execution Group, Execution Group Phases are automatically created.
After their creation, it is possible to update (edit) Execution Group Phases manually. In this case, you can:
• schedule the Execution Group Phase's execution.
• choose to permit the uploading of documents in relation to the Execution Group Phase.
• set the Machine of preference for the Execution Group Phase's execution.
In case of Opcenter EX DS and Opcenter APS integration, Work Order Operations in Execution Group Phases can be
scheduled in the Opcenter APS environment. Only released Execution Group Phases can be scheduled using the
Sequencer.
When an Execution Group has phases and more phases are added, phase dependency is created between the
existing and newly created phases if there is a dependency between the Work Order Operations. This phase
dependency is deleted when the phase is deleted which results in unlinking the Work Order Operation from the
Execution Group.
 When Work Order Operations are added to an Execution Group Phase, all dependent Work Order
Operations must also be a part of the same Execution Group Phase.
Prerequisite
The Execution Group to which the Execution Group Phase to edit belongs is in Edit or ReadyForScheduling status.
Target User
Users with the Product Engineer or the Production Coordinator roles can perform this action.

Procedure
1. In the Execution Groups page, select the Execution Group to which the Execution Group Phase to be edited
belongs.
2. Click .
3. Click the Phases tab.
4. Select the Execution Group Phase that you want to update and click .
5. In the Update Execution Group Phase panel, set the following parameters:
Name The name of the Execution Group Phase.
Collect Documents If the checkbox is selected, during the execution of the Execution
Group Phase it will be possible to upload documents.
 This setting overrides the setting of underlying Work Order

Operations. Even if some underlying Work Order Operation
does not allow collecting Documents, at runtime will still be
possible to collect Documents for it when it will be executed
during the Execution Group Phase.
Estimated Duration Estimated duration necessary to execute the Execution Group Phase.
Estimated Start Time The date and time when the Execution Group Phase is expected to
start.
Note Not enabled if there is integration with Opcenter APS.
Estimated End Time The date and time when the Execution Group is expected to end.
Preferred Machine The preferred Machine on which the Execution Group Phase is
expected to be executed.
6. Click Save.
7.8.4 Linking Print Job Files to Execution Group Phases

When Work Order Operations are linked to an Execution Group, Execution Group Phases are automatically created
if required. In case of Additive Manufacturing you can choose to associate a Print Job File to any Execution Group
Phase.
Operators can also view historical data traced for the print job files and the Execution Group Phase details by
clicking the As Built tab from the Operator Landing page.
Prerequisites
• The Execution Group to which the Execution Group Phase belongs is in Edit or ReadyForScheduling status.
• The Work Operations associated with the Work Order Operations belonging to the Execution Groups had the AM
parameter selected.

Target User
Procedure
1. In the Execution Groups page, select the Execution Group to which the Execution Group Phase belongs.
2. Click Open.
4. Select the Execution Group Phase of interest.
5. Click Link PJF.
6. In the upper area, select a 3D Printer among those that are currently associated the Work Order Operations
belonging to the Execution Group and that have been associated with Print Job Files.
7. In the lower area, select the Print Job File of interest among those associated with the previously selected 3D
Printer.
8. Click Link.
Result
The Print Job File is displayed in the Linked PJF column and it can be unlinked selecting the phase and clicking
Unlink PJF.
7.8.5 Linking Work Instructions to Execution Group Phases

Work Instructions can be linked to Execution Group Phases to be used by Operators at runtime to get detailed
instructions about how to perform specific tasks on the product.
To discriminate if a Work Instruction is to be used for providing instructions or for data collection, the Work
Instruction Steps must be configured as Acknowledge or DataCollection type, respectively. The same Work
Instruction can be linked to more than one Execution Group Phase and to associate Work Instructions to dependent
Execution Group Phases, you need to associate them individually.
User Manual.
• Linking Work Instructions to an Execution Group Phase.
• Unlinking Work Instructions from an Execution Group Phase.
Target User
Prerequisite
The Execution Group Phase to be linked is in the Open status.
Linking Work Instructions to an Execution Group Phase

1. In the Execution Groups page, select the Execution Group which contains the Execution Group Phase to which
the Work Instructions need to be linked.
2. Click .
3. Click the Phases tab. Select the phase to which you want to link the Work Instruction and click .

4. Click the Work Instructions tab and click Link Work Instruction.
5. From the Link Work Instruction page, select the Work Instruction Association Type:
– Operation: the Work Instruction will be associated with the whole Work Order Operation;
– SerialNumber: the Work Instruction will be associated with all the Serial Numbers produced by the Work
– SerialNumberOnDemand: the Work Instruction will be associated only to some Serial Numbers produced by
the Work Order Operation (only for Serialized, FullSerialized and FlexibleSerialized Work Orders). The
Operator will select at runtime, the exact list of Serial Numbers to be associated.
6. Select one or more Work Instructions to be linked and click the Link button.
7. Additionally, you can link Work Instructions of different association types to the same Execution Group Phase.
Click Link Work Instruction again to further link multiple Work Instructions.
Unlinking Work Instructions from an Execution Group Phase

1. In the Execution Groups page, select the Execution Group which contains the Execution Group Phase from
which the Work Instructions need to be unlinked.
2. Click .
3. Click the Phases tab. Select the phase from which you want to unlink the Work Instruction and click .
4. Click the Work Instructions tab and select one or more Work instructions to be unlinked
5. Click Unlink Work Instruction.
7.8.6 Associating Powders to Execution Group Phases

When Work Order Operations are linked to an Execution Group, Execution Group Phases are automatically created
if required. In Additive Manufacturing context, you can choose to associate a Powder to any Execution Group Phase.
Prerequisites
• The Execution Group to which the Execution Group Phase belongs is in Edit or ReadyForScheduling status.
• The Work Operation type must be Setup3DPrinter (which has the property Load AM Powder set to true).
Target User
Procedure
1. In the Execution Groups page, select the Execution Group to which the Execution Group Phase belongs.
2. Click Open.
4. Select the Execution Group Phase of interest and click the AM Powders tab.
5. Click . In the Set Powder pane, the upper area displays the list of 3D Printers associated with the Process
Operation.


the 3D Printer.
7. Click Set.
7.8.7 Scheduling an Execution Group

After its creation, an Execution Group can be scheduled to be executed at a later time. This procedure sets the
Execution Group in ReadyForScheduling status.
In the case of integration with Opcenter APS, the Execution Group can be scheduled for execution using
the Sequencer, in the same manner as described for Work Order Operations. This is also true for Execution Groups
created on-the-fly during runtime.
 Only released Execution Groups can be scheduled using the Sequencer.
Prerequisite
The Execution Group is in Edit status.
Target User
Procedure
1. In the Execution Groups page, select the Execution Group that you want to schedule.
2. Click to schedule the Execution Group.
3. Click OK to confirm the operation.
Result
The system changes the Execution Group status to ReadyForScheduling.
7.8.8 Releasing an Execution Group

When an Execution Group has been created and some Work Order Operations have been linked to it, it is possible to
release it for production.
Work Order Operations cannot be linked to a released Execution Group. However, it is possible to unlink them.

Prerequisite
The Execution Group is in Edit or ReadyForScheduling status.
Target User
Procedure
1. In the Execution Groups page, select the Execution Group that you want to release.
2. Click the button to release the Execution Group.
3. Click OK to confirm the operation.
Result
The system changes the Execution Group status to New. The Execution Group can be started by an Operator in the
Operator Landing page.

How to Execute Work Orders
8 How to Execute Work Orders

Provided that you have completed the preparation necessary for production execution, you can proceed to execute
your Work Order.
Executing a Work Order "full circle" means starting and completing its Work Order Operations. Depending on the
situation, it may be necessary to perform various operations "in between" so that production flows smoothly and
Work Order completion can be attained: for example, you may need to pause a certain Work Order Operation and
then resume its execution. The exact workflow is determined by the dependencies among the Work Order
Operations.
It is possible to set Work Order Operations along a sequence so that they cannot be started before the Work Order
Operations preceding them have been started or completed. If the configured dependencies permit it, Work Order
Operations can be started out of sequence.
 In case of dependencies between Work Order Operations belonging to different Work Orders, the runtime
behavior is driven by the source Work Order Operation. If the required conditions are not satisfied, the
Operator will be unable to proceed with the production execution. For more information, see Runtime
Behavior in case of Dependencies between different Work Orders.
The procedures for starting and completing Work Order Operations depend on a variety of factors: therefore, the
procedures you must perform will not necessarily always be the same.
Both the start and the completion of a Work Order Operation can be performed automatically, thanks to
appropriately configured Work Operations that drive the Work Order Operation's behavior: for more information,
see Configuring Work Operations.
 Execution Groups In Production Execution

If your system also adopts Execution Groups for production execution, see How to Execute Production on
Execution Groups.
Target User
Users with the Operator role can perform this operation.
Prerequisite
The Work Order has been released (New status).
Working Environment
The system provides a dedicated page for Production execution: this page is known as the Operator Landing Page.
In Preparation to Executing the Main Workflow

Prior to executing the Main Workflow, it is strongly suggested that you:
• Preview the content of Work Order Operations, Work Order Steps and Execution Groups.
• Preview any Document files in attachment.
Main Workflow
1. (Optional) Load the Containers. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)

Navigation of the Operator Landing Page during Production Execution
2. Start Work Order Operations one at a time.

3. Manage Work Order Operations one at a time.
4. Complete Work Order Operations one at a time.
5. (Optional) Unload the Containers. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)
In addition to the operations listed above in the Main Workflow, while executing a Work Order Operation or after
completing it, you may need to perform some of the following additional operations:
• Managing Non-Conformances
• Managing Additive Manufacturing-related Activities.
Offline Production Execution
Alternatively, you can also execute Work Order Operations in Offline mode, that is, in production contexts where
there is no network connectivity. This requires that you check-out the set of Work Order Operations to be executed
from a mobile device, which in turn must be equipped with a dedicated App.
 The App to manage Offline production execution from a mobile device must be custom implemented
according to specific customer project's requirements.
Checked out Work Order Operations are indicated as locked and cannot be managed by the Operator from the
Operator Landing page, until they are checked in.
From Opcenter EX DS you can display the Work Order Operations belonging to a specific Offline Session and you can
also manage any upload and check-in of production execution data. For more information, see How to Execute
Production In Offline Mode.
8.1 Navigation of the Operator Landing Page during Production

Execution
The Operator Landing Page is the main environment in which you will move to carry out production execution. It is
from here that you will be able to start your Work Order Operations, as well as perform other activities.
 • The Operator Landing Page provided with the Siemens_OPC_EXDS_AM UI Application contains only a
subset of the commands and buttons mentioned in this section of the manual.
• Operating on Work Order Operations or Work Order Steps that have already been started entails
accessing another screen: see Managing Work Order Operations.
Here is what you need to know to navigate this environment and interpret what is displayed on screen, as well as
adapt its contents according to your needs.

 High Automation Operator Landing Page

It is also possible to follow what is happening on screen on the basis of the Machine that has been selected
for production execution: for details on the High Automation Operator Landing Page, see Managing
Automatically Executed Work Order Operations.
Indicators Visible on Tiles

The tiles presented in the Operator Landing Page may contain dedicated indicators related to various aspects of
production execution.
Consult the legend below to comprehend their meaning.
Work Order Operation Tiles
The following indicators allow you to interpret the current status of a Work Order Operation displayed in tile format:
for a description of the corresponding states, see section Work Orders, Work Order Operations and Work Order
Steps in the Opcenter Execution Discrete Product Overview.
There are also some indicators that refer to other elements placed in relation to Work Order Operations: Work
Operations, Non-Conformances, Containers.
Indicator Meaning
Open
Ready
Active

Indicator Meaning
Partial
Future Hold
Complete
Not Executed
The Work Operation is of type Dynamic.
The Work Order Operation can be skipped.
The Work Operation is of type Optional.
A Non-Conformance is present on the Work Order Operation.
The Work Order Operation is associated with Containers.
In addition, if the Result Management configuration key has been enabled, the tile corresponding to a Work Order
Operation will show (between square brackets and with the symbols below) how many of its Material Tracking Units
have OK Results, NOK Results and no Results declared.
Here is an example: for Quantity, of the 10 MTUs that have been completed, 4 have Result OK, 2 have Result NOK
and 4 have no Result declared.
Material Tracking Unit (or Serial Number) Tiles

Indicator Meaning
A negative Result has been declared on its previous execution.
 NOK Indicator in Other Contexts

This indicator is used also in other screens, and not only in the
Operator Landing Page. It is a global indicator that is to be
interpreted as follows:
• If displayed on a Work Order tile in the Work Orders page or the
Work Order Details page, it means that a negative Result has
been declared on at least one Work Order Operation belonging to
the Work Order.
• If displayed on any Material Tracking Unit tile in other pages, it
means that a negative Result has been declared on at least one
Work Order Operation belonging to the Work Order executed to
produce the MTU.
A positive Result has been declared on its previous execution.
The MTU (or Serial Number) was re-executed after a negative Result was
declared on its previous execution.
Dependency Graph
The Dependency Graph is a graphical representation of the Dependencies that exist between the Work Order
Operations belonging to the selected Work Order (or Work Order Operations belonging to different Work Orders). Its
purpose is to guide users in managing runtime execution.
If desired, you can customize the Operation Dependency Graph to satisfy your needs:

1. To access the Operator Landing page, click the Operator Landing tile in the home page.
• In the Quick Search box on the left, type the Work Order ID (or part of it): the system displays the Work
Order Operations belonging to the Work Orders matching your search criteria.
• Type the name of the Machine, a Serial Number or a Container in the search box on the right: the system
displays all the Work Order Operations that match your search criteria and can be started.
3. Select the Work Order Operation of interest: an Operation Dependency graph, displaying all Work
Order Operations belonging to the same Work Order and the related Dependencies, guides you in managing
runtime execution. Completed Work Order Operations are displayed in green.
For more information on how to manage runtime execution, see Runtime behavior in case of dependencies
between different Work Orders.

Layout and Content Troubleshooting

If you find that the layout and/or content of the Operator Landing Page are not as expected (or do not satisfy your
specific needs) as an Operator, then the Product Engineer must intervene to set the appropriate Runtime
configuration keys so that the elements you need to work on are displayed.
If you do not see... Then the Product Engineer must set ....
both Work Order Operations and Execution Groups the Show Execution Groups in Operator
Landing page configuration key.
only those Work Order Operations that can be executed for the Show only Work Order Operation ready to
a selected Work Order be started configuration key.
the details of a Work Order Operation immediately after it the Automatic Redirect to details configuration
has been started key.
the Work Order Operations filtered according to the the Filter by Users assigned to Work Order
logged User Operations configuration key.
 The exact behavior of the filter will

depend on the value of the Filter WOOps
by logged User and show free
WOOps key.
both the Work Order Operations assigned to the currently- both the Filter by Users assigned to Work Order
logged User and those that are not yet assigned to any Operations and Filter WOOps by logged User
User and show free WOOps configuration keys.
8.1.1 Joining and Leaving Teams at Runtime

Teams are groups of Users that can be created to perform production operations together.
This procedure allows an Operator to join and/or leave a Team at runtime from the Operator Landing page.
Additionally, the Product Engineer or the Production Coordinator can directly assign Users to Teams.
Joining a Team
1. In the Operator Landing page, click Join Team.
2. If the logged User is currently active on any Work Order Operation:
• The message Confirm to show active Work Order Operations is displayed. Click OK to display the list of
active Work Order Operations.
• If possible, click Punch Out and confirm the operation to pause all the Work Order Operations at once.
3. In the Teams page, select the Team to join and click Join.

 • For active Work Order Operations, when the last Team member exits the Team, the status of all the
active Work Order Operations changes to Pause.
• The User/Team History label displays all the Users active on the Work Order Operation and their
individual association with Machines and Serial Numbers or Batches.
Leaving a Team
In the Operator Landing page, click Leave Team. The Leave Team button is disabled and the Join
Team button is enabled again.
8.1.2 Runtime Behavior in case of Dependencies between different Work

Orders
When defining dependencies between Work Order Operations of different Work Orders, bear in mind that Runtime
execution behavior can vary according to the combination of:
• dependency type: After Start, After End and Partial After End (for After End dependencies from/to a different
Work Order created with the Wait for full completion parameter set to false)
• Work Order Operation type: Auto-Start, Auto-Complete, Optional and Skippable.
In case of external dependencies, the behavior is driven by the Source Work Order Operation (which belongs to
another Work Order).
The Operation Dependency graph (displayed in the Operator Landing page) is designed to guide you in managing
runtime execution.
Work Order Operations belonging to other Work Orders are shown bearing the name of the Work Order to which
they pertain.
In the image above, Work Order Operation OP03_CC02 has an After Start dependency with 30-OP03_CC. This
means that if Operation 30-OP03_CC is not started, OP03_CC02 cannot be started as well.
The "X" next to the arrow indicates that one or more of the required conditions (see below) are not satisfied.
As a result, the Operator will be unable to start the Work Order Operation: the Start button remains disabled.
Conditions

Dependencies that block production execution are characterized by an "X".

This may occur if the dependencies are between Work Order Operations belonging to different Work Orders and one
of the following conditions applies:
• Status of the source Work Order Operation is Open and Dependency Type is After Start.
• Status of the source Work Order Operation is Future Hold, and its previous status was Open, Dependency Type
is After Start.
• Status of the source Work Order Operation is neither Complete nor Not Executed, Dependency Type is After
End and Wait for full completion is not set.
• Source Work Order Operation did not produce any Final Material, Dependency Type is After End and Wait for
full completion is not set.
8.1.3 Managing Automatically Executed Work Order Operations

The Opcenter Execution Discrete UI Application includes a page to be used to monitor Work Order Operations that
are automatically executed on a specific machine, and to contribute to their completion providing the required
data. In addition, if necessary, the user can intervene in the automatic execution of the Work Order Operation
performing the manual actions that are usually performed by the Operator from the Operator Landing page.
System Configurators can change the layout of the High Automation Operator Landing page to enable the display
of runtime tasks, similar to what is provided by the standard Operator Landing page.
For more information, see section How to Configure Runtime Screens of the Opcenter Execution Discrete Installation
and Configuration Manual.

1. In the home page, click the High Automation Operator Landing tile.
2. Select the machine to be monitored and then click the Set Machine button at the bottom of the page: the
system displays the High Automation Landing Page.
Note The page is displayed empty by default, and it is populated as soon as data relative to the Work Order
Operation execution are available.
3. To display data relative to another machine, click the Change Machine button, otherwise the focus of the
page will be maintained on the previously selected machine also after closing and reopening the page.
Working Environment

• Header Bar - Displays the main details of the Work Order Operation. To display additional information on the
Work Order Operation parameters, click the related labels. The and icons display the status of the
connection of the machines. The status of the machine is identified by the IsActive property. On the Header Bar,
you can click on the following labels:
• Machine, to display all the Machines active on the Work Order Operation and their individual association
with Serial Numbers or Batches and Users;
• Active Users/Teams, to display all the Users/Teams active on the Work Order Operation and their
individual association with Machines and Serial Numbers or Batches;
• Serial Number / Batch Id, to display all Serial Numbers / Batch IDs active on the Work Order Operation
and their individual association with Machines and Users.
• Center Zone - Displays the assembled or consumed Materials during the execution of a Work Order Operation.
You can enter the Serial Number, Batch ID or the Barcode of the Material Tracking Units to be consumed by the
The quantity of the Material Tracking Units is updated as they are being consumed. When the Material is
assembled the status changes to .
• Right Zone - Displays the Documents associated with the Work Order Operations and their related entities. To
expand the document to full screen, click the preview or the dedicated icon. The available documents are
displayed in the following tabs:
• Operation, displaying the documents associated with the current Work Order Operation.
• Product, displaying the documents associated with the Work Order to which the current Work Order
Operation belongs.
• Parts, displaying the documents associated with the Materials consumed by the current Work Order
Operation, if available.
• Bottom Bar - Displays a set of buttons to perform manual activities on the current Work Order Operation.
Procedure
1. When the Work Order Operation is started, the system populates the center zone with the Materials to be
consumed in order to execute the current Work Order Operation. When a new item is displayed, insert the
related Serial Number either manually or through a scanner.

Previewing Work Order Operations, Work Order Steps and Execution Groups
 Inserted Barcodes must be verified and validated by the system before being accepted. If the Barcode
verification succeeds, the Material Tracking Unit is consumed and error messages are displayed if they
fail verification.
2. Repeat step 1 until all required Materials are inserted and the Work Order Operation execution can be
completed.
Although the High Automation Operator Landing is dedicated to managing automatically-executed Work Order
Operations, in some cases, you may need to intervene manually on the execution of the current Work Order
Operation by clicking the buttons displayed in the bottom bar:
• Start to start the current Work Order Operation.

• Pause to pause the current Work Order Operation.
• Complete to complete the current Work Order Operation.
• Add Document to add a Document at runtime, if this has been set while creating the Work Order Operation.
• Defects to declare a Quality Non-Conformance.
• Change to declare a Change Non-Conformance (Change Request). (This functionality is not available in
• Logistic Requests to declare Logistic Requests. (This functionality is not available in
• Notes to add Notes to the Work Order Operation. (This functionality is not available in
• Join Team to join a Team. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)
• Leave Team to leave a Team. (This functionality is not available in the Siemens_OPC_EXDS_AM UI
Application.)
• Change Machine to change the focus from the currently-selected Machine to another and subsequently
view its data.
8.2 Previewing Work Order Operations, Work Order Steps and

Execution Groups
Before starting production execution, you may need to preview the content of Work Order Operations, Work Order
Steps and Execution Groups, to understand the activities that must be carried out during execution.
Work Order Operation details contain information on the Operations to be executed. They may include one or more
of the following:
• A set of instructions including precautions, warnings, and special notes. If they are available in PDF format, a
preview can be displayed in a dedicated pane.
• A list of Materials associated with a Work Order Operation which can be assembled/consumed.
• A list of Tools associated with a Work Order Operation which can be used.
• A list of Work Instructions containing Data Collection sections associated with a Work Order Operation for which
you must provide values.
Target User

Previewing Document Files
Users with the Operator role can perform this action.
Prerequisites
• The status of the Work Order Operation or Work Order Step to be previewed is Open.
• The status of the Execution Group to be previewed is New.
Procedure
1. In the Operator Landing page, select either a Work Order Operation or an Execution Group.
2. Click Show Details.
3. In the Operator Task List or Operator Details Step page, select the item for which you want to see details.
 • The Not ready icon indicates that the task in question has not been initialized. It will be done on-
the-fly by the system upon start.
• If you are previewing the content of an Execution Group, all tasks, being they related to a Work Order
Operation or a Work Order Step, will be displayed in a flat list. Refer to the second header bar to have
more details about the selected item.
8.3 Previewing Document Files

The Document Previewer available in the Operator Landing Page makes it possible for users to preview any
Documents that have been attached to a Work Order Operation or to a related entity.
Document visualization depends on its file format: see Supported File Formats.
Procedure
1. In the Operator Landing Page, after applying an appropriate filter, select the Work Order Operation for which
you want to preview its attached Document.
2. Operating on the Bottom Bar, click Document Preview: this opens the Document Previewer in the Right
Zone of the Operator Landing Page, displaying the Document for consultation.
3. The lower area displays the list of available documents, grouped by the entities to which they are associated.
Only the groups that contains documents are displayed. Select the desired group according to the following list:
• Operation for the documents associated to the current Work Order Operation.
• Step for the documents associated to the current Work Operation Step.
• Runtime for the documents associated to the Serial Numbers started by the current Work Order
Operation.
• Product for:
• the documents associated to the Final Material produced by the current Work Order Operation;
• the documents associated to the the active Material Tracking Units produced by the current Work
Order Operation.
• Parts for the documents associated to the Materials consumed by the current Work Order Operation.
• Tools for the documents associated to the Tools used by the current Work Order Operation.
4. Click the preview or the icon to expand the document to full screen. Click to maximize the details area.
Supported File Formats

The following file formats for Documents are supported by the Document Previewer in Opcenter Execution Discrete:

Loading Containers
File Types Supported File Formats
Non-video files with preview • .txt

• .svg
• .jpg
• .png
• .pdf
Video files with preview • .mp4

• .ogg
• .webm
Other file formats, such as:
• .doc
• .csv
• .xml
• .zip
are not displayed by the Document Previewer, but can be downloaded.
8.4 Loading Containers

To properly manage the execution of a Work Order Operation, it may be useful to associate it with one or more
Containers where consumed or produced Material Tracking Units will be loaded.
It is possible to load multiple Material Tracking Units within the same Container provided that the maximum
quantity of the Container is not exceeded and that all loaded MTUs belong to the same Material: as soon as the first
MTU is loaded, only remaining MTUs that belong to the same Material can be subsequently loaded, unless the
Container is completely unloaded (in this case any other MTU can be loaded).
If the Work Order Operation includes the production of multiple pieces, it is possible to manage only a subset of
them through Containers. For example, if three pieces must be produced, you can load two Serial Numbers into the
Container and manage the remaining Serial Number either without Containers or through another Container.
Containers, after being associated to a Work Order Operation, can be subsequently unloaded or loaded with
additional MTUs, provided that they have not been started yet. While, if the Container already contains completed
MTUs, it is necessary to unload them before loading new MTUs to be consumed or produced.
Work Order Steps where present, will also be associated with the same Containers and loaded with the same MTUs
as the Work Order Operation (except TransferBatch and FlexibleBatch production type).
Once the association between Work Order Operation and Container is established, the ID of the Container (and not
that of its content) is used to perform any operation until the content is unloaded.
Work Order Operations already associated with Containers can be easily identified in the Operator Landing page,
since they display the icon.
 Containers can also be loaded by the Production Coordinator from the page dedicated to Container
configuration.

Loading Containers
Prerequisites
• The Work Order Operation has not been started yet.
• The Container satisfies either of the following conditions:
• It is compatible with the Material to be consumed or produced by the Work Order to which the Work
Order Operation belongs.
• It is not compatible with any specific Material.
Procedure
1. In the Operator Landing page, select the Work Order Operation of interest.
2. Click the Load Container button.
3. In the Container step of the wizard select the Container to be associated to the Work Order Operation. The
system displays the Containers:
• associated to the Work Order to which the Work Order Operation belongs. If available these Containers
are displayed on top with a specific indicator in the tile.
• for which no compatible Material has been defined and not associated to any Work Order.
• compatible with the Final Material of the Work Order to which the Work Order Operation belongs and not
associated to any Work Order.
• whose maximum quantity has not already been reached.
• previously associated with the Work Order Operation (if they have already been partially loaded with
MTUs, the Quantity parameter displays the corresponding value).
4. Click Next.
5. Load the Material Tracking Units depending on the production type:
• For Serialized or FlexibleSerialized production type; in the Serial Number step of the wizard, select the
Serial Numbers to be loaded into the selected Container: the system displays the to be produced
Materials that have not been started, but after selecting the first one, only other Serial Numbers
belonging to the same Material can be loaded.
Materials can also be loaded based on the quantity, without selecting or specifying the Serial Numbers.
In the Serial Number step of the wizard, insert the desired number in the Number of Serial Numbers to
load field. The Max Quantity field displays the maximum Serial Numbers that can be loaded into the
Container. The quantity displayed could either be the maximum capacity of the Container or the
available quantity of the selected Work Order Operation, which ever is lower.
• For FlexibleBatch and TransferBatch production type, in the Quantity step of the wizard, type the
quantity to be loaded. In the case of Dynamic Work Order Operations, the quantity that can be loaded
can be more than or equal to the maximum capacity of the Container.
• In case of FullQuantity and FullSerialized production type no selection is necessary, since the
Container will be automatically loaded with the quantity of the Final Material specified in the Work
Order.
6. Click either of the following:
• Load, to associate the Container to the Work Order Operation and load it with the selected MTUs.
• Load and Start, to associate the Container to the Work Order Operation, load it with the selected MTUs
and proceed with the Start.
Note Containers that contain completed MTUs, cannot be started until these MTUs are unloaded.
7. (Only if you have clicked the Load button) If necessary, repeat steps 2 to 6 to associate and load additional
Containers.
 • Containers in the Active state are visible (and available for linking) to all the other Work Order
Operations of the Work Order.
• For Work Order Operations, where the available quantity of Material Tracking Units required by the
operation is already loaded into the Container; the Containers can be loaded with zero quantity to
continue the operation. In such cases, the Load button is enabled.

Starting Work Order Operations
8.5 Starting Work Order Operations

Executing a Work Order entails starting at least one Work Order Operation.
When starting a Work Order Operation, the main discriminant to keep in mind is the Production Type of the Work
Order to which it belongs. The Production Type determines the procedure to follow to start the Work Order
Operation, the resulting behavior once the Work Order Operation has been started and the possibility of taking
advantage of certain functionalities.
Keep in mind that the Production Type of the Work Order, as well as other configurations, will affect what is
displayed on screen and the procedure that you must follow to start your Work Order Operation.
In addition, according to the configurations that have been performed during engineering, it is possible that you
may need to perform additional actions and take into account certain constraints to start the Work Order Operation
with success: for more information, see Special cases and constraints when starting a Work Order Operation.
If groups of Alternative Work Order Operations have been defined, you can decide which Work Order Operations to
start according to the available paths. Keep in mind that, if you choose an Alternative Work Order Operation to be
executed, all the other Work Order Operations in the original path will necessarily be skipped.
 It is possible to automatically start a Work Order Operation by Machines or Workcenters, provided that
there is integration with Opcenter Connect MOM as described in How to Automatically Start Work Order
Operations in Opcenter Execution Discrete Installation and Configuration Manual.
The automatic start will be successfully executed if no other Work Order Operations (of the same category)
are queued on the same Machine.
Preliminary Configurations
A different start behavior is possible, according to the configurations defined during the engineering phase. In
particular:
• Through the joint adoption of Work Operations and appropriate Work Order Operation configuration, upon
starting a Work Order Operation, it is possible to:
• automatically complete the Work Order Operation in question, provided that it has been set to Auto-
Complete.
• automatically start all of its successive Operations that are in dependency AfterStart.
• automatically execute what is described in both of the bullets above.
• Setting the Result Management key makes it possible to enable Result management on the start of a specific
Work Order Operation when producing a particular Batch or Serial Number (Material Tracking Unit).
Prerequisite (valid only when using Containers)

If you want to use Containers, they must be associated with the Work Order Operation and loaded with Material
Tracking Units, before starting the Work Order Operation.
 • If the Work Order Operation has been started immediately after loading the Container, you will be
automatically redirected to step 2 of the procedure below.
For FullQuantity and FullSerialized production types in which either a single Workcenter/Machine or
no Workcenter/Machine is involved, the entire procedure can be skipped, as no parameters must be
manually set.
• For TransferBatch and FlexibleBatch production types, the Containers in the Active state can be
associated to other Work Order Operations, provided that these Operations do not have any
dependencies on other Operations in the Work Order.

Procedure
1. In the Operator Landing page, select the Work Order Operation (or Alternative Work Order Operation, if
present) to start and then click Start on the bottom bar: this opens the Start Work Order Operation panel.
2. (only if Electronic Signature validation has been enabled) Type your password, some notes and then
click Validate User.
3. Perform the actions required by the system. Here is a list of available actions, but as they vary depending on the
characteristics of the involved Work Order Operation, you may need to perform only a subset of them or, in
some cases, none whatsoever: for example, if the Work Order Operation has been associated with a single
Workcenter/Machine and it requires the production of its entire quantity.
Action Must be performed when.... Steps to be performed
Equipment Selection Several Workcenters/Machines 1 Select the Workcenter/Machine to be used

are associated to the Work to execute the Work Order Operation.
Order Operation.
 Currently-locked Workcenters/
Machines display the icon in
their tile and cannot be selected.
2 (if Setpoints have been configured for the

selected Workcenter/Machine and their
editing is permitted) If necessary, edit the
Setpoint(s) according to your needs.
Quantity Setting The Work Order Operation 1 In the Quantity field, enter the Material
belongs to either quantity on which you want to start to
the TransferBatch or work. The Max. Quantity value available to
FlexibleBatch production type. start the Work Order Operation with
Containers is the residual quantity that is left
over after the Containers are loaded with the
Material Tracking Units.
2 (Only if permitted by the Work Order
Operation settings) If necessary, modify the
quantity to be produced until the Target
Quantity is set as no longer editable.

Serial Number Selection The Work Order Operation In the Select Serial Numbers area,
belongs to either which displays the tiles of the Serial
the Serialized or Numbers (MTUs) that can be produced by
FlexibleSerialized production the selected Work Order Operation
type. (including - if Result Management has been
enabled - any Serial Numbers that have
been executed previously, but for which a
negative Result has been declared and need
to be re-executed), select the Serial
Numbers that you want to produce.
If the listed items do not satisfy your needs,
you can:
• Select other existing Serial
Numbers.
In the Input Serial Number field,
click the button, make your
selection and then click the
button.
• Generate new Serial Numbers
manually.
In the Input Serial Number field,
type the Serial Numbers you
want to generate and then click
the button.
• Generate new Serial Numbers
automatically according to the
template associated to the
Material.
In the Auto Generate Serial
Number field, enter the amount
of Serial Numbers to be
generated and then click the
button.
 To include all the listed Serial

Numbers, select the Select /
Deselect All check box.
If a Serial Number has been
previously started (for example, by
another User), the Started by
Another User indicator is displayed
in its tile.


If Result Management has been
enabled, depending on the Result
declared on its previous execution,
two indicators will be displayed
in the selected Serial Number's
tile: NOK indicates a negative
Result, whereas Repeat
indicates the strategy adopted
(that is, the Serial Number's re-
execution).
4. Click Start.
 If more than one Machine is associated to the Work Order Operation, you can distribute the workload as
preferred, starting execution on different Machines at different times. This is permitted for Work Order
Operations belonging to Work Orders of the Serialized, FlexibleSerialized, TransferBatch
and FlexibleBatch production types.
What to do next
After starting a Work Order Operation, you can display its details and manage them. Later, you can complete its
execution.
 If the Automatic Redirect to details configuration key has been set, the Details page is automatically
displayed.
8.5.1 Special Cases and Constraints When Starting a Work Order

Operation
The following sections provide dedicated information for special cases and constraints that you may encounter
when attempting to start a Work Order Operation, in addition to the standard actions to be performed on the basis
of the Production Type of the Work Order Operation.
These special cases include:
• Optional execution.
• Starting a Work Order Operation in the presence of Setpoints.
• Starting a Work Order Operation in the presence of Inbound Interlocking Checks
• Starting a Work Order Operation in the presence of Work Order Operations/Steps associated with Human
Resources.
• Starting a Work Order Operation when it is associated to a Container.
Optional execution
A Work Order Operation can be configured to be executed optionally by setting the Optional parameter of the
associated Work Operation. Depending on the Production Type of the Work Order Operation, the system exhibits a
specific runtime behavior and the actions that you can perform will differ.

In all cases, the system includes the optional Work Order Operation in the list of Work Order Operations that can be
executed: in addition to the optional Work Order Operations, the system displays the successive Work Order
Operations to be executed. You can choose to manually execute the optional Work Order Operation by clicking
Start. If you choose to skip the optional Work Order Operation, it will assume status Not Executed and the
elected Work Order operation will be executed.
Production Type Action
FullQuantity/FullSerialized You can start the optional Work Order Operation with full
quantity.
TransferBatch You can start the optional Work Order Operation with partial
quantity.
Serialized You can start the optional Work Order Operation with partial
Serial Number.
Setpoints
If Setpoints have been defined for Machines and the Setpoint Variables are linked to Automation Node
Parameters, the related values are automatically transmitted to the Machine when the Work Order Operation is
started on that Machine.
If properly configured, you can edit the Setpoint Variables at runtime and check the transmitted variables, along
with their values.
Inbound Interlocking Checks

If one or more active Inbound Interlocking Checks that were defined during the creation of the Work Order to which
the Work Order Operation to be started belongs fails, you will not be allowed to start the Work Order Operation (or
Step). An error message for each of the failed Inbound Interlocking Checks is displayed and this information is
logged into the system in the Interlocking Check History page.
To see the details about the Interlocking Check outcome, click the ITLK Check History button in the Operator
Landing page or from the Details page.
Human Resources
In case of Work Order Operations (or Steps) associated with Human Resources, and consequently requiring specific
Skills to be started, some constraints must be taken into account to properly start them. In detail, if the Human
Resource includes:
• a single Certification possessed by a single user, any user with the proper Certification and Skills can start the
related Work Order Operation or Step.
• one or more Certifications possessed by many users, only teams including a list of users with the proper
Certifications and Skills can start the related Work Order Operation or Step.
Containers
If the Work Order Operation is associated to a Container, the same Container (except TransferBatch and
FlexibleBatch production type) and MTUs are available to the Work Order Steps.

Managing Work Order Operations
8.6 Managing Work Order Operations

When executing Work Orders, you can perform various activities on a Work Order Operation previously started.
Runtime management of Work Order Operations is a complex procedure that depends on the various parameters
set during their creation. There is no set workflow that must be followed: it may consist of several independent
steps without a fixed order.

In the Operator Landing page, select the Work Order Operation that is currently active and then click the
Show Details button on the bottom bar.
 If the Automatic Redirect to details configuration key has been set, the page is automatically displayed
after starting a Work Order Operation.
Environment Description
• Header Bar - Displays the details of the current Work Order Operation
• Step List - If the current Work Order Operation is divided in several Steps, the Step List displays them vertically.
Otherwise, the Step List is not displayed.
• Task List - If the current Work Order Operation (or its active Step, if it is divided in steps) has more than one task
to be performed during its execution, the Task List displays them vertically. Otherwise, the Task List is not
displayed.
• Center Zone - Displays the elements needed to perform the current Task.
• Right Zone - Upon clicking the Document Preview button on the bottom bar, displays the Documents
associated to different entities involved in the current Work Order Operation or Step.
• Bottom Bar - Displays a set of buttons to perform various activities on the current Work Order Operation or
Step.
Operations Available in the Header Bar

The top Header Bar displays the details of the current Work Order Operation.
On the Header Bar, you can click the Active Users label to display all the Users active on the Work Order Operation
and their individual association with Machines and Serial Numbers or Batches.
Operations Available in the Step List

If the selected Work Order Operation contains Steps, then the left zone will display the Work Order Operation as a
tile, with a stack of its Steps underneath it. By clicking the individual tiles, you can perform the following actions:
• Start a Work Order Operation.
• Pause a Work Order Operation.
• Complete a Work Order Operation.
Start and Pause can also be performed on Work Order Steps, even if in this case some parameters cannot be set
since they are inherited from the related Work Order Operation.
 Steps can only be completed according to the configured AfterEnd sequence.
Operations Available in the Center Zone

The content of the center zone depends on the task to be performed on the current Work Order Operation/Step.
Refer to Managing Tasks for Work Order Operation/Step Progression for details.
Operations Available in the Right Zone

Upon clicking the Document Preview button on the bottom bar, the right zone displays the preview of the
documents associated to the various entities involved in the execution of the current Work Order Operation/Step.
Operations Available in the Bottom Bar

Click the following buttons:
• Start to start the current Work Order Operation.

• Pause to pause the current Work Order Operation.
• Skip to skip the current Work Order Operation, if it has been configured as Skippable during its creation:
• Complete to mark the current Step as completed, if the Work Order Operation is divided into Steps. This
button is available only if you are using the Operator Details page for Steps.
• Add Document to add a Document at runtime, if this has been set while creating the Work Order Operation.
• Itlk Check History to see the details about the outcome of the Interlocking Checks related to the current
Work Order Operation, if any. (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Notes to add Notes to the Work Order Operation. (This functionality is not available in
• Defects to declare a Quality Non-Conformance.
• Change to declare a Change Non-Conformance (Change Request). (This functionality is not available in
• Execution Groups to manage Execution Groups at Runtime.
• Logistic Requests to declare Logistic Requests. (This functionality is not available in
• Join Team or Leave Team to manage Teams. (This functionality is not available in

• N-P Activities to manage non-productive activities. (This functionality is not available in

• Document Preview to view the Documents attached to the selected Work Order Operation.
• Print Label to manually trigger the printout of specific labels previously configured. For more information,
see section Integrating Opcenter Execution Foundation Apps in the Opcenter EX DS Solution in the Opcenter EX
DS Installation and Configuration Manual.
• Change SN to change Serial Numbers during production. (This functionality is not available in
• Genealogy to display historical data about the Work Order in progress.
• Freeze Target Quantity to set the desired Target Quantity in case of Work Operations of type Dynamic.
• Close Flex WO to close a flexible Work Order. (This functionality is not available in
• Load Container, to associate a Container to a Work Order Operation and load it with Material Tracking
Units. (This functionality is not available in the Siemens_OPC_EXDS_AM UI Application.)
• Unload Container, to unload the Material Tracking Units inside a Container. (This functionality is not
available in the Siemens_OPC_EXDS_AM UI Application.)
• External Integration, to open an external system web UI with the Work Order Operation parameters.
 According to their prerequisites, some buttons might be disabled.
What to do next
After managing a Work Order Operation, you can complete it.
8.6.1 Managing Tasks for Work Order Operation or Step Progression

In Opcenter Execution Discrete, dedicated Tasks make it possible for users to manage the principal elements
involved in Work Order Operation/Step progression with ease.
The available Tasks concern:
• the Work Instructions related to the progression of the Work Order Operations, Work Order Steps or Execution
Group Phases, with the possibility of runtime data collection.
• the Tools to be used to execute a specific Serial Number or Batch during the Work Order Operation’s (or Work
Order Step’s) progression.
• the Materials or Batches and the relative quantities that are to be consumed/assembled/disassembled for
producing a specific Serial Number or Batch.
• quality-related measurements or inspections on specific production contexts (Work Order Operations /Steps),
produced Materials and execution Equipment.
• transferring the Print Job Files and Serial Numbers during Work Order Operations execution of type Additive
Manufacturing.
• the additional Co-Product and By-Product Materials that are produced as a result of production.
• loading the Powder into the associated 3D Printer during Work Order Operations dedicated to 3D printing
processes.
The aforementioned Tasks are carried out in parallel by default, but can be configured otherwise, if desired.
Procedure

1. From the Operator Landing page, after applying a filter appropriate to your needs, select the Work
Order Operation of interest from those displayed and click Show Details on the bottom bar to view its
details page. If you are interested in operating on a Work Order Step, select and open the Work Order Operation
to which it belongs.
2. Operating on the Task bar on the left side of the screen, which displays all available Task instances for the
selected element, select the Task instance according to the aspect of runtime behavior configured for the
selected Work Order Operation (or Work Order Step) that you want to manage: depending on your choice, the
content of the details area will vary.
 If only one task is available, you do not need to perform any selection, as the system automatically
displays the Details area.
If you want to manage... Then select The details area of the screen will
Task ….. display the following elements to be
managed...
The actions to be read, performed and Work The Work Instructions related to the
acknowledged by the Operator, as well as the data Instruction execution of the Work Order
to be collected and entered into a Data Collection Operations, Work Order Steps or
form contained in the Work Instruction during the Execution Group Phases.
execution of the Work Order Operations, Work
Order Steps or Execution Group Phases.
How a Tool or Substrate must be used during the Tool Usage The Tools or Substrates involved in
execution of the selected Work Order Operation (or the Work Order Operation’s (or Work
Substrate
Work Order Step) Order Step's) execution.
Usage
How a Serial Number or Batch must be consumed Material The Serial Numbers or Batches
during the execution of the selected Work Order Consumpti involved in the Work Order Operation’s
Operation (or Work Order Step) on (or Work Order Step's) execution.
The steps to be performed for a quality inspection, Quality Forms to insert measurement and
such as a measurement or a visual inspection Inspection visual inspection data. The panels
opened differ according to the
involved production type.
This functionality is not available in
the Siemens_OPC_EXDS_AM UI
Application.
The steps to be performed when transferring Print Print Job The Print Job Files, the associated
Job Files to 3D Printers. File Machines and the Serial Numbers (if
Transfer any) that can be used during Work
Order execution of type Additive
Manufacturing.

If you want to manage... Then select The details area of the screen will
Task ….. display the following elements to be
managed...
The steps to be performed when transferring CNC Part The Part Programs, the associated
Programs to Machines Program Machines and the Serial Numbers (if
Transfer any) that can be used during the
execution of Work Orders of type CNC.
The steps to be performed when co-producing Material To configure Material of type Co-
Materials of specification type Co-Product or By- Production Product and By-Product that can be
Product. used to produce additional Materials.
The steps to be performed when loading Powder Load The Powder and the quantity to be
into the 3D Printer. AMPowder loaded into the 3D Printer involved in
on 3D the Work Order Operation's execution.
Printer
3. Specify (or execute) the actions to be performed to complete the selected Task in relation to the runtime
behavior you want to be adopted during the execution of Work Order Operations, Work Order Step or Execution
Group Phases.
4. Click the appropriate button to confirm.
8.6.1.1 How to Manage Work Instructions

Work Instructions are specific instructions for the Operator that may require an acknowledgement or the insertion
of values.
Depending on the content of the Work Instruction (Acknowledge and/or DataCollection steps), the system
behaves differently.
Moreover, in the specific case of Work Instructions containing DataCollection steps, the following configurations
are possible:
• Work Instructions associated with the entire Work Order Operation or Step;
• Work Instructions associated with all the Serial Numbers produced by the Work Order Operation.
• Work Instructions associated only with some of the Serial Numbers produced by the Work Order Operation.
 Data is collected automatically if you have configured the system in order to exchange XML messages with
Opcenter Connect MOM (Opcenter CN MOM). For more information, see section How to Integrate Opcenter
Execution Discrete with Opcenter Connect MOM of the Opcenter Execution Discrete Installation and
Work Instructions can be managed both at Work Order Operation or Work Order Step level.
In case of Serialized production involving the execution of Work Order Operations on Containers, the ID of the
container is provided on the Work Instruction tile, along with the Serial Number loaded in the container. Also, for
Work Instructions to be added on demand on specific Serial Numbers, it is possible to select either a specific Serial
Number or a container. In the latter case, the Work Instruction will be associated to all the Serial Numbers available
in the container.
Prerequisite

Work Instructions are linked to Work Order Operations or Work Order Steps.
• Acknowledging Work Instructions
• Providing Values for Data Collections associated with a whole Work Order Operation/Step
• Providing Values for Data Collections associated with all Serial Numbers of a Work Order Operation
• Associating Data Collections to specific Serial Numbers.
Acknowledging Work Instructions

1. While managing the current Work Order Operation, select the Work Instruction task. By default, only the tabs
which contain Work Instructions are displayed.
 If only one task is available, you do not need to perform any selection, as the system automatically
2. Read the displayed Work Instructions.

3. Click Acknowledge.
 If Result management has been enabled and you have already acknowledged your Work Instruction, if
the Work Order Operation involved must be repeated due to a negative Result declared on one or more
MTUs, you must re-acknowledge it in order for the execution to be repeated.
Providing Values for Data Collections associated with a whole Work Order
Operation/Step
1. While managing the current Work Order Operation, select the Work Instruction task.
2. Select the Work Instructions tab.

3. Provide values, either by typing them manually or by clicking the Acquire button (if available) for the Data
Collections associated with the Work Order Operation/Step. Before being confirmed, the values can be updated
even if they have been acquired from the field.
4. Click Confirm to save the value.
Providing Values for Data Collections associated with all Serial Numbers of a Work
Order Operation
Help
2. Select the SN Work Instructions tab.
3. On the top, all the Serial Numbers currently started are displayed: select the one for which you want to fill the
Data Collections.

 If the Work Order Operation has been programmatically started by the

StartWOOperationSerializedLiteSingleWO command, after confirmation of the values, it is possible to
re-edit them and confirm the new values.
Associating Data Collections to specific Serial Numbers

2. Select the SN Work Instructions tab.

3. Click .
4. In the Add Work Instruction page, select:
• one Serial Number or a container
• one or more Data Collections.
5. Click Add to associate the selected Serial Number/container to the Data Collections.
8.6.1.2 Using Tools

This procedure allows you to use Tools during the execution of the Work Order Operation or Step.
The displayed content may vary according to the production type or the involvement of containers. For Work
Orders of type Serialized or Full Serialized, the Tools are grouped by each produced Serial Number. If you have
started the Work Order Operation on containers, the Tools to be used are grouped according to the containers. A
mixed situation is also possible: you may have some tools grouped according to the containers and others grouped
according to the produced Serial Numbers.
When Tools are used on containers, the usage is rescaled and the usage duration distributed proportionally
according to the content available in the Containers.
In case of integration with the Automation Layer, you will be able to acquire values related to the Tool ID, the usage
time and the usage duration. You can then decide whether to save these values or edit them manually.
Also, if you have defined Setpoints for Tools, and linked the Setpoint variables to the Automation Node Parameters,
you will be able to see the values automatically transmitted to the Tool before using it.
 Tools in OnHold status or currently locked are not available for usage at runtime.
Procedure
1. In the Operator Task List or Operator Details Step page, select the Tool Usage task.

2. (Optional) Click Setpoints to see the variables automatically transmitted to the available Tools.
3. (Optional) Do either of the following:
• In case of Serialized or Full Serialized production type, expand the Serial Number of interest.
• In case of Containers, expand the Container of interest.
4. Click the Browse button to assign a Tool to the task.
5. Set the Tool ID parameter and then at least one of Usage Time and Usage Duration parameters in either of the
following ways:
• typing the value manually and clicking Use Tool.
• clicking the Acquire button (if available).
 If the parameter Consumable had been set while creating the Tool Definition, the Consumable checkbox
will be selected. This is to remind the User that inserting the ID of the tool instance is highly recommended
(although not mandatory).
If the Tool has been defined as Lockable (either directly or through its Tool Definition), using it will set its
state as Locked.
Tracking Tool Usage

1. Click the History icon.
2. In the List of used Tools panel, select the Tool for which you want to see data related to its usage.
3. Expand the node related to the selected Tool in the bottom area, to see more details about the usage, in terms
of Tool ID, Usage Counter and Usage Duration.
 For each of the parameters, the following information is provided:

• the acquired value
• the quality of the acquired value
• the time-stamp of the acquisition
• the date for the acquisition.
If the values have been entered automatically (Tool usage was triggered by a Machine or Workcenter in
the case of integration with Opcenter CN MOM), the usage will be traced as performed by "" (blank
space indicating "no user") for the involved Equipment also.
8.6.1.3 Using Substrates

This procedure allows you to insert the details of the Substrates used by the Work Order Operation/Step. For Work
Orders of type Serialized or Full Serialized, the Substrates are grouped by each produced Serial Number.
Procedure
1. In the Operator Task List or Operator Details Step page, select the Tool Usage task.

2. Click the Browse button to assign a Tool to the task.

3. Provide values for the Usage Time, Usage Duration and Substrate ID fields.
4. Click Use Substrate. The system validates the compatibility of the Substrate with the Machine. If the
validation succeeds, the usage counter is advanced by one every time the Substrate is used.
Tracking Substrate Usage

1. Click the History icon.
2. In the List of used Tools panel, select the Tool for which you want to see data related to its usage.
3. Expand the node related to the selected Tool in the bottom area, to see more details about the usage, in terms
of Substrate ID, Usage Counter and Usage Duration,
 For each of these parameters, the following information is provided:

• If the value has been acquired or entered manually
8.6.1.4 Consuming or Assembling Material Tracking Units

This procedure allows you to consume Material Tracking Units during the execution of a Work Order Operation or
Work Order Step (for example, for assembly or Additive Manufacturing production). For Serialized, Full Serialized
or FlexibleSerialized Work Orders, the MTUs to be consumed are grouped by each Serial Number to be produced.
Assembly is feasible solely if the values of both the Serial Numbers (and/or Batch IDs) of the MTUs to be consumed
and their respective quantities are indicated.
A dedicated color code has been adopted to allow you to interpret the material consumption status at a glance.
If necessary, there exists the possibility of viewing which Materials have already been consumed (that is, Material
usage) from a chronological standpoint: for details, see Tracking Material Usage below.
 Special Cases
The procedure below is commonly followed in most cases. However, given the complexity of MTU
assembly (or production) and consumption, it is necessary that, for certain cases, the procedure will differ
and additional insight may be required.
• For pre-kitted Material Tracking Units, see Consuming or Assembling Pre-Kitted Material Tracking
Units.
• For assembly involving Containers, Decimal Remainders or MTUs with linked Documents, see Special
Cases regarding Consumption and Assembly.
Prerequisites
• For semi-automatic acquisition of Material parameters, Serial Number / Batch Id as well as Quantity
are mapped to Automation Node Instance parameters.
• For validation of scanned Serial Number Codes / Batch Ids against Barcode Rules, Barcode Rules have been
configured using the Barcode App provided by Opcenter Execution Foundation.
• The Auto-Consume Batch Materials configuration key is disabled.

Procedure
1. In the Operator Task List or Operator Details Step page, select the Material Consumption task of interest.
2. (Optional) For each MTU produced, if desired, set the Auto-Consume Batch Materials toggle to On if you want
to enable automatic consumption of Batches.
3. For each MTU to be consumed, specify the values for Serial Number / Batch Id and Quantity, consulting the
table below before proceeding:

Serial Number / Batch Id Value insertion for these parameters may fall under one of the
following cases:
• For an existing Serial Number or Batch: enter the values
either manually or using a Barcode reader.
• For a Serial Number or Batch that does not yet exist:
enter its value manually and the system will create it on-
the-fly. If the Auto-Consume Batch Materials toggle is
set to On, batches are automatically consumed, be they
already available in the system or created on-the-fly.
Moreover, if a buffer that contains the related Material is
associated to the active machine, the system
automatically consume the Material from the buffer
instead of creating a Batch on-the-fly.
• If available, click the Acquire button to
automatically fill the Serial Number / Batch Id (as well
as the Quantity field) with values.
• If the MTUs to be consumed have been loaded into a
Container, search for the Container via the Container
field on the command bar to automatically fill Serial
Number / Batch Id with the code of the respective MTUs.
Refer to Special Cases regarding Consumption and
Assembly.
The system will validate the search as follows:
Icon Description
Either the specified Container does not

exist, or none of the Material Tracking
Units in the specified Container match
the required Material to be consumed.
None of the Material Tracking Units in

the specified Container satisfy the
quantity of Material to be consumed that
is required.
The Material Tracking Units in the

specified Container satisfy Material
Consumption requirements either in full
or in part.
• If the Work Order Operation is associated to a Material

with Material Specification Type
TrackLoadedAMPowder, the Batch Id is automatically
filled with the identifier of the Powder Batch used to
print the selected items. If the same Powder Batch has
been used to print more items, only one record is
displayed showing the total quantity.

• For pre-kitted MTUs, the Serial Number Codes or Batch
Ids are suggested (if validation is required) or pre-filled
directly. Refer to Consuming or Assembling Pre-Kitted
Material Tracking Units.
• If you are using a Barcode reader and the system is
configured to validate the entered value against Barcode
Rules: scan the barcode. The system validates it as
follows:
Icon Description
The Barcode matches the Barcode Rule, the MTU

is validated.
The Barcode provided fails validation for one of

the following reasons:
• the matching Barcode Rule does not
exist in the system
• the specified Rule Part is not found
• the default Barcode Rule has not been
configured.
However, consumption is allowed.
The Barcode and the Barcode Rule Parts are valid

but the Barcode does not belong to the specified
Material. The textbox is emptied prompting the
user to enter a valid Barcode.
Quantity Enter the quantity that you want to assemble.
4. Click Assemble to consume the MTUs.
Result
Upon clicking the Assemble button, the value for Assembled Quantity will be updated accordingly and the colors
used to display the Serial Numbers or Batches will change.
The following color combinations are possible:

Overall Background Background Color of Meaning

Color Contained Elements
White All White No consumption (be it partial or total) has ever

taken place (that is, Assembled Quantity is
equal to 0): the respective total quantities
available for consumption for each of the
contained elements (Total) are intact.
 Colors used for Custom Material

Specification Types
This color combination is also
adopted in all cases involving
Materials set with an inbound Custom
Material Specification Type: in this
case, it is irrelevant whether there
has been consumption (either in part
or in full) or not.
Yellow All Yellow All the elements involved in the Work Order
Operation’s (or Work Order Step's) execution
have been consumed only partially (that is,
each element's Assembled Quantity is not
equal to Total).
Green All Green All the elements involved in the Work Order
Operation’s (or Work Order Step's) execution
have been consumed in full (that is, each
element's Assembled Quantity is equal to
Total). in this case, a is shown on the
right.
Yellow Combination of Green and/or Overall meaning:

Yellow and/or White
• At least one of the elements involved in the
Work Order Operation’s (or Work Order
Step's) execution has been consumed only
partially.
In detail:
• The individual contained elements
displayed in green have been consumed in
full.
displayed in yellow have been
partially consumed.
displayed in white have never been
consumed.

 Once completely assembled, the Material Tracking Unit remains visible in the Material Tracking Units
page with Quantity equal to zero.
Tracking Material Usage

1. Click the History button.
2. In the List of consumed Materials panel, select the Material Tracking Unit or batch for which you want to see
data related to its usage.
3. (Optional only for semi-automatic acquisition) Click the selected Material in the bottom area, to see more
details about the usage.
 For each of these parameters, the following information is provided:

• If the value has been acquired or entered manually
If the values have been entered automatically (that is, if Material consumption was triggered by a Machine
or Workcenter in the case of integration with Opcenter Connect MOM), the User is identified with an empty
space and a value is provided also for the involved Equipment.
8.6.1.4.1 Consuming or Assembling Pre-Kitted Material Tracking Units

When you consume or assemble pre-kitted Material Tracking Units, the system indicates what exactly is to be
consumed for a specific Work Order in terms of reserved Serial Number codes or Batch Ids.
If the pre-kitted Material Tracking Units to be consumed are Batches, the quantities will be displayed as they have
been pre-kitted over multiple Batches. The Material Tracking Units to be consumed may thus originate from
different Batches.
According to the configuration, the system validates the specified Material Tracking Units automatically, once you
have typed the Serial Number Code or Batch ID. You can also decide to perform the validation from a dedicated
panel, if there is a huge amount of MTUs to be validated. In this case, once the MTUs are validated, you can directly
proceed with the Assemble from that panel.
 The icon indicates that the pre-kitted MTU requires validation.
If no validation is required, pre-kitted Material Tracking Units can be automatically assembled from the Operator
Task Details page, without the need for the Operator to further interact with the system.
If you want to consume pre-kitted MTUs together with MTUs that have not been reserved, both types of MTUs will
be assembled when the Assemble button is clicked.
If the pre-kitted MTU to be consumed is not available, you can specify another MTU (be it a Serial Number Code or
Batch ID), thus changing what has been previously reserved. In addition, for Batches, it is possible to specify a
different quantity, provided that the new value is less than the original one.

 If the quantity of the pre-kitted MTU is less than the quantity of the Material to be consumed (for the
specified target MTU), once the pre-kitted MTU has been consumed, you can then continue consumption
as usual until the total quantity of the Material to be consumed has been depleted.
Prerequisites
Material Tracking Units have been reserved (pre-kitted) for the Work Order in execution.
• Validating and Assembling Pre-kitted MTUs
• Validating and Assembling Large Numbers of Pre-kitted MTUs
• Changing Pre-Kitted MTUs
Validating and Assembling Pre-kitted MTUs

1. If the Material Tracking Unit to be assembled is configured to be validated, specify the values for Serial
Number / Batch Id and Quantity, working from the Operator Task List or Operator Details Step page.
If the inserted code matches with the expected one, the icon is displayed indicating that validation was
successful.
If the inserted code does not match with the expected one, the icon is displayed indicating that validation
was not successful and that it is necessary to specify another Serial Number /Batch Id.
2. Click Assemble.
Validating and Assembling Large Numbers of Pre-kitted MTUs

1. If the Material Tracking Unit to be assembled is configured to be validated, click Validate and Assemble
Pre-Kitted MTUs.
2. In the Validate and Assemble Pre-Kitted MTUs panel, specify the Serial Number code or Batch ID to be
consumed and click Validate.
If the inserted code matches with the expected one, it is validated and the related row highlighted.
3. Repeat step 2 for each Material Tracking Unit to be validated.
4. Click Assemble to consume the highlighted MTUs.
 This procedure is recommended in case of large numbers of pre-kitted MTUs, since it allows you to easily
search for the MTUs to be validated or to filter them out according to specific criteria.
Changing Pre-Kitted MTUs

1. Click Edit next to the Pre-kitted MTU you want to change.
2. Type the new Serial Number Code or Batch ID.
3. (For Batch ID only) Type a new value for the quantity, if necessary.
4. Click Save.
8.6.1.4.2 Special Cases regarding Consumption and Assembly

In certain situations, consumption and assembly take place with a specific behavior that differs somewhat from
what is described in Consuming or Assembling Material Tracking Units.
Here is a summary of such special cases.

Assembly involving Material Tracking Units with Linked Documents

When performing an Assembly that involves a Material Tracking Unit to which one or more Documents have been
associated and the quantity to be assembled is less than the quantity of the initial MTU, the MTU will be split and
the resulting MTU will be automatically associated to the same Documents that were associated to the initial MTU.
Consumption involving Decimal Remainders

In those cases in which the total quantity to be consumed cannot be equally divided among a Work Order's Serial
Numbers or Batch IDs to permit its full consumption (that is, there exists a decimal Remainder of the total quantity
to be consumed), the Operator is free to decide on which Serial Number or Batch ID this remaining decimal quantity
can be assigned for consumption.
For example, if a serialized Work Order has a total quantity to be consumed equal to 1 and it must produce 3 Serial
Numbers, each Serial Number will consume a quantity of 0.333, with an overall remainder of .001 for the Work
Order. This remainder of .001 can be assigned to any of these three Serial Numbers, so that a full consumption of
the quantity to be consumed is achieved.
However, if Material Tracking Units belonging to the Additive Material Specification Type are to be consumed by a
serialized Work Order, should there be a decimal remainder, the system automatically forces this remainder to be
consumed on the last Serial Number to be produced by the Work Order.
Assembly involving Material Tracking Units to be produced that have been loaded
into Containers
Material Tracking Units can also be assembled on final products loaded into Containers. Likewise, MTUs to be
consumed that have been loaded into Containers can be used for assembly.
Consumption involving Containers follows the same criteria already applied according to the defined Material
Specification types.
In addition:
• If there are pre-kitted Material Tracking Units to be consumed and the MTU to be produced is available in the
Container, consumption is executed first on the MTU to be produced for which pre-kitting has been performed.
• If the Materials to be consumed are Batches, the inserted quantity is rescaled according to the final products
available in the Containers.
• If the Materials to be consumed are Serial Numbers, consumption takes place according to the values of the
assembled quantities. The smallest value will drive consumption, whereby its corresponding Serial Number will
be consumed first. If all Serial Numbers have the same value for their assembled quantities, then consumption
will take place on the first Serial Number in the list.
Assembly involving Material Tracking Units to be consumed that have been loaded
into Containers
If MTUs to be consumed have been loaded into a Container and must be assembled to form a final product, it is
necessary that the MTUs involved must have a sufficient quantity and be of the same Material for that particular
assembly.
If the Container has been loaded with MTUs to be consumed that satisfy only in part what is required for the
assembly, the MTUs that do not fulfill these conditions will remain free for use elsewhere, whereas the MTUs that
satisfy these conditions will be used for that particular assembly.
Containers containing MTUs to be consumed can be linked to a Work Order or not. Once the loaded MTUs are
completely consumed, they are automatically unloaded from the Container and, if the Container is also linked to a
Work Order, then it is also unlinked from the executed Work Order.

Moreover, if the Container was defined as reusable upon configuration, then its status changes to Unloaded,
otherwise, it will be marked as Discarded.
All the activities related to the unloading of MTUs are traced in the History tab of the Material Tracking Units
Aggregates and Containers page.
Consumption involving Materials with AutoConsume Material Specification Type

To automatically consume Materials from a Line Side Position it is necessary that the Line Side Position is
associated with both the Material to be consumed and the workcenter or unit on which the Work Order is executed.
8.6.1.5 How to Manage Quality Inspections
Quality Inspections are related to measurements to be collected at runtime in terms of frequency and sample size.
Depending on how you have configured the Quality Inspection, the form to be filled at runtime may be related to
the indication of:
• the number of detected defects in case of Visual Characteristics
• the Values for Variable Characteristics
• Ok/Not OK for Attributive Characteristics.
• (For Buy-Off) Accept or Reject.
During runtime, if a Quality Inspection of any type conducted on a Material Tracking Unit is unsuccessful (that is, the
user has declared a Non-Conformance on it browsing a Failure), this will trigger the automatic creation of a
corresponding Quality Non-Conformance in Open status, so that it can be corrected.
Quality Inspections can come about in two ways in relation to Material Tracking Units:
• Manually: there is the direct input by the Operator during any type of Quality Inspection.
• Automatically: in this case, the data regarding whether the MTU has passed or failed inspection is automatically
acquired by a Machine or Workcenter. This is possible only for Attributive or Variable Quality Inspections and
requires integration with Opcenter Connect MOM. See How to Automatically Acquire Quality Inspection Data and
Quality Inspection Data Acquisition in the Opcenter Execution Discrete Installation and Configuration Manual.
 The automatic creation of Non-Conformances is possible only if the Non-Conformance on Defect or

Failure configuration key is set to Failure.
The format used for the natural identifier of this Quality Non-Conformance will contain a dedicated
timestamp indicating when it was automatically created.
Likewise, the Notes field of the Quality Non-Conformance will contain a reference to Characteristic
Representation Identifier.
If you intend to use Failures, but do not want Non-Conformances to be generated automatically whenever
a Failure is declared, you can simply remove event
handlers OnRuntimeAttributiveOrVariableFailureTraced and OnRuntimeVisualFailureTraced in
Solution Studio: for details, see section Removing Event Subscriptions on page Configuring Event
Subscriptions in the Opcenter Execution Discrete Installation and Configuration Manual.
The automatic creation of Non-Conformances is not managed in case of Buy-Off.

In case of Serialized/FullSerialized production types, you can decide on which of the started Serial Numbers to
perform the Quality Inspection by selecting the Quality Inspection task. If a signature is required, the Quality
Inspection is mandatory.
Moreover, specifically for Part Based Quality Inspections, see Special Cases regarding Part Based Quality
Inspections.
Also, in case of Serialized production involving the execution of Work Order Operations on Containers, the ID of the
Container is provided on the Quality Inspection tile, along with the Serial Number loaded in the Container.
Prerequisites
• An Inspection Definition is linked to the Work Order Operation or Work Order Step.
• The Non-Conformance on Defect or Failure configuration key is set to Failure in the following cases:
• If the automatic creation of Non-Conformances on MTUs is desired when operating in a Quality
Inspection context
• If a Buy-Off inspection is managed.
• Managing Quality Inspections on Serialized/Full Serialized production
• Managing Quality Inspections on Transfer Batch/Full Quantity production
 Quality Inspections specifically designed for Buy-Off only require the entitled user to Accept or Reject the
inspected MTUs and to insert the Electronic Signature. If the MTU is rejected, the Work Order Operation or
Work Order Step cannot be completed.
Managing Quality Inspections on Serialized/Full Serialized production

1. While managing the current Work Order Operation, select the Serial Number to be inspected.
2. Click the Quality Inspection task.
3. Follow the instruction provided in the form in the center zone.

4. In case of Failures, click to browse and associate a Failure.
5. Click OK.
6. If the Quality Inspection requires an Electronic Signature, do the following:
• Click Sign.
• In the Signature Required panel, provide the required signature and click Sign again.
7. Repeat steps 1-5 for each Serial Number to be inspected.
Managing Quality Inspections on Transfer Batch/Full Quantity production

1. While managing the current Work Order Operation, select the Quality Inspection task.
2. Follow the instruction provided in the form in the center zone.

3. In case of Failures, click to browse and associate a Failure.

4. If the Quality Inspection requires an Electronic Signature, do the following:

• Click Sign.
• In the Signature Required panel, provide the required signature and click Sign again.
5. Click OK.
Result (valid for both procedures above)

If the Non-Conformance on Defect or Failure configuration key is set to Failure, a Quality Non-Conformance has
been automatically created: at this point, it is necessary that this Non-Conformance be sentenced.
If Complete Work Order Operation by Different User configuration key is enabled, the active Machine has the
EnabledForCompleteByDifferentUser property set to True and the Work Order Operation/Step is ready to be
completed, when a Material Tracking Unit is accepted, the Work Order Operation is automatically completed for
that specific Serial Number.
 Automatic completion is possible only if the Production Type is Serialized, FlexibleSerialized or

FullQuantity.
If you want to disable automatic completion, you can remove the subscription of the
OnSentenceBuyOffCompleteOperationForStep handler to the OnSentenceBuyOff event from Solution Studio.
8.6.1.5.1 Special Cases regarding Part Based Quality Inspections

If you have configured your system in order to automatically trigger a Quality Inspection only on a subset of
produced items (Part Based), the scenario may vary, depending on various factors.
Those Serial Numbers for which it is mandatory to perform the Quality Inspection display the indicator inside
their corresponding tile.
If desired, you can perform the Quality Inspection also on other pieces.
An indicator will be displayed on the Quality Inspection, once it is not required anymore and will disappear if
further Quality Inspections must be carried out on additional Serial Numbers.
Optional Work Order Operations in the Routing

If the Work Order Operation containing the Quality Inspection in the routing is optional, then once the pieces are
completed on the previous Work Order Operation, they are presented as available for undergoing the Quality
Inspection, regardless of the configured Frequency Value.
Work Order Operations containing only Quality Inspections

If, in a routing, the Work Order Operation dedicated to the Quality Inspection does not contain other manufacturing
activities to be performed, the completed Serial Numbers are skipped according to the configured Frequency
Value.
Work Order Operations containing various Manufacturing Activities

If the Work Order Operations contain various manufacturing activities in addition to the Quality Inspection, each
Serial Number must be started and completed, as they are not skipped. The pieces that must be inspected can be
easily recognized by the indicator displayed in their corresponding tile.
Work Orders modified after their generation from a Bill of Process

If several Work Orders are created from the same Bill of Process, they will inherit the Part Based Quality Inspection
configuration.
However, should the Referenced Operation be changed for one of the Quality Inspections pertaining to the "sibling"
Work Orders after being generated, the counter is no longer shared for that particular Quality Inspection, but is
instead triggered separately for each of the modified Work Order Operations.
8.6.1.6 Transferring Print Job Files to 3D Printers

Transferring a Print Job File to a 3D Printer means uploading to the Machine the instructions required to physically
perform the print operation.
There exist three distinct types of Print Job Files:
• The Template Print Job File is a dummy entity from which you can subsequently generate a Runtime Print Job
File, in which: the Serial Numbers that you want to be printed and the Machines on which their printout is to be
performed are specified.
• The Runtime Print Job File is generated from a Template Print Job File in Opcenter EX DS and contains the Serial
Numbers to be printed and the Machines on which the printout is to be performed.
• Ready-to-use Print Job Files are imported from an external system.
The Print Job File to be transferred can be:
• chosen manually, if Opcenter Execution Discrete has been configured to act as a repository clearing the Auto
Print Job File configuration key and Print Job Files have been previously imported and configured. This is the
default behavior.
• performed automatically on the fly by the external CAM system if the Auto Print Job File configuration key has
been set.
 For Additive Manufacturing operations where the Print Job Files belong to an Execution Group Phase,
all the Work Order Operations are transferred to the associated 3D printer together, at the same time.
The operator is not required to open the Print Job File Transfer task for each Work Order Operation
and transfer the Print Job File.
Prerequisites
• The Print Job File must be configured correctly.
• The Print Job File you intend to transfer must not be in Pending status.
• There must be mapping between the 3D printer to which you intend to transfer your Print Job File and the
Machine name of the external system.
Procedure
1. While managing the current Work Order Operation, select the Print Job File Transfer task.
2. To add a Print Job File to the list of files available for a Machine: click Add, in the Link Print Job Files to
Machine select a Machine, select one or more Print Job Files and click Add.
3. For Work Order Operations belonging to a Serialized or FullSerialized Work Order:
• The screen displays a single Print Job File-Machine association per row. The associations displayed are
only those containing at least one active Serial Number.
All Print Job Files can be opened from the screen to view their details by clicking Details.

Instead, depending on Print Job File type, you can perform different actions:
If it is a Template Print Job File, you can generate a Runtime PJF.
If it is a Runtime Print Job File or a ready-to-use Print Job File, you can view the Serial Numbers that are
currently active on the Work Order Operation. You can transfer the information contained in either of
these Print Job File types by clicking Transfer.
• if Print Job File management is automatic, the screen displays the list of the currently-active Machines
and the Transfer icon is available.
4. If the Work Order Operation belongs to a FullQuantity or TransferBatch Work Order:
• if Print Job File management is manual: for each printer, the list of available Print Job Files is displayed.
• if Print Job File management is automatic, the screen displays the list of the currently-active Machines
and the Transfer icon is available.
5. If the 3D Printer requires Print Job Files to be pre-transferred and:
• the Print Job File has not been pre-transferred in advance to the machine at least once, select the file,
click Transfer and then as soon as the final file is displayed in the dedicated area, select it and click
Use.
• the Print Job File has already been pre-transferred to the machine at least once, the system displays the
list of final files in addition to those that have been selected: select the file of interest and then click
Use.
 To display the history of past transfers, click History (available only after at least one Transfer has
been performed).
8.6.1.6.1 Generating Runtime Print Job Files

If necessary, in runtime Additive Manufacturing contexts, Operators can generate a Runtime Print Job File from a
Template Print Job File with one or more active Serial Numbers from the Operator Landing Page: it will then be
possible to print the final product including its Serial Number produced by Serialized or FullSerialized Work
Orders.
Prerequisite
If you are executing an Execution Group instead of a single Work Order, the generation of runtime Print Job Files
can be performed if the Execution Group contains at least one Work Order Operation that belongs to a Serialized or
FullSerialized Work Order.
Procedure
1. In the Operator Landing Page, select the Work Order of type Serialized or FullSerialized for which you need to
generate a Runtime Print Job File.
2. View the details of the selected Work Order and click the Print Job File Transfer task.
3. Select the Template Print Job File you require and then click the Generate icon.
4. (Not available for Execution Groups) In the Generate Runtime Print Job Files panel, select at least one active
Serial Number to be used to generate the Runtime Print Job File you require and click Save.
Result

The runtime Print Job File is generated and automatically associated to the selected Serial Numbers (in case of
Work Order) or to all related active Serial Numbers (in case of Execution Group). The runtime Print Job File is
displayed below the template from which it has been generated and it is now possible to transfer its contents to
permit the correct printing of the information necessary for the final products.
8.6.1.7 Transferring CNC Programs to Machines

Transferring a CNC Program means uploading to a Machine the instructions required to physically perform the Work
Order Operation currently active.
Prerequisites
• A valid DNC software interface (any generic system or a custom one) is installed and configured.
• DNC Integration must have been enabled in the Configuration Keys > Integrations page.
• The path of the software interface has been specified in the Configuration Keys > Integrations page.
• CNC Packages must have been imported and mapped to Machines.
Transferring from a Serialized, FullSerialized or FlexibleSerialized Work Order

1. While managing the current Work Order Operation, select the Part Program Transfer task. The center zone of
the page displays the Machines to which the CNC Program can be transferred.
2. Select the desired Machine. The lower part of the screen displays in a tree view the Serial Numbers currently
processed on the selected Machine.
• If you want to transfer the CNC Program processing all the Serial Numbers at once, click Transfer on
the tree row corresponding to the selected Machine.
• If you want to transfer the CNC Program processing a single Serial Number, select the desired Serial
Number in the tree and click Transfer on its row.
4. To download and preview a document associated to a CNC Item, do either of the following:
• If you want to preview the document associated to the CNC Package, click Preview on the tree row
corresponding to the selected Machine. The button is enabled only if there is a document associated to
the Package.
• If you want to preview a document associated to an element contained into the package, click
Details, select the element to preview and click Preview. The button is enabled only if there is a
document associated to the element.
 It is possible to preview only documents up to 10 MB in size.
Transferring from a FullQuantity or TransferBatch Work Order

1. While managing the current Work Order Operation, select the Part Program Transfer task. The center zone of
the page displays the Machines to which the CNC Program can be transferred.

2. Select the desired Machine.

• if you want to transfer at once all the elements contained in the CNC Program, click Transfer.
• If you want to manually select the elements to transfer, click Details. In the package tree details, select
the transferrable elements and click Transfer.
4. To download and preview a document associated to a CNC Item, do either of the following:
• If you want to preview the document associated to the CNC Package, click Preview. The button is
enabled only if there is a document associated to the Package.
• If you want to preview a document associated to an element contained into the package, click Details,
select the element to preview and click Preview. The button is enabled only if there is a document
associated to the element.
 It is possible to preview only documents up to 10 MB in size.
 Click History to display the history of past transfers.
8.6.1.8 Producing Material Tracking Units at Runtime

This procedure allows you to produce Material Tracking Units during the execution of a Work Order Operation or
Work Order Step.
In order for MTU production to be feasible, both the Serial Numbers (and/or Batch IDs) of the MTUs to be produced
and their quantity must be specified.
A dedicated color code has been adopted to allow you to interpret the material production status at a glance: for
details, see Color Code for Material Production Status below.
Procedure
1. In the Operator Task List or Operator Details Step page, select the Material Production task of interest.
2. For each MTU to be produced, specify the values for Serial Number / Batch Id and Quantity, consulting the

Serial Number / Batch Id Value insertion for these parameters may fall under one of the
following cases:
manually.
• For a Serial Number or Batch that does not yet exist: enter
its value manually and the system will create it on-the-fly.
 Production and Disassembly

Depending on whether the entered Batch ID
or Serial Number is already assembled
somewhere, the system will assume a different
behavior:
• If you insert a Batch ID or Serial Number
that already exists in the system and
assembled somewhere, the system
performs a disassembly: from the
Disassemble panel that opens, you can
select the Work Order Operation or Step
from which you want to dissemble the
MTU.
• If you insert a Batch ID that already exists
in the system but not assembled
anywhere, then the system adds the
quantity.
• If you insert a Serial Number that already
exists in the system but not assembled
anywhere, the system returns an error.
In all three cases, click Save to continue the
production process.
Quantity Enter the quantity that you want to produce.

If there are Material quantities preset according to what was specified
when the Operation or Step was created, you can modify these values
manually, according to your needs.
3. Click Produce to produce the MTUs.
Color Code for Material Production Status

If you have selected a Material Production Task instance, specific colors are used to display the Serial Numbers or
Batches in the details area of the screen: these colors indicate the production status of the Materials involved in
the Work Order Operation’s (or Work Order Step's) execution.
Upon clicking the Produce button, the value for Produced Quantity will be updated accordingly and the colors
used to display the Serial Numbers or Batches will change.

Overall Background Color Background Color of Contained Meaning

Elements
White All White No production (be it partial or total) has

ever taken place (that is, Produced
Quantity is equal to 0): the respective total
quantities produced for each of the
contained elements (Total) are intact.
Yellow All Yellow All the elements involved in the Work Order
Operation’s (or Work Order Step's)
execution have been produced only
partially (that is, each element's Produced
Quantity is not equal to Total).
Green All Green All the elements involved in the Work Order
Operation’s (or Work Order Step's)
execution have been produced in full (that
is, each element's Produced Quantity is
equal to Total). in this case, a is shown
on the right.
Yellow Combination of Green and/or Overall meaning:

Yellow and/or White
• At least one of the elements involved in
the Work Order Operation’s (or Work
Order Step's) execution has been
produced only partially.
In detail:
displayed in green have been produced
in full.
displayed in yellow have been partially
produced.
displayed in white have never been
produced.
Tracking Material Production

1. Click the History button.
2. In the History panel, select the Material Tracking Unit for which you want to see data related to its production.
You can also view data related to the WOO-Step from which the MTU is disassembled. Events such as the linking
or unlinking of Documents are also tracked.
8.6.1.9 How to Manage Powder Material Batches

This procedure allows you to load a Powder Batch into a 3D Printer during the execution of a Work Order Operation
specific to Additive Manufacturing production.

If the Work Order Operation belongs to a Serialized Work Order: after the first Batch has been loaded, if the
mandatory check on the Batch or Quantity has been enabled, when starting other Serial Numbers, the Operator
must give a confirmation by clicking the Confirm button before the Powder can be loaded, otherwise the Work
Order cannot be completed.
For all the other Work Order types: after the first Batch has been loaded and if you want to track the actions
performed, an optional confirmation can be given by clicking the same Confirm button (in this case even if the
mandatory check has not been enabled).
The quantity of the Powder Batch can also be replenished, if necessary. The added quantity is added to the already
loaded quantity.
 Powder Batch previously loaded can be unloaded, by clicking the button. This operation is to be
performed with caution (for example, if the Operator realizes that a wrong Batch has been loaded.)
In addition, if the Barcode App provided by Opcenter Execution Foundation has been installed, it is also possible to
type or scan a Batch Id and view the corresponding results.
A dedicated color code has been adopted to allow you to interpret the required quantity status of the Powder Batch
at a glance: for details, see Color Code for Powder Batch Quantity Status below.
Prerequisites
• The Operation/Step category Setup3DPrinter has been associated to the Process Operation.
• A Work Operation of type Setup3DPrinter (which has Load AM Powder set to true) has been configured and
associated to the Work Order Operation.
• (Optional) The required Powder has been correctly configured.
• (Optional) For validation of scanned Serial Number Codes / Batch Ids, Barcode Rules have been configured
using the Barcode App provided by Opcenter Execution Foundation.
• Load the Powder Batch.
• Replenish the Powder Batch quantity.
Loading the Powder Batch

1. In the Operator Task List page, select the Load AMPowder on 3D Printer task.
2. For the Powder Batch to be loaded, you must insert the values for both Batch ID and Quantity, consulting the

Batch ID Value insertion for this parameter may fall under one of the
following cases:
either manually or using a Barcode reader. The Quantity
field is automatically filled with the quantity inserted
when the Batch has been created.
• For a Serial Number or Batch that does not yet exist:
enter its value manually and the system will create it on-
the-fly.
• If there are more Batches with the same code (created
from the same Powder): select from the entity picker the
Batch you want to use.
• If you are using a Barcode reader and the system is
configured to validate the entered value against Barcode
Rules: scan the barcode. The system validates it as
follows:
Icon Description
The Barcode matches the Barcode Rule. The

Batch is validated by returning the associated
Batch ID/Serial Number.
The Barcode provided fails validation for one of

the following reasons:
• the matching Barcode Rule does not
exist in the system
• the specified Rule Part is not found
• the default Barcode Rule has not
been configured.
The Barcode and the Barcode Rule Parts are

valid but the Barcode does not belong to the
specified Powder. The textbox is emptied
prompting the user to enter a valid Barcode.
Quantity Enter the Powder Batch quantity.
3. Click Load to load the Powder Batch.
Replenishing the Powder Batch Quantity

1. For a Powder Batch already loaded, insert a value in the Replenish Quantity textbox (visible only if a Powder is
already loaded). The Code textbox changes automatically to Source Batch ID.
2. (Optional) Insert a value for Source Batch ID if you want to mix the quantity with another Powder Batch,
otherwise the replenished quantity is added to the Powder Batch already loaded.

3. Click the button to replenish the quantity.
Color Code for Powder Batch Quantity Status

Upon clicking the Load button, the value for Quantity is updated according to the value inserted. The background
color behind Serial Numbers or Batches in the details area of the screen changes: these colors indicate the status of
the required quantity of the Powder Batch involved in the Work Order Operation’s execution.
Overall Background Color Meaning
White No loading (be it partial or total) has ever taken place (that is,
Quantity is equal to 0).
Yellow The value of Loaded Powder Quantity is less than Required

Powder Quantity.
 If the mandatory check on the Powder Batch quantity

has been enabled, the Powder Batch cannot be loaded.
Green The value of Loaded Powder Quantity is higher than Required

Powder Quantity.
Result
You can trace activities that are performed on Powder Batches by opening a Powder Batch of your interest and
clicking the History tab.
Actions related to the loading or unloading of Powder Batches for a specific Work Order can be traced also by
opening a Work Order of interest, clicking As Built Order and then clicking the Activity History tab.
8.6.2 Changing Serial Numbers during Production

During the execution of Serialized, FullSerialized and FlexibleSerialized Work Orders, you can choose to change the
Serial Numbers automatically generated on the basis of the template associated with the Material Tracking Unit
being produced, in favor of new Serial Numbers, according to your needs.
During execution, it is possible to change Serial Numbers (from either the Operator Landing Page or the Operator
Details page):
• on a single Material Tracking Unit at a time, either by manual insertion or automatic generation;
• on all the Material Tracking Units being produced, by performing a one-shot operation that uses a template
already associated to the Material from which the Material Tracking Units to be produced are instantiated. In
this case, new Serial Numbers are generated automatically for all such Material Tracking Units produced from
that moment onward.

 New Serial Numbers can be automatically generated also when production involves Execution Groups.
Target User
Users with the Operator role can perform this action.
Prerequisites
• The Work Order being executed must belong to the Serialized, FullSerialized or FlexibleSerialized production
type.
• The Work Order being executed must not be in Verified status.
Procedure
1. In the Operator Landing page, select the Work Order Operation or Execution Group containing the Material
Tracking Units being produced for which you want to change the Serial Numbers.
Otherwise, open the Operator Details page for the Work Order Operation or Execution Group containing
the Material Tracking Units being produced for which you want to change the Serial Numbers.
2. On the bottom bar, click the CHANGE SN button: this opens the Change Serial Numbers page, listing
the Material Tracking Units being produced by the selected Work Order Operation or Execution Group, as well as
their current Serial Number.
 If you have selected an Execution Group, column Work Order is visible, listing its various Work Orders.
3. Depending on whether you want to change the Serial Number for a single Material Tracking Unit or for
all Material Tracking Units being produced in one shot, proceed as follows:
If you want to change ... Then....
The Serial Number for a single Material 1. Operating on the row containing the Material
Tracking Unit through manual insertion Tracking Unit of interest, in the New Serial
Number column, enter the new Serial Number you
want in replacement for the Material Tracking Unit
and then click the Tab key on your keyboard to
save.
2. Repeat the previous step for all other Material
Tracking Units for which you want to change the
Serial Number.

If you want to change ... Then....
The Serial Number for a single Material Click the Generate button provided at the end of
Tracking Unit through automatic generation the row displaying the Material Tracking Unit of
interest: the system will automatically fill the New
Serial Number field with the value generated by
the template associated to that particular Material
and save it.
 Clicking the Generate button

automatically saves the Serial Number
generated for the single Material Tracking
Unit.
All Serial Numbers for all the Material Tracking Click the Generate All and Save button at the
Units that are being produced by the current bottom of the page: the system will first perform a
Work Order Operation or Execution Group one-shot change on all the listed Material Tracking
through automatic generation Units, automatically filling the fields of the New
Serial Number column with the values generated
by the template(s) associated to the specific
Material from which the Material Tracking Units
are instantiated, and then save the entered values.
8.6.3 Skipping Work Order Operations

During the execution of a Work Order, this procedure allows you to skip the execution of a Work Order Operation
and to provide a reason for the skip.
Prerequisites
The Work Operation associated with the Work Order Operation has been defined as Skippable and its type is
not Quality Only.
Procedure
1. In the Operator Landing page or in its Details view, select the Work Order Operation to be skipped and click
Skip.
2. Select a Reason for the skip, choosing among the Reasons previously configured.
3. (only for Serialized and Full Serialized Work Orders) Select a Serial Number.
4. (only for Transfer Batch Work Orders) Select a quantity.
5. Click OK.
8.6.4 Adding Documents to Work Order Operations at Runtime

In addition to those added during the creation of a Work Order, Documents can be added to Work Order Operations
at runtime:
• by users with the Operator role, during the execution of a Work Order;
• by users with the Production Coordinator role, for present or past Work Orders.

In both cases, if Multi-Plant Support is enabled, tags currently enabled for the logged User are applied to the
imported Documents.
When Documents are added on Containers, they are automatically propagated to all the Serial Numbers available
in the Containers.
Prerequisite
• The Collect Document parameter has been set while creating the Work Order Operation.
• The status of the Work Order Operations is Active.
Procedure for users with Operator role

1. In the Operator Landing page, select a Work Order Operation.
2. Click Add Document.
3. (Only if the Work Order is of type Serialized or FullSerialized) Select one or more Serial Numbers/Containers to
be associated with the document.
4. In the Add Document page, and do either of the following:
• if the document is available, select it and click Add
• if the document is not available, use the Import button to import and add documents to the Work Order
Operations.
Procedure for users with Production Coordinator role

1. Click the Work Orders tile in the home page.
2. Select the Work Order of interest and click As Built Order.
3. Click the Operations tab, and select the Work Order Operation to which you want to add documents.
4. (Optional only for Serialized or Full Serialized Work Orders) If you want to add documents to a specific Serial
Number, select it in the Serial Numbers tab.
5. Click the Collected Documents tab.
6. Click Add.
7. On the Add Documents page, do either:
• If a document you require is available in the list, select it, and click Add.
• If a document is not available, click Import, and using the file explorer, select the document. On the Add
Documents page, update the Identifier if required, and click Save.
8.6.5 Adding Notes to Work Order Operations at Runtime

At runtime, the Operator has the possibility to write notes relative to the execution of a Work Order Operation which
could be useful to other Operators. Also, Production Coordinators can add notes as extra information about a Work
Order Operation.
There exists the possibility of adding notes at the Work Order level: in this case, the note that is physically added to
one Work Order Operation will be visible and valid also for all the other Work Order Operations making up the
selected Work Order.
After you add a note to a Work Order Operation, if properly configured, a notification is triggered: this results in an
increase of the value displayed in the badge associated to the Notes notification icon. At this point, it is possible to
handle the note in question: for example, the person who receives the notification can then acknowledge the note.

Target User
Users with the Operator as well as the Production Coordinator role can perform this operation.
Prerequisite
The Work Order is released.
Procedure
1. Do one of the following according to your role:
• In the Operator Landing page, select an Operation and then click More .... > Notes.
• In the Production Coordinator Dashboard, select an Operation within a Machine or Workcenter and
then click the Notes notification icon.
• Operating from the Work Orders page, select the Work Order to which you want to add a note and then
click the Notes notification icon.
The Add Notes panel is displayed: any pre-existing notes that refer to the selected Work Order Operation will be
shown as tiles therein.
2. In the Add Notes panel, click Add: this opens the New Note box.
3. In the New Note box, type the notes that you want to add.
4. If you want the note you are adding to be visible and valid also for all the other Work Order Operations
belonging to the current Work Order, select the Is Work Order Level checkbox.
Note if you are operating from the Work Orders page, this checkbox is selected by default and cannot be
changed.
5. Click Save: the new note will be added to the selected Work Order Operation (or to all of the Work Order
Operations making up the selected Work Order).
 Any notes that have been added will remain visible inside the Notes tab of the As Built page
corresponding to the selected Work Order.
8.6.6 Aborting Work Orders

You can choose to abort a Work Order that has not yet been executed or that has been paused at runtime by the
Operator.
Target User
Prerequisites
• The Work Order is in one of the following states:
• Edit
• New
• Active
• Queue
• Pause
• Pending
• The Work Order Operations belonging to the Work Order must not have dependencies towards Work Order
Operations in state Open or Future Hold belonging to another Work Order.

Procedure
1. In the Work Orders page, select the Work Order that you want to abort.
2. Click Abort.
Result
If a lock was set on the Equipment during Work Order Operation execution, the lock is released automatically
before aborting the Work Order Operation.
After aborting Work Orders in the Active state, the state of the Active Work Order Operations and Work Order Steps
changes to Partial. If Work Order Operations and Work Order Steps are complete, the state remains the same and
those in the Open or Partial state, change to the Not Executed state.
For Work Orders in the remaining states, (Edit, New, Queue, Pause and Pending) the status of Work Order
Operation and Work Order Steps changes to Not Executed.
8.6.7 Placing Work Orders on Hold

The status of the last Work Order Operation is automatically set to Future Hold if an Operator declares a Non-
Conformance on that Work Order. In addition, a Production Coordinator can also place Work Orders on hold. For
example, Production Coordinators can place a Work Order requiring changes to its Work Order Operations on Hold.
Also, Production Coordinators can plan the schedule of material batches produced by Work Orders by placing the
Work Orders in Future Hold status. For example, when an Operator starts manually the Work Order Operation, the
Future Hold status triggers the Hold of the Work Order.
Target User
Prerequisite
At least one Hold Reason has been configured.
Procedure
1. In the home page, click the Hold tile.
2. Click Create > Create Hold Work Order and select the Work Order to be placed in Hold status.
3. Select a Hold Reason.
4. (optional) In the Notes field, type some notes (for example, the details of the Hold operation).
5. Click Create.
8.6.8 Placing Work Order Operations on Future Hold

During production, you can plan the automatic halt of a Work Order execution when a specific Work Order
Operation is completed. For example, you may need to perform this operation if you want to stop the execution of
the Work Order before reaching a Work Order Operation requiring a Tool or a Machine that is not currently
available.
Target User

Prerequisite
At least one Future Hold Reason has been configured.
Procedure
1. In the home page, click the Future Hold tile.
2. Click Create and select the Work Order Operation to be placed in Future Hold status.
3. Select a Future Hold Reason.
4. Click Create.
Result
The selected Work Order Operation is placed in Future Hold status.
Later, if the conditions requiring the hold will be no longer relevant (continuing the previous example, if the
required Machine or Tool will be available again) the Work Order Operation can be returned to the status owned
before the hold (either Open or Partial) clicking Start.
8.6.9 Placing Workcenters and Machines on Hold

The following procedure describes how to exclude a Workcenter or a Machine from production, for example
because it is out of order or it must undergo a maintenance process. It is also possible to place a Workcenter or
Machine on Hold when managing a Non-Conformance.
Target User
Prerequisite
At least one Hold Reason has been configured.
Procedure
1. Click the Hold tile in the home page.
2. Click Create > Create Hold Workcenter/Machine.
3. Select the item of interest.
4. Select a Hold Reason.
5. Click Create.
8.6.10 Managing Work Order Updates

The Product Engineer may need to create a new revision of a Process, not only to produce something different, but
also to improve the previously-planned production workflow. If, in the meantime, a set of Work Orders has been
created from the original Process, these Work Orders may need to be updated. If properly configured, users in
charge of updating the Work Orders, receive a notification whenever a new revision of a Process is created.
The system provides the Operator with a page automatically displaying all Work Orders created from Processes for
which a new revision has been created, and the Operator has the possibility to update these Work Orders both
completely (if no Work Order Operation has been executed yet) or partially (if at least one Work Order Operation has
been executed and the Work Order is in Queue status). In the second case, only non-executed Work Order
Operations will be updated.

Prerequisite
• The Work Order is in status Active, Pause, New, or Queue.
• The Process has been evolved, a new revision has been created and it has been released.
Procedure
1. Click the Work Order Update tile in the home page: the Work Order Update page is displayed.
2. Select the Work Order to be updated and click Open: the system displays the new evolved Processes with
the updated revision of the Process from which the Work Order was created.
3. Select the evolved Process of interest.
4. Click Update, to align your Work Order to the new Process revision.
8.6.11 Disassembling Material Tracking Units

Material Tracking Units can be disassembled in full, as well as in part, provided that certain conditions exist.
It can be necessary to disassemble a previously-assembled Material Tracking Unit in full in either of the following
cases:
• The Work Order includes a Disassembly Operation and the Operator must perform it in order to correctly
manage the work order execution. For example, it could be necessary to disassemble an MTU in order to
perform an operation that could not have been performed before assembling that MTU.
• A problem has been found on the assembled MTU and the Production Coordinator decides to disassemble it
from the produced MTU. How to perform this operation is described below.
Instead, it might be necessary to perform a partial Disassembly to remove a portion of the MTU and reserve it for
future re-assembly, for example.
 When performing a Disassembly that involves a Material Tracking Unit to which one or more Documents
have been associated and the quantity to be disassembled is less than the quantity of the assembled MTU,
the MTU will be split and the resulting MTU will be automatically associated to the same Documents that
were associated to the initial MTU.
There exists the possibility of disassembling a consumed MTU from a Work Order when consulting the Genealogy
page: for information, see the dedicated section below.
Prerequisite
The Work Order is not in status Hold or Verified.
Procedure
2. In the Work Order page, select the Work Order of interest.
3. In the As Built page, click As Built Order.
4. Click the Material tab.
5. Select the Material of interest and click Disassemble: this opens the Disassemble Material Tracking
Units pane, from which you must set the quantity to be disassembled from the Work Order.

 When performing a full disassembly, enter the maximum allowed value for the quantity to be
disassembled.
6. (Optional) Enter a Note.

7. Click Disassemble: the portion of the consumed MTU that you want to disassemble will be automatically
subtracted from the quantity initially displayed.
Result
The previously-assembled MTU is disassembled and the Work Order's status does not change.
Disassembling Consumed Material Tracking Units from the Genealogy page

1. Click Shopfloor Execution > Genealogy in the sidebar.
2. In the search bar, type the Work Order ID and press Enter: the system displays a hierarchical representation of
the Work Order's genealogy.
3. Expand the Work Order to view its details, which are presented in a tree view.
4. Navigate the tree view to reach the node corresponding to the consumed Material Tracking Unit.
5. Click the node of the consumed MTU: its details are displayed in a pane on the right.
6. In the right-and side bar, click Disassemble: this opens the Disassemble Material Tracking Units pane
from which you can set the quantity to be disassembled from the Work Order.
7. (Optional) Enter a Note.
8. Click Disassemble: the portion of the consumed MTU that you want to disassemble will be automatically
subtracted from the quantity initially displayed and the entire page will be refreshed, reflecting the updated
situation.
8.6.12 Pausing and Resuming Work Order Operations

If you are an Operator and issues in production arise, or changes need to be made to operations, you can pause a
Work Order that is currently in execution.
After fixing or clarifying the identified issue, you can then decide to resume it: otherwise, the Production
Coordinator may decide that substantial changes need to be made to the Work Order or to some of its Work Order
Operations and thus the Work Order must be aborted.
Work Order Operations associated with Containers display the icon in the tile: pausing them means pausing
the execution of all Material Tracking Units that have been loaded into those Containers and those MTUs that are
managed without Containers in the current Work Order Operation.
 Special Case: Performing an Administrative Pause

If a Work Order needs to be paused in the case of an emergency (for example, when the assigned user is
unavailable), the Production Coordinator can perform what is known as an Administrative Pause. For
details, see Special Case: Performing an Administrative Pause.
Target User
Users with the Operator role can pause a Work Order Operation.
Procedure
1. In the Operator Landing page, select a Work Order Operation in the Active status.

2. Click Pause.
3. Select a Reason for pausing the Work Order.
4. Click OK: if Electronic Signature is not enabled, this is sufficient to pause the Work Order. Otherwise, proceed to
the next step.
5. (only if Electronic Signature has been enabled) In the prompt that appears on screen, type your password,
some notes and then click Validate User. The system checks your credentials against those of the list of
authorized Operators:
• If you pass validation, you are authorized to complete pausing the Work Order.
• If you fail validation, you are not authorized to complete pausing the Work Order, but you may continue
to handle Work Orders or Work Order Operations that do not have dependencies on the Work Order that
you are not authorized to pause.
Result
The system sets the Work Order status to Pause: if you want to resume the Work Order Operation, click Start.
 Any Equipment initially locked by the Work Order Operation will be released after the Operation has been
paused.
8.6.12.1 Special Case: Performing an Administrative Pause

In emergency situations (for example, when the assigned user is unavailable), the Production Coordinator
can override the pause applied on the Work Order Operation and pause the Work Order at the administrative level.
 Once an Administrative Pause has been performed by a Production Coordinator on a Work Order, it can be
resumed by any user (including an Operator).
Target User
Users with the Production Coordinator role can perform an Administrative Pause.
Procedure
1. In the Work Orders page, select the desired Work Order in Active status and click As Built Order.
2. On the As Built Order page, click the Operations tab and select the desired Active Work Order Operation to be
paused.
 Keep in mind that, if users who belong to a Team are working on the Active Work Order Operation that
has been selected for Administrative Pause, all of the Team's members will be punched out from
the Work Order Operation and all associated Equipment will be released.
3. Click Pause.
4. If some Serial Numbers have already been completed before pausing the Work Order Operation, you can reopen
a subset (or all) of them, clicking the Reopen button, selecting the items of interest and then clicking
Reopen.

 In case of FullQuantity or FullSerialized production type, the whole Work Order Operation is
reopened and no selection is possible.
If the Work Order has been completed, only the last Work Order Operation can be reopened.
Result
The system sets the Work Order status to Pause: if you want to resume the Work Order Operation, click Start in
the Operator Landing page.
The Administrative Pause history is also visible in the Activity History tab.
8.6.13 Closing Flexible Work Orders

During production execution, it may be necessary to close a Flexible Work Order before its full completion. This may
happen, for example if the Work Order had been created for a given work shift and consequently it is necessary to
close it until the end of that shift, even if some Work Order Operations have not yet been completed.
When a Flexible Work Order is closed, if there are Work Order Operations that need to be completed, they will be
closed together with the Work Order: in this case, a copy of the original Work Order is created to permit the
completion of those Work Order Operations that were still in progress, in order to produce the remainder of the
original Work Order.
Prerequisites
• The Work Order status is either Queue or Pause.
• The Production Type of the Work Order is either FlexibleSerialized or FlexibleBatch.
Target User
Users with the Production Coordinator role or the Operator role can perform this operation.
Procedure
• In the Work Orders page, select the Work Order to be closed.
• In the Operator Landing page, select one of the Work Order Operation the Work Order to be closed
consists of.
2. Click the Close Flex WO button.
3. Either insert the unique identifier of the Work Order in the edit box or click the Generate button to
automatically create it according to a predefined template.
4. Click Create.
Result
• The status of the Work Order changes to Complete.
• Work Order Operations in status Open are set to NotExecuted, while Work Order Operations in status Partial or
Complete do not change.
• Work Order Operations are removed from the related Execution Groups (if available).
• The Work Order quantity is automatically adjusted by the system and you can no longer modify it.
• A new Work Order related to the closed one is created with Production Type:

Completing Work Order Operations
• TranferBatch, if the Production Type of the closed Work Order was FlexibleBatch
• Serialized, if the Production Type of the closed Work Order was FlexibleSerialized
• The new Work Order contains a copy of the Work Order Operations contained in the closed one, and their status
correspond to the status of the original Work Order Operations at the moment of the closure.
• The not produced quantity (in case of TransferBatch Production Type) or Serial Numbers (in case of Serialized
Production Type) are assigned to the new Work Order.
• All completed and scrapped items are logged for the closed Work Order both in the As Built Report and in the
Genealogy page.
• All in progress and not started items are logged for the closed Work Order both in the As Built Report and in the
Genealogy page.
8.7 Completing Work Order Operations

When executing Work Orders, you can complete Work Order Operations which have been previously started and
managed.
A Work Order is to be considered as completed when all its Work Order Operations are in a final status (either
the Complete or the Not Executed status).
During the creation of the Work Order to which the Work Order Operation to be completed belongs, it is possible to
define a set of Outbound Interlocking Checks to verify various conditions (for example, the assembly of all required
Materials, the completion of the related Steps). If at least one active Outbound Interlocking Check fails, the Work
Order Operation/Step will not be completed: an error message for each of the failed Outbound Interlocking Checks
is displayed to the Operator and this information is logged into the system in the Interlocking Check History page.
To see the details about the Interlocking Check outcome, click the ITLK Check History button in the Operator
Landing page or from the Details page.
Preliminary Configurations
A different completion behavior is possible, according to the configurations defined during the engineering phase.
In particular:
• The Check Material Consumption key determines whether the Work Order Operation can be completed
without a check on material consumption and material production.
• The setting of the Complete Work Order Operation by different user key together with the configuration of
the assigned machine determine which user can complete the Work Order Operations.
• Through the joint adoption of Work Operations and appropriate Work Order Operation configuration, upon
completing a Work Order Operation, it is possible to automatically start all of its successive Operations that
are in dependency AfterEnd.
• The Result Management key makes it possible to enable Result management on the completion of a specific
Work Order Operation when producing a particular Batch or Serial Number (Material Tracking Unit).
• The Result Strategy Management key works in combination with the Result Management key and makes it
possible to determine the corrective actions to be adopted by default when Result management is enabled.
• (Only for Serialized and FlexibleSerialized production types) The Complete Serial Number(s) without
pausing others key enables you to complete, for a specific Work Order Operation, some Serial Numbers, while
the remaining Serial Numbers remain active instead of being paused.
Procedure
1. In the Operator Landing page, select the Work Order Operation to complete.
2. (only for Work Order Operations started on multiple Machines) Select the Machines where the Work Order
Operation is to be completed.

Completing Work Order Operations
 If the Work Order Type is Serialized or FlexibleSerialized, the same User can complete different Serial
Numbers on the same Work Order Operation selecting different Workcenters/Machines.
If the Work Order Type is TransferBatch, the same User can complete different quantities on the same
Work Order Operation selecting different Workcenters/Machines.
3. Click Complete. Depending on the production type of the Work Order involved, proceed as described in the
following table:
Work Order Type Step to be performed
Serialized 1 Select the Serial Numbers and/or Containers to be completed. To include all
displayed Serial Numbers and Containers, select Select All.
2 For each of the selected Serial Numbers, if desired and provided that the Result
Management configuration key has been set, click the appropriate button ( OK,
NOK or Other Results) for Result to declare that the selected Serial Number
on the Work Order Operation is completed either successfully or otherwise.
This additional information is stored for future consultation.
 Clicking the Other Results button opens a drop-down containing the

following non-Default Result values: N/A, Not Executed and any
custom positive and negative Result values that may have been configured.
See Managing Work Order Operations for information on how the Results
declared for the various MTUs completed are displayed in the Work Order
Operation tiles in the Operator Landing Page.
3 Click Complete.
FlexibleSerialized See the steps to be performed for Serialized Work Orders above.
FullQuantity No action is necessary in this case: the entire quantity is automatically executed both
for specific Material Tracking Units and for Containers in which more than one MTU
has been loaded.
FullSerialized No action is necessary in this case: the complete list of Serial Numbers is
automatically executed, regardless of whether they are managed independently or
loaded into Containers.
 If you intend to declare a Result on FullSerialized MTUs, keep in mind that it

will be applied to all Serial Numbers.

Unloading Containers
Work Order Type Step to be performed
FlexibleBatch The system displays the number of Work Orders as Available/In Progress/Complete
with their respective status (Complete/Partial/Active).
 • The Freeze Target Quantity button is enabled only when the

Operation Type is Dynamic.
• The quantity of the MTUs in the Container cannot be edited once
the Container is ready to be completed. However, the quantity of
the MTUs not associated to any Container can be edited if
required.
TransferBatch The system displays the quantity of MTUs loaded into the Container and also displays
the quantity of MTUs in the Work Order Operation that are managed independently.
 The quantity of the MTUs in the Container cannot be edited once the
Container is ready to be completed. However, the quantity of the MTUs not
associated to any Container can be edited if required.
4. If your Production Coordinator selected Electronic Signature Complete creating the Work Order Operation,
you are prompted to type your password, some notes and then to click Validate User.
Note If password validation fails, you cannot proceed with completing the Work Order, but you may continue
handling Work Orders or Work Order Operations that do not have dependencies on this Work Order.
8.8 Unloading Containers

Once Work Order Operations in the Open or Partial status are associated to Containers and loaded with Material
Tracking Units, you can unload the MTUs present inside the Container before starting the Work Order Operation.
Depending on the requirement, Containers can be fully or partially unloaded, and as configured, fully unloaded
Containers can be reused or discarded.
Prerequisite
• The Work Order Operation is in the New, Open, Partial, or Complete status.
Procedure
1. In the Operator Landing page, select the Work Order Operation of interest.
 If you do not select a Work Order Operation, the Unload Container button will be disabled.
2. Click the Unload Container button.

3. In the Container step of the wizard, select one or multiple Containers to be unloaded.

How to Manage Additive Manufacturing-related Activities
4. Click Fully Unload, to completely empty the Container or click Next to unload the Containers partially.
Note If more than one Container is selected to be unloaded, the only unloading option available is Fully
Unload.
5. Depending on the Production Type, if the Work Order Operation belongs to
• Serialized or FlexibleSerialized production type, select the Serial Numbers to be unloaded in the Serial
Number step of the wizard.
• TransferBatch and FlexibleBatch production type, type the quantity to be unloaded in the Quantity
step of the wizard. If the quantity is not specified, the maximum quantity available is unloaded.
• FullQuantity and FullSerialized production type, the option to select Serial Numbers is not present. The
Container will be automatically unloaded with the quantity of the Final Material specified in the Work
Order.
Note: When Containers where the Is Reusable property is set to false, are completely unloaded, the
Container moves to the Discarded state and cannot be reused. The status of the Containers where this
property is set to true transition to the Ready state and are available for selection once more.
6. In the Serial Number or Quantity step of the wizard, click one of the following buttons:
• Unload and Repeat, to unload the selected Serial Numbers or specified quantity from the Container.
The unloading operation can be repeated to select more MTUs to be unloaded or to select MTUs from
more than one Container.
• Unload and Finish, to unload the selected Serial Numbers or specified quantity from the Container and
end the unloading operation.
8.9 How to Manage Additive Manufacturing-related Activities

For production in Additive Manufacturing contexts, additional runtime activities are foreseen, once 3D printing has
been completed.
These activities involve Substrates and Powder Material Batches.
After creating 3D products using Powder Material Batches on a metal Substrate, the final items must be detached
from the Substrates: this is referred to as part separation. After the 3D products have been detached, Substrates
may undergo specific treatment to permit their re-utilization in the best possible condition.
A treatment operation includes specialized procedures such as:
• machining and blasting, to optimize Substrate surface quality.
• heating or chemical layering, to ensure optimal surface structure or removal of residues.
• cleaning and troubleshooting, which can be carried out regularly and ensure that any impurities on the surface
of the Substrates are removed.
Treatment operations are aimed at optimizing the Work Order Operation to which it is associated.
Optimization also applies to Powder Material Batches. These activities involve:
• loading the Powder Batch into the 3D Printer, with the possibility to amend its quantity, if different from the
quantity expected or required, or to replenish it when necessary.
• recycling and mixing leftover Powder Material Batches to form a new Material to be used in a new production
cycle, once 3D printing has been completed.
Target User
Users with the Product Engineer role can perform these operations.
• Performing Substrate Treatment
• Reducing Substrate Thickness
• Maintaining Substrates

• Loading Powder Material Batches into 3D Printers

• Recycling Powder Material Batches
• Mixing Powder Material Batches
8.9.1 Performing Substrate Treatment

Between 3D printing jobs, Substrates must be regularly treated. Substrate treatment enhances Substrate traits such
as surface bonding property and surface wetting capability. Substrates can also be treated to ensure that the
surface layer of the Substrate adheres securely to the underlying layers. Opcenter Execution Discrete supports the
capability of treating Substrates that are associated with Work Order Operations.
Treatment operations are performed to render a Substrate more adapt for production; however, over time,
repeated treatment operations might reduce the quality of the Substrate. It might therefore be necessary to
perform Substrate maintenance.
Prerequisite
The status of the substrate is Available or Warning Available. For more information, see States and Lifecycles in
the Opcenter Execution Discrete Product Overview.
Procedure
1. Click Shopfloor Execution > Substrates in the main page.
2. On the Substrates page, click a substrate that you want to treat.
3. Click Execute Treatment.
Result
The treatment execution is initiated. A notification is sent to the operator who is assigned to the Work Order
Operation with which this Substrate is associated.
If a Substrate exceeds the maximum number of treatments it can undergo (Max. Treatment Count Warning value),
the status of the Substrate is set to Warning Available, and it is still available for production. However, if the
number of treatments exceeds the value specified by Max. Treatment Count Hold, the status of the Substrate is set
to OnHold, and it is not available for further treatment, or for production.
8.9.2 Reducing Substrate Thickness

Opcenter Execution Discrete supports the capability of reducing the thickness of a Substrate without having to
open it in edit mode. You can previously enter the thickness reduction value through the automatic thickness
decrease option, and later, simply click a dedicated button to reduce Substrate thickness. However, if you did not
set the thickness reduction value previously, you must open the Substrate in edit mode, and manually enter a
reduced thickness value.
Prerequisite
• The status of the Substrate is Available or Warning Available. For more information, see States and Lifecycles.
• When configuring the Substrate, the following parameters have been set: Automatic Thickness Decrease
and Amount Set for Automatic Thickness Decrease.
Procedure
1. Click Shopfloor Execution > Substrates in the sidebar.
2. On the Substrates page, click a Substrate the thickness of which you want to reduce.

3. Click the button.
Result
The Substrate's thickness is reduced. A notification is sent to the operator who is assigned to the Work Order
Operation with which this Substrate is associated.
If the thickness of this Substrate falls below the minimum thickness warning value, the status of the Substrate is set
to Warning Available, and it is still available for production. However, if the thickness falls below the minimum
thickness allowed (Min. Thickness Warning Hold value), the status of the Substrate is set to OnHold, and it is not
8.9.3 Maintaining Substrates

Substrates may undergo regular treatment procedures such as heating or peeling, to make them more suitable for
production. However, repeatedly treating Substrates might result in deterioration of their quality. For this reason,
maintenance activities are performed on Substrates to improve Substrate quality and ensure that it can be reused.
Prerequisite
The status of the Substrate is Available or Warning Available.
Procedure
1. Click Shopfloor Execution > Substrates in the main page.
2. On the Substrates page, click a Substrate on which you want to perform maintenance activities.
3. Click Execute Maintenance.
4. On the Substrate Maintenance page, set the following parameters:
Treatment Count Represents the number of times a Substrate is treated. For each
time that a treatment operation is performed, this value increases
by 1.
Current Thickness The current thickness value of the Substrate in millimeters.
Status One of the following:

• Available, indicates that the Substrate is available for
production.
• WarningAvailable, indicates that the Substrate's
Current Thickness has fallen below Min. Thickness
Warning or its Current Treatment Count has risen
above Max. Treatment Count Warning. The Substrate
is still available for production, but with a warning.
• Maintenance, indicates that the Substrate is
undergoing maintenance activities, and hence, is not
• OnHold, indicates that the Substrate is not available for
production.
5. Click Update.

8.9.4 Loading Powder Material Batches into 3D Printers

Powder Batches can be loaded into 3D Printers, specifying also their quantity.
The quantity of the Powder Batch loaded into a 3D Printer can be:
• amended ( button), if not aligned with the information stored in the system, for example because of
recycling operations or quantities lost during mixing jobs. The value inserted must be equal to (signifying that
the 3D Printer is empty) or greater than zero.
• replenished ( button), if necessary. You can choose to provide a new Source Batch value to mix the quantity
with another Powder Batch, otherwise the new quantity is added to the already loaded quantity.
Furthermore, it is possible to fully unload the Powder Material Batch previously loaded into a 3D Printer at any time,
by clicking the button.
 After you unload the Powder Batch from the 3D Printer, the amend and replenish operations are no longer
possible.
Procedure
1. Click Product and Production Configuration > 3D Printers in the sidebar.
2. In the 3D Printers page, select a 3D Printer and click .
3. Click the Powder tab.
4. Click the button and then set the following parameters:
Batch Id The batch to be loaded into the 3D Printer. If the Id provided does not
exist, the batch is created on-the-fly (the Quantity must be specified).
If more batches with the same code are found, the list of available
batches is displayed by clicking the Select button (not available in case
of only one Batch) and you must select one from the list.
Powder (Automatically filled if a Batch has been inserted in the Batch Id field).
Mandatory if the Quantity value is provided. A Powder must be selected
from the entity picker.
Quantity (Automatically filled if a Batch has been inserted in the Batch Id field).
The quantity to be loaded.
5. Click Load Powder.
8.9.5 Recycling Powder Material Batches

While printing 3D items, a Powder Material batch might not be completely consumed, leaving behind some Powder
Material. Opcenter Execution Discrete supports the capability of collecting and reusing leftover Powder Material
from one or more Powder Material batches. The dedicated process for reusing Powder Material is called recycling.
Powder Material from a Powder Material batch can be recycled in some way (for example, by sieving) in order to
remove impurities or make it ready for production. After recycling, Powder Material from different batches can be
mixed together, or with other Powder Material batches to support a 3D print.

Prerequisite
The Powder Material batch you want to recycle must have status as Busy or Quarantine.
 To change the status of a Powder Material Batch, select it in the Powder Recycle page and then click
Amend: this action allows you to edit the Quantity, the Recycle Count and the Status fields according to
your needs. Threshold checks regarding the congruity of the status transitions you want to apply will be
performed in this particular context.
Procedure
1. Click Shopfloor Execution > Powder Recycle in the sidebar.
2. In the Powder Recycle page, select the Powder Material batch that you want to recycle.
3. Click the Recycle button.
New Recycle Count The recycle count of the Powder Material batch that the system will
create. After each recycle instance, this value is incremented by 1, if
not specified otherwise.
The recycle count of the Powder Material batch must be equal to or
greater than zero, otherwise you cannot complete the recycling job.
New Name The name to be assigned to the Powder Material batch that the
system will create.
New Code The code to be assigned to the Powder Material batch that the
system will create.
New Quantity The quantity of the Powder Material batch that the system will
create. The quantity of the Powder Material batch must be equal to
or greater than zero, otherwise you cannot complete the recycling
job.
5. Click Recycle.
Result
The recycle operation has started. The number of recycle operations for this Powder Material batch can be traced
by using the Recycle Count and the Max. Recycle Count parameters. If Recycle Count becomes greater than
the Max. Recycle Count, the status of this Powder Material batch is automatically set to Spent, and the Powder
Material batch becomes unavailable for production. Threshold checks on the batch quantity will be performed in
this context as well.
In addition, the location of the Powder Batch (for example the 3D Printer) can be traced by using the Location
parameter.

8.9.6 Mixing Powder Material Batches

One or more Powder Material batches of the same Material can be mixed to form a new Powder Material batch. This
new batch can be used for 3D printing. You can mix leftover Powder Material from multiple batches, as well as
unused Powder Material batches, to create new Powder Material batches. The newly-created batch can then be
consumed by a Work Order Operation.
It is then possible to display the genealogy of Powder Material Batches to verify how they have been mixed.
Supported Scenarios
Opcenter Execution Discrete supports the following two use cases for creating new Powder Material batches:
• Two Powder Material batches with the same Material and UOM are selected. Possible cases are:
• the system creates a new Powder Material batch having the same Material and UOM as the source
Powder Material batches, provided that neither of the two has been chosen as target batch.
• the system performs the mixing without creating a new batch, because one of the two source batches
has been chosen as target.
• Only one Powder Material batch is selected but, during mixing, it is possible to pick an existing batch among
those which are compatible with the one selected, or to create a new one to be mixed with the first batch. The
system creates a new batch having the same Material and UOM as the two source Powder Material batches.
Prerequisite
The two Powder Material batches you want to mix must have the same Material and UOM, and their status must
be Available or Mixable.
Selecting Two Powder Material batches for Mixing

1. Click Shopfloor Execution > Powder Batch Mixing in the sidebar.
2. In the Powder Batch Mixing page, only the Powder Batches with quantity greater than zero are displayed.
Select the two Powder Material batches that you want to mix.
3. Click the Mixing button. In the Powder Batch Mixing pane, the following three sections are displayed, pre-
filled with the properties of the two batches selected in step 2:
• First Source Batch
• Second Source Batch
• Target Batch
4. Both First Source Batch and Second Source Batch display the following pre-filled parameters of the two
selected batches, which can also be edited according to your needs:
is Target Flag indicating if the source Powder Material batch is used as target
batch. It is possible to choose only one target batch at a time.
If this checkbox is selected:
• the Batch ID and the Quantity fields of the Powder Batch
are displayed in read-only mode,
• the field Batch ID of the Target Batch section is
automatically updated with the identifier of the source
batch.

Batch ID The unique identifier of the selected Powder Material batch.

It is also possible to:
• select another batch through the entity picker. Only those
batches which are compatible and thus can be mixed are
visible.
• create a new batch on-the-fly typing a new Identifier.
 If the Id of the Second Source Batch is not specified, the

system creates a new target batch on-the-fly whose quantity
equals the sum of the two batches.
Quantity The system automatically sets this field to a value which corresponds
to the quantity of the source batch selected, but you can change this
value.
The quantity of the Powder Material batch must be at least 1;
otherwise, you cannot complete the mixing job.
Recycle Count Represents the number of times the Powder Material Batch is
recycled. With each recycle operation, this value is incremented by 1.
You can change this value.
Min. Quantity The minimum value set for the quantity, below which the new Powder
Material batch will not be considered valid for production. The system
automatically populates this field with the value set as the quantity
threshold during the configuration of the Powder Material to which
the selected batch belongs, but you can change it.
Max. Recycle Count The maximum number of times the Powder Material Batch can be
recycled. The first time a Powder Material batch is created, its recycle
count is set to zero, and an upper cutoff value is specified using this
parameter. Thereafter, after each recycle instance, this number is
incremented, and the batch remains available for production so long
as its value does not exceed the maximum recycle count. You can
change this value.
5. In the Target Batch section, the system displays the following pre-filled parameters which are automatically
updated according to what is configured in the two sections above, but which can be changed according to your
needs:

Batch ID The unique identifier of the Powder Material batch that the system will
create at runtime.
There are two possibilities:
• if the is Target checkbox has been flagged neither for the first
nor for the second source batch, this field is empty and you
can insert a new Id, creating a batch on-the-fly.
• if the is Target checkbox has been flagged for one of the
source batches, this field displays the Id of the source batch
selected to be the target.
Quantity The quantity of the Powder Material batch that the system will create.
The system sets this field to a value that equals the sum of the quantities
of the two source batches. You can change this value but keep in mind
that it cannot exceeds the sum of the two quantities.
If you edit the quantity of the source Batch chosen as target, this value is
automatically updated by the system.
The quantity of the Powder Material batch must be at least 1; otherwise,
you cannot complete the mixing job.
Recycle Count The recycle count of the Powder Material batch that the system will
create. The system sets this field to a value that equals the greater value
of the two sources, but you can change this value.
After each recycle instance, this value is incremented by 1.
Min. Quantity The minimum quantity value of the Powder Material batch that the
system will create. The system sets this field to a value that equals the
higher of the two source values, but you can change this value.
Max. Recycle Count The maximum recycle count of the Powder Material batch that the
system will create. The system sets this field to a value that equals the
lower of the two values. The first time a Powder Material batch is created,
its recycle count is set to zero, and an upper cutoff value is specified
using this parameter. Thereafter, after each recycle instance, this value is
incremented, and the batch remains available for production so long as
its value does not exceed Maximum Recycle Count. You can change this
value.
6. Click Save.
Selecting a Single Powder Material batch for Mixing

2. In the Powder Batch Mixing page, select the Powder Material batch that you want to mix.
3. Click the Mixing button. The Powder Batch Mixing pane opens, displaying the First Source Batch section
with the pre-filled parameters of the selected batch, and the Second Source Batch section empty.

4. Perform either one or the other of the following operations in the Second Source Batch section:
• in the Batch ID field, select an existing batch with the entity picker. Only those batches which are
compatible and thus can be mixed are visible.
• in the Batch ID field, type the new Id, creating a Powder Batch on-the-fly. If the source batch is created
on-the-fly, the is Target flag is disabled. The Min. Quantity and Max. Recycle Count fields display the
data of the Powder associated with the first source batch, but both fields can be edited if necessary.
5. (Optional) Edit the other properties according to your needs. The Target Batch section updates accordingly.
6. Click Save.
Result
Actions performed on the Powder Batch (for example, changes in status, mixing or recycling) are traced in the
History tab. The details include: the user who performed the action, the date and time when the action was
performed, and so forth.

How to Execute Production on Execution Groups
Navigation of the Execution Group Working Environment at Runtime
9 How to Execute Production on Execution Groups

If your system contemplates using also Execution Groups to speed up production execution, you can choose to
execute these Execution Groups either alone or together with single Work Order Operations.
Target User
Prerequisites
The Operator must have the required credentials specified to execute all the Work Order Operations belonging to
the Execution Group.
Working Environment
The system provides a dedicated page for Production execution involving Execution Groups: for details, see
Navigation of the Execution Group Working Environment at Runtime.
Preliminary Operations
If no Execution Group to be executed already exists, you must necessarily create an Execution Group on the fly at
runtime.
In any case, if necessary, you can modify an existing Execution Group by linking Work Order Operations to it
according to your needs prior to launching its execution.
Workflow
1. Start an Execution Group.
2. Manage the Work Order Operations that were started in the Execution Group as you would when executing
single Work Order Operations.
In addition (or in alternative) to the above, if required by your production process, perform one or both of the
following:
• In cases of Additive Manufacturing, consume the Materials.
• Manage the Work Instructions associated to Execution Group Phases.
3. (optional) Pause and resume the Execution Group.
4. Complete an Execution Group.
9.1 Navigation of the Execution Group Working Environment at

Runtime
When executing Work Orders, you can perform various activities on an Execution Group previously started.
Runtime managing of Execution Groups is a complex procedure that depends from the various parameters set
during their creation. There is no unique workflow and it may consist of several independent steps without a fixed
order.
Prerequisite
Runtime configuration key Show Execution Groups in Operator Landing Page must be set.

Navigation of the Execution Group Working Environment at Runtime
In the Operator Landing page, select the Execution Group Phase that is currently active and then click the
Show Details button.
Environment Description
• Header Bar - Displays the details of the current Execution Group Phase.
• Task List - Displays the tasks to be performed during the current Execution Group Phase.
• Center Zone - Displays the details of the task to be currently performed.
• Bottom Bar - Displays a set of buttons to perform various activities on the current Execution Group or Execution
Group Phase.
Information Available in the Header Bar

The top Header Bar displays the details of the current Execution Group.
The Header Bar displays all the Users active on the Execution Group Phase and their individual association with
Machines and Serial Numbers or Batches.
Operations Available in the Task List

The Task List displays the tasks to be performed during the current Execution Group Phase. Click on a task to
display its details in the center zone.
Operations Available in the Center Zone

The Center Zone displays the details of the task to be performed during the selected Execution Group Phase. Refer
to the Managing Tasks for Work Order Operation or Step Progression section for details about the available tasks.
In addition, if a Print Job File Transfer task is required, an additional button is available in the toolbar to add
the new Print Job File to be used.
9.1.1 Operations Available in the Bottom Bar

Click on the following buttons:

How to Prepare Execution Groups during Production Execution
• Start to start the current Execution Group Phase.

• Pause to pause the current Execution Group Phase.
• Complete to complete the current Execution Group Phase.
• Document Preview to view the Documents attached to the selected Execution Group Phase. Refer to
the Previewing Document Files section for details.
9.2 How to Prepare Execution Groups during Production Execution

Before executing Work Order Operations, to permit their simultaneous execution (even if they belong to different
Work Orders), you can choose to:
• create a new Execution Group on the fly.
• link one or more Work Order Operations to an existing Execution Group.
9.2.1 Creating an Execution Group On The Fly

 Once you have created an Execution Group at runtime, it is automatically released.
Target User
Procedure
1. In the Operator Landing page, select the Work Order Operations to be used to form an Execution Group and
click More > Execution Groups in the bottom bar. The Link Operations to Execution Group panel is displayed.
2. (Optional) If the available quantities of Serial Numbers and/or Batch Items to be produced by some Work Order
Operations are displayed in the lower panel, for each of these Work Order Operations, type the quantity to be
produced by the Execution Group you are creating in the Quantity cell. The remaining quantity can be managed
by Work Order Operations not belonging to the Execution Group
3. Click Create.
4. In the Create Execution Group panel, set the following parameters:
Identifier Unique Identifier of the Execution Group.
Name The name of the Execution Group.
Description Useful information about the Execution Group.
Estimated Duration Estimated duration necessary to execute the Execution Group. It

is expressed in hours, minutes, seconds.
Estimated Start Time The date and time when the Execution Group is expected to
start.

How to Prepare Execution Groups during Production Execution
Estimated End Time The date and time when the Execution Group is expected to
end.
5. Click Create.
 Execution Groups created on the fly can be scheduled via the APS Sequencer in the same manner as
Execution Groups created during engineering: for more information, see Scheduling an Execution Group.
9.2.2 Linking Work Order Operations to an Existing Execution Group

 Once you link a Work Order Operation to an existing Execution Group, you cannot unlink it: only a
Production Coordinator can perform an Unlink, operating from a dedicated page.
Keep in mind that unlinking a Work Order Operation from an Execution Group automatically unlinks also
all the other Work Order Operations belonging to the same Work Order.
Prerequisites
All the Work Order Operations that are to be linked to • have at least one common Machine on which they
an Execution Group must..... can be executed within the same Execution Group
Phase.
• use Tools belonging to the same Tool Definitions, if
any.
• consume Material Tracking Units belonging to the
same Materials, if any.
• require the same Skill and Skill Levels, if any.
• have a dependency on the next Work Order
Operation.
• belong to a Work Order with Production Type that
differs from FlexibleSerialized and FlexibleBatch.
The Work Operations associated to the Work Order • Not possess any of the following attributes:
Operations must... • Milestone
• Optional
• Only One Active
• Auto-Start
• Auto-Complete
• Machine Auto-Start
• Machine Auto-Complete
• Machine Auto-Pause
• Can be skipped.
• Quality Only
• Dynamic.

Starting Execution Groups
The Execution Groups to which you want to link the Have not yet been released.
selected Work Order Operations must....
Target User
Procedure
1. In the Operator Landing page, select one or more Work Order Operations to be linked to an existing Execution
Group and click More > Execution Groups in the bottom bar. The Link Operations to Execution Group panel is
displayed.
2. (Optional) If the available quantities of Serial Numbers and/or Batch Items to be produced by some Work Order
Operations are displayed in the lower panel, for each of these Work Order Operations, type the quantity to be
produced by the current Execution Group in the Quantity cell. The remaining quantity can be managed by Work
Order Operations not belonging to the Execution Group.
3. Select the Execution Group to which the Work Order Operations are to be linked.
4. Click Link.
 The Execution Groups tab on the Work Orders page displays the Execution Groups currently linked to any
of the Work Order Operations belonging to the selected Work Order. Select an Execution Group and click
Open.
9.3 Starting Execution Groups

To execute several Work Orders simultaneously, you must start an Execution Group.
Starting an Execution Group involves starting all the Work Order Operations linked to it or, if Execution Group
Phases are present, all the Work Order Operations belonging to the current phase.
 Execution Groups and Step Execution

If Work Order Operations containing Steps are linked to an Execution Group, when the Execution Group is
executed, only the Work Order Operations will be involved, and not their associated Steps. These Steps
must be executed individually in the standard mode for each single Work Order.
Procedure
1. In the Operator Landing page, select the Execution Group to start and then click Start.
2. (optional) If the Execution Group is partially linked to at least one Work Order Operation of Serialized
Production Type, a distinct list of Serial Numbers for each Work Order Operation is displayed. Select the Serial
Numbers to be started.
 • For each list, you must select exactly the required quantity of Serial Numbers.
• If Execution Group Phases are present, Serial Numbers are selected only when starting the first
one. The selection is maintained for all subsequent Execution Group Phases.
• If a Serial Number has been previously started (for example, by another User), the icon is
displayed in its tile.
• Serial Numbers already loaded into Containers cannot be started.

Consuming Materials of type Additive from an Execution Group
3. In the Start Execution Group panel, select the Equipment on which the Execution Group or the current
Execution Group Phase must be started.
 • Different Execution Group Phases can be started on different Equipment, chosen among those
that the linked Work Order Operations have in common. If a preferred Machine had been
specified while editing the current Execution Group Phase, the icon is displayed in the
Machine tile.
• If Setpoints have been defined for Machines and the Setpoint Variables are linked to
Automation Node Parameters, the related variables are automatically transmitted to the
Machine when the Execution Group is started on that Machine. If properly configured, the
Setpoint Variables are editable at runtime and you can check the transmitted variables, along
with their values.
4. Click Save.
What to do next
After starting an Execution Group, you can display the details of the Work Order Operations linked to it and manage
them. Later, you can complete the Execution Group.
Active Execution Groups can be paused if needed.
9.4 Consuming Materials of type Additive from an Execution Group

You can consume Materials of type Additive Manufacturing all having the same characteristics (Type and Quantity)
in all the Work Order Operations making up an Execution Group at the same time. The Procedure below shares
much of what is illustrated for assembling Material Tracking Units.
Procedure
1. In the Operator Landing page, start the required Execution Group Phase and click the Show Details button.
The Operator Task list page is displayed.
2. Select the Material Consumption Task from the Task list that is displayed. The Materials to be consumed for
the task are displayed on the central panel: the Quantity field displays the entire quantity to be consumed for
all Work Order Operations associated with the Execution Group. The total quantity of Materials can be edited as
required and is consumed at one time for the tasks to which they are associated. The Execution Group icon
on the accordion indicates that the material is consumed by an Execution Group Phase.
3. Select the Material to be consumed and click the Expand button. Enter the Serial Number/ Batch Id for the
selected Additive Material.
4. Click the Assemble button.
9.5 How to Manage Work Instructions for Execution Group Phases

Work Instructions associated to Execution Group Phases provide Operators with detailed steps or instructions on
how to carry out tasks during production and/or indications as to what runtime data must be inserted.
In the case of Work Instructions containing Acknowledge steps, the instructions are associated to the entire
Execution Group Phase and must be acknowledged by the Operator.
Work Instructions containing DataCollection steps on the other hand can be:
• Associated with the entire Execution Group Phase.
• Associated with all the Serial Numbers produced by the Execution Group Phase.

How to Manage Work Instructions for Execution Group Phases
• Associated with only some of the Serial Numbers produced by the Execution Group Phase.
The history of all the Work Instructions linked to the Execution Group Phases is captured on the Execution Group
page.
Details such as the Execution Group identifier details, Execution Group Phase identifier details, Step Type, etc. are
also logged in the As Built reports and the Genealogy page when Work Order Operations are associated to Work
Instructions at the Execution Group Phase level.
Prerequisite
Work Instructions are linked to Execution Group Phases
• Acknowledging Work Instructions
• Providing Values for Data Collections associated with an Execution Group Phase
• Providing Values for Data Collections associated with all Serial Numbers
• Associating Data Collections to specific Serial Numbers.
Acknowledging Work Instructions

1. While managing the current Execution Group Phase, select the Work Instruction task. By default, only the tabs
that contain Work Instructions are displayed.
2. Read the displayed Work Instructions.

3. Click Acknowledge.
 If Result management has been enabled and you have already acknowledged your Work Instruction, if
the Execution Group Phase involved must be repeated due to a negative Result declared on one or
more MTUs, you must re-acknowledge it in order for the execution to be repeated.
Providing Values for Data Collections associated with an Execution Group

Phase
1. While managing the current Execution Group Phase, select the Work Instruction task.
2. Select the Work Instructions For EG Phase tab.

Collections associated with the Execution Group Phase. Before being confirmed, the values can be updated
Providing Values for Data Collections associated with all Serial Numbers

Pausing and Resuming Execution Groups
Help
2. Select the SN Work Instructions For EG Phase tab.
3. On the top, all the Serial Numbers currently started are displayed: select the one for which you want to fill the
Data Collections.
Associating Data Collections to specific Serial Numbers

2. Select the SN Work Instructions For EG Phase tab.

3. Click Add.
4. In the Add Data Collection page, select:
• one Serial Number
• one or more Data Collections.
5. Click Add to associate the selected Serial Number to the Data Collections.
9.6 Pausing and Resuming Execution Groups

An Execution Group that is currently in execution can be paused. This action pauses all the Work Order Operations
making up the Execution Group at once so to permit the correction or verification of the issue that warranted the
pause. After the issue has been corrected or clarified, the Execution Group can be resumed.
Prerequisite
At least one Pause Reason has been configured.
Procedure
1. In the Operator Landing page, select an Execution Group in Active status.
2. Click Pause.
3. In the Select Reason panel, select a Reason for pausing the Execution Group and click OK.
Result
The system sets the status of the Execution Group to Pause and pauses all the Work Order Operations that make up
the Execution Group: if you want to resume the Execution Group, click Start.

Completing Execution Groups
9.7 Completing Execution Groups

When executing Work Orders, you can complete Execution Groups which have been
previously started and managed.
If Execution Group Phases are present, the Complete action completes all the Work Order Operations belonging to
the current phase. A subsequent Start action on the same Execution Group will start the next phase. The
completion of the last phase actually completes the Execution Group.
If a Work Instruction has been associated to an Execution Group Phase, it is mandatory that you either provide
values for the Data Collections contained in the Work Instruction and/or acknowledge the Work Instruction in order
to complete the Execution Group Phase.
To speed up the production process, an Execution Group started by one Operator can be completed by another
Operator if the proper configurations are performed during the engineering phase.
A different completion behavior is possible, according to the configurations defined during the engineering phase.
In particular, the Check Material Consumption key determines whether the Execution Group can be completed
without a check on material consumption.
Procedure
1. In the Operator Landing page, select the Execution Group to complete.
2. Click Complete: the completion of the entire Execution Group will be triggered.

How to Execute Production in Offline Mode
10 How to Execute Production in Offline Mode

Offline sessions are production execution sessions performed without connectivity to the Opcenter EX DS server.
Once an Offline Session is created on the mobile device, you can see its details in terms of its Work Order
Operations.
After uploading the Offline Session from the mobile device to Opcenter EX DS, the list of the related Offline Actions
can be accessed. This allows you to perform operations such as Amend, Check-In and Discard.
An Offline Action in the Failed status can be amended and checked-in again. The Refresh icon manually loads
the current status of the Offline Sessions and Offline Actions.
An Offline Session can also be discarded: for example, if errors are raised during check-in. When an Offline Session is
discarded, the involved Work Order Operations are unlocked and return available for execution from the Operator
Landing Page.

To access the Offline Sessions page, click Production Coordination > Offline Sessions in the sidebar.
• Displaying Work Order Operations in Offline execution
• Displaying Uploaded Offline Actions
• Checking In Offline Sessions
• Checking In Offline Actions
• Amending Offline Actions
• Discarding Offline Sessions
Displaying Work Order Operations in Offline execution

1. In the Offline Sessions page, select and open the Offline Session of interest.
2. Click the Work Order Operations tab.
Displaying Uploaded Offline Actions

1. In the Offline Sessions page, select and open an uploaded Offline Session.
2. Click the Offline Actions tab to access the details of the related uploaded Actions.
Checking In Offline Sessions

1. In the Offline Sessions page, select the uploaded Offline Sessions.
2. Click Check-In to perform a check-in of the Offline Sessions.
3. If the check-in process fails, amend the Action and repeat the check-in of the Offline Session.
Checking In Offline Actions

1. In the Offline Sessions page, navigate to the Offline Actions tab and select the uploaded or failed Offline
Actions.
2. Click Check-In to perform a check-in of the Offline Actions.
3. If the check-in process fails, amend the Action and repeat the check-in of the Offline Action.

How to Execute Production in Offline Mode
Amending Offline Actions

1. In the Offline Sessions page, select the Offline Session of interest.
2. From the Offline Actions tab, select the Offline Action in the Failed status that needs to be edited.
3. Click Edit to edit the Command Payload content and then click Save.
4. Click the Refresh icon to manually load the current status of the Offline Sessions and Offline Actions.
 It is possible to view how the check-in of the Offline Sessions and Actions is progressing in the Progress of
Check-in column of the Offline Sessions page.
Discarding Offline Sessions

1. In the Offline Sessions page, select the Offline Session of interest.
2. Click .
 In those cases in which a check-in is in progress, those check-in operations that have been completed
successfully up to this moment will not be undone (reverted).

How to Manage Non-Conformances
11 How to Manage Non-Conformances

During the execution of manufacturing activities, shop floor operators might encounter anomalies in Work Order
Operations or in related entities. In such scenarios, operators can bring these anomalies to the notice of Production
Coordinators by declaring Non-Conformances. Operators can raise a Non-Conformance if:
• A defect or failure was detected during production (Quality Non-Conformance).
• They find that something needs to be changed in the production process (Change Non-Conformance, also
known as a Change Request).
An Operator can declare Non-Conformances from the Operator Landing page during the execution of a Work Order
Operation.
In addition, the Production Coordinator can declare a Quality Non-Conformance:
• on a Work Order Operation already completed (for example, if the Operator did not detect the anomaly during
production).
• on any Machine, Material Tracking Unit or Tool, whenever deemed appropriate and not necessarily during
actual production execution.
 If multi-plant support is active, Non-Conformances can be assigned with Data Segregation tags: for
information, see Managing Multi-Plant Support.
Automatic Creation of Non-Conformances in Integration with Opcenter Connect

MOM
It is possible to automatically create Non-Conformances in integration with Opcenter Connect MOM. Quality Non-
Conformances can be declared on:
• Work Order Operations: if anomalies are detected during their execution. It is possible to automatically create
Quality Non-Conformances on Work Order Operations. For more information, see How to Automatically Create
Non-Conformances of type Quality on Work Order Operations in Opcenter Execution Discrete Installation and
• Machines: for example, if a Machine breaks down. It is possible to automatically create Quality Non-
Conformances on Machines. For more information, see How to Automatically Create Non-Conformances of type
Quality on Machines in Opcenter Execution Discrete Installation and Configuration Manual.
• Material Tracking Units: for example, if a component to be assembled is found defective. It is possible to
automatically create Quality Non-Conformances on Material Tracking Units. For more information, see How to
Automatically Create Non-Conformances of type Quality on Material Tracking Units in Opcenter Execution
Discrete Installation and Configuration Manual.
• Tools: for example, if a Tool wears out before its predicted lifespan.
Target User
Users with the Operator and Product Coordinator role can perform this procedure.
Prerequisites
• Depending on the requirement, the Non-Conformance on Defect or Failure configuration key value is set
to Defect or Failure.
• The Failures or Sub-Failures for which the Non-Conformance is to be declared have been created from the
Failures page. Refer to How to Manage Failures and Quality Actions in the Opcenter Execution Foundation User
Manual for details.

Declaring Quality Non-Conformances during Production
Workflow
1. Declare a Non-Conformance:
• (Operator): Quality or Change
• (Production Coordinator): Quality on a Work Order Operation or Quality on a Machine, Material Tracking
Unit or Tool.
2. (Production Coordinator) Handle the Non-Conformance.
• Quality
• Change
11.1 Declaring Quality Non-Conformances during Production

If a defect or failure was detected during production, you must open a Quality Non-Conformance.
 Quality Non-Conformances and Multi-Plant Support

When declaring a Quality Non-Conformance, if multi-plant support is active, keep the following in mind:
• If the Quality Non-Conformance has been created from scratch, the Data Segregation tags selected in
the dedicated widget will be automatically applied to it.
• If you have made a copy of an existing Non-Conformance, when a Split of the Work Order has been
performed, the Data Segregation tags will be copied from the parent Non-Conformance to the new
Non-Conformance.
• If the Non-Conformance has been created automatically, no Data Segregation tag will be associated to
it.
Prerequisite
The involved Work Order Operation is in status Open or Active.
Procedure
1. In the Operator Landing page, click Defects.
2. Depending on your configuration, do either of the following:
• if you are using Defects, select the applicable defect group in the Defect Groups area.
• if you are using Failures, select the required failure in the Failures area.
Note Only Failures set as Current are displayed.
3. If the selected item contains sub-groups or sub-failures, select the item of interest.
4. Select one or more defect types or failures: the selections are displayed in the Selected Defect Types or the
Selected Failures area.
5. Click Add Defects/Add Failures.
6. In the Declare Non-Conformance panel, set the following parameters:
Parameters Description
Context The entity type on which the Non-Conformance is to be declared:

• Machine
• Material Tracking Unit
• Tool
Identifier Unique identifier to be assigned to the Non-Conformance. Once saved,


Declaring Quality Non-Conformances during Production
Notes A short description of the defect observed.
Severity The severity for the defect. Possible values are: LOW, MEDIUM, HIGH.
7. According to the value selected for the Context parameter, perform the required operations:
If Context is set to Do the following
Work Order Operation Set the following parameters:

• Work Order: The Work Order to which the Non-Conformance is
associated. The field is pre-set with the current Work Order.
• Work Order Operation: The Work Order Operation to which the Non-
Conformance is associated. The field is pre-set with the current Work
Order Operation.
• Set either of the following according to the production type:
• Non-Conformance Quantity: (if the involved Work Order is of
type FullQuantity or TransferBatch) the number of instances
of the product for which the Non-Conformance is observed.
Note If the Non-Conformance is declared on a Container, the
quantity must be equal to the number of items contained in it.
• Material Tracking Units area: (if the involved Work Order is of
type Serialized or FullSerialized) click Link and select the
Serial Numbers and/or Containers on which the Non-
Conformance is to be declared.
Machine In the Equipment area, click Link, select one or more items on which the
Non-Conformance is to be declared and then click Link.
Material Tracking Unit In the Material Tracking Units area, click Link, select one or more items on
which the Non-Conformance is to be declared and then click Link.
 This area shows both the individual MTUs and the Containers that may
be present. Declaring a Non-Conformance on a Container means
declaring the Non-Conformance on all the contained Material Tracking
Units.
Tool In the Tools area, click Link, select one or more items on which the Non-
Conformance is to be declared and then click Link.
8. In the Documents area of the Declare Non-Conformance panel, click Link. The list of available Documents
is displayed.
9. If the Document you want to add is not already in the list, click Import to import it.
10. Select one or more Documents from the list and click Link to associate them to the Non-Conformance.

Declaring Quality Non-Conformances on Work Order Operations
 If there are Segregation tags associated to the Document you want to link to a Non-Conformance, the
resulting association (Non-Conformance Attachment) will automatically inherit these tags.
11. Click Save.
Results
• A Non-Conformance is created in status Open.
• The status of the last Work Order Operation making up the Work Order is changed to Future Hold. Its color is set
to red in the dependency graph.
• If the proper signal has been configured, the notification bar displays a number (or increments the existing one)
on the icon, thus prompting the Production Coordinator to manage the Non-Conformance.
11.2 Declaring Quality Non-Conformances on Work Order

Operations
This procedure allows a Production Coordinator to declare a Quality Non-Conformance on Work Order Operations.
Contrary to an Operator, a Production Coordinator can declare Non-Conformances even on completed Work Order
Operations. For example, an anomaly not noticed by an Operator during production can be declared at a later time.

Non-Conformance.
it.
Target User
Workflow
1. Create the Non-Conformance.
2. Associate Defects or Failures to the Non-Conformance.
3. (optional) Associate Documents to the Non-Conformance
4. (optional) If one or more of the associated Documents are PNG or JPG pictures, highlight them.
Creating Non-Conformances
1. Click the Non-Conformances tile in the home page
2. In the Non-Conformances page, click Create.
3. In the Declare Non-Conformance page, set the following parameters:

Declaring Quality Non-Conformances on Work Order Operations
Context The entity type on which the Non-Conformance is to be

declared. Set this parameter to Work Order Operation.
Note Setting this parameter to other values allows you to
declare Non-Conformances on Production Entities.
Identifier Unique identifier to be assigned to the Non-Conformance. Once

Work Order The Work Order to which the Non-Conformance is associated.
Work Order Operation The Work Order Operation to which the Non-Conformance is
associated.
Note this field appears only after selecting a Work Order.
Non-Conformance Quantity The number of instances of the product for which the Non-
Conformance is observed.
Note If the Non-Conformance is declared on a Container, the
quantity must be equal to the number of items contained in it.
Severity The severity for the defect. Possible values

are: LOW, MEDIUM, HIGH.
4. If the Work Order is of Serialized or FullSerialized type, in the Material Tracking Unit area select the MTUs to
be linked to the Non-Conformance.
Note You can select both Material Tracking Units and Containers. Selecting a Container means selecting at the
same time all its contained MTUs.
5. To attach a supporting document such as a log file or a screenshot, in the Documents area either click
Import to import a document from the local filesystem or Link to attach a document previously imported
into the system.
Note You can also associate Documents at a later time, see the Associating Documents to Non-
Conformances paragraph for details.
6. Click Create.
Associating Defects or Failures to Non-Conformances

1. In the Non-Conformances page, select the Non-Conformance and click Open.
2. Click the Defects tab.
3. Add previously-created Defects or Failures to the Non-Conformance by clicking Add and then selecting the
Defect Groups/Failures and Defect Types/Sub-Failures of interest.
Associating Documents to Non-Conformances
 If there are Segregation tags associated to the Document you want to link to a Non-Conformance, the
resulting association (Non-Conformance Attachment) will automatically inherit these tags.

Declaring Non-Conformances of type Quality on Production Entities

3. Click Add. The list of available Documents is displayed.
• If the Document you want to add is not already in the list, click Import to import it.
• Select one or more Documents from the list and click Add to associate them to the Non-Conformance.
Highlighting defects on pictures

If a document associated to a Non-Conformance is a picture in .JPG or .PNG format, you can draw colored lines or
shapes on it in order to highlight the defect.

3. From the list of attached Documents, select a picture in .JPG or .PNG format.
4. Click Red Lining.
5. In the Red Lining window, specify a meaningful Name to be used to differentiate the Document with the
highlights from the original Document.
6. Use the graphical instruments to draw lines, shapes or to type short notes on the picture. If required, you can
also use the Eraser icon to edit and reapply the highlighting.
7. Click Save. A new picture containing the highlights is created and associated to the Non-Conformance: the
indicator will be displayed inside the tile representing the new Document to specify that the .JPG or .PNG file
contained therein has been red-lined.
Result
on the icon thus prompting the Production Coordinator to manage the Non-Conformance.
11.3 Declaring Non-Conformances of type Quality on Production

Entities
This procedure allows a Production Coordinator to declare a Quality Non-Conformance on the following production
entities:
• Machines
• Tools
Quality Non-Conformances can be declared on production entities in two ways:
• By creating a Non-Conformance and then linking it to a Machine, Material Tracking Unit or Tool.
• By selecting a Tool and then creating a Non-Conformance on it.


Non-Conformance.
it.
Target User
Associating Non-Conformances to Production Entities

1. Operating on the sidebar, click Shopfloor Execution > Non-Conformances.
2. In the Non-Conformances page, click Create.
Context The entity type on which the Non-Conformance is to be declared.

Set this parameter according to the required production entity
type:
- Machine
- Material Tracking Unit
- Tool
 Setting this parameter to Work Order Operation allows

you to declare Non-Conformances on Work Order
Operations.
Natural Identifier Unique identifier to be assigned to the Non-Conformance. Once

Severity The severity for the defect. Possible values

are: LOW, MEDIUM, HIGH.
4. Click Link: this opens a dedicated Link Items panel, the content of which depends on the value set at step 3
for Context.
5. In the Link Items area, select one or more items (either Machines, Material Tracking Units or Tools, according to
the context) on which the Non-Conformance is to be declared and click Link.

 If Context has been set to Material Tracking Units, the area shows both the individual MTUs and the
Containers that may be present. Declaring a Non-Conformance on a Container means declaring the
Non-Conformance on all the contained Material Tracking Units.
6. Click Save: this returns you to the Non-Conformances page, which now lists the Non-Conformance you have
just created.
7. Select the Non-Conformance you have just created and click Open.
8. Click the Defects tab.
9. Add previously-created Defects or Failures to the Non-Conformance by clicking Add and then selecting the
Defect Groups/Failures and Defect Types/Sub-Failures of interest.
10. (optional) To associate Documents to the Non-Conformance:
• In the Non-Conformances page, select the Non-Conformance and click Open.
• Click the Documents tab.
• Click Add. The list of available Documents is displayed.
• Do either of the following:
• If the Document you want to add is not already in the list, click Import to import it.
• Select one or more Documents from the list and click Add to associate them to the Non-
Conformance.
 If Segregation tags have been associated to the Document to be linked to the Non-
Conformance, the resulting link (Non-Conformance Attachment) will inherit these tags.
Highlighting defects on pictures

If a document associated to a Non-Conformance is a picture in .JPG or .PNG format, you can draw colored lines or
shapes on it in order to highlight the problem.

3. From the list of attached Documents, select a picture in .JPG or .PNG format.
4. Click Red Lining.
5. In the Red Lining window, specify a meaningful Name to be used to differentiate the Document with the
highlights from the original Document.
6. Use the graphical instruments to draw lines, shapes or to type short notes on the picture. If required, you can
also use the Eraser icon to edit and reapply the highlighting.
7. Click Save. A new picture containing the highlights is created and associated to the Non-Conformance: the
indicator will be displayed inside the tile representing the new Document to specify that the .JPG or .PNG file
contained therein has been red-lined.
Editing Production Entities associated to Non-Conformances

When one or more Production Entities are associated to a Non-Conformance, the corresponding tab (either
Machines, Material Tracking Units or Tools) can be clicked in the Non-Conformances page.
1. Click the appropriate tab to display the associated Production Entities.
2. To link additional Entities to the Non-Conformance, click Link, select one or more Entities and click Add.
3. To remove a link between an associated Entity and the Non-Conformance, select the entity and click
Unlink.

Declaring Change Non-Conformances
 In the Material Tracking Units tab it is possible to select both Material Tracking Units and Containers.
Linking a Container means linking all the contained Material Tracking Units at the same time.
Associating Tools to Non-Conformances

1. In the Home page, select the Tools page.
2. Select the Tool on which you want to declare the Non-Conformance and click Add Defects.
3. Depending on your configuration, you will either see the Add Defect or the Browse Failures panel.
4. Select the applicable defect group in the Defect Groups area or select the required failure from
the Failures area.
5. If the selected item contains sub-groups or sub-failures, select the item of interest.
6. Select one or more defect types or failures: the selections are displayed in the Selected Defect Types or in
the Selected Failures area.
7. Click Add Defects/Add Failures.
Identifier Unique identifier to be assigned to the Non-Conformance. Once saved,

Severity The severity for the defect. Possible values are: LOW, MEDIUM, HIGH.
9. To attach a supporting document such as a log file or a screenshot, click the icon available in the top-right
corner.
 If you want to add other Tools to be associated to the Non-Conformance, in addition to the one
currently selected, click Link, select the entities on which the Non-Conformance is to be declared
and click Add.
10. Click Save.
Result
on the icon thus prompting the Production Coordinator to manage the Non-Conformance.
11.4 Declaring Change Non-Conformances

Typically, an Operator declares a Change Non-Conformance (also known as a Change Request) if the Process
Definition related to a Work Order Operation requires a change. For example, if the sequence of tasks in a Work
Order Operation is not correct, an Operator can open a Change Request to notify Production Coordinators that the
task sequence needs to be modified.

If necessary, Production Coordinators can also declare Change Requests. For example, if a problem is detected on a
Machine after releasing a Work Order, the Production Coordinator can open a Change Request to ask for a new
workplace.
After a Change Request is created, Production Coordinators are notified in merit and can subsequently confirm or
reject the Change Request. If confirmed, the Work Order Operation for which a Change Request is raised is suitably
altered to accommodate the change.
If the Change Request involves adding a Work Instruction containing a Data Collection section, the operator can
choose to add it to the entire Work Order Operation or only to specific Serial Numbers.
 Change Requests and Multi-Plant Support

If multi-plant support is active, when declaring a Change Request, the resulting Non-Conformance will be
automatically assigned with the Data Segregation tags that were selected in the dedicated widget at the
time of its creation.
Target User
Users with either the Operator or Production Coordinator role can perform this action.
Prerequisite
A Work Order Operation has been started.
Procedure for Operators

1. In the Operator Landing page, after selecting the Work Order Operation for which you want to declare a Change
Non-Conformance, operating on the bottom bar, select More > Change.
2. In the Notes box, type a description for the change request to be performed.
3. From the list of changes defined, click the change request to be performed. The following options are available:
• Add Work Instruction
• Add Work Instruction to SN
• Add Operation
• Add Part
• Add Process Operation
• Add Tool
• Replace Part
• Change Part Qty
• Change Routing
• Delete Dependency
• Remove Operations
• Remove Part
• Repeat Operation
 For more information, see Example of a Repeat Operation Change Non-Conformance.
4. Click Save.
Procedure for Production Coordinators

1. Click the Change Management tile in the home page.

2. Click Create: the Add Change Non-Conformance page is displayed.

3. For each of the following parameters shown in the page, click the button: this calls up the respective Select
Item dialog, in which you must set the parameters according to your needs and then click Select:
Work Order The Work Order that contains the Work Order Operation requiring a change.
Work Order The Work Order Operation for which a Change Non-Conformance is required.
Operation
Type of Change The type of change required:

• Add Operation
• Add Part
• Add Process Operation
• Add Tool
• Add Work Instruction
• Add Work Instruction to SN
• Change Part Qty
• Change Routing
 This particular Change Request cannot be declared when the Work

Order Operation for which you want to change the routing of the
Work Order involved belongs to an Alternative Group. For more
information, see Defining Groups of Alternative Work Order
Operations.
• Delete Dependency
• Remove Operations
• Remove Part
• Repeat Operation
 For details, see Example of a Repeat Operation Change Non-

Conformance.
• Replace Part
Notes Notes, if any.

4. Click Add.
Results
• The Work Order, as well as the Work Order Operation for which a Change Request was raised, are represented by
a warning icon.
• The Production Coordinator is prompted to manage the Non-Conformance.
on the icon, thus prompting the Production Coordinator to manage the Non-Conformance.

Example of a Repeat Operation Change Non-Conformance
11.5 Example of a Repeat Operation Change Non-Conformance

The following example illustrates how declaring a Repeat Operation Change Non-Conformance on a Work Order
Operation affects your workflow.
Let's say your initial Work Order 001-Rebuild contains two Work Order Operations (Rebuild-Op10 and Rebuild-Op20),
both of which have RepeatNumber set to 0.
Once the first Work Order Operation (Rebuild-Op10) has been completed, the value of RepeatNumber will still be 0
for both Work Order Operations.
At this point, you decide that you want Work Order Operation Rebuild-Op10 to be repeated: you declare a Repeat
Operation Change Non-Conformance.
 Repeat Operation Change Non-Conformances can be declared only on completed Work Order
Operations.
After this Repeat Operation Change Non-Conformance has been declared, it must be sentenced (accepted),
specifying at what point Work Order Operation Rebuild-Op10 must be repeated within the sequence of Work Order
Operations available for Work Order 001-Rebuild: in this case, let's say it must be repeated immediately after Work
Order Operation Rebuild-Op10 (10) and immediately before Work Order Operation Rebuild-Op20 (20).

Example of a Repeat Operation Change Non-Conformance
After the Change Non-Conformance has been accepted, the system will insert this new Work Order Operation to be
repeated (that is, Rebuild-Op10 with sequence 15) into the workflow: it will be displayed as Rebuild-Op10 (15)
between Rebuild-Op10 (10) and Rebuild-Op20 (20).
Note that the value of RepeatNumber for Rebuild-Op10 (10) is still 0 (= zero), whereas the value of RepeatNumber
for Rebuild-Op10 (15) will be equal to the value of RepeatNumber for the Work Order Operation to be repeated
increased by 1 (that is, 0 + 1 = 1).

How to Manage Buffer Replenishment and Transport Operations
How to Configure Handling Units
12 How to Manage Buffer Replenishment and Transport

Operations
Whenever the required Material Tracking Units (MTUs) involved in the production process are insufficient (and
therefore, must be replenished) or not in condition (and thus must be replaced) to permit the continuation of
manufacturing activities, users can manage their transportation within in the Plant by declaring a specific Logistic
Request for the Material Tracking Unit that is needed.
Within this context, the term "transportation" covers various activities, such as specifying the Source, Destination,
the MTU to be transported, loading of the Handling Units with MTUs, and successive unloading at the destination.
Target User
Users with Production Coordinator or Operator role can perform this action.
Workflow
1. Configure a Handling Unit.
Note This step can also be performed on-the-fly while executing the Transport Operation.
2. Declare a Logistic Request.
3. Accept the Logistic Request.
4. Execute the Transport Operation.
5. Unload the Handling Unit.
12.1 How to Configure Handling Units

Handling Units are created to facilitate the movement of Material Tracking Units (MTU) from a source Workcenter to
a destination.
Tracking the actual movement of the MTUs is performed directly on the Handling Units, thereby facilitating logistic
operations.
The Handling Unit's status indicates the stage reached by the Handling Unit in the progress of transporting its
content (for example, if the Handling Unit is ready to be dispatched, is in motion and so on). The History tab tracks
the chronology of all changes regarding the Handling Unit.
Prerequisites
Material Tracking Units are available.

To access the Handling Units page, click Shopfloor Execution > Handling Units in the sidebar.
Workflow
1. Create a Handling Unit.
2. Add Material Tracking Units to the Handling Unit.

Declaring Logistic Requests
3. Change the status of the Handling Unit.
Creating Handling Units

1. In the Handling Units page, click Create.
Identifier Unique identifier of the Handling Unit.
Workcenter The Workcenter in which the Handling Unit is located.

3. Click Create.
Adding MTUs to Handling Units

1. In the Handling Units page, select the Handling Unit for which you want to add MTUs, and then click to
open the details.
Note The Handling Unit must be in New or Partial state.
2. Click the Materials tab and click Link.
3. Select the material, set the Quantity, and click Save.
Changing the Status of Handling Units

1. In the Handling Units page, select the Handling Unit for which you want to change the status, and then click
to open the details.
2. Select the Change Status tab.
3. Select Dispatchable from the list.
4. Click Change Status.
12.2 Declaring Logistic Requests

You can declare a Logistic Request in two ways:

• Manually, which is the most common method adopted.
• Automatically:
• This may come in handy if you need a specific Material Tracking Unit to be transported to your workstation
regardless of the threshold level of the Buffer from which the required item is pulled, for example. In this case,
the Logistic Request is generated on demand.
• When the specific Material reaches the target quantity inside the Buffer when the material is consumed from the
Operator Landing page.

Declaring Logistic Requests
 To enable automatic Logistic Request generation, you must import the appropriate signal rule installed
with Opcenter Execution Discrete.
In this case, a Logistic Request will be automatically declared by the system whenever the Buffer level falls
below a defined threshold for MTUs.
For more information, see Integrating Opcenter Execution Foundation Apps in the Opcenter Execution
Discrete Solution in the Opcenter Execution Discrete Installation and Configuration Manual.
The following procedure is for those who want to declare Logistic Requests manually.
Procedure
1. Click Shopfloor Execution > Operator Landing in the sidebar.
2. Select More > Logistic Requests.
Identifier Identifier of the Logistic Request. It is automatically generated, but you can
change it according to your needs.
Material The Material you want to associate to the Logistic Request being declared.
Quantity (Available only after selecting a Material) The quantity of the selected
Material.
Note If the selected Material is compatible with the active machine, this
field is automatically populated with the threshold of the associated
Buffer.
Destination The Buffer to which the required Material is to be transported.

Note Only those Buffers that have been configured to contain the required
Material will be shown for selection, and if the Material is compatible with
the active machine, this field is automatically populated with one of the
associated Buffers, if available. The value selected must not be the same as
the value selected for parameter Source.
Source (Optional) Buffer from which the required Material is to be requested.

Note Only those Buffers that have been configured to contain the required
Material will be shown for selection. The value selected must not be the
same as the value selected for parameter Destination.
Due Date Date and time by which the required Material should reach the Destination.
Priority A number identifying the order in which the Transport Operations must be
generated.
4. Click Save.
Result

Accepting Logistic Requests
The Logistic Request is been created in status Open.
12.3 Accepting Logistic Requests

In order to set in motion the actual transport of the Material Tracking Unit(s) required, after a Logistic Request has
been declared, you must accept the Logistic Request. This in turn generates a new Transport Operation.
If properly configured, dedicated notifications inform users of new Logistic Request declarations. You can choose to
enable these notifications subscribing to the appropriate signals. Once subscribed, the related icon becomes
available on the Notification Bar and you will not receive any Logistic Request notification. To know more about
signal subscription, see the Configuring Roles page in the Opcenter Execution Foundation Development and
Configuration Guide.
Only after the Logistic Request has been accepted and a dedicated Transport Operation consequently generated
will it be possible to satisfy the user's request. The required Material Tracking Unit(s) will then be pulled from a
specific Buffer, placed into a specific Handling Unit and transported to the specified Workcenter.
Prerequisites
• You subscribed to the following signals: LogisticRequestCreated and LogisticRequestStatusChanged.
• The notification bar has been enabled.
• The status of the Logistic Request is Open.
• A Buffer configured with Materials/Tools is available.
Procedure
• In the home page, click the Logistic Requests tile.
• In the Notification Bar, click the Logistic Requests icon.

2. Select the Logistic Request you want to accept, and then click Accept.
The Logistic Request is accepted and the Accept Logistic Request page opens.
3. In the Accept Logistic Request page, set the following parameters:
Transport Operation Identifier Identifier of the Transport Operation.
Estimated Duration Estimated duration of the Logistic Request's execution.
Role Role of the user who can perform the action.
Source Buffer from which the Material is to be requested.
 Only Buffers for which a Workcenter or Machine

has been specified will be shown for selection.
Parameters Source and Destination should not
have the same values.

Executing Transport Operations
Destination Buffer to which the Material is to be transported.

4. Click Save. A Transport Operation is created in status Accept.
 To reject Logistic Requests, select the Logistic Request you want to reject, and click Reject.
Note You can only reject Logistic Requests that are in status Open.
12.4 Executing Transport Operations

Transport Operations facilitate shipping Material Tracking Units from one location to another. When the execution
of the Transport Operation is completed, the Material Tracking Units can be unloaded from the Handling Unit and
consumed.
Prerequisites
A Logistic Request has been accepted, resulting in the creation of a Transport Operation in status Open.
Procedure
1. Click Shopfloor Execution > Transport Operations Landing in the sidebar.
2. Select the Transport Operation for which you want to execute transportation, and then click Release.
(Optional) To take the responsibility of the entire Transport Operation, click Take Ownership.
3. Click Start to start the Transport Operation.
4. Click Show Details.
Set the following parameters:
Source Source Buffer from which the Material is to be requested.
Handling Unit Handling Unit to be used to transport the Material.
 Only Handling Units that are in either Dispatchable or

Commissioned status are available. If no Handling Units
are available, you can configure a new Handling Unit on-
the-fly and then click Ready to Dispatch. The status of the
Handling Unit changes to Dispatchable.
Destination Destination Buffer to which the Material is to be transported. Note

Once a Destination Buffer is added, you cannot change the Source
or Handling Unit.
5. Click Complete when the Handling Unit reaches the destination. The Handling Units is ready to be unloaded.

How to Unload Handling Units
12.5 How to Unload Handling Units

Handling Units can be directly unloaded once the Transport Operation has been executed or you can decide to
unload them at a later time.
Prerequisite
• A Transport Operation has been executed.
• The status of the Handling Unit to be unloaded is Transported.
• Unloading Handling Units from the Transport Operator Landing Page
• Unloading Handling Units from the Handling Units Page
Unloading Handling Units from the Transport Operator Landing Page

1. In the Unload Handling Unit panel, select the Material Tracking Units to be unloaded.
2. Click Save.
Unloading Handling Units from the Handling Units Page

1. Click Shopfloor Execution > Handling Units.
2. In the Handling Units page, select the Handling Unit to be unloaded and click .
3. Click Unload Handling Unit.
4. In the Unload Handling Unit panel, select the Material Tracking Units to be unloaded.
5. Click Save.

How to Manage Non-Productive Activities
Managing Non-Productive Activities from the Users page
13 How to Manage Non-Productive Activities

Non-Productive Activities (for example, workspace cleaning, tool maintenance, training) can be managed in
different ways:
• Production Coordinators and Product Engineers can manage Non-Productive Activities of all Users from the
Users page.
• Every User can start and/or complete his or her own Activities from the Operator Landing Page.
• Every User can start and complete his or her own Activities from the Notification Bar.
When managing Non-Productive Activities from the Users page:
• Only one Activity can be managed at a time.
• It is possible to start and/or complete Activities belonging to different Users.
• It is possible to specify start and end dates.
• Activities can be deleted from the log.
When managing Non-Productive Activities either from the Operator Landing page or from the Notification Bar:
• Multiple Activities can be started or completed at the same time.
• It is possible to start and/or complete Activities belonging only to the currently-logged User.
• Start and/or end dates of the Activities are automatically set to the current time.
• Activities cannot be deleted from the log.
• Managing Non-Productive Activities from the Users page
• Managing Non-Productive Activities from the Operator Landing Page
• Managing Non-Productive Activities from the Notification Bar
13.1 Managing Non-Productive Activities from the Users page

This procedure allows you to manage Non-Productive Activities belonging to all Users.
Specifically, it is possible to create and complete Activities, to display and edit their details and to delete them from
the log, provided that you own the required role.
Conversely, the currently logged User can start and/or complete Activities accessing the functionality from the
Notification Bar.
Target Users
Users with the Product Engineer or the Production Coordinator roles can perform this procedure.
Starting a Non-Productive Activity

1. In the home page, click the Users tile.
2. Select a User and click Open.
3. In the Non-Productive Activities tab, click Add.

Managing Non-Productive Activities from the Operator Landing Page

Identifier Identifier of the Non-Productive Activity previously created.
Start Date (Mandatory) Start date and time of the Non-Productive Activity.
End Date (Optional) End date and time of the Non-Productive Activity.
 If you leave this field blank, the counter of the Non-Productive

Activities in the notification bar will be incremented by one.
If you fill this field with a future date or time, the counter will
not be incremented.
Context (Optional) Select one of the following:

• Work Order
• Equipment
• Material Tracking Unit
5. (If you have selected a context) Insert the context items according to the Context parameter set in the previous
step.
6. Click Create.
Completing a Non-Productive Activity

1. In the Home page, click the Users tile.
3. In the Non-Productive Activities tab, select an Activity.
4. (Optional) To complete the Activity specifying a different date and time, click Edit, insert the desired date
and time in the End Date field and click Save.
5. Click Confirm.
Deleting Non-Productive Activities

1. In the Home page, click the Users tile.
3. In the Non-Productive Activities tab, select one or more Activities and click Delete.
13.2 Managing Non-Productive Activities from the Operator Landing

Page
This procedure allows a User to start and/or complete his or her own Non-Productive Activities.

Managing Non-Productive Activities from the Notification Bar
Conversely, the Production Coordinator and the Product Engineer can manage Activities belonging to all Users.
Starting Non-Productive Activities

1. In the Operator Landing page, click N-P Activities on the button bar. The Non-Productive Activities page
displays the Activities started by the current User .
2. Click Create and Start.
3. In the Create Non-Productive Activity On The Fly page, select one or more Activities from the list previously
created.
4. (Optional) In the Context drop down list, select the context of the Activity.
step.
6. Click Create.
Completing Non-Productive Activities

1. In the Operator Landing page, click N-P Activities on the button bar. The Non-Productive Activities page
displays the Activities started by the current User .
2. Select one or more Activities and click . The selected Activities are logged as completed with the current date
and time.
13.3 Managing Non-Productive Activities from the Notification Bar

This procedure allows a User to start and/or complete his or her own Non-Productive Activities.
Conversely, the Production Coordinator and the Product Engineer can manage Activities belonging to all Users.
Prerequisite
The Notification Bar has been enabled.
Starting Non-Productive Activities

1. Click the Non-Productive Activity icon in the Notification Bar: this opens the Non-Productive Activities
panel.
2. Click Create and Start.
3. In the Create Non-Productive Activity panel, select one or more Activities from the list previously created.
4. (Optional) In the Context drop-down list, select the context of the Activity.
step.
6. Click Create.
Completing Non-Productive Activities

1. Click the Non-Productive Activity icon in the Notification Bar.
2. The Non-Productive Activities page displays the Activities started by the current User .
3. Select one or more Activities and click Complete. The selected Activities are logged as completed with the
current date and time.

How to Handle Notifications
Managing Non-Productive Activities from the Notification Bar
14 How to Handle Notifications

Notifications are available as alerts on the notification bar of the Opcenter Execution Discrete web console when
specific events occur.
It is possible to choose which users can see specific sections of the notification bar on top of the pages, by simply
assigning the appropriate signal to the corresponding Role from the Roles page of Opcenter Execution Foundation
Solution Studio. For detailed information on how to perform this operation, see the Configuring Roles page in
the Opcenter Execution Foundation Development and Configuration Guide.
Target User
Prerequisites
You must subscribe to the following signals to enable notifications:
• SnagAndNoteNotificationSgn, for enabling notifications related to Notes.
• WorkOrderNotificationSgn, for enabling notifications related to Work Orders.
• ProcessNotificationSgn, for enabling notifications related to Processes.
• NonConformanceNotificationSgn, for enabling notifications related to Quality Non-Conformances and Change
Requests.
• NonProductiveActivityNotificationSgn, for enabling notifications related to Non-Productive Activities.
• LogisticRequestCreated and LogisticRequestStatusChanged, for enabling notifications related to Logistic
Requests.
Notification Bar
The following table describes the icons available on the notification bar (located in the upper right corner of the
web console), when the user is subscribed to all signals. The badge (counter) displayed above each icon on the
notification bar indicates the number of currently-open notifications. Here is an example of how the notification bar
appears when there are currently-open notifications for all available icons.
When a new notification is received, the value displayed in the badge is updated. Whenever a notification is opened,
the badge's value increases.
 The numbers indicated in the badges shown in the figure below, as well as in the Legend, are merely
examples and are in no way binding.
Notification Bar Legend
Notification Icon Related entity Reasons for notification Available Operations
Note Notes have been added to the Handling Note Notifications


Handling Note Notifications
Notification Icon Related entity Reasons for notification Available Operations
Work Order • The Work Order has been Handling Work Order
released. Notifications
• The Work Order has been
set as ready to be
scheduled.
Process A Process has been completed. Handling Process

Notifications
Change Non- A Change Non- Handling Change Non-

Conformance (Change Conformance has been Conformances
Request) declared.
Buy-Off A Work Order Operation with Handling Buy-Off

MTUs that must be Notifications
acknowledged by a Buy-Off
signature has been started.
Quality Non- A Quality Non-Conformance Handling Quality Non-

Conformance has been declared. Conformances
Non-Productive Activity A Non-Productive Activity has Managing Non-Productive

been declared. Activities from the
Notification Bar
Logistic Requests Declaring Logistic Requests. Accepting Logistic

Requests.
14.1 Handling Note Notifications

At runtime, when the Operator or the Production Coordinator write notes relative to the execution of a Work Order
Operation which could be useful to other Operators, if the system is properly configured, a notification is triggered.
Target User
Users with the Operator as well as the Production Coordinator role can perform this operation.
Prerequisites
• You have subscribed to the SnagAndNoteNotificationSgn signal.
Procedure
1. From one of the following environments, select a Work Order Operation and then click the Notes
notification icon in the notification bar:
• Operator Landing page.

Handling Work Order Notifications
• Production Coordinator Dashboard.

• Work Orders page.
2. In the Notes panel, in which all notes related to the selected Work Order Operation are listed, select the note
that you want to read and then click Acknowledge to acknowledge it: a indicator will be displayed
inside the tile corresponding to the selected note.
 If the note you are acknowledging was set as valid for the entire Work Order, acknowledging it for a
specific Work Order Operation means that it will be automatically acknowledged for all of the other
Work Order Operations making up the current Work Order.
Also, any notes that are acknowledged will remain visible inside the Notes tab of the As Built page
corresponding to the selected Work Order.
3. If necessary, click Add and type a new note in the New Note box: click Save to confirm.
14.2 Handling Work Order Notifications

Work Order notifications inform users of specific events related to Work Orders. You can choose to subscribe to
Work Order notifications by subscribing to the appropriate signal from the Roles page of Opcenter Execution
Foundation Solution Studio. Once subscribed, the Work Order notification icon becomes available on the
notification bar, and notifications are sent to the users who are assigned the Role that was used for subscription. If
you choose to not subscribe to notifications, the corresponding Work Order notification icon will not be available
on the notification bar, and Work Order notifications will not be sent. To know more about signal subscription, see
How to Handle Notifications and the Configuring Roles page in the Opcenter Execution Foundation Development and
Configuration Guide.
Prerequisites
• You subscribed to the WorkOrderNotificationSgn signal.
• Either of the following:
• A Work Order has been released (status changes to New)
• A Work Order has been set as ready to be scheduled (status changes to ReadyForScheduling)
Procedure
• Click the Work Order Notification tile in the home page.
• In the Notifications Bar, click the Work Order notification icon.
2. Select a notification of your interest and then click to close the notification.
 If the status of the Work Order changes, then the notification that was triggered in relation to the original
status is closed. For example, if a notification was triggered when the status of a Work Order becomes
ReadyForScheduling, and the status changes to Active, the corresponding notification is closed.
Similarly, after you open a notification, the system closes it.

Handling Process Notifications
14.3 Handling Process Notifications

Process notifications inform users that a new revision of a Process has been created. You can configure the users
who must receive Process notifications by associating them with the role subscribed to the appropriate signal from
the Roles page of Opcenter Execution Foundation Solution Studio. After subscribing, the Process notification icon
becomes available on the notification bar. If you choose to not subscribe to notifications, the corresponding Work
Order notification icon will not be available on the notification bar, and Work Order notifications will not be sent. To
know more about signal subscription, see How to Handle Notifications and the Configuring Roles page in
the Opcenter Execution Foundation Development and Configuration Guide.
Prerequisite
• You subscribed to the ProcessNotificationSgn signal.
• The notification bar has been enabled
• A new revision of a Process has been created.
Procedure
• Click the Process Notification tile in the home page.
• In the Notifications Bar, click the Process notification icon.
2. In the Process Notifications page, select the notification of interest, and then click to close the
notification.
 After you open and act upon a notification, the system closes it.
14.4 Handling Change Non-Conformances

When the Operator finds that something needs to be changed in the production process and declares a Change
Non-Conformance (Change Request), the Production Coordinator is prompted to manage it through a notification.
 If you are handling a Change Non-Conformance, and you are going to managing it by adding an Operation,
if Interlocking Checks have been associated to the Operation to be added, these Interlocking Checks will
not be inherited.
Prerequisite
• You subscribed to the NonConformanceNotificationSgn signal.
• The notification bar has been enabled
• A Change Non-Conformance has been declared
Procedure
1. After receiving a notification, click the Change Requests tile in the home page to display all notifications
relative to Change Non-Conformances.

Handling Change Non-Conformances
2. Browse the Non-Conformance that you want to handle inserting the relative ID in the search box and
pressing Enter.
3. Select the Non-Conformance and then click Open, to read the Non-Conformance details.
4. Click either of the following:
• Reject, to reject the request and exit.
• Confirm, to accept the change request.
5. (Only if you have clicked Confirm) Set the required parameters according to change type:
Change Type Parameters
Add Tool • Tool Definition Name, the name of the Tool to be

used to perform the Work Order Operation.
• Usage Number, how many times the Tool must be
used to perform the current Work
Order Operation.
• Notes, additional notes.
• Ref Number, an identifier to be used to track the
change.
Add Operation • Operation Name, the name of the new Work

Order Operation.
• Description, a user-friendly description of the new
 If the Add Operation involves a Work Order
for which BoM usage has been enabled, only Work Order Operation.
those operations that do not contain • Insert after Work Order Operation, the name
Materials to be consumed can be added. and sequence number of the Work Order
Operation after which the new Work Order
Operation must be placed.
• Dependency type, either of the following:
• After End: The new Work Order Operation
can start only after the previous Work
Order Operation is completed.
• After Start: The new Work Order
Operation can start only after the
previous Work Order Operation has
started.
• Machine, the Machine to be used to execute the
change.
Repeat Operation • Operation, the Work Order Operation after which

the Work Order Operation(s) must be re-executed.
change.
• The Work Order Operation(s) to be re-executed:
select them from the table listing all completed

Add Part • Operation, the name and sequence number of the

Work Order Operation that must consume the
Material.
• Material, the Material to be consumed.
• Material Specification Type, one of the following:
• Alternative, only one Material must be
consumed among the proposed Materials.
• AsRequired, the quantity to be consumed
for each Material can range from zero to
the total quantity of each Material (the
consumption is optional).
• Disassemble, if the Material is
disassembled, the disassembly action is
applied to all Materials set as Normal
Part with same ID relative to the
completed Work Order Operations
belonging to the same Work Order.
• NormalPart, the entire quantity of the
• RangeParts, the partial quantity of a
Material can range from greater than zero
to the total quantity of the Material itself.
• Reference, the Material is not directly
consumed or assembled, but is used as a
reference for other activities performed in
• SelectedFit, the total part quantity for the
selected range must be equal to the
maximum quantity of one of the parts.
• CoProduct, if you intentionally want more
than one distinct product to be produced
from the Material during the execution of
the Operation.
• ByProduct, if in addition to a distinct
product to be produced from the Material,
during the execution of the Operation,
there will inevitably be also a resulting by-
product (derivative) that may or may not
be further processed to produce something
else.
• Additive (not available in the drop-down
list and automatically selected only if the
selected Material is of type AMPowder):
similar to Normal Part, but used
specifically for Additive Manufacturing
powders. The entire quantity of the
Material must be consumed: however,
once assembled, it can no longer be
disassembled.


• AutoConsume: Material for which it is
necessary to trace the consumption
regardless of the involved Batch or Serial
Number.
• Quantity, the quantity of Material to be
consumed.
change.
• Logical Position, any kind of reference about
where the component must be placed or
Remove Part • Operation, the name and sequence number of the

Work Order Operation that consumes the Material.
• Material To Be Consumed, the Material to be
removed.
change.
Replace Part • Operation, the name and sequence number of the

• Material To Be Consumed, the Material to be
replaced.
• Material, the Material that must replace the
current one.
change.
Change Part Quantity • Operation, the name and sequence number of the
• Material To Be Consumed, the Material the
quantity of which must be modified.
• Quantity, the new quantity of the Material.
change.
Add Work Instruction • Operation, the name and sequence number of the
• Work Instruction Definitions, the Work
Instruction Definition to be associated.
change.

Add Work Instruction to SN • Operation, the name and sequence number of the
• Work Instruction Definitions, the Work
Instruction Definition to be associated.
change.
• Work Instruction SN, the list of Serial Numbers to
be associated with the Work Instruction.
Change Routing • Work Order Operation From, the name of the

Work Order Operation that influences the
execution of the other Work Order Operation.
• Work Order Operation To, the name of the Work
Order Operation the execution of which is
influenced by the execution of the previously-
selected Work Order Operation.
• Dependency type, either of the following:
• After End: The Work Order Operation
selected from the To Operation drop-
down list box can start only after the first
Work Order Operation is completed.
• After Start: The Work Order Operation
selected from the To Operation drop-
down list box can start only after the first
change.
Delete Dependency • Dependency to be removed, the dependency to

be removed.
 To populate this field, select the arrow in

the dependency graph. Keep in mind that
deleting Dependencies is not allowed for
Serialized Work Orders.

change.

Handling Buy-Off Notifications
Add Process Operation • Operation Name, the name of the new Process
Operation. This Process Operation is a copy of an
existing Process Operation that you select.
 If the Add Process Operation involves a Work
Order for which BoM usage has been • Insert After Work Order Operation, the Work
enabled, only those operations that do not Order Operation after which you want the newly-
contain Materials to be consumed can be created Work Order Operation to be positioned.
added. • Sequence, the sequence number at which the new
Process Operation should be executed. Use the
drop-down arrow to set a value.
• Dependency Type, either of the following:
• After End: The new Work Order Operation
can start only after the Work Order
Operation selected in the Insert After
Work Order Operation is completed.
• After Start: The new Work Order Operation
can start only after the Work Order
Operation selected in the Insert After
• Process, the Process to which the Process
Operation that you want to add, is associated.
• Operation, the Process Operation that you want
to add. The newly-added Process Operation is
represented by Operation Name that you set.
addition of the new Work Order Operation.
Remove Operations • Operation, the name and sequence number of the

Work Order Operation to be removed.
change.
 When a Work Order Operation is removed,

Dependencies from and to it are
automatically removed.
If there are Work Order Operation before and
after the one that is being removed, a
Dependency of type After End is
automatically inserted between them.
14.5 Handling Buy-Off Notifications


Handling Quality Non-Conformances
A Buy-Off notification is issued whenever a Work Order Operation is started from the Operator Landing page and a
Quality Inspection task, configured specifically to manage Buy-Off approvals, is linked to either a Work Order
Operation or a Work Order Step.
Buy-Off notifications are aimed at informing entitled users, such as Production Coordinators, that in order to
complete a Work Order Operation, an inspection is required on any MTU to be produced by the Work Order. If the
MTUs are rejected, the Work Order Operation cannot be completed.
If you are an entitled user, and you are not managing the Quality Inspection from the Operator Landing page, you
can handle Buy-Off notifications from the Buy-Off Management page.
From the Buy-Off Management page, you can also see the details of the Buy-Off request (for example the list of
users that signed the Buy-Off) and navigate also the As Built Order and Genealogy pages.
Prerequisite
• A Quality Inspection for Buy-Off purposes has been configured and linked to the started Work Order Operation.
• If you want to also browse Failures in case of rejection of the inspected MTUs, the Non-Conformance on Defect
or Failure configuration key is set to Failure.
Procedure
1. After receiving a notification, click the notification icon in the notification bar.
2. In the Buy-Off Management page, select the Buy-Off request to be managed and click .
3. In the Accept or Reject Buy-Off panel, do either of the following:
• click Accept, to confirm that the produced MTU is as expected.
• click Reject if you found issues on the produced MTU. Click , to link Failures as the reason for
rejection.
4. Click Sign.
5. In the Signature Required panel, provide the required signature and click Sign again.
6. Click Close.
Result
If Complete Work Order Operation by Different User configuration key is enabled, the active Machine has the
EnabledForCompleteByDifferentUser property set to True and the Work Order Operation/Step is ready to be
completed, when a Material Tracking Unit is accepted, the Work Order Operation is automatically completed for
that specific Serial Number.
 Automatic completion is possible only if the Production Type is Serialized, FlexibleSerialized or

FullQuantity.
If you want to disable automatic completion, you can remove the subscription of the
OnSentenceBuyOffCompleteOperationForStep handler to the OnSentenceBuyOff event from Solution Studio.
14.6 Handling Quality Non-Conformances

Quality Non-Conformances previously declared either by an Operator or a Production Coordinator, must then be
managed and solved. It is possible to automatically create Non-Conformances on Work Order
Operations, Machines, and Material Tracking Units.
By setting an appropriate configuration key, whenever a Non-Conformance is set to Scrap, thereby causing the
production entity with which it is associated to be scrapped, all the other Non-Conformances associated with it will
be automatically closed.

Prerequisites
• You subscribed to the NonConformanceNotificationSgn signal.
• A Quality Non-Conformance has been declared in one of the following manners:
• by an Operator;
• by a Production Coordinator;
• automatically by an Equipment or Workcenter.
Procedure
1. After receiving a notification, click the Non-Conformance Notifications tile in the home page to display all
Quality Non-Conformances.
2. (optional) Browse the Non-Conformance that you want to handle inserting the relative ID in the search box and
pressing Enter.
 If the Non-Conformance was declared automatically by an Equipment or Workcenter, the icon is

shown in the lower left corner of the relative tile.
3. Select the Non-Conformance and click Open.

4. In the Details tab, click Change Status.
5. In the Change Status Non-Conformance Name page, change the status of the Non-Conformance according to
the Lifecycle currently in use.
6. If during its creation the Non-Conformance had been associated to Serial Numbers, select them in the lower
part of the panel. It is possible to select both Serial Numbers and Containers: selecting a Container means
selecting at the same time all its contained elements.
 • Partial sentencing (that is, selecting only some of the associated Serial Numbers) is allowed
only if the status selected in the previous step is final.
• If the sentencing involves one or more Containers, they are unloaded after the sentencing itself.
7. Click Save.
 The Lifecycles for Quality Non-Conformances can be customized and it is possible to define different
Lifecycles for each associated entity type (Work Order Operations, Machines, Material Tracking Units and
Tools). Therefore, the available states and the results of their change depend on the Lifecycles currently in
use. You can also associate particular behaviors with the Lifecycle states according to your needs.
The following paragraphs describe the default Lifecycles that are provided by Opcenter Execution Discrete
for Work Order Operations and for the other entity types.
Default Lifecycle for Non-Conformances associated to Work Order Operations

Change Status from... To resolve the Non-Conformance...
OPEN to SCRAP by defining the involved Work Order Operation as scrapped.
OPEN to CHANGE by changing the involved Work Order Operation.

OPEN to REWORK by reworking the involved Work Order Operation.

Select the Rework Code to be associated with the Non-
Conformance and click Save.
OPEN to CONCESSION by defining that the Work Order Operation requires the approval
from the Product Engineer in order to execute the Work Order
differently from the Process created by the Product Engineer.
OPEN to CLOSE AND RETURN TO WORK by closing the Non-Conformance and indicating that work must be
resumed (for example, because the Non-Conformance was
declared by mistake).
OPEN to SET WKC HOLD by selecting a Workcenter in the Equipment field and setting it to
Hold. While in Hold, no other Work Order Operation inside the
selected Workcenter can be performed. This operation, even if a
Non-Conformance had not been declared, can also be performed
from a dedicated page.
OPEN to NOTIFYING-ENGINEERING- by indicating that the Non-Conformance is related to an

ISSUE engineering issue, which needs to be notified to T4EA (to be used in
case of T4EA integration).
Default Lifecycle for Non-Conformances associated to Machines or Tools

OPEN to SCRAP by defining the involved Entity as scrapped.
OPEN to CLOSE AND RETURN TO WORK by closing the Non-Conformance and indicating that work can
be resumed.
OPEN to REPAIR by defining the involved Entity as in need of repairs.
REPAIR to SCRAP by sentencing that the involved Entity cannot be repaired and
must be scrapped.
REPAIR to CLOSE AND RETURN TO WORK by sentencing that the involved Entity has been repaired and
work can be resumed.
Default Lifecycle for Non-Conformances associated to Material Tracking Units

OPEN to SCRAP by defining the involved Entity as scrapped.
OPEN to REWORK by reworking the involved Material Tracking Unit.

OPEN to CLOSE AND RETURN TO WORK by closing the Non-Conformance and indicating that work can
be resumed.
OPEN to REPAIR by defining the involved Entity as in need of repairs.
REPAIR to SCRAP by sentencing that the involved Entity cannot be repaired and
must be scrapped.
REPAIR to CLOSE AND RETURN TO WORK by sentencing that the involved Entity has been repaired and
work can be resumed.
Results
• If the Non-Conformance was associated to a Work Order Operation, the last Work Order Operation in the
Dependency graph (which was automatically placed in Future Hold status when the Non-Conformance was
declared) re-assumes the status it had before the declaration (either Open or Partial).
• If the Non-Conformance was declared on a Work Order Operation belonging to a Work Order that produces
more than one Material Tracking Unit, the Serial Numbers affected by the Non-Conformance are removed from
the Work Order if scrapped and included in the sentencing. The quantity of the Work Order is recalculated.
• If the final status of the Non-Conformance is REWORK, the system's behavior is as follows:
• The system creates additional Work Orders in New status, one for each Work Order in Rework status.
These Work Orders just created in New status will have the same name as their parent Work Orders in
Active status, but with prefix RWK- In case of multiple Work Orders, a suffix .number is added to each
Work Order after the first one. For example, if there are two sentenced Non-Conformances, two Work
Orders will be created, one without suffix and one with suffix .1.
• These Work Orders with prefix RWK- will contain the Processes of the Rework Code and can be executed
from the Operator Landing page.
• To manage the Rework phase, it is necessary to execute the RWK-Work Orders before executing the
related Rework Work Order.
• The original Work Order can be processed for the remaining Work Order Operations and the last one is
placed in Future Hold status. Once the Rework Work Order containing the affected Serial Numbers is
completed, the original Work Order Operation can be completed. The Operator Landing page indicates
that the Work Order Operation cannot be completed because there are one or more Serial Numbers that
are being reworked.
• Reworking a Serialized or FullSerialized Work Order creates a Rework Work Order of type Serialized in
which only the defective Material Tracking Units are indicated as Produced Material Tracking Units.
• The Non-Conformance counter decreases in the notification bar .

How to Monitor and Tweak Production Execution
Viewing Work Order Progress
15 How to Monitor and Tweak Production Execution

You can use Opcenter Execution Discrete to monitor how production is progressing in your production plant: on the
basis of this information, if necessary, you can also make changes to streamline execution.
In Opcenter Execution Discrete, monitoring and tweaking operations may be specific to:
• Work Orders
• Work Order Operations
• Powder Material Batches
• Non-Conformances
or generic.
Some of the possibilities offered include viewing additional details of Work Orders, displaying the history of a Non-
Conformance, rescheduling Work Order Operations, and more. Take a look below to see which operations are
available, according to the entity of interest.
Available Operations specific to Work Orders

• Viewing Work Order Progress
• Viewing Work Order Genealogy
• Displaying Historical Data
• Tracking Additional Actions
• Monitoring and Managing Output Messages at Runtime (This functionality is not available in
Available Operations specific to Work Order Operations

• Monitoring Work Order Operations in Execution on a Workcenter or Machine
• Associating Additional Users to Work Order Operations (This functionality is not available in
• Updating the Labor Time
Available Operations specific to Material Tracking Units

• Viewing and Amending the Results of a Material Tracking Unit (This functionality is not available in
Available Operations specific to Powder Material Batches

• Displaying Powder Genealogy
Available Operations specific to Non-Conformances

• Tracking Non-Conformance Histories
15.1 Viewing Work Order Progress

Opcenter Execution Discrete provides you with a page dedicated to monitoring how the execution of the
current Work Order is progressing.
The actual execution progress helps schedule future activities.
Prerequisite

Viewing Work Order Genealogy
The status of the Work Order is not Edit, ReadyForScheduling, New, Scrapped or Aborted.
Target User
Users with any role can perform this operation.
Procedure
1. Click Shopfloor Execution > Work Orders in Progress in the sidebar. The system displays the list of
running Work Orders, showing the relative:
• percentage of completion (PoC);
For FullQuantity Work Orders, the PoC corresponds to the ratio between the number of completed Work
Order Operations and total Work Order Operations, excluding those in status Not Executed, weighted by
the duration (only if the duration is provided for all Work Order Operations).
For TransferBatch Work Orders, the PoC corresponds to the ratio between the minimum count of
completed items on all compulsory Work Order Operations and the Work Order quantity, which is
reduced in case of scrapped items. Compulsory Work Order Operations are all those Work Order
Operations which are not optional and include Work Order Operations that fall outside routing.
For Serialized Work Orders, the PoC corresponds to the ratio between the number of serial numbers that
have completed all compulsory Work Order Operations and the Work Order quantity, which is reduced in
case of scrapped items.
• execution plant.
• the final material being produced.
2. Select the Work Order for which you want to view the progress, the system lists the related Work Order
Operations displaying the following information:
• status,
• produced quantity,
• scrapped quantity.
15.2 Viewing Work Order Genealogy

By viewing the Genealogy of a Work Order, it is possible to see all the changes or activities that have been
performed on each element making up the product resulting from the Work Order's execution throughout its entire
manufacturing process.
The Genealogy page comes provided with a search bar in which you can set a filter to find the traceability details
for a specific Work Order or Serial Number/Batch ID: if desired, you can further filter this information to satisfy
your needs. For example, you can filter the Work Orders according to the produced Final Material or the related ERP
Order.
A tree view has been adopted to display this information so that only the details related to the selected node are
shown in a panel opened on the right. To interpret the meaning of the various icons used in the tree view, see the
dedicated legend provided below.
Which information and how it is presented on the Genealogy page depend greatly on a variety of factors, such as
the Production Type of the Work Order that is being examined. For example:
• For Serialized Work Orders, the information is presented for each Serial Number.
• For Additive Manufacturing Work Order Operations, you can view information such as Machine,
Powder Material batch details, Substrate details, Print Job File ID along with Execution Group and Execution
Phase details.
 Powder Material batch history is also available on the Powder Genealogy page.

• For Flexible Work Orders, all activities that have been completed prior to an abrupt closure are tracked. In the
case of Work Orders created after stopping a Flexible Work Order, the related details are tracked as follows:
• All activities currently in progress or not yet started at the moment of the abrupt closure are tracked for
the new Work Order.
• The two Work Orders are displayed with the same parent node.
• If an action was performed during the execution of a Work Order Operation by a User belonging to a Team,
details of the Team are also displayed.
• If the Work Order Operation being examined belongs to an Execution Group, details of the Execution Group and
the Execution Group Phase are displayed.
• If the Work Order Operation is linked to Work Instructions at the Execution Group Phase level, details of the
Execution Group and the Execution Group Phase are also displayed.
• If Result management has been enabled, any negative Results that have been declared or any Repeat
executions are indicated on the relative elements of the tree view provided.
In those cases in which there is integration with Opcenter Connect MOM, activities are tracked as if they were
performed by no user (that is, with User = ""), meaning that they were executed automatically by a piece of
Equipment.
Other actions feasible from the Genealogy page

In addition to viewing the information illustrated above, you can also perform the following actions from the
Genealogy page:
• Replicate the genealogy of a Work Order on another machine by exporting and then importing this information
as a .json file.
• Display the details of a previously-imported Genealogy.
For more information, see sections Importing a Work Order Genealogy and Displaying the Details of a Previously-
Imported Genealogy below.
From the Genealogy page, it is also possible to disassemble a consumed MTU from a Work Order: for the detailed
procedure, see the dedicated section in Disassembling Material Tracking Units.
 Although disassemblies can be performed from the Genealogy page, regardless of whether they be total
or partial disassemblies, they will not be shown in the page: only the action (trigger) performed on the
Material to be consumed belonging to Material Specification Type Disassemble will be displayed.
Target User
 Users with the Operator role can view the Genealogy of the Work Order of a selected Work Order Operation
by clicking Genealogy on the button bar provided in the Operator Landing Page. When the button is
clicked, the system redirects the user to the Genealogy page and the Work Order of the selected Work
Order Operation is displayed in an expanded tree structure.
This option is disabled when the Work Order Operation belongs to an Execution Group or when
multiple Work Order Operations are selected.
Procedure

• Operating on the search bar, enter the Identifier of a Work Order or a Serial Number/Batch ID in the
corresponding filter and press Enter.
• Click and, from the Select Item dialog, select the required item from the grid. If necessary, you can
further refine your search.
3. Expand the displayed item to view its details in a tree view.
 If you type a Parent Batch ID or a Serial Number ID in the search bar, the corresponding item is
highlighted in the tree view.
4. (Optional) If the Work Order contains more than fifty Serial Numbers, click to display additional Serial
Numbers on screen.
Legend for Available Icons Displayed in the Tree View of the Genealogy Page
Icon Meaning
Work Order
Work Order (Details)
Material
Work Order Operation
Work Order Step
Activity
Work Instruction
Machine
Document (It can be directly downloaded clicking on )
NOK Result
Repeat
Importing a Work Order Genealogy

Displaying Historical Data
 The exported .json file generated during the following procedure remains available on your filesystem for
consultation at any time. The same is true for any other Genealogy .json files resulting from previous
Exports.

2. Follow the procedure to view the genealogy of the Work Order of interest.
3. Click Export. The genealogy of the Work Order of interest is saved as a .json file directly to your filesystem.
4. Go to the machine where you want to import the exported .json file. Go to the home page and then click the
Genealogy tile.
5. Click Import.
6. In the Import Genealogy Documents page, click Import.
7. Using File Explorer, browse to the Genealogy .json file related to the Work Order of interest, and then click Open.
Displaying the Details of a Previously-Imported Genealogy

2. Click Import.
3. In the Import Genealogy Documents page, select the Genealogy .json files of interest from the displayed list
and then click Open.
15.3 Displaying Historical Data

During production execution, you can retrieve and display historical data automatically traced for Work Orders that
are already in progress. Various dedicated tabs have been provided to present such data for consultation.
Prerequisite
The Work Order is not in Edit, ReadyForScheduling or New status.
Target User
Procedure
2. Select the Work Order of interest and click As Built Order.
3. Click the appropriate tab to view the details of interest:
Tab Contents
Details Essential information regarding the Work Order (such as

Name, Description, Identifier and Production Type).
Dependencies Dependencies between the Work Order Operations that

belong to the selected Work Order.

Tab Contents
Operations Work Order Operations belonging to the Work Order.
 Selecting one or more items in this tab will affect

what is displayed in the other tabs, filtering the
items they contain accordingly.
If one or more Interlocking Checks have been associated

to the Work Order Operation, the icon is displayed.
Click this icon to view data traced about the execution of
the Interlocking Check(s).
If the Result Management configuration key has been
enabled and at least one Serial Number has been declared
as having a negative Result, the indicator will be
displayed in the lower-left corner of its corresponding
Work Order Operation tile.
If there is already a Serial Number selected in the Serial
Numbers tab (see below in this table), this indicator will
be visible only on those Work Order Operations in which
the Serial Number has a negative Result.
Steps Information about any Work Order Steps belonging to the

Work Order Operations making up the selected Work
Order.
 Selecting one or more items in this tab will affect

what is displayed in the other tabs, filtering the
items they contain accordingly.
Activity History Details regarding the activities performed by Users in

relation to the Work Order or Serial Number.
For activities performed by Teams, the Team column
displays the team name. Click the icon near the team
name to display details of team members who were part
of the team when the Work Order Operation was started,
paused or completed.
For activities performed by Machines or Workcenters in
the case of integration with Opcenter Connect MOM,
the User is identified with an empty space and a value is
provided also for the involved Equipment.
enabled, the Result Value and Is NOk columns will be
visible only for End activities.

Tab Contents
Print Job File Details regarding the Print Job File associated to the
selected Work Order (for example, Machine, User and
(enabled only if a Work Order Operation
Action).
related to the Work Order is of type Additive
Manufacturing)
Material Details regarding Material Tracking Units consumed or

produced by the Work Order.
 • If a Work Order Operation related to the Work

Order is associated to Materials of
class AMPowder, this tab displays
information about the Powder Material
batches consumed during the execution of
the associated Work Order Operation (for
example, Quantity, Recycle count and
Status).
• If the Material is consumed from an
Execution Group, the Execution Group NId
and the Execution Group Phase NId details
are displayed.
Additional information is provided if Material parameters,

such as Quantity or Serial Number/Batch ID are acquired
from the field. The additional information can be related
to:
• the value acquired from the field
• the timestamp of the acquisition from the field.
• the timestamp of the Acquisition from the Operator at
runtime.
• the quality of the variable.
Tools Details regarding Tools associated to the Work Order or

Serial Number.
 If a Work Order Operation included in the Work

Order is of type Additive Manufacturing and
Substrates have been associated to it, this tab
displays details regarding the associated
Substrates (for example, Name, Status, and Tool
Definition).

Tab Contents
Work Instructions Details regarding Work Instructions and Forms of

associated Data Collections, such as the ID of the Data
Collection Task, the parameter value, the update time of
the value.
Additional information is provided if data collection
values are acquired from the field. The additional
information can be related to:
• the value acquired from the field.
• the timestamp of the acquisition from the field.
• the timestamp of the Acquisition from the Operator at
runtime.
• the quality of the variable.
If you selected a Work Order
Operation in the Operations tab, only Data Collections
related to that particular Work Order Operation
are displayed in this tab.
enabled, the isRepeated and Is NOk columns will be
visible.
If Work Instructions are associated to Execution Group
Phases, the Execution Group and Execution Group
Phase columns are displayed.
Hold Details regarding Work Order Operations belonging to the

Work Order that are on hold: for example, Hold Reason
and Hold Status.
Rework Details regarding the Rework code that represents an

associated Rework Operation, associated Defects, Failures
(enabled only if the selected Work Order is a
and a Final Material.
Rework Work Order)
Non-Conformances Details regarding Non-Conformances associated to the

Work Order.
Change Any Change requests for the Work Order.
Notes Any Notes regarding the Work Order.

Tracking Additional Actions
Tab Contents
Collected Documents Any Documents associated to Work Order Operations of

the Work Order at runtime.
 If you selected a Work Order

Operation in the Operations tab, only
Documents related to that particular Work Order
Operation are displayed in this tab.
Quality Inspections Data collected during inspection activities or details about

Buy-Off activities.
To see the details of a specific Buy-Off request:
1. Select the Buy-Off request itself.
2. Select the Work Order Operation/Step of interest.
3. Select the Serial Number to which the Buy-Off is
related.
4. Click the button to navigate to the Buy-Off Details
page.
5. To see the signers, click .
Serial Numbers Any Serial Numbers associated to the Work Order.

(available only for serialized production)
 Selecting an item in this tab will affect what is
displayed in the Operations, Data Collection,
Tools and Documents Collected tabs, filtering
the items they contain accordingly.
If the Result Management configuration key has
been enabled and there is at at least one Work
Order Operation for which a Serial Number has
been declared as having a negative Result on the
Work Order, the indicator will be displayed
in the lower-left corner of its corresponding
Serial Number tile.
If there is already a Work Order Operation
selected in the Operations tab (see above in this
table), this indicator will be visible only on those
Serial Numbers in which the Work Order
Operation has a negative Result.
15.4 Tracking Additional Actions

The system automatically tracks the action performed at runtime by Operators for each Work Order. But in some
cases, if this data is not correctly tracked (for example, due to a network connection problem during production),
you have the possibility to manually change tracked information or add new actions.

Monitoring Work Order Operations in Execution on a Workcenter or Machine
Target User
Procedure
1. Click Production Coordination > Production Coordinator Time Update in the sidebar.
2. Select a Work Order in the Production Coordinator Time Update page and click Open.
3. In the History tab, click Create.
Field Description
Operation The Work Order Operation on which the action has been performed.
Action Type The type of action (Start, Pause or Complete) to be performed as an

adjustment to the data related to the Work Order that is already traced.
For example, if a task is not traced by the system, you can create an action
to include tracing of this task.
User The user who performed the action.
Date The action timestamp.
Reason (Only if you have set Action Type to Pause) The reason for pausing the
5. Click Create.
15.5 Monitoring Work Order Operations in Execution on a

Workcenter or Machine
The possibility of monitoring how the execution of a certain Work Order Operation is progressing on a specific
Workcenter or Machine is a great aid to Production Coordinators, as they can make immediate decisions on the
basis of runtime data.
Target User
Procedure
1. Click the Production Coordinator Dashboard in the home page: for each Workcenter and Machine, the system
indicates how many associated Work Order Operations are in Queue, Open and Active status, respectively.
2. Select the Workcenter or Machine of interest and then click Open: the system displays information on each
Work Order Operation, showing them graphically on a timetable if their execution has been scheduled. The time
range displayed spans from the current time minus one hour to the current time plus eight hours.

Associating Additional Users to Work Order Operations
 The content of Production Coordinator Dashboard is periodically refreshed at a predefined frequency.

You can pause the refresh clicking on Disable countdown, then resuming it clicking on Resume
countdown.
3. Click the button to select one or more sets of Work Order Operations that you want to display:
Option Resulting Display
Active Operations Work Order Operations in Active status.
Ready Operations Work Order Operations in Open status that are ready to
be executed.
Open Operations Work Order Operations in Open status.
Complete Operations Work Order Operations in Complete status.
Partial Operations Work Order Operations in Partial status.
 Clicking on the button you can set additional filters on specific Work Orders, Materials or date/time
ranges.
4. If, after viewing how production is progressing, you want to reschedule a certain Work Order Operation, thereby
streamlining overall execution and bypassing any potential downtime, see Scheduling a Work Order.
15.6 Associating Additional Users to Work Order Operations

In certain cases, during the execution of a Work Order Operation, the assigned User may need to be absent from his
workstation for a period of time for a variety of reasons (for example, he may be on call elsewhere within in the
production plant, sudden illness...): this makes it necessary to assign the work in progress to another User so that
the Work Order Operation's execution can be completed, without prejudice to overall production.
It is possible to assign additional Users only to Work Order Operations that are in
status Open, Partial, Active or Future Hold.
Target User
Procedure
1. Follow all steps for monitoring Work Order Operations in execution on a Location or Machine: the Production
Coordinator Dashboard will open directly in Timeline Mode. Click > User Mode to switch to User Mode.
Otherwise, if you are already working with the Production Coordinator Dashboard in User Mode, go directly to
the step below.

Updating the Labor Time
2. Select the Work Order Operation to which you want to associate one or more Users: the system displays any
Users that have already been associated to the selected Work Order Operation, as well as the Skills required to
execute the Work Order Operation.
 Each Skill will be displayed in its assigned color, if this property was set during Skill configuration.
3. Click Link User to Work Order Operation.

4. In the Associate Users panel, select one or more Users that you want to associate to the Work Order Operation
and click Save.
 To unlink one or more Users from the selected Work Order Operation, select them and click Unlink
User from Work Order Operation.
15.7 Updating the Labor Time

The system automatically tracks when Work Order Operations are started and completed, and the time taken by
the Operators to complete Work Orders. But in some cases, if this data is not correctly tracked (for example, due to
a network connection problem during production), you have the possibility to change it manually.
Target User
Procedure
1. In the home page, click the Production Coordinator Time Update tile.
2. Select a Work Order in the Production Coordinator Time Update page and click Open.
3. In the Operations tab, select a Work Order Operation, and then click Edit.
Actual Start Time The date and time when the Work Order Operation was
actually started.
Actual End Time The date and time when the Work Order Operation
actually ended.
Labor Time (hours, minutes, seconds) The actual time taken to complete the Work Order
Operation.
5. Click Save.
15.8 Viewing and Amending the Results of a Material Tracking Unit


Viewing and Amending the Results of a Material Tracking Unit
Provided that the Result Management and Result Strategy Management configuration keys have been set, it is
possible to view the Results declared for a specific Material Tracking Unit being produced, as well as their history.
Should you deem that a declared Result needs to be changed (for example, because it was entered incorrectly), it
can be amended, provided that its corresponding Serial Number or Batch is not undergoing execution. An Amend
can be performed on a Result's value and/or the strategy that was adopted in relation to the declared Result.
Viewing the Results of an MTU (including their History)

1. In the Material Tracking Units page, select a Material Tracking Unit that is being produced and the Results of
which you want to examine and click Open.
2. Click the Results tab: a grid is displayed, listing the various Results for the selected MTU, starting from the most
recent Result (top-down chronology).
Each row of the grid contains the value declared for each Result, as well as the strategy (corrective action) adopted,
the Work Order Operation to which the Result refers and the date on which the Result was declared.
 Those Results with a history (that is, which have undergone changes, either regarding their value or their
associated corrective action) have a plus sign at the beginning of their corresponding row. To view the
history of a Result, simply click the plus sign to open the corresponding accordion: the changes that the
selected Result has undergone are listed, from the most recent to the oldest.
Amending a Result on an MTU

1. In the Material Tracking Units page, select a Material Tracking Unit that is being produced and click Open.
2. Click the Results tab.
3. Operating in the grid that is displayed, select the Result to be amended and then click the Amend icon: this
opens the Amend panel.
4. If necessary, modify Result Value as needed, according to the options illustrated in the table below: otherwise,
go to the next step.
If the Result is declared as... You can amend it to...
NOK • OK
• a custom positive value
• a custom negative value
OK • NOK
• a custom negative value
• a custom positive value
A custom negative value (for example, Bad) • OK

• NOK
• a custom positive value (for example, Good)
• a different custom negative value (for
example, NoGood)
A custom positive value (for example, Good) • NOK

• OK
• a custom negative value (for example, Bad)
• a different custom positive value (for
example, Positive).
5. If necessary, modify Corrective Action as needed: otherwise, go to the next step.

Displaying Powder Genealogy
6. Click the Amend button to confirm.
 If you intend to perform an Amend on FullSerialized MTUs, you must specify whether the Amend is to
be applied to all Serial Numbers (Do you want to amend the Result for all the Serial Numbers
produced by the selected Full Serialized Operation?).
Possible values:
• YES: The Amend is to be applied also to the other MTUs to be produced.
• NO: The Amend is applied solely to the selected Serial Number: in this case, if the corrective
action (strategy) is a Repeat, the Work Order Operation's re-execution will fail because it will not
have all of its Serial Numbers in input.
15.9 Displaying Powder Genealogy

The Genealogy of Powder Material Batches is available as a graph which shows the "parents" of a Powder Batch
and, if present, its "children" (for example, the batches created mixing it with other batches, or splitting it into
smaller quantities).
Target User
Procedure
1. In the home page, click Powder Genealogy.
2. In the Powder Genealogy page, set the following parameters:
Powder Batch Code of the Powder Material Batch to display. Either enter
directly the code or click to select it from a list.
Levels Number of hierarchical levels to be displayed.

The Powder Material Batch you searched for is displayed in light blue, while all related Powder Material Batches
are displayed in gray.
3. Select an item in the tree to display its details in the right panel:
Identifier The unique Identifier of the selected Powder Material Batch.
Code The code of the selected Powder Material Batch.
Status The current status of the selected Powder Material Batch.
Target (Visible if the Powder Material Batch has been consumed). The final
product which has been assembled from the consumed Powder
Material Batches.
Consumed Quantity (Visible if the Powder Material Batch has been consumed). The
quantity which has been consumed.

Tracking Non-Conformance Histories
Mixed Quantity (Visible if the Powder Material Batch has been mixed). It displays
the quantity of the current Powder Material Batch that was mixed
into another Powder Material Batch.
Quantity The current quantity of the selected Powder Material Batch.
Recycle Count The number of times the Powder Material Batch has been recycled.
Max. Recycle Count The maximum number of times the Powder Material Batch can be
recycled.
Created By The user that created the Powder Material Batch.
Created On The timestamp of the Powder Material Batch creation.

In addition, the panel displays the unique identifier and current quantity of each related Powder Material Batch
(both parent and child).
4. If documents have been associated to the batch or to its "parents", the Documents area is displayed listing
them: select the documents of interest and then click the button to download them.
Customizing the Graph

If necessary, you can customize the Genealogy Graph as follows:
• To display a window containing a preview of the entire graph, click Pan and Zoom, and then:
15.10 Tracking Non-Conformance Histories

The system automatically tracks the history of all changes that a Non-Conformance undergoes.
Specifically, the following details are logged:
• Actions related to a Non-Conformance:
• creation
• editing
• addition and/or removal of notes and documents
• change of status
• Defects and Failures added and/or removed from a Non-Conformance
• Attachments
• Severity.
Target User
Procedure
1. In the home page, click the Non-Conformances tile.

Monitoring and Managing Output Messages at Runtime
2. In the Non-Conformances page, select a Non-Conformance and click Open.

3. Click tab History to display the history of the selected Non-Conformance.
15.11 Monitoring and Managing Output Messages at Runtime

Opcenter EX DS enables you to monitor and manage the Output Messages generated for a specific Work Order or
Work Order Operation, by viewing which Message Definitions have already been used to send a specific Message
and which are still to be used.
The Output Messages page displays all the Message Definitions associated with a Work Order or a Work Order
Operation. From this page you can perform the following operations:
• send a new Message for a Message Definition never used before. The system automatically updates the data, if
necessary, before sending the Message.
• resend a copy, keeping the same data, of the last Message sent to a specific Message Destination.
• view the History of the Messages generated and sent for a specific Message Definition, and resend the Message if
necessary.
• download the Message content, which will contain information on the Sections previously configured for the
Message Definition.
Procedure
1. To access the Output Messages page, perform one of the following operations:
• in the Work Orders page, select a Work Order and click the button.
• in the Work Order Operations page, select a Work Order Operation of interest and then click the
button.
The system displays all the Message Definitions for the selected Work Order or Work Order Operation,
with the following data:
• Identifier - The identifier of the Output Message Definition.
• Name - The name assigned to the Output Message Definition.
• Destination - The Destination of the Output Message associated with the Message Definition.
• Is Sent - Flag indicating if the Message for a specific Message Definition has been already sent or
not.
• Last Sent On - Timestamp of the last sending (visible only if the Message has already been sent).
• Last Message Id - The identifier of the last Message sent for a specific Message Definition and Work
Order or Work Order Operation
2. To send or resend a Message, select the Work Order or Work Order Operation and click the button.
3. To view the Output Messages report, open the Work Order or Work Order Operation and select the Output
Messages tab. The system displays the following details:
• Message Id - The identifier of the Output Message.
• Output Message Definition - The Definition associated with the Output Message.
• Output Message Definition Revision - The revision of the Definition associated with the Output Message.
• Is Regenerated - Flag indicating if the Message has been regenerated, that is resent, or not.
• Destination - The Destination of the Output Message associated with the Message Definition.
• Created On - The timestamp of the Message generation.
4. If necessary, remaining in the Output Messages page, select a specific Message Id and click Download
Messages to download the content of the Message.

Monitoring and Managing Kanban Calls
15.12 Monitoring and Managing Kanban Calls

The product provides you with the possibility to monitor released Line Side Positions and the status of any related
Kanban Call (if already sent), including the answers from the Warehouse.
In addition, it is possible to:
• open a new call, if no other call is active for the selected Line Side Position,
• cancel the request for a Kanban Call previously sent.
Only for automatically managed Line Side Positions:
• increase the priority of a Kanban Call previously sent,
• update the Line Side Position actual quantity.
Target User
Procedure
1. Click Material Runtime > Line Side Positions Monitoring in the sidebar. The following information for
each Line Side Position is displayed:
Workplace The Workplace associated with the Line Side Position.
Material Identifier The identifier of the related Material.
Material Revision The Revision (version) of the related Material.
Manual Flag indicating if the Line Side Position is managed manually.
Bins to be requested Populated only in case of manual Line Side Positions.

Represents the number of Bins to be requested.
Actual Quantity The actual quantity of the Line Side Position.
Logic The logic applied to the Kanban Call. Possible values are:
• Automatic
• Manual
Status Status of the Kanban Call. Possible values are:

• Open
• In Progress
• Shipped
• Delivered
• Cancelling
• Cancelled

Monitoring and Managing Kanban Calls
Priority Priority of the Kanban Call.
Last Updated On Date and time of when the Kanban Call was last updated.
Created On Date and time of when the Kanban Call was created.
2. Select a Line Side Position and perform one of the following operations according to your needs:
• Click , to open a new call.
• Click , to cancel the call.
• (visible only in case of automatically managed Line Side Positions) Click , to increase the call priority.
• (visible only in case of automatically managed Line Side Positions) Click , to update the Line Side
Position actual quantity.
Result
You can trace actions performed on Line Side Positions by opening a Line Side Position of your interest and clicking
the Line Side Position History tab. The details include information on the previous quantity and new quantity.
The status of Kanban Calls associated with a Line Side Position can be traced by opening a Kanban Call of your
interest and clicking the Kanban Request History tab. In this tab, it is also possible to select a call and click the
button to download an XML file containing the content of the Message.

How to Integrate Opcenter Execution Discrete with Other Systems
How to Benefit from Integration with Siemens Opcenter APS
16 How to Integrate Opcenter Execution Discrete with Other

Systems
The product offers several possibilities of integration with other systems:
• Integration with Siemens Opcenter APS, for advanced planning and scheduling of manufacturing operations.
• Integration with Teamcenter (both alone and in conjunction with SAP), for Closed-Loop manufacturing.
• Integration with Opcenter Connect MOM, for structured-message exchange.
• Integration with DNC systems, to directly supply Numerical Control (NC) Machines with production planning
data.
• Integration with Siemens Opcenter QMS, for quality inspection of manufacturing operations.
To benefit by the aforementioned integration options, certain procedures must be followed: see the dedicated sub-
pages under page "Integration with Other Systems" in the Opcenter Execution Discrete Installation and Configuration
Manual.
16.1 How to Benefit from Integration with Siemens Opcenter APS

Integration with Opcenter APS allows you to close the gap between planning/scheduling and execution. The
synergy that you create with Opcenter APS helps you to streamline execution activities in a capillary manner, as
they are scheduled for each machine within the actual context of what is currently occurring on the shop
floor. In particular, this integration allows you to download scheduled Work Orders, Work Order Operations,
Execution Groups or Execution Group Phases from Opcenter APS database to Opcenter Execution Discrete
database.
During planning and scheduling activities, if changes are made to production, then Opcenter EX DS will send data
to Opcenter APS via a dedicated Alerts Window in order for corrective measures and tuning to be adopted to the
schedule.
Prerequisites
• Integration with Opcenter APS is achieved, as described in the Opcenter Execution Discrete Installation and
• Opcenter EX DS contains all necessary master data for production.
Workflow
1. In the Opcenter APS environment, schedule Work Orders/Work Order Operations from Opcenter APS to
Opcenter EX DS.
2. In the Opcenter Execution Discrete environment, verify that the system has correctly downloaded the
scheduled Work Orders, Work Order Operations, Execution Groups or Execution Group Phases from the
Opcenter APS database into the Opcenter EX DS database.
16.1.1 Scheduling Work Orders/Work Order Operations from Opcenter

APS
After the system imports Work Orders, Work Order Operations, Execution Groups or Execution Group Phases from
the Opcenter Execution Discrete database into the Opcenter APS database, you must download scheduled data
from the Opcenter APS database to the Opcenter Execution Discrete database.
During scheduling activities, if changes are made to production (for example, an Operator or a Production
Coordinator changes the operation status by starting Work Orders), then Opcenter Execution Discrete will send
data to Opcenter APS via a dedicated Alerts Window. In this case, you can decide to:

How to Benefit from Integration with Siemens Opcenter APS
• Accept the notified changes and schedule the data updated from Opcenter Execution Discrete.
• Ignore the alert and continue your planning.
 Work Orders can also be scheduled from Opcenter Execution Discrete. For more information, see
Scheduling a Work Order.
Target User
Users with the APS role can perform this operation.
Procedure
1. In the Opcenter APS environment, operating on the menu list, click Workspace > General.
2. In the General area, click Generate Schedule.
3. In the Sequencer page, click View > Editor Window.
4. Click Tools > Peg Materials.
5. From the Sequence menu, click Forward Sequence > Forward By Due Date.
6. From the File menu, click Exit: this opens the Sequencer dialog box.
7. Click Yes if you want to confirm the original scheduling. At this point, you have completed this procedure.
Otherwise, if you want to cancel the original scheduling, click No: in this case, no data will be downloaded to the
Opcenter EX DS database and you must go to step 8 to schedule the data updated from Opcenter EX DS.
8. Repeat steps 1 through 6.
9. In the Sequencer dialog box, click Yes to confirm the new scheduling: the system downloads the updated data
to the Opcenter Execution Discrete database.
16.1.2 Verifying the Download of Scheduled Work Orders/Work Order

Operations to Opcenter Execution Discrete
After the system has imported Work Orders/Work Order Operations from Opcenter EX DS database to Opcenter APS
database and after having scheduled this data from Opcenter APS to Opcenter EX DS, you must verify that the
system has correctly downloaded the scheduled Work Orders, Work Order Operations, Execution Groups or
Execution Group Phases to the Opcenter EX DS database.
To perform this check, either follow the procedure below, or see How to Monitor and Tweak Production Execution.
Target User
Users with the APS role can perform this operation.
Procedure
1. In the Opcenter Execution Discrete home page, click the Work Orders tile.
2. In the Work Orders page, select a Work Order and click Open.
3. Click the Operations tab: the list of the Work Order Operations belonging to the current Work Order is
displayed.
4. Select a Work Order Operation and click Open.
5. Check that Estimated Start Time (estimated date when the Work Order Operation is to be started)
and Estimated End Time (estimated date when the Work Order Operation is to end) have been updated.

How to Benefit from Integration with DNC Systems
16.2 How to Benefit from Integration with DNC Systems

Integration with DNC systems allows you to transfer CNC programs to CNC machines during the execution of the
Work Orders.
To benefit from DNC integration, it is necessary that a number of macro-steps be performed: what is illustrated
below refers exclusively to those aspects that involve operations on Opcenter Execution Discrete. For information
on the steps that involve operating directly on the DNC interface, see its specific documentation.
Prerequisites
• A valid DNC interface is installed. For more information, see section How to Integrate Opcenter Execution Discrete
with DNC of the Opcenter Execution Discrete Extensibility Guide
• Integration with DNC systems has been enabled.
• The CNC programs have been imported and mapped.
Workflow
1. At least one Work Operation belonging to the CNC category is created.
2. A Work Order Operation instantiated from the Work Operation indicated in the previous step is created.
3. An Opcenter Execution Discrete Machine previously mapped to a DNC machine is associated to the Work Order
Operation.
4. A CNC Program reference is associated to said Machine.
5. At runtime, the Work Order Operation is started and the CNC program is transferred to the Machine.

Deprecated Functionalities
Configuring Defects (Deprecated)
17 Deprecated Functionalities
The following functionalities have been deprecated, each page contains the links to the alternative procedures:
• Configuring Defects (Deprecated)
• Configuring 3D Printers (Deprecated)
• Configuring Powder Materials (Deprecated)
• Creating Powder Material Batches (Deprecated)
• Recycling Powder Material Batches (Deprecated)
• Mixing Powder Material Batches (Deprecated)
• Displaying Powder Genealogy (Deprecated)
17.1 Configuring Defects (Deprecated)

 Failures must be used instead of Defects that have been deprecated.
Defects are abstract representations of possible problems or anomalies that can happen during the manufacturing
processes. Defects can be categorized and divided into groups, which can optionally be associated with specific
Material or Machines or Machine Definitions. At runtime, when the Operator assigns a defect to a Work Order
Operation, he can browse the defect groups that can either belong to a specific context or not.
Failures, on the other hand, are custom problems that can occur during the life cycle of a product or process. Using
the Failures page, Failures can be created as stand-alone Failures or they can be organized into more specific Sub-
Failures.
The procedure below indicates the steps required to configure a Defect. For more information on how to create
Failures or Sub-Failures, refer to How to Manage Failures and Quality Actions in the Opcenter Execution Foundation
User Manual for details.
If contextualized, the system performs dedicated checks to verify that either of the following is true:
• The Material matches with the Final Material of the Work Order.
• The Machine or Equipment Type matches with the Machine assigned to the Work Order Operation.
Once created, Defects or Failures can be associated with specific Quality Non-Conformances (declared either by a
Production Coordinator or by an Operator) or with Rework Codes.
Defects and Defect Groups that are already in use at runtime cannot be modified or deleted.
Workflow
1. Create a Defect Group.
2. (Optional) Associate a Defect Group with Materials.
3. (Optional) Associate a Defect Group with Machines or Equipment Type.
4. Create a Defect and associate it with the Defect Group.
Creating a Defect Group

1. To access the Defect Group page, click Product and Production Configuration > Defect Groups in the
sidebar.
2. Click Create.

Configuring Defects (Deprecated)
Identifier Unique identifier to be assigned to the Defect Group. Once saved,

Name Name of the Defect Group.
Description Useful information about the Defect Group.
Parent Groups The parent group to which you want this group to belong.
Child Groups The existing groups that will become children of the selected group.
4. Click Create.
Associating a Defect Group with Materials

1. In the Defect Groups page, select a Group and click Open.
2. Click the Materials tab.
3. Click Add.
4. Select one or more Materials to be associated with the Defect Group and click Save.
Associating a Defect Group with Machines or Equipment Type

1. In the Defect Group page, select a Group and click Open.
2. Click the Machines tab.
3. Click Add.
4. Select one or more Machines and/or Equipment Type to be associated with the Defect Group and click Save.
Creating a Defect
1. To access the Defect Type page, click Product and Production Configuration > Defect Types in the
sidebar.
2. Click Create.
Identifier Unique identifier to be assigned to the Defect. Once saved, this

Name Name of the Defect.
Description Useful information about the Defect.
Defect Groups The Defect Group you want to associate with the Defect.
4. Click Create.

Configuring 3D Printers (Deprecated)
17.2 Configuring 3D Printers (Deprecated)

 Starting from version 4.2, the 3D Printers page has been replaced by a new one provided by the
PrintJobFile App. The old page, described below and provided by the AppU4DM App, is contained neither
in the Siemens_SIT_UADM nor in the Siemens_OPC_EXDS_AM UI Application but it has been installed
with the product for compatibility reasons.
While configuring Additive Manufacturing, you can configure 3D printers. This requires:
• associating the name assigned to them by Opcenter Execution Discrete to the name used by the external CAM
system;
• specifying the plugin to be used for Print Job Files transfers.
 Users with the appropriate rights can perform this procedure also while creating Equipment
Configurations.
Procedure
1. In the home page, click the 3D Printers tile.
2. Select a printer and click Assign Plugin.
Parameter Name
External Machine identifier Identifier of the 3D Printer in the external system that
generated the Print Job File.
Plugin name The name of the Plugin that manages the Print Job File
transfer.
4. Click Save.
17.3 Configuring Powder Materials (Deprecated)

 Starting from version 4.2, Powder Materials must be configured from the Powders page. This functionality
has been maintained in the Materials page, only for compatibility reasons.
Powder Materials represent a type of Material peculiar to Additive Manufacturing and from which Powder Material
Batches are instantiated at runtime. This particular type of Material requires specific configuration.
Your starting point remains the procedure for configuring a Material from scratch, but you must set additional
parameters if the Material you are configuring is intended for instantiating a Powder Material Batch.
The parameters specific to Powder Materials are described below: these parameters can be updated as needed.
Target User

Creating Powder Material Batches (Deprecated)
Procedure
1. In the Materials page, click .
2. Set the general parameters as described in Creating a Material from scratch, taking care to set Material Class to
AMPowder.
3. Set the following additional parameters specific to Powder Materials:
Max. Recycle Count The maximum number of times a Powder Material Batch can be
recycled. If the number of times the Powder Material Batch has
been recycled exceeds this value, the status of the Powder Material
Batch is set to Spent, thus making it no longer available for
production.
Min. Quantity If the quantity of the Powder Material Batch falls below this value,
the status of the Powder Material Batch is set to Quarantine, thus
making it unavailable for production.
4. Click Save.
17.4 Creating Powder Material Batches (Deprecated)

 Starting from version 4.2, Powder Material Batches must be configured from the Powder Batches page.
This functionality has been maintained in the Material Tracking Units page, only for compatibility
reasons.
Opcenter Execution Discrete supports a special type of Material Tracking Unit specific to Additive Manufacturing
known as Powder Material Batch. Powder Material Batches represent the raw material to be used for a 3D printing
operation. Powder Material Batches are instantiated from a special type of Material known as Powder Material.
Your starting point remains the procedure for instantiating a Material Tracking Unit, but you must set additional
parameters if the MTU you are creating is to be used as a Powder Material Batch.
Powder Material Batches are created solely from the Material Tracking Units page, but can be managed from the
Powder Genealogy, Powder Batch Mixing and Powder Recycle pages.
Once you have created a Powder Material Batch, it is possible to associate one or more Documents to it to provide
the Operator with additional relevant information (for example, laboratory analysis results) after recycling or
mixing during runtime.
As other batch-type MTUs, existing Powder Material Batches can be split into smaller batches or, conversely, mixed
to create greater ones.
It is possible to change the status of a Powder Material batch according to your needs.
 In certain contexts (for example, when mixing Powder Material Batches), you can force a Powder Material
batch to transition to any state, even if contrary to what is standard behavior regarding its lifecycle:
however, no threshold checks are performed when the status of a Powder Material Batch is changed
manually. Therefore, this action should be performed with caution.

Creating Powder Material Batches (Deprecated)
Target User
Procedure
1. In the Material Tracking Units page, click Add Material Tracking Unit.
2. Set the general parameters as described in How to Create and Prepare Material Tracking Units, taking care to
select a Powder Material: that is, the Material Class of the Material you select must be set to AMPowder.
3. Set the following additional parameters specific to Powder Material Batches:
Max. Recycle Count The first time a powder batch is created, its Recycle Count is set to
zero. Thereafter, following each recycle, this value is incremented.
If the incremented value becomes greater than the Max. Recycle
Count, the status of the powder batch is set to Spent, and the
powder batch is not available for production. The value of this
parameter is inherited from its corresponding Material, but can be
superseded, if necessary.
Min. Quantity If the powder batch quantity falls below this value, the status of the
powder batch is set to Quarantine, and the powder batch is not
available for production. The value of this parameter is inherited
from its corresponding Material, but can be overridden, if
necessary.
4. Click Create.
Associating Documents to a Powder Material Batch

1. Select the Powder Material Batch in the Material Tracking Units page and click .
 This step can also be performed from the Powder Batch Mixing and Powder Recycle pages.

3. Click .
4. If the Document to be associated is not displayed in the list, click Import and then browse the file of interest.
5. Select the Document to be associated to the Powder Material Batch and then click Save.
Changing the Status of a Powder Material Batch

1. In the Material Tracking Units page, select the Powder Material Batch the status of which you want to change
and click .
2. Click .
3. Edit the Verb field according to your needs and click Save.

Recycling Powder Material Batches (Deprecated)
17.5 Recycling Powder Material Batches (Deprecated)

 Starting from version 4.2, the Powder Recycle page has been replaced with a new one provided by the
PowderMgt App. The old page, described below and provided by the AppU4DM App, is contained neither
While printing 3D items, a Powder Material batch might not be completely consumed, leaving behind some Powder
Material. Opcenter Execution Discrete supports the capability of collecting and reusing leftover Powder Material
from one or more Powder Material batches. The dedicated process for reusing Powder Material is called recycling.
Powder Material from a Powder Material batch can be recycled in some way (for example, by sieving) in order to
remove impurities or make it ready for production. After recycling, Powder Material from different batches can be
mixed together, or with other Powder Material batches to support a 3D print.
Prerequisite
The Powder Material batch you want to recycle must have status as Busy or Quarantine.
 To change the status of a Powder Material Batch, select it in the Powder Recycle page and then click
Override: this action allows you to edit the Status field according to your needs. Threshold checks
regarding the congruity of the status transitions you want to apply will be performed in this particular
context.
Procedure
1. Click Shopfloor Execution > Powder Recycle in the sidebar.
2. In the Powder Recycle page, select the Powder Material batch that you want to recycle.
3. Click the Recycle button.
Result
The recycle operation has started. The number of recycle operations for this Powder Material batch can be traced
by using the Current Recycle Count and the Maximum Recycle Count parameters. If Current Recycle
Count becomes greater than the Maximum Recycle Count, the status of this Powder Material batch is
automatically set to Spent, and the Powder Material batch becomes unavailable for production.
17.6 Mixing Powder Material Batches (Deprecated)

 Starting from version 4.2, the Powder Batch Mixing page has been replaced with a new one provided by
the PowderMgt App. The old page, described below and provided by the AppU4DM App, is contained
neither in the Siemens_SIT_UADM nor in the Siemens_OPC_EXDS_AM UI Application but it has been
installed with the product for compatibility reasons.
One or more Powder Material batches of the same Material can be mixed to form a new Powder Material batch. This
new batch can be used for 3D printing. You can mix leftover Powder Material from multiple batches, as well as
unused Powder Material batches, to create new Powder Material batches. The newly-created batch can then be
consumed by a Work Order Operation.
It is then possible to display the genealogy of Powder Material Batches to verify how they have been mixed.

Mixing Powder Material Batches (Deprecated)
 Secondary effects of mixing Powder Material Batches

• When a Mix involving a Powder Material Batch to which one or more Documents have been associated
is performed, by default these Documents are not associated to the resulting Batch. To enable this
association, you must enable its related Post Action. Refer to Configuring Command Settings in
the Opcenter Execution Foundation Development and Configuration Guide for details.
• When a total Mix involving Powder Material Batches belonging to different Buffers is performed, the
source Powder Material Batches will be automatically removed from the original Buffers to which the
source Powder Material Batches belonged.
• When a Mix is performed on Powder Material Batches belonging to the same Buffer, the resulting Batch
will belong to the original Buffer to which the source Powder Material Batches belonged.
Supported Scenarios
Opcenter Execution Discrete supports the following two use cases for creating new Powder Material batches:
• Two Powder Material batches with the same Material and UOM are selected, and the system creates a new
Powder Material batch having the same Material and UOM as the source Powder Material batches.
• Only one Powder Material batch is selected, but during mixing, the system creates a Powder Material batch
having the same Material and UOM and mixes them.
Prerequisite
The two Powder Material batches you want to mix must have the same Material and UOM, and their status must
be Available or Mixable.
Selecting Two Powder Material batches for Mixing

2. In the Powder Batch Mixing page, select the two Powder Material batches that you want to mix.
3. Click the Mixing button.
Identifier Unique identifier to be assigned to the Powder Material batch.

Batch ID The unique identifier of the Powder Material batch. Either type it
manually or click the Generate button to automatically create it
according to a predefined template.
Material Tracking Unit Quantity The system sets this field to a value that equals the sum of the
quantities of both Powder Material batches. You can change this
value. The quantity of the Powder Material batch must be at
least 1; otherwise, you cannot complete the mixing job.

Minimum Quantity Threshold The minimum value you want to set for the quantity, below
which the new Powder Material batch will not be considered
valid for production. The system automatically populates this
field with the value set as the quantity threshold during the
configuration of the Material to which the selected batches
belong, but you can change it.
Maximum Recycle Count The lower of the two Maximum Recycle Count values. The first
time a Powder Material batch is created, its recycle count is set
to zero, and an upper cutoff value is specified using Maximum
Recycle Count. Thereafter, after each recycle instance, this
number is incremented, and the batch remains available for
production so long as its value does not exceed Maximum
Recycle Count. You can change this value.
Current Recycle Count Represents the number of times a Powder Material Batch is
recycled. With each recycle operation, this field is incremented.
Current Recycle Count is set to the greater value of the two. You
can edit this field.
5. Click Save.
Selecting a Single Powder Material batch for Mixing

2. In the Powder Batch Mixing page, select the Powder Material batch that you want to mix.
3. Click the button.
Identifier Unique identifier to be assigned to the Powder Material batch.

Batch ID The unique identifier of the Powder Material batch. Either type it
manually or click the Generate button to automatically create it
according to a predefined template.
Material Tracking Unit Quantity The system sets this field to a value that equals the sum of the
quantities of both Powder Material batches (the one you select,
and the one that the system creates). The quantity of the Powder
Material batch must be at least 1; otherwise, you cannot
complete the mixing job.

Minimum Quantity Threshold The minimum value you want to set for the quantity, below which
the new Powder Material batch will not be considered valid for
production. The system automatically populates this field with
the value set as the quantity threshold during the configuration
of the Material to which the selected batch belongs, but you can
change it.
Maximum Recycle Count The lower of the two Maximum Recycle Count values. The first
time a Powder Material batch is created, its recycle count is set to
zero, and an upper cutoff value is specified using Maximum
Recycle Count. Thereafter, after each recycle instance, this
number is incremented, and the batch remains available for
production so long as its value does not exceed Maximum
Recycle Count. You can change this value.
Current Recycle Count Represents the number of times a Powder Material batch is
recycled. With each recycle operation, this field is incremented.
You can edit this field.
New Material Identifier Unique identifier to be assigned to the Powder Material batch
that the system will create at runtime. Once saved, this
New Material Batch ID The unique identifier of the Powder Material batch that the
system will create at runtime. Either type it manually or click
New Material Quantity The quantity of the Powder Material batch that the system will
create. The quantity of the Powder Material batch must be at
least 1; otherwise, you cannot complete the mixing job.
New Material Maximum Recycle The recycle count of the Powder Material batch that the system
Count will create. After each recycle instance, this value is incremented
by 1.
New Material Current Recycle Count Represents the number of times the Powder Material Batch that
the system will create is recycled. With each recycle operation,
this field is incremented and it is set by default to zero. You can
edit this field.
5. Click Save.

Displaying Powder Genealogy (Deprecated)
 To change the status of a Powder Material Batch, select the Powder Material Batch and then click
Override available on the command bar: this action places the focus on the Status field, which can then
be edited according to your needs. In this particular context, threshold checks are not performed in regard
to the status transitions that you want to apply. Therefore, use caution when performing an Override when
you are operating in the Powder Material Mixing page.
Changing the status of a Powder Material Batch, as well as other actions (such as linking and unlinking
Documents) that are performed from the Powder Batch Mixing screen are traced in the History tab. Such
details include: the user who performed the action, the date and time when the action was performed, the
action that was performed on the Powder Material Batch (for example, changes in status, linking/unlinking
of Documents) and so forth.
17.7 Displaying Powder Genealogy (Deprecated)

 Starting from version 4.2, the Powder Genealogy page has been replaced with a new one provided by the
PowderMgt App. The old page, described below and provided by the AppU4DM App, is contained neither
Powder batches can be mixed to create new batches. The history is available as a graph which shows the "parents"
of a Powder Batch (that is, the batches mixed to create it) and, if present, its "children" (that is, the batches created
mixing it with other batches). Genealogy is provided for Powder Material Batches.
For the new batch resulting from the mixing of Powder Material Batches, in the panel on the right of the screen, you
can view:
• the details regarding the batch resulting from the mix;
• the details of its parent Powder Material Batches;
• the documents (if any) previously associated to the "parent" powder batches.
Genealogy is also provided when Powder Material Batches are split into smaller quantities.
Target User
Procedure
1. In the home page, click Powder Genealogy.
2. In the Powder Genealogy page, set the following parameters:
Identifier Identifier of the Powder Material Batch to display.
Note You can enter directly the identifier or click to select

it from a list.
Max No. of Genealogy Levels Number of hierarchical levels to be displayed, relative to the
selected Powder Material Batch.
The genealogy graph of the selected Powder Material Batch is displayed in the bottom panel.

Displaying Powder Genealogy (Deprecated)
3. Click a batch object in the tree: the right panel displays the details of the selected object.
Customizing the Graph

Perform the following operations to customize the Powder Material Batch Genealogy Graph:
• To display a window containing a preview of the entire graph, click Pan and Zoom, and then:
Downloading the associated Documents

1. Click a batch object in the tree: if there are Documents associated to the batch or to its "parents", the lower area
of the right panel displays their list, that can be sorted clicking on .
2. Click to download a Document.

OpcenterEXDS UserManual

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

OpcenterEXDS UserManual

Uploaded by

Copyright:

Available Formats

Opcenter Execution Discrete 4.

Siemens AG PL20210504131482743 Copyright © Siemens AG 2021

Opcenter Execution Discrete 4.2 - User Manual iii

iv Opcenter Execution Discrete 4.2 - User Manual

Opcenter Execution Discrete 4.2 - User Manual v

6 How to Configure and Manage Output Messages .........................................154

vi Opcenter Execution Discrete 4.2 - User Manual

8 How to Execute Work Orders..........................................................................238

Opcenter Execution Discrete 4.2 - User Manual vii

9 How to Execute Production on Execution Groups ........................................306

viii Opcenter Execution Discrete 4.2 - User Manual

Opcenter Execution Discrete 4.2 - User Manual ix

x Opcenter Execution Discrete 4.2 - User Manual

Title User Manual

Product Title Opcenter Execution Discrete

Version Title 4.2

Product Version OpcenterEXDS_4.2.0.0

Summary Provides detailed information on how to use the Opcenter

Audience Operator, Supervisor, Support Engineer

Opcenter Execution Discrete 4.2 - User Manual 11

1 Basic Know-How Before Getting Started

Accessing the Applications

 The direct paths of the Applications are:

2. Log in to the Opcenter EX DS web page in either of the following ways:

The Home Page

12 Opcenter Execution Discrete 4.2 - User Manual

Apps and Extension Apps included in the Discrete Solution

Selecting and searching for elements

• selecting the tile and clicking Open.

Applying User Preferences

Import and Export of Data from the Runtime Database

1.1 Apps and Extension Apps included in the Discrete Solution

Opcenter Execution Discrete Apps

Opcenter Execution Discrete 4.2 - User Manual 13

Apps and Extension Apps included in the Discrete Solution

Name Provided Functionalities U4DM DS4AM

AppU4DM Core functionalities for managing

BoP Bill of Processes, Catalogs and

MaterialTraceability Material consumption tracing.

FunctionalCode Functional Code management.

OutputMessage Output Message management.

QualifCriteria Qualification Criteria management.

Kanban Kanban Call and Line Side Position

AMMaterialRemoteInt Integration between microservices

AMMaterialInt Synchronization of Materials used in

AMEquipmentInt Synchronization of Equipment used

AMEquipmentRemoteInt Integration between Equipment used

AMPowderRtRemoteInt Integration between runtime

DSAMRemoteInt Integration between services used

14 Opcenter Execution Discrete 4.2 - User Manual

Apps and Extension Apps included in the Discrete Solution

Name Provided Functionalities U4DM DS4AM

MaterialAMRemoteInt Integration between Materials used

PrintJobFile 3D Printing Management.

PowderMgt Powder Management.

EquipmentAMInt Synchronization of Equipment used

PluginMgt Management of Plugins handling

PJFPluginMgt Integration between Print Job Files

RtAMPowderRemoteInt Integration between Materials used

RuntimeAMPowderInt Integration between Powders used in

PjfRtRemoteInt Integration of Print Job File runtime

RtPJFInt Synchronization of runtime 3D

Opcenter Execution Discrete Extension Apps