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

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

Attachment J-01

Data Requirement Descriptions

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

Attachment J-01 Page 2 xEVAS

Table of Contents

Section Page

1.0 DATA REQUIREMENTS DESCRIPTIONS (DRD)

2.0 ORGANIZATION OF DATA REQUIREMENTS DESCRIPTIONS (DRD) ..6

2.1 DRD NUMBERING

2.2 DATA TYPES

2.3 DATA FIDELITY

3.0 DATA REQUIREMENTS DESCRIPTIONS (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 PROCECURES

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 PLAN

5.2.4 XEVAS-ENG-04: VERIFICATION CLOSURE NOTICES

Attachment J-01 Page 3 xEVAS

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)

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

5.2.10 XEVAS-ENG-10: COMPUTER-AIDED DESIGN (CAD)

MODELS

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

5.4 XEVAS - INFORMATION TECHNOLOGY (IT)

5.4.1 XEVAS-IT-01: INFORMATION TECHNOLOGY (IT) SECURITY

MANAGEMENT PLAN AND IT SECURITY PLAN

5.4.2 XEVAS-IT-02: INFORMATION TECHNOLOGY (IT) CAPITAL

PLANNING AND INVESTMENT CONTROL (CPIC)

5.4.3 XEVAS-IT-03: DATA AND RECORDS MANAGEMENT PLAN

5.5 XEVAS – OPERATIONS (OPS)

5.5.1 XEVAS-OPS-01: INTEGRATED OPERATIONS TRAINING

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

Attachment J-01 Page 4 xEVAS

5.6.4 XEVAS-PC-04: EVA EXCELLENCE DETERMINATION

5.7 XEVAS – PROGRAM MANAGEMENT (PM)

5.7.1 XEVAS-PM-01: PROGRAM MANAGEMENT PLAN

5.7.2 XEVAS-PM-02: INSIGHT & COLLABORATION IMPLEMENTATION

PLAN

5.7.3 XEVAS-PM-03: MISSION INTEGRATION AND OPERATIONS

MANAGEMENT PLAN

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 146

5.7.7 XEVAS-PM-07: IMAGERY PLAN, PRODUCTS AND CATALOG

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-04: REPORTS REQUIRED FOR LOGISTICS

5.8.5 XEVAS-PR-05: ENVIRONMENTAL COMPLIANCE REPORTS

5.8.6 XEVAS-PR-06: SMALL BUSINESS SUBCONTRACTING PLAN AND

REPORTS

5.8.7 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: PROBALILISTIC RISK ASSESSMENT

Attachment J-01 Page 5 xEVAS

1.0 DATA REQUIREMENTS DESCRIPTIONS (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 Program. The records shall be organized in accordance with the instructions in NPR.1441.1, NASA Records Retention Schedules as applicable. The Contractor shall disposition records and non-records in accordance with NPR 1441.1, which has been approved by NASA and the NASA. All questions on records management issues shall be directed through the Contracting Officer to the ISS Records Liaison Officer (RLO) or applicable Program Office

RLO.

Attachment J-01 Page 6 xEVAS

2.0 ORGANIZATION OF DATA REQUIREMENTS DESCRIPTIONS (DRD)

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 (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:

o CLIN 1 = ISS Program EVA Capability o CLIN 2 = Artemis Program EVA Capability o CLIN 3 = Advanced Missions EVA Capability o 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

1 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.

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

3 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.

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 DRL 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 DESCRIPTIONS (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, or Type 3 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 (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 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 Distribution Requirement (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 attach a Delivery Notice (DN) to deliverable notify the Contracting Officer and the Contracting Officer Representative (COR) electronically of DR Delivery.

Attachment J-01 Page 11 xEVAS

DRs listed as requiring updates: 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).

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

(c) Provide the DRDs in an electronic format that is readable, printable, 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.

Attachment J-01 Page 12 xEVAS

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 DRDs shall be provided in an electronic format that meets three basic requirements:

“Readable”, “Printable”, 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 three basic requirements.

3.4 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.

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:

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

Attachment J-01 Page 13 xEVAS

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 PROCECURES

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.

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: OX/External Integration Office

Initial Submission:

Plan: Initial at Proposal.

Audit Results: October 15, 2022

Submission Frequency: As Required

Plan: Annually by October 15 if updates to the plan are made.

Audit Results: Annually by October 15

Format: Contractor format is acceptable.

Interrelationship: NFS 1852.225-70, Export Licenses, SOW 2.2.8, Export Control, xEVAS- PM-01, Program Management Plan, PWS 2.2.8, Export Control, J-08 Work Plan

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

Attachment J-01 Page 16 xEVAS

2190.1, JSC Export Compliance (reference JSC Advisory Implementing Instruction [JAII] 2190.1, Export Services Team (EST) Operations Manual), Program 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: No special instructions.

Maintenance: Any updates to the plan require a resubmission of the plan.

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 & Specifications Compliance & 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.

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: XX Technical Monitor or designee

Initial Submission: Content Item numbers 1 through 5 due with proposal (Attachment A completed to identify the Contractor’s proposed standards and specifications)

Submission Frequency: Baseline due at CBR, Update due at CDR, Final due at DCR (Note:

Updates after DCR are as required).

Format: Content Item numbers 1 through 3 shall be in Microsoft Word or Excel format.

Contractor’s format is acceptable for delivery of standards and additional requested data.

Interrelationship: PWS 2.6.1, Human System Integration, J-08 Work Plan

Applicable Documents: See Attachment B

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:

Attachment J-01 Page 18 xEVAS

Specific content includes:

1) The Contractor shall identify in Attachment A each instance in which it is proposing to use 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 completed to define the Contractor’s standards and specifications to be applied to the development of the xEVA systems.

2) 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; the process for creating and maintaining internal company standards.

3) 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.

4) 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.

5) 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.

6) 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.

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

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

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.