Scribd
Upload
1K views2 pages

Available DELMIA Apriso Entities

DELMIA Apriso divides manufacturing processes into a hierarchy of entities including processes, process operations, standard operations, steps, functions, inputs, and outputs. Processes are made up of operations which are broken down into steps that contain functions with inputs and outputs. Standard operations are reusable while process operations are not. Screens, layouts and views enable managing screen flows and displaying updated user interfaces in DELMIA Apriso.

Uploaded by

Anil Kesana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views2 pages

Available DELMIA Apriso Entities

DELMIA Apriso divides manufacturing processes into a hierarchy of entities including processes, process operations, standard operations, steps, functions, inputs, and outputs. Processes are made up of operations which are broken down into steps that contain functions with inputs and outputs. Standard operations are reusable while process operations are not. Screens, layouts and views enable managing screen flows and displaying updated user interfaces in DELMIA Apriso.

Uploaded by

Anil Kesana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

7/18/2018 Available Apriso Entities

Available DELMIA Apriso Entities


Like the real-life processes they represent, each Process in Process Builder can be broken down into a sequence of
activities, executed by an agent (human or machine), which consume resources and produce an output. DELMIA Apriso
has divided Processes into a hierarchy of entities.

Process
A Process is the entity at the top of the Process model, executed when there is a task initiated in DELMIA Apriso. It is a
collection of Process Operations, Standard Operations, Resources, and Materials with links to Specifications.

Process Operation
A Process Operation is the child entity of a Process. It is the unit of manufacturing that is to be performed at a Work Center
by Resources that consume Materials. It is usually one task performed by one person in one place at one time. It is a
collection of Steps, Resources, and Materials with links to Specifications. Process Operations are not reusable.

Standard Operation
A Standard Operation is a standalone entity with the same structure as a Process Operation. Standard Operations may be
consumed by Processes or invoked independently (e.g., called with a button in the Portal). It is a collection of Steps,
required Resources, and Materials with links to Specifications. Standard Operations are reusable.

Step
A Step is the child entity of a Process Operation or Standard Operation. It is a work instruction with a collection of
Functions, Resources, and Materials with links to Specifications and Sample Plans. Steps are not reusable, but they may
be copied.

Function
A Function is the child entity of a Step contained in a Process Operation or Standard Operation. It provides the ability to
create and use business logic, and it constitutes a collection of Inputs and Outputs (linked to business logic) that perform
specific business functions. They may be used to perform data collection, data transformation, control Step navigation,
invoke business logic, and more.

Input
An Input is the child entity of a Function. It incorporates the data received by a Function to be used when processing the
Function's logic.

Output
An Output is the child entity of a Function. It incorporates data sent by a Function to be used further down the Process
Flow.

http://hjvmmesapp.kpit.com/Apriso/Help/en-us/ProcessBuilder/index.htm#t=Available_Entities.htm 1/2
7/18/2018 Available Apriso Entities

Screens, Layouts, and Views


Functionality enabling Managing Screen Flows
Displaying up-to-date UI in DELMIA Apriso requires the use of several Sub Operations (e.g., Header, Context, and Footer).
Dividing the UI per Sub Operation is a good practice, as it allows for reusing the parts that are common between the
different screens (e.g., the Header or Footer).
This approach is the basic concept for Screen Flows. Please note that each Screen in a Screen Flow consists of:
A list of Views that will be displayed in the Screen
Definitions of the positions and sizes of the Panels on which Views will be linked (which are called Layouts)
Definitions of Views, Layouts, and Screens are the only elements responsible for how the end-user UI is displayed.
For details, go to Managing Screen Flows section.

http://hjvmmesapp.kpit.com/Apriso/Help/en-us/ProcessBuilder/index.htm#t=Available_Entities.htm 2/2

You might also like