DELMIA Apriso 2023 Implementation Guide

Explosion, Navigation and Tasking

®2022 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA, NETVIBES, and 3DXCITE
are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners.
Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 2

Contents
1 Overview 3
1.1 Explosion and Navigation 3
1.2 Exploding Work Orders and Operations 3
1.3 Navigation of Quantities between Operations 6
1.4 Tasking 7
1.4.1 Design-Time Configuration of Tasks 8
2 Jobs to Service Requests 10
3 Data Model 11
4 High-Level Flows 13
4.1 Work Order Explosion 13
4.2 Discover Process 13
4.3 Discover Recipe 14
4.4 Process Order Explosion 15
4.5 Standard Operation Order Explosion 16
4.6 3DEXPERIENCE Process-Based Order Explosion 16
4.7 Operation Explosion 17
4.7.1 Process Operation and Standard Operation Explosion 17
4.7.2 3DEXPERIENCE Process Operation Explosion 17
4.8 PPR Process Explosion 18
4.9 Operation Step Explosion 19
4.9.1 Process Based Explosion 19
4.9.2 Recipe Based Explosion 19
4.9.3 Standard Operation Based Explosion 19
4.9.4 3DEXPERIENCE Based Explosion 20
4.10 Component Explosion 20
4.11 Required Resource Explosion 24
4.12 Cross Order Explosion 25
4.13 Push Navigation 25
4.14 Pull Navigation 25
4.15 Extension Points for 3DEXPERIENCE Process-Based Order Explosion 26
5 Troubleshooting 28
6 Documentation Availability 29
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 3

1 Overview
The purpose of this document is to provide a high-level introduction to the DELMIA Apriso
concepts of Explosion, Navigation, and Tasking.

1.1 Explosion and Navigation

DELMIA Apriso Explosion and Navigation encapsulate the asynchronous functionality for
“executing” a Work Order.
In particular, Explosion:
Selects a relevant Process for a given Process-based Work Order
Selects a relevant Recipe for a given Recipe-based Work Order
Selects a sequence of relevant Standard Operations for a given Standard Operation-based
Work Order
Selects a relevant 3DEXPERIENCE Process (filtered or not) for a given 3DEXPERIENCE
Process-based Work Order
Creates and/or updates a multitude of database records and associates them to the given
Work Order
These records are consumed by Business Components to “execute” the Work Order
And Navigation:
Inserts quantities into initial Operations after Explosion
Moves quantities between Operations after they have been reported at an Operation (Push
Navigation)
Merges quantities in Operations into a consistent set of quantities visible to Operations by
the Tasks (Pull Navigation)
Creates and dispatches Tasks to relevant resources when modifying Operation quantities

1.2 Exploding Work Orders and Operations

There are two ways of executing determination considering the entire explosion in DELMIA
Apriso: from Standard Operation or from Local Determination.
The system first tries to invoke a Local Determination. When a Local Determination does not
exist or does not return any values, the system tries to execute the Standard Operation (the list
of Standard Operations and corresponding Local Determinations below in the table).

Standard Operation Name Local Determination Name

FLX_EXPLOSION_DETERMINATON_ORDER_ APR_EXPLOSION_ORDER_TYPE
TYPE
FLX_EXPLOSION_DETERMINATON_PROCESS APR_EXPLOSION_PROCESS
FLX_EXPLOSION_DETERMINATON_OPERATION APR_EXPLOSION_OPERATION
FLX_EXPLOSION_DETERMINATON_REVISION APR_EXPLOSION_REVISION
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 4

FLX_EXPLOSION_DETERMINATION_3DX_ APR_EXPLOSION_3DX_PROCESS
PROCESS
APR_PPR_EXPLOSION_
OPERATION
Table 1 List of standard Operations and corresponding Local Determination Functions

A work order is a request for a type of work. How this work will be performed is defined by a
design-time entity such as a Process, recipe, Standard Operation, 3DEXPERIENCE Process,
filtered 3DEXPERIENCE Process, or a combination of them all. Explosion will select and create
an instance of the relevant design-time entity by inserting a sequence of database records,
each of them relating to an important aspect of the work order (e.g. Operations, required
resources, components, etc).
A work order is either Process-based, PPR Process-based, Recipe-based, Standard-Operation
based, or 3DEXPERIENCE Process-based.
A Process-based order requires the discovery and instantiation of a process and its
contained operations,
A Recipe-based work order requires explosion to discover and instantiate a recipe and its
associated process,
A Standard-Operation based order is defined by an external ERP and downloaded through
Business Integrator. Orders and their work operations are defined by an external ERP and
then downloaded to DELMIA Apriso via Business Integrator. Explosion then explodes this
work order by analyzing its work operations through associating each one to a DELMIA
Apriso Standard Operation.
A PPR Process based order is exploded when it is downloaded from ERP (only the Header
is delivered from ERP). Based on the selected PPR Process, the Work Instructions are
created and linked to Standard Operations. The explosion is a connection of Process-based
and Standard Operation-based explosions.
A 3DEXPERIENCE Process-based order originates from an ERP utilizing the
3DEXPERIENCE platform to retrieve the process definition. The 3DEXPERIENCE platform
supports such features as process filtering or configuration, which DELMIA Apriso does not
support when an order is created. DELMIA Apriso uses the 3DEXPERIENCE platform to
employ these features.
Before exploding an order, DELMIA Apriso must determine what type of explosion to invoke
(Process based, PPR Process based, Standard Operation based or Recipe based). This
determination is made by invoking the FLX_EXPLOSION_DETERMINATION_ORDER_TYPE
Operation (or APR_EXPLOSION_ORDER _TYPE Local Determination. See Table 1 List of
standard Operations and corresponding Local Determination Functions) which contains the
“determination strategy” configuration (i.e. the type of explosion to invoke) on a work order type
& facility basis. Depending on this value, explosion proceeds differently as follows:
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 5

0. Do nothing
The order is not exploded, and explosion simply returns success. As this explosion strategy
has no implementation, it will not be discussed any more.
1. Process-based Explosion
Explosion proceeds to select (and explode) a process by gathering details from the work
order and various associated business entities and invoking the FLX_EXPLOSION_
DETERMINATION_PROCESS Operation (or APR_EXPLOSION_PROCESS Local
Determination. See Table 1 List of standard Operations and corresponding Local
Determination Functions) which returns either a process id or a process name. In the case of
the process name, the proper process revision is determined by a revision determination on
all processes with that name.
2. Standard Operation-based Explosion
For each externally defined and downloaded WIP_OPERATION record for the given work
order, explosion discovers (and explodes) a standard operation by invoking the FLX_
EXPLOSION_DETERMINATION_OPERATION Operation (or APR_EXPLOSION_
OPERATION Local Determination. See Table 1 List of standard Operations and
corresponding Local Determination Functions) which returns either an operation id or an
operation name. In the case of an operation name, the proper operation revision is
determined by a revision determination on all operations with that name.
3. Recipe-based Explosion
When selecting a recipe for a recipe-based work order, explosion selects a unique record
from the RECIPE table matching necessary criteria (review flow charts for Recipe
Discovery). If a unique recipe cannot be matched, then explosion fails with a relevant error
message. The Process used for the recipe is contained within the recipe record.
4. PPR Process-based Explosion
Explosion proceeds to select a Process downloaded from DELMIA PPR (Product, Process,
Resources) by gathering details from the work orders and invoking the FLX_EXPLOSION_
DETERMINATION_PROCESS Operation (or APR_EXPLOSION_PROCESS Local
Determination. See Table 1 List of standard Operations and corresponding Local
Determination Functions) which returns either a Process ID or a Process name. Every
Process Operation defined in PPR process is an empty Operation without any business logic
or execution context. An explosion will invoke the APR_PPR_EXPLOSION_OPERATION
Operation which returns either an Operation ID or an Operation name with an
ExecutionTemplate Input (defined and downloaded from PPR process). For more
information about PPR Process based explosion and example refer to DELMIA Plan
Approval And Distribution Integration Implementation Guide.
5. 3DEXPERIENCE Process-based Explosion
Explosion proceeds to download a process definition using data provided from ERP or by
gathering details from Local Determinations (see Table 1 List of standard Operations and
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 6

corresponding Local Determination Functions), which return DSProcessID, DSFilter, and

DSPlatformAlias. Using these columns, DELMIA Apriso requests a process plan from the
3DEXPERIENCE platform. DSProcessID and DSFilter can be used to retrieve process
details from the 3DEXPERIENCE platform specified by DSPlatformAlias and store it in
memory. DSFilter is a JSON object. Use any properties in the object that match (case
insensitive) property on the API. Finally, DELMIA Apriso creates an order based on the
process.
Whenever an Operation returns a name and not an ID, then the FLX_EXPLOSION_
DETERMINATION_REVISION (or APR_EXPLOSION_REVISION Local Determination. See
Table 1 List of standard Operations and corresponding Local Determination Functions) is
invoked to determine a strategy for figuring out the precise revision for that entity. The strategy
dictates how to isolate a revision based on the EffectiveDate and DiscontinueDate of that
revision.
Strategy 1: finds a revision of the entity such that the Work Order ReleasedDate lies within
the revision’s EffectiveDate and DiscontinueDate
Strategy 2: finds a revision of the entity such that the Work Order ExpectedStartDate lies
within the revision’s EffectiveDate and DiscontinueDate
Strategy 3: finds a revision of the entity such that current UTC time lies within the revision’s
EffectiveDate and DiscontinueDate
If the EffectiveDate is null, then the lower time boundary always matches. If the
DiscontinueDate time is null for that revision, then the upper time boundary matches.

Initial lot Navigation and initial serial Navigation are not supported.

1.3 Navigation of Quantities between Operations

Figure 1 Push Navigation

In the Push Navigation flow (Figure 1 Push Navigation), a quantity producer denotes an entity
that produced progress (usually a single Work Operation). A quantity consumer denotes an
entity that will accept the produced progress.
A quantity consumer can be a single Operation, a set of Operations, or a set of sets of
Operations. If there is cross-order sequencing defined for this Work Order, then the destination
Operations need not be in the same Work Order. If a quantity consumer is an Operation without
the NEXT sequences, then it is assumed to be a final Operation. The Work Order’s completed
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 7

quantity is then updated with the progress as well as the completed quantity for the reporting
Operation (found in the source WIP_CONTENT records).
When “push navigating” to destination Operations, WIP_CONTENT records at the destination
Operation are created to uniquely denote the source Operation from which it came. These
WIP_CONTENT records denote an “in transit” quantity, not the official quantity at that
Operation.
Pull Navigation is responsible for merging “in transit” quantity into a unique WIP_CONTENT
record (called the “good WIP_CONTENT”), which denotes the “official” quantity at that
operation.

Figure 2 Pull Navigation

For each quantity consumer to which the progress is pushed, Pull Navigation is invoked via a
workflow manager event (Figure 2 Pull Navigation). Pull Navigation merges the quantities
found in the intermediary WIP_CONTENT records of that Operation into the good WIP_
CONTENT of that Operation.
This good WIP_CONTENT is used by Tasking to dispatch Tasks for that Operation (alongside
the associated WIP_CONTENT _DETAIL records, which denote the type of quantity [product,
lot, etc.]). All of this is performed asynchronously by the Navigation Push and Navigation Pull
agents.

1.4 Tasking
Tasking decouples the “execution” aspect of a Work Operation into a separate entity called a
“Task.”
For example, when a Work Operation has quantities that must be processed, there are Tasks
which link to that Work Operation and which are available for manipulation by resources. When
a resource starts a Task from the DELMIA Apriso Portal, the user can begin executing the work
instructions of that Task (these instructions are designed in DELMIA Apriso Process Builder
through Operations and Process Operations).
Tasks provide a means for resources to interact and modify the state of a Work Operation and
(transitively) their Work Orders. In particular, Tasks provide a means for:
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 8

Concurrency – the ability for multiple resources to be working at an Operation

Function Interpreter State – when resources are executing a Task, the Function Interpreter
state for the work instructions are essentially maintained by Tasks
Quantity Management – a Task encapsulates a set of quantities from the Work Operation
(e.g., there may be separate Tasks for each different type of product at an Operation)
Automated Execution – Tasks can be executed automatically by the background Tasking
agent

1.4.1 Design-Time Configuration of Tasks

When designing a Process Operation or Standard Operation, the sections of the Operation
header below are relevant to Tasks.

Figure 3 Process Operation Properties

Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 9

Figure 4 Operation Additional Properties

1. Process Operation type: this has three values, and each value affects what will be
executing the Task.
Labor
Machine
Background
A background Operation should not invoke Business Components requiring User
Input, as no User Input is available to the agent
2. Create a Task for each: this specifies how the Tasks will be created for that Work
Operation. The options are:
Serials – creates Tasks for individual serials
Lots – creates Tasks for individual lots
Products – creates Tasks for individual products
Serials & Products – creates Tasks for individual serials, then individual products
Serials & Lots – creates Tasks for individual serials, then individual lots
Serials, Lots & Products – creates Tasks for individual serials, then individual lots, and
then individual products
Operation – creates one Task for everything
Lots & Products – creates Tasks for individual lots and then products.
3. Task dispatch rule – Code: dictates when the Tasks will actually be dispatched and made
visible to resources for production. The values are:
On any positive allocation – dispatches immediately to resources
Release on percentage – dispatches the Task to resources when the Task quantity is a
percentage of the net Work Order quantity
Release on quantity – dispatches the Task to resources when the Task quantity equals or
exceeds a specified quantity
Custom rule – deprecated
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 10

2 Jobs to Service Requests

Each action to be performed by Explosion is executed via a job. Jobs are used to move the
processing away from the user experience and into a background Process.
Order Exploder Job Handler is executed when a job of the Explosion type is to be run. The
job handler then performs order Explosion (or re-Explosion) for the specified Work Order. Initial
Navigation is then invoked directly.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 11

3 Data Model
The main tables used to create and maintain Work Orders, Work Operations, Operation
sequencing, and Tasks in DELMIA Apriso are described in the table below.

Table Name Description

COMPONENT_ Stores component instance information defined in a DELMIA 3D Work
INSTANCE Instruction and other objects.
The allocation of the components is based on the component allocation type
which is taken from COMPONENT_ ALLOCATION_TYPE.
TASK A unit of work. A Work Operation has 0 to n of these.
TASK_ Describes the quantity information for a Task. A Task has 0 to 1 of these.
MATERIAL_
USE
WIP_CHECK_ Contains links between WIP Orders, Operations or Steps and Checklists.
LIST
The information is copied from PROCESS_OPERATION_CHECK_LIST.
WIP_ Contains instances of components that are associated to a runtime entity.
COMPONENT
WIP_DATA_ Specification of data collects linked to WIP.
COLLECT
WIP_ORDER A Work Order that encapsulates an order for some type of work.
WIP_ORDER_ Maintains a parent/child relation between Work Orders. A Work Order has 0
RELATION to n of these.
WIP_ A Work Order Operation. A Work Order has 1 to n of these. Work Operations
OPERATION are ordered based on a sequence.
WIP_ Dictates the routing between Work Operations. A Work Operation has 0 to n
OPERATION_ of these.
SEQUENCE
WIP_ A Step in a Work Operation. A Work Operation has 1 to n of these (they are
OPERATION_ populated during Recipe Explosion only).
STEP
WIP_ A Step has 0 to n of these. These are copied from RECIPE_
OPERATION_ CHARACTERISTIC and/or STEP_CHARACTERISTIC.
STEP_CHAR
WIP_ A Step characteristic has 0 to n of these. They are copied from STEP_
OPERATION_ CHARACTERISTIC_ATTR.
STEP_CHAR_
ATTR
WIP_ORDER_ When the WIP Operation is of the type "first" (initial) and its
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 12

SERIAL_ NO TaskStrategyType is Serials, SerialsAndLots, SerialsAndProducts, or

SerialsLotsAndProducts, records from this table (for parent WIP Order) are
used to create Tasks separately for each Serial Number (no other Tasks are
created for that WIP Operation). This occurs when the WIP Order is
exploded and then Navigation and Tasking are performed (e.g., by calling
the NavigateOrderToFirstOperations or ExplodeWipOrder_v96 BC with the
appropriate flag).
WIP_REQ_ Contains instances of resource specifications that are required by Work
RESOURCE Operations. A Work Operation has 0 to n of these.
Resources maintain parent-child relation. The allocation of the resources is
based on the resource allocation type which is taken from RESOURCE_
ALLOCATION_TYPE.
UNIT_DOUCEMENT records linked by UnitID are copied from PROCESS_
REQ_RESOURCE.

For more information on the tables, please refer to the Database Documentation.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 13

4 High-Level Flows
This section presents examples of business transactions in a high-level flow.

4.1 Work Order Explosion

When a Work Order is downloaded from an external ERP or created from the Order Cockpit, an
Explosion Event job is created. The flow of this job is presented in Figure 5 Work Order
Explosion.

Figure 5 Work Order Explosion

4.2 Discover Process

This flow is an elaboration of the “Determine Process” from the flow in Figure 5 Work Order
Explosion and shows precisely how the Explosion Business Components invoke determination
functions in order to select an appropriate Process for a Work Order.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 14

Figure 6 Discover Process

4.3 Discover Recipe

Recipe-based orders require the discovery of a Recipe based on certain Work Order
parameters. The flow in Figure 7 Discover Recipe describes how Explosion selects a Recipe for
a Work Order.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 15

Figure 7 Discover Recipe

Select strategies:

Strategy Implementation
1 Selects active Recipes matching a Work Order’s BomNumber, resource, product,
and facility that are valid for the Work Order’s expected start date.
2 Selects active Recipes matching a Work Order’s BomNumber, resource, and
product that are valid for the Work Order’s expected start date with a NULL facility.
3 Selects active Recipes matching a Work Order’s BomNumber and product that are
valid for the Work Order’s expected start date with a NULL facility and NULL
resource.
4 Selects active Recipes matching a Work Order’s BomNumber, product, and facility
that are valid for the Work Order’s expected start date with a NULL resource.

*If a Work Order has a NULL expected start date, the current UTC time is used.

4.4 Process Order Explosion

This flow is an elaboration of the “Explode Process Order” from the flow in Figure 5 Work Order
Explosion. This flow is invoked for both Process and Recipe Work Orders.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 16

Figure 8 Process Order Explosion

4.5 Standard Operation Order Explosion

This flow is an elaboration of the “Explode Standard Operation Order” from the flow in Figure 5
Work Order Explosion. Standard Operation-based orders are Work Orders which are not bound
to a Process or Recipe, but are defined by an external ERP and then downloaded for execution
via Business Integrator.

Figure 9 Standard Operation Order Explosion

After modifying the Standard Operation for the determination, it is necessary to restart
all of the services and IIS on the server so that the Work Order Explosion's changes are
visible. There is no immediate effect, as Standard Operations are cached.

4.6 3DEXPERIENCE Process-Based Order Explosion

This flow is an elaboration of the "Explode Process Order" from the flow in Figure 5 Work Order
Explosion.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 17

Figure 10 3DEXPERIENCE Process-based Order Explosion

4.7 Operation Explosion

4.7.1 Process Operation and Standard Operation Explosion
This flow describes what occurs when a Process Operation or Standard Operation is exploded.

Figure 11 Operation Explosion

4.7.2 3DEXPERIENCE Process Operation Explosion

This flow is an elaboration of the 4.6 3DEXPERIENCE Process-Based Order Explosion. It
describes what occurs when 3DEXPERIENCE Operation is exploded.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 18

Figure 12 3DEXPERIENCE Process Operation Explosion

4.8 PPR Process Explosion

This flow is a combination of Discover Process and Discover Operation flow.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 19

Figure 13 PPR Process Explosion

4.9 Operation Step Explosion

This flow is an elaboration of the “Explode Standard Operation Order” from the flow in Figure 5
Work Order Explosion. Standard Operation-based orders are Work Orders that are not bound
to a Process or Recipe, but are defined by an external ERP and then downloaded for execution
via Business Integrator.
The following sub-sections define how the Operation’s Steps are exploded for each of the
different Explosion strategies.

4.9.1 Process Based Explosion

WIP_OPERATION_STEP à PROCESS_OPERATION_STEP or OPERATION_STEP (only
create if there is a Step characteristic available for this Step)
WIP_OPERATION_STEP_CHAR à STEP_CHARACTERISTIC
WIP_OPERATION_STEP_CHAR_ATTR à STEP_CHARACTERISTIC_ATTR

4.9.2 Recipe Based Explosion

WIP_OPERATION_STEP à PROCESS_OPERATION_STEP or OPERATION_STEP
WIP_OPERATION_STEP_CHAR à RECIPE_CHARACTERISTIC
WIP_OPERATION_STEP_CHAR_ATTR à nothing

4.9.3 Standard Operation Based Explosion

WIP_OPERATION_STEP à OPERATION_STEP (only create if there is a Step
characteristic available for this Step)
WIP_OPERATION_STEP_CHAR à STEP_CHARACTERISTIC
WIP_OPERATION_STEP_CHAR_ATTR à STEP_CHARACTERISTIC_ATTR
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 20

4.9.4 3DEXPERIENCE Based Explosion

Figure 14 3DEXPERIENCE Based Explosion

4.10 Component Explosion

The basic terms used in this section are explained in this table:

Term Description Location in DB

IssueQ The quantity of the component required WIP_
[Link]
OrderQ The order quantity in the standard product WIP_ORDER.OrderQuantity
UOM
StdBatch The standard batch size of the product PRODUCT_
being produced [Link] of
the product being produced
BomQ The quantity of the BOM component [Link]
CompScrap% The standard scrap percentage of the BOM [Link]
component
Shrink% The standard shrinkage of the product PRODUCT_
being produced or the shrinkage of the [Link] of
entity the BOM component was associated the product being produced or
to, i.e., the PRODUCT, PROCESS, WORK_LOAD.ShrinkRate
PROCESS_OPERATION, PROCESS_
OPERATION_STEP, OPERATION, or
OPERATION_STEP
Component The quantity on the standard BOM [Link]
Quantity
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 21

Components are linked at various levels. They can be linked by:

Products as defined in PRODUCT_COMPONENT
Processes as defined in PROCESS_COMPONENT
Process Operations as defined in PROCESS_COMPONENT
Standard Operations as defined in OPERATION_COMPONENT
Process Operation Steps as defined in PROCESS_COMPONENT
Standard Operation Steps as defined in OPERATION_COMPONENT
Recipes as defined in RECIPE_COMPONENT
A component Explosion’s job is to explode the components linked to by those above tables
(and which are relevant to the Work Order) into the WIP_COMPONENT table, and to issue the
correct number of quantities for each exploded component.
Components are only exploded if their effective and discontinue dates are valid for the order
being exploded.
When components are exploded from the PROCESS_COMPONENT, PRODUCT_
COMPONENT, or RECIPE_COMPONENT table to the WIP_COMPONENT table, the effective
date of each is validated based on the WIP_ORDER.ScheduledStartDate.
When components are exploded from the PROCESS_COMPONENT table to the WIP_
COMPONENT table, any COMPONENT_INSTANCE is also cloned with the COMPONENT.
The validation is:

[Link] < WIP_ORDER.ScheduledStartDate

and
[Link] > WIP_ORDER.ScheduledStartDate

If both of the above conditions are true for an individual component, it is processed during the
Explosion.
If the scheduled date is not supplied for a given component (in the WIP_ORDER table), then
the current time in the UTC standard is used.

Figure 15 Component Explosion

Calculating the issued quantity of the components is based on the following logic:
1. The first thing that is validated is the usage type of the component being exploded, and the
usage type affects the quantity in the following ways:
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 22

Usage Type Description Effect

1 Regular None
2 Active ingredient None
3 Compensating ingredient None
4 Non-compensating ingredient None
5 Constant ingredient IssueQ = component quantity
6 Variable by-product None
7 Constant by-product IssueQ = component quantity
8 Variable co-product None
9 Constant co-product IssueQ = component quantity
10 Incidental None

2. If the effect of the usage type is "None,” then the issue type of the component is validated as
such:

Issue Type Description Effect

1 Consume Use consume formula
2 Produce Use produce formula

The consume and produce formulas are defined as follows:

The consume formula:

where

The produce formula:

3. The derivation of the data used within the formulas is described in this table:
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 23

Component Uses Uses Shrink Rate from Product

Is Attached Product Allows
to Information Fraction
Standard
Batch
Process Yes [Link] record is available, otherwise Uses
Product Information for WIP Order product component
product
Process Yes [Link] record is available, Uses
Operation otherwise Product Information for WIP Order component
product product
Process Yes [Link] record is Uses
Operation available, otherwise Product Information for WIP component
Step Order product product
(without
Recipe)
Process Yes [Link] record is Uses
Operation available, otherwise Product Information for WIP component
Step Order product product
(with
Recipe)
Standard Yes [Link] record is available, otherwise Uses
Operation Product Information for WIP Order product component
product
(Explosion
types 1 and
2)
Standard Yes [Link] record is available, otherwise Uses
Operation Product Information for WIP Order product component
Step product
(with
Recipe)
Standard Yes [Link] record is available, Uses
Operation otherwise Product Information for WIP Order component
Step product product
(without
Recipe)
Product Yes WIP Order [Link] record is available, Uses
otherwise Product Information for WIP Order component
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 24

product product

4. The issue quantity is calculated as above, and the system determines if fractions are
allowed. This processing is done regardless of the usage type, and will be performed on the
issue quantity as such:
When IssueType is Consume, and if Allow Fraction is false for the component, then
IssueQ will be rounded up to the nearest integer
When IssueType is Produce, and if Allow Fraction is false for the component, then IssueQ
will be rounded down to the nearest integer

4.11 Required Resource Explosion

Required resources are linked at various levels. They can be linked to Processes, Process
Operations, Standard Operations, and Steps. When exploding these entities, if they contain
required resources, then those required resources are exploded in the WIP_REQ_RESOURCE
table. Both primary and secondary resources are exploded.
Processes, Process Operations, and Process Operation Steps define their required resources
in the PROCESS_REQ_RESOURCE table. Standard Operations and Standard Operation
steps define their required resources in the OPERATION_REQ_RESOURCE table.
The flow In Figure 16 Resource Explosion shows how resource Explosion works in general.

Figure 16 Resource Explosion

WIP_REQ_RESOURCE records are created based on PROCESS_REQ_RESOURCE records

according to the following rules:
Resources at the Process level are exploded to the WIP_ORDER record to which it is
associated
Resources at the Operation level are exploded to the WIP_OPERATION record to which it is
associated
Resources at the Step level are exploded to the WIP_OPERATION_STEP record to which it
is associated
WIP_REQ_RESOURCES are used by the DELMIA Apriso Portal to know whether or not to
display a Task to a certain employee. For example, if an Operation requires a type of resource
matching ten employees, then those then will see Tasks for that Operation in their lists.

If WIP_REQ_RESOURCE.ExternalSource is set to "1" (true), then WIP_REQ_

RESOURCE fields will not be deleted during re-Explosion.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 25

4.12 Cross Order Explosion

When a Work Order has made a child of another Work Order, then cross-Explosion is invoked
in order to merge any Operation routings between the parent/child orders (the entire tree is
considered).

Figure 17 Cross-order Explosion

4.13 Push Navigation

Navigation consists of two phases. The first is the Push phase, which moves quantities from a
source Operation to its destination Operations via the Operation routing. The end result of the
Push phase is simply that the quantity has been transferred to the destination Operations’ WIP_
CONTENT and WIP_CONTENT_DETAIL records.

Figure 18 Push Navigation

4.14 Pull Navigation

The Pull phase of Navigation is the second and final phase. It is concerned with examining all of
the quantities which were pushed, and then creating Tasks for them in the correct way.

Figure 19 Pull Navigation

Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 26

4.15 Extension Points for 3DEXPERIENCE Process-Based

Order Explosion
Extension points help to create a custom revision and implement a custom business logic. A
default extension point revision is called by 3DEXPERIENCE Process-based Order Explosion.
By default, these extension points are not called.
The list of supported extension points:
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
Before in extension point name means it is used before creating data in DELMIA Apriso. After
in extension point name means it is used after creating data in explosion for a currently
processed identity.
Create extension points create data that can be shared with multiple WIP Orders (for example,
NOTICE). Link extension points create a link between shared master data and WIP Orders (for
example, WIP_NOTICE).

Example

[Link] is called after creating WIP_NOTICE record. WIP_

NOTICE links NOTICE to WIP_OPERATION or WIP_OPERATION_STEP. If
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 27

StepSequenceNo equals 0, the extension point is called for WIP_OPERATION. If

StepSequenceNo is populated, the extension point is called for WIP_OPERATION_STEP.
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 28

5 Troubleshooting
Operations and Other Entities Missing After Order Explosion
Errors are logged in the AprisoSchedulingService_ErrorRolling.log file located in
<drive>\Temp\AprisoLogs on the DELMIA Apriso server. Review the latest error messages to
determine the failure.

Quantities Not Being Navigated to the Destination Operation After Reporting

Production
To identify the cause, try the following:
In Order Cockpit, review the source Operation quantity
If it is not zero, then the problem may be that the Operation sequencing does not navigate
quantity for the reported class/reason code
Validate the Operation sequencing, then retry
Check the log files for the application that executed Report Production and validate that the
Report Production BC was successfully executed
Since Navigation is a background business transaction, it can only be invoked if Report
Production succeeded
If it did not succeed, fix the errors that lead Report Production to fail and retry
Review the errors that are logged in the AprisoSchedulingService_ErrorRolling.log file
located in <drive>\Temp\AprisoLogs on the DELMIA Apriso server
Review the latest error messages to determine the failure
Explosion, Navigation and Tasking | DELMIA Apriso 2023 Implementation Guide 29

6 Documentation Availability
All DELMIA Apriso documentation is available from <server name>/apriso/start and at 3DS
Support.
For more information, refer to the 3DS Support Knowledge Base.