SSP_50420-Rev_B.docx

SSP 50420

Revision B Appendix D – TEST SHEET FORMAT NASA/JAXA Bilateral Integration and Verification Plan for HTV

International Space Station Program

Revision B

January 2010

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas

REVISION AND HISTORY PAGE

PREFACE

NASA/JAXA bilateral integration and verification plan for htv The contents of this document are intended to be consistent with the tasks and products to be prepared by the International Space Station Program Participants as defined in SSP 50011-01, Concept of Operation and Utilization, Volume 1.

The NASA-JAXA Bilateral Integration and Verification Plan equally apply to the NASA and the JAXA. This document is under the control of the International Space Station Control Board (SSCB), with the concurrence of the respective International Participants. The Space Station Control Board delegates any future updates and/or revisions to the Vehicle Control Board bi-laterally. Plans specific to each HTV vehicle will be documented in the associated BIVP annex. The baselines for these annexes is delegated to the Vehicle Control Board bi-laterally.

INTERNATIONAL SPACE STATION PROGRAM

verification plan for htv

CONCURRENCE

january 2010 verification plan for htv

CONCURRENCE

january 2010 iv

NASA/JAXA bilateral integration and verification plan for htv

LIST OF CHANGES

january 2010 All changes to paragraphs, tables, and figures in this document are shown below:

Board Name

Entry Date

Change

Paragraph(s)

August 2004

Baseline

All

March 2008

Revision A

All

April 2010

Revision B

1.1, 1.2, 1.4.2, 4.1, 4.1.1, 4.1.2, 5.1, 5.2, Deleted 5.2.1 -5.2.15, 5.2.15.1, 5.2.15.2, 5.2.16 – 5.2.21, 5.3, 5.3.1, 5.3.2, 5.3.2.1, 5.3.2.2, 5.3.3 – 5.3.5, Appendix E, F, G, H

TABLE OF CONTENTS

APPENDIX

TABLE

v

INTRODUCTIOn The National Aeronautics and Space Administration (NASA)/Japan Aerospace Exploration Agency (JAXA) Bilateral Integration and Verification Plan (BIVP) for the H-II Transfer Vehicle (HTV) defines the verification plan for the integration and verification of the HTV segment to the International Space Station (ISS).

purpose This NASA/JAXA BIVP for the HTV documents the agreements between NASA and JAXA for the integration and verification of the generic HTV Segment into the ISS as established in SSP 50030, NASA/NASDA Joint Management Plan (JMP). Changes to this baseline will be documented in new annexes for the specific vehicle. Plans specific to each HTV vehicle are in the Bilateral Integration and Verification Plan (BIVP) Annexes.

This is the main document that defines the joint NASA and JAXA integration and verification activities. The BIVP Annexes identify the organizational roles and responsibilities involved in implementing specific vehicle requirements. The NASA/JAXA BIVP formalizes agency level verification commitments between NASA and JAXA. The agreements defined in this BIVP and the BIVP Annexes address the verification tasks required to confirm compliance with the requirements of:

This BIVP defines the verification planning specifically addressing the interrelationship between NASA and JAXA when verifying the requirements specified in these documents as well as any joint and/or other tests where Partner support is needed.

For the implementation of joint and other tests, where partner support is needed, the BIVP Annexes contain the NASA/JAXA agreements for each vehicle.

SCOPE

This NASA/JAXA BIVP defines the data, products, tasks, and planning agreements for the integration and verification of the HTV Segment with the ISS as necessary.

This BIVP is applied to each HTV flight model as well as to the HTV proto-flight model. This document includes the followings:

When verification of an interface or a functional performance requirement necessitates the use of facilities, hardware, software, data, or any supports of the interfacing partner, these needs are defined in the applicable BIVP Annex. The specifics of the hardware, software, and data exchanges required for the integration and verification and the associated bilateral agreement of the successful facilitation of these exchanges will be documented in the associated SSP 50614, NASA/JAXA Bilateral Data Exchange Agreements, Lists and Schedules (BDEALS) for HTV, and SSP 50615, NASA/JAXA Bilateral Hardware and Software Exchange Agreements, Lists and Schedules (BHSEALS) for HTV.

Integration and Verification of the ISS Ground System including United States Ground Segment (USGS) and Ground Segments of International Partners (IPs) are not part of this document. The Ground System integration and verification activities are addressed in SSP 54501, International Ground System Integration, Verification and Test Management Plan.

The HTV Operations System interfaces with the USGS and the preparations and checkout for the actual HTV operations such as Proximity Communication System (PROX) are out of the scope of this BIVP except for the joint end-to-end data flow tests described in BIVP Annex 1, Tests 15-1 and 15-2. Details of verification by analysis are contained in the SSP 50614 and will not be covered in this document. Analysis reports shall be maintained in NASA ISS Electronic Data Management System along with other verification documentation.

Test Sheet Joint test sheets for each HTV flight model will be developed and appended to the applicable NASA/JAXA Bilateral Integration and Verification Plan (BIVP) for the H-II Transfer Vehicle (HTV) Annex (BIVP Annex). The BIVP Annex documents include:

A. Definition of the activities to be completed for integration and verification of the subsystems, flight hardware, and flight software.

B. Definition of the verification information to be exchanged and their intended use.

C. Description of the NASA and JAXA test and support equipment and facilities to be used to support joint verification D. Definition of the verification processes and program policies to be used for the joint integration and verification activities.

E. The program milestones associated with the bilateral verification activities precedence This NASA/JAXA BIVP is prepared in compliance with the NASA/JAXA Joint Management Plan (JMP), Memorandum of Understanding (MOU) between the Government of Japan (GOJ) and NASA, and the Inter-government Agreement (IGA). The NASA/JAXA BIVP for HTV is the only top level ISS integration and verification planning document for NASA/JAXA ISS/HTV interface and takes precedence over any NASA or JAXA interface verification plans, including D684-10020-1, Program Master Integration and Verification Plan (PMI&VP), and the HTV integration and verification plan included in the HTV Verification Requirement Document, (KAE-01001/HTV-VE-001). In the event of a conflict, the documents shall apply in the following order of precedence:

DELEGATION OF AUTHORITY

The NASA and JAXA Space Station Program Managers or their delegated authorities bilaterally control the NASA/JAXA BIVP for HTV, through approval signature. The BIVP is developed and maintained by the Vehicle Office in coordination with JAXA. Changes to the baselined BIVP must be dispositioned and approved by the NASA and JAXA Space Station Managers or their authorized representatives following a review process in accordance with the process guidelines defined in the SSP 50030, NASA/NASDA JMP.

Notification of Document Change Process The Notification of Document Change (NDC) process is a process to generate, track, negotiate, and implement changes to the BIVP. NASA transfers proposed updates to the BIVP resulting from protocols, TIMs, telecons, videocons, e-mails, or a need to update the BIVP onto the NDC form. NASA then routes the NDC for technical concurrence signatures from all impacted IP, NASA, and Boeing technical and/or management teams. After technical concurrence is received, the Bilateral Document Managers sign. Finally, if the NDC requires NASA support, the signatures confirming NASA support are obtained; if NASA support is not required, a “not required” is entered in these fields. An NDC may be implemented when it has received all signatures. When a new BIVP revision is required, NASA will generate an administrative CR to formally release the new BIVP. The new BIVP revision will contain all NDCs that are completely signed.

Test Sheet Approval The Test Sheets contained in the applicable vehicle BIVP Annex shall be controlled through approval signatures by the NASA and JAXA Manager for HTV, the NASA and JAXA HTV Test and Verification Manager, appropriate NASA and JAXA engineering leads, and ISS Test and verification Control panel chairman.

verb application The verb “shall” will be used in this document to indicate a requirement. Verbs such as will, are, should, etc. are used to express a declaration of purpose or in cases where simple future tenses are required but do not articulate a requirement binding on the ISS participants.

deviation/waiver All requests for deviation or waiver of joint requirements must be submitted by the NASA and JAXA ISS Program Managers or their delegated authorities who bilaterally control SSP 50420, NASA/JAXA Bilateral Integration and Verification Plan for HTV, for approval signature.

SSP 50420

Revision B

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

KAE-01001*

(HTV-VE-001)

H-II Transfer Vehicle (HTV) Verification Requirement Document (*HTV-VE-001 is English version of KAE-01001)

SSP 41178-35

<TBD 1-1>

Software Interface Control Document Internal Multiplexer/Demultiplexer to International Space Station Book 35, H-II Transfer Vehicle Interface

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

SSP 30223

Problem Reporting and Corrective Action for Space Station Program

2-3

INTERFACING HARDWARE DESCRIPTION

ISS DESCRIPTION

ISS SYSTEM DESCRIPTION

The ISS is an international endeavor being developed by NASA, JAXA, the European Space Agency (ESA), the Agenzia Spaziale Italia (ASI), the Canadian Space Agency (CSA), and the 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 microgravity, materials, life science research and development, earth and stellar observation as well as other technology development and demonstration by the United States (U.S.) and the International Partners.

The ISS is comprised of the United States On-Orbit Segment, (USOS), International Ground System (IGS), ESA Columbus module, JAXA Japanese Experiment Module (JEM), Russian Space Agency (RSA) Russian Segment (RS), ASI Multi-Purpose Logistics Modules (MPLM), and the CSA Mobile Servicing System (MSS). The NASA Space Shuttle, the RS Progress vehicle, JAXA H-II Transfer Vehicle (HTV), Commercial Orbital Transport Systems (COTS), and ESA Automated Transfer Vehicle (ATV) are cargo transportation systems for the ISS.

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 will be used to reference the verification reporting. Changes within an assembly stage will be considered in the verification of that stage.

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 & control; data processing; storage and transportation; crew health care; housekeeping; personal hygiene; food preparation and storage; extravehicular activity access; payload utilities; attitude control; pointing support and robotics system control. The USOS system diagram is shown in SSP 41162, Segment Specification for the United States On-Orbit, Figure 1, (USOS System Diagram).

The United States (U.S.) pressurized modules contain equipment to provide laboratory, habitation, logistics re-supply, and overall Station command and control functions. The U.S. pressurized elements include the U.S. Laboratory Module (U.S. Lab), the Node 1, the Node 2, the Node 3, the Airlock, Pressurized Mating Adapters, and the Cupola. The Nodes are pressurized, environmentally controlled elements that serve to connect the US Lab, and the International Partners' modules. With four radial ports and two axial ports each, the Nodes are the building blocks for the pressurized elements for the ISS. Node 2 serves primarily as the berthing location for the Pressurized Mating Adapter (PMA)-2, the forward end of the U.S. Lab, the Columbus module, the JEM, and the Mini-Pressurized Logistics Module and HTV when it arrives at the International Space Station on its re-supply missions.

The U.S. unpressurized elements include the Integrated Truss Assembly (ITA), the Unpressurized Cargo Carriers (UCC), the Photovoltaic (PV) power modules, the Control Moment Gyro (CMG), and the external central Thermal Control Subsystem (TCS), Mobile Transporter (MT), and storage and logistics carriers and platforms.

HTV DESCRIPTION

The HTV is an automated, unmanned cargo transportation system developed by the JAXA for the ISS. This system is composed of the H-II Transfer Vehicle, the HTV Operations System, the HTV Proximity Communication System (HTV PROX or PROX), and the HTV Laser Radar Reflector (HTV LRR or LRR). The HTV transports pressurized and unpressurized cargos (experiment equipment and materials, system equipment, crew items, consumable, etc.) to the ISS. It can also reload nonrecoverable items from the ISS for disposal and perform destructive reentry.

The HTV is composed of the Pressurized Logistics Carrier (PLC), the Unpressurized Logistics Carrier (ULC), the Exposed Pallet (EP), the Avionics Module and the Propulsion Module. The pressurized section carries the pressurized cargos. The unpressurized section holds unpressurized cargos. The unpressurized cargos are attached to the Exposed Pallet and the entire pallet is transferred to and from the HTV to ISS via the Space Station Remote Manipulator System (SSRMS) and JEM Remote Manipulator System (RMS). The Avionics Module has the functions for navigation and guidance of the HTV and generates control commands to the Propulsion Module. It also has the functions for communication, data processing, and power supply to the components. The Propulsion Module receives commands from the Avionics Module and controls the trajectory and the attitude of the HTV. The HTV System is defined in SSP 50273.

HTV OPERATIONS SYSTEM

The HTV Operations System supports the operation of the HTV and the cargo loaded on the HTV. The characteristics of the HTV Operational Control Segment (OCS) are defined in SSP 54500, International Ground System Specification Document. The HTV Operations System is out of the scope of this BIVP except for the end-to-end data flow validation.

HTV TO NODE 2 INTERFACES

The HTV berths to the Node 2 of the USOS for cargo supply and loading of disposal items. The HTV and the Node 2 have access envelope, structural and mechanical, thermal, electrical and electronic, communication, software and environment control and life support interfaces during the HTV attached operation. The HTV interface with Node 2 is defined in SSP 50438, except software interface.

The HTV Data Handling subsystem (HTV-DH) software interface with the Internal Multiplexer/Demultiplexer (INT MDM) via Node 2 is defined in SSP 41178-35 <TBD 1-1>, while the PROX software interface including the HTV software interface via PROX with the Command and Control (C&C) MDM is defined in SSP 41175-35.

ROBOTICS INTERFACES

The HTV berthing/unberthing operations to and from the ISS are executed by the SSRMS attached on the Node 2 Power and Data Grapple Fixture (PDGF). The HTV has dynamical, mechanical, structural and optical interfaces with the SSRMS. The specific HTV interface with the SSRMS is defined in the SSP 50273, SSP 50438, and SSP 42004, Part 1, Mobile Servicing System (MSS) to User (Generic) Interface Control Document.

The SSRMS is used to draw out the HTV-Exposed Pallet (HTV-EP) from the HTV ULC. Several types of EPs are planned and each involves unique robotics operations including HTV-EP hand over to the JEM Remote Manipulator System (JEM-RMS). The descriptions for SSRMS, SPDM, and JEM-RMS along with HTV-EP handling are defined in SSP 50575, NASA/JAXA Bilateral HTV Operations Plan.

GROUND SEGMENT INTERFACES

The HTV Operation Control System (HTV OCS) interfaces with the USGS via the Space Station Integration and Promotion Center (SSIPC) of JAXA to exchange visual/audio and operation data. HTV Operations System interfaces with USGS are defined in the SSP 45012, Space Station Control Center to Japan Aerospace Exploration Agency (JAXA) Ground Segment Interface Control Document.

SSP 50420

Revision B

3-3

VERIFICATION MANAGEMENT

VERIFICATION PROGRAM ROLES AND RESPONSIBILITIES

NASA and JAXA are both responsible for the integration and verification of their own end items in accordance with the respective segment specifications. The agency responsible for the hardware (HW) and software (SW) which represents a mating side of the interface, is also responsible for the verification that its own system/element is in compliance with the interface requirements established in the SSP 50438, Part 1, International Space Station to H-II Transfer Vehicle Interface Control Document and the associated ISS/HTV software ICDs (SSP 41178-35 <TBD 1-1> and SSP 41175-35) and that the “as-built” configuration is in compliance with SSP 50438, Part 2, International Space Station to H-II Transfer Vehicle Interface Control Document.

NASA is responsible for ensuring the USOS meets all of the requirements of its specification, and that the USGS meets all of its requirements and those of the applicable ICDs. NASA is also responsible for the overall integration and verification of the ISS, including the management of all International Partners. JAXA will support NASA in the integration and verification of the HTV to the ISS as defined in this document. The detailed Interface Requirements are defined in various HTV to ISS ICDs. NASA and JAXA are jointly responsible for implementation of these requirements.

If technical support from NASA is judged to be necessary to properly verify requirement compliance, the availability and planning of the required support from NASA will be negotiated and documented in this BIVP. The BIVP will document all JAXA support requirements as well. The lead and support responsibility for each joint verification activity will be negotiated, bilaterally agreed and specified in this BIVP. The items and descriptions of identified joint verification tasks for NASA and JAXA are included in each joint test sheet in the applicable BIVP Annex.

JAXA RESPONSIBILITIES

JAXA is responsible for the verification of the HTV, including both hardware and software.

JAXA responsibilities are as follows:

NASA RESPONSIBILITIES

NASA responsibilities are as follows:

ISS 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 verification plans for the overall system and for the NASA contractors, and the BIVPs for the International Partners. In addition the IT&V team:

<TBD 1-1> and SSP 41175-35).

J. Verifying action items resulting from verification procedures are resolved prior to closure of the referenced requirements.

NASA/JAXA VERIFICATION MATRIX

The NASA/JAXA verification requirements are documented in several separate documents and reports. Interface requirements determined to be stand-alone verification activities are located in the corresponding JAXA and NASA Segment Specifications. Requirement verification matrices for joint test requirements will be maintained by the NASA Vehicle Office and made available to JAXA.

The lead and support responsibility assignments for each joint verification activity will be negotiated and defined in the joint test sheets in the applicable BIVP Annex. In a joint verification activity, one agency will be the lead with support provided by the other. The detailed tasks of joint verification activities are described in these test data sheets.

RELATIONSHIP BETWEEN NASA AND JAXA VERIFICATION MANAGEMENT

The NASA Integration Test and Verification (IT&V) team will participate in HTV program reviews conducted by JAXA and the IT&V team leader will be a member of these review boards. The IT&V team shall provide personnel to perform review of the verification related material, coordinate support for verification assessment and joint test activities, and aid in the identification of tests requiring contractor support. In addition, each partner will make the best effort to provide the other with access to program verification data such as databases and documentation, and aid in resolution of integration and verification issues. If major issues such as proprietary data prevent direct disclosure of data, each partner will provide the other with alternative data such as a summary of the data or other authorized confirmation documentation.

VERIFICATION REQUIREMENTS

Verification requirements (e.g., methods, objectives, conditions, success criteria) for the ISS System, USOS, USGS, all U.S. End Item specifications and Segment specifications are defined in their respective Section 4, Quality Assurance Provisions. Verification requirements for the HTV System are defined in the Verification Section of the SSP 50273. Verification planning and implementation for the HTV are documented in JAXA documentation.

JAXA VERIFICATION PROCESS

JAXA is responsible for the HTV verification including development phase, performance and functional requirements compliance and flight article acceptance. The primary objectives are:

The verification process begins with the translation of design, performance and interface requirements (documented in specifications and ICDs) into verification requirements, i.e. with the allocation of these requirements to the appropriate method of verification. Verification will start at the lowest practical level and progress in an incremental integrated process through the various intermediate levels to the element verification. With this determination, the objective and conditions are established forming the basis for preparation of plans, specifications, and procedures.

Establishment and maintenance of the Verification Control Documents (VCD) provides the practical implementation of the verification program. The VCD is used to plan, control, and report status/completion of verification activities. The VCD will be generated and delivered to NASA prior to Critical Design Review (CDR). An updated VCD reflecting final requirement verification for review shall be included in each HTV Post Qualification Review (PQR) Data package as verification documentation.

The VCD document will be prepared as required indicating:

The HTV verification campaign is considered concluded when all elements of the HTV system have been verified. The JAXA HTV verification requirements and process are described in HTV-VE-001, HTV Verification Requirement Documentation.

The requirements of the SSP 50273, Segment Specification for the H-II Transfer Vehicle (HTV Segment Specification) are allocated to NASDA-ESPC-2020, HTV System Specification and Module Development Specifications and in verification matrices. Based on these verification requirement, verification plans for HTV overall system and modules are developed. Verification methods requirements are defined in section 4 of development specifications and in verification matrices. Based on these verification requirements, verification plans for HTV overall system and sub-systems are developed.

A Verification Compliance Notice (VCN) is generated following the completion of each verification activity. The VCN will be generated and delivered to NASA prior to the Post Qualification Review (PQR) as verification closure documentation.

The VCN document will include:

NASA VERIFICATION PROCESS

The verification process followed by the ISS is described in the D684-10020-1, Program Master Integration and Verification Plan (PMI&VP). The approach is to verify specification compliance starting at the lowest level (components, equipment) and building to the ISS System level. Each organization responsible for the development of an end item is responsible for the verification of that item to its allocated requirements. Specification compliance at the system and USOS level is verified using processes as defined in the D684-10020-1. The verification process followed by the ISS is described in D684-10025-1, Integration and Verification Implementation Plan for the ISS system and the U.S. Segment. Stage verification for the HTV will follow these processes.

The interface requirements documented in the various ICDs will be verified in accordance with verification matrices, and the joint and other tests related to interface verification contained in the applicable BIVP Annex. Joint analysis verification will be in accordance with SSP 50614.

VERIFICATION METHODS

The verification methods used for the NASA/JAXA HTV bilateral verification activity are as follows:

The definitions of these verification methods are described in the following subsections.

INSPECTION

Engineering inspection, hereafter referred to as inspection, is a method of verification that determines conformance to requirements by the use of standard quality control methods to ensure compliance by review of drawings and data. This method is used wherever documents or data can be visually used to verify the physical characteristics of the product instead of the performance of the product.

There is a difference between NASA and JAXA regarding the use of the term "Inspection" on software verification and some extra explanation is required. "Inspection" as used by NASA includes the verification activity for the confirmation that the ground/flight software complies with applicable software development (coding) standards. JAXA uses the same verification method on software verifications when it is appropriate, but the activity is considered "Analysis".

ANALYSIS

Analysis is a verification method utilizing techniques and tools such as math models, prior test data, simulations, analytical assessments, etc. Analysis may be used in lieu of, or in addition to, other methods to ensure compliance to specification requirements. The selected techniques may include, but not be limited to, engineering analysis, statistics and qualitative analysis, computer and hardware simulations, and analog modeling. Analysis may be used when it can be determined that (1) rigorous and accurate analysis is possible, (2) test is not cost effective, and (3) verification by inspection is not adequate. Examples of verification by analysis include thermal analysis and stress analysis to show that the use of the hardware does not exceed specification limits during the mission operation.

SIMILARITY

Verification by similarity is acceptable if the subject article is similar or identical in design, manufacturing process, and quality control to another article that has been previously verified to an equivalent or more stringent criteria. Verification by similarity is the process of analyzing the specification criteria for hardware configuration and application for an article to determine if it is similar or identical in design, manufacturing process, and quality control to an existing article that has previously been qualified to equivalent or more stringent specification criteria. Special effort will be made to avoid duplication of previous tests from this or similar programs. If the previous application is considered to be similar, but not equal to or greater in severity, additional qualification tests will concentrate on the areas of new or increased requirements.

Similarity may be treated as a type of Analysis for NASA tracking of requirement closures.

REVIEW OF DESIGN

Review of design is the verification method used only by JAXA to verify lower level design implementation requirements by use of approved design documentation. Review of design consists in utilizing approved design reports, technical descriptions, and/or engineering drawings to unambiguously demonstrate that the interface is designed as documented in ICDs.

Review of Design is often used combined with other verification methods to verify requirement compliance. For requirement verified only by Review of Design, other verification method will be performed for its corresponding higher-level (more general) requirement. To this case, requirement traceability is also discriminated.

Review of design may be treated as a type of inspection for NASA tracking of requirement closures.

DEMONSTRATION

Demonstration consists of a qualitative determination of the properties of a test article. This qualitative determination is made through observation, with or without special test equipment or instrumentation, which verifies characteristics such as human engineering features, services, access features, and transportability. Demonstration requirements are normally implemented within a test plan, operations plan, or test procedure.

TEST

Test is a method in which technical means, such as the use of special equipment, instrumentation, simulation techniques, and the application of established principles and procedures are used for the evaluation of components, subsystems, and systems to determine compliance with requirements. Testing is the preferred method for requirement verification. Testing is required when analytical techniques do not produce adequate results; failure modes exist which could compromise personnel safety, adversely affect flight systems or payload operation, or result in a loss of mission objectives; or for any components directly associated with Space Station and orbiter interfaces. The analysis of data derived from tests is an integral part of the test program, and should not be confused with analysis as defined above. Tests will be used to determine quantitative compliance to requirements and produce quantitative results.

VERIFICATION REPORTING

JAXA VERIFICATION REPORTING

JAXA will:

PROBLEM REPORTING AND CORRECTIVE ACTIONS

Design, manufacturing and operational discrepancies discovered in HTV flight hardware or software are resolved through the Material Review Board (MRB), NASA/JAXA joint problem resolution team if necessary and its result is registered to the J-PRACA system of JAXA. This system establishes a disciplined process of reporting and determining corrective action for problems detected during integration and verification. NASA/JAXA exchanges of failure reports will be in accordance with SSP 50614, NASA/JAXA Bilateral Data Exchange Agreements, Lists and Schedules for H-II Transfer Vehicle (HTV).

NASA PROCESS SAMPLING

Process sampling is an activity performed by NASA, and/or NASA contractors, to witness selected HTV verification activities or processes. This sampling is not to confirm design conformance or test results. The focus of process sampling will be on critical verification activities to ensure the established verification process is followed. It will not be a technical review by NASA of the correctness or completeness of the verification data nor to approve JAXA processes, but NASA will use the findings in support of CoFR endorsements. The applicable BIVP Annex contains a list of process sampling activity reports for that has been developed and conducted by NASA or Prime.

The criteria for these activities will vary with that aspect of verification implementation being sampled. The depth of penetration will vary based on the specific process to be sampled and the agreement obtained from JAXA. JAXA will provide a set of instructions to the process sampling team prior to the activity to be witnessed. Process sampling activity will not interfere with work at the site to be inspected nor cause additional task for the visited partner (Including question and answer activities on a non-interference basis). At the completion of activities, a 7-Day Quick-Look-Report will be prepared that documents the conclusion of the process sampling activities. Within 30 days of test completion, the process sampling team and the IT&V organization will complete a more In-Depth-Report. This report will provide a detailed description of the verification activities and their results.

The reports developed during process sampling activities, such as the 7-day Quick Look Report, or the In Depth Report will be an assessment of JAXA’s verification process and will not be intended for review of the test results. The Process Sampling team will submit reports to the JAXA verification teams and the ISSP Integrated Test and Verification team, and be placed in the NASA ISS Electronic Document Management System (EDMS).

The NASA Verification team will coordinate with the JAXA verification team to identify those verification activities that are to be process sampled. To this end, JAXA will communicate the schedule for these activities to NASA with sufficient lead time to permit the team to observe the activity.

CERTIFICATION OF FLIGHT READINESS (CoFR) SSP 50030, Paragraph 3.4, Certification and Launch Readiness Verification, defines the agreement between NASA and JAXA concerning the CoFR.

JAXA is responsible for the certification and qualification of the HTV.

The Space Station CoFR is to ensure the elements meet their requirements and are ready to arrive on orbit. NASA assurance will be based on HTV integration and verification activities defined in this BIVP, ISS integration and stage verification.

The ISS CoFR Process is documented in SSP 50108, Certification of Flight Readiness Process Document. The JAXA internal CoFR process related to HTV is illustrated in SSP 50108.

SSP 50420

Revision B

4-9

SUMMARY OF VERIFICATION ACTIVITIES DESCRIPTION

general This section defines the principles which will be applied when executing the activities defined in Appendix E of the applicable BIVP Annex, which comprise joint test activities, hereafter referred to as joint tests and JAXA support for NASA I/F tests and NASA support for JAXA I/F tests (“Other Tests”). Standard test sheet format is defined in Appendix D of this BIVP.

For Joint Tests For each joint test, the partner Agency hosting the test will be assigned the lead, unless otherwise agreed on the test sheet. Pass/fail criteria shall be identified for each test. Both I/F partners will approve test specifications, test procedures, the verification report, and co-chair pre-and post-test review boards.

Each partner will approve all the above in those cases where its support has been agreed on individual joint (bi-lateral) test sheets. Hardware and software exchanges necessary to support these tests as identified in the test sheets will be provided by NASA or JAXA as documented in SSP 50615. Except where specifically documented, these items are to be returned to the providing Agency after completion of the test. Test sheets for joint tests are contained in Appendix C of the applicable BIVP Annex.

The obligations of the lead Agency are as agreed on individual test sheets and typically include:

The obligations of the partner Agency are as agreed on individual test sheets and typically include:

For Other Tests:

Stand-alone tests are all interface requirements tests that are not specified as joint.

In some cases the proper conduct of a stand-alone I/F verification test by one partner is not feasible without HW/SW and/or resources support from the interfacing partner. Such support is agreed to in this BIVP, the test sheets, the HW/SW exchange list, and the test is identified as Other Test. For each Other Test, the Partner who requires support for their stand-alone test is the Lead Agency unless otherwise agreed on the test sheet.

The supporting Partner will review test procedures, receive verification closeout documentation and will participate in the pre-and post-test review boards. The supporting partner supplies HW/SW, resources/accessibility and skills, as agreed on the test sheets, and ensures that the HW/SW support conforms to the agreed requirements and the applicable I/F design as per ICD.

The obligations of the lead Agency are as agreed to on individual test sheets and typically include: