Tim.honeycutt

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

Integrated Testing at KSC Integrated Testing at KSC between Constellation between Constellation

SystemsSystems

Tim HoneycuttTim Honeycutt

February 2008February 2008

[email protected]@nasa.gov

321321--867867--65676567

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

2

KSC Constellation Project OfficeKSC Constellation Project Office

KSC Constellation Project Office

Logistics

Command, Control, and

CommunicationsLaunch Vehicle

Crew Vehicle Ground Systems (GS)

Project

Project Control

Systems Engineering & Integration

(including IT&V)

Operations & Integration

Business Staff Office

GS Project Support Office

GS Project Integration & Requirements

GS Project Management

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

3

Presentation OutlinePresentation Outline

• History of Multi-Element Integration Tests (MEITs)– MEIT Concept– Previous MEITs– Major Problems Found– Benefits

• Integrated Testing at KSC for the Constellation Program– Integrated Tests

• Multi-Element Integrated Tests (MEITs)• Flight Element Integrated Tests (FEITs)• Integrated Verification Tests (IVTs)

• Summary

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

4

HistoryHistory

• “Ship and shoot” was the strategy for the International Space Station Program (ISSP) during the early 1990’s

– It proposed transporting flight elements directly from the factory to the launch site and begin the mission without further testing.

– Factory level testing and element interface verifications at thesubsystem-level, and interface analysis were all that was planned.

• Before the end of that decade a shift in testing strategy occurred within the ISSP

– The ISSP adopted a more integrated approach for ground validation of it’s flight hardware.

– Availability of elements at the launch site created a feasible opportunity to test multiple elements together.

– The notion of validation testing on the ground was presented andaccepted by the ISSP due to the criticality of the on-orbit functionality, including safety concerns for the crew .

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

5

History (cont)History (cont)

• Multi Element Integration Tests (MEITs) and Integrated Systems Tests (ISTs)

– Risk mitigation tests performed on the ground, used for validating the operation of the flight elements and their systems in an environment that is as flight-like as possible.

– These tests were used to demonstrate the interoperability and functionality of Space Station elements as integrated “in-space”assemblies on the ground before they were assembled in space for the first time.

• Space Station element-to-element interface capability was verified as well as systems end-to-end operability with hardware and software.

• Mission Sequence Testing (MST), also known as “end-to-end”integration testing, included a full-up configuration with the Mission Control Center, Tracking Data Relay Satellite System (TDRSS), and the “station” operating on the ground.

• Also verified limited on-orbit system compatibility.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

6

KSC ISS MEIT/IST ExperienceKSC ISS MEIT/IST Experience

• Planned/developed and implemented the following for ISSP:

– MEIT1: • U.S. Lab, Z1, P6, SSRMS, Node1 (emulated)

– MEIT2: • S0/MT/MBS, S1, P1, P3/4, US Lab (emulated)

– MEIT3: • JEM, Node2, US Lab (emulated)

– Node2 Systems Test• Node2, US LAB & Node1 (emulated)

MEIT ConfigurationsExternalPayload

24

2

UniversalDockingModule

3

Z

N

A

PS

F3

3 3

3

MBS18 18

18 18

31

31

32

3 DC-2

29

8

JEM PM18

9

9

8

DSM

3

3

ExternalPayload

24JEM ELM ES

29

JEM EF29

29

RM-1 3

RM-23

ProgressM1

3

CAM8 9

S6

17

16

16

17

14

11 S5 81111

1 1PMPMA2 48

1AFT FWD

PORT

STBD

NADIR ZENITH

NODE 1simulated

1

8

9

99

9

9

9

8

8

8

8

23

MT

31

30 30

32

21

S022 22

24

S3S4 28 22

17

16

16

17

11

1424

2424

P5811 11

25 25

P3 P42822

17

16

16

17

11

14

26

CETA 30

15 15

2222

13

15

S1

1226

CETA 30

8

CUPOLA27

27

2727

27

27

27

P6

17

16

16

17

14

11

3

SoyuzTM

PMA348

1 AFT

FWD PORT

STBD

NADIR ZENITHNODE 3

8

88

8 89

9

8

9

9 9

9

1

8

CRVadapt

CRV#11

SLP (or ULC)

25

ExternalPayload

24

ExternalPayload

24

3

SoyuzTM

89MPLM

COF

8

9

SSRMSSPDM 18

ServiceModule

5,7

5,7

43 2

2

2

4

FA

N

Z

4

4

12

18

FGB

5,7

5,7

42 1

3

4

FA

N

12

7 places

EFGF

Strela

8

9

AIRLOCK

19

20 20NTA

20 20OTA

20 20OTA

20 20NTA

9 9U.S. LAB

ZENITH

NADIR

18

8 8

27

21

JEMELM PS

8 95,7 5,7

5,7 5,7

5,75,7

5,75,7

26

SPPERAERA

18

AFT FWD

PORT

STBD

NADIR ZENITH

NODE 2

8

9

99

9

9

9

8

8

8

8

8

Z8 Z1N

A

F

11

10

P

S

12CMGs (4)

Ku-Band

27

8U.S.HAB

9 98

S0-to-Lab Struts

Primary Orbiter Docking Interface

Alternate Orbiter Docking

Interface

Alternate MPLM Berthing Location

1515

22 22

13

15

P1

12S-Band

ULC (or SLP)

25

PMA1PMA3 simulation

MEIT-2 UsesUS Lab Simulation

16 Beta Gimbal Assembly17 Solar Array Deployment18 Power/Data Grapple Fixture (PDGF)19 Orbiter ‘D’ Hatch20 NTA/OTA Attachment Mechanism21 Lab Cradle Assy / MTSAS22 Segment to Segment Attach System (SSAS)23 Mobile Transporter Drive24 Payload Attach System (PAS)25 ULC Attach System (ULCAS)26 CETA Rollers27 Window Shutter28 Solar Alpha Rotary Joint (SARJ)29 JEM Berthing Mechanism30 CETA Coupler31 Common Attach System (CAS)32 Trailing Umbilical System (TUS) (2)

11 Rocketdyne Truss Attachment (RTAS)12 Deployable Antenna13 Thermal Radiator Rotary Joint (TRRJ)14 EPS Radiator Deployment15 TCS Radiator Deployment

1 Modified APAS2 Hybrid Docking Assembly (HDA)3 Probe and Cone (P&C)4 APAS Hatch5 RSA Solar Array Deploy Mechanism6 RSA Radiator Deploy Mechanism7 RSA Array Pointing Mechanism8 Common Berthing Mechanism (CBM)9 US Common Hatch10 Manual Berthing Mechanism (MBM)

MEIT 1 Completed 2/00



LEGENDRemotely actuated mechanisms

EVA operated mechanismsIVA operated mechanisms

Articulating/Deployable mechanisms

Translation mechanismspassive active

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

8

MEIT 2 Hardware at KSCMEIT 2 Hardware at KSC

S1Truss

P3 TrussP1Truss

S0 Truss

P4 Truss

US Lab Emulator

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

9

Problems Found in MEITs (Top Examples)Problems Found in MEITs (Top Examples)

• P6 truss failed to power up due to Auxiliary Power Converter Unit (APCU) under voltage trip condition.

– Impact: Unable to start P6 on Orbit.

• US Lab critical activation took 36 hours during the first MEIT Power-up (computer/procedure problems), Requirement <2 hrs. During MEIT regression Mission Sequence Test, Critical Activation took 1 hr, 15 minutes.

– Impact: Loss of Lab element during on-orbit activation due to thermal loading.

• Command and Control (C&C) computers failed several times due to task overrun problems (CPU utilization problems).

– Impact: Significant operational issues (Loss of Vehicle commanding, Vehicle health visibility, visibility to crew/ground) would occur because of continued loss of C&C computers.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

10

Problems Found in MEITs (Top Examples)Problems Found in MEITs (Top Examples)(continued)(continued)

• Video lines were swapped between Trailing Umbilical Systems 1, 2 (NASA) and Mobile Base System (Canadian Space Agency).

– Impact: Significant operational impact to manually route video signals. Extra Vehicular Activity (EVA) would have been required to replace two harnesses to correct the problem.

• C&C computers failed when performing synchronization to Global Positioning System (GPS) time.

– Impact: Loss of accurate GPS capability, degraded attitude control capability until development /testing and on-orbit upload of new software patch.

• Quality of Space to Ground Audio was unacceptable.

– Impact: Operation and potential safety impact to crew due to lack of understanding between Crew/Ground.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

11

MEIT BenefitsMEIT Benefits

• Significant findings from MEIT have created an opportunity to correct major operational problems which would have resulted in:

– Cost/Schedule Slip• Major milestone slippage in the Program

– Critical On-orbit Operations impacts• Safety concerns for the crew• Loss of mission objectives• Loss of flight hardware

– Nominal Operations impacts• Unknown operation risks (loss of redundancy capability)

– Unplanned EVA’s

The cumulative effect of identifying & resolving integrated hardware, software and procedure problems before flight has proven to save the International Space Station Program major on-orbit issues.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

12

• Testing that occurs between two or more individual ConstellationSystems to verify the interfaces between those Systems and to validate the integrated Systems' functionality and interoperability.

• Includes testing mechanical, electrical, data and fluid interfaces.

• Integrated testing applies to the in-space flight and integrated vehicle stack configurations.

– Multi-Element Integration Testing (MEIT) – Flight Element Integration Testing (FEIT) – Interface Verification Testing (IVT)

Integrated Testing at KSC Integrated Testing at KSC for the Constellation Program (CxP) for the Constellation Program (CxP)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

13

Constellation ArchitectureConstellation Architecture

ConstellationArchitecture

CEV

LunarLander

Lunar SurfaceSystems

Flight CrewEquip.

EVASystems

CLV

CaLV

Future

MissionSystems

GroundSystems

CEV Elements-Launch Abort System (LAS)-Crew Module (CM)-Service Module (SM)-Spacecraft Adapter (SA)

CLV Elements-1st Stage-Upper Stage-Upper Stage Engine Architecture

System

ElementSubsystem

Future

Level 2

Level 3

Level 4Level 5

CxProgram

Project

Subsystems: examples include data, power, thermal, etc.

Crew Vehicles& Systems

Launch Vehicles& Systems

Ground & MissionSystems

Crew Exploration Vehicle – CEV/OrionLunar Lander – Lander/Altair

Crew Launch Vehicle – CLV/Ares ICargo Launch Vehicle – CaLV/Ares V

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

14

MultiMulti--Element Integration Test (MEIT)Element Integration Test (MEIT)

MEIT:• An integration test between two or more flight systems that will be launched

on separate launch vehicles and integrated together for the first time in space.– Interfaces between the flight systems, mission systems, and other

appropriate CxP/ISSP and external systems may be also tested as part of each MEIT.

• The primary objectives of MEIT are: – Demonstrate the interoperability, functionality, and stability of the flight

systems, elements, and sub-systems as an integrated “in-space” vehicle assembly on the ground before they are assembled in space for the first time.

– Validate critical mission sequence activities and flight procedures prior to their first-time execution in-flight.

• A secondary objective of MEIT is:– To collect functional and performance data from the integrated flight

systems to support validation of the different interface test tool sets, emulators, and simulators used by the Projects in accepting future serial numbers of those flight systems.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

15

MEIT (continued)MEIT (continued)

• MEIT serves as a training ground for:– Flight crews and trainers– Mission Operations Division (MOD)/Mission Control Center (MCC)

personnel– Constellation system engineers

• MEITs are executed after all of the system-level requirements have been satisfied by the involved Project offices and those offices declare their system designs as verified for flight.

• MEITs are one time tests with a potential for a follow-on regression test.– Performed prior to first crewed missions

• Use of flight-like emulators and cables/connectors may be used when integration between the flight systems is not practical.

• Planned MEITs:– CEV to International Space Station (ISS) (using ISS emulation)– CEV to Lunar Lander/Earth Departure Stage (EDS) (using EDS

emulation)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

16

MEIT 1MEIT 1

MEIT 1 Test ConfigurationMEIT 1 Test Configuration(performed in the Multi(performed in the Multi--Payload Processing Facility)Payload Processing Facility)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

17

MEIT 1: CEV to ISS (Emulator)MEIT 1: CEV to ISS (Emulator)

• CEV-International Space Station (ISS) MEIT– To be performed in the year 2012, prior to first ISS flight.– Tests interoperability/functionality and all functional interfaces: data,

audio, video, RF, power.– End-to-end test with Mission Control performed via TDRSS.– Uses emulation in place of ISS flight hardware.– Mated with flight-like cables and connectors.

LID

SISS Flight EmulatorCEV

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

18

CEV-ISS Interfaces

– Mechanical• CxP will utilize newly developed Low Impact Docking System

(LIDS)

• LIDS is not compatible with ISS Docking System (APAS: Androgynous Peripheral Attach System)

• CxP will construct two APAS To LIDS Adapter Segments (ATLAS)

• ATLAS will be installed permanently on Peripheral Mating Adapters (PMAs) 2 and 3

• Provides power and data pass through capability

– Power• ISS will provide 120 VDC to CEV via two redundant power feeds

• CEV will convert 120 VDC ISS power to 28 VDC for internal buses

– Fluids/Gases• Only requirements are for Inter Module Ventilation (IMV) air

circulation – essentially same as for Shuttle orbiter

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

19

CEVCEV--ISS InterfacesISS Interfaces

– Avionics

• Audio, video, and data are distributed internally to CEV over a Gigabit Ethernet network

• CEV bus would connect to CxP provided Common Communications Adapter (CCA) which would provide conversion to legacy ISS networks.

– CCA required for MIL-STD-1553 (ISS) and Gigabit Ethernet (CEV) data conversions

– CCA installed on ISS

– CCA or prototype would be integrated into ISS emulator and tested with CEV in MEIT

• Separate CEV to ISS S-Band RF link would be implemented for rendezvous/proximity ops

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

20

MEIT 2MEIT 2

MEIT 2 Test Configurations (MEIT 2 Test Configurations (TCsTCs))(performed in the Space Station Processing Facility)(performed in the Space Station Processing Facility)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

21

MEIT 2: Test Configuration #1MEIT 2: Test Configuration #1(TC1)(TC1)

LIDSLI

DS

EDS(Emulation)

CEV to Lunar Landerwith EDS Emulation

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

22

MEIT 2: Test Configuration #2MEIT 2: Test Configuration #2(TC2)(TC2)

LIDSLI

DS

CEV to Lunar Lander

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

23

Flight Element Integration Test (FEIT)Flight Element Integration Test (FEIT)

FEIT:– An integration test between the new or significantly modified systems

and elements being assembled into an integrated launch vehicle for the first time.

• Interfaces between the flight systems, ground systems, mission systems, and other appropriate CxP and external systems may be also tested as part of each FEIT.

• The primary objectives of the FEIT are:– Demonstrate the interoperability, functionality, and stability of the flight

systems, elements, and sub-systems as an integrated “launch vehicle” assembly prior to the first operational test flight of that particular launch vehicle configuration.

– Validate critical mission sequence activities and flight procedures prior to their first-time execution.

• A secondary objective of the FEIT is:– To collect functional and performance data from the integrated flight

systems to support validation of the different interface test tool sets, emulators, and simulators used by the Projects in accepting future serial numbers of those flight systems.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

24

FEIT (continued)FEIT (continued)

• FEITs are executed after all of the system-level requirements have been satisfied by the involved Project offices and those officesdeclare their system designs as verified for flight.

• FEITs are planned and scheduled as part of the assembly and preparation of the integrated launch vehicle.

• FEITs are currently planned for every test flight (except for Ares 1-X).

• Planned FEITs:– CEV/CLV– Lunar Lander/EDS/CaLV

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

25

FEIT 1FEIT 1

FEIT 1 Test Configuration(performed in the Vehicle Assembly Building)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

26

FEIT 1 FEIT 1 –– Ares 1 Launch Vehicle StackAres 1 Launch Vehicle Stack

• Test Configuration:– CEV/CLV Integrated Stack– Ground Systems– Missions Systems– SCaN (Space Communications

and Navigation)

CLV Upper Stage

CLV 1st Stage

CEV

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

27

FEIT 2FEIT 2

FEIT 2 Test Configurations (TCs)(performed in the Vehicle Assembly Building)

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

28

FEIT 2 FEIT 2 –– Ares V Launch Vehicle StackAres V Launch Vehicle Stack

• Test Configurations:– Lunar Lander/EDS/CaLV (TC1)

• Integrated Stack– Lunar Lander/EDS (TC2)

• On-orbit Configuration

• Both test configurations include:– Ground Systems– Missions Systems– SCaN (Space Communications

and Navigation)

EDS

TC2

EDS

Launch Vehicle

TC1

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

29

Interface Verification Testing (IVT)Interface Verification Testing (IVT)

• Interface Verification Testing (IVT) verifies the mechanical and/or electrical interfaces between two or more flight systems after these systems have been mated.

• IVT consists of the minimal set of activities to verify the integrity of all physical and functional interfaces between the systems involved for each specific vehicle stack configuration.

• IVTs are performed as a subset of the FEITs during the flight tests and then performed for every flight after Full Operational Capability (FOC) has been obtained with the flight and ground Systems.

• Performed in the Vehicle Assembly Building.

• MEITs/FEITs would be required if any significant design upgrades or modifications have occurred.

KS

C C

onst

ella

tion

Gro

und

Ope

ratio

ns P

roje

ct O

ffice

30

SummarySummary

• Based on the previous success of MEITs for the International Space Station Program, these type of integrated tests have also been planned for the Constellation Program:– MEIT

• CEV to ISS (emulated)• CEV to Lunar Lander/EDS (emulated)• Future: Lunar Surface Systems and Mars Missions

– FEIT• CEV/CLV• Lunar Lander/EDS/CaLV

– IVT• Performed as a subset of the FEITs during the flight tests and then

performed for every flight after Full Operational Capability (FOC) has been obtained with the flight and ground Systems.

"Standing alone, components may function adequately, and failure modes may be anticipated. Yet when components are integrated into a total system and work in concert, unanticipated interactions can occur that can lead to catastrophic outcomes." (Columbia Accident Investigation Report (CAIB) Report 2003)

Tim.honeycutt

Technology

Transcript of Tim.honeycutt