Attachment J-2 MAV RCS 5N Thruster Data Procurement Document 10 May 2021.pdf

J-2-1

DATA PROCUREMENT DOCUMENT

NO. ISSUE

1753 RFP

80MSFC21R0020

CONTRACT/RFP

EXHIBIT NUMBER

J-2

ATTACHMENT NUMBER

Mars Ascent Vehicle (MAV) Reaction Control System (RCS) 5N Thruster

PROJECT/SYSTEM

Contractor

CONTRACTOR

May 10, 2021

DATE

National Aeronautics and Space Administration

05/10/21

J-2-2

National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

NO. ISSUE

1753 RFP

INCORPORATED REVISIONS

OUTSTANDING REVISIONS

AS OF:

05-10-21

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 CM Configuration Management DE Design and Development Engineering MA Management MP Materials and Processes QE Quality Engineering RM Reliability and Maintainability SE Systems Engineering

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.

J-2-4

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.

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

J-2-5 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.

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: Hardcopy of the DPD is not required unless electronic delivery is not possible or practical. The contractor’s transmittal memo shall be delivered in a hardcopy to the Contracting Officer (CO). The DPD shall be emailed to the CO.

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:

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 data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

If the contract contains FAR 52.227-14 Alternate II, the Limited Rights Notice may be applicable to technical data (other than computer software) delivered under this contract. The “Limited Rights Notice” is as follows:

computer software delivered under this contract. The “Restricted Rights Notice” is as follows:

(which does not qualify as technical data or computer software) delivered under this contract.

SBIR Rights Notice (DEC 200 ) These SBIR data are furnished with SBIR rights under Contract No._____ (and subcontract _____, if appropriate). For a period of 4 years, unless extended in accordance with FAR 27.409(h), after acceptance of all items to be delivered under this contract, the Government will use these data for Government purposes only, and they shall not be disclosed outside the Government (including disclosure for procurement purposes) during such period without permission of the Contractor, except that, subject to the foregoing use and disclosure prohibitions, these data may be disclosed for use by support Contractors. After the protection period, the Government has a paid-up license to use, and to authorize others to use on its behalf, these data for Government purposes, but is relieved of all disclosure prohibitions and assumes no liability for unauthorized use of these data by third parties. This notice shall be affixed to any reproductions of these data, in whole or in part.

Restricted Rights Notice (Dec 2007)

(a) This computer software is submitted with restricted rights under Government Contract No. _______ (and subcontract ________, if appropriate). It may not be used, reproduced, or disclosed by the Government except as provided in paragraph (b) of this notice or as otherwise expressly stated in the contract. (b) This computer software may be— (1) Used or copied for use with the computer(s) for which it was acquired, including use at any Government installation to which the computer(s) may be transferred; (2) Used or copied for use with a backup computer if any computer for which it was acquired is inoperative; (3) Reproduced for safekeeping (archives) or backup purposes; (4) Modified, adapted, or combined with other computer software, provided that the modified, adapted, or combined portions of the derivative software incorporating any of the delivered, restricted computer software shall be subject to the same restricted rights; (5) Disclosed to and reproduced for use by support service Contractors or their subcontractors in accordance with paragraphs (b)(1) through (4) of this notice; and

(6) Used or copied for use with a replacement computer. (c) Notwithstanding the foregoing, if this computer software is copyrighted computer software, it is licensed to the Government with the minimum rights set forth in paragraph (b) of this notice. (d) Any other rights or limitations regarding the use, duplication, or disclosure of this computer software are to be expressly stated in, or incorporated in, the contract. (e) This notice shall be marked on any reproduction of this computer software, in whole or in part.

Limited Rights Notice (Dec 2007)

a) These data are submitted with limited rights under Government Contract No. _____ (and subcontract ______, if appropriate). These data may be reproduced and used by the Government with the express limitation that they will not, without written permission of the Contractor, be used for purposes of manufacture nor disclosed outside the Government; except that the Government may disclose these data outside the Government for the following purposes, if any; provided that the Government makes such disclosure subject to prohibition against further use and disclosure: [Agencies may list additional purposes as set forth in 27.404-2(c)(1) or if none, so state. (b) This notice shall be marked on any reproduction of these data, in whole or in part.

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

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 copyright in data first produced in the performance of the 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.

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.

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://nasa.sharepoint.com/sites/msfcrm/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2Fmsf crm%2FShared%20Documents%2FDCMT%20Electronic%20Submittal%20Instructions%2Epdf&parent=% 2Fsites%2Fmsfcrm%2FShared%20Documents. 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.

J-2-8

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 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 artwork, 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

J-2-9 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-10

Mar Ascent Vehicle (MAV) 5N Reaction Control Thruster

Data Requirements List

DRD DATA TYPE TITLE OPR

CD – Contractual Data 1753CD-001 3 Technology Reports ST22

CM – Configuration Management 1753CM-001 1 Acceptance Data Package (ADP) ED10 1753CM-002 1 Deviation/Waiver Approval Request ED10 1753CM-003 1 Engineering Change Proposals (ECPs) and Associated ED10 Documentation 1753CM-004 3 Engineering Drawing and Associated Lists ED10

DE – Design and Development Engineering

1753DE-001 2 As-Built EEE Parts List ES33 1753DE-002 2 Acceptance Test Plan ER13/ER41 1753DE-003 2 Acceptance Test Procedure ER13/ER41 1753DE-004 2 Qualification Test Plan ER13/ER41 1753DE-005 2 Qualification Test Procedure ER13/ER41 1753DE-006 2 Qualification Test Report ER13/ER41 1753DE-007 3 Component Performance Analysis ER13 1753DE-008 3 Structural Strength and Fatigue Analysis Report ER41

MA – Management 1753MA-001 1 Organizational Conflict of Interest (OCI) Plan LS01 1753MA-002 2 Program/Project Schedules CS10/ST20 1753MA-003 2/3 Major Review Documentation ER41 1753MA-004 3 Financial Management Report (533M and 533Q) RS20

MP – Material and Processes 1753MP-001 1 Contamination Control Plan (CCP) with Foreign Object EM04 Debris (FOD) Plan 1753MP-002 1 Materials Identification and Usage List (MIUL) EM04 1753MP-003 1 Material Usage Agreement (MUA) EM04

QE – Quality Engineering 1753QE-001 1 Quality Plan QD10

RM – Reliability and Maintainability 1753RM-001 1 Failure Modes and Effects Analysis (FMEA) QD21 1753RM-002 2 Limited Life Items List QD21 1753RM-003 3 Reliability Analysis Report QD22

SE – System Engineering 1753SE-001 3 Verification/Validation Compliance (VVC) Assessment ED10

J-2-11

DATA REQUIREMENTS DESCRIPTION (DRD)

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753CD-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 provide NASA with data to review for possible patentable items.

8. OPR: ST22 9. DM: ST20

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NASA Form 1679): Immediately or within three months of identification of reportable item(s).

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.

12. SUBMISSION FREQUENCY:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NASA Form 1679): Upon identification of each reportable item.

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.

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

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

14. INTERRELATIONSHIP: SOW paragraph 5

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Technology Reports include technical detail as is necessary to identify and fully describe a

"Reportable Item". Per NFS 1852.227-70, "Reportable Item" means any invention, discovery, improvement, or innovation of the contractor, whether or not the same is or may be patentable or otherwise protectable under Title 35 of the United States Code, conceived or first actually reduced to practice in the performance of any work under this contract or in the performance of any work that is reimbursable under any clause in this contract providing for reimbursement of costs incurred prior to the effective date of this contract.

15.2 APPLICABLE DOCUMENTS/CLAUSES:

NFS 1852.227-70 New Technology - Other than a Small Business Firm or Nonprofit Organization

J-2-12

DRD Continuation Sheet TITLE: Technology Reports DRD NO.: 1753CD-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 NFS 1852.227-70

(e)(2), the disclosure to the agency shall be in the form of a written report and shall identify the contract under which the reportable item was made and the inventor(s) or innovator(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 physical, chemical, biological, or electrical characteristics of the reportable item. The disclosure shall also identify any publication, on sale, or public use of any subject invention and whether a manuscript describing such 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 a subject invention for publication or of any on sale or public use planned by the Contractor for such invention. This reporting requirement may be met by completing NASA Form 1679 (latest revision) in hardcopy or online at: 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-13

DRD Continuation Sheet TITLE: Technology Reports DRD NO.: 1753CD-001

DATA TYPE: 3 PAGE: 3/3

15. DATA PREPARATION INFORMATION (CONTINUED):

b. Interim NASA New Technology Summary Report (NTSR): This report shall consist of a listing of reportable items for the reporting period or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts.

Completion of the Interim NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at: 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 (NTSR): This report shall consist of a comprehensive list of all reportable items for the contract duration or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts. Completion of the Final NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at: https://invention.nasa.gov/ is preferred; however an alternate format is acceptable provided all required information is provided.

d. Subcontracts: The contractor shall provide copies of subcontracts containing a patent rights clause upon Contracting Officer’s request.

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://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://invention nasa.gov/, or provide sufficient information to meet the reporting requirement.

15.5 MAINTENANCE: None required

J-2-14

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753CM-001

3. DATA TYPE: 1 4. DATE REVISED:

5. PAGE: 1/2

6. TITLE: Acceptance Data Package (ADP)

7. DESCRIPTION/USE: To provide the documentation needed by MSFC to establish the acceptability of the component for the intended use.

8. OPR: ED10 9. DM: ST20

10. DISTRIBUTION: Per program/project/activity determination

11. INITIAL SUBMISSION: Preliminary two weeks prior to each Acceptance Review (AR)

12. SUBMISSION FREQUENCY: Baseline following delivery of each Configuration Item (CI)

13. REMARKS:

14. INTERRELATIONSHIP: SOW paragraph 5.4

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Acceptance Data Package (ADP) contains the elements of documentation required to establish the acceptability of the component.

15.2 APPLICABLE DOCUMENTS/CLAUSES: None

15.3 CONTENTS: An Acceptance Data Package (ADP) for the component contract configuration items shall contain the items and format shown in Attachment 1.

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: The ADP shall be maintained current. Changes and/or updating shall be in accordance with the provider/contractor’s approved change control system.

J-2-15

DRD Continuation Sheet TITLE: Acceptance Data Package (ADP) DRD NO.: 1753CM-001

DATA TYPE: 1 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

ATTACHMENT 1

SECTION TITLE DESCRIPTION

1 Item Name, Serial Number, Part Number Cover sheet

2 Approvals w/MSFC Quality, Program Manager (PM) & Engineer Acceptance Data Package (ADP) Approval Sheet

3 As-Built Materials List (ABML) List of Drawings and Bill of Materials (BOM) with revision level noted

4 As-Built Parts List May be same list provided with #3 above.

5 As-Built Final Top-level Interface Control Document (ICD) Drawing tree with the ICD

6 Problem/anomaly reporting Nonconformance Reports List and copy

7 Deviations/Waivers Request for Deviation (RFD)/Request for Waiver (RFW) List and copy

8 Shortages List of items shipping short

9 Open Items List of items and actions pending closure

10 Action Items List of Action Items from previous reviews

11 Class 1 Changes and Material Review Board (MRBs)

List of NCRs with a Class 1 Change. Copy of Closed NCR with MRB final disposition provided with # 6 above

List of As-Built Materials and Processes Used with material/process certifications showing pedigree

May be same documents as provided in #3. List of processes identified in #5 above. Copy of material and process certifications and manufacturing/test verification documentation

13 Achieved cleanliness data Cleanliness Certification with supportive data

14 Completed specification verification matrix Specification Verification Matrix

Test data and Reports (qualification and acceptance)

Weld qualification and acceptance test reports w/data

Qualification test report w/data

Acceptance test report w/data

16 Photographic documentation (post-test) Photograph of the delivered hardware

17 End Item Inspection Report Certificate of Compliance and DD250

18 Storage and Transportation Plans and Requirements

Contamination Control/Foreign Object Debris Plan, specific to the Thruster

19 Operational Constraints

J-2-16

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753CM-002

5. PAGE: 1/1

6. TITLE: Deviation/Waiver Approval Request

7. DESCRIPTION/USE: Deviation: A specific written authorization granted before the fact to depart from a particular Government-controlled requirement for a limited application. Waiver: A specific written authorization accepting a departure after occurrence from a Government-controlled requirement for a limited application.

8. OPR: ED10 9. DM: ST20

11. INITIAL SUBMISSION: As required

12. SUBMISSION FREQUENCY: As required

13. REMARKS:

14. INTERRELATIONSHIP: SOW paragraph 5.4

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Deviation/Waiver Approval Request (DAR) requests approval to depart from a Government-controlled requirement.

15.2 APPLICABLE DOCUMENTS/CLAUSES:

MSFC-STD-3394 Standard for Contractor Configuration Management, MSFC Programs/Projects

15.3.1 CONTENTS: DARs shall be prepared as specified in MSFC-STD-3394. The Program Control Number

(PCN), as assigned by MSFC and the DAR number assigned by the contractor shall be shown on all forms.

15.4 FORMAT: MSFC Form 847, “Deviation/Waiver Approval Request (DAR)”or equivalent, shall be used to document deviations/waivers.

15.5 MAINTENANCE: All requested changes to a DAR require submittal of a DAR revision.

15.6 APPROVAL OF DEVIATIONS/WAIVERS: Receipt of contractual approval from the procuring activity shall constitute the sole authority for the contractor to effect a DAR. This approval will be noted by disposition notation and the authorizing signature on the MSFC Form 847, or equivalent.

J-2-17

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753CM-003

5. PAGE: 1/2

6. TITLE: Engineering Change Proposals (ECPs) and Associated Documentation

7. DESCRIPTION/USE: To propose changes to Government controlled configuration documentation, e.g., engineering changes to drawings, parts lists, specifications, and interface control documents.

8. OPR: ED10 9. DM: ST20

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION: As required

12. SUBMISSION FREQUENCY: As required

13. REMARKS:

14. INTERRELATIONSHIP: SOW paragraph 5.4

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: To describe proposed changes with supporting rationale to Government-controlled configuration documentation.

15.2 APPLICABLE DOCUMENTS/CLAUSES:

MSFC-STD-3394 Standard for Contractor Configuration Management, MSFC Programs/Projects

15.3 CONTENTS: The requirements of MSFC-STD-3394 shall be used in the preparation of proposed changes to

Government-controlled configuration documentation.

a. The following MSFC forms or equivalent shall be prepared as required to define the specific requirements for a proposed change.

1. Engineering Change Proposals (ECP's) - MSFC Form 2348, or equivalent. Appropriate information shall be provided for each block on the ECP and yes/no questions will be answered with either a yes or no.

b. Changes to specifications, documents, drawings and parts lists shall be provided in From/To or Was/Is format so that the change is clearly defined and included with the submittal of the ECP.

The program control number (PCN) (or its equivalent) assigned by MSFC and the proposal number assigned by the contractor shall be shown on all forms and messages.

15.4 FORMAT: The formats shall be as defined in paragraph 15.3.

15.5 MAINTENANCE:

a. ECP maintenance shall be accomplished by complete revision.

b. PIRN's shall be a complete reissue.

J-2-18

DRD Continuation Sheet TITLE: Engineering Change Proposals and Associated DRD NO.: 1753CM-003 Documentation

DATA TYPE: 1 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

15.6 MSFC APPROVALS:

a. Receipt of contractual approval shall constitute the sole authority for the contractor to effect a Class I engineering change.

b. Changes to documentation shall be approved as a part of the ECP.

c. PIRN's shall be approved as part of the ECP.

The contractor shall prepare and submit ECP's when requested by MSFC to implement a Government-directed change.

J-2-19

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753CM-004

5. PAGE: 1/2

6. TITLE: Engineering Drawings and Associated Lists

7. DESCRIPTION/USE: To provide engineering data defining the design to the extent required to support manufacturing, test, and logistics support of the vehicle and payload systems and required spare parts.

Engineering drawings and associated lists shall be sufficient to depict the detailed configuration of the component. 2D and 3D Computer-Aided Design (CAD) models shall be submitted as supplemental information.

An indentured parts list shall be submitted for each configuration item that depicts the hierarchical structure of drawings-parts from the configuration item down to assemblies, subassemblies, and components in a tabular format. An Interface Control Drawing shall address all physical and functional requirements necessary to describe the interfaces that must be met to ensure hardware compatibility. The Interface Control Drawings shall not contain Proprietary data to allow the un-inhibited transmission of the drawings.

8. OPR: ED10 9. DM: ST20

11. INITIAL SUBMISSION: Two weeks prior to Design Conformance Review (DCR)

12. SUBMISSION FREQUENCY: Two weeks prior to the Design Conformance Review (DCR), as part of an

Acceptance Data Package (ADP), and as requested. In addition, 3D CAD Models shall be submitted between milestones as requested by the procuring activity, and updated Drawing Trees shall be submitted for the related configuration items Physical Configuration Audit (PCA).

13. REMARKS:

14. INTERRELATIONSHIP: SOW paragraph 5.4

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: Engineering drawings disclose (directly or by reference) the physical and functional requirements of an item by means of graphics or textual presentation or combinations of both, as supplemented by 3D models.

Drawing Trees depict the hardware and software configuration item drawing in graphic, top down, hierarchical structures.

ASME Y14.100 Engineering Drawing Practices ASME Y14.41 Digital Product Definition Data Practices ASME Y14.5 Dimensioning and Tolerancing

15.3 CONTENTS: Requirements:

a. Part I - Engineering drawings and associated lists shall meet the requirements of ASME Y14.100.

Geometric Dimensioning and Tolerancing shall be implemented in accordance with ASME Y14.5.

Supplemental 2D/3D CAD shall meet the requirements of ASME Y14.41. Engineering drawings and associated lists of end items, elements and/or all components and assemblies shall be provided to define the details necessary for the manufacture, test, inspection, operations and logistic support of the system.

This definition shall:

1. Reflect the end-product at its current level of design maturity.

2. Provide the engineering data for logistics support products.

3. Provide the necessary data to permit manufacture and/or acquisition of items identical to the original item(s).

J-2-20

DRD Continuation Sheet TITLE: Engineering Drawings and Associated List DRD NO.: 1753CM-004

DATA TYPE: 3 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

4. Document directly or by reference the following:

(a) Details of unique processes (i.e., not published or generally available to industry) when essential to design and manufacture.

(b) Performance ratings.

(c) Dimensional and tolerance data (Geometric Dimensioning and Tolerancing (GDT) shall be required between all external and major internal interfaces).

(d) Critical manufacturing processes and assembly sequences, and rigging procedures.

(e) Diagrams.

(f) Mechanical and electrical connections.

(g) Physical characteristics, including form and finish.

(h) Details of material identification, including heat treatment and protective coatings.

(i) Inspection, test, and evaluation criteria.

(j) Equipment calibration requirements.

(k) Quality assurance requirements.

(l) Hardware marking requirements.

(m) Requirements for reliability, maintainability, environmental conditions, shock, and vibration testing and other operational or functional tests.

5. Limited rights-in-data items - Engineering drawings for items which the Government does not have unlimited rights in data shall specify the form, fit, and function requirements of the item and conform to the requirements for a control drawing as defined in ASME Y14.100 or a specification prepared in accordance with project requirements.

b. Part II - Cable interconnect diagrams (CID's), electrical system schematics, and wiring lists. Cable interconnect diagrams, electrical system schematics, wiring lists, and fluid system schematics shall be prepared in accordance with ASME Y14.100. Part I drawings shall be utilized to the maximum extent possible in providing the design definition. The drawings shall include the following:

1. Component Level Documentation - Schematics and/or wiring lists for components, including interconnecting cable harnesses, shall be provided.

c. Engineering drawing shall specify marking criteria and methods for identification of parts produced or procured. Markings shall meet criteria defined in the component specification. All parts shall be physically marked. When physical marking or tagging causes a deleterious effect, labels, tags, and nameplates may be considered.

d. A drawing tree shall be submitted for each configuration item that graphically depicts the hierarchical structure of drawings-parts from the configuration item down to assemblies, subassemblies, and components.

15.4 FORMAT: Format of engineering drawings shall be in accordance with ASME Y14.100. Drawings shall be delivered in PDF format. 2D/3D CAD shall be in accordance with ASME Y14.41, in the current version of native developed CAD, fully parametric and associative. Originator format is acceptable for drawing trees. The contractor shall deliver Creo compatible 3D models (.STP, .IGS, etc.) of the component. Alternate formats may be acceptable upon negotiation. All documentation/data shall include the contractor's Commercial and Government Entity (CAGE) code and document numbers. The Contractor may submit electronic files of drawings and CAD models via CD, DVD, or direct electronic transfer (Product Data Management (PDM) Tool, File Transfer Protocol (FTP), etc.) as specified by the Government.

15.5 MAINTENANCE: All documents produced under this DRD must be maintained current. Changes to and/or updating of engineering drawings, associated lists, and drawing trees shall be in accordance with the contractor's approved drawing system and the provisions herein. Changes to engineering drawings under the Government's Class I change control shall be submitted by Engineering Change Proposal. The contractor shall maintain the capability to restore and modify any engineering data used in the design through the project lifecycle.

J-2-21

1. DPD NO.: 1753 ISSUE: RFP 2. DRD NO.: 1753DE-001

5. PAGE: 1/1

6. TITLE: As-Built EEE Parts List

7. DESCRIPTION/USE: To identify the Electrical, Electronic, and Electromechanical (EEE) parts actually used, to identify manufacturers of those parts, and to serve as a traceability record for the EEE parts installed in delivered equipment.

8. OPR: ES23 9. DM: ST20

10. DISTRIBUTION: Per contracting officer's letter

11. INITIAL SUBMISSION: As part of the Acceptance Review (AR)

12. SUBMISSION FREQUENCY: Subsequent changes in configuration

13. REMARKS: This data is used to verify acquisition of parts from qualified sources and for determining applicability of problems reported (such as Problem Advisories and ALERTs).

14. INTERRELATIONSHIP: SOW paragraph 4.1.1

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The As-Built EEE…