Creating jobs via Magics CSV import

Starting with version 4.12 it is possible to 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 needs to be activated in the admin panel under Organization → Switches.

Changed Magics CSV import button placement from version 22.3 onwards

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

Prerequisites for Successful Part Matching using Magics CSV Import

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

Prerequisites in 3YOURMIND

MES is activated
Order is updated to any status of the “in progress” category - i.e. relevant parts are existing in MES
Workflows and workstations are configured
Workflows are assigned to parts
Part_ID is set as 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
Each part copy is written in a separate line (Setting in Materialise Magics for Build Reports)

In case you want to produce a higher quantity than was ordered, there is an additional prerequisite (see https://3yourmind.atlassian.net/l/cp/vFgE0Z8W):

The sequence group for which you want to produce an excess quantity must be in the first workflow step

Prerequisites of the Magics CSV

3D files need to be imported to Magics with the part_id at the beginning of the file name
A Magics report needs to be exported and saved as .CSV
The names of the 3D files need to be written in the first column of the CSV
Each copy of a part in the build needs to 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)
The CSV file needs to be exported in UTF-8 format

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_2
438-269309_O1-pa12-10_optimized_3

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.