SSP 50964 Visiting Vehicle ISS Integration Plan.pdf

SSP 50964

Baseline

Visiting Vehicle ISS Integration Plan

International Space Station Program

Incorporates SSCD 15818

August 2013

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract No.: NNJ12GA46C

Existing Vehicle Integration document to be updated for USDV application

REVISION AND HISTORY PAGE

REV. DESCRIPTION PUB.

DATE

- Initial Release (Reference per SSCD 013856, EFF. 09-09-13) 09-09-13

DCN 001 (Reference per SSCD 014196, EFF. 08-12-14)

Early Release

Program Release

DCN 002/Update (Reference per SSCD 15818, EFF. 02-20-18)

Program Release 02-28-18 i

PREFACE

VISITING VEHICLE ISS INTEGRATION PLAN

The Visiting Vehicle (VV) International Space Station (ISS) Integration Plan defines the jointly agreed-to processes, roles and responsibilities for closure of the safety, operations and verification program for VV missions to the United States On-orbit Segment (USOS) of the ISS.

The contents of this document are intended to be consistent with the tasks and products to be prepared by the International Space Station Program Participants as defined in SSP 50011-01, Concept of Operation and Utilization, Volume 1. This document is under the control of the Space Station Program Control Board (SSPCB). Any future revisions or updates will be delegated to the Transportation Integration Control Board (TICB) for approval.

ii

INTERNATIONAL SPACE STATION PROGRAM

VISITING VEHICLE ISS INTEGRATION PLAN

CONCURRENCE

AUGUST 2013

iii

TABLE OF CONTENTS

PARAGRAPH PAGE

1.0 INTRODUCTION ................................................................................................................... 1-1

1.1 PURPOSE ............................................................................................................................. 1-1

1.2 SCOPE .................................................................................................................................. 1-1

1.3 PRECEDENCE ...................................................................................................................... 1-1

1.4 DELEGATION OF AUTHORITY ............................................................................................ 1-1

2.0 DOCUMENTS ....................................................................................................................... 2-1

2.1 APPLICABLE DOCUMENTS................................................................................................. 2-1

2.2 REFERENCE DOCUMENTS ................................................................................................ 2-1

3.0 ISS INTEGRATION PROCESS ............................................................................................. 3-1

3.1 ISS INTEGRATION DEFINITION .......................................................................................... 3-1

3.2 ROAD TO ISS INTEGRATION .............................................................................................. 3-1

3.3 ISS INTEGRATION DESCRIPTION, ROLES AND RESPONSIBILITIES ............................. 3-2

3.3.1 ISS VISITING VEHICLE INTEGRATION MANAGER RESPONSIBILITIES .......................... 3-2

3.3.2 ISS VISITING VEHICLE VERIFICATION RESPONSIBILITIES ............................................ 3-3

3.3.3 VISITING VEHICLE PROVIDER RESPONSIBILITIES ......................................................... 3-3

3.4 ISS REQUIREMENTS & JOINT INTEGRATION DOCUMENTS ........................................... 3-3

3.4.1 INTERFACE REQUIREMENTS DOCUMENT (IRD) AND INTERFACE CONTROL

DOCUMENTS (ICDS) ........................................................................................................... 3-4

3.4.2 ISS/VV JOINT INTEGRATION, VERIFICATION AND TEST PLAN (JIVTP) ......................... 3-5

3.4.3 BILATERAL DATA EXCHANGE AGREEMENTS LIST AND SCHEDULE ............................ 3-5

3.4.4 BILATERAL HARDWARE & SOFTWARE EXCHANGE AGREEMENTS LIST AND

SCHEDULE ........................................................................................................................... 3-6

3.5 MAJOR REVIEW DESCRIPTIONS, RESPONSIBILITIES & SUCCESS CRITERIA ............. 3-6

3.5.1 SAFETY REVIEW PANEL (SRP) .......................................................................................... 3-6

3.5.2 FLIGHT OPERATIONS REVIEW (FOR) ............................................................................... 3-7

3.5.3 POST QUALIFICATION REVIEW (PQR) .............................................................................. 3-7

3.5.4 VEHICLE ASSESSMENT REVIEW (VAR)/ISS INTEGRATION COMPLETE ....................... 3-8

3.5.5 STAGE OPERATIONS READINESS REVIEW ..................................................................... 3-8

3.5.6 FLIGHT READINESS REVIEW ............................................................................................. 3-8

3.5.7 ISS MISSION MANAGEMENT TEAM ................................................................................... 3-8

4.0 VISITING VEHICLE VERIFICATION PROCESS .................................................................. 4-1

4.1 VISITING VEHICLE VERIFICATION DESCRIPTION ........................................................... 4-1

4.2 VERIFICATION PLANNING .................................................................................................. 4-1

4.2.1 VERIFICATION AND VALIDATION (V&V) PLAN .................................................................. 4-1

4.2.2 JOINT VERIFICATION EVENTS ........................................................................................... 4-2

4.2.2.1 JOINT VERIFICATION TEST SHEET ................................................................................... 4-2

4.2.3 PROCESS SAMPLING ......................................................................................................... 4-2

4.2.3.1 PROCESS SAMPLING ACTIVITIES LIST ............................................................................ 4-3

4.2.3.2 PROCESS SAMPLING REPORTS ....................................................................................... 4-3

4.2.4 NONCONFORMANCE PROCESS ........................................................................................ 4-3

4.2.4.1 WAIVERS VS. EXCEPTIONS ............................................................................................... 4-4

4.2.4.2 NONCONFORMANCE DECISION PROCESS ..................................................................... 4-4 iv

4.2.4.3 NONCONFORMANCE APPROVAL PROCESS ................................................................... 4-5

4.2.4.4 VERIFICATION TAILORING ................................................................................................. 4-6

4.2.5 ALTERNATE STANDARDS .................................................................................................. 4-6

4.3 VERIFICATION EXECUTION ................................................................................................ 4-7

4.3.1 VISITING VEHICLE VERIFICATION ..................................................................................... 4-7

4.3.2 DETAILED VERIFICATION EVENT PLAN REVIEW ............................................................. 4-7

4.3.3 VERIFICATION COMPLIANCE MATRIX .............................................................................. 4-7

4.3.4 VERIFICATION EVENT REPORTS ...................................................................................... 4-8

4.3.5 VERIFICATION SUBMITTAL ................................................................................................ 4-8

4.3.6 NASA REVIEW OF VERIFICATION COMPLIANCE DATA .................................................. 4-8

4.3.6.1 VERIFICATION REVIEW COMMENTS ................................................................................ 4-8

4.3.7 COMPLIANCE ISSUE RESOLUTION ................................................................................... 4-9

4.3.8 VERIFICATION CLOSURE ................................................................................................... 4-9

4.4 PQR PROCESS .................................................................................................................... 4-9

4.4.1 PQR KICK-OFF ..................................................................................................................... 4-9

4.4.2 OPEN VERIFICATION EVENTS ........................................................................................... 4-9

4.4.3 PQR BOARD ......................................................................................................................... 4-9

4.4.4 PQR BOARD CERTIFICATE................................................................................................. 4-10

4.4.5 SRP & PQR DETAILED RELATIONSHIP ............................................................................. 4-10

4.4.5.1 HAZARD CONTROL TO REQUIREMENT MAPPING .......................................................... 4-11

4.4.5.2 VERIFICATION CLOSURE DEPENDENCIES ...................................................................... 4-12

4.5 SUBSEQUENT FLIGHTS ...................................................................................................... 4-12

4.5.1 VISITING VEHICLE ACCEPTANCE ..................................................................................... 4-12

4.5.1.1 REQUIRED VISITING VEHICLE DELIVERABLES ............................................................... 4-13

4.5.1.2 RECURRING VERIFICATION EVENTS ............................................................................... 4-13

4.5.2 DELTA VERIFICATION ......................................................................................................... 4-14

4.5.2.1 DESIGN CHANGES .............................................................................................................. 4-14

4.5.2.2 CARGO SPECIFIC ................................................................................................................ 4-14

APPENDIX

A ACRONYMS AND ABBREVIATIONS ................................................................................... A-1 B GLOSSARY <RESERVED> .................................................................................................. B-1 C OPEN WORK ........................................................................................................................ C-1 D PROGRAM INTEGRATION CONTENT FROM CRS SOW ................................................... D-1 E TEMPLATES ......................................................................................................................... E-1 F JOINT VERIFICATION EVENTS LIST .................................................................................. F-1 G BILATERAL DATA EXCHANGE AGREEMENTS LIST AND SCHEDULES .......................... G-1

H BILATERAL HARDWARE AND SOFTWARE EXCHANGE AGREEMENTS LIST AND

SCHEDULE ........................................................................................................................... H-1 I GENERIC ISS POST QUALIFICATION REVIEW AGENDA/SCOPE .................................... I-1

TABLE

3.4.1-1 ISS VISITING VEHICLE SOFTWARE ICDS ......................................................................... 3-5 C-1 TO BE DETERMINED ITEMS ............................................................................................... C-1 C-2 TO BE RESOLVED ISSUES ................................................................................................. C-1 v

FIGURE

3.2-1 ROAD TO ISS INTEGRATION .............................................................................................. 3-2 3.4-1 ISS INTEGRATION DATA REQUIREMENTS ....................................................................... 3-4 4.4.5-1 ISS SAFETY REVIEW AND VERIFICATION PROCESS ...................................................... 4-10 E.1-1 VCN SIGNATURE FORM TEMPLATE .................................................................................. E-3 I.1-1 TYPICAL PQR TIMELINE ..................................................................................................... I-2

1-1

1.0 INTRODUCTION

This document describes the generic execution plan for the International Space Station (ISS) Program Integration of the Visiting Vehicle (VV) flight to the United States On-orbit Segment (USOS) of ISS, including the development of joint integration and requirements documents, review plan, review process, organization, and schedule. Any partner or contractor (a.k.a. VV provider) intending on developing a VV for approaching and/or mating, and conducting joint operations with ISS should follow the process and timeline within. Tailoring is allowed to meet the intent of this plan and will be documented in the Partner-specific Joint Integration, Verification and Test Plans

(JIVTP).

1.1 PURPOSE

The purpose of this document is to define the generic process by which the VV spacecraft will achieve integration with the ISS. The specific focus will be on development of joint products and closure of verification requirements through the Post Qualification Review (PQR) and other related ISS integration reviews.

1.2 SCOPE

Section 3.0 defines the ISS Integration review activities, requirements, relationships, and timeline. Section 4.0 defines the VV verification process.

1.3 PRECEDENCE

In the event of a conflict between the text of this integration plan and requirements specified in applicable and reference documents cited herein (listed in Section 2.0), the applicable and referenced documents take precedence. Nothing in this document supersedes applicable laws and regulations, unless a specific exemption has been obtained through the appropriate Federal or State agency.

1.4 DELEGATION OF AUTHORITY

This document is prepared and maintained in accordance with SSP 50010, Standards for ISS Program Documentation. The responsibility for assuring the definition, control, and implementation of the interfaces identified in this document is vested with the NASA ISS Program Office.

2-1

2.0 DOCUMENTS

2.1 APPLICABLE DOCUMENTS

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are applicable to the extent specified herein. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

CCT-REQ-1130 ISS Crew Transportation and Services Requirements Document

JSC 35089 Visiting Vehicle Operations Document

SSP 30599 ISS Safety Review Process

SSP 50108 ISS Program Certification of Flight Readiness Process Document

SSP 50808 International Space Station (ISS) to Commercial Orbital Transportation Services (COTS) Interface Requirements Document (IRD)

SSP 50833 International Space Station Program Cargo Transport Interface Requirements Document

2.2 REFERENCE DOCUMENTS

The following documents contain supplemental information to guide the user in the application of this document. These reference documents may or may not be specifically cited within the text of this document.

MIL-STD-1553 Data Bus Amplitude Test

NASA-STD-8719.13B Software Safety Standard

SSP 30426 Space Station External Contamination Control Requirements

SSP 30695 Acceptance Data Package Requirements Specification

SSP 41170 Configuration Management Requirements

SSP 41175-39 Software Interface Control Document Station Management and Control to International Space Station (ISS) Book 39, Commercial Orbital Transportation Services (COTS) Free Flyer Common Interface

2-2

SSP 41177-09 Software Interface Control Document Guidance Navigation and Control Multiplexer/Demultiplexer to International Space Station Book 9, International Docking Adapter (IDA)-Docked Visiting Vehicle and Pass-Through Portable Computer System Interface

SSP 41178-42 Software Interface Control Document Internal Multiplexer/Demultiplexer to International Space Station (ISS) Book 42, Commercial Orbital Transportation Services (COTS) Berthed Common Interface

SSP 50010 Standards for ISS Program Documentation

SSP 50011-01 Concept of Operation and Utilization, Volume 1

SSP 50123 Configuration Management Handbook

SSP 50482 ISS Program Software Management Plan.

SSP 52051,

Volume 1

User Electric Power Specifications and Standards Volume 1:

120 Volt DC Loads

3-1

3.0 ISS INTEGRATION PROCESS

3.1 ISS INTEGRATION DEFINITION

• ISS integration is defined as the activities required to ensure that ISS requirements [i.e. SSP 50808, International Space Station (ISS) to Commercial Orbital Transportation Services (COTS) Interface Requirements Document (IRD), SSP 50833, ISS Cargo Transportation Interface Requirements Documents, International Partner (IP)-specific requirements documents, and CCT-REQ-1130, ISS Crew Transportation and Services Requirements Document, “I” (for crewed vehicles)] have been met, necessary hardware and software development to interface with the ISS has been completed, and joint on-orbit integrated operations plans and products have been baselined, with any further updates to joint operations products to be completed through periodic operations and configuration reviews, as well as through real-time mission support.

• The ISS integration process typically begins well before a VV provider has reached a Critical Design Review (CDR) level of maturity with the establishment of baseline ISS Interface Requirements Documents (IRD); joint hardware, software and ground segment Interface Control Documents (ICDs); and other joint VV-specific ISS integration documents as discussed within.

• ISS Integration is a milestone used as input for NASA-managed Stage Operations Readiness Review (SORR) which produces the ISS Certificate of Flight Readiness (CoFR).

• ISS Integration is considered complete when the PQR, phase III Safety Review Panel (SRP) approval, and Joint Flight Operations Review (FOR) and final mission operations products have been completed, and the VV provider and NASA are in agreement on the open actions and closure methodology.

Additional ISS Program and mission integration responsibilities typically required of ISS VV providers are captured in Appendix D, Program Integration Content from CRS SOW. Partner-specific agreements will be defined in their respective contract SOW.

For subsequent flights, ISS integration activities will be determined by previous mission results, vehicle hardware/software redesign, and proposed new mission content.

Specifically:

• PQR will focus on verification of changes in requirements, design, recurring verification events and unique crew and cargo requirements.

• Baselined flight safety assessments will be evaluated and updated as required as a result of vehicle design and/or operational changes.

• FOR will be focused on mission-specific or updated flight rules and procedures.

3.2 ROAD TO ISS INTEGRATION

Figure 3.2-1, Road to ISS Integration, captures the major products that flow into and out of each major review, as well as the relationships, and timeline for each step. While Integrated Hazard Reports (IHR) will reference final vehicle phase III approved hazard

3-2 reports, the development of phase III IHRs may begin with delivery of the vehicle Safety Data Package (SDP).

FIGURE 3.2-1 ROAD TO ISS INTEGRATION

3.3 ISS INTEGRATION DESCRIPTION, ROLES AND RESPONSIBILITIES

3.3.1 ISS VISITING VEHICLE INTEGRATION MANAGER RESPONSIBILITIES

The Visiting Vehicle Integration Manager (VVIM) is the ISS Program technical lead for conducting and/or ensuring that all integration activities are complete for enabling the VV flight to the ISS. The VVIM interfaces with the VV provider(s), as well as other NASA program offices, when needed. VVIM responsibilities include:

• Lead the Visiting Vehicle Integration Team (VVIT) meetings, which is comprised of ISS subsystem requirement owners, technical experts, and VV provider(s), to develop and execute the Road-to-ISS Integration.

• Develop and maintain ISS/VV interface requirements and Bilateral Data Exchange Agreements List and Schedule (BDEALS) with VV providers/Partners.

• Disposition and process requirement non-conformances through the appropriate ISS Board(s).

• Serve as ISS Program focal for VV interface issues, data exchanges, technical and schedule performance and Increment Management Center (IMC) operations.

• Develop and maintain ISS integration schedule.

3-3

3.3.2 ISS VISITING VEHICLE VERIFICATION RESPONSIBILITIES

ISS Visiting Vehicle Verification (VVV) supports the VVIM to conduct Test and Verification integration for VV. ISS VVV responsibilities will include:

• Support development and review of verification requirements, establish requirement verification ownership and support the development and review of any exceptions and/or waivers to those verification requirements.

• Coordinate VV verification plans with the appropriate NASA requirement owners.

• Manage joint verification and process sampling activities.

• Manage the joint ISS/VV verification closure process and products.

• Status joint ISS/VV verification closure progress (e.g., to the appropriate ISS Boards).

• Serve as book manager for Joint Integration, Verification and Test Plans

(JIVTP).

3.3.3 VISITING VEHICLE PROVIDER RESPONSIBILITIES

The VV provider responsibilities will include:

• Provide key integration personnel for the planning, development and execution of joint products and activities.

• Develop and maintain the VV provider products identified in Section 3.0 and Section 4.0.

• Deliver verification closure documentation with full rationale and data to support closure of each requirement.

• Assist in resolution of any verification closure issues identified by NASA.

• Support ISS Program major reviews and ISS Program boards as required.

3.4 ISS REQUIREMENTS & JOINT INTEGRATION DOCUMENTS

This section describes the main ISS interface requirements and joint integration documents used throughout the ISS integration process. All of these documents should be developed early in the VV design phase (Preliminary Design Review (PDR) time frame) and baselined by CDR. Figure 3.4-1, ISS Integration Data Requirements, shows the relationship between the primary data requirement sources throughout the ISS integration process.

3-4

FIGURE 3.4-1 ISS INTEGRATION DATA REQUIREMENTS

3.4.1 INTERFACE REQUIREMENTS DOCUMENT (IRD) AND INTERFACE CONTROL

DOCUMENTS (ICDS)

The ISS Program manages IRDs (such as SSP 50808 for COTS VVs), which provide interface requirements between the ISS and VVs, design requirements for operations and ground systems supporting VV flights to ISS, as well as design requirements on the VV to ensure safe integration with the ISS. All changes to ISS requirements are coordinated through a Document Change Notice (DCN), per SSP 41170, Configuration Management Requirements. Supporting NASA Programs and VV providers are responsible for reviewing, approving and/or impacting DCNs. VV providers are also responsible for maintaining verification plans against the latest agreed-to revision and DCN throughout the ISS integration process and into the services phase.

For commercial crew vehicles, SSP 50808 in conjunction with the CCP-managed CCT-REQ-1130, International Space Station (ISS) Crew Transportation and Services Requirement Document (SRD), provides all the ISS requirements necessary for the Commercial Crew System design and joint operations plans.

The detailed design implementation of the ISS to VV interfaces are controlled in vehicle specific ICDs. The VVIM, or delegate, will work with a VV provider and ISS Program to coordinate development of a unique hardware and ground segment ICD prior to VV design baseline at a CDR. Common ISS software interfaces are defined in existing ICDs in the below Table 3.4.1-1, ISS Visiting Vehicle Software ICDs.

3-5

TABLE 3.4.1-1 ISS VISITING VEHICLE SOFTWARE ICDS

Vehicle Document # Title COTS Vehicles SSP 41175-39 Software Interface Control Document Station Management and Control to International Space Station (ISS) Book 39, Commercial Orbital Transportation Services (COTS) Free Flyer Common Interface

Docked Visiting Vehicles

SSP 41177-09 Software Interface Control Document Guidance Navigation and Control Multiplexer/Demultiplexer to International Space Station Book 9, International Docking Adapter (IDA)-Docked Visiting Vehicle and Pass- Through Portable Computer System Interface

Berthed COTS Vehicles

SSP 41178-42 Software Interface Control Document Internal Multiplexer/Demultiplexer to International Space Station (ISS) Book 42, Commercial Orbital Transportation Services (COTS) Berthed Common Interface

3.4.2 ISS/VV JOINT INTEGRATION, VERIFICATION AND TEST PLAN (JIVTP)

The ISS/VV JIVTP defines the joint NASA and VV provider integration and verification activities where standalone verification and/or validation are not sufficient to assure performance and safety with the ISS. JIVTP defines the data, products, tasks, and planning agreements for the integration and verification of the VV with the ISS and identifies the organizational roles and responsibilities involved in implementing these requirements. ISS VVV will develop and serve as the book manager for the JIVTP.

These documents are baselined through the CR process described in SSP 50123, Configuration Management Handbook. A list of expected joint verification events, based on ISS requirements, is provided in Appendix F, Joint Verification Events List.

3.4.3 BILATERAL DATA EXCHANGE AGREEMENTS LIST AND SCHEDULE

BDEALS describes the programmatic and technical data, documented as a compilation of individual Data Item Descriptions (DID) that will be exchanged between NASA and the VV provider to facilitate NASA's tasks for integration of the total ISS and the VV provider’s completion of the VV design and verification. A BDEALS can be captured as a formal, jointly signed ISS Program document or a list of exchanges managed by the VVIM. However, joint agreement on the full list of DIDs should be completed early in the ISS integration phase, and well before the VV CDR. Each DID should consist of at least the following data. A list of typical DIDs is provided in Appendix G, Bilateral Data Exchange Agreements List and Schedule, and details will be defined in the partner-specific JIVTP.

• Purpose/Use of the Data

• Scope

• Reference

• Description of the Data

• Requesting Team

• Feedback required

• Delivery format

• Delivery dates

3-6

3.4.4 BILATERAL HARDWARE & SOFTWARE EXCHANGE AGREEMENTS LIST AND

SCHEDULE

A Bilateral Hardware and Software Exchange Agreements List and Schedule (BHSEALS) defines the hardware and software that will be exchanged between NASA and the VV provider, as well as the technical support that will be provided for the hardware and software, in carrying out their respective roles for the VV within the ISS Program. A BHSEALS can be captured as a formal, jointly signed ISS Program document or a list of exchanges managed by the VVIM. However, joint agreement on the full list of DIDs should be completed early in the ISS integration phase, and well before the VV CDR. This agreement includes VV related hardware and software exchanges such as the following. A list of typical DIDs is provided in Appendix H, Bilateral Hardware and Software Exchange Agreements List and Schedule, and details will be defined in the partner-specific JIVTP.

• Development hardware and software to be used in interface simulations and verification testing;

• Support equipment, either provided by the VV provider or NASA, for use in simulations, verification testing, demonstrations, training, and operations;

• NASA flight hardware and software that will be integrated into the VV flight elements prior to launch.

3.5 MAJOR REVIEW DESCRIPTIONS, RESPONSIBILITIES & SUCCESS CRITERIA

3.5.1 SAFETY REVIEW PANEL (SRP)

The SRP is responsible for the overall integrated safety of the ISS and is required to provide the overall assurance that the U.S. elements, International Partner (IP) Elements, support equipment, Government Furnished Equipment (GFE), ISS visiting vehicles, ISS crew return vehicles, and payloads are safe.

The safety review process is an incremental process that will focus on: assessing the design and operations against applicable safety requirements; assuring that all hazards and hazard causes inherent in the design and operations have been identified;

evaluating the means employed to control the hazard; and assessing the methods identified to verify all hazard controls. For COTS visiting vehicles, the applicable safety requirements are documented in SSP 50808, Paragraph 3.3.11. These requirements apply to the VV during all ISS-related mission phases.

The ISS safety review process is defined in SSP 30599, ISS Safety Review Process and implemented through three phased safety reviews with the VV provider presenting their VV hazard reports to the SRP board for approval. SSP 30599 identifies the standard timing, general effort required, data requirements and objectives for each phase.

Prior to the SRP phase III board, all significant hazard control verifications will be completed, with an overall goal of 90% verifications complete. The remaining open hazard control verifications will be captured in a Safety Verification Tracking Log (SVTL), which will be delivered as part of the safety data package, and is described in

3-7 detail in SSP 30599. Closure of a hazard control verification within the SVTL, usually does not require NASA SRP approval. However, the SRP may choose to hold a hazard report open pending closure of a hazard control verification event in the SVTL.

3.5.2 FLIGHT OPERATIONS REVIEW (FOR)

For flight to ISS, the expected joint operations between the VV provider and NASA Mission Operations Directorate (MOD) are defined in JSC 35089, Visiting Vehicle Operations Document, and as required for COTS VVs per SSP 50808, Paragraph 3.4.5.

FOR is a formal review evaluating flight operations products, required for a specific flight or mission activity, conducted by the MOD with support from the VV provider for the ISS Program. The goal of the FOR is to baseline the set of operations documentation, with concurrence from both ISS and VV provider flight control and engineering disciplines, partners, ISS Program management representation, and vendors, in order to ensure the safe and accurate implementation of mission requirements.

Operational products will be published for review by the community about six weeks before the FOR start date. This will be announced to FOR participants via letter, which will include the URL for the FOR website, and details on the rest of the process.

Reviewers may submit updates via Discrepancy Notices (DN), which will be collected until about a week before the FOR. At the FOR, the board will review and disposition every DN, and may also assign actions to any participating organization, which are then tracked to closure via the Joint Operations Panel (JOP).

The products which will be reviewed at FOR may include: Flight Rules (vehicle-specific Volume and applicable Volume B rules); Operational Interface Procedures (OIP);

Operational Data File (ODF) procedures required for VV support; Short Term Plan (STP)/Crew Timeline for major VV activities; VV systems manual; VV Demonstration Objectives Report (DOR). In general, these products are authored by NASA MOD personnel, with input from the VV provider.

After the FOR, all approved DNs are incorporated into the affected operational products for the baseline mission publications. It is possible that further changes will be required to support the mission between FOR and launch as we proceed with detailed mission training, testing and planning. As changes are identified to the JOP team, the appropriate change request (CR) process will be initiated to incorporate the new information.

3.5.3 POST QUALIFICATION REVIEW (PQR)

The purpose of the PQR is to confirm verification compliance of the VV with ISS requirements, and related ICD requirements, in order to confirm the vehicle characteristics, design and construction, safety, joint operations plans and external interfaces.

The PQR board is the final milestone of a long-term verification coordination and execution process to establish requirement compliance by the NASA requirement owners. The board will review the results of VCN coordination and give a direction to forward work for screened findings and issues. Any open VCNs or action items will

3-8 have a resolution plan and estimated closure date, which are nominally set for completion before SORR. The VV provider is responsible for closing all open VCNs and action items by the dates identified at the PQR board.

3.5.4 VEHICLE ASSESSMENT REVIEW (VAR)/ISS INTEGRATION COMPLETE

The VVIM will conduct a VAR to confirm completion of ISS integration and as an ISS Program-wide input for SORR, to ensure that all VV requirements have been met, hazard controls verified, joint on-orbit integrated operations plans finalized and all ISS interface hardware and software development completed. VAR/ISS integration is typically completed after the PQR, SRP, and FOR have been held, and NASA and the VV provider are in agreement on the open actions and closure methodology. VV provider participation to VAR is optional but expected based on past VV integration experiences.

3.5.5 STAGE OPERATIONS READINESS REVIEW

[From SSP 50108, ISS Program Certification of Flight Readiness Process Document]

SSP 50108, Section 5.0, describes the organizational participation, responsibilities, requirements, and procedures to ensure effective planning and conducting of the ISS Program CoFR reviews, which assess and certify readiness of ISS Program HW/SW and supporting ground facilities and personnel to execute the planned objectives and requirements of the specified Flight and Stage. The ISS SORR will be conducted approximately one month prior to launch and the Flight Readiness Review (FRR) at two weeks prior to launch.

For VV missions, the ISS Certification of Flight Readiness (CoFR) will be conducted by NASA. The ISS Transportation Integration Office (TIO) or a representative from the NASA Program Office managing the certification effort for the VV (such as CCP) will provide formal certification for the VV provider. The VVIM's CoFR endorsement confirms that ISS integration and mission integration have been completed. The VV provider is required to present a readiness assessment and will be polled for their position on readiness for flight at the conclusion of the SORR.

3.5.6 FLIGHT READINESS REVIEW

[From SSP 50108, ISS Program Certification of Flight Readiness Process Document]

For a VV launch of a first flown VV or if significant changes have been made to the vehicle, a NASA FRR will be held following the SORR to verify the agency’s readiness for the VV launch and return and the specified flight/stage.

3.5.7 ISS MISSION MANAGEMENT TEAM

The ISS Mission Management Team (IMMT) is the multilateral program decision-making body responsible for making programmatic trades and decisions associated with maintaining ISS flight and crew safety, ensuring ISS systems remain operational and enhancing mission success, following the successful completion of the SORR and/or FRR. The IMMT is led by the NASA ISS program manager and includes the IP program managers and other technical experts. The IMMT provides programmatic oversight and

3-9 direction during real-time operations of the ISS and is responsible for the final ISS readiness review nominally 7 days prior to a scheduled major activity or event (e.g., VV launch, docking/berthing, undocking/unberthing, EVA and major software upgrades).

This readiness review covers any open action items or CoFR exceptions affecting the planned activity or event. The final results of the readiness review will be “go/no go” for the execution of the planned activity or event.

During real-time on-orbit operations, and if time to make a decision is available, issues outside the scope of the approved operations products are taken to the IMMT for resolution. For time critical decision, if a consensus cannot be reached the IMMT Chair will make a decision to be implemented by the MCC-H Flight Director (FD), the International Partner (IP) FDs, and other ISS program representatives, as applicable. If time is available, the decision may be appealed to the designated management representatives.

4-1

4.0 VISITING VEHICLE VERIFICATION PROCESS

4.1 VISITING VEHICLE VERIFICATION DESCRIPTION

VV verification includes all activities required to ensure VV compliance with its applicable specification and interface requirements with the ISS. The VV verification process defines the typical steps and products to be completed for VV verification planning, execution and closure. The VV verification process leads up to the PQR board, which will be used as an input for the ISS CoFR. Most of the VV design verification will be completed with its first flight. However, a PQR, or equivalent, will be completed for every VV flight, with reduced scope for subsequent flights focusing on verification of delta design, unique cargo requirements, and recurring verification events.

4.2 VERIFICATION PLANNING

Verification planning is initiated early in a new VV project lifecycle, during the requirements development phase. Most of the VV verification planning products will be developed by the VV provider in the form of a Verification and Validation (V&V) plan, with ISS VVV responsible to coordinate review with the applicable requirement owners for concurrence on the verification plans. The JIVTP is prepared early in the design phase and baselined by CDR.

4.2.1 VERIFICATION AND VALIDATION (V&V) PLAN

The VV provider will deliver and maintain a V&V plan prior to the VV CDR and throughout the ISS integration process, in accordance with the content defined below.

ISS VVV will coordinate review of the V&V plan, its activities, methods, products, and processes that develop the evidence all ISS requirements are met and have acceptable verifications.

• Partners requirement statements and associated verifications.

• Traceability from the Partners requirement to the ISS requirement number.

• Detailed descriptions of the Verification Events (VE) to be performed to complete the verifications for all requirements traceable to ISS requirements.

The VE details will include the configuration of the activities relative to the planned flight configuration, the specific activities to be performed including the lifecycle verification, qualification and flight unit acceptance test activities, the measurable criteria for determining if the activities successfully verified the requirement, identification and validation of critical models and analyses, joint verifications with the ISS Program, and any proposed nonconformances, with required supporting material defined in Paragraph 4.2.2.

• Detailed descriptions of the activities to be performed to complete validation of the VV. The details will include the configuration of the activities relative to the planned flight configuration, the specific activities to be performed, and the measurable criteria for determining if the activities successfully validated the VV.

4-2

• Schedule of V&V activities and the products to be delivered and made available to NASA.

• Manufacturing and operations V&V plans including those that implement hazard controls.

4.2.2 JOINT VERIFICATION EVENTS

Joint verification is an activity performed by ISS Program with active participation by the VV provider and vice-versa when it is determined either that more than stand-alone verification activities are necessary to close a requirement or that validation is necessary to minimize program risks. The verifications/ validation that are identified as joint will be captured in an ISS/VV JIVTP and associated annexes, as applicable. A list of expected joint verification events are provided in Appendix F, Joint Verification Events List.

Active participation includes one or more of the following:

• Development of verification objectives

• Detailed verification planning

• Verification implementation and documentation

• Requirement compliance determination and documentation

• Identification/coordination of test facilities

• Provision for test equipment and/or support equipment for verification/integration

4.2.2.1 JOINT VERIFICATION TEST SHEET

Verifications identified as joint tests in the JIVTP will have a joint test sheet developed to identify lead agency, source requirements, test objectives, test set-up, personnel, success criteria, responsibilities, and test execution schedule. The standard layout for a joint verification test sheet is provided in Appendix E, Templates. Typically the lead agency will initiate joint test sheet development, working with ISS VVV to coordinate final content and approval, through signature of appropriate parties, of all joint test sheets prior to the conduct of the joint tests. Joint test sheets will typically be captured by a Notification of Document Change (NDC) and are incorporated into the JIVTP revisions through the CR process described in SSP 50123, if developed after initial baseline.

4.2.3 PROCESS SAMPLING

Process sampling is an activity performed by NASA to witness selected VV verification activities or processes. Process sampling is in addition to and does not supersede or invalidate agreements under NASA insight. This sampling is not to confirm design conformance or verification results. The focus of process sampling will be on critical verification activities to ensure that the established verification processes are followed and to evaluate process equivalency to industry, NASA and/or ISS standards. It will not be a technical review by NASA of the correctness or completeness of the verification

4-3 data nor to approve VV provider processes, but rather it develops confidence in the VV provider that will facilitate verification closure and supports ISS CoFR endorsements.

4.2.3.1 PROCESS SAMPLING ACTIVITIES LIST

ISS VVV will coordinate with NASA subsystems and the VV provider to identify those activities and/or processes that are to be process sampled, including the rationale and timing/schedule for the event to be process sampled. The number and scope of activities will depend on the criticality of the event and the ability of the VV provider to support sampling on a non-interference basis. The VV provider will communicate their internal schedule for these activities and provide updates when necessary. The depth of penetration will vary based on the specific process to be sampled, the specific concern identified, and the agreement obtained from the VV provider. The VV provider will provide their event plan/procedures/process documentation to the process sampling team prior to the activity to be witnessed as early as possible within the already established development flow. The delivery date of each plan will vary depending on the area being process sampled. In cases where a plan cannot be provided until just before the event, then technical subsystem communications should be ongoing to develop an understanding of what the procedure/plan will entail. The importance of this review period is to allow the NASA reviewers time before the event to become familiar with the procedures, ask questions and close any open issues prior to the verification event. The questions and issues will be technical in nature only as the VV provider has an established process for developing its reports. Process sampling activities by NASA will not interfere with work at the site to be witnessed nor cause unnecessary additional tasks for the VV provider. Ideally, questions and issues raised during the review period will be coordinated within the already established subsystem telecons or the VVV

Forum.

4.2.3.2 PROCESS SAMPLING REPORTS

At the completion of activities, a seven-day quick-look verbal or email report should be provided by the NASA process sampling team, followed by a complete process sampling report that has been coordinated between the NASA and VV subsystem counterparts, and documents the conclusion of the process sampling activities due within 30 days of event completion. This report will provide a detailed description of the sampling activity, an assessment of VV provider verification/processes and will not be intended for review of verification results. The process sampling team will submit reports to VVV, who will retain them as records associated with the verification campaign.

4.2.4 NONCONFORMANCE PROCESS

The following VV nonconformance process documents the definitions, roles and responsibilities and process for developing and approving ISS nonconformances (waivers/exceptions/Non-Conformance Report (NCRs)). In general, the VV provider will develop the initial nonconformance decision package, and either the VV provider or VVIM will take lead for processing approval depending on which change paper it will be documented on. Any nonconformances submitted against CCT-REQ-1130 “I”

4-4 requirements will follow this same process but will be coordinated with the appropriate CCP representative and management before going to the Space Station Program Control Board (SSPCB) for approval.

4.2.4.1 WAIVERS VS. EXCEPTIONS

Waivers, per SSP 41170, are written authorization, granted after the fact, for use or acceptance of a flight article that does not meet specified requirements, but is considered suitable for use “as is”, or after repair by an approved method. “Granted after the fact” is typically considered after baseline of a design at a CDR, and is used to distinguish between when to proceed with a deviation, not used on VV interface requirements, or waiver. Waivers are typically granted on a single serial number for a specific flight, but may also be written as recurring against a part number for multiple or all flights, with identified constraints. Waivers are processed through ISS Configuration Management (CM) via form ISS_CM_011 for program evaluation and are approved at the Space Station Program Control Board (SSPCB). A safety NCR is a sub-category of waiver that impacts ISS safety and is processed through the SRP per SSP 30599, Section 6.0, and, if deemed a program-level NCR, approved at the SSPCB. Equivalent safety NCRs may be approved by the SRP and do not go through ISS CM review.

Exceptions, again per SSP 41170, are a type of engineering change, when approved, is written authorization to tailor a baselined specification requirement to a given configuration item (CI), or part number, or group of CIs that may limit the applicability of the requirement to the item(s). For exceptions, there is no designation of a period within the project flow for which they can be granted. However, because exceptions are tied to a CI, they are typically linked to a specific design or design change. Exceptions are typically baselined into an appendix of the specification for which the exception is being granted via a DCN. However, with SSP 50808 being levied on multiple commercial VVs and the proprietary nature of exceptions, COTS VV exceptions will be baselined into an appendix in the VV-specific hardware ICD via a Program Interface Revision Notice (PIRN). An exception is considered approved once the final DCN/PIRN has been presented to ISS management and received all concurrence from impacted requirement owners.

Therefore, both waivers and exceptions are valid nonconformance paper for all current VVs for the remainder of the verification and services phase, and the distinguishing criteria for choosing between the two forms should be: 1) is the nonconformance attached to a CI design, or as-built article(s); 2) is the non-conforming requirement tailorable such that the modified requirement meets the intent of the original requirement, and/or is acceptable to ISS management and requirement owners from an ISS-integrated perspective.

4.2.4.2 NONCONFORMANCE DECISION PROCESS

A. The VV provider will identify a requirement compliance issue or operational constraint through submittal of an Engineering Change Notice (ECN), Request For Waiver (RFW) or equivalent package to ISS and initial discussions at the VVIT

4-5 meeting or VVV forum to reach agreement on proposed forward plan. Examples of ECNs and RFWs are provided below.

1. ECN: Exceptions are typically driven by design, and, at this point with Visiting

Vehicles, specifically by changes to vehicle design or internal requirements that impact an ISS requirement. ECN should include:

a. Detailed design package

b. Reason for change

c. Impacted ISS requirements

d. Proposed tailoring

e. Rationale for acceptance

2. RFW: Waivers/NCRs are driven by as-built design and/or verification results showing non-compliance with an ISS requirement or hazard control. RFW should include:

a. Impacted ISS requirements

b. Flight/units affected

c. Description of waiver

d. Need for waiver including full technical acceptance rationale

e. Operational impacts

f. Impacts if not approved

B. NASA will present issue and proposed forward plan to ISS management outside of board for authorization to proceed with the approval process.

C. The nonconformance package will be finalized through the VVIT or VVV meeting to reach agreement on final wording, acceptance rationale, risk mitigation, etc, and update package prior to submitting for ISS management approval.

4.2.4.3 NONCONFORMANCE APPROVAL PROCESS

The nonconformance approval process varies based on the form on which it is being documented, as described below. The below approval process descriptions are in compliance with SSP 50123. A requirement change may also be a valid option, particularly in place of an exception, if the acceptance rationale is applicable to any VV-provider. The proposed change would need to be coordinated with all applicable VV-providers and would remove the need for a VV-specific nonconformance.

Requirement Change: NASA will prepare a DCN, or equivalent, with the specific FROM/TO agreed to at the VVIT or VVV meeting, present to ISS management OSB, and submit to document management for formal concurrence by the VV provider(s), requirement owners and incorporation into the appropriate document.

4-6

Exception: NASA will prepare a PIRN, or equivalent, with the specific FROM/TO agreed to at the VVIT or VVV meeting,…