Posts Tagged ‘Revision & Version’

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

June 4, 2012

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’.


Information Release and Data Vault Management in Aras

April 20, 2012

MarcL: When a document or any other type of data is formally released through the PLM solution, the vault must then recognize the file as released as a result of the workflow completion, and provide appropriate control of the document. This should also set the release baseline, and do notification of the change to the designated access group.

Peter Schroer:

The Aras Innovator platform’s Lifecycle and Workflow services are normally used together to coordinate the Enterprise Change and Release processes.

Lifecycle ensures that baselines of configurations are created and frozen (against future changes), and Lifecycle drives the automatic changes in access control rights that your company will need for release processes.

Notifications are handled by Lifecycle (one-way distribution list) and Workflow (certified response required) as required.

The default process templates with the downloaded version of Aras Innovator are the CMII standard processes.

These can of course be modified by your company, and we provide training so you can customize these processes yourself.

For more info on this see posts like ‘Version & Revision Release Levels in Aras’ or check out the Posts Tagged ‘Revision & Version’.

Versioning of Items & Files in Aras

April 19, 2012

MarcL: PLM solutions at a minimum should provide Version tracking for the most recent released revision and previous revs with date/time stamps. A new version should be based on an update of the PLM database which should occur whenever an item is checked into the PLM solution, and also should occur when the user initiates an update, but typically does not need to coincide with the user saving changes on their local disk.

Peter Schroer:

Aras internally used the terms Major_Rev, Minor_Rev and Generation.

The “Version” and “Revision” are just labels that do not impact the underlying web services behaviors.  In our experience, everyone calls it something different;  it’s the defined behaviors that are important. 

CMII revision behaviors are supported by the standard out-of-the-box Aras configuration.

All edits, whether work-in-process or formal releases are tracked in Aras Innovator (these are the Generations), and your company decides which of the increments are exposed to which users.

Once a File is checked-out,   a Generation is reserved,    and that user can make multiple edits which are saved to disk without bumping the Generation.

This Generation behavior is configurable and for security intensive scenarios can be set-up to log every save, but the default settings allow local saves that are not recognized by the PLM system.

For more info on this see posts like ‘Version & Revision Release Levels in Aras’ and ‘Data Relationships and Fixed / Float Rules in Aras

Or check out the Posts Tagged ‘Revision & Version’.

Released Data, Baselines and Single “View” of the Truth in Aras

April 18, 2012

MarcL: PLM solutions should ensure that all users receive the latest version of any item managed which requires the solution to track all changes to the item as well as formal releases of final changes.    PLM solutions should also be able to provide a snapshot of data states and associated object release levels for specific user-defined release levels of an Item.

Peter Schroer:

The underlying architecture of Aras Innovator preserves “baselines” of configurations automatically as data is changed;  both Work-In-Process (WIP) editing and the release events.

Your company can then define which of these Baselines you want to expose, by default in the CMII model, the ECN Workflow automatically creates the configuration baseline.

If you would like to create named snapshots, you can tailor the rules to allow exposing the underlying “baselines” as required, and applying a name to the selected configuration.  All WIP and Release changes are tracked by default, this is Aras’s out-of-the-box configuration.

User permissions and profiles determine whether the user sees    the latest version,    the latest released version,     the latest version released in his / her location (may not be the “latest” revision), etc.

At Aras we recognize that in a globally distributed company, the single version of the truth, may have different “viewpoints” (single view of the truth) depending on the user’s context.

All of these views are supported, in addition to the classic CMII-style of configuration management which is the out-of-the-box set up.

Version & Revision Release Levels in Aras

April 17, 2012

MarcL: PLM solutions must provide support for user-defined multiple release and revision levels, and should be able to assign default release levels based on object types or other attributes, as well as, be able to reset release levels for specific items at check-in by users with appropriate assigned authority.

Peter Schroer:

The out-of-the-box Aras Innovator data model has 3 levels of versioning control on all business items (Major, Minor, and Generation).

Your company can use the three levels to implement just Revisions, or      Revisions + Versions, or    Versions + Revisions + Baselines,    etc.

The exact terminology belongs to you / your company, and you can make it whatever you need. The underlying platform handles the 3 revision levels, and you can use the OOTB setup or configure them however you need.

Our out-of-the-box installation implements the standard CMII processes as defined by the Institute of Configuration Management.

Out-of-the-box Aras supports the ability to assign default release levels based on object types or other attributes as well as the ability to reset release levels for specific items at check-in, and this is easily extended or modified over time as needed.

Each ItemType is linked to a defined Revision sequence (and these can be different for different ItemTypes),  and the standard methodology would be to use the Lifecycle engine to trigger revision changes.  This behavior is driven by CMII standards in the OOTB Aras solutions, and can be easily tailored as needed or applied to add-on solutions or custom solutions that your company develops.

You can quickly enable special scenarios for manual revision changes, over-rides, executive decisions, and other behaviors which occur in the real world – or any combination of these.

Learning how to configure the revisioning rules is covered in the Aras introductory class “Configuring Solutions”, and we provide training on how to customize Aras Innovator for self-sufficient operation to satisfy your company’s on-going requirements.

Document & File Management Check-in / Check-out, Lifecycle and Security in Aras

April 10, 2012

MarcL: PLM solutions must be able to store, manage, archive, and retrieve digital data at the file level. PLM should enable check-in / check-out which are authorized by the security schemes, and should also allow checkouts to be cancelled if needed. Please describe how this is supported.

Peter Schroer:

Check-in / Check-out and Security

Any digital data in file form can be vaulted and managed by the Aras Innovator vault server, and out-of-the-box Aras supports Check-in and Check-out according to established / authorized security permissions.

All actions and data are controlled by platform-level rights management infrastructure in Aras Innovator for document & file management.

Check-outs can be cancelled by the end-user or an Administrator can override a check-out by clearing the reservation flag.  Additional capabilities can be easily added if needed.

Also, the Aras Innovator security model enforces update and delete actions (CRUD) by user by business object providing the ability for approved users with appropriate security credentials to make changes / delete any incorrect data in the vault as required which further simplifies administration while ensuring that security is enforced.

Lifecycles and Security

The Aras Innovator Lifecycle web service is often used to implement access controls that are based on Status.

Lifecycle status security is a default behavior of Aras solutions.

As business items / objects move through a lifecycle,  the access rights are modified automatically to patterns (sets of permissions for users/roles/groups) appropriate for that state in the lifecycle.

The permission structures and user access can be configured to support multiple, simultaneous company-specific security control structures for work-in-process business items and files.

You can set-up, administer and modify/customize these capabilities yourself and we’ll train you how.

Item Number Generation and Cross Referencing in Aras

April 6, 2012

MarcL: PLM solutions must support the assignment of new numbers, and it should be possible to have the system assign automatically the next available number based on rules. Many companies also need multiple numbering of the same information such as part #s, doc #s, spec #s, equipment #s and other identifying numbers, as well as, provide cross-references and allow data to be retrieved by any number that is applicable to it. For example, users should be able to enter a supplier part number and find the internal id number and access the record/document itself.

Peter Schroer:

PLM Software Item Numbering

Item Numbering in PLM

You are able to modify the business object definitions to create multiple searchable identifiers (internal part number, supplier part number, SKU, old legacy number, etc) and all of these numbers are available for searching and cross reference.

The Aras Innovator platform includes a rules-based identifier creation service (we call Sequences).   Sequences are used for unique identifiers on any object such as part numbers, document numbers, supplier IDs, corrective action IDs, ECR #s, etc.

You can combine the automatic Sequence generator with business object-specific attributes such as classification, part family, lifecycle state, etc. to create intelligent numbering schemes.

A typical example would be a prefix based on classification followed by 6 digits from a sequence, followed by a Suffix based on part family.

You can also pull numbers from other systems, such as getting new part numbers from the ERP environment like SAP or generating document numbers from an existing PDM system like Teamcenter or Windchill.

And of course you can do manual entry of numbering as well.

With Aras Innovator you can combine all of these approaches for different aspects of the system and different processes.

You might have Part numbers come from different sources depending on the Part’s classification, organization, etc.

Mechanical part numbers at the Aerospace division come from Teamcenter, whereas mech part #s in the Oil & Gas division are pulled from Windchill and the Industrial group uses the Aras Sequences services with specific dash (-) designations. And then maybe all Supplier IDs are generated in SAP.

Or you could just use our OOTB numbering for all of these different Items.    It’s up to you and it’s not hard.  We provide training on how to set-up, administer and modify these capabilities yourself.

Image from Banner

Ability for Items to Exists without a Permanent Object Identifier in Aras

April 3, 2012

MarcL: PLM solutions must be able to substantiate an object in a preliminary form… IOW, objects must be allowed to exist without assigning a permanent object identifier. How does Aras handle this?

Peter Schroer:

Aras Innovator supports this scenario with standard out-of-the-box functionality.   OOTB we use the CMII rules for configuration & change management.

All Items / objects move through a lifecycle, and the rules about numbering / naming, which fields are required, what actions are valid, etc changes naturally over the lifecycle.  These rules are fully customizable as well.

It’s normal for a CAD model to be named “My Bracket” for the first few revisions, and not re-identified to a formal part number until much later in the innovation / development process.

When items are re-identified, this does not impact the configurations they are linked to.  Aras Innovator uses an internal identifier (not end user visible) to maintain configuration structures.

%d bloggers like this: