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:
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
Tags: classification, configuration management, customize, Federation, Integration, Items, Lifecycle, numbering, Objects, platform, Revision & Version, Web services
April 6, 2012 at 11:11 pm |
The identification discussion is always fascinating. In my view, identification is a predecessor of classification schemas. So, why need to build codes? I think we need to use classification schemas instead of. Here are some thoughts and discussion about the topic. The comments are the most interesting piece, btw.
Part Numbers and External classification schemas
http://beyondplm.com/2012/02/07/part-numbers-and-external-classification-schemas/
PLM, Data indentifications and part numbers
http://plmtwine.com/2010/04/09/plm-data-identification-and-part-numbers/
Simplicity wins. So, whatever, complicated rules you create it will not keep for long time and will require re-formatting. What is your take on this?
Just my opinion and thoughts…
Best, Oleg
April 18, 2012 at 6:15 am |
Just thought I’d mention that CycleOp has developed a dynamic add-on for part numbering in Aras, which takes any number of attributes and concatenates them in the order needed, to generate a perfect nomenclature of values. Call or visit us at http://www.cycleop.com.
October 30, 2012 at 5:45 pm |
[…] more see previous post ‘Item Number Generation and Cross Referencing in Aras’ and for additional information see Posts Tagged ‘Configuration Management’ and ‘Product […]
January 12, 2013 at 3:20 am |
How to manage Controlled Relationship in Aras (differentiate between specific requirements having specific functions).