SSP_50420-HTV1-Baseline.docx

SSP 50420-HTV1

Baseline NASA/JAXA Bilateral Integration and Verification Plan for HTV, Annex 1: HTV1

International Space Station Program

Baseline

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 initial release of this document is under the control of the International Space Station Control Board (SSCB), with the concurrence of the respective International Participants. The SSCB delegates approval of any future updates and/or revisions to the Vehicle Control Board bi-laterally.

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, ANNEX 1: HTV 1

CONCURRENCE

january 2010

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, ANNEX 1: HTV1

CONCURRENCE

january 2010 iii

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, ANNEX 1: HTV 1

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)

April 2010

Baseline

All

TABLE OF CONTENTS

APPENDIX

TABLE

iv

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

purpose This NASA/JAXA BIVP Annex 1 for the HTV documents the agreements between NASA and JAXA for the integration and verification of the HTV 1 Segment into the ISS as established in SSP 50030, NASA/NASDA Joint Management Plan (JMP).

SCOPE

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

precedence In the event of a conflict between this document and SSP 50420, NASA/JAXA Bilateral Integration and Verification Plan for HTV, SSP 50420 shall take precedence.

Notification of Document Change Process The Notification of Document Change (NDC) process is a process to generate, track, negotiate, and implement changes to this document.

Test Sheet Approval The Test Sheets of Appendix E 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. Original signed version will be maintained in International Space Station Electronic Document Management System (EDMS).

SSP 50420-HTV1

Baseline

1-1 documents applicable documents In addition to the documentation defined in SSP 50420 paragraph 2.1, the following documents include specifications, models, standards, guidelines, handbooks, and other special publications which are required for HTV 1. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

N/A No additional terms or definitions are required reference documents In addition to the documentation defined in SSP 50420 paragraph 2.2, the following documents contain supplemental information to guide the user in the application of this document for HTV 1. These reference documents may or may not be specifically cited within the text of this document.

N/A No additional terms or definitions are required

SSP 50420-HTV1

Baseline

2-1

SUMMARY OF VERIFICATION ACTIVITIES DESCRIPTION

general This section defines the principles which will be applied when executing the activities defined in Appendix C, 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”).

JOINT TESTS

This section describes the Joint tests performed by one partner with active participation by the other partner for the HTV. Note selected tests have been reclassified as stand-alone as noted in their description. Active participation includes one or more of the following:

NASA and JAXA will jointly generate the test report. Baselined Joint Test Sheets are included in Appendix E.

PROX I/O Test (Test #1) This test is an early phase risk mitigation test to test Proximity Communication System (PROX) software input/output (I/O) conformance to SSP 41175-35. This test will help identify problems and/or issues with the software ICD. The results of the test will be used to reduce the need for redesign and rework that could impact the development of the PROX system.

PROX RT Validation (Test #2) PROX RT validation will be performed by JAXA in stand alone testing. No joint test will be performed.

PROX SW Interface (Test #3) This test is an early integration test for USOS to demonstrate commanding, telemetry routing and software functionality across the USOS to HTV-PROX interface. JAXA will verify PROX flight software conformance to SSP 41175-35 during this test.

HTV Data Handling I/O (Test #4) This test is an early phase risk mitigation test to test HTV Data Handling System (HTV-DH) software input/output conformance to SSP 41178-35. This test will help identify problems and/or issues with the software ICD. The results of the test will be used to reduce the need for redesign and rework that could impact the development of the HTV-DH system.

HTV- Data Handling RT (Test #5) HTV- Data Handling RT will be performed by JAXA in standalone testing. No joint test will be performed.

HTV- Data Handling SW Interface (Test #6) This is a test of the ISS to HTV-DH software interface for

Integrate PROX/HTV-DH with PFM SW Interface (Test #7) This test is a hardware/software integration test of command and data transmission functional interfaces between the ISS and PROX-FEU/HTV Protoflight Model (PFM) Avionics Module/Propulsion Module. The purpose of this test is to:

INTEGRATED HTV STAGE TEST (Test #8) The Integrated HTV Stage test will test PROX and HTV flight software (CCS, INTSYS, RWS, PCS, etc.) system level functionality and compatibility including

RF VERIFICATION (Test #9) RF verification will be performed by JAXA in standalone testing. No Joint test will be performed.

STEP 2 Power Interface Test on PFM (Test #10) The purpose of the STEP 2 Power Interface Test (Test #10) is to evaluate the electrical characteristics of the HTV Protoflight Model (PFM) in the attached phase (i.e., in a system environment when powered by a Node 2 emulator). Testing of steady state voltage, normal transient voltage, ripple voltage (time and frequency domain), small and large signal stability, EMI (noise current – CE01/03) and inrush/surge current (activation/start-up) will be performed. Key verification interfaces will include DDCU output (Interface A), Node 2-HTV, Node2-APM (reference only), HTV ISS DC/DC Output (monitor 50VDC bus via 0.1 Hz telemetry data), HTV ISS DC\DC Input (Interface C), HTV GLA input (Interface C), HTV smoke sensor input (Interface C) and VFU input (Interface C). SSP 50438, SSP 30482 Volume 1 (Source Power Quality: Interfaces B and C) and SSP 52051 volume 1 (Load Power Quality: Interface B) and SSP 50273 requirements will be tested.

TDRSS INTERFACE TEST Category 1 (Test #11) The purpose of the Category 1 Compatibility Test is to test the HTV functional/performance interface with the Tracking and Data Relay Satellite System (TDRSS). The test is performed during the HTV development phase using an HTV Engineering Model (EM) transponder. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed to address requirements in the SSP 50273, for the HTV to send and return data destined for the HTVCC, and receive the forward link command data originated at the HTVCC through data relay satellites and for the HTV to have the capability to support ranging and Doppler measurement by data relay satellite systems. Radio frequency interfaces between the TDRS and the HTV are defined in KAE-99003, 451-RFICD-HTV-TDRSS and 450-SNUG, Space Network Users Guide.

TDRSS INTERFACE TEST Category 2 (Test #12) The purpose of the TDRSS/HTV Category 2 Compatibility Test is to verify the HTV functional/performance interface with the TDRSS. The test is performed using an HTV Protoflight Model (PFM) transponder. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed to verify requirements in the SSP 50273, for the HTV to send and return data destined for the HTVCC, and receive the forward link command data originated at the HTVCC through data relay satellites and for the HTV to have the capability to support ranging and Doppler measurement by data relay satellite systems. Radio frequency interfaces between the TDRS and the HTV are defined inKAE-99003, 451-RFICD-HTV-TDRSS and 450-SNUG, Space Network Users Guide.

WATER/LIQUID WASTE TRANSFER TEST (Test #13) The Water/Liquid Waste Transfer Test was deleted due to a change in interface requirements and HTV design (i.e., elimination of HTV tanks for water/liquid waste).

CBM ACCEPTANCE VERIFICATION (Test #14) The purpose of the test is to verify that all PCBM components are within design limits to ensure interoperability. Additionally, the tests will include a seal leak test to ensure proper Gask-O-Seal installation and to verify the integrity of the PCBM sealing surface. The following shall be verified:

END TO END TESTs (Test #15) End to end tests are performed to confirm dataflow for command and data signal processing for various pathways for the ISS/HTV flight and ground segments. End to end testing will address ISS/HTV/Ground Segment (GS) command and data signal processing (15-1) and HTV/TDRS/GS communication and data transmission capability during free flying/rendezvous phase (15-2).

HTV/ISS/Ground Segment end to end test (15-1) The purpose of the HTV/ISS/Ground Segment End to End Test is

HTV/TDRSS/GROUND SEGMENT END TO END TEST (15-2)

The purpose of the HTV/TDRS/Ground Segment End to End Test is to:

PCS and RWS Display Data Compatibility Test (Test #20) The purpose of HTV/ISS PCS Monitor/Control and RWS Display Data Compatibility Test is to exercise command/telemetry data capabilities of PCS and RWS display software to HTV, including PROX, as risk mitigation prior to integrated stage verification testing. PROX and HTV flight software to US Segment flight software (CCS, INTSYS, RWS, PCS, etc.) system-level functionality and compatibility are exercised during this test. Through this test, consistency between HTV IPCL data and actual data of HTV avionics system is indirectly confirmed. A subset of the HTV Crew Monitoring (HCM) verification is performed during this test. Objectives of this test include, but are not limited to:

REFLECTOR TOOL IMPACT TEST (Test #21) The purpose of this test is to evaluate the HTV Laser Radar Reflector (LRR) for failures due to unintentional EVA hazards, such as sharp edges or contamination. A primary objective of this test is to verify compliance of the HTV Laser Radar Reflector with SSP 50005, Flight Crew Integration Standard (NASA-STD-3000/T), paragraph 14.1.3N. The test will show whether EVA tool impacts will create any hazards, such as sharp edges or contamination.

HTV Berthing camera system (HBCS) Integration test (Test #23) The purpose of this test is to verify the HBCS berthing camera system for EP insertion/extraction to HTV by SSRMS. The test will include crew in the loop testing to demonstrate:

The HBCS Avionics Package has primary and redundant electronics, which have the capability to operate the cameras, receive the camera data, create video data and send video data to MSS RWS through SSRMS/PDGF. It sends video data to MSS RWS through SSRMS/PDGF during SSRMS handling. The HBCS target is installed inside the HTV as a guide system for EP insertion. HBCS provides the crew steering cue to insert the EP to the HTV guide capture envelope.

Other TESTS Other tests performed by one partner with support provided by the other partner to verify the interface requirements or minimize risk in the applicable documents. Support activities include one or more of the following:

The Test Lead will generate the test/verification report. Other Verification Test Sheets are included in Appendix E.

HTV /tdrss/gs end to end check-out (Test #15-3) The purpose of the HTV /TDRSS/GS END TO END CHECK-OUT is to check end to end command and telemetry dataflow for TDRSS link just prior to launch of the HTV. The test will be performed after the HTV flight vehicle has been shipped to Tanegashima, Japan and preparing for launch. The checkout will be conducted using TDRSS, HTVOCS, JEMOCS and the HTV PFM. NASA will schedule and provide TDRSS availability for the checkout.

UTILITIES MATING TESTS (Test #16) The purpose of the Utilities Mating Test is to ensure the physical connection compatibility of power and data cables, and fluid lines for successful mate of the HTV and Node 2 on orbit. The objective of the utilities mating test is to confirm successful connection engagement and that each connection point is correctly matched to the corresponding connection point across the interface. The utilities mating process involves four phases: As-Design Audit, As-Built Audit, Mate-Fit Check , and On-Orbit Constraints Test (OOCT).

AS-DESIGNED AUDIT (16-1)

The purpose of the As Designed Audit is to demonstrate, through comparison of the ICD to the Drawings/Schematics, that there is high confidence that the fluids and cables jumpers between the HTV and Node 2 will successfully mate on orbit.

AS-BUILT AUDIT (16-2)

The purpose of the As Built Audit is to conduct a physical audit of the bulkhead feed through on the HTV element to demonstrate that the fluids and cables jumpers between the HTV and Node 2 will successfully mate on orbit.

MATE FIT CHECK (16-3)

The purpose of the Mate-Fit Check Test is to verify that the fluids and cables jumpers that mate the HTV to the Node 2 will physically mate without obstruction.

ON-ORBIT CONSTRAINTS TEST (16-4)

The purpose of the On Orbit Constraints Test is to:

DIGITAL PRE-ASSEMBLY (Test #17) The purpose of Digital Pre-Assembly (DPA) measurements of HTV flight hardware is to create an as-built model of the HTV to allow identification of any differences between as-designed and as-built hardware. DPA measurements define precise as-built berthing camera system target locations on the HTV. DPA data may be used to develop software-specific element berthing procedures using the berthing cue system. DPA measurements are taken to precisely define grapple fixture locations and orientations. This data is critical for developing SSRMS software used to support element removal of the EP and EP payloads from the HTV cargo area and berthing those same elements to the on-orbit ISS. DPA measurements may identify off-nominal variances on the mating surfaces, alignment and latching components, and also interferences involving externally mounted components, and fluid lines and cables which may encroach in the hardware 'stay out' zone. A measurement list defining HTV hardware to be measured by DPA will be coordinated between NASA and JAXA and may include EVA/EVR hardware, HTV flight modules (e.g., the Pressurized Logistics Carrier) and the Common Berthing Mechanism (CBM). DPA measurements are taken on flight hardware using digital photogrammetry equipment.

ON-ORBIT CONFIGURATION TEST (OOCT) (Test #18) This test has been combined with utilities mating tests.

PLC ACOUSTIC VIBRATION TEST (Test #19) The purpose of the PLC Acoustic Vibration Test is

SSP 50420-HTV1

Baseline C. To perform early risk mitigation testing of ISPR to HTV bonding 3-9

Appendix A - Acronyms and abbreviations

In addition to the acronyms and abbreviations defined in SSP 50420 Appendix A, the following acronyms and abbreviations are required for HTV 1. Inclusion of applicable acronyms and abbreviations herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of SSP 50420.

N/A No additional acronyms and abbreviations required A-1 Appendix B - glossary of terms

In addition to the terms defined in SSP 50420 Appendix B, the terms are required for HTV 1. Inclusion of applicable terms herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of SSP 50420.

N/A No additional terms or definitions are required

B-1 Appendix C - open work Table C-1 lists the specific To Be Determined (TBD) items in the document that are not yet known. The TBD is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBD item is numbered based on the section where the first occurrence of the item is located as the first digit and a consecutive number as the second digit (i.e., <TBD 4-1> is the first undetermined item assigned in Section 4 of the document). As each TBD is solved, the updated text is inserted in each place that the TBD appears in the document and the item is removed from this table. As new TBD items are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBDs will not be renumbered.

Table C-1 to be determined items

Table C-2 lists the specific To Be Resolved (TBR) issues in the document that are not yet known. The TBR is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBR issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBR 4-1> is the first unresolved issue assigned in Section 4 of the document). As each TBR is resolved, the updated text is inserted in each place that the TBR appears in the document and the issue is removed from this table. As new TBR issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBRs will not be renumbered.

table C-2 TO BE RESOLVED ISSUES

Table C-3 lists the specific To Be Supplied (TBS) issues in the document that are not yet known. The TBS is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBS issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBS 4-1> is the first unresolved issue assigned in Section 4 of the document). As each TBS is resolved, the updated text is inserted in each place that the TBS appears in the document and the issue is removed from this table. As new TBS issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBSs will not be renumbered.

table C-3 TO BE supplied ISSUES

C-2

Appendix D - bILATERAL jOINT VERIFICATION TESTs table d-1 HTV-ISS I/F JOINT VERIFICATION TEST SHEETS SUMMARY (page 1 of 2)

End to End Test

NASA

JSC/Japan

JAXA

Japan/JSC

HTV/TDRSS/GS End to End Checkout (15-3)

table D-1 HTV-ISS I/F JOINT VERIFICATION TEST SHEETS SUMMARY (page 2 of 2) Utilities Mating Test

Other

NASA

JSC

As-Built Audit (16-2)

Other

JAXA

Japan

Mate-Fit Check (16-3)

Other

JAXA

Japan

PCS and RWS Display Data Compatibility Test

D-2

NASA/JAXA BI-LATERAL VERIFICATION PLAN –

TEST SHEET #1

1 Test 1A: HTV Proximity Communication System (PROX) Input/Output (I/O) Risk Mitigation Test

2 Lead Agency: JAXA Test Location: JAXA/Mitsubishi Electric Corporation (MELCO) Testing Facility, Japan Type: Bi-lateral Software Interface Test

3 Requirements:

As minimum the subset of requirements listed below in the Software Interface Control Document Station Management and Control to International Space Station Book 35, Proximity Communications system Interface – SSP 41175-35 will be tested but none will be verified during this test Implemented Mode Code Definitions; Stats Word BIT Usage; Cyclic Data Acquisition; Broadcast Sync; Broadcast Ancillary Data; Bus Failure Detection, Isolation and Recovery (FDIR) Bus Control; Standard Command

4 Purpose:

Perform the early-phase software I/O risk mitigation test To detect issues with the requirements from the SW ICD identified in section 3 of this document To reduce the need for redesign and re-work that could impact the development scheme of PROX hardware and software

5 Identification of test set-up, Equipment needed and Test Facility:

5.1 Test Set-up

Representative test set-up is shown in figure 5.1-1. Test Plan will contain details.

5.2 Equipment Needed

5.2.1 Equipment Supplied by JAXA

PROX Base Band Processor (BBP) – Engineering Model (EM) PROX – EM Software (latest version available) Ground Support Equipment including controller PC for command and data interface, and appropriate test model Cables and connectors within JAXA responsible region depicted in Figure 5.1-1 and details defined in the test plan Extension power cables for NASA GSE

5.2.2 Equipment Supplied by NASA

Enhanced Space Station (ESS) Command & Control (C&C) Multiplexer/Demultiplexer (MDM) Flight Equivalent Unit (FEU) Command & Control Software (CCS) with HTV test functionality.

PASS 3200 Bus Tester Simulations for MDM

MATE

Cables and connectors within NASA responsible region depicted in figure 5.1-1, and details defined in the test plan.

Power conditioner for NASA supplied equipment.

5.3 Test Facility

The tests will be performed at the testing facility of MELCO Kamakura Works in Japan.

Figure 5.1-1 PROX I/O Test Configuration

6 Test parameter and Success Criteria:

The Test Plan will document the parameters and success criteria.

7 Responsibilities of Lead Agency and Partner:

7.1. Responsibility of JAXA:

As Lead for the test, JAXA will:

Provide inputs, review, and concur with the Test Plan Generate, and incorporate NASA procedures and provide the Test Procedures Generate and provide procedures necessary to support the utilization of Ground support Equipment (GSE) or other equipment required for test execution Provide the personnel and technical expertise for all phases of the test, including assistance (if required) to the Partner during set up of test equipment Co-Chair the Boards Be the Test Director Run the execution of the test Review and provide inputs to the Quick-Look report (QLR) Generate, incorporated NASA inputs, and provide the Final test Report

7.2. Responsibility of NASA:

As Partner for the test, NASA will:

Generate the Test Plan and incorporate JAXA corrections Review the JAXA developed Test Procedures and generate the Procedure(s) that are necessary to support the utilization of NASA equipment Provide the personnel and technical expertise for all phases of the test and, in particular, during execution of the test Ship the equipment necessary for the test, and track it to ensure that it arrives at the final destination in due time Inspect equipment after unpacking Coordinate with test Lead in setting up of equipment Set up the equipment and declare its readiness After the test, dismantle the test equipment pack it and prepare it for shipping.

Prepare documents, process and execute steps for shipment of equipment back to Houston Co-Chair the Boards Assist in running of the test Generate, incorporate JAXA inputs, and provide the QLR.

Review, provide inputs, and concur to the Final Test Report

8 Test schedule execution:

Shipping details will be documented in a separate document to ensure changes or updates can be controlled. A template will be established for any shipments to Japan necessary to support testing in the facilities where development of the PROX or HTV is being conducted. The following document will provide shipping details: “International Space Station (ISS) to H-II Transfer Vehicle (HTV) C&DH Shipping Plan.”

Hardware On-dock: No later than Test Date – 5 days [Includes setup and readiness check] Test Readiness Review: Test Date – 1 day Test duration: 5 working days Target Test date: May 16, 2005. Actual test date will be coordinated via the Schedule Issue/Change Form (SIF) and approve by the MASCB Post Test Review: End of Test + 1 day Quick Look Report: End of joint Test 1B + 5 days Final test Report: End of Test + 4 weeks

Approvals:

NASA Avionics & Software IP Integration Manager (HTV)

JAXA HTV CDH Engineer

NASA IP Element Manager

JAXA HTV Project Manager

NASA T&V Manager for HTV

Chairman, NASA T&V Control Panel

SSP 50420-HTV1

Appendix E - bILATERAL jOINT VERIFICATION TEST SHEETS

E-4

NASA/JAXA BI-LATERAL VERIFICATION TEST SHEET #2

1. Test 2: HTV-DH RT Validation Test Deleted

E-5

NASA/JAXA BI-LATERAL VERIFICATION TEST SHEET #3

1. Test 3 : Test 2A-PROX Software Interface Test

2. Lead Agency: NASA Location: SDIL, NASA in Houston

HTV SW shall complete the FQT program.

SW ICD Station Management and Control to ISS Book 35, Proximity Communications System Interface (SSP41175-35)- Basic version

4. Purpose of the Test and Method of Implementation:

4.1 Purpose of the Test:

JAXA to verify PROX Flight Software conformance to the SW ICD – SSP 41175-35.

Early integration test for USOS to demonstrate commanding, telemetry routing and software functionality across the USOS to HTV-PROX interface using the best available engineering SW release available

4.2 Method of Implementation:

Detailed test objectives will be defined and agreed to in the Test Plan and will include a subset of the following SSP 41175-35 requirements, based on functionality available in the USOS engineering software releases under test.

Remark: Section 3.1.2.3.5 – C&C MDM and PROX BBP RT FDIR will be conducted as a demonstration in this test 2A.

A representative test set-up for the FEU configuration is shown in Figure 1 for the software interface test. The Test Plan will contain a detailed description of the test configuration.

· PROX BBP-A –FEU (can be set as both BBP-A and BBP-B)

· PROX Flight SW Command and Telemetry PC controller

· Ground Support Equipment including:

· PROX /TRX interface to confirm TRX H&S monitor and control, command output to HTV and telemetry data input from HTV

· PROX/GPSR (JEM- SIGI) interface to confirm GPS H&S monitor and control, data input fro GPSR

· PROX/HCP interface to confirm HCP input and control

· PROX/another BBP interface to confirm another BBP monitor and control

· Cables and connectors within JAXA responsible region in Figure 1.

· Power Conditioner for JAXA supplied equipment as necessary.

5.2.2 Equipment Supplied by NASA

· Enhanced Space Station (ESS) Command & Control (C&C) Multiplexer/Demultiplexer (MDM) Functional Equivalent Unit (FEU)

· Command & Control Software (CCS) with the appropriate HTV functionality

· Multiplexer/Demultiplexer Application Test Environment (MATE)

· Simulations as required for operation of the MDM to be used.

· PCS with the s/w capable of supporting the HTV test as best available

· PASS 3200 Bus Analyzer

· Cables and connectors within NASA responsible region in Figure 1.

5.3 Test Facility:

The test will be performed in the SDIL, NASA in Houston, Texas.

6. Test Parameters and Success Criteria:

The parameters and success criteria will be documented in Test Plan and Test Procedures.

BBP

A

BBP

A

BBP

B

BBP

B

HCP

Interface

(GSE)

HCP

Interface

(GSE)

TRX

Data I/F

(GSE)

TRX

Data I/F

(GSE)

SIGI

Data I/F

(PC)

SIGI

Data I/F

(PC)

Controller (PC) TLM Check CMD Generate TLM Generate CMD Check

PCS

PCS

C&C Simulations

MAT

E 1553B

BBP

A

BBP FEU

BBP-A

(BBP-B)

BBP

B The other

BBP I/F

(GSE)

HCP

Interface

(GSE)

TRX

Data I/F

(GSE)

TRX

Data I/F

(GSE)

SIGI

Data I/F

(PC)

Controller (PC) TLM Check CMD Generate TLM Generate CMD Check 1553B

CB EXT

NASA Test Equipment

PASS 3200

Bus Monitor

PCS

PCS

PCS

PCS

MDM

CES

PROX (BBP) FEU Test Equipment

(CB EXT

2)

SIG

Data

(GSE)

HCP

Interface

(GSE)

Figure 1 – PROX Software Interface Test Configuration (Joint Test 2A) (RWS should be deleted. It is not listed in section 5.2.2 )

7.Responsibilities of the Lead Agency and Partner:

7.1 NASA Responsibilities

As Lead for the test, NASA will:

· Generate the Test Plan and incorporate JAXA inputs

· Generate the Test Procedure(s) including those necessary to support the utilization of NASA equipment and incorporate JAXA inputs

· Provide the personnel and technical expertise for all phases of the test

· Coordinate with JAXA in integrating of test equipment

· Co-Chair the Boards

· Be the test Executer of the test

· Run execution of the test

· Generate and provide the Quick-Look Report (QLR)

· Generate, incorporate JAXA comments to, and provide the Final Report

7.2 JAXA Responsibilities

As partner for the test, JAXA will:

· Review and concur the Test Plan

· Provide NASA inputs to and review test procedures. Generate and provide any procedures necessary to support the utilization of JAXA Ground Support Equipment (GSE) or other equipment required for test execution

· Ship the equipment necessary for the test, and track it to ensure that it arrives at the final destination in due time

· After unpacking, set up the equipment and declare its readiness

· Coordinate with Lead in setting up of equipment and support of its integration

· After the test, dismantle the test equipment, pack it, and prepare it for shipping.

· Prepare documents, process and execute steps for shipment of equipment back to Japan

· Provide the personnel and technical expertise for all phases of the test, including assistance (if required) to the Partner during set up of test equipment

· Co-Chair the Boards

· Assist in running of the test

· Review and provide inputs to the QLR

· Review, provide inputs and comments to, and concur with the Final Report

8. Schedule of Execution:

· See the following document for shipping details: “International Space Station (ISS) to H-II Transfer Vehicle (HTV) C&DH and Software Interface Test Shipping Plan Hardware On-dock: No later than Test Date - 5 days [includes setup and readiness check]

· Dry Run Test Duration: 5 working days

· Test Readiness Review: Test Date - 1day

· Test Duration: 10 working days

· Target Test date: No earlier than Dec. 1, 2006. The actual test date will be coordinated via the SIF and approved by the MASCB

· Post Test Review: End of Test + 1 day

· Quick Look Report: End of Test + 2 days

· Equipment packed for shipping: End of Test + 5 days

· Final Test Report: End of Test + 4 weeks

9. Concurrence:

_______/signed/ ________________________ ___11/30/06______ Diep Nguyen Date NASA ISS Avionic & Software IP Integration Manager (HTV)

Yuusuke Suzuki Date JAXA HTV Avionic Function Manager

Bob Zurawski Date NASA, HTV T&V manager

Quan Le Date NASA, Launch Package Manager

Rafael Garcia Date T&V CP Chair

E-11

NASA/JAXA BI-LATERAL VERIFICATION TEST SHEET #4

1. Test 1B: HTV Data Handling System (HTV-DH) software Input/Output (I/O) Risk Mitigation Test

2. Lead Agency: JAXA Location: JAXA/Mitsubishi Electric Corporation (MELCO) Testing Facility, Japan Type: Bi-lateral Software Interface Test

3. Requirements:

As minimum the subset of requirements listed below in the Software Interface Control Document Station Management and Control to International Space Station Book 35, H-II transfer vehicle Interface – SSP 41175-35, basic version will be tested, but none of these requirements will be verified during the test Implemented Mode Code Definitions; Stats Word BIT Usage; Cyclic Data Acquisition; Broadcast Sync; Broadcast Ancillary Data; Bus Failure Detection, Isolation and Recovery (FDIR) Bus Control; Standard Command

4. Purpose:

· Perform the early-phase software I/O risk mitigation test To detect issues with the requirements from the SW ICD identified in section 3 of this document To reduce the need for redesign and re-work that could impact the development scheme of HTV-DH hardware and software

5. Identification of test set-up, Equipment Needed and Test Facility:

Test Set-up.

Representative test set-up is shown in figure 5.1-1. Test Plan will contain details.

Equipment Needed

5.2.1 Equipment Supplied by JAXA

HTV-DH Engineering Model (EM) HTV-DH EM Software latest versions available Ground Support Equipment (GSE) including controller PC for command and data interface, and appropriate test model Cables and connectors within JAXA responsible region in Figure 5.1-1 Extension power cables for NASA GSE

5.2.2 Equipment Supplied by NASA

Enhanced Space Station (ESS) Command & Control (C&C) Multiplexer/Demultiplexer (MDM) Flight Equivalent Unit (FEU) Command & Control Software (CCS) – Latest release with the appropriate HTV functionality to support test requirements as specified in the test plan Multiplexer/Demultiplexer Application Test Environment (MATE) Internal MDM FEU Internal MDM Software – Latest release with the appropriate HTV functionality to support test requirements as specified in the test plan Simulations as required for operation of the MDMs to be used PASS 3200 Bus Tester Cables and connectors within NASA responsible region in Figure 5.1-1 Power Conditioner for NASA supplied equipment.

Figure 5.1-1: HTV-DH I/O Test Configuration Note: Data flow in LB-SYS-N2 must be monitored for INTSYS/HTV-DH Interface, but CB EXT is not necessary to monitor from the point of INTSYS/HTV-DH IF (CB EXT in this test should be monitored from the point of CCS/INTSYS I/F, but this is beyond JAXA responsibility.

5.3 Test Facility

The tests will be performed at the testing facility of MELCO Kamakura Works in Japan.

6. Test parameter and success criteria:

The Test Plan will document the parameters and success criteria.

7. Responsibilities of Lead Agency and partner:

7.1. NASA Responsibilities:

As Partner for the test, NASA will:

Generate the Test Plan and incorporate JAXA corrections Review the JAXA developed Test Procedures and generate the Procedure(s) that are necessary to support the utilization of NASA equipment Provide the personnel and technical expertise for all phases of the test and, in particular, during execution of the test Ship the equipment necessary for the test, and track it to ensure that it arrives at the final destination in due time Inspect equipment after unpacking Coordinate with test Lead in setting up of equipment Set up the equipment and declare its readiness After the test, dismantle the test equipment pack it and prepare it for shipping.

Prepare documents, process and execute steps for shipment of equipment back to Houston Co-Chair the Boards Assist in running of the test Generate, incorporate JAXA inputs, and provide the QLR.

Review, provide inputs, and concur to the Final Test Report

7.2. JAXA Responsibilities:

As Lead for the test, JAXA will:

Provide inputs, review, and concur with the Test Plan Generate, and incorporate NASA procedures and provide the Test Procedures Generate and provide procedures necessary to support the utilization of Ground support Equipment (GSE) or other equipment required for test execution Provide the personnel and technical expertise for all phases of the test, including assistance (if required) to the Partner during set up of test equipment Co-Chair the Boards Be the Test Director Run the execution of the test Review and provide inputs to the Quick-Look report (QLR) Generate, incorporated NASA inputs, and provide the Final test Report

8 Test schedule execution:

Shipping details will be documented in a separate document to ensure changes or updates can be controlled. A template will be established for any shipments to Japan necessary to support testing in the facilities where development of the PROX or HTV is being conducted. The following document will provide shipping details: “International Space Station (ISS) to H-II Transfer Vehicle (HTV) C&DH Shipping Plan.”

Hardware On-dock: No later than Test Date – 5 days [Includes setup and readiness check] Test Readiness Review: Test Date – 1 day Test duration: 5 working days Target Test date: May 20, 2005. Actual test date will be coordinated via the Schedule Issue/Change Form (SIF) and approve by the MASCB Post Test Review: End of Test + 1 day Quick Look Report: End of joint Test 1B + 5 days

1. Concurrence

NASA Avionics & Software IP Integration Manager (HTV)

JAXA HTV CDH Engineer

NASA IP Element Manager

JAXA HTV Project Manager

NASA T&V Manager for HTV

Chairman, NASA T&V Control Panel

E-15

NASA/JAXA BI-LATERAL VERIFICATION TEST SHEET #5

1. HTV-DH RT Validation Test Deleted

E-16

HTV BI-LATERAL VERIFICATION TEST SHEET #6

1. Test #6: HTV-DH Software Interface Test (Joint Test 2B)

2. Lead Agency: NASA

3. Source of Test Requirements

SSP 41178-35 Basic (with approved PIRNs) Software Interface Control Document Internal Multiplexer/Demultiplexer to International Space Station Book 35, H-II Transfer Vehicle Interface