Importing Routings from a CSV file
At Production planning -> Routings -> Import from CSV it is possible to upload the routings for several products at once. Also, it's possible to update existing routings.
- Demo video: Importing data.
- Importing new routings.
- Example table and file.
- Updating existing Routings.
- Important notes.
What is CSV? CSV (Comma-Separated Values) is a universal format for importing or exporting tabular data. A CSV file can be obtained by saving/exporting e.g. an Excel file as CSV (Comma delimited) (*.csv).
When uploading the CSV file:
- Select and match the names of the fields corresponding to the columns in the data.
- Check the "The first row is heading" option if the first row of the file contains headers. Then the first row will not be imported.
- Select "Do not import" as the column type if some column is not to be imported.
- Click Import to upload the data into the appropriate fields of the database.
- If importing some data failed, a skip file will be generated and downloaded to your computer, which indicates all errors line-by-line.
When uploading Routings, the fields that can be used are:
The routing's ID number.
If present, lines with operations are grouped into routings by this column. If the routing number is absent, lines with operations are grouped by product.
If a routing with this number exists, it will be updated. If a routing with this number does not exist, a new routing is created.
If present, the routing number is required on every row.
Name of a routing.
The part number of the product, as in Stock -> Items.
If a routing number is absent, or a new routing is created, the product's ID number is required on every row (this allows importing routings for several products at once. E.g. Sub-assembly Routing Product code is the sub-assembly code).
The code or the name of the workstation group.
If the workstation group does not exist, a new one will be created.
The code or the name of the vendor.
Available, if the if the Subcontracting functionality is enabled.
Free text description of the operation.
Fixed time in minutes for preparing/setting up the operation.
Time in minutes per cycle of making "Quantity" of products.
The default cost per "Setup time" (manufacturing overhead cost).
The "Hourly rate" in the workstation details overrules this setting during actual scheduling. (Fixed cost = Setup time / 60 minutes * Hourly rate)
The default cost per "Cycle time" (manufacturing overhead cost).
The "Hourly rate" in the workstation details overrules this setting during actual scheduling. (Variable cost = Cycle time / 60 minutes * Hourly rate)
The number of products produced per "Cycle time".
If not imported, defaults to "1".
The number or name of the department, or the username of the worker assigned by default. The "Default worker" in the workstation's details overrules this setting during actual scheduling.
For several workers, separate the list with a comma (,). If your CSV separator is also a comma, then the list must be quoted ("worker1, worker2").
The cost per piece paid to the worker (labor cost).
Available, if the Piece Payment functionality is enabled.
The minimal processed quantity of the previous operation before this operation can start, if this operation should start before the last operation fully finishes (i.e. the subsequent operations overlap).
Warning: If subsequent operations are not balanced (i.e. equal lengths), or 2nd longer than 1st, then a too low value can fragment this operation into several pieces (depending on total MO quantity).
Available, if the Overlap function is enabled.
Enable (1), if the production run should be divided into smaller parallel operations among all available workstations of the same group.
Available, if the Parallel Execution of Production Operations function is enabled.
|Operation order number||
The line number (ID) of the operation in the routing.
Optional. If missing, operations will be sorted in the order they appear in the import file.
If used, must be defined on all lines. The numbers must start from 1 and be incremented with a step of 1.
|Sequence||The number(s) (ID) of the operation(s) which must be completed, before this operation can start.
Optional. If missing, the sequence corresponds to the order of operations.
If used, must be defined on all lines. At least one line must be 0, so it could start immediately. Separate several values with a comma, e.g. “1,2,4”.
Available, if the Overlap and Special Sequences functionality is enabled.
|Product||workstation group||Operation||Setup time||Cycle time||Fixed cost||Variable cost||Quantity||Department|
|IA-0005||Oven||Heat treatment||120||100||Heat treating|
|(Up to 3000 lines can be imported at once)|
Download a sample file: import-routings.csv
At Production planning -> Routings -> Import from CSV it is possible to update existing Routings by uploading a CSV file containing the new Routings.
Upload a CSV file with routings as described in the help section "Import Routings from a CSV file". A routing is updated if:
- the file contains a column with a routing number, and routing with this number exists,
- or the file does not contain a column with a routing number, a column with a product is selected, and the product has a routing.
After upload, to update the routings of planned Manufacturing Orders:
- Open a routing.
- Press Save.
- Proceed to update the MOs.
- If the imported file contains non-Latin characters, the file must be in UTF-8 (preferred) or Unicode encoding. If Excel is used to save the file, select the "Unicode Text (*.txt)" option in the "Save as type" field. Even though the extension of the file is TXT, it can be imported as a CSV-file.
- The limit is 3000 lines per upload. If the file is bigger, divide it into several smaller files.
- Since importing can be a question of trial-and-error, we strongly suggest making a back-up of the database before importing. In that case, if anything goes wrong, it is always possible to restore the previous session.