All Collections
Technical Documentation
Update of models in Makersite
Update of models in Makersite

versions, BOM update, model change

Team Makersite avatar
Written by Team Makersite
Updated over a week ago

Status:

The BOM in the system is uploaded and mapped to datasets.

The different scenarios describe different cases for file uploads and how Makersite responds.

Scenario 1 Reupload

Case: The file is unchanged from the last upload:

Result: The model in Makersite remains unchanged. In the import window, the existing mappings are shown.

Scenario 2: Create a new dataset.

Case:

  • The name, part number, and composition differentiate from the original uploaded BOM.

Result:

  • A new product model is set up in Makersite.

Scenario 3 Update the existing BOM. (Change overwrite existing properties)

Case:

  • The part number (or the name, another property) of the main part (level 0) of your BOM has changed.

  • The original BOM was copied, and the file has a new name.

Result:

  • The existing dataset in Makersite is updated.

  • The existing part number is overwritten with the new one.

  • Additionally, a new folder in my drive is generated.

  • Both folders (for the original and the new upload) contain the same information.

Scenario 4 Update the existing BOM (Change overwrite existing properties)

Case:

  • The part number (or the name, another property) of the main part (level 0) of your BOM has changed.

  • The file name was not changed.

Result:

  • The existing dataset in Makersite is updated.

  • The existing part number is overwritten with the new one.

  • No second folder is generated.

Scenario 5 Creation of a new part with the same material composition.

Example: Two screws have the same weight and composition. Only their part number varies.

Case:

  • A new column called GUID needs to be added to your BOM.

  • The GUIDs need to be unique. (These can be generated in various online tools or excel)

Result:

  • Separate models for the 2 parts are generated.

  • Product groups with GUIDS are unique datasets and can only exist 1 time in Makersite.

  • The approach of GUIDs is required in all cases where two Product datasets are made the same way but have different part numbers.

Scenario 6 Update of a sub-part with different material/component amounts in a sub-level.

For e.g. the amount of copper (level 7) used in a wire on level 6 of the BOM has changed.

Case:

File name is unchanged

Names and part numbers stay the same in the file

Only the amount of copper has changed

Result:

The process for the manufacturing of the wire is updated everywhere it is used.

The different amount of is now modeled.

The entire BOM chain from level 6 (wire manufacturing) until level 0 is newly generated.

Product groups and processes exist as alternatives in parallel in the model.

Scenario 7 Creation of a new part with different material/component amounts in a sub-level.

For e.g. the amount of copper (level 7) used in a wire on level 6 of the BOM has changed

Case:

  • The file name is changed

  • Names and part numbers stay the same in the file

  • A new column called GUID needs to be added to your BOM.

  • The GUIDs need to be unique. (These can be generated in various online tools or excel)

  • Only the amount of copper has changed

Result:

  • A complete new sub-part is generated.

  • A new product model is set up.

  • Old process is still (unchanged) in use in another model.

Did this answer your question?