Posts Tagged ‘numbering’

PLM Product Structure Management Functionality in Aras

October 30, 2012

MarcL: PLM should provide product structure functions including:

• Assign specific part numbers to parts & assemblies

• Modify structures by adding phantom assemblies

• Modify structures by adding part numbers from raw materials, suppliers, customers and other sources

• Add revision level part numbers to control configurations

• Modifying coordinates and orientation of components

• Making mass component replacements

Peter Schroer:

All of the PLM functionality in the bulleted list is available in the standard Aras Innovator solution Out-Of-The-Box (OOTB).

Depending on the configuration management methodology and rules implemented (CMII or other) some companies require an automatic Engineering Change generated for all parent assemblies affected by a mass change, while others allow changes without formal approval processes.

If the “components” in the your company’s use case are purchased components, then Aras Innovator has an included best practice that allows mass change of a purchased component, without use of an Engineering Change.

In this case you would use the Aras default OOTB data model which separates your company’s internal part object from the purchased components using the Approved Manufacturers List (AML) relationship model. This is straightforward for your end users.

If your company needs a different use case for making mass change, then the Aras structure management functionality can be adapted to your specific requirements.

We provide training on how to use, administer and customize Aras Innovator’s structure management capabilities including part / item numbering.

For more see previous post ‘Item Number Generation and Cross Referencing in Aras’ and for additional information see Posts Tagged ‘Configuration Management’ and ‘Product Structure’.

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.

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


%d bloggers like this: