Procurement
Procurement is where a purchase need turns into a paid contract. An employee picks a project and submits a request from the Employee Portal; Procurement reviews and approves it as a requisition; an approved requisition becomes an RFQ (request for quote) sent to invited vendors; the strongest quote is awarded; and the award becomes a contract. Vendors sits alongside that pipeline as the directory Procurement invites quotes from.
Every request needs an eligible project
About Testing Hub
The rest of this section follows Testing Hub, the same organization used throughout these docs. Procurement is enabled for it, but nobody has used it yet: zero vendors, zero requisitions, zero RFQs, and zero contracts on file. Testing Hub also has no projects at all yet, so right now its New procurement request button in the Employee Portal is disabled, with the tooltip "No project has completed its Plans (P1) checklist yet." Where Testing Hub has no real example to point to, these pages describe what the screen shows and what happens when you use it, rather than inventing data that isn't there.
The sub-components
Each of the following covers everything you can do in that part of Procurement, with real use cases rather than a feature list.
- Requisitions: Review employee purchase requests and move them through the pipeline
- Vendors: The vendor directory Procurement sources from and invites to quote
- RFQ/RFP: Turn an approved request into a quote request, then award a vendor
- Contracts: Register the agreement with the awarded vendor and track its status
Two separate vendor lists