This is an Agency service. ITCD provides this Web page as a courtesy to NASA Headquarters users.
What is the Scientific and Technical Information (STI) Program
The STI Program is a critical component in the worldwide activity of scientific and technical aerospace research and development. Collected from U.S. and international sources, STI is organized according to content prior to being added to the NASA Aeronautics and Space Database (NASD), which is a world-class collection of STI that includes over 4 million bibliographic records and a growing number of full-text documents. A public interface is available through the NASA Technical Reports Server (NTRS).
The STI Program at Langley Research Cener (LaRC) manages the activities of the NASA Center for AeroSpace Information (CASI) in Maryland. CASI is the contract operational arm of the STI Program that acquires, organizes, disseminates and preserves NASA STI.
The STI Program is essential to help NASA avoid duplication of research by sharing information and to ensure that the U.S. maintains its preeminence in aerospace-related industries and education.
Access the STI Program Web Site
(This process is for NASA Headquarters personnel)
This page explains the steps to publish a NASA STI document, including links to reference documents, templates, and other information you need at each stage of the process.
STI Documents You Will Need
The following documents contain the information you need to successfully publish your STI:
Visit the STI Program Web site for more information. Be sure to review the Publish STI page for report templates, layout guidelines, forms, links to the documents mentioned above, and other important information.
Develop an outline and an abstract. The abstract should not exceed 200 words.
Decide what type of document you wish to publish, and find out the publishing requirements for that type of document. There are several things you need to consider that will affect how the process works for your STI. The process will go more smoothly if you make these decisions ahead of time.
- Will the document be in an STI Report Series? (See Chapter 2 of NPR 2200.2). External publication? (See chapter 3 of NPR 2200.2). Also see section 2 of the SP-7602 for more information.
- What are the standards for the type of document you choose? (See chapter 2 of NPR 2200 or publisher’s requirements or specifications.)
- What are the technical reviews (see Guidance and Levels of Technical Review for NASA STI) and dissemination availability reviews (via NASA Form (NF)-1676, Document Availability Authorization, at the NASA Electronic Forms site, required for the type of document you choose?
- What other forms may be needed (Standard Form (SF)-298, Report Documentation Page) for STI Report Series at the NASA Electronic Forms site?
- Who will produce the document? Templates for the STI Report Series are available on the Publish STI page.
- In what final format (electronic, multimedia, paper) do you need your STI? Requirements for electronic file formats are available for review on the Publish STI page.
- What are your deadlines and how will they impact preparation of the STI?
- What level of editing (proofreading, minimal, or extensive) will be recommended to you? Check with the Editing/Graphics/Layout/Printing Office for an explanation of these levels of editing.
Discuss your proposed document with your manager to begin the publication process. You will also want to check the technical and peer review process:
- If your document needs an STI number and how you get it.
- What Headquarters requires to fund a document, if applicable.
- Whether your document should be produced in black and white or color (and what restrictions exist for color).
- If paper copies are needed, and if so, how they are provided.
Once informal approval is granted and you have gotten additional information, go to step 4.
Develop the draft document and determine who will review it for technical content. Technical review is normally done between steps 1 and 2 on NF-1676 (Aug 05 version). See guidance about technical and peer review.
Initiate NF-1676, and route it by following the instructions on the form. The NF-1676 indicates who must review the document to determine the dissemination or if any restrictions will apply to dissemination. Remember that you may not release a document external to NASA (including on a public Web site) or present it at an internal meeting or workshop at which foreign nationals may be present without an approved NF-1676.
The following individuals will sign, or can answer questions about the categories of restrictions on, the NF-1676.
Export Control Administrator (signs for ITAR and EAR restrictions)
• Ken Hodgdon
• David Richards
Intellectual Property/Patent Counsel (signs, if applicable, and answers questions on 3c and 4 of NF-1676)
• Jeff Heninger
• Helen Galus
Physical Security (answers questions on National Security Classification and SBU (Sensitive But Unclassified) categories)
• James Nicholas
HQ Document Availability Authorization (DAA) Representative (signs, assigns STI Report Series number, sends NF-1676 and files to NASA CASI)
• Darline Brown
Printing and Design Office (for Editing/Graphics/Layout/Printing specifics)
• Dwight Bennett
Based on reviews, make changes to your draft STI and prepare the final report. Once the review process is complete, the STI is in final form and the NF-1676 has been approved, send the electronic files of the STI and a copy of the NF-1676 to the Headquarters DAA representative. He or she will send the electronic files and copy of the DAA to the NASA Center for AeroSpace Information (NASA CASI), NASA’s STI repository. NASA CASI will enter it into the STI database.
Submit your STI in as final form as possible to the NASA Contracting Officer (CO). The NASA CO will send your STI to the appropriate NASA Contracting Officer's Technical Representative (COTR), who determines if NASA will publish it externally or utilize it internally. The NASA COTR will handle the necessary steps to process the document. When the document has been processed, the COTR should notify you.