Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
133 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
PROCUREMENT
|
.
|
.
|
|
|
|
.
|
.
|
|
|
|
.
|
.
|
|
|
Project Procurement Management
|
.
|
.
|
|
|
The processes required to acquire goods and services from outside the performing organization. Is discussed from the perspective of the buyer and assumes the seller is outside the performing organization.
|
.
|
.
|
|
|
Project Procurement Management (12)
|
.
|
.
|
|
|
1. Procurement Planning
|
.
|
.
|
|
|
The process of identifying which project needs can be best met by procuring products or services outside the performing organization. It involves consideration of whether to procure, how to procure, what to procure, how much to procure and when to procure it.
|
.
|
.
|
|
|
2. Solicitation Planning
|
.
|
.
|
|
|
Involves preparing the documents needed to support solicitation.
|
.
|
.
|
|
|
3. Solicitation
|
.
|
.
|
|
|
Involves obtaining information from prospective sellers on how project needs can be met. Most of the actual effort in this process is expended by the prospective sellers, normally at no cost to the project.
|
.
|
.
|
|
|
4. Source Selection
|
.
|
.
|
|
|
Involves the receipt of bids or proposals and the application of the evaluation criteria to select a provider. However, the process is seldom straightforward. On major procurement items, this process may be iterated. A short list of qualified sellers will be selected and then a more detailed evaluation will be conducted based on a more detailed and comprehensive proposal.
|
.
|
.
|
|
|
5. Contract Administration
|
.
|
.
|
|
|
Is the process of ensuring that the seller’s performance meets contractual requirements. The legal nature of the contractual relationship makes it imperative that the project team be acutely aware of the legal implications of actions taken when administering the contract. Project management processes that must be applied include
|
.
|
.
|
|
|
a. Project plan execution – Authorize the contractor’s work at the appropriate time,
|
.
|
.
|
|
|
b. Performance reporting - Monitor contractor cost, schedule and technical performance,
|
.
|
.
|
|
|
c. Quality control – Inspect and verify the adequacy of the contractor’s product,
|
.
|
.
|
|
|
d. Change control – Ensure that changes are properly approved and that all those with a need to know are aware of such changes.
|
.
|
.
|
|
|
6. Contract Close-Out
|
.
|
.
|
|
|
Is similar to administrative closure in that it involves both product verification and administrative close-out. Early termination of a contract is a special case of contract close-out.
|
.
|
.
|
|
|
Procurement Planning (12.1)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Scope statement
|
.
|
.
|
|
|
b. Product description
|
.
|
.
|
|
|
The description of the product of the project provides important information about any technical issues or concerns that would need to be considered during procurement planning.
|
.
|
.
|
|
|
c. Procurement resources
|
.
|
.
|
|
|
If the performing organization does not have a formal contracting group, the project team will have to supply both the resources and expertise to support project procurement activities.
|
.
|
.
|
|
|
d. Market conditions
|
.
|
.
|
|
|
Must consider what products and services are available in the marketplace, from whom, and under what terms and conditions.
|
.
|
.
|
|
|
e. Other planning outputs
|
.
|
.
|
|
|
Other planning outputs, which must often be considered, include preliminary cost and schedule estimates, quality management plans, cash flow projections, the WBS, identified risks and planning staffing.
|
.
|
.
|
|
|
f. Constraints
|
.
|
.
|
|
|
g. Assumptions
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Make-or-buy analysis
|
.
|
.
|
|
|
Technique used to determine whether a particular product could be produced cost-effectively by the performing organization. It must reflect the perspective of the performing organization as well as the immediate needs of the project.
|
.
|
.
|
|
|
b. Expert judgment
|
.
|
.
|
|
|
c. Contract type selection
|
.
|
.
|
|
|
1) Fixed price or lump sum contracts – Involves a fixed total price for a well-defined product. To the extent that the product is not well defined, both the buyer and seller are at risk.
|
.
|
.
|
|
|
2) Cost reimbursable contracts – This category of contract involves payment to the seller for its actual costs. Costs are usually classified as direct or indirect costs.
|
.
|
.
|
|
|
Direct costs are incurred for the exclusive benefit of the project while indirect costs are allocated to the project by the performing organization as a cost of doing business.
|
.
|
.
|
|
|
3) Unit price contracts – Seller is paid a preset amount per unit of service and the total value of the contract is a function of the quantities needed to complete the work.
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Procurement management plan
|
.
|
.
|
|
|
Should describe how the remaining procurement processes will be managed.
|
.
|
.
|
|
|
b. Statement(s) of work
|
.
|
.
|
|
|
The SOW describes the procurement item in sufficient detail to allow prospective to allow prospective sellers to determine if they are capable of providing the item.
|
.
|
.
|
|
|
Solicitation Planning (12.2)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Procurement management plan
|
.
|
.
|
|
|
b. Statement(s) of work
|
.
|
.
|
|
|
c. Other planning outputs
|
.
|
.
|
|
|
Solicitation planning should be closely coordinated with the project schedule. Other planning outputs which may have been modified from when they were considered as part of the procurement planning.
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Standard forms
|
.
|
.
|
|
|
b. Expert judgment
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Procurement documents
|
.
|
.
|
|
|
Are used to solicit proposals from prospective sellers. The terms “bid” and "quotation” are generally used when the source selection process will be price driven while the term “proposal” is used when non-financial considerations such as technical skills or approach are paramount. Common names include Invitation for Bid (IFB), Request for Proposal (RFP), Request for Quotation (RFQ), Invitation for Negotiation, and Contractor Initial Response.
|
.
|
.
|
|
|
b. Evaluation criteria
|
.
|
.
|
|
|
Used to rate or score proposals, as they may be objective or subjective. They are often included in the procurement documents. Criteria may include:
|
.
|
.
|
|
|
1) Understanding the need – Demonstrated by the seller’s proposal
|
.
|
.
|
|
|
2) Overall or life cycle cost – Will the selected seller produce the lowest total cost?
|
.
|
.
|
|
|
3) Technical capability – Does the seller have, or can the seller be reasonably expected to acquire, the technical skills and knowledge needed?
|
.
|
.
|
|
|
4) Management approach - Does the seller have, or can the seller be reasonably expected to develop, management processes and procedures to ensure a successful project?
|
.
|
.
|
|
|
5) Financial capacity - Does the seller have, or can the seller be reasonably expected to obtain, the financial resources needed?
|
.
|
.
|
|
|
c. Statement of work updates
|
.
|
.
|
|
|
Solicitation (12.3)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Procurement documents
|
.
|
.
|
|
|
b. Qualified seller lists
|
.
|
.
|
|
|
Some organizations maintain lists or files with information on prospective sellers. These lists will generally have information or relevant experience and other characteristics of the prospective sellers.
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Bidder conferences
|
.
|
.
|
|
|
Bidder conferences are meetings with prospective sellers prior to preparation of a proposal. They are used to ensure that all prospective sellers have a clear, common understanding of the procurement.
|
.
|
.
|
|
|
b. Advertising
|
.
|
.
|
|
|
Existing lists of potential sellers can often be expanded by placing advertisements in general circulation or specialty publications.
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Proposals
|
.
|
.
|
|
|
Proposals are seller-prepared documents that describe the seller’s ability and willingness to provide the requested product.
|
.
|
.
|
|
|
Source Selection (12.4)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Proposals
|
.
|
.
|
|
|
b. Evaluation criteria
|
.
|
.
|
|
|
c. Organizational policies
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Contract negotiation
|
.
|
.
|
|
|
Involves clarification and mutual agreement on the structure and requirements of the contract prior to the signing of the contract.
|
.
|
.
|
|
|
b. Weighting system
|
.
|
.
|
|
|
A weighting system is a method of quantifying qualitative data in order to minimize the effect of personal prejudice on source selection.
|
.
|
.
|
|
|
c. Screening system
|
.
|
.
|
|
|
Involves establishing minimum requirements of performance for one or more of the evaluation criteria.
|
.
|
.
|
|
|
d. Independent estimates
|
.
|
.
|
|
|
The procuring organization may prepare its own estimates as a check on proposed pricing. Significant differences from these estimates may be an indication that the SOW was not adequate or the seller either misunderstood or failed to respond fully to the SOW.
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Contract
|
.
|
.
|
|
|
A contract is a mutually binding agreement, which obligates the seller to provide the specified product, and obligates the buyer to pay for it. Although all project documents are subject to some form of review and approval, the legally binding nature of a contract usually means that it will be subjected to a more extensive approval process. The legal contractual relationship that exists between the buyer and the seller is called “Contract Privacy.”
|
.
|
.
|
|
|
Contract Administration (12.5)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Contract
|
.
|
.
|
|
|
b. Work results
|
.
|
.
|
|
|
The seller’s work results – which deliverables have been completed and which have not, to what extent are quality standards being met, what costs have been incurred or committed – are collected as part of the project plan execution.
|
.
|
.
|
|
|
c. Change requests
|
.
|
.
|
|
|
Change requests may include modifications to the terms of the contract or to the description of the product or service to be provided.
|
.
|
.
|
|
|
d. Seller invoices
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Contract change control system
|
.
|
.
|
|
|
Defines the process by which the contract may be modified. It includes the paperwork tracking systems, dispute resolution procedures, and approval levels necessary for authorizing changes.
|
.
|
.
|
|
|
b. Performance reporting
|
.
|
.
|
|
|
Provides management with information about how effectively the seller is achieving the contractual objectives.
|
.
|
.
|
|
|
c. Payment system
|
.
|
.
|
|
|
Payments to the seller are usually handled by the accounts payable system of the performing organization.
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Correspondence
|
.
|
.
|
|
|
Contract terms and conditions often require written documentation of certain aspects of buyer/seller communications.
|
.
|
.
|
|
|
b. Contract changes
|
.
|
.
|
|
|
Changes (approved and unapproved) are fed back through the appropriate project planning and project procurement processes and the project plan or other relevant documentation is updated as appropriate.
|
.
|
.
|
|
|
c. Payment requests
|
.
|
.
|
|
|
This assumes that the project is using an external payment system.
|
.
|
.
|
|
|
Contract Close-Out (12.6)
|
.
|
.
|
|
|
1. Inputs
|
.
|
.
|
|
|
a. Contract documentation
|
.
|
.
|
|
|
Includes but is not limited to, the contract itself along with all supporting schedules, request and approved contract changes, any seller-developed technical documentation, seller performance reports, financial documents and the results of any contract-related inspections.
|
.
|
.
|
|
|
2. Tools and Techniques
|
.
|
.
|
|
|
a. Procurement audits
|
.
|
.
|
|
|
Is a structured review of the procurement process from procurement planning through contract administration. The objective of a procurement audit is to identify successes and failures that warrant transfer to other procurement items on this project or to other projects.
|
.
|
.
|
|
|
3. Outputs
|
.
|
.
|
|
|
a. Contract file
|
.
|
.
|
|
|
A complete set of indexed records should be prepared for inclusion with the final project records.
|
.
|
.
|
|
|
b. Formal acceptance and closure
|
.
|
.
|
|
|
The person responsible for contract administration should provide the seller with formal written notice that the contract has been completed.
|
.
|
.
|
