Create New Pipeline Project form
Use the Create New Pipeline Project form to provide details about the pipe project.
| Field | Description |
|---|---|
| Pipeline Project | |
| Number | An auto-generated number that uniquely identifies the pipeline project. |
| State | The current state of the pipeline project. Available values:
|
| Priority | Indicates how quickly you must complete the pipeline project. |
| Project type | Specifies the type of project based on the sourcing objective. Available values:
|
| Assigned to | Person assigned to the pipeline project. |
| Short description | Name of the pipeline project. |
| Description | Description of the pipeline project. |
| Project summary | |
| Opportunity source | The source of the pipeline project. This field takes its value based on where the pipeline is created.
|
| Business owner | The person who initiates the pipeline project and provides key input and approvals. |
| Spend category | Spend category used to report on savings. |
| Business unit | The business unit associated with the pipeline project, such as IT, Finance, HR, or Sales. |
| Estimated start date | The projected date when the project is expected to begin. |
| Estimated end date | The projected completion date for the pipeline project. This field reflects the due date specified in the sourcing request. If the pipeline project is associated with multiple sourcing requests, the earliest due date among them is used. |
| Actual start date | Actual start date of the pipeline project. Note: This field is automatically populated when the pipeline project moves to the Work in Progress state. |
| Actual end date | Actual end date of the pipeline project. Note: This field is automatically populated when the pipeline project moves to the Close Complete state. |
| Savings start date | The date from which savings are expected to begin. Note: This field becomes mandatory when the pipeline project moves to the Planned state. |
| Savings end date | The date until which savings are expected to be captured. Note: This field becomes mandatory when the pipeline project moves to the Planned state. |
| Financials | |
| Estimated spend | The anticipated expenditure for the goods or services covered by the pipeline project. |
| Annual hard savings | The measurable, recurring cost reductions achieved each year as a result of sourcing activities, contract negotiations, or process improvements. |
| Annual cost avoidance | The estimated yearly savings realized by preventing future costs or price increases through proactive sourcing strategies or negotiations. |
| Estimated hard savings | The projected, quantifiable cost reduction expected from the pipeline project, typically derived from direct price decreases or efficiency gains. |
| Estimated cost avoidance | The projected financial benefit resulting from mitigating potential cost increases, avoiding additional expenses, or improving purchasing efficiency. |
| Other savings | Any additional savings achieved that don't fall under hard savings or cost avoidance categories. |
| Final spend | The actual amount spent at the completion of the pipeline project. |
| Lost savings | Forecasted savings that were not realized due to delays, project cancellations, or scope changes. |
| Associated records | |
| Previous record type | The classification of the preceding project record. |
| Previous record ID | The unique identifier of the previous related project or sourcing record, used for reference. |