LABEN contribution to: Workshop on European Space Information Technology in the 21st Century Launche

1
LABEN contribution toWorkshop on European
Space Information Technology in the 21st
CenturyLaunchers - Session 3Darmstadt,
September 27-28th , 2000

• Luciano Micciché - Marketing Manager -
  micciche.l_at_laben.it
• Marco Turri - Ground Dept./ Head of Ground
  Stations - turri.m_at_laben.it

2
What we are talking about
In our understanding, Health Monitoring applied
to launchers opens two main product lines

• Composite Materials. This applies to both
  airframe structure and fuel tanks that include
  specific embedded sensors for structural
  monitoring, for both ground (direct) and
  in-flight (telemetry) diagnosis.
• Vertical integration of ground technologies. This
  applies to the use of EGSE, AIV, Ground Segment
  and refurbishment into an integrated system,
  covering both the launcher development and flight
  operation support (i.e. integration, pre-launch
  and launch activities).

3
What we are talking about (contd)

• HMS (Health Monitoring System) also means
• identification and handling of false alarm
  events. They are as critical as they may lead
  even to launch sequence abort.
• flight instructions and on-board application SW
  debugging (at integration facilities) by means of
  the "mission simulation" tool.
• support the whole launcher development and
  checking at different integration levels,
• support to operations at launch pad (fuelling,
  transfer of main control from EGSE to on-board
  computer, re-entry in case of RLV, etc.) in
  co-operation with the FCC (Flight Control
  Center),
• support design enhancements,
• in case of RLV, also support re-entry activities
  and check status of airframe.

4
Health Monitoring Operational Lay-out
EGSE test results
flight data records
launch sequences records (at pad)
Health Monitoring inputs
refurbishment maintenance records
MAIT component PA screening records
structural integrity data records
5
Health Monitoring Operational Lay-out
flight parameters structural stress simulation
pre-launch sequences support false alarm
detection
Health Monitoring outputs
support to design and retrofit
trend analysis
what if ? function
operational support (launch, flight,
maintenance, etc.)
6
Functions Breakdown
7
System Overall Deployment Phases
8
System Overall Deployment Phases
9
Health Monitoring application
The Health Monitoring concept, in its full
deployment, will be based on two different levels
of data processing, fed by data packages
proceeding from two different levels

• Level 1 is a subset of the full-blown Health
  Monitoring, that just processes the data normally
  used by the EGSE by complex algorithms (such as
  signature analysis, trend analysis, etc.)
  elaborated against reference and historical data,
  with the main goal to avoid possible launch
  aborts due to false alarms.
• Level 1 doesnt rely on additional sensors
  either applied or embedded in the launcher.

Note the function is associated to a dedicated
data base that collects knowledge (in the form of
processing algorithms, warning/alarm messages and
check lists to be sent to the Operators). Health
Monitoring even though conceived for RLVs,
because of its characteristic is immediately
applicable also to the ELVs.
10
Health Monitoring application (contd)

• Level 2 completes the operational functions of
  the previous level, by constantly monitoring the
  integrity of the structure, pressure tanks, etc.,
  as well as the freedom from wear out of moving
  parts.
• It avails itself of a network of dedicated
  sensors and front-end signal conditioning, either
  embedded or applied on the launcher.

Note as and when launchers equipped with
built-in Health Monitoring sensors (e.g. optical
fibers embedded in CFRP composite) become
operational, the level 1 health monitoring
workstation will progressively evolve into a
level 2 as sub_set of it. Consequently it seems
appropriate to implement this function, at EGSE
level, as a separate Health Monitoring
Workstation loosely connected with the remainder
of the EGSE. The following two figures show
respectively a principle functional scheme, and a
data model, based only on data normally available
to the EGSE, for the Health Monitoring
application to both ELVs and RLVs.
11
Health Monitoring Layout
12
Example of immediate applicability of the HM
function to an EGSE of ELVs
13
Health Monitoring SW Functions
14
The Spaceport - Concept Drivers

• This new concept of facility is going to replace
  the former one consisting in dedicated pad(s)
• Both the future RLV families or the current ELVs
  could be supported by the same equipment and
  infrastructure (multifunction) the cost of which
  being shared by different types of launchers
  that lead to lower space transportation costs
• In general new technologies should get to
• a general reduction of the overall costs of the
  entire operational life-cycle of the spaceport
• a reduction of the overall launch costs of
  satellite
• a common use of ground infrastructure and
  resources among Commercial Users and Space
  Agencies as a driving factor for maintenance cost
  reduction

15
The Spaceport - Concept Drivers (contd)

• the spaceport operational procedures should be
  oriented against airport ones
• upper stage capability should be transferred from
  satellite to launcher (its flight control will be
  more complex)
• availability of an integrated and common LCC
  (Launch Control Center) and a dedicated world
  wide ground network, including advanced Ground
  Station Net for supporting flight instruction
  activity (by TLC HK TLM)
• spacecraft/payload integration in a common
  facility
• integrated and common testing equipment (EGSE)
• spacecraft/payload test capability at pad
• integrated Health Monitoring facility with both
  LCC (real time) and launcher Builders premises
  (off line)

16
The Spaceport - Envisaged Functions

• advanced internal data dissemination networks in
  optic fiber
• advanced communication infrastructure (external
  network)
• HM (Health Monitoring) support, including the
  simulation capability based on the flight
  parameters envelop belonging to the launchers
  which reside at spaceport
• capability to transfer the acquired Health
  Monitoring data into the space vehicle model
  flight envelope simulation DB, for flight support
• tools and procedures to integrate EGSE, AIV, Pad
  operations, Ground Station Network and Launch
  Control Center activities
• tools and procedures to plan the overall
  operation phases starting by the integration and
  up to the space vehicle lift-off
• .