Final report and briefing

1
Final report and briefing
2
Final report requirements

• Each team is responsible for two (2) submittals
• A written report (75 of final report grade)
• Some sections will receive team grades
• Overall System (25 - of written grade)
• (6) Preferred and alternative air vehicles
  (50-60)
• (7) ABET criteria (5)
• - Others will get team or individual grades
• (2) ConOps (assigned student or team _at_ 5)
• (3) Communications (assigned student or team _at_
  5)
• (4) Control station(s) (assigned student or team
  _at_ 5)
• (5) Payload (assigned student or team _at_ 5)
• 2. A briefing (25 of final report grade _at_ 100
  team effort)

1 extra credit problem
Depending on how team responsibility assigned
(if individual student, name must appear on
assigned section
3
Written report

• Assume that I have released a request for
  proposal (RFP) and that your team is trying to
  sell me on your selected baseline concept. The
  purpose of the write-up is to convince the
  customer (me) that you have carefully thought
  through the system design concept issues and that
  your system concept is viable (note your
  customer has no tolerance for fluff or
  unsubstantiated performance claims)
• There is no requirement to stay with the starting
  system concept described in previous individual
  student reports. If your team has found problems
  with the original concept and/or made
  improvements, describe the changes and the
  accompanying rationale.
• Submit your team report as a MSWord email
  attachment by COB Thursday, May 6 (no penalty
  for late submittal until 5/14
• For each section assigned to an individual,
  identify the student responsible (for individual
  grades)
• Remember the proposal and briefing up must
  convince me that the team(1) understands my
  requirements, (2) has a good understanding of the
  problem and technical issues and (3) has selected
  the best concept to meet my requirements

4
Report outline read carefully
1.0 Overall system requirements In your own
words describe (list) what the UAV system has to
do (defined requirements). Include follow-up
responses to questions asked as defined
requirements. Also describe (list) system level
derived requirements. 1.1 Overall system
concept describe the preferred system concept
proposed to meet customer requirements. Include
the numbers of air vehicles, payloads, control
stations and communication element ADTs and GDTs
required for 24/7 coverage. Include graphic.
1.3 Alternate systems concepts describe
alternative system concepts you considered and
your rationale for selecting the preferred
concept. Include graphics if needed. 1.2 Overall
cost effectiveness Provide quantitative
evidence that the selected system concept is the
most cost effective solution to meet my
requirements using air vehicle plus payload
procurement cost as the primary figure of merit.
Qualitatively describe why the communications and
control station concepts are cost effective. 1.4
Overall system risks summarize what you think
are the system concept risks excluding the air
vehicle. Briefly discuss what you think should
be done to mitigate the risk
5
Outline (contd)
2.0 Concept of operations Describe the complete
ConOps. Start at home base and describe what
each element does including, numbers, speeds and
altitudes, how missions are performed, how
payloads and air vehicles are controlled and
communicate, how and when they go back to base,
etc. Include graphic. 2.1 Alternate ConOps
describe alternative ConOps considered, their
strengths and weaknesses and your rationale for
final selection. Include graphics if needed. 3.0
Communication system requirements List
communication system requirements, identify which
are defined, which are derived. 3.1 Communication
system concept describe the communications
system and how it operates (physical and
functional description). Include a description
of how ranges, weights, power, etc. were
determined. Include graphic to show
location(s). 3.2 Alternate communications systems
concepts describe alternative communications
concepts considered and your rationale for final
selection. Include graphics if needed.
OK to reference course notes but be specific
6
Outline (contd)
4.0 Control station requirements List control
station requirements identifying which are
defined and which are derived. 4.1 Control
station concept describe the control station(s)
and how it (they) operate (physical and
functional). Include a description of locations,
functions, number and roles of operators,
weights, etc. and how they were derived. Include
graphic to show location(s). 4.2 Alternate
control station concepts describe alternative
control station concepts considered and your
rationale for final selection. Include graphics
if needed. 5.0 Payload requirements List
payload requirements identifying which are
defined and which are derived. 5.1 Payload
concept describe all payload elements and how
they operate (physical and functional
description). Describe how ranges, weights,
power, etc were derived. Provide installation
graphic. 5.2 Alternate payload concepts
describe alternative payloads considered since
mid term and your rationale for final selection.
Include graphics if needed
OK to reference course notes but be specific
7
Outline (contd)
6.0 Air vehicle requirements List air vehicle
requirements, identifying which are defined and
which are derived. 6.1 Preferred air vehicle
physical description Summary description of air
vehicle(s) including configuration sketch and
configuration data list per Air Vehicle Design
Report (AVDR) section 3.1. 6.2 Preferred air
vehicle functional description Summarize how
air vehicle(s) perform primary and secondary
missions (from engine start to shut down) per
AVDR 3.2 6.3 Preferred air vehicle optimization
Summarize trade study results to convince me that
the concept is reasonably optimized (AVDR
4.2) 6.4 Preferred air vehicle performance
estimate primary and secondary mission
performance summary per AVDR 3.3 6.5 Performance
methodology Summarize aero/propulsion/weight,
geometry and mission performance methods per AVDR
3.4 6.6 Preferred air vehicle parametric
comparison Use parametrics to convince me that
your aero/propulsion/weight estimates are
reasonable per AVDR 3.5.
8
Outline (contd)
6.7 Preferred air vehicle parametric correlation
(Extra Credit) - Resize your concept to
approximate an existing air vehicle and
rationalize size and weight differences, if any
6.8 Alternate air vehicle concepts briefly
describe alternative air vehicles considered and
the rationale for selection of the preferred
concept. Show a scaled PowerPoint drawing of each
concept. 6.9 Preferred air vehicle risks
Discuss what you think are the primary risk areas
and what you think can be done to mitigate them
per AVDR 5.1. 6.10 Preferred air vehicle
performance sensitivities Quantify cost
sensitivity to airframe weight and drag and
engine SFC or TSFC per AVDR 5.2.
9
Outline (contd)
7.0 ABET criteria Address each of the
following points and document your conclusions.
Note that not all of these issues may be relevant
to your project, but you should think about them
before concluding that they are irrelevant and
justify your decision. See ASE261.ABET.ppt for
issue details. One short paragraph per issue 7.1
Economic Issues 7.2 Environmental Issues
7.3 Sustainability Issues 7.4
Manufacturability Issues 7.5 Ethics Issues 7.6
Political Issues 7.7 Health and Safety
Issues 7.8 Social Issues 7.9 Global Impact

10
Team briefing

• Each team will present a 30 minute (including 10
  minute QA) PowerPoint briefing on your preferred
  system concept. The purpose of the briefing is
  to convince me (your customer) that your team
• Understands my requirements
• Has carefully thought through the key system
  design issues and come up with a viable overall
  system concept, all of the elements of which are
  identified and should work
• Has carefully thought through the ConOps,
  iterated it with the air vehicle-payload-communica
  tions elements, and come up with a good overall
  solution
• Has systematically optimized the air vehicle
  (engine type or BPR, wing loading, aspect ratio
  and cruise speed/altitude at a minimum) against
  consistent takeoff, climb and/or specific excess
  power and operational loiter time and/or dash
  distance criteria
• Has, based on procurement cost, sized the most
  cost effective air vehicle/payload combination
  for 30 days of 24/7 operations

11
Briefing schedule
Date 7 May Location WRW 112 1200 - TBD 1230
- TBD 1300 - TBD 1330 - TBD 1400 - TBD 1430 -
TBD 1500 - TBD 1530 - TBD 1600 - TBD 1700 - End
12
Evaluation criteria

• Report evaluation criteria (shoot for 20 pages)
• Understanding of the problem 25
• Logic and rationale 25
• Solution viability 25
• Clarity and conciseness 25

• Briefing and QA evaluation criteria (maximum 30
  minutes )
• Understanding of the problem 25
• Technical quality 35
• Briefing quality 15
• Demonstrated knowledge (team) 25