Your team will hold a gate review with your guide at the end of each semester. This page should document any information needed for the review, as well as outcomes.

(note that the links are not yet live, and will eventually be file attachments to the wiki page)

MSD I: Readiness to Move to Build & Test

Self Evaluation Results:

Status Review

Requirements: 

Customer Requirements Table:

CategoryCR #Customer RequirementRankDescription
Testing/Evaluation1Pump is volumetrically efficient9In order to improve complaint body pump design, a pump that is volumetrically efficient is desired
2Pump performance can be tested and evaluated9Testing is to be performed on the pump through design of experimental testing fixture and procedure such that performance can be compared and bench-marked against developed theoretical model
Manufacturing3Pump has 2 chambers3

Required to take advantage of the multi directional performance of the pump. Through application of one oscillatory torque, both chambers can be actuated. 

Engineering Requirements Table:

Importance

Engineering Requirement

Corresponding CR

Description

Measure

Target Value

Acceptable Value

9Pump can achieve a minimum pumping potential of 4Pump is volumetrically efficientThe pump should have a pumping potential of greater than or equal to that of a human heart. PP = (Δv/V)/(Δl/L)PP84
3Experimentally determine pump power efficiencyPump performance can be tested and evaluatedThe maximum power required to operate the composite pump at the optimal operating frequency should be experimentally determinedWattsN/AN/A
9Pump angle of twist relative to applied torque can be experimentally determinedPump performance can be tested and evaluatedA plot should be generated showing applied torque versus angle of twistDegrees/(N-m)0.6696º/Nm0.4464º/Nm
9Pressure versus volumetric displacement should be able to be experimentally verifiedPump performance can be tested and evaluatedA plot should be generated showing pressure versus volumetric displacement. This will be used to determine power efficiencyJoulesTBD*TBD*
9Determine the optimal operating frequencyPump is power efficientThe optimal operating frequency of the pump should be known. This will be the frequency in which the torque is applied during operationHertzNatural FrequencyWithin 10% of natural frequency
3Pump will have two fixed ends with a centered torsional couplingPump has 2 chambersThe pump should be composed of two chambers connected by a torsional coupling to utilize all of the applied torqueNo. of Chambers21
9Pump and test fixture are capable of operating at the optimal operating frequencyPump performance can be tested and evaluatedThe composite pump and test fixture should be able to operate for at least 100 cycles at the optimal frequencyNo. of Cycles10,000 cycles100 cycles

Action Items from Detailed Design Review:

Verification/Validation Plans for Subassemblies:

Updated Purchasing Status:

  • Blue items have been ordered
  • We currently have Green Items
  • Yellow Items still require further inspection to determine if they are necessary.
  •  Red items are free or no longer need to be ordered
  • Unhighlighted items will be purchased after the summer break. They are short lead time items that are not high priority. 

Risk Assessment

MSD II: Project Close-out

Status Review

Current State of the Project

Performance vs. Requirements

  • Testing Summary:
    • Unmet/not completed requirements were deemed unnecessary via consultation with customer throughout the testing process. P4 deemed not necessary as it is an intermediate step to determining power efficiency, P2. 
    • P6 was met, but in a less than ideal way. Torsional stiffness was experimentally determined, just not including the fluid system. 
    • Primary test plans of pumping potential and power efficiency were determined and satisfied via customer approval. 

  • Robustness of Design:
    • Final Design of test facility is very robust. No expected wear, easily adjustable to changes in pump length, etc. Pumps were always considered a finite, wearable item, however, one pump tested last over 500+ cycles, much beyond the expected lifecycle. 
    • Project met final budget, with approximately $200 unspent. 
    • Customer was extremely satisfied with the final work and results delivered. The scope of this project, by the customer's own voicing, was extremely large, including pump design and manufacturing as well as integration into a complex test facility. All target for compliant body pumps for testing were based on intuition, so have real results to quantify analytical research was extremely satisfying to the customer. 
  • Comparison of Scheduling:
    • Project scope did not change in MSDII. Clarification of testing requirements changed once customer was able to visualize test facility and testing potential. I.e. some previous ER's were just intermediate steps to completing the main ER. 
    • MSDII schedule was purposely design by the project manager to be extremely aggressive. Knowing the scope of the project and parts required to be manufactured, tested, and integrated into the electrical system, schedule was designed with all of Phase 4 to be for testing and troubleshooting. Schedule changed in the specific day-to-day often as a result of things taking more or less time than expected, however the major milestones of delivery and finishing parts, or completing testing did not often change as the group knew they must be completed on time to ensure the project got finished. 
    • Major takeaway: schedule things aggressively so when unexpected challenges arise, you have time to fix them. Trust the schedule, even if very aggressive, because during last few weeks, when things are going wrong, at least you have scheduled time to fix it! 

Team Self Assessment

  • Team worked extremely well together. 
  • All team members upheld all norms and no issues with team behavior was every present beyond engineering discussion and decision making. 
  • All team members made significant contributions to the completion of this project. 
  • Communication amongst the team was early, often, and in good spirits. 
  • Everyone was willing to devote all the time needed to complete what the project required. 

All team members contributed significantly. Here is a breakdown of major contributions. 

  • Elijah: Leadership, scheduling, design, analysis, manufacturing, testing, documentation, problem-solving, troubleshooting. 
  • Zach: Testing, documentation, manufacturing, assembly, troubleshooting, system integration.
  • Chris: Design, manufacturing, testing, troubleshooting, problem solving, analysis, documentation, drawing package. 
  • Joe: Testing, design, manufacturing, analysis, prototyping, documentation, presentations, customer communication.
  • Doug: Electronics, circuits, controls, system integration, coding, electrical assembly, schematics, purchasing.

Risk Assessment: 

  • All risks addressed and communicated to customer. 

Deliverables Checklist and Website Status

  • Website complete,. 
  • Deliverables handed off to customer
  • Completing final clean-up of space. 


Future Work

  • Create tooling for the winding of several chambers and have several (4+) wound chambers ready to be utilized for testing. 
    • Pump chambers wear and can become leaky after several repeated cycles. Multiple chambers would reduce testing time, not having to rely on 24+ hours for remanufacture of an additional chamber for testing. 
  • Integration of torque measurement sensor/method on the designed test facility. 
    • Generate "wet" data for pump torsional stiffness.
    • Could test at various operational frequencies.
  • Shim protocol to reduce excess vertical translation of PIG. 


Lessons Learned, etc.

  • Throughout the MSD process, the primarily learned the value of completing things as soon as possible to discover any potential failures or risks they may arise. A weakness of MSDI for the team was in early prototyping of the pump. This left primarily all phases of MSDII to perfecting the winding technique, alongside all other MSDII deliverables. The team is in unison however, that the proceedings of MSDII were significantly more favorable to the completion of the project and the group dynamic than MSDI. For our group, MSDI was much too structured, and required much too much time in concept selection, scheduling, risk assessment, etc. This, at the time and even currently feels unnecessary as we were planning testing, benchmarking, and hypothesizing risks to something we hadn't finished the design on or in which we had no intuition of failure sources of the design. We understand the reason and the necessity for MSDI to set the team up for success in identifying the problem, and generating a well engineered solution, however, perhaps our team did not utilize that time in conjunction with prototyping and manufacturing components, taking some of the weight of MSDII. The freedom to follow our own schedule and complete engineering tasks allowed in MSDII was much more refreshing and we attribute much of the team's success to this. 



  • Aucune étiquette