1. Inputs
1.1. PM Plan
1.1.1. scope, cost and schedule baselines to ID where procurements are needed & understand constraints
1.2. Requirements Docs
1.2.1. scope related req's that will guide end product/service from Seller
1.3. Activity Resource Req's
1.3.1. Provide info on the req'd skills, # and type of resources. Helps ID resources not available w/in org to determine what services need to be procured
1.4. EEFs
1.5. Org Process Assets
1.6. Risk Register
1.7. Stakeholder Register
1.8. Procurements already in place
1.9. Project Schedule
1.10. Initial Cost Estimates for work to be procured
2. Definition
2.1. The process of documenting project procurement decisions, specifying the approach and identifying potential sellers
3. Benefit
3.1. Determines whether to acquire goods/services from outside of the project. If so, what, how and when to acquire it
4. Process
4.1. 1. Define Roles / Responsibilities
4.2. 2. Prepare the Procurement SOW or Terms of Reference (TOR)
4.3. 3. Prepare a high-level cost estimate to determine the budget
4.4. 4. Identify a short list of qualified sellers
4.5. 5. Prepare and issue bid docs
4.6. 6. Prepare and submit proposals by seller
4.7. 7. Conduct a Technical Eval of the proposals including quality
4.8. 8. Perform a cost eval of the proposals
4.9. 9. Prepare the final combined quality & cost eval to select winning proposal
4.10. 10. Finalize Negotiations & sign contract
5. Outputs
5.1. Procurement Management Plan
5.2. Procurement Strategy
5.2.1. Delivery Methods
5.2.2. Contract Payment Types
5.2.3. Procurement Phases
5.3. Bid Documents
5.3.1. RFI
5.3.2. RFQ
5.3.3. RFP
5.4. Procurement SOW (or TOR)
5.5. Source Selection Criteria
5.5.1. Capability & Capacity
5.5.2. Product Cost & Lifecycle Cost
5.5.3. Delivery dates
5.5.4. Technical expertise
5.5.5. Specific Relevant experience
5.5.6. Adequacy of the proposed approach & work plan in responding to the SOW
5.5.7. Key staff qualifications, avails, competency
5.5.8. Financial Stability of the firm
5.5.9. Management Experience
5.5.10. Suitability of the Knowledge Transfer program (including training)
5.6. Make or Buy Decisions
5.6.1. Make or Buy Analysis
5.7. Independent Cost Estimates
5.8. Change Requests
5.9. Project Doc updates
5.9.1. Lessons learned register
5.9.2. Milestones list
5.9.3. Requirements Docs
5.9.3.1. Technical req's the seller is req'd to satisfy
5.9.3.2. Req's w/Contractual and Legal implications
5.9.4. Requirements Traceability Matrix
5.9.5. Risk Register
5.9.5.1. Each approved seller comes w/its own unique set of risks.
5.9.6. Stakeholder register
5.9.6.1. Add'l stakholders (regulatory agencies, contracting personelle, legal personell)