14Q80068_Attachment_No._2.doc
DOC document 2 MB Posted
- Attached to
- Abdominal Impact Testing of the Hybrid III Rail Safety Anthropomorphic Test Device (ATD)
- Solicitation number
- DTRT5714Q80068
About this file
Attachment No. 2
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 14Q80068_SOW_8-14.doc | DOC document | |
| 14Q80068_Attachment_No._3.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Draft
[PLEASE INSERT COVER ART]
(photo or illustration)
NOTICE
This document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof. Any opinions, findings and conclusions, or recommendations expressed in this material do not necessarily reflect the views or policies of the United States Government, nor does mention of trade names, commercial products, or organizations imply endorsement by the United States Government. The United States Government assumes no liability for the content or use of the material contained in this document.
NOTICE
The United States Government does not endorse products or manufacturers. Trade or manufacturers’ names appear herein solely because they are considered essential to the objective of this report.
REPORT DOCUMENTATION PAGE
Form Approved
OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.
1. AGENCY USE ONLY (Leave blank)
2. REPORT DATE
Month 20XX
3. REPORT TYPE AND DATES COVERED
Technical Report
4. TITLE AND SUBTITLE
5. FUNDING NUMBERS
6. AUTHOR(S)
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)
Contracting Agency Name Street Address City, State 02451-1196
8. PERFORMING ORGANIZATION REPORT NUMBER
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)
U.S. Department of Transportation
Federal Railroad Administration
Office of Railroad Policy and Development
Office of Research and Development
Washington, DC 20590
10. SPONSORING/MONITORING
AGENCY REPORT NUMBER
DOT/FRA/ORD-XX/XX
11. SUPPLEMENTARY NOTES
COR:
12a. DISTRIBUTION/AVAILABILITY STATEMENT This document is available to the public through the FRA Web site at http://www.fra.dot.gov.
12b. DISTRIBUTION CODE
13. ABSTRACT (Maximum 200 words)
[INSERT ABSTRACT]
14. SUBJECT TERMS
[INSERT SUBJECT TERMS]
15. NUMBER OF PAGES
xxx
16. PRICE CODE
17. SECURITY CLASSIFICATION
OF REPORT
Unclassified
18. SECURITY CLASSIFICATION
OF THIS PAGE
Unclassified
19. SECURITY CLASSIFICATION
OF ABSTRACT
Unclassified
20. LIMITATION OF ABSTRACT
NSN 7540-01-280-5500
Standard Form 298 (Rev. 2-89)
Prescribed by ANSI Std. 239-18
298-102
METRIC/ENGLISH CONVERSION FACTORS
| ENGLISH TO METRIC |
| METRIC TO ENGLISH |
| LENGTH (APPROXIMATE) |
| LENGTH (APPROXIMATE) |
| 1 inch (in) |
| = |
| 2.5 centimeters (cm) |
| 1 millimeter (mm) |
| = |
| 0.04 inch (in) |
| 1 foot (ft) |
| = |
| 30 centimeters (cm) |
| 1 centimeter (cm) |
| = |
| 0.4 inch (in) |
| 1 yard (yd) |
| = |
| 0.9 meter (m) |
| 1 meter (m) |
| = |
| 3.3 feet (ft) |
| 1 mile (mi) |
| = |
| 1.6 kilometers (km) |
| 1 meter (m) |
| = |
| 1.1 yards (yd) |
| 1 kilometer (km) |
| = |
| 0.6 mile (mi) |
| AREA (APPROXIMATE) |
| AREA (APPROXIMATE) |
| 1 square inch (sq in, in2) |
| = |
| 6.5 square centimeters (cm2) |
| 1 square centimeter (cm2) |
| = |
| 0.16 square inch (sq in, in2) |
| 1 square foot (sq ft, ft2) |
| = |
| 0.09 square meter (m2) |
| 1 square meter (m2) |
| = |
| 1.2 square yards (sq yd, yd2) |
| 1 square yard (sq yd, yd2) |
| = |
| 0.8 square meter (m2) |
| 1 square kilometer (km2) |
| = |
| 0.4 square mile (sq mi, mi2) |
| 1 square mile (sq mi, mi2) |
| = |
| 2.6 square kilometers (km2) |
| 10,000 square meters (m2) |
| = |
| 1 hectare (ha) = 2.5 acres |
| 1 acre = 0.4 hectare (he) |
| = |
| 4,000 square meters (m2) |
| MASS - WEIGHT (APPROXIMATE) |
| MASS - WEIGHT (APPROXIMATE) |
| 1 ounce (oz) |
| = |
| 28 grams (gm) |
| 1 gram (gm) |
| = |
| 0.036 ounce (oz) |
| 1 pound (lb) |
| = |
| 0.45 kilogram (kg) |
| 1 kilogram (kg) |
| = |
| 2.2 pounds (lb) |
| 1 short ton = 2,000 pounds (lb) |
| = |
| 0.9 tonne (t) |
| 1 tonne (t) |
1,000 kilograms (kg)
1.1 short tons
| VOLUME (APPROXIMATE) |
| VOLUME (APPROXIMATE) |
| 1 teaspoon (tsp) |
| = |
| 5 milliliters (ml) |
| 1 milliliter (ml) |
| = |
| 0.03 fluid ounce (fl oz) |
| 1 tablespoon (tbsp) |
| = |
| 15 milliliters (ml) |
| 1 liter (l) |
| = |
| 2.1 pints (pt) |
| 1 fluid ounce (fl oz) |
| = |
| 30 milliliters (ml) |
| 1 liter (l) |
| = |
| 1.06 quarts (qt) |
| 1 cup (c) |
| = |
| 0.24 liter (l) |
| 1 liter (l) |
| = |
| 0.26 gallon (gal) |
| 1 pint (pt) |
| = |
| 0.47 liter (l) |
| 1 quart (qt) |
| = |
| 0.96 liter (l) |
| 1 gallon (gal) |
| = |
| 3.8 liters (l) |
| 1 cubic foot (cu ft, ft3) |
| = |
| 0.03 cubic meter (m3) |
| 1 cubic meter (m3) |
| = |
| 36 cubic feet (cu ft, ft3) |
| 1 cubic yard (cu yd, yd3) |
| = |
| 0.76 cubic meter (m3) |
| 1 cubic meter (m3) |
| = |
| 1.3 cubic yards (cu yd, yd3) |
| TEMPERATURE (EXACT) |
| TEMPERATURE (EXACT) |
| [(x-32)(5/9)] F |
| = |
| y C |
| [(9/5) y + 32] C |
| = |
| x F |
For more exact and or other conversion factors, see NIST Miscellaneous Publication 286, Units of Weights and Measures. Price $2.50 SD Catalog No. C13 10286 Updated 6/17/98 Acknowledgements (optional) Contents
1Executive Summary
1.
Introduction 1.1 Background 1.2 Objectives 1.3 Overall Approach 1.4 Scope 1.5 Organization of the Report 2.
Section 2 Title 2.1 Subsection 1 2.2 Subsection 2 3.
Conclusion 4.
References Appendix A. Appendix Title Abbreviations and Acronyms
Illustrations
2Figure 1.
Tables
2Table 1.
Executive Summary
Text
1. Introduction
Introductory Paragraph
1.1 Background
Text
Figure 1.
1.2 Objectives
Text
1.3 Overall Approach
Text
1.4 Scope
Text
1.5 Organization of the Report
Text
2. Section 2 Title
Introductory Paragraph
2.1 Subsection 1
Text
2.2 Subsection 2
Text
2.2.1 Subheading 1
Table 1.
2.2.2 Subheading 2
2.2.3 Subheading 3
Text
Heading 4
Text Heading 5
Text
3. Conclusion
4. References
Appendix A.
Appendix Title Abbreviations and Acronyms
| BLE |
| Brotherhood of Locomotive Engineers |
| CFR |
| Code of Federal Regulations |
| FMVSS |
| Federal Motor Vehicle Safety Standards |
| MBTA |
| Massachusetts Bay Transit Authority |
| OSHA |
| Occupational Safety and Health Administration |
| UTU |
| United Transportation Union |
Social Media Posting
Social Media Accounts:
Facebook: facebook/usdotfra
Twitter: twitter/usdotfra
YouTube: youtube/usdotfra
Would you like to share this report on FRA’s social media pages?
YES FORMCHECKBOX
Please provide the following:
1) For a Facebook post: 2–3 sentences about the report, along with any images, pictures, graphs, or charts that support the content.
(Insert info here)
2) For a Twitter tweet: 140 characters or less on the subject of the report.
(Insert info here)
3) Who is the target audience for this report? (e.g., railroaders, management, policy makers, etc.)
(Insert info here)
4) Why is it important to distribute information about this report on social media?
(Insert info here)
NO FORMCHECKBOX
Please provide a brief explanation for choosing not to share.
(Insert info here) Samples:
Facebook:
Twitter:
Contact the social media team at fra.socialmedia@dot.gov with any questions.
Title – in text box
�Office of Research�and Development�Washington, DC 20590
U.S. Department of Transportation
Federal Railroad Administration
DOT/FRA/ORD-XX/XX�
Draft Final Report�Month 20XX�
�An Acknowledgments page is an optional section of the report. Acknowledgment of FRA staff is not necessary. A simple statement that indicates the work was funded by the FRA Research and Development program is all that is required.
(Please use paragraph and heading styles set up in this document to enable proper Table of Contents compilation and to maintain format.)
The Executive Summary
We write an executive summary for readers who want to quickly understand the results, recommendations and main, supporting points of our research. Your executive summaries must be succinct and clear. These guidelines will help you write effective executive summaries:
State the result of the research in the first sentence. Write it in the active voice. For example:
---Transportation Technology Center, Inc. tested a full-size passenger railcar and demonstrated the car’s ability to withstand an 800,000-pound force compressive load.
Then, state the recommendations or next steps:
---The same car will now be tested to determine its ultimate strength under compressive loading.
Then, give some relevant background:
---The purpose of this series of tests is to validate the proposed waiver guidelines to the crashworthiness requirements in the Code of Federal Regulations—49 CFR 238.203.
Then, summarize the report’s main points. Make sure they appear in the same order as they are in the body of the report.
Use the same key words and phrases from the body of the report in the executive summary.
Do not include information in the executive summary that does not appear in the main report.
Use Plain English. The following link takes you to a checklist:
� HYPERLINK "http://www.plainlanguage.gov/howto/quickreference/checklist.cfm" �www.plainlanguage.gov/howto/quickreference/checklist.cfm�
Aim for an executive summary that is one to two pages long.
Writing Style
For rules related to grammar, spelling, punctuation, and general form, FRA uses the U.S. Government Printing Office’s (GPO) Style Manual as a guide which is available online at � HYPERLINK "http://www.gpoaccess.gov/stylemanual/browse.html" ��www.gpoaccess.gov/stylemanual/browse.html�.
About Plain Language
Plain language or Plain English is communication your audience can understand the first time they read or hear it. Avoid passive voice, long sentences, and jargon, in other words, “government-ese!”
�An introductory paragraph should engage your reader. It lets the reader know what the topic/subject of the report is and explains why the research is relevant.
�The Background should discuss the origins of the research project and previous research studies that are of relevance to the topic at hand. This section should provide a general overview of those prior research studies and projects, not an in-depth review. A more in-depth discussion of previous studies may be made in upcoming sections of the report.
�In this section, the report will discuss the goals of the research program/project being carried out. Is the goal to enhance an already-existing technology? To implement a new safety program? Here you will identify the end goal of the research.
�What research methods and/or strategies are being used to conduct the research? Will the approach be quantitative, qualitative, a mixed-method approach, or other?
�In the Objectives section of the paper, you’ve explained the intended goal of the research. In the Scope section, you’ll explore the limitations of that research. The scope identifies the parameters of the project, including the requirements necessary to achieve the stated objectives.
�FRA’s technical reports are organized by sections, subsections, etc., which are all clearly indicated with sequential numbers and section titles, as shown in this template. To avoid redundancy and repetition, please follow as closely as possible these guidelines for section content.
�The following sections and subsections further delve into the primary research question. These sections may also offer more in-depth discussion of prior research studies and projects pertaining to the main research topic.
Sections that may be included in the Technical Reports are: Method, Analysis, Testing, Results, and Discussion.
�The conclusion of the report indicates why the preceding information is important. It briefly revisits the main points of the report to gesture towards future implications of the research. While the conclusion does not introduce new topics or ideas, it does consider the broader implications of the research question, discuss possibilities for future research, and restate the significance of the research findings.
�This section provides the information a reader would need to locate the articles, journals, and/or other publications referred to in the report.
Please see the U.S. Government Printing Office Style Manual’s section titled “Bibliographies or references (2008)” for guidelines on citation formats for different documents.
�Below is a sample Abbreviations and Acronyms list. Be sure to include on this page all abbreviations and acronyms that appear in the report.
ii
_962466326
_962466325
File details come from the government source that posted it. Updated .