Demands

Last updated
Save as PDF

Demands represent programs, projects and initiatives of the enterprise, which can be organized into a hierarchy.

You can use demands as a demand management solution to track projects, programs, and initiatives and associate them to other entities (systems, connections, technologies, etc.) to assess their impact on the enterprise. The default impact types are add, modify, test or remove, but you can customize them.

Demands are not intended for use as a day-to-day task management tool.

You can also do the following:

track future demand and capture potential impact to make more informed investment decisions
align current and future demand to approved strategies to ensure you are focused on the right initiatives
view your complete demand portfolio in real-time
use the entry of demands in as your project charter

Demand fields

Field name	Description
Reference ID	The identifier, typically from an external system for integration, import/export, or reference purposes.
Name	Name of the entity record. Names should be descriptive and intuitive.
Description	Description of the entity.
Demand Domain	Category for classifying the entity record. Domain is a way to classify or bucket your Demand initiatives. Tip: * You can use domains to classify demand records any way that you want. Examples could be "Keep the Lights On" vs. "Investment Projects" or "Web Projects" vs. "Infrastructure"
Type	Type of demand, for example: program, project, or initiative.
Priority	The relative criticality of the demand record to the enterprise.
Budget Status	State of the project with respect to the budget allocated for it (on, over or under).
Investment Scale	Classification of the scale of investment for the demand.
Investment Range	Classification of the financial requirements of the demand
Funding Type	Indicates the type of funding that the demand requires, such as capital and/or expense.
Lifecycle State	The state of the entity with respect to enterprise management and planning.
Enterprise Approved	State of the entity with respect to the enterprise approval process.
Start Date End Date	The actual or estimated start date and end date for the demand.
Schedule Status	The status of the demand with respect to the schedule for the demand
Risk Level	Classification of the demand risk to the enterprise.
Business Value	Classification of the demand in the context of business value to the enterprise.
Content Status	State of the entity record. Content status is used to control contributions throughout the lifecycle of an entity. The statuses are as follows, in order: Identified – entity record has been added, perhaps with very minimal information. Planned – entity record has been prioritized for inventory, with a completion date. In Process – entity record is being inventoried, with a completion date. Completed – inventory is complete, but is yet to be reviewed. Approved – inventory has been reviewed and verified.
Detail	Additional information about the entity.
Lifecycle Roadmap	Chart that displays the lifecycle states for the entity graphically in a time frame according to their date ranges (if set).
Links	URLs to online resources that provide additional information about the entity.
Tags	A custom flag that you can add to entity records to group them into a collection or report.