Demand Management Overview

Demand Management is a planning methodology used to forecast, plan for, and manage the demand for products and services.

The Demand is the process of organization, which is put internally to collect new ideas, projects, and needs during the creation of the Portfolio.

Demand Management has a proactive process, which can be used as a strategy while addressing/analyzing/collecting new ideas. The process implements a correct prioritization and selection in identifying:

• Objectives and requirements
• Strategic alignment
• Scheduling
• Budget and source of funding
• Level of risk
• Impact on the Organization
• Pre-requisites 

Demand Management's final output will be contained in a single database, as this data will be used many times from now until the implementation.

Demand Management Roles

The following end-user roles are for the Demand Management module of the BMC Helix Portfolio Management application.

Demand Contributor

Demand Contributor can create new demands from the Portfolio Management application. Demand Contributors can only edit demands created by them. Demand Contributor has access to BMC Helix Digital Workplace and Portfolio Management application. Demand Contributors can create ideas from both consoles and can view, vote, and add activity notes in ideas created by them and other contributors as well.

Demand Manager

Demand Manager has all access to Demand Management Console. Demand Managers can create/edit, demands created by them and demands where they are assigned as Demand Managers. Demand Managers can also create new ideas from BMC Helix Digital Workplace and Portfolio Management application. They can view, vote, and add activity notes in ideas created by them and other contributors as well.

Portfolio Manager

Portfolio Manager can create new demands. They can also edit the ones that are present under portfolios and programs, provided they are assigned as the Portfolio Managers or Program Assignees for the respective Portfolios and Programs. The portfolio manager can also create new ideas from BMC Helix Digital Workplace and Portfolio Management application. They can view, vote, and add activity notes in ideas created by them and other contributors as well.

Stakeholders

Stakeholders are related to the demand and they are users of the organization involved in assessing, reviewing, and re-considering the demand based on Cost, Benefits, and the long-term goal for the product. They can access the demand and can create comments but they can not edit the demand. Stakeholders can be related to the demand with the responsibility to approve or reject the demand.

End-to-end process

The following figure provides an overview of the demand lifecycle.

The demand management process consists of the following procedures for handling new demands.

1. Demand contributor logs in to Portfolio Management application and creates a new demand by following the steps in Creating-demands.
2. Demands are created in 'Draft' status. Demand contributor writes all details of that demand for data associated with fields, see Viewing-and-updating-demand-details.
3. Demand contributor updates 'Requested' status (steps defined in Changing-demand-statuses) to start looking into by demand manager. Demands generated from an idea are created in the 'Requested' status whereby the demand manager is associated with the portfolio manager by default. 
4. The demand manager starts looking at the demand with all the details entered by the demand contributor. The demand manager performs the following tasks:
   • creates requirements, see Creating-demand-requirements.
   • identifies risks, see Identifying-risks.
   • introduces stakeholders, see Entering-Stakeholders.
   • collects resources, see Collecting-resources.
5. Once the demand manager finds it useful/needful based on the current details, proceed with the next status 'Investigation' by following the steps in Changing-demand-statuses. If the demand manager does not find it, the required status can be changed to 'Pending' or 'Cancelled'.
6. The demand manager investigates whether this Demand has and can fulfill the organization's goal. Further analysis of the Risk associated, Resources required, Stakeholders' approval, Financial Cost, and Total Budget is investigated in detail with concerned stakeholders of the Demand.
7. The demand manager allocates Resources and Stakeholders for them to approve the demand and puts the demand in 'Assessed' status by following the steps in Changing-demand-statuses.
8. Stakeholders assess, review, and re-consider the demand based on Cost, Benefits, and the long-term goal for the product. Stakeholders can Approve, Reject and Hold the demand by following the steps in Approving-and-rejecting-demands.
9. Once all stakeholders approve, the status of demand moves to 'Approved' automatically, and a new project or a new portfolio is created.
   • If demand creates a new portfolio, then the requirements are copied 'In Backlog' status into the new portfolio automatically.
   • If demand creates a new project, then the requirements are copied into the portfolio to which demand belongs, and a new task is created in 'Backlog' status for each requirement into the new project automatically, relating requirement and task. 
10. If demand creates a new project, the demand is completed automatically when the project is completed, or if demand creates a new portfolio then demand moves to 'Completed' status. 

Demand Management Data Access Model

The Demand Management application uses row-level security (RLS) to control access to the record and fields. RLS is applied by using Security Labels in BMC Helix Innovation Studio. 

The following table describes the Security Labels required for Demand Management: