Test Plans & Test Results

Transcription

1 Table of contents P13631 Process Control - Gravity Fed Test Plans & Test Results Note: Once you complete each of the three sections, right click on the table below and select Update Field to update the Table of Contents.) 1. MSD I: WKS 8-10 PRELIMINARY TEST PLAN WHAT Sub-Systems/ Functions/ Features Template Test Equipment MSD II WKS 2-3 TEST PLAN HOW, WHO, WHEN Data Collection Test Procedure, timeline MSD II WKS 3-10 DESIGN VERIFICATION Logistics Analysis of Data Design Summary Conclusion or Design Summary... 7 RIT KGCOE MSD Program Page 1 Revision:

2 P10XXX Your Project Name Preliminary Test Plan 1. MSD I: WKS 8-10 PRELIMINARY TEST PLAN WHAT In this phase, the team needs to focus on WHAT needs to be verified (i.e. demonstrate, data results, data analysis, code review and so on). I good point of reference is to visualize your final project and then how you plan to verify your project to your Guide and at the completion of MSD II. Refer to Test Lecture slides on MSD I MyCourses/ Content/ Week 3/ Reference Material/ Testing Phases. Particular attention should be paid to verification the interfaces between the sub-systems, features and/ or functions for testing and debugging Sub-Systems/ Functions/ Features If necessary, use your high level block diagram completed leading up to your System Level Review to list your sub-systems, features and/ or functions. Major Sub-Systems/ Features/ Function 1) Fixtures 2) Gravity Drained Tank/ Flow Subsytem 3) LabVIEW control interface/ Data Acquisition 4) Safety (continued) RIT KGCOE MSD Program Page 2 Revision:

3 (continued) 1.2. Template If not already, apply ifications to each sub-system, feature and/or function. Project clustered into chunks, as described in MyCourses reading Ulrich Chap. 9: Product Planning & Systems Design. Review page 174; Exhibit 9-7, and page 183; Exhibit For previous team examples, see MSD I MyCourses/ Content/ Week 6 Detailed Design Test Plan (samples) and For example of completed test results, see A general template Subsystem/ Function/ Feature Name: Fixtures ES3 Design for User Assembly/Disassembly Time min Time study of assembly/dissembly using Lab Technition ES7 ES12 ES17 ES20 Minimum Space Requirements area ft^2 8 6 Area measurements Mobility adaptability in Lab setting Operationally Binary N Y Electrical devices are fully protected from physical, electrical and chemical interference Operationally Binary Yes No All fittings are water tight Operationally Binary Yes No Successful operation by nontechnical students Leak Check of all connections before commissioned Subsystem/ Function/ Feature Name: Gravity Drained Tank/Flow Subsystem RIT KGCOE MSD Program Page 3 Revision:

4 ES1 Minimum Operating Flow Rate Flow Rate Measurement gr/min Simulate minimum flow rate and monitor Flow transmitter reading. ES2 Maximum Operating Flow Rates Flow Rate Measurement gr/min Simulate maximum flow rate and monitor Flow transmitter reading. ES13 ES18 Manual Operation of Intstruments Operationally Binary N Y Gravity Feed Height Length ft TBD TBD Successful operation by non-technical students Measure pressure and flow rate at operational height, before implementation. Subsystem/ Function/ Feature Name: LabVIEW Control Interface/Data Acquisition ES10 Automated Operation of Instruments Operationally ma 4, 20 4 to 20 Measure controller output to I/P before installation. Compare to expected output ES15 Automated Data Collection Operationally Binary N Y Successful operation by non-technical students RIT KGCOE MSD Program Page 4 Revision:

5 ES8 ES18 Instrument and Controller Power Supply Voltage V Proportional, Integral and Derivative Control of Devices Operationally Binary Yes No Voltage Measurements using Multimeter Successful operation of PID control of valves from LabVIEW VI. Subsystem/ Function/ Feature Name: Safety ES14 Safe and Ergornomic Design Operationally Binary N Y Successful 3 hour run time, no component failure, no spills, all electrical devices remain safe. Check off by lab supervisor on safe operation 1.3. Test Equipment Focus on any equipment that the team requires to measure ifications but is not available to measure ifications. Discuss this with your Guide. Some examples of ifications that teams could not measure were: measurement of forces, vibration, rf frequency trum, field strength, serial communication data accuracy, static and dynamic force measurements, very accurate velocity measurements, rf noise (S/N), complex data acquisition. Contact your Department Guide for any further equipment that may be necessary.. Spec. # ES1 ES2 ES n-1 ES n Instrumentation or equipment not available (description) EXAMPLE OF TABLE RIT KGCOE MSD Program Page 5 Revision:

6 2. MSD II WKS 2-3 TEST PLAN HOW, WHO, WHEN Now that you documented what you are going to verify or test in MSD I, you need to document how, who and when. Be critical of your test equipment requirements, any ial conditions and so on. Be critical of your testing sequence. That is, test in subsystems before fully integrating? 2.1. Data Collection Data Collection Structure Update list of tests to be performed (indicate test # and name, test description and so on) Sampling Techniques How to measure and any setup needed? Sample Size Do you have tolerances on your ifications? Reporting Problems; Corrective Action 2.2. Test Procedure, timeline Who is testing what and when? Are there interdependencies between subsystems (Block Diagram)? Can test equipment enable preliminary simulation of needed signals prior to integrating into the next level of completion? RIT KGCOE MSD Program Page 6 Revision:

7 3. MSD II WKS 3-10 DESIGN VERIFICATION For and example of completed test results, see Logistics Where are the test results being performed, logged (i.e. project notebook) and documented (i.e. excel spreadsheet)? EDGE team website structure (i.e. document names, file types, and header location) Analysis of Data Design Summary 3.3. Conclusion or Design Summary Can you explain why a particular function doesn t work? Conclusions are reported or summarized (i.e. significance with confidence, pass/fail, etc.) as applicable Lab Demo with your Guide and Faculty Consultants Perform each of the ifications and features Meeting with Sponsor See Acceptance above. Field Demonstration. Deliver the project. Demonstrate to the Sponsor. needs met / not met. RIT KGCOE MSD Program Page 7 Revision: