Import 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.
- Which fields can be used for importing Routings?
- Example table and file.
- How to update existing Routings via CSV import?
- 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).
Before you start, we strongly advise to read the routings documentation and add at least one routing manually.
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 of some data failed, a skip file will be generated and downloaded to your computer, which indicates all errors line-by-line.
The part number of the product, as in Stock -> Items.
The product's part number is required on every row (this allows importing routings for several products at once. E.g. Sub-assmebly 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.
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.
The cost per piece paid to the worker (labour 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 in to 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.
|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 the routing as described in the help section "Import Routings from a CSV file". If the product has a Routing, it will be replaced, if not, a new Routing will be created.
- 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.