Search Dryden

Go

Text Size

The Dryden Publications Manual

NASA Report Series Procedure Details

The preceding steps are explained in further detail below:

1. Collect and analyze data. This step is the beginning of the reporting process in which the author(s) collect and analyze their data, whether it is flight data, ground-based information, or theoretical derivation. From this data, results are determined, and conclusions are drawn.

2. Prepare outline / abstract. Once the data have been obtained and preliminary results determined, a proposed outline should be made and an abstract written for the outline review. The abstract should include the purpose of the research and give some preliminary results and conclusions. Sample figures that show typical results should be included.

3. Schedule outline review. Contact the Code R research reports facilitator to schedule an outline review. This requirement can be waived for senior authors with approval of the Code R research reports facilitator or Directorate office. At this time, a technical review chairperson will be chosen by the Code R research reports facilitator, usually with the advice of the appropriate branch chief. A time and location will be scheduled for the outline review and appropriate people notified. Copies of the outline and abstract will be distributed to the Code R research reports facilitator, the technical review chairperson, and the author's branch chief. A sample of an outline and abstract is given in Appendix C.

4. Outline review. At this meeting, the author(s) presents to the author's branch chief and the Code R research reports facilitator the author's thoughts on the tone of the report, subject matter to be covered, scope or depth to be covered, preliminary results and conclusion derived from the data.

5. Submit DAA. At this point, the author, with the assistance of the RA Branch documentation specialist, submits DAA (Appendix A) to the Code R Directorate for approval.

6. Write draft. This is where the real work begins. The author completes the analysis of the data and reports the results and conclusions of the research in the draft. The text should be double spaced and pages numbered. The figures should all have proper titles, and be numbered. Each one should be referred to in the text. All concluding remarks or conclusions must be in the discussion of the results. Copies of the NASA Publications Manual, NASA SP-7047, are available from the TPO, Room 1048 to use as a guide to the recommended sections and style of NASA reports.

7. Review draft. When the author completes a draft of the report, the author submits it to the branch chief or designee for review. The branch chief will review the draft report for technical content and writing clarity. The reviewer should not try to "wordsmith" the draft because that will be done by professionals in the final editing. The branch chief or designee needs to make a thorough and complete review of the draft at this point. A poor quality branch reviewed draft will reflect badly on the branch otherwise.

8. Incorporate comments. The author reviews the comments of the branch chief or designee and incorporates the changes to the report as necessary. Several iterations with the branch chief or designee may be required.

9. Review revised draft. The branch chief or designee reviews the final draft of the report and if satisfied with the report content and style, signs and dates the approval form, DFRC Form 54. A copy of the approval cards are shown in Appendix B.

10. Schedule technical review. After the revised draft has been approved by the branch chief, a technical review is scheduled by the Code R research reports facilitator and the rest of the committee is selected. Recommendations for technical committee members may be solicited from the author and branch chief. Usually, one member of the committee will be from outside the branch, and at least one should be a participant of the project. For NASA series reports, the committee usually consists of at least four members, including the chairperson. The Code R research reports facilitator has copies of the draft made, then assemblies and distributes them.

11. Peer review. The committee members should normally receive the draft copy at least one week before the technical review meeting. Members will read the report and, preferably, write down any comments they might have. At the technical review meeting, the committee will discuss their comments with the author(s). The author should bring the report references to the meeting. The responsibilities of the committee members, chairperson, and author are spelled out on the cover letter. If appropriate, the report will be sent out for intercenter review at this time.

12. Incorporate technical review comments. After the technical review meeting, the author collects the review copies and notes from the committee members. The author then reviews them so that the appropriate comments can be incorporated into the report. The author, with the concurrence of the chairperson, need not incorporate technical review comments that the author feels are not appropriate.

13. Review final draft. After the author incorporates the recommendations of the technical review committee, the chairperson reviews the report to see that the recommendations have been followed. If there is a disagreement between the author and chairperson over the incorporation of some of the recommendations, the chairperson has final say but can be overruled by the Research Engineering Directorate Chief. The chairperson signs and dates the approval form when satisfied with the content of the report.

14. Review by Research Engineering Directorate Chief or designee. Submit report to Code R Directorate for review and approval. Attach approval form for signature.

15. Submit approved report to TPO. At this point, the report is given to the TPO for editing. A checklist of other TPO-required material will be provided by the Code R research reports facilitator. A copy of this checklist is given in Appendix I.

16. Edit final draft. The editing of the writing style and content is accomplished at this point. The figures are then sent to Graphics for paste up or electronic imaging. Photos are sent to Imaging Technology and the text is given to tech typing.

17. Final report review. This is the author's last chance to review the text and figures before the printing of the report. The author should carefully review the report for any inadvertent errors or omissions.

18. Incorporate author comments. The editor corrects any errors found by the author during the final report review.

19. Approve author release. The author signs the release form (Appendix J) after giving careful scrutiny to the finished product. At this time, the author also specifies the number of copies of the report desired.

20. Print report. At this point, the report is printed in the Dryden duplicating facility and the TPO distributes copies. If color copying is required, the report must be submitted to the Dryden Printing Officer for approval.

Skip Top nav bar link group
back  Back Table of Contents Forward  forward