SSP_50347-Rev_B-DCN002-CollatedMaster.docx

NODE 3 NASA/ESA BILATERAL INTEGRATION & VERIFICATION PLAN

INTERNATIONAL SPACE STATION PROGRAM

Revision B September 2009

Incorporates DCN 002

Space Administration

Program Office

Houston, Texas

SSP 50347

Revision B

CR_011403_ATTB

DRAFT

)SSP 50347 Revision A December 14, 2006

PREFACE

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

The Node 3 NASA/ESA BIVP equally applies to the NASA and the ESA. This document is under the control of the Space Station Control Board (SSCB) with the concurrence of ESA. Any changes or revisions will be approved by the SSCB and ESA.

In late spring 2004, before the baselining of this document, it was decided to tranfer the management of the Node 2/3 project from the Agenzia Spaziale Italiana (ASI) to ESA. For simplicity, this document only reflects the latest interfacing organizations, i.e., NASA and ESA. However, it should be pointed out that exchanges performed prior to that event were performed between NASA and ASI.

i

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

NASA/ESA BILATERAL INTEGRATION AND VERIFICATION PLAN

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

NASA/ESA BILATERAL INTEGRATION AND VERIFICATION PLAN

REVISION AND HISTORY PAGE

DATE

Revision A incorporates the following: CR9713C, CR9977A, and administrative edits.

12/14/2006

SSP 50347 December 22, 2010

TABLE OF CONTENTS

DCN 00

FIGURES

SSP 50347 December 22, 2010

1. Purpose and Scope of the Document

The Node 3 NASA/ESA Bilateral Integration and Verification Plan (BIVP) documents the agreements between NASA and ESA for the integration and verification of the Node 3 element into the United States On-orbit Segment (USOS) of the ISS as established in the SSP 50698, NASA/ESA Nodes 2/3 Project Joint Implementation Plan (JIP).

This document defines the ESA 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 in the design, development and post-delivery activities of the Node 3 element.

The activities defined in this plan address the verification tasks required to comply with the requirements in the SSP 50318, Prime Item Development Specification for Node 3 and to integrate the Node 3 with the USOS.

1.1 Precedence

This document is prepared in compliance with the JIP and the Node 3 Prime Item Development Specification (PIDS). The NASA/ESA documentation and relationship to other program documentation is shown in Figure 1-1. These documents are jointly developed by NASA and ESA. 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 SSP 50528, Node 3 Bilateral Hardware and Software Exchange Agreement Lists and Schedules, 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 SSP 50359, Node 3 Bilateral Data Exchange Agreements, Lists and Schedules , document reflects the bilateral decisions and agreements for the exchange of data. The JIP or the Node 3 PIDS takes precedence in case of conflict with the Node 3 NASA/ESA BIVP.

The top level overall verification planning document for the International Space Station (ISS) Program is documented in the D684-10020-1, Program Master Integration and Verification Plan (PMIVP). The Node 3 NASA/ESA BIVP shall comply with the JIP 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 3 NASA/ESA BIVP is controlled bilaterally, through approval signature, by the NASA ISS Program Office Manager and the ESA 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 ESA Space Station Managers or their authorized representatives following a review process in accordance with the process guidelines defined in the JIP.

Figure 1-1 Documentation

NASA/ESA

Nodes 2/3 Project Joint Implementation Plan SSP 50698

Program Master Integration and Verification Plan D684-10020-1

NASA/ESA Bilateral Integration and Verification Plan (BIVP)

SSP50347

Node 3 Prime Item Development Specification

SSP 50318

Node 3 Verification Plan

N3-PL-AI0008

Node 3 Ground Operations Definition Plan, SSP 50732

Node 3 Integrated Test and Verification Plan D683-53475 -1

DRAFT July 18, 1997

SSP 50347

Revision B 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 ESA.

2.1 Applicable Documents

Applicable documents are those documents that are considered authoritative in the context of this document. The first two 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 ESA per the ISS Program change processing.

DOCUMENT NO. TITLE

SSP 50698 NASA/ESA Nodes 2/3 Project Joint Implementation Plan Basic September 17, 2004

SSP 50318 Prime Item Development Specification for Node 3 Rev. G

TBD

SSP 50200-10 Station Program Implementation Plan, Volume 10:

Sustaining Engineering

December 14, 2006

TBD (CR11386)

KPL-LSSP-21549 Node 3 Launch Site Support Plan Basic April 2009

2.2 Reference Documents

Reference documents are those documents that are sources of information 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 ESA as per the ISS Program change processing.

DOCUMENT NO. TITLE

D683-53475-1 Node 3 Integrated Test and Verification Plan

D684-10020-1 Program Master Integration and Verification Plan (PMIVP)

D684-10021-1 Program Verification Information System (PVIS) Process Document

D684-10097-1 Space Station Program Configuration Management Plan

NSTS 08117 Space Shuttle Requirements and Procedures for Certification of Flight Readiness

NSTS 14046 Payload Verification Requirements

SW684-10022-1 Program Verification Information System (PVIS) Software Requirements Specification

SSP 30459 International Space Station Interface Control Plan

SSP 30558 Fracture Control Requirements for Space Station

SSP 30559 Structural Design and Verification Requirements

SSP 30560 Glass, Window, and Ceramic Structural Design and Verification Requirements

SSP 41172 Qualification and Acceptance Environmental Test Requirements

SSP 41173 Space Station Quality Assurance Requirements

DOCUMENT NO. TITLE

SSP 42004 Mobile Serving System (MSS) to User (Generic) Interface Control Document

SSP 50108 Certificate of Flight Readiness Process Document

SSP 50123 Configuration Management Handbook

N3-RP-AI-0009 Node 3 Baseline Configuration Report (TASI)

N3-RP-AI-0030 Node 3 MDM Connectivity (TASI)

N3-PL-AI-0008 Node 3 Verification Plan (TASI)

DOD-STD-2167A Defense System Software Development (Refer to MIL-STD-498, Software Development and Documentation)

MIL-STD-1553B Digital Time Division Command/Response Multiplex Data Bus

SSNPO-N3-0003 Node 3 Electromagnetic Environments (EME) Control Plan

SSNPO-N3-0033 Node 3 Labels Plan

N3-PL-AI-0019 Closeout for Flight Plan (TASI)

3. International Space Station System Description

The ISS is an international endeavor being developed by the NASA, the Japan Aerospace Exploration Agency (JAXA), the European Space Agency (ESA), the Agenzia Spaziale Italiana (ASI), the Canadian Space Agency (CSA), and the Russian Federal Space Agency (Roscosmos). 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), JAXA Japanese Experiment Module (JEM), Roscosmos Russian Segment (RS), and the CSA Canadian Mobile Servicing System (MSS).

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 that require physical changes to the Node 3 will be processed through an ISS Program Office change process. For a description of the Node 3 systems and interfaces involved in the verification process, see the N3-RP-AI-0009, Node 3 Baseline Configuration Report.

3.1 United States 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; extravehicular activity access; payload utilities; attitude control; pointing support and robotics system control.

3.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.3 Node 3 Element Description

A detailed description of Node 3 is contained in the N3-RP-AI-0009, Node 3 Baseline Configuration Report.

4. Integration and Verification

The verification process for the United States (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 3 complies with the Node 3 PIDS, applicable Interface Control Documents (ICDs), and capable of integration with the USOS.

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 Acceptance Review Board process documented in the JIP

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

· Reference Configuration Review (RCR)

· Design Review 1 (DR-1)

· Design Review 2 (DR-2)

· Pre-shipment Acceptance Review (PAR)

· Acceptance Review Board (ARB)

Post-delivery inspection is limited to visual inspection and transportation items. The acceptance process will conclude with the ARB being conducted with ESA/TASI as part of the delivery process of the Node 3 element to NASA.

TASI will be responsible for ground operations processing as detailed in the KPL-LSSP-21549, the Node 3 Launch Site Support Plan.

There will be PIDS requirements that cannot be verified until completion of the final integration activities. The assembly and checkout phase encompasses launch package processing and the On-orbit Assembly and Checkout (OACO) functions for the flight of the Node 3. Appropriate reviews shall be held by NASA to ensure that the necessary checkout demonstrations and tests have been completed. After the ISS Program Office acceptance of the Node 3 at KSC, the data from the joint reviews will be used to support the endorsement statements for the Certification of Flight Readiness (CoFR) 1 and CoFR 2 per the JIP. The ISS CoFR 1 precedes the Payload Readiness Review (PRR) and CoFR 2 precedes the Flight Readiness Review (FRR). Refer to SSP 50108, Certificate of Flight Readiness Process Document, Appendix E for the ESA ISS CoFR process requirements. NSTS 08117, Space Shuttle Requirements and Procedures for Certification of Flight Readiness, defines the endorsement process for any element launched on the National Space Transportation System (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 3 capabilities will have requirements included in SSP 50318.

4.1.1 NASA Responsibility

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

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

· Management of the implementation of the ISS Program Office verification process

· Conducting ISS System program verification functions

· Maintenance of the Verification Control Document (VCD) after ARB to completion of Node 3 PIDS verification activities

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

· Obtaining CoFR endorsements for Shuttle Launch Packages

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

· Integration of the Node 3 into the integrated ISS

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

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

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

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

· Development and Maintenance of the Node 3 Bilateral Data Exhange Agreements, Lists, and Schedules (BDEALS) and Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules (BHSEALS)

· Development and Maintenance of the Node 3 Ground Operations Definition Plan

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

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

· ISS end to end system verification and launch package verification

· Assurance that all GFE components shipped to ESA have passed Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA)

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

· On-Orbit integration of the Atmosphere Revitalization System (ARS), Oxygen Generation System (OGS), Water Recovery System (WRS)#1, and WRS#2 Racks

4.1.2 ISS Program Test & Verification Team

The Integration Test and Verification (IT&V) Team in the Vehicle Office of the ISS Program Office is responsible for ISS Program verification. The IT&V team develops and/or approves the following verification plans: PMIVP, and NASA's Prime Contractor (Boeing) D683-53475-1, Node 3 Integrated Test and Verification Plan, and International BIVPs. 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

· Program Verification Information System (PVIS) development, training, and maintenance

4.1.3 Deleted

4.1.3.1 Closed for Flight

ESA will provide a Closed for Flight Plan and provide evidence at PAR that this plan has been implemented to ensure that the Node 3 requirements for Closed Out for Flight have been met to the extent possible at delivery.

4.2 ESA Integration and Verification Approach

ESA responsibility for the Node 3 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 for the functions tested at Alcatel Alenia Space Italia S.p.A. (TASI).

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.

TASI will utilize component test data for all final analyses that shows the correlation between the analysis and test data. This is acceptable to TASI 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 ESA/TASI 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 3 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 ESA verification process is presented in Figure 4-1. The flow shown is valid for qualification and acceptance, considering that analysis and inspection of documents are clearly applicable only for qualification purposes.

Figure 4-1 Summary of ESA Verification Process

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

The VCD will contain this information for all PIDS requirements, with the NASA information being provided to ESA via Letters of Transmittal. 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.4.4.2, PVIS Data Format.

For all NASA provided GFE, including ISS common equipment and software, the ISS PROGRAM verification approach will be used and is not the responsibility of ESA. ESA is responsible for ensuring that ESA provided GFE meets ISS Program verification standards. All the verification documents related to GFE (including equipment level compliance data) are provided by the NASA. Traceability from the above items to the Node 3 PIDS in PVIS will be accomplished by the NASA.

The ESA provided end items verification campaign, including VCD maintenance, is considered concluded when the module is accepted and delivered to NASA.

Alcatel Alenia Space Italia S.p.A.

NODE 2&3

PIDS for Node 3 - V C D

DOC. : N3-VC-AI-0001

CLASS:

Spec. Number : SSP50318 Level : 1 - Phase : PTF Title : PIDS for Node 3 Issue : - -

Figure 4-2 Node 3 VCD Format

Revision B

4.2.1 ESA Verification Responsibilities

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

· Qualification and acceptance verification of the Node 3 Partially Integrated Element –Two avionics racks at ESA/TASI provided Ground Systems and follow-on support for qualification and acceptance of the Node 3 Element support per SSP 50732, Ground Operations Definition Plan.

· Verification of ESA provided GSE

· Support of the ISS Program and NSTS CoFR processes and endorsements to the Node 3

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

· Qualification of the Node 3 to the PIDS

· Provision of verification data to the NASA

· The ESA witnessing at Node 3 stage testing in the Software Verification Facility (SVF), if necessary, will be negotiated at the appropriate time.

· Support activities at the KSC as agreed to by NASA and ESA/TASI

· Support for the ARB

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

· Provision of test and checkout requirements for launch/landing site processing support as defined in SSP 50732.

· Closeout of Node 3 for flight per TASI’s N3-PL-AI-0019, Closeout for Flight Plan.

4.2.2 NASA/ESA Integration and Verification Approach

Both NASA and ESA are jointly responsible for the following:

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

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

· Supporting joint testing of agreed to interfaces/subsystems

4.2.3 NASA/ESA Verification Matrix

Design and development requirements for the Node 3 are contained in the SSP 50318, Node 3 PIDS. Section 4.0 of the PIDS contains the Node 3 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 that have joint assigned verification tasks responsibility according to the matrix are elucidated upon in this document.

4.2.4 Deleted.

4.3 Relationship between NASA and ESA Verification Management

The NASA IT&V team shall participate in Node 3 program reviews held by ESA. 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 that require Boeing support. In addition, the IT&V team shall provide ESA with access to program verification data, databases and documentation, and aid in resolution of integration and verification issues.

4.4 NASA/ESA Verification Requirements

ESA chairs the Verification Control Board at the Node 3 Element Level held at TASI, 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 3 system reviews which shall include verification reviews and are:

· Reference Configuration Review (RCR)

· Design Reviews (DRs)

· Pre-shipment Acceptance Review (PAR)

· Acceptance Review Board (ARB)

During the Flight Article Acceptance Phase which concludes with the ARB in the U.S., an ADP for each hardware item and software delivery shall be exchanged between NASA and ESA, in accordance with the JIP. The mutually agreed to data items in the ADPs accompanying each hardware and software delivery are defined in the SSP 50359.

Problems (failures) found during acceptance testing shall be reported under the Problem Reporting and Corrective Action (PRACA) system. The PRACA 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 3 to ISS functional/physical interfaces and critical systems. The dispositions shall be jointly agreed upon by ESA and NASA. The data exchange of failure reports shall be in accordance with SSP 50359.

In addition to formal reviews and data delivery, NASA, with support from Boeing, shall perform verification assessment activities (see Section 4.4.5) and assist ESA in the certification of the Node 3 Element.

4.4.1 Verification Requirements

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

The Node 3 PIDS requirements constitute the starting point for lower level specifications. The ESA lower level Node 3 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, Defense System Software Development.

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

NASA shall interface with ESA and its contractor on the subject of verification.

4.4.2.2 ESA Verification Interfaces

ESA and its contractor shall interface with the NASA on the subject of verification.

4.4.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.4.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.4.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.4.3.3 Test and Demonstration

As specified in the Node 3 PIDS Paragraph 4.0, the quality assurance provisions and qualification requirements are detailed in Section 4.3 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 3 interfaces. All requirements with safety impacts shall be demonstrated or tested. A full acceptance test program shall be conducted on the assembled Node 3 end item.

4.4.4 Verification Traceability and Close-out

The process for verification traceability and closeout of Node 3 PIDS requirements is shown in Figure 4-4. NASA shall establish and maintain the traceability from the Node 3 PIDS requirements to the ISS specification requirements in the PVIS database.

ESA shall provide the verification traceability and closeout data for all verification requirements, in the Node 3 PIDS via NASA, to the PVIS database through ARB. NASA is responsible for all remaining Node 3 PIDS requirements verification traceability and closeout after ARB.

b B

Figure 4-3 ESA Verification Traceability and Closeout Process

Figure 4-3 ESA Verification Traceability and Closeout Process - continued

4.4.4.1 Program Verification Information System (PVIS)

The PVIS is an automated database that provides the ISS Program the capability to track the large amounts of technical and programmatic data associated with the ISS Program 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 ISS Program management, including ESA, to assess the status of the ISS Program verification process.

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

4.4.4.1.1 PVIS Node 3 Requirement Traceability Data

Traceability data shall be developed and maintained by ESA for the lower level specifications for which ESA is responsible. Compliance data will be provided by ESA as per the SSP 50359.

Spec Section 3 Performance & Functional Requirements (S/A) Referenced Requirements Spec Section 4 Quality Assurance Provisions Detailed Verification Objectives Verification Activities Verification Reports Verification Closure Documentation Detailed Plans & Procedures

Test Analysis Demonstration Inspection (S/V) (V/A) (V) (S/A) (V/A) (V & A) Activity Schedules

(PP&C)

Relates To Relates To Direction Direction Relates To Legend:

S A V

PP&C

- Specification Team

- Architecture Team

- Verification Team

- Program Planning & Control Team Figure 4-4 NASA/Boeing Verification Traceability Process

4.4.4.2 PVIS Data Format

ESA shall have "read-only" access to the PVIS database remotely from Italy. Node 3 verification data shall be transferred electronically from ESA to NASA through ARB. The data will be loaded into the PVIS database by NASA. Figures 4.5.a and b represent a typical format for transferring this data from the VCD database to the PVIS database.

4.4.4.3 ESA to PVIS Database Configuration

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

Figure 4-5a ESA Verification Data Format for Transfer to PVIS (page 1 of 2)

Figure 4-5b ESA Verification Data Format Transfer to PVIS (page 2 of 2)

4.4.5 Verification Assessment

An agreed upon matrix allocating close out responsibility for specific verification tasks between NASA/Boeing and ESA/TASI 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/ESA verification teams. When ESA 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 ESA 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.

Periodically personnel from the Nodes Team and appropriate technical discipline will visit TASI to accomplish assessments. Through coordination with ESA/TASI, a memo of intent with an agenda of assessment activities will be developed prior to each visit. Concentration will be on the implementation (execution) of verification activities, including observance of specific test, inspection processes, and/or verification demonstration activities, and discussion of analysis results.

A memo of intent to TASI will be generated by NASA prior to TASI-onsite review. The memo of intent will inform TASI of the NASA intent to visit their facilities for a review of certain portions of their verification program. The memo will contain specifics as to the verification areas to be reviewed.

For verification tasks that 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 3 (CoFR) endorsements.

4.4.6 Verification Certification

Certification is defined as a culmination of verification activities that confirms that all verification requirements were met. Verification certification shall be accomplished by ESA for ESA 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 3 program reviews, the NASA IT&V team manager will provide test and verification manpower for these reviews.

NASA is responsible for all verification assessment efforts and reports. Verification assessment reports will be an addition to verification/certification documentation. ESA will provide documentation as evidence of completion leading to certification per the BDEALS.

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 that 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 is then transferred to PVIS by NASA.

4.4.6.1 Launch Vehicle Certificate of Flight Readiness

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

4.4.6.2 ISS Certificate of Flight Readiness

The CoFR for the ISS is the formal document that attests to the successful accomplishment of the work required to safely support on-orbit operation of the ISS. Within the ISS Program 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 ISS Program CoFR process shall be controlled by the ISS Program Manager.

For the Node 3, ESA 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.5 Node 3 Program Milestone Reviews

Detailed schedules will be provided by ESA to NASA on the development, manufacturing, and verification for the ESA/TASI activities. NASA will work with ESA to schedule the major program milestone reviews as identified below. The Node 3 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. NASA and ESA will conduct formal reviews and other meetings on the Node 3 project activities, products, and progress as defined in the JIP.

Detailed schedules are provided by NASA to ESA 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 3 PIDS have positive margins of safety considering all launch, landing and on-orbit environments have adequately met the requirements of NSTS 14046, Payload Verification Requirements.

5. Subsystem Verification

In the Node 3 element configuration, where flight hardware/software have been integrated, tests shall be performed to validate the following functions. Both NASA and ESA will participate in the test, which can be considered part of Node 3 end-item testing as indicated in Appendix C to this document. 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 for the various GFEs, which have been provided, including flight software (S/W) for which it will maintain responsibility to perform software trouble shooting and patching during this phase of verification. The remainder of the responsibilities belongs to ESA.

This section contains summary level descriptions of subsystem verification approaches relevant to the Node 3 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 ESA required for the integration and verification activities agreed by this plan will be documented in the SSP 50359 and the SSP 50528.

The air velocity closeout (AVCO) panels will only be available after delivery of Node 3 to KSC. Therefore, the AVCOs have to be considered as installed when ARS, Environmental Control and Life Support System (ECLSS) and W&HC racks are not present during the ventilation & illumination analyses.

Qualification of the Node 3 structure will be by similarity to the Node 2 for loads that are enveloped by the Node 2 qualification test. Stress analysis of each component per SSP 30559, Structural Design and Verification Requirements, will be performed to verify that positive margins of safety exist at yield and ultimate load levels. Fracture and fatigue analysis per SSP 30558, Fracture Control Requirements for Space Station, shall be performed to verify that the structure has adequate service life.

5.1.1.1 Node 3 Flight Article Proof Pressure Test

The Node 3 flight article will be proof pressure tested to 22.8 psid to verify structural integrity of the pressure shell. Flight Common Berthing Mechanisms (CBMs) (structural rings) and flight hatches will be installed on all radial and axial ports. An analysis will be performed by ESA to determine the secondary structure required to be installed to replicate the primary load paths of the integrated flight article. The hatch windowpanes will be visually inspected for flaws after the proof test per SSP 30560, Glass, Window, and Ceramic Structural Design and Verification Requirements, and the map of known flaws will be updated for future evaluation of the windowpanes. TASI must inspect the window surfaces prior to closing out the node for shipment to KSC. Window mylars will be updated at this time.

TASI should perform window inspections and update mylars at these recommended intervals:

1. Upon delivery of the hatch from Boeing (acceptance)

2. Following any activity which requires the window protective covers be removed

3. Following node proof test

The proof pressure test will be repeated in the open hatch configuration with closeouts on all of the CBM rings. TASI will provide closeouts for the open hatch configuration. Flight CBMs (structural rings) and hatches will be provided as GFE. The Node 3 primary structure will be instrumented with 50 channels to verify that the structural behavior of primary structure of Node 3 is similar to Node 2. Two strain gauges will be installed on radial port CBM rings at specified locations prior to the test. Nondestructive evaluation (NDE) of the pressure shell welds will be performed after completion of the second proof pressure test.

5.1.1.2 Node 3 Flight Article Pressure Decay Test.

The Node 3 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 ESA/TASI, 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.)…