The workplan structure organizes the tasks that define all of the work in a project. Project managers and task managers can create tasks and define their attributes, such as task schedules, resource assignments, and dependencies.
A workplan structure includes the following functionality:
–You can create multiple versions of the workplan. This enables what–if analysis for project managers and a historical archive of changes to the workplan.
•Workplan Approval and Publication
–You can submit a workplan for approval for change control purposes. Once approved, or if approval is not necessary, you can publish the workplan. Publishing the workplan communicates new tasks, dates and changes that affect the schedule of the workplan.
–You can designate a version of the Workplan as the baseline version.
–When comparing two versions of a workplan structure for a project, you may have a task present in one workplan version, but missing in the other workplan version. Depending on which version you are viewing, different rules will apply in displaying and rolling up the task.
You can define workplans that meet the requirements of your projects. You can:
•Set up basic starting information for a workplan, including the structure name, lifecycle, current phase, and default display outline level.
•Enable workplan versioning.
•Enable work quantity planning and progress collection for a workplan and each task.
•Automatically update the tasks’ transaction dates.
•Define approval options for the workplan (if versioning is enabled).
•Select a planning resource list for the workplan.
•Enable workplan cost tracking.
•Enable multiple currency amount planning and define the list of transaction currencies used by your workplan.
•Enable reporting of workplan cost amounts against a selected resource breakdown structure.
•Determine whether resources assigned to the workplan use actual rate or planning rates for costing of planned quantities. If you use planning rates you can define the planning rate schedules.
–Enter a name for the workplan structure.
–A lifecycle is a collection of sequential project phases. Each phase represents a set of logically related project activities.
–Select a default current lifecycle phase for the workplan. The current phaseis the starting phase for workplans associated with projects.
•Default Outline Level
–The number of levels to initially display on any page displaying the Work Breakdown Structure hierarchically.
•Enable Workplan Versioning
–You can enable workplan versioning to create multiple versions of the workplan for your project. You must also enable workplan versioning to take advantage of workplan approval, publication, and workplan baseline functionality.
–If a workplan structure and financial structure are shared, you can only have one working version at any time.
•Enable Work Quantity
–Select this box to enable work quantity planning and progress collection for the workplan.
•Automatically Publish Workplan upon Project Creation from Project Template
–If your workplan is enabled for a project template, and you choose to enable workplan versioning, the system will automatically publish the workplan when a project is created from the template.
–You can only enable this option at the project template level.
•Schedule Using Third Party Software
–Select this box if you want to use a third-party software application to perform workplan scheduling operations. You can indicate whether you want the system to schedule forward from the project start or backward from the project finish.
•Allow Dependencies Only for Lowest Tasks
–Select this box to enable dependencies only for the lowest tasks in the workplan structure.
•Enable Task Workflow
–Select this box to enable the Task Execution workflow process for the workplan structure. You must also enable the Task Execution workflow at the task level for the tasks that you want to include in the process.
•Automatically Update Task Transaction Dates and Date Adjustment Buffer
–Task transaction dates control the financial aspects of tasks, such as when expenditures can be charged and when budget defaults can be processed. If the workplan structure is shared with a financial structure, Oracle Project Management updates the transaction dates of all tasks with their actual start and finish dates (or their scheduled start and finish dates, if actual dates are unavailable).
–If your workplan does not have versioning enabled, the system adjusts transaction dates whenever you update task actual and scheduled dates.
–Use the Date Adjustment Buffer to adjust the transaction dates automatically generated by the system. The system subtracts the buffer value from newly derived transaction start dates and adds it to newly derived transaction finish dates.
–For example, the adjusted transaction start and finish dates before the buffer is applied are 15-JAN-2007 and 20-JAN-2007. If the buffer value is 5, then the system subtracts 5 from the start date and adds 5 to the finish dates. The resulting transaction dates are saved as 10-JAN-2007 and 25-JAN-2007.
–You can require that the workplan be approved before it can be published. If you require workplan approval, you must designate an approver. You can also arrange for the system to automatically publish the workplan when it is approved.