User Manual

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.

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:

  1. Select and match the names of the fields corresponding to the columns in the data.
  2. 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. 
  3. Select "Do not import" as the column type if some column is not to be imported.
  4. Click Import to upload the data into the appropriate fields of the database.  

When uploading Routings, the fields that can be used are:

  • Product - 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);
  • workstation group - the code or the name of an existing workstation group. If the workstation group does not exist, a new one will be created. This field is required;
  • Operation - free text description of the operation;
  • Setup time - fixed time (in minutes) for preparing the operation;
  • Cycle time - time (in minutes) per cycle of making "Quantity" of products;
  • Fixed cost - the default cost per "Setup time". The "Hourly rate" in the workstation details overrules this setting. (Fixed cost = Setup time / 60 minutes * Hourly rate);
  • Variable cost - the default cost per "Cycle time". The "Hourly rate" in the workstation details overrules this setting. (Variable cost = Cycle time / 60 minutes * Hourly rate * Manufacturing Order quantity);
  • Quantity - the number of products produced per "Cycle time". If not imported, defaults to "1";
  • Department/Worker - the number or name of the department, or the username (e-mail) of the worker assigned by default. The "Default worker" in the workstation's details overrules this setting;
  • Piece-payment - the cost per piece paid to the worker. Available, if the Piece Payment functionality is enabled;
  • Overlap - the minimal finished quantity of the last operation before this operation can start if this operation should start before the last operation finishes (i.e. the operations overlap). Available, if the Overlap function is enabled;
  • Parallelize (1/0) - enable (1) if the operation 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. 

Example, importing routings for two products:

Product workstation group Operation Setup time Cycle time Fixed cost Variable cost Quantity Department
IA-0004 Wooodworks Assembling 30 15  10 5 1  
IA-0004 Paint room Painting    5    10 1  
IA-0005 CNC Machining 180 5     1 CNC operators
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

Updating existing Routings via CSV upload

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.

Important!

  • 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.