1. 1 Agenda for acquire-products activity r1. Objective r2. Level of products r3. Role of customer r4. Make or buy r5. Subcontractor selection r6. Acceptance of incomplete products r7. Materials and parts r8. Other products

2. 2 1. Objective rAcquire-products activity rAcquire-products tasks rCompletion criteria rPseudo-completion criteria 1. Objective

3. 3 Acquire-products activity rAcquires all the lower level products necessary to build the product of interest 1. Objective

4. 4 Acquire-products tasks plan costs & sched reviews risks TPPs issues actions test specs provide spec& I/Fs lower products lower test results acquire lower products collect lower test results lower wants select subcontractor and execute contract monitor progress deliverables & sell-off agreements lower specs & I/Fs lower products lower test results 1. Objective

5. 5 Completion criteria rAll the lower-level products have been accepted 1. Objective

6. 6 Pseudo-completion criteria rNone 1. Objective

7. 7 2. Level of products rThe products at the next level don’t need to be of the same type Subsystems Boxes HWCIs/CSCIs FPGAs/ASICs Motherboards Chassis Resistors Material Documents Services 2. Level of products

8. 8 3. Role of customer rProduct engineer becomes customer rResponsibilities as customer 3. Role of customer

9. 9 Product engineer becomes customer rProduct engineer is the customer rDeveloper of the lower product asks for the same things that the product engineer asked of from his or her customer 3. Role of customer

10. 10 Responsibilities as customer rActs as team member and advocate rGrants RAA to the lower product developer rDoesn’t micro-manage rHas approval authority at product level & not lower rDoesn’t ask for many deliverable documents 3. Role of customer

11. 11 4. Make or buy rProduct engineer decides whether to make or buy each lower product rMake if there is A cost or schedule advantage Company has experience Company wants to be in this line of work Competent subcontractors cannot be found Customer does not direct that the product be purchased rBuy otherwise 4. Make or buy

12. 12 5. Subcontractor selection rSelection criteria rOther considerations 5. Subcontractor selection

13. 13 Selection criteria rPrevious experience with the subcontractor rCapability of the subcontractor to do the job rTechnical approach rCost and schedule 5. Subcontractor selection

14. 14 Other considerations rLimit choice to set of preferred subcontractors rChoose another part of the same company rTreat all subcontractors the same, and fairly rProtect subcontractor proprietary information 5. Subcontractor selection

15. 15 6. Acceptance of incomplete products rIdeal rPartial deliveries 6. Acceptance of incomplete products

16. 16 Ideal rComplete sell-off before going to build rSometimes, schedule doesn’t allow ideal 6. Acceptance of incomplete products

17. 17 Partial deliveries rPlan partial deliveries rInsure that RAA for success of the lower product is not lost Who has RAA for lower product meeting requirements? Who fixes the lower product if it breaks before final tests? Who tests each lower product that’s delivered early? 6. Acceptance of incomplete products

18. 18 7. Materials and parts rProducts that don’t require development rOften handled through buyers rCompanies benefit from using standard parts and materials Volume purchases can be made Design and reliability information is known 7. Materials and parts

19. 19 8. Other products rProducts that are acquired such as services, STE, capital, documents, and building fixtures rProduct-based development process can be applied to each rCustomarily segregated and not counted as part of the product being delivered 8. Other products