Lec 09 - Procurement Management
Lec 09 - Procurement Management
PMP
Plan Procurement Management
Presented by:
2
PROJECT
PROCUREMENT
Project Procurement Management includes the processes
MANAGEMENT necessary to purchase or acquire products, services, or
results needed from outside the project team
2 24 10 12 1
384
Trial engagements.
Some projects will engage several candidate sellers for initial deliverables and work products on a paid basis
before making the full commitment to a larger portion of the project scope.
This accelerates momentum by allowing the buyer to evaluate potential partners, while simultaneously
making progress on project work.
386
TAILORING CONSIDERATIONS
• Complexity of procurement.
• Physical location
• Governance and regulatory environment.
• Availability of contractors
387
Contracts Type
Firm Fixed Price Contracts
01 PROJECT CHARTER
02
BUSINESS DOCUMENTS
• Business case
• Benefits management plan
04
PROJECT MANAGEMENT PLAN.
• Milestone list. • Resource requirements.
• Project team assignments. • Risk register.
• Requirements documentation. • Stakeholder register.
• Requirements traceability matrix.
01
EXPERT JUDGMENT
02 DATA GATHERING
Market research includes examination of industry and specific seller capabilities.
03 DATA ANALYSIS
Make-or-buy analysis
05
Meeting
392
03 BID DOCUMENTS
Biding document can include:
o Request for information (RFI): is used when more information on the goods
and services to be acquired, needed from the sellers.
o Request for quotation (RFQ) : used when more information is needed on how
vendors would satisfy the requirements and/or how much it will cost.
o Request for proposal (RFP). is used when there is a problem in the project and
the solution is not easy to determine.
393
• The SOW describes the procurement item in sufficient detail (specifications, quantity desired,
quality levels, performance data, period of performance, work location, and other requirements).
• The procurement SOW should be clear, complete, and concise.
• terms of reference (TOR) is sometimes used when contracting for services.
• SOW, a TOR typically includes these elements:
• Tasks the contractor is required to perform as well as specified coordinationrequirements;
• Standards the contractor will fulfill that are applicable to the project;
• Data that needs to be submitted for approval;
• Detailed list of all data and services that will be provided to the contractor by the buyer
• Definition of the schedule for initial submission and the review/approval time required.
07
INDEPENDENT COST ESTIMATES
08 CHANGE REQUESTS
09
PROJECT DOCUMENTS UPDATES.
• Lessons learned register. • Requirements traceability matrix.
• Milestone list. • Risk register.
• Requirements documentation. • Stakeholder register.
02
PROJECT DOCUMENTS
• Lessons learned register.
• Project schedule.
• Requirements documentation.
• Risk register.
• Stakeholder register.
398
03
PROCUREMENT DOCUMENTATION
• Bid documents.
• Procurement statement of work.
• Independent cost estimates.
• Source selection criteria.
04 SELLER PROPOSALS
• If the seller is going to submit a price proposal, good practice is to require that it be
separate from the technical proposal.
• The evaluation body reviews each submitted proposal according to the source selection
criteria and selects the seller that can best satisfy the buying organization’s
requirements.
05
ENTERPRISE ENVIRONMENTAL FACTORS(EEF).
01 EXPERT JUDGMENT
02 ADVERTISING
• Advertising is communicating with potential users of a product, service, or result.
• Existing lists of potential sellers often can be expanded by placing advertisements in
general circulation publications such as selected newspapers or in specialty trade
publications.
• Most government jurisdictions require public advertising or online posting of pending
government contracts.
03 BIDDER CONFERENCES
• (also called contractor conferences, vendor conferences, and pre-bid conferences) are
meetings between the buyer and prospective sellers prior to proposal submittal.
• They are used to ensure that all prospective bidders have a clear and common
understanding of the procurement and no bidders receive preferential treatment.
400
04 DATA ANALYSIS
• Proposal evaluation. to ensure they are complete and respond in full to the bid
documents, procurement statement of work, source selection criteria, and any other
documents that went out in the bid package.
• Negotiation
401
12.2 Conduct Procurement Management Outputs
01 SELECTED SELLERS
• The selected sellers are those who have been judgedto
be in a competitive range based on the outcome of theproposal
or bid evaluation.
• Final approval of complex, high-value, high-risk
• procurements will generally require organizational
• senior management approval prior to award.
02 AGREEMENTS
A contract is a mutually binding agreement that obligates the seller to provide the specified
products, services, or results; obligates the buyer to compensate the seller; and represents a legal
relationship that is subject to remedy in thecourts.
The major components in an agreement document:
Procurement statement of work - Schedule, milestones, or date - Performance reporting - Pricing
and payment terms - Inspection, quality, and acceptance criteria - Warranty & support - Incentives
and penalties - Insurance - Subordinate subcontractor approvals - General terms and conditions -
Change request handling - Termination clause
03 CHANGE REQUESTS.
402
12.2 Conduct Procurement Management Outputs
05
PROJECT DOCUMENTS UPDATES
• Lessons learned register.
• Requirements documentation.
• Requirements traceability matrix.
• Resource calendars.
• Risk register.
• Stakeholder register.
06
ORGANIZATIONAL PROCESS ASSETS UPDATES
403
02 PROJECT DOCUMENTS
• Assumption log.
• Lessons learned register.
• Milestone list.
• Quality reports.
• Requirements documentation.
• Requirements traceability matrix.
• Risk register.
• Stakeholder register.
03 AGREEMENTS
405
04 PROCUREMENT DOCUMENTATION
01 EXPERT JUDGMENT
02 CLAIMS ADMINISTRATION
• The contested changes are called claims. When they cannot be resolved, they become
disputes and finally appeals.
• Claims are documented, processed, monitored, and managed throughout the contract
life cycle, usually in accordance with the terms of the contract.
• If the parties themselves do not resolve a claim, it may have to be handled in
accordance with alternative dispute resolution (ADR) typically following procedures
established in the contract.
• Settlement of all claims and disputes through negotiation is the preferred method.
03 DATA ANALYSIS
• Performance Reviews. Measure, compare, and analyze quality, resource, schedule,
and cost performance against the agreement.
• Earned Value Analysis (EVA).
• Trend Analysis. Trend analysis can develop a forecast estimate at completion (EAC)
407
04 INSPECTION
a structured review of the work being performed by the contractor.
05 AUDITS
• A structured review of the procurement process.
• Rights and obligations related to audits should be described in the procurement contract.
• Resulting audit observations should be brought to the attention of the buyer’s project
manager and the seller’s project manager for adjustments to the project, when
necessary.
408
01 CLOSED PROCUREMENTS
• The buyer, usually through its authorized procurement administrator, provides the seller with
formal written notice that the contract has been completed.
• Requirements for formal procurement closure are usually defined in the terms and conditions
of the contract and are included in the procurement managementplan.
• Typically, all deliverables should have been provided on time and meet technical and quality
requirements, there should be no outstanding claims or invoices, and all final payments should
have been made.
• The project management team should have approved all deliverables prior to closure.
02
WORK PERFORMANCE INFORMATION
how a seller is performing by comparing the deliverables received, the technical performance
achieved, and the costs incurred and accepted against the SOW budget for the workperformed.
409
04
PROJECT MANAGEMENT PLAN UPDATES
• Risk management plan.
• Procurement management plan.
• Cost baseline.
• Schedule baseline.
410
05
PROJECT DOCUMENTS UPDATES
• Lessons learned register.
• Resource requirements.
• Requirements traceability matrix.
• Risk register.
• Stakeholder register.
Presented by: