Skip to content
Fieldnode Help Center home
Fieldnode Help Center home

2.6 Part Versions

https://www.youtube.com/watch?v=Coztp_8mSlk

Objective

To provide a clear and concise step-by-step guide for team members to create a new version of a product efficiently and accurately, minimizing misunderstandings and errors

Key Steps

  1. Navigate to Product Versions Tab

    • Access the product you wish to create a new version for by selecting the "Product Versions" tab

  2. Initiate Version Creation

    • Click the Create Version button (blue button)

  3. Input Version Details

    • Add suffixes for the product title and product ID. to differentiate the new version from the original

  4. Add Description

    • Provide a brief description of the new version

  5. Enter Manufacturing Data

    • Select the manufacturing process (e.g., Material Extrusion)

    • Choose the material type (e.g., Polymer)

    • Select the applicable standard (e.g., API 20T)

    • Assign a criticality level (e.g., Criticality 1)

  6. Upload Relevant Files

    • Attach any necessary files related to the new version using the designated upload method

  7. Alternative Version Creation Method

    • If sending the part for RFQ (Request for Quotation), be aware that a new version may be created automatically if the manufacturer suggests changes to the scope of work or inspection/test plan during negotiations

  8. Finalize Version Creation

    • Review all entered information for accuracy

    • Click Create and Publish to finalize the new version

  9. Verify New Version

    • Return to the product overview and click on View to see the details of the new version

    • Click on the version name to access the specific details of that version

Cautionary Notes

  • Ensure that all inputs are accurate before clicking Create and Publish, as errors may lead to confusion in future product management

  • Always check for existing versions to avoid duplication of effort

Tips for Efficiency

  • Familiarize yourself with the product's existing versions and their details before creating a new one to ensure clarity in naming and descriptions

  • Use a consistent naming convention for suffixes to make version tracking easier