--- title: Create demand to rationalize software applications description: Create demands to rationalize SaaS and SSO applications by discontinuing software subscriptions, reducing software usage, and migrating users to approved software. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-asset-management/software-asset-management/soft-asset-demand.html release: australia product: Software Asset Management classification: software-asset-management topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Use SAM Workspace, Software Asset Management, IT Asset Management, Asset Management] --- # Create demand to rationalize software applications Create demands to rationalize SaaS and SSO applications by discontinuing software subscriptions, reducing software usage, and migrating users to approved software. ## Before you begin Role required: sam\_admin or sam\_user **Note:** The sam\_admin and sam\_user roles must have the it\_demand\_user role to create demand. The PPM Standard \(com.snc.financial\_planning\_pmo\) plugin must be installed to create demands. The Software Asset Management application includes the following demand actions that are ready for you to use: - Discontinue after expiration - Migrate to approved product - Discontinue immediately - Reclaim licenses - No action ## About this task Use the Overlapping usage view to drive SaaS and SSO application rationalization by viewing the feature level usage of each application. For more information, see [Overlapping usage view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/app-ration.md). ## Procedure 1. Navigate to **Software Asset Workspace** > **Overlapping usage**. 2. Select the **Application feature usage** tab. 3. Select the application in a category for which you want to create a demand. 4. Select **Create demand**. The **Create demand** option is available only when you select an application that you want to create a demand for. 5. On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Name of the demand. |
| Number | Unique auto-generated identification number for the demand. |
| Submission status | Stage of the demand record.- Draft - Submitted - Screening - Qualified - Approved |
| Start date | Start date for the demand.The field name is replaced by **Planned start date** when the demand type is converted to a Project. **Note:** When you change the planned start date of a demand or project, the associated cost and resource plans also change. |
| Due date | Requested completion date for the demand.The field name is replaced by **Planned end date** when the demand type is converted to a Project. |
| Category | Software category of the demand.- Strategic - Operational |
| Type | Type of demand.- Enhancement - Project - Change - Defect The **Category** field selection determines the selections available in this field. |
| Assessment required | Option for enabling the assessments for the demand.By default, the field is selected. When clear, the assessment questionnaire isn’t triggered for the demand. When this field is clear, and you reset the demand to **Draft**, the value for the **Assessment Required** field is retained as clear. |