The schedule maintenance program deals with the definition and management of the specific tasks needed for a book to be published. For example; prepare first page proofs, approve artwork. As many or as few Tasks, as required by each Project, may be defined. The resource for each Task can be assigned to various personnel. [Read more…]
Add a task
- In the menu, expand Publishing Modules > Book Publishing > Entry and double-click BP Work with Project. BPM005 Project Selection panel is appears. BPM005 Work with Project panel appears.
- Key in the required fields to select project(s) or leave blank to select all and click OK. BPM005 Work with Project panel appears.
- Select project and click option Schedule. BPM300 Schedule Maintenance panel appears.
| Note | If the project consists of several books, BPI100 Book Selection panel will be displayed. Then select the required book and click OK. |
| Field | Description |
| Scheduling On/Off | To turn On scheduling or turn Off scheduling. |
| Schedule method |
There are 3 scheduling methods, Forward, Backward or Both. The Task Maintenance program within the Scheduling option allows a scheduling method for backward scheduling. The system schedule backwards from the date entered and aligns the schedule backwards. |
| Task sch | Start scheduling task or finish scheduling task. |
| Task | The task code for the work performed. Note: if this field is left blank the default task set up on the Employee Masterfile defaults. Determines which GL account is debited for the cost of the work. This task code also determines whether text and the Project ID are required to be entered. The sequence given to the task and the task description for the work to be performed. |
| S |
Status of the task. On starting a task, its status is changed from O to A On finishing a task, its status is changed from A to C On locking a task, its status is changed to L |
| Schedule date start/finish | The date when the task has to start and by when it has to be finished. |
| Actual date start/finish | Actual Start and finish date of the task |
| Dur | The estimated time the task can be completed in days. The actual duration is generated once the task is complete. |
| Work Hrs |
This is the estimated amount of hours it takes to complete the task. The actual work hours it took for the task to be completed is generated once the task is completed. Note: Even though a task may have duration of 7 days, it may only take 5 actual working hours to complete the task. |
| Prdrsr Task | A predecessor is a task to which another has succeeded. Predecessors should be specified to imply dependency of tasks. A predecessor for a sub-task cannot be its main task; neither can it be any directly associated with the main task therefore the next task cannot be started until the nominated task has been finished. |
| Dly day | Determines how many days a task can be delayed. This is an informational field. |
| Function | Description |
| Re-Sch | Reschedule Tasks from the start or finish date or the end and schedule backwards. On rescheduling if the start date is changed then the finish date is re-calculated based on the duration. All other tasks affected by this change (based on predecessors) are altered. However if the main task start date is changed, the change is not effected since the main task is dependent on sub-tasks. The schedule dates are then adjusted according to the selection. |
| Fmt | Changes the display format to show the following fields: Resource, Dur day, Work Hrs, Prdsr Task, Dly day or Comments. |
| All/Sum/Child | Shows All tasks/Summary tasks/Child tasks. |
| Baseline | Display the baseline dates for the schedule. |
| Chg seq | Change the sequence of the tasks. |
| Lock | Lock the schedule dates. |
| Baseline option | Apply the baseline to the schedule to transfer start and finish dates. |
| Txt | Add text to a schedule. |
| Prt | Prints the schedule. |
| Option | Description |
| Lock/Unlock | Lock/Unlock the schedule dates. |
| Availability | Check resource availability for a task. |
| Copy Act date | Copy actual start and finish dates to scheduled start and finish dates respectively. |
| Start | Start a task, the status is changed from O to A and the actual start date is highlighted in a different color. |
| Finish | Finish a task, the status is changed from A to C and the actual finish date is highlighted in a different color. |
| Activity | Accesses BPM310 Activity Maintenance to add activity to a task or to maintain an existing activity for a task. |
| Expand | Expand a schedule. By expanding, the tasks and the sub tasks are indented on the screen. |
| Collapse | Collapse a schedule. By collapsing only the tasks are shown, the sub tasks are hidden. |
| Delete | This option deletes a task. This option must exist in TMSBP/MNT-BS and be defined for each user or user group in TMSBP/OPT-BOOK.
TMSDS/CFM-MSG holds the message to display on screen when deleting a schedule to allow the user to confirm the deletion. TMSDS/CFM-PGM determines the programs that call the confirm screen program. BPM300 has been added to this Control File to enable the confirmation screen to be called when deleting a schedule. |
| Text | Accesses BPM900 Task Text maintenance to add text to a task. |
| Commit | Add a commitment. |
| Action | Add an action to a task. |
- Click function Add. BPM300 Task Maintenance panel displays in Add mode.
| Field | Description |
| Task | The task code for the work performed. Note: if this field is left blank the default task set up on the Employee Masterfile defaults. Determines which GL account is debited for the cost of the work. This task code also determines whether text and the Project ID are required to be entered. The sequence given to the task and the task description for the work to be performed. |
| Status | Status of the task. When a task is started, its status is changed from O to A and when it is finished, its status is changed from A to C. |
| Cost type | The cost type is a unique 3 digit number. It can be allocated to one WIP account per cost type for a 1 to 1 ratio, or can have many costs types to the one WIP account. The cost type defaults from the account set created for the selected Project. |
| Task type | Only used when receipting stock to determine if advances or stock was received. |
| Parent task | This is the parent task used when creating sub tasks. This is the task the sub task is a part of. Parent tasks are tasks that must be completed before the next Parent Task is started. |
| Predecessor | A predecessor is a task to which another has succeeded. Predecessors should be specified to imply dependency of tasks. A predecessor for a sub-task cannot be its main task; neither can it be any directly associated with the main task therefore the next task cannot be started until the nominated task has been finished. |
| Resource | This is the person who is completing the task. |
| Delay days | Determines how many days a task can be delayed. This is an informational field. |
| Work hour | This is the estimated amount of hours it takes to complete the task. The actual work hours it took for the task to be completed is generated once the task is completed. Note: Even though a task may have duration of 7 days, it may only take 5 actual working hours to complete the task. |
| Actual work hour | The actual number of work hours it took to complete the task is generated once the task is complete. |
| Duration | The estimated time the task can be completed in days. The actual duration is generated once the task is complete. |
| Current start | This is the current start date for the task used for scheduling. |
| Current finish | This is the current finish date for the task used for scheduling. |
- Enter the required fields, as necessary.
- Click OK. The task gets added to the schedule.
