Results of Technical Review
Team specific comments from David are written on this page, below the section of comments for all teams. Please be sure to read these comments. Comments from other reviewers, compiled for each team, are accessible through the "feedback" links below (certs required). Feedback will be coming in Friday, and no later than 5 PM Saturday.
All teams have shown good progress since the mockup review and a lot has been learned.
The technical review prototypes are good platforms for testing and provide a concrete reference point from which one can carefully design and detail a product. While some models were more refined than others, across all teams the prototypes are closer to engineering mockups than a designed product. Using what you have learned, now is the time to move from the mindset of exploring options to thinking through the design details of making a usable, real product. It's time to design and implement a looks-like, works-like prototype for the final presentation/product launch! This is where the jump to being a product, as opposed to the exploration of a concept or bench-level experiment takes place.
In preparing for the design review on Monday and working towards the final presentation, please refine and execute your device as a coherent, integrated, elegantly-resolved product, thinking carefully about efficient use of materials, ease of fabrication, cost and user safety, overall form, and human factors (amongst many other things).
One of the first things to do in preparing for Monday is to step back, look at, and discuss the prototype as a team. Regroup, and get the team on the same page about what the product is, your core value proposition, and implementation vision. Having been focused on different items/details in the push for the technical review, different team members may not be aware of how aspects of the product have changed. Or, based on what has been learned, how things should change. As a reflection of this, inconsistent descriptions and rationales about the products were provided by different members of the same team to review sub-groups. The review prototypes can be used to test and understand how to resolve challenges.
Please read the team-specific comments from me below (Prof Wallace). The written comments from other reviewers will be received no later than 5 PM Saturday. Also, carefully review your own notes from the review. Think about how your current prototype needs to change to be comparable in detail and execution to existing products that you can already buy. Looking at details in related, real products for inspiration can be very helpful at this point in the design process. We are aiming for comparable levels of detailing to what is seen in real products.
If your team has key functional aspects or system integration issues yet to be resolved, it is very important to tackle these problems soon in order to avoid surprises a few days before the final presentation. Core, integrated functionality should be solidly resolved this coming week so that there is time for implementing, planning, product testing, and preparation/practice for the final presentation.
All teams should aim to have the final prototypes completely ready and available for presentation practice by the Saturday before the final presentation. Your team will need to take a split approach during the final weeks, working on the prototype and at the same time designing/preparing materials for the final presentation.
My team-specific comments/suggestions that follow are intended to help each team in preparation for the next design revision/design review on Monday. Please consider these comments along the written feedback you will receive from other instructors as you make decisions,. Feel free to ask questions too.
Finally, please be sure to schedule a time to meet with me on Tuesday to discuss set design (if you have not done so already).
The average scores from reviewers for each prototype, with standard deviations, is at the bottom of this page.
Red: Beehive box lifting system
The architecture progressed a lot from the assembly review. While there are a number of issues, I think that the bones for a good solution are there... It's now time to resolve and execute details.
For myself, I learned more from the "pre-review" on Tuesday than during the technical review. The sketch I sent after that review still encapsulates what I learned related to addressing lateral stiffness, stability, using standard boxes, allowing fine box positioning separate from lifting, simplifying shipping and assembly, and allowing potential for one device to service multiple hives. I was not able to get a sound impression for changes in direction/thinking post the Tuesday pre-review. Also, in the technical review, the proposition of "I'm a beekeeper and this is what the product does for me" did not come across as clearly as it might.
My impression is that further simplification while addressing issues with the current prototype is needed. The beehive itself is a really simple, wooden structure. For some beekeepers there is an aesthetic component to beekeeping. Can the design be resolved in a way that it belongs with the hive. For example, could wood be used for key structural elements rather than tubular steel or aluminum?
The prototype was nicely executed and provides a good platform to work with and gain understanding for implementing the final product prototype. Given that the eddy current motion brake required motion to work, it's hard for me to visualize how it's so stiff at such a low speed. I wonder if there is friction somewhere that is providing most of the resistance? Are magnets actually clamping on the disc? The technical review prototype can now be looked at carefully and with some detective work more insight will be gained. Maybe friction is good... perhaps consider a centrifugal drum brake (sort of like a chain saw)?
Some other thoughts follow:
Blue: aircraft baggage loading
The design has come a long way since the assembly review. That's nice! Overall, the devie definitely helped compared to lifting. The general approach seems solid, so now it's about working the details to get it into a nicely usable product form. Also, it makes sense that it works for a 737, but it would be nice to convey the range of planes that it might be used in. In particular, when does the flat of the cargo hold become too narrow?
A few more specific thoughts:
Yellow: modular surf board
It's good that you are getting a handle on fiberglass layup techniques. Also, your overall plan for making a 3 part board and total of 4 modules is a good strategy.
• having looked at the process of modifying and patching existing boards, in combination with the level of precision needed in fabrication, it seems like making molds that integrate the necessary features and inserts for mating hard-points might be the way to a better executed prototype, and could be a time saver. We have the tools needed to fabricate such molds at the necessary scale. Happy to discuss further, as are your instructors. It would also be good to order some two-part urethane foams to do some experiments with. We can help with that.
Orange: custom lipstick
The color mixing and replication process has a lot of potential. It is quite believable that this approach could allow less trained store staff do the job. Some pigments have different "strengths" in mixing, so you will likely need a few sizes of plugs rather than just one plug size. Please get implements that are stiff enough to mechanically mix the plugs. It's nice that the customer can see the color mix being accurately replicated. Perhaps the containers of "production size" plugs could be in a nice visual display?
The mixer and melting phase of the system has potential for nice visual qualities and letting the customer see the process of their color mix coming together. For the physical unit, detailing of sub-systems and integration into a coherent product, designing housings with as-manufactured design intent, and mounting electronics needs to be addressed. I'm happy to sketch with you on this a bit to think about directions. Also, if you have not done it, making a mood board to have insight while designing would be really helpful. (e.g., here's some free work from pinterest!).
The final stage of the process (casting the stick and installing the case) is the part of the experience that seems to need the most conceptual resolution. At the moment it is quite complicated and seems to have the most remaining conceptual challenges.
From the technical review you have a proof of concept. That is good.
Now one really needs to think about how to make it into a product. You'll probably not build the system completely from off-the-self plumbing components. The pump system and electronics, remote controlled valve and electronics all need careful detailing and resolution. It is likely that a custom designed, integrated valve/actuator may be needed. A few times the phrase in "future versions of the product..." came up in the review. That future is now!
It seems like the scope of the product should include a system profile and installation guides for different situations. In which situations is it applicable? In which is it not? Could temperature, wind conditions, and a bit of information about the type of construction and date of construction be used to less conservatively estimate when pipe freezing is likely? If there were documented profiles for regions/house types/freezing issues this might help people understand if they want to buy the product.
I may have missed this discussion, but my impression is that this is a plumber-installed system. To work properly, it seems that all end-of-loops for areas that might freeze (i.e., near exterior walls) should have the device. Further, since parallel loops may have different flow resistance, there might be balancing required between branches. Seems like the system and plumbing knowledge required might preclude most homeowners from installation. Think that a good installation guide is important.
How does a user know if the system is working properly (i.e., the circulation is correct/calibrated)?
It would be nice to have a structured storyboard for the overall UI to think through different aspects of the system.
To help with freezing in the test rig, it would be good to make a better thermal conduction circuit between the pipe and the blast freezer. Just let me know and I can sketch with you. For both consumers, and also those interested in understanding your product, it would be really helpful to find ways to clearly demark existing plumbing or test setup equipment from the actual product.
Silver: oven shelf lift
The current prototype seems like a workable proof of concept/path. That's great. That said, it is executed at in a mockup form. Now it's time to design and detail it knowing what the system is.
• please think through what level/quality of oven this is most likely to be on. We can buy such an oven, even if it is a more expensive model.
Pink: scuba neutral buoyancy
You did a lot of tests and many/most failed, but the exciting thing is that it seems a lot was learned. The in-water test at the pool was really informative. It's design time!
Here's what I learned from the review...