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:- Draft - Planned - Work in Progress - Closed Complete - Closed Canceled |
| Priority | Indicates how quickly you must complete the pipeline project. |
| Project type | Specifies the type of project based on the sourcing objective. Available values:- Supplier Optimization – Consolidating suppliers to reduce spend - Contract Optimization - Renegotiating an existing contract - Savings Potential – Using market intelligence to potentially lower spend - Spend Optimization – Use sourcing events \(RFI, RFQ, RFP\) to lower spend - Risk Reduction – Supplier issues or backup for an existing supplier |
| 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. - Intake Request: When the pipeline project is created from the Employee Center intake request. - Adhoc: When the Sourcing Manager or Procurement Specialist manually create the from the list view in Source-to-Pay Workspace. - System-generated: When the pipeline project is created by AI. |
| 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. |
| Actual end date | Actual end date of the pipeline project. |
| Savings start date | The date from which savings are expected to begin. |
| Savings end date | The date until which savings are expected to be captured. |
| Financials | |
| Estimated spend | The anticipated expenditure for the goods or services covered by the pipeline project. |
| Hard savings | Direct, measurable cost reductions resulting from the pipeline project. |
| Targeted savings | The savings goal set for the pipeline project. |
| Cost avoidance | Potential costs prevented through negotiation, process changes, or alternative sourcing. |
| Final spend | The actual amount spent at the completion of the pipeline project. |
| Other savings | Any additional savings achieved that don't fall under hard savings or cost avoidance categories. |
| 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. |
Parent Topic:Sourcing and Procurement Operations reference
Related topics
Base system procurement case type reference
Pipeline project record tabs and UI actions
Purchase requisition, purchase order, and sourcing request states
SPO and ITAM data model mappings