1 / 21

Technical Communication: Written documents

Technical Communication: Written documents. Introduction to Engineering Systems Lecture 9 (9/25/2009). Prof. Andrés Tovar. Announcements. Technical communication.

azizi
Download Presentation

Technical Communication: Written documents

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Communication: Written documents Introduction to Engineering Systems Lecture 9 (9/25/2009) Prof. Andrés Tovar

  2. Announcements Technical communication Look at the NOTE listed on the lower left hand corner of the design constraints which states that if there is "no bracing allowed" on a given floor you can still add 2 vertical members on the interior plane. SAP is now on computers in cluster and Cushing 303. Instructions for use of SAP in cluster is posted on CONCOURSE. Bring a camera to Learning Center next week if you want a picture of your group or design for the report.  Review Learning Center 6 prior to testing day. In F.O.S. kSAP refers to the stiffness in SAP of unbraced five-story tower.

  3. From last class up to 20 binary design variables per face Technical communication • Optimum refers to the best. • An optimization problems has: • Objective function • Design variables (design space) • Constraints (feasible space) • Optimization methods include: • Graphic • Analytic • Numeric • Heuristic • Factor of safety (F.O.S.) • How to determine • How to use • Probability of failure associated to F.O.S. (cdf) • Results from topology optimization

  4. FAQ on probability m=0;s=1;d=0.01; x=-3*s:d:3*s; f=pdf('norm',x,m,s); plot(x,f) y=[m-3*s,m-2*s,m-s,m,m+s,m+2*s,m+3*s]; p=cdf('norm',y,m,s) p = 0.0013 0.0228 0.1587 0.5000 0.8413 0.9772 0.9987 Source: Wikipedia.com Technical communication Probability in normal distribution

  5. FAQ on probability What is the probability of failure? For N = 1 (one sigma design) P(D ≤ m-s) = 0.1587 ≈ 0.1% + 2.1% + 13.6% Technical communication

  6. DESIGN STAGE CONSTRUCTION & VERIFICATION Investigate Designs using Model Construct Design Optimize Design Experimentally Verify Behavior Predict Behavior Where we are in the tower design process MODEL DEVELOPMENT Gather Data Develop Model Verify Model Technical communication

  7. In-class exercise Technical communication About the report “An Analysis of Colliding Pendulums” • Read the paper and circle/write comments on any problems (5 min) • In groups of 4 work assemble a list of all the problems they find (5 min) • Each group identifies the most relevant issue with the paper • Is there enough information in the report so that another person who has not seen the experiment might be able to repeat it? • Are the calculations clear? Is enough information provided that another person could rework them? Are the variables in equations, including the use of subscripts or superscripts, well-selected and their meaning clearly defined. • Are tables and graphs clear and unambiguous? • Are there spelling or grammatical errors, or poor word choice? • Is there appropriate use of references? • Are the conclusions drawn from the results reasonable?

  8. In-class exercise Technical communication About the report “An Analysis of Colliding Pendulums” – Section 3 • Lacking explanation • Lack of clarity • Charts have no labels • Poor use of references • Blames others • Unclear procedures • Unrealistic results • Poor grammar and spelling • Poor explanation of formulas • The experiment cannot be recreated

  9. In-class exercise • Too informal • No info in abstract Technical communication About the report “An Analysis of Colliding Pendulums” – Section 4 • Not enough information • Graph doesn’t have title nor units • Blames others • Graph’s lines are the same • No citations • Procedure is out of order • Figure’s captions not defined • Not explicit equation • No units on table • Variables are undefined • Misspellings and grammatical errors • Wrong conclusion • Significant figures don’t match in table

  10. About equations C Technical communication

  11. About equations B Technical communication

  12. About equations A Technical communication

  13. About equations Technical communication Use punctuation. Equations are part of the sentence. Do not use mathematical symbols unless they serve a purpose. Avoid starting a sentence with a mathematical expression. Use equations that are easy to read, e.g., exp instead of e. An equation is displayed when it needs to be numbered, when it be hard to read in-line, or when it merits special attention. Reference earlier (not future) equations. Do not use a letter as a dummy variable if it already serves other purpose, e.g., e, i. Be aware of universally accepted symbols, e.g., ∞, p, e, i.

  14. Table number and caption above Table 1: Results of 6 trial launches of a softball from the slingshot column headings with units Technical communication

  15. Plot title label axes with units line for theoretical result or best-fit points for experimental data figure number and caption below Figure 1: Experimental data and best-fit, least squares line for slingshot flight distance vs. pullback Technical communication

  16. Report Expectations Technical communication • Read LC 6 Document! • Read Sample Good Report on Concourse • Body of Report - Limited to 10 pages • Abstract • Introduction • Procedure • Results/Discussion • Conclusion MAKE SURE TO INCLUDE REFERENCES!!!

  17. Rubric for Tower Builder Project Technical communication

  18. What to Bring to Testing Day Technical communication • PRINTOUT OF SAP MODEL • CONSTRUCTED TOWER • DATA FOR UNBRACED TOWER • SAP Stiffness (kSAP) • Mean Stiffness from Experimental Database (mk)

  19. What to Bring to Testing Day Technical communication • DATA FOR BRACED TOWER • Target Deflection Limit State (Dmax) • Factor of Safety • Predicted displacement (DSAP) • Bracing Ratio: B = LTotal/3000 mm • Stiffness Ratio (SAP): S = kbraced/kunbraced • Predicted Efficiency Ratio: E = S/B

  20. Testing Day • No Instructions given on Test Day • READ LC 6 Document!! • Testing procedure identical to that used in Learning Center 1, repeating for three trials • Correct for initial displacement • Calculate average displacements • Plot forces vs. displacement in MATLAB and fit line • Correct for spring stiffness • Other Calculations • Stiffness, Bracing, and Efficiency Technical communication

  21. What if My Tower Fails? Technical communication • Teams showing honest effort still receive majority of points • Force-displacement plot will be analyzed for non-linear behavior • Indicates connection failure

More Related