Job Dispatch

To dispatch a new job, the workcenter must not currently be running a job. There are two ways jobs can be dispatched. First, from the workcenter view. Second, from the performance dashboard.

Workcenter

At the bottom center of the workcenter view, click the "Start Job" button in order to begin dispatching a job. If the selected workstation is currently running a job or in setup, the current job will need to be stopped in order to start a new one. Read more about the workcenter view here.

 

Once the Start Job screen has appeared, you may dispatch a new job to this workcenter. Select when the job should stop and whether to start the job in setup or directly in production and the job will begin.

 

The Start Job screen:

  1. Search Bar - Allows the user to search for a job by name.
  2. Job Name - A unique descriptor to identify each job. When a job name is selected the user will have the option to start the job in setup, or start the job directly in production. Additionally, the user can click on the job name again to return to the job list and select a different job.
  3. Job Cycle Time - The amount of time each cycle is expected to take during this job.
  4. Expected Setup Time - The amount of time the workcenter is expected to be in setup status before moving the job into production.
  5. Close Button - Brings the user back to the workcenter view.

 Performance Dashboard

Jobs can also be dispatched from the performance dashboard. First, click the unscheduled (grey) workcenter you want to dispatch a job to, then select the "Start Job" button:

 

Job_Dispatch_Tile.png

 

The "Start Job" window will appear on screen which contains the same information and functionality as above using a different interface.

 

 

Just as when a job is started from the workcenter view, jobs can be searched for by name and started in either setup or production. Additionally, when starting a job from the performance dashboard, jobs that are not already configured for the workcenter can be configured on the fly and dispatched to the machine. This configuration will then be saved for future dispatches of the same job to this workcenter.

 

 

 

Being able to start a job directly from the performance dashboard makes it much more efficient to start multiple jobs on multiple workcenters since the user does not need to open the individual workcenter view for each machine.

 

 

 

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk