<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2>Aaron-</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff size=2>I
apologize for the delayed response. I hope my reply is still
useful.</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004>
<LI><FONT face=Arial color=#0000ff size=2>Firstly, what are the actual due dates
for the 2 weekly reports (I am assuming that the dates listed on the SP, April
22nd and 29th, are no longer accurate)? </FONT></LI></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=382064818-14042004>Prof
Hall has responded with the schedule update. I repeat it below for
completeness:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=382064818-14042004><FONT
face="Times New Roman" color=#000000 size=3>(2) SP 9 is a two-week problem.
Originally, Part I was to be due this week (April 15), and Part II was to be due
two weeks later (April 29). This scheduled allowed for the signals lab to
offered in the week in between. Many students expressed their desire to complete
SP 9 in two consecutive weeks. Therefore, Part II of SP 9 will be due <B><?color><?param FFFE,0000,0000><?bigger>April 22, <?/bigger><?/color></B>and
the signals lab will be the following week.</FONT><BR></SPAN></FONT></DIV>
<DIV><FONT><SPAN class=382064818-14042004>
<LI><FONT face=Arial color=#0000ff size=2>Secondly, through the template
document, you refer to both a 'System' and '(Subsystem)' (I.1.1 and I.1.7 are
the first occurrences respectively). What exactly do you mean by 'System'
and '(Subsystem)'? </FONT></LI></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff size=2>In
general filling in the subsections is </FONT><FONT face=Arial color=#0000ff
size=2><STRONG>OPTIONAL</STRONG>! If you have something specific in your system
(people, product, process) that you would like to discuss in detail, please do
so in one or two paragraphs. For example if there is something truly unique or
innovative about your landing gear build procedures, please let me know. I'd
love to read about it! </FONT></SPAN><SPAN class=382064818-14042004><FONT
face=Arial color=#0000ff size=2>Subsystem is just a placeholder for any subpart
of your system that I did not cover in the headings that I gave
you.</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004>
<LI>Thirdly, sub-section 4 of each section, includes a time estimates &
actual table as well as sub-sub-sections for each component. In addition
to the numbers we will put in the table, do you wish for us to write a
justification of our time estimates for each component (in short is this
redundant, or intentional)? </LI></DIV>
<DIV> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff size=2>It
would be nice if you would write a few sentences explaining how you got your
estimates. "We guessed" is fine. "We budgeted." is fine. Or "we extrapolated
from our baseline build" is a fine response. Really this is mostly for your
benefit, to get you use to tracking and estimating performance. This is a good
life skill to have in many situations. You will find in the future that many
organizations have very complex high fidelity models for estimation and
tracking. Best to get you use to the process now so it doesn't look so foreign
to you in the future. </FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#0000ff size=2>In
general documenting a design solution is extremely important. Documentation is
often the artifact we turn to when we are trying to understand why things were
done the way they were done. Without this information humans often have a great
deal of trouble understanding accidents and failures, and modifying systems
without producing grave errors. So documenting your goals, procedures,
estimates and actuals is very important. We'd have a much better understanding
of the spectacular Kemetic (Egyptian), Incan, and Mayan engineering achievements
if we had better documentation of what they did, why they did it and how they
did it. </FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT color=#0000ff size=2>
<LI><FONT face=Arial color=#000000>Fourthly, on the System Performance table
(IV.1) there are several performance criteria with 'Not applicable' listed as
their Actual Value (Required Power, Motor Power, Motor RPM and C<FONT
size=1>L,max</FONT> to be specific). Why is this, are we not equipped to
take actual values or are we just not responsible for those actual values?
</FONT></LI></DIV>
<DIV><FONT face=Arial color=#000000></FONT> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#000000>I guess I
didn't think you would be equipped to measure the actual values, so why ask you
to be responsible for reporting them.</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial
color=#000000></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#000000><FONT
face="Times New Roman">Not directly related to the Weekly Report, do you have
any more information regarding "orientation" for the CNC foam cutter and/or any
other lab safety procedure we might need for Build I &
II.</FONT><BR></FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#000000>OK. I got an
update from Col Young on this. First, there will be no required lab safety
orientation. Secondly, CNC orientation is by appointment with Col Young. E-mail
him at <A href="mailto:pwyoung@mit.edu">pwyoung@mit.edu</A>.</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial
color=#000000></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial color=#000000>Hope this
clearly answers all your questions!</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial
color=#000000></FONT></SPAN> </DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial
color=#000000>Best-</FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004><FONT face=Arial
color=#000000>Charles</FONT></SPAN></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial></FONT><X-TAB></FONT></SPAN></DIV>
<DIV><SPAN class=382064818-14042004></SPAN></SPAN></FONT></SPAN><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Aaron Bell
[mailto:ahbell@MIT.EDU]<BR><B>Sent:</B> Friday, April 09, 2004 12:30
AM<BR><B>To:</B> ccoleman@mit.edu<BR><B>Cc:</B>
backrow@mit.edu<BR><B>Subject:</B> SP9
clarification<BR><BR></DIV></FONT>Professor
Coleman,<BR><X-TAB> </X-TAB>I was
hoping you could clarify a few things regarding Systems Problem 9.
<UL>
<LI>Firstly, what are the actual due dates for the 2 weekly reports (I am
assuming that the dates listed on the SP, April 22nd and 29th, are no longer
accurate)?
<LI>Secondly, through the template document, you refer to both a 'System' and
'(Subsystem)' (I.1.1 and I.1.7 are the first occurrences respectively).
What exactly do you mean by 'System' and '(Subsystem)'?
<LI>Thirdly, sub-section 4 of each section, includes a time estimates &
actual table as well as sub-sub-sections for each component. In addition
to the numbers we will put in the table, do you wish for us to write a
justification of our time estimates for each component (in short is this
redundant, or intentional)?
<LI>Fourthly, on the System Performance table (IV.1) there are several
performance criteria with 'Not applicable' listed as their Actual Value
(Required Power, Motor Power, Motor RPM and C<FONT size=1>L,max</FONT> to be
specific). Why is this, are we not equipped to take actual values or are
we just not responsible for those actual values?
</LI></UL><X-TAB> </X-TAB>Not
directly related to the Weekly Report, do you have any more information
regarding "orientation" for the CNC foam cutter and/or any other lab safety
procedure we might need for Build I & II.<BR>Thanks for taking the time to
address my questions, I hope I haven't been too confusing in my
inquiries.<BR>Regards,<BR><BR>Aaron Bell<BR>Team 14<BR><BR><X-SIGSEP>
<P></X-SIGSEP>Aaron Bell<BR>MIT Class of 2006<BR>Aero/Astro
Engineering<BR>Mobile: (203) 247-6331<BR>Email: ahbell@mit.edu
</P></BODY></HTML>