Runs With Job Group |
|
A Runs With Jobs Group is two or more jobs with the exact same routings that are grouped and scheduled together. The scheduler totals the quantity for the Runs With Jobs in the group and schedules the group based on the selected parent job. When the parent job has been completed, the entire Runs With Job group will be completed.
A Runs With job in a group may be "Deactivated" by the user manually, or it may be "Deactivated by system" during a schedule run if the Runs With job's routing does not match the parent job.
For more information see the sections below:
1.Manufacturing Order Job Details and Runs With Jobs
2.Scheduler and Runs With Jobs
3.Job Status Updating and Runs With Jobs
4.SQL and Text Imports and Runs With Jobs
Manufacturing Order Job Details and Runs With Jobs
Once a Runs With Job Group is set up, changes can be made in the operations grid. If not a parent and a Runs With job is changed, the number of operations, resource and pool must match or a warning is issued. If the user continues with the save, the Runs With job may be deactivated by the scheduler. If the above parameters match, the parent status is updated to in-process if the Runs With job operation is in-process.
If a parent is updated, the following Runs With job parameters are updated:
1.Operation Ident
2.Resource
3.Pool
4.Route command
5.Route parameter
6.Min resources
7.Max resources
8.Status:
1.If the parent operation is Completed, set all other Runs With corresponding operations to Completed.
2.If the parent operation is In Process, set all other Runs With corresponding operations to In Process if their current status is not Completed.
3.If the parent operation is null, set all other Runs With corresponding operations to null.
Before a schedule run, each Runs With Job Group is compared to the Runs With parent. The Runs With jobs are matched to the parent using:
1.Number of operations must match
2.Operation Ident
3.Route command
4.Route Parameter
5.Resource
6.Pool
7.Min Resources
8.Max Resources
If they do not match, the Runs With job is set to "Deactivated by system" and is scheduled independently.
After a Runs With Job Group is scheduled, the following columns are updated from a parent Runs With job to all other Runs With jobs in the group that are not deactivated in the schedule:
1.Was Planned Days Used
2.Operation Ident
3.Route Command
4.Route Parameter
5.Runtime Method
6.Runtime
7.Setup Time
8.Max Resources
9.Min Resources
10.Min Max Setup Time
11.Min Max Runtime
12.Min Max Act Setup Time
13.Min Max Act Runtime
14.Min Max Qty To Build
15.Min Max Qty Scrapped
16.Min Max Qty Completed
17.Start Date
18.Start Shift
19.Start Hrs
20.Status to C if parent C
21.End Date
22.End Hrs
23.End Shift
24.Resource
25.Pool
26.Wait Start Date
27.Wait Start Shift
28.Wait Start Hrs
29.Wait End Date
30.Wait End Shift
31.Wait End Hrs
32.Move Start Date
33.Move Start Shift
34.Move Start Hrs
35.Move End Date
36.Move End Shift
37.Move End Hrs
38.Schedule History ID
39.Freeze Schedule History ID
40.Lock Selection
41.Actual Type Of Work
Job Status Updating and Runs With Jobs
If updating a Runs With Job Group and the Runs With job is Activated, the following fields are updated if the Parent Seq and number of ops match:
1.Operation Ident
2.Route Command
3.Route Parameter
4.Resource
5.Pool
6.Max Resources
7.Min Resources
8.Start Date
9.Start Shift
10.Start Hrs
11.End Date
12.End Hrs
13.End Shift
14.Status:
1.If the Runs With parent operation is In Process, set all Runs With jobs' corresponding operations in the group to In Process if their current status is not Completed.
2.If the Runs With parent operation is Completed, set all Runs With jobs' corresponding operations in the group to Completed.
3.If the Runs With parent operation is null, set all Runs With jobs' corresponding operations in the group to null.
4.If a Runs With job (not a parent) operation is In Process, set all other Runs With jobs' corresponding operations in the group and parent to In Process.
5.If a Runs With job (not a parent) operation is Completed, set all other Runs With jobs' corresponding operations in the group and parent to In Process if there current status is not Completed.
SQL and Text Imports and Runs With Jobs
No special handling is made in the imports as each Runs With Job's operation is updated separately. The scheduler will handle any mismatched operations in Runs With Job Groups and set jobs that do not match to "deactivated by system".
See Also: