Demand form

  • Release version: Xanadu
  • Updated August 1, 2024
  • 12 minutes to read

    • The demand form information is used to create a demand.

    Table 1. Demand form fields
    Field Description
    Name

    Name of the demand.
    Category Category of the demand:
    • Strategic: For demands for plans, such as projects or stories.
    • Operational: For demands for operational work, such as changes or defects.
    Type The Category field selection determines the selections available in the Type field.
    • The following demand types are available if the demand category is Strategic:
      • Continual Improvement Management
      • Enhancement
      • Project
      • Epic
      • Story
      • SAFe Epic
      • SAFe Story
      • SAFe Feature
      • No Conversion
    • The following demand types are available if the category is Operational:
      • Change
      • Defect
      • No Conversion

    If the Agile Development 2.0 application is active, the Story, Epic, Enhancement, and Defect options are available.

    If the Essential SAFe or Portfolio SAFe features are active, the SAFe Story, SAFe Feature, and SAFe Epic options are available.

    The No Conversion option enables you to use your demand to fund a large project that includes one or more projects, epic, or programs.

    The selections in the Category and Type field also determine the fields that are displayed in the Assessment Data section.
    Project Name of the project created from this demand.

    This read-only field is visible only when you convert the demand into a project.
    Enhancement Number of the enhancement created from this demand.

    This read-only field is visible only when you convert the demand into an enhancement.
    Epic Name of the epic created from this demand.

    This read-only field is visible only when you convert the demand into an epic.
    Story Name of the story created from this demand.

    This read-only field is visible only when you convert the demand into a story.
    Number Unique, auto-generated identification number for the demand.
    Approved start date The formal date approved by stakeholders for starting the demand. This date is set after prioritization and stakeholder approval and represents the committed and authorized timeline for execution. It’s used for governance and traceability.

    For example, the approved date to start the database upgrade is 2026-01-10.

    This field is carried forward to the Approved start date field of the Project form if the demand is converted to a project and remains unchanged, even if the project starts later.

    This field is highlighted in red if the date is different than the value in the Start date field.

    Note:
    If this field is empty while creating a demand, the date from the Start date field is inserted.
    Approved end date The formal date approved by stakeholders for completing the demand. This date is set after prioritization and stakeholder approval and defines the approved execution window and supports historical tracking.

    For example, the approved end date to complete the demand is 2026-02-15.

    This field is carried forward to the Approved end date field of the Project form if the demand is converted to a project and remains unchanged, even if the project ends later.

    This field is highlighted in red if the date in this field is different than the value in the Due date field.

    Note:
    If this field is empty while creating a demand, the date from the Due date field is inserted.
    Start date The preliminary or estimated date when the work is initially planned to begin. This date helps outline the intended timing for early demand planning and prioritization. You can set this date during initial demand creation or anytime in the planning phase when a rough idea forms. This date can be updated until the demand is officially approved.

    For example, you’re planning for a database upgrade to start on 2025-11-01.

    This date is changed to Planned start date when the demand is converted to a project.
    Note:
    When you change the planned start date of a demand or project, the associated cost plans and resource assignments also change. The Change Resource Plan and Cost Plan Start Date with Demand or Project Start Date Change property controls the behavior for a demand date change. This property isn’t enabled by default. For more information, see and Properties installed with Project Management.
    Due Date The preliminary or estimated date when the planned work is expected to be completed. This date provides an expected completion window for planning and stakeholder communication. You can set this date anytime in the planning phase when a rough idea forms and can be updated until the demand is officially approved.

    For example, you’re planning to complete the database upgrade by 2025-12-31.

    This date is changed to Planned end date when the demand is converted to a project.
    Description Description of the demand.
    Similar demands Demands that have similar values for the Short description fields using predictive intelligence and machine-learning algorithms. For more information, see Predictive Intelligence for Demand Management.
    Related Search Search results matching the specified term. The default is the value in the Name field.
    Table 2. Details section of the Demand form
    Field Description
    Portfolio Portfolio indicating the business focus of the demand.
    Program Name of the program to which the demand belongs.
    Investment Class Type of investment class category assigned to the demand:
    • Run: Investment made to sustain the existing business.
    • Change: Investment made to implement a change in the business.
    Investment Type Investment type of the demand:
    • Cost Reduction
    • End User Experience
    • Legal and Regulatory
    • Revenue Generating
    • Service Sustaining
    • Strategic Enabler
    • Artificial Intelligence
    Demand Manager Name of the demand manager.
    Collaborators Users who can edit or contribute to the demand. A demand requester can select any user as a collaborator.
    Expense type The type of the expense, either capex (capital expense) or opex (operational expense).
    Priority The priority of the demand.
    Department Department in a business unit to which the demand submitter belongs.
    Note:
    If you don’t select a department, the default value is the name of the department to which the submitter belongs.
    Project Manager Project manager that would be assigned to the project created from this demand. When a project is created, this field becomes read only. This field appears if the Category field is set to Strategic and the Type field is set to Project. If you delete the project created from this demand, this field becomes editable.
    Business Unit Business unit to which the demand submitter belongs.
    Impacted Business Units Business units affected by the submitted demand. The selected units could experience operational impact, process changes, technology adoption, and so on.

    For example, if a demand is submitted by the procurement business unit, it can impact the finance, legal, and IT business units.
    Idea Unique identification number of the idea from which the demand was created.
    Business Capabilities Business capabilities associated with the demand that links the demand to organizational goals and value. Business capabilities are defined in the Enterprise Architecture (formerly Application Portfolio Management) module.
    Impacted Business Applications If the demand is to change, enhance, or add one or more business applications, the applications associated with the demand. Business applications are defined in the Enterprise Architecture (formerly Application Portfolio Management) module. For more information, see Business applications.

    You can select any business application in your enterprise regardless of whether it’s related to a capability selected in the Business Capabilities field.
    Business Applications If the demand is to change, enhance, or add one or more business applications, the applications associated with the demand. Business applications are defined in the Enterprise Architecture (formerly Application Portfolio Management) module. For more information, see Business applications.

    You can select any business application in your enterprise regardless of whether it’s related to a capability selected in the Business Capabilities field.
    Table 3. Business Case section of the Demand form
    Field Description
    Strategic priority Strategic objectives of the organization that the demand fulfills. A demand can fulfill multiple strategic objectives.

    If a business unit has been selected in the Details tab, the business strategies for the selected business unit along with other enterprise strategies are available for selection.
    Primary goal The primary goal associated with the strategy selected in the Strategic priority field.

    If a strategy hasn’t been selected, all goals are available for selection.
    Business case Business arguments that support the demand.
    Risk of performing Risks if the demand is approved and implemented.
    Risk of not performing Risks if the demand isn’t approved, for example, risk of loss of opportunity.
    Enablers Key enablers for the demand that would aid the demand to be completed. For example, clearly defined resource and cost plans.
    Barriers Major barriers to the demand that would obstruct the demand's completion. For example, incomplete or unclear demand details.
    In scope Scope of the demand, which is the set of boundaries that define the extent of a demand.
    Out of scope Activities or deliverables not in the scope of the demand. Anything not defined in the scope is out of scope.
    Assumptions Assumptions made for the demand. Assumptions help to define the scope and risks, and fine-tune the estimates for time and cost.
    Table 4. Financials section of the Demand form
    Field Description
    Rate Model Rate model assigned to the demand. This setting is used to derive hourly rates for the associated resource assignments and time cards. For more information, see Rate Models.
    Note:
    If the rate model assigned to the demand is changed or removed, the cost fields on the associated resource assignments aren’t recalculated.
    Project Currency Currency used to execute the project once the project is created from this demand.

    You can select any active currency from the values listed in the Currency [fx_currency] table.

    After you create a project in the selected project currency, you can't change the project currency in the Project form if the demand contains a cost plan, a benefit plan, or a project budget. If the demand has no attached plan or budget, you can change the project currency in the Project form.
    Note:
    The value of this field defaults to the Project currency field of the Financials tab in the project currency view of the Project form as well. This field is available only when the PPM Standard Multicurrency (com.snc.ppm_multicurrency) feature is activated and the Demand Currency view is enabled.
    Capital expense Capital expenditure (capex) for the demand.
    Operating expense Operational expenditure (opex) for the demand.
    Total planned costs Result calculated based on the values in the Capital expense and Operating expense fields.
    Financial return Result calculated based on the values in the Total costs and Financial benefit fields.
    Financial benefit Estimate of revenue if the demand is approved.

    This value is rolled up from the benefit breakdown of the demand.

    You can also enter the value manually by selecting a currency icon and entering a value.
    ROI % ROI calculated based on the values in the Total costs and Financial return fields.

    The value in this field is updated when a cost plan, benefit plan, or resource assignment is created or updated for the demand in the Qualified or Approved state.
    Capital budget Total capital budget allocated to the demand across all fiscal years.

    The value is rolled up from the capex budget of the demand.
    Operating budget Total operational budget allocated to the demand across all fiscal years.

    The value is rolled up from the opex budget of the demand.
    Discount Rate % Demand discount rate, which is the interest rate to determine the present value of future cash flows.
    Net present value Present value of future cash based on the given annual interest rate, a measure for comparing money spent today against future expected financial benefits. This value is useful when evaluating the overall investment performance.

    For example, at a 12% discount rate, $1.00 today is worth $0.80 in two years. Therefore, receiving $1.00 in two years is the same as receiving $0.80 today.

    Net present value (NPV) is calculated from total costs according to year, financial benefit per year, and the discount rate for the demand.
    Internal rate of return % Annual interest rate required to achieve an NPV of zero.

    Internal rate of return (IRR) helps to determine which demands can deliver a higher rate of return in terms of revenue.
    Demand Actual Cost Total cost incurred while working on a demand and demand tasks. Demand actual cost is calculated after the assignee of the demand task creates and submits a time card. When the time card is approved, the resource rate, which is derived from the rate card, labor rate, or system properties, is used to populate this field.
    Demand Actual Effort Time accrued or spent by a resource while working on a demand or a demand task as derived from the submitted and approved time cards. This field isn’t available on the Demand form by default.
    Note:
    If you’re creating a demand with the PPM Standard Multicurrency (com.snc.ppm_multicurrency) plugin activated and the Demand Currency view enabled, then the fields in the Financials tab differ from the Default view. For more information about the fields that are available only in the Demand Currency view, see Multicurrency in Demand Management.
    Table 5. Assessment Data section of the Demand form
    Field Description
    Impact Level of business impact created by the demand.
    Risk Risk value calculated from the demand assessment.
    Value Business value of the demand calculated from the Impact and Financial return fields.
    T-Shirt size Size of the demand.

    Before using this value as an indicator of demand size, consider creating and publishing definitions for each option outside the application. That process ensures that the values are interpreted correctly and consistently across the organization or department.
    Score The demand score is calculated based on the risk, value, and size attributes in the base system.
    The value of the risk, value, and size attributes are derived from the assessment metric category results. For more information, see assessment categories and assessment category results.
    • When the risk and size values are high, the score of the demand is low.
    • When the value setting is high, the score of the demand is high.
    Assessment Required Option for enabling the assessments for the demand. This option is active by default.

    Only a demand manager can update this value when the demand is in the Draft or Submitted state.

    Note:
    If this option isn’t selected and you reset the demand to the Draft state, the option remains unselected.
    Note:
    The values in the Value and Score fields are updated when a cost plan, benefit plan, or resource assignment is created or updated for the demand in the Qualified or Approved state. The values in the fields are updated only until an artifact such as project, enhancement, defect, or change is created from the demand.
    Table 6. Notes section of the Demand form
    Field Description
    Watch list The groups and users subscribed to the demand who can view the information in the Additional comments field.
    Work notes list The groups and users subscribed to the demand who can view the information in the Work notes field.
    Work notes Information about the demand. This information isn’t visible to customers. Work notes are added throughout the demand management life cycle to communicate with other users associated with the demand.
    Table 7. Preferences section of the Demand form
    Field Description
    Close Demand
    Determines when to close the demand automatically if it’s converted to a project.
    • None: Keeps the demand in the Open state after it’s converted to a project.
    • On creation of project: Closes the demand when the demand is converted to a project.
    • On closure of project: Closes the demand when the project created from the demand is closed.
    Note:
    The On creation of project and On closure of project options appear when the value for the Type field is set to Project. If the Type field is set to Enhancement, the default setting is None.
    Project Calculation Determines the calculation to use for task dependencies for the project when the demand is converted to a project. The default value is Automatic.
    • Manual: Task dates don’t reflect any changes made to dependencies.
    • Automatic: Task dates are automatically updated to reflect any changes made to dependent or child tasks.