Section: Volume D
Explanation:
12.1.3.3 Procurement Documents
Procurement documents are used to solicit proposals from prospective sellers. Terms such as bid, tender, or quotation are generally used when the seller selection decision will be based on price (as when buying commercial or standard items), while a term such as proposal is generally used when other considerations, such as technical capability or technical approach are paramount. Common terms are in use for different types of procurement documents and may include request for information (RFI), invitation for bid (IFB), request for proposal (RFP), request for quotation (RFQ), tender notice, invitation for negotiation, and invitation for seller's initial response. Specific procurement terminology used may vary by industry and location of the procurement.
The buyer structures procurement documents to facilitate an accurate and complete response from each prospective seller and to facilitate easy evaluation of the responses. These documents include a description of the desired form of the response, the relevant procurement statement of work (SOW) and any required contractual provisions. With government contracting, some or all of the content and structure of procurement documents may be defined by regulation.
The complexity and level of detail of the procurement documents should be consistent with the value of, and risks associated with, the planned procurement. Procurement documents are required to be sufficient to ensure consistent, appropriate responses, but flexible enough to allow consideration of any seller suggestions for better ways to satisfy the same requirements.
Issuing a procurement request to potential sellers to submit a proposal or bid is normally done in accordance with the policies of the buyer's organization, which can include publication of the request in public newspapers, in trade journals, in public registries, or on the internet.

Section: Volume D
Explanation:
The project team must complete a scope statement for developing a common understanding of the project scope among stakeholders. This lists project deliverables - summary level sub-products, whose full and satisfactory delivery marks the completion of the project Process: 6.6 Develop Schedule Definition: The process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule model.
Key Benefit: The key benefit of this process is that by entering schedule activities, durations, resources, resource availabilities, and logical relationships into the scheduling tool, it generates a schedule model with planned dates for completing project activities.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Project schedule network diagrams
5. Activity resource requirements
6. Resource calendars
7. Activity duration estimates
8. Project scope statement
9. Risk register
10.Project staff assignments
11.Resource breakdown structure
12.Enterprise environmental factors
13.Organizational process assets
Tools & Techniques
1. Schedule network analysis
2. Critical path method
3. Critical chain method
4. Resource optimization techniques
5. Modeling techniques
6. Leads and lags
7. Schedule compression
8. .Scheduling tool
Outputs
1. Schedule baseline
2. .Project schedule
3. Schedule data
4. Project calendars
5. Project management plan updates
6. Project documents updates