MarcL: PLM solutions must support the ability to define multiple change procedures with different flows, timing constraints and voting rules, and the same process(es) should be able to be used for both part-centric and document-centric change processes. PLM solutions should also be able to model and execute multiple-step work processes at multiple levels (parent-child processes).
Peter Schroer:
This requirement is exactly the reason that Aras has created a general-purpose BPM (business process management) service instead of a hard-coded engineering change workflow module.
It is also the reason why Aras has a separation between Lifecycle and Workflow where Lifecycle is about “State” management (i.e. a Part is In Draft, In Review, Released, etc) and Workflow is about “Process” management (i.e. routing a Form with attached Items & Files around for activities).
It is quite typical for companies to have common Lifecycles for Parts. These can be a single standard Lifecycle or different Lifecycles based on Classification, such as Mechanical having a different Lifecycle than Electrical which is different than Software/Firmware, etc.
The Workflow process map for any specific Part might be completely different. These differences can be driven by the different business units, the Classification of the Parts, the complexity or risk level of the Change, etc.
A typical large company running Aras will have a dozen Lifecycle definitions (parts, documents, tools, specifications, etc.), and then many dozens of Workflow Process definitions for controlling those Lifecycles. In this way, Aras is able to model the real-world business practices without compromise.

Aras Workflow Process Studio Provides Customization through Modeling and Powerful Web Services Integration Capabilities
The Aras Workflow service supports multi-step processes, with combinations of serial and parallel activities, branching based on business rules, and automatic escalation to ensure that every workflow instance that is started will be closed-loop.
Workflows are inherently hierarchical, and can be organized into libraries of Sub-Workflows that are initiated at a certain step in the Parent workflow. This also means they can easily be re-used.
Workflows can be executed by people and other systems as well as a combination of both.
The Aras Workflow service can be used in conjunction with other systems that have BPM or Workflow capabilities like SAP, Oracle, Teamcenter, Windchill, etc or any of the BPM-specific systems and can be either Parent or Sub-Workflow in conjunction with the other system’s Workflow. It’s a Web service.
We provide training on how to implement, customize, integrate and optimize the use of these Aras Innovator workflow process capabilities.
For additional information on workflow see the previous post ‘Lifecycle, Workflow and Other Types of Process Management in Aras’ or check out the Posts Tagged ‘Workflow’.
Like this:
Like Loading...