50281.DOC

1-1

SSP 50281

December 20, 2002

SSP-50281

Node 2 NASA/ASI BILATERAL INTEGRATION & VERIFICATION PLAN

INTERNATIONAL SPACE STATION PROGRAM

December 20, 2002

Initial Release

Space Administration

Program Office

Houston, Texas

REVISION AND HISTORY PAGE

Intentionally Left Blank

PREFACE

The Node 2 National Aeronautics and Space Administration (NASA)/ASI Bilateral Integration and Verification Plan (BIVP) is the document that defines the joint NASA and ASI integration and verification activities and identifies the organizational procedures involved in implementing the integrated verification requirements of the Node 2 Element. The goal of this document is also to ensure integration of the Node 2 as part of the International Space Station (ISS).

The Node-2 NASA/ASI Bilateral Integration and Verification Plan equally applies to the NASA and the Agenzia Spaziale Italiana (ASI). This document is under the control of the International Space Station Control Board (SSCB) with the concurrence of ASI. Any changes or revisions will be approved by the International Space Station Control Board and ASI.

/s/ William Gerstenamier

/s/ Andrea Lorenzoni

NASA

ISS Program Manager

ASI

Node 2 Program Manager

04/17/03

04/01/03

Date

Date

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

NASA/ASI BILATERAL INTEGRATION AND VERIFICATION PLAN

Prepared by:

(NASA)

David Aycock Jr.

/s/David Aycock Jr.

(Signature)

Node 2 T&V Engineer

12/17/2002

(Date)

Concurred by:

Donna Prsha

/s/Donna Prsha (Signature) Node 2 T&V Lead

12/17/2002

Concurred by:

Steve McClard

/s/Steve McClard

(Signature) Node 2 Project Manager

12/19/2002

Concurred by:

Kenny Mitchell

/s/Kenny Mitchell (Signature) Nodes 2/3 Program Manager

1/7/2003

Concurred by:

(Alenia)

Walter Cugno

/s/ Walter Cugno (Signature) Node 2 Program Manager

04/01/03

Concurred by:

Rafael Garcia

/s/ Rafael Garcia

(Signature) ISS T&V Manager

03/28/03

Concurred by:

Stephen V. Porter

/s/ Stephen V. Porter

(Signature) ISS Vehicle Manager

03/28/03

Concurred by:

Sandra Boriack

/s/Sandra Boriack

(Signature)

CM DQA

04/18/03

List of Changes

DATE

(N2-RP-AI-0042)

4650, 5144, 5389, 5654, 6260

TABLE OF CONTENTS

71.

Purpose and Scope of the Document

1.1 Precedence 1.2 Document Editing, Maintenance and Release Authority 2.

Documents 2.1 Applicable Documents 2.2 Reference Documents 3.

International Space Station System Description 3.1 On-Orbit Segment (USOS) Description 3.1.2 Ground Segment Description 3.2 Node 2 Element Description 4.

Integration and Verification 4.1 Integration and Verification Approach 4.1.1 NASA Responsibility 4.1.2 ISSP Test & Verification Team 4.2 ASI Integration and Verification Approach 4.2.1 ASI Verification Responsibilities

4.3 NASA/ASI Integration and Verification Approach

4.3.1 NASA/ASI Verification Matrix

4.4 Relationship between NASA and ASI Verification Management

4.5 NASA/ASI Verification Requirements

4.5.1 Verification Requirements

4.5.2 Responsibility Assignments

4.5.3 Verification Procedures and Methods (including software)

4.5.4 Verification Traceability and Close-out

4.5.5 Verification Assessment

4.5.6 Verification Certification

4.6 Node 2 Program Milestone Reviews

5.

Subsystem Verification

5.1 Subsystem Hardware/Software Integration Verification Approach

5.2 Subsystem Hardware Verification Approaches

5.2.1 Structural and Mechanisms Verification

5.2.2 Environmental Control and Life Support Subsystem (ECLSS) Verification

5.2.3 Thermal Control Subsystem (TCS) Verification

5.2.4 Avionics Subsystems Verification

5.2.5 Electromagnetic Compatibility (EMC) Verification Approach

5.3 Software Verification Approach

5.3.1 Joint Software Verification Test and Analysis

5.4 Ionizing Radiation Verification Approach

5.5 Crew Habitability

5.6 Flight Crew Interface Test Activities _______________________________ 44 6.

USOS Verification

6.1 Crew Systems Joint Verification Approach

6.2 Robotics Support Joint Verification Approach

7.

Ground Check-out of On Orbit Assemblies

7.1 Digital Pre-Assembly (DPA) Process

7.1.1 DPA Validation At NODE 2 / Other ISS Element Interfaces

7.2 Cable and Fluid Line Assessment

8.

Support Equipment

9.

Facilities

9.1 NASA Software Facilities

9.1.1 Software Development and Integration Laboratory (SDIL)

9.2 Space Power Electronics Lab (SPEL)

APPENDIX A: Definition of Terms

APPENDIX B: Abbreviations and Acronyms

APPENDIX C: Verification Matrix

APPENDIX D : EPS Verification Task Responsibility Matrix APPENDIX E: Video Requirements

FIGURES

8Figure 1.1 NASA/ASI Documentation

Figure 1.2 Verification Policy and Planning Documentation Tree Figure 4.1 ISS Program Phases and Milestones Figure 4.2 Summary of ASI Verification Process Figure 4.3 Node 2 Verification Control Document (VCD) Format (page 1 of 2) Figure 4.4 ASI Verification Traceability and Closeout Process Figure 4.5 NASA/Boeing Verification Traceability Process Figure 4.6 ASI Verification Data Format for Transfer to PVIS (page 1 of 2) Figure 4.7 ASI Verification Data Format for Transfer to PVIS (page 2 of 2)

1.

Purpose and Scope of the Document

The Node 2 NASA/ASI BIVP documents the agreements between NASA and ASI for the integration and verification of the Node 2 element into the United States on Orbit Segment (USOS) of the ISS as established in the NASA/ASI Joint Management Plan (JMP), SSP 50076.

This document defines the Agenzia Spaziale Italiana (ASI) and the NASA integration and verification activities and identifies the organizational elements involved in implementation of those activities including the responsibilities and involvement of both parties leading up to the delivery of the Node 2 element.

The activities defined in this plan address the verification tasks required to comply with the requirements in the Node 2 Prime Item Develop Specification (PIDS) SSP 50290, and to integrate the Node 2 with the USOS.

1.1 Precedence

This document is prepared in compliance with the NASA/ASI Memorandum of Understanding (MOU), NASA/ASI JMP, and the Node 2 PIDS. The NASA/ASI documentation and relationship to other program documentation is shown in Figure 1-1. These documents are jointly developed by NASA and ASI. They are intended to document the agreed to joint policies and processes. The Bilateral Plans are prepared within the guidelines provided in those documents. The Node 2 Bilateral Hardware/Software Exchange Agreements, Lists and Schedules (BHSEALS), SSP 50280 document reflects the bilateral agreements and decisions made as to the delivery or transfer of hardware and or software from one organization to another. It is a listing of actual hardware and software. The Node 2 Bilateral Data Exchange Agreements, List and Schedules (BDEALS ), SSP 50301 document reflects the bilateral decisions and agreements for the exchange of data. The MOU, JMP, or the Node 2 PIDS takes precedence in case of conflict with the Node-2 NASA/ASI BIVP.

The top level overall verification planning document for the International Space Station Program (ISSP) is documented in the Program Master Integration and Verification Plan (PMIVP), D684-10020-1. The Node 2 NASA/ASI BIVP shall comply with the NASA/ASI JMP and shall receive source data from PMIVP. The BIVP shall address the engineering and verification processes utilized. The verification documentation relationship between these documents and other verification documents is shown in the Verification Policy and Planning Documentation Tree (Figure 1-2).

1.2 Document Editing, Maintenance and Release Authority

The Node 2 NASA/ASI BIVP is controlled bilaterally, through approval signature, by the NASA International Space Station Program Office (ISSPO) Manager and the ASI Program Manager or their delegated authorities. The baseline BIVP shall be maintained by the NASA Configuration Management Office. Changes to the baseline BIVP must be dispositioned and approved by the NASA and ASI Space Station Managers or their authorized representatives following a review process in accordance with the process guidelines defined in NASA/ASI JMP SSP 50076.

Figure 1.1 NASA/ASI Documentatin

Figure 1.2 Verification Policy and Planning Documentation Tree

2.

Documents

The following documents are specified in their current version and any major changes made to the specified documentation shall be done with the visibility of both NASA and ASI.

2.1 Applicable Documents

Applicable documents are those documents which are considered authoritative in the context of this document. The first three listed will take precedence over the BIVP in case of conflict with the BIVP (as stated in 1.2). The remaining documents reflect the agreements made in the BIVP. When no revision or date is specified, the latest revision is considered applicable. The applicable revision shall be the one agreed to between NASA and ASI per the ISSP change processing.

DOCUMENT NO.

TITLE

No Number

Memorandum of Understanding between the United States National Aeronautics and Space Administration and the Italian Space Agency for the Design, Development, Operation and Utilization the Node 2 end item, SSP 50076

NASA/ASI Joint Management Plan (JMP)

SSP 50290

Node 2 Prime Item Development Specification (PIDS)

SSP 50301

Bilateral Data Exchange Agreements, Lists and Schedules for Node 2

(BDEALS)

SSP 50280

Node 2 Bilateral Hardware and Software Exchange Agreements, Lists and Schedules (BHSEALS)

2.2 Reference Documents

Reference documents are those documents which are sources of information which are helpful in developing the context of this document. Only documents called up in the text of this document are referenced here. When no revision or date is specified, the latest revision is considered applicable. The applicable revision shall be the one agreed to between NASA and ASI as per the ISSP change processing.

DOCUMENT NO.

TITLE

D684-10020-1

Program Master Integration and Verification Plan (PMIVP)

D684-10021

Program Verification Information System (PVIS)

Process Document

D684-10056-1

Software Standards and Procedures Specification

Document

NSTS 08117

Space Shuttle Requirements and Procedures for

Certification of Flight Readiness

NSTS 14046

Payload Verification Requirements

SW684-10022

Program Verification Information System (PVIS)

Software Requirements Specification

SSP 30233

Space Station Requirements for Materials and Processes

SSP 30459

ISS Interface Control Plan

SSP 41000

System Specification for ISS

SSP 41149

Berthing Visual Cues to Pressurized Elements Interface

Control Document

SSP 41162

Segment Specification for the United States on-Orbit

Segment Specification

SSP 41172

Environmental Qualification and Test Requirements

SSP 50017

Assembly Sequence and Manifest Document (AS&MD)

SSP 41174

ISS Interface Control Working Group (ICWG) Operating Procedures

SSP 42004

Mobile Serving System to User (Generic) Interface Control

Document

SSP 50005

Space Station Flight Crew Integration Requirements

(NASA-STD-3000/T)

SSP 50011

Concept of Operations and Utilization Document

SSP 50021

Safety Requirements for ISSP

SSP 50108

ISSP Certificate of Flight Readiness Process Document

SSP 50182

NASA/ASI Bilateral Safety and Product Assurance

Requirements

SSP 54500

International Ground System Specification Document

SSP 50263

Space Station Segment Specification

SSP 50123 Appendix Q

Configuration Management Handbook

N2-Pl-AI-0010

EME Control Plan

N2-PL-AI-0011

Node 2 Verification Plan

N2-VC-AI-0001

Verification Control Document

N2-PL-AI -0012

Node 2 Configuration and Data Management Plan

N2-RP-AI-0029

Node 2 Baseline Configuration Report

SSNPO-NC-0024

Node 2 Master Verification Plan

3.

International Space Station System Description

The ISS is an international endeavor being developed by the NASA, the National Space Development Agency of Japan (NASDA), the European Space Agency (ESA), the Agenzia Spaziale Italiana (ASI), the Canadian Space Agency (CSA), and the Russian Space Agency (RSA). The ISS consists of pressurized modules and unpressurized systems and elements that form a human base in low earth orbit. The ISS provides science capabilities for micro-gravity, materials, life science research and development, earth and stellar observation as well as other technology development and demonstration by the United States and the International Partners.

The ISS is comprised of the USOS, Ground Segment, ASI Italian Mini-pressurized Logistics Module (MPLM), ESA Attached Pressurized Module (APM), NASDA Japanese Experiment Module (JEM), RSA Russian Segment (RS), and the CSA Canadian Mobile Servicing System (MSS). The Node 2 is part of the USOS.

The ISS development is accomplished in stages using a pre-defined sequence of assembly flights. Every physical station configuration in each stage shall be verified. The assembly sequence flight numbers shall be used to reference the verification reporting. Changes within an assembly stage shall be considered in the verification of that stage. Changes to the assembly stage which require physical changes to the Node 2 will be processed through an ISSPO change process. The following represents a brief description of the relevant hardware for the USOS, and the Node 2 systems and interfaces involved in the verification process. For a description of the Node 2 systems and interfaces involved in the verification process, see the Node 2 Baseline Configuration Report, N2-RP-AI-0029.

3.1 On-Orbit Segment (USOS) Description

The USOS is an earth orbiting facility which houses experiment payloads, distributes resource utilities, and supports permanent human habitation for conducting research and science experiments in a micro-gravity environment. The USOS supplies the following services and capabilities to the ISS: electric power generation, storage, distribution and control; primary communications and data links to ground support facilities; environmental control and life support; thermal control and heat rejection; navigation and control; data processing; stowage and transportation; house keeping; personal hygiene; food preparation and storage; extravehicular activity access; payload utilities; attitude control; pointing support and robotics system control.

3.1.2 Ground Segment Description

The Ground Segment consists of the ground facilities, hardware, and software utilized in performance of the ground based support functions to the on-orbit Space Station. The Ground Segment provides the capability for the integration and verification of the ISS products (hardware, software, displays, procedures, and data). The Ground Segment provides ground based monitoring and command and control of the Station and user payloads. The Ground Segment provides the capability for training, operations planning, logistics, and for the processing of station equipment, payloads and waste returned from orbit.

The Ground Segment also provides support to other functions. The Ground Segment provides external interface functional support to the Space Shuttle Orbiter space transportation system, launch/landing site facilities, ground communication systems, and orbiting communication systems.

3.2 Node 2 Element Description

The Node 2 acts as a building block to connect other system elements; provide a pressurized passage way between berthed elements; and distribute / transfer commands and data, audio and video, electrical power, atmosphere, water, thermal energy to adjacent elements as an element of the USOS and provide locations for Crew Quarters. A detailed description of the Node 2 element is contained in the Node 2 Baseline Configuration Report, N2-RP-AI-0029.

ASI is responsible for constructing the Node 2 structure and integrating the hardware provided by NASA.

4.

Integration and Verification

The verification process for U.S. elements is put in place to implement and control processes that confirm that the ISS is compliant with specifications, properly functions as an integrated unit, and will serve its intended purpose. The BIVP is the documentation of the joint integration and verification activities established to ensure that the Node 2 complies with the Node 2 PIDS, applicable Interface Control Documents (ICDs), Interface Requirements Documents (IRD), and the integration of the Node 2 with the USOS.

Figure 4-1 depicts the ISS program phases and their relationship to program milestones as it relates to the Node 2 and also identifies the different verification activities that occur during each phase. The verification activities described within this document encompass the phases up to the Final Acceptance Review (AR).

4.1 Integration and Verification Approach

During the Performance and Functional Requirements Compliance Phase, specification requirements are defined, stage-assembly configurations are defined and developed from end items, and unique stage assembly configuration designs are qualified. The delivery of the integrated element shall be accomplished through the Functional Configuration Audit/Physical Configuration Audit (FCA/PCA) process documented in the Space Station Program Configuration Management Plan (D684-10097-1). Control and certification of the acceptance review process is an integral part of the quality assurance program per SSP 41173 Space Station Quality Assurance Requirements. An FCA is conducted to ensure specification requirements have been met by the design. PCA ensures that the hardware and software is built to the design.

In accordance with NASA/ASI Memorandum of Understanding, the Node 2 (Flight and Ground Support Equipment (GSE)) hardware and software shall be shipped and delivered to Kennedy Space Center (KSC) by ASI, who shall also be responsible for the post-delivery visual inspection of the flight article and transportation articles with the assistance of NASA, to ensure the equipment was not damaged or changed during shipment. As far as Alenia is concerned the Node 2 program addresses three specific reviews:

· Design Review 1 (DR-1)

· Design Review 2 (DR-2)

· Final Acceptance Review/Physical Configuration Audit (FAR/PCA)

In addition a post delivery review to be held after transportation to USA and relevant inspection. Post delivery inspection is limited to visual inspection and transportation items. The acceptance process will conclude with an FAR/PCA being conducted with ASI/Alenia as part of the delivery process of the Node 2 element to NASA.

Figure 4.1 ISS Program Phases and Milestones

The assembly and checkout phase encompasses launch package processing and the on-Orbit Assembly and Checkout (OACO) functions for the flight of the Node 2. Appropriate reviews shall be held by NASA to ensure that the necessary checkout demonstrations, and tests have been completed. After the ISSPO acceptance of the Node 2 at KSC, the data from the ASI FAR and other joint reviews will be used to support the endorsement statements for CoFR 1 and CoFR 2. The ISS CoFR 1 precedes the Payload Readiness Review (PRR) and CoFR 2 precedes the Flight Readiness Review (FRR). Refer to SSP 50108, Appendix C for the ASI ISS CoFR process requirements. National Space Transportation System (NSTS) CoFR, the CoFR for the Space Shuttle, NSTS 08117, defines the endorsement process for any element launched on NSTS. NASA will work directly with the NSTS office and support the NSTS CoFR process.

Verification data developed during the first three phases is used to support the Operations and Utilization Phase. This phase encompasses the developing ISS on-orbit configuration. Stage assemblies that require unique Node 2 capabilities will have requirements included in the SSP 50290.

4.1.1 NASA Responsibility

Under the U.S. portion of the verification approach, NASA is responsible for:

· Assuring that all the Node 2 requirements are verified by the appropriate parties in accordance with Appendix C.

· Management of the implementation of the ISSPO verification process

· Conducting ISS System program verification functions

· Certification that the on-orbit ISS is ready to support the Node 2

· Obtaining CoFR endorsements for Shuttle Launch Packages

· Integration and verification of the Node 2 into the launch package during launch processing at KSC

· Integration of the Node 2 into the integrated ISS

· Verification of all NSTS/USOS utility ports to Node 2 external interfaces

· Verification of control and data capabilities needed to support the Node 2

· Establishing and maintaining the ISS requirement and verification traceability from the top level ISS specification to the Node 2 PIDS

· Providing Certificate of Qualification (COQ) and Acceptance Data Package (ADP) for NASA Government Furnished Equipment (GFE) hardware, software, and firmware incorporated or used for the Node 2

· Development and Maintenance of the Node 2 NASA/ASI BDEA and BHSEALS

· Provision of items designated as NASA supplied according to the Node 2 BHSEALS

· Upon delivery of the Node 2 to NASA, NASA shall be responsible for the Node 2 and Node 2 GSE provided by ASI

· ISS end to end system verification and launch package verification

· Assurance that all GFE components have passed FCA/PCA

· Providing assistance to ASI for problems (failures) associated with NASA GFE

4.1.2 ISSP Test & Verification Team

The Integration Test and Verification (IT&V) Team in the Vehicle Office of the ISSPO is responsible for ISSP verification. The IT&V team develops and/or approves the following verification plans: PMIVP, NASA's Prime Contractor (Boeing) Integration and Verification Implementation Plan (I&VIP), and International BIVPs. The MSFC Nodes Project Office performs this task for the Vehicle Office on Nodes 2 & 3. In addition the IT&V team:

· provides a forum and verification focus to sub-system and discipline teams

· acts as a focal point and conveys unique needs for verification activity

· provides access to verification mechanisms

· ensures sub-system and discipline teams receive appropriate reports (type and content)

· verification/test assessment

· PVIS development, training, and maintenance

4.2 ASI Integration and Verification Approach

ASI responsibility for the Node 2 verification encompasses Development phase, Qualification phase, and Flight Article Acceptance. The primary objectives to be accomplished by the verification program during the above phases include:

· support the design development

· certification that the design fulfills all specified requirements and therefore is qualified

· demonstration that the delivered hardware and software is free of workmanship defects and performs as specified

The verification process begins with the translation of design and performance requirements (documented in the specifications) into verification requirements, i.e., with the allocation of these requirements to the appropriate method of resolution. With this determination, the objectives and conditions for analysis and/or testing/demonstration/inspection are established, forming the basis for preparation of plans, specifications and procedures.

Alenia will utilize component test data for all final analyses that shows the correlation between the analysis and test data. This is acceptable to Alenia provided that the component test data is within the specification values for the component. If the test data is not within the specification values for the component, then Alenia will re-perform the analysis, utilizing the component test data in place of the component specification values. This method will provide compliance to the Node 2 PIDS section 4 requirements.

The results of the analysis, inspection, demonstration and test activities are evaluated against the established requirements. Confirmation of the satisfaction of each requirement provides an increment in the verification process. A summary of the ASI verification process is presented in Figure 4-2. The flow shown is valid for qualification and acceptance, considering that analysis and inspection of documents are clearly applicable only for qualification purposes.

The practical implementation of the verification program is accomplished by establishing and maintaining the Verification Control Documents (VCDs). VCDs are those documents used to plan, control and report status/completion of verification activities.

Verification Control Document (VCD) structure is shown in Figure 4-3 and the document shall be prepared as required indicating:

· specification text

· verification method at the applicable level

· applicable verification phase

· applicable execution document (specification, procedure, etc.)

· verification reporting document (verification reports, inspection reports, analysis reports, test/demonstration reports)

· supporting information (approved request for waivers, comments, etc.)

· verification compliance and approval status

The VCD will contain this information for all PIDS requirements, with the NASA information being provided to ASI. The VCD data will be a part of the Verification Data Base (VDB) whose automation will be maximized. Format and content of this Data Base, to be delivered to NASA, are detailed in paragraph 4.5.4.6 PVIS Data Format.

For all GFE, including ISS common equipment and software, the ISSP verification approach will be used and is not the responsibility of ASI. All the verification documents related to GFE (including equipment level compliance data) are provided by NASA. Traceability from the above items to the Node 2 PIDS in PVIS will be accomplished by NASA.

The ASI - provided end items verification campaign is considered concluded when the module is accepted and delivered to NASA.

Figure 4.2 Summary of ASI Verification Process

¦ ¦ ¦ VERIFICATION CONTROL DOCUMENT ¦

¦ ¦ ¦ DOC.NR. : N2-VC-AI-0001 PHASE : PROTOFLIGHT ¦

¦ ¦ ¦ ISSUE ..: 02 REVISION : DATE .: 28/APR/98 PAGE : 1 of 2 ¦

LEGENDA :

* Verification Levels :

- A1 = ALENIA RESP-ELEMENT

- A2 = NASA RESP-ELEMENT

- B1 = ALENIA RESP-EQUIPMENT

- B2 = NASA RESP-EQUIPMENT

* Verification Methods :

- T = TEST

- A = ANALYSIS

- I = INSPECTION

- D = DEMONSTRATION

* Verification Notes :

- N/A = NOT APPLICABLE

- TBD = TO BE DEFINED

- N/R = NOT REQUIRED

- I/O = INFO ONLY

Figure 4.3 Node 2 Verification Control Document (VCD) Format (page 1 of 2)

Figure 4.3 Node 2 Verification Control Document (VCD) Format (page 2 of 2)

4.2.1 ASI Verification Responsibilities

ASI shall integrate and verify the Node 2 in accordance with this BIVP. ASI shall also provide traceability in accordance with this BIVP. ASI shall support assembly and checkout of the Node 2 element as agreed to in joint NASA/ASI documentation. The integration and verification planning and status shall be provided to NASA for incorporation into the PVIS. PVIS is the database used to provide traceability and verification close-out data. ASI will provide traceability for ASI controlled equipment. ASI responsibilities include:

· qualification and acceptance verification of the Node 2 element and ASI provided Ground Systems

· Verification of ASI provided GSE

· Support of the ISSP and NSTS CoFr processes and endorsements to the Node 2

· Integration of the results of verification activities into Node 2 program reviews

· Qualification of the Node 2 to the PIDS

· Provision of verification data to the NASA/MSFC

· The ASI witnessing at Node 2 stage testing in the SVF, if necessary, will be negotiated at the appropriate time.

· Support activities at the KSC as agreed to by NASA and Alenia

· The PCA will be a part of the FAR

· Generation and provision of Acceptance Data Packages for the Node 2 on element delivery

· Provision of test and checkout requirements for launch/landing site processing

4.3 NASA/ASI Integration and Verification Approach

Both NASA and ASI are jointly responsible for the following:

· Exchange of data, hardware and software per agreed to bilateral agreements (BHSEALS and BDEA)

· Monitoring NASA/ASI bilateral activities and maintaining NASA/ASI data exchange agreements

· Supporting joint testing of agreed to interfaces/subsystems

4.3.1 NASA/ASI Verification Matrix

Design and development requirements for the Node 2 are contained in the Node 2 PIDS, SSP 50290 Rev C. Section 4.0 of the PIDS contains the Node 2 verification requirements, and is the basis for verification. A verification matrix allocating responsibility for verification of those requirements is presented in Appendix C. These allocations have been agreed to by all parties. Those section 4.0 paragraphs which have joint assigned verification tasks responsibility according to the matrix are elucidated upon in this document.

4.4 Relationship between NASA and ASI Verification Management

The NASA IT&V team shall participate in Node 2 program reviews held by ASI. The NASA IT&V team leader may be a member of these review boards. The IT&V team shall provide personnel to perform reviews of verification related material. The NASA IT&V team shall coordinate support for verification assessment and for joint test activities and aid in identification of those tests which require Boeing support. In addition the IT&V team shall provide ASI with access to program verification data, databases and documentation, and aid in resolution of integration and verification issues.

4.5 NASA/ASI Verification Requirements

ASI chairs the Verification Control Board at the Node 2 Element Level, for reviewing verification status and results, and reviewing and approving VCDs below the element level. NASA will review and approve the element level verification test plans, the verification specification, the verification procedures, the verification reports, and the element level VCDs. NASA chairs the Node 2 system reviews which shall include verification reviews and are:

· Reference Configuration Review (RCR)

· Design Reviews (DRs)

· Final Acceptance Reivew/Physical Configuration Audit (FAR/PCA)

During the Flight Article Acceptance Phase which concludes with the Final Acceptance Review in Italy, an ADP for each hardware item and software delivery shall be exchanged between NASA and ASI, in accordance with NASA/ASI JMP, SSP 50076. Section 3.1.4.5 of that JMP describes the purpose, content, and responsibilities of NASA and ASI in the generation, delivery and maintenance of the ADPs. The mutually agreed to data items in the ADPs accompanying each hardware and software delivery are defined in the Node 2 NASA/ASI BDEA, SSP 50301.

Problems (failures) found during acceptance testing shall be reported under the Problem Reporting and Corrective Action (PRCA) system. The PRCA system is to ensure the proper identification, reporting, disposition and control of failures. It provides for the mutual reporting and joint resolution of failures affecting the Node 2 to ISS functional/physical interfaces and critical systems. The dispositions shall be jointly agreed upon by ASI and NASA. The data exchange of failure reports shall be in accordance with the Node 2 NASA/ASI BDEA, SSP 50301.

In addition to formal reviews and data delivery, NASA, with support from Boeing, shall perform verification assessment activities (see section 4.5.5) and assist ASI in the certification of the Node 2 Element.

4.5.1 Verification Requirements

For the Node 2 Program, design and development requirements are contained in the Node 2 PIDS, SSP 50290. External design interface requirements are detailed in the ICDs and are referenced in the Node 2 PIDS. The closeout verification of ICD requirements are accomplished through closeout of the PIDS requirements that reference these requirements. Section 3.0 of the PIDS contains the Node 2 requirements that shall be used to build the element. Section 4.0 of the PIDS contains the Node 2 qualification and verification requirements and is the basis for verification and traceability.

The Node 2 PIDS requirements constitute the starting point for lower level specifications. The ASI lower level Node 2 specifications contain traceability data with respect to upper level specifications, for each design requirement (i.e. section 3.0 requirements). Software specifications are prepared in-line with DOD-STD-2167A.

Changes to the Node 2 PIDS shall be controlled by the Configuration Management Handbook, SSP 50123.

4.5.2 Responsibility Assignments

4.5.2.1 NASA/Boeing Verification Interfaces

The NASA/MSFC Node 2 Project Office shall interface with ASI and its contractor on the subject of verification.

4.5.2.2 ASI Verification Interfaces

ASI and its contractor shall interface with the NASA/MSFC Node 2 Project Office on the subject of verification.

4.5.3 Verification Procedures and Methods (including software)

The U. S. verification procedure for the ISS is described in the PMIVP. The objective of the verification procedure is to ensure that all of the requirements have been met. The U. S. verification methods, as documented in the ISS PMIVP, are analysis, inspection, test and demonstration.

4.5.3.1 Analysis

The analysis verification method is normally used during the qualification phase, very often in combination with test. Different methodologies include:

· Functional analysis

· Mathematical modeling

· Qualitative analysis

· Similarity analysis

For verification by analysis to be selected, the physical system must be modeled and the model used must be described and its use justified. The analysis boundary conditions and assumptions must be known and stated, the nominal and worst case conditions must be evaluated, and the range of validity must be specified. In addition, the analysis must show that the specified performance is exceeded by the amount of uncertainty in the analysis. Analysis may be used whenever any of the following apply:

· The spectrum of flight conditions cannot be simulated adequately on the ground and it is necessary to extrapolate test data beyond the performed test points.

· It is not cost effective to test.

· It is necessary to confirm that software complies with applicable coding standards. This can also be accomplished by inspection with documentation of the results of the inspection.

· It is desired to determine closure status of verification activities being performed at lower levels of assembly to support closures at higher levels.

4.5.3.2 Inspection

Inspection shall mainly be utilized to verify those requirements where physical interface characteristics are involved. Safety hazard controls may also be verified by inspection methods. Inspection methods shall be utilized even for those requirements where a revision of the documentation is necessary. Main areas where verification by inspection shall be performed at the element level are the physical configurations, interfaces, leakage and mechanisms.

4.5.3.3 Test and Demonstration

As specified in the Node 2 PIDS paragraph 4.0, the quality assurance provisions and qualification requirements are detailed in the 4.3 section of the specification. Test programs shall be designed to demonstrate full functionality of the complete element in nominal and limit conditions. Ad hoc simulators of the external element/equipment interfacing with the module shall be utilized during these tests, as required, to verify Node 2 interfaces. All requirements with safety impacts shall be demonstrated or tested. A full acceptance test program shall be conducted on the assembled Node 2 end item.

4.5.4 Verification Traceability and Close-out

The process for verification traceability and close-out of Node 2 PIDS requirements is shown in Figure 4-4. NASA shall establish and maintain the traceability from the Node 2 PIDS requirements to the USOS specification requirements in the PVIS database.

NASA shall provide traceability from Node 2 PIDS. ASI shall provide the verification traceability and close-out data for the ASI responsible verification requirements, in the Node 2 PIDS via NASA, to the PVIS database. NASA shall be responsible for all remaining verification requirements.

Figure 4.4 ASI Verification Traceability and Closeout Process

Figure 4.4 ASI Verification Traceability and Closeout Process 4.5.4.1 Program Verification Information System (PVIS)

The PVIS is an automated database that provides the ISSP the capability to track the large amounts of technical and programmatic data associated with the ISSP verification process. The PVIS database uses the Requirements and Traceability Management (RTM) software application to provide the traceability of ISS specification requirements, verification requirements, verification objectives, verification plans, verification activities, verification reports, and verification closure documentation to ensure that all program requirements have been satisfied. The NASA/Boeing Contractor’s verification traceability process is shown in Figure 4-5. The PVIS database shall track specification requirements to closure by referencing the specific verification report that documents the successful verification of each requirement.

Status reports are available from the PVIS database to allow ISSP management, including ASI, to assess the status of the ISSP verification process.

The PVIS database is defined in the PVIS Process Document (D684-10021-1), and the PVIS Software Requirements Specification (SW684-10022-01).

4.5.4.2 PVIS Node 2 Requirement Traceability Data

Traceability data shall be developed and maintained by ASI for the four lower level specifications that ASI is responsible for. Compliance data will be provided by ASI as per Figure 4-3.

Figure 4.5 NASA/Boeing Verification Traceability Process 4.5.4.3 PVIS Data Format

ASI shall have "read-only" access to the PVIS database remotely from Italy. Node 2 verification data shall be transferred electronically from ASI to NASA and loaded into the PVIS database by NASA. Figures 4-6a and b represent a typical format for transferring this data from the VCD database to the PVIS database.

4.5.4.4 ASI to PVIS Database Configuration

ASI shall provide the associated hardware required to interface with the PVIS database. NASA shall provide any required training for searching and retrieving requirements and verification traceability data into the PVIS database.

4.5.5 Verification Assessment

An agreed upon matrix allocating close out responsibility for specific verification tasks between NASA/Boeing and ASI/Alenia and their respective representatives is defined in Appendix C.

The agreed intent of verification assessments shall be to ensure that the established PIDS verification requirements are satisfied. All verification assessments shall be coordinated by the NASA/ASI verification teams. When ASI testing/demonstration is required to satisfy a PIDS verification requirement, NASA and/or their appointed representative reserves the right to witness or monitor the verification activities, review verification analyses, and perform an assessment to ensure that the documented results shall be sufficient to support the closure of the verification requirement. When ASI performs analyses or inspections for a PIDS verification requirement, NASA and/or their appointed representative also reserves the right to monitor and review the verification activities and perform an assessment.

For verification tasks which involve both agencies, one agency has been given the closeout responsibility according to Appendix C, while the Appendix may also specify allocated tasks for more than one party within that task. Test plans/procedures will be the responsibility of the agency performing the test according to Appendix C. When a NASA verification activity is indicated, to be conducted in Italy, a case by case course of actions and associated responsibilities have to be agreed to by both parties. NASA has the responsibility to ensure all verification requirements are accomplished with sufficient rigor to support the Node 2 (CoFR) endorsements.

Figure 4.6 ASI Verification Data Format for Transfer to PVIS (page 1 of 2)

Figure 4.7 ASI Verification Data Format for Transfer to PVIS (page 2 of 2)

4.5.6 Verification Certification

Certification is defined as a culmination of verification activities which confirms that all verification requirements were met. Verification certification shall be accomplished by ASI for ASI responsible verification requirements. NASA verification management will participate in the review of delivered verification data as defined in this document. In addition to participation in these Node 2 program reviews, the NASA IT&V team manager will provide test and verification manpower for these reviews.

The MSFC Node 2 Project Office is responsible for all verification assessment efforts and reports. Verification assessment reports will be an addition to verification/certification documentation. ASI will provide documentation as evidence of completion leading to certification per the NASA/ASI BDEA.

For all joint tasks, the appropriate verification methods for a given task, as described in the PIDS and Appendix C of the BIVP, will be performed by the assigned parties. Joint tasks are defined as those verification activities which have tasks performed by both agencies and have an equal level of responsibility. In this case, a final verification closure analysis must be performed by NASA, specifically by the appropriate technical team with appropriate Program Management approval. Test plans will remain the responsibility of the agency performing the test. Information from the VCDs are then transferred to PVIS by NASA.

The Node 2 will be accepted in the following procedure: The Final Acceptance Review for Node 2 will be held in Italy. Any ASI responsible verification tasks left open at the FAR will be discussed between ASI and NASA to determine resolution. Open work under NASA responsibility to be resolved in the U.S. will be concluded after shipment of the Node 2 with ASI support. Acceptance data will be added to the ADP by the responsible agency.

4.5.6.1 Launch Vehicle Certificate of Flight Readiness

The CoFR for the Space Shuttle, as defined in NSTS 08117, is the document which is signed at designated review points during the preparation for flight. For the Node 2, NASA is the responsible organization for launch vehicle CoFR process with ASI support.

4.5.6.2 ISS Certificate of Flight Readiness

The CoFR for the ISS is the formal document which attests to the successful accomplishment of the work required to safely support on-orbit operation of the ISS. Within the ISSP CoFR process, the CoFR 1 attests to the readiness for Launch Package integration into the Launch Vehicle, and the CoFR 2 attests to the readiness for launch and on-orbit operations. The ISSP CoFR process shall be controlled by the ISS Program Manager.

For the Node 2, ASI will provide the ADP to certify it has been properly completed, reviewed and judged to be ready to support assembly, launch, activation, operation and utilization of the ISS.

4.6 Node 2 Program Milestone Reviews

Detailed schedules will be provided by ASI to NASA on the development, manufacturing, and verification for the ASI/Alenia activities. NASA will work with ASI to schedule the major program milestone reviews as identified below. The Node 2 program is divided into main phases at the end of which, reviews are conducted to ascertain the status and provide authorization on continuation of the activities. The following activities occur through development and documentation of requirements to the final acceptance of hardware/software from ASI. Typical reviews planned for Node 2 are:

· RCR: performance and functional requirements have been properly flowed down into the system and sub-system design. This is conducted by ASI with participation by NASA;

· DR1: Node 2 structural design has been defined and flight configuration design can be integrated and tested. This is conducted by ASI with participation by NASA;

· DR2: Node 2 critical designs (subsystems and integrated subsystems) has been defined and flight configuration design can be integrated and tested. This review is conducted by both NASA and ASI;

· FAR/PCA: The ASI allocated requirements as defined in the Node 2 PIDS have been met as a consequence of the successful functional verification configuration of the item. This is conducted after the completion of the verification phase. This audit is conducted by NASA on ASI hardware/software with ASI participation. In addition, it certifies that the hardware and software have been designed with no defects. It formally establishes and documents the exact configuration of each item of hardware and software at the time of acceptance. This review is conducted by NASA with participation by ASI;

Detailed schedules are provided by NASA to ASI of the mission integration activities as defined in the ISS Mission Integration Plans (MIP). The MIP reviews are held primarily to ascertain that the mission specific configuration of the integrated Node 2 PIDS have positive margins of safety considering all launch, landing and on-orbit environments have adequately met the requirements of NSTS 14046.

5.

Subsystem Verification

5.1 Subsystem Hardware/Software Integration Verification Approach

In the Node 2 element configuration, where flight hardware/software have been integrated, tests shall be performed to validate the flight hardware/software in Italy. Both NASA and ASI will participate in the test which can be considered part of Node 2 end-item testing. Data will be taken during these tests to support all necessary hardware and software analyses. Test control equipment shall be used as required to effectively perform each test. NASA has the responsibility to perform software trouble shooting and patching during this phase of verification. NASA is responsible for the flight software provided to ASI. The remainder of the responsibilities belong to ASI.

5.2 Subsystem Hardware Verification Approaches

This section contains summary level descriptions of subsystem verification approaches relevant to the Node 2 to the ISS stage configurations. Further detailed planning and agreements leading to the eventual implementation of verification activities will be documented in the test plans and test procedures. Agreements necessary for the successful exchange of data, hardware, and software between NASA and ASI required for the integration and verification activities agreed by this plan will be documented in the Node 2 NASA/ASI BDEALS, SSP 50280.

5.2.1 Structural and Mechanisms Verification

5.2.1.1 Structural Qualification

Qualification of the Node 2 structure will be by a combination of analysis and test. A stress analysis of each component per SSP 30559 will be performed to verify that positive margins of safety exist at yield and ultimate load levels. Fracture and fatigue analysis per SSP 30558 shall be performed to verify that the structure has adequate service life. The analysis will be supplemented by the following static and dynamic tests.

5.2.1.1.1 Node 2 Flight Article Proof Pressure Test

The Node 2 flight article will be proof pressure tested to 22.8 psid to verify structural integrity of the pressure shell. Flight CBMs (structural rings) and flight hatches will be installed on all radial and axial ports. An analysis will be performed by ASI to determine the secondary structure required to be installed to replicate the primary load paths of the integrated flight article. The proof pressure test will be repeated in the open hatch configuration with closeouts on all of the CBM rings. Alenia will provide closeouts for the open hatch configuration. Flight CBMs (structural rings) and hatches will be provided as GFE.

5.2.1.1.2 Node 2 Flight Article Pressure Decay Test

The Node 2 flight article will undergo a pressure decay test to verify that PIDS paragraphs are met. Flight CBMs (structural rings) and hatches will be installed on all radial and axial ports. The test, performed by ASI/Alenia, will be conducted at 14.7 psid in two configurations; all hatches closed, and all hatches open. The open hatch leak test will be performed with closeouts on all CBM rings.

The leakage of the non-redundant seals (e.g. Valves, sensors, etc.) will be verified by local leak tests. The total leakage will be the sum of that obtained from the local and global leak tests. Global level is the module level and the local level is the equipment (penetration items) level. Alenia will perform leak check tests after installation of equipment and utilize leak check data from manufacturers. Alenia will perform leak check tests on equipment/components installed on the Node 2. Alenia will use test procedures for vendor equipment that are provided by the vendor. Alenia will perform an acceptance leak check test of the hatch and CBM to pressurized element after installation in accordance with vendor provided installation procedures.

5.2.1.1.3 Node 2 Static Test Article (STA) Proof Pressure Test The Node 2 STA will be a closed cylinder comprised of two adjacent radial port sections, an end cone, two forged CBM rings, and two hatches. The Node 2 STA will be proof pressure tested by Alenia to 22.8 psid to verify structural integrity of the pressure shell, hatches, and rings. An analysis will be performed by Alenia to determine the secondary structure required to be installed to replicate the primary load paths of the integrated flight article. The proof pressure test will be repeated in the open hatch configuration with closeouts on all of the CBM rings.

5.2.1.1.4 Node 2 STA Ultimate Pressure Test

After all previous structural testing has been completed. Alenia will perform a Node 2 STA ultimate pressure test to 30.4 (TBR) psid in hatch open configuration.