| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nProject Name\n\n | \n\nName of the project.\n\n |
| \n\nProject manager\n\n | \n\nProject manager assigned to the project.\n\n |
| \n\nStatus\n\n | \n\nCurrent status of the project. This information is retrieved from the **Overall health** field in the most recent project status report of the project.\n\n |
| \n\nNumber\n\n | \n\nSystem-generated number with a configurable prefix.\n\n |
| \n\nPercent complete\n\n | \n\nPercentage of the project that has been completed.\n\n |
| \n\nState\n\n | \n\nCurrent state of the project. All new projects begin as **Pending**. The state of the project can be set on the Project form or derived from the task state.The default available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped.\n\n You can also [create a custom state](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/customize-project-task-states.md) for each state type by overriding the state dictionary attributes.\n\n For example, say that for the project tasks you have created a custom state called **Testing** for the **Work in Progress** state type. When you update the project task state to **Testing**, the project state is also updated to **Testing**. However, if you have not created a **Testing** state for the **Work in Progress** state type, the project state is updated to the default **Work in Progress** state.\n\n |
| \n\nDescription\n\n | \n\nDetailed description of the project.**Note:** Special characters are not supported in the project description. Also, avoid copying text from text processor as it ma cause issues while displaying project information on the planning console.\n\n |
| \n\nSimilar projects\n\n | \n\nDisplays projects that have similar values for the **Description** and **Short Description** fields using predictive intelligence and machine-learning algorithms. For more information, see [Predictive Intelligence for Project Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/predictive-intelligence-for-project.md).\n\n |
| \n\nRelated Search\n\n | \n\nDisplays search results matching the **Name** field by default. You can use this field to search for matching projects using other terms also.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nSchedule\n\n | \n\nWork schedule to be used for this project. The default schedule is an 8-hour work day \\(from 8 a.m. to 12 p.m. and 1 p.m. to 5 p.m.\\). A day is considered to be a work day and not a 24-hour day.\n\n |
| \n\nApproved start date\n\n | \n\nThe date to start the project. This field retains the demand approved start date if the project is converted from a demand. The project schedule is not applied to this date and the date remains unchanged when you add project tasks to your project. This field is highlighted with red color if the date in this field is set to a date later than the **Planned start date** field.**Note:** The approved start date of the project is also carried forward to any sub-project associated with the project.\n\n |
| \n\nApproved end date\n\n | \n\nThe date when this project ends. This field retains the demand approved due date if the project is converted from a demand. The project schedule is not applied to this date and the date remains unchanged when you add project tasks to your project. This field is highlighted with in red if the date in this field is set prior to the date in the **Planned end date** field.**Note:** The approved end date of the project is also carried forward to any sub-project associated with the project.\n\n |
| \n\nPlanned start date\n\n | \n\nThe start date of the project tasks within the project. This date is rolled up from the project tasks. This date is copied from the **Approved start date**. After planned tasks are added, this value is set to the earliest time that the project schedule allows. For example, if the project task is created at 3 a.m. and the default schedule is in use \\(which has an 8 a.m. start date\\), then the default task start is 8 a.m. the next day.\n\n **Note:** The planned start date must be within 10 years of the current date. The [project property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/r_InstalledWithProjectManagement.md) **Max date span into future or past from the current date** controls the behavior for project planned start date.\n\n When you convert a demand to a project, the start date of the demand is carried forward as the **Planned start date** for the project. If the demand start date is a weekend and your project follows a project schedule, the **Planned start date** is adjusted to the first working day of the week.\n\n When you create the project from My Projects Space page, the **Planned start date** field is automatically populated. You must select the calendar icon and select a date to start the project. Projects do not automatically start on the planned start date.\n\n **Note:**\n\n- When you change the planned start date of a project, the associated cost plans and resource plan also change. The [project property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/r_InstalledWithProjectManagement.md) **Change Resource Plan and Cost Plan Start Date with Demand or Project Start Date Change** controls the behavior for project start date change.\n- This field is not available when creating a project by default. Use the **Approved start date** field to specify the project start date. Configure the form to display this field. However, this field is available for existing projects and projects converted from a demand.\n\n |
| \n\nPlanned end date\n\n | \n\nThe end date of the project tasks within the project. After you add tasks, the value in the field is calculated from the tasks. For a manual project, any update to the actual start date does not update the planned end date of the project. Enable the project property **Enable alter of planned date with Actual for Manual Project** to update the planned end date from the actual start date and planned duration.\n\n **Note:** This field is not available when creating a project by default, use the **Approved end date** field to specify the project end date. Configure the form to display this field.\n\n When you convert a demand to a project, the due date of the demand is carried forward as the **Planned end date** for the project. If the demand due date is a weekend and your project follows a project schedule, the **Planned end date** is adjusted to the first working day of the week.\n\n |
| \n\nPlanned duration\n\n | \n\nExpected duration of the tasks within the project. After you add tasks, the value in the field is calculated from the duration of the tasks. The duration also considers the project schedule, accounting for any non-work time in the schedule. **Note:** The [project property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/r_InstalledWithProjectManagement.md) **Max duration \\(in days\\) allowed for a project/project task** controls the behavior for project planned duration.\n\n For example, if the default schedule is used, with a standard 8-hour work day, a project that starts at 8 a.m. on 1 July and ends at noon on 2 July is calculated as 1 day and 4 hours, not 28 hours.\n\n |
| \n\nPlanned effort\n\n | \n\nEstimate of the time that it takes to complete the project. This calculation sums up planned effort values for all tasks and stories \\(in the case of Agile and Hybrid projects\\) in this project. After you add tasks, this field becomes a read-only, roll-up calculation and overwrites any earlier entry that you made.\n\n |
| \n\nActual start date\n\n | \n\nDate on which the planned tasks start.\n\n The time component in the actual start and end dates depends on the value of the **Derive time component from planned dates** field in the **Preferences** tab when you manually populate the actual dates.\n\n However, when you change the **State** or **Percent complete** of the project, the actual dates are auto-populated with the time component copied from the planned dates. The value of the **Derive time component from planned dates** field has no effect on the time component of actual dates in this case.\n\n |
| \n\nActual end date\n\n | \n\nDate on which the planned tasks ends.\n\n |
| \n\nActual duration\n\n | \n\nDuration of the project tasks from project start to project closure. As with the planned duration, the actual duration shows the total project time and takes the project schedule into consideration.\n\n |
| \n\nActual effort\n\n | \n\nActual number of hours charged to the resources on this project. If you are using the Time Cards application, it automatically calculates the value for this field. It uses the totals for the time worked from the approved time cards of all the resources who worked on a project and all its tasks.**Note:** The actual effort from the stories for Agile and Hybrid projects is also rolled up to the project's actual effort.\n\n The field is not editable if the **Update actual effort from time card** field is set to **Yes** on the **Preferences** tab.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nPortfolio\n\n | \n\nPrimary portfolio to which the project belongs. A project can belong to multiple portfolios. **Note:**\n\n- If a project, for which the **Portfolio** field is not set is associated to a portfolio using the portfolio form, then the portfolio name is populated in the **Portfolio** field.\n- If a portfolio is deleted, the portfolio name is removed from the **Portfolio** field on the Project form.\n\n |
| \n\nProgram\n\n | \n\nProgram to which the project belongs.**Note:** If the **Portfolio** field is not set, you can select from the list of all programs in the system. If the **Portfolio** field is set, you cannot select programs that belong to other portfolios.\n\n |
| \n\nInvestment Class\n\n | \n\nType of investment class category assigned to the project:- **Run**: Investment made to sustain the existing business.\n- **Change**: Investment made to implement a change in business.\n\n |
| \n\nInvestment Type\n\n | \n\nInvestment type of the project.- Cost Reduction\n- End User Experience\n- Legal and Regulatory\n- Revenue Generating\n- Service Sustaining\n- Strategic Enabler\n- Artificial Intelligence\n\n |
| \n\nExecution Type\n\n | \n\nExecution methodology used to run the project: **Waterfall**, **Agile**, and **Hybrid**. The default value is **Waterfall**.\n\n The **Execution Type** field selection determines the related links and related lists that are available. For example, the **Agile Planning & Tracking** related link appears when you set the Execution Type value to **Agile**. You must have the appropriate plugins such as Agile Development 2.0 and Test Management to view these related links and related lists. Also, you must have the appropriate role to use these related links and related lists.\n\n |
| \n\nDemand\n\n | \n\nDemand from which the project was created. The field is visible only if the project has a demand associated to it.**Note:** When a demand gets converted into a project, the data on **Business Case** tab gets carried forward from demand to project.\n\n |
| \n\nPhase\n\n | \n\nCurrent phase of the project. In addition to the **Phase** field, the different project phases are also shown at the top of each project record. The selected phase is highlighted.\n\n The default phases are **Initiating**, **Planning**, **Executing**, **Delivering**, and **Closing**.\n\n |
| \n\nDepartment\n\n | \n\nDepartment in a business unit to which the project belongs.\n\n |
| \n\nBusiness Unit\n\n | \n\nBusiness unit to which the project belongs.\n\n |
| \n\nImpacted Business Units\n\n | \n\nBusiness unit that is impacted by the project.\n\n |
| \n\nBusiness Capabilities\n\n | \n\nIf the project is to change, enhance, or add one or more business capabilities, those capabilities can be associated with the project. Business capabilities are defined in the Application Portfolio Management module.\n\n |
| \n\nBusiness Applications\n\n | \n\nIf the project is to change, enhance, or add one or more business applications, those applications can be associated with the project. Business capabilities are defined in the Application Portfolio Management module.You can select any business application in your enterprise regardless of whether it is related to the capability selected in the **Business Capabilities** field.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nStrategies\n\n | \n\nStrategic objectives of the organization that the project fulfills. A project can fulfill multiple strategic objectives.If a **Business Unit** for the project is selected in **Details** tab, then the list displays the business strategies for the selected business unit along with other enterprise strategies.\n\n |
| \n\nGoals\n\n | \n\nGoals associated with the selected strategy. A project can fulfill multiple goals.If a strategy is not selected, then all goals are displayed in the list.\n\n |
| \n\nBusiness case\n\n | \n\nBusiness arguments that support the project.\n\n |
| \n\nRisk of performing\n\n | \n\nRisks associated if the project is carried out.\n\n |
| \n\nRisk of not performing\n\n | \n\nRisks associated if the project is not carried out, for example, risk of loss of opportunity.\n\n |
| \n\nEnablers\n\n | \n\nKey enablers for the project.\n\n |
| \n\nBarriers\n\n | \n\nMajor barriers to the project.\n\n |
| \n\nIn scope\n\n | \n\nScope of the project. The scope is the set of boundaries that define the extent of a project.\n\n |
| \n\nOut of scope\n\n | \n\nActivities or deliverables that are not in the scope of the project. Anything that is not defined in the scope is out of scope.\n\n |
| \n\nAssumptions\n\n | \n\nAssumptions made for the project. Assumptions help define scope and risks, and fine-tune the estimates for time and cost.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nRate Model\n\n | \n\nRate model assigned to the project. The [rate model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/rate-model/rate-model.md) is used to derive hourly rates for the associated resource plans and time cards.\n\n When you create a project from a demand, the rate model is copied from the demand to the project.\n\n The subprojects in a project derive their resource plan calculations from the rate model associated with the top task.\n\n If the assigned rate model is removed or replaced or the hourly rates in the rate model are changed, the cost fields on the associated resource plans are not recalculated automatically. You must [update costs of all resource plans in the project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/recalculate-resource-costs-of-a-project.md) using the **Recalculate Resource Costs** menu option to reflect new rates from the rate model.\n\n You can also [update costs of a single resource plan one at a time](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/resource-management/recalculate-resource-costs.md).\n\n |
| \n\nTotal planned cost\n\n | \n\nEstimated cost of the project. If an operational expenditure, capital expenditure, or both are associated with the project, then the planned cost is the sum of the operational expenditure and capital expenditure, which is in the selected currency for the project.\n\n For Agile and Hybrid projects, the planned cost for stories is considered when the resource plan is created for Agile assignment group.\n\n **Note:** To create a resource plan for Agile assignment group, you must assign the pps\\_resource role to the group.\n\n |
| \n\nPlanned capital\n\n | \n\nCapital expenditure \\(Capex\\) for the project. If no cost plans are associated with the project, the **Planned capital** field is editable. Select a currency type and enter a value.\n\n |
| \n\nPlanned operating\n\n | \n\nOperational expenditure \\(Opex\\) for the project. If no cost plans are associated with the project, the **Planned operating** field is editable. Select a currency type and enter a value.\n\n |
| \n\nBudget cost\n\n | \n\nBudgeted cost for this project. This field is automatically populated from the project budget breakdowns in the cost plan breakdown table. When project funds are allocated for a fiscal year, the cost plan breakdown stores the budget allocation for each fiscal period. These amounts are rolled up and stored in the budget cost. To manually enter a value, select a currency icon and enter the value.\n\n |
| \n\nActual cost\n\n | \n\nActual cost of this project. Select a currency icon and enter a value.\n\n |
| \n\nEstimate at completion\n\n | \n\nSum of all actuals for past fiscal periods added to the planned cost for future fiscal periods.**Note:** The current month is considered as a future month for EAC calculation purposes.\n\n For example, if the duration of a project is from January 01 to December 31 and you check the Estimate at Completion in the month of May, it is calculated as: `Sum of actuals from Jan to April + Sum of planned cost from May to December`.\n\n |
| \n\nPlanned benefit\n\n | \n\nPlanned benefit for the project.This value is rolled up from the benefit breakdown of the project.\n\n You can also enter the value manually. Select a currency icon and enter a value.\n\n |
| \n\nPlanned return\n\n | \n\nThe **Planned return** value is derived from the difference between the **Planned benefit** and **Planned cost** values:\\(The value in the **Planned benefit** field – the value in the **Planned cost** field.\\)\n\n |
| \n\nPlanned ROI%\n\n | \n\nThe ROI \\(return on investment\\) percentage result is calculated based on values in the **Planned return** and **Estimated cost** fields.`(Planned return/Estimated cost x 100)`\n\n |
| \n\nDiscount Rate %\n\n | \n\nProject discount rate. The discount rate is the interest rate to determine the present value of future cash flows.\n\n |
| \n\nNet present value\n\n | \n\nPresent value of future cash based on the given annual interest rate.This value is a measure for comparing money spent today against future expected financial benefits. This information is useful when evaluating the overall investment performance.\n\n For example, at 12% discount rate, $1.00 today is worth $0.80 in two years. Therefore, expecting to receive $1.00 in two years is the same as receiving $0.80 today.\n\n Net present value \\(NPV\\) is calculated from the estimated cost per year, the planned benefit per year, and the discount rate for the project.\n\n |
| \n\nInternal rate of return %\n\n | \n\nAnnual interest rate required to achieve an NPV of zero.Internal rate of return \\(IRR\\) helps to determine which projects can deliver a higher rate of return in terms of revenue.\n\n |
| \n\nEstimate to completion\n\n | \n\nSum of all planned costs for future fiscal periods.You can define the frequency to calculate EAC and ETC values to match with the expense lines. Navigate to **System Definition** > **Scheduled Jobs**, select the **Calculate Project Completion Estimates** job, and set the frequency using the Run list.\n\n **Note:** The current month is considered as a future month for ETC calculation purposes.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nRisk Score\n\n | \n\nCalculated based on the project risk.\n\n |
| \n\nValue Score\n\n | \n\nCalculated based on the ROI% of the project.\n\n |
| \n\nSize Score\n\n | \n\nCalculated based on the value in the **Planned Cost** field.\n\n |
| \n\nScore\n\n | \n\nCalculated based on the individual scores of the attributes **Risk Score**, **Value Score**, and **Size Score**, which in turn are calculated based on the risk, planning ROI%, and estimated cost attributes on a project, respectively. **Note:**\n\n- You can configure the formula for score calculation.\n- When a demand is converted to a project, the score calculated on the demand is carried forward to the project.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nAllow time card reporting on\n\n | \n\nLevel at which the [time cards](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateATimeCard.md) for project tasks can be created:- **Project only**: All time cards for the project are created at the project level only. For example, if a user is assigned to multiple tasks in a project, then the time spent on all tasks is recorded under one time card only for the project.\n\n**Note:** In the [Time Sheet Portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/worker-portal.md), tasks, the project are listed on the **Tasks** tab. For these tasks, the **Add to Time Sheet** and **Add selected to Time Sheet** options are not available. Only the **Quick Add** option is available. On selecting **Quick Add**, a time card is created against the top project, not against the task.\n\n- **Project tasks only**: Separate time cards are created corresponding to each planned task.\n\n**Note:** In the Time Sheet Portal, the **Add to Time Sheet**, **Quick Add**, and **Add selected to Time Sheet** options are not available for the project.\n\n- **Project and project tasks**: Time cards can be created at the project level as well as the project task level. The default value is **True**.\n- **No time reporting**: No time cards are created for the project. If the user submits the time card manually, the business rules prevent the user from submitting the time card.\n\n**Note:** In the Time Sheet Portal, the **Add to Time Sheet**, **Quick Add**, and **Add selected to Time Sheet** options are not available for both project and project tasks.\n\n\n |
| \n\nUpdate actual effort from time card\n\n | \n\nDetermines whether the **Actual effort** field on the **Dates** tab should be updated based on the hours entered in the time cards for the project. If the field is set to **Yes**, then the **Actual effort** field is not editable. If it is set to **No**, then the actual hours from time cards are not rolled up to the project and task. By default, the field is set to **No**.\n\n |
| \n\nCalculation\n\n | \n\nType of calculation to use for task dependencies: - **Manual**: Task dates do not reflect any changes made to dependencies.\n- **Automatic**: Task dates are automatically updated to reflect any changes made to dependent or child tasks.\n\n |
| \n\nShow on Program Status Report\n\n | \n\nOption to specify whether the project and its key aspects such as cost, resource, scope, and schedule should be included in the status report of the program to which the project belongs.Default: Selected\n\n |
| \n\nConstraint date\n\n | \n\nA read-only field that displays the project's planned start date. The date in this field is used for calculate the start date of the tasks with **Start ASAP** constraint. Use the **Move Project** related link to change the constraint date. Changing this date also changes the start date for all the tasks with **Start ASAP** constraint. For more information, see [Change the planned start date of a project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/change-planned-start-date-of-project.md).\n\n |
| \n\nDerive assignee list from resource plan\n\n | \n\nOption to constrain the resources in the **Assigned to** and **Additional assignee list** fields on the project and project task forms to be derived only from the associated allocated resource plans.\n\n |
| \n\nRecalculate score on project change\n\n | \n\nDetermines whether to recalculate and update the project score.- If the value of the field is set to **Yes**, the project score is recalculated when the projects planned ROI%, estimated cost, or risk is modified.\n- If the value of the field is set to **No**, the project score remains the same even if the project's planned ROI%, estimated cost, or risk is modified. The value of the field can be set to **No** when the user wants to preserve the score value while converting the project to a demand.\n\n |
| \n\nProject schedule date format\n\n | \n\nDetermines whether the dates in the planning console should be displayed with the time component. The default is **Date**.\n\n |
| \n\nDerive time component from planned dates\n\n | \n\nDetermines whether the time component in the actual start and end dates should be copied from the time component in the planned start and end dates. By default, it is set to **True**.If the **Project schedule date format** field is set to **Date**, this option is selected and inactivated.\n\n **Note:** When you change the **State** or **Percent complete** value for the project, the actual dates are auto-populated with the time component copied from the planned dates. The value of the **Derive time component from planned dates** field has no effect on the time component of the actual dates in this case. The value of the field affects the time component only when you populate the actual dates manually.\n\n |