Using PLM Change Control Workflows to Manage the PLM System’s Own Definition in Aras

MarcL: The PLM solution should be able to have workflows managed by the system itself as objects that can be placed under change control and can be assigned versions.

Peter Schroer:

Aras Innovator’s Workflow Maps (e.g. Aras term for the business process definition) are Item Types (e.g. business object) in the PLM system.

As such they have permissions, versions, and can be controlled by their own change approval workflow.   In this way, the PLM is used to control its own internal system definition of processes.

This style of change management for the PLM system can also be applied to Forms, Lifecycles, business rules, etc.

NOTE:  while Aras can be used to control its own system/process definition,  and changes can be made in real-time by real-people,  this is not the recommended best practice after the system Go-Live to production.

At one point in the evolution of a PLM deployment the end-users are thrilled that PLM change requests (add a field, change the form, etc) are made in real-time as fast as they ask for the changes.

Later though, if the form layout continues to change in real-time when they are using the system,  the video arcade effect of the moving buttons will affect productivity.

The recommended best practice after Go-Live is to instantiate three instances of the PLM solution;  Development, Test, and Production.

All model changes made using the Solution Studio drag-and-drop design tools, can be exported as XML Packages, and easily moved between Aras Innovator instances (this is also how we synchronize federated networks of separate Aras Innovator instances).

Normal practice is to move multiple Packages from development to Test for integration testing, and then at defined intervals, move the tested Packages into the Production environment for rollout.

We provide training on how to tailor, customize and manage Aras Innovator’s workflows and business items.

For additional information see ‘PLM Solution Tailoring and Customization by End Users in Aras’ and ‘Electronic Signatures, Workflows, Lifecycles and Security in Aras’.


Tags: , , , , , , , , , , , , ,

what's your take?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: