Project Procurement Management
Open in the Padhaiko app12.1 Procurement management process flow
Project Procurement Management encompasses the processes necessary to purchase or acquire products, services, or results needed from outside the project team. In ICT projects, organizations frequently procure cloud infrastructure, enterprise software licenses, specialized cybersecurity audits, networking hardware, or custom software modules from external vendors.
Because procurement involves legally binding contracts between a buyer (the project organization) and a seller (vendor, contractor, or supplier), procurement decisions require rigorous technical, financial, and legal coordination.
Six-Stage Procurement Management Process Flow
- Plan Purchases and Acquisitions: Determine what to buy vs. make in-house, when to acquire it, and how much is needed; produce the Procurement Management Plan and Procurement Statement of Work (SOW).
- Plan Contracting: Select appropriate contract types, prepare standard bid documents (RFP/RFQ/IFB), and establish objective seller evaluation criteria.
- Request Seller Responses: Distribute solicitation packages to qualified vendors, conduct bidder conferences, and collect proposals or bids.
- Select Sellers: Evaluate vendor responses using scoring models and independent estimates, negotiate contract terms, and award the signed contract.
- Administer the Contract: Monitor seller deliverables against SOW and SLAs, manage contract changes, authorize milestone payments, and resolve claims.
- Close the Contract: Verify final deliverables, settle payments and claims, conduct a procurement audit, issue formal written closure, and archive lessons learned.
12.2 Plan purchases and acquisition process, enterprise environmental factor, organizational process assets
12.2.1 Plan Purchases and Acquisitions Process
Plan Purchases and Acquisitions identifies which project needs are best met by purchasing or acquiring products/services from outside the organization versus building them internally. The primary analytical tool is Make-or-Buy Analysis, which compares total life-cycle costs (development, licensing, maintenance, training) alongside strategic factors such as core competency, intellectual property protection, and internal staff availability.
For a constant ongoing cost comparison over periods:
The break-even point occurs where :
12.2.2 Enterprise Environmental Factors and Organizational Process Assets
- Enterprise Environmental Factors (EEFs): External market conditions that shape acquisition choices—availability of capable ICT vendors, market pricing benchmarks, software licensing models, government procurement laws and tax rules, and currency exchange stability.
- Organizational Process Assets (OPAs): Internal organizational guidelines and history—formal procurement policies, pre-approved/qualified seller lists, standard contract templates, legal review checklists, and lessons learned regarding past vendor performance.
Key Outputs:
- Procurement Management Plan: Defines how procurement processes will be managed (contract types, authority limits, lead times, vendor risk handling, coordination with project schedule).
- Procurement Statement of Work (SOW): A clear, unambiguous description of the item or service to be procured so prospective sellers can determine whether they can deliver it (scope, technical specs, SLAs, location, delivery schedule, acceptance criteria).
- Make-or-Buy Decisions: Documented rationale for every component to be built internally or outsourced.
1
An organization needs a Helpdesk Ticketing System for an expected project life cycle and evaluates two options:
- Make (Build In-House): Initial development cost plus ongoing hosting and maintenance cost of .
- Buy (Commercial SaaS): Initial configuration and migration fee plus monthly subscription of .
Determine: (a) the break-even duration in months, (b) the total cost of each option, and (c) which option should be selected purely on cost.
Setting Up Cost Equations ( in months):
Finding the Break-Even Duration (): Equating :
Before , Buy is cheaper; beyond , Make becomes cheaper.
Comparing Total Cost at :
Building in-house saves over .
- (a) Break-even duration: .
- (b) 24-month total costs: Make , Buy .
- (c) Decision: Choose Make (Build In-House), saving over the horizon (assuming internal developer capacity is available).
12.3 Plan contracting process, standard forms, evaluation criteria
Plan Contracting prepares the procurement documents required to solicit proposals from sellers and establishes the contract structure and evaluation criteria that will govern selection.
12.3.1 Contract Types and Risk Allocation
Choosing the right contract type balances cost certainty against scope flexibility by allocating financial risk between buyer and seller:
| Contract Type | How Pricing Works | Risk Bearer | Best ICT Use Case |
|---|---|---|---|
| Firm Fixed Price (FFP) | Fixed total price regardless of seller's actual cost | Seller bears cost-overrun risk | Well-defined scope (e.g., server hardware supply, fixed UI spec) |
| Fixed Price Incentive Fee (FPIF) | Fixed target cost/fee + shared savings/overruns up to a ceiling price | Shared (up to ceiling) | Large software delivery with measurable schedule/cost incentives |
| Cost Plus Fixed Fee (CPFF) | Buyer reimburses all allowable actual costs plus a fixed fee | Buyer bears cost risk | R&D prototypes where scope cannot be fully specified upfront |
| Cost Plus Incentive Fee (CPIF) | Buyer reimburses actual costs plus an incentive fee tied to target performance | Shared within limits | Complex systems integration with shared efficiency targets |
| Time and Materials (T&M) | Fixed unit rate (e.g., USD/hour) plus actual materials, often with a Not-to-Exceed cap | Shared (rate fixed, hours open) | Staff augmentation, agile discovery sprints, urgent consulting |
For Fixed Price Incentive Fee (FPIF) contracts, the Point of Total Assumption (PTA) is the cost point above which the seller bears of every additional dollar of cost overrun:
where .
12.3.2 Standard Procurement Forms
- Request for Information (RFI): Non-binding market inquiry used to discover vendor capabilities, products, and rough pricing before drafting formal requirements.
- Request for Proposal (RFP): Formal solicitation used when the solution requires technical creativity and vendor expertise (evaluated on both technical approach and price).
- Request for Quotation (RFQ) / Invitation for Bid (IFB): Used for standardized, commodity items (e.g., switches, cloud credits, off-the-shelf licenses) where vendors meet exact specifications and award goes primarily to the lowest qualified price.
12.3.3 Evaluation (Source Selection) Criteria
Objective criteria defined prior to issuing the RFP/RFQ prevent bias during selection:
- Understanding of Need & Technical Approach: Architecture quality, security compliance, scalability.
- Life-Cycle Cost: Upfront bid price plus ongoing licensing, cloud hosting, and maintenance costs.
- Technical Capability & Past Performance: Relevant ICT domain experience, client references, CMMI/ISO certifications.
- Management Approach & Staffing: Dedicated team qualifications, delivery methodology, QA practices.
- Financial Capacity, Warranty, and Intellectual Property (IP) Rights: Solvency, SLA uptime guarantees, and source-code ownership.
2
An enterprise signs a Fixed Price Incentive Fee (FPIF) contract for a network security upgrade with:
- Target Cost
- Target Fee
- Ceiling Price
- Share Ratio
Calculate: (a) the Target Price, (b) the Point of Total Assumption (PTA), and (c) the final price the buyer pays if actual allowable cost reaches .
Computing Target Price:
Computing Point of Total Assumption (PTA):
Final Price When Actual Cost Is : First check the shared-formula price:
Because exceeds the Ceiling Price of (as expected since actual cost ), the buyer's payment is capped at the ceiling:
(The seller earns only profit, absorbing of costs above .)
- (a) Target Price: .
- (b) Point of Total Assumption (PTA): .
- (c) Final Price Paid at Actual Cost: (capped at Ceiling Price).
12.4 Request seller response process; Select seller process
12.4.1 Request Seller Response Process
Request Seller Responses focuses on obtaining bids, quotes, or proposals from prospective sellers in a transparent, competitive manner:
- Advertising & Qualified Seller Lists: Publishing open tenders (mandatory in public-sector ICT projects) or inviting pre-vetted vendors from the organization's qualified seller list.
- Bidder Conferences (Vendor Conferences): Formal Q&A meetings held with all prospective sellers simultaneously prior to proposal submission. Every question and answer is documented and shared equally with all bidders so no vendor receives an unfair information advantage.
12.4.2 Select Seller Process
Select Sellers evaluates submitted proposals, selects the best-qualified vendor, and negotiates a mutually binding contract:
- Screening System: Eliminates vendors that fail mandatory pass/fail thresholds (e.g., ISO 27001 certification, minimum turnover, legal eligibility).
- Weighted Scoring Model: Assigns quantitative weights to each evaluation criterion (e.g., Technical , Experience , Support SLA , Price ) to produce an objective total score.
- Independent Estimates ("Should-Cost" Check): Compares vendor bids against an internal benchmark estimate to flag unrealistically low bids (which signal misunderstood scope) or inflated pricing.
- Contract Negotiation: Clarifies technical scope, delivery milestones, SLA penalties, acceptance testing procedures, warranties, and IP ownership before signing the final Contract.
3
Three ICT vendors submit proposals for a campus Wi-Fi and firewall overhaul. Each criterion is scored out of with weights: Technical Solution (), Past Experience (), Support SLA (), and Bid Price ().
| Criterion | Weight | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| Technical Solution | ||||
| Past Experience | ||||
| Support SLA | ||||
| Bid Price (Score) |
Compute the weighted score for each vendor and determine which seller should be selected for contract negotiation.
Computing Weighted Scores ():
- Vendor A:
- Vendor B:
- Vendor C:
Selection Decision: Although Vendor B offered the most competitive price (), Vendor C achieved the highest overall weighted score () due to superior technical architecture and support SLA, and advances to contract negotiation.
Weighted scores: Vendor A , Vendor B , Vendor C . Select Vendor C for contract negotiation.
12.5 Contract administration process
Contract Administration (Control Procurements) ensures that both the seller's and the buyer's performance meet contractual requirements and that legal rights are protected throughout contract execution. Because a contract is a legal document, informal agreements outside the contract can create severe liability.
Core activities in contract administration include:
- Contract Change Control System: Defines the formal written procedure for modifying contract scope, deliverables, pricing, or timelines. All changes require mutual written contract amendments (change orders)—never informal email or verbal promises.
- Buyer-Conducted Performance Reviews & Inspections: Regular milestone reviews, code/architecture walkthroughs, and acceptance tests verifying seller compliance with the SOW and Service-Level Agreements (SLAs).
- Payment System & Financial Tracking: Reviewing seller invoices against verified deliverable sign-offs before authorizing payment, and tracking earned value or burn rate on T&M / cost-reimbursable contracts.
- Claims Administration: Documenting, processing, and resolving contested changes or constructive changes (where buyer and seller disagree on whether work is extra or inside scope). Preferred resolution escalates through negotiation mediation/arbitration (ADR) litigation (last resort).
- Records Management System: Maintaining a centralized, indexed repository of the signed contract, amendments, correspondence, inspection logs, and payment certificates.
12.6 Contract closure process
Contract Closure (Close Procurements) completes and settles every contract—whether the work finished successfully or was terminated early—and verifies that all deliverables were satisfactorily accepted. Note that contracts are closed individually before or during overall project closure.
Key steps and tools in contract closure include:
- Product Verification & Formal Acceptance: Confirming all deliverables passed UAT, security audits, documentation handover, and warranty setup, followed by formal written notice of contract completion issued by the procurement administrator.
- Procurement Audits: A structured review of the entire procurement process (from Plan Purchases through Contract Administration) to identify lessons learned, process bottlenecks, and best practices for future contracts.
- Negotiated Settlements & Final Payment: Resolving any remaining open claims, releasing retention funds or performance bank guarantees, and processing the final invoice.
- Early Termination Handling: If a contract ends prematurely—either termination for convenience (buyer cancels due to changed business needs, paying for work completed plus agreed demobilization) or termination for default/cause (breach by either party)—closure documents the exact settlement terms.
- Updating OPAs (Contract File & Vendor Rating): Archiving the complete contract dossier and recording vendor performance evaluations to inform future Qualified Seller Lists.
Exercises
Practice Exercises — Project Procurement Management
Trace the six stages of the Procurement Management Process Flow and explain the role of EEFs, OPAs, and Bidder Conferences in the early stages.
Six-Stage Procurement Process Flow:
- Plan Purchases and Acquisitions: Make-or-buy analysis, Procurement Management Plan, and SOW.
- Plan Contracting: Contract type selection, RFI/RFP/RFQ preparation, and evaluation criteria.
- Request Seller Responses: Distribution to vendors and bidder conferences.
- Select Sellers: Weighted scoring, independent estimates, negotiation, and contract award.
- Administer the Contract: Deliverable inspections, change control, milestone payments, and claims handling.
- Close the Contract: Formal acceptance, procurement audit, final settlement, and OPA archiving.
Role of EEFs, OPAs, and Bidder Conferences:
- EEFs: Market pricing, vendor availability, and statutory procurement laws constrain acquisition choices.
- OPAs: Approved vendor lists, contract templates, and historical vendor ratings accelerate planning.
- Bidder Conferences: Give all prospective vendors equal, transparent answers to SOW questions before bidding.
The procurement flow runs from Plan Purchases & Acquisitions Plan Contracting Request Seller Responses Select Sellers Administer the Contract Close the Contract. EEFs supply market/legal constraints, OPAs supply templates and vendor history, and Bidder Conferences guarantee fair, uniform information to all bidders.
A fintech company needs an automated KYC verification engine for . Building it in-house costs upfront plus in maintenance. Licensing an external API platform costs for integration plus in subscription fees. Calculate the break-even month and the total cost of both options.
Break-Even Calculation:
30-Month Cost Comparison:
Break-even occurs at . Over , Make costs vs. Buy at (Make saves ).
Compare Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF), and Time and Materials (T&M) contracts in terms of financial risk allocation, scope clarity, and ideal ICT project scenarios. Also distinguish between RFP and RFQ.
Comparison of Contract Types:
- FFP: Seller bears cost-overrun risk; requires crystal-clear scope; best for standardized hardware supply or fixed-spec modules.
- CPFF: Buyer bears cost risk (reimburses allowable costs + fixed fee); suits exploratory R&D or evolving architecture where scope cannot be locked upfront.
- T&M: Hybrid with fixed hourly rate and variable hours (often capped by NTE); ideal for staff augmentation or agile consulting sprints.
RFP vs. RFQ:
- RFP (Request for Proposal): Used for complex, customized ICT solutions where technical quality, architecture, and approach weigh heavily alongside price.
- RFQ (Request for Quotation): Used for well-defined, commodity products/licenses where technical specs are identical and price drives selection.
FFP shifts risk to the seller (clear scope), CPFF shifts cost risk to the buyer (uncertain R&D scope), and T&M splits risk via fixed unit rates (staff augmentation/agile). RFPs solicit complex technical proposals, whereas RFQs solicit price quotes for standard items.
An FPIF software contract specifies Target Cost , Target Fee , Ceiling Price , and a share ratio. Compute the Target Price and the Point of Total Assumption (PTA), and explain what happens when actual costs exceed the PTA.
Target Price and PTA Calculation:
Meaning Above PTA: Once actual cost exceeds , the buyer's total payment hits the Ceiling Price cap, so the seller absorbs of every additional dollar of cost overrun out of its fee (and potentially incurs a net loss above ).
Target Price and . Above the PTA, the buyer pays no more than the ceiling and the seller absorbs of further overruns.
Explain the key activities of Contract Administration and Contract Closure, highlighting how claims administration and procurement audits protect the project organization.
Contract Administration: Monitors seller compliance with the SOW and SLAs, enforces a formal written Contract Change Control System, verifies deliverables before payment, maintains indexed contract records, and manages claims administration (resolving disputed scope/payments via negotiation or ADR before costly litigation).
Contract Closure: Verifies final deliverable acceptance, issues formal written completion notice, settles final payments/retention and early-termination terms if applicable, archives records/vendor ratings in OPAs, and performs a procurement audit—an objective review of the entire procurement life cycle to capture reusable lessons learned.
Contract Administration controls ongoing vendor performance, written change orders, payments, and claims resolution (preventing informal scope creep and legal disputes). Contract Closure confirms formal acceptance, settles accounts, archives records, and runs a procurement audit to improve future contracting.