Agenda for Acquire Products Activity

1. Agenda for Acquire Products Activity 1 Objectives 2. Level of products 3. Role of customer 4. Make or buy 5. Subcontractor selection 6. Acceptance of incomplete products 7. Materials and parts 8. Other products

2. 1. Objectives • Acquire products activity • Product-based activities • Products used to manage • Completion criteria 1. Objectives

3. Acquire Products Activity • Acquires all the lower level products necessary to build the product of interest 1. Objectives

4. Acquire-Products Tasks lower specs & I/Fs lower products Acquire lower products Provide spec& I/Fs lower products lower test results Collect lower test results Select subcontractor and execute contract Monitor progress plan costs & sched reviews risks TPPs issues actions test specs SOW deliverables & sell-off agreements lower test results lower specs & I/Fs lower SOW 1. Objectives

5. Completion Criteria • All the lower-level products have been accepted 1. Objectives

6. Pseudo-Completion Criteria • None 1. Objectives

7. 2. Level of Products • The products at the next level don’t need to be of the same type 2. Level of products

8. Example -- Types of Products at Lower Level • Subsystems • Boxes • HWCIs • CSCIs • FPGAs • ASICs • Motherboards • Chassis • Resistors • Material • Documents • Services 2. Level of products

9. 3. Role of Customer • Product engineer becomes customer • Responsibilities as customer 3. Role of customer

10. Product Engineer as Customer • Product engineer is the customer • Developer of the lower product asks for the same things that the product engineer asked of from his or her customer 3. Role of customer

11. Responsibilities as Customer • Acts as team member and advocate • Grants RAA to the lower product developer • Doesn’t micro-manage • Has approval authority at product level & not lower • Doesn’t ask for many deliverable documents 3. Role of customer

12. 4. Make or Buy • Product engineer decides whether to make or buy each lower product • Make 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 power product be purchased • Buy otherwise 4. Make or buy

13. 5. Subcontractor Selection • Selection criteria • Other considerations 5. Subcontractor selection

14. Selection criteria • Previous experience with the subcontractor • Capability of the subcontractor to do the job • Technical approach • Cost and schedule 5. Subcontractor selection

15. Other Considerations • Limit choice to set of preferred subcontractors • Choose another part of the same company • Treat all subcontractors the same, and fairly • Protect subcontractor proprietary information 5. Subcontractor selection

16. 6. Acceptance of Incomplete Products • Ideal • Partial deliveries 6. Acceptance of incomplete products

17. Ideal • Complete sell off before going build • Sometimes, schedule doesn’t allow ideal 6. Acceptance of incomplete products

18. Partial Deliveries • Plan partial deliveries • Insure 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

19. 7. Materials and Parts • Products that don’t require development • Often handled through buyers • Companies benefit from using standard parts and materials • Volume purchases can be made • Design and reliability information is known 7. Materials and parts

20. 8. Other products • Products that are acquired such as services, STE, capital, documents, and building fixtures • Product-based development process can be applied to each • Customarily segregated and not counted as part of the product being delivered 8. Other products

21. Agenda for Build Activity • 1. Objectives • 2. Build plan • 3. Build steps • 4. Other build concepts • 5. Homework 1. Objectives

22. 1. Objectives • Design activity • Product-based activities • Products used to manage • Completion criteria 1. Objectives

23. Build Activity • Assembles all lower products into a working version of the product of interest and delivers the product for final test • Verify may proceed in parallel with build 1. Objectives

24. Build Tasks Build steps lower products product design Build product plan Plan build environment Create build environment 1. Objectives

25. Completion Criteria • Product is complete and ready for final test 1. Objectives

26. Pseudo-Completion Criteria • None 1. Objectives

27. 2. Build Plan • Generated by contractor • Defines build environment • Defines role of build steps 2. Build plan

28. 3. Build Steps • Generated by contractor • Defines the steps in building the product from the lower products • Depends upon the familiarity and skill of the builders 3. Build steps

29. 4. Other Build Concepts • Problem resolution system • Configuration management • Partial deliveries • Interaction of build and design • Interaction of build and verify • Engineering tests 4. Other build concepts

30. Problem Resolution System • Necessary tool for management of work • Requires capability to deal with problems and configuration 4. Other build concepts

31. Configuration Management • Necessary to prevent inadvertent redesign • Problem arises when design activity separated from build activity 4. Other build concepts

32. Partial deliveries • Described earlier in the acquire products activity • Requires coordination with design and acquire products activities 4. Other build concepts

33. Interaction of Build and Design • Flow of requirements and design may make building in parallel with design desirable • Parallel design and build is often done in prototyping and software • Parallel design and build is often handled by treating each separate build as an independent product 4. Other build concepts

34. Interaction of Build and Verify • Build and verify may interact • Testing is easier at a point in the build • Alternate path may be taken in build dependent upon test results 4. Other build concepts

35. Engineering Tests • Formal testing aligns with specification and not with design • Engineering tests verify elements of design • Design elements are often overlooked and not treated formally 4. Other build concepts

36. 5. Homework • Problem • Assumptions 5. Homework

37. Problem • 1. List the products that need to be acquired to build a basketball half-court in someone's backyard within a city • 2. List the products that are not part of the final product • 3. Define the build steps resulting in a finished product • 4. List where verification -- if any -- is included in the process • 5. State how we know when we’re done 5. Homework

38. Assumptions • The turn-key job cannot be subcontracted • Subcontracting allowed otherwise 5. Homework