Page Comparison

Starting with version 4.12 it is possible to You can automate the part selection for job creation by importing a Magics CSV report. The magics CSV import functionality is released with version 4.12 and This functionality needs to be activated in the admin panel under Organization → Switches.

...

Image Removed

The A Magics CSV file can be imported during job creation to automatically match parts and their individual quantities with the build generated in magicsMagics. This allows for major time savings during job creation while at the same time minimizing human error and ensuring correct data.

...

process significantly saves time, minimizes human error, and ensures data accuracy.

...

Prerequisites for Successful Part Matching using Magics CSV Import

For the matching logic to work, certain To ensure successful part matching using Magics CSV import, specific prerequisites must be met in the 3YOURMIND MES, and specific certain requirements must be adhered to when working with Magics CSV. This section outlines these prerequisites and requirements.

Prerequisites in 3YOURMIND

• MES Activation: Ensure MES is activated.

• Order is Status: The order must be updated to any status of the “in progress” category - i.e. relevant parts are existing in MES

• Workflows and workstations are configured

• Workflows are "in progress" status, ensuring relevant parts exist in MES.

• Configuration: Workflows and workstations must be configured and workflows must be assigned to parts

• File Naming: The MES Part _ID is set as ID (“Part #”) must be the first variable in the file naming format and is , followed by a dash “-” in the configured format. See also https://3yourmind.atlassian.net/wiki/spaces/PD/pages/124617060/Configuring+the+Agile+MES#File-naming-format

• Separate Lines: Each part copy is must be written in a separate line (Setting setting in Materialise Magics for Build Reports)

...

• .

• Overquantity Production: If producing a higher quantity than

...

• ordered,

...

• The the sequence group for which you want to produce an excess quantity must be in the first workflow step. See https://3yourmind.atlassian.net/l/cp/vFgE0Z8W)

Prerequisites of for the Magics CSV

• File Naming: 3D files need to must be imported to Magics with the part_id MES Part ID (“Part #”) at the beginning of the file name.

• Export Report: A Magics report needs to be exported and saved as a .CSV file.

• UTF-8 Format: The CSV file needs to be exported in UTF-8 format.

• Parts in First Column: The names of the 3D files need to must be written in the first column of the CSV.

• Separate Lines for Copies: Each copy of a part in the build needs to must be written to the CSV template in a separate line (e.g., a part with a quantity of 5 needs to have 5 individual lines in the CSV).

• No Empty Lines: The CSV file needs to be exported in UTF-8 formatmust not contain empty lines.

Example CSV File

An example CSV containing only the needed information is shown below. The following file represents a build containing part #437 with a total quantity of 5 (the number of lines are counted) and #438 with a total quantity of 3.

437-269309_O1-pa12-10_optimized_1
437-269309_O1-pa12-10_optimized_2
437-269309_O1-pa12-10_optimized_3
437-269309_O1-pa12-10_optimized_4
437-269309_O1-pa12-10_optimized_5
438-269309_O1-pa12-10_optimized_1
438-269309_O1-pa12-10_optimized_21
438-269309_O1-pa12-10_optimized_3

The important part of the part file name is the Part ID at the beginning of the string. The remaining name is not considered when matching csv content and parts in the MES.

Handling of Bad Content in CSV Files

The CSV import functionality of Magics has been enhanced to ensure successful import and matching of parts and quantities. Specifically, it now handles the following scenarios more effectively:

• Empty lines in the CSV: These are now ignored during the import process, preventing any disruptions they might have caused.

• Unknown parts in the CSV: The system now disregards any parts that it doesn't recognize, allowing the import process to continue smoothly with the known parts.

File Validation During the Import

As an MES operator, it's crucial to understand issues with the CSV file during job creation to proceed efficiently. Furthermore, it is paramount that the created job contains exactly the parts and quantities as expected from the CSV file.

This section provides guidance on handling failures during the Magics CSV import process, explaining potential issues and offering solutions.

When Magics CSV Import Fails

Upon clicking the "Import Magics CSV" button on the Create Job page, if any part in the CSV cannot be imported, an interface will display the following information:

• Which parts are failing the import.

• Reasons for the failure.

...

Partial Success: If some parts are imported successfully, users will have the option to either continue or cancel the operation. Choosing "Cancel" will remove all imported parts, while "Continue" will allow the user to proceed with the job creation using the successfully imported parts.

Reasons for (Partial) Import Failure