Task Cycle Definition - CMUPTC

Some types of Contracts have a definable list of tasks that need to be accomplished, the result of which is the fulfillment of the Contract. A perfect example of one type of Contract that falls into this category is a Contract for a new building. There is a definable list of tasks that need to be accomplished in order to build a new building. Typically, those tasks need to be done in a certain order (e.g., clear the site, pour the foundation, frame the walls, etc.). The Contract Management (CM) Task/Cycle Definition (CMUPTC) page allows the user to define individual tasks and then group those tasks into cycles. The cycle is identified by a Cycle ID and can be hierarchical by step if needed. Once a Cycle ID is created, it can then be associated with a Contract. Once a Cycle ID is associated with a Contract on the Contract Management (CMUPCM) page, the system will automatically default the Task Tracking tab on the Contract Tracking (CMUPTK) page with the tasks in that cycle. In this way, the definition of the Cycle ID acts as a "template" for the defaults on the Task Tracking tab in Contract Tracking. One Cycle ID can be used on many Contracts. After the Task Tracking tab on Contract Tacking is defaulted with the template cycle, it can be modified to fit the specific Contract and used to track detailed information about the approval, timeline, status, etc., of each of those Tasks on that particular Contract.

Tasks Tab

Task ID: This is the unique identifier for this Task.
Task Title: This is the short description that the user will see when entering Tasks on the Cycles tab and on the Task Tracking tab on Contract Tracking page, it is important that it be fairly descriptive.
Task Description: Enter a more detailed description of this Task.
Number of Days: This field is used to hold the estimate of how many days this Task will take to complete. The type of days is determined by the Type of Days field below.
Type of Days: There are two (2) different types of days represented in the Number of Days field above, as follows:

• BUS Business Days are the days of the work week, Monday through Friday.
• CAL Calendar Days include all seven (7) days of the week, Monday through Sunday.

Pre-Task: If there is a Task that must be completed before this Task can be started, enter its Task ID here.
Post-Task: If there is a Task that must be completed after this Task is finished, enter its Task ID here.
Comments: This optional field is used to enter any additional description or information about this Task that is not already included in the Task Title or Task Description.

Cycles Tab

Cycle ID: This is the unique identifier for this Cycle. This Cycle ID is associated with a Contract on the Contract Management page, Contract Details tab.
Cycle Title: This is the short description of this Cycle. The Cycle title echoes on the Contract Details tab of the Contact Management page and should be descriptive.
Cycle Description: Enter a more detailed description of the purpose/goal/end result of this Cycle.
Total Business Days: This is the system-generated sum of the business days it will take to complete this Cycle. Only those tasks that have day estimates in business days (as opposed to calendar days) will be included in this sum.
Total Calendar Days: This is the system-generated sum of the calendar days it will take to complete this Cycle. Only those tasks that have day estimates in calendar days (as opposed to business days) will be included in this sum.
Comments: Enter up to 60 characters to provide an additional description or information about this Cycle.
Step: Typically, Tasks must be completed in a particular order. This field is used to identify the task order of completion.
Task ID: This is the unique identifier for a Task that was created on the Tasks tab.
Number of Days: The read-only value in this field echoes from the Tasks tab for the Task identified in the Task ID field. This is the estimated number of days that it will take to complete.
Type of Days: The read-only value in this field echoes from the Tasks tab for the Task identified in the Task ID field. This is the types of days that are represented in the Number of Days field above.
Other Requirement Code: The Other Requirement Code indicates the type of approval required to indicate a task has been completed. There are two (2) different types of codes represented:

• APRV Get Verbal Approval.
• APRW Get Written Approval

Page Business Rules

Inherent to every Contract Management page are a couple base functionality features. These features are as follows:

• Upon deletion of a parent table record all child records associated with the specified parent will also be deleted. (For example, deleting a compliance vendor from a contract on the Contract Tracking page will result in all compliance detail records sharing the same Contractor ID being deleted as well).
• When creating a new record in a table, the system will automatically check to make sure that a record with the same name (primary key) does not already exist. (For example, attempting to create a new contract with the same contract number, as another contract, will result in an error message being displayed).

All other, more specific, rules are detailed on a page-by-page basis below:

CM Task/Cycle Definition Business Rules

• Calculate the sum of the business days of all tasks within a cycle
• Calculate the sum of the calendar days of all tasks within a cycle