24
[Fill in sections 4, 7, 9, 16 and 17.] Technical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] 6. 7. Author(s) 8. Performing Organization Report No. 9. Performing Organization Name and Address 10. Project/Task/Work Unit No. [Department] [University] [Address] 11. Contract (C) or Grant (G) No. 12. Sponsoring Organization Name and Address 13. Type of Report and Period Covered Minnesota Department of Transportation Office of Research & Innovation 395 John Ireland Boulevard, MS 330 St. Paul, Minnesota 55155-1899 14. Sponsoring Agency Code 15. Supplementary Notes http://mndot.gov/research/reports/2019/2019XX.pdf 16. Abstract (Limit: 250 words) 17. Document Analysis/Descriptors 18. Availability Statement [Keyword 1, keyword 2, keyword 3, keyword 4, etc.] No restrictions. Document available from: National Technical Information Services, Alexandria, Virginia 22312 19. Security Class (this report) 20. Security Class (this page) 21. No. of Pages 22. Price

Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

  • Upload
    others

  • View
    6

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

[Fill in sections 4, 7, 9, 16 and 17.]

Technical Report Documentation Page1. Report No. 2. 3. Recipients Accession No.

MN/RC 2019-XX4. Title and Subtitle 5. Report Date

      [Month 201X]6.

7. Author(s) 8. Performing Organization Report No.

     9. Performing Organization Name and Address 10. Project/Task/Work Unit No.

[Department][University][Address]

     11. Contract (C) or Grant (G) No.

     

12. Sponsoring Organization Name and Address 13. Type of Report and Period Covered

Minnesota Department of TransportationOffice of Research & Innovation395 John Ireland Boulevard, MS 330St. Paul, Minnesota 55155-1899

     14. Sponsoring Agency Code

15. Supplementary Notes

http://mndot.gov/research/reports/2019/2019XX.pdf16. Abstract (Limit: 250 words)

     

17. Document Analysis/Descriptors 18. Availability Statement

[Keyword 1, keyword 2, keyword 3, keyword 4, etc.] No restrictions. Document available from: National Technical Information Services, Alexandria, Virginia 22312

19. Security Class (this report) 20. Security Class (this page) 21. No. of Pages 22. Price

Unclassified Unclassified      

Page 2: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

[Report Title -- Limited to 250 characters including spaces, but may be several lines long. Add or delete blank lines to keep all this info on one page.] (“Title” style)

FINAL REPORT

Prepared by:

[Example: Author #1Author #2Department of Civil EngineeringUniversity of Minnesota][Example: Author #3Department of Redundancy DepartmentUniversity of Texas]

[Publication Month and Year]

Published by:

Minnesota Department of TransportationOffice of Research & Innovation395 John Ireland Boulevard, MS 330St. Paul, Minnesota 55155-1899

This report represents the results of research conducted by the authors and does not necessarily represent the views or policies of the Minnesota Department of Transportation or [author’s organization]. This report does not contain a standard or specified technique.

The authors, the Minnesota Department of Transportation, and [author’s organization] do not endorse products or manufacturers. Trade or manufacturers’ names appear herein solely because they are considered essential to this report.

Page 3: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

ACKNOWLEDGMENTS (“TITLE” STYLE)

[Acknowledge Technical Advisory Panel members and others here. Keep Acknowledgments to about 1/3 page, if possible. Use the “paragraph” style for all report body text.]

Page 4: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

TABLE OF CONTENTS (“TITLE” STYLE)

CHAPTER 1: Introduction (“Level 1 Heading” style)...............................................................................1

1.1 [SUBHEAD HERE] (“Level 2 Heading” style).......................................................................................1

1.1.1 [Subhead Here] (“Level 3 Heading” style)..................................................................................1

CHAPTER 2: [Title Here] (“Level 1 Heading” style).................................................................................3

CHAPTER 3: [Title Here] (“Level 1 Heading” style).................................................................................4

CHAPTER 4: [Title Here] (“Level 1 Heading” style).................................................................................5

CHAPTER 5: [Title Here] (“Level 1 Heading” style).................................................................................6

REFERENCES (“Title” style)...................................................................................................................7

APPENDIX A (“Level 1 Heading” Style) [A’S TITLE HERE – NO PAGE NUMBER]

APPENDIX B (“Level 1 Heading” Style) [B’S TITLE HERE – NO PAGE NUMBER]

APPENDIX C (“Level 1 Heading” Style) [C’S TITLE HERE – NO PAGE NUMBER]

LIST OF FIGURES (“TITLE” STYLE)

Figure 1.1 Sample photo. [use “Caption” style; include image source credit if applicable].........................1

Figure 1.2 Sample chart. [use “Caption” style; include image source credit if applicable]..........................2

LIST OF TABLES (“TITLE” STYLE)

Table 1.1 Sample table [use “Caption” style]..............................................................................................2

Page 5: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

LIST OF ABBREVIATIONS (optional; “TITLE” STYLE)

[If the report contains a long list of frequently-used abbreviations, include the list before the Executive Summary.]

Page 6: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

EXECUTIVE SUMMARY (“TITLE” STYLE)

[The executive summary should be

Concise. Present a synopsis of the research issue, the main findings or results, conclusions, the significance of the research, and recommendations.

3 (or fewer) pages. A stand-alone summary of the research project.

Readers often turn first to the executive summary for an overview of the project. Because of its importance, you may be asked to rewrite or rework the executive summary to better reflect the research project findings and conclusions.]

Page 7: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

CHAPTER 1: INTRODUCTION (“LEVEL 1 HEADING” STYLE)

1.1 [SUBHEAD HERE] (“LEVEL 2 HEADING” STYLE)

1.1.1 [Subhead Here] (“Level 3 Heading” style)

1.1.1.1 [Subhead Here] (“Level 4 Heading” style)

[Use “Paragraph” style and insert text. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.]

Figure 1.1 Sample photo. [use “Caption” style; include image source credit if applicable] [Sample alternative text: “Color photograph of two MnDOT employees inspecting pavement.” See Appendix G in the MnDOT Research Report Guidelines for additional help on alt-text.]

Page 8: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

Category 1 Category 2 Category 3 Category 40

1

2

3

4

5

6

Series 1Series 2Series 3

Figure 1.2 Sample chart. [use “Caption” style; include image source credit if applicable]

Table 1.1 Sample table [use “Caption” style; if table spans multiple pages, please repeat headers at the top of each page for accessibility purposes]

Cell 1 Cell 2

[Arrange other chapters to fit your project’s content and organization.]

Page 9: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

CHAPTER 2: [TITLE HERE] (“LEVEL 1 HEADING” STYLE)

[Text starts here.]

Page 10: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

CHAPTER 3: [TITLE HERE] (“LEVEL 1 HEADING” STYLE)

[Text starts here.]

Page 11: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

CHAPTER 4: [TITLE HERE] (“LEVEL 1 HEADING” STYLE)

[Text starts here.]

Page 12: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

CHAPTER 5: [TITLE HERE] (“LEVEL 1 HEADING” STYLE)

[Text starts here. Add more chapters as needed to clearly communicate your research.]

Page 13: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

REFERENCES (“TITLE” STYLE)

[Use a well-known bibliographic format, preferably the Chicago Manual of Style (author-date system) or the APA (American Psychological Association).

List complete references, including names of authors or editors; article title; chapter, book, journal, or report title; publisher or issuing agency; location of publisher; year of publication; volume and issue or report number; DOIs; and page numbers.

Attribute unpublished material, telephone conversations, and other personal communication in the reference section.

For web sources, include the complete URL and the date accessed.

When (Author, Date) citations are used in the text, alphabetize this list.

If numbered citations are used in the report, references should be listed in the order in which they are referred to in the text. List each reference only once in this numbered list. Use the same number to refer to that text multiple times. When numbered, references do not need to be alphabetical.]

Resources: Chicago Manual of Style

The following website provides assistance on formatting common sources such as books, journal articles, and websites. Be sure to follow the “author/date” instructions.

http://www.chicagomanualofstyle.org/tools_citationguide.html

Here are sample citations for less common types of sources:

Technical report:

Swenson, Tanner W., and Catherine E. French. Effect of Temperature on Prestressed Concrete Bridge Girder Strand Stress During Fabrication. Minnesota Department of Transportation, December 2015. http://www.cts.umn.edu/Publications/ResearchReports/reportdetail.html?id=2476.

Standard:

ASTM International. ASTM C990-09(2014) Standard Specification for Joints for Concrete Pipe, Manholes, and Precast Box Sections Using Preformed Flexible Joint Sealants. West Conshohocken, PA: ASTM International, 2014. doi:http://dx.doi.org/10.1520/C0990.

Presentation:

Hanstedt, Paul. “This is Your Brain on Writing: The Implications of James Zull’s The Art of Changing the Brain for the Writing Classroom.” Presentation at the Annual Convention of the

Page 14: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

Conference on College Composition and Communication, San Francisco, CA, March 11-14, 2009.

Resources: American Psychological Association (APA)

The following website provides assistance on formatting common sources such as books, journal articles, and websites:

http://writing.umn.edu/sws/assets/pdf/quicktips/apa_References.pdf

Here are sample citations for less common types of sources:

Technical report:

Swenson, T. W., & French, C. E. (2015, December). Effect of Temperature on Prestressed Concrete Bridge Girder Strand Stress During Fabrication. Retrieved from http://www.cts.umn.edu/Publications/ResearchReports/reportdetail.html?id=2476

Standard:

ASTM International. (2014). ASTM C990-09(2014) Standard Specification for Joints for Concrete Pipe, Manholes, and Precast Box Sections Using Preformed Flexible Joint Sealants. Retrieved from http://dx.doi.org/10.1520/C0990

Presentation:

Adams-Labonte, S. K. (2012, August). Daytime impairment due to college students’ technology use during sleep: Similarities to sleep apnea. Poster session presented at the meeting of the American Psychological Association, Orlando, FL.

[Ensure “NEXT PAGE” section break is inserted before Appendix Cover]

Page 15: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

APPENDIX A (“LEVEL 1 HEADING” STYLE)[A’S TITLE HERE – NO PAGE NUMBER]

[Ensure “NEXT PAGE” section break is inserted after appendix title and that footer is blank with “link to previous” NOT selected]

Page 16: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

[Appendix A text or tables here. Please use original (and not scanned) documents whenever possible. If appendices are not needed, simply delete these sections.]

[Ensure that page number is inserted with letter marker in footer and “link to previous” is NOT selected. Add “next page” section break to the page before the next appendix chapter, if applicable]

A-1

Page 17: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

APPENDIX B (“LEVEL 1 HEADING” STYLE)[B’S TITLE HERE – NO PAGE NUMBER]

Page 18: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

[Appendix B text or tables here. Page number B-1 and so on.]

B-1

Page 19: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

APPENDIX C (“LEVEL 1 HEADING” STYLE)[C’S TITLE HERE – NO PAGE NUMBER]

Page 20: Report Title · Web viewTechnical Report Documentation Page 1. Report No. 2. 3. Recipients Accession No. MN/RC 2019-XX 4. Title and Subtitle 5. Report Date [Month 201X] [Report Title

[Appendix C text or tables here. Page number C-1 and so on.]

C-1