The purpose of Supplier Agreement Management (SAM) (CMMI-DEV) is to manage the acquisition of products and services from suppliers.
Introductory NotesThe scope of this process area addresses the acquisition of products, services, and product and service components that can be delivered to the project’s customer or included in a product or service system. This process area’s practices can also be used for other purposes that benefit the project (e.g., purchasing consumables). This process area does not apply in all contexts in which commercial off-the-shelf (COTS) components are acquired but does apply in cases where there are modifications to COTS components, government off-the-shelf components, or freeware, that are of significant value to the project or that represent significant project risk. Throughout the process areas, where the terms “product” and “product component” are used, their intended meanings also encompass services, service systems, and their components. The Supplier Agreement Management process area involves the following activities:
- Determining the type of acquisition
- Selecting suppliers
- Establishing and maintaining agreements with suppliers
- Executing supplier agreements
- Accepting delivery of acquired products
- Ensuring successful transition of acquired products
Examples of products and product components that can be acquired by the project include the following:To minimize risks to the project, this process area can also address the acquisition of significant products and product components not delivered to the project’s customer but used to develop and maintain the product or service (for example, development tools and test environments). Typically, the products to be acquired by the project are determined during the early stages of planning and development. The Technical Solution process area provides practices for determining the products and product components that can be acquired from suppliers. This process area does not directly address arrangements in which the supplier is integrated into the project team and uses the same processes and reports to the same management as the project team members (e.g., integrated teams). Typically, these situations are handled by other processes or functions (e.g., project management processes, processes or functions external to the project) though some of the specific practices of this process area can be useful in managing the supplier agreement. This process area typically is not implemented to address arrangements in which the project’s customer is also a supplier. These situations are usually handled by either informal agreements with the customer or by specification of the customer furnished items in the overall agreement that the project has with the customer. In the latter case, some of the specific practices of this process area can be useful in managing the agreement, although others may not, due to the fundamentally different relationship that exists with a customer as opposed to an ordinary supplier. See the CMMI-ACQ model for more information about other types of agreements. Suppliers can take many forms depending on business needs, including in-house suppliers (i.e., suppliers that are in the same organization but are external to the project), fabrication departments, suppliers of reuse libraries, and commercial suppliers. (See the definition of “supplier” in the glossary.) A supplier agreement is established to manage the relationship between the organization and the supplier. A supplier agreement is any written agreement between the organization (representing the project) and the supplier. This agreement can be a contract, license, service level agreement, or memorandum of agreement. The acquired product is delivered to the project from the supplier according to the supplier agreement. (See the definition of “supplier agreement” in the glossary.)
- Subsystems (e.g., navigational system on an airplane)
- Documentation (e.g., installation, operator’s, and user’s manuals)
- Parts and materials (e.g., gauges, switches, wheels, steel, raw materials)
Refer to the Technical Solution (TS) (CMMI-DEV) process area for more information about performing make, buy, or reuse analysis.
Refer to the Requirements Development (RD) (CMMI-DEV) process area for more information about eliciting, analyzing, and establishing customer, product, and product component requirements.
Refer to the Project Monitoring and Control (PMC) (CMMI-DEV) process area for more information about monitoring the project against the plan and managing corrective action to closure.
Refer to the Requirements Management (REQM) (CMMI-DEV) process area for more information about maintaining bidirectional traceability of requirements.