05-15-17_RFQ_DPD_1616.pdf

J-2-1

DATA PROCUREMENT DOCUMENT

NO. ISSUE

1616 RFQ

NNM17624019Q

CONTRACT/RFP

EXHIBIT NUMBER

J-2

ATTACHMENT NUMBER

Powder Specification: Iconel 718 for Laser Powder Bed Fusion Additive Manufacturing

PROJECT/SYSTEM

Contractor

CONTRACTOR

May 15, 2017

DATE

National Aeronautics and Space Administration

05/15/17

J-2-2

National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

NO. ISSUE

1616 RFQ

INCORPORATED REVISIONS

OUTSTANDING REVISIONS

AS OF:

05-15-17

SUPERSEDING:

PAGE:

AUTHORITY PORTION AFFECTED - PAGE NO./NO. REMARKS

(DPD Revision) INTRO SGR DRL DRD

J-2-3

1.0 INTRODUCTION

1.1 Scope: Subject to the Rights in Data clause, this Data Procurement Document (DPD) sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required by the DPD for the contract. The contractor shall furnish data defined by the DRDs listed on the Data Requirements List

(DRL) by category of data, attached hereto, and made a part of this DPD. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this DPD. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement

(NFS) clause, that clause shall take precedence over the DPD, consistent with clause FAR 52.215-8.

1.2 DPD Description: This DPD consists of a Document Change Log, an Introduction, a Statement of General

Requirements, DPD maintenance procedures, a DRL, and the DRDs.

1.2.1 General Requirements: The general requirements, as specified in paragraph 2.0 of this DPD, prescribe those requirements applicable to the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRDs.

1.2.2 Data Requirements List (DRL): Throughout the performance of the contract, the DRL provides a listing by data category of the data requirements of the DPD.

1.2.3 Data Requirements Description (DRD)

1.2.3.1 Each data requirement listed on the DRL is given complete definition by a DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements.

1.2.3.2 For the purpose of classification and control, DRDs of this DPD are grouped into the following broad functional data categories:

CATEGORY SYMBOL DESCRIPTION

CD Contractual Data

EE Environmental

MA Management

SA Safety

1.2.3.3 The symbols representing these data categories form part of the prefix of the DRD identification number. The first numerical characters reflect the DPD number.

1.2.3.4 To facilitate the usage and maintenance of the DPD, the DRDs have been sectionalized in accordance with the above data categories.

1.2.3.5 The DRDs are filed by data category and are in alpha-numeric sequence as listed on the DRL page (or pages) that precedes the DRDs.

1.2.4 Document Change Log (DCL): The Document Change Log chronologically records all revision actions that pertain to the DPD.

1.2.5 DPD Maintenance Procedures: Maintenance procedures define the detailed methods to be employed in maintaining the DPD. Detailed maintenance procedures are specified in paragraph 3.0 of this DPD.

1.3 Data Types for Contractual Efforts: The types of data and their contractually applicable requirements for approval and delivery are:

TYPE DESCRIPTION

1* All issues and interim changes to those issues require written approval from the requiring organization before formal release for use or implementation.

J-2-4

2* NASA reserves a time-limited right to disapprove in writing any issues and interim changes to those issues. The contractor shall submit the required data to NASA for review not less than 45 calendar days** prior to its release for use. The contractor shall clearly identify the release target date in the

“submitted for review” transmittal***. If the data is unacceptable, NASA will notify the contractor within 45 calendar days** from the date of submission, regardless of the intended release date***. The contractor shall resubmit the information for reevaluation if disapproved. The submittal is considered approved if the contractor does not receive disapproval or an extension request from NASA within 45 calendar days**.

3 These data shall be delivered by the contractor as required by the contract and do not require NASA approval. However, to be a satisfactory delivery, the data shall satisfy all applicable contractual requirements and be submitted on time.

4 These data are produced or used during performance of the contract and are retained by the contractor.

They shall be delivered only when NASA requests in writing and shall be delivered in accordance with the instructions in the request. The contractor shall maintain a list of these data and shall furnish copies of the list to NASA when requested to do so.

5 These data are incidental to contract performance and are retained by the contractor in those cases where contracting parties have agreed that formal delivery is not required. However, the Contracting Officer or the Contracting Officer’s Representative (COR) shall have access to and can inspect this data at its location in the contractor’s or subcontractor’s facilities, or in an electronic database accessible to the

Government.

* Note: Type 1 and Type 2 data may be placed under NASA configuration management control when designated by NASA. CM control requires the contractor to submit Type 1 and Type 2 data updates through Engineering Change Proposals (ECPs).

** Note: This time limit may be tailored for individual DRDs to meet the requirements of the procuring activity.

*** Note: If the contractor does not identify a release target date or if the intended release date is shorter than 45 calendar days from the date of submission, the 45 calendar days review cycle stands (or the tailored Type 2 time limitation for the specific procurement).

2.0 STATEMENT OF GENERAL REQUIREMENTS

2.1 Applicable/Reference Documents: Documents included as applicable documents in this DPD are the issue specified in the Statement of Work, and form a part of the DPD to the extent specified herein. Applicable documents listed in Item 15.2 of a DRD are applicable only to the preparation of the deliverable documentation described by that DRD.

References to documents other than applicable documents in the data requirements of this DPD may sometimes be utilized, and shall be indicated in 13. Remarks of the DRD. These do not constitute a contractual obligation on the contractor. They are to be used only as a possible example or to provide related information to assist the contractor in developing a response to that particular data requirement.

2.2 Subcontractor Data Requirements

2.2.1 The contractor shall specify to subcontractors and vendors, if any, the availability source of all data required for the satisfactory accomplishment of their contracts. The contractor shall validate these requirements for documents when appropriate; where the requirement concerns other contractor data, the contractor shall provide his subcontractor or vendor with the necessary documents. All such requests shall be accomplished under the auspices of the contractor.

2.2.2 Reference to subcontractor data in the contractor’s responses is permissible, providing the references are adequate and includes such identification elements as title, number, revision, etc., and a copy of the referenced data is supplied with the response document at time of delivery to NASA.

J-2-5

2.3 Data Distribution, Format, Data Restriction Marking, and Transmittal

2.3.1 Distribution: Distribution of required documentation shall be in quantities determined by the Contracting

Officer. Recipient names and email (if applicable) addresses shall be noted on a separate distribution list to be furnished by the Contracting Officer. The Contracting Officer’s letter may include other information pertinent to delivery of data, as required.

2.3.2 Format

2.3.2.1 Electronic Format: Electronic submission of data deliverables is preferred. Electronic deliverables shall be printable. Data deliverables shall be delivered to NASA in the format specified below unless a specific format is required by a DRD. Data submittals shall consist of a single Adobe Acrobat PDF file and the native format electronic file(s). The preferred native formats include Microsoft Word, Excel, PowerPoint or CAD drawing plot file, as appropriate. Where a single native format file is not possible, multiple files may be integrated into a single ZIP file for submission. The organization of the contents of the integrated ZIP file shall be made readily apparent to the reader, and each file within the integrated product shall be clearly identifiable and traceable within the organization of the integrated product. If files are fragmented, file names shall be labeled logically and contiguously, and the files shall be easily reassembled or merged (e.g. 1 filename, 2 filename, 2a filename, etc.). The software versions shall be confirmed prior to submittals.

2.3.2.2 Hardcopy Format: In addition to the electronic submittal, one hardcopy package of specific data deliverables shall be delivered to the NASA Contracting Officer for the Government contract file. The hardcopy package shall consist of the contractor’s Transmittal Memo and one copy of the data deliverable.

2.3.3 Data Restriction Marking

2.3.3.1 Data Restriction Determination and Marking Requirements: The contractor shall determine the data restriction that applies to each data deliverable and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The contractor shall make a determination for each individual data deliverable item, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the contractor applied data restriction, the NASA Contracting

Officer shall return the data to the contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

2.3.3.2 Data Restriction Categories and Marking Statements: The contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

If data delivered under this contract is subject to the International Traffic in Arms Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice

This document contains information which falls under the purview of the U.S. Munitions List (USML), as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

J-2-6

If the contract contains FAR 52.227-14 Alternate II, the “Limited Rights Notice” may be applicable to data

(other than computer software) delivered under this contract.

If the contract contains FAR 52.227-14 Alternate III, the “Restricted Rights Notice” may be applicable to computer software delivered under this contract.

If the contract contains FAR 52.227-20, the “SBIR Rights Notice” may be applicable to SBIR data delivered under this contract.

If the contract contains NFS 1852.237-73, a sensitive information legend may be applicable to information delivered under this contract.

In accordance with the applicable data clause (e.g., FAR 52.227-14(c) or FAR 52.227-20(c)), the contractor may be able to assert a copyright claim in data delivered under this contract. When claim to copyright is made, the Contractor shall affix the applicable copyright notices of 17 U.S.C. 401 or 402 and acknowledgment of

Government sponsorship (including contract number) to the data when such data are delivered to the

Government.

2.3.4 Transmittal

2.3.4.1 Data shall be transmitted to NASA by email, CD or DVD, hardcopy, or other mechanism agreed to by the

Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data deliverables.

2.3.4.2 If email is used to transmit data deliverables, the email size shall be 10 Megabytes or less to ensure receipt by the NASA email servers. Encrypted email format shall be used to transmit data which has been judged sensitive by the contractor (e.g., export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.).

2.3.4.3 Data Transmittal Package: Each data transmittal package shall include:

a. Transmittal memorandum that specifies the meta-data below for each data transmittal:

1. Contract number.

2. Data Requirements Description (DRD) number.

3. DRD data type (specified in Item 3 on the DRD).

4. Submission date or milestone being satisfied.

5. Document number and revision.

6. Document title.

7. File names of all files being delivered; file naming convention shall clearly identify the document being delivered.

8. Distribution (as defined by the Contracting Officer’s letter).

9. Requested response date.

10. Contractor assigned data restriction (export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.) if not marked on data.

11. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS 1441.1, NASA

Records Retention Schedules).

b. Printable electronic files or hardcopy data.

Export Administration Regulations (EAR) Notice

This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR 730-774, and is export controlled. It may not be transferred to foreign nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exception is obtained/available from the Bureau of Industry and Security, United

States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment, or both.

J-2-7

2.3.5 When electronic data deliverables are transmitted directly to the MSFC Repository, the Documentum Webtop web interface shall be utilized. Instructions for electronic data submittals can be found at https://explornet.nasa.gov/docs/DOC-38150. Document submitters to the Repository must register for a

MSFC EDMS (Documentum) user account, through the Identity Management and Account Exchange

(idMAX) system. Computer-Aided Design (CAD) drawings shall be submitted in the original native vector, Hewlett-Packard Graphic Language (HPGL), and raster image formats. For further information, contact the

MSFC Repository Manager.

2.4 Printing: All printing, duplicating, or binding shall be in accordance with NFS 1852.208-81, Restrictions on

Printing and Duplicating. Printing of formal reports and Type 1 and 2 data in book format shall be in accordance with the following general specifications:

a. Method of reproduction – offset/xerography.

b. Finished size – 8 1/2” X 11”.

c. Paper – 20-pound opaque bond.

d. Cover – Litho cover stock.

e. Pages shall be printed on both sides; blank pages shall be avoided when possible.

f. Oversize pages shall be avoided when possible, but if necessary shall be folded to 8 1/2” X 11”.

g. Binding shall be the most economical method commensurate with the size of the report and its intended use.

2.5 Contractor’s Internal Documents: The contractor’s internal documents shall be used to meet the data requirements of this DPD unless a specific format is required by the applicable DRD.

2.6 Document Identification: Type 1 and 2 documents published by the contractor and submitted in response to the data requirements of this DPD shall be identified within an organized identification numbering system prescribed to NASA by the contractor and, if applicable, as approved by NASA. For all data types, the document number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization shall be included on the title page. The document number, change legend, and date shall appear on each page of the document. In the front matter of each document, identify the DPD number and applicable DRD number(s) required for document preparation.

Successive issues or revisions of documents shall be identified in the same manner as the basic issue and shall have appropriate change identification. Drawings and ECP's are excluded from the marking provisions of this paragraph. All Type 1 documentation, excluding configuration management requirements, shall be marked

“PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED

BY NASA” and the date and approval authority annotated on the cover.

2.7 Reference to Other Documents and Data Deliverables in Data Submittals: All referenced documents shall be made readily available to the cognizant NASA organization upon request. The contractor shall make sure that the references are available to NASA in a manner which does not incur delays in the use of the response document. Reference may be made, within one data submittal, to other data submittals delivered in response to this DPD in those cases where the data required by one DRD may have been delivered by the contractor in response to another DRD. The reference to previously-submitted data shall include the applicable DRD number, data submittal version date, and location within the referenced document.

2.8 Maintenance of Type 1 Document Submittals

2.8.1 Revisions of Type 1 documentation may be accomplished either by individual page revision or by a complete reissue of the document identified in accordance with requirements of 2.6 above, with the exception of drawings (which shall be revised in accordance with contract configuration management requirements).

2.8.2 Individual page revisions shall be made as deemed necessary by the contractor or as directed by the Contracting

Officer.

2.8.3 A Type 1 document shall be completely reissued when, in the opinion of the contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the

Contracting Officer. When complete reissues are made, the entire contents of the document shall be brought https://explornet.nasa.gov/docs/DOC-38150

J-2-8 up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

2.8.4 Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a technical change is made, unless the accuracy of the document is affected.

2.8.5 All revised pages shall be identified by a revision symbol and a new date. Each document shall contain a log of revised pages that identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated by the use of vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

2.8.6 Contractor Type 1 document shall not be submitted containing pen and ink markups which correct, add to, or change the text, unless schedule problems exist and approval is obtained in writing from the Contracting

Officer. Such markups, however, shall not exceed 20 percent of the page content and shall be acceptable provided that the reproduced copies are legible. In addition, hand-drawn schematics, block diagrams, data curves, and similar charts may be used in original reports in lieu of formally prepared art work, as long as legibility of copies is not impaired. Acceptability shall be determined by the Contracting Officer.

3.0 DPD MAINTENANCE PROCEDURES

3.1 NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion of the DPD shall be appended. The contractor shall notify the Contracting

Officer in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision to DPD is appended. In such cases, the contractor shall submit the requested changes to NASA for approval. See paragraph 3.3.1 for change procedures.

3.2 Contractor-Initiated Change: Contractor-proposed data requirements or proposed changes to existing requirements shall be submitted to NASA for approval.

3.3 DPD Change Procedures

3.3.1 Changes to a contractual issue of this DPD shall be identified by NASA on the Document Change Log.

3.3.2 The date of the DPD shall be entered under the “as of” block of the Document Change Log. The date that was in the “as of” block shall be entered in the “Superseding” block.

3.3.3 The Document Change Log entitled “Incorporated Revisions” shall be changed to indicate the modification number, portions affected, and remarks. All changes to the DPD/DRDs shall be identified in the “Remarks” column.

3.4 DPD Reissues

3.4.1 When conditions warrant, the DPD shall be reissued by NASA for each contract modification that affects the

DPD and shall supersede the existing DPD in its entirety. Reissues shall be issued by contractual direction.

3.4.2 All revision dates shall remain in the Date Revised block on all DRDs. The issue symbol, which shall commence with "A" and progress through "Z," shall be entered in the DPD identification block of each DRD page of the DPD.

J-2-9

Powder Specification: Inconel 718 for Laser Powder Bed Fusion Additive Manufacturing

Data Requirements List

DRD DATA TYPE TITLE OPR

CD – Contractual Data

1616CD-001 3 Technology Reports ST22

EE – Environmental

1616EE-001 3 Environmental Compliance Reports AS10

MA – Management

1616MA-001 3 Final Scientific and Technical Report IS02

1616MA-002 3 Monthly Progress Report EM42

SA – Safety

1616SA-001 3 Off-site Mishap and Safety Statistics Reports QD12

J-2-10

DATA REQUIREMENTS DESCRIPTION (DRD)

1. DPD NO.: 1616 ISSUE: RFQ 2. DRD NO.: 1616CD-001

3. DATA TYPE: 3 4. DATE REVISED:

5. PAGE: 1/3

6. TITLE: Technology Reports

7. DESCRIPTION/USE: Provides NASA with technical information concerning any invention, discovery, improvement, or innovation made by a contractor in the performance of work under this contract for the purpose of disseminating this information to obtain increased use and to provide NASA with data to review for possible patentable items.

8. OPR: ST22 9. DM: EM42

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION: Disclosure of Invention and New Technology (NASA Form 1679): Immediately or within three months of identification of subject invention.

Interim NASA New Technology Summary Report (NTSR) Form: 12 months from the date of the contract.

Final NASA New Technology Summary Report (NTSR) Form: Immediately or within three months after completion of contracted work. Final payment is contingent upon submission of the Final NTSR.

Utilization Report: Upon Contracting Officer’s request.

12. SUBMISSION FREQUENCY: Disclosure of Invention and New Technology (NASA Form 1679): For each subject invention as soon as it occurs or within three months of identification.

Interim NASA New Technology Summary Report (NTSR) Form: Every 12 months.

Final NASA New Technology Summary Report (NTSR) Form: Immediately or within three months after completion of contracted work. Final payment is contingent upon submission of the Final NTSR.

Utilization Report: No more frequently than annually.

13. REMARKS: Copies of NASA Forms 1679 and the NASA New Technology Summary Report (NTSR) Form

(Interim and Final) may be obtained and filled out electronically at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/. These forms may also be obtained from the New Technology Representative (mailto:

Carolyn.E.McMillan@nasa.gov).

14. INTERRELATIONSHIP: SOW paragraph 5

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The New Technology Reports should include sufficient technical detail as is necessary to identify and fully describe a "Subject Invention". Per FAR 52.227-11, "Subject Invention" means any invention of the contractor conceived or first actually reduced to practice in the performance of work under this contract.

15.2 APPLICABLE DOCUMENTS:

FAR 52.227-11 Patent Rights – Ownership by the Contractor (APR 2015) - As modified by NASA

FAR Supplement 1852.227-11 (APR 2015) https://ntr.ndc.nasa.gov/ https://invention.nasa.gov/ mailto:mailto:%20Carolyn.E.McMillan@nasa.gov mailto:mailto:%20Carolyn.E.McMillan@nasa.gov

J-2-11

DRD Continuation Sheet

TITLE: Technology Reports DRD NO.: 1616CD-001

DATA TYPE: 3 PAGE: 2/3

15. DATA PREPARATION INFORMATION (CONTINUED):

15.3 CONTENTS: The Technology Reports consist of:

a. Disclosure of Invention and New Technology (Including Software): In accordance with FAR 52.227-11(c), the disclosure to the agency shall be in the form of a written report and shall identify the contract under which the invention was made and the inventor(s). It shall be sufficiently complete in technical detail to convey a clear understanding to the extent known at the time of the disclosure, of the nature, purpose, operation, and the physical, chemical, biological or electrical characteristics of the invention. The disclosure shall also identify any publication, on sale or public use of the invention and whether a manuscript describing the invention has been submitted for publication and, if so, whether it has been accepted for publication at the time of disclosure. In addition, after disclosure to the agency, the Contractor shall promptly notify the agency of the acceptance of any manuscript describing the invention for publication or of any on sale or public use planned by the Contractor. This reporting requirement may be met by completing NASA Form

1679 (latest revision) in hardcopy or online at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/. Use of this form or the online system is preferred; however, if the form is not used the following information should be provided in order to meet the reporting requirement:

1. Descriptive title.

2. Innovator(s) name(s), title(s), phone number(s), and home address(es).

3. Employer when innovation made (name and division).

4. Address (place of performance).

5. Employer status (e.g., Government, college or university, non-profit organization, small business firm, large entity).

6. Origin (e.g., NASA grant number, NASA prime contract number, subcontractor, joint effort, multiple contractor contribution, other).

7. NASA Contracting Officer’s Representative (COR).

8. Contractor/grantee New Technology Representative.

9. Brief abstract providing a general description of the innovation:

(a) Description of the problem or objective that motivated the innovation’s development.

(b) Technically complete and easily understandable description of innovation developed to solve or meet the objective.

(c) Unique or novel features of the innovation and the results or benefits of its application.

(d) Speculation regarding potential commercial applications and points of contact (including names of companies producing or using similar products).

10. Additional documentation.

11. Degree of technological significance (e.g., modification of existing technology, substantial advancement in the art, major breakthrough).

12. State of development (e.g., concept only, design, prototype, modification, production model, used in current work).

13. Patent status.

14. Dates or approximate time period during which this innovation was developed.

15. Previous or contemplated publication or public disclosure including dates.

16. Answers to the following questions (for software only):

(a) Using outsiders to beta-test code? If yes, done under beta-test agreement?

(b) Modifications to this software continue by civil servant and/or contractual agreement?

(c) Previously copyrighted (if so, by whom?)?

(d) Were prior versions distributed (if yes, supply NASA or Contractor contract)?

(e) Contains or is based on code owned by a non-federal entity (if yes, has a license for use been obtained?)?

(f) Has the latest version been distributed without restrictions as to use or disclosure for more than one year (if yes, supply date of disclosure)?

17. Name(s) and signature(s) of innovator(s).

J-2-12

DRD Continuation Sheet

TITLE: Technology Reports DRD NO.: 1616CD-001

DATA TYPE: 3 PAGE: 3/3

15. DATA PREPARATION INFORMATION (CONTINUED):

b. Interim NASA New Technology Summary Report: This report shall consist of a complete listing of subject inventions for the previous 12-month period or certification that there are none. Completion of Interim

NASA New Technology Summary Report (NTSR) Form shall satisfy this reporting requirement. Use of the form utilizing the online system at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/.

is preferred; however an alternate format is acceptable provided all required information is provided.

c. Final NASA New Technology Summary Report: This report shall consist of a comprehensive list of all subject inventions for the duration of the contract or certification that there are none. Completion of Final

NASA New Technology Summary Report (NTSR) Form shall satisfy this reporting requirement. Use of the form utilizing the online system at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/ is preferred;

however an alternate format is acceptable provided all required information is provided.

d. Report on utilization of subject inventions: This report provides information on the utilization of a subject invention or on efforts at obtaining such utilization that is being made by the contractor or its licensees or assignees. Per FAR 52.227-11, this report shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the contractor, and other data requested by the Contracting Officer.

15.4 FORMAT: To report a Disclosure of Invention and New Technology (Including Software) NASA Form 1679

(latest version) may be used or submit the report online at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/, or provide sufficient information to meet the reporting requirement.

The interim and final NASA New Technology Summary Reports may use the NTSR Form (Interim or Final whichever is applicable) utilizing the online system at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/, or provide sufficient information to meet the reporting requirement.

15.5 MAINTENANCE: None required

https://invention.nasa.gov/ https://ntr.ndc.nasa.gov/ https://invention.nasa.gov/ https://ntr.ndc.nasa.gov/ https://invention.nasa.gov/

J-2-13

1. DPD NO.: 1616 ISSUE: RFQ 2. DRD NO.: 1616EE-001

5. PAGE: 1/2

6. TITLE: Environmental Compliance Reports

7. DESCRIPTION/USE: To provide the Government data related to contractor compliance with green purchasing, waste reduction, and ozone depleting substances environmental requirements.

8. OPR: AS10 9. DM: EM42

10. DISTRIBUTION: Per Contracting Officer’s letter

11. INITIAL SUBMISSION: Annual Green Purchasing Report - End of contract year. Waste Reduction Activity

Report - End of contract year. Ozone Depleting Substances (ODS) Notifications - End of contract year.

Equipment Notifications - Prior to purchasing.

12. SUBMISSION FREQUENCY: Annually, at the end of contract year, except for equipment notifications that shall be submitted prior to purchasing.

13. REMARKS: For 15.3a and 15.3c, where the Contractor does not purchase any designated product or equipment during the contract year or duration of contract, the report shall be a statement to that effect. For 15.3d, if the

Contractor does not purchase, own, operate, maintain, or repair Ozone Depleting Substances (ODS) equipment on-site, the report shall be a statement to that effect.

15.1 SCOPE: The Environmental Compliance Reports will include the contractor compliance data for Annual Green

Purchasing Report, Waste Reduction Activity Report, Ozone Depleting Substances (ODS) Notification, and

Equipment Notifications.

40 CFR 82.162 Certification by owners of recovery and recycling equipment

MWI 8540.2 Green Purchasing Program

MWI 8550.5 Hazardous Material Management

15.3 CONTENTS: The Environmental Compliance Reports are as follows:

a. Annual Green Purchasing Report:

1. Track and report purchases of all products on the U. S. Environmental Protection Agency (EPA)

Comprehensive Procurement Guideline list and items in the United States Department of Agriculture

(USDA) BioPreferred® catalog, utilizing the appropriate MSFC form in Section 15.4.

2. Reporting of purchases applies to Contractor and all Subcontractors.

3. Submit report to Environmental Engineering and Occupational Health Office according to Section 5.2 of MWI 8540.2.

b. Waste Reduction Activity Report:

1. Track and report any new process improvements or programs that have contributed to waste reduction during the previous contract year. Waste reduction means preventing or decreasing the amount of waste being generated through recycling* or waste prevention**. Limit responses to one page or less per item. The response shall include a description of the activity, the materials or wastes reduced, estimated volume or weight of reduction, and a contact name and phone number for a person knowledgeable about the reduction activity.

J-2-14

DRD Continuation Sheet

TITLE: Environmental Compliance Reports DRD NO.: 1616EE-001

DATA TYPE: 3 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

* Recycling means the series of activities, including collection, separation, and processing by which products or other materials are recovered from the solid waste stream for use in the forms of raw materials in the manufacture of products.

** Waste prevention means any change in the design, manufacturing, purchase, or use of materials or products (including packaging) to reduce waste or toxicity before they are discarded. Waste prevention also refers to the reuse of products or materials.

2. Reporting of waste reduction activities applies to Contractor and all Subcontractors. If there was no reduction activity, then a negative response is required.

3. Submit report to Environmental Engineering and Occupational Health Office.

c. Ozone Depleting Substances (ODS) Notifications:

1. Track and report the following information for the previous fiscal year related to ODS containing equipment that the Contractor purchases, owns, operates, maintains or repairs on-site:

(a) A list of the names of all EPA-Certified service technicians employed and their certification dates.

(b) A list of any ODS recovery/recycling equipment that will be used and a copy of the 40 CFR 82.162

EPA registration.

2. ODS Notifications apply to Contractor and all Subcontractors.

3. Submit notifications to Environmental Engineering and Occupational Health Office.

d. Equipment Notifications:

1. Notifications are required when equipment that may require air permitting or inclusion in the Spill

Prevention, Control, and Countermeasures (SPCC) inventory is brought onto the Center. Examples of such equipment include boilers, generators, hydraulic pumps, grit or sand blasters, parts washers, tanks, non-digital photography equipment, vent hoods, wood working equipment, metal working equipment, vapor degreasers, x-ray developing, surface coating equipment, cleaning equipment, autoclaves, engines, fueling stations/equipment, propulsion engine and launch system testing equipment/articles, paint booths, or any other equipment that emits smoke, fumes, vapors, or particles into the air, or contains oil.

2. Notifications apply to Contractor and all Subcontractors.

3. Submit notifications to Environmental Engineering and Occupational Health Office and Safety and

Mission Assurance prior to purchase according to the Hazardous Material and Environmental Sensitive

Equipment (ESE) Purchases guidelines in Section 5.1 of MWI 8550.5.

15.4 FORMAT: Contractor format is acceptable on all other reports except the Green Purchasing Reports shall be submitted on the following MSFC forms.

a. MSFC Form 4510, “MSFC Construction Green Purchasing Reporting Form”.

b. MSFC Form 4543, “MSFC General Green Purchasing Reporting Form”.

c. MSFC Form 4544, “MSFC Office Green Purchasing Reporting Form”.

https://forms.neacc.nasa.gov/documents/11002/121691/MSFC4510F.pdf https://forms.neacc.nasa.gov/documents/11002/121691/MSFC4543F.pdf https://forms.neacc.nasa.gov/documents/11002/121691/MSFC4544F.pdf

J-2-15

1. DPD NO.: 1616 ISSUE: RFQ 2. DRD NO.: 1616MA-001

5. PAGE: 1/1

6. TITLE: Final Scientific and Technical Report

7. DESCRIPTION/USE: To provide a summary of the results of the entire contract effort, including recommendations and conclusions based on the experience and results obtained.

8. OPR: IS02 9. DM: EM42

10. DISTRIBUTION: Final report shall be submitted to the Contracting Officer. In addition, the contractor shall concurrently provide to the Center STI/Publication Manager and NASA STI Support Services (STISS), formerly

Center for AeroSpace Information (CASI), a copy of the letter transmitting the final report to the Contracting

Officer. The copy of the letter shall be submitted to STISS at the address listed at https://www.sti.nasa.gov/ under the “Contact/Help” link.

11. INITIAL SUBMISSION: 30 days after completion of contract

12. SUBMISSION FREQUENCY: One-time submittal

13. REMARKS:

15.1 SCOPE: The Final Scientific and Technical Report summarizes the results of the entire contract work.

NFS 1835.70 Center for AeroSpace Information – Final Scientific and Technical Report

NFS 1852.235-73 Final Scientific and Technical Reports

MPR 2220.1 Scientific and Technical Publications

NPR 2200.2 Requirements for Documentation, Approval, and Dissemination of NASA Scientific and

Technical Information

15.3 CONTENTS: The Final Scientific and Technical Report shall be prepared and submitted in accordance with

NFS 1835.70 and meet the requirements of 1852.235-73. The report shall summarize the results of the entire contract, including recommendations and conclusions based on the experience and results obtained. The report shall include tables, graphs, diagrams, curves, sketches, photographs, and drawings in sufficient detail to explain comprehensively the results achieved under the contract. The report shall include a completed NASA Form 1676 and Standard Form 298 as the final page, per MPR 2220.1, NPR 2200.2 and NFS 1852.235.73(c).

15.4 FORMAT: The final report shall be of a quality suitable for publication and shall follow the formatting and stylistic guidelines contained in MPR 2220.1 and NPR 2200.2. Electronic formats are required. See https://www.sti.nasa.gov/, “Publish STI” for appropriate types of formats. The final page of the report shall be in accordance with NASA Form 1676 and Standard Form 298. One electronic copy of each NASA STI Report Series publication is sent to NASA STISS, formerly CASI. One hard copy is requested but not required. (The hard copy may be used to validate that math and symbols have not encountered a font substitution during transmission.).

Electronic format shall be in accordance with NFS 1852.235-73.

https://www.sti.nasa.gov/ https://www.sti.nasa.gov/

J-2-16

DATA REQUIREMENTS DESCRIPTION (DRD)

1. DPD NO.: 1616 ISSUE: RFQ 2. DRD NO.: 1616MA-001

5. PAGE: 1/1

6. TITLE: Monthly Progress Report

7. DESCRIPTION/USE: To provide visibility to contractor and MSFC project management of actual and potential problems and progress toward meeting the cost, technical and schedule requirements.

8. OPR: EM42 9. DM: EM42

11. INITIAL SUBMISSION: The first submission shall be provided by the 15th day of the month following the contractor’s accounting month-end. If the contract is awarded beyond the 15th day of the month, the first report shall cover the period from award until the following accounting month-end, unless otherwise specified by the Contracting Officer.

12. SUBMISSION FREQUENCY: Monthly by the 15th day of the month after the close of the contractor’s accounting period

13. REMARKS:

15.1 SCOPE: The Monthly Progress Report provides data for the assessment of monthly cost, technical and schedule progress.

NFS 1852.235-74 Additional Reports of Work - Research and Development

15.3 CONTENTS: The Monthly Progress Report shall meet the requirements of NFS 1852.235-74 and shall contain the following:

a. Work accomplished for current reporting period, including a report of overall cost, technical and schedule performance.

b. Work planned for next reporting period.

c. Current problems or risks which may impede performance or impact program schedule or cost, and proposed corrective action.

d. Other information that assist the Government in evaluating the contractor’s cost, technical and schedule performance, e.g., innovative processes and cost reduction initiatives.

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

05/11/17

J-2-17

1. DPD NO.: 1616 ISSUE: RFQ 2. DRD NO.: 1616SA-001

5. PAGE: 1/3

6. TITLE: Off-site Mishap and Safety Statistics Reports

7. DESCRIPTION/USE: To provide initial and follow-up reporting of mishaps, close calls, serious non-occupational injuries or illnesses, and Contractor quarterly safety metrics to the Government for Contractors that are physically located Off-site or at another National Aeronautics Space Administration (NASA) Center.

8. OPR: QD12 9. DM: EM42

11. INITIAL SUBMISSION:

a. Safety Statistics specific to this contracted effort shall be submitted by the end of the first quarter (calendar year) after Authority to Proceed (ATP) or contract award. The safety statistics submitted by the Contractor shall be for the work performed by the Contractor (including subcontractors) for the previous quarter.

Contractors shall submit the quarterly safety statistics to the Center’s Safety Office. At MSFC to the MSFC

Industrial Safety Branch/QD12. At MAF to the MAF Safety and Mission Assurance (SMA) Manager/QD12, unless directed to send it to the MSFC Industrial Safety Branch/QD12. (NOTE: If the work is performed on another NASA Center provide a copy to the Center’s Safety Office, if requested.)

1. Safety statistics shall be reported by one of the following: 1) direct entry into “eContractor (Form 4371)” located on the MSFC SMA Sharepoint page on the MSFC “Inside Marshall” explornet web page; 2) submittal of a hardcopy MSFC Form 4371; or 3) an equivalent electronic notification method that includes all of the information contained on the MSFC Form 4371 and listed in 11.a.2. (NOTE: A

NASA Identification/NASA e-mail address is required to access to the MSFC SMA sharepoint page.

Your Contracting Officer can provide information for obtaining a NASA Identification/NASA e-mail address. See section 12 of this DRD for directions to the MSFC SMA Sharepoint page.)

2. Safety statistics reports shall include: contract number, North American Industry Classification System

(NAICS) codes and the following for the reporting period: number of employees; number of supervisors, hours worked; number of injuries including days away from work and/or first-aid cases;

number of incidents involving NASA related equipment or property damage including dollar losses;

and current days away from work injury/illness frequency rate. Prime contractor safety statistics include their subcontractor(s) safety statistics in this report. (NOTE: The safety statistics report includes all work performed in direct support of this NASA or MSFC contracted effort where the Contractor is charging man-hours to NASA or MSFC for this contract.)

b. Initial reporting of a NASA reportable mishap/close call defined in NPR 8621.1 shall be within the timelines listed below.

1. Reported as soon as possible after initiating emergency response but no later than 1 hour of occurrence or awareness for Type A, Type B, and High-Visibility Mishaps/Close Calls (e.g., an occupational injury or illness resulting in a fatality, serious injury or potential hospitalization; a potential total direct cost of mission failure or property damage equal to or greater than $500,000; or may be consider as a high-visibility event for NASA and specific to this contracted effort by one of the following methods:

(a) Call the MSFC Safety Hotline (256) 544-0046. (NOTE: If the work is being performed on another NASA Center also notify that Center’s Safety Office within the same timeline.)

(b) Direct input into the NASA Mishap Information System (NMIS) by the Contractor’s designated

NMIS representative at http://nmis.sma.nasa.gov. Contact the Center’s Safety Office for assistance if needed. (See section 11.f.)

http://nmis.sma.nasa.gov/

J-2-18

DRD Continuation Sheet

TITLE: Off-site Mishap and Safety Statistics Reports DRD NO.: 1616SA-001

DATA TYPE: 3 PAGE: 2/3

11. INITIAL SUBMISSION (CONTINUED):

2. Reported quarterly by one of the following: 1) direct entry into “eContractor (Form 4371)” located on the MSFC SMA Sharepoint page; 2) submittal of a hardcopy use of the MSFC Safety Statistics Report

(MSFC Form 4371); or 3) an equivalent electronic submittal for Type C, Type D, and those

Mishaps/Close Calls not considered as High-Visibility (e.g., an occupational injury or illness resulting in a non-serious injury or first aid treatment; a potential total direct cost of mission failure or property damage less than $500,000; or not considered as a high-visibility event for NASA) specific to this contracted.

c. Initial reports for a NASA reportable mishap/Close Call listed in 11.b.1 specific to this contracted effort shall include the following: location and time of incident, number of fatalities, number hospitalized, type of damage, estimated cost, brief description, and contact person’s name and phone number. (See NPR 8621.1.)

d. Follow-up actions and/or reporting for a NASA reportable mishap/close call listed in 11.b.1 when requested shall include, any or all of, the following:

1. Be investigated within the timeline specified by the Center’s Appointing Official (investigation for these type mishaps/close calls do not to exceed 75 calendar days unless additional time is granted by the

Center’s Appointing Official).

2. Have a Mishap Investigation Report developed at the completion of the investigation and entered directly into NMIS or submitted to the Center’s Safety Office (At MSFC, the Industrial Safety

Branch/QD12 or MAF, the SMA Manager/QD12.) (See NPR 8621.1.)

3. Have a Corrective Action Plan (CAP) developed and submitted for concurrence within the timeline specified by the Center’s Appointing Official upon Endorsing Official approval. (See NPR 8621.1.)

4. Provide CAP status/updates into NMIS or to the Center’s Safety Office not to exceed 30 calendar day intervals from the date of concurrence until the CAP is closed. (See NPR 8621.1.)

e. Safety Concerns, Hazards, and non-reportable mishaps for Contractors working on another NASA

Center shall be reported to that Center’s Safety Office in accordance with that Center’s reporting requirements. (See NPR 8715.1.)

f. Contractor NMIS Representative shall be identified to enter, track and close Contractor mishaps/close calls entered in NMIS. After contract award the contractor shall contact the Center’s NMIS Administrator or

Center’s Mishap Investigation Program Manager located in the MSFC Industrial Safety Branch for access to the NMIS database.

12. SUBMISSION FREQUENCY: Safety Statistics [Reported by one of the following: 1) direct entry into

“eContractor (Form 4371)” located on the MSFC SMA Sharepoint page; 2) submittal of a hardcopy MSFC Form

4371; or 3) an equivalent electronic submittal] - By the end of the first quarter (calendar year) after Authority to

Proceed (ATP) or contract award and submitted quarterly thereafter by the 10 th day of the month following the end of the quarter to MSFC Industrial Safety Branch. A copy can also be sent to the Center’s Safety Office if requested. Mishaps: As specified in section d of this DRD until the NMIS case is closed. NOTE: Access to

“eContractor (Form 4371) is on MSFC’s “Inside Marshall” located on the NASA Explornet page. Start by selecting “Centers,” select “Marshall,” select “Sharepoint,” select “Safety and Mission Assurance Directorate,” and select “eContrator (Form 4371).”

13. REMARKS: Data type 3 applies to Mishap and Safety Statistics. Government approval/endorsement of Mishap

Investigations reports is performed in accordance with NPR 8621.1 or MWI 8621.1 when requested. The reporting to NASA of NASA reportable mishaps/close calls does not relieve the Contractor of their responsibility to notify the Occupational Safety and Health Administration (OSHA) as specified by 29 CFR 1904.

15.1 SCOPE: For the Government to be notified by the Contractor of all Contractor mishaps, close calls, and serious non-occupational injuries or illnesses as required in NPR 8621.1.

DRD Continuation Sheet

J-2-19

TITLE: Off-site Mishap and Safety Statistics Reports DRD NO.: 1616SA-001

DATA TYPE: 3 PAGE: 3/3

15. DATA PREPRATION INFORMATION (CONTINUED):

15.2 APPLICABLE DOCUMENTS:

NPR 8621.1 NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and

Recordkeeping

MWI 8621.1 Mishap and Close Call Reporting and Investigation Program

15.3 CONTENTS: Initial and follow-up mishap reports shall contain all information required by NPR 8621.1 and

MWI 8621.1. Mishap and Safety Statistics Reports shall contain the information listed in 11.a.2 and on the MSFC

Form 4371or equivalent electronic format.

15.4 FORMAT: The following formats or electronic equivalent shall be submitted:

a. Direct entry into “eContractor (Form 4371)” located on the MSFC SMA Sharepoint page; submittal of a hardcopy MSFC Form 4371, “MSFC Contractor Accident and Safety Statistics”; or an equivalent electronic notification system that…