1. Wednesday 9/20 Syllabus Info Session Ansys Training
Simulation vs Engineering
Project Statement
Moonshine Event

2. https://goo.gl/forms/nyfI0xMm7kpmOMTJ2

3. Syllabus 4
M9/18 W 9/20
F 9/22
Resumes, Communication and Listening (BW)
Oral Presentations, Design Reviews (BW/VM)
Ansys Training 5
M 9/25 W 9/27
Moonshine
Reading People, Personality Types, Jackie Gallo
No class meeting, Whitcraft Moonshine event prework 6
M 10/2 W 10/4
F 10/6
Prj Schedule
Proj St’ment
Hardware Ordering, Pugh Charts, Unit Problems Oral Presentations 1 Problem, Design Review
Optional Closeout event at Whitcraft 7
M 10/9 W 10/11
Unit Prob
Oral Presentations 1 Problem, Design Review Oral Presentations 1 Problem, Design Review 8
M 10/16 W 10/18
Theory
Unit Prob.
Oral 1 Feedback/References, Theory (BW/VM?) Marketing Dr. Mary Caravella

4. A World Leader in the Design, Manufacture,
and Service of Aircraft Engines
Wednesday, September 20, 2017
6:00 – 9:00 PM
Next Generation Hall
University of Connecticut
Represented Groups:
Hot Section, Materials & Processes Engineering, Mechanical Systems, Externals, Fan, and Compression Systems, Controls Diagnostic Systems, Quality and Process Engineering
Please join us for pizza and learn about exciting jobs and internship opportunities at Pratt & Whitney!
This page contains no technical data subject to the EAR or the ITAR

5. Ansys Training Friday September 22 Thermo /Fluids
12:00 to 5:00 EII Rm 202
Dr. Kringan Saha, Sr. Application Engineer
All teams should be there for start
Structures/Mechanics –TBD
Work around your class schedule

6. Objectives Overview of Ansys and Ansys Fluent
Simulation setup and meshing
Simple problems
Available training and other resources for students
Contact Name(s)

7. Expected to Attend

8. Moonshine Event Whitcraft ,LLC World Class Lean Manufacturing
76 County Rd
Eastford CT
14 mi from campus

9. Why are We Doing This?
Most difficult part for a team is to “get something done” – learning
Teaming Event
Applies to all teams (including Acc Masters)
Non US Citizens can participate
Team Competition – fun
Google form NLT Friday (this week)

10. Presentation Topics basics of kaizen (“continual improvement”)
moonshine examples
-moonshine war project criteria for the teams

11. Expected to Participate

12. Project Statement .

13. What is a Project Statement?
A project usually begins with a vague need expressed by a sponsor (internal or external).
The purpose of a project statement is to define the problem to be solved so that work can begin on the project.
Once the project is completed, the sponsor will be satisfied with the result.
Beginning of your Interim (final) report

14. Stages of Building a Project Statement
Contact key individuals in the sponsoring organization (or the internal division).
Arrange to meet with sponsor
Background research – before visit
Ask questions
Listen
Take good notes in your design notebook – write stuff down!!
At conclusion of meeting, summarize and restate what you heard

15. Format for the Project Statement
Cover Page
Body: Project Statement with all the necessary elements (as described before) clearly labeled.
Additional Information: Identify key technical areas/skills used in the project.

17. Body of Statement Statement of Need Requirements Basic Limitations
-Introduction/Background
Requirements
-What is the project goal(s)?
Basic Limitations
-Metrics/Specifications/other data
Verification Approach
-What are you going to do?
Schedule

18. Elements of a Project Statement
Statement of Need
Preliminary Requirements
Basic Limitations
Other Data
Verification Approach
Schedule

19. Statement of Need A couple of paragraphs
Include brief overview of sponsor
Discusses the problem/need
Concise – but detailed enough so you can
talk to it
Does NOT include a solution

20. Preliminary Requirements
Describes the requirements broadly
Level of detail for initial sponsor meeting
Does not require a detailed spec list

21. Basic Limitations Describes known constraints
Notes applicable codes/restrictions
Discusses undesirable features
May include simple sketches

22. Other Data
Includes relevant information that does not fit in other sections such as that about:
equipment,
facilities and/or
policies of sponsoring organization
software*****

23. Specifications (defined)
List the requirements that project must meet.
There are different types of specifications, including those for hardware and software.

24. Specifications (warnings)
In general, you should NOT specify any components.
However, if modifying an existing device [hardware or software], describe the current device in as much detail as possible.

25. Technical Specifications
Contains in a tabular form all of the facts & figures needed to undertake the design project.

26. Specifications Format (example)
Mechanical Parameters (sample)
Button:
Size 5” x 5’’ (min.)
Actuation Force N (max.)
Weight: 5000 lbs. (max.)
Durability: Should survive 10-ft. drops.
Electrical Parameters
Battery Life 6 months (continuous use)
Display:
Number of Characters 30 (minimum)
Size 2’ min. height x 1.75’ min. width
Illumination Visible in strong sunlight

27. Specifications Format (cont.)
Environmental
Location Basement (6’ underground)
Temp. Range -40 to +700 F
Storage temp to 1000 F
Moisture?, Corrosive liquids?, Vibrations?
Software
Execution time seconds (max.)
Termination/Reset 1 button
Interrupts Standard ^C
Memory MB
Platform Windows PC

28. Activity
Follow the instructions as given by Prof. Weber

29. A Final warning: Be Specific!