Create demands to capture your strategic and operational demands.

1. Navigate to Demand > Demands > Create New.
   Alternatively, any user can create a demand from the following locations:

   • Service Catalog > Can We Help You > Create a new demand.
   • Self-Service > Demands > Create New.
2. On the Demand form, fill in the fields.

   Table 1. Demand form

   Field	Description
   Name	Name of the demand.
   Category	Category of the demand: Strategic Operational
   Type	Type of demand: Project Enhancement Change Defect The Category field selection determines the selections available in this field. The Enhancement and Defect options only appear if the administrator has activated the Agile Development 2.0 plugin. The selections in the Category and Type field also determine the fields that are displayed in the Assessment Data related list. The Category and Type fields become read-only when a work entity is created from a demand. If you delete the created work entity, these fields become editable.
   Project	Name of the project created from this demand.
   Enhancement	Number of the enhancement created from this demand.
   Change	Number of the change created from this demand.
   Defect	Number of the defect created from this demand.
   Number	Unique, auto-generated identification number for the demand.
   Start date	Start date for the demand. Note: When you change planned start date of a demand or project, the associated cost and resource plans also change. The project property Change Resource Plan and Cost Plan Start Date with Demand or Project Start Date Change controls the behavior for demand date change. This property is not enabled by default.
   Due Date	Requested completion date for the demand.
   Details
   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 business.
   Investment Type	Investment type of the demand.
   Submitted by	User submitting the demand.
   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.
   Department	Department in a business unit to which the demand submitter belongs. Note: If you do not select a department, the value defaults as 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 unit which is impacted due to the submitted demand.
   Idea	Unique identification number of the idea from which the demand was created.
   Business Capabilities	If the demand is to change, enhance, or add one or more business capabilities, they can be associated to the demand. Business capabilities are defined in the Application Portfolio Management module.
   Business Applications	If the demand is to change, enhance, or add one or more business applications, they can be associated to the demand. Business applications are defined in the Application Portfolio Management module. You can select any business application in your enterprise, irrespective of it being related or not related to the capability that you have selected in the Business Capabilities field.
   Business Case
   Strategies	Strategic objectives of the organization that the demand fulfils. A demand can fulfil multiple strategic objectives. If a Business Unit for the demand is selected in Details tab, then the choice list displays the business strategies for the selected business unit along with other enterprise strategies.
   Goals	Goals associated to the selected strategy. A demand can fulfill multiple goals. If a strategy is not selected, then all goals are displayed in the list.
   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 is not approved, for example, risk of loss of opportunity.
   Enablers	Key enablers for the demand.
   Barriers	Major barriers to the demand.
   In scope	Scope of the demand. It is the set of boundaries that define the extent of a demand.
   Out of scope	Activities or deliverables that are not in the scope of the demand. Anything which is not defined in the scope is out of scope.
   Assumptions	Assumptions made for the demand. Assumptions help to define scope and risks, and fine-tune the estimates for time and cost.
   Financials
   Rate Model	Rate model assigned to the demand. The rate model is used to derive hourly rates for the associated resource plans and time cards. Note: If the rate model assigned to the demand is changed or removed, the cost fields on the associated resource plans are not recalculated.
   Capital expense	Capital expenditure (Capex) for the demand.
   Operating expense	Operational expenditure (Opex) for the demand.
   Total planned costs	Result is calculated based on values in the Capital expense and Operating expense fields.
   Financial return	Result is calculated based on 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. Select a currency icon and enter a value.
   ROI %	Result is calculated based on values in the Total costs and Financial return fields. The value in this field is updated when a cost plan, benefit plan, or resource plan is created or updated for the demand in 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. The discount rate 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. It is a measure for comparing money spent today against future expected financial benefits. It helps when evaluating the overall investment performance. For example, at 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 per 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 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 comes after the assignee of the demand task creates and submits a time card. When the time card is approved, the resource rate derived from the rate card, labour rate, or system properties is used to populate this field. Note: If you are upgrading to New York, this field remains blank for existing demands. To populate this field, run the Update Demand Actual Cost and Actual Effort schedule job.
   Demand Actual Effort	Time accrued or spent by a resource while working on a demand or demand task as derived from the submitted and approved time cards. This field is not available on the Demand form by default. Configure the form to add this field if required. Note: If you are upgrading to New York, this field remains blank for existing demands. To populate this field, run the Update Demand Actual Cost and Actual Effort schedule job.
   Assessment Data
   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 T-Shirt size as an indicator of demand size, consider creating and publishing definitions for each option, outside the application. This process ensures that the values are interpreted correctly and consistently across the organization or department.
   Score	Demand score is calculated based on 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 metric categories and their results. When the risk and size are high, the score of the demand is low. When the value is high, the score of the demand is high.
   Assessment Required	Check box for enabling the assessments for the demand. By default the field is selected. When clear, the assessment questionnaire is not triggered for the demand. Only a demand manager can update the field when the demand is in Draft or Submitted state. Note: When this field is clear, and you reset the demand to draft, the value for Assessment Required is retained as clear.
   Note: The values in Value and Score fields are updated when a cost plan, benefit plan, or resource plan is created or updated for the demand in 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.
   Notes
   Watch list	List of groups and users who are subscribed to the demand and who can view the Additional comments.
   Work notes list	List of groups and users who are subscribed to the demand and who can view Work notes.
   Work notes	Information about the demand. Not visible to customers. Work notes are added throughout the demand management life cycle to communicate with other users associated with the demand.
   Preferences
   Project Currency	Currency that is used to run the project once the project is created from this demand. You can select any active currency from the list of values that are listed in the Currency [fx_currency] table.
   Close Demand	Specify when to close a demand automatically when it is converted into a project. None: Select this option if you want the demand to remain in Open state after it's converted to a project. On creation of project: Closes the demand when a 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 on when the value for the Type field is set as Project. If the Type field is set as Enhancement, then None appears as the default option.

3. Click Save to save the record.
   Note: Requesters or collaborators can edit their demand as long as the demand is in the Draft state.