SSP_50420-HTV2-Baseline.docx

SSP 50420-HTV2

Baseline

NASA/JAXA Bilateral Integration and Verification Plan for HTV, Annex 2: HTV2

International Space Station Program

Baseline

December 2010

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

SSP 50420-HTV2

REVISION AND HISTORY PAGE

PREFACE

NASA/JAXA bilateral integration and verification plan for htv The Vehicle Office and the Japan Aerospace Exploration Agency (JAXA) is responsible for the maintenance and development of SSP 50420-HTV2 which defines the verification test sheets for the integration and verification of the HTV 2 segment to the International Space Station. 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

CONCURRENCE

December 2010 ii

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv

CONCURRENCE

december 2010

INTERNATIONAL SPACE STATION PROGRAM

NASA/JAXA bilateral integration and verification plan for htv

LIST OF CHANGES

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

Board Name

Entry Date

Change

Paragraph(s)

February 2011

Baseline

All

TABLE OF CONTENTS

APPENDIX

TABLE

iii

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

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

SCOPE

This NASA/JAXA BIVP Annex 2 defines the data, products, tasks, and planning agreements for the integration and verification of the HTV 2 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 C 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).

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

2-1

SUMMARY OF VERIFICATION ACTIVITIES DESCRIPTION

general 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 C.

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

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

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

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

HTV pre-launch check-out test (Test #15-3) The purpose of the HTV Pre-Launch Check-Out Test 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 within L-1 week of planned launch date, after the HTV has been integrated to the H-IIB launch vehicle and is preparing for launch at Tanegashima, Japan. The checkout will be conducted using TDRSS, HTVOCS, JEMOCS and the HTV PFM. NASA will schedule and provide TDRSS availability for the checkout.

SSP 50420-HTV2

Baseline

3-3

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

#15

NASA

JSC/Japan

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

D-1

Appendix E - bILATERAL jOINT VERIFICATION TESTs

HTV BI-LATERAL VERIFICATION TEST SHEET #8

1. Test 8: HTV Stage Joint Test

2. Lead Agency: NASA Location: SDIL, NASA Houston Type: Joint Bilateral Test of Final ISS/HTV flight software 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). 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 PROX and HTV flight software to US Segment flight software (CCS, INTSYS, RWS, PCS, etc.) system-level functionality and compatibility including but not limited to

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

· Command transmission and data processing 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, station moding, and load shed 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). .

· 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 process 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.

Hardware:

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 simulator 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

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

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

As Lead for the test, NASA will:

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

· Generate the ISS DVOs 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

· 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 DVOs

· 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 runs and run for records.

· Ship the required equipment including 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 runs and formal runs

· 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 of Dry Run Test: NET 4 October 2010

· Test Duration: Five (5) days

· Beginning of Formal Test: NET 11 October 2010

· Test Duration: Five (5) days

· (October 18th and 19th reserved for makeup)

· 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. Approval:

NASA HSI Engineer

NASA AVSW IP Integration Manager for HTV

JAXA HTV Avionics Module Function Manager

JAXA HTV Test & Verification Lead

NASA HTV Test & Verification Lead

JAXA HTV Function Manager

JAXA HTV Launch Package Manager

Chairman, NASA T&V Control Panel

SSP 50420-HTV2

Baseline

E-4

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 the HTV/ISS/Ground Segment End-to-End Test Plan.

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 Set-Up

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.

ISS Simulators

SSCC/MCC-H

N A S D A G A T E W A Y 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

C&W

PROX BBP FEU

HTV CDP/ BIU/GCC Simulator/ BTE

HCP

HTV MCU FEU

CMD

TLM

PCS

RWS

SSRMS

CMD

N A S D A G A T E W A Y 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

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

5.2 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

· RWS FEU, software and simulation

· 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 parmameters and success criteria will be documented in the test plan and procedures. Examples:

· 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 demonstrate that MCC-H can send commands 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: September 28, 2010

· Test Duration: three (3) days (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 / 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

E-11

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

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

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

Test Type: Joint Bi-lateral Checkout of HTV/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 HTV 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 HTV\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 TDRSS

SSP 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:

HTV pre-launch check-out test (Test #15-3)

A. To check that SSIPC/HTVOCS is able to receive HTV telemetry via the TDRSS link and MCC-H bent pipe.

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

C. To check that SSIPC/HTVOCS is able to send commands to HTV via the TDRS link and MCC-H bent pipe.

5. Identification of Test Set-Up

5.1 Test Set-Up

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

Figure 5-1: HTV/TDRS/Ground Segment End-to-End checkout Set-Up

5.2 Equipment

5.2.1 Equipment Supplied by JAXA

· HTV (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 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

· 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 and MCC-H bent pipe.

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

c. Successfully from SSIPC/HTVOCS to HTV sends send encrypted commands to HTV via the TDRS link and MCC-H bent pipe, and HTV receives and processes commands from HTV OCS via TRDRSS link and MCC-H bent pipe.

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.

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

· Inspect equipment (ARO laptop) after unpacking at HTVOCS

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

· 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

JAXA Representative, GSCB

NASA Network Director, GSFC

NASA MFSC GSCB Representative

____________/Signed/______________________ __5/26/10______ Hirohide Uematsu Date JAXA HTV Avionics & Software Lead

JAXA Test & Verification

NASA IP Element Manager

JAXA HTV Project Manager

NASA HTV Test & Verification Lead

ISS Test and Verification Control Panel (T&VCP)

E-13

Appendix F - Certifications of Qualification Table F-1 Certificate of Qualification

*Note: COQ’s located in EDMS HTV cabinet

Baseline

F-1

Appendix G - Sampling Process Reports Table H-1 Actual Process Sampling Activity Reports

*Note: Report located in EDMS HTV cabinet

G-1 image3.emf image4.emf image5.emf image6.png image7.emf image1.png image2.wmf