|
|
|
Use this procedure to create a subproject using a project template. The default field values, defined in the project template, vary depending on the selections made in the template.
Follow these steps:
The properties page appears.
The Gantt view appears.
The available project templates appear.
The create page appears.
Specifies the pool of resources allowed when assigning resources to tasks.
Values:
Default: Resource Pool
Required: Yes
Defines the name for the project.
Limits: 80 characters
Required: Yes
Defines the unique identifier for the project that is typically auto-numbered.
Limits: 20 characters
Required: Yes
Defines the description.
Limits: 240 characters
Required: No
Specifies the name of the resource responsible for managing the project. The manager of a project automatically receives certain rights for the project.
The project manager is not the same as the collaboration manager. The person creating the project becomes the collaboration manager for the project by default.
Default: The resource creating the project. If you are creating a project that someone else can manage, change the default to another resource.
Required: No
Specifies the page layout to view project information. Available layouts are company-specific and dependent on the values set by your CA Clarity PPM administrator. Layouts also depend on whether an add-in is installed. If other layouts are not available, the field is display only.
Default: Project Default Layout
Required: Yes
Defines the start date that you identify for a project initially. As you create tasks and assignments, this date is auto-calculated to match the first date that a task is scheduled to start. At that point, to edit this date, adjust the following dates:
Default: Current date
Required: Yes
Defines the finish date that you identify for a project initially. As you create tasks and assignments, this date is auto-calculated to match the last date that a task is scheduled to finish. At that point, to edit this date, adjust the following dates:
Default: Current date
Required: Yes
Specifies if the planned cost dates are synchronized with the investment dates. Selecting the option for a detailed financial plan does not affect the planned cost dates.
Default: Selected
Required: No
Defines the stage in the investment lifecycle. The list of choices is company-specific and depends on the values that your administrator sets.
The metric is used in portfolio analysis when you use comparable stage criteria across all portfolio investments.
Specifies the purpose or business case for this project.
Values: Cost Avoidance, Cost Reduction, Grow the Business, Infrastructure Improvement, and Maintain the Business
Required: No
Defines the relative importance of this investment in relation to all other investments. The priority controls the order in which tasks are scheduled during autoscheduling. The priority is subject to dependency constraints.
Values: 0 - 36 (where zero is the highest importance)
Default: 10
Required: No
Indicates the level of work completed on the tasks.
Values:
Default: Not Started
Required: Yes
Indicates the status for the project.
Values: Approved, Unapproved, and Rejected
Default: Unapproved
Required: Yes
Specifies to pin this investment when added to a portfolio. This field is used during scenario generation.
Default: Cleared
Required: No
See the Portfolio Management User Guide for more information.
Specifies the method for calculating the percent complete value for the project and tasks.
Values:
Summary Task % Complete = Total Detail Task Duration Complete / Total Detail Task Duration
Summary Task % Complete = Sum of Detail Task resource assignment Actuals / Sum of Detail Task resource assignment Effort Detail Task % Complete = Sum of resource assignment Actuals / Sum of resource assignment Effort
Default: Manual
Defines the department OBS for the project.
Defines the location OBS for the project.
Defines the release checklist for the department OBS.
Displays the name of the project template from which data is used to populate the new project. Use a template to create a project with the following types of information predefined:
A template enables you to implement projects with common elements throughout the organization.
not sure if we need to describe all this in the field definition. this info is already provided in the conceptual text that precedes the procedure and the field descriptions
Defines the percentage by which the work estimates on each task is required to be increased or decreased for the new project. The scaling is relative to the template.
Values: 0-100 (where zero means no change)
Default: Zero
Required: No
Defines the percentage (positive or negative) as the scaling factor for the dollar amounts defined in project cost plans and benefit plans.
Values: 0-100 (where zero means no change)
Default: Zero
Required: No
Example: The template project from 1/1/2009 to 12/31/2009 allocates $10,000 for planned cost and $20,000 for planned benefit for the project duration. If a Scale Budget By value of 20 percent is defined, the plans copy over to the new project as follows. Assumed that the project duration is same as the template project:
The planned benefit shows $24,000 (scaled up by an additional 20 percent of the original value).
Specifies to replace the resources in the new project with the primary roles, or team roles of the named resources on the project template. If a named resource has no primary role or team role, the named resource is retained on the new project. This setting overrides the default project management setting on the settings page.
Suppose, a cost plan uses a resource as a grouping attribute. Selecting the check box, copies the cost plan from the template, but without converting the resource values to roles. The resource value can be the only value that differentiates one line item detail row from another. In the absence of the value, duplicate detail rows can result in the cost plan.
Default: Cleared
Required: No
| Copyright © 2012 CA. All rights reserved. |
|