Job Import CSV Format

Below is a list of fields that should be present in the CSV file used to import jobs into MachineMetrics. To import jobs, please send this file to support@machinemetrics.com and we will perform the import.

name
part
operation
lot
description
due_date
quantity
partvalue
default_expectedcycletime
default_idealcycletime
default_setuptime
default_partcountmultiplier
default_actualparts
warningpercent
failurepercent
workcenter
expectedcycletime
idealcycletime
setuptime
partcountmultiplier
actualparts
programname

 

The CSV file you generate will create what we call JobMachines. These are jobs associated with the workcenters (machines) that can run them. Each row will contain a unique job-workcenter pair. Any workcenter can appear multiple times within the file -- as can any job. But each job can only be associated with any given workcenter once. It is also critical that any given program name only be associated with a single job (if provided).

name: The name of the job / workorder.

part: (optional) The part number.

operation: (optional) The operation number.

lot: (optional) The lot number.

description: (optional) A description of the job.

due_date: (optional) The date that the job / workorder is due

quantity: (optional) The number of pieces required to complete the job / workorder

partvalue: (optional) The value of the part in dollars. This is used on the score card report.

default_expectedcycletime: The average time expected to produce one part. This can contain some padding for things like part changeover. This value will be used when creating new Job/Workcenter associations or schedules. This is measured in milliseconds.

default_idealcycletime: The ideal time expected to produce one part. It should be the time required in the most ideal scenario. This value will be used when creating new Job/Workcenter associations or schedules. This is measured in milliseconds.

default_setuptime: The expected setup time for the job. This value will be used when creating new Job/Workcenter associations or schedules. This is measured in milliseconds. If a value is not specified, the workcenter will immediately be placed into production when dispatching a job. If the value is zero, all setup time recorded will be considered unplanned. For values greater than zero, setup time will be considered planned until that time has elapsed. This is measured in milliseconds.

default_partcountmultiplier: In cases where the workcenter does not report the same number of parts that were produced during a single cycle, this value should reflect that. If 4 parts were produced in a cycle, but the workcenter only increments its part counter by 1, the Part Count Multiplier would be 4.

default_actualparts: This is the number of parts that are produced each cycle regardless of what is reported. If 4 parts are produced per cycle, the value for Actual Parts would be 4 -- whether the workcenter increments its part counter by 4 or by 1, it does not matter. This is rarely used, and almost always equal to partcountmultiplier.

warningpercent: The percent of the Parts Goal that, if reached, will result in tiles turning orange and warning-level notifications being sent out. Should be a value between 0 and 100. If left blank, it will use the default value of 100.

failurepercent: The percent of the Parts Goal that, if reached, will result in tiles turning red and failure-level notifications being sent out. Should be a value between 0 and 100. If left blank, it will use the default value of 80.

workcenter: The name, id, or ERP ID of the workcenter as it is recorded in MachineMetrics. Since the name can change, it is recommended that you use its id. The id can be found on the Workcenters page under the gear in the upper right corner of the site.

This field can also contain the name of the Workcenter Group to associate this job with. If this is provided, non-default values for expectedcycletime, idealcycletime, setuptime, partcountmultiplier, actualparts, and programname can be left blank. Automatic Job Dispatch is not supported for workcenters only associated with a job via a Workcenter Group (default_programname is coming soon to support this scenario).

If you are associating both a Workcenter Group as well as individual machines, the Workcenter Group must be first in the CSV for that Job.

expectedcycletime: Similar to the default_expectedcycletime mentioned above, but this specifically applies to the workcenter that this particular row is associating with the job. This is typically the same value as default_expectedcycletime, but can be used to override the default value if this workcenter runs parts at a different rate.

idealcycletime: Just like default_idealcycletime, but for this Job/Workcenter association. Typically the same value as default_idealcycletime, but can be used to override that default.

setuptime: Just like default_setuptime, but for this Job/Workcenter association. Typically the same value as default_setuptime, but can be used to override that default.

partcountmultiplier: Just like default_partcountmultiplier, but for this Job/Workcenter association. Typically the same value as default_partcountmultiplier, but can be used to override that default.

actualparts: Just like default_actualparts, but for this Job/Workcenter association. Typically the same value as default_actualparts, but can be used to override that default. This is rarely used, and almost always equal to partcountmultiplier.

programname: (optional) The name of the program that (if configured for the given workcenter -- and the workcenter's data stream provides this information) will automatically cause this job to be dispatched on this workcenter.

(note: please do not format numbers to include commas, dollar signs, etc - this will cause the information to be interpreted incorrectly)

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk