Parts list

Definition

As a first step in developing the Project, the Parts List should be compiled from the existing information on parts and assemblies, containing all tangible and functional components that can contribute to the cost of the Project. The components may be numbered in the form of a Simple Parts List or contain layers of hierarchy, in which case it is a Structured Parts List.

Lineamientos

Here are some guidelines to keep in mind when developing the Part List:

'Simple parts list'

]]

<'Structured parts list'

]]

• A simple Parts List is used when, in the assembly or equipment, none of its components can be disassembled or broken down into more basic parts.
• A Structured Parts List is used when, in the assembly or equipment, any of its components can be disassembled or decomposed into more basic parts.

• For each level of hierarchy, use Arabic numerals, cardinal numbers, and in ascending order 1, 2, 3...
• Always try to list the most important parts or assemblies first, according to criteria such as function, cost, size, and so on.
• The Parts List should contain the following columns (column names should be exactly as indicated):
  • POS -> This is the number assigned to the part or assembly.
  • POS. OLD -> If you have previous drawings of the assembly or equipment, it corresponds to the number assigned in these.
  • QTY -> It is the total quantity required for the part or assembly within the complete assembly or equipment.
    • The use of whole quantities is preferred, e.g. for two lengths of cable 1.5 meters each, the name would be '1.5 m cable', and the quantity 2.
  • PART NAME -> The unique name assigned to the part or assembly.
    • It must be free from redundancies.
    • It must be related to functionality.
    • Must not include detailed technical specifications.
    • If necessary, it may include a suffix number for duplicate names.
  • PART CODE-> Currently, the POS field is used to replenish this column.
  • PART TYPE -> It is a classifier that applies to parts, not to assemblies, it can acquire the following values:
    • Production -> for manufactured parts or parts that undergo a modification or shaping process.
    • Standard -> for standardized or catalog parts, such as screws, connectors, standardized electrical components, among others.
    • Buy -> for purchased and non-standardized parts, which must be acquired for the project.
  • SPECIFICATIONS -> For parts, the information necessary for their manufacture or purchase must be indicated:
    • For fabricated parts, indicate material, surface treatment, special manufacturing processes (if applicable).
    • For standard parts, indicate DIN designation or similar information.
    • For purchased parts, please indicate information such as technical data, supplier, order number, website.
• Names of parts, assemblies, specifications, and other technical information must be in English.
• At the beginning of the Parts List, the following lines must be included:
  • One or more lines for the project overview pages, which includes all sub-assemblies or assemblies.
    • It is identified in the POS field with the letter A.
    • If more than one page is required to display the entire project, these are identified with a sequential number: A1, A2....
    • In the case of several lines, these can be summarised in a single row identified as A.
    • Includes a explosion view of the Project.
  • One or more lines for the Parts List pages.
    • It is identified in the POS field with the letter B.
    • If more than one page is required to display the entire part list, they are identified by a sequential number: B1, B2....
    • In case of several lines, these can be summarised in a single row identified as B.
• For validation in OHO, the developer must deliver The Parts List in CSV format, UTF8 encoded.
  • The CSV file name is unique, must be in lower case, and must be composed of:
    • Organisation abbreviation, e.g. oseg for Open Source Ecology.
    • Underscore separator '_'
    • Project abbreviation, e.g. sp for Screw Press
    • Underscore separator '_' *** Project name without spaces, e.g. sp for [ Screw Press
    • Project name without spaces, example screw-press
  • Complete example for the name: oseg_sp_screw-press.