Attachment_02,_Data_Requirements_Descriptions.pdf

Attachment 02

Gateway Logistics Services

Data Requirements Descriptions

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

ATTACHMENT 02 DATA REQUIREMENTS DESCRIPTIONS (DRDs)

1.0 DATA REQUIREMENTS LIST (DRL) DESCRIPTION

The DRL provides the Data Requirements Descriptions (DRD) number, title, data type, submittal frequency, and reference information for each data deliverable item.

The DRL identifies critical elements of the contracted effort where NASA requires aspects of mission integration insight and approval. The DRL defines the scope of documentation required; however, NASA will use the Contractor’s existing documentation to the extent practical. Where there is not a direct match between a DRD item and the Contractor’s standard documentation, the Contractor’s documentation will be acceptable provided it contains equivalent data requirements.

2.0 ORGANIZATION OF DATA REQUIREMENTS LIST (DRL)

2.1 DRD Number

For the purpose of classification and control, the individual data deliverables in the DRL are grouped into the following categories:

0XX series DRDs are applicable to all contract activities

1XX series DRDs are applicable to CLIN 1 tasks only

2XX series DRDs are applicable to CLIN 2 tasks only

2.2 Data Types

The types of data and their contractually applicable requirements for approval and delivery after contract award are:

TYPE DESCRIPTION

1 Type 1 DRDs are provided for NASA’s review and approval.

2 Type 2 documents are provided for review only and do not require NASA approval;

however, the DRD must satisfy all applicable contractual requirements.

For Type 1 DRDs, if the Contractor has not been notified of disapproval within 30 days, the DRD shall be considered approved.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

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. Date of Current Version: Date of most recent version of the DRD in effect

3a. DRD No.: Unique identifier for the DRD

3b. DRD Type: Type 1 Approve or Type 2 Review

4. DRD Use: The purpose of and NASA’s intended use for the data.

5. DRD Category: Technical, Administrative, or S&MA

6. References: SOW, Clause, etc.

7. Interrelationships: Relationship to other DRDs

8. Preparation Information: Description/Purpose, Data Requirements, and Format of the DRD

9. OPR: NASA Responsible Organization

10. Submission Date and Frequency: Date of initial submittal and subsequent submittal frequency

11. DRD Maintenance: Special instructions for DRD maintenance, as required

12. Copies/Distribution: No of copies required and distribution list of recipients

13. Remarks: This field provides additional submittal information, if necessary

DRD initial and recurring deliveries shall occur per Tables A2-1, A2-2, and A2-3.

DRDs shall be maintained electronically in the Contractor’s preferred format unless a specified format is defined in the DRD. All electronic DRDs shall be submitted to the Gateway Program Repository. The

Contractor shall notify the Contracting Officer electronically of the DRD delivery. 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.

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

4.0 DATA TRANSMITTAL AND FORMAT

DRDs shall be transmitted to NASA electronically, via hardcopy, or by other mechanism agreed to by the

Contracting Officer. The Contractor shall notify the Contracting Officer and the Contracting Officer

Representative (COR) in writing of DRD delivery.

Electronic Format

The DRDs shall be provided in an electronic format that is readable, printable, and downloadable by

NASA using publicly available off-the-shelf software.

5.0 DRD MAINTENANCE PROCECURES

The DRL shall be maintained throughout the performance of the contract.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

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

5.2 Reference to Other Documents and DRDs in Data Submittals

The Contractor’s submittal of a DRD may make reference 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.

5.3 Additional Information Regarding Type 1 and Type 2 DRD Submittals

All Type 1 submittals shall be marked as “Pending NASA Approval”, and once approved shall be delivered and marked as “Approved by NASA”. Type 1 DRDs shall be updated and delivered 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.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

TABLE A2-1 DRDs REQUIRED FOR ALL CLINs

Item Document Type Initial Due Date Recurrence Reference

GLS-001 Integrated Master

Schedule (IMS)

2 Preliminary with proposal

Baseline at

ATP+90D,

Updates monthly, Each mission

GLS-002 Mission Success Criteria

& Determination

Methodology

1 NLT L-4M As changed, GLS-003 Mission Integration and

Operations Management

Plan (MIOMP)

1 Draft with proposal

Baseline at SRR, Update as changed

GLS-004 Safety and Mission

Assurance Plan(s)

1 With proposal When updated

GLS-005 Mishap Notification, Investigation and Mishap

Preparedness, and

Contingency Plan

2 ATP+60D When updated

GLS-006 Safety Data Package

(SDP)

1 See DRD See DRD

GLS-007 Orbital Debris Assessment and End of Mission Plan

1 See DRD See DRD

GLS-008 Safety Documentation

Required by Non-NASA

Entities

2 When requested by NASA

When requested by NASA

GLS-009 Safety Documentation

Required for Processing in

NASA Provided Facilities

1 When requested by NASA

When requested by NASA

GLS-010 Alternatives to NASA

Standards and

Specifications

2 Items 1-3 with proposal

Baseline at

ATP+60D,

Update at CDR, Final at SCR

GLS-011 Mass Properties Data 2 L-18M See DRD

GLS-012 Verification & Validation

Plan

1 Draft at SRR Baseline at PDR, Final CDR, Update A/R at

VBR,

GLS-013 Information Technology

(IT) Security Management

Plan

1 ATP+30D Update annually, as required

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

TABLE A2-1 DRDs REQUIRED FOR ALL CLINs

GLS-014 Information Technology

(IT) System Security

Documents (ITSSDs)

1 ATP+30D Update annually, as required

GLS-015 Technical Imagery Plan 1 L-6M See DRD

GLS-016 Post Arrival Assessment 2 Docking+2W Each mission

GLS-017 Post Departure

Assessment

2 Departure from

Gateway+2W

GLS-018 Post Mission Report 2 EOM+60D Each mission

TABLE A2-2 DRDs REQUIRED FOR CLIN 1 ONLY

GLS-101 Common Configuration

Integration Milestone

Reviews Documentation

1 SRR-1W Each review-1W, GLS-102 Mission Technical

Reviews Documentation

2 VBR-1W Each review-1W, GLS-103 Vehicle Interface

Definition Document

(IDD)

1 Draft at PDR Baseline at CDR, Update A/R at

VBR/MIR,

As needed for subsequent missions

GLS-104 Pressurized Cargo

Interface Control

Document (ICD), Interface Control

Agreement (ICA), or

Stowage Integration

Agreement (SIA)

1 Draft at VBR Final at scheduled Cargo

Turnover-30D, and each mission for new cargo items and changes from previous mission

GLS-105 Unpressurized Cargo

Interface Control

Document (ICD)

1 Template at

VBR

Draft at

L-18M, Update at

L-14M, Final at L-10M, Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

TABLE A2-2 DRDs REQUIRED FOR CLIN 1 ONLY

GLS-106 Mission Resource

Allocation Document

(MRAD)

1 Initial at L-10M Update at L-3M, Final at L-1M, GLS-107 Engineering Computer-

Aided Design (CAD)

Models

2 See DRD See DRD

GLS-108 Launch Vehicle Flight

Software Input for IV&V

2 At VBR Updates only, at mission VBRs

GLS-109 Launch Vehicle Guidance, Navigation and Controls

Input for IV&V

2 At VBR Updates only, at

GLS-110 Launch Vehicle Key

Systems Qualification and

Acceptance Data

2 At VBR Updates only, at

TABLE A2-3 DRDs REQUIRED FOR CLIN 2 ONLY

GLS-201 Specialized Missions

Management, Technical and Integration Formal

Reviews

1 Initial review-

1W

Each review-1W, GLS-202 Vehicle/Element Interface

Control Document (ICD)

1 Preliminary at

ATP+6M

Baseline at

L-24M, Final at SAR, As required, GLS-203 Vehicle/Element ICD

Requirements Verification

Matrix

1 At Preliminary

ICD

approval+3M

As required and with each ICD revision, GLS-204 Vehicle Data Package 2 ATP+6M As changed, GLS-205 Mission Specific

Drawings

1 See DRD As changed, GLS-206 Vehicle/Element

Integrated Procedures

1 Draft at Final at Test-1W, Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

Test-45D for each integrated test

GLS-207 Mission Specific

Hardware Test Plan

2 At MSCDR As changed, GLS-208 Mission Specific

Hardware Test Report

2 Test

Complete+30D

Each test, GLS-209 Reserved

GLS-210 Performance and

Guidance Accuracy

Analysis (PGAA)

I – 2

U/F – 1

Initial at

ATP+6M

Update at L-12M, Final at L-6M, GLS-211 Final Mission Analysis

(FMA)

2 Receipt of

Element

Data+60D

GLS-212 Element/Expended Stage

Separation Analysis

2 Initial at

MSPDR

Final at SAR, GLS-213 Payload Fairing Venting

Analysis

2 Receipt of

Element

Data+60D

GLS-214 Payload Fairing Clearance

2 Initial at Receipt of Model+60D

Update at

MSPDR,

Final at MSCDR, GLS-215 Vehicle Pre-Flight

Controls and Stability

Analysis

2 L-18M As required, GLS-216 Coupled Dynamic Loads

2 Receipt of

Element

Model+3M

Update at L-15M, Final at L-26W, GLS-217 Vehicle Integrated

Thermal Analysis

2 L-24M As required, GLS-218 RF Link Analysis 2 L-12M As required, GLS-219 Element/Vehicle EMC, RF, and EED

Compatibility Analysis

2 See DRD As changed, GLS-220 Mission Specific Software 2 Preliminary at

MSPDR

Final at L-45D, Update as required, Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-221 Vehicle and GSE

Telemetry Formats

2 Test+1D At FRR, Launch+1W, GLS-222 Vehicle and GSE

Telemetry (test, pre-launch, and launch)

2 Test+1D At FRR, Launch+1W, GLS-223 Vehicle Space Charging and Single Event Effects

Analysis

2 Initial at L-24M Final at L-6M, Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-001

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Integrated Master Schedule (IMS)

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-001

3b. DRD Type

Type 2: Review

4. Use (Define need for, intended use of, and/or anticipated results of data)

See description/purpose.

5. DRD Category

☐ Technical

☒ Administrative

☐ S&MA

6. References (SOW, Clause, etc.)

SOW 3.2, 3.9

7. Interrelationships (e.g., with other DRDs)

DRDs GLS-003, GLS-012, GLS-102

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

To provide NASA the Contractor’s integrated project schedule using established standard processes, data structures and reporting conventions to plan, manage, and report the work required in the performance of this contract. This schedule will be used to provide management insight into contract status, verify attainability of contract objectives and requirements, and evaluate progress.

Schedule consistency as used in this DRD is defined as the degree to which the Contractor uses standardized scheduling approaches between similar processing activities and flows. Accurate scheduling as used in this DRD is defined as the accurate representation of work content and tasks duration

(predicted vs. actuals). A stable schedule as used in this DRD refers to the degree to which daily schedule changes are minimized and limited to unforeseen hardware or software problems or NASA-directed changes.

DATA REQUIREMENTS:

(a) The IMS shall include all tasks necessary to accomplish the total scope of work defined in the RFP, SOW, DRDs, and other contract requirements.

(b) The entire scope of work shall be broken into schedule tasks and milestones at a consistent level of detail to allow discrete progress measurement and visibility into the overall development, fabrication, integration, assembly, test, and delivery phase of each end item deliverable.

(c) All schedule tasks/milestones shall be integrated with the appropriate sequence relationships to clearly depict the interrelationships and constraints among related tasks, provide a total end-to-end logic network leading to each end item delivery, and provide vertical traceability from detailed tasks to higher level project milestones.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-001

(d) The IMS shall include a top-level, Gantt-type summary that reflects all contract and controlled milestones, major project phases (e.g., design, fabrication, assembly, test, launch, transit, GW integration, disposal), and all end item deliveries.

(e) The scheduling approach shall ensure a consistent, accurate, and stable IMS that provides for the identification, coordination, sequencing, control, implementation and tracking of all required activities.

(f) The approach shall provide the ability to fully identify, analyze, mitigate and control scheduling risks and impacts; accurately identify and analyze critical path activities; and allow its users to easily measure the progress towards achieving the intended plan.

(g) The IMS shall reflect both the project approved time-phased plan (including all subsequent approved changes), and the time-phased plan with its current task progress, sequence, and forecasts.

(h) The IMS shall identify primary and secondary critical path, schedule margin, and dependencies and relationships among tasks, and the requirements commitment from all interfacing organizations.

(i) The IMS shall clearly identify tasks or activities which have a dependency on a NASA delivery or approval (for example, delivery of a GFE item) and shall distinguish tasks or activities which are conducted jointly with NASA.

(j) Tasks and milestones from major subcontractors and the commercial launch vehicle provider shall be included with sufficient detail to develop a realistic critical path. Their data shall be consistent, statused monthly, and based on the same next-higher level need date to enable a realistic critical path.

(k) The IMS shall also include Gateway integration milestones and Gateway integration verification closures.

(l) The IMS shall be formatted with the largest increment of time being measured in units of months.

(m) Along with the IMS monthly deliverables, the Contractor shall provide a brief description of any significant schedule variances or slips since the last month, the root cause of those slips, impacts to the critical path (if any), and options for recovery of that time in the remaining work left on the schedule. The Contractor shall also track the status of previously reported variances or slips and the progress made to resolve them. Any other variances or slips that are of concern to the Contractor and/or have potential to impact the critical path in the future should also be reported at the discretion of the Contractor.

FORMAT: The Preliminary IMS with proposal shall be in the format defined in the solicitation.

Baseline IMS and subsequent updates shall be in native file format using Microsoft Project or alternate schedule management software approved by NASA. A legend identifying the contractor’s schedule symbols used and their meaning shall also be provided..

9. OPR: NASA Contracting Officer Representative

10. FIRST SUBMISSION DATE: Preliminary with proposal

Additional Submissions: Baseline at ATP+90D, updates monthly, and for each mission

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-001

11. MAINTENANCE: N/A

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA

Contracting Officer Representative, NASA GW Logistics Element Manager, NASA Launch

Services Program (LSP), NASA GW Documentation Repository Representative, Contractor’s

Contract Representative, others as negotiated

13. REMARKS:

The Contractor is encouraged to use modern manufacturing resource planning, industrial engineering techniques and other approaches to ensure schedule stability, accuracy, reliability, predictability, and achievability.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-002

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Mission Success Criteria &

Determination Methodology

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-002

Type 1: Approval

☒ Technical

☐ Administrative

☐ S&MA

6. References (SOW, Clause, etc.)

Clause 2.2.17

7. Interrelationships (e.g., with other DRDs)

DRDs GLS-016, GLS-017, GLS-018, GLS-

102, GLS-103, GLS-104, GLS-105, GLS-222

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

This data item proposes the criteria and methodology to support the Contracting Officer’s determination of mission success

DATA REQUIREMENTS:

(a) A list of proposed criteria to be used to determine the success of the mission. These criteria shall be based on applicable flight related ICD requirements as defined in DRDs GLS-104, Pressurized Cargo

Interface Control Document (ICD), Interface Control Agreement (ICA), or Stowage Integration

Agreement (SIA), GLS-105, Unpressurized Cargo Interface Control Document (ICD), and/or GLS-

103, Vehicle Interface Definition Document (IDD), for CLIN 1 missions; and DRD GLS-202, Vehicle/Element Interface Control Document (ICD), for CLIN 2 missions.

(b) The Contractor’s proposed methods, including required vehicle telemetry measurements, ground observation, and analysis/reconstruction techniques, for verifying that each proposed mission success criterion is satisfied. Allowances for sensor measurement accuracy shall be explicitly identified and justified.

FORMAT: Contractor’s preferred format.

9. OPR: NASA Contracting Officer Representative

10. FIRST SUBMISSION DATE: NLT L-4M

Additional Submissions: As changed, and for each mission

11. MAINTENANCE: N/A

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-002

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA

Contracting Officer Representative, NASA GW Logistics Element Manager, NASA Launch

Services Program (LSP), NASA GW Documentation Repository Representative, Contractor’s

Contract Representative, others as negotiated

13. REMARKS:

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-003

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Mission Integration and Operations

Management Plan (MIOMP)

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-003

☐ Administrative

☐ S&MA

6. References (SOW, Clause, etc.)

SOW 3.3, 3.5.1, 3.5.4, 4.2.1, 4.2.1.2, 4.2.1.2.1, 4.6

7. Interrelationships (e.g., with other DRDs)

DRDs GLS-001, GLS-104, GLS-105

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

To define the various operations and processes, product delivery templates, and organizational interfaces necessary for the Contractor to implement the Integration and Operations (I&O) activities required for the

Contractor’s logistics supply missions.

DATA REQUIREMENTS:

This DRD covers the end-to-end array of principal functions carried out by the Contractor in the performance of contract I&O responsibilities, including:

(a) Cargo capabilities, including:

(1) Standard cargo turnover schedule and location for pressurized cargo

(2) Standard cargo turnover schedule and location for unpressurized cargo

(3) Late stow pressurized cargo capacity and turnover schedule and location

(4) Powered cargo capacity and turnover schedule and location

(b) Cargo manifesting, integration support, and schedules in accordance with DRD GLS-001, Integrated

Master Schedule (IMS)

(c) Contractor to Gateway Program Mission Integration support

(d) Vehicle flight operations documentation preparation

(e) Vehicle and unpressurized systems operations training

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-003

(f) Simulations and mission operations support using JSC 35089, Visiting Vehicle Operations Document as a guide for the type and level of joint-planning and coordination required to execute the logistics service

(g) Ground facility interfaces

(h) Data Management

The Contractor will keep this document current with established processes, schedules, interfaces, and vehicle design modifications throughout the contract period of performance. The document shall contain integrated text and graphics as required to describe and/or illustrate the various aspects of services provided, including process descriptions, schedule flows, facility and tool illustrations, organizational hierarchies, etc.

The main body of this document shall be non-proprietary in nature and available for dissemination among the GW Program. Any proprietary information may be included in appendices and access-controlled separately.

The following information shall be included under the corresponding principal function material:

1) Cargo Capabilities:

Define the Contractor’s cargo capability and schedule flexibility in the following table:

Cargo Capabilities Table

Cargo Type Maximum

Volume

Maximum

Mass

Turnover

Schedule

Standard Pressurized m3 kg L-months

Standard Unpressurized m3 kg L-months

Late Stow m3 kg L-days

Powered Cargo m3 kg L-days

The contractor may also choose to use additional graphics, tables, or other means to best describe their stowage capabilities and trash accommodations concepts for both launch and on-orbit configurations

2) Cargo Manifesting and Integration Support:

Presents a functional breakdown and description of how the Contractor works with the GW Program

Office, the COR, and hardware developers to establish a mission manifest within the capability of the vehicle and identify candidate non-NASA cargo. The processes shall include the collection and documentation of pertinent technical and operational data, establish mission manifests, perform analyses, and physically integrate cargo and perform stowage retrieval and restow operations, and trash stowage operations, for both the pressurized volume or the unpressurized carrier of the logistics vehicle for loading/installation and on-orbit operations scenarios.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-003

3) Mission Integration Support:

Presents a functional breakdown and description of how the Contractor interfaces with the GW Program

Office to ensure the timely provision of data to support the associated development of GW mission integration documentation, and to provide the necessary data for GW to determine pre-mission status and flight readiness.

4) Mission Operations Process and Products:

Presents a functional breakdown and description of how the Contractor manages the processes and products, using JSC 35089, Visiting Vehicle Operations Document as a guide, for the vehicle and cargo flown in the logistics vehicle pressurized module or unpressurized carrier. This includes Contractor procedures development, control, validation, and publication.

5) Vehicle Systems and Commercial Payload Operations Training:

Presents a functional breakdown and description of how the Contractor manages the logistics vehicle and unpressurized carrier systems cargo and payload training for the various NASA flight crews, console operators, and simulator instructors. This includes the approach to (1) development of training plans, study materials, and hardware and software aids; (2) development of training requirements and schedules;

and (3) development and utilization of training mockups.

6) Equipment Interface Demonstration and Payload Compatibility Testing:

Presents the approach to scheduling, conducting and documenting results of Equipment Interface

Demonstrations and Payload Compatibility Testing.

7) Ground Facility Utilization:

Presents a functional breakdown and description of the Contractor’s approach to the utilization of (or support to the NASA utilization of) major Government and Contractor facilities during the preparation, and execution of logistics mission operations.

8) Data Management:

Presents a functional breakdown and description of how the Contractor manages the logistics vehicle command and data. This includes the approach to development of vehicle, cargo and payload data requirements (including requirements for data processing, storage, and distribution), coordination of the method(s) by which this data is integrated into the standard GW communication and data services, establishment of interfaces with NASA and non-NASA components of the space-to-ground communications network, coordination of the Contractor’s data management plan with NASA.

FORMAT: Contractor’s preferred format except as noted above

9. OPR: NASA GW Logistics Element Manager

10. FIRST SUBMISSION DATE: Draft with proposal

Additional Submissions: Baseline at SRR, Update as changed to maintain current

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-003

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA

Contracting Officer Representative, NASA GW Logistics Element Manager, NASA Launch

Services Program (LSP), NASA GW Documentation Repository Representative, Contractor’s

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-004

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Safety and Mission Assurance Plan(s)

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-004

☐ Administrative

☒ S&MA

6. References (SOW, Clause, etc.)

SOW 3.7.1.1, 3.7.2, 3.7.3, 3.7.5, NASA FAR Supplement

1852.223-73

7. Interrelationships (e.g., with other DRDs)

DRDs GLS-012, GLS-108, GLS-109

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

Detailed S&MA Plans are required to show how the Contractor will implement Safety, Quality, Reliability and Software S&MA for Gateway Logistics Missions. The intent is for the Contractor to use existing corporate S&MA plans to the greatest extent practical and identify areas where Gateway and

Logistics mission requirements necessitate policies, practices, and procedures in addition to corporate

S&MA plans.

DATA REQUIREMENTS:

The Contractor shall provide their corporate S&MA Plans applicable to this contract related to Safety, Quality, Reliability, and Software. S&MA Plans shall demonstrate Safety and Mission Assurance is incorporated into all phases of the logistics service lifecycle and use DSG-RQMT-010, Gateway Safety and Mission Assurance Requirements, as a guide. If implementation of the Gateway Logistics Services contract requires S&MA Plans/Processes in addition to corporate S&MA Plans, those may be provided in this DRD as a supplement.

Plans may consist of a single S&MA plan or multiple plans that address the S&MA discipline areas described in this DRD.

The S&MA plan(s) shall be accompanied with a contents summary identifying where in the plan the specific items listed in the SOW and this DRD are addressed. This DRD shall be resubmitted when changes to

S&MA Plans are made.

Safety and Health

The Contractor shall provide a Safety and Health Plan in accordance with NASA FAR Supplement

1852.223-73.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-004

The Contractor’s Safety and Health Plan shall also describe the process for assuring the safety and health of the public, personnel, crew, Gateway, and facilities/property. The plan should include detailed discussions of the policies, procedures, and techniques for all anticipated working conditions that will be encountered throughout the performance of the contract.

This Plan shall describe the Safety organization including structure of management interfaces and system safety methods employed to ensure compliance with applicable Gateway and launch processing site safety requirements.

The Contractor’s plan shall describe the approach to be taken to document its safety and health program performance and provide necessary visibility and insight into activities that could affect NASA employees or property.

System Safety

The System Safety plan shall describe a system for managing safety risks by identifying, characterizing, communicating, and mitigating hazards to eliminate, reduce, or control the risk. The System Safety plan shall describe the process for acceptance of residual risk.

The Contractor’s System Safety plan shall also describe the approach to the Safety Review Process and

Hazard Analysis. The Contractor’s plan shall describe the approach to identify hazards and eliminate or control them. For hazardous operations, the Contractor’s plan shall describe policies and procedures for the management and implementation of hazardous operating procedures.

Quality Plan

The Contractor’s Quality plan shall describe the Contractor’s internal quality requirements, Quality organization including structure of management interfaces, and quality methods employed to ensure product and service quality.

At a minimum, the Contractor’s quality plan shall describe their approach to:

1. AS9100 Compliance

2. Subcontractor/Provider/Vendor Quality

3. Critical Item Identification and Data Requirements

4. Quality Workmanship Standards to be used

5. Metrology and Calibration

6. Foreign Object Debris Control

7. EEE Parts Control

8. Electrostatic Discharge Control

9. Limited Life Items

The Provider’s plan shall address how the requirements in SOW Paragraph 3.7.2 will be met to provide

NASA audit schedules, audit reports, and As Build Configuration Lists for the Logistics vehicle.

Reliability Plan

The Contractor’s Reliability Plan shall describe the Contractor’s approach to incorporating reliability into the entire lifecycle of the logistics service. The Reliability Plan shall also describe techniques and methods

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-004

that will be used to develop and maintain a reliable Logistics Service and meet quantitative reliability requirements.

The Contractor’s Reliability plan shall describe the approach to Failure Modes and Effects Analysis/Critical

Items List for the logistics vehicle within the Gateway Rendezvous Sphere through Disposal.

Software SMA Plan

The Contractor’s Software S&MA Plan (SSMAP) shall describe the Safety, Quality Assurance, Reliability, Verification and Validation, Independent Verification and Validation, Certification, and

Configuration Management activities for all computer software programs including the software portion of the firmware and complex electronic devices. The Contractor shall describe an approach to safety critical software in accordance with NASA-STD-8719.13C, NASA Software Safety Standard. The

Contractor’s SSMAP shall also describe implementation of a Software Quality Management System in accordance with AS9115, Quality Management Systems – Requirements for Aviation, Space and Defense

Organizations - Deliverable Software (Supplement to AS9100) and an IEEE 730-2014, Standard for

Software Quality Assurance Processes, compliant Software Assurance Plan. The Contractor’s software assurance plan shall use NASA-STD-8739.8 section 6, 7.1, 7.2, 7.3, 7.4, and 7.5 as a guide.

These SSMAP activities shall provide evaluations of the software lifecycle, including patches and updates, and assess the resulting software and associated documentation to assure compliance with

Contractor requirements and applicable software development plans, as well as, conformance to software safety and software assurance requirements.

The SSMAP activities shall also assure standards and procedural controls are established and implemented; audits, evaluations, and reviews are accomplished; procedures are followed; and all assurance activities are performed as scheduled.

The SSMAP shall address Verification and Validation (V&V), and show how Contractor Software

Assurance will collect and maintain records during the V&V efforts and provide objective evidence to

NASA. The Contractor’s SSMAP shall ensure verification and validation activities satisfy functional, performance, and other requirements and that each phase of the development process has been performed and yields the right products.

The Contractor’s plan shall ensure products requiring certification in accordance with Contractor software development plan meet the following prerequisites:

1. Verification the products were developed and supported according to an approved process.

2. Verification all software products are present, complete, current and controlled and no open nonconformances exist which are safety or mission critical.

3. Validation the software products meet all of the appropriate requirements including safety and reliability requirements.

4. Validation the software products meet the requirements contained in a joint integration verification and test plan.

The Contractor’s SSMAP shall address if third-party IV&V is to be performed for GLS missions, and if so provide a description of what IV&V is planned.

FORMAT: Contractor’s preferred format.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-004

9. OPR: NASA Safety and Mission Assurance

10. FIRST SUBMISSION DATE: With proposal

Additional Submissions: When updated

11. MAINTENANCE: N/A

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA

Contracting Officer Representative, NASA GW Logistics Element Manager, NASA Launch

Services Program (LSP), NASA GW Documentation Repository Representative, Contractor’s

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-005

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Mishap Notification, Investigation and Mishap Preparedness, and

Contingency Plan

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-005

☐ Administrative

☒ S&MA

6. References (SOW, Clause, etc.)

SOW 3.7.1

7. Interrelationships (e.g., with other DRDs)

DRDs GLS-008, GLS-009, GLS-017, and

GLS-018

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

To provide NASA with an understanding of the Contractor’s processes notifying NASA of mishaps, as well as how the Contractor plans to investigate and establish corrective action plans for mishaps that occur while performing the work required in support of this SOW. Contractor employees on NASA-owned property, custodians of NASA assets elsewhere to the extent those assets are involved, or contactors involved in

NASA-owned payload or cargo to logistics vehicle integrating operations, or contractors involved in integrated Gateway operations shall report mishaps or close calls.

DATA REQUIREMENTS:

1. GENERAL: Mishap reporting, investigation and corrective action requirements differ according to whether the specific mishap occurs on NASA property. Mishaps occurring on third party property will be handled in the same manner as those occurring on Contractor property.

2. NASA MISHAP: An unplanned event that results in at least one of the following:

a) Injury to non-NASA personnel, caused by NASA operations.

b) Damage to public or private property (including foreign property), caused by NASA operations

c) Occupational injury or occupational illness to NASA personnel.

d) NASA mission failure before the scheduled completion of the planned primary mission.

e) Destruction of, or damage to, NASA property except for a malfunction or failure of component parts that are normally subject to fair wear and tear and have a fixed useful life that is less that the fixed useful life of the complete system or unit of equipment, provided that the following are true: 1) there was adequate preventative maintenance; and 2) the malfunction or failure was the only damage and the sole action is to replace or repair that component.

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-005

2.1 Mishap classification shall occur as documented in NPR 8621.1C, NASA Procedural

Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping.

3. ONSITE MISHAPS OCCURRING ON NASA PROPERTY:

3.1 Immediate Notification and Reporting of Mishaps Occurring on NASA Property.

a) Mishap Reporting. The Contractor shall notify the local safety office in accordance with local reporting requirements for all Type A or B injury and/or property damage mishaps occurring on NASA property while performing work in support of this SOW.

b) Emergency Reporting. All onsite emergencies, immediately notify both emergency response

(e.g., 911, fire, ambulance, Center security office) and a supervisor, management official, or a safety/health staff member of the circumstance of the mishap in accordance with the local emergency reporting requirements. The Contractor shall ensure that contract employees on NASA property know and comply with local safety, health and emergency response requirements. The Contractor’s plan shall describe the processes required to accomplish this task.

4. MISHAPS OCCURRING ON CONTRACTOR PROPERTY, THIRD PARTY PROPERTY OR

OTHER NON-NASA GOVERNMENT PROPERTY:

4.1. Immediate notification and reporting of mishaps occurring on Contractor property, Third Party property or other non-NASA Government Property. The Contractor shall immediately notify KSC Safety

Office in the event of a Type A or B mishap occurs to NASA personnel or property while on Contractor, third party property or other non-NASA government property. The Contractor’s plan describe the process through which notification will take place.

4.2. Mishap investigation and corrective action for mishaps on Contractor property, Third Party property, or other non-NASA Government Property.

a) An initial investigation by the Contractor is required for all mishaps which have been reported to

NASA. NASA reserves discretionary authority to investigate mishaps which involve NASA personnel or resources regardless of location. The Contractor has the discretion to perform any collateral investigations. However, investigations implemented by NASA will take priority with regard to access to evidence, data, and witnesses. The proceedings of NASA investigations will remain confidential. The

Contractor will have an opportunity to comment on the investigation report in accordance with NASA protocols.

b) Contractor Final Report. After the Contractor completes its investigation of the mishap and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 15 days of completion. This plan will include any verification activities identified by the Contractor to ensure that corrective actions to be implemented by NASA or a third party have been implemented or, if applicable, accomplished.

5. MISHAPS OCCURRING POST LAUNCH AND PRIOR TO INTEGRATED OPERATIONS

5.1. Immediate notification and reporting of mishaps occurring post launch and prior to integrated operations. The Contractor shall immediately notify KSC Safety Office in the event of a Type A or B

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-005

mishap occurs to NASA personnel or property post launch and prior to integrated operations. The

Contractor’s plan describe the process through which notification will take place.

5.2. Mishap Investigation and Corrective Action for Mishaps Occurring Post Launch and Prior to

Integrated Operations.

a) An initial investigation by the Contractor is required for all mishaps which have been reported to

NASA. NASA reserves discretionary authority to investigate mishaps which involve NASA personnel or resources regardless of location. The Contractor has the discretion to perform any collateral investigations. However, investigations implemented by NASA will take priority with regard to access to evidence, data, and witnesses. The proceedings of NASA investigations will remain confidential. The

Contractor will have an opportunity to comment on the investigation report in accordance with NASA protocols.

b) Contractor Final Report. After the Contractor completes its investigation of the mishap and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 15 days of completion. This plan will include any verification activities identified by the Contractor to ensure that corrective actions to be implemented by NASA or a third party have been implemented or, if applicable, accomplished.

6. MISHAPS OCCURRING DURING INTEGRATED OPERATIONS:

6.1 Immediate notification and reporting of mishaps occurring during integrated operations shall follow guidelines and requirements as documented in DSG-PLAN-XXX (TBD), Gateway Mishap Preparedness and Contingency Plan, using NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call

Reporting, Investigating, and Recordkeeping, as a guideline.

6.2 All GLS mishaps occurring during integrated operations will be considered NASA Mishaps, specifically Gateway Program Mishap.

a) Mishap investigation and corrective action shall be performed per DSG-PLAN-XXX (TBD), using NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping as a guideline. The Contractor has the discretion to perform any collateral investigations. However, investigations implemented by NASA will take priority with regard to access to evidence, data, and witnesses. The proceedings of NASA investigations will remain confidential. The

Contractor will have an opportunity to comment on the investigation report in accordance with NASA protocols.

b) Contractor Final Report. After the Contractor completes its investigation of the mishap and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 15 days of completion. This plan will include any verification activities identified by the Contractor to ensure that corrective actions to be implemented by NASA or a third party have been implemented or, if applicable, accomplished.

7. MISHAPS OCCURRING AFTER INTEGRATED OPERATIONS:

7.1 Immediate notification and reporting of mishaps occurring after integrated operations. The

Contractor shall immediately notify KSC Safety Office in the event of a Type A or B mishap occurs to

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-005

NASA personnel or property after integrated operations. The Contractor’s plan describe the process through which notification will take place.

7.2 Mishap investigation and corrective action for mishap occurring after integrated operations.

a) An initial investigation by the Contractor is required for all mishaps which have been reported to

NASA. NASA reserves discretionary authority to investigate mishaps which involve NASA personnel or resources regardless of location. The Contractor has the discretion to perform any collateral investigations. However, investigations implemented by NASA will take priority with regard to access to evidence, data, and witnesses. The proceedings of NASA investigations will remain confidential. The

Contractor will have an opportunity to comment on the investigation report in accordance with NASA protocols.

b) Contractor Final Report. After the Contractor completes its investigation of the mishap and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 15 days of completion. This plan will include any verification activities identified by the

Contractor to ensure that corrective actions to be implemented by NASA or a third party have been implemented or, if applicable, accomplished.

FORMAT: Contractor’s preferred format.

9. OPR: NASA Safety and Mission Assurance

10. FIRST SUBMISSION DATE: ATP+60D

Additional Submissions: When updated

11. MAINTENANCE: N/A

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: NASA Contracting Officer, NASA

Contracting Officer Representative, NASA GW Logistics Element Manager, NASA Launch

Services Program (LSP), NASA GW Documentation Repository Representative, Contractor’s

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-006

DATA REQUIREMENTS DESCRIPTION

1. DRD Title:

Safety Data Package (SDP)

2. Date of Current Version

8/6/19

3a. DRD No.

GLS-006

The Gateway Logistics Element S&MA will use the Safety Data Package to assess the design and operations for compliance with Safety and Mission

Assurance requirements and overall level of risk.

☐ Administrative

☒ S&MA

6. References (SOW, Clause, etc.)

SOW 3.7.1.2, 3.7.1.4, 3.7.3, 3.7.4

7. Interrelationships (e.g., with other DRDs)

DRD GLS-101, GLS-102, GLS-204

8. PREPARATION INFORMATION: The contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

The Contractor shall submit a Safety Data Package at each phase of the safety review process detailed in the tailored DSG-RQMT-011, Gateway Program Hazard Analysis Requirements. Reliability Analysis and

Failure Modes and Effects Analysis/Critical Items List shall be included as part of the Safety Data

Package as described in the body of this DRD. Where conflicts between this DRD and the tailored DSG-

RQMT-011 exist, the tailored DSG-RQMT-011 shall take precedence.

DATA REQUIREMENTS:

(a) Scope of Analyses

(1) Failure Modes and Effects Analysis / Critical Items List (FMEA/CIL). Documentation of this analysis shall be provided for the logistics vehicle within the Gateway Rendezvous

Sphere through Disposal.

(2) Reliability Analysis. This analysis shall document the reliability of the logistics vehicle, excluding the launch vehicle.

(3) System Safety Analysis Report (SSAR), including Hazard Reports. This report shall document the Hazard Analyses performed for the logistics vehicle within the Gateway

Rendezvous Sphere.

(b) Analytical Methods and Requirements

(1) Failure Modes and Effects Analysis / Critical Items List (FMEA/CIL). This analysis shall include the following at a minimum: a summary of the analysis methodology, a list of ground rules and assumptions, FMEA work sheets, and CIL with retention rationale. For critical item retention rationale requiring inspection verification, the Contractor shall reference the work-authorizing document that implements the inspection. This analysis may

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-006

be developed using the Contractor’s existing FMEA/CIL methodologies or using DSG-

RQMT-012, Gateway Program Failure Modes and Effects Analysis/Critical Items List

(FMEA/CIL) Requirements. The documentation delivered by the Contractor shall include the data required by DSG-RQMT-012 at a minimum. To provide consistency of criticality definitions across the Gateway, the Contractor shall use the criticality definitions provided in

DSG-RQMT-012.

(2) Reliability Analysis. This analysis shall be performed in accordance with the Contractor’s

Reliability Plan and use Section 5.4 of DSG-RQMT-010 as a guide.

(3) System Safety Analysis Report (SSAR), including Hazard Reports. The Hazard Analyses and Hazard Reports shall be developed in accordance with the tailored DSG-RQMT-011, Gateway Program Hazard Analysis Requirements.

(c) Phased Safety Reviews and Data Package Submittals

(1) Phase 0 Safety Review

The Phase 0 review is an informal review conducted at an appropriate time during requirements definition and conceptual design. The review is for the Contractor to begin discussions and obtain guidance from NASA on safety-related concerns. The review will also give NASA familiarity with the system, safety analysis approach, and address areas of concern. When requirements will not be met, the discussion should include why the design solution provides an acceptable approach for controlling hazards, the rationale for confidence in the proposed design solution, and why the risk is low and should be acceptable to NASA.

The following topics shall be addressed in the Phase 0 Safety Data Package:

(i.) Introductions and Agenda

(ii.) Scope and Objective

(iii.) System Overview

1. Organizational Structure

2. System Description

3. Interface Overview

4. Operations

(iv.) Presentation of Analysis Approaches

(v.) Overview, Ground Rules, & Assumptions

1. Hazard Analysis Approach

2. Fault Tree Approach

3. FMEA/CIL Approach

4. Reliability Approach and system level reliability allocations

Attachment 02: Data Requirements Descriptions RFP 80KSC019R0002

GLS-006

(vi.) Approach for Controlling Hazards

1. Fault Tolerance

2. List of candidate 0 Fault Tolerance areas

(vii.) Special Topics (Including any Areas of Concern)

(viii.) Forward Plan for Phase I

(2) Phase I Safety Data Package

The Safety Data Package for the Phase I Safety Review shall include the following:

(i.) An overview description of the design and operations of the logistics vehicle being addressed in the review including the following:

1. A brief description of the logistics vehicle

2. Interfaces to Gateway and Cargo/Payloads

3. Planned and proposed functions

4. Operational scenarios related to all mission phases including disposal

5. Figures or illustrations to show all major configurations and identify all hazardous systems and subsystems

(ii.) Functional, power, and control circuit technical documentation and drawings

(at a preliminary design review level) reflecting known safety features, inhibits, controls, etc. Identify and document independence of inhibits and associated controls.

(iii.) SSAR, Hazard Reports, and appropriate supporting data.

(iv.) For hardware that is being proposed or selected, provide drawings (at a PDR level) of components and mechanisms that show the internal parts, flow paths, seals, housings, springs, position indicator switches, mechanical fluid fittings, electrical connectors, etc.

(v.) FMEA/CIL at a PDR level of maturity

(vi.) Reliability Analysis at a PDR level of maturity including data sources, tools, ground rules and assumptions and the following:

1. Quantitative reliability allocations from system level down to the

LRU/component level.

2. Quantitative reliability predictions with traceable documentation of data source information, failure rate estimation factors, models, reliability performance parameters (e.g.