Att J-01 xEVAS Data Requirements Descriptions (DRD)-A0002.pdf

Exploration Extravehicular Activity Services (xEVAS) SOLICITATION No. 80JSC021R0006

PART III-LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

Attachment J-01

Data Requirement Descriptions

Attachment J-01 Page 2 xEVAS

TABLE OF CONTENTS

SECTION PAGE

1.0 DATA REQUIREMENTS DESCRIPTION (DRD)

2.0 ORGANIZATION OF DATA REQUIREMENTS DESCRIPTIONS

2.1 DRD Numbering

2.2 Data Types

2.3 Data Fidelity

3.0 DATA REQUIREMENTS DESCRIPTION (DRD) FORM

3.1 Distribution Requirements

3.1.1 Data Transmittal and Format

3.2 Data Transmittal

3.2.1 Data Transmittal Package

3.3 Data Format

3.4 Data Restriction Categories and Marking Statements

4.0 DRD MAINTENANCE PROCEDURES

4.1 Configuration Management of DRD

4.2 Reference to Other Documents and DRDs in Data Submittals

5.0 DRDS

5.1 xEVAS – Export Control (EC) DRDs

5.1.1 xEVAS-EC-01: Export Control Plan and Audit Results

5.2 xEVAS – Engineering (ENG) DRDS

5.2.1 xEVAS-ENG-01: NASA Standards and Specificiations Compliance and Tailoring

5.2.2 xEVAS-ENG-02: Integration and Test Plan

5.2.3 xEVAS-ENG-03: Verification and Validation (V&V) Plan

5.2.4 xEVAS-ENG-04: Verification Closure Notices (VCN)

5.2.5 xEVAS-ENG-05: Data Input for NASA Integration and Independent Verification and Validation (IV&V)

5.2.6 xEVAS-ENG-06: xEVA System Interface Definition Document (IDD)

Attachment J-01 Page 3 xEVAS

5.2.7 xEVAS-ENG-07: Mission Resource Allocation Document (MRAD)

5.2.8 xEVAS-ENG-08: xEVA Systems Guide

5.2.9 xEVAS-ENG-09: Integrated Systems Performance Analysis (IPSA)

5.2.10 xEVAS-ENG-10: Computer-Aided Design (CAD) Models

5.2.11 xEVAS-ENG-11: Ground Test Safety Plan

5.3 xEVAS – Human Health and Performance (HHP)

5.3.1 xEVAS-HHP-01: Human Error Analysis (HEA) Plan, Reports, and Analysis

5.3.2 xEVAS-HHP-02: NASA Human Rating Certification Data Products

5.3.3 xEVAS-HHP-03: Human System Integration Plan (HSIP)

5.3.4 xEVAS-HHP-04: Food Process and Certification Plan (FPCP), Anaysis, and Reports

5.4 xEVAS – Information Technology (IT)

5.4.1 xEVAS-IT-01: Information Technology (IT) Security management Plan and IT Security Plan

5.5 xEVAS – Operations (OPS)

5.5.1 xEVAS-OPS-01: Integrated Operations and Training Plan

5.6 xEVAS – Program Control (PC)

5.6.1 xEVAS-PC-01: Program Management Review (PMR)

5.6.2 xEVAS-PC-02: Integrated Master Schedule (IMS)

5.6.3 xEVAS-PC-03: Mission Success Criteria and Determination methodology

5.6.4 xEVAS-PC-04: EVA Excellence Determination

5.7 xEVAS – Program Management (PM)

5.7.1 xEVAS-PM-01: Program Management (PM) Plan

5.7.2 xEVAS-PM-02: Insight and Collaboration Implementation Plan

5.7.3 xEVAS-PM-03: Mission Integration and Operations Management Plan (MIOMP)

5.7.4 xEVAS-PM-04: Demonstration Milestone Review Plan

5.7.5 xEVAS-PM-05: Mission Milestone Review Plan

5.7.6 xEVAS-PM-06: Demonstration Objectives Plan and Report

5.7.7 xEVAS-PM-07: Imagery Plan, Products and Catalog

Attachment J-01 Page 4 xEVAS

5.8 xEVAS – Procurement (PR)

5.8.1 xEVAS-PR-01: Organizational Conflict of Interest (OCI) Avoidance mitigation plan

5.8.2 xEVAS-PR-02: Government Property Management Plan (PMP)

5.8.3 xEVAS-PR-03: Financial Reporting Contractor – Held Property

5.8.4 xEVAS-PR-05: Environmental Compliance Reports

5.8.5 xEVAS-PR-06: Small Business Subcontracting Plan and Reports

5.8.6 xEVAS-PR-07: Close-Out Plan

5.9 xEVAS – Safety and Mission Assurance (SMA)

5.9.1 xEVAS-SMA-01: Safety and Health Plan

5.9.2 xEVAS-SMA-02: Safety and Mission Assurance Plan

5.9.3 xEVAS-SMA-03: System Safety Assessment Report (SSAR)

5.9.4 xEVAS-SMA-04: Probailistic Risk Assessment

5.9.5 xEVAS-SMA-05: Failure Modes and Effects Analysis (FMEA) and Critical items List (CIL)

Attachment J-01 Page 5 xEVAS

1.0 DATA REQUIREMENTS DESCRIPTION (DRD)

The following pages set out the documentation requirements of this contract. Each Data Requirements Description (DRD) prescribes the required data product content, schedule, type, and any other particulars for specific data submission requirements.

The DRD defines, by an individual Data Requirement (DR), the information and data required for each deliverable document. The data types are used to identify the approval and control required for each DR.

Subject to the Rights in Data (Deviation) clause, this document sets forth the data requirements in each DRD and shall govern the data required under this contract. The Contractor shall furnish data defined by the DRDs listed by category of data. Such data shall be prepared, maintained, and delivered to National Aeronautics and Space Administration (NASA) in accordance with the requirements set forth herein. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, the regulation takes precedence, pursuant to FAR 52.215.33. NASA-Owned/Contractor Held records shall be managed by the Contractor in accordance with Title 36 of the Code of Federal Regulations, Chapter XIII B. Records Management and NPD 1440.6, NASA Records Management. The records shall be organized in accordance with the instructions in NPR.1441.1, NASA Records Management Program Requirements as applicable. The Contractor shall disposition records and non-records in accordance with NPR 1441.1, which has been approved by NASA. All questions on records management issues shall be directed through the Contracting Officer to the International Space Station (ISS) Records Liaison Officer (RLO) or applicable Program Office RLO.

Attachment J-01 Page 6 xEVAS

2.0 ORGANIZATION OF DATA REQUIREMENTS DESCRIPTIONS

2.1 DRD NUMBERING

All DRDs begin with “xEVAS” to denote the contract name.

The next number describes the type of document:

o EC = Export Control o ENG = Engineering o HHP = Human Health and Performance o IT = Information Technology o OPS = Operations o PC = Program Control o PM = Program Management o PR = Procurement o SMA = Safety and Mission Assurance

The third part of the DRD number is the sequence number in the specific DR type (e.g.

xEVAS-PM-01, xEVAS-PM-02, etc.).

Within the DRD itself, it will indicate when it is only applicable to a Contract Line Item Number (CLIN) or sub-CLIN in the format CLIN #A, CLIN #B, or CLIN #C, where # = the CLIN number and A, B, and C are the sub-CLIN indicator.

CLIN numbers:

CLIN 1 = ISS Program EVA Capability

CLIN 2 = Artemis Program EVA Capability

CLIN 3 = Advanced Missions EVA Capability

CLIN 4 = Special Studies

Sub-CLIN letters applicable to CLIN 1 thru 3:

A. EVA Demonstration

Attachment J-01 Page 7 xEVAS

B. EVA Services

C. Mission Unique Capabilities

2.2 DATA TYPES

For the purposes of this clause, the types of data and their contractually applicable requirements for approval and delivery after contract award are listed in Table 2.2-1 Data Types.

TABLE 2.2-1 DATA TYPES

Type Description

That information and documentation which requires NASA approval prior to release. Approved Type 1 information and documentation shall be controlled, and deviations from or changes to the concepts, techniques, and/or requirements stated therein shall require NASA approval prior to implementation. All work under this contract covered by type 1 documents shall be performed in accordance with those approved documents. The Contracting Officer’s Representative has approval authority and signs the data prior to its release. Contractually binding documents shall only be implemented or revised via a contract modification.

That information and documentation for which NASA reserves a time-limited right to disapprove. Type 2 data shall be submitted to designated repository for review not less than 45 calendar days prior to its release for use or implementation. The Contractor shall clearly identify the target release date in the ‘submitted for review’ transmittal. If the Contractor has not received any comment prior to the target released date, the document may be released for appropriate use. Any NASA comment received shall be appropriately dispositioned and resubmitted prior to implementation, restarting the 45-day review period.

That information and documentation which does not require formal NASA review and approval. Information in this category would include statuses, analyses, test results, handbooks and other designated lists, reports, etc. While type 3 deliverables do not require NASA approval, the deliverable must satisfy all applicable contractual requirements.

That information and documentation that the Contractor shall deliver within the Contractor’s electronic system where NASA has been granted read, print, search and download access through contract completion. The Contractor’s act of placing the data within their system wherein NASA is provided the ability to read, print, search and download the data shall constitute delivery for purposes of defining NASA’s rights in data as set forth in FAR 52.227- 14, Rights in Data – General (Deviation), as modified in this contract. Type 4 DRDs do not require NASA approval; however, the DRD must satisfy all applicable contractual requirements. For Type 4 DRDs, the Contractor shall notify the Contracting Officer or designated representatives when the data has been delivered into the Contractor system.

Note: Documents submitted under this clause, even though directly (Type 1) or implicitly (Type

2) approved by NASA, shall not take precedence of the specifications as set out in the Performance Work Statement, Section C.

Any Type 1 or Type 2 data requirement requiring revision based on NASA review shall be delivered complete, with NASA comments incorporated, within 30 calendar days of receipt of NASA comments.

Attachment J-01 Page 8 xEVAS

2.3 DATA FIDELITY

In addition to the required frequency for data deliverable submittals, the DRD also defines the level of readiness/fidelity, which applies to the submission of DRDs:

Baseline (B) - A preliminary version of a delivery for NASA review. Baseline submittals may contain some To be Determined (TBD) items. Baseline version fidelity shall reflect the Contractor’s internally approved baseline of the product and be adequate to permit NASA disposition in accordance with the DRD Type. Baseline versions may be submitted periodically leading to a Final version.

Final (F) - A Final version of a delivery shall reflect the Contractor’s internally approved final version of the product and is ready for NASA disposition in accordance with the DRD Type. No TBDs may be included. Unless otherwise specified within the DRD, after final version DRD has been dispositioned by NASA, the Contractor shall submit any changes or additions for NASA review and disposition in accordance with the DRD Type.

Attachment J-01 Page 9 xEVAS

3.0 DATA REQUIREMENTS DESCRIPTION (DRD) FORM

This section provides a description of the fields of the DRDs.

1. DRD Title: Unique name for the DRD

2. DRD No.: Unique identifier for the DRD

3. Data Type: Type 1 Approve, Type 2 Review, Type 3 Submit, Type 4 Submit

4. Solicitation No.: The solicitation number

5. Contract No.: The contract number

6. Date Issued: The date the baseline version of the DRD was issued

7. Date Revised: The date the latest revision of the DRD was issued (if revised)

8. DRD Category: Technical, Administrative, or Safety and Mission Assurance (S&MA)

9. Description/Use: A brief description of the DRD and what the intended use is for the data

10. Distribution: Distribution list of recipients

OPR: NASA’s Office of Primary Responsibility

Initial Submission: When the first submission is due to the Government

Submission Frequency: When subsequent submissions are due to the Government

Format: Identify the specific format

Interrelationship: Identify the Performance Work Statement (PWS) references, CLIN references, DRD references, clauses, or provision numbers

Applicable Documents: Applicable directives, plans, guides, etc.

Scope: The extent to which the requirement is relevant. For example, the onsite employee listing provides a listing of all Contractor employees working on this contract

Contents: The Government’s expectations for the deliverable, i.e. what items should be included/addressed

Remarks: Special instructions, if applicable

Attachment J-01 Page 10 xEVAS

Maintenance: The required maintenance, e.g. changes shall be incorporated by complete reissue

DRDs shall be maintained electronically in the Contractor’s own format unless a specified format is defined in the DRD. The Government may define specific DRD data format to support the utilization of this data in the Management Information System.

All electronic DRDs shall be submitted to the Program authorized repository Electronic Document Management System (EDMS) or equivalent unless otherwise specified in the DRD.

When a DRD does not require an update from one mission to the next, the Contractor shall notify the Contracting Officer electronically prior to the due date that the product of the previous mission is still valid and need not produce a new one.

A Distribution Requirement (DR) follows a workflow process once it is delivered into Program authorized repositories or equivalent, where it may either be approved or “reworked”. If NASA approves a DR, the contractor is notified via e-mail that the DR has been approved. If the DR is rejected, NASA will provide comments to the contractor through the “rework” process detailing why it has not been approved. The contractor has 30 calendar days from the date the DR was rejected to disposition NASA comments and resubmit the DR electronically into EDMS. The DR is then either approved or sent back again to the contractor via the “rework” process. There is not a limit on how many times a DR can go through the “rework” process before it is finally approved.

Note: NASA will assist the Contractor in obtaining an EDMS account and provide training on the EDMS upload capabilities.

Nothing contained in this DRD clause shall relieve the Contractor from furnishing data not identified and described in this attachment but called for by, or under the authority of, other provisions or as specified elsewhere in this contract.

3.1 DISTRIBUTION REQUIREMENTS

The Contractor shall provide one copy of each DR to the standard distribution list shown in Item 10 of the DRDs. Additional distribution shall be made as directed, in writing, by the Contracting Officer. Delivery Notices will be used to confirm delivery of electronically resident DR Deliverables.

3.1.1 DATA TRANSMITTAL AND FORMAT

This section provides additional detail regarding the transmittal and format of the DRDs.

3.2 DATA TRANSMITTAL

DRs shall be transmitted to NASA electronically to the Program Authorized Repository (EDMS or equivalent), or by other mechanism agreed to by the Contracting Officer. The Contractor shall

Attachment J-01 Page 11 xEVAS attach a Delivery Notice (DN) to deliverable notify the Contracting Officer and the Contracting Officer Representative (COR) electronically of DR Delivery.

DRs listed as requiring updates: The Contractor shall review the document to ensure that all content in the deliverable is verified as current and accurate. If the Contractor’s review determines that all content in the deliverable is verified as current and accurate, the Contractor shall submit a transmittal memorandum with a Delivery Notice to the Program Authorized Repository (EDMS or equivalent) stating that the document has been reviewed for currency and accuracy and requires no revision at this time (referencing the most current version and date– Basic, Rev 1, with date). If the Contractor’s review determines that any content in the deliverable is not current and accurate, the Contractor shall resubmit the deliverable with appropriate updates to ensure it is current and accurate.

3.2.1 DATA TRANSMITTAL PACKAGE

For each DRD, the transmittal package shall:

(a) Provide the following information in a Contractor transmittal memorandum:

1. Contract number

2. Contractor name

3. DRD number

4. DRD data type

5. Task Order Number

6. Submission date

7. Milestone being satisfied (if applicable)

8. Document number, date, and revision

9. Document title

10. File names of all files being delivered; multiple files per document must be clearly related to the document

11. Distribution (Notification list as defined by the DRD distribution field and the Contracting Officer’s letter)

12. Targeted release date

(b) Submit electronic files to the appropriate NASA or Contractor site

Attachment J-01 Page 12 xEVAS

(c) Provide the DRDs in an electronic format that is readable, printable, searchable, and downloadable by NASA using publicly available off-the-shelf software. If the electronic format is not supported by publicly available off-the-shelf software, the Contractor shall provide NASA with the necessary software.

3.3 DATA FORMAT

Existing Contractor internal documents may be used to meet the data requirements of the DRD to the extent practicable. The DRD will call out any special format requirements if they are required.

The Contractor’s submittal in response to the DRDs shall be provided in an electronic format that meets four basic requirements: “Readable”, “Printable”, “Searchable” and “Downloadable” by NASA utilizing publicly available off-the-shelf software. If the electronic format is not supported by publicly available off-the-shelf software, the Contractor shall provide NASA with the necessary software and approach to support the four basic requirements.

3.4 DATA RESTRICTION CATEGORIES AND MARKING STATEMENTS

The Contractor shall ensure all Controlled but Unclassified Information (CUI) is marked in accordance with NASA Interim Directive (NID) 2810.135, Controlled Unclassified Information and ITS-HBK-CUI, Controlled Unclassified Information Handbook.

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 United States (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.

FIGURE 3.4-1 INTERNATIONAL TRAFFIC IN ARMS REGULATIONS (ITAR) NOTICE

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

Attachment J-01 Page 13 xEVAS

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.

FIGURE 3.4-2 EXPORT ADMINISTRATION REGULATIONS (EAR) NOTICE

Data otherwise delivered under this contract, meaning delivered pursuant to one or more DRDs contained herein, shall comply with the marking requirements contained in clause I.16, Rights in Data – General (Deviated), and contract section H clauses Marking Requirements for Technical Data and Computer Software, and Validation and Challenge Procedures for Technical Data and Computer Software.

In accordance with FAR 52.227-14(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.

Attachment J-01 Page 14 xEVAS

4.0 DRD MAINTENANCE PROCEDURES

4.1 CONFIGURATION MANAGEMENT OF DRD

The Contractor shall employ a system for organizing, identifying, and tracking all submittals of DRDs, to include any changes or revisions.

4.2 REFERENCE TO OTHER DOCUMENTS AND DRDS IN DATA SUBMITTALS

The Contractor’s submittal of a DRD may refer to other documents and/or other DRDs. At the time of submission of the DRD, any referenced document within the DRD shall be made available to NASA. The Contractor shall provide NASA with access to any referenced document and the location of that data within the referenced document. Any reference made to data associated with another DRD that is required separately by the contract shall include the DRD number of and location of the data within the referenced DRD.

Attachment J-01 Page 15 xEVAS

5.0 DRDS

5.1 XEVAS-EXPORT CONTROL (EC) DRDS

5.1.1 XEVAS-EC-01: EXPORT CONTROL PLAN AND AUDIT RESULTS

1. DRD Title: Export Control Plan and Audit Results

2. DRD No.: xEVAS-EC-01 3. Data Type: Plan: Type 2, Audit Results: Type 3

4. Solicitation No.: To be filled in by CO at final RFP release

5. Contract No.: To be filled in by CO at award

6. Date Issued: To be filled in by CO at award

7. Date Revised: To be filled in by CO following first revision after award

8. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

9. Description/Use: Document the Contractor’s approach for Export Control (EC).

10. Distribution: 1 electronic copy: Program Authorized Repository (EDMS or equivalent) Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA Contracting Officer Representative, NASA Documentation Repository Representative, Contractor’s Contract Representative, others as negotiated

OPR: EVA Office (JSC-XX)

Initial Submission:

Plan: Baseline due at Proposal.

Audit Results: October 15, 2022

Submission Frequency: As Required

Plan: Final at 60 days post contract award. Annually by October 15 if updates to the plan are made.

Audit Results: Annually by October 15.

Format: Contractor format is acceptable and in accordance with Section 3.3 Data Format.

Interrelationship: H.4 NFS 1852.225-70, Export Licenses, DRD xEVAS-PM-01, Program Management Plan, PWS 2.2.8, Export Control, Attachment J-08, Work Plan

Applicable Documents: NPR 2190.1, NASA Export Control Program, NPD 2190.1, NASA Export Control Program, NASA Advisory Implementing Instruction (NAII) 2190.1, NASA Export Control, JSC Work Instruction (JWI) 2190.1, JSC Export Compliance (reference JSC

Attachment J-01 Page 16 xEVAS

Advisory Implementing Instruction (JAII) 2190.1, Export Services Team (EST) Operations Manual

Scope: The plan shall describe all export control activities related to the performance of contract requirements.

Contents:

Plan: The Contractor shall prepare and submit an Export Control Plan (ECP), describing the Contractor’s planned approach for accomplishing contract functions while adhering to NASA and U.S. export laws, regulations, and directives. The plan shall include an explanation of expected exports, approval process and authorities used, and managing of foreign nationals in complying with export control laws.

Audit Results: The Contractor shall include a thorough examination of all export control processes (as outlined in the Contractor’s Export Control Plan) associated with this contract, areas for improvement (if any), and corrective action plans for identified areas of improvement. Affected subcontractors are required to do their own self-audits and report the results of the audit to NASA through the xEVAS prime contractor. Prior to audit completion, inclusion on the audit process thru informal statuses to the ISS Lead Export Control Representative, the JSC Export Services Team or Center Export Administrator is optional and might prove useful in the success of this effort.

(a) Define current audit processes,

(b) Document the export control processes audited and audit findings,

(c) Based on audit findings, the contractor/subcontractor shall include corrective action plans for any processes identified for improvements and notification of when the correction of any non-conformances has been completed.

Remarks: The Export Control Plan shall become a part of the contract as Attachment J-09.

Maintenance: Any updates to the plan require a resubmission of the plan. Changes shall be incorporated by complete reissue with a change log in the front matter of the document. Changes shall be highlighted using track changes “redlining”

Attachment J-01 Page 17 xEVAS

5.2 XEVAS-ENGINEERING (ENG) DRDS

5.2.1 XEVAS-ENG-01: NASA STANDARDS AND SPECIFICIATIONS

COMPLIANCE AND TAILORING

1. DRD Title: NASA Standards and Specifications Compliance and Tailoring

2. DRD No.: xEVAS-ENG-01 3. Data Type: Type 1

4. Solicitation No.: To be filled in by CO at final RFP release

5. Contract No.: To be filled in by CO at award

6. Date Issued: To be filled in by CO at award

7. Date Revised: To be filled in by CO following first revision after award

8. DRD Category:

☒ Technical ☐ Administrative

☐ S&MA

9. Description/Use: The Contractor shall identify the standards and specifications used for the development of the xEVA System, the corresponding equivalency of these standards and specifications relative to meeting or exceeding a NASA-provided reference-set of design and construction standards, and the data required for understanding and assessing the risk associated with the use of non-equivalent industry standards and specifications.

Contracting Officer Representative, NASA Documentation Repository Representative, Contractor’s Contract Representative, others as negotiated

OPR: EVA Office (JSC-XX)

Initial Submission: Baseline of Content Item numbers a through e due with proposal (Attachment A completed to identify the Contractor’s proposed compliance and tailoring to NASA standards and specifications).

Submission Frequency: Baseline update due at Mission Concept (MC), Baseline update due at CBR, Final due at Preliminary Design Review (PDR). (Note: Updates after PDR are as required per details described in the Content Item h below).

Format: Content Item numbers a through c shall be in Microsoft Word or Excel format.

Contractor’s format is acceptable for delivery of standards and additional requested data. All deliverables in accordance with Section 3.3 Data Format.

Interrelationship:, PWS 2.5.3, Adjudication of Standards, PWS 2.6.2, Human Systems Integration, DRD xEVAS-PM-04, Demonstration Milestone Review Plan, DRD xEVAS-PM-05, Mission Milestone Review Plan, Attachment J-08, Work Plan

Applicable Documents: See Attachment B

Attachment J-01 Page 18 xEVAS

Scope: Provide a description of the approach to the identification and application of design and construction standards and specifications to be used for the development of the xEVA System as required to take full advantage of the demonstrated reliability benefits of commercial system.

Contents:

Specific content includes:

(a) The Contractor shall identify in Attachment A the desired method of addressing each standard listed in Attachment B. Either meeting the NASA referenced standard as listed or use of a proposed alternate standard relative to meeting or exceeding one of the NASA standards, and then provide the proposed alternate standard, specification or approach that the Contractor proposes to follow instead. Attachment A of this DRD, will need to be completed to define the Contractor’s standards and specifications to be applied to the development of the xEVA systems.

(b) A summary of the Contractor’s design and construction standards and specification philosophy to include the following: descriptions of the heritage of the standards and specifications the Contractor uses; the process of adopting and/or tailoring government and industry standards for Contractor usage; and the process for creating and maintaining internal company standards.

(c) A description of the Contractor’s technical decision-making process describing the review and approval process and level of authority required for deviations and waivers against the Contractor’s applicable design and construction standards and specifications.

(d) An assessment of the equivalency of the Contractor’s application of design and construction standards to meet or exceed the NASA standards in Attachment B of this DRD, Reference List of NASA Design and Construction Standards and Specifications.

(e) For each standard, justification for the suitability of using industry non-equivalent standards and specifications to meet or exceed the NASA standard including relevant data on past usage and other supplemental information that allows NASA to adequately assess the risk associated with their usage.

(f) Copies of the Contractor’s design and construction standards and specifications not found in the public domain, even if not listed in Attachment B, shall be provided electronically.

(g) With the final submittal, identify and provide all deviations and waivers against the Contractor’s applicable design and construction standards.

(h) After PDR, all deviations and waivers and/or proposed updates are required to be submitted within 30 calendar days of identification by the Contractor, as a formal DRD re-submit, per Maintenance requirements listed below.

Attachment J-01 Page 19 xEVAS

Remarks: The NASA Standards and Specifications Compliance and Tailoring shall become a part of the contract as Attachment J-16.

Additional details regarding potential tailoring of the standards listed in Attachment B can be found in EVA-EXP-0034, Exploration EVA System Technical Standards.

Maintenance: Updates to this document shall be incorporated by resubmission of the document after coordination with the NASA Contracting Office Representative. Changes shall be incorporated by complete reissue with a change log in the front matter of the document.

ATTACHMENT B

TABLE DRD XEVAS-ENG-01-02 APPLICABLE LIST OF NASA DESIGN AND

CONSTRUCTION STANDARDS AND SPECIFICATIONS

Document Number

Document Revision Document Title Applicability Notes

AIAA-S-

080A-

Revision A 4/13/18

Metallic Pressure Vessels, Pressurized Structures, and Pressure Components

ALL

AIAA-S-

081B-

Revision B 4/13/18

Composite Overwrapped Pressure Vessels

ALL

ANSI/ES

D S20.20

Edition 14 06/11/2014

For the Development of an Electrostatic Discharge Control Program for – Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

ALL

ASTM

D6193

07/01/2020 Standard Practice for Stitches and Seams

ALL

EP-19-001 03/25/2019 Interpretation Memo for the Battery TR Propagation Requirements in JSC 20793 Rev D

ALL

GEIA-

STD-

0005-1

Revision A 02/24/2016

Performance Standard for Aerospace and High- Performance Electronic Systems Containing Lead-free Solder

ALL

GEIA-

STD-

0005-2

Revision A 05/01/2012

Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High- Performance Electronic Systems

ALL GEIA-STD-0005-2 has a selection of five control levels.

NASA will adjudicate the appropriate level of control with the offeror. Typically, for EVA spacesuit hardware, a control level of 2C will be required.

GP 10023 Baseline 09/05/2018

Gateway Program Safety and Mission Assurance Requirements

ALL

Document Number

Document Revision Document Title Applicability Notes

GP 11461 Baseline 11/14/2019

Gateway Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

ALL except

3.5 and 3.9.3

The following sections are not applicable: 3.5 Lightning, and

3.9.3 Hazards of electromagnetic

radiation to ordnance.

GP 11464 Baseline 11/14/2019

Gateway Electromagnetic Environmental Effects (E3) Requirements

ALL

IEC

61000-4-2

Edition 2.0 12/01/2008

Electromagnetic Compatibility (EMC) – Part 4-2: Testing and Measurement Techniques – Electrostatic Discharge Immunity Test

ALL

IPC-2152 Baseline 08/01/2009

Standard for Determining Current Carrying Capacity in Printed Board Design

ALL

IPC-2220

Series

2221: B 2222: A 2223: E 2224: Baseline 2225: Baseline 2226: A

Family of Printed Board Design Standards

ALL

IPC-6010

Series

6011: BL

6012: E

6012: ES

6013: D AMD 1

6015: Baseline 6017: Baseline

6018: CS

Family of Printed Board Fabrication Standards

ALL The xEVA System shall meet the intent of the requirements defined in IPC-6011, Generic Performance Specification for Printed Boards, as well as the associated technology performance specifications of the IPC-6010 series per Performance Class 3 with the exception for IPC-6012, where the Space Addendum is applicable instead of Performance Class 3.

IPC-CM-

770E

Revision E 01/2004

Guidelines for Printed Board Component Mounting

ALL

IPC J-

STD-001G

Revision G 09/1/2018

Requirements for Soldered Electrical and Electronic Assemblies

Document Revision Document Title Applicability Notes

IPC J-

STD-

001GS

03/2018 Space Applications Electronic Hardware Addendum to IPC J-STD- 001GS Requirements for Soldered Electrical and Electronic Assemblies

ALL

IPC/WHM

A-A- 620D-S

Revision D 09/01/2020

Space Applications Electronic Hardware Addendum to IPC/WHMA- A-620D

ALL

ISO/IEC

17025:201

11/01/2017 General requirements for the competence of testing and calibration laboratories

ALL

JPR-

1800.5

Baseline 07/19/2017

Biosafety Review Board Operations and Requirements

ALL

JSC-

08080-2

Revision B 08/04/2020

JSC Design and Procedural Standards

ALL The Spacesuit and EVA hardware shall meet the intent of JSC- 08080-2, JSC Design and Procedural Standards. This clause is only applicable for the design, manufacture, fabrication, assembly, or test of space-flight equipment and Ground Support Equipment.

JSC 20793 Revision D 03/28/2017

Crewed Space Vehicle Battery Safety Requirements

ALL

JSC 26895 Revision A 04/2014

Guidelines for Assessing the Toxic Hazard for Spacecraft Chemicals and Test Materials

ALL

JSC 62809 Revision D 04/22/2010

Human Rated Spacecraft Pyrotechnic Specification

Document Revision Document Title Applicability Notes

JSC 65828 Revision B, Change1 07/15/2014

Structural Design Requirements and Factors of Safety for Spaceflight Hardware

ALL All flight hardware structures of the xEVA System, except for glass or ceramic windows, shall meet the intent of JSC 65828.

The following sections of JSC 65828 are not applicable: 3.2.7 Parachute and Parafoil Systems,

3.2.8.4 Pressure Vessels, 3.8.35

Composite Overwrapped Pressure Vessels, 3.2.8.7 Doors and Hatches in Habitable Modules, 3.2.9 Liquid Propulsion Engine Structures, 3.2.10 Solid Rocket Motors. Due to JSC 65828 sections 3.2.8.4 and 3.2.8.5, referencing outdated version of AIAA-S-80 and AIAA-S-081the versions above should be used.

Previous EVA spacesuit softgoods have been qualified with lower test factors of safety than listed here. NASA expects tailoring of suit softgoods test factors.

Previous EVA spacesuit softgoods have been qualified with lower test factors of safety than listed here. NASA expects tailoring of suit softgoods test factors.

JSC 67035 Revision A 08/2017

Best Practices and Guidelines for Thin Wall Pressure Boundaries for Human Spaceflight Applications

ALL JSC 67035 is intended to serve as recommendations to supplement hardware Program requirements as defined in existing standards (e.g. NASA-STD-6016, NASA-

STD-5006, NASASTD-5012,

NASA-STD-5017, NASA-STD-

5001, AIAA-S-080, MSFC-

DWG-20M02540, MSFC-SPC-

166 and SMC-S-016 or approved alternate standards).

JSC 67551 Baseline 04/16/2021

Avionics Ionizing Radiation Effects Standard

Document Revision Document Title Applicability Notes

MIL-STD-

Revision C 08/13/2015

Design, Manufacturing and Quality Standards for Custom Electromagnetic Devices for Space Applications

ALL

MSFC-

DWG-

20M02540

Revision E 01/15/1992

Assessment of Flexible Lines for Flow-Induced Vibration

ALL The xEVA System shall prevent Flow-Induced Vibration (FIV) in metal bellows and flexhoses over their operating flow range +/- 10% or show that part life is 4 times the operational life when FIV cannot be eliminated.

The FIV analysis to determine the predicted FIV flow range shall be performed to meet the intent of

MSFC-DWG-20M02540,

Assessment of Flexible Lines for Flow-Induced Vibration.

MSFC-

SPEC-626

Baseline 02/28/1990

Test Control Document for Assessment of Flexible Lines for Flow Induced Vibration

ALL

NASA-

HDBK-

Revision C

Forced Limited Vibration Testing

ALL

NASA-

HDBK-

Revision A 10/19/2017

Mitigating In-Space Charging Effects – A Guideline

ALL

NASA-

STD-1008

Baseline 09/21/2021

NASA Classifications and Requirements for Testing Systems and Hardware to Be Exposed to Dust in Planetary Environments

ALL

NASA-

STD-4003

Revision A 03/09/2016

Electrical Bonding for NASA Launch Vehicles, Spacecraft, Payloads, and Flight Equipment

ALL

NASA-

STD-4005

Revision A 02/04/2016

Low Earth Orbit Spacecraft Charging Design Standard

ALL

NASA-

STD-5002

Revision A 09/25/2019

Load Analyses of Spacecraft and Payloads

ALL

NASA-

STD-5005

Revision D 08/27/2020

Standard for the Design and Fabrication of Ground Support Equipment

Document Revision Document Title Applicability Notes

NASA-

STD-5012

Revision B 06/16/2016

Strength and Life Assessment Requirements for Liquid Fueled Space Propulsion System Engines

ALL

NASA-

STD-5017

Revision A Change 1 07/31/2015

Design and Development Requirements for Mechanisms

NASA-

STD-5018

Baseline 08/12/2011 with Change 1 (11/27/2019)

Strength Design and Verification Criteria for Glass, Ceramics, and Windows in Human Space Flight Applications

Sections 4.6.3, 5.6.3, 4.10.2 and 5.10.2 are not applicable

For window systems (or portions of window systems) that use non-brittle materials such as plastic panes refer to requirement JSC 65828.

NASA-

STD-5019

Revision A, Change 08/24/2020

Fracture Control Requirements for Spaceflight Hardware

ALL

NASA-

STD-5020

A, Change 1 02/11/2019

Requirements for Threaded Fastening Systems in Spaceflight Hardware

ALL

NASA-

STD-6016

Revision A 11/30/2016

Standard Materials and Processes Requirements for Spacecraft

ALL

NASA-

STD-6030

Baseline 04/21/2021

Additive Manufacturing Requirements for Spaceflight Systems

ALL

NASA-

STD-7009

Revision A 07/13/2016 with Change 1 (12/07/2016)

Standard for Models and Simulations

4.1.1, 4.7, 4.8

NASA-

STD-7012

Baseline 11/13/2020 with Change 1 (11/13/2020)

Leak Test Requirements ALL

NASA-

STD-

8739.1

Revision B 06/30/2016

Workmanship Standard for Polymeric Application on Electronic Assemblies

ALL

NASA-

STD-

8739.5

Revision A 10/05/2015

Fiber Optic Terminations, Cable Assemblies, and Installation

ALL

NASA-

STD-

8739.6

Revision B 02/04/2021

Implementation Requirements for NASA Workmanship Standards

Document Revision Document Title Applicability Notes

NASA

STD-

8739.8

Rev. A 6/10/2020

Software Assurance and Software Safety Standard

ALL

NASA-

STD-

8739.10

Baseline 06/13/2017

Electrical, Electronic, and Electromechanical (EEE) Parts Assurance Standard

ALL

NPR

7150.2

Revision C 08/02/2019

NASA Software Engineering Requirements

ALL xEVA system to meet NPR

7150.2 for all class A software, or safety critical as defined in

NASA-STD-8739.8A

NPR

8735.1

Revision D 07/29/2018

Exchange of Problem Data Using NASA Advisories and the Government- Industry Data Exchange Program (GIDEP)

ALL

SAE

AS5553

Revision C 03/26/2019

Counterfeit Electrical, Electronic, and Electromechanical (EEE) Parts; Avoidance, Detection, Mitigation, and Disposition

ALL

SAE

AS6174

Revision A 07/29/2014

Counterfeit Materiel, Assuring Acquisition of Authentic and Conforming Materiel

ALL

SAE-

AS7928

Revision C 05/01/2019

General Specification for Terminals, Lug: Splices, Conductor: Crimp Style, Copper

ALL

SAE

AS9003

Revision A 08/06/2012

Inspection and Test Quality Systems Requirements for Aviation, Space, and Defense Organizations

ALL

SAE

AS9100

Revision D 09/01/2016

Quality Management Systems – Requirements for Aviation, Space and Defense Organizations

ALL

SMC-S-

4/12/13 Space and Missile Systems Center Standard Technical Requirements for Electronic Parts, Materials, and Processes Used in Space Vehicles

Document Revision Document Title Applicability Notes

SMC-S-

Revision N/A 09/05/2014

Space and Missile Systems Center Standard Test Requirements for Launch, Upper-Stage and Space Vehicles

ALL The xEVA System and associated subsystems and units shall meet the intent of the environmental and structural ground testing requirements as defined in SMC Standard SMC-S-016, Test Requirements for Launch, Upper- Stage, and Space Vehicles, with the following exceptions:

1)NASA-STD-7012, Leak Testing, 2)Shock as an acceptance test is not required.

3)For burn-in testing, the xEVA System and associated subsystems and units shall meet the intent of the burn-in testing requirements defined in SSP 41172.

4) For life testing of mechanisms, the life test factor from NASA- STD-5017 shall be used.

5) For vibration, shock, and acoustics qualification testing, a test margin of 3 dB rather than 6 dB is acceptable provided that test tolerances for random vibration are covered and low side tolerance for shock is not below the required design level.

6) Forced limited vibration testing shall meet the intent of NASA-HDBK-7004, Force Limited Vibration testing. Note:

SSP 41172 is an acceptable alternative with exceptions 1, 2 and 4-6 applying

Document Revision Document Title Applicability Notes

SSP 30312

Volume 1

Revision L 10/24/2014

Electrical, Electronic, and Electromechanical (EEE) Parts Management and Implementation Plan for the Space Station Program

ALL SSP 30312 Volume 1, Electrical, Electronic, and Electromechanical (EEE) Parts Management and Implementation Plan for the Space Station Program defines four grades for parts with the grades varying from grade 1 for most critical applications to class 4 for the least critical applications. The appropriate grade is to be identified and applied at the initiation or the project or at an early project milestone, such as Systems Requirements Review

(SRR).

Note: SSP 30312 Grade 1 is equivalent to SMC-S-010, Space and Missile Systems Center Standard, Parts, Materials, and Processes Technical Requirements for Space and Launch Vehicles with the exception of SMC-S-010’s Appendix A on radiation. For radiation requirements refer to

JSC 67551.

SSP 41172 Revision AE 01/16/2020

Qualification and Acceptance Environmental Test Requirements

4.2.11, 4.4.4, 5.1.7, 5.1.8, 5.2.3, 6.1.2

SSP 51721 Baseline 10/18/2019

ISS Safety Requirements Document

ALL

SSP 30237 Revision T 01-17-2012

Electromagnetic Emission and Susceptibility Requirements

5.2.2 XEVAS-ENG-02: INTEGRATION AND TEST PLAN

1. DRD Title: Integration and Test Plan

2. DRD No.: xEVAS-ENG-02 3. Data Type: Type 1

4. Solicitation No.: To be filled in by CO at final RFP release

5. Contract No.: To be filled in by CO at award

6. Date Issued: To be filled in by CO at award

7. Date Revised: To be filled in by CO following first revision after award

8. DRD Category:

☒ Technical ☐ Administrative

☐ S&MA

9. Description/Use: To document the Contractor’s system level integration and testing methodologies and processes, including areas proposed for Joint Test with NASA. It documents the detailed integration and testing activities and test reports needed to verify conformance to the technical specifications, demonstrate design requirement compliance and verify end item acceptance.

Contracting Officer Representative, NASA Documentation Repository Representative, Contractor’s Contract Representative, others as negotiated

OPR: EVA Office (JSC-XX).

Initial Submission: Baseline due at Certification Baseline Review (CBR).

Submission Frequency: Baseline update at PDR. Final due at Critical Design Review (CDR).

Update required for currency if the content changes, as needed.

Format: The Contractor’s format is acceptable and in accordance with Section 3.3 Data Format.

Interrelationship: PWS paragraph(s) 2.3.5.3, Training Hardware and Data Provision, 2.5.5, System Analysis and Engineering Evaluations, 2.5.6, Host and Transport Vehicle Integration and Testing, 3.2.5, Milestone 5 – ISS Analog Demonstration and Design Certification Review (DCR), 4.2.5, Milestone 5 – Artemis Analog Demonstration and Design Certification Review (DCR), Attachment J-08 Work Plan, DRD(s) xEVAS-ENG-01, NASA Standards and Specifications Compliance and Tailoring, xEVAS-ENG-03, Verification and Validation (V&V) Plan, xEVAS- ENG-04, Verification Closure Notices (VCNs).

Applicable Documents: CK-WI-28, Flight Operations Directorate (FOD) Safety and Test Readiness Review Process for Ground support Activities at non-NASA Facilities, JPR 1700.1, JSC Safety and Health Plan, NASA/TP-2014-218556, Human Integration Design Processes, xEVAS-SRD-001, xEVAS System Requirement Document

Scope: The Integration and Test Plan addresses the overall integration and test program for the xEVA System, to include all testing to support verification, validation, and certification, procedural development, and on-orbit checkout. The plan encompasses flight hardware, personnel and facilities that are involved in the effort. The Contractor shall ensure that the Integration and Test Plan and the Verification and Validation Plans are consistent and provide a complete set of activities necessary to ensure readiness and to certify the xEVA System.

Contents: The Integration and Test plan shall address the following items:

(a) Overview of Contractor’s Integration and Test Program.

(b) Overall system level test program requirements, objectives, and strategy. This should include overall approach to qualification and acceptance testing per standards tailored in DRD xEVAS-ENG-01, NASA Standards and Specifications Compliance and Tailoring.

(c) Lower level assembly and component test plans.

(d) Test approach, types of tests, pass/fail criteria, decision process, software versions used for the test, and decision points for proceeding to the next test.

(e) Summary of all tests and analyses that is performed at each level, including integrated hardware and software testing.

(f) How integration and test program is managed and staffed including the level of independence of test team.

(g) Schedule for test execution including the location and types of tests for the xEVA System and lower level systems/components.

(h) Description of individual tests to be performed, the test configuration (including ground systems and interfaces), test objectives to include verification and certification requirements, support equipment, special equipment, and all requirements in xEVAS- SRD-001, xEVAS System Requirement Document, by the tests per SMC-S-016, Space and Missile Systems Center Standard Test Requirements for Launch, Upper-Stage and Space Vehicles or approved alternate standard, including Test as you Operate exceptions.

(i) Plan for informing NASA of testing anomalies and mishaps.

(j) Plan for safety protocols during test operations (flight hardware and personnel).

(k) Flight hardware contamination and environmental control requirements, protocols, and implementation.

(l) Flight hardware security requirements, protocols, and implementation.

(m) Requirements for handling deviations, exceptions, omissions, and discrepancies during testing.

(n) Listing of additional plans and procedures written in support of this plan for Contractor-defined key system and subsystem level testing, including but not limited to the following:

(1) Vibration/Acoustic/Shock

(2) Crewed Thermal Vacuum

(3) Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC)

(4) Power Quality

(5) Wear In

(6) Proof/Bust

(7) System Level End-to-End Validation

(8) Functional

(9) System level interfaces to external emulators/simulators.

(o) Transportation plan for all flight hardware moves, including any instrumentation to record environments.

(p) Plan for support equipment certification.

(q) Plan for certification of assembly, integration, and test personnel.

(r) Identification of receivables and deliverables for flight hardware, flight software, flight sequences, ground support equipment, and documentation (baseline).

(s) Process for ensuring that lower level assemblies are ready for integration into the system Joint Integration Verification Test flow (e.g., subsystem acceptance approach).

(t) Integration, test, and handling constraints.

(u) Plans for testing (1) critical sequences; (2) significant operational sequences; and (3) mission scenarios.

(v) Identification of NASA provided ground support equipment (mechanical, electrical) and software needed to verify that the flight system meets all technical requirements.

(w) Identification of Government provided facilities or support needed to verify that the flight system meets all technical requirements.

(x) Human In The Loop (HITL) strategy showing how HITL testing is used during system development to evaluate and improve user interface designs beginning with concept development through verification and certification. Additional information on evaluation methods for usability, workload, and handling qualities found in NASA/TP-2014-218556, Human Integration Design Processes.

(y) The following test events shall occur by the indicated milestones:

(1) Crew Capability Assessment by PDR. The Contractor shall support joint testing and involve multiple NASA approved subjects using a high fidelity prototype of the xEVA System Suit pressure garment system pressurized at intended operating pressure in an appropriate environment (e.g. Neutral Buoyancy Lab (NBL) for micro-g, Active Response Gravity Offload System (ARGOS) or AXES for partial-g) to demonstrate crew capabilities including but not limited to the following:

i. Display and Control Access/Usability

ii. Tool Interface/Use – including APFR ingress for micro-g

iii. Translation(micro-g)/Ambulation (partial-g)

iv. Airlock Egress/Ingress

v. Assessment of Airlock (A/L) Fit with Tools/Equipment and xEVA System Hardware

vi. Transport of Hardware

vii. Assessment of reach and visibility for movement and tasks

viii. Worksite Stabilization (micro-g)

ix. Worksite reach and access for a variety of worksites

x. Crew evaluation of mobility, comfort, and fatigue levels

xi. Self-recovery from fall and tasks while kneeling (partial-g) for CLIN 2A only

xii. Assessment of all CLIN applicable tasks in Attachment A: Mobility Task Matrix

Note: Formal crew consensus requires at least six crewmembers.

(2) Concept of Operations Demonstration by CDR. In support of this review milestone, the Contractor shall demonstrate, using moderate fidelity training hardware, end to end operations from the beginning of EVA preparation, through EVA execution, to the completion of post EVA cleanup.

(3) Task Capability Assessment by CDR. In support of this milestone review for ISS, the Contractor…