Posts Tagged ‘Files’

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

Advertisements

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

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.

Multiple Files for a Single Document and Referencing Hard Copy Documents in Aras

April 11, 2012

MarcL: PLM solutions should make it possible to link multiple files to various versions of a managed object so they may be managed, checked-in/out or reported on as unit including view versions (PDFs, docx, CAD, etc.) as appropriate with mark-ups.

And if a company continues to maintain some documents in paper formats or off-site on digital back up, then the indexing capabilities of the PLM solution should be able to reference that data.

Data collections or packages of managed files should be able to be created and referred by a common name or number, and should support folders containing or referencing other folders.

Please describe how this is supported.

Peter Schroer:

Multiple Files for 1 Document Item

One-to-Many relationships from business objects (Document, Part, Folder, etc) to File are standard out-of-the-box in Aras Innovator.

A common example of a use case for this data model rule is allowing a native CAD file and one or more viewable formats of that CAD file to be controlled as a single record.

This OOTB capability is extensible in Aras and can be easily customized to accommodate special circumstances at your company.

aras-plm-document-with-multiple-files

Screenshot Example of an Aras Document Item with Multiple Files Associated

Referencing Hard Copy Data

Often a company continues to maintain some documents and other related data in paper form or off-site in archive (like Iron Mountain) or in digital back-up format, and you need the PLM environment to account for these by indexing and referencing that data.

Out-of-the-box Document Management in Aras allows document control records to exist and be managed through lifecycles without physical files attached.

As a convenience to your end users, you could even add an attribute to the data model to specify the location of the paper drawings (Level effort to add this field is < 1 hour).

Using Folders for Files

The Aras Innovator platform has a Folder item out-of-the-box which is used to group documents, specifications, parts, tooling, etc. that are affected by a single enterprise change order.

If your company wants a more general Folder-style management of documents, then a “Folder” Item can easily be added and used for a wide variety of purposes.

Your Folder item naturally inherits all of the Aras Innovator core platform services and can have security permissions, business rules, lifecycles, workflow routings, etc. applied to them.


%d bloggers like this: