Job Scheduling

Job Scheduling Lite options are an alternative for finite capacity scheduling. They are available for users that either don’t need the rigidity of finite capacity scheduling or don’t have all the data required for finite capacity scheduling, for example, runtimes.

SETUP – DEFINING THE SCHEDULE-AGAINST RESOURCE (AREA / LINE) FOR EACH PROCESS SPEC. Standard finite scheduling uses the controlling machine and labor resources called out on each stage recipe for the schedule-against resource. The Schedule Lite options instead use the Process Spec Sequencing Group to indicate the schedule-against resource. The sequencing group represents an area or line where manufacturing requirements are processed. Please note that if multiple factories are in use, the factory might have to be indicated within the sequence code, because standard Ross does not provide that breakdown.

SETUP – SEQUENCING DIFFERENT PROCESSES WITHINTHE SAME SCHEDULE-AGAINST RESOURCE (AREA / LINE). Similar to finite scheduling, Schedule “Lite” DOES use the process spec Primary, Secondary and Tertiary Sequencing codes to sequence different processes within the same sequencing group.

     a. MPS Schedule Lite. Inquiry against a specific Master Production Schedule, sorted by ascending bucket date (although most of the time only one bucket is selected, a bucket representing a week, day etc), ascending sequencing group (area / line), descending low level code, ascending process sequence 1, 2 and 3. The displayed rows represent bucket aggregate planned production quantity (not individual jobs). The resulting output looks very much like the MPS “Production Report”, but with an inquiry / grid appearance that can be easily downloaded into a spreadsheet. That information could be used to create and schedule live jobs. Drilling into a row will display a list of live jobs for that requirement and drilling in again will display the job status inquiry for the selected job.
     b. Job Schedule Lite. Inquiry against a group of live jobs starting within the desired start date range (for example a week’s worth of jobs). The resulting data is sorted by ascending sequencing group (area / line), descending low level code, and ascending process sequence 1, 2, and 3. This is more than an inquiry in that the user can prioritize jobs within sequencing group and that priority is saved on the jobs record. The inquiry data can be downloaded into a spreadsheet. If the user drills into an inquiry row, the job status inquiry will be performed for the selected job. While the user is drilled into a job schedule row, the job status inquiry is available from the active links box.