Transiting Exoplanet Survey Satellite (TESS) Project Mission Operations Concept Document

!"##$%&$%'()$*!
+,
./012134 !+,
BRAFT veision, Becembei 1S, 2u12
CHECK https://TBDMIS.gsfc.nasa.gov
TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.

Transiting Exoplanet Survey Satellite
(TESS) Project
Mission Operations Concept Document

TESS-PM-PLAN-TBD

Revision DRAFT

Effective: TBD Date

Expiration: TBD Date

"#$$%&$ '(%)* +,-./0 1*20*&
"&**23*,04 5%&6,%2$
7%0-#2%, 8*&#2%90-): %2$
'(%)* 8$;-2-:0&%0-#2
!"##$%&$%'()$*!+,
./012134 !+,

Page ii of 42
CHECK https://TESSmis.gsfc.nasa.gov
15 +<=>?<=@

This uocument is a TESS Configuiation Nanagement (CN)-contiolleu uocument. Changes
to this uocument iequiie piioi appioval of the applicable Configuiation Contiol Boaiu
(CCB) Chaiipeison oi uesignee. Pioposeu changes shall be submitteu to the TESS CN 0ffice
(CN0), along with suppoitive mateiial justifying the pioposeu change. Changes to this
uocument will be maue by complete ievision.

Questions oi comments conceining this uocument shoulu be auuiesseu to:

TESS Configuiation Nanagement 0ffice
Nail Stop TBB
uouuaiu Space Flight Centei
uieenbelt, Naiylanu 2u771

Page 3 of 42

Transiting Exoplanet Survey Satellite (TESS) Project
Mission Operations Concept Document

All ieviews anu appiovals aie electionic via the TESS NIS.

Page 4 of 42
CBANuE REC0RB PAuE

B0C0NENT TITLE: TESS Pioject Nission 0peiations Concept Bocument
ISS0E BATE PAuES
AFFECTEB
BESCRIPTI0N Appioveu By:
Initial Biaft 1192u1S

ALL BRAFT Bocument ieleaseu foi
ieview by the TESS team

Page 5 of 42

Insert page listing TBD/TBC/TBRs, Tables of Content and Figures,
1. Introduct|on
The Transiting Exoplanet Survey Satellite (TESS) will discover thousands of exoplanets
around the brightest stars, measuring temporary drops in brightness caused by planetary
transits. The TESS legacy will be a catalog of the nearest and brightest main-sequence
stars hosting transiting exoplanets, which will forever be among the most favorable
targets for detailed investigations
1.1 urpose
The primary purpose of the TESS Mission Operations Concept of document is to provide
a description of the planned functions and operations of the TESS System space and
ground assets. This is not a requirements document and does not contain TESS
requirements. It presents a functional view of the TESS system and operations based on
higher level guidance. It represents the operational approaches used to develop and set
context for mission and segment requirements. Functions and scenarios in this
Operations Concept are not intended to imply design or implementation approaches for
the specific elements of the TESS system.
1.2 Scope
The scope of this document includes all functions associated with the TESS system as
well as those external entities that interact with the TESS system, encompassing data
collection by the observatory, transmission of data to the ground, and processing and
distribution of the data to the user community.
1.3 Document Crgan|zat|on
Section 1 of the document provides the introduction to the TESS System and this
Operations Concept document. Section 2 provides a high level overview of the TESS
system. Section 3 describes the TESS operational concept as a series of segments and
functions, in sufficient detail to understand the system capabilities and interfaces.
Section 4 describes the operational phases of the mission and illustrates TESS operational
scenarios for selected sequences of events during the mission life.

Page 6 of 42
1.4 1LSS M|ss|on Cb[ect|ves
TESS is an all-sky survey mission developed to create a catalog of the brightest main
sequence stars hosting transiting exoplanets, which will forever be the most favorable
targets for detailed investigation. TESS is expected to launch in 2017.
The observatory will be launched into phasing orbits toward a lunar flyby that enables a
high earth orbit with period ! that of the moon. Perigee will remain well above the
crowded geosynchronous belt, and apogee will be near 70 Re. The final science orbit is
slightly variable over time due to lunar and solar perturbations, but is stable and
predictable, dependent only on the initial launch time and energy and subsequent
trajectory correction maneuvers. This orbit combines the favorable thermal environment
of a distant L2-style orbit with a close perigee approach that facilitates high data volume
downlink.
The TESS observatory has a single instrument, a camera suite composed of 4 wide field
optical cameras. These high precision photometers measure the output of all the bright
stars in the field continuously, and capture the small variation when they are occulted by
exoplanets.
The science objectives of TESS are chosen to provide a diversity of planet sizes, masses,
orbital parameters, types of host stars, etc. This diversity is the key element that will
make the TESS catalog an enduring resource for the community. In particular, because
the frontier of exoplanetary science is advancing to planets smaller than Neptune, the
primary objectives of TESS are to:
1. Discover at least 500 sub-Neptune and smaller planets
2. Discover hundreds of super-Earths
3. Discover a sample of Earth-sized planets around bright stars

1.S keference Documents
NPR 2810.1A Security of Information Technology
NPD 8715.6A Requirements for Limiting Orbital Debris
NASA-STD 8719.14 Process for Limiting Orbital Debris
NPR 1600.1 Security Program Procedural Requirements

Page 7 of 42
2. System Descr|pt|on
The TESS System includes all components and capabilities, both space and ground based,
that are under the developmental and operational responsibility of the TESS mission. For
mission definition and formulation purposes, the TESS System is defined at the highest
level in terms of three segments the Observatory System, Ground System, and Launch
System:

2.1 Cbservatory System
The Observatory System consists of the Observatory and pre-launch ground support
equipment (GSE). The observatory will operate in a lunar-resonant (P/2) High Earth
Orbit (HEO) with a 13.7-day period. Initial perigee is 17 Re and apogee 59 Re, but these
values slowly shift over mission lifetime (depending on initial launch conditions) to 7-22
Re for perigee and corresponding apogees that maintain the P/2 orbital period.
Science and ancillary data are collected, stored, and downlinked to DSN 34m BWG
antenna ground stations when scheduled from the Ground Segment via a Ka-band
communications link. About every 3-4 days, an S-band orbit determination pass is
conducted for 1 hour, without repointing the observatory from the science target.

Page 8 of 42
The Space Segment is comprised of the spacecraft and a single instrument. The
spacecraft block diagram is shown in figure TBD, and the Instrument block diagram is
shown in figure TBD.

Page 9 of 42
2.2 Ground Segment
The Ground Segment provides for the monitoring and health and safety of the
observatory on-orbit. The ground segment will provide the mission planning and
scheduling, coordination with the ground stations for the Ka-band downlink of the
science data, generation of the observatory command loads necessary to execute the
mission plan, and the sustainment of the observatory. In addition, the ground segment
provides the functions for science data processing of higher-level data products, archive
and distribution to the Mikulski Archive for Space Telescopes (MAST).
The Ground Segment consists of the Mission Operations Center, the Science Operations
Center, the TESS Science Office, and the GSFC Flight Dynamics Facility.

2.3 Launch Segment
The Launch Segment provides those assets and services associated with the launch
vehicle (LV) and the observatory to launch vehicle integration. Included are all LV GSE
(including hardware and software), property, and facilities to integrate the observatory to
the LV, verify their integration, and conduct pre-launch testing with ground-based
functions.

2.4 Lxterna| Interfaces
TESS will be utilizing institutional support for command and telemetry service through
the JPL Deep Space Network, and NASAs Space Network. TESS has contracted GSFC
Flight Dynamics Facility to provide orbit determination, maneuver planning and flight
dynamic services for the mission. Other components of the TESS mission are remotely
located, such as the SOC and SPOC. Since they are key TESS mission systems assets
they are considered remote facility and internal interfaces.

TESS will coordinate activities to prevent conflict with other missions and operating
agencies. A DSN Service Agreement (DSA) will be negotiated between the TESS
Project office and the DSN Commitments Office to encompass all required DSN support
for prelaunch compatibility testing, End-to-End testing, ATLO, and mission operations,
through End of mission. The DSN Commitments Office will also support the TESS
Project in negotiations with the Space Network (SN) and/or other organizations as
required to acquire communication services for mission-critical events and/or specific
activities where spacecraft communications are required or desirable and a DSN station is
not in view. The project will coordinate science activities with the various organizations
listed in Section 5 with respect to follow-up programs. The project will coordinate
communications frequency spectrum allocation with the NTIA.

Page 10 of 42
2.4.1 Deep Space Network
The Deep Space Network (DSN), is a world-wide network of large antennas and
communication facilities that supports interplanetary spacecraft missions. It also performs
radio and radar astronomy observations for the exploration of the solar system and the
universe, and supports selected Earth-orbiting missions. DSN is part of the NASA Jet
Propulsion Laboratory (JPL).

DSN currently consists of three deep-space communications facilities placed
approximately 120 degrees apart around the Earth. They are:

Goldstone Deep Space Communications Complex outside of Barstow,
California.
Madrid Deep Space Communication Complex west of Madrid, Spain; and
Canberra Deep Space Communication Complex (CDSCC) in the Australian
Capital Territory southwest of Canberra, Australia near the Tidbinbilla Nature
Reserve.

Each facility is situated in semi-mountainous, bowl-shaped terrain to help shield against
radio frequency interference. The strategic 120-degree placement permits constant
observation of spacecraft as the Earth rotates, and helps to make the DSN the largest and
most sensitive scientific telecommunications system in the world.

The antennas at all three DSN Complexes communicate directly with the Deep Space
Operations Center (DSOC) located at the JPL facilities in Pasadena, California. DSOC
personnel monitor and direct operations, and oversee the quality of spacecraft telemetry
and navigation data delivered to network users. In addition to the DSN complexes and the
operations center, a ground communications facility provides communications that link
the three complexes to the operations center at JPL, to space flight control centers in the
United States and overseas.

The DSN supports NASA's Space Missions and provides the vital two-way
communications link for deep space and interplanetary Missions, information these
probes collect. All DSN antennas are steerable, high-gain, parabolic reflector antennas.
The antennas and data delivery systems make it possible to:

Acquire telemetry data from spacecraft.
Transmit commands to spacecraft.
Upload software modifications to spacecraft.
Track spacecraft position and velocity.
Perform Very Long Baseline Interferometry observations.
Gather science data.
Monitor and control the performance of the network.

Page 11 of 42

LEO MOC
C&T
System
MAESTRO
C&T
System
MAESTRO
A
T
S
FDF
TESS
Acquisition Data
Generation
Manuever
Planning
Orbit
Determination
Ka-Band - Recorded Tlm
100 Mbps Mode 1
OQPSK
S-Band - Real-time Tlm
430 kbps
NRZ-L/PM/BPSK
S-Band - Cmd Packets
32 kbps
NRZ-L/BiPhase-L/PM
S-Band - Ranging
Seq Rng & Doppler
DSN
CDSCC
DSS
GDSCC
MDSCC
SPC
DTT
F
E
P
DSOC
SLE
Gateway
JPL Data
Capture and
Delivery
Offline Data
Storage Tracking Data
RMDC
Servers
OSCARX
TRK-2-230
Tracking Data
(backup)
Acquisition
Data
Special Function
Gateway
Tracking Data
Tracking Data
P/B Tlm Data DSN Central
CFDP Entity
Tracking Data
Processor
Monitor Data
Server
Monitor
Interface
Assembly
Monitor Data
Server
Uplink System
TRK-2-229
DSCC
DCD
Monitor
Data
CCSDS Command Packets
VC0 (RT Tlm)
DSN Monitor Blocks
VC1 (SLE Playback Tlm)
V
C
0
R
T
tlm
Customer
Interface
Layer
(CIL)
Target Star Catalog
T
a
rg
e
t S
ta
r C
a
ta
lo
g
u
e
V
C
1
P
/B
tlm
RIONet
TCP/IP
RIONet TCP/IP

+-.9&* AB@4 A>''C: @'7 D20*&E%)*:

Page 12 of 42
2.4.2 Space Network

The SN consists of a constellation of geosynchronous satellites and associated ground
systems and operates as a bent pipe relay system between customer platforms and customer
ground facilities. The SN ground segment is operated out of the White Sands Complex in Las
Cruces, NM, the Guam Remote Ground Terminal (GRGT), the Bilateration Ranging
Transponder System (BRTS), Contingency S-Band Tracking, Telemetry and Command
(TT&C) sites (Australian TDRSS Facility (ATF) and Canberra), the NCCDS, and the
Network Integration Center (NIC). WSC, GRGT, BRTS, and the NCCDS are dedicated to
SN operations only, but the NIC is shared with another NASA element, the Near Earth
Network (NEN).

MCC
LEO MOC
LTO MOC
C&T
System
MAESTRO
Planning and
Scheduling System
C&T
System
MAESTRO
A
T
S
WSC
TDRS
WSC
RCVR WDISC
S-Band Comm Only
TESS
V
C
0

R
T

t
lm
Long Term
Archive
DAT
T
a
r
g
e
t

S
t
a
r

C
a
t
a
lo
g
u
e
V
C
1

P
/
B

t
lm
RIONet
TCP/IP

+-.9&* AB@4 A>''C: '7 -20*&E%)*
The combination of the WSC, the GRGT and the TDRS constellation is also known as
the Tracking and Data Relay Satellite System (TDRSS). For TESS SN coverage will be
used during the Launch and Early Orbit (LEO) phase of the mission. The Space Network
will provide Tracking and Data Relay Satellite (TDRS) services using the NISN

Page 13 of 42
restricted IONet. The SN will also provide services during spacecraft orbit raising
phasing loops when the spacecraft is near Earth. LEO support will consist of S-Band
Forward, Return and Tracking services. The same services will be provided during the
orbit raising phasing loops provided the link margin is adequate to acquire spacecraft
command and TDRSS ground receiver locks. Once the spacecraft reaches the mission
designated orbit (P/2), the mission support will transition to DSN support only.

2.4.3 NISN

The NASA Integrated Services Network (NISN) is a global system of communications
transmission, switching, and terminal facilities that provides NASA with wide area
network communications services. The NISN services that support the Space Network
(SN); include real-time and mission critical Internet Protocol (IP) routed data, as well as
high-rate data and video services that connect the SN ground facilities. Inter-Center
mission voice communications services are also provided for management of the network
and support of user missions.

2.4.4 GSIC I||ght Dynam|cs Iac|||ty

The GSFC Flight Dynamics Facility (FDF) provides the flight dynamics services for
TESS for the life of the mission. FDF interfaces through the NISN restricted IONet with
the DSN and SN for tracking data and acquisition vectors; and the Flight Dynamics
Analysis Branch for conjunction assessment and risk analysis.

For the TESS Mission FDF will provide;
Pre-launch mission analysis, launch support, post launch operations,
Pre-mission trajectory design and analysis, operational orbit control and
maintenance
Pre-mission orbit error analysis, tracking requirements analysis, or for
operational orbit determination and contact acquisition
Tracking station and network trouble-shooting, or transponder or link analysis,
or for tracking data evaluation, we have the tracking syst

Page 14 of 42
FDF
WSC
TDRS
to MOC
FEP
WSC
RCVR WDISC
S-Band Comm Only
Acquisition Data
Generation
Manuever
Planning
Orbit
Determination
Acquisition
Data
DSN
OSCARX
Tracking Data
(backup)
Acquisition
Data
TESS
Customer
Interface
Layer
(CIL)
Tracking Data
RIONet TCP/IP
RIONet - TCP/IP

+-.9&* AB@4 A>''C: +@+ -20*&E%)*:

Page 15 of 42
3.0 Iunct|ona| V|ew of Cperat|ona| Concept
The TESS operational concept is presented in this section as a set of functions required to
operate TESS. The allocation of functions to specific segments and any grouping of
functions within segments are based on experience gained from developing similar
systems. However, this allocation is not meant to constrain the TESS system architecture
that will be refined later in the development cycle. Therefore, while the objective of the
OpsCon is to capture all necessary functionality of TESS operations, some functions may
ultimately be allocated to different segments at a later time.
3.1 Space Segment
The TESS Observatory and associated GSE make up the Space Segment. The TESS
observatory consists of the Spacecraft and Instrument.
Planned for a 2 year mission life with possible 2 year extended mission, the TESS
observatory will operate in a P/2 lunar resonant orbit with perigee >7 Re and < 22 Re,
and apogee near the lunar distance. This allows the observatory to collect science data in
the thermally stable region far from Earth, and downlink science data when close to Earth.
3.1.1 Spacecraft
The TESS spacecraft will perform the standard functions of instrument support, data
collection, communications, command and data handling, attitude and orbit control,
power and thermal control, launch vehicle interface, and health and safety monitoring. It
also provides safe hold protection in the event of anomalous conditions. The following
sections outline these functions.
!"#"#"# %&'()&* +,*-
The TESS Spacecraft will autonomously control internal functions to execute the mission,
in both nominal and contingency states with appropriate fault management. Spacecraft
operation can be characterized by defined states, named for their scope of activities and
exist in name only. A change in state occurs by a change in mode(s) that defines the state.
Within each subsystem, one or more modes define the configuration of the subsystem and
further characterize the Spacecraft operation. A detailed description of these states and
modes and the transitions from one to another are listed in the TESS Spacecraft States
and Modes Description Design Note.
The list of spacecraft states is (TBR) Launch, SRM, Acquisition, Housekeeping, Science,
Eclipse, and Contingency. The TESS System States and State Transitions are shown in
figure TBD.
!"#"#". %&//0'123(, 41(5 6)&0'7 89+(,/
The Spacecraft will communicate with the Ground System via Ka and S band. A fixed,
body-mounted HGA transmits science data during LAHO. Two omni antennas provide
4pi steradian coverage to transmit housekeeping data during LAHO and ranging data
during the 1 hour HASO contacts. Communication will be with both DSN and SN assets.

Page 16 of 42
Data types will include Spacecraft Housekeeping, Instrument State-of-Health, Science
Data, Instrument Ancillary, Spacecraft Ancillary, and Instrument Housekeeping
!"#"#"! :3'3;, %<=>
The Spacecraft will use both stored and real-time commanding for both the spacecraft
and instrument. ATS and RTS command loads are (TBD, describe in more detail. The
Spacecraft will receive and store Instrument State-of-Health data from the instrument.
The Spacecraft will send Spacecraft Ancillary data and time-referenced pulses to the
instrument. The Spacecraft will receive and downlink instrument data, and will receive
and process instrument fine pointing data. An oveiview of the uata types anu stoiage
locations is shown below:

!"#"#"? %&'()&* 3((1(07, 3'7 &)@1(
The Spacecraft will control its attitude during all phases of the mission. During spinning
operations such as SRM Burn, the Spacecraft will control nutation. During science data
acquisition, the Spacecraft will point to inertial targets specified by the ground, using
both coarse and fine control modes. During LAHO, the Spacecraft will point to and track
ground stations when downlinking, and unload momentum from reaction wheel
assemblies using a monopropellant hydrazine propulsion system. Both small (5N) and
large thrusters (22N) are used to unload momentum, correct launch vehicle dispersions,
raise the initial parking orbit perigee if required, raise apogee during phasing orbits,
target a lunar flyby for gravity assist, adjust the final orbital period to the P/2 lunar
resonance, and execute various trajectory correction maneuvers as needed.
!"#"#"A %&'()&* (5,)/3* 1'(,)-32,
The spacecraft will maintain the instrument interface within temperature limits and
temperature stability requirements. The limits and temperature stability requirements are
in the Spacecraft to Instrument ICD.

Page 17 of 42
!"#"#"B 6,',)3(, 3'7 71+()1@0(, C&4,)
The Spacecraft will generate electrical power with solar arrays and provide switched and
unswitched power to spacecraft components and the Instrument.
!"#"#"D :&'1(&) 5,3*(5 3'7 +3-,(9
The Spacecraft will measure and digitize critical temperatures, voltages, and currents to
assess performance and state of health.
!"#"#"E F'(,)-32, 41(5 *30'25 G,512*,
The Spacecraft will send housekeeping data to the launch vehicle, and will sense when
launch vehicle separation occurs.
!"#"#"H 80CC&)( F'+()0/,'(
The Spacecraft will provide the necessary mechanical, thermal, electrical power, and data
interfaces to the Instrument as needed for execution of the TESS science mission. The
interfaces are described in the Spacecraft to Instrument ICD.
3.1.2 Instrument
The TESS Instrument measures the light curves of stars to determine exoplanet
characteristics such as orbital period and diameter. The Instrument performs the
following functions (TBR):
o Control Instrument operation
o Measure Instrument health status
o Accumulate CCD images
o Compress and store data
o Communicate with spacecraft
! Send fine pointing and state of health data to spacecraft
! Send science data to the Ka band transmitter for downlink
! Receive data such as star targeting tables and ancillary data from
spacecraft
!"#"."# %&'()&* F'+()0/,'( IC,)3(1&'
The Instrument will use information from the spacecraft and from internal health status to
control its operational modes. The Instrument will have the following operational states
(TBR):
OFF State in the OFF State, no power is supplied to the instrument with the exception
of power to survival heaters. To the extent possible, the Instrument is designed to allow
the spacecraft to monitor its health and safety while in the OFF State. For example, the
spacecraft will monitor critical instrument temperatures. Survival heaters are provided as
necessary to protect the instrument in this mode.
STANDBY State the Instrument is powered on but not collecting science data or
providing fine pointing data to the spacecraft.

Page 18 of 42
SCIENCE State Nominal science data collection is taking place. Fine pointing data is
being sent to the spacecraft.
DIAGNOSTIC State The Instrument is powered on during ground testing for
verification and diagnosis.
!"#".". :,3+0), F'+()0/,'( 5,3*(5 +(3(0+
The Instrument will measure and digitize critical temperatures, voltages, and currents for
inclusion in the instrument telemetry data. The Instrument telemetry data also includes
all data required for status and health monitoring of the instrument, including mode,
configuration, temperatures, supply current and voltages, and any other telemetry data
required to support performance evaluation.
!"#"."! J220/0*3(, %%= 1/3;,+
The Instrument will receive light from the targeted stars within the required wavelengths
(600-1050nm) and convert to electronic form. Both 10 x 10 pixel subarrays centered on
the target stars and full-frame images will be accumulated.
!"#"."? %&/C),++ 3'7 +(&), 73(3
The Instrument will perform on-board lossless compression and store the science data.
Stored data will remain accessible in the event of a power cycle.
!"#"."A %&//0'123(, 41(5 +C32,2)3-(
The Instrument will determine its ensemble boresight pointing and send data to the
spacecraft so that the ACS system can adjust to the correct pointing. During a perigee
pass, the Instrument will send science and housekeeping data from the recorder to the
spacecraft for downlink. The Instrument will also receive uplinked information from the
spacecraft such as targeting tables.
3.1.3 Ground Support Lqu|pment
Electrical and mechanical Ground Support Equipment (GSE) interfaces to the TESS
observatory are essential to successful observatory integration and verification. The
electrical GSE originates test commands and receives responses from the observatory
during observatory level integration and test. The mechanical GSE is used during final
assembly of the observatory for the installation and testing of any mechanical
components.
A subset of the integration and test GSE will travel to the launch site to support
observatory final preparations for launch. The electrical GSE at the launch site will be
used in the payload process for launch as well as during the launch count down to place
the TESS observatory in its final launch configuration.

Page 19 of 42
3.2 Ground Segment
3.2.1 M|ss|on Cperat|ons Center

The MOC is responsible for communicating with the spacecraft through DSN using the
NISN restricted IONet. Science Tasking Files are generated within the POC (see 3.2.2
below), and are then checked iteratively between the MOC and the POC. The MOC then
generates the final spacecraft and payload command loads. MOC engineers will establish
baseline performance, monitor performance trends over time, and generate S/C
housekeeping command loads. The MOC performs the following functions:
Real-time T&C
Mission Planning
Contact Scheduling
ATS/RTS generation and Uplink
Trending and Analysis
FSW Maintenance
Data accounting
Ground System configuration
3.2.2 Sc|ence Cperat|on Center (SCC)

The SOC is comprised of the Payload Operations Center (POC) formerly called the
Payload Operations Group (POG), located at MIT, and the Science Processing
Operations Center (SPOC), formerly called the Data Processing Group (SPG) Located at
Ames Research Center. Figure n.n shows the interaction between the elements of the
SOC.

Page 20 of 42
MCC
Planning and
Scheduling
System
POC
SPOC
Commissioning
Tools
Data Relay
Payload
Operations
Payload
Pointing
Pipeline Infrastructure
Science
Pipeline
Photometer Mgnt
TSO
Identify TESS Objects of
Interest (TOI)
TOI Followup Primary Website
Target Selection
MAST
USER Community
STF
TIC
TOI List
TOI List
TOI List Archive
Modified
Target
List
Target
List
TIC
Aux
Target
List
Pipeline Framework (PF)
S
c
ie
n
c
e
F
IT
S
V
a
lid
a
tio
n
D
a
ta
C
o
m
m
is
s
io
n
in
g
D
a
ta
Target Star
Catalog
SFTP
SFTP
Support Libraries
(SLIB)
Mission Reports
(MR)
Data Receipt
(DR)
File Store (FS)
Archive
(AR)
Calibration (CAL)
Photometric
Analysis (PA)
Pre-search Data
Conditioning
(PDC)
Transiting Planet
Search (TPS)
Data Validation
Target Mgnt
Catalog Mgnt
(CM)
Target and
Aperature
Definitions (TAD)
Photometer
Performance
Assessment (PPA)
Photometer Data
Quality (PDQ)
Focal Plane
Characterization
(FPC)
End to End Model
(ETEM)
L0 data
Validation
Data
Commissioning
Data
F
F
I
FFI
L
0
D
a
ta
F
F
I
Science FITS
Science FITS
Science FITS
S
c
ie
n
c
e
F
IT
S
Science FITS
L1 Uncalibrated FITS
L2 Calibrated FITS
L3 Light Curves
Science
Metadata
Focal Plane
Geometry
Pixel
Response
Function
FFI FFI
SOH
Monitoring
STF
Generation
Target Star
Pixels
Boresight
Pointing
Boresight
Coord.
Boresight
Coordinates
L
0
D
a
ta
V
a
lid
a
tio
n
D
a
ta
S
c
ie
n
c
e
M
e
tric
s
To
(FS)
Science
Metrics
Engr Data
E
n
g
in
e
e
rin
g
D
a
ta
To
(PDQ)
Engr Data
From
(FS)
Engr
Data
TIC
Stellar
Catalog
V
a
lid
a
tio
n
D
a
ta
L0
Generation
R
a
w
S
c
ie
n
c
e
L
0
D
a
ta
R
e
tra
n
s
m
it R
e
q
u
e
s
ts

!"."."# K39*&37 IC,)3(1&' %,'(,) LKI%M

The POC is responsible for payload operations and state of health monitoring. Science
data from the spacecraft are collected and checked for completeness by the POC and
forwarded to the SPOC via a Secure FTP connection. This includes operations timing and
spacecraft pointing, and the development and operation of commissioning tools. The
POC also collects and maintains calibration data utilized in pipeline processing. The POC
regularly monitors payload housekeeping data for instrument state-of-health. Data
downlinked during twice-weekly S-band contacts provide insight into payload operations
outside of perigee and can enable corrective commanding during the subsequent uplink
period. The POC generates a Science Tasking File containing instrument commands and
delivers it to the MOC via SFTP for ATS generation. (Need to describe the format and
method of ingest for the STF into the MPS) The POC performs the following functions:
Science planning / STF generation
Science data downlink validation
Level 0 science product generation

Page 21 of 42

!".".". 821,'2, K39*&37 IC,)3(1&'+ %,'(,) L8KI%M

The SPOC develops and produces the TESS science data pipeline prior to launch.
During science operations, the SPOC maintains and operates the pipeline. Every orbit
(every ~28 days); the SPOC receives a new set of data from the POC via the SFTP
connection. The SPOC takes this data and processes it through the pipeline, calibrating
images, producing light curves, and calibrating the light curves. Based upon the
calibrated light curves, the pipeline automatically detects Threshold Crossing Events
(TCEs) that indicate the possibility of a transit event. For each of these events, the
Pipeline then produces Data Validation reports that provide additional information for
future rejection of false positives. The spacecraft data, including the raw data, calibrated
data, light curves, and calibrated light curves, are then sent via SFTP to both the MAST
and to the TSO. The list of TCEs and Data Validation reports are also sent to the TSO.
The SPOC performs the following functions:
Pipeline reduction
Calibration
Preliminary analysis
Software development (will this be ongoing for the science data?)

Page 22 of 42
3.2.3 1LSS Sc|ence Cff|ce (1SC)

The TSO is responsible for evaluation of all potential transit events. Such events can not
only be caused by transiting exoplanets, but also by astrophysical phenomena (e.g.
background eclipsing binaries) or by instrumental effects. The TSO examine the data and
the Data Validation reports to eliminate false positives from the list of TCEs. The
remaining events then become TESS Objects of Interest (TOIs). This list is made
available to the community via the TSO website as candidates are vetted; the first TOIs
should become public within ~6 months of data acquisition, but as has been seen with
Kepler, continued analysis of data will likely result in the identification of additional
TOIs. The TSO then also vets the list of TOIs to determine which of these objects are
best-suited to ground-based follow-up observation with TESS project collaborators; these
objects are then prioritized for follow-up observations. The TOIs are prioritized based
not only upon the observational accessibility of individual objects, but also upon the
objective to validate and obtain masses for a diverse sample of small (R<3R
Earth
) planets.
The TSO performs the following function:
Science data analysis
Science target selection
3.2.4 M|ku|sk| Arch|ve for Space 1e|escopes (MAS1)

TESS data will be archived at the Mikulski Archive for Space Telescopes (MAST). The
data archived will include the raw TESS data, uncalibrated FITS file, calibrated FITS
data files, and calibrated light curves. New TESS data will be released to the community
via the MAST website every four months, ensuring that all data is made public within 6
months of data download.
3.3 Secur|ty

TESS Project plans for implementing requirements for information, physical, personnel,
industrial, and counterintelligence/counterterrorism security, and for security
awareness/education requirements, in accordance with NPR 1600.1, Security Program
Procedural Requirements and NPD 1600.2. NASA Security Policy will be addressed in
the TESS IT Security Plan. The POC and SPOC are not in the critical path for spacecraft
commanding and realtime telemetry and will develop separate security plans for their
respective facilities.

Command encryption is not planned for TESS. GSFC and HQ security personnel will
perform a TESS Threat Assessment to recommend other space asset protection measures.
The TESS Project will evaluate the recommended measures for implementation or
accepted risks.

Page 23 of 42
3.4 Launch Segment
The Launch Segment delivers the Observatory to the initial orbit of 200 km x 250,000 km.
It provides the Structural, Electrical, and Conditioned Atmosphere Interfaces to the
Observatory and Ground and Launch Environments as specified in the Launch Vehicle
Interface Requirements Document.
The launch segment consists of the Launch Vehicle (LV) and associated facilities,
equipment, and services needed to place the TESS observatory into orbit. This includes
the payload processing facilities and the range support for the launch vehicle and the
observatory.
The TESS observatory will be launched from TBD (CCAFS or WFF depending on
selected LV). The TESS space segment will be transported to the range to prepare for
launch. A payload processing facility (PPF) will be assigned at the range to support the
final observatory integration and test activities required before launch.
3.4.1 Launch Veh|c|e
NASA will procure the TESS launch vehicle and associated launch services. The LV is
TBD. The LV will be delivered to the launch site. The observatory will be mated to the
LV at the launch site.
3.4.2 Launch Veh|c|e Ground Support Lqu|pment (LV-GSL)
The launch vehicle ground support equipment (LV-GSE) are those mechanical, electrical,
communications, propulsion, and monitoring equipment needed to provide launch
services
3.4.3 ay|oad rocess|ng Iac|||t|es
The TESS observatory will be assigned to a payload processing facility located at or near
the launch site. After a PPF is assigned, the PPF products and services required to
support the mission from the delivery of the observatory to the PPF until after the launch
will be determined and the requirements will be documented in a Launch Site Support
Plan (LSSP)
It is anticipated that the observatory will arrive at the launch site TBD months before
launch. The TESS project will arrange for the transportation to the PPF. Final
integration and test activities required before launch are performed at the PPF.
Observatory checkout equipment will be linked remotely to the MOC via voice and data
lines. The observatory checkout equipment will be linked to the launch complex with
voice and data links and video and RF links can be established if required. The MOC
will have the ability to exchange telemetry and commands with the observatory through
the checkout equipment in the PPF and at the launch complex.
The observatory will be loaded with propellant, weighed, and prepared for transport to
the launch site at the PPF.

Page 24 of 42
3.4.4 kange Support
Range Support provides products and services to the TESS Project such as security and
escort services, communication and data lines, photography and video support, laboratory
service, RF protection, and weather forecasting. The range will also be responsible for
overall range safety. Range support will be documented in a jointly developed
requirements document after selection of the launch vehicle and site are determined. The
Project will develop (TBD) a Missile System Pre-Launch Safety Package (MSPSP) for
the range. The MSPSP provides an assessment for the risks involved with the
Observatory transportation, handling, integration and test, and mate operations to the LV.
It also includes a description of the TESS flight hardware, GSE, test procedures, and
launch complex operations and testing.

Page 25 of 42
4. Cperat|ona| hases and Scenar|os

The TESS mission is comprised of five distinct phases: Pre-Launch, Launch, Ascent and
Commissioning, Science Operations, and Decommissioning. The altitude of TESS and
associated maneuvers during Ascent and Commissioning are shown below:

4.1 re-Launch

Pre-Launch begins with power up, and ends with the final removal of inhibits on the
Observatory before launch. (Add list of s/c and instrument activities during prelaunch) A
timeline is shown:

(add prelaunch timeline)
4.2 Launch

The Launch phase begins at the end of Pre-Launch and ends with the separation of the
observatory from the launch vehicle. It includes events such as spin up to 60 rpm, despin
after SRM separation (if required, depending on the selected LV), transmitter turn on, solar
Lunar Swing-
by
DV-1
DV-2
Phasing
Loop 1
Phasing
Loop 2
Phasing
Loop 3
PAM
Science Orbit 1
ra = 400,000 km
Cal
Burn
TCM
TCM
ra = 361,400 km
DV-3 TTI
ra = 250,000 km
Perigee Passage
DV Burn
Burn if necessary
Transfer
Orbit
Ascent and
Commissioning
Science
Operations

Page 26 of 42
array deployment, three-axis stabilization, and slew to sun acquisition. The instrument is
OFF during launch mode.

The Observatory must launch within a certain window of time to properly intercept the moon
for a gravity-assist flyby. Over the course of a 27 day sidereal (TBR) month, there exist ~23
potential launch days where the required hydrazine to raise the orbit to final science altitudes
is not prohibitively expensive. On those potential launch days, the window of time available
is approximately 1 hour (TBR).

TESS launches from TBD (location depends on selected LV) to a TBD circular parking
orbit of 200 or 600 km, depending on LV (Taurus or Athena). The LV partly spins up to
57 or 5 rpm, arms the SRM, and separates the flight system. The S/C completes the spin
up to 60 rpm and autonomously fires the SRM via timer sequence, targeting an initial
apogee of 250,000 km. TBD seconds after burnout, the SRM is separated and Launch
phase ends.

A timeline is shown below:

(add detailed timeline)
4.3 Ascent and Comm|ss|on|ng

The Ascent and Commissioning phase begins at the end of Launch phase and ends with
the final maneuver to enter the science orbit. It includes the phasing orbits and
maneuvers required for gravity-assisted lunar flyby and insertion into the science orbit,
and all spacecraft and instrument commissioning and calibration activities.

After launch, if the LV placed the observatory into an initial orbit with perigee 200km,
the perigee is adjusted to 600 km. The engineering team assesses the initial observatory
health and ephemeris. Immediately after launch, telemetry and uplink is via SN for the
first hour of LEOPS. Tracking is via DSN S-band, and occurs at various times to ensure
sufficient orbit determination and maneuver planning (see Table G-6 from the CSR)

Two full additional phasing orbits are planned before the Lunar flyby (See Figure tbd).
Overburn or underburn of the SRM and launch vehicle dispersions are corrected during
these 2 orbits and apogee is raised to 400,000 km. Trajectory Correction Maneuvers are
executed to target lunar flyby at an altitude of 3,500 to 25,000 km above the lunar surface.
Post lunar encounter apogee is 75 Re and perigee is 17 Re. A final maneuver at perigee
adjusts the final apogee so that the period is P/2 resonant with the moon (13.7 days). If
any of these maneuvers are missed the contingency plan is to TBD, Section 5.11.TBD.
Timelines showing these events are below.

Page 27 of 42
Phasing Orbit 1 (Day 0-5)

Phasing Orbit 2 (Days 5-13)

(ADD PHASING ORBIT 3, transfer orbit)

4.3.1 Spacecraft comm|ss|on|ng act|v|t|es (LkAND)
Initial acquisition and checkout
DSN ranging to determine LV dispersions
Instrument
Spacecraft
Ground
System
L+5
Perigee 1 Launch
1 3
2 1
Acquisition
Checkout
Continue
Checkout
Power Up DHU, Cameras
Initial Checkout
Send SOH to MAU, SSR
4/5/6
2
Continue
Checkout

L+1
L+2 L+3 L+4
1 DAY
SPOC
Activities
FDF, MOC, POC Activities
Post-maneuver Slew,
Comm, Slew, Continue
Checkout (TBD)
Transfer H/K Data,
Stored Test Images
(TBR) (Ka)
3
L
A
H
O

1

Apogee 1
# Maneuver Approximate
Duration
1 Cal Burn TBD seconds
2 Perigee Raise 2 minutes
3 Apogee Raise 1 9 minutes
Contact
(band)
DSN Coverage
(CE=critical event)
1(S) Initial 24 hour acquisition
and OD
2(S) Cal Burn (CE)
3(S) Perigee Raise (CE)
4/5/6
(S, Ka)
2 OD at 3 hrs each, LAHO
1 at 2/4/8 hrs TBR (CE)
Instrument
Spacecraft
Ground
System
Slew to anti-solar and coarse point 3-axis stable
7/8/
9
L+7 L+9 L+11
FDF, MOC, POC Activities
L+5 L+8 L+10 L+12 L+6
4
Complete
Checkout
Collect full images (Common P/L boresight and xform matrices not yet defined)
L
A
H
O

2

Page 28 of 42
Spin down maneuvers
SA deployment and sun acquisition
ACS checkout
Propulsion system test burn
EPS checkout
RF Comm checkout
Ka band HGA boresighting
Thermal control system checkout
Payload interface checkout

4.3.2 Instrument comm|ss|on|ng act|v|t|es
The payload commissioning will occur during the 3.5 phasing orbits before lunar flyby.
After a period of outgassing, power-up and checkout, calibration data will be collected to
validate and modify the mechanical transformation matrices of the cameras for use in the
fine pointing control mode of the spacecraft. The impact of Earth and Moon on camera
sensitivity will be assessed and used in planning science operations. Calibration mode
operations will be controlled by timed command. The commands will allow for collection
of full frame data both single frames and stacked images as well as
subarray data. Precise camera pointing and attitude control matrices will be calculated
from downlinked data. Attitude control tables can be uploaded during tracking contacts to
allow for tuning of ACS parameters. A detailed timeline of instrument commissioning
events is shown:

(add instrument commissioning timeline)
4.4 Sc|ence Cperat|ons

The Science Operations phase begins at the end of Ascent and Commissioning, and ends
with the last downlink of science data. Science Operations consist of Low Altitude
Housekeeping Operations (LAHO) near perigee and High Altitude Science Operations
(HASO) outside of the perigee portion of the orbit. Activities during Science Operations
include acquiring images of targeted stars, downlinking science data, (add other ops here)
LAHO lasts for ~16 hours (perigee 8 hours), and HASO for ~13 days. During HASO,
the spacecraft is dedicated to acquiring science data for the mission and maintaining
contact periodically with the ground for orbit determination and status updates.
During LAHO, the spacecraft performs science data downlink, state of health monitoring
and stored command / table loads. Upon entering LAHO, the instruments suspends
science imaging and the spacecraft slews to point the High Gain Antenna towards DSN
and makes contact with the MOC. The MOC uploads the command & target star catalog
for the next ~4 orbits (providing robustness in case of a failed contact) and commands the
data dump from the spacecraft. The science data download takes ~4 hours. Following
download, the spacecraft unloads momentum from the reaction wheels, and slews back to

Page 29 of 42
the observation field. Over the course of the 2 year DRM, no additional orbit
maintenance or other maneuvers will be required. The orbit natural variability will keep
perigee well above GEO and below 22 Re.
During HASO, the spacecraft maintains fine pointing toward the desired location, and
executes four 60-minute housekeeping and ranging contacts (separated by ~3 days,
evenly spaced around the orbit), which do not interrupt science data acquisition. During
this time the instrument acquires the full frame images and postage stamp 10x10 pixel
subframes around each targeted star.

4.S Decomm|ss|on|ng

After the nominal 2-year mission and any extended mission, the spacecraft is passivated
and disposed of in place. For TESSs final science orbit, there is no NASA required
EOM plan. An analysis of typical orbit propagations over 100 years shows that TESS
remains well outside the GEO belt and does not impact the Moon. The stable nature of
the P/2 orbit is a result of many small lunar perturbations that on average cancel each
other out since they change direction at every apogee when TESS is near the lunar
altitude and either 90 degrees ahead or behind the moon.

Page 30 of 42
S. Cperat|ons Capab|||t|es and Scenar|os

This section describes the operational capabilities for the mission including nominal and
anomaly scenarios. Figure n.n shows the data flow of the ground system.
DSN
MOC
POC SPOC
SN
FDF
TSO
MAST
CCSDS Commands
ATS
Table Loads
R/T S-band Tlm
P/B S-band Tlm
DSN Monitor Blocks
CCSDS Commands
R/T S-band Tlm
P/B S-band Tlm
Ephemeris
Mnvr Plans
Observatory Parms
T
r
k

D
a
t
a
A
c
q

D
a
t
a
A
c
q

D
a
t
a
T
r
k

D
a
t
a
Ka-band Data
Ephemeris
STF
ATS
CAR
Target Star Cat
L0
FFI
Engr Data
Validation Data
Cmsn Data
Modified Target list
V
a
l
i
d
a
t
i
o
n

D
a
t
a
S
c
i
e
n
c
e

F
I
T
S
V
a
l
i
d
a
t
i
o
n

D
a
t
a
S
c
i
e
n
c
e

F
I
T
S
T
I
C
T
a
r
g
e
t

L
i
s
t
A
u
x

T
a
r
g
e
t

L
i
s
t
T
O
I

L
i
s
t
User Community
TESS
Archive
Schedule Request
Contact Schedule
Schedule Request
Contact Schedule

S.1 Commun|cat|ons opportun|t|es

DSN performs all radiometric tracking for the TESS mission using the S-band 34m BWG
stations. Tracking products during the phasing and mission orbits are the standard DSN
tone ranging and two-way Doppler. There are four 60-minute housekeeping and ranging
contacts (separated by ~3 days) planned during HASO, which do not interrupt science
data acquisition, to support spacecraft SOH monitoring and Orbit Determination.

LAHO is defined as the 16 hour part of the orbit +/- 8hrs of perigee. During LAHO, a
five hour contact is planned using S-band for housekeeping and Ka-band science data
downlink. During this contact the s/c will also perform reaction wheel momentum
unloading. The S/C uses its reaction wheels to re-orient the HGA toward the DSN ground
station for data downlink while using the SADAs to keep the SAs pointed toward the sun.
After the downlink, TESS uses thrusters to unload momentum before repointing the

Page 31 of 42
observatory for science operations. Figure n.n illustrates a typical Orbit-In-The-Life for
TESS.

Need to talk to Sean about how he plans the momentum unloading.

HASO
~13 days
LAHO
8 hrs
13.7 days
LAHO HASO
1 hr H/K and ranging
contacts
Perigee
Perigee
DSN Contact
Begin
Slew
Begin Return
Slew
Uplink ATS & Target Star
Catalog; Start data dump
Begin Science
Operations
Science Operations
(Entirely at HASO)
Science Operations
Spacecraft Operations
Payload Operation Center (POC)
&
Mission Operations Center (MOC)
Pointing, Target Star
Selection (POC)
(every other Orbit)
Generate Science
Tasking File
(POC)
STF Check
(MOC/POC)
Generate ATS
Load (MOC)
Retrieve Ka-band
data from DSN
Send L0 data to
SPOC (POC)
(every other orbit)
Science Processing Operations Center
(SPOC)
&
TESS Science Office (TSO)
Rcv L0 data from
POC (SPOC)
(every other orbit)
Ingest L0 data
(SPOC)
Pixels calibrated
L1 (SPOC)
Raw light curves
generated L2
(SPOC)
Calibrated light curves
generated L3 (SPOC)
Transit planet
candidates sent to
TSO (SPOC)
Data sent to MAST
(SPOC)
Transit planet
candidates rcvd
from SPOC (TSO)
Generate TOIs
(TSO)
TOI voting, analysis and
follow up (TSO)

S.2 Commun|cat|ons aths

The DSN is the primary network for communications with the spacecraft. SN will be used
during the first hour of launch and during the first 2 apogee raise maneuvers at perigee. DSN
uses the 34M BWG apertures at GDS, MAD, and CAN for S-Band and Ka-band data. SN
uses SSA for real-time S-band. TESS uses 4 modes of communication. Mode 1 is the Ka-
band downlink. It downlinks the raw science data, full frame images and engineering
telemetry at 100MBps. Mode 2 is the DSN S-band High Speed link with an uplink rate of 32

Page 32 of 42
kbps and a downlink rate of 434 kbps. Modes 1 and 2 are used simultaneously during the
LAHO contacts between 7Re and 22Re. Mode 3 is the DSN S-band Low Speed link with an
uplink rate of 2 kbps and a downlink rate of 8 kbps. Mode 3 also provides sequential tone
ranging and is used during the 4 ranging contacts at HASO between 7Re and 90Re. Mode 4
is the TDRSS S-band Single Access (SSA) Low Speed link with an uplink rate of 2 kbps and
a downlink rate of 8 kbps. It is planned for contingency and critical Events.

S.3 Command|ng

The MAESTRO T&C system uses MAESTRO scripts for all real-time commanding to
the observatory. Each script is tested against the flatsat and the spacecraft (to the extent
possible) prior to launch. Each script is executed as part of a Standard Operations
Procedure or a Contingency Operations Procedure that has been developed and verified
prior to launch. All critical commands will require real-time user approval prior to
execution. All stored commands are executed via an Absolute Time Sequence or
Relative Time Sequence that has been uplinked to a buffer on the observatory. The
Mission Planning System receives a Science Tasking File containing the instrument
commands from the POC. It combines these commands with spacecraft commands. The
instrument commands are combined with the spacecraft bus commands and compiled
into an ATS or RTS. At this point the command load is treated like a memory load.
The ATS/RTS is sent to MAESTRO for uplink. MAESTRO performs a checksum
validation and uplinks the ATS/RTS to the observatory via MAESTRO script. After
uplink of commands, the memory section on the spacecraft that contains the command
load is linked and compared to verify that the spacecraft command load was successfully
implemented.
The observatory I&T scripts will be converted to MAESTRO scripts and used for
operations. Each I&T script will be scrubbed to remove any commands, arguments or
logic that is specific to the testing environment. The scripts will undergo a table top
review and then verified against the flatsat prior to being approved for operations.

S.4 Data Management

The MOC receives telemetry for observatory state of health monitoring via S-band. Any
alarms generated in the real-time system will be addressed immediately. Subsystem
performance trending is performed on a regular basis to identify trends towards
degradation. Particular attention will be given to the attitude system performance, HPS
fuel budget and performance evaluation, battery and solar panel performance, and
thermal parameters.

Page 33 of 42
The POC is responsible for the configuration and performance of the payload. The POC
receives instrument and selected spacecraft bus state of health telemetry from the DSN in
the Ka-band data stream.
There are 2 recorders onboard the spacecraft; the science data storage and the spacecraft
SOH storage. The science data storage is a Flash Memory Card (FMC-GEN3) that
provides 192 GB of data storage, enough for one orbits data with >100% margin. All of
data on the FMC is downlinked every LAHO contact and forwarded to the POC via the
SN Gateway post pass. The FMC contains 2 orbits of data. Therefore each orbit of data
is downlinked twice at consecutive LAHO contacts increasing the likelihood of
successful downlink to 97.9% The POC will receive all of the science data from the
DSN within 1 day of successful downlink. The spacecraft SOH data is stored in the
Master Avionics Unit. The MAU combines the C&DH and EPS electronics into a single
unit. During mission science operations, the MAU provides storage for up to 70 days
(five orbits) of SOH telemetry at a minimum SOH rate of 1.3 kbps. During the phasing
orbits, when higher-rate downlink is available more frequently, storage is available for 15
days of SOH at a rate of 6 kbps. For the safe-hold telemetry rate of 2 kbps, the MAU
provides over 40 days of storage. The MAU formats stored SOH data to CCSDS
standards and add forward error correction symbols, then send it to the ground through
the S-band transmitter at a minimum rate of 430 kbps. All of the spacecraft SOH storage
is downlinked at every LAHO contact and forwarded to the MOC post pass. The MOC
will receive all of the S-band Playback data within 1 day of successful downlink.

S.S ro[ect Database

TESS C&T Project DataBase (PDB) will be developed prior to and during the I&T flow.
The PDB building blocks will use the existing Orbital LeoStar/MAESTRO format and
schema. As the TESS observatory is developed, component specific updates will be
made to the PDB to ensure the as-built S/C Bus is properly defined in the PDB. Prior to
use in I&T the S/C Bus PDB will be verified against the Flatsat using the TESS FSW
releases. After initial testing a baseline will be released for I&T and MOC for I&T and
Flight product development and use.
The instrument PDB (IPDB) inputs will be provided by the instrument provider.
The IPDB will be developed in support of the initial instrument build and test. The IPDB
will be delivered to the S/C I&T Team for integration in the PDB prior to the start of
instrument integration. The integrated IPDB will be verified as part of the
Observatory PDB on FlatSat prior to electrical integration of the instrument and
spacecraft. The PDB will be placed under TESS CCB control and will follow the Orbital
Engineering Change Request (ECR) process. The Instrument Team will be part of
the CCB to help disposition any instrument specific issues.

Page 34 of 42
The PDB will contain the flight limits. I&T and TVac specific limits sets will be overlaid
in MAESTRO as required, to support those activities.
Several Releases of the PDB will be made in support of the incremental Releases of the
TESS FSW. These deliveries will be carried on the I&T schedule.

S.6 Software Updates

S.6.1 Spacecraft I||ght Software Ma|ntenance

The spacecraft flight software will be maintained for the duration of the mission by the
Orbital Flight Software Engineers at Orbitals Dulles, Va. facility. The facility will house
the TESS FLATSAT to test all updates thoroughly before software loads are generated
and transferred to the MOC for uplink. The FLATSAT will be accessed remotely by the
MOC to execute all maneuver commands prior to execution to ensure the proper thrusters
are being activated at the proper times.
S.6.2 Instrument I||ght Software Ma|ntenance

The POC at MIT is responsible for Flight Software and table maintenance and will
facilitate uplink of these updates when they are needed. Flight Software or tables may be
updated in order to improve instrument performance or overcome anomalies. These
updates are commanded via operations load scripts and are requested through the MOCs
Command Authorization Request (CAR) process. Any update to the instrument software
or tables will be validated by MIT with the appropriate engineering unit or simulator.
When finalized and approved for uplink, the POC determines an appropriate contact for
upload and informs the MOC.
S.6.3 Ground Segment Software Ma|ntenance

A"B"!"# :I% 8&-(43), :31'(,'3'2,

MOC software updates are tested on the backup string in the MOC. The backup string
then supports operations in a shadow mode for an orbit. Upon successful completion of
testing and shadow operations, updates are promoted to the operational system.
A"B"!". 8I% 8&-(43), :31'(,'3'2,

POC/SPOC software updates are verified on the test string. After successful testing the
updates are promoted to the operational string.

Page 35 of 42
A"B"!"! N8I 8&-(43), :31'(,'3'2,

TSO software updates are verified by tabletop reviews. Updates are made to the
operational system after approval. Time Management

Fine adjustments to spacecraft clock can be made to correct clock drift by uploading a
command to adjust the period of a second. The period can be increased or decreased by
increments of 80ns in either a one-shot mode where only the next second is affected, or in
a continuous mode where each second is adjusted.

S.7 Crb|t determ|nat|on

FDF is tasked to provide all Orbit Determination (OD) and Maneuver Planning, Attitude
determination and other Flight Dynamics analysis for the TESS Mission. To perform OD
FDF requires radiometric tracking data from the DSN. All DSN contacts will also include
the required tracking data service for the TESS mission using the S-band 34m BWG
stations. Tracking products during the phasing and mission orbits are the standard DSN
tone ranging and two-way Doppler that produce precise measurements at the appropriate
cadence, enabling orbit predictions of the required accuracy. Details of the ranging
capability of the transponder aboard the S/C are provided in Spacecraft RF Comm
Subsystem section. The Flight Dynamics Facility (FDF) at GSFC receives TESS tracking
data, performs OD, and provides the MOC with the required ephemeris predictions, well
within the time required. The FDF provides initial OD based on input from the SN during
Launch and Ascent on the first day of the mission. Subsequent OD will be performed
using the DSN tracking data. Navigation responsibilities include: orbit determination and
trajectory analysis; maneuver design, execution, and analysis; and generation of predicted
and reconstructed S/C ephemeris. FDF aides the Orbital mission operations team as sole
provider of navigation products: orbit determination and prediction and orbit maneuver
design.

S.8 M|ss|on p|ann|ng

Mission planning activities include orbit updates, ground system resource planning, and
prediction of orbit events. Orbits are updated to maintain the required accuracy and
predictions of orbit path and events are generated. Ground contact times are identified, as
well as perigee and apogee events, and eclipse periods.
Special operations for orbit raising or the North-South Flip are identified long in advance.
Ground station resources are coordinated.
The Mission Planning System (MPS) receives orbital events from FDF, confirmed
contact schedules from DSN and SN, and a Science Tasking File (STF) as input for ATS

Page 36 of 42
generations 3 days (TBD) prior to uplink. An ATS is generated that contains commands
for instrument operations, s/c slew for HGA pointing, Ka-band and S-band transmitter
on/off, and SOH and science data downlink. The ATS is sent to the POC for approval.
The POC sends a CAR to the MOC approving the ATS 1 day prior to uplink. Figure n.n
shows the nominal mission planning flow.

- 8 weeks
DSN provides mid-
range resource
allocations
schedule
-8 wks to -3 wks
DSN Users
resolve resource
conflicts
-3 weeks
DSN Master
Schedule available
- 3 Weeks
TDRS requests
submitted to SN
-3 Weeks
Forecast schedule
Released
-2 wks to -1 wk
SN Users resolve
conflcts
-1 Week
Final Schedule
Released
- 3 Days
POC delivers STF
to MPS
- 3 Days
FDF delivers
Orbital Events to
MPS
- 2 Days
ATS Generation
-1 Day
ATS Approval
Realtime
ATS Uplink
-2 wks to -1 wk
POC generates
boresight
coordinates and
STF
-3 Weeks
TSO delivers
Target list to POC
-4 wks to -3 wks
TSO Identifies
targets of interest

Propulsive maneuvers require a separate ATS and follows different timeline. The finite
maneuver plan is delivered to the MPS 7.5 hours prior to the maneuver. The maneuver
ATS is generated and validated on flatsat/HDS 6 hours prior to the maneuver and
delivered to the MOC for uplink. Table n.n shows the maneuver planning and execution
timeline.

Page 37 of 42

The P/L pointing vector and target star catalog is generated by the POC, passed to the
MOC, and uploaded through the DSN several orbits before it is required. (Are these
already in a format to be uplinked to the s/c or do they have to be compiled by MPS
first?)

S.9 Commun|cat|ons ass Schedu||ng

S.9.1 SN Contact Schedu||ng

The Space Network Access System (SNAS) will be utilized to schedule SN support
services. The SNAS provides Space Network (SN) customers with a network interface to
the Network Control Center Data System (NCCDS), located in the Data Services
Management Center (DSMC). Customers will be able to schedule SN support just prior
to the requested period and also have support tools to ease in scheduling for long-term
planning.
Requests for SN coverage are submitted to the NCCDS 3 weeks prior to acquisition.
NCCDS resolves conflicts with other missions based on s/c priority. A first order
schedule is delivered to TESS 2 weeks prior to acquisition. TESS will then adjust the
timeline of planned activities and request additional coverage as needed. NCCDS
delivers a final schedule 1 week prior to acquisition.
S.9.2 DSN Contact Schedu||ng

The DSN Service Scheduling Software / Service Preparation Subsystem (SSS/SPS) is
used to schedule DSN services. The SSS/SPS provides the user with a web-based

Page 38 of 42
interface to perform the contact scheduling function. TESS mission planning team
provides comm. coverage requirements to the DSN Service Scheduling Software (SSS).
The SPO Office provides DSN Scheduling with a conflict-free 7-day schedule of the
Mid-Range Resource Allocation Schedule at 8 weeks prior to real-time. The TESS
mission planning team logs into SSS and, working with other users, performs conflict
resolution in a collaborative environment. The DSN SPO releases the master schedule
and makes it available to the SPS portal. Upon transfer of the mid-range resource
allocation schedule, DSN Scheduling is responsible for processing all schedule changes
for all weeks transferred up through and including real-time.

S.10 Spec|a| Cperat|ons

S.10.1 Instrument 8ores|ght Ca||brat|on

The boresight calibration begins with the receipt of the full frame images at the first
LAHO contact. The full frame images are sent to the POC. The images are processed to
calculate the boresight vector of each camera. The individual boresights are compared
with one another to define a common P/L boresight and to produce the transformation
matrices between the four individual camera boresights and the common P/L boresight.
The transformation matrices are uplinked to the P/L during an S-band contact in the
second phasing orbit.

S.10.2 ACS Ca||brat|on

Attitude data collected from the star trackers is compared with the common P/L boresight
to produce the transformation matrix between the P/L and S/C bus. The transformation
matrix is uplinked to the bus an S-band contact in the second phasing orbit and the
calibrated pointing is validated. Attitude control tables can be uploaded during tracking
contacts to allow for tuning of ACS parameters.

S.10.3 North ] South I||p

The mission is planned so that the northern ecliptic hemisphere is observed in Year 1 of
the mission and the southern hemisphere in Year 2. At the beginning of the 2
nd
year the
observatory will be reoriented so that the instrument is able to observe the southern
hemisphere. During the LAHO pass at the 26
th
orbit a quaternion will be loaded to rotate
the observatory 180 degrees about the z axis using reactions wheels. TESS will begin
observing the southern ecliptic hemisphere at the start of the 27
th
orbit and remain in that
configuration for the rest of the 2 year mission.

Page 39 of 42
S.10.4 nGA 8ores|ght

Prior to the first Ka-band downlink the HGA antenna will be boresighted. During the first
LAHO contact the HGA will be pointed to the ground based on a predicted boresight. The
boresight will be offset in steps by n degrees for each step. The DSN will report the signal
strength for each step back to the MOC.

Talk about how and when we do momentum unloading (RTS)
S.11 Anoma||es and Cont|ngenc|es (contents from other CSC m|ss|ons)

Orbital has developed a flight-proven anomaly response process designed to guarantee
consistent, effective technical support for Orbital satellite and ground systems. As soon
as anomalous behavior is observed, TESS operations personnel immediately classify the
fault into one of four categories:

Table TBD Anomaly Response Summary

'>F>=DAG @>+D7DAD<7 =>'H<7'> AD5>
Level I Imminent potential foi haiuwaie uamage;
cuiient oi imminent loss of seivice
Immeuiate
Level II Potential foi haiuwaie uamage oi loss of seivice
if not auuiesseu
Eailiest Baytime
Bouis
Level III 0nanticipateu change oi uegiauation of satellite
peifoimance
Next Business Bay
Level Iv 0peiational inconvenience Within 0ne Week

Once the anomaly has been assigned an initial severity level, the control center contacts
the Mission Operations Manager (MOM) or the designated Spacecraft System Engineer
(SSE) for the spacecraft bus or payload. The MOM or the SSE acts as a single point of
contact for all satellite and ground system anomalies. An On-Call Engineer contact is
available 24 hours per day, seven days a week. The control center is given work, pager,
and home contact info to access at all times of the day and night. Orbital also supplies
contact information for a backup SSE in case the primary SSE cannot be reached.
After being contacted by TESS operations personnel, the SSE first ensures that the
satellite is in a safe state. The SSE will authorize the use of pre approved red-limit
response emergency command procedures if necessary. Any action taken will follow the
TESS anomaly escalation procedure and will include the notification of the proper NASA

Page 40 of 42
and project authorities. Once the vehicle has been put in a safe state, the SSE confirms
the severity assessment made by the operations team. The SSE is responsible for
coordinating the FOTs initial anomaly response efforts. The response time is a function
of the severity of the anomaly
Once the observatory has been safed, a full anomaly response team will determine the
proper satellite command activity in response to the anomaly and will perform the
necessary corrective action, once authorized by the project and NASA.
The SSE has business hours and non-business hours and contact information for all
engineering support personnel. In addition, the FOT maintains an escalation list of
management personnel who will be alerted at the level commensurate with the severity of
the problem.
For brief anomaly resolution efforts, the SSE will coordinate the FOT anomaly
response. However, for investigations requiring more than a few days, the Program
Office will appoint a dedicated anomaly team leader who will manage the anomaly
response project. All anomalies are documented in the SOARS database.
S.11.1 Spacecraft Cnboard-Detected Anoma||es
The spacecraft has the ability to detected and respond to a limited set of faults. Upon
detection of a fault, the spacecraft will execute the appropriate fault detection commands
to place the Observatory into a safe configuration. This configuration will be a sun point
safe state depending on the fault. The spacecraft may perform appropriate load shedding
depending on the fault or if the battery voltage drops below preset levels. Payload power
will be removed (it may be abruptly removed dependent on the fault) and the survival
heaters will be activated to maintain payload thermal safe conditions. The table in Figure
4-8 shows the load-shed regimen for the spacecraft and under what conditions the science
payload is turned off.

Page 41 of 42

If possible, upon the next scheduled contact, the spacecraft will establish the S-band
downlink and begin the downlink of telemetry. The spacecraft will indicate that it is in
safe state in the initial state of health telemetry placed into the downlink. Upon receipt of
the telemetry, the MOC will detect the change in configuration to safe state and notify the
FOT as described above.

An on-board anomaly may cause a ground contact to be missed. If a contact is missed the
MOC will detect the missed contact and notify the FOT as described above. During the
next contact the MOC will attempt to turn the transmitter on and perform state of health
data dumps.

S.11.3 Software reset
Need to talk about what to do in the event of software recycle, when to command a recycle
(do we ever want to do this?)
S.11.4 M|ssed maneuver
(add plan in case maneuver is missed)

Page 42 of 42
6. Acronyms

CSR Concept Study Report
TESS Transiting Exoplanet Survey Satellite
HEO High Earth Orbit
TCM Trajectory Correction Maneuver
EOM End of Mission
DRM Design Reference Mission
FSW Flight Software
DSN Deep Space Network
S/C Spacecraft
SOC Science Operations Center
POG Payload Operations Group
DPG Data Processing Group
MOC Mission Operations Control
TSO TESS Science Office
TOIs TESS Objects of Interest
MAST Mikulski Archive for Space Telescopes
DHU Data Handling Unit

Transiting Exoplanet Survey Satellite (TESS) Project Mission Operations Concept Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transiting Exoplanet Survey Satellite (TESS) Project Mission Operations Concept Document

Uploaded by

Copyright:

Available Formats

!"##$%&$%'()$*!

You might also like