SSP_50420-HTV3-Baseline.docx

SSP 50420-HTV3

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

HTV3

International Space Station Program

Baseline

September 2011

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, annex 3: htv3 The Vehicle Office and the Japan Aerospace Exploration Agency (JAXA) are responsible for the maintenance and development of SSP 50420-HTV3 which defines the verification test sheets for the integration and verification of the HTV3 segment to the International Space Station (ISS). This document is under the control of the International Space Station Vehicle Control Board (VCB) bi-laterally with JAXA.

i

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, Annex 3: htv3

CONCURRENCE

september 2011 ii

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, Annex 3: htv3

CONCURRENCE

september 2011

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv, annex 3: htv3

LIST OF CHANGES

september 2011 All changes to paragraphs, tables, and figures in this document are shown below:

Board Name

Entry Date

Change

Paragraph(s)

November 2011

Baseline

All

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) Annex 3 for the H-II Transfer Vehicle (HTV) defines the verification test sheets for the integration and verification of the HTV3 segment to the International Space Station (ISS).

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

SCOPE

This NASA/JAXA BIVP Annex 3 defines the data, products, tasks, and planning agreements for the integration and verification of the HTV3 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, the SSP 50420 document 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

SSP 50420-HTV3

Baseline The Test Sheets of Appendix D 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 of each test sheet will be maintained in the International Space Station Electronic Document Management System (EDMS).

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 HTV3. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

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 HTV3. These reference documents may or may not be specifically cited within the text of this document.

2-1

SUMMARY OF VERIFICATION ACTIVITIES DESCRIPTION

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

INTEGRATED HTV STAGE TEST (Test #8) The purpose of the Integrated HTV Stage Test is to test integrated PROX, HTV flight software and US Segment flight hardware (CCS, INTSYS, RWS, PCS, etc.) system level functionality and compatibility including:

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

HTV/TDRSS/GS End to End Checkout (Test #15-3) The purpose of the HTV/TDRSS/GS End to End Checkout is to check end-to-end command and telemetry dataflow for TDRSS including:

A. SSIPC/HTVOCS is able to receive HTV telemetry via the TDRSS link B. Transmission of processed TDRSS link HTV real-time telemetry from SSIPC/HTVOCS to MCC-H/BCC-HOSC as send-back telemetry C. SSIPC/HTVOCS is able to send commands to HTV via the TDRS link.

TDRSS/HTV INTERFACE TEST CATEGORY 1 FOR JAXA DOMESTIC TRANSPONDER (Test #24) The purpose of the TDRSS/HTV Category 1 Compatibility Test for JAXA Domestic Transponder is to test the HTV functional/performance interface with the TDRSS. The test is performed during the HTV development phase using an HTV Engineering Model (EM) of JAXA domestic transponder. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed to address requirements in the SSP 50273, HTV Segment Specification for the HTV to send and return data destined for the HTVCC via the new JAXA developed transponder, 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/HTV INTERFACE TEST CATEGORY 2 FOR JAXA DOMESTIC TRANSPONDER (Test #25) The purpose of the TDRSS/HTV Category 2 Compatibility Test for JAXA Domestic Transponder is to verify the HTV functional/performance interface with the TDRSS. The test is performed using an HTV Protoflight Model (PFM) of JAXA domestic transponder. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed to verify requirements in SSP 50273, HTV Segment Specification for the HTV to send and return data destined for the HTVCC via the new JAXA developed transponder, 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.

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.

3-2

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 HTV3. 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 In addition to the terms defined in SSP 50420 Appendix B, the terms are required for HTV3. 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 Bilateral JOINT VERIFICATION TEST SHEET SUMMARY (page 1 of 2) Test Number

table d-1 HTV-ISS I/F Bilateral JOINT VERIFICATION TEST SHEET SUMMARY (page 2 of 2) Test Number

X

X

X

X

D-2

Appendix e - bILATERAL jOINT VERIFICATION TEST sheets

HTV3 BI-LATERAL VERIFICATION TEST SHEET #8

1. Test 8: HTV3 Stage Joint Test

2. Lead Agency: NASA Location: SDIL, NASA Houston Type: Joint Bilateral Test of ISS/HTV command and data transfer with final flight software at system-level verification

3. Requirements Source:

Prerequisite: All flight software shall be verified or have under gone the Flight Qualification Test (FQT) validation process prior to formal stage testing.

Requirements for this test will be explicitly defined via DVOs (Detailed Verification Objectives) and/or RVA (Re-Verification Assessments) Requirements used to formulate the DVOs may include material from the following documents:

· Software related documents, especially related with HTV command/telemetry data transmission, control and display such as SSP41000: ISS segment spec SSP41162: USOS Segment Spec SSP50350: RWS CCTV Screen Overlay Requirements, Annex 1 SSP50337: Software Requirements Specification for MSS GUI, Book 2 SSP50754: HTV Crew Monitoring Requirements JSC26975: PCS User Display Requirements Specification SSP41175-10: C&C MDM to CEU Software ICD (for HTV data display on RWS)

- HTV related documents such as SSP50273: Segment Specification for HTV SSP50438, Part1: ISS to HTV Interface Control Document (ICD) SSP41175-35: C&C MDM to PROX Software ICD (for command and data item, i.e., IPCL aspects only) SSP41178-35: INT MDM to HTV Software ICD

4. Purpose of Test and Way of Implementation:

4.1 Purpose:

To test integrated PROX and HTV flight software and US Segment flight software (CCS, INTSYS, RWS, PCS, etc.) system-level functionality and compatibility considering multiple visiting vehicle configuration including but not limited to

· Command and data exchange between PROX, HTV and ISS for detached (berthing / de-berthing)

· Command and data exchange between HTV and ISS during attached phase through (1) the INT MDM and (2) via PROX as the back up command/data path)

· HTV/PROX caution and warning interactions as they affect the rest of the ISS

· ISS and HTV/PROX synchronization on frame count

· Station Management and Control functionality (examples: Bus/RT communication and FDIR functionalities, events)

· Overall consistency of displayed data on the Video Overlay, the Portable Computer System, and the PROX Hardware Command Panel LEDs.

· Successful commanding from US interfaces and proper HTV responses, including telemetry

· Configurations which include the Proximity, ready for SSRMS grapple, berthing/de-berthing and released from the SSRMS in nominal and off-nominal cases

4.2 Way of Implementation:

Detailed requirements for this test will be explicitly defined via DVOs (Detailed Verification Objectives). DVOs are replaced by RVAs (Re-verification Assessments).

· DVO

· DVOs define the integrated verification strategy (e.g., test, inspection, analysis etc.) that are required to demonstrate proper system-level functionality across multiple modules and software products (horizontally)

· Stage-Testing DVOs are agreed to by Subsystem/Technical team and Hardware and Software Integration team (HSI) prior to baselining

· DVOs are baselined /re-baselined by Test and Verification (T&V) Control Panel

· DVOs are closed by Data Assessment Reports

· Preliminary Stage-testing DVOs versions due to HSI 6 months prior to start of Stage Formals

· Final (baselined) Stage-testing DVO versions due to HSI 3 months prior to start of final Stage Formals

· JAXA specific DVOs can be included in the stage testing but must be submitted to NASA for review to determine if the DVO can be satisfied in the test environment for Stage testing. The process and the dates for submittal as well as the exchange of DVOs for partner review will be discussed and agreed upon at the Stage test Technical interchange meeting (TIM) and documented in the protocol and test plan as required.

The Stage test is a multi-CSCI test. The DVOs are typically focused on the entire space station assembly for a given stage or increment. There will be objectives focused on USOS software and other IP software configurations (for example, Service Module and the Columbus Module). The stage test exercises the software interfaces and interactions across all elements. .

The stage test schedule, plan, and process will be documented via SIF, test plan. Deviation will be discussed via the AST and/or stage test TIM as needed.

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

The HTV stage test utilizes the existing HTV avionics simulators located in the Software Development and Integration Laboratory (SDIL) at JSC.

5.1 Test Set-up

A representative test set-up of JAXA HTV responsible region is shown in Figure 1 for the stage verification software interface test. The final test configuration and test equipment details will be included in the Stage Test Plan.

Refer to ISS and HTV Avionics Simulators (ASIM) SDIL ICD for JAXA provided HW. See Figure 1 test configuration Software:

Updated PROX, HTV flight software and simulated software will be delivered to MBF and loaded to the HTV ASIM as required. Ref to HTV stage test SIF for details

5.2.2 Equipment Supplied by NASA: ref test plan for details

The equipment to be used for the Stage Test is all the components that make up a complete stage and will consist of the items in the SDIL Integrated Test Rig (ITR) or SVF lab. The items that will be specifically used during the portion of testing with the HTV equipment will include, at a minimum, the following:

· C&C MDM FEU and Command & Control Software (CCS)

· Internal MDM FEU and Flight Software

· Guidance, Navigation and Control MDM FEU and Flight Software

· Multiplexer / De- multiplexer Application Test Environnent (MATEs) and software

· PCS laptop and software

· RWS FEU, software and simulation

· MIL-STD-1553 bus monitoring system/devices

· MIL-STD-1553 Cables

· Power Sources

5.3 Test Facility:

The test will be performed in the NASA Software Development and Integration Laboratory (SDIL) in Houston, Texas

6. Test Parameters and Success Criteria:

Test parameters and success criteria will be documented in the test plan.

7. Responsibilities of the Lead Agency and Partner:

7.1 NASA Responsibilities:

As Lead for the test, NASA will:

· Generate and provide the Test Plan with inputs from the Partner

· Generate the ISS DVOs and RVAs to define the test objectives

· Review HTV specific DVOs with JAXA as required

· Generate and provide the Test Procedures with inputs from the Partner

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

· Provide final concurrence of DVOs and RVAs

· Be the Test Director

· Run the execution of the test

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

· Generate and provide the Final Report

· Certify the results of the Test.

7.2 JAXA Responsibilities:

As Partner for the test, JAXA will:

· Provide inputs and review the Test Plan and RVAs

· Provide HTV JAXA specific detailed test objectives in the DVO format provided by NASA

· Review the Test Procedures and provide inputs and generate the Procedure(s) that are necessary to support the utilization of their equipment

· Provide the personnel and technical expertise for all phases of the test and, in particular, during execution of the test dry run and run for records.

· Ship additional required equipment including updated software for the test as required if required and track it to ensure that it arrives at the final destination

· Inspect equipment after unpacking

· Coordinate with Lead in setting up of equipment

· Set up the equipment and declare its readiness

· Assist in running the tests during the dry run and formal run

· Review the QLR

· Review the Final Report

· If certifying JAXA HTV Software, JAXA will provide the Quality Assurance and configuration management support required to satisfy the JAXA processes for certification per S/W Management Plan and SIF

8. Schedule of Execution:

Estimated schedule is listed below. Actual schedule for the test will be coordinated via the SIF (Schedule Issue/Change Form) and associated approval process.

· Shipping of Equipment: Test equipment on dock at test start minus two (2) months.

· Software Certification: Software and displays test-ready at test start minus one (1) month

· Test Readiness Review: TRR held at test start minus one (1) week

· Beginning Test: NET 24 October 2011

· Test Duration: No more than twelve (12) days

· Post Test Review: Test completion plus one (1) day

· Quick look Report: Test completion plus one (1) week

· Final test and verification Report: Test completion plus two (2) months

9. Approvals:

NASA HSI Manager

NASA/HTV AVSW IP Integration Manager

JAXA HTV Avionics Module Function Manager

JAXA HTV Test & Verification Lead

NASA HTV Test & Verification Lead

JAXA HTV Deputy Project Manager

JAXA HTV Launch Package Manager

Chairman, NASA T&V Control Panel

E-6

JAXA/NASA BI-LATERAL VERIFICATION TEST SHEET #15-1

1. Test #15-1: HTV/ISS/Ground Segment End to End Test

2. Lead Agency: NASA Test Location: MCC-H, NASA Houston SSIPC/HTVOCS, JAXA Tsukuba Space Center SDIL, NASA Houston

Test Type: Joint Bi-Lateral Test of HTV/ISS/Ground Segment Command and Data Signal Processing

3. Source of Test Requirements:

SSP 50273, Segment Specification for the H-II Transfer Vehicle;

SSP 54500, International Ground System Specification Document.

SSP 50273 Requirements:

3.2.1.3 Proximity Operation Phase and Departure Phase Capability (various paragraphs related to Ground Segment capabilities)

3.2.1.3.2.3 Capability: Communication with HTVCC via MCC-H

3.2.1.5.4 Capability: Acquire function and status data

SSP 54500 Requirements:

D.3.7.2.5 Provide Data for Uplink D.3.7.3.6 Support Downlinked Data

The test plans for specific requirements verified in end-to-end testing are defined in SSP-50931, NASA/Japan Aerospace Exploration Agency (JAXA)/HII-Transfer Vehicle – 3 (HTV3)/International Space Station (ISS)/Ground Segment End-To-End Test Plan and Procedure.

4. Test Objectives:

a. To verify SSIPC/HTVOCS is able to receive HTV/PROX telemetry in all ISS S-Band telemetry formats and command the HTV/PROX via the U.S. Ground Segment in the PROX Link using the HTVOCS to EIS direct command link and via the JEMOCS to EIS command link.

b. To verify SSIPC/HTVOCS is able to receive HTV telemetry in all ISS S-Band telemetry formats, and command the HTV via the U.S. Ground Segment in the C&D H 1553B Link using the HTVOCS to EIS direct command link and the JEMOCS to EIS command link.

c. To demonstrate MCC-H can send commands to HTV through the ISS-to-PROX link.

5. Identification of Test Set-Up, Equipment and Facilities

5.1 Test Setup

The test set-up for HTV/ISS/Ground Segment End-to-End testing is summarized in Figure 5-1. The configuration of ISS/HTV simulators/FEU at SDIL in Houston will be similar to that utilized for Stage Test. The ISS/HTV simulators will be configured different for HTV proximity phase and for attached phase testing. Specific test configurations for end to end tests are documented in the HTV/ISS/Ground Segment End-to-End Test Plan.

SSCC/MCC-H

J A X A G W C D S S F E P

CMD

SRV

E I S MCC-H ISS Workstation

SSIPC

CMD

TLM

TLM

SDIL

C&C

MDM

INT

MDM

GNC

MDM

PROX BBP FEU

HTV CDP/ BIU/GCC Simulator/

BTE

HCP

HTV MCU FEU

CMD

TLM

PCS

CMD

J A X A G W MCC-H Video System DVIS Audio System Audio Video

JEM

Flt Ctrl System

JEM OCS

HTV OCS

HTV

Flt Ctrl System HTVOCS Direct Cmd Link

HTV/PROX Simulators/FEU ISS Simulators

Figure 5-1: HTV/ISS/Ground Segment End-to-End Test Set-Up

5.2 Test Equipment

5.2.1 Equipment Supplied by NASA

5.2.1.1 SDIL Equipment Supplied by NASA:

The equipment to be used in the SDIL for this test will be the subset of the HTV stage test configuration:

· C&C MDM FEU and Command & Control Software (CCS)

· Internal MDM FEU and Flight Software

· Guidance, Navigation and Control MDM FEU and Flight Software

· Multiplexer / de multiplexer Application Test Environment (MATEs) and software

· PCS laptop and software

· 1553 bus monitoring system/devices

· MIL-STD-1553 Cables

· Power Sources

5.2.1.2 MCC-H Equipment supplied by NASA:

· Standard MCC-H Services to support ISS Operations.

5.2.2 Equipment Supplied by JAXA

5.2.2.1 SDIL Equipment Supplied by JAXA:

· SDIL HTV Avionics Simulator (refer to SDIL/HTV-Avionics Software Simulator ICD for detailed configuration

· HTV and PROX Updated Software, if applicable

5.2.2.2 SSIPC Equipment supplied by JAXA:

· Standard SSIPC Services to support JEM and HTV Operations.

5.3 Facilities

· MCC-H, Houston

· SSIPC/JEM OCS, Tsukuba, Japan

· SSIPC/HTV OCS, Tsukuba, Japan

· SDIL, Houston

6 Test Parameters and Success Criteria

· Details of the test parameters and success criteria will be documented in the test plan and procedures.

· Successfully receive and monitor telemetry at SSIPC/HTV OCS, MCC-H and PCS for HTV proximity operation and attached phases.

· Successfully send commands from SSIPC/HTVOCS, MCC-H and PCS to HTV in proximity operation and attached phases.

· Successfully send commands from MCC-H to HTV/PROX.

7 Responsibilities of the Lead Agency and Partner

7.1 As Lead for this Test, NASA Responsibilities Include:

· Input and review the Test Procedures.

· Generate test Plan and serve as Book Manager

· Provide the personnel and technical expertise for all phases of the test and, in particular, during the execution of the test

· Coordinate as Lead in setting up equipment and preparing MCC-H and SDIL facilities for the test.

· Be the test director

· Run the execution of the test where MCC-H is prime (i.e., Send commands from MCC-H)

· Generate and provide the quick look report from the test with JAXA inputs for JAXA facilities and the HTV test item.

· Review and Input on the test and verification Report from the Test

7.2 As Support for this Test, JAXA Responsibilities Include:

· Input and review the Test Plan

· Generate, incorporate NASA inputs, and provide the test procedures

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

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

· Inspect equipment (HTV/PROX simulators/FEU, etc.) after unpacking at SDIL, if required.

· Provide software support and displays (if required) to the Partner for execution of the test.

· Coordinate as Lead in setting up equipment and preparing SSIPC/HTVOCS for the test.

· Assist in running the test during formal runs.

· Run the execution of the test where SSIPC/HTVOCS is prime (i.e., Command and monitoring from HTVOCS)

· Review and Input on the quick look report from the test

· Prepare and provide the test and verification Report from the test

· Certify the results of the test

8 Schedule of Execution:

Estimate template/schedule is listed below. Actual schedule for the test will be coordinated via the SIF (Schedule Issue/Change Form) and associated approval process.

· Test Readiness Review: TRR per SIF

· Beginning of Test: October 24, 2011.

· Test Duration: 2 days (one (1) test day plus 1 day contingency)

· Post Test Review: Test completion plus one (1) day

· Quick look Report: Test completion plus one (1) week

· Final test and verification Report: Test completion plus two (2) months

9 Approvals:

NASA Ground Segment Control Board

JAXA HTV Avionics Module Function Manager

NASA H SI manager

NASA / HTV Avionics Software Integration Manager

JAXA Representative, GSCB

JAXA HTV Project Team T&V Lead

NASA HTV Test and Verification Lead

JAXA HTV System Function Manager

NASA IP Element Manager

Chairman, NASA ISS T&V Control Panel

JAXA/NASA BI-LATERAL VERIFICATION TEST SHEET #15-3

1. Test #15-3: HTV3/TDRSS/GS End to End Checkout

2. Lead Agency: JAXA Test Location: MCC-H, NASA Houston BCC-HOSC, NASA Huntsville SSIPC/HTVOCS/JEMOCS, Kagoshima Space Center (Tanegashima) NASA Space Network

Test Type: Joint Bi-lateral Checkout of HTV3/TDRS/GS Communication and Data Transmission Capability for TDRS Direct link.

3. Source of Test Requirements:

All function and capability of HTV/TDRSS/GS End to End communication were already confirmed in HTV/TDRSS/GS End to End Test conducted on September, 2008.

This checkout is not verification test but final confirmation of this communication path prior to the HTV3 launch. Thus there is no specification document for test requirement. All test requirements will be described in this test sheet and more detail will be described in the HTV3/TDRSS/GS End to End checkout Plan.

As reference, the following are the test requirements which were already verified or confirmed in HTV/TDRSS/GS End to End Test.

SSP 50273, Segment Specification for the H-II Transfer Vehicle; SSP 54500, International Ground System Specification Document.

SSP 50273 Requirements:

3.2.1.2.2.1 Capability: Communication with HTVOCS via TDRSS

3.2.1.3.2.2 Capability: Communication with HTVOCS via data relay satellites

3.2.1.3.2.5 Capability: Command Protection

The communication capability of the following 3 requirements will be verified by this test.

3.2.1.3.4.5 Capability: Proximity Rendezvous Maneuver Plan

3.2.1.3.4.6 Capability: Departure and Reentry Maneuver Plan

3.2.1.3.4.7 Capability: Initiation of AI Maneuver

3.2.1.7.1.1 Capability: Communication with HTVOCS via TDRS, SSSP

54500 Requirements:

D.3.7.2.4.1 Monitor and Assess HTV System Operation D.3.7.2.4.2 Execute On-Orbit HTV Operations D.3.7.2.5 Provide Data for Uplink D.3.7.2.6 Support Downlinked Data

4. Test Objectives:

· To check that SSIPC/HTVOCS is able to receive HTV telemetry via the TDRSS link

· To check the transmission of processed TDRSS link HTV real-time telemetry from SSIPC/HTVOCS to MCC-H/BCC-HOSC as send-back telemetry.

· To check that SSIPC/HTVOCS is able to send commands to HTV via the TDRS link .

5. Identification of Test Set-Up

5.1 Test Set-Up

The test set-up for HTV/TDRS/GS End-to-End Checkout is summarized in Figure 5-1. Specific test configurations for end to end checking are documented in the HTV3/TDRS/Ground Segment End to End Test Plan. In this checkout, TDRSS and HTV3 shall be utilized.

Figure 5-1: HTV3/TDRS/GS End-to-End checkout Set-Up

5.2 Equipment

5.2.1 Equipment Supplied by JAXA

· HTV3 (Avionics Module and Propulsion Module)

· HTV Ground Support Equipment (Power supplies, monitoring equipment, etc.)

· Tanegashima HTV Checkout Station (THCS)

· Standard SSIPC services to support JEM and HTV operations

5.2.2 Equipment Supplied by NASA

· Standard MCC-H/BCC-HOSC services to support ISS operations

· NASA Space Network (TDRS, WSC, GSFC)

5.3 Facilities:

5.3.1 JAXA Facilities

· SSIPC/JEM ODNS (Gateway), Tsukuba, Japan

· SSIPC/HTV OCS, Tsukuba, Japan

· STA2, SFA2, Tanegashima, Japan

· Tanegashima HTV Checkout Station (THCS), Tanegashima, Japan

5.3.2 NASA Facilities

· MCC-H, NASA Houston

· HOSC, NASA Huntsville

· NASA Space Network (GSFC, WSC)

6. Checkout Parameters and Success Criteria

a. Successfully receive and monitor HTV telemetry at the SSPIC/HTVOCS transmitted via the TDRSS link.

b. Successfully receive and monitor send-back telemetry at MCC-H/BCC-HOSC.

c. Successfully send encrypted commands to HTV from SSIPC/HTVOCS via the TDRS link, and HTV receives and processes commands from HTV OCS via TDRSS link.

7. Responsibilities of the Lead Agency and Partner

7.1 JAXA Responsibilities

As lead for the checkout, JAXA will:

· Generate and provide the Checkout Plan.

· Generate and provide the Checkout Procedures.

· Provide the personnel and technical expertise for all phases of the checkout and, in particular, during the execution of the checkout.

· Set up and prepare JAXA equipment and facilities for the checkout, including HTV PFM equipment, SSIPC/HTVOCS and THCS.

· Be the checkout director

· Run the execution of the checkout.

· Generate and provide the Quick Look Report from the checkout

· Generate and provide the Final Report from the checkout.

· Certify the results of the checkout.

7.2 NASA Responsibilities

In support of the test, NASA will;

· Review and provide inputs on the Checkout Plan.

· Review and provide inputs on the Checkout procedures.

· Provide the personnel and technical expertise for all phases of checkout and, in particular, during execution of the checkout.

· Set up and prepare NASA equipment and facilities for the checkout, including the NASA Space Network (SN) (GSFC, WSC), MCC-H and BCC-HOSC.

· Assist in running the checkout.

· Review and provide inputs on the Quick Look Report from the checkout.

· Review and provide inputs on the Final Report from the checkout.

8. Schedule of Execution:

The estimated template/schedule for execution of the checkout is listed below. The actual schedule for the checkout will be coordinated and approved by GSCB.

9. Approvals:

NASA Ground Segment Control Board (GSCB)

JAXA Representative, GSCB

JAXA HTV Avionics Lead

JAXA Test & Verification

NASA IP Element Manager

JAXA HTV Systems Lead

NASA Test and Verification

ISS Test and Verification Control Panel (T&VCP)

NASA Network Director, GSFC

JAXA/NASA BI-LATERAL VERIFICATION TEST SHEET #24

1.0 Test #24: TDRSS/HTV Interface Test Category 1 For JAXA Domestic Transponder

3.0 Source of Test Requirements

Test requirements for the TDRSS/HTV Interface Test Category 1 for JAXA Domestic Transponder (CAT1d) are contained in the following documents.

450 SNUG

Space Network User’s Guide, Rev 8, June

KAE-99003 (JAXA No)

451-RFICD-

HTV/TDRS(NASA No)

Radio Frequency (RF) Interface Control Document (ICD) between the H-II Transfer Vehicle (HTV) and the Tracking and Data Relay Satellite system (TDRSS) of the NASA Spaceflight tracking and Data Network (STDN), NOTE: HTVCC participation in the CAT1d test is not required.

4.0 Test Objectives

The purpose of the CAT1d test is to test the HTV functional/performance interface with the TDRSS. The test is performed during the HTV development phase using an HTV Engineering Model (EM) of JAXA domestic transponder. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed based on the requirements in the SSP 50273.

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. Test Activities are described in the Test Plan for Engineering Model (EM) and Proto-Flight Model (PFM) H-II Transfer Vehicle (HTV) Transponder/TDRSS Compatibility Tests, GSFC/ISS HTV-CTP

5.0 Identification of Test set-up, Equipment needed, and Facility

5.1 Test Set-up

The test set-up is depicted in Figure 1.

Ground Forward Return HTV Transponder and

EGSE

GSFC

CTL/CTV

Test Equipment

TDRSS

RF

Figure 1: TDRSS/HTV Category 1 Compatibility Test Set-Up at the GSFC compatibility test laboratory

5.2.1. Equipment supplied by JAXA

· HTV IOS transponder (EM)

· HTV IOS diplexer (EM)

· EGSE with harness and connectors

5.2.2. Equipment supplied by NASA

· GSFC Compatibility Test Laboratory (CTL)

· Compatibility Test Van (CTV) test equipment with command and data handling simulator,

· Cable to HTV transponder for closed loop and RF relay test.

· TDRSS

· Facility/Ground Support Equipment

5.3 Test Facility

The test will be performed at Goddard Space Center in the NASA/GSFC Compatibility Test Laboratory (GSFC Building 25).

6.0 Test Parameters and Success Criteria

The CAT1d Test will be considered successful when the JAXA developed transponder is proved compatible with Tracking and Data Relay Satellites System in accordance with following documents. Test parameters are also shown in these documents.

· Radio Frequency (RF) Interface Control Document (ICD) between H-II Transfer Vehicle (HTV) and the Tracking and Data Relay Satellites System (TDRSS) of the NASA Spaceflight Tracking and Data Network (STDN)

· Tracking and Data Relay Satellites System (TDRSS) of the NASA Spaceflight Tracking and Data Network (STDN) and Space Network User’s Guide, 450 SNUG, Rev 8, June 2002.

· Test Plan for Engineering Model (EM) and Proto-Flight Model (PFM) H-II Transfer Vehicle (HTV) Transponder/TDRSS Compatibility Tests, GSFC/ISS HTV-CTP

7.0 Responsibility by Lead Agency and Partner

7.1 Responsibilities of Lead Agency

As Lead Agency for this test, NASA will

· Provide existing GSFC compatibility test procedures

· Identify, in co-ordination with JAXA, applicable NASA GSFC TDRSS compatibility test procedures for the HTV

· Generate the HTV/TDRSS compatibility test plan and test specifications

· Make US resources at GSFC Building 25 and the TDRSS resources available

· Provide facility arrangements for JAXA test article and equipment (i.e., compatible power, floor space, cooling)

· Provide necessary office accommodations for JAXA test personnel (i.e., work area, phone, fax, PC access)

· Assist in delivery of the JAXA equipment to the test location

· Set up the NASA equipment, and declare their readiness

· Act as Test Director and run the execution of the test

· After the test, pull down test configuration and assist JAXA with packing and shipment

· Generate the test and engineering evaluation report for the NASA GSFC compatibility test activities and provide to JAXA

· Provide the manning and technical expertise for all stages of the test activity, and in particular, for the execution of the test

· Co- chair the test related boards (pre-test/post-test/daily)

· Provide necessary office accommodations for JAXA test personnel (i.e., work area, phone, fax, PC access)

· Generate and provide the Quick Look Report (QLR) and the Final Test Report

7.2 Responsibilities of Partner Agency

As Partner Agency for this test, JAXA will

· Review the HTV/TDRSS compatibility test procedures

· Identify, in co-ordination with NASA GSFC, applicable NASA GSFC TDRSS compatibility test procedures for the HTV

· Review and agree on the test plan and test specifications

· Provide handling instructions for JAXA equipment

· Ship/deliver JAXA equipment to the NASA GSFC facility and after testing equipment back to JAXA

· Provide Quality Assurance as JAXA deems necessary

· Set up JAXA equipment necessary and declare its readiness for test

· Provide the manning and technical expertise for all stages of the test activity

· Receive the NASA GSFC compatibility test and engineering evaluation report

· Generate a test/engineering evaluation report for the JAXA provided equipment under test

· Co-Chair the test related boards (pre-test/post-test/daily)

8.0 Schedule of the Test Execution

The test duration will be 12 working days. Note that the actual execution on the tests should be completed within 7 working days. The Beginning Of Test (BOT) is in June 2008, and the End of Test (EOT) is July 2008.

8.1 Shipping of equipment

The equipment will be shipped early enough to meet an unpacking data at BOT minus 2 working days.

8.2 Preparation of Test Set-up

The test set-up will take 2 working days and will start as soon as the equipment is unpacked. The incoming inspections and set-up will be performed and completed at BOT minus 1 working day.

8.3 Performance of Test, Pre-Test, Post-Test, and Daily reviews Just prior to the NASA GSFC compatibility BOT, the pre-test review will take place and immediately after NASA GSFC compatibility EOT the post-test review will be performed. In addition, daily review of test activities will occur to discuss the results from previous day testing and to review upcoming test activities for the day of testing.

8.4 Preparation of Test Report

All results generated during the execution of the NASA, GSFC compatibility tests will be collected and assessed initially in a quick-look report to determine the success or the failure of the test and take the relevant measures. The formal NASA GSFC compatibility test report, including the HTV/TDRSS statement of compatibility, will be developed by NASA and delivered to JAXA and JAXA/ISS at EOT plus 60 working days..

8.5 Return of Equipment

The equipment will be shipped in a timely manner as determined by NASA and JAXA after the testing has been completed and both parties agree on packing, shipping, and delivery dates.

9.0 Approval

NASA Network Director for Human Space Flight

JAXA GTV Avionics & Software Lead

NASA C&T Lead

JAXA HTV Project Team C&T Engineer

NASA T&V Lead

JAXA HTV Project Team T&V Engineer

NASA IP Element Manager

JAXA HTV Launch Package Manager

JAXA/NASA BI-LATERAL VERIFICATION TEST SHEET #25

1.0 Test #25: TDRSS/HTV Interface Test Category 2 For JAXA Domestic Transponder

3.0 Source of Test Requirements

Test requirements for the TDRSS/HTV Interface Test Category 2 for JAXA Domestic Transponder (CAT2d) are contained in the following documents.

450 SNUG

Space Network User’s Guide, Rev 8,June 2002

KAE-99003

451-RFICD-HTV/TDRS

Radio Frequency (RF) Interface Control Document (ICD) between the H-II Transfer Vehicle (HTV) and the Tracking and Data Relay Satellite system (TDRSS) of the NASA Spaceflight tracking and Data Network (STDN),

4.0 Test Objectives

The purpose of the CAT2d test is to test the HTV functional/performance interface with the TDRSS. The test is performed during the HTV production phase using a Proto-Flight Model (PFM) of new JAXA domestic transponder, which is developed for HTV-3 and its subsequent flights. Testing of the HTV functional/performance interfaces with the NASA Space Network (SN) will be performed based on the requirements in the SSP 50273.

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. Test activities are described in, the Test Plan for the Engineering Model (EM) and Proto-Flight Model (PFM) H-II Transfer Vehicle (HTV) Transponder/TDRSS Compatibility Tests, GSFC/ISS HTV-CTP.

5.0 Identification of Test set-up, Equipment needed, and Facility

5.1 Test Set-up

The test set-up is depicted in Figure 1.

Ground Forward Return

HTV

Integrated Comm System

GSFC

CTL/CTV

Test Equipment

TDRSS

RF

Figure 1: TDRSS/HTV Category 2 Compatibility Test Set-Up at GSFC Compatibility Test Laboratory

5.2.1. Equipment supplied by JAXA

· HTV IOS transponder (PFM)

· HTV IOS diplexer (PFM)

· HTV CCSDS Processor (CDP) simulator

· EGSE with harness and connectors

· Clean Bench

5.2.2.