Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Create demand form

Create a demand for your application or capability.

FieldDescription
AssumptionsAssumptions made for the demand. Assumptions help to define scope and risks, and fine-tune the estimates for time and cost.
Approved end dateThe approved date for completing the demand.
Approved start dateThe approved date for starting the demand.
ActionCourse of action for the demand.
BarriersMajor barriers to the demand.
Business capabilitiesOne or more capabilities to associate the demand with.
Impacted business applicationsBusiness applications that are impacted by the demand.
Capital budgetTotal capital budget allocated to the demand across all fiscal years. The value is rolled up from the Capital expenditure \(Capex\) budget of the demand.
Category

Category of the demand. The available options are:

  • Strategic
  • Operational
Business unitBusiness unit to which the demand submitter belongs.
Capital expenseCapital expenditure \(Capex\) for the demand.
Business caseBusiness arguments that support the demand.
CollaboratorsUsers who can edit or contribute to the demand. A demand requester can select any user as a collaborator.
Demand managerName of the demand manager.
DemandThe name of the demand.
EnablersKey enablers of the demand.
Demand actual costTotal cost incurred while working on a demand and demand tasks. Note: To populate this field, you must run the Update Demand Actual Cost and Actual Effort schedule job.
Demand actual effortTime accrued or spent by a resource while working on a demand or a demand task. Note: To populate this field, you must run the Update Demand Actual Cost and Actual Effort schedule job.
Financial returnResult is calculated based on values in the Total costs and Financial benefit fields.
Risk levelThe level of risk associated with the demand. The available options are: - Critical - High - Moderate - Low - Planning
Financial benefitEstimate 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 %Assesses demand return on investment \(ROI\) compared to other demands.
Impacted business unitsBusiness unit that is impacted by the demand.
Labor costsExpenses associated with the manpower required to work on the demand.
In scopeScope of the demand. It’s the set of boundaries that define the extent of a demand.
Operating budgetTotal operational budget allocated to the demand across all fiscal years. The value is rolled up from the Operational expenditure \(Opex\) budget of the demand.
Related recordsRecords associated with the demand.
Risk of not performingRisks if the demand is not approved, for example, risk of loss of opportunity.
Due dateRequested completion date of the demand.
Risk of performingRisks if the demand is approved and implemented.
Operating expenseOperational expenditure \(Opex\) for the demand.
Other costsOther miscellaneous costs associated with the demand.
Out of scopeActivities or deliverables that aren’t in the scope of the demand. Anything which isn’t defined in the scope is out of scope.
CostTotal cost associated with the demand.
ScoreDemand score is calculated based on Risk, Value, and Size attributes in the base system. - 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.
RiskRisk value calculated from the demand assessment.
Strategic AlignmentA value to assess how closely the demand aligns with the strategic goals of the organization.
ValueBusiness value of the demand.
Type

Type of the demand. The available options are: - Project - Change

The Category field selection determines the options available in the Type field.

SizeSize of the demand.
T-shirt size

Categorizing the demand into different sizes, to give a quick understanding of the relative complexity of the demand and the effort required for its completion.

The available sizes are:

  • S- Small
  • M- Medium
  • L- Large
  • XL- Extra Large
  • XXL- Extra Extra Large
StageThe current state of progression of the demand.
Start dateStart date of the demand.
Submitted onDate on which the demand was submitted for approval.
Total planned costResult is calculated based on values in the Capital expense and Operating expense fields.
Visited states

The different states through which the demand has passed through.

For example, the demand has gone through the states of Open and Closed. The visited state number in this scenario will be 2.

Primary goalThe primary goal behind the creation of the demand
Digital integrationDigital integration associated with the demand.

Parent Topic:Enterprise Architecture Workspace reference

Related topics

Exploring demands

Add or edit a demand