You can automate the part selection for job creation by importing a Magics CSV report. This functionality needs to be activated in the admin panel under Organization → Switches.
A Magics CSV file can be imported during job creation to automatically match parts and their quantities with the build generated in Magics. This process significantly saves time, minimizes human error, and ensures data accuracy.
The Magics CSV Import functionality needs to be activated in the Admin Panel under Organization → Switches.
Prerequisites for Successful Part Matching using Magics CSV Import
To ensure successful part matching using Magics CSV import, specific prerequisites must be met in the 3YOURMIND MES, and 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 Status: The order must be updated to any "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 (“Part #”) must be the first variable in the file naming format, followed by a dash “-” in the configured format. See https://3yourmind.atlassian.net/wiki/spaces/PD/pages/124617060/Configuring+the+Agile+MES#File-naming-format
Separate Lines: Each part copy must be written in a separate line (setting in Materialise Magics for Build Reports).
Overquantity Production: If producing a higher quantity than ordered, 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 for the Magics CSV
File Naming: 3D files must be imported to Magics with the 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 must be written in the first column of the CSV.
Separate Lines for Copies: Each copy of a part in the build must be written to the CSV in a separate line (e.g., a part with a quantity of 5 needs 5 individual lines in the CSV).
No Empty Lines: The CSV file must 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 437-269309_O1-pa12-10_optimized 437-269309_O1-pa12-10_optimized 437-269309_O1-pa12-10_optimized 437-269309_O1-pa12-10_optimized 438-269309_O1-pa12-10_optimized_1 438-269309_O1-pa12-10_optimized_1 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
Error | Potential Reasons | Solution |
|---|---|---|
Part Not Found | The Part ID from the CSV file could not be matched with any part in the MES. | Check whether indicated Part ID is correct. |
Quantity Issue | The specified quantity cannot be imported (e.g., overquantity cannot be applied) | Check whether the indicated part has a sequence in the first workflow step. |
Parsing Error |
| Check all the prerequisites listed under “Prerequisites for the Magics CSV” above. |
Empty File | The CSV file is empty | Check that your CSV file exported correctly. |