Lunar Reconnaissance Orbiter Mission Operations Review (MOR ...

NASA’s Goddard Space Flight Center
Lunar Reconnaissance Orbiter
Flight Operations Review (FOR)
March 11-12, 2009
Day 1

Introduction
LRO Flight Operations Review – Section 1.0
NASA’s Goddard Space Flight Center
Rick Saylor
Deputy Mission System Engineer

Agenda: Day One (March 11, 2009)
GSFC, Bldg 26, Rm 205
Sect. Topic Presenter Time
1 Introduction Rick Saylor/Carolyn Dent 8:30 am
2 Project Overview Cathy Peddie 8:45 am
3 Mission Overview Martin Houghton 9:15 am
4 Ground System & Operations Overview Rick Saylor, Mike Kohout, Jan McGarry 10:00 am
5 IT Security Jim Clapsadle 11:15 am
6 Mission Operations Center Readiness Jim Clapsadle, Jack Murphy, Oscar Hsu 11:30 am
7 Flight Dynamics Facility Support Rivers Lamb, Michael Mesarch 1:00 pm
8 Launch, Network, & Voice Communications Jim Clapsadle 2:00 pm
9 Science Data Management Overview Stan Scott 2:15 pm
9.1 MRF Science Operations Matt Hillyard 2:30 pm
9.2 CRaTER Science Operations Mike Golightly 3:00 pm
9.3 DLRE Science Operations Charlie Avis 3:30 pm
9.4 LEND Science Operations Karl Harshman 4:00 pm
9.5 LOLA Science Operations Mark Torrence, Greg Neumann 4:30 pm
9.6 LAMP Science Operations Joel Parker 5:00 pm
End of Day 1 5:30 pm
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 3

Agenda: Day Two (March 12, 2009)
GSFC, Bldg 26, Rm 205
Sect. Topic Presenter Time
9.7 LROC Science Operations Ernest Bowman-Cisneros 8:30 am
10 Mission Readiness Testing Dave Waters, Ralph Casasanta 9:00 am
11 Launch and Early Mission Operations Rick Saylor 10:00 am
12 Normal Operations Jack Murphy 11:15 am
13 Contingency Preparations Martin Houghton, Rick Saylor 12:15 pm
14 Mission & Operations Systems Testing Rick Saylor 12:45 pm
15 FSW Sustaining Engineering Mike Blau, Scott Snell 1:55 pm
16 Mission Assurance Ron Kolecki 2:15 pm
17 Summary & Forward Plan Cathy Peddie 2:30 pm
18 Review Board Caucus and Concluding Comments Carolyn Dent and Panel 3:00 pm
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 4

MOR Review Board
Review Panel Member Role
Carolyn Dent Co-Chair
David Nichols JPL, Co-Chair
Steven Scott GSFC Chief Engineer
David Martin AETD Deputy Chief Engineer
Elizabeth Corderman Control Center Offline Systems
Raymond Echols MSFC,ISS Payload Operations Director
Chris Jones JPL, Director Solar System Exploration Directorate
Gordon Chin LRO Associate Project Scientist
Maureen Bartholomew Flight Software
John Moses Science Data Processing Systems
Lauri Newman Flight Dynamics Analysis
Linda Pacini LRO Mission IIRT Chair
Wayne Powell Ground Networks
Ivar Tillotson Mission Operations Engineering
Steve Tompkins Ground Systems Engineering
F. Joshua Krage Associate CIO for Information Security
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 5

FOR Objectives
• The objectives of the FOR are to demonstrate that:
(a) All mission requirements, including any changes since MOR, have been fully supported
by the mission operations concept, the ground system architecture, and the
organizational and staffing approach;
(b) Asset protection considerations, including IT and physical security, are complete and
compatible with applicable policies and procedures;
(c) Organizational reporting, roles and responsibilities, staffing and training of mission
operations personnel are complete;
(d) The design of mission unique ground system elements as well as any required
institutional elements has been verified as compatible with mission requirements and all
discrepancies have been satisfactorily resolved;
(e) Comprehensive independent verification and validation of the ground system, including
mission readiness testing and interactive testing with the flight system has been
completed and all discrepancies have been satisfactorily resolved;
(f) Plans for remaining pre-launch activities as well as all operational scenarios and
contingencies are complete with adequate simulation planned for all situations;
(g) The scope and approach for maintaining appropriate mission system elements (such as
flight and ground software) throughout their operational lifetime are fully defined,
planned, and staffed.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 6

FOR Guidelines vs Topic Coverage
FOR Guidelines Sec 1 Sec 2 Sec 3 Sec 4 Sec 5 Sec 6 Sec 7 Sec 8 Sec 9 Sec 10 Sec 11 Sec 12 Sec 13 Sec 14 Sec 15 Sec 16 Sec 17 Sec 18
Mission Requirements/
Operations Concept X X X X X X X X X X X X
Documentation X X X X X X X X X X X X X
Risk Management X X X X X X X X X X X X
Safety/Security X X X X X X
Assurance Activities X X X X
Operations Planning/
Demonstration X X X X X X X X X X
Flight Team
Development X X X X X X X X X
Implementation X X X X X X X X
Testing X X X X X X X X X X X X X
Project and Independent
Review Activity X X X X X X X X X X
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 7

Review Decorum
Attendance Sheet
• Ensure you sign the attendance list on both days of the review.
Review Discussions
• Use the microphone when asking questions and/or have the presenter repeat the
question before providing the response.
• Only ask questions relevant to the subject of the review. Out of scope questions will
be referred to other forums.
• Offline discussions should be taken outside of the meeting room.
Requests For Action (RFAs)
• Blank RFA forms are available from the review Chair.
• Each RFA must clearly state the action that the project is required to take. Provide a
target due date.
• The RFA rationale must clearly state the consequences of the project not taking the
recommended action.
• RFAs must be written or sponsored by a review board member.
• Ensure you provide contact information (e-mail address and telephone number).
• RFAs will be dispositioned with the project at the end of the review.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 8

Review Logistics
• Review packages made for Review Panel
– Supporting documentation in back of the room
– Electronic version of packages will be made available via Webdrive
• Lunch suggestions and locations are located on the sign-in table
• Fire drill exit instructions
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 9

ADS Attitude Determination System
ADST Attitude Determination System Team
AETD Applied Engineering Technology Directorate
AGS Attitude Ground System
AP Archive Plan
APID Application Packet Identification
AS Antenna System
ASCII American Standard Code for Information Interchange
ASU Arizona State University
ATS Absolute Time Sequence
BER Bit Error Rate
BMOC Backup Mission Operations Center
BPSK Biphase Shift Keyed
BWG Beam Wave Guide
CBE Current Best Estimate
CCB Configuration Control Board
CCSDS Consultative Committee for Space Data Systems
CDDIS Crustal Dynamics Data Information System
CDF Consolidated Data Format
CDR Critical Design Review
Acronym List (1)
CFDP CCSDS File Delivery Protocol
CPU Central Processing Unit
CRaTER Cosmic Ray Telescope for the Effects of Radiation
CTT Compatibility Test Trailer
DB Database
DEM Digital Elevation Model
DLRE Diviner Lunar Radiation Experiment
DM&AP Data Management & Archive Plan
DMR Detailed Mission Requirements
DMS Data Management System
DPS Data Processing System
DR Discrepancy Report
DRB Discrepancy Review Board
DSMC Data Services Management Center
DSMC Data Systems Management Center
DSMS Deep Space Mission System
DSN Deep Space Network
EDR Experiment Data Record
EELV Evolved Expendable Launch Vehicle
ESR Engineering Support Room
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 10

FD Flight Dynamics
FDF Flight Dynamics Facility
FDMT Flight Dynamics Maneuver Team
FDPC Flight Dynamics Product Center
FEP Front End Processor
FISMA Federal Information Security Management Act
FMEA Failure Modes Effect Analysis
FSMF Flight Software Maintenance Facility
GigE Giga Bit Ethernet
GN Ground Network
GN&C Guidance Navigation & Control
GNSO Ground Network Scheduling Office
GPS Global Positioning System
GS Ground System
GS&O Ground System & Operations
GSE Ground System Electronics
GSFC Goddard Space Flight Center
HDR High Data Receiver
HGA High Gain Antenna
Acronym List (2)
HGAS High Gain Antenna System
HTML HyperText Markup Language
HTSI Honeywell Technology Solutions Inc.
HV High Voltage
HW Hardware
I&T Integration & Test
I/F Interface
ICD Interface Control Document
IDQ Ingest Data Quality
IIRV Improved Inter-Range Vectors
IKI Institute for Space Research
ILIADS Integrated Lunar Information Architecture for Decision Support
ILRS International Laser Ranging Service
IOC Initial Operational Capability
IT Internet Technology
ITDF Internal Transponder Data Format
ITOS Integrated Test & Operations System
ITPS Integrated Trending & Plotting System
JPL Jet Propulsion Laboratory
kbps kilo-bits per second
KSC Kennedy Space Center
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 11

LAMP Lyman Alpha Mapping Project
LAN Local Area Network
LDWG Lunar Data Working Group
LEND Lunar Exploration Neutron Detector
LOI Lunar Orbit Insertion
LOLA Lunar Orbiter Laser Altimeter
LR Laser Ranging
LRO Lunar Reconnaissance Orbiter
LROC LRO Camera
LSOC LAMP Science Operations Center
LTS Lunar Terminator Sensor
LTT Lifetime Trend
MAS Monitoring & Alert System
MB Mega-Byte
Mbps Mega Bits per Second
MCC Mid Course Correction
MCS Mars Climate Sounder
Acronym List (3)
MCS Monitor & Control Subsystem
MDPS MOC Data Processing System
MERR Mission Event Readiness Review
MET Mission Elapse Timer
mJ milli-Joules
MIPL Multimission Image Processing Lab
MOC Mission Operations Center
MOR Mission Operations Room
MORR Mission Operations Readiness Review
MOT Mission Operations Team
MPS Mission Planning System
MRO Mars Reconnaissance Orbiter
MRT Mission Readiness Test
MRTP Mission Readiness Test Plan
MRTT Mission Readiness Test Team
ms millisecond
MSP Mission Support Plan
MSSS Malin Space Science Systems
MSTA Mission Service Training Activities
MTASS Multi-mission Three Axis Stabilized Spacecraft
MTBF Mean Time Between Failure
MTTR Mean Time To Repair
NACK Negative Acknowledge
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 12

NAIF Navigation and Ancillary Information Facility
NASA National Aeronautical and Space Administration
NENS Near Earth Network Services
NIC Network Interface Card
NISN NASA Integrated Network Services
NIST National Institute of Standards and Technology
nm nanometer
NMC Network Management Center
NOM Network Operations Manager
NOP Network Operations Plan
NPR NASA Procedure Requirement
NRD Network Requirements Document
O&M Operations & Maintenance
OD Orbit Determination
PC Personal Computer
PDS Planetary Data System
PDU Packet Data Unit
PHP Hypertext Preprocessor
Acronym List (4)
POC Payload Operations Center
PPDF Plot Parameter Definition Files
PSLA Project Service Level Agreement
RAID Redundant Array of Independent Disks
RAS Remote Access System
RDR Reduced Data Record
RGS Remote Ground Station
RMA Reliability, Maintainability, Availability
ROI Regions of Interest
RTAD Real-time Attitude Determination
RTS Relative Time Sequence
SA System Administrator
SAT Site Acceptance Testing
SC Spacecraft
SCN Space Communications Network
SCP Secure Copy
SDM Science Data Management
SDPS Station Data Processing System
SDR Single Design Review
SDS Science Data System
SE System Engineering
SIS Software Interface Specification
SISDL Systems Integration & Software Development Lab
SLE Space Link Extension
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 13

SLR Satellite Laser Ranging
SN Space Network
SOARS Spacecraft Orbital Reporting System
SOC Science Operations Center
SPC Signal Processing Center
SPEC Specification
SPICE Spacecraft Planet Instrument C-Matrix Events
SPS Service Preparation Subsystem
SPS Signal Processing Subsystem
SQL Structured Query Language
SSA S-Band Single Access
SSC Swedish Space Corporation
STOL System Test and Operations Language
SW Software
SWRI Southwest Research Institute
SWSI Space Network Web Services Interface
T&C Telemetry & Command
TCP Transmission Control Protocol
TLM Telemetry
TO Task Order
Acronym List (5)
UCLA University of California, Los Angeles
UPD User Performance Data
USN Universal Space Network
UTDF Universal Tracking Data Format
VC Virtual Channel
VCDU Virtual Channel Data Units
WAN Wide Area Network
WDISC White Sands Data Interface Service Capability
WOTIS Wallops Orbital Tracking Information System
WS1 White Sands 1 (Ground Station)
WSC White Sands Center
XML Extensible Markup Language
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 14

Project Overview
LRO Flight Operations Review – Section 2.0
NASA’s Goddard Space Flight Center
Catherine Peddie
LRO Deputy Project Manager

LRO Driving Objective
• Strategic Goal 6: Establish a lunar return program
having the maximum possible utility for later
missions to Mars and other destinations.
– 6.1. By 2008, launch a Lunar Reconnaissance Orbiter
(LRO) that will provide information about potential human
exploration sites.
• NASA has moved LRO launch to May 2009 to
accommodate both other national launch priorities and
problems with missions ahead of LRO in the launch
manifest
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 16

LRO Mission Objectives
Locate Potential Resources
Hydrogen/water at the lunar poles
Continuous solar energy
Mineralogy
Safe Landing Sites
High resolution imagery
Global geodetic grid
Topography
Rock abundances
Space Environment
Energetic particles
Neutrons
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 17

LRO Mission Overview
• Launch in early 2009 on a Atlas V into a
direct insertion trajectory to the moon.
Co-manifested with LCROSS lunar
impactor mission.
• On-board propulsion system used to
capture at the moon, insert into and
maintain 50 km mean altitude circular
polar reconnaissance orbit.
• 1 year exploration mission with planned
extended science mission.
• Orbiter is a 3-axis stabilized, nadir
pointed spacecraft designed to operate
continuously during the primary mission.
• Investigation data products delivered to
Planetary Data Systems (PDS) within 6
months of primary mission completion.
LRO & LCROSS on Atlas-Centaur Upper Stage
LRO in 50 km polar orbit
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 18

Orbiter
LRO Mission Segment Definition
Space Segment
– Payload
• CRaTER • Diviner • LAMP
• LEND
• Mini-RF
• LOLA • LROC
– Spacecraft Bus
Launch Segment
• Launch Vehicle
• Launch Support Services
• Payload Processing Support
Key:
Ground Segment
Ground System
• Space Communications
Network
• Mission Operations Center
• Networks (Voice & Data)
• Flight Dynamics Facility
Science Data Systems
– Science Operations Centers
• CRaTER • Diviner • LAMP
•LEND •LOLA •LROC
• Mini-RF
– Planetary Data System
LRO Mission Data Command and Telemetry
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 19

The LRO Spacecraft
INSTRUMENT MODULE
(6 instruments, 460 Gbits/day)
2 m
PROPULSION MODULE
(898 kg N2H4)
SPACECRAFT BUS
(Modular Honeycomb Design)
AVIONICS PANEL
(SpW/1553, 412 GbitsStorage)
LRO Orbiter Characteristics
Mass (CBE) 1916 kg Dry: 1018 kg, Fuel: 898 kg (1313 m/sec)
Orbit Average Bus Power 681 W
Data Volume, Max Downlink rate 461 Gb/day, 100Mb/sec
Pointing Accuracy, Knowledge 60, 30 arc-sec
HIGH GAIN ANTENNA
(40 W KaTx, 100 Mbps)
SOLAR ARRAY
(2000 W BOL, 80 AH Battery)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 20
Y
Z
X

LRO Reserves & Margin
LRO Reserves & Margins at PSR
Cost (reserve on cost-to-go) 16%
Schedule (usable free shifts) 12
Technical Resource Limit CBE Margin
Mass, Dry (kg) 1066.5 1018.4 4.7%
Power (W) 823 685 20.3%
RF Link - At Lunar Distance
Uplink HGA – S-Band (WCS)
Omni – S-Band (DSN)
Downlink HGA - S-Band
(USN)
(WCS)
HGA - Ka-Band (WCS)
- -
- -
20.3 (dB)
15.9 (dB)
6.93 (dB)
4.64 – 7.44 (dB)
7.46 (dB)
RF Link – Worst Case (Tumble at Lunar Distance)
Uplink Omni – S-Band (DSN) - - 15.9 (dB)
Data & Computational Margins
Ka Downlink Utilization (min) 180 85.0 47%
Measurement Interruptions – Data Capture (Orbits) 234 80 193%
1553 Bus Utilization (kbits/sec) 300 193 35%
CPU (% utilization) 100% 29.6% 67%
EEPROM (Kb) 2048 983 23%
uP RAM (kB) 36864 18860 26%
PCI Bus (% utilization) 100% 21.8% 62%
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 21

The Lunar Reconnaissance Orbiter
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 22

LRO Instruments and Investigations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 23

LRO-LCROSS Launch Segment
• Launch Services Provided by KSC
• Atlas V 401 through NLS Contract
• 2000 kg/C 3 ~-2.0;
Sun Exclusion thru Ascent
• 4m fairing; H/K data thru EELV I/F
• Co-manifested with LCROSS lunar
mission
• Launch Site Processing at Astrotech
including Fueling and Control Center
LRO Atlas Fairing at Astrotech
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 24

LRO at Astrotech Building 2 North
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 25

LRO Project Organization & Execution
LRO Project Overview
• Directed in-house NASA GSFC Mission
executed for NASA ESMD
• Competitive AO for Instruments,
selection on 12/23/04
• In-house Spacecraft Bus & Mission
Operations leveraging previous and
ongoing GSFC missions.
• Project Funded in February 2005 and
development begun in earnest.
• Approximately 300 people, a mix of CS
and on-site contractors, plus Instrument
Teams.
• Project transitions to (and retains)
Mission Director role after
commissioning for ESMD mission.
• Mission Director role transitions from
Project to GSFC SSMO for SMD
extended mission. Plan being
developed per 400-PG-7120.0.1
– Transition Plan will include a Transition
Review which will include any Flight
Operations changes required by SMD.
02/24/2009
ACS
J. Simpson
C&DH
Q. Nguyen
Comm.
A. Rodriguez
Arroyo
Electrical
D. Duvall
Project Scientist
R. Vondrak
Deputy 600
J. Keller
Science Data Mgmt.
S. Scott
Chief Safety and
Mission Assurance300
Officer
R. Kolecki
Deputy CSMO
L. Lee
EEE Parts
R. Williams
Manufacturing
N. Virmani
Materials
P. Joy
Quality Assurance
A. Lacks
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 26
Reliability
L. Lee
Safety
J. Rezac
Lunar Reconnaissance Orbiter (LRO) Project
S/W Quality Assurance
C. Taylor
Laser Ranging
R. Zellar
Mechanical
G. Rosanova
Power
T. Spitzer
LRO Project Manager
C. Tooley
200
Deputy Project Manager
C. Peddie
Public Affairs
Deputy Project Manager /
Resources
100
Officer
N. Neal-Jones
B. Sluder
Admin. - P. Gregory 400
600
EPO Lead
B. Hsu
Financial
Manager
Vacant
400
Mission System Engineer (MSE) - ITA
D. Everett
Mission Business Mgr.
J. Smith
500 Deputy MSE - Mission Architecture & Design
Resource Analysts
V. Martinez
M. Houghton
Project Support
Manager
K. Opperhauser 400
CM/DM
D. Dusterwald/
W. Schultzaberger
EVM
R. Hesenperger
General Business
J. Reid
MIS
A. Hess/J. Brill
Scheduling
A. Eaker
Propulsion
C. Zakrzwski
Software
M. Blau
Thermal
W. Ousley/C. Baker
Original Signed By:
Craig Tooley Date
Lunar Reconnaissance Orbiter (LRO)
Project Manager
Deputy MSE - I&T and Operations
R. Saylor
Avionics Systems
P. Luers
Contamination Ctrl.
C. Lorentson
Flight Dynamics
M. Beckman
GN&C Systems
E. Holmes
Mech./Thermal Sys.
S. Wasserzug
LEND
I. Mitrofanov
ISR, Moscow
CRaTER
H. Spence
Boston University
LOLA
D. Smith
GSFC
Contracting
Officer
J. Janus
Safing
S. Andrews
S/C Bus & LV Systems
T. Ajluni
S/C Sys. & Verification
M. Pryzby
SW/HW Systems
C. Wildermann
Systems Analysis
L. Hartz
Spacecraft
Orbiter
Launch Vehicle Ground Systems Payload Systems
Bus
I & T Lead
Manager
& Operations
Manager
T. Ajluni 500 J. Baker 500
T. Jones 400
R. Saylor 400
A. Bartels 400
GS&O Deputy
TBD
MOT Lead
Payload Systems
Engineers
500
J. Murphy
GS&O System Engr.
J. Cerullo
L. Hartz
J. Clapsadle
M. Reden
Diviner
D. Paige
UCLA
LROC
M. Robinson
Arizona State Univ.
LAMP
R. Gladstone
SWRI
431-REF-000223
Mini - RF
S. Nozette
ACT

LRO Top Level Schedule
Ver. 17B
Program Control
LRO Mission Milestones
LRO S/C Des/Fab/Build
CRaTER
DLRE
LAMP
LEND
LROC
LOLA
Mini-RF
GS/MO Development
Implemention & Test
Integration and Test
Ship/Launch Site Ops
Flight Operations
2005 2006 2007 2008 2009 2010
CY Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
PSR LAUNCH
SRR 9/27
CDR 11/ 6
PER 2/9 4/24
AO
Select 4/27
10/6 2/ 7
NAR
5/ 17
IBR ICDR
6 complete
6/28 (MRF 2/20)
MOR
9/14
7/22
MRR
3/31
FORR 3/11
4/22
IA R IP DR PDR S-Band Award
ITP PSE PM Ka S.Array 3/11
LRR
Phase B Phase C Phase D
Solar Mod
PDR
Phase
(9/28)
B Battery Award CDR (6/26) GNC HW
Awarded
Flight Battery
to I&T
PER (9/11-completed)
(Rec) @ GSFC
(1/7) DELIVERED
PDR (9/14) CDR (5/18) TRR (8/27-completed)
PER (9/12) CDR (4/13) PER (6/6-compl eted)
PDR (9/21) CDR (6/12) PER (8/22-completed)
PDR (9/8) CDR (5/ 31)
DPDR (10/5) CDR (7/13)
Network Decision Regt's Peer
Review
WAC/SCS TRR
(completed on 11/1)
PDR (5/11) CDR (2 /20) TRR (10/16-compl eted)
GS Release #1
Mission ConOps
(start) Integ.
(Fi nal)
I&T Start
(AM/Core S/C build)
(Rec) @ GSFC
(2/25)
(Rec) @ GSFC
(2/19)
(Rec) @ GS FC
(3/ 24)
(Del) to LRO
(4/14)
Mission Ops Testing
Rehearsals/Excercises
(complete)
LRO Ship to KSC
Env. Test
to KSC (2/11/09)
12 days Slack
Test/Align/Fuel/Install
Nominal
Mission (end)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 27
(PER) 11/14)
WS1 Test
Read iness
IM Integ. complete
(less Instruments)
(Del) to LRO
5/4/08
GS Release #3
GS Release #2
(GS Freeze)
Orbit er I&T
(complete)
AM Integ.
(complete)
(Rec) @ GSFC
(5/9)
DELIVERED
DELIVERED
DELIVERED
DELI VERED
Commissioning Complete
DELIVERED
DELIVERED
LAUNCH
1/31/09

Ver 18B
LRO I&T Path to Launch
EVENT
1 SN RF Compatability Test
2 C&DH Integration & Testing
3 TT&C Integration & Testing
4 LAMP Integration
5 ST Installation
6 CRaTER Integration
7 Diviner Integration
8 LEND Integration
9 LOLA Integration
10 DSN RF Compatability Test
11 CSS Integration & Testing
12 LROC Integration & Testing
13 Mini-RF Installation & Testing
14 SAS Installation and Testing
15 MR#2 Launch & Early Cruise
16 Comp Perf. Testing (stage 1 complete)
17 HGAS Installation and Testing
18 PER
19 Sine Vibe Test Completed
20 Acoustics Test Completed
21 Mass Properties Test Completed
22 EMC Test Completed
23 TVAC Testing (start/finish)
24 Post Env. Testing CPT's Completed
25 MR#4 Day in the Life Completed
26 SIMS (early mission contingencies)
27 SIMS (LOI-1 contingencies)
29 PSR
30 Ship To KSC (arrival date)
31 SIMS (early mission)
32 MR#5 (launch & cruise activities)
33 FORR
34 Launch Day Aliveness
35 MRR
36 LRO PLA Mate
37 Ready for Launch (+18 days Slack)
2008 2009
2/28/09
Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May
2/14
2/26
3/5
3/19
3/19
4/2
4/4
4/16
4/19
4/23
5/12
5/16
5/19
5/23
6/10 7/14
6/16
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 28
8/13
6/23 7/22
6/26 7/25
6/30 7/30
7/8 7/18
- new launch date (5/20/09) baseline milestone revisions
8/19
9/9 11/19
1
12/23
12/10 1/14
12/22 1/22 1
1/24
1/29
2/1 2/7
2/3 2/10
2/11 2/12
2/20
3/1 3/30
3/11
3/24 4/14
3/9 1
3/30
4/7 4/28
4/24 5/20

LRO Path to Launch – Key Upcoming Events
FOR 3/11-12/2009
WGS Atlas launch (LRO Training) 3/14/2009
Final Instrument Tests/Closeouts 3/13-20/2009
SIM 23 - Launch 3/24/2009
MR 5 – Launch and Cruise thru LOI 3/30- 4/3/2009
Configure Orbiter for Atlas Integration 4/6-14/2009
LVGOR & LVRR 4/2/2009
Atlas Vehicle Erection on stand 4/7-8/2009
MRR (unconfirmed date, may change) 4/16/2009
MR 3 - Lunar Orbit Acquisition & S/C Commissioning 4/15-17/2009
LRO Fueling Ops 4/17-23/2009
SMSR 4/24/2009
LRO Mate to PLA and LCROSS 4/28/2009
Atlas Launch Wet Dress Rehearsal 4/29/2009
Encapsulation in Fairing 5/4-5/2009
SIM 25 – Integrated Launch Day 5/11/2009
FRR 5/14/2009
LRR 5/19/2009
Launch 5/21/2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 29

LRO/LCROSS Launch Dates
• LRO directed by LPRP to plan for the launch dates below
– May 20 not shown, LRO does not plan on launching May 20th although it is in
the official set.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 30

LRO Overall Status – Project Perspective
• Launch site testing and preparatory activities are proceeding on schedule.
– Post shipment functional testing of spacecraft and instruments has been completely
successful thus far.
Orbiter Functional
Payload Functional
Propulsion ETE test
Launch Day Configuration Procedure (multiple runs)
HGAS Pop & Catch
SA Panel Aliveness
CSS & Star Tracker Functional/Aliveness
LAMP ETE
LEND ETE
Alignment Checks
DSN Compatibility Testing (follow-up to prior testing)
Flight Procedure check-out on Orbiter (multiple sessions)
• Additional slack imposed on us by directed launch date slip has given us ample time
to deal with problems with the hardware or flow should they arise.
• Project Management believes the LRO Team and Ground Systems will be ready to
fly the mission upon launch on May 21, 2009.
• Management, Engineering, and Assurance are in concordance with respect to risks
and overall risk posture
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 31

LRO Status – Hardware Changes Since MOR
• Two Significant Changes to the Orbiter since MOR
– Solar Array Gimbal thermal design changes implemented to lower
unexpectedly high temperatures seen in T-Vac
Radiator added & thermal blankets modified
Solar Array off-pointing (30 deg.) now planned during peak
power/temperature environments. Implemented via existing off-set
capability.
– LEND Flight Unit replaced with spare to resolve problems with high
voltage discharge, and subsequent internal LEND damage, seen in T-
Vac.
No significant operational impacts, some LEND thermistor calibration curves
will be modified after LOI.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 32

LRO Flight Operations Status – Project
Perspective
• LRO’s I&T was the Project’s main priority and focus over the last year. The intense LRO I&T
schedule impacted the Project’s ability to make our expected progress in this area. The MOT, as
well as the rest of the LRO Team, was heavily involved in I&T and in addition, the Orbiter was not
available for flight operations testing as much as is typical during I&T at GSFC. The extension of
Orbiter Thermal-Vacuum testing to resolve the LEND and SAS problems at the end of I&T
precipitated a re-assessment and re-plan of the work remaining from there to FOR. Just prior to
Christmas the LRO Project decided to delay FOR until after shipment and further re-prioritize the
flight operations work to focus on early mission (through LOI), accepting some risk to the
efficiency of the commissioning phase.
– A table top independent review of the revamped plan forward was conducted in January with
a positive outcome.
– The Project has communicated and vetted the prioritization of work and the attendant risks to
the timeliness of the start of the nominal mission phase to the Program and HQ. We do not
anticipate a delay in nominal mission start.
– Not only was the flight operations work re-prioritized, the entire Project was re-focused on
making flight operations readiness a priority. (For example the ongoing work at KSC is
replanned as necessary, within imposed constraints, to support critical flight operations work
such as SIMs, Rehearsals, and command and automated procedure testing).
• The progress since the revised ops plan was implemented has been outstanding.
Although our posture is not as ideal as we would like, the Project is completely confident
we can safely deliver LRO to lunar orbit and highly confident the nominal mission will
successfully begin on-time once we’re there.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 33

Revised Mission Ops Plan Forward
LRO Mission Op Overview Plan
Activity
Finalize TVAC
CPT‐2
STOL Procedures
develop
checkout/test
finalize
1
January
2 3 4 1
February
2 3 4 1
March
2 3 4 1
April
2 3 4 1
May
2 3 4
Flight Procedures Document
develop
finalize and review
Draft Release
Baseline
Contingency Procedures Document
develop
finalize and review
Ops Documentation
Flight Operations Plan
Launch & Early Msn Hdbk
Flight Rules
Operations Agreements
Launch Early Msn Team document
S/C User Guide
Instrument User Guides (from all)
GS&O Launch Coutdown Script
Mission Timelines
update releases
MRT Testing
complete MRT #3
complete MRT #6
ORT Testing
USN retest
MOC SW verficiation
All Drafts Submit Final Drafts Submit
ITOS
DMS
ITPS
MPS
AGS
Simulations
LRO‐SIM‐09 (Reserve)
LRO‐SIM‐25 (Integrated Launch Sim)
LRO‐SIM‐14 (LOI‐1 Contingencies)
LRO‐SIM‐28 (Early Msn w/contingencies)
LRO‐SIM‐21 (LOI Contingencies)
LRO‐SIM‐15 (Early Msn w/contingencies)
LRO‐SIM‐24 (Early Msn w/contingencies)
LRO‐SIM‐19 (Spacecraft Contingency Testng)
LRO‐SIM‐13 (Instr Calibration)
LRO‐SIM‐26 (Nominal Ops)
LRO‐SIM‐06 (LOI Contingencies)
LRO‐SIM‐22 (Instr Calibration)
LRO‐SIM‐23 (Integrated Launch Sim)
Rehearsals
MR#4 ‐ Nominal Ops
MR#5 ‐ Launch to LOI
MR#3 ‐ Lunar Orbit Acq & S/C Commissioning
Flight Ops Review
Coordination w/external org
ETE Test w/SOCs
preparation, dry runs, etc
review
Draft Slides
Dry Run
Final Slides
Pre‐ship Review
FOR
preparation
review
PSR
ship S/C
Reviews
Launch
Early Mission
Commissioning
Ship LRO S/C
Flt Cntler TIM
MRR? LRR?
Orbiter 'offline' 1 week for ship to KSC 4/5 last day to access 4/22 LRO fueling 4/28 LRO mate to PLA,
NASA’s Goddard Space Flight Center orbiter
LCROSS
LRO Flight Operations Review (FOR) Day 1 - 34

LRO Review History & RFA Summary
Review Date
LRO Mission Review Chronology & RFA Status as of Mission FORR
Total # of
RFAs
Responses
Submitted by
Project
RFAs closed/
suspended by
Review Team
Open RFAs Overdue
Mission SRR 8/18/2005 32 32 32 0 0
Mission PDR 2/7/2006 81 81 81 0 0
Confirmation Review - - - - -
Mission CDR 11/10/2006 61 61 61 0 0
LRO Ground Segment SDR 1/18/2007 30 30 30 0 0
LRO Ground Segment MOR 9/19/2007 14 14 14 0 0
Mission PER 7/22/2008 25 25 24 1 0
Mission PSR 2/9/2009 11 6 3 8 0
LRO Payload RFA Status as of Mission FORR
I-PDR I-CDR I-PER I-PSR
Total Open Total Open Total Open Total Open
CRaTER 5 0 9 0 8 0 1 1*
DLRE 48 0 14 0 29 0 0 0
LAMP 14 0 6 0 15 0 2 0
LEND 3 0 11 0 5 0 0 0
LOLA 57 0 11 0 27 0 10 1*
LROC 17 0 25 0 19 0 0 0
Mini-RF 35 0 39 0 0 0 0 0
* Open RFA is advisory only
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 35

LRO Open RFA Status
RFA # Title Requester Status
LRO-MOR-ADV-0002 LOI Contingency Timelines C. Jones Project responded, advisory RFA,
originator plans to close at FOR
LRO-Mission-PER-0006 FlatSat Fidelity C. Jones Project responded, originator
requested further details
LRO-Mission-PSR-ADV-0001 Mission Planning Interface Exercise C. Dent Project responded, advisory RFA,
originator has concurred closure
LRO-Mission-PSR-0003 Star Tracker Ram Upload Practice F. Huegel Open
LRO-Mission-PSR-0005 LOLA Exercising of Redundant Laser E. Dukes Project responded, believed to be
closeable
LRO-Mission-PSR-0006 Contingency Procedure Development E. Dukes Project responded, believed to be
closeable
LRO-Mission-PSR-0007 Review Final Flight Temperature Predicts E. Powers Open, awaiting completion of final
predicts by LRO Thermal
LRO-Mission-PSR-0009 Titanium in Flight hardware L. Pacini Open, report in work
LRO-Mission-PSR-0011 Launch, Ascent, Separation Thermal Analysis M. Bay Open, response being formulated
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 36

L
I
K
E
L
I
H
O
O
D
5
4
3
2
1
8
CONSEQUENCES
Criticality Approach
High
Med
Low
6
1 2 3 4 5
LRO Open Risk Matrix
1
7
M – Mitigate
W – Watch
A – Accept
R – Research
2 3
4
5
Rank Approach Risk Title Risk ID
1 M LOLA Laser Design Lifetime not Qualified by Lifetest prior to Launch LOLA-261*
2 R Suspect Part in Transponder LROP-284
3 M Flight Operations Readiness Behind Schedule LROP-281
4 M LOI Mission Risk LROP-121*
5 W Mission Critical Event – Initial Sun Acquisition LROP-123*
6 W FAA Potential Disapproval of LR Radar Operation LROD-254
7 M Blanketing of Spacecraft While Powered On LROP-270
8 M DMS Development GN&O-262
*Note: Marked risks will be residual risks at the time of LRO’s launch.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 37

LRO Open Risks
LRO Risk: LOLA Laser Design Lifetime not Qualified by Lifetest Prior to Launch Risk ID: LOLA-261*
Rank Risk Statement Approach & Plan Comments/Status
1 Given The failure in the LOLA EM
laser life test,
Then: LOLA may not achieve the
recommended 800 million shots
necessary to meet its Level 1
science requirements.
M
Mitigate:
Examine and review why EM laser lifetest
failed. Most likely cause established
(failure of laser optics common to both
lasers, possibly contamination induced).
Laser 2 cavity undamaged. Rebuild
common optics train and resume lifetest on
Laser 2 only (complete, lifetest resumed
9/19). In parallel, LRO to examine ways to
extend flight laser lifetime operationally
and plan to minimize the number of shots
at the orbiter level pre-launch. Examples:
automated safing to shut laser down if
thermistor failure causes diode
temperature increase.
Additional Watch Plan: Monitor
performance of rebuilt EM laser after
resumption of testing. Make operational
decisions based on performance during
test.
Contingency:
Assuming Laser performance floor of 500
million shots, LOLA science team to
examine impact of more-limited lifetime on
the LOLA L1 data products.
In Progress:
Apr 08: Root cause not established, effects (common optics
damage, L1 diode heat sink burn marks) known. Possible ways to
extend flight operational lifetime include safing, minimizing shots
on ground & duty cycling lasers .
May 08: As result of 5/31 LRO/LOLA risk assessment meeting,
LRO and Proj. agree that LRO proposes to fly LOLA as-is, and
will resume the EM laser lifetest ASAP, ensuring that the
hardware is as flight-like as possible .
Aug 08: Rebuild/retest of the EM laser currently on schedule to
resume extended ops testing by end of Sept.
Sept 08: Rebuild of the EM laser completed and extended vac
testing has resumed. W/launch delay, there is time for the rebuild
EM laser to reach 500 million shots by launch. Test results and
risk assessment to be monitored monthly.
Oct 08: As of 11/05, LOLA has accumulated 92 million shots in
vacuum towards the goal of 500 million shots by 4/24/09. Laser
performance is nominal.
As of 12/01, LOLA EM laser has accumulated 152 Mshots in
vacuum. Performance remains nominal (this includes normal
increasing of the switch out time, which has increased from 170
usec to 180 usec over the test to date).
Dec 08: 219 Mshot in vac as of 12/24, switch out time still 180
usec. Reassess likelihood when total number of shots hits 350-
400 million shots, predicted by the end of March.
Jan 09: As of 1/29, EM laser now at 304 million shots. All
performance, including switch out time, remains nominal.
Feb 09: As of 2/25, EM laser now at 366 million shots. All
performance parameters remain nominal. Switchout time
continuing slow, steady increase, but no changes to diode current
setting have been performed to date.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 38

LRO Open Risks
LRO Risk: Suspect Part in Transponder Risk ID: LROP-284
Rank Risk Statement Approach & Plan Comments/Status
2 If: The Teledyne-Cougar Amplifier
in the General Dynamics (GD)
Transponder must be inspected or
replaced,
Then: LRO will not be able to
launch on time.
M
Research:
has already performed an extensive
investigation regarding the part’s hermetic
packaging, and LRO EEE Parts
engineering, LRO Mission Assurance, and
key AETD personnel are now also
engaged in an investigation the potential
problem.
In Progress:
Investigation is ongoing. Preliminary assessment is that the LRO
parts will eventually be exonerated and approved to fly as-is.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 39

LRO Open Risks
LRO Risk: Flight Operations Readiness Behind Schedule Risk ID: LROP-281
Rank Risk Statement Approach & Plan Comments/Status
3 If: An acceptable level of flight
operations readiness is not
achieved prior to LRO fueling,
Then: The LRO launch may be
delayed.
M
Mitigate:
Mission Operations development work
replanned in late December 2008 and
moved FORR to post PSR and shipment.
Overall integrated LRO schedule also
replanned to give Ops work 1st priority.
Operations work prioritized based on
ensuring successful lunar orbit insertion
and Orbiter safety. The Project has
accepted some risk that the
commissioning phase may have to be
extended if there are issues with nominal
operations activities due to lack of full
testing and problem resolution.
*Sim15 completed 3/9/09.
Context:
This risk is the more comprehensive continuation of risks # 228
and 182. The aggressive LRO I&T schedule and its extension
through a series of T-vac test extensions to resolve hardware
problems has impacted the progress in the readiness posture of
the LRO MOT. Key elements of the MOT were engaged in
supporting I&T throughout the past year.
In Progress:
Jan 09: MR4 (nominal Ops) completed with only major issue
being problems with DMS (see risk 262). Sim28 successfully
completed (early mission contingencies). Overall plan reviewed
with independent experts and judged sound.
Feb 09: Sims 14, 21, & 24 completed successfully. DMS dataflow
test to resolve MR4 issues ongoing, successful thus far. MOT has
made excellent progress and is preparing for FOR.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 40

LRO Open Risks
LRO Risk: LOI Mission Risk Risk ID: LROP-121*
Rank Risk Statement Approach & Plan Comments/Status
4 If: A failure or error occurs during
the critical Lunar Orbit Insertion
(LOI) phase of the mission
Then: Loss of the mission may
occur.
M
Mitigate:
Detailed reliability and mission success
analysis will be applied to all mission
elements, including ground operations, for
this phase of the mission. The results of
these analyses will be used to define
mitigations that will be implemented in
hardware and operational planning. Refine
planned trajectory to provide fly-by fallback
and thus eliminate mission ending
level of risk.
In Progress:
Oct 07: Planning to generate LOI Implementation Plan by end of
year. Will review with all interested parties.
Mar 08: The various end items associated with the planning and
execution of LOI are falling into place. FD and Ops have well
established procedures in place. Some contingency actions still
need to be formalized. The testing of the "system as a whole" will
begin in relatively short order.
Apr 08: The first simulation of LOI was run last week at Flatsat.
Problems with the dynamic simulator prevented a successful
completion of the test, but much was learned about both the GSE
and the Orbiter. Plan to perform simulation again week of 5/12,
as problems are believed to be resolved.
May 08: Successful LOI Mission Simulation was completed using
FlatSat and the nominal sequence. Future sims will include LOI
contingencies.
Jul 08: LOI timeline was an integral part of recent Orbiter
Functional (ran as part of CPT). Closed-loop sim was run
numerous times, successfully, via the onboard ATS. LOI will be
practiced in upcoming Mission Sims/Rehearsal, which will include
contingency operations.
Feb 08: LOI was successfully practiced during MR2 8/21/08 and
Simulated twice during Orbiter T-Vac as part of the Orbiter
Functional. LOI contingency SIMs run the week of 2/2/09.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 41

LRO Open Risks
LRO Risk: Mission Critical Event – Initial Sun Acquisition Risk ID: LROP-123*
Rank Risk Statement Approach & Plan Comments/Status
5 If: LRO fails to acquire the sun
before the battery is discharged
Then: the mission may be lost.
M
Watch:
Detailed reliability and mission success
analysis will be applied to all mission
elements, including ground operations, for
this phase of the mission. The results of
these analyses will be used to define
mitigations that will be implemented in
hardware and operational planning.
In Progress:
Oct 06: If we fail to acquire the sun, analysis shows that we have
an additional 2 hours before battery reaches 40% State of
Charge. Nominal ground contact in

LRO Open Risks
LRO Risk: FAA Potential Disapproval of LR Radar Operation Risk ID: LROD-254
Rank Risk Statement Approach & Plan Comments/Status
6 If: The FAA disapproves the use of
ground radar system at the laser
ranging optical site,
Then: The LR ground site may be
non-operational.
L
Watch:
Project is proceeding at risk with LR
installation and ground radar system setup
pending FAA approval. The formal FAA
approval process has been initiated, FAA
has returned a memo with comments to
which the project will respond.
Contingency:
Forward observer may be used to spot
aircraft in the event that the FAA
disapproves use of radar. This enables
laser ranging to occur without radar use.
However, full ranging capability may not be
achieved, and there would be a cost
impact associated with hiring observer
staff. If an objection letter is received,
GSFC and LRO will pursue HQ approval
for operation of the laser with the radar
and will proceed with the operation.
In Progress:
Feb 08: Project proceeding at risk pending FAA approval of radar
use. Project has also received approval for use of radar from
GSFC Code 250 (Safety), and is pursuing approval with NASA
HQ.
May 08: A letter of objection from the FAA may be pending. If this
letter is received, GSFC and LRO will pursue HQ approval for
operation of the laser with the radar and will proceed with the
operation. Ground Site open beam testing may be impacted by ~
2 - 4 wks.
July 08: Code 453 has briefed LRO and GSFC management. HQ
brief pending. No objection received from FAA yet. Likelihood
probably decreasing since objecting FAA personnel reportedly
moved to new position.
Nov 08: Code 453 met with FAA rep and inspected optical site
radar. FAA indicated approval is likely, but wanted input from
another FAA colleague. 2nd FAA rep visiting optical site on
11/24/08.
Dec 08: Update pending based on results of optical site visit.
Jan 09: GSFC Safety & Environmental Division received a verbal
non-objection from the FAA for operation of the LR Ground
System laser. Anticipate receipt of formal letter stating no
objection prior to the launch of LRO. Risk will be closed upon
receipt of letter.
Feb 09: Still awaiting ‘no objection’ letter. Intend to operation LR
unless FAA formally objects.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 43

LRO Open Risks
LRO Risk: Blanketing of Spacecraft While Powered On Risk ID: LROP-270
Rank Risk Statement Approach & Plan Comments/Status
7 If: Proper procedures are not
followed while performing thermal
blanket installation on a powered
spacecraft,
Then: Ongoing testing may be
interrupted and/or the spacecraft
may be damaged.
L
Mitigate:
Work to procedures, ensure that all WOAs
are in place prior to work. Monitor all
powered activities.
In Progress:
Jun 08: Personnel have been trained on procedures. Appropriate
staff in place to monitor activities.
Aug 08: Procedures in place have been adequate to date.
Jan 09: Orbiter has completed I&T with no incidents. Will
continue to monitor thru launch preparation.
Feb 09: Continue to monitor activities through encapsulation.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 44

LRO Open Risks
LRO Risk: DMS Development Risk ID: GN&O-262
Rank Risk Statement Approach & Plan Comments/Status
8 If: DMS (Data Management
System) does not work,
Then: Ground transfers of products
will not happen and will require the
GS&O team to develop
tools/scripts to accomplish the
tasks, possibly delaying the
execution of the nominal mission
on schedule after Orbiter
commissioning.
L
Mitigate:
Dedicated a system in the MOC for SW
developer to test and verify incremental
patches. Developer has been support
simulations and focus on testing different
pieces required for each SIM. Additional
end-to-end testing planned (WS1->MOC-
>SOCs) to verify fixes to DMS in February
2009.
In Progress:
Apr 08: DMS has been able to transfer FDF products, but issues
remain with orbiter files and modeling of files.
May 08: DMS development continues and during simulations
pieces have been working, but still missing the complete model,
signature, and web portal modules.
Jun 08: Development continues, due to CPT preparations and
CPT itself, mission simulations have been halted.
Jul 08: DMS progress has slowed down in the MOC due to delay
of sims from CPT. But DMS was installed in I&T and is being
used for transferring files. Setup has identified new problems
which are being addressed.
Sept 08: DMS had some issues during MR2, plan is to release 2
patches before MR4.
Oct 08: DMS Software delivered with most features. Waiting for
final testing.
Nov 08: System is going through testing.
Dec 08: Completed release 3 SW testing. 56 discrepancy reports
(DRs) found during testing. Plan to take new update before MR 4.
Jan 09: DMS did not successfully transfer instrument
measurement files during MR4. Other (MOC internal) aspects of
DMS are working properly. Key problems found and fixed and
MR4 data being transferred via DMS to SOC before the month’s
end.
Feb 09: DMS delivered post MR 4 release patch to address
problems encountered during the rehearsal. Simulated MR4 data
dump using the DMS (WS1->MOC->SOCs) was successfully
completed. Over 99% of the files were successfully transferred
autonomously. 8 files required manual intervention. This meets
the requirements and is acceptable performance for the nominal
mission.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 45

LRO Readiness – PM Perspective
• The LRO TC\FLT
Controllers have been
operating the Orbiter
beginning with the
board level testing of
each of the LRO
subsystems.
• This table illustrates
the depth of
experience we have
with the critical
functions and
operations of the LRO
spacecraft.
• We have been honing
our skills in the
operation of LRO
throughout the entire
development and I&T
phase of our mission.
• LRO Project
Management is
completely confident
that we know how to fly
and operate LRO.
Mission Activity CPT 1 & 2 T‐Vac/Bal
LRO Mission Activity Mapping to Test Activities
Orbiter
Functional
& Payload
Functionals
Pop &
Catch
Tests
Sep
Test MRTs ORTs
LRO Orbiter Separation from Atlas X X X X X X
Space Network Telemetry Acquisition X X X X X X
AOS @ 2kbs ‐ DSN Goldstone X X X X
AOS WS1 X X X X
Post Sep Verification X X X X
Transition to 128kbps telemetry X X X X X X X
AOS @ DSN Madrid X X X X
SSR turn on X X X X X
PDE Inhibit Checks & Catbed turn on X X X X X X
AOS @ USN Weilheim X X X X
Solar Array Deployment X X X X
High Gain Deployment X X X X
Transition to Observing Mode X X X X X
Thruster 1‐shots X X X X X X
Delta‐H Momentum Unload X X X X X
Post Sep FDF Product Update X X
Generate Ephemeris & ATS Loads X X
Uplink Cruise Loads to Orbiter & Start ATS X X X X X
Transition to HGA Communications X X X X X
GNC KF Configuration X X X X X
Prelim MCC Maneuver Planning Verification X X
Final MCC Manuever Planning Verification X X
Load MCC‐E & MCC‐1 Manuever Plans X X
Pre‐MCC‐E Config Verification X X
MCC‐E Burn & Post Burn Activities X X X X
Pre MCC‐1 Config Verification X X
MCC‐1 Maneuver & post Burn Activities X X X X
CRaTER Instrument Turn‐on Activities X X X X X
LEND Instrument Turn‐on Activities X X X X X
Early Cruise Mini‐Gyro Calibration X X
LOI‐E & LOI‐1 Maneuver Plan Released & Tested X X
Pressurize Prop Sys ‐ Open HPLV & Fire Pyros X X X X X X
LOI Manuevers X X X X X
Spacecraft Commissioning X X
HGA Calibrations X X
Gyro & ST Calibrations X X
NASA’s Goddard Space Flight Center
Ka‐Band Checkout
S‐Band Rate Checkout
X X
LRO Flight Operations Review X (FOR) X
X
X
X
Day X1 - 46
X
X
Instrument Commissioning X X X X
Nominal Mission X X X X X
Propulsion
System
Tests
Mission
SIMs
Mission
Rehearsals

Project & Mission Overview Backup Slides
• Backup slides include:
– Risk management definitions
– Residual risk info
– Flight system diagram
– Spacecraft views
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 47

RISK
DEFINITIONS
LRO Accepted and Residual Risk Definitions
RISK: A risk is any potential set of circumstances that may affect mission
cost, schedule, technical performance or safety.
ACCEPTED RISK: A LRO “accepted risk” is defined as a risk that the
Project opts to accept on the basis of any of the criteria stated below:
–The risk has been mitigated to an acceptable level as deemed by
Project management (implies minimal impact to the Project if the
conditions occur).
–The cost/schedule/technical impact of further mitigation exceeds
the perceived value of the mitigation.
–The mechanisms for mitigating the risk lie outside of LRO control.
–No further mitigation options are available/viable for the risk.
*Note: An accepted risk may or may not be a residual risk, but continued efforts to
mitigate are not deemed practical.
RESIDUAL RISK: A LRO “residual risk” is any accepted risk with the
capacity to affect LRO’s ability to meet Level 1 Requirements (full mission
success criteria).
*Note: A residual risk must always be an accepted risk. Residual risks cannot be
further mitigated without undue impact to cost, schedule, or technical performance.
Risk Management Process and Responsibilities
Project
Manager
Accept
(if necessary)
RMB/
Subsystem Leads
Control
Control
Identify
Identify
Analyze
Analyze
Individuals
and Teams
Sources: NPR 8000.4 and GPR 7120.4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 48
Close
Close
Plan
Plan
Communicate
& Document
Track
Track
NASA’s Continuous Risk Management Model

C
O
N
S
E
Q
U
E
N
C
E
Criticality L
High
Med
Low
LRO Risk Management Criteria Summary
Reference: 431-PLAN-000193
I
K
E
L
I
H
O
O
D
5
4
3
2
1
1 2 3 4 5
CONSEQUENCES
Level Very Low (1) Low (2) Medium (3) High (4) Very High (5)
Technical
Schedule
Cost
No impact to full mission
success criteria.
Consumes ≤ 25%
remaining slack.
Consumes ≤ 1% of
remaining Project reserves.
Safety Negligible or No impact.
Minor impact to full mission
success criteria.
Consumes 25% - 50%
remaining slack.
Consumes 1%-5% of remaining
Project reserves.
Could cause the need for only
minor first aid treatment .
Moderate impact to full mission
success criteria. Minimum mission
success criteria achievable, with
some margin remaining.
Consumes 50% - 75% remaining
slack; planned launch maintained.
Consumes 5% - 20% of remaining
Project reserves.
May cause minor injury or
occupational illness or minor property
damage.
Major impact to full mission success criteria.
Minimum mission success criteria is
achievable.
Consumes 75% – 100% slack, launch
remains within planned launch opportunities.
Consumes 20% - 50% of remaining Project
reserves.
May cause severe injury or occupational
illness or major property damage.
Minimum mission success criteria
is not achievable.
Consumes all slack, planned
launch opportunities missed.
Consumes > 50% of remaining
Project reserves.
May cause death or permanently
disabling injury or destruction of
property.
S *As per the LRO CRM Plan, safety risks shall be managed according to existing NASA and GSFC safety and hazard processes. Safety risks shall be recorded in the LRO NGIN RM system only if they affect other
parameters such as schedule, cost, or technical performance.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 49
L
I
K
E
L
I
H
O
O
D
Level
Very High
(5)
High
(4)
Medium
(3)
Low
(2)
Very Low
(1)
Technical Risk
Probability
Programmatic Risk
Probability
P > 50% P > 75%
25 < P ≤ 50% 50% < P ≤ 75%
15% < P ≤ 25% 25% < P ≤ 50%
2% < P ≤ 15% 10% < P ≤ 25%
0.1% < P ≤ 2% P ≤ 10%
*All risks closed prior to August 1, 2008 were evaluated according to previous schedule assessment criteria wrt to an October 2008 Launch Date*

L
I
K
E
L
I
H
O
O
D
5
4
3
LRO Residual Risk Matrix
2 5 3 4 1
1
17 18
19 20
21 22
11 12
13 14
15 16
6 7 8 9
10
1 2 3 4 5
CONSEQUENCES
Criticality Approach
High
Med
Low
M – Mitigate
W – Watch
A – Accept
R – Research
2
Rank Risk Title Risk ID
1 Launch Vehicle Integrity LV-279
2 No Independent Safe Hold Mode LROP-282
3 CRaTER EEE Part Reliability – PH300 CRaTER-236
4 Swapout of LEND Flight Unit for Flight Spare after TVac Testing LEND-278
5 LROC NAC Primary Mirror Grounding Payload-266
6 LOLA Flight Analog Board FPGA May Not Be Staked LOLA-250
7 JPL Noncompliance with LRO MAR LRO MA-137
8 Premature Failure of Diviner Actuator Payload-212
9 Potential Crack Propagation in HGA Bonding due to Thermal Cycling LROSE-269
10 Integrated Reaction Wheel Assembly Life Test ACS-145
11 Surface Charging Requirements LROSE-134
12 Tyco Contacts LRO MA-272
13 Test-as-you-fly Exception for LOLA Sapphire Lens Deep Charging Payload-240
14 LOLA Contamination LOLA-73
15
LOLA Detectors May Have Been Damaged by Inadvertent Pressure Increase
During LOLA TVac Test
16 LOLA Laser Diode Qualification Performed in Non Flight Test Conditions LOLA-66
17 SAS Gimbal Over Temperature Therm-276
18 Damage due to High Power Lasers LROD-198
19 DSB Memory Errors C&DH-274
20 White Sands RFI GN&O-112
21 LAMP Aperture Door Inoperable in Orbiter TVac Configuration Payload-268
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 50
LOLA-256
22 Symmetricon Ultra Stable Oscillator Tin Whisker Growth LROD-271

LRO Project Residual Risks (1 of 5)
Rank Risk # Title Risk Statement Closure Statement L C
1
2
3
4
5
LV-279 Launch Vehicle Integrity If Atlas V integrity can not be proven prior to LRO
launch, then the LRO spacecraft may be rendered
inoperable or destroyed by an LV failure.
LROP-
282
CRaTER
-236
LEND-
278
Payload-
266
No Independent Safe
Hold Mode (Gold Deviation
DE-0007, Rule 1.17)
CRaTER EEE Part
Reliability – PH300
Swapout of LEND Flight
Unit for Flight Spare after
TVac Testing
LROC NAC Primary
Mirror Grounding
If a temporary failure of the main processor occurs,
then the lack of a separate safe hold processor will
result in loss of mission.
Amptek PH300 EM parts have failed twice in the
CRaTER EM after several month’s use. This
presents a risk that the PH300 may fail in flight,
affecting CRaTER’s functionality. Code 562
conducted an investigation of the failed part. No
root cause was able to be determined.
IF LRO replaces the LEND flight unit with the
LEND flight spare after Orbiter TVac testing is
complete, then the LEND Flight Spare Unit will not
have seen the typically-prescribed number of
operating hours (1000) expected of a flight
Instrument.
If an ungrounded NAC primary mirror should build
up a charge, and a discharge event were to
happen, then there could be an impact to the S/C
and/or performance of the NAC.
Project has relayed this risk to the program office with a recommended
best case plan (utilize flight spare components and ETU structure, and
enable long lead items to be ordered ASAP, attempt to maintain
experienced staff). Project accepts this as a residual risk as potential
mitigations are outside of project control.
A watch dog was added to the S-Comm card to power cycle the C&DH if
the processor stops communicating. This will reset the spacecraft to its
default power on condition, which has been tested extensively. This
mitigation makes the occurrence of this risk extremely unlikely. The risk
was accepted by the center, program office, and NASA HQ through the
confirmation review process.
Circuit design around the PH300 was modified between the EM and
flight. Flight should not have this problem with the PH300 because the
circuit cannot deliver enough current to cause the failure seen Flight unit
does not show any evidence of degradation to date. No further
mitigations are viable.
Due to damage to the original flight unit (see risk 277), the LRO project
opted to accept the potential residual risk associated with this item. In
addition, the flight spare (FU02) was delivered with 210 operating hours,
including over 100 in vacuum (twice what was expected). The project
plans to run LEND on orbiter as much as possible until launch,
anticipating that it will have >400 op hrs before launch. Project believes
this risk has been mitigated to an acceptable level, and that flying the
original flight unit would impose a greater risk to the mission.
ESS waiver to fly as is has been approved, risk is minimal and
implementation of further grounding practices poses potential damage to
sensitive mirror coatings. Further mitigations are not viable within
programmatic constraints.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 51
2 5
1 5
2 3
2 3
2 2

LRO Project Residual Risks (2 of 5)
Rank Risk # Title Risk Statement Closure Statement L C
6
7
LOLA-
250
LRO MA-
137
8 Payload-
212
9 LROSE-
269
LOLA Flight Analog
Board FPGA May Not Be
Staked
JPL Noncompliance with
LRO MAR
Premature Failure of
Diviner Actuator
Potential Crack
Propagation in HGA
Bonding due to Thermal
Cycling
10 ACS-145 Integrated Reaction
Wheel Assembly Life Test
(Gold Waiver WA-0033, Rule
4.23)
LOLA may be flying unstaked Flight Analog Board
FPGA, with potential to affect LOLA’s functionality.
If JPL does not adequately address all the
requirements listed in the LRO MAR the Diviner
(JPL) instrument may not meet mission success
criteria.
If the Diviner Actuators fail on orbit, Level 1
requirements will be impacted.
If suspected voids in the HGA bonding cause crack
propagation due to thermal cycling on orbit, then
HGA functionality may be lost or degraded.
IF the Integrated Reaction Wheel Assembly
experiences a failure in it's life test or cannot meet
2x life demonstration before launch, then IRWA’s
might not meet on-orbit life requirements.
Main Electronics Box (MEB) with unstaked FPGA on analog board has
successfully competed vibration and thermal vacuum testing. Visual
inspection indicates that the FPGA also survived tests mechanically.
Risks presented by re-work of the board are greater than the risk of
flying as-is.
Memorandum of Understanding in place between GSFC and JPL. DLRE
will be following JPL standards and practices, which do not include any
reliability analysis. Although some reliability analysis will be done at
GSFC, no further mitigations are available at the project level.
Probable root cause of MCS anomaly has been indicated as grit
released and ground up in the elevation actuators. Due to increased
supervision of Starsys build process, it is believed that this problem is
extremely unlikely to occur on orbit.
It is suspected that voids exist in the HGA bonding which may expand
and contract during thermal cycling, potentially causing crack
propagation that in flight may result in loss of some HGA functionality.
However, after initial thermal testing, the visible surfaces of the HGA
bond show no evidence of crack propagation. To further examine the
bond (i.e. internally by xray or other methods), would cause significant
schedule impact and is not deemed viable. Project management
determined that the minimal likelihood of this risk indicated that
inspection after thermal vacuum posed a more significant risk to the
project than flying as is.
Gold Rules require that this item be tested to 2x life to demonstrate
reliability prior to launch. Life test will not meet 2x life prior to launch
without launch date extension. Nominal performance in life test to date
demonstrates minimal risk and shows that it is not worthwhile to extend
the life date to meet the requirement; a waiver against this rule has
already been approved.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 52
1 4
1 4
1 4
1 4
1 4

LRO Project Residual Risks (3 of 5)
Rank Risk # Title Risk Statement Closure Statement L C
11 LROSE-
134
12 LRO MA-
272
13 Payload-
240
Surface Charging
Requirements
If the external surfaces of the Instruments do not
have an adequate bleed path for surface charge
build up, damage to the LOLA receiver lens, LROC
telescope, LAMP cabling, Mini-RF, solar array, high
gain antenna, and/or C&DH may occur.
Tyco Contacts If bad contacts are not detected prior to launch,
there will be an intermittent connection which could
lead to open circuit, resulting in lost functionality on
orbit.
Test-as-you-fly Exception
for LOLA Sapphire Lens
Deep Charging (LRO
Waiver, CCR 780)
If LOLA is unable to test the expected deepcharging
flight environment on a representative
sapphire lens of the LOLA design, LOLA may
experience degraded performance on-orbit.
14 LOLA-73 LOLA Contamination If adhesives in the laser cavity migrate to LOLA
optical surfaces, then contamination-induced
optical damage may occur either on the ground or
on orbit.
15 LOLA-
256
LOLA Detectors May
Have Been Damaged by
Inadvertent Pressure
Increase During LOLA
TVac Test
During LOLA TVac test, the chamber pressure
increased from 10^-5 to 20 torr while LOLA was
operating, resulting in a possibility of latent damage
to the instrument.
Implemented all corrective actions recommended by Aerospace
Corporation (consulted), but final independent confirmation was not
received. Project believes that this risk has been mitigated to an
acceptable level, and that no significant threat remains.
LRO uses approximately 1650 G08S1 socket contacts, all from the
GIDEP affected date code range. These are used in the Avionics Box,
harness, avionics harness, and LOLA Instrument. Pin retention tests
were conducted contacts from both the LRO flight lots, as well as on
LRO’s residual Tyco contacts. All pulled in-family and all passed pin
retentions testing. In addition, the spacecraft is being monitored
throughout testing for any intermittencies, and will be investigated fro the
potential of a bad contact in the event of an anomaly. The remaining
G08S1 contacts have been quarantined. The risk has been thoroughly
investigated and mitigated to an acceptable level. There is minimal
probability of a contact failure on LRO, and further efforts to mitigate this
risk would not be worth associated schedule and financial costs.
Test performed, although test facility unable to achieve on-orbit
predicted levels. No optical degradation seen. Waiver against ESS
approved. No further mitigation options available (outside scope of cost
& schedule).
Mitigation plans including precision cleaning of LOLA parts and limitation
of the amount of adhesives in the cavity were executed. LOLA laser
output energy was monitored through TVac. The only orbiter level
activity which would have been likely to realize this risk was the orbiter
level Tvac test, which was successfully completed; EM laser life test has
seen >319Mshots with nominal results. No further mitigations are
available and likelihood is minimal.
LOLA detectors now have over 900 op hours at the orbiter level without
anomaly. All available mitigations have been put in place, risk has been
mitigated to very low likelihood. Any further mitigations are out of
cost/schedule scope.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 53
1 3
1 3
1 3
1 3
1 3

LRO Project Residual Risks (4 of 5)
Rank Risk # Title Risk Statement Closure Statement L C
16 LOLA-66 LOLA Laser Diode
Energy Degradation
17 Therm-
276
18 LROD-
198
SAS Gimbal Over
Temperature
Damage due to High
Power Lasers
If LOLA laser diode is not qualified under space
flight conditions, diode energy may degrade faster
than manufacturer specifications, leading to failure
on orbit. Diode failure mode is associated with
vacuum.
If the SAS gimbal and or cable wrap temperatures
become too warm due to harness power
dissipation, then the lubricant may boil off causing
the actuator or cable wrap to fail in orbit.
Residual risk is that if LRO is in a hot sunlit sunsafe
scenario for an extended period the gimbal life
may be shorted due to accelerated loss of
lubricant. Risk is primarily to extended mission.
If a 532nm laser energy of sufficient energy density
to exceed the detector damage threshold impinges
on the LR Telescope, then LOLA channel 1 will be
damaged and Laser Ranging capability will be
disabled.
LOLA diode qual unit has more than 1 billion shots at ambient. At the
time of launch, the laser diodes will have been tested to over 1x mission
life, and will have been verified under space flight conditions. Remaining
risk associated with not testing in vacuum is accepted.
XZ Cablewrap radiator built, installed and tested. 30° SA off-point
implemented, will be used if needed. 1/31/2009: Model correlation
improved, predications now acceptable. The results of the assessments
and recommendations regarding the thermal math model correlation &
functional qualification of the gimbal assembly are contained in 451-
MEMO-003443. Risk has been mitigated down to an acceptable level,
further mitigations are out of cost/schedule scope.
Ops plan has been modified to implement available mitigations to
prevent damage while ranging from apache point. LRO LR team
assessed laser sites that are members of the International Laser
Ranging Society to determine which sites had the capability to damage
the detector. It was found that 22 of these sites have the capability to
damage the detector. In addition, there are 4 sites where capability could
not be computed. Sites outside the ILRS, or unknown to the LRO LR
team also present a potential threat to the detectors. At present, only
two sites have expressed interest in partnering with LRO (preventing the
possibility of unintentional damage). See SER 451-SER-001200 for
more details.
In addition to asking ILRS sites to forgo ranging, LRO will turn the HGA
away by approximately 2°for less than 3 mins while passing near a
Lunar Surface retro. Specific passes and turn-away times will be
determined at the LOLA SOC and sent to the LRO MOC for inclusion in
mission planning products.
No further mitigation options are available.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 54
1 3
1 2
1 2

LRO Project Residual Risks (5 of 5)
Rank Risk # Title Risk Statement Closure Statement L C
19 C&DH-
274
20 GN&O-
112
21 Payload-
268
22 LROD-
271
DSB Memory Errors If additional memory errors develop within the DSB,
LROs ability to store science data could be
affected.
White Sands RFI If Radio Frequency Interference (RFI) exists
between the SDO, LRO ground stations and SN
EET systems, then service impacts or data loss
could occur.
LAMP Aperture Door
Inoperable in Orbiter
TVac Configuration
Symmetricon Ultra Stable
Oscillator Tin Whisker
Growth
It’s a remote possibility that damage to the LAMP
aperture door was incurred in vibe/acoustics and
will remain undetected in Tvac, in which case
LAMP may need to deploy the fail-safe door on
orbit, and will suffer degraded science.
If tin whisker growth becomes apparent on the
Backup Symmetricon USO, then LOLA and LR
data may be degraded.
GSFC Code 560 recommends that LRO fly as-is. Analysis and testing
indicate it's extremely unlikely that an increase in bit errors that may
impair the mission could occur. Mitigations (including mapping of
affected memory areas) have been implemented, and a contingency
plan is in place. Further mitigation is out of cost/schedule scope.
Mitigations including the installation of a filter to the MA Cal antenna
were executed, and a contingency plan is in place. Effectiveness of
mitigation steps unknown until SDO launches. Further mitigations are
impractical, the project accepts remaining residual risk.
WOA-01914 successfully executed to verify that the aperture door
deploys. LAMP Aperture Door only has positive design margin in 1-g
environment when Orbiter is in (+Y) vertical orientation; TVac
configuration did not allow for aperture door actuation during TVac.
CPT2 successfully completed; LAMP aperture door actuation remains
nominal. Ambient testing shows that door has survived cycling, but does
not demonstrate that the door operates over temperature extremes.
Further mitigations are not available.
Based on recommendations from Rick Schnurr and Henning Leidecker,
no action is required by LRO to change the USO system design or the
USO electronics. Backup USO should remain unpowered while LRO
operates with the Primary USO. Risk mitigated to acceptable level.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 55
1 2
1 2
1 2
1 2

LRO System Block Diagram
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 56

LRO Dimensional Layout (Deployed)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 57

LRO Dimensional Layout (Stowed)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 58

Mission Overview
LRO Flight Operations Review – Section 3.0
NASA’s Goddard Space Flight Center
Martin B. Houghton
Mission Systems Engineering

Instrumentation / Data Products
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 60

Level 1 Success Criteria
Full Mission Success Criteria
• Meet all requirements set forth in ESMD-RLEP-0010 (Level 1 requirements
document), including operating LRO in the primary lunar mapping orbit for at
least one year and delivering the specified data products to the Program Office
via the PDS within six months of acquisition.
Minimum Mission Success Criteria
• Meet the following criteria in the North and South polar regions (lat > 88.5°)
– Assess meter-scale surface features (including rock size and abundance).
– Obtain geodetic topography with a spatial resolution of 50 m, horizontal, by
2 m, vertical, to an accuracy of 500 m, horizontal, by 18 m, vertical.
– Characterize the illumination environment to identify permanently shadowed
regions (for potential water-ice locations) and permanently illuminated sites.
• Deliver the acquired data sets to the PDS within 12 months of acquisition.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 61

Success Criteria Bottom Line
Full Mission Success
• Requires 1 year (minimum) of S/C & P/L operations
Minimum Mission Success
• Multiple ways of getting at each of the data products
– e.g. image-based topo; topo-based illumination models
• Begin to meet these criteria in as little as 3 months
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 62

Spacecraft Overview
INSTRUMENT MODULE
(6 instruments, 460 Gbits/day)
2 m
PROPULSION MODULE
(898 kg N2H4, 1313 m/s)
Total Mass: 1916 kg
SPACECRAFT BUS
(Modular Honeycomb Design)
AVIONICS PANEL
(SpW/1553, 412 Gbits Storage)
HIGH GAIN ANTENNA
(40 W Ka Tx, 100 Mbps)
SOLAR ARRAY
(2000 W BOL, 80 AH Battery)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 63
Y
Z
X

Sun-Safe
• Manage sun relative to S/C
• Wheels, CSSs, IRU-optional
• SA in predefined position
• HGA in predefined position
Observing
• Nadir, Inertial, Offset pointing
• Wheels, IRU, STs
• SA tracking Sun
• HGA tracking Earth
Spacecraft Control Modes
Power-On/Reset
Sun-Safe Delta-H
Cmd,
Safing
Cmd
Cmd
Auto, Cmd,
Safing
Cmd
Auto, Cmd,
Safing
Cmd
Observing Delta-V
Auto, Cmd,
Safing
Delta-H
• Hold attitude, unload mom.
• Thrusters, IRU
• SA in predefined position
• HGA in predefined position
Delta-V
• Hold attitude, adjust velocity
• Thrusters, IRU, STs
• SA in predefined position
• HGA in predefined position
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 64

Mission Trajectory / Orbits Overview
NASA’s Goddard Space Flight Center Day 1 - 65

Mission Timeline / Phases
Launch & Early Ops Nominal Mission
Extended Mission
NASA’s Goddard Space Flight Center Day 1 - 66

1 Initial Sun Acquisition Time Critical
2
3 Propulsion Activities Critical
4
Early Mission Timeline / Critical Events
Deployment Activities Time Critical
Mid-Course Correction Time Critical
Critical Events List
Nominally autonomous (protects instruments). In worst case anomaly, battery provides
at least 2 hours of contingency time.
Solar Array and High Gain Deployments will be performed through ground command
and monitoring. Backup onboard script will deploy solar array after 75 minutes
otherwise.
Momentum management , trajectory and orbit maneuvers will be performed through
ground command and monitoring.
Must be performed within 24-hrs of separation or correction will exceed on-board
propulsive allocation.
5 Lunar Orbit Capture Burn Time Critical
Must be initiated within 10 minutes of target time or capture requirements will exceed
unallocated margin.
NASA’s Goddard Space Flight Center Day 1 - 67

Nominal Mission Timeline
Launch & Early Ops Nominal Mission
Extended Mission
Shadow ~28 minutes Pole
Sun Light ~57 minutes Pole Shadow ~28 minutes
NASA’s Goddard Space Flight Center Day 1 - 68

The Moon-Centered Universe
• Twice a month, LRO’s orbit will be in full
view of the Earth for roughly 2 days.
• Twice a month, LRO will perform a
momentum management maneuver while
the ground has complete coverage.
• Once a month, LRO will perform a stationkeeping
(SK) maneuver while the ground
has complete coverage.
• Twice a year, LRO’s orbit will be in full
view of the Sun for roughly one month.
• During the eclipse season, LRO will have
a max. lunar occultation of 48 minutes.
• LRO’s orbit will be targeted such that lunar
solstice occurs near maximum occultation.
• Twice a year, LRO will perform a 180°
yaw maneuver.
• Twice a year, the Moon will pass through
the Earth’s shadow (Lunar Eclipse).
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 69

Solar Array Off-Pointing (NEW)
Solar Beta 30
• SA Angle ≠ Solar Beta Angle
• Thermal & Power are Drivers
• No impact to Instrument Ops
• No change to FSW (existed)
• From Beta 0-30, add 30 deg
• From Beta 30-90, subtract 30
• Performed via MOC support
• Offset change @ 2/4 months
NASA’s Goddard Space Flight Center Gordon Chin - Science OverviewLRO Flight Operations Review (FOR) Day 1 - 70

Lunar Eclipses: 2009-2013
Date Type Penum.
2009 Feb 09
2009 Jul 07
2009 Aug 06
2009 Dec 31
2010 Jun 26
2010 Dec 21
2011 Jun 15
2011 Dec 10
2012 Jun 04
2012 Nov 28
2013 Apr 25
2013 May 25
2013 Oct 18
Lunar Eclipse Overview
(2) 4:03
(1)
(1)
(2)
(3)
(4)
(4)
(4)
(3)
(2)
(2)
(1)
(2)
2:12
3:16
4:15
5:26
5:38
5:39
6:00
4:33
4:41
4:12
0:54
4:04
Partial Total
– –
– –
– –
1:02 –
2:44 –
3:29 1:13
3:40 1:41
3:33 0:52
2:08 –
– –
0:32 –
– –
– –
Type 1: 2009 Jul 07
Type 2: 2009 Feb 09
Type 3: 2010 Jun 26 Type 4: 2010 Dec 21
Lunar Eclipses are “seasonal” w/ ~ 4 year severity cycle
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 71

Delta-V / Fuel / Mass Totals
MISSION PLAN
Δ V
(m/sec)
Fuel
(kg) SOURCE
Mid-Course Correction 16 15.4 3σ LV errors
LOI-1 (with Checkout) 579 441.3 Deterministic
Subsequent LOI Man. 360 224.4 Deterministic
Mission Orbit Insertion 56 31.7 Deterministic
Orbit Station-Keeping 162 88.3 Deterministic
Ext. Mission / Margin 140 70.9 N/A
Momentum Unloading – 17.0 4 years Total
Other (Residuals) – 9.0 Conservative
Total 1313 898
- Atlas V 401 allocation
imposed a 2000 kg limit
- Mission limit = 1965 kg
- Launch Mass = 1916 kg
- 898 kg fuel (tank limit)
set final ΔV = 1313 m/s
- Extra Contingency Fuel
and/or Extended Mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 72

Extended Mission Options
• Up to 140 m/s of Extended Mission Fuel
- 10 more months in 50 km Mission Orbit
- 18 yrs in Frozen Orbit (not supportable)
• Other options have been discussed
• Decision made during Nominal Mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 73

Eventual End-of-Mission
• EOM Disposal is covered in 451-PLAN-003504 (everything’s in order)
NASA’s Goddard Space Flight Center Day 1 - 74

Flight Rules Overview
• Flight Rules are contained in LRO Flight Rules and Constraints Document (431-OPS-000309)
• 4 Levels of Classification:
– Class A: Violation of this rule would result in loss of mission, in the loss of key objectives (specifically
the loss of the capability to collect measurement data), orbiter damage, or the loss of consumables.
– Class B: Violation of this rule would result in loss of a component or degradation of measurement data.
– Class C: Violation of this constraint would result in less optimum performance of the orbiter, data loss or
temporary measurement interruption. Violation of this rule may not necessarily affect the ability of the
mission to meet full mission success criteria.
– Class D: Violation of this rule may not lead to any loss of data or service, but could if compounded by
additional circumstances. The rules are captured to provide the preferred way of implementing
operations activities to prevent these situations.
CDH
COMM
CRAT
DLRE
FSW
GNC
LRO Flight Rules & Constraints Summary
LAMP
LEND
LOLA
• Each rule has been documented, together with rationale & detailed implementation approach
(Flight Procedure, Safing Check, FSW Constraint, Ops System, etc.) & thoroughly reviewed.
LR
A 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 6 0 0 0 7
B 0 1 1 3 0 4 10 0 0 1 0 0 2 0 0 2 0 2 0 26
C 0 1 0 1 0 7 4 0 1 0 0 4 7 0 0 0 4 5 0 34
D 1 1 0 2 0 8 1 0 0 0 0 2 9 0 0 0 3 4 0 31
Total: 1 3 1 6 0 19 15 0 1 1 0 7 18 0 0 8 7 11 0 98
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 75
LROC
MINI-RF
OPS
PAYLD
PDE
PROP
PWR
SYSTEM
THERM
Total

Flight Rules (1)
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
1 LRO-FR-CDH-033 CDH D C&DH Reset Counter Management
2 LRO-FR-COMM-019 COMM D Ka-Band TWTA Turn-on
3 LRO-FR-COMM-045 COMM B Hotswitching Omni/HGA
LRO Mission Flight Rules and Constraints
The C&DH Reset counter shall be reset to zero after
cause of the problem was determined and resolved.
The TWTA shall be turned on 300 seconds before AOS of
the Ka Band Pass.
RF Switch shall not be commanded while S-Band
transmitter is on. Commanding the RF switch should be
done while transmitter is off.
Spacecraft performs power cycle after 3 successive processor
resets have occurred. If the counter is not reset, on the 3rd
reset, the spacecraft will perform a power cycle.
TWTA needs 300 seconds to warm-up. The turn on sequence
should turn on the Modulator first, followed by the TWTA turn
on and warm-up
Prevent possible damage to RF components.
Ops Procedure
Ops Procedures
MPS Rules
Ops Procedure
Mission Database
Ops Procedures
4 LRO-FR-COMM-046 COMM C S-Band/Ka-Band Transmitters turn-off
S-Band and Ka-Band transmitter shall be powered off after
Prevent possible thermal and power issues.
LOS.
MPS Rules
5 LRO-FR-CRAT-034 CRAT B CRaTER High Temperature
CRaTER shall not operate when the instrument
Damage to instrument could occur.
temperature is greater than 35 degrees C for more than 60
S/C Safing
Mission Database
DLRE shall not be commanded to begin scanning or DLRE actuators do not generate sufficient torque to overcome
69 LRO-FR-DLRE-001 DLRE C DLRE Minimum Scan Temperatures
allowed to scan when either the DLRE actuator
temperature sensor is reading less than 0 C or the S/C
lubricant viscosity below 0 C. Actuator torque is also affected
Ops Procedures
by the bus voltage. Actuators may "stall" during nominal
bus voltage is less than 28 volts.
scanning which cause DLRE fault protection to safe the
6 LRO-FR-DLRE-003 DLRE D DLRE Equator Crossing Command
A equator crossing command shall be sent from the onboard
ATS before each descending node crossing.
DLRE requires this command for the internal calibration
sequencing. Current plan is to insert the commands 1 minute
before the descending node crossing predict from FDF.
Grnd System
7 LRO-FR-DLRE-004 DLRE B DLRE Minimum Power On Temperature
DLRE should not be powered on when any DLRE
temperature sensor is reading less than -20 C.
Lubrication in the actuators is not rated below -20 C and the
lubricant will not flow properly which may damage the
Instrument can be safed by sending the DLRE "safe" command
Ops Procedures
8 LRO-FR-DLRE-005 DLRE B DLRE Power-Off Safing
DLRE should be "safed" 34 seconds prior to the
instrument power-off command being sent.
or withholding the DLRE heartbeat. If power is removed before S/C Safing
instrument is "safed" then the DLRE detectors may be Ops Procedures
destroyed if instrument boresight is swept through the Sun.
9 LRO-FR-DLRE-006 DLRE D DLRE Power-On Delay
Five minutes are required for FPGA voltages to drain to a point
A minimum of 5 minutes must pass between DLRE power-
that allow proper power-up phasing. If power on occurs faster Ops Procedures
off and subsequent DLRE power-on commands.
than 5 minutes, power-on transient will increase significantly.
DLRE Shall not be allowed to scan and shall remain
10 LRO-FR-DLRE-007 DLRE B DLRE Solar Avoidance
"safed" unless:
- S/C is nadir pointing and in lunar orbit
- DLRE is completely shaded by the S/C
- DLRE representative specifically approves scanning
DLRE can not look into the Sun, if it does, DLRE detectors may On-Board Safing
be destroyed.
Ops Procedures
If any of the reaction wheels are turned off, they must Time delay is needed to ensure the "soft-start" circuitry works
11 LRO-FR-GNC-002 GNC C Reaction Wheel Turn-On
remain off for at least 3 seconds before wheels can be correctly. If the wheel is turned off & on without waiting for 3 Ops Procedures
turned on.
seconds, the wheel may not work properly.
Solar array needs to be in the indexed position to ensure the
12 LRO-FR-GNC-010 GNC B SA Position for Thruster Maneuvers
Before any thruster maneuver, the solar array must be
placed in the indexed position.
proper spacecraft CG properties and avoid any thermal,
contamination issues or gimbal mechanical constraints on the
acceleration.
Ops Procedures
13 LRO-FR-GNC-017 GNC C Deployment Command Timing
Deployment commands for both the HGA and SA shall be Issue is only valid if deployment commands are performed
spaced with 1 second interval.
using either RTS or ATS
Ops Procedure
SA Deploy RTS
15 LRO-FR-GNC-021 GNC B System Momentum Limit
Momentum dumps (Delta-H) shall be performed within 24 If momentum dump is not performed, system momentum may
hrs if the system momentum exceeds 70 Nms.
increase beyond wheel capacity.
Ops Procedures
S/C Safing
14 LRO-FR-GNC-022 GNC C GCE STOP Commanding
The ground shall send a STOP command to the GCE
before issuing the INDEX, HOME or TRACK commands
If a stop command is not issued, the GCE will not respond to
the mode change request.
Ops Procedures
16 LRO-FR-GNC-036 GNC B Sun Angle Violation
The mission shall prevent the Sun from entering the 60
degrees cone about the +Z axis.
Prevent possible damage to instruments. Some instruments
are not affected, others have doors, but in general, the
instrument should not pass or look at the Sun
S/C Safing
Grnd System
17 LRO-FR-GNC-076 GNC D KF Operations with MIMU Failure
Do not use the KF as the attitude source or the bias
source when the MIMU has failed.
Even though it is possible to choose this option in the FSW, it
has not been verified that this will produce a converged and
valid solution
Ops Procedures
STOL Procedures
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 76

Flight Rules (2)
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
18 LRO-FR-GNC-077 GNC D KF Startup
19 LRO-FR-GNC-078 GNC D ST Latency Correction with MIMU Failure
LRO Mission Flight Rules and Constraints
A single tracker must not be occulted when the KF is
enabled and the unocculted tracker must be the selected
attitude source before enabling the filter.
ST Latency correction needs to be set to 0 seconds when
the MIMU has failed
The KF needs a good known initial attitude solution to function
properly.
Star Tracker derived rates do not produce a satisfactory rate
source to produce an accurate compensation value; no
performance requirement for this configuration anyway ( Note:
star tracker derived rates can be used at anytime in place of
MIMU rates via a ground command for rate selection, but star
tracker derived rates should only be used for propagation or
STOL Procedures
Ops Procedures
20 LRO-FR-GNC-079 GNC D Delta-V Mode Entrance
Attitude Error and Rate Error needs to be below 10 deg
and 1 deg/sec before mode entrance.
when using star tracker solutions directly )
FSW rejects a Delta-V Mode command if the Attitude Error and
Grnd System
Rate Error are above the specified limits.
21 LRO-FR-GNC-080 GNC D Positive 4th Component - Quaternions
Absolute and Delta Quaternion must contain a positive 4th
FSW rejects the quaternion if the 4th component is negative.
component.
STOL Procedures
Grnd System
The table value Flag_UseTargetQuat for the High Gain The option exists to switch between using a target quaternion
22 LRO-FR-GNC-081 GNC B HGA Shall Use Target Quaternion
Antenna shall be set such that the HGA derives pointing
solutions based on the target quaternion and NOT the
and estimated quaternion, since analysis has not been
Ops Procedures
completed on the impact of using the estimate, it should not be
estimated attitude.
used.
23 LRO-FR-GNC-082 GNC D Max Slew Rate for Observing Mode
Operational planning should consider Observing Mode
slew rates up to 0.1 deg/sec, per axis
Controller design has gains set to handle rates up to this limit;
higher rates will need updates to the controller gains and
simulation verification.
Grnd System
24 LRO-FR-GNC-083 GNC D Nominal Wheel Momentum
Wheel momentum shall be less than 80 Nms. A Delta-H
maneuver is required if wheel momentum exceeds 80
Reduced torque authority can occur at momentum above 80
Nms.
Ops Procedures
25 LRO-FR-GNC-084 GNC D Disable Sun Avoidance FDC - DELETED
Separation tipoff rates can be high enough to make the Sun
If possible, should disable the Sun Avoidance FDC during
Avoidance FDC logic ineffective and may actually add time
separation.
required for acquisition
DELETED
26 LRO-FR-GNC-085 GNC C
Attitude Source Selection during Thruster
Firings
The attitude source shall be set to ŅPropagatedÓ during
Thruster Firings.
The rates induced by the thrusters could cause the trackers to
drop out of Fine Acquisition Mode and as a result cause the
controller to use erroneous data and therefore possibly cause
spacecraft instability or performance degradation
The rates induced by the thrusters could cause the trackers to
STOL Procedures
Grnd System
Ops Procedures
27 LRO-FR-GNC-086 GNC C
The IRU bias source shall be set to "Constant" during
Rate Bias Selection during Thruster Firings
thruster firings.
drop out of Fine Acquisition Mode and as a result the KF
convergence may not be valid and the KF estimated bias can
become erroneous and therefore possibly cause spacecraft
instability or performance degradation.
STOL Procedures
Grnd System
Ops Procedures
28 LRO-FR-GNC-087 GNC C
Dump System Momentum Prior to Delta-V System momentum magnitude must be below 10 N-m-s
Maneuvers
prior to a Delta-V maneuver
High system angular momentum negatively effects Delta-V
controller performance and cause larger than required out-ofplane
attitude error.
If the trackers are turned on when the CCD temperature is
Ops Procedures
32 LRO-FR-GNC-094 GNC C Star Tracker Turn On Temperature
The base plate temperature for the Star Trackers shall be
above 30°C, the TEC can behave in a undesirable manner.
less than +40° C when turning on the star trackers.
The TEC potentially will change from off to max current
repeatedly until temperatures stabilize. This behavior can
thermally stressed the CCDs.
Ops Procedures
29 LRO-FR-LAMP-023 LAMP B LAMP Bright Object Avoidance
LAMP boresight shall not be pointed within 15 degrees of
Possible thermal damage to instrument
the Sun with either the aperture door or fail safe door open
Grnd System
Ops Procedure
S/C Safing
30 LRO-FR-LAMP-024 LAMP B LAMP Excessive Count Rates
When the detector high voltage is > 2000 V, the LAMP
boresight shall not be pointed within 20 degrees of the
Sun with either the aperture door or fail safe door open
When the detector high voltage is > 2000 V and the
Possible thermal damage to instrument
Inst. Safing
S/C Safing
31 LRO-FR-LAMP-025 LAMP B LAMP Excessive Count Rates #2
aperture door or fail safe door open, no portion of the
LAMP slit as viewed through the aperture shall ever be
pointed to any sources on the LAMP Bright Star
Possible thermal damage to instrument Ops Procedure
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 77

Flight Rules (3)
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
33 LRO-FR-LAMP-026 LAMP B LAMP LVPS Configuration
34 LRO-FR-LAMP-027 LAMP D LAMP Operations after Anomaly
35 LRO-FR-LAMP-028 LAMP B LAMP Initial HV Turn-On
36 LRO-FR-LAMP-029 LAMP B LAMP General HV Turn-ON
37 LRO-FR-LAMP-030 LAMP B LAMP Latch Operation
38 LRO-FR-LAMP-031 LAMP B LAMP Aperture Door Opening
39 LRO-FR-LAMP-032 LAMP B LAMP Detector Door Opening
40 LRO-FR-LAMP-052 LAMP B LAMP Vent Valve HV Activation
41 LRO-FR-LAMP-095 LAMP C LAMP HV ramp down for thruster firings
LRO Mission Flight Rules and Constraints
From launch until LAMP is fully commissioned, power
shall be applied to only one side of the LVPS
LAMP has a state-machine timeout that with both low voltage
supplies on and the C&DH failing to operate, the state-machine
will activate the HVPS and enter into state machine mode
Ops Procedure
within 32 seconds. With only one side powered, the timeout is
18 hours. (Note: Only one LTS channel is active with only one
LVPS side operating.)
Ensure instrument team is involved with the planning and
Ops Procedure
execution of any troubleshooting and recovery.
LAMP Authorization is required to perform any instrument
operations following an anomaly where the instrument was
shut down.
LAMP Initial HV turn-on shall occur once the following
requirements are met:
(i) Spacecraft environment has reduced ambient
pressures to 24 hours of decontamination heating of the OAP
mirror and grating shall have been performed.
(v) The LAMP temperature reference point shall be
between Š5

Flight Rules (4)
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
42 LRO-FR-LAMP-096 LAMP C LAMP HV ramp up after thruster firings
LAMP High Voltage shall remain safe for at least 3 hrs
following any thruster firings.
Safe turn on requirements for LAMP High Voltage
Ops Procedures
Grnd System
43 LRO-FR-LAMP-097 LAMP C LAMP Door Closing for thruster firings
LAMP Door shall be closed and remain closed for at least
Safe instrument configuration for thruster firings
2 hours after the completion of any thruster activities.
Ops Procedures
Grnd System
50 LRO-FR-LAMP-098 LAMP C
LAMP Decon Operations after thruster
firings
After 2 hrs of thruster firings, the LAMP instrument shall
perform a 24-hr decontamination operation.
Decontaminate instrument after thruster firings
Ops Procedures
Grnd System
44 LRO-FR-LOLA -012 LOLA C LOLA Laser Operation
Laser output shall be disabled during any thruster
maneuvers or attitude slew maneuvers.
Since lasers are limited life items, prevent wasting of laser
shots when instrument may not be pointed at the Moon.
Ops Procedure
45 LRO-FR-LR-013 LR B HGA Gimbal motion at low temperature
Gimbal motion should be prohibited when the fiber optic
temperature is below -10¼ C.
Operations of the HGA gimbals below -10¼ C may cause
damage to the fiber optic cables running from the LR receiver
to the LOLA instrument.
To avoid solar array blockage and EMI issues, the solar array
S/C Safing
Ops Procedures
46 LRO-FR-MINI-RF-008 MINI-RF A Solar Array position for Mini-RF operation
Solar array shall be positioned in the Beta 90 while Mini-
RF operations are planned.
will be parked in the beta 90 position. When operating at low
beta angles, operations of Mini-RF should not affect energy
balance on the battery.
Mini-RF Power Amp and LROC Decon Heater share the same
Ops Procedure
S/C Safing
47 LRO-FR-MINI-RF-014 MINI-RF C Mini-RF and LROC Decon Heater
LROC decontamination shall be complete prior to
powering the Mini-RF instrument.
relay within the PDE box. Mini-RF operations will need to be
coordinated around LROC Decon. Heater Operations. Don't Ops Procedure
want to jeopardize LROC decontamination by flipping the relay
early in the mission.
48 LRO-FR-MINI-RF-016 MINI-RF C Mini-RF - LROC Operations
If both instruments are sending high data rate (LROC NAC and
Mini-RF shall not operate simultaneously with LROC NAC
Mini-RF high rate), the data will exceed C&DH high data rate Ops Procedures
data collection and storage activities.
ingest capabilities.
49 LRO-FR-MINI-RF-018 MINI-RF C Mini-RF Data Collections
Mini-RF shall plan operating opportunities around
available data storage capability.
When transitioning from X Band to S Band, a deactivating
LROC and Mini-RF share the same spacecraft recorder
partition. When Mini-RF operates, LROC will need to account
for the data collection from Mini-RF.
Ops Procedures
51 LRO-FR-MINI-RF-074 MINI-RF D X & S Band Transitions
the ARxEx is required otherwise no S-Band data will be
collected.
Deactivate command is required between the transition SOC Procedures
73 LRO-FR-MINI-RF-075 MINI-RF D Limit operations during high solar activity
ARxEx PNP Frequency Synthesizers are sensitive to radiation
During Mini-RF operations, instrument activities should be
induced latch-up. Operation during high solar activity should
limited during high solar activities. If operations occur,
SOC Procedures
be limited, risk of data loss may increase if latch-up occurs
concurrence is required from the Mini-RF team.
during data collections.
Mini-RF shall be powered on using the following
sequence:
55 LRO-FR-MINI-RF-088 MINI-RF C Mini-RF Turn ON/Off Sequence
1) MRF Main, 2) MRF Power Amp
Mini-RF shall be turned off using the following sequence:
Current inrush will occur if the Power Amp service is on when
the main service if off.
Ops Procedures
STOL Procedures
68 LRO-FR-OPS-009 OPS C Spacecraft Clock Adjustments
LRO Mission Flight Rules and Constraints
Spacecraft clock adjustments shall not be performed
within 10 (TBR) minutes of an LROC NAC image
command.
Clock adjustments on LRO are expected to be infrequent, but
an adjustment close to an LROC NAC image may cause timing
problems in data processing.
Ops Procedures
Operations shall schedule a Delta-H maneuver prior to If yaw maneuvers are performed without a Delta-H, the larger
52 LRO-FR-OPS-011 OPS C Delta-H prior to Yaw Maneuver
any Yaw maneuver. Yaw maneuvers are performed prior maneuver with high system momentum can cause large Ops Procedures
to each monthly SK maneuver and twice a year.
excursions away from the nominal path.
Laser Ranging shall not be performed when the spacecraft Avoid any potential issues with the LR hitting any other parts of
53 LRO-FR-OPS-020 OPS C Laser Ranging Operations
attitude does not allow a line of sight from the LR ground the orbiter. While analysis shows the laser energy can not Ops Procedures
site to the LR receiver.
damage any detectors or sensors, this is just "good practice".
54 LRO-FR-OPS-037 OPS C Monthly SK Maneuver Sequence
The entire sequence including Delta-H is estimated to take 140
The 2 SK maneuvers shall be performed with at least 1 full
minutes. This duration may cause the battery to discharge Ops Procedure
orbit in between them.
below safing limit.
70 LRO-FR-OPS-038 OPS B Command Rate Limit for Ops RTSs/ATSs
Spacecraft FSW can process up to 8 commands per second.
Operations shall limit ATS and RTS commands to no more
Limiting the ground to 5 provides margin for on-board safing
than 5 commands per second.
RTSs
Grnd System (MPS)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 79

Flight Rules (5)
LRO Mission Flight Rules and Constraints
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
71 LRO-FR-OPS-039 OPS C LROC Recorder Allocation
The MOC shall provide a daily recorder allocation based
on data downlinked and pass schedule.
Provides an allocation to LROC each day to prevent recorder
partition from filling.
Grnd System
56 LRO-FR-OPS-040 OPS D USN S-Band Telemetry Rate Limit USN S-Band telemetry rate shall not exceed 128kbps
USN link can not support any higher rates. The 128kbps link is
Grnd System
assuming HGA operations
57 LRO-FR-OPS-041 OPS D WS1 S-Band Telemetry Rate Limit WS1 S-Band telemetry rate shall not exceed 256kbps
WS1 link can not support any higher rates. The 256kbps link is
Grnd System
assuming HGA operations
58 LRO-FR-OPS-042 OPS D Daily ATS Uplink
For normal operations, the operations team will uplink an
ATS load each day.
Ensures the latest input products are used in the generation of
Ops Procedure
the ATS and provides the best possible LROC targeting
59 LRO-FR-OPS-044 OPS D Daily ephemeris Table Uplink
For normal operations, the operations team will uplink a
new spacecraft and Lunar ephemeris tables each day.
Ensures the latest products are being used by the spacecraft
FSW.
Ops Procedure
60 LRO-FR-OPS-047 OPS D Operations Requests/Inputs
All daily requests/inputs for the planning process shall
arrive by Noon (local time).
Ensure proper time in receiving and processing request for
generation/verification of daily ATS load.
Ops Procedure
61 LRO-FR-OPS-048 OPS C LOLA HK data during Laser Ranging
LOLA HK data shall be unfiltered in the S-Band link during LOLA HK data is used to monitor ground base laser
laser ranging supports.
performance and timing.
Mini-RF has a limit of accepting 10 commands per second.
Ops Procedure
Grnd System
62 LRO-FR-OPS-058 OPS D Mini-RF Real-time commanding
Operations shall limit Mini-RF commands from the ground The Stored command processor could send up to 8 commands
Ops Procedure
to 2 commands per second.
per second, so by limiting the ground to 2 per second ensures
that commands will be accepted by Mini-RF.
63 LRO-FR-OPS-059 OPS B Tracking & Ranging following separation
Tracking & Ranging shall occur within 2 hrs following
separation
Data is needed to plan for MCC which occurs at L+24 hrs Ops Procedure
64 LRO-FR-OPS-060 OPS D HGA Station Target HGA station target shall be updated prior to each AOS.
Ensures the maximum link performance and verifies that the
HGA is in position for LR operations.
Ops Procedure
65 LRO-FR-OPS-061 OPS D
Thruster maneuvers during Ground
Contact
All thruster maneuvers shall be performed during ground
contacts.
Ensure safe monitoring and assist in troubleshooting problems.
Ops Procedure
If special situations or contingencies arise, it should be noted
Grnd System
when flight rules are not being followed.
66 LRO-FR-OPS-062 OPS D Non-Routine Activities
All Non-Routine Activities shall be either monitored or
performed by the operations team.
Ensure safe monitoring and assist in troubleshooting problems. Ops Procedure
67 LRO-FR-OPS-065 OPS C Daily Table Loads
Operations shall manually perform daily table loads which
Ensure safe monitoring and assist in troubleshooting problems. Ops Procedure
includes the ATS and the two ephemeris tables.
74 LRO-FR-PROP-035 PROP B Low Pressure Latch Valves Operation
Low Pressure Latch valves will remain open throughout
the mission once commanded during the early mission.
Low Pressure Latch valves are closed at launch, once
Ops Procedure
commanded opened, the valves will remain in that state for the
Mission Database
entire mission.
72 LRO-FR-PROP-043 PROP B Thruster Catalyst Bed Operations
Each thruster catalyst bed shall be turned on at least 45
minutes prior to any thruster maneuvers.
Prevent damaging of catalyst bed and reducing thruster
performance.
Ops Procedure
75 LRO-FR-PROP-049 PROP A Propulsion System Heaters
Both sets of propulsion heaters circuits must be turned on Heater circuits are not fully redundant, both circuits are
at all times during the mission.
required to maintain propulsion temperatures.
Ops Procedures
Mission Database
76 LRO-FR-PROP-050 PROP A Propulsion system regulation
The pressurant valves shall not be opened until just prior
to LOI.
Due to full fuel load and possible temperature changes, the
tank pressure may exceed tank rating. The tank can not
exceed a 10 degree C increase in temperature.
Ops Procedure
Mission Database
77 LRO-FR-PROP-051 PROP A Pyro Valve firing
When opening the pyro latch valves, on orbit, the time
between commands shall be equal or greater than 10
seconds
Firing pyro NSI too close together has been demonstrated to
cause pyro-valve mis-fire.
Ops Procedures
78 LRO-FR-PROP-053 PROP A Insertion Thruster Configuration
When using the four insertion thrusters, all 8 attitude
thrusters should be enabled.
All 8 attitude thrusters are required to maintain pointing when
the four insertion thrusters are used.
Ops Procedure
Grnd System
79 LRO-FR-PROP-064 PROP A
High Pressure Latch Valve Initial
Operations
The high Pressure Latch Valve will be opened prior to
firing any of the propulsion pyro valve
The HPLV has not been qualified to survive a slam start in the
closed position.
Ops Procedures
80 LRO-FR-PROP-066 PROP A High Pressure Latch Valve Operations
The HPLV will be opened prior to each thruster
maneuvers and will be closed after each thruster
maneuver.
PSE switches OM3-13 and OM3-12 are jumpered
together. When turning on OM3-13, the PSE will turn on
The HPLV is to be used for long term isolation between the
high pressure tank and the low pressure propellant tanks
independent of the regulator.
Ops Procedures
Grnd System
81 LRO-FR-PWR-015 PWR D PSE Switch services for DLRE
OM3-12 (3ms delay). This causes a FDC violation since
OM3-12 was not commanded. When activating the
switches, OM3-12 should be commanded before/after the
OM3-13 command.
To avoid false FDC violation. Ops Procedure
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 80

Flight Rules (6)
LRO Mission Flight Rules and Constraints
No Rule ID System Class Title Rule/Constraint Rationale/Description Implementation
82 LRO-FR-PWR-054 PWR D Nominal Battery Discharge Limit
For nominal operations, the maximum discharge on the
battery shall not exceed 29.9V
Exceptions are required for large lunar eclipses in 2010 and
2011.
Grnd System
83 LRO-FR-PWR-055 PWR C S/C Bus Voltage
Operating components outside nominal range will impact
The operating bus voltage should be between 27-34 volts.
performance.
S/C Safing
Mission Database
84 LRO-FR-PWR-056 PWR D Nominal Bus Voltage - DELETED
During nominal operations, the nominal battery voltage
limit shall be set to 32V.
For any critical operations (such as thruster, early mission,
This will limit battery fade. DELETED
85 LRO-FR-PWR-057 PWR C Battery Voltage for Critical Operations
slews, etc), the battery voltage limit shall be set to 33.6 V Increasing the battery voltage will provide increased capacity
prior to these activities. The voltage limit shall be returned which will provide longer time in contingency scenarios.
to 32V when the activities are complete.
Ops Procedure
After a PSE reset either through ground command or After the PSE resets, the default battery voltage limit is 33.73V.
86 LRO-FR-PWR-092 PWR C Battery Voltage Set point after reset occurred during a processor reboot, the battery voltage It is not harmful, but the battery voltage should be set to either Ops Procedures
should be commanded to 33.6V.
33.6V or the nominal mission voltage set point following the
87 LRO-FR-PWR-093 PWR C Nominal Battery Voltage Set point
The nominal battery voltage set point shall be 32.5V
during nominal mission.
32.5V gives margin above the safing trigger point of 30.92V on
Ops Procedures
worst case power balance orbits.
88 LRO-FR-SYSTEM-063 SYSTEM D Cruise Nominal Attitude
During Cruise, the nominal attitude in observing mode is
inertial Sun-point
Best thermal and power configuration.
Ops Procedure
Grnd System
89 LRO-FR-SYSTEM-067 SYSTEM C Daily Off-Nadir Slews
Daily off-nadir slews shall be limited to 3 per day. Each
slew shall not exceed 20 degrees and 20 minutes.
Limit science impact on entire instrument suite. The limit of 3
Ops Procedure
per day is for the orbiter. There could be cases where request
Grnd System
come from LROC, LOLA and Mini-RF.
90 LRO-FR-SYSTEM-068 SYSTEM C Monthly calibrations
Payload monthly calibrations shall be limited to 2 orbits
per month. This covers all calibration activities for the
entire instrument suite.
Limit science impact on entire instrument suite. If conflicts
occur, project will mediate during weekly planning meetings.
Ops Procedure
91 LRO-FR-SYSTEM-069 SYSTEM C Attitude Slews
All attitude slews for instrument and spacecraft
calibrations shall be performed in eclipse.
Prevent violating any thermal or power limits.
Ops Procedure
Grnd System
92 LRO-FR-SYSTEM-070 SYSTEM C
When transition to Observing mode from Sun-Safe, a
Transitioning to Observing Mode from Sunquaternion
override sequence shall be used to place the
Safe
spacecraft in an inertial sun-pointing attitude.
Prevents any accidental sun violation Ops Procedure
93 LRO-FR-SYSTEM-071 SYSTEM C
Transitioning to inertial Sun-Point and
Nadir pointing.
When transitioning from observing mode inertial sun-point
Slew sequence will ensure no Sun Violation and allows a safe
to nadir pointing, a sequence of attitude points shall be
transition to nadir pointing.
computed.
Ops Procedure
Grnd System
During orbiter operations, instrument shall be kept out of
Ops Procedures
94 LRO-FR-SYSTEM-072 SYSTEM B Instrument Sun Avoidance
the Sun-Avoidance cone. Sun avoidance cone is defined Some instruments can be damaged if slew rate is too slow. Grnd System
as 60 degrees about the -Z axis
S/C Safing
95 LRO-FR-SYSTEM-073 SYSTEM B Orbit timing for LCROSS impact
The LRO team shall synchronize the mission orbit so the
orbiter just passes the impact zone for LCROSS.
For maneuver events, the thruster bank shall be selected
By synchronizing the orbit, this will allow maximum time for the
particles to settle before LRO crosses the impact site on the Ops Procedures
next orbit.
96 LRO-FR-SYSTEM-089 SYSTEM D Thruster thru-put limit
based on total accumulated on-time. The bank with the The maneuver team will track thru-put on each bank. Purpose
Ops Procedures
least thru-put time will be used. This rule applies to when is to distribute thruster on-time throughout the mission.
just one bank is used.
The nominal/default current settings for the SA gimbals
97 LRO-FR-SYSTEM-090 SYSTEM D
Nominal Current Settings for SA Gimbal
Motors
shall be:
80% for Gimbal Y
55% for Gimbal Z
The nominal/default current settings for the HGA gimbals
Minimum level to lower power but maintain enough control
torque.
STOL Procedures
98 LRO-FR-SYSTEM-091 SYSTEM D
Nominal Current Settings for HGA Gimbal
Motors
shall be:
60% for Gimbal Y
60% for Gimbal Z
Minimum level to lower power but maintain enough control
torque.
STOL Procedures
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 81

MGS Failure Report
• Reviewed “Report on the Loss of the Mars Global Surveyor” – June 2007
• Recommendations are divided into six distinct categories:
– Memory Loads & FSW Memory Load Process (4 items)
– Spacecraft Test Bed (3 items)
– Spacecraft and Mission Design (6 items)
– Extended Mission (3 items)
– Training (2 items)
– Response to Anomaly (4 items)
• Incorporated recommendations into operations plans. Found two in which
LRO doesn’t fully comply:
R5.2.2-2
R5.2.4-6
Predefined commands should be used in preference to
general memory loads
Key data should be captured and returned autonomously
to the ground at the next scheduled downlink
Due to the nature of LRO flight file system, the preferred method for any updates
are table or file loads. However, we have implemented a one-time, canned
memory poke, at startup, to patch the FSW Heater Control Task.
For faults where the ATS remains executing, events will be dumped automatically
on the next scheduled support. For faults that stop the execution of the ATS (i.e.
processor resets), ground commands are required to establish communication.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 82

MGS Failure Report Recommendations (1)
Memory Loads and FSW Load Process
Rec. Title Compliance
R5.2.1-1
R5.2.2-1
R5.2.2-2
R5.2.2-3
Spacecraft Test Bed
Rec.
R5.2.3-1
R5.2.3-2
R5.2.3-3
Ground alarm limits should be set equal to or within
expected flight SW and HW performance limits
Projects should be required to conduct, prior to upload, a
thorough review of all proposed flight software patches,
non-routine parameter and data/table modifications and
any change affecting fault protection or contingency mode.
Predefined commands should be used in preference to
general memory loads
When parameters modification is absolutely necessary and
no spacecraft command is available, the process should be
supported with “user friendly” data manipulation tools that
mitigate the risk of human error.
Title
FSW Configuration Management
Ability to perform functional and performance testing
related to in-flight operational issues.
Develop and maintain tools to automatically load system
testbeds with memory readouts.
Database sets limits within expected performance. Reviewed limits during I&T
testing and prior to launch. Review included operations, systems and applicable
subsystem leads.
Any change to flight configuration requires review and approval of the change and
implementing procedures by the project. All changes will be verified on FlatSat
prior to upload.
Due to the nature of LRO flight file system, the preferred method for any updates
are table or file loads. However, we have implemented a one-time, canned
memory poke, at startup, to patch the FSW Heater Control Task.
Updates are applied by loading files. File uploads follow the standard CFDP
process. Files are loaded to RAM and are never written to EEPROM directly from
the ground.
Compliance
FSW Sustaining Engineering team maintains the ground reference image. A well
defined FSW configuration management process exists. In addition, the MOC will
utilize a memory model that logs all file uplinks and maintains the current file
details on-board the spacecraft.
LRO will have two high fidelity platforms for ops. The first is flatsat which will be
located near the MOC for operations and FSWM activities. The FSW sustaining
engineering team will also utilize the current FSW development test bed.
As part of Flatsat startup procedures, current version of the FSW and updated file
checks will be performed to ensure they match the current on-orbit configuration.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 83

Spacecraft and Mission Design
MGS Failure Report Recommendations (2)
Rec. Title Compliance
R5.2.4-1 Safe modes shall be design to provide thermal safety
R5.2.4-2
R5.2.4-3
R5.2.4-4
Waiver approval processes should include identification of
any required operational contingency procedures
Equipment that can overheat due to internal or external
causes should always be monitored.
LRO Sun-Safe mode is design to roll about the Sun-line to provide the best
thermal conditions.
All contingency operations will be documented on the activity change request form
which will contain all procedures and activities which are approved by the project.
Current safing specification contains several key temperature monitors which will
take appropriate action to reduce/eliminate potential damage from excessive heat.
R5.2.4-5 Provide autonomous protection against battery anomalies Current safing specification contains battery protection.
R5.2.4-6
Extended Mission
Rec.
R5.2.5-1
R5.2.5-2
R5.2.6-1
Operation at an allowable hardware limit should not be
interrupted by autonomous Fault Protection as a fault.
Key data should be captured and returned autonomously
to the ground at the next scheduled downlink
Title
Extended mission should be formally and independently
reviewed across the board.
Operational processes need to be routinely updated
For extended mission, project should identify the risks and
operational process changes that are required.
Current safing implementation should not detect faults when hardware is operated
near limits. Verified as part of the safing functional.
For faults where the ATS remains executing, events will be dumped automatically
on the next scheduled support. For faults that stop the execution of the ATS (i.e.
processor resets), ground commands are required to establish communication.
Compliance
Extended mission will not be fully defined until midway through the nominal
mission, but it will be thoroughly reviewed by all interested parties.
LRO will maintain all training & operational documentation throughout the mission.
When extended mission objectives and goals are identified, the plan is to assess
objectives against current on-orbit processes and procedures. A list of changes
will be developed and addressed as part of the extended mission review.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 84

Training
MGS Failure Report Recommendations (3)
Rec. Title Compliance
R5.2.7-1
R5.2.7-2
Anomaly Response
Rec.
R5.2.8-1
R5.2.8-2
R5.2.8-3
R5.2.8-4
Systematic training methodology should be applied to all
support disciplines.
Training process should teach that there are discrete
points in the operational procedures when the engineer
should stop and have another member check.
Title
Ground operations should have in place a procedure to
quickly acquire stored telemetry
Special loads should have prepared/approved back out
commands ready to radiate
Prepare plans to utilize RF open loop receiver recording for
trouble shooting anomalies
When sending recovery commands to the spacecraft
whose orientation or state is unknown, transmit commands
multiple times and resweep the uplink prior to redundant
transmission.
The ops team will follow the plans and guidelines outlined in the MOT training and
certification plan. For subsystem/system engineers during nominal or extended
mission GS&O will provide refresher training to system/subsystem personnel prior
to critical events such as Delta-H, Delta-V maneuvers, spacecraft calibrations, etc.
The refresher training will focus on operations procedures/processes as well as
refresher on using operational tools within the MOC.
Will be incorporated into the current Operational training plan. All command
procedures and flight procedures will identify and ask the engineer to receive
approval or check before proceeding.
Compliance
Contingency/flight procedures will be identified and developed for each
contingency that includes retrieving necessary data to aid in the investigation.
All special loads will identify sequence of activities that will remove the load and
return the orbiter to the previous state.
As part of any contingency scenario where loss of comm or troubleshooting
potential comm problems, the plans will incorporate detailed receiver data from
the ground network. Current plas is for the stations to forward receiver data in
real-time to the MOC, the MOC plans to archive, and maintain, the data in the
MOC trending data system.
LRO plans to incorporate recommendation into recovery procedures.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 85

Ground Systems and Operations Overview
LRO Flight Operations Review – Section 4.0
NASA’s Goddard Space Flight Center
Rick Saylor
Deputy Mission System Engineer

GS&O Overview
• Space Communications Network (SCN)
– Global S-Band coverage for Tracking, Telemetry and Commanding
USN, WS1, and DSN networks
SN network provides post separation coverage only
– Ka-Band service for high rate data dumps
WS1 is operational, supports all LRO data rates
– Laser ranging support
Greenbelt Laser Ranging Station provides 1-way laser tracking
• Mission Operations Center
– Support mission operation functions
Telemetry & Commanding, Mission Planning, Attitude Planning & Products, and offline
engineering analysis
– Store all data for the life of the mission
• Flight Dynamics Facility
– Provides Orbit Determination, Maneuver Planning and product generation
• NASA Integrated Service Network (NISN)
– Provides voice and data interfaces between ground elements
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 87

LRO GS&O System Architecture
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 88

GS&O Review History
• GS&O Reviews
– Requirements Peer Review January 11, 2006
33 RFAs Received – All Closed
– Design Peer Review July 17, 2006
10 RFAs Received – All Closed
– Ground Segment Single Design Review January 17-18, 2007
30 RFAs Received – All Closed
– Ground Segment Mission Operations Review September 18-19, 2007
14 RFAs Received – All Closed
• Project Reviews
– Mission System Requirements Review August 16-18, 2005
– Mission Preliminary Design Review February 7-9, 2006
– Mission Critical Design Review November 6-9, 2006
– Mission Pre-Environmental Review July 21-22, 2008
– Mission Pre-Ship Review February 9-10, 2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 89

• Requirements
GS&O Requirements Summary
– At MOR, had 635 requirements
– At FOR, have 636 requirements
Added 11 new requirements
– 10 new requirements were for additional GS products
– 1 new requirement identifying idle pattern for SN
Deleted 10 requirements
– Ground System Requirements Document (431-RQMT-000048) Revision E is final baseline
version
• Three Requirement Waivers on baseline requirements document
– DMR-624: The LR Ground System (GS) interface with the LR Flight System shall comply with
the LRO LR Flight System to Laser Ground System ICD (431-ICD-000596)
Waiver was submitted change document reference to the GS ICD
– DMR-678: The DMS shall provide the ability to read orbiter file listings and compare them with
ground generated file listings to determine whether files are being created onboard the orbiter.
Waiver was submitted, function is being performed by the LROC SOC
– DMR-644:Maneuver Notification -- Flight Dynamics Maneuver Team shall send the maneuver
plan for momentum management unload to the Attitude Ground System (AGS), as defined in the
Lunar Reconnaissance Orbiter Ground System External Interface Control Document (431-ICD-
000049).
Waiver was submitted, using the OAR process to capture required information
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 90

GS Accomplishments Since MOR
• White Sands – WS1 Ground Station is operational
– Tracking data was certified by Flight Dynamics
– Currently providing operational supports
• Universal Space Network
– Completed tracking data certification for all ground stations support LRO
• All Ground Networks (DSN, SN, USN, and WS1) performed RF Compatibility
testing with the LRO Orbiter
• Integration of the MOC facility and hardware is complete
• Backup MOC facility is complete and verified through MRT testing
• Performed over 400 hundred hours of mission simulations and rehearsal testing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 91

WS1 Ground Station
WS1 antenna
WS1 Monitor and Control Subsystem (MCS)
WS1 Station Equipment Racks
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 92

LRO Mission Operations Facilities
Mission Operations Center
Launch Support Room
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 93

Key Documentation Status
Document Description/Purpose Current Status
GS&O System Implementation Plan (SIP) Captures WBS, cost plan, and major milestones. Released – Rev A
GS&O Product Development Plan Approach to implementing and testing the overall ground
system
Released – Rev A
Mission Concept of Operations Operations approach and scenarios for the mission. Released – Rev -
Detailed Mission Requirements Level 3 requirements for the ground system, traces to the
MRD
Mission Readiness Test Plan Approach to planning and coordinating the ground
readiness and end-to-end tests
RF Interface Control Document Defines communication links between LRO and the different
networks (DSN, USN, SN, and WS1)
GS&O External ICD Defines products and interfaces between Ground Segment
Elements
Project Service Level Agreements (PSLA) Describes space communications and data system
requirements
Released – Rev E
Released – Rev -
Released – Rev 1
Released – Rev C
Released – Rev A
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 94

Key Documentation Status (2)
Document Description/Purpose Current Status
LRO Telemetry & Command Formats
Handbook
Defines CCSDS implementation for LRO Released – Rev B
LRO Launch & Early Mission Handbook Defines early mission timeline, procedures and
operations processes for through commissioning
LRO Operations Contingency Flight
Procedures
Contains flow charts and detail procedures for possible
on-orbit and ground contingencies
CFDP Implementation Specification Defines the implementation approach for both ground
and flight CFDP.
LRO Mission Operations Center Design
Document
Describes detailed design implementation and
concepts for the MOC.
GS&O MOC Internal ICD Defines products and interfaces between MOC
components
SOC Operations Agreements
CRaTER SOC
DLRE SOC
LAMP SOC
LEND SOC
LOLA SOC
LROC SOC
Mini-RF POC
Revision -
In Signature Cycle
Revision -
In CCR Review
Released – Rev B
Released – Rev A
Released – Rev C
Capture operations agreements between the
operations team and SOC elements CRaTER - Released
DLRE - Released
LAMP –Review Complete
LEND – Released
LOLA – In Review
LROC – In Signature
Mini-RF – Review Complete
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 95

Key Documentation Status (3)
Document Description/Purpose Current Status
LRO Spacecraft Operations Description
Manual
Describes spacecraft subsystems and provides
information relevant to operations.
LRO Mission Operations Plan Describes details of flight operations activities and
ground system operations
LRO Launch & Early Mission Handbook Defines early mission timeline, procedures, and
operations planning processes from launch through
commissioning
LRO Operations Trending Plan Describes processes and tools used by the MOT to
perform data trending
Mission Flight Rules and Constraints
Document
Provides single reference for all of LRO’s flight rules
and constraints
GS&O Configuration Management Plan Provides configuration management procedures for
flight operations. Identifies products that are controlled
by the procedures within the plan.
Released – Rev 3
Released – Rev A
Released , Rev -
Released, Rev -
Released – Rev A
Released – Rev -
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 96

Ground System Freeze Plan
• Operations and Ground System Freeze Plan Developed
– Includes MOC Software and Operations Products, LRO interfaces to
external elements that are multi-mission
– Configuration is frozen at L-60 days, March 22, 2009
• Process established to review and approve post-freeze change
– Captured in the Operations Configuration Management Plan
Waiver is generated capturing rationale and impacts (both with or without the
change)
Waivers are reviewed and approved
– Project Management
– GS&O Lead
– GS&O System Engineering
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 97

Ground System Element Summaries
LRO Flight Operations Review – Section 4.1
NASA’s Goddard Space Flight Center
Mike Kohout
LRO Mission Commitment Engineer

Space Communications Network (SCN)
Overview
DSN 34-Meter S-Band
Goldstone, California
USN 13-Meter S-Band
South Point, Hawaii
WS1 – Prime S/Ka GS
USN Ground Stations
DSN Ground Stations
Laser Ranging
WS1 - 18-Meter S/Ka-Band
WSC, New Mexico
DLR 15-Meter S-Band
Weilheim, Germany
LR – Laser Ranging
Greenbelt, Maryland
DSN 34-Meter S-Band
Madrid, Spain
SSC 13-Meter S-Band
Kiruna, Sweden
USN 13-Meter S-Band
Dongara, Australia
DSN 34-Meter S-Band
Canberra, Australia
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 99

Networks Documentation & Reviews
• Networks Loading & Analysis NEN Feasibility Assessment for LRO Project Nominal Ops
– Assessed the ability of the Near Earth Network (NEN) to provide telecommunication services to
the Lunar Reconnaissance Orbiter (LRO) Project for their nominal operations phase
– Completed on January 8, 2009. Reviewed and accepted by the project.
• Networks Loading & Analysis Feasibility Assessment for LRO Project LEOP
– Assessed the ability of the Space Network (SN), Near Earth Network (NEN) including their
Commercial Service Providers (CSPs), and Deep Space Network (DSN) to provide
telecommunication services to the Lunar Reconnaissance Orbiter (LRO) Project for their
Launch and Early Operations Phase (LEOP) through lunar orbit insertion
– Completed on February 11, 2009. Reviewed and accepted by the project.
• LRO Project Service Level Agreement (PSLA), DCN#2 February 24, 2009
– DCN pending for PSLA to add a 8 kbps downlink rate for the DSN.
• LRO Networks Requirements Document (NRD), DCN#2 February 24, 2009
– DCN pending for NRD to add a 8 kbps downlink rate for the DSN.
• LRO Radio Frequency Interface Control Document, Rev. 1 February 25, 2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 100

Networks Documentation & Reviews
• LRO Network Test Plan (NTP) February 13, 2008
• LRO Network Operations Support Plan (NOSP) March 3, 2009
• LRO Network Operations Plan (NOP), DSN February 12, 2009
• Launch Schedule Request April 27, 2009
• Interim Support Instructions (issued by the NOM)
– ISI 001 - Mission Status May 11, 2009
– ISI 002 – Launch Count May 14, 2009
– ISI 003 – SN/NEN Requirements May 14, 2009
– Launch Briefing Message May 18, 2009
– ISI 004 – Hardware/Software Freeze May 18, 2009
• Mission Event Readiness Review, DSN April 7, 2009
• ELV Mission Operations Readiness Review (MORR) April 9, 2009
• Payload Mission Operations Readiness Review (MORR) April 9, 2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 101

Space Network Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 102

SN Support Summary
• The SN shall provide S-band Single Access (SSA) return services (GN
mode) 2 kbps, Bi-phase Shift Keyed (BPSK) modulation. The SN shall
provide SSA forward services (GN Mode), 4 kbps, 16-kHz subcarrier,
BPSK/PM modulation. Services will be limited to the LEOP (from L to
~L+120 minutes).
• Initial acquisition (scheduled to occur between ~L+30 minutes to ~L+90
minutes, during the Early Cruise Phase) is when the Trans-Lunar Injection
(TLI) burn will occur, which is considered a mission time critical activity.
• LRO will transition to the NEN or DSN as soon as a view period permits.
When the LRO is within view of a selected ground station, the SN will be
utilized as a backup.
• Documented in the 450 PSLA and NRD.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 103

SN Tests to Date
• WDISC Interface Test
– Conducted 01/25/2008
– Successfully connected to the LRO MOC and flowed S-Band telemetry.
• SN RF Compatibility Test
– Conducted 02/13 to 02/15/2008
• LRO Mission Readiness Testing
– SN participated in MRT #4.a on 02/25/2008
– Successfully completed
• Will participate in ORT testing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 104

USN Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 105

S-Band Network via USN
• The NEN shall provide an S-band Network comprised of stations selected
by the project to support the mission:
– Dongara, Australia
– Kiruna, Sweden
– Weilheim, Germany
– South Point, Hawaii
• For nominal operations, all stations shall provide S-band services including
Tracking (Doppler and Ranging), Telemetry receipt at various S-band data
rates, and Command (TT&C). The S-band ground station shall be capable
of demodulating the S-band signal; and decoding, recovering, and storing
telemetry data.
• Via the S-Band stations (and WS1), the NEN shall provide a minimum of 30
minutes of tracking data per orbit.
• Documented in the 450 PSLA and NRD.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 106

USN Overview
• Four Ground Stations in the LRO S-Band
Network
– Dongara, 13 Meter
– South Point, 13 Meter
– Kiruna, 13 Meter
– Weilheim, 15 Meter
Dongara
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 107
Kiruna
Weilheim South Point

S-Band Network Tests to Date
• USN/FDF Tracking Certification
– Conducted from March 2008 to July 2008
– Doppler Certification achieved on 07/25/2008
– Ranging Certification achieved on 07/25/2008
• USN RF Compatibility Test
– Conducted 03/05/2008
– 2nd test conducted 01/15/09
Command Receiver Phase Modulation Sensitivity - verified that this parameter meets
the expected performance.
High Rate Telemetry - verified the high rate telemetry modification to the COTEX
Telemetry unit works correctly with the LRO spacecraft
• LRO Mission Readiness Testing
– LRO MRT 4.c 02/11/08
– LRO MRT 6.a 06/05/2008
– LRO MRT 6.c 06/13/2008
– LRO BMOC Test 1/15/09
• Will participate in ORT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 108

DSN Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 109

DSN Support Summary
• The DSN shall provide LEOP support, most notably for two mission time
critical activities - the MCC Burn (scheduled at approximately L+24 hours
during the Mid Cruise Phase) and the first Lunar Capture Burn (scheduled
between L+4 days and L+5 days during the Lunar Orbit Insertion Phase).
Due to their critically, the DSN shall provide a prime and backup antenna for
these supports.
• For nominal operations, the DSN shall support monthly station keeping
maneuvers. For the life of the mission, the DSN shall serve as a provider
for emergency, and contingency support.
• The DSN shall provide services including Tracking (Doppler and Ranging),
Telemetry receipt via the full range of S-band data rates, and Command
(TT&C).
• Documented in the 450 PSLA and NRD.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 110

Deep Space Network Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 111

Deep Space Network Tests to Date
• DSN RF Compatibility Test
• Conducted 04/21/08 to 04/26/2008
• Successfully completed, confirming RF compatibility with DSN
• Recertification at KSC/MIL-71 complete as of 3/3/09
• DSN Mission Service Training Activities (MSTA)
• DSN MSTA completed for LRO S-Band TTC Support
• DSN MSTA conducted 05/06/08 – 08/05/08
• DSN LRO Mission Interface Testing
• Conducted 06/11/2008 – 11/04/2008
• DSN Interface Test (Offline Test)
• Conducted 02/01/2009
• DSN Interface Test (End to End Data Flow)
• Conducted 02/05/2009
• Will participate in ORT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 112

WS1 Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 113

White Sands 1 (WS1) Development Process
• SRR/PDR 11 January 2006
• CDR 8 & 9 June 2006
• WS1 Reflector Arrival at WSC 9 March 2007
• WS1 Pedestal Shipment to WSC 22 June 2007
• WS1 Reflector Lift 29 June 2007
• WS1 rack shipment to WSC 11 July 2007
• WS1 Antenna Available for initial testing 29 October 2007
• WS1 Antenna Vendor Site Acceptance Test 23 February 2008
• NENS WS1 Acceptance Testing (inc. FDF Val. Test) 5 March 2008
• WS1 Test Results Review (TRR)/ORR 27 March 2008
• FDF Certification Passes 10 October 2008
• WS1 Delta ORR 15 December 2008
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 114

WS1 2KW HPA Installation
• The original WS1 2KW transmitters provided by General Dynamics (GD) had
repeated failures despite GD’s numerous attempts to correct the problems.
– NASA elected to install 300 Watt Solid State amplifiers to mitigate the risk to the
LRO mission
– The 300 Watt amplifiers provide the needed power for nominal mission activities
but do not have enough power for LRO contingency scenarios
– DSN provides LRO contingency support
• GD proposed the unreliable transmitters be replaced with systems
manufactured by Communications and Power Industries (CPI)
– The CPI systems are very similar to the SN klystrons in Guam and Australia
– L3-Datron, HTSI, and NASA accepted the GD proposal
• Installation of the 2KW transmitters does not change the existing 300 Watt
transmitter configuration
• Because the new transmitters are in addition to the existing transmitters
rather than replacing them, there is very little risk to this approach
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 115

WS1 2KW HPA Installation (cont.)
• The WS1 2KW Klystron HPA transmitters will be installed prior to the LRO
launch
– Ample Schedule available
– Low/No Installation Risk to LRO
– Provides increased contingency capability for LRO and other missions
• WS1 2KW Klystron HPA Transmitter Installation Schedule
– Factory Acceptance Test March 12
– Pack and ship to White Sands March 13 – 20
– Installation, Test, and Training March 23 – April 3
– NEN Freeze May 6
– LRO Launch May 20 (No Earlier Than)
– Installation and test complete 33 days prior to planned network freeze, 40 days
prior to earliest potential launch date
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 116

WS1 Key Performance Parameters
# Parameter Requirement
1 G/T Ka-band ≥ 45 dB/K 47 dB/K
2 G/T S-band ≥ 27 dB/K 29.1 dB/K
Expected
Performance
3 Implementation Loss Ka-band ≤ 2 dB 1.75 - 1.95 dB
4 Implementation Loss S-band ≤ 2 dB 1.35 - 1.55 dB
5 Doppler Measurement Error < 1 mm/sec < 0.2 mm/sec
6
One Way Range Measurement
Error
< 10 m (1 sigma) < 2 m (1 sigma)
Comment
Clear sky, 10 degrees Elev.,
25.5 GHz
Clear sky, 5 degrees Elev. RF ICD
assumes 26.6 dB/K with lunar
effects at 5 degrees Elev
1.5 dB allocated to HDR, 0.35 to
antenna, 0.15 dB reserve
FDF-30-025 White Sands 1
Tracking Data Certification for
Lunar Reconnaissance Orbiter
FDF-30-025 White Sands 1
Tracking Data Certification for
Lunar Reconnaissance Orbiter
7 EIRP >72 dBW >72 dBW
8 Command Timestamp Error ≤ 1 ms ≤ 10 μs
9 Ka-band Downlink Frequency 25.5 - 27.0 GHz 25.5 - 27.0 GHz LRO uses 25.65 GHz
10 S-band Downlink Frequency 2200 - 2300 MHz 2200 - 2300 MHz
11 S-band Uplink Frequency 2025 - 2120 MHz 2025 - 2120 MHz
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 117

SDO#2
WS1
White Sands S/Ka Station
• SDO #2 and WS1 antennas at STGT pointing toward the Blue Mesa
Collimation tower.
• An agreement has been established to use SDO#2 for contingency support
in the event of an extended Ka-band outage
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 118

WS1 Requirements
• The NEN shall provide the LRO project with a newly constructed ground
station (designated as WS1) at the White Sands Complex (WSC), capable
of S/Ka-band support.
• WS1 shall provide services including Tracking (Doppler and Ranging),
Telemetry receipt at various S/Ka-band data rates and Command.
• Nominally, all measurement (science) data will be collected solely via Kaband
downlink to WS1. Simultaneously, WS1 will provide S-band services.
WS1 shall be capable of demodulating the S- and Ka-band signal; and
decoding, recovering, and storing telemetry data.
• For its nominal mission, LRO shall be given top priority for use of WS1. All
available Ka-band view periods exceeding 10 minutes shall be scheduled.
WS1 with the S-Band Network stations provides global S-band coverage for
the LRO, providing a minimum of 30 minutes of tracking data per orbit.
• Documented in the 450 PSLA and NRD.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 119

WS1 Tests to Date
• WS1 Acceptance Test
• Conducted from February 2008 to April 2008
• WS1 was transferred to NEN control December 2008.
• WS1/FDF Tracking Certification
• Conducted from January 2008 to October 2008
• Doppler Certification achieved on 10/10/2008
• Ranging Certification achieved on 03/15/2008
• WS1 RF Compatibility Test
• Conducted 04/27 to 05/02/2008
• Successfully completed.
• LRO Mission Readiness Testing
• LRO MRT 4.c 02/11/08
• LRO MRT 5.d 02/21/2008
• LRO MRT 6.a 06/05/2008
• LRO MRT 6.c 06/13/2008
• LRO BMOC Test 1/15/09
• LRO MRT 6.b and 6.d retest 2/11/09
• Will participate in ORT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 120

Space Communications Network
Networks Scheduling – SN, GN, and DSN
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 121

Networks Scheduling Support Summary
• The GN Scheduling Office (GNSO) shall perform generic scheduling for the
LRO mission, producing schedules that will include all LRO supports
regardless of the station (USN, DSN, or WS1).
• The LRO Networks Operations Manager (NOM) shall provide SN
scheduling support for all pre-mission testing and the LEOP via the SN Web
Services Interface (SWSI) in the NIC.
• WS1 shall schedule preventive maintenance on the antenna system during
non-LRO view windows. Maintenance will be scheduled and communicated
to the operations team at least 28 days in advance.
• Documented in the 450 PSLA and NRD.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 122

Networks Scheduling Tests to Date
• WOTIS/WS1/FDF Engineering Interface Test
– Conducted on 01/29/2008
• LRO Mission Readiness Testing (MRT 4.e)
– 1 st Test Conducted on 10/03/2008
– 2 nd Test Conducted on 01/06/2009
– 3 rd Test Conducted on 02/09/2009
• Representative Schedule Test
– Conducted on 02/24/2009
– Generated a one week schedule for the NEN (WS1 and S-Band Network) based
on LRO coverage/scheduling requirements (established in the Project DMR and
450 NRD).
• Generating station schedules for ORT Testing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 123

Ground System Laser Ranging Overview
LRO Flight Operations Review – Section 4.2
NASA’s Goddard Space Flight Center
Jan McGarry
Laser Ranging Ground Lead

Laser Ranging Overview
• Laser Ranging Driving Requirements Summary
– Provide relative range measurements between the Earth and the LRO spacecraft
when the spacecraft is in view of the Earth station, at better than 10cm
precision, at 1/sec measurement rate, with 407 hours over the course of 12 months.
The LR Ground System shall deliver a signal with power of between 1 and 10fJ per
square centimeter to the receiver aperture.
The LR Ground System shall measure the relative laser time of fire to better than 200
psec (1 sigma) shot-to-shot over a 10 sec period.
The LR Ground System shall maintain the transmitted pulse time stamp accuracy to
within 100 ns of UTC.
– Conform to NASA and FAA laser safety regulations and procedures.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 125

Laser Ranging
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 126

Primary Laser Ranging Ground System:
NGSLR
• Status
– Software and hardware are ready for LR operations.
– Operations Plan is being written. Will be completed by March 31st .
– Operators are in training. Training will be completed by April 30th .
– There will be two full-time dedicated operators and 2 backup operators. In
addition the engineering development team will provide operational backup and
additional coverage.
• Testing performed
– Multiple in-house tests to verify pointing, timing, and feedback were successfully
passed and documented.
– One-way system delay measurement was successfully completed 2/9/2009 and
is being documented.
– Independent timing verification with Instrument Scientist was successfully
completed 1/2/2009 and documented.
– End to end tests (8/20/2008, 8/26/2008, 1/21/2009) were successfully performed.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 127

Primary Laser Ranging Ground System:
NGSLR (cont)
• Testing still to be performed
– Independent verification by LOLA Science Team that fire times will hit LOLA
Earth Window is in progress. Data taken – analysis will be complete by March
27th . This test is not critical to mission success - will just take longer to search
for LOLA Earth Window.
• Remaining issues
– Still some question on the SCLK offset (between spacecraft UT and MET). In
End to End testing it was correct on Aug 26th and not correct on Jan 21st . We
believe we understand why it was wrong – plan to retest this at Cape on March
14th . This is not a critical issue for LR – can search for LOLA Earth Window.
• NGSLR station by itself is sufficient to meet LR requirements. Global LR
partners will further enhance and broaden the LR coverage. Currently have
4 other stations around the world that will participate.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 128

• Status
Laser Ranging Scheduling and Data Flow
– Software for LR schedule generation is ready and tested.
– Data flow from NGSLR to CDDIS is ready and tested.
– Real-time LOLA House-Keeping website display is ready and tested.
– Go/No-Go flag has been successfully tested at NGSLR.
• Testing performed
– End to End tests (8/20/2008, 8/26/2008, 1/21/2009) successfully tested data flow
and website of real-time LOLA HK data. Multiple computers at NGSLR and
LOLA SOC were able to bring up the website at the same time.
• Remaining issues
– None.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 129

Information Technology Security
LRO Flight Operations Review – Section 5.0
NASA’s Goddard Space Flight Center
Jim Clapsadle
Deputy Ground System & Operations Lead
Information System Security Official

Agenda
• Security Organizational Hierarchy
• Responsibilities of the LRO Information System Security Official (ISSO) for
IT Security
• Project Element Status
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 131

Security Organization Hierarchy
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 132

Responsibilities of the LRO ISSO for IT
Security
• ISSO responsibilities can be found in NPR 2810.1A, paragraph 2.3.5.
• The LRO Project’s representative who coordinates with the project
Computer Security Officer (CSO) to interface with the Center IT Security
Manager
• Manages the security of the LRO Ground Segment and IT Security
resources (including off-site and remote locations)
• Reviews and assesses impacts and security infrastructure of networks and
systems outside of the LRO MOC to determine impacts to operations
• Identifies and maintains a list of security points of contact and system
administrators within the LRO ground segment and communicates all
appropriate IT security information
• Implements a risk management and security planning process for the LRO
systems and networks
• Implements a process for providing contingency planning and reasonable
continuity of operations for the LRO systems, networks, and applications
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 133

Project Element Status
Project Element Status
Mission
Operations
• Data Categorization Complete – Classification Moderate
• Under Code 400 Master Plan, Flight Projects Moderate Explorations Systems EX-007-M-GSF-
4320 – Complete 4/30/07
• Risk Assessment/Plan (451-PLAN-000877) – Complete 3/30/07
• Security Plan Revision A (451-PLAN-000229) – Complete 5/30/07
• IONet Checklist – Complete 3/30/07
• Contingency Draft (451-PLAN-000230) – Completed 4/3/07
• IONet Audit – Complete 5/3/07
• IONet Connection – Authorization received 5/17/07
New from MOR
• Certification and Accreditation achieved 9/30/2007
FDF • Data Categorization Complete – Classification High Mission Essential Infrastructure
• Under Master Plan, Space Operations SO-004-H-GSF-5005 – Completed 7/29/07
New from MOR
• Certification and Accreditation achieved 9/30/2007
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 134

Project Element Status
Project Element Status
SCN-WS1 • Data Categorization Complete – Classification Moderate
• Under Code 400 Master Plan, Flight Projects Moderate Explorations Systems EX-007-M-GSF-
4320 – Complete 4/30/07
New from MOR
• Certification and Accreditation achieved 9/30/2007
• Certification of System Administrators – Complete
SCN-SN • Data Categorization Complete – Classification High Mission Essential Infrastructure
• Under Code 400 Master Plan: SO-001-H-GSF-4012, Space Network Mission Essential
Infrastructure (MEI) system
New from MOR
• Certification and Accreditation achieved 9/30/2007
SCN-DSN • IONet Connection – Existing
• New from MOR
• Security Documentation (D-7155, Rev. 10 DocID# 36852) – Revalidated 4/24/2008
• JPL is currently working towards FISMA compliance
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 135

Project Element Status
Project Element Status
SCN-USN • Data Categorization Complete – Classification Low
• Under Code 400 Master Plan, SO-003-L-GSF-4005 Flight Projects Space Operations Systems
SCN-Laser
Ranging
Science
Operations
• No requirement for Independent Certification and Accreditation completed self assessment
5/29/07
• Data Categorization Complete – Classification Low
• Under Code 600 Security Documentation : CD-014-L-GSF-6004, Sciences and Exploration
Directorate Multi-Program/Project IT Science Systems - Completed 11/30/06
• Completed self assessment 5/1/07 and accredited by CAO 7/19/07
• Data Categorization Complete – Classification Low
• Risk Assessments, Security Plans, and Contingency Plans completed and signed by for all
SOCs
• All documentation reviewed by LRO ISSO
• Note: The LOLA SOC & LEND SOC presence at GSFC is covered under Code 600 Security
Documentation: CD-014-L-GSF-6004, Sciences and Exploration Directorate Multi-
Program/Project IT Science Systems - Completed 11/30/06
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 136

Summary
• All LRO MOC IT security controls (administrative and technical) have been
completed and tested
• All systems are at a working CIS baseline, patching, testing and internal
scanning policies are in effect
• Patchlink has been installed on all systems
• Firewall rules in place and verified
• All quarterly IONet scans have been successful
• Personnel Screening done via HSPD-12 NACI process and is complete
• Command Authentication in place for uplink
• Re-certification and Accreditation planned for August 2010
We are secured for launch!
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 137

Mission Operations Center Readiness
LRO Flight Operations Review – Section 6.1
NASA’s Goddard Space Flight Center
Jim Clapsadle
Deputy Ground System & Operations Lead
Information System Security Official

MOC Overview
• The Mission Operations center contains the systems, personnel and
products necessary to control the LRO mission
– Orbiter commanding
– Orbiter telemetry health and safety monitoring
– Mission Planning and Scheduling
– Telemetry data processing and distribution
– Data trending
– Mission products distribution and monitoring
– Operations automation
• The Mission Operations Team is responsible for the safe operations of the
orbiter to meet the mission objectives
– Operate the MOC systems based on approved procedures
– Interface with other mission elements to coordinate mission planning, operational
status, data recovery and analysis, and anomaly resolution
– Manage the operations products required for planning and execution of orbiter
operations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 139

MOC Architecture
Station Acq. Data
Space
Communications
Networks
WS1
SN
WOTIS
USN
DSN
WS1-
DPS
FDF
RT
Commands
RT
Telemetry
CFDP Status
CFDP Control
Schedules
S/C
Data
Files
Raw
Data
Files
S/C
Telemetry
MOC-DPS
CFDP Status
CFDP Control
T&C System
MOC-AGS
All MOC
Elements
FD Products
LRO MOC
Raw Data
Files
Raw Data
Files
Daily Load
Data
RT
Spacecraft
Telemetry
Attitude Slew
Commands
Status
Instrument – Spacecraft HK Data Files
Data
Management
System
Mission
Planning
System
Monitoring/Alert
System
Trending Data Files
Data
Storage
Real-time HK
Trending
System
Pages Ops
Team
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 140
Orbiter
FSW
Loads
Planning and
Mission
Products
Archive
Products
FSWM
Mission
Products
Instrument
Data Files
Planning
Products
PDS/
NAIF
LRO
SOCs LRO
SOCs LRO
SOCs LRO
SOCs LRO
SOCs LRO
SOCs LRO
SOCs

Facility Overview
• All Facilities are ready for launch
• MOC Facility located at GSFC in Building 32
– Main operations and test area (C221)
– Server Room (C221A)
– Office/support space (W235)
– Operations Conference Room (W225)
• Launch Support Room located near the MOC (Room N202)
– Accommodates all equipment and teams during launch and early mission activities
• Power Configuration
– All MOC systems fed through two separate UPS
– Emergency power provided by Building 31 power plant
• Physical Security provided by GSFC
– Keycard access required for building 32
– Secondary keycard access required for MOC areas within building 32
– Combination code access required for Launch Support Room
• Timing via Network Time Protocol (NTP) from IPNOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 141

Facility Overview
• Backup MOC located at USN Network Management Center in Horsham, PA
– Orbiter health and safety only, no science operations
– Includes MOC workstations for T&C, DPS, MPS, and MAS/AGS
• Mission Equipment at WS1
– Data processing servers onsite, tested and verified at WS1
• Flatsat
– Flatsat will be re-located from I&T to building 32, Room W30; (after transition to
nominal mission)
– Facility modifications will be complete by 5/25/09
Power runs
CNE network drops
Voice Line
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 142

MOC Facility
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 143

Launch Support Room
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 144

MOC Hardware
• All MOC hardware has been verified in tests/sims and are operational
• Hardware:
– Workstations (include MOC, BMOC, test, and WS1) : (35) Linux Servers, (15) Windows
Servers
– Launch Support Room has another 26 Linux PCs
– Storage Server/Array: RAID 6 configuration with 49TB allocated to our archive and 16 TB
allocated to backups
6 tiers available for expansion (example if we used 2TB drives we would have an additional 96TB
available)
– Tape Library (dual unit)
– Firewalls: (2) sets of redundant high-availability Juniper Networks Netscreen firewalls
Vendor service contracts with next business day delivery
– Switches: (2) sets of redundant Cisco 3560G Gigabit switches and (2) sets of redundant
3560 switches
local spares available
– Video Switches (3)
local spare available
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 145

MOC Rack Elevations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 146

MOC Software
• All MOC software has been verified in tests/Sims and are launch capable
• Software:
– MOC System developed in 3 major releases and minor releases to correct discrepancies
ITOS (T&C and DPS) Release 3.5 delivered and is launch capable
MPS Release 3.1.3 delivered and is launch capable (no further releases planned)
ITPS Release 3.1 delivered and is launch capable
DMS Release 3.3 delivered and is launch capable
AGS Release 3.2 delivered and is launch capable
MAS Release (Attention COTS release 2.1) delivered and is launch capable
RAS Release (SSL-VPN version 1.01) installed and launch capable (no further releases planned)
– Patches delivered as necessary to resolve open DRs prior to the freeze
ITOS (T&C and DPS) Release 3.6 planned to correct both open SOARS by March 20, 2009
ITPS Release 3.1.1 delivered 3/6/09 and is in testing which will correct the 6 significant SOARS
DMS Release 3.4 to deliver 2 outstanding level 4 requirements and to correct 16 SOARS by March
12,2009 and follow-up 3.5 release to close out the rest of the SOARs on March 20, 2009
MAS Release (Attention S/W patch) planned to correct all 5 outstanding SOARS by March 20, 2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 147

Backup MOC Overview
• BMOC verified and ready to support contingency operations
• BMOC provides capability to perform Orbiter commanding and telemetry
monitoring as well as minimal mission planning in the event of major failure
of the primary MOC
– Located at the USN, Network Management Center in Horsham, PA
– Orbiter health & safety only, no science operations
– Provides capability to schedule contacts, generate orbit products, generate
ATS/RTS loads, uplink commands, process r/t and stored telemetry, and monitor
and notify in the event of anomalous behavior
– Includes (6) MOC workstations for T&C, MPS, DPS, and MAS/AGS, and (2)
general access systems which allow connectivity to any of the major applications
– MOC and BMOC are synchronized every night to facilitate a quick transition
– Procedures in place for failover from MOC to BMOC, BMOC operations, and
restoring operations to the MOC
Upon restoration of the primary MOC, FOT will transfer TLM data and other products
from BMOC to MOC and resume operations
– BMOC has been tested and requirements verified in MRT tests
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 148

MOC Level 4 Requirements Verification
• 94% of MOC Level-4 requirements fully verified (1077 of 1145)
• 6.1% of the delivered requirements not fully verified due to SOARS written,
dependencies on the database, system configuration, data and on-going system test
(69 of 1143 )
• 0.1% of the requirements will be delivered in a future release (2 of 1145)
• Only 2 Level 4’s not delivered and the plan is to have them delivered by March 13 th
COMPONENT TOTAL NUMBER OF
REQUIREMENTS
VERIFIED PARTIALLY
VERIFIED
TESTED BUT
NOT VERIFIED
DELIVERED BUT
NOT TESTED
DPS 75 73 2 0 0
0
DMS 559
505 12 35 5
2
ITOS T&C
(including CA)
128
TO BE
DELIVERED IN A
FUTURE
RELEASE
124 4 0 1
0
ITPS 101
93 5 3 0
0
MPS 282 282 0 0 0
0
TOTAL 1145
1077 23 38 6
2
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 149

Spacecraft Orbital Anomaly Reporting
System
• Used for capturing all system discrepancies
• Since inception we have reported 600 SOARS of which 537 have been
closed or rejected
– Currently there are 63 open (16 delivered but not tested)
– Of the 18 Critical/Significant SOARS 10 have been delivered but not completed
testing yet, all Significant/Critical SOARS to be closed by 3/20/2009
• 3 Designations, Critical, Significant, Routine
– Critical – An issue exists such that there is no immediate workaround that can be
implemented for mitigation.
– Significant – An issue exists which requires a workaround for mitigation, but
requires significant effort or time for implementation.
– Routine – An issue exists in which the desire is to resolve but does not
adversely impact operations. A nonintrusive workaround is available.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 150

Discrepancy Report Status
Subsystem Critical DRs
(CDR)
ITOS-T&C
ITOS-DPS
ITPS
DMS
MAS
MOC
MOT
WS1
DLRE SOC
Totals
CDR Delivered
not tested
Significant
DRs (SDR)
SDR Delivered
not tested
Routine
DRs (RDR)
RDR Delivered
not tested
0 0 1 0 2 0
0 0 1 1 1 0
0 0 6 6 6 3
0 0 7 2 19 1
0 0 1 0 4 0
0 0 0 0 8 0
1 1 1 0 3 1
0 0 0 0 1 0
0 0 0 0 1 1
1 1 17 9 45 6
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 151

Critical and Significant Discrepancy Reports
SOAR ID Anomaly Title
S-LRO-0572
S-LRO-0562
S-LRO-0593
S-LRO-0473
ITOS problem with LAMP
memory load commands
File with wrong checksum
continues transfer
PM17d: Pull failed
recovery not working
ERROR8: Push Queued
Time Out Alert Not Issued
SOAR
Current
Status
Subsystem Criticality Plan to Close
DELIVERED MOT Critical
DELIVERED DMS Significant
ASSIGNED DMS Significant
ASSIGNED DMS Significant
An alternative load procedure has been
developed, using a modified version of the
LAMP-supplied memory load file. Memory
load file modifications have been reviewed
by LAMP and tested at FlatSat. Requires
testing from the MOC.
To be tested; Workaround is to rely on the
TCP protocol for maintaining file integrity
and using successful return status from
SCP to confirm successful transfer
To be delivered in DMS release 2.3/MOC
release 3.4 on 3/12/09; can trigger an
arrival failed event which would notify the
ops team to manually go in and pull the
product
To be delivered in DMS release 2.3/MOC
release 3.4 on 3/12/09; Product is taking
to long to push to the next destination;
alert message is not issued; does not
prohibit the product from continuing to be
pushed. Could issue an SQL query on a
periodic basis to identify products currently
on a push queue and how long they have
been there.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 152

Critical and Significant Discrepancy Reports
SOAR ID Anomaly Title
S-LRO-0490
S-LRO-0559
S-LRO-0529
STRESS3c: Agents and
Signatures
Remote Agents
"forgetting" previous
actions
Instrument measurement
and housekeeping files
not delivered by DMS
SOAR
Current
Status
Subsystem Criticality Plan to Close
ASSIGNED DMS Significant
ASSIGNED DMS Significant
DELIVERED DMS Significant
To be delivered in DMS release 2.3/MOC
release 3.4 on 3/12/09; Product is taking to
long to push to the next destination; alert
message is not issued; does not prohibit the
product from continuing to be pushed.
Could issue an SQL query on a periodic
basis to identify products currently on a
push queue and how long they have been
there.
To be delivered in DMS release 2.3/MOC
release 3.4 on 3/12/09; Files that were in
progress and have failed as a result of the
transfer are in a lost and found location and
can be manually restarted from the DMS
web portal. The failed events and lost and
found arrival events are used to notify the
operations team, via the MAS to manually
restart the process.
Released in DMS2.2.3/MOC3.3 to be
Tested; Mitigation is to have members of
the development and or additional
operations personnel monitor data transfers
and perform them manually or come up with
independent scripts to ensure data is
distributed in a timely fashion.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 153

Critical and Significant Discrepancy Reports
SOAR ID Anomaly Title
S-LRO-0560
Remote Agents not saving
event messages
SOAR
Current
Status
Subsystem Criticality Plan to Close
DELIVERED DMS Significant
S-LRO-0098 Syslog Agent Crashes ASSIGNED MAS Significant
S-LRO-0367
S-LRO-0318
1Meg file uplinked at
4.0kbps fails.
Telemetry controller dies
on opsitos3 during mission
sim 11
DELIVERED M-DPS Significant
ASSIGNED T&C Significant
Released in DMS2.2.3/MOC3.3 to be
Tested; files continue to flow but the
events are not recorded in the database
which can cause expectations to fail, these
notifications can alert operators of an
issue. In addition when remote agents
abort abnormally there is an event
message that can alert ops personnel
which allows them to investigate quickly.
Problem identified by vendor, waiting on
release from Attention Inc; expected by
March 20th. Workaround is to use the file
collector agent
To be tested; Nominal load sizes used
throughout I&T and rehearsals have
worked fine, only when testing maximum
size loads are we having issues. No
operational loads are thought to be near
this threshold.
To be released in patch 9 give MOC
release #, 3/13/09; requires resetting the
telemetry controller on the software,
(disable tlm, enable tlm, then run
connection procs); this will cause
temporary drop in all other tlm connections
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 154

Critical and Significant Discrepancy Reports
SOAR ID Anomaly Title
S-LRO-0567
Operations Actions from MR #4
3. Large number of events were
generating causing the event buffer to
fill between passes. No mention of this
in the pass reports. Should ensure the
procedure is updated to check the
stored HK files for events since realtime
events are deleted.
5. During MR 4, the ST went into
occultation several times. Verify routine
procedures has the MOT checking the
event times with the AGS Occultation
report. Once the times are verified, the
FDC faults due to ST losing lock can be
reset.
7. ATS load has LROC imaging during
Delta-H, need to add this check to the
loading checking procedure or develop
a rule to flag this condition.
8. ATS load for DH had the AP
reconfiguration just before LOS. For
flight, the actual times should be
adjusted so we can observe the events
from the ground and if needed, recommand
from the ground.
SOAR
Current
Status
Subsystem Criticality Plan to Close
ASSIGNED MOT Significant
Consists of a list of actions
from MR-4 that have yet to be
resolved. The outstanding
issues:
3. Still investigating this issue.
The event buffer onboard the
orbiter is only so large. The
thought was to use the SSR
event log file, however this
presents problems early
mission since the SSR is not
on. Expect to close by 20
March 2009.
5. An FPD needs to be
developed to address this
issue. Expected completion
20 March 2009
7. MPS checklist will be
modified to address this
concern. Expect to complete
by 20 March 2009.
8. This issue needs to be
added to the ATS checklist.
Expect to be complete 20
March 2009.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 155

Critical and Significant Discrepancy Reports
SOAR ID Anomaly Title
S-LRO-0404
S-LRO-0479
RequestQueueService
Goes Down
Request Queue Viewer
Goes Down
SOAR
Current
Status
Subsystem Criticality Plan to Close
DELIVERED Trending Significant
DELIVERED Trending Significant
S-LRO-0541 DyP Issue during MR#4 DELIVERED Trending Significant
S-LRO-0544 DyP Naming Convention DELIVERED Trending Significant
S-LRO-0553 DyP Notification DELIVERED Trending Significant
S-LRO-0554 DyP job stalling DELIVERED Trending Significant
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
Addressed in Release 3.1.1, to be tested;
preliminary testing has been successful;
modified trending plan to manually initiated
production
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 156

MOC Sustaining Engineering Plan
• MOC facility maintenance responsibility of GSFC
– HVAC, Power, and structural - coordinated with the B-32 Utilities workgroup
– Comm Lines, Voice systems - coordinated with the NISN
• MOC hardware maintenance
– Firewalls and Switches under NISN Maintenance contract for next day support
Systems are split across both switches and there are enough ports to swap critical systems in the
event of a failure
– Dell Servers - next day support
There is no hardware single point of failure (dual power, mirrored drives, dual processor, and dual
systems; Spares on site for swapping parts and primary and backup configuration for all critical
systems)
– Data Direct Storage Array - next day support
There is no hardware single point of failure (dual power, RAID-6 configuration, dual processor, and
dual systems; Spares on site for swapping parts)
– Avocent Video Switches- next day support
Spare onsite, test switch could be used in extreme emergency
• MOC COTS software maintenance agreements in place
– Includes Attention, Flexplan, STK, PV-Wave, MatLab, McAfee Antivirus, Patchlink, SSL-VPN
• MOC GOTS software maintenance by GSFC providers
– Includes ITOS, ITPS, DMS, AGS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 157

Summary
• Facilities and Maintenance ready for launch
• BMOC has been exercised during MRT and is ready for launch
• MOC software launch capable; however patches expected prior to software freeze date to cleanup
discrepancies
• All hardware and software are under configuration management, changes are only performed with
an associated SOAR or ECR
• Sustaining Engineering for hardware and software in place
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 158

MOC Readiness Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 159

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
ITOS-909 Deferred
ITOS-501
ITOS-508
ITOS-
905.2
ITOS-
CFDP-101
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
ITOS shall provide the capability to define and ingest raw binary table
files dumped from the spacecraft and display them in a readable format.
ITOS shall provide the capability to distribute all or a selected set of
telemetry frames, packets, and/or individual data values to at least 64
external systems via TCP or UDP IP socket connection. NOTE: The
number of TCP/IP socket connections supported are unlimited by ITOS,
but may be limited by the operating system, although it is usually a large
number.
ITOS shall provide the ability for the user to define limits for an integer or
floating-point telemetry mnemonic. A limit set consists of two concentric
ranges called the yellow limits and red limits. A limit definition may
contain an unlimited number of limit sets. The system chooses which limit
set to apply to a mnemonic based on which range the mnemonic value
falls in. ITOS provides the ability to define a minimum of 4 limit sets per
database mnemonic.
ITOS shall provide the ability to plot any single mnemonic against time at
a minimum 10 Hz data frequency arrival rate. (Will be tested for a
maximum of 5 HZ since that is LRO's fastest rate.)
The ITOS CFDP shall support CFDP class 1 and class 2 uplinks at a rate
of 4000 bps.
Need OPS Support
to verify L4
S-LRO-0318
Need OPS Support
to verify L4
Need ITOS
development Team
Support to verify L4
ITOS 7.8 Patch 8
being installed and
availability of
FlatSat.
Test with ITOS 7.8
Patch 8 3/13/2009
Re-Test with ITOS
7.8 Patch 9 which
has not been
delivered
Test with ITOS 7.8
Patch 8
Test with ITOS 7.8
Patch 8
Run test case
TRANSFER3d
using FlatSat
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 160
3/13/2009
3/13/2009
3/13/2009
3/13/2009

Level 4 Verification Summary
L4 Req # State Description Dependency
ITOS-
CFDP-401
Partial
Pass
ITPS-65 Fail
ITPS-66 Fail
The ITOS CFDP shall send a CCSDS packet to the MOC containing status, the
MIB control configuration values, and the ITOS control at a user selectable
rate. MIB control will include node ID, max outgoing file data length,
response to fault, whether to save incomplete files, ACK/NAK limits and
timeouts and inactivity timeout values. Status will include summaries and
information about each active transaction. ITOS control includes DPS ID,
temp file name, max number of uplink transactions allowed, control of RS error
frame filtering, input connection status, input connection hostname, and
mission phase. Format of the status packet will be defined in the ITOS
database. See LRO CFDP Implementation Specification (431-SPEC-000078)
Section 4.2.6 for further information.
The ITPS Daily Production capability shall allow the unmanned production of
any ASCII Report, Limit Report, Statistics Report, Mnemonic Change Report,
Plot, or Lifetime Trend addition job.
ITPS users shall be able to set up the system so that Daily Production jobs
execute only once a certain percentage of data for the day in question has been
received. If the percentage has not been met, then ITPS will retry the Daily
Production jobs every hour for the next 23 hours or until the percentage of data
is met. However, if it is not reached after 23 hours, the scheduled Daily
Production jobs are abandoned.
The configuration
values input
connection status
and input
connection
hostname to able to
be sent in the status
packet.
S-LRO-0553
S-LRO-0554
S-LRO-0544
S-LRO-0541
S-LRO-0552
Closeout
Activity
Run test case
CONTROL9.
Re-Test when
ITPS 3.2 is
delivered
Re-Test when
ITPS 3.2 is
delivered
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 161
Target
Date
3/20/2009
3/12/2009
3/12/2009

L4 Req # State
ITPS-67 Fail
ITPS-2
ITPS-3
ITPS-9
ITPS-10
ITPS-80
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
Level 4 Verification Summary
Description
The Trending subsystem shall provide user capability to select reports
for automatic generation, based upon selectable time interval or upon
completion of data ingest process.
The ITPS ASCII Report shall contain a single comma delimited
column for every mnemonic in the Input Definition File, in the order
listed in the Input Definition File.
For each mission supported, ITPS shall automatically detect and
process mission specific raw housekeeping telemetry files deposited on
the ITPS computer.
The ITPS shall be able to ingest 2 Gigabytes (GB) of LRO
housekeeping telemetry in one hour.
The ITPS shall eliminate any duplicate data from the housekeeping
telemetry Archive.
The ITPS request queue job window shall display for all report, plot
and LTT addition jobs the status, user name, input definition file name,
start time, stop time, report type, and report output filename (when
applicable).
DMS-1.1 Fail The DMS shall record the quality for all telemetry products.
Dependency Closeout Activity Target Date
S-LRO-0554
S-LRO-0381
S-LRO-0392
S-LRO-0403
S-LRO-0405
L4 was recently
changed from 400 MB
to 2 GB
Assistance from the
OPS team required
S-LRO-0404
S-LRO-0479
Resolution of SOAR S-
LRO-0522
Re-Test when ITPS
3.2 is delivered
Re-Test when ITPS
3.2 is delivered
Re-Test when ITPS
3.2 is delivered
Test when ITPS 3.2
is delivered
Test when ITPS 3.2
is delivered
Re-Test when ITPS
3.2 is delivered
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 162
3/12/2009
3/12/2009
3/12/2009
3/12/2009
3/12/2009
3/12/2009
Successful
execution of DMS
test case PM1b 3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-1.2
DMS-1.3
DMS-
2.15.1
DMS-
2.15.2
DMS-2.16
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
The DMS shall record a checksum for each product file. When the
product file is a CFDP downlinked spacecraft file, the DMS will
extract the md5 checksum from the metasummary file.
The DMS shall verify the checksum for each product file at each
location.
Remote agents shall be able to determine whether to start a transfer of a
file based on the time since the file was last updated.
The DMS shall allow a different staleness timeout value for each file
using the staleness attribute. The value will be entered in the
spreadsheet or the xml file.
Remote agents shall be able to determine whether to start a transfer of a
file based on the permissions of the file.
CFDP extracted
checksum not working
for files with metasummary
file generated
by
itos_cfdp_gap_handler.
CFDP extracted
checksum not working
for files with metasummary
file generated
by
itos_cfdp_gap_handler.
Pull transfer not
working with staleness.
Pull transfer not
working with staleness.
Pull transfer not
working with
permissions.
Successful
execution of DMS
test case PM1b
Successful
execution of DMS
test case PM1b
Successful
execution of DMS
test case PM15d.
Successful
execution of DMS
test case PM15d.
Successful
execution of DMS
test case PM16d.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 163
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-2.17
DMS-2.21
DMS-4.8.1
DMS-
4.12.1
Partial
Pass
Partial
Pass
Partial
Pass
Partial
Pass
DMS-5.1 Deferred
The DMS shall have the ability to restart failed and timed out products
at the location which they failed or timed out.
The DMS shall have tunable parameters for the push element that
allows a remote agent to attempt a configurable number a pushes at a
configurable time interval after the first push was unsuccessful.
The portal shall allow users to query products by subsystem,
product type, product name, location, arrival time, quality, signed
or unsigned, and/or spacecraft time.
Administrators shall be able to edit all tunable parameters through the
web portal.
The DMS shall manage the short and long-term storage of all files and
products for the life of the mission.
The pull fail does not
allow retry of
transfer.
Works as originally
designed. SOAR
written to address
problems in MR4 that
occurred because of
design..
Product search for
spacecraft time and
quality.
Pruning parameter not
on web portal for
remote agent specific
values.
Verification of Level-4
during MRT testing.
Successful
execution of the
following tests:
PM17d
Successful
execution of test
case MOVE3f as
run through a
scenario that
mimics OPS.
Successful
execution of
PM6a and PM1b.
Successful
execution of test
case PM19
Verification of
Level-4 during
MRT testing.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 164
3/27/2009
3/27/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-6.9 Deferred
The DMS shall track "redelivery requested" events over the life of the
mission.
DMS-7.4 Deferred The DMS shall not require scheduled down time for maintenance.
DMS-7.5 Deferred
DMS-7.10 Deferred
DMS-7.21 Deferred
DMS-7.25 Fail
DMS-9.1 Deferred
It shall be possible to backup the DMS database while the DMS is
running.
It shall be possible to recover the entire DMS database from a previous
database backup plus the transaction log since that backup was created.
The DMS shall be able to update the XML model with the current
configuration of the database by running a database script.
Remote agents shall limit, to a configurable number, the number of
actions than can be placed in the “to central agent queue”.
The DMS shall be capable of storing five years of real-time and
engineering data files online.
Level-4 not delivered
yet.
Verification of Level-4
during MRT testing.
Setting up database to
write to transaction
logs.
Setting up database to
write to transaction
logs.
Level-4 not delivered
yet.
Successful run of test
case STRESS10
Verification of Level-4
during MRT testing.
Successful
execution of test
case PM9.
Verification of
Level-4 during
MRT testing.
Successful
execution of test
case STRESS4
Successful
execution of test
case STRESS4
Successful
execution of test
case STRESS5
Successful
execution of test
case STRESS10
Verification of
Level-4 during
MRT testing.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 165
3/20/2009
3/20/2009
4/1/2009
4/1/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-
15.1.6
DMS-
15.3.1
DMS-
15.3.2
DMS-
15.3.3
DMS-
15.3.4
DMS-
15.3.5
DMS-
15.9.1
DMS-
15.9.2
Fail
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
The DMS shall issue a “push queued timed out event” alert when a
remote agent does not finish pushing a product from one location on
a system to another location on another system before the push
queue timeout period has expired.
The DMS shall support a “push queued timeout” period which is the
amount a time a remote agent will wait for a queued list of products
that are to be pushed to complete.
The DMS shall support a default “push queued timeout” period that
is used when the remote-agent-specific “push queued timeout” is not
set.
The “push queued timeout” period shall be specified in the xml
database file in the following locations: dms-model-defaults,
remote-agent, and/or push elements.
The DMS shall allow administrators to change the default “push
queued timeout” period through the web portal.
The DMS shall allow administrators to change the “push queued
timeout” period for a specific remote-agent through the web portal.
The DMS shall support a different “push queued timed out event”
alert template for each remote agent.
The DMS shall support a default “push queued timed out event” alert
template that is used when the remote agent-specific “push queued
timed out event” alert template is not set.
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 166
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-
15.9.3
DMS-
15.9.4
DMS-
15.9.5
DMS-
17.1.1
DMS-
17.1.2
DMS-
17.1.3
DMS-
17.2.1
Incomplete
Incomplete
Incomplete
Fail
Incomplete
Incomplete
Fail
The DMS shall support a null “push queued timed out event” alert
template that prevents the “push queued timed out event” alert from
being issued.
The DMS shall allow administrators to edit the default template for
“push queued timed out event” alerts through the web portal.
The DMS shall allow administrators to edit the template for the
“push queued timed out event” alert for a specific remote agent
through the web portal.
The DMS shall issue a “partial product anomaly event” alert when all
files of a mutli-file product do not arrive at a specific location.
The DMS shall allow specific information about a partial product
anomaly event to be included in the partial product anomaly event
alert message. Information which can be included in the partial
product anomaly event message are product type, location, product
name, timestamp, product version and time waited for completion.
The DMS shall allow a partial product anomaly event alert message
to be specified under the following locations in an xml database file:
dms-model-defaults, product, and/or at-location elements.
The DMS shall support a “partial product timeout” period which is
the amount a time a remote agent will wait for a multi-file product to
arrival at a location.
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-473
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR8.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 167
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-
17.2.2
DMS-
17.2.3
DMS-
17.2.4
DMS-
17.2.5
DMS-
17.3.1
DMS-
17.3.2
DMS-
17.3.3
DMS-
17.3.4
DMS-
17.3.5
Fail
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
Incomplete
The DMS shall support a default “partial product timeout” period that
is used when the product/at-location-specific “partial product
timeout” is not set.
The “partial product timeout” period shall be specified in the xml
database file in the following locations: dms-model-defaults,
product, and/or at-location elements.
The DMS shall allow administrators to change the default “partial
product timeout” period through the web portal.
The DMS shall allow administrators to change the “partial product
timeout” period for a specific product type through the web portal.
The DMS shall support a different “partial product anomaly event”
alert template for each remote agent.
The DMS shall support a default “partial product anomaly event”
alert template that is used when the remote agent-specific “partial
product anomaly event” alert template is not set.
The DMS shall support a null “partial product anomaly event” alert
template that prevents the partial product started event alert from
being issued.
The DMS shall allow administrators to edit the default template for
“partial product anomaly event” alerts through the web portal.
The DMS shall allow administrators to edit the template for the
“partial product anomaly event” alert for a specific remote agent
through the web portal.
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Closure of SOAR S-
LRO-0475
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
Successful
execution of
ERROR6a.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 168
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-
19.1.10
DMS-
19.1.13
DMS-
20.1.3
DMS-
21.5.1
DMS-
21.5.2
DMS-
21.5.3
Partial
Pass
Partial
Pass
Partial
Pass
Fail
Fail
Fail
The DMS shall allow specific information about a signature event to be
included in the signature event alert message. Information which can
be included in the signature event message is product name, product
type, version, and timestamp. The alert-event-signature-added and
alert-event-signature-removed messages can also include user and
signature group..
The DMS shall issue a “waiting for signature timed out” alert when the
central agent receives a “waiting for signature timed out” message from
a remote agent indicating a product was not signed within the “timeoutsignature-wait”
timeout.
The “local poll” interval shall be specified in the xml database file in
the following locations: dms-model-defaults, remote agent, and/or atlocation
elements.
The DMS shall issue a “remote agent startup event” alert when a remote
agent is started.
The DMS shall allow specific information about a remote agent startup
event to be included in the remote agent startup alert message.
Information which can be included in the duplicate product event
message are remote agent name, config-version, and timestamp.
The DMS shall allow a remote agent startup event alert message to be
specified under the following locations in an xml database file: dmsmodel-defaults,
and/or remote-agents elements.
Closure of SOAR S-
LRO-0569.
Closure of SOAR S-
LRO-0569.
Need to run test case
PM13 during Release
3.3 testing.
Closure of SOAR S-
LRO-0587.
Closure of SOAR S-
LRO-0587.
Closure of SOAR S-
LRO-0587.
Rerun test case
SIGN2
Rerun test case
SIGN2
Successful
execution of test
case PM13.
Successful
execution of test
case HEART1.
Successful
execution of test
case HEART1.
Successful
execution of test
case HEART1.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 169
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

Level 4 Verification Summary
L4 Req # State Description Dependency Closeout Activity Target Date
DMS-
21.6.1
DMS-
21.6.2
DMS-
21.6.3
DMS-
21.7.1
DMS-
21.7.2
DMS-
21.7.3
Fail
Incomplete
Incomplete
Fail
Fail
Fail
The DMS shall issue a “product deletion anomaly event” alert when
a file is deleted from a multi-file product before it is completed at a
specific location.
The DMS shall allow specific information about a product deletion
event to be included in the product deletion alert message.
Information which can be included in the product deletion event
message, are location, product type, product name, version, and
timestamp.
The DMS shall allow a product deletion event alert message to be
specified under the following locations in an xml database file: dmsmodel-defaults,
products, and/or at-location elements.
The DMS shall issue a “checksum mismatch event” alert when a
computed checksum of a file is different than a previous checksum
of the same file at a different location.
The DMS shall allow specific information about a checksum
mismatch event to be included in the checksum mismatch alert
message. Information which can be included in the checksum
mismatch event message, are location, product type, product name,
and version.
The DMS shall allow a product deletion event alert message to be
specified under the following locations in an xml database file: dmsmodel-defaults,
products, and/or at-location elements.
Closure of SOAR S-
LRO-0476
Closure of SOAR S-
LRO-0476
Closure of SOAR S-
LRO-0476
Checksum mismatch
does not issue alert
message put in DMS
model
Checksum mismatch
does not issue alert
message put in DMS
model
Checksum mismatch
does not issue alert
message put in DMS
model
Successful
execution of
ERROR6b.
Successful
execution of
ERROR6b.
Successful
execution of
ERROR6b.
Successful
execution of
ERROR11
Successful
execution of
ERROR11
Successful
execution of
ERROR11
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 170
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009
3/20/2009

SOAR Summary
SOAR ID Anomaly Title
SOAR
Current
Status
S-LRO-0274 LRO-SIM-03: DLRE OAR (DLRE-1) DELIVERED DLRE SOC Routine
S-LRO-0202 No message for edited fallback values ASSIGNED DMS Routine
S-LRO-0433 DMS signature via portal ASSIGNED DMS Routine
S-LRO-0463
S-LRO-0465
ARRIVE6: Incorrect product name in central
agent message
Firefox problems when trying to get data for
product
Subsystem Criticality Plan to Close
ASSIGNED DMS Routine
ASSIGNED DMS Routine
File received to be verified with
ICD
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; informational
message, value is
implemented in the database
and web portal is still functional
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; Can issue a
manual SQL query to retrieve
the information from the
database.
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; Correct in the
database and on the Web
Portal the product name was
displayed the correct product
name.
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; restart Firefox
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 171

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0470
PM15d: Pull transfer method not using
staleness value.
SOAR
Current
Status
Subsystem Criticality Plan to Close
ASSIGNED DMS Routine
S-LRO-0472 PM16d: Pull does not attempt with permissions ASSIGNED DMS Routine
S-LRO-0475 ERROR6a: Partial Product Timeout Not Used ASSIGNED DMS Routine
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; currently the
method is not used but may
need to be for FDF
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; currently the
method is not used but may
need to at the WS1 DPS
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; incomplete
products (one or more files but
not the complete set) will still
exist in the directory but no
further processing will be
performed, it will require
manual intervention at this
point, ops team will know
because either an arrival or
creation expectation event will
fail
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 172

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0476
ERROR6b: Product Deletion Anomaly does
not Work
SOAR
Current
Status
Subsystem Criticality Plan to Close
ASSIGNED DMS Routine
S-LRO-0507 Level-4's not Delivered ASSIGNED DMS Routine
S-LRO-0517 Alert messages not picking up dms model ASSIGNED DMS Routine
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; incomplete
products (one or more files but
not the complete set) will still
exist in the directory but no
further processing will be
performed, it will require
manual intervention at this
point, ops team will know
because either an arrival or
creation expectation event will
fail, the product that no longer
exists will have to be recovered
from the archive
Final requirements to be
delivered in DMS release
2.3/MOC release 3.4 on
3/12/09
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; informational no
impact, similar to a
typographical error
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 173

SOAR Summary
SOAR ID Anomaly Title
SOAR
Current
Status
S-LRO-0522 CFDP Checksum Extraction not working ASSIGNED DMS Routine
S-LRO-0561
S-LRO-0569
No event messages when Remote Agent
retries a push
Issues with alert-event-waiting-for-signaturetimed-out
Subsystem Criticality Plan to Close
ASSIGNED DMS Routine
ASSIGNED DMS Routine
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; This is a problem
extracting data from the meta
data file to the database, the
data is still available in the
meta file, the database tables
could be manually updated to
add the information, but the
files continue in the transfer
process.
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; Informational
message to give you an idea of
how many times the product
was attempted. If the product
exceeds that maximum
number of tries set it will fail
and there is a notification for
that.
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; informational no
impact; similar to a
typographical error
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 174

SOAR Summary
SOAR ID Anomaly Title
SOAR
Current
Status
S-LRO-0584 Idle Web Portal processes to database ASSIGNED DMS Routine
S-LRO-0587
S-LRO-0588
Remote agent startup message no longer
issued
Product search does not have spacecraft time
and quality
Subsystem Criticality Plan to Close
ASSIGNED DMS Routine
ASSIGNED DMS Routine
S-LRO-0589 SIGN5: Blocking and Unblocking Product ASSIGNED DMS Routine
S-LRO-0594 {options} not being read on pull transfers ASSIGNED DMS Routine
Currently under investigation,
unable to reproduce, has only
occurred once
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; informational no
impact
To be delivered in DMS
release 2.4/MOC release 3.5
on 3/20/09; information is in
the database and can be
manually queried if necessary
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; signature process
still functions there are just
unwanted side affects
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; setup the model
not to use any options for the
pull transfers
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 175

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0568
Alert-event-duplicate-product-anomaly not
issued in fan-in scenario
SOAR Current
Status
Subsystem Criticality Plan to Close
DELIEVERED DMS Routine
S-LRO-0092 Create Action panel does not work ASSIGNED MAS Routine
S-LRO-0093 Certain Help buttons do not work. ASSIGNED MAS Routine
S-LRO-0096 FieldSet Won't Save ASSIGNED MAS Routine
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; duplicate files have
a .dup-# attached, therefore
they are identified even if the
alert message is not issued.
We could write an independent
cron to monitor directories for
files with a .dup in it to notify
the ops team
Waiting on release from
Attention Inc; expected by
March 20th. Administrator can
create actions.
Waiting on release from
Attention Inc; expected by
March 20th. Help files put on
the desktop.
Waiting on release from
Attention Inc; expected by
March 20th. Don’t use special
characters in the fieldset.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 176

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0568
Alert-event-duplicate-product-anomaly not
issued in fan-in scenario
SOAR Current
Status
Subsystem Criticality Plan to Close
DELIEVERED DMS Routine
S-LRO-0092 Create Action panel does not work ASSIGNED MAS Routine
S-LRO-0093 Certain Help buttons do not work. ASSIGNED MAS Routine
S-LRO-0096 FieldSet Won't Save ASSIGNED MAS Routine
To be delivered in DMS
release 2.3/MOC release 3.4
on 3/12/09; duplicate files have
a .dup-# attached, therefore
they are identified even if the
alert message is not issued.
We could write an independent
cron to monitor directories for
files with a .dup in it to notify
the ops team
Waiting on release from
Attention Inc; expected by
March 20th. Administrator can
create actions.
Waiting on release from
Attention Inc; expected by
March 20th. Help files put on
the desktop.
Waiting on release from
Attention Inc; expected by
March 20th. Don’t use special
characters in the fieldset.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 177

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0464
S-LRO-0494
Firefox closes without notice when using
mouse scroll button
No Access to FDF and WOTIS if BMOC is
Down
SOAR
Current
Status
Subsystem Criticality Plan to Close
ASSIGNED MOC Routine
ASSIGNED MOC Routine
S-LRO-0539 Countdown Clock Malfunction ASSIGNED MOC Routine
S-LRO-0597 DDN Chassis H Failed ASSIGNED MOC Routine
S-LRO-0598 Event Notification Application at Login ASSIGNED MOC Routine
Redhat site monitored for
Firefox and desktop updates to
address error type. Restarting
Firefox is the only workaround.
Firewall implementation in
place, but unable to verify,
troubleshooting with IPNOC
Replace stale schedule and
pass script with new files.
Manual process.
RMA submitted replacement
expected 3/9/09
Redhat site monitored to
desktop updates to address
error type. Closing out the
screen closes all open
screens.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 178

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0600
S-LRO-0439
S-LRO-0540
S-LRO-0543
S-LRO-0371
Operational Network Port
Conflicts
DMS remote agent logs filled
up C: drive on opsags1
causing extreme slowness
Pass Script Not Including
Activities That Cross a GMT
Day
HGA/SA FSW Accel/Decel
Profile Should be disabled
during large array slews
Xlib Messages Seen When
Navigating
SW_DS_DEST_TABLE page
SOAR Current
Status
Subsystem Criticality Plan to Close
ASSIGNED MOC Routine
DELIVERED MOT Routine
ASSIGNED MOT Routine
ASSIGNED MOT Routine
ASSIGNED T&C Routine
Has to do with cycling through the source ports
for LDAP, this happens infrequently every couple
months and is easily fixed with a reboot.
Investigating if we can reserve source ports for
LDAP
To be Tested, logs moved to D: drive because
there is more space and the model has been
updated, to be complete by 3/12/09
Requires manual review to ensure activities that
span days are captured and transferred into the
next days script
The software commands have not made it into
the MPS command database yet because they
were probably added in the last few FSW
releases. The MOT is planning on one last MPS
command update before launch, but is waiting
until after the PDB freeze (at G/S freeze date).
This SOAR is on-hold until after the database
update on MPS.
Reported on developers system Bugzilla 631,
Under investigation but no impact to operations,
often can be addressed with a page clear and
redisplay
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 179

SOAR Summary
SOAR ID Anomaly Title
SOAR
Current
Status
S-LRO-0599 DSN Monitor Block Filter Failure ASSIGNED T&C Routine
S-LRO-0381 Mnemonics out of order ASSIGNED Trending Routine
S-LRO-0392
Mysterious Packets Being Ingested Into ITPS
from Realtime VC0 Data Stream
Subsystem Criticality Plan to Close
ASSIGNED Trending Routine
S-LRO-0403 .HOLD files DELIVERED Trending Routine
S-LRO-0405 Ingest Service does not stay active DELIVERED Trending Routine
To be released in ITOS
7.8p9/MOC release 3.6 on
3/13/09;Does not filter the
specific station desired instead
receives all monitor data. DSN
status data is not critical
Unable to recreate, awaiting reoccurrence.
Not addressed in R 3.1.1 but
we believe that this only
occurred as a consequence of
other Ingest issues. Those
issues have been addressed,
so it is believed that this SOAR
no longer occur.
We were unable to recreate,
but have changed the way the
Request Viewer updates in Rel
3.1.1 and hope that this fixed.
We were unable to recreate,
but have changed the way the
Request Viewer updates in Rel
3.1.1 and hope that this fixed.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 180

SOAR Summary
SOAR ID Anomaly Title
S-LRO-0552
1-Hour DyP jobs execute regardless of %
complete
SOAR
Current
Status
Subsystem Criticality Plan to Close
DELIVERED Trending Routine
S-LRO-0590 Clear Completed Jobs window ASSIGNED Trending Routine
S-LRO-0591
Two WS1 status data points not populated
correctly -- Describes a fault where two values
in the WS1 Station Status are shown as zero
instead of being populated with correct values.
Specifically, the two values are the number of
telemetry frames received in the 'lock' status
and number of frames that contained errors
which were successfully corrected.
ASSIGNED WS1 Routine
We were unable to recreate,
but have changed the way the
Request Viewer updates in Rel
3.1.1 and hope that this fixed.
Developer and MOT believe
behavior may have been result
of user selection - no s/w
changes are planned to
address this.
These values are only in error
for the second string of Ka
Band equipment, the first string
values are reported correctly.
This SOAR is being tracked by
WS1 Sustainment as CDS#
26800. The anomaly will be
corrected in the next release,
however that release has not
been scheduled.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 181

Software Inventory & Sustaining Plan
Item Product Description Vendor Current Release Mission
Version Date Critical
MOC Telemetry and Command System (T&C)/Data Processing System (DPS)
1 Red Hat Enterprise Linux Linux operating system. Red Hat, Inc. 5.3 12/17/2008 Yes Source code is
(OS)
available.
2 ITOS (GOTS) Software used to support
Telemetry and command
capabilities
3 Apache (COTS) Web server environment for Linux
to support web-based pages.
4 Java Development Kit
(JDK)
Software us ed to s upport ITOS
page creation and display.
5 PatchLink (COTS) Automated patch management
s oftware for Linux.
MOC Mission Planning System (MPS)
1 Red Hat Enterprise Linux
(OS)
2 FlexPlan (COTS) Software used to support
mission planning capabilities.
Code 584.0
owned
software
3.5 (7.8p8) 2/23/2009 Yes Owned and
maintained by Code
584 for multiple
Apache
2.2.3 7/27/2006 No
GSFC missions.
Supported by the
Foundation
Apache Foundation
and freely available.
Sun
6.0r11 1/10/2009 No Supported by Sun
Micros ys tem s
Microsystems and
freely available.
PatchLink 6.4.378 12/8/2008 No Provided by and
SP1
supported by Code
700 Helpdesk
Linux operating system. Red Hat, Inc. 5.3 12/17/2008 Yes Source code is
available.
3 Oracle 10g (COTS) Database software required by
FlexPlan for storing the mission
planning database.
3 Java Development Kit
(JDK)
Software us ed to s upport ITOS
page creation and display.
4 PatchLink (COTS) Automated patch management
s oftware for Linux.
GMV Space
Systems
3.1.3 2/26/2009 Yes Owned and
maintained by GMV
Space Systems.
Oracle, Inc. 10g r2 11/15/2006 Yes Provided by and
supported by GMV
Space Systems as
part of FlexPlan.
Sun
Micros ys tem s
PatchLink 6.4.378
SP1
6.0r11 1/10/2009 No Supported by Sun
Microsystems and
freely available.
12/8/2008 No Provided by and
supported by Code
700 Helpdesk
Risk Mitigation GSFC Code/P.O.C/
Maintenance Information
Support provided by Dell
Silver Enterprise Support (3
years from date of
purchase)
G. Greer/584
(301) 286-5999
ggreer@hammers.com
http://www.apache.com/
http://www.java.com/
Code 700 Helpdesk
(301) 286-7342
Support provided by Dell
Silver Enterprise Support (3
years from date of
purchase)
As s af Barnoy
(301) 216-3840
abarnoy@gmvspacesyste
ms.com
As s af Barnoy
(301) 216-3840
abarnoy@gmvspacesyste
ms.com
http://www.java.com/
Code 700 Helpdesk
(301) 286-7342
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 182

Software Inventory & Sustaining Plan
Item Product Description Vendor Current Release Mission
Version Date Critical
MOC Data Management System (DMS)
1 Red Hat Enterprise Linux Linux operating system. Red Hat, Inc. 5.3 12/17/2008 Yes Source code is
(OS)
available.
2 DMS (GOTS) Software used to track delivery of
files throughout ground system
and manage digital signatures.
3 Apache (COTS) Web server environment for
Linux.
4 PHP (COTS) Interpreted server-side scripting
language to be used with
Apache.
5 PostgreSQL (COTS) Database software required by
DMS for storing the data
management database.
6 Java Development Kit
(JDK)
Software used to support DMS
page creation and display.
7 PatchLink (COTS) Automated patch management
software for Linux.
MOC Web and Product Server
1 Red Hat Enterprise Linux
(OS)
2 SSL-Explorer Enterprise
Edition (COTS)
3 Java Development Kit
(JDK)
Code 584.0
owned
software
Apache
Foundation
Zend
Technologies
3.3
(2.2.3)
11/5/2006 Yes Owned and
maintained by Code
584 for multiple
2.2.3 7/27/2006 Yes
GSFC missions.
Supported by the
Apache Foundation
and freely available.
5.1.6 11/2/2006 Yes Source code is
available.
PostgreSQL 8.2.4 9/10/2007 Yes Source code is
available.
Sun
Micros ystem s
PatchLink 6.4.378
SP1
6.0r11 1/10/2009 No Supported by Sun
Microsystems and
freely available.
12/8/2008 No Provided by and
supported by Code
700 Helpdesk
Linux operating system. Red Hat, Inc. 5.3 12/17/2008 Yes Source code is
available.
Software to provide secure
encrypted remote access to MOC
resources with two-factor
authentication.
Software used to support web
server.
3SP Inc. 1.01 11/5/2007 Yes Source code is
available.
Sun
Micros ystem s
6.0r11 1/10/2009 No Supported by Sun
Microsystems and
freely available.
Risk Mitigation GSFC Code/P.O.C/
Maintenance Information
Support provided by Dell
Silver Enterprise Support (3
years from date of
purchase)
T. Singletary/584
(301) 345-5300
tsingle@hammers.com
http://www.apache.com/
http://www.php.net/
http://www.postgresql.org/
http://www.java.com/
Code 700 Helpdesk
(301) 286-7342
Support provided by Dell
Silver Enterprise Support (3
years from date of
purchase)
Richard Pernavas
sales@3sp.com
http://www.sun.com/
4 PatchLink (COTS) Automated patch management PatchLink 6.4.378 12/8/2008 No Provided by and Code 700 Helpdesk
software for Linux.
SP1
supported by Code (301) 286-7342
700 Helpdesk
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 183

Software Inventory & Sustaining Plan
Item Product Description Vendor Current Release Mission Risk Mitigation GSFC Code/P.O.C/
Version Date Critical
Maintenance Information
MOC Integrated Trending and Plotting System (ITPS)
1 Microsoft Windows Server Microsoft Windows Operating Microsoft 2003 R2 12/6/2005 Yes Risk is accepted Support provided by Dell
2003 (OS)
System.
Silver Enterprise Support (3
years from date of
purchase)
2 ITPS (GOTS) Integrated Trending and Plotting Honeywell 3.1.1 3/6/2009 Yes Owned and H. Brumer/583
System
maintained by code (301) 805-3584
583 for multiple Haim.Brumer@honeywell-
GSFC missions. tsi.com
3 PV-Wave (COTS) Plotting library used by ITPS to VNI 8.51 11/7/2006 Yes Provided by and H. Brumer/583
generate plots and trends.
supported by code (301) 805-3584
583 as part of ITPS. Haim.Brumer@honeywelltsi.com
4 MySQL 5 (COTS) Database software required by MySQL, Inc. 5.0.30 11/30/2006 Yes Provided by and H. Brumer/583
ITPS for storing the trending
supported by code (301) 805-3584
database.
583 as part of ITPS. Haim.Brumer@honeywelltsi.com
5 Java Development Kit Software used to support ITPS. Sun
6.0r11 1/10/2009 No Supported by Sun http://www.java.com/
(JDK)
Microsys tems
Microsystems and
freely available.
6 Microsoft Office 2007 Microsoft Office 2007
Microsoft 2007 9/27/2007 Yes Risk is accepted Microsoft license for
(COTS)
environment.
updates
7 Adobe Reader 9 (COTS) Adobe Acrobat Reader PDF
viewing environment.
Adobe 9.0 1/5/2009 Yes Risk is accepted Provided by Adobe
8 ActiveState Perl (COTS) Perl environment for Microsoft ActiveState 5.6.1 4/16/2004 Yes Provided by and H. Brumer/583
Windows.
supported by code (301) 805-3584
583 as part of ITPS. Haim.Brumer@honeywelltsi.com
9 GNU
PostScript and PDF converts for GhostScript 8.5 5/30/2006 Yes Provided by and H. Brumer/583
GhostScript/GhostView Microsoft Windows.
supported by code (301) 805-3584
(COTS)
583 as part of ITPS. Haim.Brumer@honeywelltsi.com
10 Apache Tomcat (COTS) Web server/Java Web Services Apache
6.0 7/16/2008 Yes Risk is accepted http://tomcat.apache.org/
environment for Microsoft
Windows.
Foundation
11 PatchLink (COTS) Automated patch management PatchLink 6.4.378 12/8/2008 No Provided by and Code 700 Helpdesk
software for Windows.
SP1
supported by Code
700 Helpdesk
(301) 286-7342
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 184

Software Inventory & Sustaining Plan
Item Product Description Vendor Current Release Mission Risk Mitigation GSFC Code/P.O.C/
Version Date Critical
Maintenance Information
MOC Monitoring and Alert System (MAS)
1 Microsoft Windows Server Microsoft Windows Operating Microsoft 2003 R2 12/6/2005 Yes Risk is accepted Support provided by Dell
2003 (OS)
System.
Silver Enterprise Support (3
years from date of
purchase)
2 Attention! Notification Software to provide automated Attention 6.1.1257 6/11/2007 Yes Owned and Tim Cogswell
System (COTS)
response to triggered events by Software, Inc.
maintained by (800) 684-1684 x200
notifying personnel.
Attention Software, tcogswell@attentionsoftwar
Inc.
e.com]
3 Attention! Alarm Manager Software to manage alarms to be Attention 2.1.1258 6/12/2007 Yes Owned and Tim Cogswell
(COTS)
trigger by events.
Software, Inc.
maintained by (800) 684-1684 x200
Attention Software, tcogswell@attentionsoftwar
Inc.
e.com]
4 SQL Server Express 2005 Database software required by Microsoft 2005 11/7/2005 Yes Risk is accepted. Support availab e via
(COTS)
Attention! for storing the anomaly
notification database.
Microsoft
5 Java Development Kit Software used to support Sun
6.0r11 1/10/2009 No Supported by Sun http://www.java.com/
(JDK)
Attention.
Micros ys tems
Microsystems and
freely available.
6 PatchLink (COTS) Automated patch management PatchLink 6.4.378 12/8/2008 No Provided by and Code 700 Helpdesk
software for Windows.
SP1
supported by Code
700 Helpdesk
(301) 286-7342
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 185

Software Inventory & Sustaining Plan
Item Product Description Vendor Current Release Mission Risk Mitigation GSFC Code/P.O.C/
Version Date Critical
Maintenance Information
MOC Attitude Ground System
1 Microsoft Windows Server Microsoft Windows Operating Microsoft 2003 R2 12/6/2005 Yes Risk is accepted Support provided by Dell
2003 (OS)
System. Provides Active Directory
Silver Enterprise Support (3
controller capabilities to
years from date of
authenticate users across all
MOC systems.
purchase)
2 Attitude Ground System Software to provide attitude Code 590 3.2 2/25/2009 Yes Owned and FDF on call support for
determination support
maintained by code
590.
software maintenance.
3 Matlab Mathematical analysis software Mathworks 2008B 11/7/2008 Yes Under software
maintenance
http://www.mathworks.com/
4 Java Development Kit Software used to support web Sun
6.0r11 1/10/2009 No Supported by Sun http://www.java.com/
(JDK)
server.
Micros ys tem s
Microsystems and
freely available.
5 PatchLink (COTS) Automated patch management PatchLink 6.4.378 12/8/2008 No Provided by and Code 700 Helpdesk
software for Linux.
SP1
supported by Code
700 Helpdesk
(301) 286-7342
MOC Active Directory and SQL Server (ADS)
1 Microsoft Windows Server Microsoft Windows Operating Microsoft 2003 R2 12/6/2005 Yes Risk is accepted Support provided by Dell
2003 (OS)
System. Provides Active Directory
Silver Enterprise Support (3
controller capabilities to
years from date of
authenticate users across all
MOC systems.
purchase)
2 PatchLink (COTS) Automated patch management PatchLink 6.4.378 12/8/2008 No Provided by and Code 700 Helpdesk
software for Linux.
SP1
supported by Code
700 Helpdesk
(301) 286-7342
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 1 - 186

Mission Operations Center Readiness
Attitude Ground System
LRO Flight Operations Review – Section 6.2
NASA’s Goddard Space Flight Center
Oscar Hsu
LRO AGS Lead

Outline
• Spacecraft Overview
• AGS Overview
• AGS Support Plan
• Attitude Maneuver Support Plan
• Sensor Calibration Support Plan
• Attitude Determination Support Plan
• AGS Readiness
• Transition Plan for hand-over to MOT
• Issues, Risks, Future Work
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 188

• Sensors
AGS-Centric Spacecraft Overview
– 2 Star Trackers
– 1 Inertial Reference Unit
– 10 Coarse Sun Sensors
• Actuators
– 4 80 N-m-s Reaction Wheels
– 8 20 N Class Thrusters
– 4 80 N Class Thrusters
SA AXIS-2
- 45 DEGREES
SA AXIS-1
0 DEGREES
HGA AXIS-2
0 DEGREES
HGA AXIS-1
0 DEGREES
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 189
Z
X
S/C
COORDINATE
SYSTEM
Y

AGS Software Status Since MOR
• AGS Software is Matlab Based and located in and operated from the LRO
MOC.
• AGS consists of three main components
– Mission Three Axis Stabilized Spacecraft System (MTASS)
– Real Time Attitude Determination System (RTADS)
– Attitude Maneuver Planning Utility (AttMan)
• B3.0 – Released June 2, 2008
– RTADS predicted HGA Gimbal Angles not fully verified
– HGA Calibration Utility not fully tested
• B3.1 – Released January 23, 2009
– Issue with RTADS Socket Read
• B3.2 – Released February 13, 2009
– No known issues
• B4.0 – Launch + 60 Days
– Post-Launch Build
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 190

AGS Requirements Updates Since MOR
• 32 Requirements added since MOR
• The new requirements:
– Defined the slew constraints and slew types that AttMan shall support.
– Are derived from the original 16 requirements presented at MOR
• The requirements were already implemented in AttMan at the time of MOR,
but they had not been remapped at the time.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 191

AGS Hardware Configuration
• Mission Operations Center (MOC)
– 2 Dedicated Windows XP PCs located in the MOC Equipment Rack
– Matlab 2008B Installed
– 1 for critical attitude support
– 1 for offline support and backup for critical support
• Backup Mission Operations Center (BMOC)
– No dedicated PCs.
– Matlab 2008B Installed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 192

LRO AGS Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 193

AGS Software Modifications/Additions to
Support LRO
• MTASS Major Updates
– Attitude Determination System (ADS)
Telemetry Processor (TP)
IRU Calibration Parameter Output File
Star Tracker Alignment Parameter Output File
– Guide Star Availability Tool (GSAT)
– Guide Star Interference Tool (GSIT)
– High Gain Antenna Calibration (HGACAL)
– Trending Tool
• SPICE CK File Tool
• HGACAL Planning Tool
• Real Time Attitude Determination System (RTADS)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 194

AGS Software Modifications/Additions to
Support LRO (con’t)
• Attitude Maneuver (ATTMAN)
– Maneuver Constraint Checks slews
Sun Avoidance Constraint
Power Constraint
Slew Rate Constraint
Omni-antenna constraint
Star Tracker Constraint
Thermal Constraint
– Slews Modeled
Solar-inertial nominal
On-orbit nadir-point phases
Thrust vector pointing (file from FDF)
Sensor Calibration slews
Roll, pitch, and yaw slews in Lunar Orbit Coordinate System
Z-axis pointing slews with optional raster scans
Mini-RF checkout
Lunar eclipse attitude
– Output
ASCII attitude file with keywords to MPS for each slew
Data for SPICE CK Predictive Attitude History File (from calculated attitudes)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 195

AGS Acceptance Testing
• Baselined in LRO AGS Software Test Plan (FDF-178-015)
– Approx. 100 tests spanning 15 subsystems (TP, DA, CFADS, EKF, QUEST, ATTVAL, BICAL, ALIQUEST,
HGACAL, AttMan, SPICE CK, HGACAL Planning Tool, GSIT, GSAT, RTADS)
– Served as basic tests for Builds 1 & 2; served as basis for regression testing in all later releases
• Variety of test methodologies used:
– AGS results were compared to independent calculations (e.g., all TP/DA results checked using Matlab
command line; GSIT interference results checked using independent Matlab testing tool)
– AttMan constraint results independently checked with FreeFlyer
– Benchmarks established for ADS, RTADS, and definitive SPICE CK using a variety of simulated LRO data
Hi-Fi data used early on before sequential prints were available
Sequential prints used from Sim3, Sim29, & Mission Rehearsal #1
– Benchmarks established for predictive subsystems: AttMan, GSIT, Predictive SPICE CK, HGA Planning
Tool, and GSAT
– Benchmarks established for calibration subsystems: BICAL, ALIQUEST, and HGACAL
• New development items (post Build 2) tracked in AGS “Checklist”
– Approx. 200 independently tested items documented in checklist
– AGS Releases 3.0, 3.1, and 3.2 fully regression tested against benchmarks
• Requirement Verifications
– 47 of 48 requirements are verified
– AGS-16 (The AGS Team shall provide user documentation, procedures, and training for the AGS delivered
to the MOC.) has not been verified and cannot be verified until transition to the MOT has occurred at ~L+60
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 196

Operations Concept
• Launch through mission orbit insertion (~L+60 days)
– AGS Ops Team provides primary support but transition to MOT can occur earlier
if formal training is complete.
– AGS Ops Team will cover critical operations regardless of MOT training status.
– AGS Ops Team will perform MOT Training
• After Mission Orbit Insertion (Post ~L+60 days)
– MOT supports routine operations
– AGS Team is on-call for contingencies, AGS anomaly resolution, and attitude
sensor calibration as needed.
– FDF on-call for software maintenance support
– Code 590 is on-call for anomaly resolution
– AGS Sustaining Engineering Support will be part of the MOC MOMS Task
– AGS Software Maintenance Support is provided by FDF.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 197

AGS L&EO Operations Support Plan
• AGS Ops Team provides support until early spacecraft check is completed
(~L+60 days)
– Attitude Determination and Verification (real time and offline)
– Attitude Sensor Calibration Maneuver Planning and Support
– Attitude Planning Product generation
– MOT Training
• AGS Ops Team support will be 24 hours during critical periods
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 198

Attitude Maneuver Support Plan
• Orbit Maneuvers
– Wheels used to acquire initial burn attitude
– Thruster based during orbit maneuver
• IRU Sensor Calibration
– MiniCal Pre-LOI
– Post LOIs and infrequently afterwards
– Wheel Based
• Star Tracker (ST) Sensor Calibration
– Preliminary Alignment Calibration performed prior to IRU MiniCal
– Post LOIs and infrequently afterwards
– Wheel Based
• Instrument Calibration Maneuvers
– Periodic throughout the mission
– Will be performed after Star Tracker/MIMU calibration completed
– Wheel Based
• HGA Calibration Maneuvers
– During the commissioning orbit
– HGA Raster Scan required and may require roll offsets
– Wheel Based
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 199

Sensor Calibration Support Plan
• Attitude Sensor calibration includes
– Star Tracker Alignment Matrices
– IRU scale factors, alignments, and biases
• Preliminary Star Tracker Calibration performed prior to Mini IRU Calibration
• Mini IRU Calibration is performed prior to LOI-E
• Full sensor calibration is planned for commissioning orbit
• Expectation of infrequent sensor calibrations but the Moon environment
may change that plan.
• Calibration Supported in Mission Rehearsals
– Preliminary Star Tracker calibration performed during MR#2
– Mini IRU Calibration was performed during MR#2
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 200

Attitude Determination
• Real-Time Attitude Determination
– Critical phases or otherwise as needed with best achievable accuracy
– Socket interface
• Offline Attitude Determination
– Performed daily in order to validate the onboard attitude solution (30 arcsec/axis,
3-sigma)
– ASCII sequential print interface
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 201

LRO AGS Ops Team Staffing Plan
• Two 12-hour operations shifts (critical periods)
– L to L+7 Days
• Prime Shift (centered around critical events)
– Two AGS Ops Team members
• Off Shift
– One AGS Ops Team member
• LOI through MOI (~L+60 days) Operations
– Single 8-hour shift staffed by One AGS Ops Team Member or until MOT is fully
trained.
– Orbit Maneuvers will be staffed by two AGS Ops Team Members
– AGS Personnel are on call for sensor calibration as needed
• Normal Operations
– Staffing provided by MOT for planning products, SPICE CK, attitude validation.
– AGS Personnel are on call for sensor calibration as needed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 202

AGS Team Training Plan
• AGS Team Consists of 10 Team Members from a.i. Solutions
• AGS Ops Team Consists of 9 Team Members from a.i. Solutions
• AGS Ops Team Training Accomplished by:
– Individual prior experience and expertise
– LRO specific training in product generation and process
– Internal simulation – nominal and contingency situations
– External simulation – nominal and contingency situations (Mission Sims)
– Mission Rehearsals
– AGS Ops Team will provide documentation of operating procedures
– Launch Version will be completed by L-60 days
– Final Version will be delivered by L+90 days
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 203

MOT Training Plan and
Responsibilities
• The MOT’s AGS responsibility includes seven functions:
– Generating slew plans
– Generating predictive SPICE CK attitude files.
– Generating definitive SPICE CK attitude, solar array angle, and high gain antenna files.
– Generating ASCII attitude files for FDF.
– Performing onboard attitude validation
– Performing sensor residuals and attitude error trending.
• Informal training has already begun and will continue during simulations with the MOT
shadowing the AGS team.
• Formal training will start at Launch -60 days, with full certification by Launch +60
days. Formal training will consist of the following:
– Obtaining data and products from a previous normal day ops sim
– Processing the data and generating all products
– MOT independently processes the same data again and the products are compared to those
generated by AGS team.
– Another normal ops sim datasets and products are obtained and processed by AGS team
– MOT processes same datasets and the AGS team evaluates products.
– If processing is correct, then the MOT obtains preliminary certification for AGS functions (full
certification cannot be granted until post launch when ops procedures are modified based
upon flight performance/anomalies)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 204

MOT Training Plan and
Responsibilities (con’t)
• Full Certification training will be completed by L+60 days. This certification
process will consist of the following:
– AGS team member will train MOT on official procedures using daily flight
products and telemetry (1 day).
– AGS team member will assist MOT on processing telemetry and generating
products for 5 days (look over their shoulders).
– For the following day, AGS personnel will process telemetry and generate
products independently of the MOT.
– If the MOT can duplicate the results, then they are certified to Level 3
Proficiency.
• From Launch +60 days to Launch +90 days:
– After the first week, AGS personnel will gradually decrease their staffing in the
MOC so the MOT will be independently performing normal AGS ops well before
Launch +90 days.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 205

• Past Support
AGS Ops Team Mission Rehearsal and
Simulation Support Status
– Mission Rehearsal #1 (normal ops)
– Mission Rehearsal #2
(launch to LOI-1)
– Mission Rehearsal #4 (normal ops)
– Sim4 (LOI-1)
– Sim7 (MCC)
– Sim8 (nominal mission)
– Sim11 (day 1)
– Sim12 (LOI-1)
– Sim17 (LOI)
– Sim18 (SK)
– Sim20 (MCC)
– Sim27 (launch)
– Sim29 (day in the life)
– Sim30 (launch)
• Upcoming Support
– Mission Rehearsal #3 (Lunar Orbit Acq
and SC commissioning)
– Mission Rehearsal #5
(Launch to LOI)
– Sim06 (LOI-1 Contingency)
– Sim13 (Instrument Calibration
– Sim22 (Instrument Calibration)
– Sim23 (Integrated Launch Sim)
– Sim25 (Integrated Launch Sim)
– Sim26 (Nominal Ops)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 206

AGS Team Training Status
LRO AGS Support Activities/Procedures JS JH JG NO DF GN JB ES LM MOT
Generate slew plan & predicted attitude (AGS4) 4(4) 4(4) 4(4) 4(4) 4(4) 2(3) 3(3) 2(3) 3(3) 0(3)
Generate GSIT interference report & plots (AGS8) 4(4) 4(4) 4(4) 4(4) 4(4) 2(3) 2(3) 2(3) 2(3) 0(3)
Generate predictive CK products (MOC41, MOC74) 4(4) 4(4) 4(4) 4(4) 4(4) 2(3) 2(3) 2(3) 2(3) 0(3)
Generate OBC attitude validation report (AGS3) 4(4) 4(4) 4(4) 4(4) 4(4) 2(3) 2(3) 2(3) 2(3) 0(3)
Generate definitive CK products (MOC42-44, 65-67) 3(4) 3(4) 4(4) 4(4) 3(4) 2(3) 2(3) 2(3) 2(3) 0(3)
Monitor real-time events using RTADS 4(4) 4(4) 4(4) 4(4) 4(4) 3(3) 2(3) 2(3) 2(3) 0(2)
Generate early mission maneuver special products 3(4) 2(4) 4(4) 1(4) 3(4) 1(3) 1(3) 1(3) 1(3) 0(0)
Perform star tracker analysis with GSAT 4(4) 4(4) 3(3) 1(2) 2(3) 4(4) 1(2) 1(2) 1(2) 0(0)
Perform star tracker alignment calibration (AGS7) 4(4) 4(4) 1(2) 0(0) 0(2) 0(0) 0(0) 0(0) 0(0) 0(0)
Perform gyro alignment calibration (AGS5) 4(4) 4(4) 1(2) 0(0) 1(2) 0(0) 0(0) 0(0) 0(0) 0(0)
Perform HGA gimbal alignment calibration (AGS6,9-10) 4(4) 4(4) 1(2) 0(0) 0(2) 0(0) 0(0) 0(0) 0(0) 0(0)
0 - no formal training yet on procedure Note: Required training level in parentheses ( )
1 - can perform procedure with supervision
2 - can perform procedure independently, with little or no troubleshooting capability
3 - can perform procedure independently, with some troubleshooting capability
4 - can perform procedure independently, with full troubleshooting capability
Formal Training will be
completed by the end of
Mission Rehearsal #5
*With the exception of MOT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 207

Key Documentation Status
Document Document Number Current Status
AGS Requirements Specification LRO Doc No.: 451-SPEC-003500 Rev 1.2 in CCR Process
AttMan Functional Specifications LRO Doc No.: 451-RPT-003366
MOMS Doc. No: FDF-178-014
Rev 9.4 Released: 12/12/2008
LRO AGS Software Test Plan MOMS Doc. No.: FDF-178-015 Rev 1 Released: 2/20/2008
FD LRO AGS User’s Guide and
Operations Handbook
MTASS Users Guide NASA Doc. No.: 464-GS-SPEC-0083
MOMS Doc. No.: FDF-85-001
MOMS Doc. No.: MOMS-FD-UG-0414 Original Released: 7/21/2008
Next Release Planned: L-60 Days
Update 9 Released: 2/2009
AGS MOT Training Materials LRO Doc No: 451-xxxx-xxxxxx Draft
Final Version Due L+45 Days
AGS MOT Certification Plan LRO Doc No: 451-xxxx-xxxxxx Draft
Final Version Due L-60 Days
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 208

Issues/Risks/Future Work
• Issues and Risks
– Spice CK HGA and SA Data Files may need to change to accommodate new
SOC requests. This will require a patch to the AGS software.
• Future Work
– Mission Simulation and Rehearsal Support
– B4.0 – Post Launch Delivery
– Documentation
– Training
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 209

AGS Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 210

AGS Requirements (1 of 3)
ID Description
AGS-1 The Attitude Ground System (AGS) shall provide LRO attitude knowledge relative to a reference AST of 30 arc-seconds (3sigma)
per axis provided both ASTs and 30 or more minutes of data are available.
AGS-2 The AGS shall generate attitude slew plans in a format defined by the MOC
AGS-3 The AGS shall constraint check each requested attitude slews and list the constrains violated.
AGS-4 AGS shall provide the capability of predicting the occultation of the star trackers during all phases of the mission.
AGS-5 The AGS shall ingest various attitude target plans as well as model the nominal Lunar pointing target in order to generate the
predicted Attitude History File (AHF). The format of AHF file shall be in the SPICE CK format.
AGS-6 AGS shall generate a calibration report for the LRO HGA gimbals.
AGS-7 AGS shall generate a Definitive AHF in the SPICE CK file using OBC estimated quaternions.
AGS-8 AGS shall generate a Definitive HGA file using the observed HGA gimbal angles and outputting them as SPICE CK files.
AGS-9 AGS shall generate a Definitive Solar Array file using the observed SA gimbal angles and outputting them as SPICE CK files.
AGS-10 AGS shall compute a real-time estimate of the spacecraft attitude using best achievable accuracy.
AGS-11 AGS shall validate the Onboard Computer (OBC) computed attitude estimate.
AGS-12 AGS shall provide as needed the ACS sensor calibration parameters for the IRU alignment, scale factors, and biases with the
assumption this delivery will be infrequent and delivered to the MOC.
AGS-13 AGS shall provide as needed the ACS sensor calibration parameters for the ASTs alignments with the assumption this deliveries
will be infrequent and delivered to the MOC.
AGS-14 AGS Hardware shall be located in the LRO MOC
AGS-15 The AGS Team shall develop, test, and deliver the AGS to the MOC
AGS-16 The AGS Team shall provide user documentation, procedures, and training for the AGS delivered to the MOC.
AGS-17 AGS shall allow one or more slew constraints to be waived by the appropriate personnel.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 211

AGS Requirements (2 of 3)
ID Description
AGS-18 AGS shall have a slew constraint that maintains a Sun 60 degree keep-out half-cone about the spacecraft +z-axis.
AGS-19 AGS shall either attempt the maneuver using the longest euler axis angle instead of the default smallest angle or issue an error
message stating the requested slew is invalid
AGS-20 AGS shall keep Spacecraft –Y axis less than 90 degrees away from the sun
AGS-21 AGS shall have a maximum slew rate per axis < 0.1 deg/sec
AGS-22 AGS shall maximize Omni-Antenna performance.
AGS-23 AGS shall maintain an Eclipse Safe Attitude.
AGS-24 AGS shall generate attitude slew plans encompassing the following slew types subject to required constraints
AGS-25 AGS shall generate a Solar Inertial Target defined by the -y-axis to sun vector and one of two OMNI antennas (in the spacecraft
x-y plane as close as geometrically possible to Earth)
AGS-26 AGS shall generate Delta-V maneuver target quaternions
AGS-27 AGS shall generate Ingest Delta-V timed target vectors from FDF
AGS-28 AGS shall generate Delta-V target quaternions needed to point spacecraft +x-axis to the Delta-V vector with angle between
generated targets specified by FDF.
AGS-29 AGS shall generate Delta-V target quaternions that keep –y-axis as close as possible to sun.
AGS-30 AGS shall insure the Delta-V target quaternions does not have to undergo a large attitude angle change during the maneuver due
to sun constraints.
AGS-31 AGS shall generate Normal Lunar target quaternions defined by +z-axis to Lunar Nadir and ±x-axis to velocity vector
AGS-32 AGS shall generate target quaternions for a Stellar Slew (+z-axis to directed star and –y-axis as close as possible to sun)
AGS-33 AGS shall generate target quaternions that produce a 90-Degree Yaw Slew
AGS-34 AGS shall generate target quaternions for Mars/Jupiter Raster Scan Pointing (+z-axis to selected target). The box size, step
size, and delta-t between raster steps shall be provided by LOLA.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 212

AGS Requirements (3 of 3)
ID Description
AGS-35 AGS shall generate target quaternions for Earth Raster Scan Pointing (+z-axis to selected target). The box size, step size, and
delta-t between raster steps shall be provided by LOLA.
AGS-36 AGS shall generate target quaternions for off-nadir stepped roll slew with step size, the number of steps, and the time between
steps provided by LEND.
AGS-37 AGS shall generate target quaternions for a Stellar Slew (+z-axis to directed target)
AGS-38 AGS shall generate target quaternions for a slew to Dark Space (+z-axis to directed target)
AGS-39 AGS shall generate target quaternions for a Stellar Slew (+z-axis to directed target)
AGS-40 AGS shall generate target quaternions for a 90-Degree roll slew
AGS-41 AGS shall generate target quaternions to point Mini-RF towards a ground station
AGS-42 AGS shall generate target quaternions for a 180 Degree Yaw maneuvers
AGS-43 AGS shall generate target quaternions for a Lunar Eclipse Maneuver
AGS-44 AGS shall output the star tracker occultation report to the MOC.
AGS-45 AGS shall calibrate HGA gimbal angles to relative accuracy of 0.1 degrees (3-sigma) to Earth antenna.
AGS-46 AGS shall generate target quaternions for any attitude slews necessary to calibrate the HGA
AGS-47 AGS shall generate predicted HGA gimbal angles
AGS-48 AGS shall be capable of inputting the OBC calculated spacecraft to ground Station vectors in J2000 GCI coordinates and
outputting them into an ASCII file to FDF.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 213

Training Levels
• Level 0 personnel have not received any training
• Level 1 personnel shall be able to generate assigned products with
supervision
• Level 2 personnel shall be able to generate assigned products without
supervision
• Level 3 personnel shall be able to recognize and resolve issues such as:
– incorrect or corrupted input file
– ephemeris file not covering the expected time span (e.g. 4 day rather than 10)
– time conflict between requested slews
– prepare an HGA contact file with a mix of roll angles
• Level 4 personnel shall be able to recognize and resolve issues such as:
– due to contingency conditions, the Sun constraint needs to be suppressed
– prepare an HGA raster pattern with steps half as big as normal
– prepare an HGA contact file designed to be completed in one day
– "resolve" the issues, may mean changing a namelist parameter, or simply
knowing to report the problem back to the MOT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 214

LRO AGS Input Products and Status
ID Description Status
FDF-20 Predicted LRO Ephemeris File Successfully Received and Processed
FDF-38 Target Thruster Vector File Successfully Received and Processed
FDF-40 Definitive GTDS Ephemeris File Successfully Received and Processed
FDF-42 FDF Time Coefficient File Successfully Received and Processed
FDF-44 Trajectory Insertion Data Successfully Received and Processed
MOC-2 SPICE Clock Correlation File Successfully Received and Processed
MPS-11 Slew Request File Successfully Received and Processed
NAIF-2 SPICE LSK – Leap Seconds Successfully Received and Processed
TC-1 RTADS Socket Connection Successfully Received and Processed
TC-3 Raw Attitude Data File Successfully Received and Processed
TC-14 Real-time Raw Attitude Data Successfully Received and Processed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 215

LRO AGS Output Products and Status
ID Description Status
AGS-1 Application Log Verified
AGS-3 Attitude Determination Validation Plan Verified
AGS-4 Attitude Slew Plans Verified
AGS-5 Gyro Calibration Data Verified
AGS-6 HGA Calibration Data Verified
AGS-7 Star Tracker Calibration Data Verified
AGS-8 General Sensor Interference Report Verified
AGS-9 HGA Raster Scan Product Verified
AGS-10 Preferred Station Contacts Verified
MOC-41 SPICE Predicted CK (Predicted S/C Orientation) Verified
MOC-42 SPICE Definitive CK (Definitive S/C Orientation) Verified
MOC-43 SPICE Definitive HGA Orientation CK Verified
MOC-44 SPICE Definitive SA Orientation CK Verified
MOC-65 Definitive Space Body Frame Attitude -ASCII Verified
MOC-66 Spacecraft HGA Motion File –ASCII Verified
MOC-67 Spacecraft Solar Array Motion File –ASCII Verified
MOC-69 LRO Provided Separation Data Verified
MOC-74 Predictive LRO Spacecraft Body Attitude File -ASCII Verified
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 216

Mission Operations Center Readiness
LRO Flight Operations Review – Section 6.3
NASA’s Goddard Space Flight Center
Jack Murphy
Mission Operations Team

Product Overview and Summary
• Documentation
– Flight Procedures (Narrative step-by-step procedures)
– Ops Documents (MOP, SDD, etc)
• ITOS Products
– Database
Telemetry and Command Mnemonics (single source for all database users, e.g. MPS,
ITPS)
Ground Mnemonics for configuration and ground system status
– Other Products
Command Procedures (Executable STOL)
Display Pages
Sequential Prints (inputs to AGS)
Configuration Monitors
• FlexPlan Products
– Binary Absolute Time Sequence (ATS), Relative Time Sequence (RTS), Lunar
and Orbiter ephemeris load files
– Attitude Ground System Inputs
– Pass Scripts
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 218

Operations Product Development
Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 219

Configuration Management
• Documented in the LRO GS&O Configuration Management Plan
431-PLAN-000083
• MOC Software is controlled by LRO Project CCB
– Chaired by Mission Director with support from MOT, GS Engineer, and
LRO Project
• Operational Products are controlled by Operations CCB
– Chaired by MOT Lead with support from MOT, LRO Project and LRO
FSW Maintenance as required
• All changes require generation of Engineering Change Request
(ECR)
– Includes Project Database, STOL Procedures, MPS Rules, System &
Software Configurations, All RTS definitions, including Orbiter Safing,
DMS Model
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 220

Flight Procedures Summary
• Flight Procedures defined
– Narrative description of steps to complete a specific Orbiter or Ground System
Operation; covers launch and early mission, normal operations and non-routine
• Flight Procedures contained in four documents, summary below
– “Other” defined: All "other" RT Operations FPDs that are not C&DH or Instrument
related. These include: ACS, Deployables, Ground System, Orbiter, Power,
Propulsion, and RF
• Remaining Flight Procedures needing development are in-work
– List of FPDs requiring development are in backup slides
Type Document
Real-time
Number
Developed
In-Work
C&DH 59 0
Instrument 55 27
Other 49 0
Off-Line Off-Line 71 11
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 221

STOL Procedures
• STOL Procedures Defined
– ITOS STOL procedures that issue Orbiter commands, ground system directives,
CFDP ground control, monitor telemetry for end-item verification
– Procedures are verified against Orbiter and/or FlatSat
• Remaining procedures to be verified
– Orbiter:
All procedures that can be verified against the Orbiter are complete
Remaining procedures must be verified against FlatSat
– These procedures modify onboard memory
– Expected completion: 13-Mar-2009
– Ground: Procedures require interface to ground stations. Will be fully verified
following completion of ORTs
Expected completion (based on current ORT schedule): 13-Apr-2009
Procedure Identified Written Tested % Developed % Tested
Orbiter 423 423 411 100% 97%
Ground 102 102 88 100% 86%
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 222

Project Database
• Project Database consists of Orbiter and Ground System database
– CM controlled by the LRO GS&O CCB
Change requests submitted through LRO GS&O Engineering Change Request system
Version control maintained by MOC using Subversion tool
– Distributed to other ground system elements
– ITOS Database Exchange format is single source for all other products (ITPS,
MPS)
• Current database version 2.09 (as of 3/3/2009)
• At GS Freeze, database version will be Version 3.0
• Project System Engineering team generated a System Engineering Report
to capture command details (451-SER-003317)
– Identifies critical commands and rationale
– Captures test verification information (when the command was used)
– 840 Commands in the project database (68 commands are identified as critical)
– Critical Commands were identified using the following definitions
Performs critical or hazardous activity
Potentially could be hazardous if component or orbiter is not in the correct configuration
Could impact orbiter performance and/or science observations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 223

MOT Orbiter and Ground System
Involvement
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 224

MOT Certification
• MOT Certification criteria is documented in LRO MOT Training and
Certification Plan document
• Each team member is required to complete minimum hours and complete
checklist pre-launch; All hours are based on Mission Sim, Reh, and ORTs:
– Telemetry & Command
Test Hours Required: 50
Real-Time Operations Checklist: Complete (44 of 44 items)
– Mission Planner:
Test Hours Required: 50
Mission Planning Checklist: Complete (35 of 35 items)
– Offline Engineer:
Test Hours Required: 25
Offline Engineering Checklist: Complete (34 of 34 items)
• Team launch certification requires the following:
– 10 Ops Engineers certified as Telemetry & Command
– 6 Ops Engineers certified as Mission Planner
– 10 Ops Engineer certified as Off-Line Engineer
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 225

MOT Certification Status
Team Member
Telemetry & Command Mission Planning Offline Engineering
Hours
Checklist
Completed Hours
Checklist
Completed Hours
Checklist
Completed
Total
Hours
50 50 25 125
Carrington 67 39 12 118
Crew 50 62 X 86 198
Dixon 42 64 68 174
Gardner 51 36 48 135
Ignasiak 62 14 54 130
Johnson 108 26 12 146
Koenig 90 11 70 X 171
Kowalski 118 X 82 X 61 261
Murphy 34 X 0 74 108
Parker 95 12 24 131
Patel 59 34 15 108
Sanidad 84 7 44 135
Saylor 32 16 24 72
Sutermeister 71 24 24 119
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 226

MOT Certification - Plan Forward
• Plan to achieve MOT Certification by April 15, 2009
• MOT is actively reviewing Flight Procedure Documents and other related
documentation
• Perform group training sessions – In Progress
– Focused on the concepts defined in the checklist
• Continue to execute Operational Readiness Tests
– Tests are actively being scheduled via the SCN Scheduling Process
• Support Mission Simulations and Rehearsals
– LRO-SIM-15 – Early Mission with Contingencies
– LRO-SIM-23 – Integrated Launch Simulation
– Mission Rehearsal #5 – Launch to Lunar Orbit Insertion
• Perform Ground System Only Training Exercises
– Additional training exercises for checklist validation
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 227

MOT Certification - Plan Forward
• Plan forward is based on events identified below
• Expect to meet MOT Certification Criteria minimum with
additional margin
Event Scheduled Date Hours Planned
Simulation 15 – Early Mission Contingencies Mar 9, 2009 6
Simulation 23 – Integrated Launch Simulation Mar 24, 2009 12
Operational Readiness Tests Multiple Planned 2 per test
Mission Rehearsal #5 – Launch to LOI Mar 30, 2009 5 days
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 228

Backup Slides – FPD’s In-Work
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 229

Flight Dynamics
LRO Flight Operations Review – Section 7.0
NASA’s Goddard Space Flight Center
Rivers Lamb
Flight Dynamics Ground System Lead

Agenda
• Flight Dynamics Overview
– Support by Mission Phase
– Team Roles and Responsibilities
– Hardware and Software Status
– Interface and Product Testing
• Maneuver Team Status
– Support Requirements
– Staffing Plan
– Training Status
• Orbit Team Status
– Support Requirements
– Staffing Plan
– Training Status
• Tracking Data Evaluation
– Tracking Station Certification
– Three-Way Tracking Demonstration
– Staffing and Training
• Flight Dynamics Status Summary
– Documentation
– Open Action Items and Risks
– Future Schedule
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 231

Flight Dynamics Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 232

Pre-Launch Support
• LRO will be launched into a direct lunar trajectory by an Atlas V
– Pre-launch LRO flight dynamics analysis defined valid launch window based on
mission requirements (lunar beta angle, lunar inclination, etc)
– Final LRO target state vectors were provided to United Launch Alliance (ULA);
ULA provided final (“Cycle 3”) data to LRO in December
– These best available trajectories for each launch date and time are available in
FDF as STK satellite files
• The FDF-LRO GS Operations Agreement (451-MOA-002960), released
March 2009, defines the required pre-launch FDF products
– DSN required a set of SPK products in January to analyze launch cases
– MOC required eclipse and view period products in January for all launch cases
– A defined subset of the FDF products are delivered to the MOC three days prior
to the planned launch date
– For a slip to a new launch date, FDF will deliver this defined subset of products
for new launch date within one hour of the announced slip
• FDF goes into freeze at L-3 days
• FDF is not mandatory for launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 233

Launch and Mid-Course Correction
• Most launch dates have seven instantaneous launch times in a one-hour window
– If launch slips within the one-hour window, FDF will deliver new products immediately
following launch based on pre-launch analysis
• Launch will be supported by FDF ELV team, under contract to KSC
– Separation vector is provided by ELV team to LRO FDF team by Sep + 10 min
– FDF products will be updated based on the separation vector by Sep + 2 hrs
• Ground station tracking is continuous from first contact following separation through
lunar orbit insertion
– First orbit determination expected no later than Sep + 6 hrs, at which point all FDF products
will be updated
• Mid-Course Correction (MCC-1) maneuver planned to correct for Atlas V dispersions
– MCC-E is planned for Sep + 22 hrs and MCC-1 is planned for Sep + 24 hrs
– Preliminary maneuver plans (MCC-E and MCC-1) delivered to MOC at Sep + 11 hrs
– Results from MOC FlatSat simulation of maneuvers delivered to FDF at Sep + 17 hrs
– Final maneuver plans (MCC-E and MCC-1) delivered to MOC at Sep + 19 hrs
• After MCC-1, no maneuvers planned until LOI-1
– Post MCC-1 orbit determination expected no later than MCC-1 + 36 hrs
• Above deliveries are in FDF-LRO GS Operations Agreement (451-MOA-002960)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 234

Launch Window
• Current launch date: 5/21/2009 (Eastern Time)
• Ten launch dates in 30-day contractual launch window provided to
ULA
– Approximately three days every two weeks
– One 1 hour launch window per day
• Additional launch targets generated and delivered to ULA through
7/30/2009 in case of launch slip
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 235

Conjunction Assessment
• KSC Final Launch Vehicle Orbital Debris Assessment Report (ODAR) for the
LRO/LCROSS Mission states no added orbital debris from LRO/LCROSS launch
except in event of catastrophic failure
– NPD 8710.3, “Policy for Limiting Orbital Debris Generation,”
• Mission Assurance (MA) COLA is required per GPD 8000.1
– MA COLA protects other on-orbit assets from LRO/LCROSS launch
– Performed approximately 3 days prior to launch day with updated low accuracy catalog
– KSC/ULA accepted requirement to perform MA COLA analysis
• Range Safety COLA performed by KSC
– Safety COLA protects on-orbit manned assets
• NPR 8715.6a does not require Conjunction Assessment analysis (with respect to
orbital debris) for missions with parking orbits only in LEO
• LRO/LCROSS conjunction assessment
– Separation states for both missions analyzed by ULA for conjunction during lunar transfer
– GSFC Code 595 providing flight dynamics for both missions
– Informal exchange of ephemerides and conjunction assessments
– Formal exchange of ephemerides and maneuver planning for LCROSS impact
• LRO/Kaguya/Chandrayaan-1 conjunction assessment
– Best effort (ephemerides not available publicly)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 236

Lunar Orbit Insertion
• The Lunar Orbit Insertion (LOI-1) maneuver occurs 4-5 days after launch
– LOI-E is planned for seven hours before the middle of the LOI-1 maneuver
– Preliminary maneuver plans (LOI-E and LOI-1) delivered to MOC at LOI-E – 11 hrs
– Results from MOC FlatSat simulation of maneuvers delivered to FDF at LOI-E – 5 hrs
– Final maneuver plans (LOI-E and LOI-1) delivered to MOC at LOI-E – 3 hrs
– LOI-1 has duration of approximately 40 minutes, targets a lunar orbit with a 5 hr period
– FDF monitors Doppler residuals in real-time during maneuver
• Four additional maneuvers (LOI-2-5) lower the orbit, establish commissioning orbit
– Each maneuver occurs approximately one day following the previous maneuver
– Schedule allows maneuver sequence to be completed while in view from Earth
– In lunar orbit, orbit determination takes two orbits following maneuver
– Preliminary maneuver plans delivered to MOC at LOI-X – 11 hrs
– Results from MOC FlatSat simulation of maneuvers delivered to FDF at LOI-X – 7 hrs
– Final maneuver plans delivered to MOC at LOI-X – 5 hrs
• Above deliveries are documented in FDF-LRO GS Operations Agreement
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 237

Lunar Orbit
• Commissioning orbit duration is up to 60 days
– Frozen orbit (30 x 216 km); no orbit maneuvers required
– Momentum unloading expected once every two weeks
– Orbit determination and product generation completed daily
• Set of three Mission Orbit Insertion (MOI-1-3) maneuvers achieves mission orbit
– Preliminary MOI-1 maneuver plan delivered to MOC at MOI-1 – 48 hrs
– Results from MOC FlatSat simulation of maneuvers delivered to FDF at MOI-X – 36 hrs
– Final MOI-1 maneuver plan delivered to MOC at MOI-1 – 24 hrs
– In lunar orbit, orbit determination takes two orbits following maneuver
• Mission orbit duration is one year
– Polar orbit with altitude of 50 ± 20 km
– Pair of stationkeeping maneuvers required once every 27 days
– Momentum unloading expected once every two weeks
– Orbit determination and product generation completed daily
– Twice during mission, definitive orbit determination using laser ranging data
• Daily products in lunar orbit are documented in LRO External Systems ICD
– Timing of maneuver-related deliveries is in FDF-LRO GS Operations Agreement
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 238

Contingency Planning
• Three critical operations for LRO FDF support
– Post-separation orbit determination to calculate accurate orbit state
– MCC-1 planning and execution for correcting Atlas V dispersions
– LOI-1 planning and execution for capturing into lunar orbit
Contingencies include delaying the maneuver, aborting & restarting the maneuver, &
capturing with reduced thrust
Extensive internal and project level contingency simulations have been performed to
prepare all subsystems to handle these contingencies
Contingency plans are in place in the event that the LOI-1 maneuver is missed
completely
• A Flight Dynamics Tiger Team will be available for contingency support
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 239

Roles and Responsibilities
• Flight Dynamics support provided by two teams in FDF
– Maneuver Team (5 people)
Lead: Michael Mesarch
Navigation and Mission Design Branch Civil Servant Team
Mission Design
Maneuver Planning and Calibration
– Orbit Determination Team (8 people)
Lead: Steve Slojkowski
Contractor Team under MOMS Task 28
Orbit Determination
Product Generation
• General facility software support under MOMS Task 33
• Facility sustaining engineering support under MOMS Task 34
• Launch vehicle support under MOMS Task 49 (ELV Team)
• Tracking data evaluation support under MOMS Task 30
• Through L-3 months, analysis support was under MOMS Task 178
– Analysts transitioned to MOMS Task 28
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 240

FDF Support from Building 28
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 241

FDF Hardware Status
• Four workstations are dedicated to LRO support in FDF
– Two workstations for Orbit Team, two for Maneuver Team
– Other FDF workstations have been configured for LRO support if needed
Requires a particular STK configuration to use network file updates
File update process documented in LRO Orbit Reference Files (FDF-178-023)
– These workstations have been used to support internal and external sims
• Communications Server handles interface between FDF and MOC
– MOC requires secure file transfers not available through FD Product Center
– Server is currently operational and has supported the internal and external sims
– Documented in Product Center Communication (MOMS-FD-PRCD-0378R2)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 242

FDF Software Status
• Navigation Software Release 1 has been used in operations since 8/1/08
– Includes launch-critical upgrades to GTDS and TRAMP
– Test plan documented in MOMS-FD-PLAN-0383R1 GTDS Build 1 LRO
– Software performance documented in FDF-178-024: LRO Software Performance
• Commercial software has been defined and used in operations extensively
– STK version 8.1.3 – six licenses available to LRO and LCROSS teams
Two attitude module licenses also required for each mission
– FreeFlyer version 6.5 – available on LRO Orbit Team workstations
– MATLAB version 2007b – available on LRO Maneuver Team workstations
• Supporting scripts for automation and product generation are on a server
which is backed up and archived on an hourly basis
• Navigation Software Release 2 is in development
– Includes laser-specific GTDS enhancements and scripts to process laser data
– Release is not needed for launch; first use expected at ~L+6 months
– Extensive testing will occur after launch in coordination with the LOLA SOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 243

SN
IIRV
FDF
External Interface Testing
S-band Telemetry
SPK
DSN
2-way S-band R&D
TRK
2-34
2-way S-band R&D
White Sands
WOTIS & WS1
INP2, OEM,
View Periods
LRO
1-way
Ka-band
Telemetry
forward LR
Closed IONet Open IONet
2-way S-band R&D
CDDIS
LR Data
UTDF
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 244
CPF
UTDF
FDF Internal
Product Exchange Product
Center
USN
LR
Data
CRD
MOC LOLA SOC
All Other
Products
Communications
Server
FDF

External Product Testing
• All external FDF interfaces have been tested and are functioning correctly
– As part of this testing, product formats have been tested by end users
– All 30 outgoing FDF products and 7 incoming FDF products critical for launch
and early mission support have been tested successfully
– Two ELV team products to be tested during MR-5
SN acquisition data and TVHF state vector exchange with Orbit Team
– Documented in LRO External Systems ICD (431-ICD-000049)
• Product issues to be resolved or tested
– MOC products currently being delivered with an *.IN-TRANSIT extension
– Several laser ranging products have not been tested (not needed for launch)
• Product quality is validated against other software tools
– Documented in LRO Product Validation (FDF-178-025)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 245

Internal Interface and Product Testing
• Internal FDF product exchange documented in the LRO Flight Dynamics
Facility Mission Support Plan
• Maneuver Team Internal Products
– STK Satellite Files – used by Orbit Team to prepare products
Delivered daily and at key points in mission (e.g. post-separation, prior to every
maneuver, etc.)
• Orbit Team Internal Products
– Maneuver Plan Summary – based off of Maneuver Team Satellite file deliveries
Delivered at key points in mission to facilitate personnel scheduling
– Orbit Solution Vectors – solutions written to TVHF with hard copy delivery
Delivered after key points in mission (e.g. post-separation, 2-hours before Maneuver
Team deliveries, etc.)
• Product exchanges have been exercised at various internal and external
simulations
– Extensively exercised during MR-2 (August, 2008) and MR-5 (March, 2009)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 246

Maneuver Team Status
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center
Michael Mesarch
Maneuver Team Lead

Sample Manuever Timeline
Maneuver Thrusters* Timing Duration Maneuver Target
MCC-E 0x4 Sep + 22 hrs 30 sec Observe ACS response
MCC-1 0x4 Sep + 24 hrs TBD Correct for launch dispersions
LOI-E 4x8 LOI-1 – 7hrs 30 sec Observe ACS response
LOI-1 4x8 L + 4-5 days 38 min Capture into 5 hr orbit period at 216 km
periapsis altitude
LOI-2 2x8 LOI-1 + 1 day 12 min Lower apoapsis
LOI-3 2x8 LOI-1 + 2 days 12 min Lower apoapsis
LOI-4 2x8 LOI-1 + 3 days 12 min Circularize at 216 km
LOI-5 2x8 LOI-1 + 4 days 4 min Lower periapsis to 30 km
MOI-1 2x8 LOI-1 + ~45 days 3 min Circularize at current periapsis altitude
MOI-2 0x4 MOI-1 + 1 day 1 min Set MO apoapsis altitude
MOI-3 0x4 MOI-2 + 1 day 40 sec Set MO periapsis altitude
SK-01a 0x4 LLAN = 270° 2 min Two burn transfer to reset MO altitude
SK-01b 0x4 SK-01a + 169 min 2 min Two burn transfer to reset MO altitude
* NxM thruster configuration specifies # of 20-lbf Insertion thrusters (N) and # of 5-lbf attitude thrusters (M) used for each maneuver
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 248

FlatSat
Simulation
LRO
Maneuver Planning Process
• Predicted Duty Cycles
• Attitude Performance
Preliminary
Plan
Final
Plan
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 249

Maneuver Team Staffing Plan
• From Launch through LOI sequence (~10 days)
– Two 12 hr shifts per day (2 people per shift)
– May reduce to 1 shift between MCC-1 and LOI-1 (nominal plan)
• A Flight Dynamics Officer (FDO) will be resident in the LRO MOC during
critical maneuver support periods (i.e. maneuver events)
– FDO will act as “eyes & ears” in MOC to facilitate contingency support
– FDO will have access to LRO workstation to view maneuver related telemetry
• All other support (MOI’s and SK’s) is as required to support maneuver
planning process
– No day-to-day operations support
– Emergency contact information available to MOC
• Currently negotiating for AGI STK support
– Post-separation, early orbit
– On-site for critical maneuver
– On-call for other times
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 250

Maneuver Team Training
• Supported many training exercises (both internal and external) to practice
procedures for
– Maneuver Planning (over multiple mission phases)
– Product Generation and Delivery
• Maneuver Team members have supported 18 internal simulations and 10
Project simulations (MOC & MR)
• Team will conduct weekly (at minimum) simulations from now until launch
• Support hours for Maneuver Team are listed below
Simulation Support Hours
Beckman Folta Lamb Mesarch Richon
Internal 43 46 44 79 40
Project Level 75 24 55 101 37
Total 118 70 99 180 77
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 251

Maneuver Team Procedures
• Maneuver procedures have been developed and documented in the
Maneuver Team Handbook (451-HDBK-001281)
• The Handbook covers STK configuration and procedures for designing and
executing the LRO maneuvers
• Procedures cover
– Orbit to Maneuver Team OD deliveries
– Maneuver planning (ranges from MCC-1 to LOI to MOI to SK maneuvers)
– LOI-1 Contingencies
– Product Generation & Delivery
– Maneuver Reconstruction & Calibration
– Propellant Bookkeeping
• Matrix mapping procedures into simulation support is in backup charts
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 252

Maneuver Team Readiness
• Maneuver Team readiness per procedure is
being defined on a 5-point scale
– 1: Never Used Procedure
– 2: Runs Procedure with Assistance
– 3: Runs Procedure Nominally
– 4: Runs procedure with some troubleshooting
capability
– 5: Expert
• 100% readiness in a procedure equates to
– 2 Analysts at Level 5
– 1 Analyst at Level 4
– 2 Analysts at Level 3
• Based on this requirement, the overall
Maneuver Team Readiness is at 74%
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 253

LCROSS Impact Support
• LRO will be in its 50 km mission orbit at the time of LCROSS impact
• LRO will position itself past the impact point at the time of LCROSS impact
– This is to minimize the effect of flying through the LCROSS debris cloud
• LRO plans to alter its stationkeeping maneuvers to help with phasing LRO
with respect to the LCROSS impact event
• Data required from LCROSS includes
– Target Impact Point and Date/Time of Impact (changes as function of launch
date and possible during launch window)
– Predicted ephemeris
– Predicted maneuver schedule
• Preliminary analysis was performed during Summer of 2008 to check ability
to phase LRO with respect to simulated LCROSS Impact
– No showstoppers identified
• Further analysis using real LCROSS trajectory data is pending
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 254

Orbit Team Status
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center

Orbit Support Requirements
• Orbit Determination Requirements
– Daily Navigation OD using S-band tracking data
Predictive ephemeris requirement in lunar orbit is 800 m after 84 hours
Definitive ephemeris is 500 m RSS and 18 m radial
Tracking arcs broken at maneuvers and momentum unloads
– Post-maneuver OD using S-band tracking data
Goal: update acquisition data and MOC products following maneuvers
In mission orbit, two orbits of data will be used for post-maneuver OD estimation.
– Reprocessing of definitive OD using S-band and laser tracking data
Performed twice: following first gravity model update (as late as L+6 months) and
following the 1-year nominal mission orbit
Uses updated lunar gravity model provided by LR team
Goal is 50 m RSS, 1 meter radial
• Mission Product Generation
– Schedule
MOC External ICD defines daily, weekly, and monthly schedules for product updates
• Support requirements documented in Mission Support Plan (FDF-178-016)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 256

Orbit Team Staffing Plan
• From Launch through end of LOI sequence (~10 days)
– Three 8 hr shifts per day (minimum of two people per shift)
– Team members will support 24/7 through LOI unless released
• All other support is as required to support OD and product generation
– Standard support is to deliver updated products by noon daily
– Post-maneuver products will be generated and delivered following postmaneuver
OD
– Daily OD and product generation is automated
– Multi-mission support staff available during business hours and critical events
– Emergency contact information available to MOC at all other hours
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 257

Orbit Team Training
• Training of Orbit Team Staff
– Team leads have been supporting LRO since 2006 and developed training
material for other team members
– Team members support other FDF missions; trained for specific LRO support
– Team has had regular weekly training since summer of 2008 in exercises
designed by the team leads
• All procedures documented in Orbit Team Handbook (MOMS-FD-UG-0411)
• Project Simulation and Mission Rehearsal support
– Sim-01, 02, 03, 04, 05, 07, 08, 10, 11, 12, 15, 16, 17, 18, 24, 26, 27, 29, 30
– MR-1, 2, 4
• Upcoming support
– Sim-06, 13, 22, 25, 26
– MR-3, 5
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 258

Orbit Team Readiness
• Orbit Team readiness per procedure is being defined on a 5-point scale
– 1: Never Used Procedure
– 2: Runs Procedure with Assistance
– 3: Runs Procedure Nominally
– 4: Runs procedure with some troubleshooting capability
– 5: Expert
• Required: one person at level 5 and one at level 3 for each shift
• Goal: all staff at level 4 by launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 259

Tracking Data Evaluation
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center

Tracking Station Certification
• The SCN provides continuous S-band tracking (Doppler and Ranging)
through lunar orbit insertion and for at least 30 minutes per LRO lunar orbit
– Ranging tracking data has a required accuracy of 10 meters (1 sigma), and
range measurements are collected at least once every 40 seconds
– Doppler tracking data requirements vary by station and require all stations to use
a 5 second integration period
WS1 Doppler accuracy 1 mm/s (1 sigma)
USN Doppler accuracy 3 mm/s (1 sigma)
• Five new or upgraded stations required certification for LRO support
– Four modified USN sites at Dongara, South Point, Kiruna, Weilheim
– One new GN station at White Sands (WS1)
• Certification requires 5 consecutive passes that meet Ranging and Doppler
requirements on valid “targets of opportunity”
– USN Ranging certification completed with Landsat-5
– WS1 Ranging certification completed with TDRS-7
– USN and WS1 Doppler certification completed with THEMIS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 261

USN Certification Results
• The four USN sites achieved required Ranging and Doppler accuracies
• Results documented in USN Tracking Data Certification (FDF-30-024)
USN Hawaii – Landsat-5
Ranging Residuals from 5/27/08
USN Hawaii – THEMIS
Doppler Residuals from 6/23/08
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 262

WS1 Certification Results
• Ranging certification completed using
TDRS-7 as target of opportunity
• Tighter Doppler requirement (1 mm/s)
required additional analysis because
requirement could not be met due to
contribution from THEMIS spin
– Doppler data collected at rate of 1 data
point every second (1:1)
– Spin effect analytically removed using a
Fast Fourier Transform
– Moving average filter then used to
reduce sampling to 1:5 rate
• Results documented in WS1 Tracking
Data Certification (FDF-30-025)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 263

TDE Team Support
• Monthly proficiency passes on each of the certified stations have been
required and are required through launch
– Goal is to show that no station changes have been made that impact data quality
• The team is responsible for real-time tracking data evaluation support
through launch and early orbit and lunar orbit insertion maneuvers
– Detailed support information in FDF LRO Mission Support Plan (FDF-178-016)
• No LRO unique training required
– Six team members fully trained and available to support LRO
• Team is also supporting testing for three-way tracking demonstration
– Three-way LRO tracking requested by Constellation Program
– New FDF automation handles large quantities of three-way data
– Legacy GN sites will take three-way data during the LRO early mission
– Demonstration has no impact to FDF LRO support
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 264

Flight Dynamics Status Summary
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center

Summary
• All documentation has been released
– Minor edits expected in MSP and Maneuver and Orbit Team Handbooks
– Minor edits possible in FDF-LRO GS Operations Agreement (DSN products)
• No open action items from previous reviews or from simulation support
• Current issues and risks
– Closed-loop maneuver planning process has not been completed, as FlatSat
updates have not been provided by the MOC for the final maneuver plan
Planned for MR#5
• Upcoming schedule
– Division Operations Readiness Review
– Continued internal simulations and project simulation support
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 266

FDF Backup Material
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 267

ΔV Budget
Maneuver ΔV (m/s)
3 sigma
Notes
MCC-1 Eng 2 Tests ACS behavior
MCC-1 14 Critical Maneuver: Corrects 3-sigma LV dispersions
LOI-1 Eng 8 Tests ACS behavior
LOI-1 571 Critical Maneuver: Worst case launch day
LOI-others 360 Total of 4 Maneuvers
MOI 56 Total of 3 Maneuvers
SK 162 One pair every 27 days
Margin & Extended Mission 85
Total 1258 CDR ΔV budget
Dry mass reductions 55 Added dV from updated dry mass
Total 1313 Flight ΔV budget
Margin & Extended Mission 140 Flight margin
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 268

Maneuver Product Deliveries
Maneuver Preliminary
Maneuver Plan
Final
Maneuver Plan
Post Mnvr
Report
Thruster
Cal Report
MCC-E -11 hrs -3 hrs N/A N/A
MCC-1 Delivered with
MCC-E plan
Delivered with
MCC-E plan
LOI-E -11 hrs -3 hrs N/A N/A
LOI-1 Delivered with
LOI-E plan
Delivered with
LOI-E plan
LOI-2 -11 hrs -5 hrs +6 hrs +20 hrs
LOI-3-5 -11 hrs -5 hrs +6 hrs +20 hrs
MOI-1 -48 hrs -24 hrs +6 hrs +20 hrs
MOI-2-3 -48 hrs -6 hrs +6 hrs +20 hrs
SK-nn -72 hrs -24 hrs +6 hrs +48 hrs
Notes
+6 hrs +48 hrs MCC-1 occurs 2 hours
after MCCE
+6 hrs +20 hrs LOI-1 occurs ~6.5
hours after LOIE
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 269

Procedure Mapping
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 270

Detailed Timeline for MCC and LOI
Complete Final OD Processing for use in Preliminary Maneuver Plan
OT
Create MT Preliminary Maneuver Plan Products
MT
Create OT Preliminary Maneuver Plan Products
OT
Create AGS Preliminary Maneuver Plan Products
AGS
MOC Conducts Maneuver Simulation
MOC
Create MT Final Maneuver Plan Products
FDF to MOC Delivery
MOC to FDF Delivery
Create OT Final Maneuver Plan Products
MT OT
Create AGS Final Maneuver Plan Products
-14h -13h -12h -11h -10h -9h -8h -7h -6h -5h -4h -3h -2h -1h MCC-E/LOI-E
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 271
AGS
MOC Prepares for Maneuver
MOC

Network and Voice Communications
LRO Flight Operations Review – Section 8.0
NASA’s Goddard Space Flight Center
Jim Clapsadle
Deputy Ground System & Operations Lead
Information System Security Official

Agenda
• LRO Data Communications
• Mission Data Flows
• Network and Voice Circuit testing and plans
• Pre-Launch Networks
• Voice Lines for Launch and Nominal Mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 273

Data Communications
• All data communications links verified in tests/simulations
• Restricted IONet connected to MOC subnet for all functions
– RIONet direct connectivity to:
WS1, USN & DSN
BMOC
Mini-RF SOC
– RIONet to Closed IONet connectivity for:
SN
– RIONet to Open IONet connectivity for:
Flight Dynamics Facility & White Sands Scheduling
Pathway to non-operational networks:
– CNE (LEND GSFC SOC, LOLA SOC, Laser Ranging, CDDIS)
– Internet (LAMP SOC, CRaTER SOC, LEND UA SOC)
– PIP (KSC, Diviner SOC, NAIF/PDS)
– Abilene (LROC SOC)
• MOC Facility provides connectivity via CNE for access to Internet, email,
etc.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 274

LRO Mission Data Flows
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 275

Pre-Launch and Initial Acquisition
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 276

Voice Communications
• All voice communications links verified and ready for launch except
for shared voice lines at KSC
• Voice communications among LRO MOT and supporting elements via
Goddard Voice Distribution System (VDS)
– NISN provided voice equipment and lines in MOC, BMOC, and LSR
– Provides communication between MOC, BMOC, LSR, Space Communications
Network Elements, Flight Dynamics, KSC
Black phone teleconference used for SOCs
– DKS units provided for each console position for the operations and launch
support areas
– Select circuits at KSC only provided to mission next in queue to launch
• Anticipating transition to MOVE voice system, after transition to normal
operations
– Have already provided information requested to support the transition
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 277

Voice Matrix
Title Voice Loop ID Purpose MOC LSR FDF WS1 DSN USN NOM KSC
LRO Mission Ops (Prime) SCAMA 280 Primary voice net for MOT and ground network coordination T/L T/L T/L T/L T/L T/L MON
LRO Mission Ops
(Backup)
Systems Voice Loop
(Eng 1)
Flight Director Loop
(Eng 2)
Flight Dynamics Loop
(Eng 3)
Operations Team Voice
Loop
(Eng 4)
Backup Loop
(Eng 5)
Subsystem Loop
(Eng 6)
KSC‐GSFC System Voice
Loop
KSC‐GSFC Subsystem
Voice Loop
KSC‐GSFC Management
Voice Loop
LRO/LCROSS
Communications
Launch Vehicle/KSC
Launch Cord. Loop
SCAMA 281
Backup voice net for MOT and ground network coordination. During
Early Mission, plan to tie in SOCs on teleconference line to SCAMA 281.
CCL 79 Assigned to either the LRO systems or ME position. T/L T/L T/L
CCL 80
CCL 83
CCL 54
Flight Director Loop ‐ Used only by the flight director or any
communications with the flight director T/L T/L T/L
Flight Dynamics Voice Loop ‐ Used by FDF facility to communicate with
the MOC. Also used by FiDO to talk to FDF during maneuvers. T/L T/L T/L
Offline voice line, used by the MOT to coordinate tasks. Should not be
used for real‐time activities with the orbiter. Can be used to call for help
with MOC problems/requests.
T/L T/L T/L T/L T/L MON
T/L T/L
CCL 67 Backup voice net can be used as assigned by the flight director. T/L T/L
CCL 73
SCAMA 18
SCAMA 30
SCAMA 32
Voice network used by the LSR for subsystem to subsystem
communications. LRO system position will monitor voice loop.
KSC ‐ LRO System Voice Loop, used by systems and Flight Director for
communication during ground testing and pre‐launch activities between
the GSFC and KSC.
KSC ‐ LRO Subsystem Voice Loop, used for subsystem to subsystem
communication during ground testing and pre‐launch activities between
the GSFC and KSC.
KSC ‐ LRO Management Voice Loop. Used by the Mission Director, KSC
LRO Systems, and Flight Director for poll and status information during
pre‐launch count.
T/L T/L
T/L T/L T/L
T/L T/L T/L
T/L T/L T/L
SCAMA 286 LRO/LCROSS Mission Coordination Loop, used for KSC only T/L T/L T/L
SCAMA 287 KSC ‐ Launch Coordination Loop MON MON MON MON
LCC Monitor Loop SCAMA 282 LCC Monitor and Flight Commentary MON MON MON MON
KSC‐LV Anomaly Loop SCAMA 283 KSC Anomaly Voice Net MON MON MON MON
MET NET Loop SCAMA 200 MET Network (Range Weather Officer) MON MON MON MON
KSC Range Operations
Loop
SCAMA 285 KSC Range Operations MON MON MON MON
NASA Launch Manager
Loop
SCAMA 284 NASA Launch Manager Loop MON MON MON MON
T/L = Talk‐Listen (Full Communication) MON = Monitor Only
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 278

Summary
• All data communications in place and verified through, interface testing,
Mission Readiness Testing, Operational Readiness Testing, and Mission
Rehearsals
• All nominal operations voice connections in place and verified through,
interface testing, Mission Readiness Testing, Operational Readiness
Testing, and Mission Rehearsals
• Final voice circuits at KSC to be tested as soon as they are released to LRO
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 279

Network & Voice Communications
Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 280

Data Communications
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 281

PVAN Processing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 282

Overview of ASO Data Transports
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 283

ASO Building 1 Control Room
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 284

Science Data Management Overview
LRO Flight Operations Review – Section 9.0
NASA’s Goddard Space Flight Center
Stan Scott
LRO Science Data Manager

Stanford
University
•
LRO SOCs and PDS Nodes/Data Nodes
Jet Propulsion
Laboratory
University of
Hawaii
University of
Maryland
RADIO
SCIENCE
Navigation and
Ancillary
Information
Facility (NAIF)
Planetary Science
Institute
Cornell
University
ENGINEERING
SMALL BODIES
SETI Institute
ATMOSPHERES
RINGS
New Mexico
State
University
GEOSCIENCES
PLANETARY
PLASMA
INTERACTIONS
IMAGING
United States
Geological Survey
(Flagstaff, AZ)
University of
Arizona
Washington
University
Arizona State
University
Jet Propulsion
Laboratory
Arizona State
University
University of
Arizona
University of
California at
Los Angeles
Southwest
University
(San Antonio, TX)
University of
Iowa
DIVINER SOC
@JPL&UCLA
LEND SOC
@UA, GSFC,
& IKI
LOLA SOC
@GSFC
Mini-RF SOC
@JHU APL
CRaTER SOC
@BU
LAMP SOC
@SwRI
LROC SOC
@ASU
GSFC/MOC
& FDF
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 286

Data Delivery Plan
SOCs deliver 3-6 month old, validated, initial version of LRO data to PDS every 3 months
(MRF: every 6 months), starting 6 months after end of Commissioning (Initial Operations)
Notes: 1) Subsequent versions and derived data products due to PDS in next 3-month delivery after
creation and validation.
2) Creation of subsequent versions and derived data products is on a time scale
commensurate with the level of data processing required.
3) Final data processing and release can not exceed 6 months from end of
primary mission or extended mission, as applicable.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 287

SOC Deliverables/Document Status
Document/Activity RS CRaTER DLRE LAMP LEND LOLA LROC MRF
SOC Requirements L
SOC-PDS ICD L&P
SOC DM&AP L
SOC Test Plan L
SOC Design Peer Review (Note 2) B
SOC Risk Assessment Plan (RAP) N Notes 4&5 Note 4
SOC IT Security Plan (SP) N Notes 4&5 Note 4
SOC Contingency Plan (CP) N Note 5
EDR Data Product S/W I/F Spec (SIS) P
EDR Archive Volume SIS P
EDR SIS Peer Review P
RDR Pipeline Data Product SIS P
RDR Pipeline Archive Volume SIS P
RDR Pipeline SIS Peer Review P
SOC Requirements Verification Matrix L
RDR Non-Pipeline Data Product SIS P Note 6 Note 6
RDR Non-Pipeline Archive Volume SIS P Note 6 Note 6
RDR Non-Pipeline SIS Peer Review P Note 6 Note 6
Notes:
1. RS is requirement source (L= LRO Project;
P=PDS; N=NASA; B=IRB suggestion)
2. SOC Design Review was not a Deliverable
3. MRF matched Instrument Team Deliverables
4. JPL SOC in JPL Plan & LOLA SOC in GSFC Code 600 Plan
5. UCLA SOC delivered RAP, SP, & CP per new contract (2/09)
6. Non-Pipeline SISs deferred until after launch
STATUS COLOR SCHEME: = Document/task completed
= Work remains
= Behind schedule
= Not applicable
S. Scott 3/5/2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 288

SOC – PDS Testing
Archive Test 1: Interface Mechanism
Checklist
Done
Test
Done
Report
Date
CRaTER & PDS PPI 2/25/08 2/25/08 3/4/08
DLRE & PDS GEO 2/25/08 2/25/08 3/4/08
LAMP & PDS IMG 2/11/08 3/10/08 3/4/08
LEND & PDS GEO 2/25/08 2/25/08 3/4/08
LOLA & PDS GEO 2/25/08 2/25/08 3/4/08
LROC & PDS IMG 2/11/08 3/10/08 3/4/08
MRF & PDS GEO 2/28/08 2/28/08 3/4/08
Archive Test 2: Archive Completeness
Checklist
Done
Test
Done
Report
Date
CRaTER & PDS PPI 3/10/08 4/7/08 4/14/08
DLRE & PDS GEO 3/10/08 3/20/08 4/14/08
LAMP & PDS IMG 3/10/08 4/14/08 4/14/08
LEND & PDS GEO 3/10/08 3/12/08 4/14/08
LOLA & PDS GEO 3/10/08 4/7/08 4/14/08
LROC & PDS IMG (Archive Test 2 combined with Test 3) 7/28/08 7/28/08 8/26/08
MRF & PDS GEO 3/10/08 3/19/08 4/14/08
Archive Test 3: Simulate Actual Delivery; PDS Validates
Checklist Test Report
Delivery
Done Done Date
CRaTER & PDS PPI 6/13/08 6/16/08 7/31/08
DLRE & PDS GEO 5/19/08 5/19/08 7/31/08
LAMP & PDS IMG 5/19/08 7/22/08 7/31/08
LEND & PDS GEO 5/19/08 7/14/08 7/31/08
LOLA & PDS GEO 4/22/08 7/14/08 8/26/08
LROC & PDS IMG 7/28/08 7/28/08 8/26/08
MRF & PDS GEO 5/19/08 5/19/08 7/31/08
Note: Green= finished; Yellow= underway; Red= not started/finished S. Scott 3/6/2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 289

Future Work
• SOC teams to complete requirements verification testing when possible
• SOC teams to continue participation in LRO GS&O Sims, MRs, ORTs, etc.
• SOC-PDS teams to complete revision of SIS documents to remove TBD Items (prior
to data deliveries to PDS)
• LOLA & LROC teams to remove SIS TBD Items prior to data availability via their
respective PDS Data Nodes
• SOC (& PDS) operations status reporting & frequency are TBD, may include:
– SOC teams’ LCROSS support
– SOC teams’ removal of SIS TBDs
– SOC teams’ PDS data delivery preparation
– PDS teams’ SOC delivery validation & public availability of new data
– SOC-PDS teams’ non-pipeline RDR SIS preparation and peer review
– Issues/problems affecting SOCs and/or PDS Nodes
• LDWG to continue meeting with TBD frequency (monthly?) during LRO mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 290

Summary
• SOCs’ Documentation Deliveries successfully completed
• SOC - PDS Interface Testing successfully completed
• All applicable Software Interface Specifications (SIS) have completed PDS
Peer Reviews
• SOC teams have fully participated in LRO GS&O testing program
• SOCs’ Requirements Verification nearly complete
• Schedule for SOC data deliveries to PDS is well-defined and included in all
SOCs’ DM&AP and SOC-PDS ICD
• LOLA and LROC SOCs will host PDS Data Nodes for quick public access to
their instrument data products
• SOCs are well positioned to perform
– Instrument command generation & health and safety monitoring
– Ingest of data from MOC
– Instrument data processing
– Provision of data products to PDS in timely fashion
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 291

Mini-RF Science Operations Center
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center
9.1
Matt Hillyard
Mini-RF Instrument Engineer
Johns Hopkins University / Applied Physics Laboratory

Agenda – Mini-RF SOC
• SOC Functions
• SOC Peer Review Status
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 293

SOC Facility
Mini-RF SOC Functions
Calibration Processor
SAR Processor
Burst mode
Continuous mode
Bistatic mode
Data Archiving
Level 3 Product Generation
SAR Mosaic Generation
Sandia Labs Level 3:
Topography Mosaic
Data
Task Protocol
Planning & Commanding
Visualization Tools
Planning Interface
Command Sequence Generation
Command Tracking
Coverage Mapping
Data
Catalog
Data
Ancillary Data
Data Pipeline
Goddard Interface
Task Scheduler Cataloging
Pre-Processing
User Interface
Operations
Opportunity
Command
Files
Instrument Cmd Protocol
Instrument Tlm Protocol
Ancillary Data
Opportunity TImelines
LRO
MOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 294

Peer Review Status
Review Level Date Current Status
Mini-RF Project SRR Chandrayaan-1 / LRO January 2005 Passed; AIs
Closed
July 2006
Mini-RF POC PDR Chandrayaan-1 / LRO Passed; AIs
Closed
Mini-RF POC CDR Chandrayaan-1 / LRO January 2007 Passed; AIs
Closed
LRO MOR Mini-RF SOC: LRO September 2007 Passed; AIs
Closed
Mini-RF POC
Operations TIM
LRO Flight
Operations Review
LRO SOC Readiness
Review
Chandrayaan-1 / LRO September 2007 AIs Closed
Mini-RF SOC: LRO March 2009 You Are Here
Mini-RF SOC: LRO March 2009 March 26th
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 295

• Staffing Plan
Operations Concept Overview
• Organization Chart
• Manual / Automated Ops Activities
• SOC Facilities
• Operations Systems / Data flows
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 296

FTE's
3.50
3.00
2.50
2.00
1.50
1.00
0.50
Feb-
05
Staffing Plan
Mar-
05
Apr-
05
May-
05
Jun-
05
Jul-
05
Aug-
05
Operations Science Systems Admin
Sep-
05
Oct-
05
Nov-
05
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 297
Dec-
05
Jan-
06
Feb-
06
Mar-
06
Apr-
06
May-
06
Jun-
06
Jul-
06
Aug-
06
Sep-
06

Mini-RF SOC Organization
SAR
SAR
Processor/
Processor/
Calibration
Calibration
Processor
Processor
Science
Science
Team
Team
Liaison
Liaison
Ben Bussey (APL)
Ben Bussey (APL)
Marzban Palsetia (Vexcel)
Marzban
Kuhn Zang
Palsetia
(Vexcel)
(Vexcel)
Kuhn Zang (Vexcel)
Data
Data
Archiving
Archiving
Mike Reid (APL)
Mike Reid (APL)
Sustaining
Sustaining
Engineering
Engineering
Matt Hillyard (APL)
Stuart
Matt
Nylund
Hillyard
(APL)
(APL)
Stuart Nylund (APL)
SOC
SOC
IPT
IPT
Dave LaVallee (APL)
Dave LaVallee (APL)
Systems
Systems
Administration
Administration
Gabrielle Griffith (APL)
Gabrielle
Mike Mejia
Griffith
(APL)
(APL)
Mike Mejia (APL)
Data
Data
Pipeline
Pipeline
David Carl (APL)
David Carl (APL)
Higher-Level
Higher-Level
Data
Data
Products
Products
Ben Bussey (APL)
Jack
Ben
Jakowatz
Bussey
(Sandia)
(APL)
Jack Jakowatz (Sandia)
Planning
Planning
&
&
Commanding
Commanding
Joe Skura (APL)
Joe Skura (APL)
Radar
Radar
Systems
Systems
Keith Raney (APL)
Keith Raney (APL)
SPICE
SPICE
Support
Support
Scott Turner (APL)
Lil
Scott
Nguyen
Turner
(APL)
(APL)
Lil Nguyen (APL)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 298

LRO
MOC
Command Generation Process
Operations Opportunity
Operations Activity Request
Command Timeline
Daily Command Load Report
Legend
Automated Process
Manual Process
Generate
Opportunities
Generate
Commands
Mini-RF SOC
MOC I/F
Command
Verification
MOC I/F
MOC I/F
Planning & Commanding
Subsystem
Command
Verification
Select
Opportunities
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 299

Planning & Commanding Tool
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 300

LRO
MOC
Telemetry Processing
Instrument
Telemetry
Protocol
Ancillary Data
SOC Facility
Data Pipeline
Goddard Interface
Task Scheduler Cataloging
Pre-Processing
User Interface
Catalog
Data
Calibration Processor
Sandia Labs Level 3:
Topography Mosaic
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 301
Data
Data
Task Protocol
SAR Processor
Burst mode
Continuous mode
Bistatic mode
Level 3 Product Generation
SAR Mosaic Generation
Data Archiving
Data
PDS

Mini-RF SOC Facility
• Physical Facility
– On JHU/APL Campus, Laurel, MD
– Located in a secured facility
– Area accessed by key card system
Separate access list for building access and server / network access
Card access disabled when person leaves project
Access reviewed annually
– Access approved by Project Manager.
– Visitors are required to sign log and be escorted at all times
Logs removed and reviewed weekly
– UPS /Generator provides backup power
• Under the Mini-RF SOC IT Security Plan 7420-9010
• Big Brother
– System monitoring tool for critical services and environmental conditions
– Checks Status every 5 minutes: Connection, CPU and Disk load, Services, Memory
– Website Interface Alerting
– Emails to SOC Lead, Science Team, Space Department Unix Team and Space Department
Ground Systems Team
• SOC Shared with Chandrayaan-1 Mini-RF
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 302

SOC
Internet
To External
Users
SOC Facilities
Firewall
Network – LRO Mini-RF
APL Internal
Network
Instrument
DMZ
Science
DMZ
Visitor DMZ
APL IP
Addresses
Firewall
NASA
Restricted
IONet
NASA IP
Addresses
Firewall
Internet
LRO
MOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 303
To
JPL

SOC Facilities
LRO MOC
Physical Block Diagram – LRO Mini-RF
d i g i t a l
d i g i t a l
APL SOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 304

Operations Systems / Data Flows
P
D
S
SOC
Planning &
Commanding
Data
Archiving
Mini-RF Instrument subset Spacecraft
Science Data
subset
Receiver
Recorder &
Science Data
Firmware
Downlink
Legend
Control
Processor
Software
Level 2-
Processing
Level 3+
Processing
Mini-RF Systems
GSFC Systems
Housekeeping Data
Commands
Data Pipeline
Data
Repository
Housekeeping
Telemetry
Downlink
Command Table Loads
Commands
Science Data
Housekeeping
Ground
System
Ground Station
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 305
LRO
MOC

Software / Tools Test Status
Planning & Commanding
DataPipeline
Subsystem Simulations Mission
SIM #3
SIM #8
SIM #3
SIM #8
Rehearsal
MR #1
MR #4
MR #1
MR #4
Future
Test Needed
Science and Ancillary Data
In
Catalog SIM #26
Process*
SAR Processor
Calibration Processor
PDS Archiver
PDS Test
1,2,3
Note: SIM-29 and MR#4 did not generate complete science and ancillary data sets.
MR#1 ancillary data recently received.
In
Process*
In
Process*
SIM #26
SIM #26
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 306

• SOC software
Sustaining Engineering
– Software under Configuration Management using Subversion
– Problem tracking system in use
– CCB approval required for changes
• Flight Software
– NO flight software loads anticipated
– Event-driven Parameter loads and Waveform loads as needed
– Brassboard testing of all proposed modifications
– CCB approval required for changes
• Subcontracts
– Vexcel (source code in escrow)
– Raytheon
– Northrop Grumman
– BAE
– Sandia National Laboratories
– ATC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 307

Testing
Requirements Verification Matrix 1 of 10
ID Requirement Test Method Configuration
Item
1.1.1 The POC shall provide the user with a graphical representation of
predicted spacecraft position and orientation, based on predicted
ephemeris data
1.1.2 The POC shall provide the user with a graphical representation of
swath location
1.1.3 The POC shall provide the ability to zoom-in on regions of the
coverage displays
1.2 The POC shall provide the user with a list of opportunities to take
observations
1.2.1 The POC shall determine times during the orbital phase when the
spacecraft can roll and point the radar antenna towards Earth and
communicate with antenna sites at Greenbank and Arecibo
1.3 The POC shall allow the user to select from the list of
opportunities
1.4 The POC shall provide a user interface for non-real-time
commanding from within the POC.
1.5 The POC shall automatically generate command mnemonics (in
accordance with Ground ICD) and associated parameters based on
user-selected opportunities
1.6 The POC shall forward instrument command mnemonics and
associated parameters to ISSDC/MOC (in accordance with the
ISSDC-POC ICD / LRO MOC-POC ICD) (per SRR: The POC shall
forward Science Team command sequences to ISSDC)
*Will be implemented and verified prior to LRO launch
Inspection
Demonstration
Demonstration
Demonstration
Demonstration
Demonstration
Demonstration
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Operational
Operational
Operational
Operational
Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 308
Test
Test
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding/
ISSDC interface
Type Tested
*Future
build
Operational
Operational
Operational
Interface

Testing
Requirements Verification Matrix 2 of 10
ID Requirement Test Method Configuration
Item
1.7.1 The POC shall verify that each command set generated comprises
a combination identified by the Systems Engineer as posing no
danger to the instrument
1.7.2 The POC shall provide password protection for the commanding
interface.
1.7.3 The POC shall provide an option to prevent commands that
activate the transmitter during I&T (but not in every case. Note
that this is a safety issue, so must prevent accidental commanding
of the transmitter on).
1.8 The POC shall perform a predictive calculation such that the
telemetry resulting from commanding will not exceed the recorder
capacity and notify the user if such is predicted to occur
1.12.2 The POC shall be capable of calculating the CRC over any portion
a ground-based mapping of the EEPROM memory. (i.e. given a
"start" and "stop" byte location
1.12.3 The POC shall be capable of calculating the CRC over a groundbased
mapping of the loaded memory image
1.12.4 The POC shall ensure that any planned command sequence does
not produce more science data than is allowed by the spacecraft
interface
1.12.5 The POC shall verify that planned command sequences produce
science data in a quantity that is less than the allocated Mini-RF
recorder space
Demonstration
Inspection
Demonstration
Demonstration
Demonstration
Demonstration
Analysis
Demonstration
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Type Tested
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 309

Testing
Requirements Verification Matrix 3 of 10
ID Requirement Test Method Configuration
Item
1.13 The POC shall obtain Planned Timelines from MOC and process
them for use in creating the planned commanding schedule
2.1 The POC shall store metadata for produced data products in a
database with the associated files stored in a directory structure,
through final PDS delivery
2.2 The POC shall store metadata for delivered command sets in a
database, with the associated files (information retained to include
no less than all command-related information sent; waveforms
specified; user-specified parameters used in generation of
command set, etc.) stored in a directory structure, through final
PDS delivery
2.3 The POC shall store metadata for (received and produced)
ancillary data in a database, with the associated files stored in a
directory structure, through final PDS delivery
2.4.1 The POC shall maintain a EEPROM memory image on the ground
2.4.2.1 The POC shall calculate and store the expected CRCs
2.4.2.2 The POC shall log any errors detected between expected and
actual downloaded CRCs, and generate an alarm
2.5.1 The POC shall retain unique version identification for each data
product and command set produced.
Demonstration
Planning &
Commanding
Type Tested
Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 310
Test
Test
Test
Demonstration
Demonstration
Demonstration
Data Mgt/
Data Pipeline
Planning &
Commanding
Data Mgt/
Data Pipeline
Planning &
Commanding
Planning &
Commanding
Planning &
Commanding
Operational
Operational
Operational
Operational
Operational
Operational
Demonstration All Operational

Testing
Requirements Verification Matrix 4 of 10
ID Requirement Test Method Configuration
Item
3.1.1.1 The POC shall receive raw instrument science telemetry data from
ISSDC/MOC (in accordance with the ICDs)
3.1.2.1 The POC shall receive health and safety telemetry (housekeeping)
from ISSDC/MOC (in accordance with the ICDs)
3.1.2.2 The POC shall decommutate (LRO only) and limit check all
housekeeping data
3.1.4 The POC shall provide automated telemetry processing to
automate the data pipeline process, initiating each stage when the
requisite set of data are available
3.1.5 The POC shall trigger an alarm when automated processing is
delayed because data required to operate the data pipeline have
not become available within an adaptable threshold of time
3.1.6.1 The POC shall perform a check of the data files to verify that they
are correctly formatted (based on packet size recorded in the
CCSDS header), with no gaps or duplicates
Demonstration
Note: SIM-29 and MR#4 did not generate complete science and ancillary data sets.
MR#1 ancillary data recently received.
Data Pipeline/
ISRO Interface
Interface
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 311
Test
Data Pipeline/
ISRO Interface
Type Tested
In
process*
Interface
Test Data Pipeline Operational
Demonstration Data Pipeline Operational
Demonstration Data Pipeline Operational
Test Data Pipeline Operational

Testing
Requirements Verification Matrix 5 of 10
ID Requirement Test Method Configuration Item Type Tested
3.1.6.2.1 The POC shall log any errors detected in the Telemetry format
(based on packet size recorded in the CCSDS header), halt
processing (if error represents a nonreconcilable condition), and
generate an alarm
3.1.6.2.2 The POC shall log any gaps detected in Telemetry, and generate
an alarm
3.1.6.2.3 The POC shall log and remove any duplicates (telemetry is
determined to be duplicate where time, sequence count & APID
are duplicate) detected in Telemetry Screening
3.1.7.1 The POC shall correlate telemetry received to the initiating
command and retain such mapping in a database
3.1.7.2 The POC shall automatically generate an alarm when no telemetry
is received corresponding to an initiated command after an
adaptable threshold of time
3.2.1 The POC shall provide an interface to display instrument
housekeeping to the user in the POC
3.2.2 The POC shall provide automatic notification to designated points
of contact if a designated housekeeping value limit is exceeded
3.2.3 The POC shall provide password protection for data access.
Test Data Pipeline Operational None*
Test Data Pipeline Operational None*
Test Data Pipeline Operational
Test Planning &
Commanding
Demonstration
Inspection
Planning &
Commanding
Data Pipeline/
User Interface
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 312
Test
Data Pipeline/
User Interface
Operational
None*
Operational
Operational
Operational
Demonstration User Interface Operational
*Note: We need to create the test data from simulated data. Will be tested prior to launch.

Testing
Requirements Verification Matrix 6 of 10
ID Requirement Test Method Configuration Item Type Tested
3.2.5 The POC shall offer database access via an SQL-based interface
(in addition to the standard product access).
3.2.6 The POC shall provide the capability to display housekeeping
telemetry over the lifetime of the instruments.
3.3.1 The POC shall provide an interface for authorized users to access
data products
3.3.2 The POC shall make available a list of all gaps in data for a given
acquisition
3.3.3 The POC shall provide a utility for locating data from observations
taken based on selectable search parameters
3.3.4 The POC shall provide a utility displaying surface coverage of the
target, based on data from observations taken
3.3.5 The POC shall provide quick look of level 2 data products
generated by the SAR Processor, using the Vexcel-provided
viewer
3.3.7 The POC shall retain and make available a log of alarms generated
by the POC
3.3.8 The POC shall obtain As-Flown Timelines, catalog them and make
them available for user access
Inspection User Interface Operational
Demonstration
Demonstration
Demonstration
Demonstration
Planning &
Commanding
User Interface /
Vexcel
Data Pipeline/
User Interface
Data Pipeline/
User Interface
Plan &
Commanding
Operational
Operational
Operational
Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 313
Test
Demonstration
Data Pipeline/
User Interface
Data Pipeline/
User Interface
Operational
Operational
Demonstration VEXCEL Operational
Demonstration
Data Pipeline/
User Interface
Operational

Testing
Requirements Verification Matrix 7 of 10
ID Requirement Test Method Configuration Item Type Tested
3.4.1 The POC shall reformat the telemetry and ancillary data for
ingestion by the SAR processor. (format specified in Intra-POC
ICD)
3.4.2 The POC shall automatically invoke the SAR Processor upon
receipt and pre-processing of SAR telemetry (based upon APID),
and other data required to process the SAR telemetry. (protocol
specified in Intra-POC ICD)
3.4.3 The POC shall invoke the SAR Processor upon manual command
(will be done as needed to reprocess)
3.6.1 The POC shall be nominally capable of processing telemetry from
point of receipt of a complete data set to level 2 SAR and level 1
Scatterometry products within eight hours. (Note: scatterometry
applies to Chandrayaan-1 only.)
3.6.2 The POC shall plan to make Level 2 SAR and level 1 Scatterometry
products available with in two working days of complete data set
receipt. (Note: scatterometry applies to Chandrayaan-1 only.)
4.1 The SAR Processor shall process telemetry to Vexcel Level 0 (The
POC shall create Level 0 data)
4.2 The SPS system shall generate Level 1 data products from Level 0
STF data
4.3 The SPS shall generate Level 2 data products from Level 1 floating
point data (cross-product format)
4.4 The POC shall support generation of SAR mosaics, using STprovided
algorithm
Test Data Pipeline Operational
Test Data Pipeline Operational
Demonstration Data Pipeline Operational
Demonstration Data Pipeline Performance
Demonstration Data Pipeline Performance
Test SAR Processor Operational
Test SAR Processor Operational
Test SAR Processor Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 314
Test
Science Ops
Support
Operational

Testing
Requirements Verification Matrix 8 of 10
ID Requirement Test Method Configuration Item Type Tested
6.1 The POC shall support the Science Team in the generation of a
Data and Archive Management Plan
6.2 The POC shall support the generation of an ICD between the POC
and the PDS, in accordance with PDS guidelines
6.3 The POC shall generate the Software Interface Specification(s)
(SIS) specifying data products and their format for delivery to PDS
6.4 The POC shall deliver standard data products and ancillary data to
PDS. (in accordance with the Data Management & Archive Plan
and SIS)
6.5 The POC shall reformat all data in accordance with the Data
Management & Archive Plan and SIS
6.6 The POC shall respond to all PDS liens within three months of
receipt
7.1 APL shall provide a physical POC facility
7.2 The catalog (database & directory structure/files) and applications
of the POC shall be scheduled for a full backup each month and
an incremental backup each night
7.3 The POC facility shall offer storage to accommodate commands
sent, all data used in generating the command message files, all
instrument and related housekeeping, and all data used in
processing the telemetry
7.5 Access to POC equipment shall be controlled via badge access or
similar security measure
Inspection
Data Management/
Archiving
Operational
Inspection Data Archiving Operational
Analysis Data Archiving Operational
Inspection Data Archiving Operational
Analysis Data Archiving Operational
Analysis
Data Archiving/
Data Pipeline
Operational
Inspection Facility Operational
Inspection
Facility
Operational
Inspection Facility Operational
Inspection Facility Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 315

Testing
Requirements Verification Matrix 9 of 10
ID Requirement Test Method Configuration Item Type Tested
7.6 The POC facility shall automatically notify the identified contact
person via email if a specified alarm condition occurs
7.7 The POC facility shall include the hardware and applications
needed to support execution the POC software (as presented at
the PDR)
7.8.1 The POC facility shall include a web server
7.8.2 The POC facility shall include a relational database server
7.8.3 The POC facility shall include an SFTP server or equivalent to
facilitate secure file transfers (intended for science users rather
than transfer between the POC and ISRO)
7.9.1 The POC facility shall include AC power needed to operate the
hardware
7.9.2 The POC facility shall include an uninterruptible power supply
(UPS)
7.10 The POC facility shall include any climate control determined to be
needed to safely operate the hardware
8.1.1 The POC team shall present at the instrument System
Requirements Review
8.1.2 The POC team shall hold a POC Design Review
8.2.1 The POC shall provide a Users' Guide / Administrator's Guide.
Demonstration Facility
Inspection Facility
Operational
Operational
Inspection Facility Operational
Inspection Facility Operational
Inspection
Facility Operational
Inspection Facility Operational
Inspection
Facility Operational
Inspection Facility Operational
Inspection Reviews Operational
Inspection Reviews Operational
Inspection Documentation Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 316

Testing
Requirements Verification Matrix 10 of 10
ID Requirement Test Method Configuration Item Type Tested
8.2.2 The POC shall develop a POC Requirements Traceability Matrix
8.2.3 The POC team shall write an Intra-POC ICD
8.2.5 The POC team shall write Test Plan
8.2.6 The POC shall write a POC-specific SDP/CM Plan, complementing
the project-level SDP
8.2.7 The POC shall review/provide input to LRO’s Ground ICD
9.1 The POC shall include a calibration processor (requirements to be
derived)
9.2 The POC shall generate calibration reference data
9.3 The POC shall maintain calibration reference data
9.4 The POC shall maintain pre-flight calibration reference data
9.5 The POC shall maintain in-flight calibration reference data
Inspection Documentation Operational
Inspection Documentation Operational
Inspection Documentation Testing
Inspection Documentation Operational
Inspection Documentation Interface
Test Calibration Operational
Test Calibration Operational
Demonstration Calibration Operational
Analysis Calibration Operational
Analysis Calibration Operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 317

Instrument ICD Compliance
• Derived requirements from the LRO MOC-SOC ICD
– Tested Products
Mini-RF Command Timeline
LRO Beta Angle Predict File
Lunar Orbit Ascending and Descending Node Predicts
Predicted Lunar Ground Track File
Definitive Lunar Ground Track File
LRO Definitive SPICE SPK File
LRO Predictive SPICE SPK File
LRO Operations Activity Request
Mini-RF Load Files
Mini-RF Operations Activity Request
SPICE SCLK – Clock Correlation File
Mini-RF - Spacecraft HK Data File
Daily Command Load Report
Mini-RF HK Data Files
Mini-RF Raw Measurement Data Files
Mini-RF Real-time VC0 HK data
SPICE FK – Frame Kernels
SPICE Predicted CK (Predicted S/C Orientation)
SPICE Definitive CK (Definitive S/C Orientation)
Mini-RF HK Meta Summary Report
Mini-RF Measurement Meta Summary Report
SPICE Planetary SPK
SPICE LSK (Leap Second Kernel)
SPICE Generic PCK (Planetary Constants)
SPICE High Precision Lunar Orientation PCK
– Implemented Products awaiting testing
- FDF Reprocessed SPICE Definitive Ephemeris Data SPK Not needed before launch
- RTS Command Load Report Not received, test during SIM-26
- Mini-RF Operations Opportunity Not received, test during SIM-26
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 318

Summary
• Mini-RF SOC software developed, tested and under configuration
management
• Problem tracking system in use
• Active Configuration Control Board in place
• Operations Team experienced with LRO Mission Rehearsals, Mission
Simulations and Mission Readiness Tests
• LRO Mini-RF and Chandrayaan-1 Mini-RF share common SOC facility,
Operations Team and much software
• Lessons learned from Chandrayaan-1 experience applied
Mini-RF SOC is ready to support LRO launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 319

Mini-RF Strip Overlay
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 320
Image Credit: ISRO/NASA/JHUAPL/LPI/Smithsonian/Cornell
Uncalibrated Mini-RF data strip

Abbreviations and Acronyms
APL Applied Physics Laboratory
ARxEx Analog Receiver Exciter
CCB Configuration Control Board
CDR Critical Design Review
CM Configuration Management
CMD Command
DMZ De-militarized Zone
FSW Flight Software
GSFC Goddard Space Flight Center
JPL Jet Propulsion Laboratory
LRO Lunar Reconnaissance Orbiter
I/F Interface
IPT Integrated Product Team
MOC Mission Operations Center
MOR Mission Operations Review
Ops Operations
PDR Preliminary Design Review
PDS Planetary Data System
SAR Synthetic Aperture Radar
SOC Science Operations Center
SRR System Readiness Review
ST Science Team
TIM Technical Interchange Meeting
UPS Uninterrupted Power Source
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 321

Mini-RF SOC Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 322

Day in the Life for Planning & Commanding
Choose Operational
Timeframe
Display Opportunities
And Suggested Waveforms
Create Command Sequence
From Opportunities
User Clicks on Button
To Send Command File
Software Action
User Action
Read in Ephemeris Files
And Coverage Maps
Set Parameters For
Calibration and Data Taking
Format Command Sequence
To Command File
Command File Sent to MOC
If Problem,
Notify User
Enter Parameters
For Opportunities
Search for
Opportunities
Click on Button to Create
Command Sequence
User Reviews
Command File
Check MOC Command
Verification Message
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 323

Planning & Commanding Tool
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 324

CRaTER Science
Operations
LRO Flight Operations Review – Section
NASA’s Goddard Space Flight Center
9.2
Michael J. Golightly
Deputy Instrument Scientist/
CRaTER SOC Lead
Boston University

CRaTER Science Operations
• SOC Functions
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 326

CRaTER Science Operations
• SOC Functions
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 327

CRaTER SOC Operations Concept
SOC Functions
• Provide a secure network connection between LRO MOC and SOC
computer systems
• Ingest real-time CRaTER secondary science and housekeeping data and
make available to instrument team and investigators
• Receive instrument raw data and ancillary flight product files from the MOC
and move to appropriate storage locations
• Process raw instrument data into defined L0, L1, and L2 data products
• Maintain local archive of L0, L1, and L2 data products
• Submit L0, L1, and L2 data products to PDS PPI Data Node for permanent
archiving and public access
• Provide displays of appropriate measurement and housekeeping data for
use in instrument performance monitoring and trending
• Provide mechanisms for data access by distributed instrument and science
team
• Provide interface between CRaTER team and LRO MOT
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 328

CRaTER Science Operations
• SOC Functions
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 329

CRaTER SOC Operations Concept
Staffing Plan: Launch → LOI
• Prelaunch, Launch, Launch + 1
– SOC
L- 4 h → L+ 3 h: 1 staff member
After L + 3 hours: 1 staff member during normal business hours, on-call during non-business hours
– KSC
Science Team
– LRO MOC
N/A
– Home Institutions
Support engineers (MIT, Aerospace-El Segundo)
• Launch + 1 → LOI
– SOC
1 staff member during normal business hours, on-call during non-business hours
– LRO MOC
SOC staff member
Support engineer (MIT)
– Home Institutions
Science Team (BU, Aerospace-Chantilly): normal business hours, on-call during non-business hours
Support engineers (Aerospace-El Segundo): on-call
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 330

CRaTER SOC Operations Concept
Staffing Plan: LOI → End of Commissioning
• LOI End of Commissioning
– SOC
1 staff member during normal business hours, on-call during non-business hours
– LRO MOC — 1 st CRaTER calibration period
Science Team (BU)
– LRO MOC — all other periods
N/A
– Home Institutions
Science Team (BU, Aerospace-Chantilly): normal business hours, on-call during nonbusiness
hours
Support engineers (MIT, Aerospace-El Segundo): on-call
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 331

CRaTER SOC Operations Concept
Staffing Plan: Nominal Operations
• Nominal Operations
– SOC
SOC Operator
– 2 hours/d between 8:30 am - 5:30 pm, Mon-Fri
– on-call during non-business hours
Backup SOC Operator/SOC Staff
– LRO MOC
on request
– in office during normal business hours, Mon-Fri
– on-call during non-business hours
– Home Institutions
Science Team (BU, Aerospace-Chantilly): normal business hours, on-call during nonbusiness
hours
Support engineers (MIT, Aerospace-El Segundo): on-call
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 332

CRaTER SOC Operations Concept
SOC Organization Chart
Hire by end of
Spring ‘09 semester
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 333

CRaTER SOC Operations Concept
Manual/Automated Ops Activities
Automated Activities
Relocate incoming data, MOC, and FDF
files
Post lists of received files
Distribute real-time data Compute and post key parameter daily
total
Pipeline data processing Compute and post key parameter running
averages
Filter and aggregate all SOC computer log
files
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 334

CRaTER SOC Operations Concept
Manual/Automated Ops Activities
Manual Activities
Verify receipt of all expected files Request archived data via DMS
Check for new SPICE kernels (e.g.,
spacecraft clock correlation kernel, leap
second kernel, etc)
Update pipeline furnsh kernel
Verify operation of real-time data servers Perform daily, weekly, monthly, and annual
IT security audits
Review pipeline process logs Create and submit PDS archive updates
Review daily status plots for evidence of
unusual environment conditions or
instrument performance
Create and submit OARs
Check SOC email and phone messages Attend weekly planning telecons, LDWG
telecons
Maintain log of SOC ops activity Maintain operator staffing schedules
Submit daily SOC status report Maintain current CRaTER SOC contact
information
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 335

CRaTER SOC Operations Concept
SOC Facilities – Boston University CAS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 336

CRaTER SOC Operations Concept
SOC Facilities – Boston University
Days are always sunny
and warm . . .
sunrises and sunsets clear
and spectacular . . .
. . . and completely strange and alien
universe is here!
. . . Bostonians believe the center
of our Universe is here, . . .
We study our Universe here, . . .
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 337

CRaTER SOC Operations Concept
SOC Facilities – “Family Photos”
SOC’s core system installed in a
secure, environmentally-controlled
server room.
SOC Ops Room: Support Team Area
SOC Ops Room: CRaTER EM Unit
connected to network.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 338

CRaTER Ops Room:
public display system
CRaTER SOC Operations Concept
SOC Facilities – “Family Photos”
CRaTER public display – Graduate College of
Arts & Sciences, 4th floor hallway.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 339

CRaTER SOC Operations Concept
SOC Facilities: Hardware/Network Architecture
• CRaTER Hardware
and Network Architecture
– Unix workstations and
RAID array receive,
process, store, and
distribute real-time
telemetry and down-loaded
instrument data
– Security and risk managed
by segregating
workstations/user access
into 3 groups
SOC-A
(only sysadmin access)
CRaTER-A
(only software team +
access)
CRaTER-Work-A
(only mission support +
team access)
CRaTER-Science
(science team + and other
designated users)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 340

CRaTER SOC Operations Concept
SOC Facilities: Hardware/Network Architecture
• CRaTER Hardware/
Network Architecture
– Additional security and risk
management steps
on-going maintenance
support from Redhat for
bug fixes and security
patches
logs automatically
collected and analyzed for
evidence of problems or
(attempted) intrusions
– CRaTER-Logger
NO group user accounts;
password expirations
all software changes/
patches tested first on
development system
before installation on other
operational workstations
– CRaTER-Devel
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 341

CRaTER SOC Operations Concept
SOC Facilities: Hardware/Network Architecture
• CRaTER Hardware/
Network Architecture
– Minimize outages/time to
recover from hardware
failures
main workstations
installed in a secure,
environmentally controlled
room with automatic fire
suppression
redundant workstations at
all three levels
– SOC-B
– CRaTER-B
– CRaTER-Work-B
spares for other key
hardware
– firewall router
– RAID array drives
automated system-wide
backups off-site
storage
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 342

CRaTER SOC Operations Concept
Ops Systems/Data Flow: Real-Time Data
• Real-Time (VC0) Data
Distribution
– Process on SOC-A
continuously listening for
telemetry
rtserver
– All raw data recorded to
data files
– Data decom’d and passed
through firewalls to
CRaTER-A
– Process on CRaTER-A
distributes to applicable
clients
rtserver
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 343

CRaTER SOC Operations Concept
Ops Systems/Data Flow: Real-Time Data
• Real-Time (VC0) Data
Distribution
– Very flexible system
– Input from one stream,
output to many streams
– Clients “register” with
rtserver
default set of clients
– always receive data
whenever rtserver is
running
additional clients added/
removed via the command
line
– Clients specify
protocol (UDP or TCP),
format (ascii, binary),
content (all or a subset of
available ApIDs)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 344

CRaTER SOC Operations Concept
Ops Systems/Data Flow: Data Processing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 345

CRaTER SOC Operations Concept
Ops Systems/Data Flow: Data Processing
• Pipeline Process: PDS Archive Content Creation
– creates PDS compliant detached data label files
one label file for each L0, L1, and L2 file
– creates an index file with L0/L1/L2 file names and creation dates
– creates files listing data gaps during UTC day
separate “gap” files for primary science, secondary science, and housekeeping data
– logs pipeline process messages
– copies all output, label, gap, and log files to appropriate locations in local archive
directory tree
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 346

CRaTER Science Operations
• SOC Functions
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 347

CRaTER SOC Readiness
Software/Tools
• Rtserver → Real-Time (VC0) Data
– Tested during numerous mission readiness tests and mission rehearsals
MRT-5a, MRT-6a (2008-06-26)
MR-1 (2008-12-15) – 2 day test, MR-4 (2009-01-21) – 4 day test
– Performed without problems
• crater_pipeline → Data Processing Pipeline
– Tested with instrument data and FDF/MOC products delivered during Mission
Rehearsal #1
No issues
• Archive creation tools and delivery process tested during PDS Archive
Delivery Tests
– Test 1 2008/02/15
– Test 2: 2008/03/26
– Test 3: 2008/04/23
– Successfully completed all tests
• All software and documentation maintained under version control with
Subversion
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 348

CRaTER SOC Readiness
Sustaining Engineering
• SOC Sustaining Engineering
– Sustaining engineering support baselined in budget
– Permanent SOC staff
sys admin, programmer
– Department and University
computer and local network hardware support (Department)
network maintenance and support, backup system maintenance (University)
– Continue software license and maintenance agreements
Redhax Linux Enterprise maintenance
IDL, Matlab (university), Mathematica (university)
– Hardware spares
spare RAID drives and network router procured with original hardware purchases
redundant system for major components
– SOC-A/SOC-B, CRaTER-A/CRaTER-B
rapid return to operations from major hardware failure
– CRaTER instrument engineering model
located in CRaTER SOC
available for testing instrument commands or troubleshooting instrument anomalies
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 349

CRaTER SOC Readiness
Sustaining Engineering
• Instrument Flight Software
– Instrument firmware burned into FPGA
– NO capability to modify existing firmware or upload new firmware
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 350

CRaTER SOC Readiness
Requirements Verification: Functional
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
FN_010 Shall perform measurement data processing to produce CRaTER T P 2009/01/14 Case/ Processed CRaTER data and FDF files
standard data products.
Golightly delivered as part of LRO Mission
Rehearsal #1 (15-16 Dec 2008).
FN_020 Shall perform measurement data reprocessing to update CRaTER I P 2008/10/24 Case/ Verified CRaTER data processing
standard data products as required by the science team.
P 2009/01/14 Golightly pipeline can be manually executed with
user-supplied input data file names—
this will permit any necessary
reprocessing.
FN_030 Shall create the following CRaTER primary data products:
T P 2009/01/14 Case/ Processed CRaTER data and FDF files
a. Time-ordered listing of event amplitude in each detector (L1)
P
Golightly delivered as part of LRO Mission
b. Linear Energy Transfer (LET) for each processed event (L2)
c. Time-ordered listing of secondary science data (L1)
d. Time-ordered listing of housekeeping data (L1)
Rehearsal #1 (15-16 Dec 2008).
FN_040 Shall provide the CRaTER data products (CRATER_FN_030) and L0 T P 2008/02/15 Wilson/ Verification completed during PDS
data to the PDS PPI Node for archive and distribution
P 2008/03/26 Golightly Archive Delivery Tests 1, 2, &3.
P 2008/04/23
FN_050 Shall provide sufficient disk space for:
A, I P 2009/02/18 Bradford/ Verified by comparison of estimated
a. 10 days of incoming data from the MOC
Golightly 10-day file volume to capacity of
b. 10 days of L1 derived products
partitions designated to store incoming
c. 10 days of L2 derived products
MOC data and L1/L2 products.
FN_060 Shall provide backup storage for disk space used for software
T, I P 2009/02/18 Bradford/ Applies to following machines:
development, user accounts and on-line disk space used for analysis
Golightly CRaTER-A, CRaTER-B, CRaTER-
Devel, and CRaTER-Science
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 351

CRaTER SOC Readiness
Requirements Verification: Functional
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
FN_070 Shall provide sufficient disk resources to stage PDS deliverables A, I P 2009/02/18 Golightly/
Bradford
FN_080 Shall support priority assignment of processing jobs based on input
from the science team
A P 2009/02/18 Bradford/
Wilson
FN_090 Shall be capable of providing operational and testing configurations T,I P 2009/02/19 Bradford/
Wilson/
Golightly
FN_110 Networking connections shall be capable of capturing, storing and
processing CRATER science and housekeeping at the maximum data
rate possible
T P 2009/01/26 Bradford/
Wilson/
Golightly
Verified by comparison of capacity of
partition used to stage the PDS
deliverables to the estimated 91-day file
volume for L1/L2 data products and
associated ancillary files.
Verification by moderate fidelity testing
during PDS Archive Delivery Tests 1,
2, &3 (2008/02/15, 2008/03/26,
2008/04/23)
SOC-A: N/A
CRaTER-A: controlled through Linux
job priority assignment
CRaTER-Science: controlled through
Linux job priority assignment
Parallel redundant hardware
architecture and dedicated development
machine supports simultaneous
operational and testing configurations.
Verified during Mission Rehearsal #4
(21-25 Jan 2009)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 352

CRaTER SOC Readiness
Requirements Verification: Functional
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
FN_500 Shall provide resources to support the development and maintenance T, I P 2009/01/30 Bradford/ CRaTER-Devel--dedicated SOC ops
of CRATER measurement data processing software
Wilson/ software development and test system.
Case/ CRaTER-Science—BU CRaTER team
Golightly computer which supports development
and testing of higher-level CRaTER
data products.
FN_510 Shall provide resources to support testing with the LRO Ground
T P 2008/12/16 Golightly/ Verified by successfully supporting all
System
P 2009/01/24 Bradford/ required Mission Readiness Tests,
Wilson Simulations, and Mission Rehearsals.
FN_520 The SOC shall provide resources to support testing with the PDS PPI T P 2008/02/15 Golightly/ Verified by successfully completing
Node
P 2008/03/26 Wilson/ PDS Archive Delivery Tests 1, 2, &3.
P 2008/04/23 Sharlow
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 353

CRaTER SOC Readiness
Requirements Verification: Interface
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 354

CRaTER SOC Readiness
Requirements Verification: Interface
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
IF_070 Shall obtain LRO SPICE SCLK, LSK and FK kernels from the LRO T P 2009/02/18 Golightly Have been provided initial LRO-
as needed
specific SPICE kernels via email
IF_500 Shall provide the PDS PPI Node with the following CRATER data T P 2008/02/15 Wilson/ Verified by successfully completing
products:
P 2008/03/26 Golightly/ PDS Archive Delivery Tests 1, 2, &3.
a. Energy deposited in each detector for every processed event.
P 2008/04/23 Sharlow Proper content of L1 and L2 science
b. Linear energy transfer in each detector for every processed
P 2009/01/14
data product verified during processing
event.
of CRaTER data files from Mission
c. CRaTER mass model
Rehearsal #1 (15-16 Dec 2008)
IF_510 Will provide to the LRO MOC instrument command sequences T, I P 2008/03/12 Wilson/ MRT5a: Created and submitted
P 2009/02/18 Golightly/ CRAT_OAR_2008_072_01.txt to
Goeke/ perform CRaTER electronic calibration
Sanidad STOL procs: provided input and
review of 19 instrument commanding
procs
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 355

CRaTER SOC Readiness
Requirements Verification: Performance
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
PF_010 Shall take action to start the ingest of incoming data within 3 hours T, I P 2008/12/16 Wilson/ Verified during LRO Mission
after they are made available by the LRO MOC
P 2009/01/25 Golightly Rehearsal #1 (15-16 Dec 2008) .
Verified during LRO Mission
Rehearsal #4 (21-25 Jan 2009)
PF_020 Shall receive data from the LRO MOC on a daily basis 24 hours per T, I P 2009/01/20 Wilson/ CRaTER SOC-A machine continuously
day, 7 days per week, and 52 weeks per year
Golightly monitoring and recording VC0
telemetry streams from the MOC for 6
months. Eval period includes several
Mission Readiness Tests, Sim-29,
Mission Rehearsal #1, and Mission
Rehearsal #4.
PF_030 Shall process CRATER measurement data for the entire nominal A, I P 2009/02/18 Golightly/ CRaTER SOC infrastructure capacity
mission.
Bradford supports processing CRaTER
measurement data for entire nominal
mission.
PF_040 Shall be capable of processing CRATER measurement data for an A P 2009/02/18 Golightly/ CRaTER SOC infrastructure capacity
extended mission, should the mission be extended
Bradford supports processing CRaTER
measurement data for a 12 month
extended mission. Extended mission
longer than 12 months will require
either additional storage capacity or the
use of file compression for locally
archived data.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 356

CRaTER SOC Readiness
Requirements Verification: Performance
SOC Requirement Test
No. Description Method Status Date Engineer Additional Info
PF_050 Shall provide standard data products to the PDS PPI Node every 3 A, T P 2009/02/19 Golightly Capability to create and submit a valid
months starting at launch +6 months
Wilson/ 3-month archive submission validated
Sharlow during PDS Archive Delivery Tests 1,
2, &3.
PF_060 Shall provide adequate on-line storage to buffer 10 days of incoming A, I P 2009/02/18 Golightly/ Verified by comparison of estimated
data
Bradford/ 10-day file volume to capacity of
partitions designated to store incoming
data from MOC
PF_070 Shall provide adequate on-line storage to buffer 10 days of outgoing A, I P 2009/02/18 Golightly/ Verified by comparison of estimated
data
Bradford 10-day file volume to capacity of
partitions designated to store outgoing
data to MOC
PF_080 SOC shall provide adequate on-line storage for 10 days of CRATER A P 2009/02/18 Bradford/ Verified by comparison of estimated
standard data products
Golightly 10-day file volume to capacity of
partitions designated to store L1/L2
products.
PF_100 Shall provide a mechanism for the science team to validate incoming A, I P 2009/02/19 Golightly/ CRaTER science team will have access
data
Case/ to all L1 and L2 data, contemporary
Goeke measurements from other spacecraft for
comparisons, and access to modeling
tools.
PF_110 Shall provide performance and trending information T, I P 2009/02/19 Golightly/ Trending tools used extensively during
Case/ spacecraft I&T (including TVac) and
Goeke instrument testing at accelerators.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 357

CRaTER Science Operations
• SOC Functions
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 358

CRaTER SOC Summary
• CRaTER SOC has been developed and tested at Boston University
• CRaTER SOC systems are ready to support the LRO MOT and the
CRaTER science team
CRaTER SOC is ready for flight
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 359

Additional Information
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 360

CRaTER SOC Operations Concept
Ops Systems/Data Flow: File Copy/Storage
• All data and MOC/FDF files pushed from the MOC to “inbox” on SOC-A
• Automated script moves file from “inbox” to appropriate storage location
– runs once/hour
– daily log of files received/moved
– instrument raw data files → SOC-A/working_directory
– MOC/FDF files required by data pipeline process → SOC-A/working_directory
– MOC/FDF files used for operations/planning → CRaTER-
A/ops_support_directory
– MOC/FDF files used for future reference → SOC-A/local_archive
– NAIF and LRO kernel updates → SOC-A/new_kernel_directory
– files other than above → SOC-A/miscellaneous_file_directory
• Pipeline process at completion moves products to local archives
– L0/L1/L2 products, PDS label/index files → SOC-A/local_archive
– L2 products → CRaTER-A/local_archive
• PDS Archive submissions
– quarterly submission
– L0/L1/L2 and associated PDS files copied to PDS PPI Node
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 361

CRaTER SOC Operations Concept
Ops Systems/Data Flow: Data Processing
• Pipeline Process: Data Processing
– raw → L0: ingest CRaTER raw science and housekeeping files and aggregates
data by ApID
ApID 120 = primary science, ApID 121 = secondary science, ApID 122 = housekeeping
output as separate primary science, secondary science, and housekeeping files in
binary format
– L0 → L1: use conversion coefficients and calibration values to convert binary
data into engineering/scientific values
output as separate primary science, secondary science, and housekeeping files in ascii
format
– L1 → L2: spacecraft location and instrument pointing information appended to
L1 information
use definitive SPICE ephemeris and orientation kernels to compute spacecraft position
and instrument pointing
spacecraft location computed in multiple coordinate systems (selenographic, GSE,
GSM)
output as separate primary science, secondary science, and housekeeping files in ascii
format
– L0, L1, and L2 files contain data for one UTC day
9 L0/L1/L2 files per day
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 362

SOC Readiness
Requirements Verification: Functional Notes
SOC Requirement
No. Additional Info
FN_010
FN_020
FN_030
FN_040
FN_050 10 days MOC data 11.409 GBytes, 10 days L1 6.250 GBytes, 10 days L2 14.840 GBytes
Partition storing incoming data from MOC (soc-a/work/) = 190 GBytes
Partition storing L1 and L2 data products prior to moving to local archive (soc-a/scratch/) = 321 GBytes
Estimated total volume of delivered FDF, MOC, and CRaTER science and housekeeping file = 1.141 GByte/d (using worst case assumption of maximum
instrument throughput of 1200 events/s for 10 days). File volume based on analysis of files delivered during Mission Rehearsal #4, and computed CRaTER
primary science file size using file description in Spacecraft to CRaTER Data Interface Control Document (32-02001.01, Rev G).
Estimated L1 and L2 data volume from CRaTER Standard Product Data Record and Archive Volume SIS (32-01211, Rev D), Table 10
FN_060 On BU OIT’s website, verified current backup schedule l for crater-a, crater-science, and crater-devel as follows:
crater-a weekly = /home, monthly = /usr/local/crater;
crater-devel weekly = /home;
crater-science weekly = /home, /work, and /data1
Restore of encrypted backup tested by D. Bradford on 2009-01-26: per request, IT Operations (S. Yu) restored subdirectory SOC-A:/home/crater_adm/ to
CRATER-A:/usr/local/restore_test/crater_adm/ The size of each decrypted file verified against the original file size. The contents of one text file were also
checked for decoding errors—the file appeared to be restored without error.
FN_070 Estimated file volume of archive products (L1 and L2 data products; ancillary files FDF-29, MOC-3, MOC-7, MOC-42, MOC-46, and MOC-47) = 2.27
GBytes/day. Allow and additional 0.001 GBytes/day for associated PDS label, format, and catalog files 2.271 GBytes/day. PDS products are delivered
quarterly (~91 days). Total file volume to be staged prior to compression = 91 days x 2.271 GBytes/day 206.7 Gbytes. Assuming a 95% compression (all
staged files are ascii), an additional 10.3 GBytes must be staged. This results in a requirement to stage 217 Gbytes for delivery. Partition staging PDS files prior
to delivery (soc-a/scratch/) = 321 GBytes. The compressed and uncompressed staged files will be deleted after receipt and acceptance by the PDS PPS node
(expected within two weeks of delivery).
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 363

SOC Readiness
Requirements Verification: Functional Notes
SOC Requirement
No. Additional Info
FN_080 Adjusting priority assignment of processing jobs based on input from the science team not applicable to SOC-A—users are restricted from accessing this
machine. Adjusting job priority assignments minimally applicable to CRaTER-A—this machine is used primarily as a data server for CRaTER science team
member accessing CRaTER data products produced by the data pipeline. There are currently no plans to host individual user jobs on CRaTER-A. CRaTER-
Science will host individual user accounts and scientific analysis and modeling codes. Upon request by a user, job processing priority will be managed through
Linux’s job priority assignment and/or batch jobs controlled by the cron scheduling utility.
FN_090 SOC Parallel Redundant Architecture:
SOC-A/CRaTER-A operational system
SOC-B/CRaTER-B backup/testing system
CRaTER-Devel development/testing only
Identification of Flight vs Test Data:
Flight instrument and non-flight instrument (ie, test) VC0 stream and stored data files are discriminated by the instrument serial number imbedded in the CCSDS
packet headers : flight instrument = S/N 02; flight instrument spare = S/N 01; engineering model = S/N 10; flatsat simulator = S/N 09.
FN_110 Mission Rehearsal #4: checked rtserver.log for rehearsal periodno decom errors.
2009-01-30 email from R. Casasanta (LRO GS&O Systems Engineering Team) re—MR#4 used highest telemetry rate:
". . . MR4 did showcase the downlink of VC0 data to the MOC at 64 kbps. That's the highest bandwidth we'll nominally take.
So, indirectly, you received the highest d/l rate. I don't believe we pump it to the SOCs at 64kbps, we do send it based on our getting it at 64 and then sub-setting
it to your specific set of APIDS and then you get it at that highest rate."
FN_500 CRaTER-Devel uses same hardware and operating system as SOC-A and CRaTER-A machines.
CRaTER-Science includes: (1) advanced data analysis and visualization development tools such as IDL; (2) instrument radiation response analysis tools such as
GEANT4.9.
FN_510
FN_520
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 364

SOC Readiness
Requirements Verification: Interface Notes
SOC Requirement
No. Additional Info
IF_010
IF_020
IF_030
IF_030 Mission Rehearsal #1: received 4 Daily Command Load Report (MOC-7) files for simulation day 2009-350 on simulation day 2009-351
Mission Rehersal #4: received Daily Command Load Report (MOC-7) files for simulation days 2010-084, -085, and -086; did not receive the required file for
simulation day 2010-087 (not received as of 2009-02-18).
IF_040 CRaTER SOC requirement is to receive LRO SPICE SPK (FDF-30) kernel files at least monthly. The requirement specified in LRO Project External Systems
ICD for the LRO Ground System (431-ICD-000049, Rev B, Sep 16, 2008) is to deliver LRO SPICE SPK (FDF-30) kernel files daily (covering next 28 days).
This delivery requirement satisfies the CRaTER SOC requirement. Daily deliveries of LRO SPICE SPK (FDF-30) kernel files verified during Mission Rehearsal
#1.
IF_050 CRaTER SOC requirement is to receive LRO SPICE CK (MOC-41) kernel files at least monthly. The requirement specified in LRO Project External Systems
ICD for the LRO Ground System (431-ICD-000049, Rev B, Sep 16, 2008) is to deliver LRO SPICE CK (MOC-41) kernel files daily (covering next 7 days). This
delivery requirement satisfies the CRaTER SOC requirement. Daily deliveries of LRO SPICE SPK (MOC-41) kernel files verified during Mission Rehearsal #1.
IF_060 Verified functionality of DMS link on RAS/LRO SSL-Explorer (accessed 2009-02-23, user = mgolightly, using Firefox from crater-a.bu.edu). Checked several
of the DMS daily subdirectories for years 2008, 2009, and 2010--noted CRaTER and MOC subdirectories present, but there appeared to be no data. Capability to
retrieve archived instrument data from the DMS via RAS has not been available for test during Mission Rehearsals, Mission readiness Tests, or Simulations.
IF_070
IF_500 Verified L1 science product contained energy deposited in each detector for every processed event.
Verified L2 science product contained the linear energy transfer in each detector for every processed event.
IF_510 MRT5a: CRaTER OAR submission “passed” (R. Saylor. “LRO Mission Readiness Test 5.a MOC to CRaTER and DLRE Interface Test Summary .” 16 May
2008)
STOL procs: collaborated with R. Sanidad in development of following instrument command procs--crcal_amp.proc, crcal_highrange.proc, crcal_lowrange.proc,
crcal_rate.proc, cr_data_test_mode.proc, cr_detbias.proc, cr_discaccmask.proc, cr_echocmd.proc, cr_elect_cal_rate.proc, cr_enadis_detector_processing.proc,
cr_evtampdiscthk.proc, cr_evtampdiscthn.proc, cr_first_powerup.proc, cr_nomfltconfig.proc, cr_onoff_detector_bias.proc, cr_pwrdown.proc, cr_pwrup.proc,
cr_pwruptlmver.proc, cr_reset.proc
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 365

SOC Readiness
Requirements Verification: Performance Notes
SOC Requirement
No. Additional Info
PF_010 Inbox for files delivered from LRO MOC is checked every 60 minutes for new files; new files are copied to appropriate working directories.
PF_020 2009-01-28 email from E. Wilson (CRaTER SOC Software Lead) re rtserver evaluation period:
“For the most part I would always just let it (rtserver) run until there was a problem or source change which required a restart. The first version of the server
committed was on July 10th 2008, it was probably running for extended periods in June since the bugs with Goeke's software were detected in March, and
rtserver was written in March/June.”
2009-01-27 email from E. Wilson (CRaTER SOC Software Lead) rertserver performance
Since 2008-07-10 “100% of tests with ITOS succeeded, 100% of data downloaded, 2 real-time server crashes due to hardware problems, 2 decom bugs resolved.”
PF_030 Nominal mission = 1 week launch through LOI + 2 months commissioning + 12 months nominal operations = 14.25 months (427 days)
Estimated daily volume for L0, L1, and L2 pipeline products and associated ancillary FDF/MOC files = 2267.253 Mbyte/day
Estimated nominal mission volume for L0, L1, and L2 pipeline products and associated ancillary FDF/MOC files = 969.25 GBytes
Total local archive storage capacity = 1824 GBytes
Budget plan continues hardware and software maintenance contracts and support for SOC staff salaries through end of mission.
PF_040 Extended mission (estimate) = 14.25 months nominal mission + 24 months extended mission = 38.25 months (1147 days)
Estimated daily volume for L0, L1, and L2 pipeline products and associated ancillary FDF/MOC files = 2267.253 Mbyte/day
Estimated nominal mission volume for L0, L1, and L2 pipeline products and associated ancillary FDF/MOC files = 2602 GBytes
Total local archive storage capacity = 1824 Gbytes can support 12 month extended mission with no change in existing hardware
Supporting a 24 month extended mission will require procuring an estimated 778 GBytes of additional storage capacity (6 additional RAID drives), moving the
existing 6-drive RAID from CRaTER-A to SOC-A, or compressing the files in the local archive (assuming 95% compression for L1 and L2 ascii files total daily
file volume decreases to 263.703 Mbytes/d or 302 GBytes for 24 month extended mission.
Strategy to meet the additional capacity need will be determined after the extended mission orbits are selected and estimated spacecraft fuel lifetime computed.
Data from actual measurements of archive volume vs time will provide a more exact estimate of expected archive file capacity necessary to support an extended
mission.
Current budget plans continues hardware and software maintenance contracts and support for SOC staff salaries through end of mission.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 366

SOC Readiness
Requirements Verification: Performance Notes
SOC Requirement
No. Additional Info
PF_050
PF_060 10 days incoming data 11.409 Gbytes
Partition storing incoming data from MOC (soc-a/work/) = 190 GBytes
Estimated total volume of incoming data (FDF, MOC, and CRaTER science and housekeeping files) = 1.141 GByte/d (using worst case assumption of maximum
instrument throughput of 1200 events/s for 10 days). File volume based on analysis of files delivered during Mission Rehearsal #4, and computed CRaTER
primary science file size using file description in Spacecraft to CRaTER Data Interface Control Document (32-02001.01, Rev G).
PF_070 10 days outgoing data < 60 kBytes
Partition storing outgoing data to MOC (soc-a/work/) = 190 GBytes
Only out going data to MOC are OARs. Estimated size of each OAR files derived from OAR created for Mission Rehearsal #5a (CRAT_OAR_2008_072_01.txt,
2 kBytes) . CRaTER commanding expected to be very infrequent—much less than an average of one OAR per day. Assume 2 OAR/day x 10 days x 3 kByte
60 kBytes.
PF_080 10 days CRaTER standard data products = 2.161 Gbytes
Partition storing L1 and L2 data products prior to moving to local archive (soc-a/scratch/) = 321 GBytes
CRaTER standard data products consist of L0, L1, and L2 science and housekeeping files and associated PDS label files, and browse plots.
Estimated L1 and L2 data volume from CRaTER Standard Product Data Record and Archive Volume SIS (32-01211, Rev D), Table 10.
PF_100 Verification will be done through comparison with other spacecraft measurements (e.g., NOAA GOES, ACE) and model calculations using GCR fluence models
and proton+heavy-ion transport codes. GEANT4 transport code currently installed and available on CRaTER-Science. Instrument mass, material, and geometry
information required for transport codes has been compiled and is currently available (information has already been used in modeling results of instrument
accelerator testing).
PF_110
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 367

CRaTER SOC Operations Concept
Ops Systems/Data Flow: MOC/FDF/NAIF Files
• Planning and Instrument Operations
Delivery
D = daily M = monthly AR = as required
W = weekly 2X = twice during mission
Coverage
H = hour W = week + = next N/A = not applicable
D = day M = month - = previous
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 368

CRaTER SOC Operations Concept
Ops Systems/Data Flow: MOC/FDF/NAIF Files
• CRaTER Data Processing Pipeline
Delivery
D = daily M = monthly AR = as required
W = weekly 2X = twice during mission
Coverage
H = hour W = week + = next N/A = not applicable
D = day M = month - = previous
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 369

• Archive
Delivery
CRaTER SOC Operations Concept
Ops Systems/Data Flow: MOC/FDF/NAIF Files
D = daily M = monthly AR = as required
W = weekly 2X = twice during mission
Coverage
H = hour W = week + = next N/A = not applicable
D = day M = month - = previous
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 370

CRaTER SOC Operations Concept
Ops Systems/Data Flow: MOC/FDF/NAIF Files
• SPICE LRO-Specific Kernels
• SPICE Generic and Lunar Kernels
Delivery
D = daily M = monthly AR = as required
W = weekly 2X = twice during mission
Coverage
H = hour W = week + = next N/A = not applicable
D = day M = month - = previous
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 371

CRaTER SOC Readiness
SOC Deliverable Documentation Status
Document Title Current Status
32-01209 SOC Requirements Document Rev B: 10/25/2006
32-02080 Science Team and the PDS Planetary Plasma Interactions Node ICD Rev B: 11/21/2006
32-01210 Data Management and Archive Plan Rev A: 10/25/2006
32-01213 Science Operations IT Risk Assessment Rev B: 06/01/2007
32-01208 IT Security and Contingency Plan Rev A: 07/01/2007
32-01212 SOC Test Plan Rev A: 10/24/2007
32-01211
Standard Product Data Record and Archive Volume SIS
(includes EDR and RDR data product and archive volume software
interface specifications)
Rev D: 01/29/2009
Input to LRO Mission Flight Rules and Constraints (431-OPS-000309) Rev A: 01/13/2009
PDS/PPIs EDR/Pipeline RDR SIS Peer Review 11/06/2007
Inputs to CRaTER Instrument User’s Manual for MOC Draft inputs: TBD
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 372

CRaTER SOC Development Status
Software/Tools – Displays
VC0 data--overview
VC0 data--details
Display during MR4 (21-25 Jan 2009)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 373

CRaTER SOC Development Status
Software/Tools – Displays
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 374

CRaTER SOC Development Status
Software/Tools – Displays
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 375

CRaTER SOC Operations Concept
SOC Facilities – “Family Photos”
Graduate College of Arts and Sciences, 4 th Floor Hallway:
CRaTER and IBEX Public Displays.
CRaTER Display IBEX Display
CRaTER SOC shares physical space, system design, and support
personnel with IBEX SOC.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 376

DLRE Science Operations
LRO Flight Operations Review – Section 9.3
NASA’s Goddard Space Flight Center
Charlie Avis - JPL
Mark Sullivan - UCLA

DLRE SOC Functions
• Safely operate instrument & maintain its health
• Generate all products in DMAP
• Produce and deliver archive products
• Provide data access to Science team
• Implement Science team observations in support of LRO science goals
• Provide outreach products and web content
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 378

DLRE SOC Peer Review Status
LRO Single Design Review 1/18/2007
• No RFA’s written
DLRE Detailed Design Review 8/15/2007
• 5 RFA’s written – all closed
LRO Mission Operations Review 9/18/2007
• 1 RFA written - closed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 379

DLRE SOC Operations Plan Overview
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 380

DLRE SOC Organization Chart
Mark Sullivan
UCLA SOC Manager/Archivist
S/W developers Science Team
Sys Admin
Outreach
David Paige
PI / UCLA
Charlie Avis
JPL SOC Manager
S/W developers Ops Engineers Database Admin
I&T, Sys Admin, CM staff
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 381

DLRE SOC Phase E Staffing Plan
Assuming 09Q3 Launch and no extended mission
JPLTask 09Q4 10Q1 10Q2 10Q3 10Q4 11Q1 11Q2
SOC Lead/Sys Eng 0.5 0.5 0.5 0.5 0.5 0.25 0.25
Commanding 0.5 0.5 0.5 0.5 0.5
Instrument Eng. 0.5 0.5 0.5 0.5 0.5
EDR/RDR Production 1 1 1 1 1 1 1
GSW maint 0.2 0.2 0.2 0.2
FSW maint 0.1
SA, DBA 0.3 0.3 0.3 0.3 0.3 0.3 0.3
Supervisor 0.1 0.1 0.1 0.1 0.1 0.05 0.05
JPL Total 3.2 3.1 3.1 3.1 2.9 1.6 1.6
UCLA Data Prod. / Mapping / Archiving 1.5 1 1 1 1 1 1
Grand Total 4.7 4.1 4.1 4.1 3.9 2.6 2.6
Launch will be supported from JPL; turn-on activities
will be supported from TBD
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 382

JPL SOC
DLRE SOC Staffing Status
• Development staffing in decline (except for RDR programming)
• Testing currently with ½ of planned Ops personnel
• Rest of Ops staff on-board in March and April
UCLA SOC
• All staff has been hired
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 383

DLRE SOC Ops Activities
• JPL SOC receives real-time telemetry
– Ingests from socket during passes
– Automated alarm notification
– Operator monitors in Prime Shift
• JPL SOC receives science and engineering data files post-pass
– JPL SOC produces/delivers EDR/RDR products
• Receive ancillary files daily – predicts, refinements
– Reprocess data products if necessary and distribute
• JPL SOC implements Science team observations/calibration tweaks
– Receive Ops guidelines from science team
– Generate new commands & table updates
– Run s/w simulator and/or brassboard/EGSE
– Deliver table updates/OAR to MOC
– Operator monitors receipt by instrument
• UCLA SOC prepares archive volumes
• UCLA SOC produces high-level science products
• UCLA SOC produces web content and outreach products
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 384

DLRE SOC Data Flows/Interfaces
DLRE SOC Interfaces
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 385

outer
DLRE SOC Facilities - JPL
EGSE
Institutional LAN
Internet
Instrument
Brassboard
MOC Oxford
PDS
UCLA
router
Science Teams
4 DLRE Linux
platforms
MIPL LAN
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 386
coda8
Zorro
Admin
mipldev
mipl storage
Coda7
Kerberos/LDAP
ccc
mipldev
All components currently in place
miplbk1
miplbk2
mipl9
Spice
miplfiler1
mipl
MAIL
rushmore
www
BU
Tape
BU
Tape
miplmon
BBMON
miplcon
console
This facility, the Multimission Image Processing Lab (MIPL) is
developed and maintained by the Science Instrument Services (SIS)
System within IND to meet requirements that span the NASA family of
planetary missions.

DLRE SOC Facilities - UCLA
Rocks Frontend
Cisco Switch
Web Server
Development Node Production Node
Firewall
RAID Array
(50 TB)
Compute Nodes
(160)
Cisco Router Cisco Router
Rocks Frontend
Cisco Switch
SOC Boundary
* Secure to DLRE JPL SOC
and PDS Geosciences
RAID Array
(20 TB)
Compute Nodes
(60)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 387
SCSI
10 Gig
* Public Outreach (read-only)
1000-Base-T
Campus Backbone

DLRE SOC Facilities Status
JPL SOC
• Separate Ops, Test and Dev environments – complete
• Multiple linux servers in secure computer room – complete
• Data storage in secure computer room – procuring additional storage
• Distributed workstations for Ops folks and developers - complete
• Connectivity to LRO MOC, Oxford and UCLA - tested and functional
• Brassboard – configuration for Ops support incomplete
UCLA SOC
• Development Node - complete
– All network firewalls and switches installed/configured/tested
– All frontend and compute nodes installed/configured/tested
• Production Node - 20% completed
– All network firewalls and switches installed/configured/tested
– Frontend and compute nodes assembled, not yet installed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 388

DLRE SOC Readiness
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 389

DLRE SOC SW Development Status
JPL Software component Status
Tests used for
verification
Planning/commanding/simulation Complete Sim-29, MR-1, MR-4
Health analysis Complete MR's, MRT's, Sim's
Data delivery Complete MR's, MRT's, Sim's
Real-time monitoring Complete MR's, MRT's, Sim's
Database and database s/w 90% complete MR-4
Telem processor and EDR pipeline 90% complete MR's, MRT's, Sim's
RDR processing pipeline 90% complete MR's, MRT's, Sim's
RDR product generation 60% complete
• Latest s/w delivery to test: 16 March
• Likely will have another (at least for RDR
product generation) before Launch
See slide 18 for schedule
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 390

DLRE SOC SW Development Status
UCLA Software component Status
Planning tools In development
Data Processing Pipeline Subscriptions to JPL complete; need
final h/w
Archive processing 50% complete
Database In development
Website/Public Outreach Second revision done; third in
progress
Higher-level product generation Model program 50% complete; in
development
See slide 18 for schedule
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 391

Formal Testing
DLRE SOC Testing Status
• Formal testing with MOC is a progression of
complexity as MOC and SOC capabilities come online.
• Complete testing of SOC performance and capabilities
has been hampered by MOC data handling and
transfer problems.
• Several short ORT’s are scheduled prior to launch.
Interface Testing
• MOC-SOC - tested multiple times both ways
• JPL-UCLA - tested daily during Thermal/Vac
• JPL-Oxford - tested daily during Thermal/Vac
• UCLA-Oxford - tested daily during Thermal/Vac
• UCLA-PDS - tested during formal SOC-PDS tests
Date Completed Test
03/12/08 Msn Readiness 5.a
04/17/08 Msn Simulation 3
05/29/08 Msn Simulation 8
06/05/08 Msn Readiness 6.a
08/21/08 Msn Rehearsal 2
09/15/08 Msn Simulation 29
12/15/08 Msn Rehearsal 1
01/08/09 Msn Readiness 6.b & 6.d
01/21/09 Msn Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 392

JPL SOC Plans
DLRE SOC Sustaining Engineering
• Phase E budget has:
– Task Lead/Sys Eng at 0.5
– GSW maintenance for 1 year (plus test support)
– FSW maintenance for 1 quarter
– JPL engineering staff still accessible
UCLA SOC Plans
• Full-time archivist in Phase E budget also has system engineering role
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 393

DLRE SOC Work-to-go Plans
JPL SOC
• Complete final s/w deliveries – by May 1
• Complete coding/testing of RDR algorithms – by Launch
– Get fully functional with prototype algorithms
– Tweak algorithms post-Launch and reprocess data
• Complete procedure documentation – by May 1
• Participate in rest of MOC test schedule – through Launch
• Conduct internal data production testing – through Launch
• Configure Brassboard/EGSE – April
• Add/train staff for Ops – March/April
UCLA SOC
• Complete planning tools - 95% by Launch; 100% by mid-commissioning
• Complete installation of Production Node computer cluster – by April 1
• Install FEI subscriptions and Oxford viewer s/w on new cluster – by April 1
• Complete database, web site, and outreach materials - by Launch
• Complete “modeling” software used to generate higher-level data – by April 1
• Write non-pipeline RDR SIS, pass review
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 394

DLRE SOC Concerns & Risks
Concern Risk
Some MOC capabilities coming too
late for end-to-end testing
LRO multi-day end-to-end testing is
over before all s/w in place
Complexity of RDR s/w causing
stretch-out of task
Verification not as thorough as could
be
Adds work to DLRE personnel to
simulate Ops
Some capabilities and refinements
moving to post-launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 395

DLRE SOC Requirements Scorecard
JPL Complete Partial Not
tested
Total % Completely
tested
External 15 0 4 19 79
Internal 38 4 14 56 68
Total 53 4 18 75 71
UCLA Complete Partial Not
tested
Total % Completely
tested
External 0 0 0 0 n/a
Internal 7 0 8 15 47
Total 7 0 8 15 47
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 396

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 397

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 398

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 399

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 400

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 401

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 402

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 403

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 404

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 405

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 406

DLRE SOC Requirements Verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 407

DLRE SOC Summary
• JPL and UCLA SOC have some remaining development and testing, but
critical Ops functions are ready now
• Plans are in place to reach completion of key elements by launch
• Testing to date shows staffing and facility plans will adequately support
orbital Ops
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 408

LEND SOC
LRO Flight Operations Review – Section 9.4 Karl Harshman
NASA’s Goddard Space Flight Center
Institute for Space Research
Federal Space Agency of Russia

SOC Functions
• IKI SOC
– Monitor real-time data
– Collaborate with GSFC SOC on commanding
– Prepare Commanding requests
– Prepare high level data products
• GSFC SOC
– Monitor real-time data
– Collaborate with IKI SOC on commanding
– Submit Commanding request to MOC
• University of Arizona SOC
– Maintain a database to store all data products
– Receive and store all raw data
– Receive and store SPICE kernels
– Produce level 1 data products
– Provide access to all data products via a web interface
– Deliver data products to PDS
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 410
Federal Space Agency of Russia

SOC Peer Review Status
• Peer review held at University of Arizona in May of 2007
• Reviewers:
– Chuck Fellows, Rick McCloskey, Olivier Gasnault, Rick Saylor, Jim Clapsadle,
Stan Scott
• Presenters:
– Igor Mitrofanov, Richard Starr, Erik Timmermann, Karl Harshman
• Items presented:
– Data Products Overview
– SOC Overview
– SOC Schedule
– SOC Facilities Description
– External Interfaces
– SOC Interfaces Detailed Designs
– Instrument Planning and Monitoring Detailed Design
– Data Processing Detailed Design
– Data Storage Detailed Design
– Preparation of Data Products for PDS: Detailed Software Design
– SOC Design Implementation Status
– SOC Test Plan Overview
– Issues and Risks
• All Action Items coming out of the review, have been addressed
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 411
Federal Space Agency of Russia

SOC Staffing
• Staffing Plan
– All SOCs will have personnel on call during off duty hours
– IKI
Early Mission
– One person at GSFC
– One person at UA
– IKI SOC staffed during normal working hours
Normal Ops
– All personnel at IKI during normal working hours
– GSFC
Early Mission
– Normal working hours
Normal Ops
– Normal working hours
– UA
Early Mission
– Normal working hours
Normal Ops
– Normal working hours
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 412
Federal Space Agency of Russia

SOC Staffing
• SOC Organization Chart Igor Mitrofanov
Principal Investigator
Erik
Timmerman
Programmer
Hariolf Haefele
Programmer
Mike Fitzgibbon
Programmer
Mike Finch
Programmer
William
Boynton
Co-Investigator
Heather Enos
Manager
Karl Harshman
UA SOC
manager
University of Arizona
rRichard Star
Co-Investigator
Tim McClanahan
Larry Evans
Co-Investigator
Goddard Space Flight Center
Anton Sanin
Project
Manager
Alexey
Molokhov
Lead Ground
Software
Engineer
Maxim Litvak
Lead Data
Analyst
Russian Space Institute
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 413
Federal Space Agency of Russia

SOC Facilities
• SOC Facilities and Equipment
– IKI
Work areas are established and will remain available throughout mission
Hewlett-Packard PC running Microsoft Windows 2003 Server
Database Microsoft SQL Server 2000
PC workstations connecting through LAN
One workstations connected to Internet to receive raw data from UA
– GSFC
Offices established and available
Two PCs (windows XP operating system)
One primary and one backup.
Administered by GSFC Code 690 approved System Administrator.
– UA
Secured Server room available throughout mission
Sun Sun-Fire-480R running Solaris 5.10 - Operating System Platform
Sun 10 terabyte Raid Array
Sun Sun-Fire 880 running Solaris 5.8 - Operating System Platform
Sun StorEdge L9 Robotic Backup Tape Array
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 414
Federal Space Agency of Russia

SOC Operations Concept Overview
• Automated Ops Activities
– Raw data receipt
– Data ingest into UA database
– SPICE kernel receipt
– Calculation of Spatial and Temporal data
– Reprocessing on Spatial and Temporal data at receipt of definitive CK and SPK
kernels
– Distribution of raw and spatial data to other SOCs and Science Team
• Manual Ops Activities
– Data monitoring
– Command request generation
– Higher level data product generation and distribution
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 415
Federal Space Agency of Russia

• Operations
Systems /
Data Flows
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 416
Federal Space Agency of Russia

SOC Operations Concept
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 417
Federal Space Agency of Russia

SOC Operations Concept Overview
• Operations Systems / Data Flows (UA centric)
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 418
Federal Space Agency of Russia

SOC Operations Concept Overview
• Operations Systems / Data Flows (GSFC centric)
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 419
Federal Space Agency of Russia

SOC Operations Concept Overview
• Operations Systems / Data Flows (IKI centric)
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 420
Federal Space Agency of Russia

SOC Commanding
• LEND is a passive instrument and should require little nominal commanding
• GSFC and IKI will evaluate LEND performance on a daily and weekly basis and
consider commanding options through regular telecons and e-mail.
– Goddard LEND team members will participate in weekly LRO mission operations meetings to discuss
instrument status and plans for instrument commanding.
– Any instrument anomalies will be documented and provided to the project in a formal report.
• GSFC and IKI will discuss upcoming command loads via telecons and e-mail.
– IKI fills out Command Request Form and transmits to Goddard
– GSFC will complete project approved standard form for command loads based on provided Command Request
Form transmit from IKI.
– IKI will acknowledge receipt and provide approval or make corrections.
– IKI approved command load will be transmitted to the MOC by the GSFC SOC.
Commands
• LEND commands consist of 4 bytes.
Command format:
Byte 0 Byte 1 Byte 2 Byte 3
Command code Argument 1 Argument 2 Checksum
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 421
Federal Space Agency of Russia

SOC Readiness
• Software / Tools
– Real-time and Static data displays
– Web App Query Tool
– Data Distribution Network
– Database data ingest
– Spatial Computations and Re-computations
• Sustaining Engineering
– SOC
All software under version control
Engineers available to maintain all of it
Sharing a DBA with other projects
– Instrument FSW
The instrument has no FSW, all controls within electronics (FPGA)
• SOC Requirements Verification
– 43 requirements to verify
41 have been verified
The 2 remaining ones deal with creation of map products
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 422
Federal Space Agency of Russia

LEND Query Tool
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 423
Federal Space Agency of Russia

LEND Query Tool
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 424
Federal Space Agency of Russia

LEND Query Tool
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 425
Federal Space Agency of Russia

LEND Quick Look Visualizer
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 426
Federal Space Agency of Russia

LEND Quick Look Visualizer
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 427
Federal Space Agency of Russia

Documentation
Document Description/Purpose Due Date Status
LEND SOC / PDS ICD Interface Control Document between
PDS and SOC
LEND EDR SIS Software Interface Specification for
LEND EDR data to PDS
LEND RDR SIS Software Interface Specification for
LEND RDR data to PDS
LEND SOC
Requirements
SOC Data Management
and Archive Plan
LEND SOC Security
Plan
LEND SOC Risk
Assessment
LEND SOC Contingency
Plan
Detailed list of requirements SOC
must meet
Details of SOC data management and
archiving
March 2007 Complete
May 2007 Complete
February 2008 Complete
December 2006 Complete
December 2006 Complete
Details of security risk mitigations June 2007 Complete
Details of security risks April 2007 Complete
Plans for contingency operations Sept 2007 Complete
LEND SOC Test Plan Detail of SOC test plans Sept 2007 Complete
Requirements
Verification Matrix
Status of Requirements Verification March 2009 Complete
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 428
Federal Space Agency of Russia

Requirement ID
(From LEND SRD)
LEND_FN_010
LEND_FN_011
LEND_FN_013
LEND_FN_015
LEND_FN_016
LEND_FN_017
Requirements Matrix
Requirement
Description
U of A and GSFC SOCs shall
receive level 0 LEND data, both
science and housekeeping files,
from the Mission Operations
Center (MOC) at Goddard.
U of A shall deliver level 0
LEND data, both science and
housekeeping files, to the IKI
SOC.
U of A and GSFC SOCs shall
receive real-time LEND
housekeeping data from the
MOC through a socket
interface.
U of A SOC receives both
predictive and definitive SPICE
kernels (SPK and CK) from the
MOC as they become available.
U of A SOC receives SPICE
kernels (FK and SCLK) from
the MOC as they become
available.
U of A shall deliver predictive
and definitive SPK and CK
SPICE kernels to the IKI SOC.
Verification
Method(s)
Test
Demonstration
Inspection
Analysis
Test Name(s)
T, I FN_MOC_INPUT_UA,
FN_MOC_INPUT_GSFC
T, I, D FN_SOC_OUTPUT_IKI
T, I, D FN_MOC_REALTIME_INP
UT_UA,
FN_MOCREALTIME_INP
UT_GSFC
T, I, D FN_MOC_P_SPICE_INPU
T_UA
T, I, D FN_MOC_SPICE_INPUT_
UA
T, I, D FN_SOC_P_SPICE_OUTP
UT_IKI
Status Comments Who passed
Requirement
Completed MRT-5b ( 03/05/08).
This tested the TCP/IP socket
interfaces as well as the scp file
transfers.
Completed MRT-5b ( 03/05/08) .
This test tested the TCP/IP socket
interfaces as well as the scp file
transfers. The SOC used this data
to test their TCP/IP transmissions
The files were delivered
from the MOC. An issue
with file permissions has
been encountered. This
issue still occurs
occasionally.
Erik Timmermann
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 429
Federal Space Agency of Russia
to IKI.
Completed SIM 29 ( 09/01/08) .
This tested the TCP/IP socket
interfaces as well as the scp file
transfers during a normal mission
phase.
Complete Rehearsal #1 ( 12-15-
08). End to End test of the MOC
and SOC systems.
Complete Rehearsal #1 ( 12-15-
08). End to End test of the MOC
and SOC systems.
Complete Rehearsal #1 ( 12-15-
08). End to End test of the MOC
and SOC systems.
The files were delivered via
TCP/IP to the LEND
Displays Software at IKI.
All the VC0 types were
delivered to GSFC and UA
LEND SOCs via TCP/IP.
Predictive and Definitive
SPICE kernels were
delivered. An issue with file
permissions has been
encountered. This issue has
not resurfaced.
SPICE kernels were
delivered. An issue with file
permissions has been
encountered. This issue has
not resurfaced.
SPICE kernels were
delivered. An issue with file
permissions has been
encountered.
Erik Timmermann
Erik Timmermann,
Richard Starr
Erik Timmermann
Erik Timmermann
Erik Timmermann

LEND_FN_020
LEND_FN_021
LEND_FN_022
LEND_FN_023
LEND_FN_024
LEND_FN_025
Requirements Matrix
U of A SOC shall store all raw
LEND data in a relational
database.
U of A SOC shall store LEND
SCIENCE EDR data in a
relational database.
U of A SOC shall store LEND
HOUSE KEEPING EDR data in
a relational database.
U of A SOC shall store LEND
INTERMEDIATE SCIENCE
data – time ordered science
spectral data with spatial and
temporal information in a
relational database.
U of A SOC shall store LEND
DERIVED SCIENCE data in a
relational database.
U of A SOC shall store LEND
AVERAGED SCIENCE data in a
relational database.
T, I FN_SOC_INPUT_INGEST_
RAW
T, I FN_SOC_INPUT_INGEST_S
CI_EDR
T, I FN_SOC_INPUT_INGEST_
HK_EDR
T, I FN_SOC_INPUT_INGEST_S
PATIAL
T, I FN_SOC_INPUT_INGEST_
DERIVED
T, I FN_SOC_INPUT_INGEST_
AVERAGED
Completed MRT-5b (
03/05/08) . This test
tested the TCP/IP socket
interfaces as well as the
scp files transfers.
Complete Rehearsal #1 (
12-15-08). End to End
test of the MOC and
SOC systems.
Complete Rehearsal #1 (
12-15-08). End to End
test of the MOC and
SOC systems.
Complete Rehearsal #1 (
12-15-08). End to End
test of the MOC and
SOC systems.
All the data sent from the
MOC are being stored in
the UA database.
The EDR Science data has
been processed and stored
correctly in UA database.
The EDR House Keeping
data has been processed
and stored correctly in UA
Erik Timmermann
Erik Timmermann
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 430
Federal Space Agency of Russia
database.
raw science data with the
spatial information are
stored during the ingest
process.
Internal Test (2-18-09) The LEND Derived
Science files were created
in the specified format and
stored in the database.
Internal Test (2-18-09) The LEND Averaged
Science files were created
in the specified format and
stored in the database.
Erik Timmermann
Erik Timmermann
Erik Timmermann
Erik Timmermann

LEND_FN_026
LEND_FN_027
LEND_FN_030
LEND_FN_035
LEND_FN_040
LEND_FN_045
LEND_FN_050
Requirements Matrix
U of A SOC shall store LEND
SURFACE COMPOSITION data
in a relational database.
U of A SOC shall store LEND
RADIATION data in a relational
database.
U of A SOC shall store SPICE
kernels to allow for easy retrieval
as needed.
U of A SOC shall produce LEND
level 0 data from raw LEND data
received from the MOC.
U of A SOC shall provide a
secure web base interface into the
LEND database to allow
members of the LEND team to
retrieve both raw and processed
LEND data listed in
LEND_FN_050.
U of A SOC shall provide frontend
software to read in and
display records from the U of A
database.
U of A SOC shall produce PDS
compliant LEND data products
for release to PDS at regularly
scheduled intervals.
T, I FN_SOC_INPUT_INGEST_S
URFACE_CMP
T, I FN_SOC_INPUT_INGEST_
RADIATION
T, I FN_SOC_INPUT_SPICE_ST
ORAGE
T, I, D FN_SOC_OUTPUT_RAW_T
O_LVL0
T, I, D FN_SOC_QUERY_TOOL
T, I, D FN_SOC_QUICKVIEW_VIS
UALIZER
T, I, D FN_SOC_OUTPUT_PDS_D
ATA_PROD
The Data to perform this
task is not available.
Not Verified.
The Data to perform this
task is not available. Not
Verified.
These are high level
products that will not be
produced until end of
primary mission
These are high level
products that will not be
produced until end of
primary mission
Complete (11/01/08) Kernel script moves SPICE
files to their permanent
Complete Rehearsal #1 (
12-15-08). This test
was a full run though of
the MOC and SOC
Not yet verified
Not yet verified
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 431
Federal Space Agency of Russia
systems.
location.
This data can be
downloaded via the LEND
Query Tool.
Complete (01/21/09) GSFC LEND SOC was
able to download LEND
data via the LEND Query
tool.
Completed SIM 29 (
09/01/08)
Completed PDS E-t-E
Test 3 (07/08/2008)
GSFC LEND SOC is
receiving and viewing
LEND data via the LEND
Displays Software.
GeoSciences PDS node
verified that compliant
PDS data was received
from the LEND SOC.
Erik Timmermann
Erik Timmermann
Erik Timmermann via
Richard Starr
Erik Timmermann via
Richard Starr
Erik Timmermann via
Susan Slavney

LEND_FN_055
LEND_FN_060
LEND_FN_070
LEND_FN_080
LEND_FN_090
LEND_IF_010
Requirements Matrix
IKI SOC shall produce Post
Processed data products (in
formats that are not PDScompliant)
and provide them to
the U of A SOC.
Goddard SOC, in collaboration
with IKI SOC, shall provide
formatted instrument commands
to the MOC for validation and
upload to the spacecraft.
U of A SOC shall provide
computing resources to support
the development and maintenance
of LEND data processing
software.
U of A SOC shall provide
computing resources to support
testing with the LRO Ground
System.
U of A SOC shall provide
computing resources to support
testing with the PDS Geosciences
Node.
U of A and GSFC SOCs shall
accept raw LEND data products
from the MOC at GSFC.
T, I FN_IKI_INPUT_POST_UA
T, I, D FN_GSFC_IKI_OUTPUT_C
OMMANDS_MOC
T, I FN_SOC_SUPPORT
T, I, D FN_SOC_LEND_GDS_TEST
ING
T, I, D FN_SOC_LEND_PDS_TEST
ING
T, I, D IF_MOC_INPUT_UA,
IF_MOC_INPUT_GSFC
Internal Test (2-18-09) IKI is currently using
existing and working
mechanisms for files
delivery.
Erik Timmermann
Complete (01/23/09) Erik Timmermann via
Richard Starr
Complete The Computer called
Utopia.lpl.Arizona.EDU
runs the LEND SOC’s
server processes as well as
the relation database. This
machine is regularly
Completed/Currently
Participating. Fully
verified during the
backed up.
Erik Timmermann
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 432
Federal Space Agency of Russia
TVAC.
Completed PDS E-t-E
Test 3 (07/08/2008)
Complete (11/26/08)
Complete MR4
(01/21/09)
The UA LEND SOC
provided sci and hk files as
well as distribution of VC0
data .
GeoSciences PDS node
verified that compliant
PDS data was received
from the LEND SOC.
The computer
Utopia.lpl.Arizona.EDU is
receiving data into
/home/lromoc/newdata.
The computer lendsoc.gsfc.nasa.gov
is
receiving data.
Erik Timmermann
Erik Timmermann via
Susan Slavney
Erik Timmermann ,
Richard Starr

LEND_IF_011
LEND_IF_015
LEND_IF_020
LEND_IF_030
LEND_IF_040
LEND_PF_010
LEND_PF_020
LEND_PF_030
Requirements Matrix
U of A and GSFC SOCs shall
accept SPICE kernels from the
MOC at GSFC.
U of A SOC shall provide
software for Goddard SOC to
read and display raw data
received from the MOC.
U of A SOC shall accept
processed LEND data from the
LEND team at the Russian Space
Institute to be put into the U of A
database.
U of A SOC shall provide access
to all LEND data within the
LEND database to IKI SOC,
GSFC SOC, and UMD LEND
facility.
U of A SOC shall deliver PDS
compliant data products, to the
Geosciences PDS node.
U of A shall be able to receive 10
kilobytes per second from the
MOC.
The U of A LEND database
access tool will be able to support
at least 10 simultaneous users.
The U of A LEND database shall
have the capacity (250 Gigabytes
of RAID hard drive) to store all
raw and processed data generated
during the primary mission
phase.
T, I, D
IF_MOC_INPUT_SPICE_UA
,
IF_MOC_INPUT_SPICE_GS
FC
T, I, D IF_GSFC_QUICKVIEW_DIS
PLAYS
T, I, D IF_IKI_INPUT_POST_UA
T, I, D IF_SOC_QUERY_TOOL
T, I, D IF_GEO_PDS
T, I, D PF_MOC_SPEED
T, I, D PF_QUERY_TOOL_USERS_
LIMIT
T, I, D PF_BIG_DISK
Completed SIM 29 (
09/01/08) . This tested
the TCP/IP socket
interfaces as well as the
scp file transfers.
Complete MR4
(01/21/09)
Complete (9/23/2008)
Complete MR4
(01/21/09)
The computer
Utopia.lpl.Arizona.EDU is
receiving data into
/home/lromoc/newdata.
The computer lendsoc.gsfc.nasa.gov
is
receiving data.
GSFC LEND SOC is
receiving and viewing
LEND data via the LEND
Displays Software.
Internal Test (2-18-09) The processing and storage
of IKI files has been tested.
The delivery method has
also be tested and verified.
Complete (01/23/09)
verified via Email.
Complete MR4
(01/21/09)
Completed PDS E-t-E
Test 3 (07/08/2008)
Complete (11/26/08)
Complete MR4
(01/21/09)
GSFC LEND SOC was
able to download LEND
data via the LEND Query
tool.
GeoSciences PDS node
verified that compliant
PDS data was received
from the LEND SOC.
Verified via System
Administrator test.
Erik Timmermann ,
Richard Starr
Erik Timmermann via
Richard Starr
Erik Timmermann
Erik Timmermann via
Richard Starr
Erik Timmermann via
Susan Slavney
Erik Timmermann via Joe
Gotobed
Complete (11/26/08) Multi user test preformed Erik Timmermann via
Harilof Haefele
Complete (11/26/08) Utopia.lpl.Arizona.EDU
has more than 250
Gigabytes of RAID
storage.
Erik Timmermann via Eva
McDonough
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 433
Federal Space Agency of Russia

LEND_PF_040
LEND_PF_050
LEND_PF_060
LEND_PF_070
LEND_PF_080
LEND_PF_090
LEND_PF_100
LEND_PF_110
LEND_PF_120
Requirements Matrix
The U of A SOC shall provide
backup storage for disk space
used for analysis.
The U of A SOC shall provide
backup storage for disk space
used for software
development.
The U of A SOC shall provide
backup storage for user
accounts.
The U of A SOC shall backup the
incoming raw LEND science
data.
The U of A SOC shall backup the
incoming raw LEND
housekeeping data.
As SPK SPICE kernels become
available the U of A SOC shall
compute spatial and temporal
information corresponding to the
time the raw LEND data was
taken on the spacecraft.
The U of A SOC shall provide
the computing resources to
reprocess any or all raw LEND
data received if the need arises.
The U of A SOC shall deliver
data to the PDS at 3 months
intervals starting 6 month after
launch.
The U of A SOC shall provide
data processing of raw LEND
data for the nominal one year
mission.
T, I, D PF_BACKUP_ANALISYS
T, I, D PF_BACKUP_DEV
T, I, D PF_BACKUP_USER
T, I, D PF_BACKUP_RAW_SCI
T, I, D PF_BACKUP_RAW_HK
T, I PF_SPICE_CALC
T, I PF_RECALC_SPATIAL
T, I, D PF_PDS_DELIVER
T, I, D PF_DATA_PROC_ONE_YE
AR
Complete (11/26/08) The database has a weekly
incremental backup and a
monthly full backup.
Complete (11/26/08) The backup of the database
is stored onto a rotating set
of tapes.
Complete (11/26/08) The backup of the user
accounts is store onto a
rotating set of tapes.
Complete (11/26/08) The backup of the LEND
Data is store onto a rotating
set of tapes.
Complete (11/26/08) The backup of the LEND
Data is store onto a rotating
Completed SIM 29 (
09/01/08) . This tested
the TCP/IP socket
interfaces as well as the
scp file transfers..
Completed SIM 29 (
09/01/08) . This tested
the TCP/IP socket
interfaces as well as the
scp file transfers.
Completed PDS E-t-E
Test 3 (07/08/2008)
Complete
Complete MR4
(01/21/09)
set of tapes.
The SPK kernels are stored
and that data in inserted
and/or updated with this
information.
As data needs to be
reprocessed the LEND
SOC has software and
procedures to
update/reprocess the data.
GeoSciences PDS node
verified that compliant
PDS data was received
from the LEND SOC.
All data being processed
and stored the UA
Database.
Erik Timmermann via John
Pursch
Erik Timmermann via John
Pursch
Erik Timmermann via John
Pursch
Erik Timmermann via John
Pursch
Erik Timmermann via John
Pursch
Erik Timmermann
Erik Timmermann
Erik Timmermann via
Susan Slavney
Erik Timmermann
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 434
Federal Space Agency of Russia

Summary
• All elements of all LEND SOCs, needed for early and nominal mission are
complete and functional.
• All LEND SOCs are prepared for LRO operations.
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 435
Federal Space Agency of Russia

LEND SOC Backup
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 436
Federal Space Agency of Russia

SOC Commanding
Command code Command description Argument 1 Argument 2
1 Set Mode 0 – Standby
1 – Measurements
2 – Measurements with default parameters
2 Set High Voltage Detector
(0 – 9)
3 Set anticoincidences Bit values: 0 - off, 1 - on
Bit 0 – inner SC neutrons
Bit 1 – inner SC gamma
Bit 2 – outer SC
4 Set discriminator level Detector
(0 – 9)
5 Set Value 0-3 – set trigger temperature level for
corresponding heater
4 – 1PPS signal usage
6 Set collection interval time
(default value = 1 second)
Always 0
0 – HV off
1 – HV level 1
2 – HV level 2
Always 0
MSB LSB
0 – level 0
1 – level 1
0 – 255
(0 – heater is always off, 255 –
heater is always on). All
intermediate values
between 0 and 255 means
temperature level.
0 – (default value) use spacecraft
1PPS signal
1 – use LEND internal 1PPS
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 437
Federal Space Agency of Russia

LEND STOL Procedures
MOC STOL Procedure Parameter #1 Parameter #2
logic_mode
Procedure Description
ln_acilogic.proc aci_logic
ENABLE
Manage the LEND instrument ACI logic
ALL, SCOUT, SCING, SCINN
DISABLE
ln_config.proc
cfg
1 - 7
Configure LEND to a pre-defined configuration
ln_inst_htr_setpt.proc
heater
STN1, SETN, STN2, STN3
temp
-16C - 85C
Manage the 4 LEND specific instrument heater set-points
ln_pwroff.proc Power OFF the LEND instrument
ln_pwron.proc Power ON the LEND instrument
ln_set1pps.proc
pps_mode
INT
EXT
Set the LEND 1PPS Source Internal (FPGA 1PPS) or External (SC
1PPS)
ln_setdctime.proc
dc_time
1 - 65535
detector
Set the LEND Data Collection Time
ln_setdiscmstat.proc
ALL, STN1 ,SETN, STN2, STN3
CSETN1, CSETN2, CSETN3
discm_stat
ON
Manage the LEND instrument HV detector discriminator
CSETN4, SHENOUT, SHENIN
OFF
detector
hvmode
ln_sethvdet.proc
ALL, STN1, SETN, STN2, STN3
CSETN1, CSETN2, CSETN3
OFF
HIGH
Manage the LEND instrument HV detector
CSETN4, SHENOUT, SHENIN
stat
LOW
ln_setmode.proc
MEAS
STBY
Set the LEND instrument to MEAS mode or STBY mode
ln_set_config_1.proc LEND to Config #1 and do other LEND post MCC activities
ln_set_config_2.proc LEND to Config #2 and do other LEND post MCC activities
ln_set_config_3.proc LEND to Config #3 and do other LEND post MCC activities
ln_set_config_4.proc LEND to Config #4 and do other LEND post MCC activities
ln_set_config_5.proc LEND to Config #5 and do other LEND post MCC activities
ln_set_config_6.proc LEND to Config #6 and do other LEND post MCC activities
ln_set_config_7.proc LEND to Config #7 and do other LEND post MCC activities
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 438
Federal Space Agency of Russia

SOC Commanding
Command Request Form
Date Commands to be executed:
Reason for Commanding:
LEND-OAR Filename:
LRO-OAR Number:
Command
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Procedure code Procedure description Parameter 1 Parameter 2 Time Delay From Previous
Procedure (Seconds)
Institute for Space Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 439
Federal Space Agency of Russia

LOLA SOC
LRO Flight Operations Review – Section 9.5
NASA’s Goddard Space Flight Center
Mark Torrence
GSFC/SGT, Inc.

LOLA SOC: Presentation Outline
• SOC Functions
• SOC Peer Review Status
• SOC Operations Concept Overview
– Staffing Plan (Early Mission and Normal Ops)
– SOC Organization Chart
– Manual/Automated Ops Activities
– SOC Facilities
– Operations Systems/Data Flows
• SOC Readiness
– SOC Data Node Status
– Software/Tools – When was it tested
– Sustaining Engineering (SOC and Instrument FSW)
– SOC Requirements Verification
• Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 441

• LOLA-MOC
SOC Functions
– realtime
– playback
– altimetry, POD, gravity
• LOLA-LR
– ranging (ITDF)
– web display
– Consolidated Ranging Data (CRD) output
• LOLA-FDF
– CRD output
• LOLA-PDS
– science product generation
– data node
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 442

Operations Concept: Staffing Plan
• Staffing model based upon successful MOLA and NLR SOC operations
– co-I’s Neumann and Lemoine facility configuration, testing, operation.
– D. Rowlands (measurement modeling)
– M. Torrence (production lead)
– E. Mazarico (operations and analysis) post-doc.
• EDR and preliminary RDR processing is largely automated
• Early Mission:
– SOC staff monitor LOLA.
• Normal Operations: Technical Assistants - 2 FTE
– One assistant edits LOLA range data and merged LR data.
– One assistant processes tracking/OD/LR/crossover data.
– Precision Orbit Determination (POD) performed during normal work week
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 443

Operations Concept: Org. Chart
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 444

Operations Concept: Ops Activities
• Automated Operations 24x7x365
– LOLA and ancillary support data pushed by MOC distributed to appropriate SOC directories
– ITDF Data files pulled from CDDIS
– CRD and normal points generated and pushed to CDDIS and FDF.
– Real-time Earth Range/Energy display pushed to CDDIS
– Formation of EDR files
– Nominal editing and formation of quick-look RDR files
– PDS-Data Node
– Nightly synchronization to local and remote backup servers
• Manual operations
– Daily:
RDR generation using preliminary OD solutions
Editing of shots, earth ranges, review for gross errors on LROC images
Anomaly reporting
Crossover updating
– Monthly:
Crossover solutions and updates
Gravity normals and precision orbit determination
Level 5 products updated
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 445

Operations Concept: SOC Facilities
GSFC Building 33, room 321 B
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 446

Operations Concept: SOC Facilities
• Operations computers: real-time and level 0 and 1 product production
– MOC connection: Macintosh G-4, OS 10.4
– Routine processing: Macintosh G-5, OS 10.4
– ITOS: Dell lynx
• Analysis computers
– 4 Macintosh Pro dual Quad-Core 2.8 GHz Intel Xeon processor,
32 Gb RAM, 4 1-Tb internal disks, OS 10.5, with 30 in Dell flat panel monitor(s)
– 2 e-SATA external 5 Tb RAID level-5 disks
• SOC access controlled with keys; keycard access implemented prior to
launch.
• Physical security provided by GSFC
• IT security covered under GSFC Code 600 security plans
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 447

Network:
Operations Concept: Ops Sys/Data Flow
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 448

Data flow:
Laser
Fires
Laser Ranging LOLA LRO
HTSI
NGSLR
Ground Station
LR Flight
Segment
Operations Concept: Ops Sys/Data Flow
LRO Predictions, Visibility File,
SCLK file, Go/NoGo, WOTIS sched
LR Schedule,
Laser Fires
Predictions, Go/NoGo,
SCLK, Tracking Schedule
Laser
Data Flow
optical fiber
All incoming &
outgoing LR data,
plus Laser Fires & website.
CDDIS LOLA SOC
Data inputs to LR-GS
Data outputs from LR-GS
LOLA
LR Ranges
Gravity Model
LR Schedule
LOLA H/K TLM, WOTIS Sched,
SCLK file, Go/NoGo file,
Visibility File, LRO Predictions,
LRO Predictions
time, power
LOLA TLM
Ground Systems
Data Node Queries
LRO FDF
LRO MOC /
S-Band /
Ground Network
LOLA TLM
LRO
Spacecraft
PDS
PDS-D
S,Ka Sched
Ground
Network
Sched. Office
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 449

SOC Readiness: SOC Data Node Status
• IP port waivers for PDS Data Node approved by GSFC
CNE Feb 2008
• PDS archive test plan approved Jan 2008
• Data Node End-to-End data flow test passed May 2008
• LOLA Archive Volume, EDR SIS approved Aug 2008
• LOLA preliminary RDR SIS sufficient to meet most science goals approved
Nov 2008.
• Search capabilities implemented via PDS-D software
• Data Node implementation of SOC allows frequent (~monthly) updates to
Level 3-5 products, and rapid access to latest versions by science teams
and Project, as the POD, gravity, and crossover analysis proceeds.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 450

SOC Readiness: Software/Tools
• EDR and RDR processing written in Fortran and C using GNU compiler
suite.
– PDS labels and browse products are generated using shell/perl scripts, Generic
Mapping Tools (GMT), and Ghostscript (GS).
– Editing uses filters similar to those employed for MOLA, with manual editing as
needed.
– Software tools are open source GNU Public License or “Technology and
Software Publicly Available” for export control.
– MOLA/NLR/MLA architecture extensively reused.
• Precision orbit determination uses GEODYN2 software.
• RDR, GDR, and LR processing - preliminary, edited, revised
– SPICE toolkit V.62 is used for geolocation.
– Crossover software is derived from GMT.
– GDR processing uses shell scripts and GMT.
• PDS-D product server developed by Planetary Data System Engineering
Node at JPL. Grid services, profile handlers, and product handler clients to
be developed cooperatively per MOA with PDS.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 451

SOC Readiness: Software/Tools
Tool Testing Status
Activity requests originated by SOC
via scp to MOC
Internal SOC file management and
data flow
LOLA EDR and RDR automated
pipeline processing to Level 2
Tested during MRs; Sims
Tested during MRs; Sims
Not yet tested due to MOC/DMS data delivery
problem; currently being tested during GS&O
tests
LR automated pipeline processing Not yet fully tested due to lack of a fullup time
synchronization test, and lack of complete
pipeline software. The software will be finished
and tested in late March/early April during global
laser tracking network data flow tests.
Housekeeping, LR, and quick-look
display on protected website
Tested during MRs; Sims. web latency issue will
be will be tested during future GS&O tests
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 452

SOC Readiness: Software/Tools cntd.
Tool Testing Status
SPICE Tools N.62 Completed
Generic Mapping Tools (GMT) 64 bit
version
Generic Mapping Tools (GMT):
Crossover analysis and topographic
model production
GEODYN2: OD, S-band, DSN
tracking
Completed Feb 2009
tested: MOLA, NLR, etc.
Tested: e.g. see many, many publications
GEODYN2: gravity model estimation Tested: e.g. see many, many publications
GEODYN2: LR measurement model will be tested during early mission
GEODYN2: Altimeter crossover model development ongoing, will be tested during early
mission
PDS product server Completed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 453

SOC Readiness: Sustaining Eng – SOC
• SOC Ground Software maintained in consultation with
science/measurement team.
• Project reporting
• Database enhancements
– geographical search capability
• PDS node performance monitoring
– access statistics
• Hardware upgrades:
– add/upgrade analysis computers
– storage as needed to handle ancillary LRO data, mainly images
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 454

SOC Readiness: Sustaining Eng – FSW
• CRC monitors memory corruption, SEU’s flagged in telemetry
• LOLA will run even with FSW held in reset; few changes are anticipated.
• Parameter changes will be reviewed by Change Control Board:
– Review by LOLA science PI or co-I, Instrument Scientist or Engineer, and Project
member or scientist outside the immediate LOLA team.
• Parameters allow optimization of thresholds and range gates to minimize
noise and maximize sensitivity. Some adjustments will be desired during
commissioning orbit phase (30x210 km).
• Primary mission phase should require parameter changes only if there are
hardware anomalies.
• LOLA EM, BCE, and simulator available in B33/321A next to the SOC to
test changes.
• Configuration Control Board reviews changes to FSW requirements
– Algorithm Scientist, S.E., I.M., FSW Lead
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 455

SOC Readiness: Rqmt Verification
name description Partial pass verification plan
LOLA_FN_050 construct LR normal points from
full-rate data
LOLA_IF_030 ingest daily FDF OD files and
SPICE products
LOLA_IF_040 ingest ITDF formted LR data from
NGSLR and cooperating stations
via the CDDIS.
LOLA_IF_060 provide LR data to CDDIS and
FDF in CRD Format
LOLA_IF_090 provide daily updated data
products to the LOLA Data Node
of the PDS.
LOLA_PF_030 update real-time h/k Earth range
window plots within 30 seconds of
receipt
Requirement type Total Pass Partial pass
(below)
functional 10
9 1
interface 9 5 4
performance 7 5 2
Data flow incomplete, analysis underway. Verification will completed before LRO launch.
Will be verified during future GS&O testing.
Ingest of files from cooperating laser ranging sites will be tested before LRO launch
The interface has been tested and verified. s/w for exists but not yet fully tested. Will be
verified prior to launch.
Preliminary data node access verified by Engineering Node of PDS, final verification by
making actual delivery to the PDS.
An unknown latency exists somewhere in the pathway. Will be addressed during future
GS&O testing prior to launch.
LOLA_PF_040 calibrate LOLA ranges Provisional limits set based on JAXA data. Final calibrations are unavailable. Absolute
reflectance calibrations will be done in flight. s/w and resources are in place
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 456

Summary
• The LOLA SOC facility exists
• SOC peer reviews were held
• SOC personnel are identified
• Operational software has been, or will be exercised prior to launch
• Analysis software is in place
• SOC requirements have been met
The LOLA SOC is ready
to process and analyze LOLA and LR data
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 457

LOLA SOC Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 458

SOC Readiness: Requir. Ver. pt 1
name description status when comments
LOLA_FN_010 collect, analyze and trend all LOLA PASS SIM's
and
MR's
LOLA_FN_020 process approximately 2.5 Gb
telem data daily
LOLA_FN_030 maintain secure on-site and off-site
storage
LOLA_FN_040 provide for archiving and
distribution of LOLA data products
to PDS
LOLA_FN_050 construct LR normal points from
full-rate data
LOLA_FN_060 provide measurement, editing and
geolocation revisions to the RDR
monthly
LOLA_FN_070 produce Gridded Data Records
(GDR)
LOLA_FN_080 produce spherical harmonic
(SHADR) gravity potential and
selenodetic shape models
LOLA_FN_090 provide sequences to the LRO
MOC for commanding LOLA and
LR
PASS Feb
2009
PASS fall
2008,
PASS Jun
2008
Partial
PASS
PASS fall
2008
PASS fall
2008
PASS fall
2008
Full verification takes place during orbital instrument checkout
operations, and when actual PDS deliveries take place.
10 minutes to process one-day to Level 3. (MR4)
Offsite backup is at a secure MIT facility established Feb 2009
All archive files created except for higher-level product catalog file
data flow incomplete, analysis underway. Verification will completed
before LRO launch.
Simulations, numerical studies published, and prototypes implemented
on JAXA data. Geolocation revisions through crossover analysis
demonstrated using other lunar altimetric datasets. Results used for
LCROSS targeting, ULCN2005 and GSSR comparison
GMT 4.4.0 made global 128x128 px/deg topo from one-day synthetic
RDR dataset. Test of finer scale subsets demonstrated as well, using
64-bit GMT
Papers presented regarding preliminary models.
PASS MR's OAR sent during MR1 and MR4. REACT tools installed.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 459

SOC Readiness: Requir. Ver. pt 2
name description status when comments
LOLA_FN_100 host and operate PDS data search
software
PASS mid
2008
LOLA_IF_010 monitor sampled LR data in real- PASS SIM''s
and
MR's
LOLA_IF_020 obtain the daily LOLA telem and hk
data
LOLA_IF_030 ingest daily Orbit Determination
files and ancillary SPICE products
from FDF
LOLA_IF_040 ingest ITDF formted LR data from
NGSLR and cooperating stations
via the CDDIS.
PDS-D s/w installed demo. via LOLA query passed to PDS node
data are ingested from the LRO R/T h/k stream
PASS MR's sci ,MOC, and h/k data during MR1 and MR4 transferred manually by
MOC. Will be verified during future GS&O testing.
partial
PASS
partial
PASS
SIM''s
and
MR's
LOLA_IF_050 provide a real-time plot of LR data PASS Jul
2008
LOLA_IF_060 provide LR data to CDDIS and
FDF in CRD Format
LOLA_IF_070 provide instrument command files
to the MOC
LOLA_IF_080 provide the PDS Geosciences
Node with the LOLA Measurement
Data Archive Volume.
partial
PASS
Will be verified during future GS&O testing.
Ingest of files from cooperating laser ranging sites will be tested before
LRO launch
Waiting on better simulations. s/w for exists but sufficient data fidelity
is lacking, but analysis indicates adequate resources and the interface
has been tested.
PASS MR's Instrument commanding demonstrated in MR1, MR4
PASS Apr
2008
Sample archive volume submitted to PDS and peer reviewed.
Manifest and Data Brick delivered via secure copy protocol
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 460

SOC Readiness: Requir. Ver. pt 3
name description status when comments
LOLA_IF_090 provide daily updated data
products to the LOLA Data Node of
the PDS.
LOLA_PF_010 support delivery of LOLA telemetry
data from the LRO MOC within 15
minutes
LOLA_PF_020 maintain a realtime h/k telem
connection to the MOC
LOLA_PF_030 update real-time h/k Earth range
window plots within 30 seconds of
receipt
partial
PASS
PASS SIM's.
MR's
PASS SIM's.
MR's
Partial
PASS
LOLA_PF_040 calibrate LOLA ranges Partial
PASS
SIM's.
MR's
fall
2008
Preliminary data node access verified by Engineering Node of PDS,
final verification by making actual delivery to the PDS
Supported delivery of science data from MOC during each SIM, MR
and during I&T
If the cognizant data source fails to close its connection, the SOC must
manually reiitiate the connection
An unknown latency exists somewhere in the pathway. Will be
addressed during future GS&O testing
Provisional limits set based on JAXA data. Final calibrations are
unavailable. Absolute reflectance calibrations will be done in flight. s/w
and resources are in place.
LOLA_PF_050 process LOLA measurement PASS All necessary resources and capabilities are in place.
LOLA_PF_060 produce a global DEM within 30
days of nominal EOM
LOLA_PF_070 provide secure data storage and
access to the LOLA PDS Data
Node Archive.
PASS fall
2008
PASS Apr
2008
All necessary resources and capabilities are in place. Sample DEMs
produced from synthetic data, as well as from other altimetric datasets
Locations of all storage units are frozen as of Ground System
configuration freeze, 24 February 2009
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 461

LAMP Science Operations
LRO Flight Operations Review – Section 9.6
NASA’s Goddard Space Flight Center
Joel Parker
Southwest Research Institute

SOC Functions
• Monitor LAMP instrument health and safety
• Provide reports and telemetry data to instrument engineers
• Generate LAMP operations activity requests / command sequences
• Support LRO calibration planning and coordination
• Receive and process LAMP measurement data to CODMAC Level 2 and
higher
• Provide science team access to LAMP data
• Archive measurement data products and transfer to the PDS Imaging Node
• Maintain LAMP flight software and tables
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 463

SOC Design Peer Review Status
• Held 06 September 2007 at SwRI, Boulder
• Participants
– LAMP Team
– LRO Project
– LRO MOT
– External reviewers (David Gell, Sandee Jeffers, Joe Peterson)
• Primary issue categories
– SOC facilities (security, hardware capacity, flexibility of design, configuration
management)
– Contingency planning
– Operations planning
– Instrument monitoring
– Data products and PDS archives (generation, validation, documentation)
– Testing (including with simulated data)
• All substantive issues raised have been addressed in the final design of the
LAMP SOC.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 464

Staffing Plan
FTE
Level
1.5
1
0.5
0
Early Mission Normal
Operations
Management
Developers
Operational Staff
Support Staff
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 465

SOC Organization Chart
LAMP science team is
actively involved in SOC
development and ops
activities.
LAMP SOC
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 466

Automated Operations Activities
• LRO MOC will push LAMP science and HK data files, plus selected S/C telemetry
and ancillary files, to the LAMP SOC.
• Incoming LAMP science and HK data will be processed automatically to CODMAC
Level 3 on a daily basis by the data processing pipeline.
– The Pipeline Executive function will execute automatically once per day, detect and ingest
newly arrived data files, and initiate pipeline processing.
– The Data Reformat (“Lima”) function will convert raw HK values to engineering units,
reformat and package the raw science and HK data into EDR data files, and generate
engineering database files to support LAMP trending and performance monitoring.
– The Data Reduction (“Mike”) function will apply instrumental corrections and calibrations to
the raw data contained in the EDR files, temporally and geometrically locate the data via
SPICE, and output the results into RDR data files.
• Standard set of cumulative CODMAC Level 5 UV maps and spectra will be generated
automatically, but less frequently.
• Instrument performance plots will also be updated daily by the automated pipeline’s
Engineering Assessment Tool to facilitate trending analysis and health & safety
monitoring.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 467

Manual Operations Activities:
Nominal Daily Operations
• Monitoring of data processing reports and LAMP performance
– Check instrument health and safety status reports.
– Respond to non-nominal event alerts.
• Daily Planning – only a low level of planning will be needed once standard
operations are established, since LAMP observations will be highly
repetitive and autonomous.
– LAMP will be ON throughout nominal observations.
– Lunar Terminator Sensor (LTS) will be used to control cycling of HVPS levels
and aperture door.
– Standard operations will include dayside observations (through aperture door
pinhole) after minimum mission required night side data have been obtained.
– The start of new HK & science files will be tied to the start of a new acquisition
(dayside equatorial crossing).
– The LAMP team will attend the weekly ops telecons and have planning meetings
to monitor and modify activities and standard observing script as needed.
– If more substantial daily planning is required (e.g., if LTS fails), the operations
plan will be generated using predicted terminator crossing times as inputs and
will allow entry of special operations (cals, heaters, etc.).
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 468

Manual Operations Activities:
Special Operations
• Commissioning and Early Operations
• “Routine non-nominal” (monthly) activities will generally have a standard
format, though specific targets (due to visibility) and instrument parameters
will change through the mission. These activities will include:
– Calibrations (using UV standard stars)
– Heater decontamination
– Limb-tangent acquisitions
– Door performance test
• Generation of “non-standard” maps and spectra, as desired by Science
Team.
• Reprocessing of raw data through the pipeline will be commanded
manually, as needed (e.g., when new calibration or SPICE data become
available).
• Generation of PDS archives will be initiated manually. The LAMP PDS
Archive Generation function will collect processed output into archives that it
validates for submission to the PDS Imaging Node.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 469

Small
computer
room
(backup
HW location)
SOC Facilities
Large computer
room (primary
HW location)
Tombaugh Science
Operations Center
(LAMP SOC console location)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 470

SOC Network
• Data are transferred
between the LRO
MOC and the LAMP
SOC over the open
Internet using the
Secure Shell protocol.
• PDS archives on
physical media are
sent from the LAMP
SOC to the PDS
Imaging Node using a
shipping service.
• Additional processers
will need to be
purchased for pipeline
to keep up with data
flow.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 471

LRO
MOC
LRO Ancillary Data
Operations Systems / Data Flows
LAMP Real-time
VC0 HK Data
FSW Loads &
LAMP HK &
Science Data
Operations Activity Requests
LAMP Health &
Safety Monitoring
Processed LAMP HK Data
Lima
(EDR Product
Generation)
LAMP Upload /
OAR
Generation
LAMP SOC
EDR Products
Mike
(RDR Product
Generation)
Supporting
Database
RDR Products
UV Map &
Spectrum
Generation
PDS Archive
Generation
UV Maps &
Spectra
Obs Log,
Cal Data
LAMP Team
Website
(data access,
monitoring)
PDS Archives
PDS
Imaging
Node
Feedback from Engineering / Science Data Analysis
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 472

Software/Tools
SW Component Name Functional Description Status Completion Date
Pipeline Executive Controls overall data pipeline processing In implementation* 2009 April 08
SOC Web Interface Provides user-friendly data access for LAMP science
and instrument teams and SOC staff
In implementation 2009 May 01
Pipeline “Front End”
Engineering Assessment Tool Performs offline health and safety monitoring In implementation 2009 Apr 24
Data Reformat (“Lima”) Generates EDR products Complete** 2008 Dec 16
Data Reduction (“Mike”) Generates RDR products Complete** 2008 Dec 16
Mapping Suite
Pipeline “Back End”
Generate specific requested maps: counts, exposure,
flux, brightness, landform albedos, water absorption
feature depths
In design 2009 July 01
Spectrum Extractors Generate spectra of the lunar atmosphere:
nadir-pointed, limb-pointed
In design 2009 July 01
PDS Archive Generator Produces PDS archives of LAMP products Complete** 2008 May 06
Real-time VC0 Monitor
Operations
Performs real-time health and safety monitoring Complete 2008 Mar 05
FSW Upload / Operations
Activity Request Generator
Generates FSW loads and activity requests Complete 2008 Dec 16 ***
*Basic functionality in place to satisfy SOC requirements, enhancements ongoing.
green = need by launch
blue = want by early science phase
**Additional modifications in progress.
***FSW image delivery and upload ETE testing (on FlatSat) not yet done; scheduled to be completed before launch.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 473

Sustaining Engineering
• Configuration Management
– The LAMP SOC team employs the Subversion version control system to provide
configuration management for LAMP SOC files, including software source code
and related documentation.
• Error Tracking and Correction
– The LAMP SOC team employs the open source defect tracking system known as
Bugzilla to track bugs and code changes in the LAMP SOC software.
• LAMP SOC CCB
– Actions to be taken on Configuration Change Requests (CCRs) / bug reports
submitted via Bugzilla are determined by the LAMP SOC Configuration Control
Board (CCB).
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 474

Instrument FSW Maintenance Plans
• FSW and Parameter Control
– Instrument contains a version 1.00 of the flight software in PROM. This is a fully operational
version of the software that is planned to be able to support the complete mission.
– LAMP instrument flight software is maintained under CVS version control.
– Some operational parameters are maintained in a parameter file that is redundantly stored in
EEPROM in the flight instrument. This table contains settings and parameters that are
expected to need adjustment during the mission.
– Monthly maintenance will include checking the contents of the code and the parameter file.
• FSW Patches and Testing
– If during flight operations, problems are detected in the FSW or functional extensions are
deemed necessary, a patch may need to be developed for the flight software.
– Testing of a patch (including regression testing) will both use an available software simulator
and the FlatSat.
– After validation, the patch may be uploaded into one of four available EEPROM pages in the
instrument. Since the complete code image is small (

• Partial Pass
SOC Requirements Verification
Pass Partial Pass Not Verified Total
Functional 12 6 2 20
Interface 11 1 1 13
Performance 1 0 5 6
Total 24 7 8 39
– 6 requirements (5 functional, 1 interface) involve the generation and archiving of LAMP
CODMAC Level 5 maps and spectra, which are due for delivery to PDS six months after the
end of the nominal mission.
– 1 functional requirement involves data storage capacity (additional RAID storage on order,
scheduled to be in place prior to LRO launch)
• Not Verified
– 2 requirements (1 functional, 1 interface) involve the generation and delivery of LAMP FSW
images to the MOC (scheduled to be tested prior to LRO launch)
– 4 requirements (4 performance) involve future deliverables (capacity to generate deliverables
has been tested and analysis indicates adequate resources)
– 2 requirements (1 functional, 1 performance) related to pipeline upgrades that are underway.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 476

Issues / Concerns
• Full ETE Flight Operations Readiness tests have not yet been executed, including
FSW update procedure and exercise of all the ground procedures and contingencies
documented in the LRO MOC – LAMP SOC Operations Agreement.
• Overall LRO commissioning plan and how LAMP fits in is not clearly defined.
• Flight version of some RTSs and scripts that are to be scheduled for the nominal
operations and commissioning by the flight ops system are still in development.
• Not all LAMP flight rules yet incorporated in LRO Flight Rules doc (431-OPS-000309)
and implementation of flight rules by MOC and the process of feedback to instrument
team is not understood or tested.
• LAMP data pipeline is still not ready; though EDR and RDR generation and PDS
product creation and delivery are all functional, some automation is still necessary
and map generation for scientific analysis is far behind schedule.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 477

L
I
K
E
L
I
H
O
O
D
5
4
3
2
1
LAMP SOC Ops Risk Matrix
(n.b., LAMP team internal-defined matrix; not based on GSFC/LRO risk matrix schema)
5
6
4
1 2 3 4 5
CONSEQUENCES
1
7 2
3
Criticality L x C Trend
High - Decreasing (Improving)
Med
- Increasing (Worsening)
- Unchanged
Low - New Since Last Period
Approach
M - Mitigate
W - Watch
A - Accept
R - Research
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 478

Summary
• LAMP SOC Design Peer Review was held and was successful
• Staffing Plan:
– 2 FTEs planned for SOC operations, management, development and support
– Needed personnel currently identified and in place
• Planning Tools:
– Nominal LAMP operations will be autonomous, so no dedicated planning tools are needed
• Data Processing Pipeline:
– “Front-end” that generates EDR and pipeline RDR data products is complete (with some
additional functionality mods still being done) but not yet fully automated.
– “Back-end” that generates higher level map and spectral data products is behind schedule.
Completion expected by July; those data products not needed for launch or early flight.
• Data Archiving:
– EDR and pipeline RDR data products and archive volumes defined, and capability to
generate valid PDS archives developed and tested.
– Definition of higher level data products and capability to generate these PDS archives
currently under development; those products are to be delivered after nominal mission.
• Although required basic LAMP SOC functions are ready for flight operations, some
outstanding ops issues and concerns remain:
– Commissioning plan and process not yet clearly defined.
– Some aspects of nominal and contingency operations still not ready and tested/simulated.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 1 - 479

NASA’s Goddard Space Flight Center
Lunar Reconnaissance Orbiter
Flight Operations Review (FOR)
March 11-12, 2009
Day 2

LROC Science
Operations Center
LRO Flight Operations Review – Section 9.7
NASA’s Goddard Space Flight Center
Ernest Bowman-Cisneros
Arizona State University

SOC Functions
1. Planning
– ROI
2. Targeting
– Daily imaging
plan
– Off-nadir slews
3. Processing
– Systematic
4. Analysis
– Validation
– Verification
5. Distribution
– Science Team
– Public
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 3

SOC Peer Reviews
• November 27, 2005 - LROC SOC Requirements Review at NU
– Review panel: GSFC LRO project, PDS Imaging Node, Science Community
– Review of LROC SOC requirements
– 21 RFAs submitted (21 closed)
• Fall 2006, LROC moves from Northwestern University to Arizona State
University (PI, Business Manager, SOC Manager)
• February 2, 2007 - LROC SOC Peer Design Review at ASU
– Review panel: GSFC LRO Project, THEMIS, HiRISE
– Review of SOC design, software and hardware needs, staffing
– 17 RFAs submitted (17 closed)
• December 10, 2008 - LROC SOC Peer Review at ASU
– Technical staff from HiRISE and THEMIS instrument teams in attendance
– Review SOC implementation to date, including review of SOC requirements
verification matrix
– 15 RFAs submitted (11 closed, 4 open)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 4

SOC Operations Concept Overview
• Staffing Plan (Early Mission and Nominal Ops)
• SOC Organization Chart
• Manual / Automated Ops Activities
– Instrument Commanding
– Data Processing
– Data Distribution
• SOC Facilities
– Interdisciplinary A (Office / SOC Workroom / Visitor Gallery)
– ISTB-1 (Primary Machine Room / Storage)
– Goldwater (Secondary Machine Room / Storage)
• Operations Systems / Data Flows
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 5

Staffing Plan
• Early Mission (Launch, Commissioning, through first month of Primary)
– SOC Team
8 Operations Staff, 2.5 SysAdmin, 3 SW Developers, 3 Post-Docs, 3 Graduate
Students, numerous undergraduate students
– Instrument Team
– Jmoon Developers
– ISIS Developers
– HPCI Storage Team
– PIPE/REACT Developers (as needed)
• Nominal Ops (first month of Primary through EOM)
– SOC Team
8 Operations Staff, 2.5 SysAdmin, 2 SW Developers, 3 Post-Docs, 3 Graduate
Students, and about a dozen undergraduate students
– HPCI Storage Team
– Instrument Team (as needed)
– Jmoon Developers (as needed)
– ISIS Developers (as needed)
– PIPE/REACT Developers (as needed)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 6

SOC Organization
• Science Operations Team
– Operations Staff
Shane Thompson
Julie Stopar
Tim Donnelly
Sean Merritt
David Nelson
Frank Centinello
Zack Bowles
Kristen Paris
– System Administrators
Ian Bennett
Ken Bowley
Nick Estes
Student SysAdmin
– Software Developers
Jacob Danton
Nick Avlonitis
Darrin Chandler
Student developers
– High Performance Computing Initiative
Dan Stanzione, Jr. (Director)
Kirt Karl
• Science Operations Team (cont.)
– Numerous Undergraduate Students
– Jmoon Development Team (ASU)
– ISIS Development Team (USGS)
– REACT/PIPE Development Team (ACT)
• Science Team
– 7 Co-investigators
– 3 ASU Post-Doc’s
– 3 ASU Graduate Students
• Participating Scientists
– 10 Participating Scientists
• Instrument (MSSS)
• EPO Team
– Adler Planetarium
Doug Roberts
– Arizona State University
Carmen Salas
Wendy Taylor
Meg Hufford
Sue Selkirk
Sam Lawrence
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 7

SOC Uplink Operations
• Weekly tele-conference with MOC & instrument SOCs (including Mini-RF)
• Daily status meeting with on-rotation Ops, SOC manager and P.I.
• Weekly rotating schedule, with two uplink designated positions (10hr/7day
during early mission, transition to 8hr/5day - emergency contact 24hr/7day)
• Uplink-1
– Daily NAC targeting sequence for at least three days of operations
– Generate LROC command load and target request files
– Insure delivery of LROC command load and target request files to MOC
– Resolves any issues with delivered command loads and/or target request files
• Uplink-2
– Generate list of potential off-nadir observations for planning period (1 week
ahead)
– Daily NAC targeting of off-nadir slews (one week ahead)
– Special observations, submitted as an Operations Activity Request (OAR)
– Assist UL#1 if needed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 8

LROC Observation Targeting
• Command load is minimally a 3 day sliding window of NAC & WAC
observations
– Delivery timestamp, image priority (1-5), command mnemonic with submnemonics
– Validated at SOC for operational and engineering constraints
– Validated at SOC for format and naming guidelines (431-ICD-000049)
– Second and third days can be partial or complete observation plans
– Further validation and constraints checking at MOC before integration
• Target request is minimally a 3 day sliding window of off-nadir slews for
NAC observations
– Slew timestamp, off-nadir angle, duration
– Validated at SOC for operational and engineering constraints
– Validated at SOC for format and naming guidelines (431-ICD-00049)
– Further validation and constraints checking at MOC before integration
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 9

LROC Observation Targeting (cont.)
• Observation planning checklist:
– Special Observations (calibration)
– Off-nadir slews
– Priority 1 targets for NASA Constellation
– Priority 2 targets for LROC requirements
– Priority 3 and 4 targets for general science
– Priority 5 to maximize LROC downlink allocation
• Factors that affect observation planning:
– Lighting conditions, what is required by ROI
– NAC readout shadow
– Solid State Recorder usage (LROC observations)
– Mini-RF observing (share SSR partition with LROC)
– Downlink (if LRO in downlink contingency mode)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 10

LROC Targeting Examples
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 11

SOC Downlink Operations
• Weekly teleconference with MOC & instrument SOCs (including Mini-RF)
• Daily status meeting with on-rotation Ops, SOC manager and P.I.
• Weekly rotating schedule, with two downlink dedicated positions (10hr/7day
during early mission, transition to 8hr/5day - emergency contact 24hr/7day)
• Downlink-1
– Monitoring MOC delivered products
– Monitoring and maintain EDR/CDR processing pipelines
– Reporting on NAC/WAC downlink completeness for a given DOY period
• Downlink-2
– SOC Point of Contact (POC), always available by cell phone to coordinate high
priority issues (especially after-hours)
– Daily real-time instrument trending reports (for current DOY)
– Stored housekeeping instrument trending for previous 24 hrs and 1 week period
• Additional OpsTeam members are either off-schedule or monitoring RDR
product pipelines, generating special products, and other data analysis
tasks as required
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 12

• Systematic
LROC Data Verification & Validation
• Feedback loop from validation efforts by LROC Science Team
• 1st Level Verification
– MOC generated META file (missing bits in file?)
– Parameters correlation (what was commanded?)
• 2nd Level Verification
– Image Statistics (assess image quality and suitability for further processing)
– Pointing (did we capture the correct region of interest?)
– Visual Inspection (labor intensive)
• 3rd Level Verification
– Conformance to PDS product SIS (EDR/CDR/RDR)
• Validation
– Science Team, Operations Team and others (was ROI satisfied by acquired
observations?)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 13

Engineering Data Record (EDR)
Generation
• RECTOR pipeline queuing system
• NAC and WAC EDR
– LROC Science file (NAC / WAC observations)
– LROC META file (record of missing file bits during downlink)
– Housekeeping (instrument temperatures)
– MOC SPICE kernels (LRO location, pointing information, time correlation,
events)
– NAIF SPICE kernels (planetary ephemeris, leap seconds)
• Observation parameters stored in label
• Database stores meta-data (label + geographic information)
• Pipelines perform automated processing after receipt of all necessary data
• Automated Q&A tasks performed in pipeline processing
• In-house developed software (completed, undergoing testing)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 14

Calibrated Data Record (CDR)
Generation
• RECTOR pipeline queuing system
• NAC and WAC CDR (using ISIS software)
– EDR Input
– De-companding (8-bits to 16-bits)
– Dark current removal
– Flat field correction
– Conversion to radiance or I/F
– Output PDS compliant CDR file
• PDS label information is transcribed from EDR into CDR label
• Automated Q&A task performed in pipeline processing
• In-house & USGS developed software (completing development)
• On going testing between now and launch to verify functionality and product
format
• Additional development during mission as needed, based on feedback from
early mission observations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 15

Reduced Data Record (RDR)
Generation
• Use ISIS v3.x for creating mosaic products
and additional processing
• ISIS NAC camera model developed at
Arizona State University
– Development ongoing, completed end of
March
– Can test using I&T acquired data, real testing
occurs during commissioning
• ISIS WAC camera model implementation by
USGS
– Camera model developed by Peter Thomas
(Cornell)
– Monochrome mosaic generation straight
forward for framing camera
– Multi-spectral mosaic generation presents
interesting issues
– Can test using I&T acquired data, real testing
occurs during commissioning
• RDR product is PDS compliant JPEG 2000
format
– University of Arizona (HiRISE) developed
software
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 16

RDR Generation - WAC
• MARCI global mosaic 0-360 longitude,
30N to 30S latitude, 5 bands
• 80 observations used in the mosaic:
– even.cal.cub = calibrated, even framelets
– odd.cal.cub = calibrated, odd framelets
– geom.cub = geometrically processed
with even and odd framelets mosaiced
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 17

RDR Generation - NAC
• CTX mosaic, 273.6 to
275.3 longitude, -6.3 to -9.6
latitude, 10 meters/pixel
• 3 images
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 18

SOC Facilities
3 Separate Buildings on ASU
Tempe campus
• Interdisciplinary A
– Offices
– SOC Workroom
– Visitor Gallery
– Conference Rooms
• ISTB-1
– Primary Machine Room
– Enterprise Storage Volumes
• Goldwater
– Secondary Machine Room
– Enterprise Storage Volumes
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 19

SOC Facilities (cont.)
• Interdisciplinary-A
– Office Space
– SOC Workroom
– Conference Rooms
– Lunar History Walk
– Visitor Gallery
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 20

• ISTB-1
SOC Facilities (cont.)
– Server room facilities
– 1 dedicated rack for LROC hardware
– DES, Production compute nodes,
database
– 2 factor card lock, video surveillance
– UPS backup and redundant power
feeds
– Primary LROC Storage Volume
• Goldwater
– Server room facilities
– 1 dedicated rack for LROC hardware
– DES, Production compute nodes,
database2 factor card lock, video
surveillance
– 2 factor card lock, video surveillance
– UPS backup and redundant power
feeds
– Secondary LROC storage Volume
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 21

SOC Readiness - Documentation
Document Description/Purpose Current Status
SOC Requirements Capture SOC functional requirements Signed 8/2006
PDS-to-SOC ICD Captures SOC to PDS interconnection Signed 9/2006
LROC SOC Data Management &
Archive Plan
Captures SOC data management, both input and outputs, and
archive management
Signed 2/2007
IT Security Risk Assessment Captures SOC IT security risk assessment Signed 5/2007
SOC IT Security Plan Captures test plans for SOC component verification Signed 12/2007
SOC Contingency Plan Captures contingency operations for SOC Completed 12/2007
(updates with testing)
SOC Test Plan Captures test plans for SOC component verification Signed 2/2008
EDR/CDR Data Product SIS Define LROC EDR/CDR data products Signed 12/2008
LROC Data Archive SIS Define LROC EDR/CDR/RDR data archive Signed 12/2008
RDR Data Product SIS Define LROC RDR data products Signed 12/2008
LROC SOC Users Guide LROC SOC user guide & conception of operations Final Submitted
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 22

SOC Readiness - Testing
• Internal SOC testing
– Individual hardware and software components
– Integrated systems testing
– Acceptance Testing
• PDS End-to-End Testing
– Partial and complete PDS deliveries
– Data Node testing (Product Server)
• LRO Project testing
– Simulations (Sims)
– Mission Readiness Testing (MRT)
– Mission Rehearsal (MR)
• Nominal Mission Schedule by SOC personnel (Jan 1, 2009)
– Flowing data acquired from I&T and LRO Testing through system (SOC only)
– Interleaved with LRO project testing, as needed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 23

SOC Readiness - Software/Hardware
• SOC Computing Hardware (operational)
– SOC Workstations (4x Quad-core Xeon 2.8GHz, 16GB RAM, 1.2TB storage capacity)
– Database servers (2x Dual Core Opteron 2.6GHz, 8GB RAM, 2TB storage capacity)
– Data Exchange Servers (2x Dual Core Opteron 2.6GHz, 8GB RAM, 2TB storage
capacity)
– Linux Computer Servers (8x Dual Core Opteron 2.6GHz, 8GB RAM, 2TB storage
capacity)
– Data Node (Dual Xeon 2.8GHz, 2GB RAM, 1.4TB storage capacity)
– Storage Volume (NetApp storage, 530TB of storage capacity)
• Software
– Jmoon development completed and undergoing testing
– Autotarget development complete for basic, enhanced version under development
– CmdGen development complete and undergoing testing
– Sci2EDR development complete and undergoing testing
– ISIS development complete and undergoing testing
– ITOS operational
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 24

SOC Readiness - Sustaining
Engineering for SOC
Planned SW updates at end of Commissioning Phase, and at 6 months for
non-critical bugs/issues; as-needed for critical bugs/issues.
• Key ground system SW components:
– LROC cmdgen (generate products for MOC)
– Jmoon (LROC commanding)
– LROC autotarget (LROC commanding)
– ISIS: lrowac2isis, lronac2isis (ingest and processing of LROC images)
• Build/Test/Release (under source code control)
– Track bugs and new functionality
– Build SW release candidate (development environment)
– Test SW release candidate (development environment)
– Pass SW release candidate to SysAdmin for deployment to production
environment
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 25

SOC Readiness - Sustaining
Engineering for FSW
• Performed by MSSS
• Changes under strict configuration control
• Test environment used for development and test maintained at
MSSS
• Flight-like hardware for validation maintained at MSSS
• Review and approval prior to implementation via Change Review
Board
• Thorough documentation of all changes
• Committed to support through end of mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 26

SOC Readiness - LROC Data Node
• LROC Data Node (http://lroc.sese.asu.edu)
• PDS End-to-End Testing
– Partial and complete PDS deliveries
– Data Node testing (Product Server)
• Three distinct methods for searching LROC data (ongoing development):
– Textual search based on image properties
– Image Browse
– Map Browse
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 27

• Functional
SOC Requirements Verification
– 22 out of 22 verified
• Interface Requirements
– 19 out of 19 verified
• Performance Requirements
– 3 out of 12 verified
– Remaining 9 to be tested prior to LRO launch
Generation of RDR products to meet specific LROC requirements such as polar
illumination (NAC/WAC), test 7 band area mosaics, Apollo Panoramic re-imaging,
Process can be tested, actual verification requires data acquired during commissioning
and collection of actual data sets for verification
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 28

Summary
• Staffing - hired and trained, with ongoing operations testing up to launch
• Facilities - ready and occupied
• Computer Hardware - operational and tested, with ongoing testing
• Large Capacity Storage - operational and tested, with ongoing testing
• Software Development - Core capabilities operational and tested, ongoing
development for enhanced capabilities
• Instrument Commanding - operational and tested, with ongoing testing
• Data Processing - EDR and CDR generation operational, with ongoing
testing
• Data Processing - RDR generation is being completed, with testing up to
launch
• Data Node - Core capabilities operational and tested, ongoing development
for enhanced capabilities
LROC SOC is Ready!
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 29

LROC SOC Backup Slides
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 30

• 4888 defined
• Includes Cx
targets
• Apollo re-
Imaging under
review (4497)
• Planning
continues after
launch
Current ROI Master Target List
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 31

• Approach 1
Apollo Panoramic Re-Imagine
– Any opportunity where
incidence angle < 45º
• Approach 2
– Match incidence angle
and azimuth for Pan
observation
– Summed NAC
observation in extended
mission
• ROI’s defined, need
review
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 32

AutoTarget - NAC Polar Campaign
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 33

LROC Public Interface for Target
Suggestions
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 34

Mission Readiness Testing
LRO Flight Operations Review – Section 10.0
NASA’s Goddard Space Flight Center
Dave Waters
Ralph Casasanta

Test Effort to Date
• Mission Readiness test effort is an independent test effort led by the
Mission Readiness Test Lead (MRTL – Dave Waters)
– Mission readiness test effort exercises/verifies all elements within the ground
segment interfaces, end-to end data flows and Level-3 system requirements
• Ground System test effort
– Includes a series of MRTs;
– Uses other simulations, mission rehearsals, or operational readiness tests, as
required to follow-up on requirements verification
• Ground System requirements are defined in the LRO Detailed Mission
Requirements (DMR) Document
– Ground system requirements are derived from Level-2 mission requirements
– Ground system requirements are tracked via the MRT Verification Matrix,
maintained by the MRTL
– Level-3 ground system requirements maintained in DOORS and associated
requirements verification status maintained in DOORS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 36

Significant Accomplishments Since MOR
• Completed the following series of Mission Readiness Testing
– MRT1 Telemetry and Command Testing (08/13/2007 through 10/19/2007)
Initial command, telemetry and resource testing. Basic receipt, archive display and
monitoring of telemetry and the exercise of COP-1 command protocol.
– MRT2 Offline Processing Testing (11/14/2007)
Initial daily load generation and forecast scheduling capabilities. Verification of internal
MOC interface connectivity.
– MRT3 MOC Internal System Testing (8/22/2008 through 03/31/2009)
Internal MOC subsystem interface testing in conjunction with MRT, SIM, Mission
Rehearsal and ORT.
– MRT4 Space Communication Network Testing (02/25/2008 through 02/26/2009)
Initial SCN interface testing to the MOC. SCN interfaces were exercised to verify the
ability of the MOC systems to receive, process, record and account for LRO formatted
command and telemetry. Testing also leveraged network compatibility testing when
possible
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 37

Significant Accomplishments Since MOR (2)
• Completed the following series of Mission Readiness Testing (Cont'd)
– MRT5 Science Operations Center Testing (03/05/2008 through 03/27/2009)
Testing verified the ability of the SOCs to receive health and safety data from the MOC.
Testing also exercised the ability to deliver and receive pre and post support products to
and from the SOCs.
– MRT6 End to End Functional Testing (06/11/2008 through 02/13/2009)
ETE testing exercised the capability of the MOC to receive S-Band and Ka-Band
telemetry and files from the SCN and pass the data on to the SOCs. Products were
exchanged between the MOC, SCN, SOCs and FDF.
Connectivity during Mission Rehearsals were also leveraged.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 38

Documentation Status
• All documentation resides on LRO NGIN host
• LRO Ground System DMR – 431-RQMT-000048 Rev E
• ICDs
– 431-ICD-000049 – Ground System External ICD; Rev-C
– 431-ICD-000711 – Ground System Internal ICD, Rev-C
– 451-ICD-001201 – LRO MOC to NAIF ICD, Rev-C
– 451-RFICD-LRO/SN/GN Rev-1
• LRO Mission Readiness Test Plan
– 431-PLAN-000079
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 39

Documentation Status (2)
• LRO Mission Readiness Test (MRT) Test Procedures
– MRT1: Initial command, telemetry and resource testing
PROCS: 451-PROC-001194, -001272, -001319
– MRT2: Initial daily load production testing
PROCS: 451-PROC-001320,
– MRT3: Internal MOC subsystem testing
PROCS: 451-PROC-002411, -002413, -002414,-002416,-002417
– MRT4: Space Communications Network Interface testing
PROCS: 451-PROC-001613, -001684, -001787, -003054, -003205, -003307
– MRT5: MOC to SOC interface testing
PROCS: 451-PROC-001609, -001627, -001653,-001671
– MRT6: SCN-MOC-SOC; complete E2E testing
PROCS: 451-PROC-002682, -003091, -003166, -003172, -003183, -003442
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 40

Documentation Status (3)
• LRO Mission Readiness Test (MRT) Test Reports
– MRT1: Initial command, telemetry and resource testing
Reports: 451-RPT-001288, PROC-001368, -001369
– MRT2: Initial daily load production testing
Reports: 451-RPT-002883
– MRT3: Internal MOC subsystem testing
Reports: 451-RPT-003333, -003334, -003335, -003336, -003356
– MRT4: Space Communications Network Interface testing
Reports: 451-RPT-002963, -002964, -002965, -002966, -003337
– MRT5: MOC to SOC interface testing
Reports: 451-RPT-002884, -002885, -002886,-002887
– MRT6: SCN-MOC-SOC; complete E2E testing
Reports: 451-RPT-003069, -003070, -003071, -003072, -003338, -003339, -003340,
-003341, -003342, -003343, -003344, -003345, -003346, -003347, -003348, -003349,
-003350, -003351, -003352, -003353, -003354, -003355, -003356
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 41

Ops Data Product Verification Summary
• All ICD Products (External and Internal) mapped to specific DMR
requirements and requirements tracked via DOORS
• All Products flows between systems or elements verified via specific MRTs
or other mission tests, such as simulations, rehearsals, or ORTs
• Any Product failures captured via SOARS and tagged against requirement
or subsystem and associated mission test
• Total number of External ICD products identified for verification – 346
– 344 (99.4%) products verified
– 2 (0.6%) products not verified
MOC-73 MOC archive of CRaTER real-time feed – Tested in ORT by 03/13/2009
MOC-38 Telemetry to KSC – To be tested during MR5 (03/30/2009)
• Total number of Internal ICD products identified for verification – 94
– 94 (100.0%) products verified
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 42

External Product Verification Summary
• Product status by subsystem
– MOC Products- 136; 134 Verified (98.5 %)
MOC to SOC products – MOC-73 (ECR submitted to update MOC configuration for
creating CRaTER archive of real-time feed)
MOC to KSC products – MOC-38 (MOC real-time data to KSC data flow)
– FDF Products – 101; All Verified (100 %)
– NAIF Products – 32; All Verified (100 %)
– SOC Products – 25; All Verified (100 %)
– WS1 Products – 17; All Verified (100 %)
– USN Products – 11; All Verified (100 %)
– WOTIS Products – 9; All Verified (100 %)
– DSN Products – 6; All Verified (100 %)
– KSC Products – 6; All Verified (100 %)
– SN Products – 1; Verified (100 %)
– Launch Vehicle Product – 1; Verified (100 %)
– FSWM Product – 1; Verified (100 %)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 43

Internal Product Verification Summary
• Product status by subsystem (94 total products tracked)
– MPS Products – 28; All Verified (100 %)
– AGS Products – 22; All Verified (100 %)
– ITOS Products – 21; All Verified (100 %)
– MDPS Products – 11; All Verified (100 %)
– MOC Utility – 7; All Verified (100 %)
– MOT Products – 3; All Verified (100 %)
– ITPS Products – 2; All Verified (100 %)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 44

LRO
TT&C
RF Port
Test
Port
TT&C
TT&C
TT&C
BMOC
T - 025
V - 025
PV-000
N- 000
F - 000
100 %
Requirements Verification Summary
TT&C
SN
T - 053
V - 053
PV-000
N- 000
F - 000
100%
WS1
T - 096
V - 095
PV-001
N- 000
F - 000
99 %
DSN
T - 073
V - 072
PV-001
N- 000
F - 000
99 %
KSC
T - 006
V - 005
PV-001
N- 000
F - 000
83 %
USN/NMC
T - 076
V - 076
PV-000
N- 000
F - 000
100 %
Tlm/Cmds
Voice
Voice
Sched Sched / / Acq
Acq
Tlm/Cmds
Voice
Sched / Acq
Tlm/Cmds
Voice
Voice
Sched Sched / / Acq
Acq
Tlm/Cmds
Voice
Sched / Acq
Tlm/Cmds
Voice
Voice
Sched Sched / / Acq
Acq
N
IS
N
IP
T - 012
V - 011
PV-001
N- 000
F - 000
92%
Telemetry
Data
(R/T Data
Science Data
HK Data)
Commands
Voice
Scheduling
Measurement
Data
LR
T - 019
V - 019
PV-000
N - 000
F - 000
100 %
MOC/MOT
T - 077
V - 074
PV- 003
N - 000
F - 000
96 %
ITOS
T - 146
V - 144
PV-002
N- 000
F - 000
99%
Tlm
ITPS
T - 038
V - 038
PV-000
N- 000
F - 000
100 %
FSW Memory &
Table Loads
LRO MOC
FSMF
T - 001
V - 000
PV-001
N - 000
F - 000
0 %
Command
Loads
Attitude
Telemetry
Real Time And
Non-real Time
Telemetry
R/T Telemetry
Telemetry Files
Tracking Data
Acq Data
ACS Data
Loads
Science
Commands
Science
Planning
Products
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 45
Tlm Log
Files
System
Status
Orbit
Products
MAS
T - 021
V - 018
PV- 001
N - 002
F - 000
86 %
MPS
T - 055
V - 051
PV-002
N- 002
F - 000
93 %
AGS
T - 022
V - 021
PV-001
N- 000
F - 000
95 %
DMS DPS
T - 024
V - 015
PV-006
N- 001
F - 002
63 %
All
Elements
Archive Products
T - 053
V - 053
PV-000
N- 000
F - 000
100 %
FDF
T - 054
V - 054
PV-000
N- 000
F - 000
100 %
Command
Timeline
Attitude
Data
Science
Planning
Products
Summary As Of 03/07/2009
(T) Total Requirements 949
(V) Verified 922
(PV) Partial Verified 20
(N) Not Verified 5
(F) Failed 2
(%) Percent Completed 97%
N
IS
N
IP
CRaTER
Voice
Data
T - 014
V - 014
PV- 000
N - 000
F - 000
100 % DLRE
Voice
Data
LAMP
Voice T - 014
V - 014
Data
PV- 000
N - 000
F - 000
100%
T - 014
V - 014
PV- 000
N - 000
F - 000
100%
Voice
Data
Voice
Data
Voice
Data
LOLA
T - 014
V - 014
PV- 000
N - 000
F - 000
100 %
Voice
Data
Mini-RF
T - 014
V - 014
PV- 000
N - 000
F - 000
100 %
LEND
T - 014
V - 014
PV- 000
N - 000
F - 000
100 %
LROC
T - 014
V - 014
PV- 000
N - 000
F - 000
100 %

MRT Definitions
• All requirements are classified into three categories:
– Launch Critical: Requirements needed to support launch and early mission
– Mission Critical: Requirements needed to support the nominal mission
– Other: Remaining requirements that are neither launch or mission critical
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 46

Requirements Verification Summary
• Total number of requirements identified for verification – 949
– 922 (97.2 %) requirements fully verified
– 20 (2.1%) additional requirements partially verified
– 5 (0.5%) additional requirements not verified
– 2 (0.2%) Requirements failed and awaiting retests
– Need to retest these 27 Requirements via ORTs, SIMS, Rehearsals, or other
stand-alone tests
• Total number of requirements identified as launch critical– 621
– 619 (99.7%) launch critical requirements fully verified
– 2 (0.3%) launch critical requirements partially verified
– 0 (0.0%) launch critical requirements not verified
• Total number of requirements identified as mission critical – 217
– 214 (98.6%) mission critical requirements fully verified
– 3 (1.4%) mission critical requirements partially verified
– 0 (0.0%) mission critical requirements not verified
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 47

Requirements Verification Summary –
Failed Requirements
Req ID SOARS # Req
Criticality
DMR #265 S-LRO-0507
(OPEN)
DMR #267 S-LRO-0507
(OPEN)
Other New DMS
Delivery
Elements To be tested Via
DMS Delivery 03/13/2009
Retest as Stand alone MRT3 (03/25/2009)
Other DMS Will retest to verify as part of MR4 reflow –
scheduled for (03/05/2009 thru 03/13/2009)
• DMR-265 All The DMS shall provide an interface to allow users to
request data retransmissions from a list of allowable products
• DMR-267 All retransmitted data files shall be re-sent in their original
form
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 48

Req ID Req
Criticality
Requirements Verification Summary –
Deferred/Untested Requirements
Elements Need Identifier To be tested Via
DMR-197 Other MAS MAS Configuration Stand alone MRT3 (NLT 03/31/2009)
DMR-549 Other DMS New DMS Delivery DMS Delivery 03/13/2009
Retest as stand alone MRT3 (NLT 03/31/2009)
DMR-107 Other MPS MPS delivery
02/27/2009
Stand alone MRT3 (NLT 03/31/2009)
DMR-198 Other MAS MAS Configuration Verify during stand alone MRT3 (NLT 03/31/2009)
DMR-514 Other MPS MPS Delivery
received 02/27/2009
Promote to operational string
Standalone MRT3 (NLT 3/31/2009)
• DMR-197 The MOC notification system shall accept acknowledgements from paged staff
members and cease notification attempts.
• DMR-549 The DMS shall provide the ability to setup automatic reporting features to execute
either at a time interval or based upon a particular event.
• DMR-107 The MPS shall continuously update the activity map and keep an active display based
upon product creation and ingestion and/or manual editing.
• DMR-198 The MOC notification system shall utilize a schedule of personnel and escalation
scheme in the event the original staff member called does not respond. Notification and response
will be available via alphanumeric paging and electronic mail.
• DMR-514 The MPS shall provide the ability to compare what was planned versus what actually
occurred.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 49

Requirements Verification Summary –
Partially Verified Requirements (1)
Req ID Req
Criticality
DMR-204 Launch NISN &
KSC
DMR-573
SOAR 572
DMR-195
SOAR 098
Elements Need Identifier To be tested Via
Mission ITOS New LAMP FSW
Load Product
voice loops Configured and bring up Voice Loops (L-30 Days)
MOT Tests against FlatSat (NLT 03/13/2009)
Mission MAS SW Patch Stand alone MRT3 ( NLT 03/31/2009)
DMR-263 Mission DMS Awaiting Test Retest as part of MR4 reflow
Scheduled (03/05/2009 thru 03/13/2009
• DMR-204 Voice and data shall be provided for testing and launch at the KSC launch site.
Details will be documented in Launch Site Support Plan.
• DMR-573 The T&C shall support formatting and loading instrument table and software loads as
specified in the Lunar Reconnaissance Orbiter Ground System External Interface Control
Document (431-ICD-000049).
• DMR-195 The MOC notification system shall monitor all critical workstations system event
messages and logs, for system faults or out of tolerance conditions and identify those events that
require FOT notification. These systems include but are not limited to the primary T&C, MPS,
station DPS, MOC DPS, trending, network switches, firewalls, and storage arrays
• DMR-263 The MOC shall automatically transmit measurement file data to the SOC as it is made
available and full delivery will be within 12 hours.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 50

Requirements Verification Summary –
Partially Verified Requirements (2)
Req ID Req
Criticality
Elements Need Identifier To be tested Via
DMR-051 Other FSMF CNE Firewall Rules Firewall Rules form submitted
Tested immediately after rules in place
DMR-052 Other MOT In process Retest as part of MR4 reflow
Scheduled (03/05/2009 thru 03/13/2009)
DMR-106 Other MPS MPS delivery
received 02/27/2009
DMR-108 Other MPS MPS delivery
received 02/27/2009
Promote to Operational string
Standalone MRT3 (NLT 03/31/2009)
Promote to Operational string
Standalone MRT3 (NLT 03/31/2009)
• DMR-051 The MOC shall interface to other GS elements and external elements as defined in
the Lunar Reconnaissance Orbiter Ground System External Interface Control Document (431-
ICD-000049).
• DMR-052 The MOC shall receive, process, and/or distribute all real-time or periodic mission and
telemetry products as defined in the Lunar Reconnaissance Orbiter Ground System External
Interface Control Document (431-ICD-000049) and Lunar Reconnaissance Orbiter Ground
System & Operations Internal Mission Operations Center Interface Control Document (431-ICD-
000711).
• DMR-106 The MPS shall provide an activity map that includes a history of executed events, a
current plan of events, and a forecast of future events. The activity map will be created from the
occurrence or execution of events, promoted loads for uplink, manual input, and forecasted
events.
• DMR-108 The MPS shall ingest information from available MPS products, T&C event files, and
miscellaneous system files.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 51

Requirements Verification Summary –
Partially Verified Requirements (3)
Req ID Req
Criticality
DMR-146
SOAR 507 (OP)
DMR-218
SOAR 529 (OP)
DMR-262
SOAR 537 (CL)
Elements Need Identifier To be tested Via
Other DMS DMS Patch DMS Delivery 03/13/2009
Retest as Stand alone MRT3 (NLT 03/31/2009)
Other DMS DMS Patch Retest as part of MR4 reflow
Scheduled (03/05/2009 thru 03/13/2009)
Other DMS DMS Patch Received
02/24/2009
SOAR Closed via SWAT
Retest as Stand alone MRT3 (NLT 03/31/2009)
• DMR-146 The DMS shall provide the ability to manage and assign privileges to different users
for applying, re-signing, or removing digital signatures to the identified output file.
• DMR-218 Data processing, distribution, and management shall include real-time processing,
postpass processing as well as the management and distribution of data or data products to their
expected ground element destination as specified in the Lunar Reconnaissance Orbiter Ground
System External Interface Control Document (431-ICD-000049).
• DMR-262 The DMS shall receive file listing information from onboard the orbiter, including
filenames, size, and location, then compare to files received on the ground for data accountability.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 52

Requirements Verification Summary –
Partially Verified Requirements (4)
Req ID Req
Criticality
DMR-316
SOAR 591 (OP)
DMR-346
SOAR 328 (CL)
DMR-374
SOAR 328 (CL)
DMR-544
SOAR 522 (OP)
Elements Need Identifier To be tested Via
Other WS1 WS1 Patch Prime system works correctly, problem only on backup
string. WS1 patch not expected until after launch
No retest prior to launch
Other DSN ITOS Patch SOAR Closed via SWAT
Retest during all scheduled DSN ORTs
Other ITOS ITOS Patch SOAR Closed via SWAT
Retest during all scheduled DSN ORT s
Other DMS DMS Patch DMS Delivery 03/13/2009
Retest as Stand alone MRT3 (NLT 03/31/2009)
• DMR-316 WS1 shall minimally provide statistics included in Table 3-2. WS1 Ground Station
Quality Statistics and will be delivered using the status packets as defined in the Lunar
Reconnaissance Orbiter Ground System External Interface Control Document (431-ICD-000049).
• DMR-346 At a minimum, the statistics provided from the ground station shall be via station
monitor block and will include the items in Table 3-4. S-Band Ground Station Quality Statistics.
• DMR-374 The T&C shall provide the capability to receive, process, and store SCN status data
independently from the SC telemetry. The packet format for status data is specified in the Lunar
Reconnaissance Orbiter Telemetry and Command Database Handbook (431-HDBK--000053).
• DMR-544 The DMS shall determine file data quality information and the time period covered
within the file (start and stop time), then determine, calculate, and track data accountability and
continuity associated with a particular data product.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 53

Requirements Verification Summary –
Partially Verified Requirements (5)
Req ID Req
Criticality
DMR-547
SOAR 522 (OP)
Elements Need Identifier To be tested Via
Other DMS DMS Patch DMS Delivery 03/13/2009
Retest as Stand alone MRT3 (NLT 03/31/2009)
DMR-563 Other AGS AGS Training Plan Training done post-launch (NLT L+60 D)
DMR-670 Other MOT NAIF Accounts
configured
DMR-687 Other MOT Provide ssh keys to
NAIF personnel
Retest as Stand alone MRT5 with NAIF (NLT
03/27/2009)
LRO sys admin coordinating with NIAF
Retest as Stand alone MRT5 (NLT 03/27/2009)
• DMR-547 The DMS shall provide the ability to query and report the results to the user based
upon any information stored while gathering data quality and accounting information. The
information reported back to the user will be available for custom reporting.
• DMR-563 The AGS group shall provide user documentation, procedures, and training for the
AGS delivered to the MOC.
• DMR-670 The MOC shall generate and distribute the SPICE Spacecraft Clock (SCLK)
Coefficients as defined in the NAIF/PDS Interface Control Document with the LRO Ground
System (451-ICD-001201).
• DMR-687 The MOC shall be capable of retrieving and distributing products to the NAIF as
defined in the NAIF/PDS Interface Control Document with the LRO Ground System (451-ICD-
001201).
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 54

Remaining Work
• Complete all remaining documentation and DOORS updates
• Verify two remaining Ground System Products
– MOC-73 product for CRaTER – ORTs completed NLT 03/13/2009.
– MOC-38 telemetry to KSC – MR5 rehearsal scheduled for 03/30/2009
• Verify all remaining requirements
– Failed – Two remaining (neither launch nor mission critical)
DMR-265 (SOARS 507) – Retest via stand-alone MRT3 (NLT 03/31/2009)
DMR-267 (SOARS 507) – Retested via Mission Rehearsal 4 reflow (03/05-13/2009)
– Deferred – Five remaining (neither launch nor mission critical)
DMR-197 – Verify during stand-alone MRT3 (NLT 03/31/2009)
DMR-549 – Verify during stand-alone MRT3 (NLT 03/31/2009)
DMR-107 – Verify during stand-alone MRT3 (NLT 03/31/2009)
DMR-198 – Verify during stand-alone MRT3 (NLT 03/31/2009)
DMR-514 – Verify during stand-alone MRT3 (NLT 03/31/2009)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 55

Remaining Work (2)
• Verify all remaining requirements (Cont)
– Partially Verified:
Launch Critical – One remaining (DMR-204)
– Partially Tested for data circuits, need to complete for voice circuits
– Scheduled for NLT L-30 days
Mission Critical – Three remaining (DMR-573, DMR-195, DMR-263)
– LAMP FSW Load (SOAR572) MOT Retest NLT 03/13/2009
– MAS Configuration (SOAR 098) Stand-alone MRT3 NLT 03/31/2009
– Deliver file data to SOCs Ongoing as part of MR4 reflow (03/05-13/2009)
Others – fifteen remaining
– FSMF (1) – Require CNE Firewall rule update; retest immediately
– DMS (5) – Retesting several as part of MR4 file reflow; one during MR5, others require new
DMS patch (03/13/2009) and will retest/verify as a stand-alone MRT3 NLT 03/31/2009
– MPS (2) – MPS SW patch delivered 02/26/2009); going through SWAT phase; retest as a
stand-alone MRT3 NLT 03/31/2009
– ITOS (1) – retest as part of upcoming DSN ORTs
– AGS (1) – Only requires AGS training of MOT staff; completed NLT L+60 days
– MOT (3) – retest as stand-alone MRT5 with NAIF NLT 03/27/2009
– WS1 (1) – only affects back-up string; SW patch delivered post-launch. LRO will revalidate
after delivery and will coordinate with MOT to ensure no test impact to mission
– DSN (1) - .retest as part of upcoming DSN ORTs
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 56

Summary
• The ground segment is ready to support LRO
• Functionality and operability of the LRO ground system, networks, Flight
Dynamics, and Science centers has been demonstrated
• All interface products verified
– DMS Remote agent validates naming convention
– LRO elements verify data format, content, and values since no errors
encountered
• All requirements expected to be completely verified by ground system
freeze date (L – 60 D) with the following exceptions
– DMR-562 – AGS Training – no impact since this occurs naturally within the L+60
time frame
– DMR-316 – WS1 SW patch for backup system; no expected impacts. The
missing data specifically are for two station status mnemonics:
Neither of the identified mnemonics are mission or launch critical
– the number of telemetry frames received in the 'lock' status
– number of frames that contained errors which were successfully corrected
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 57

Launch and Early Mission Operations
LRO Flight Operations Review – Section 11.0
NASA’s Goddard Space Flight Center
Rick Saylor
Deputy Mission System Engineer

Agenda Topics
• Changes since MOR
• Pre-Launch Timeline and Configuration
• Pre-Launch Communications
• Launch Commit Criteria
• LRO Launch Configuration
• Early Mission Activities
– Launch through Separation
– Initial Acquisition
– Cruise
– LOI
– Commissioning
– Transition to Nominal Mission
• Staffing for Early Mission
• Planning & Coordination
• Contingency Management
• Trending
• Road to Launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 59

Launch Countdown Overview
• Atlas V Integrated Launch Count (ILC)
– Typical Atlas V countdown sequence, includes launch vehicle activities, launch
polls, etc. LRO Project Manager responsible for providing LRO status and ‘GO /
NO-GO’ poll.
• LRO Orbiter Launch Day Configuration Procedure
– Activities are outlined in the System Engineering Report: LRO Launch Day
Configuration (451-SER-002727). Identifies orbiter activities that will be
performed by the LRO launch team at KSC. The procedure includes power-up,
aliveness checks, and verification of launch mode configuration.
• LRO Ground System Launch Countdown Sequence
– Integrated countdown sequence for the ground system and operations elements.
Includes activities to checking and verifying ground system and operations
launch readiness status. Sequence identifies polls in the ILC and status
information is relayed prior to these polls from the flight director to the LRO
Project Manager
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 60

Pre-Launch Timeline
Time (min) Events
L – 720 MOC is staffed, prepares for Launch
L – 660 Initial MOC Network I/F Tests start
L – 360 LRO begins power up
L – 300 Initial MOC Network I/F Tests Complete
L – 330 Weather Briefing
L – 240 LRO Aliveness Test is complete
L – 240 GS&O Network Status Poll
L – 180 Final MOC to Ground Network I/F tests
L – 160 Flight Director provides Status to LRO SMD
L – 148 LV Poll for Cryogenic Tanking
L – 140 Weather Briefing
L – 120 GS&O Network Status Poll
L – 120 Built in 5 minute hold
L – 60 GS&O in Initial Acquisition Configuration
L – 30 LRO Orbiter transition to 2kbps EELV tlm
L – 13 Final Launch Poll
L – 10 LRO Orbiter transition to internal power
L – 5 Poll LRO SMD, S/C Ready for Launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 61
LRO
LCROSS

LRO Launch Day Configuration Procedure
• Plan to start orbiter launch mode configuration
procedure ~L-6 hrs
– Power up the orbiter
Verify telemetry connections to the MOC/LSR from KSC
– Aliveness Tests
Test EELV Telemetry I/F
MIMU Telemetry Checks
1553 Bus Checks
PDE telemetry verification
USO (9500 & 9600) checks
Reaction Wheel tests
Power on ST 1 & 2
Aliveness checks with each instrument except Mini-RF
– Configure orbiter into launch configuration mode and verify
– Synchronize time with GMT
– Start FSW Command Loop Test (~15 minutes)
– At L-31 minutes, transition to 2kbps EELV launch telemetry
– At L-11 minutes, transition to internal power
– If launch occurs
Setup and prepare for telemetry connections from the MOC for initial acquisition
– If recycle occurs
Enter new launch time and re-enter the flow, decision will be made to return to external power
– If abort occurs
Bring orbiter back on external power
After polling of the engineering team, power down the orbiter
• Launch day procedure exercised three times at GSFC
and twice at KSC
LRO Launch Mode Configuration Procedure
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 62
Mission
Lunar Reconnaissance Orbiter (LRO)
Report Title
LRO Launch Mode Configuration Procedure
Prepared By:
Rick Saylor
LRO Deputy Mission System Engineer
(451-SER-002727, Rev E)
Date
February 15, 2009
SER Status/Revision
Released / Rev E
Document Number: 451-SER-002727
Scope/Purpose:
The purpose of this SER is to document the top-level requirements for configuring the Lunar
Reconnaissance Orbiter (LRO) for launch. The detailed procedure for placing the LRO orbiter
in the launch configuration will be a ITOS STOL procedure called,
“orbiter_launch_config.proc”.
Revision History:
06/09/2008 - Initial Release, includes just top level outline for orbiter testing
08/09/2008 - Updated based on latest concepts for orbiter configuration and aliveness testing
08/18/2008 - Updated based on initial review and added missing items to the configuration proc
09/29/2008 - Updated based on initial execution during MR #2
11/20/2008 - Revision D, updates based on additional testing during thermal vac
02/15/2009 - Revision E, updates based on first test run at KSC

Countdown Monitoring
• LRO will have two teams monitoring launch day telemetry
• KSC team will be responsible for executing the launch day procedure
– Include System Engineer, Spacecraft Test Conductor, and selected subsystem
engineers
– Team supports from the Astrotech control room
– Lead System Engineer responsible for pre-launch status and readiness “GO”
calls to the LRO Project Manager on the state of the orbiter
• Engineering team located at GSFC Mission Operations Center
– Include Systems Engineers, orbiter engineering team and operations
– Provide a second level of monitor and helps to troubleshoot any potential
problems
– Ground system and operations team verifies ground element status
– Flight Director responsible for pre-launch status and readiness “GO” calls to the
LRO Project Manager
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 63

LRO Early Mission Roles
KSC
Location
GSFC
Position/Role ASO ASOC MOC LSR Description
Overall responsibility for the LRO project, progress, and key mission descision.
Mission Director For pre‐launch, provides the official readiness status (GO / NO‐GO) for the LRO
project team.
Final authority for all real‐time decisions and command activities with the
Flight Director orbiter. Only person that is allowed to provide direction to the MOT
regardling orbiter commanding.
Assists the flight director during critical operations such as Launch, MCC, and
Mission Engineer LOI. Mission Engineer helps to collect and process information coming from
the engineering team and through telemetry.
Real‐time position for all early mission thruster maneuvers. Communicates
Flight Dynamics Officer with flight dynamics team. During LOI, will provide restart information and
calculate minimum capture time.
System engineer helps maintain situational awareness across the orbiter
LRO Systems systems and advises the flight director. Helps communications across
subsystem teams in the LSR.
Operations Lead
Operations lead or shift lead for the MOT. Responsible for directing the flight
controller and other positions within the MOT.
KSC LRO Systems
Lead systems engineering at KSC for the LRO launch team. Responsible for
directing and monitoring the launch day configuration procedure.
Spacecraft Test Conductor
Responsible for executing the launch day configuration procedure and any
orbiter commanding activities from KSC.
Payload Systems
Single point of contact for all real‐time instrument activities. Monitors
instrument telemetry and interfaces to the individual instrument teams.
Subsystem Engineering
Engineering point of contact for each subsystem. For launch, engineering
support will be provided both at KSC and at GSFC.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 64

Pre-Launch Communications
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 65

Launch Commit Criteria
LRO Launch Commit Criteria is documented in the Launch & Early
Mission Handbook (451-HDBK-001299) and the KSC LSP Launch Commit
Criteria Matrix
Mandatory
A requirement that is necessary to either make mission or verify mission success.
Can only be waived in extreme cases, and only prior to the terminal count. NASA
Policies LSP-PD-120.05 and NPD 8610.24A prohibit waiving mandatory constraints
within the terminal count.
Required
A requirement that is necessary to either make or verify mission success; however,
can be waived with the proper work around or rationale. For spacecraft constraints,
assets defined as required can be waived by the Mission Director with concurrence
from the NASA Launch Manager.
Desired
A “nice to have” asset, but not necessary to make mission or verify mission success
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 66

Launch Commit Criteria
Element Rule ID Rule Rationale State
LC-01
Orbiter shall be in launch configuration mode prior to final LV
Maximizes success for initial acquisition
Poll
Mandatory
Orbiter
LC-02
Orbiter telemetry is being received by the LRO GSE located
at Astrotech facility
Ability to monitor health of orbiter prior to launch Mandatory
LC-03 Battery is fully charged prior to switch to internal power Maximizes power for initial acquisition contingencies Required
LC-04 Prime & Backup T&C system are operational
Ability to receive telemetry and send commands during
initial acquisition
Mandatory
LC-19
MOC is receiving orbiter telemetry from KSC during prelaunch
count
Allows LRO engineering team to monitor events and
health of orbiter prior to launch
Required
LC-05 Engineering telemetry stations are operational Ability to receive telemetry for engineering team Required
MOC
LC-06 Offline trending system is operational
Ability to trend and troubleshoot problems during
mission
Required
LC-07 Mission Planning System is operational
Ability to re-plan nominal sequence of events after
launch
Required
LC-08
Launch Support Room Operational and receiving data from
the MOC
Ability to support engineering team Required
LC-09 Mission launch team is staffed and on console
Perform pre-launch functional checks and monitor
orbiter data
Required
Flight Dynamics
LC-10
LC-11
FDF is staffed and operational
FDF Product Center is operational
Perform post-launch product updates
Allows MOC to retrieve necessary product updates
Required
Desired
LC-12
Voice lines are configured and operational between the MOC Aids in directing and communicating with the different
and early mission ground stations
groups during initial acquisition
Mandatory
LC-20
Voice lines are configured and operational between the MOC Required for relaying ground and mission team
and LRO team at KSC
readiness for launch.
Mandatory
NISN
LC-13
Data lines are operational between the MOC and Early
mission ground stations
Ability to send commands and receive telemetry Mandatory
LC-14 Data lines are operational between FDF and WOTIS Ability to send updated acquisition aids to networks Required
LC-14 Data lines are operational between FDF and DSN Ability to send updated acquisition aids to networks Required
LC-15 Data lines are operational between the MOC and FDF
Ability to send product updates to the MOC for planning
Desired
and troubleshooting
LC-16 Space Network is operational for post-separation coverage
Allows coverage during gaps after separation. The gaps
Required
are dependent on launch day.
Space
Communications LC-17
Network
LC-18
Ground station is operational that can provide full TT&C
support within the first 30 minutes after separation
GN WOTIS system is operational
Required for post-separation health monitoring and
commanding activities
Forward mission products to the different networks
Required
Required
LC-21 GN WOTIS System can interface to USN and WS1
Allows for the WOTIS system to send update acquisition
Required
products if needed.
Launch Vehicle
LC-22
LC-23
Required to prevent liftoff loads from exceeding
ASWS - Water suppression system active
allowable levels
Fairing and LRO Separation Video received near real-time at Allows video coverage near real-time of critical launch
LRO MOC
events
Mandatory
Required
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 67

Early Mission Timeline
• Early Mission Timeline was developed to provide detailed activity sequence
from separation through start of commissioning activities
– Timeline from separation through LOI-1 was used during MR2
– Pieces of the timeline was also the basis for several mission simulations
• Timeline updates since MOR include
– Adding additional information for possible contingencies
– Include key verification for steps
– Several minor updates to the sequence based on test results
• Plan to release final revision at L-30 days and include in the Launch and
Early Mission Handbook
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 68

Early Mission Timeline
Lunar Reconnaissance Orbiter Highlights Version: 1.1
Early Mission Sequence of Events (Launch through End of Lunar Orbit Acquisition) ‐ Launch Date: May 21, 2009 Shifts Date: February 25, 2009
ID P/B
GMT
(mm/dd ‐ hh:mm:ss) DOY
Time since
Separation
(dd ‐ hh:mm:ss)
Type Resp. Activity Description Operations Procedure Sequence
Duration
(hh:mm:ss)
Key Verification
Planned Contingencies
ID‐0027 P 05/21 ‐ 22:16:50 141 00 ‐ 00:00:00 R/T Orbiter Orbiter Separation from Altas V
ID‐0028 P 05/21 ‐ 22:16:59 141 00 ‐ 00:00:09 R/T Space Network Telemetry Acquisition 00:01:00
P R/T Station 28 ‐ A: SN Telemetry Acquisition @ 2kbps A. LRO‐COMM‐001 (Negative Acq)
P R/T Station 28 ‐ B: SN Command Carrier is OFF
P R/T Ops 28 ‐ C: Acquire SN telemetry on OPSITOS4
P R/T Ops 28 ‐ D: Distribute Telemetry within MOC and LSR
P R/T Ops 28 ‐ E: Setup Relay to KSC for VC0
ID‐0029 P 05/21 ‐ 22:17:59 141 00 ‐ 00:01:09 R/T Ops Post Separation Verification 00:15:00
P R/T Ops 29 ‐ A: Verify Separation Sequence RTS 5 State = "EXECUTING"
RW1‐4 Pwr State = "ON"
S‐Band Xmit State = "ON"
S‐Band Ranging St = "OFF"
Xmit Subcarrier = "OFF"
Telemetry Rate = "2kbps"
A. SWSC_STARTSTOP_RTS(START, 5)
P R/T Ops 29 ‐ B: Post‐Separation Config Check SC_LAUNCH_CONFIG_VERIFY Sys Mom < 72 Nms B. LRO‐GNC‐008 (Emergency De‐Spin)
C. LRO‐GNC‐007 (RW Failure)
P R/T Flight 29 ‐ C: Poll team on Post‐Separation Telemetry Mission Engineer = GO / NO‐GO
Comm = GO / NO‐GO
Systems = GO / NO‐GO
GN&C = GO / NO‐GO
Power = GO / NO‐GO
ACS HW = GO / NO‐GO
FSW = GO / NO‐GO
P R/T Ops 29 ‐ D: Verify Sun Acquisition D. LRO‐GNC‐003 (Sun Acq. Failure)
ID‐0030 P 05/21 ‐ 22:20:51 141 00 ‐ 00:04:01 R/T AOS @ 2kbps ‐ USN ‐ Dongara (USPS) 05:35:00
P R/T Ops 30 ‐ A: OPSITOS1 Configure
P R/T Station 30 ‐ B: Lock @ 2kbps Direct Carrier
P R/T Station 30 ‐ C: Command Carrier Off
P R/T Station 30 ‐ D: LOS @ 01:06:38
ID‐0031 P 05/21 ‐ 22:21:15 141 00 ‐ 00:04:25 Info Mission Eclipse ‐ Penumbra Entry 00:00:04
ID‐0032 P 05/21 ‐ 22:25:51 141 00 ‐ 00:09:01 R/T Poll for Transition to Higher S‐Band Rate 00:01:00
ID‐0033 P 05/21 ‐ 22:25:53 141 00 ‐ 00:09:03 R/T Station AOS @ 2kbps ‐ DSN ‐ Canberra 34m BWG‐1 (DS34) 06:33:00
P R/T Ops 33 ‐ A: Verify 2kbps telemetry lock
P R/T Ops 33 ‐ A: Acquire telemetry using OPSITOS2
P R/T Ops 33 ‐ B: Perform command sweep @ test cmds /SWCINOOP CDU State = "LOCK"
Uplk Recv = "LOCK"
P R/T Station 33 ‐ D: LOS @ 01:19:10
ID‐0034 P 05/21 ‐ 22:26:51 141 00 ‐ 00:10:01 R/T Transition to 128kbps Telemetry 00:05:00
P R/T Ops 34 ‐ A: Verify station has lock on 2kbps
P R/T Ops 34 ‐ B: Verify Station 128kbps configuration
P R/T Ops 34 ‐ C: Verify Command Link /SWCINOOP CI Cmd Counter = +1
CI Reject Counter = 0
P R/T Ops 34 ‐ D: Switch to 128kbps Telemetry SWTO_SET_SBAND_TLM_RATE(128, TO64KTABLE) S‐Band Rate: S_128Kb
TO Filter Tbl: TO64Knom
P R/T Ops 34 ‐ E: Disable AP 80 SWLC_ACPTCFG(DISABLED, 80, 80) AP 80: "DISABLED"
P R/T Ops 34 ‐ F: Configure Orbiter and Ground Station for SWTO_ENADIS_SBAND_RANGING
Ranging = ON
Ranging
Ranging Filter = GN / DSN
GS Ranging = ON
P R/T Ops 34 ‐ G: Start LDS Data Dump SWCF_PLAYBACK_LDS(DIR, YES) LDS Mode = "NOWRAP"
CFDP D/L = "ACTIVE"
P R/T Ops 34 ‐ H: Release SN Support
ID‐0035 P 05/21 ‐ 22:31:51 141 00 ‐ 00:15:01 R/T SSR Turn‐ON & Configuration 00:10:00
P R/T Ops 35 ‐ A: Power and Configure DSBs SWFM_PWR_ON_DSB(ON_EDAC) DSB 1‐4 = "ON"
MS Scrubbing = "ENABLED"
Scrub Rate = "24‐Hours"
P R/T Ops 35 ‐ B: Change DS Filter Destination Table SWDS_CHANGE_FILTER_TABLE("NOMINAL") DS Table = "DSNOMINAL"
P R/T Ops 35 ‐ C: Set Max File Size for SSR SC_SETMAXFILESIZE(SSR, 15000000)
P R/T Ops 35 ‐ D: Verify Basefile names are set Base File Name = SC_2009141_ A. SC_SETALL_BASEFILENAMES
P R/T Ops 35 ‐ E: Dump FSW Spacecraft Events SC_DUMP_EVENTS
ID‐0036 P 05/21 ‐ 22:41:51 141 00 ‐ 00:25:01 R/T PDE Inhibit Checks & Catbed Turn‐On 00:01:00
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 69

Atlas V Flight Profile
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 70

Space Network
Post-Launch Data Flow Overview
WS1/USN
DSN
Orbiter Telemetry
EELV Interface
Tracking Data
Main
TCW
(ITOS)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 71
Pre
Launch
MOC
Tracking Data
Post
Launch
Eng.
Terminals
(ITOS)
LSR
FDF
Astrotech
GSFC

Separation Activities
• Spacecraft FSW monitors three separation
breakwire status
– At least 2 out of 3 signal indicates separation, the FSW
separation flag is set to “SEPARATION”
– FSW Action Point monitors the telemetry point and
starts RTS 5 after 3 seconds
RTS ID Functions
RTS #5 Cycle PDE Load Services (remove inhibits)
Turn on S-Band Transmitter
Command Sun-Safe
Turn on RW 1-4
Starts RTS #6 (after 75 minutes)
RTS #6 Configures PDE
Fires Solar Array Release Mechanism
Start RTS #7
RTS #7 Turns on Solar Array GCE
Configures gimbals
Start RTS #8
RTS #8 Drives Solar Array Z Gimbal 90°
Wait 20 minutes
Drives Solar Array Z Gimbal back to INDEX
Disables RTS 6-8
Nominal plan is to command solar array deployment from the ground after Sun-Acquisition is complete
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 72

Initial Acquisition
• Initial Acquisition Contingencies
– Negative Acquisition (LRO-COMM-001)
– Failed Separation Signals (Start RTS 5)
– Sun Acquisition Failure (LRO-GNC-003)
– High Tip-Off Rates (LRO-GNC-008)
– Solar Array Deployment Failure (LRO-MECH-002)
– HGA Deployment Failure (LRO-MECH-001)
Successfully exercised during MR-2, SIM-05, SIM-
10, SIM-11, SIM-24, SIM-27, SIM-28, SIM-30
Initial Acquisition State
RWs ON
S-Band Transmitter ON
Telemetry Rate 128 kbps
Solar Array Deployed
Solar Array GCEs ON
HGA Deployed
HGA GCEs OFF
LDS Recorder Dumping
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 73

Initial Acquisition Coverage Details
• SN Coverage is planned for post-separation
– Plan to release SN coverage after successful transition to 128kbps
• May 21 st Launch Date
– Ground Station coverage starts ~4 minutes after separation
– First station is USN – Dongara
Initial command uplink is planned for Dongara
– DSN – Canberra views starts ~9 minutes after separation
– Both USN and DSN maintain view of LRO for several hours
Station ID 22:16
May 21st Launch Date
22:17
22:18
22:19
22:20
22:21
22:22
22:23
22:24
22:25
22:26
22:27
22:28
22:29
22:30
22:31
22:32
22:33
22:34
22:35
22:36
22:37
22:38
22:39
22:40
22:41
22:42
22:43
22:44
22:45
22:46
22:47
22:48
22:49
22:50
22:51
22:52
22:53
22:54
22:55
22:56
22:57
22:58
22:59
23:00
23:01
23:02
23:03
DSN‐Goldstone 34m BWG DS24
DSN‐Goldstone 34m HSB DS27
DSN‐Canberra 34m BWG DS34 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
DSN‐Canberra 34m HEF DS45 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
DSN‐Canberra 26m DS46 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
DSN‐Madrid 34m BWG DS54
DSN‐Madrid 34m HEF DS65
USN‐Hawaii USHS
USN‐Dongara USPS X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
USN‐Kiruna KU1S
USN‐Wielheim WU2S
GN‐WS1 WS1S
SN‐TDRS X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 74
23:04
→
→
→
→

LRO Post-Separation Power
Assumes power on one Solar Array Panel
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 75

LRO Post-Separation Power
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 2 - 76

Cruise Activities
Day 1 Day 2 Day 3 Day 4
• Separation
• Initial Acquisition
• SA and HGA Deploy
• Observing Mode Transition
• Thruster 1-shots
• Delta-H maneuver
• Load Ephemeris & ATS
• Transition to HGA Comm
• Collect tracking data
• MCC maneuver planning
• MCC – E Maneuver
• MCC maneuver
• CRaTER Turn-On
• LEND Turn-On
• Mini-Gyro Calibration
• LEND Config (~3 hrs)
• LEND Config (~3 hrs)
• LOI Maneuver Planning
• LROC SW HTR Turn On
• LOI Maneuver Planning
• Open HPLV and Pyro Valve
• Delta-H Maneuver
• LOI-E Maneuver
• LOI-1 Maneuver
• LOI-2 Maneuver Planning
• All activities captured on Early Mission Timeline
• Priority given to activities for planning and executing MCC and LOI Maneuvers
• All critical activities will occurred during the “prime” shift, backup shift will monitor, perform
offline line activities, and prepare for next day’s prime shift activities
• SSR data will be dumped almost continuously, priority given to spacecraft engineering data
Activities successfully exercised during MR-2, SIM-04, SIM-05, SIM-07, SIM-10, SIM-11,
SIM-12, SIM-14, SIM-17, SIM-20, SIM-21, SIM-24, SIM-27, SIM-28 and SIM-30
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 77

MCC Planning Overview
Pre-Burn Activities
Switch to 8kbps Telemetry for maneuver, Switch to Omni Communication
Enable Catbed Heaters
Configure Safing
Index SA and HGA
Configure PDE and Thrusters
Perform Slew to burn attitude
Load Delta-V Parameters to FSW
Start Delta-V Maneuver
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 78

Lunar Orbit Acquisition
• Series of five maneuvers, final maneuver achieves the commissioning orbit
– Each LOI maneuver will occur on separate days, roughly 24 hrs apart
• For each LOI maneuver, flight dynamics will generate a preliminary and final
maneuver plans
– Both plans will be generated and verified on flatsat prior to uplink to the orbiter
Nominal May 21 Launch Times
Time
Duration
(hh:mm:ss)
LOI ‐ 1 05/25 ‐ 19:44:13 0:38:11
LOI ‐ 2 05/26 ‐ 20:54:53 0:12:00
LOI ‐ 3 05/27 ‐ 21:28:08 0:12:00
LOI ‐ 4 05/28 ‐ 21:14:32 0:10:45
LOI ‐ 5 05/29 ‐ 19:24:05 0:03:52
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 79

LOI – 1 Maneuver Details
• Plan to use dual DSN coverage for LOI-1
– DSN – Goldstone will provide coverage
– DS24 (BWG-1) is Prime (w/Command)
– DS27 (HSB) is backup
– Station comes into view ~3 hrs before LOI
• LOI Maneuver ATS
– Contains all commands for maneuver
– Command sequence starts ~60 minutes before burn
Telemetry configuration
Catbed Turn On
Safing Configuration
SA and HGA Gimbal Control
Attitude slew to burn target
Thruster/PDE Configurations
– Contains ~90 minutes of attitude commands for
contingencies
LOI-1 maneuver was exercised
during MR-2, SIM-04, SIM-12, SIM-
14, SIM-17, and SIM-21
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 80

LOI – 1 Contingency Operations
• LOI Contingency and Recovery procedure define in LRO-SYSTEM-004
– LOI Contingencies were exercised during MR-2, SIM-14, and SIM-21
– Restart will be attempted if not captured (~less than 50% of the maneuver)
If burn interruption occurs after minimum capture point (based on Flight Dynamics
Determination), burn restart will not be attempted
Burn Contingencies
• Loss of Communications
BMOC & MOC Simultaneous
telemetry
Processor Reset (Cold or Pwr Cycle)
• Burn Interruptions
Attitude Errors
PDE or IRU problems
Processor Reset (Soft)
LOI-1 Contingency Restart Aids
• Nominal ATS Load – Burned to EEPROM
Eliminate need to uplink ATS following a processor Reset
• Default LOI Configuration RTSs loaded to EEPROM
Allows ground to re-configure safing and thruster configuration
• Default Delta-H Configuration RTSs loaded to EEPROM
Allows ground to select and perform De-Spin
• Use the same Burn Restart procedure regardless of burn interruption
Simplifies contingency flow and restart decisions
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 81

LOI-1 Restart Flow
• LOI Restart STOL procedure was
developed
– Procedure would run after any burn interruption
– Procedure reduces decisions required for restart
• Successfully executed during SIM-14
and SIM-21
– Ran 7 contingency scenarios
– Successfully captured into Lunar Orbiter
in all 7 scenarios
1. Stops RTS #20
2. Re-Enable Heaters
Catbed and Propulsion heaters
3. Ask to Jam Time
4. Ask to Reload ATS from EEPROM
5. Prepares for Delta-H (RTSs)
Ask Bank 1 or 2 for AT thrusters
Configures thrusters and Safing
6. Ask if Propagated Attitude is Valid, If NO
Stops ATS
Commands Sun-Safe
Configures Star Trackers
Load Target Quaternion
Command to Delta-H
Abort Delta-H and check Star Tracker Data
If STs are occulted, repeat steps with new Delta-Q
7. Loads Current Target Q
8. Start ATS and wait for first attitude Q
9. Enter Delta-H mode (get to burn attitude)
10. Load LOI Burn Parameters
11. Switch to Observing Mode
12. Configure thrusters and safing for LOI (RTSs)
13. Begins Delta-V Maneuver
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 82

Commissioning Activities
• Commissioning is broken into 2 separation phases
1. Spacecraft Commissioning
Sensor Calibrations (Star Trackers, IRU, HGA)
Communications Checkouts, Ka-Band & S-Band Checks
Instrument turn on preparations
– Thermal Configurations
2. Instrument Commissioning
Instrument activation and checkouts
Instrument Calibrations
• Following instrument commissioning, series of 3 maneuvers (Mission Orbit
Insertion) burns will occur to achieve nominal mission orbit
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 83

Spacecraft Commissioning Overview
• Spacecraft Commissioning Activities
– Transition from Sun Inertial Pointing to Nadir pointing
AGS generated slew plan
– HGA Calibrations
Approximately 13 supports required with orbiter slews
Expect to take ~1 week to cover all geometry angles
During Ka-Bands, RTS sequence will be used to perform HGA raster scan (~20 minute scan)
Upload HGA calibration table based on results
– Gyro Calibrations
Perform four different 90 degree slews (X, Y, Z, and Combination)
AGS Performs the slew planning
Star Track Calibration will be performed in parallel with gyro calibrations (verify tracker to tracker alignment)
– S-Band Data Rate Checks
Cycle through different S-Band modes to verify configurations
– Configuration of thermal system
Complete thermal operations heaters and Software heater configurations
– Ka-Band Data Rate Checks
Before HGA calibration checks are complete, plan to test Ka Band HGA pointing
After calibrations, cycle through the different Ka-Band rates
– Data Dumps
Depending on Ka-Band use, plan to schedule high rate S-Band passes with DSN
Orbiter will be storing more data than it can downlink using the nominal S-Band rates
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 84

Spacecraft Commissioning Timeline
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7
Initialize SA Gimbals Gyro Calibration Gyro Calibration S‐Band Data Checks S‐Band Data Checks S‐Band Data Checks HGA Cal (Pass 12)
Nadir Slew HGA Cal (Pass 4) HGA Cal (Pass 7) High Rate Data Dumps High Rate Data Dumps HGA Cal (Pass 10) HGA Cal (Pass 13)
Ka‐Comm Test HGA Cal (Pass 5) HGA Cal (Pass 8) HGA Cal (Pass 9) HGA Cal (Pass 11) High Rate Data Dumps
HGA Cal (Pass 1) HGA Cal (Pass 6) High Rate Data Dumps High Rate Data Dumps
HGA Cal (Pass 2) High Rate Data Dumps
HGA Cal (Pass 3)
High Rate Data Dumps
• Sequence of activities is dependent on Ka-Band Passes
– Priority is to complete the HGA calibration
Currently looking at the geometry for May 21 st launch and generating the plan to
perform the HGA calibration in the shortest time
Full HGA calibration may take up to 3 weeks
– Investigating a limited calibration that will take less time until full calibration is complete.
– Limited calibration may required reduced Ka downlink rates
Activities will be exercised during Mission Rehearsal #3
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 85

Instrument Commissioning Overview
• Allocated 1 day for instrument activation and post-turn on checks
– Plan to turn on the instruments in the following order:
LROC, LOLA, DLRE, Mini-RF and LAMP
• Daily planning meetings will identify for the next 3-5 days, orbiter operations
– Instrument teams can use this information for planning instrument activities
Identify orbits when the orbit is not pointing nadir for calibrations
– Once LROC is turned on, expect daily timelines
• Plan to verify stored command loads for any large angle slews or complex calibration
activities
• Instrument calibrations details are captured in LRO document
– LRO Instrument Calibration Specification (451-SPEC-002967)
• During commissioning, expect to perform momentum dumps every 2 weeks
• Target window to transition to nominal mission orbit is every 2 weeks
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 86

Instrument Commissioning Overview
Commissioning
Calibration Activity Restrictions
CRaTER 90 Degree Off‐Pointing
Min 200 minutes
Goal of 500 minutes
Eclipse
DLRE Field of View Wing Calibration
Min of Two Wing Calibrations
Desire four Calibrations
Beta

Instrument Commissioning Overview(2)
Commissioning
Calibration Activity Restrictions
LEND Off Nadir Pointing Perform at least once Ten minutes at each 15 ° step
LEND 90 Degree Yaw Done in parallel with LAMP and/or LROC
Stay at 90 ° Yaw for 10 minutes
Eclipse
LOLA Passive Earth Raster Scan One scan is required
LOLA Active Raster Scan of GSFC w/GSFC Laser
LOLA Active Raster Scan of GSFC w/LOLA Laser
One scan is required
Min of 20 laser shots
One scan is required
Min of 20 laser shots
LR Passive Earth Raster Scan Perform at least once
LR Active Ranging Perform at least once
LR Timing Perform at least once
LR Active Raster Scan of GSFC Perform at least twice
Performed at least 1 week Active Scans
Earth appear at least half full
Eclipse
Performed at least 1 week after passive
GSFC LR in view
3‐4 days between additiona scans
Eclipse
Performed at least 1 week after passive
GSFC LR in view
3‐4 days between additiona scans
Eclipse
GSFC LR in view
Earth half to fully lit
After HGA calibration
GSFC LR in view
After HGA calibration
At least 4 days after LR Passive Scan
GSFC LR in view
GSFC LR in view
After HGA Calibration
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 88
Nominal

Instrument Commissioning Overview(3)
LROC Deep Space Imaging for Dark Signal
LROC Star Imaging ‐ NAC Two Raster Scans
LROC Star Imaging ‐ WAC
Calibration Activity Restrictions
Commissioning
Perform for 5 integration times for NAC
Perform for 11 inegration times for WAC
One Raster Scan for UV
One Raster Scan for Visible
Eclipse
Eclipse
After NACs have outgassed completely
At least 4 days before scans
Calibration star in view
Eclipse
At least 4 days before scans
Calibration star in view
Constellation in view
Jupiter in view
LROC Constellations and Jupiter Imaging
One Raster Scan for a Constellation
One Raster Scan for Jupiter
LROC Lunar Limb Imaging Performed 5x at different latitudes Beta Angle

Early Mission Staffing
LRO Early Mission Support Requirements
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 S/C Comm
Inst.
Comm MOI
Mission Director 24 24 24 24 24 24 24 16 16 8
Flight Director 24 24 24 24 24 24 24 24 24 24
Systems 24 24 24 24 24 24 24 24 12 24
MOT 24 24 24 24 24 24 24 24 24 24
ACS HW 24 24 24 24 24 24 24 16 On‐Call 12
AGS 24 24 24 24 24 24 24 12 12 12
C&DH 24 24 24 24 24 24 24 16 On‐Call On‐Call
Comm. 24 24 24 24 24 24 24 16
Deployables 24 On‐Call On‐Call On‐Call On‐Call On‐Call On‐Call On‐Call On‐Call On‐Call
Flight Software 24 24 24 24 24 24 24 24 12 8
Gimbals 24 24 24 24 24 24 24 16 On‐Call On‐Call
GN&C 24 24 24 24 24 24 24 24 12 24
Power 24 24 24 24 24 24 24 16 On‐Call On‐Call
Propulsion 24 24 24 24 24 24 24 On‐Call On‐Call 8
Thermal 24 24 24 24 24 24 24 24 16 8
Payload Systems 24 24 24 24 24 24 24 24 16 8
CRaTER Remote 12 12 Remote Remote Remote Remote Remote Remote Remote
LEND Remote 12 12 Remote Remote Remote Remote Remote Remote Remote
LAMP Remote Remote Remote Remote Remote Remote Remote Remote 12* Remote
DLRE Remote Remote Remote Remote Remote Remote Remote Remote 12* Remote
LOLA Remote Remote Remote Remote Remote Remote Remote Remote 12* Remote
LROC Remote Remote Remote Remote Remote Remote Remote Remote 12* Remote
Mini‐RF Remote Remote Remote Remote Remote Remote Remote Remote 12* Remote
* Instrument teams required to cover instrument activation, coverage for calibrations is optional
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 90

Early Mission Communications
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 91

Early Mission Planning and Coordination
• Flight Director leads planning meetings
– Planning meetings occur at beginning and end of Prime Shift
– Additional coordination meetings will occur before critical operations such as
MCC and LOI
– Planning Meetings:
Review previous shift activities
Discuss upcoming shift activities
Review issues/anomaly items
• Daily planning process is similar through early mission, but there are slight
differences
– Launch through start of Commissioning
1 st shift: Majority of orbiter commanding activities is scheduled
2 nd shift: Planning and preparation for next day’s activities is primary goal
– Commissioning
1 st shift: All commanding activities is scheduled, planning and preparations also occur
during prime shift. Planning is more long term (next several days).
2 nd Shift: Monitor orbiter health, perform offline activities such as trending. Engineering
staff is reduced
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 92

Early Mission Planning Process
Launch through Start of Commissioning
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 93

Early Mission Planning Process
Commissioning
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 94

Contingency Management
• For any on-orbit anomaly, an anomaly resolution team (ART) will be formed
– Flight Director will designate team lead and required members
– Consists of experts/engineers from various functional areas
– Team will gather data, identifies the problem, and recommends a resolution
• All anomalies will be documented in the GSFC Spacecraft Operations
Anomaly Report System (SOARS)
• All anomaly operations will have an operations activity request form
completed and authorized
– Ensures changes to nominal plans are well understood
– Ensures the MOT understands and execute approved changes
• Anomaly Management Process is outlined in SER: 451-SER-000874
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 95

Road to Launch
• Finalize Early Mission Timeline
– Review and update activities due to launch date change
• Update Commissioning Daily Activities based on May 21 st launch
• Perform update to Launch and Early Mission Handbook
– Incorporate final version of mission timeline and launch countdown sequences
• Exercise timeline and procedures in upcoming sims and rehearsals
– Mission Rehearsal #3 (Spacecraft Commissioning)
– Mission Rehearsal #5 (Launch through LOI-1)
– Simulation #06 (LOI Contingencies)
– Simulation #22 & #13 (Instrument Calibrations)
– Simulation #23 (Integrated Launch Simulation)
– Simulation #25 (Integrated Launch Simulation)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 96

Normal Operations
LRO Flight Operations Review – Section 12.0
NASA’s Goddard Space Flight Center
Jack Murphy
LRO Mission Operation Team

Key Operational Drivers
• Perform Daily Mission Planning and Scheduling
• Generate and Send All Commands
• Perform Command Authentication in accordance with the LRO Command
Authentication Plan
• RF Communications via the LRO Space Communication Network
• Receive and Process Telemetry
• Monitor Orbiter Health & Safety During All Ground Station Contacts
• Monitor Orbiter Health & Safety During Back Orbit Telemetry Processing
• Distribute Orbiter and Ground Data Products to SOCs
• Distribute Science Measurement Files to SOCs within 24 Hours of Receipt
On Ground
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 98

Changes Since MOR
• Removed the following operations
– Solar Array Indexing is no longer required
• Added the following operations
– Lunar Retro-Reflector Avoidance Plan
– Solar Array Off-Pointing
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 99

Mission Operations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 100

Mission Planning – Daily Operations
Successfully Exercised During Mission Rehearsals 1 and 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 101

• Purpose
Recorder Model
– Assist LROC SOC in image planning process to maximize recorder usage
• Recorder Model Tool provides a forecast of recorder usage
– Forecast is based on:
Current recorder usage
Scheduled Ka-Band supports
Current LROC command sequence
Mini-RF operations opportunities
– Tool provides estimated recorder availability at the beginning of each orbit for a
three day period
Covers same time span as LROC Daily Command Timeline
• Distributed to the LROC SOC by 9 AM each morning
Successfully Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 102

Recorder Model Report
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 103

State Vector & Lunar Ephemeris Generation
• MOC receives daily updates to Orbiter State Vector and Lunar Ephemeris
Tables from FDF
– Two separate products
– ASCII files containing a list of vectors
– Products spans 7-day period on a 10 minute interval
• Products are ingested by MPS
– MPS generates binary Orbiter table files and associated reports
• Reports are reviewed and signed by two MOT Operation Engineers via the
DMS
– Binary Tables are released to Real-Time Operations for uplink to Orbiter
Successfully Exercised During Mission Rehearsals and Simulations to Date
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 104

Slew Planning
• Slew Requests are Received from External Elements
– Total slews per day are limited to three
• MOT Compiles the Requests using Slew Planning Tool
– ASCII file which is ingested onto slew schedule
– Operations Activity Requests which are manually entered onto Slew Schedule
• Slew Planning Tool constraint checks requests
– Conflicts are resolved by MOT
• Slew Planning Tool generates a Compiled Slew Request File
– ASCII file containing list of slews and associated parameters
• Slew Request sent to AGS for Slew Plan Generation
– AGS performs a different set of constraint checks from MPS
– Output of AGS is a list of quaternion commands to be ingested by MPS and
included on daily ATS Schedule
Successfully Exercised During Mission Rehearsals 1, 2 and 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 105

Daily Schedule Generation
• Ingest FDF, SCN Schedule, LROC Command Timelines and AGS products
into MPS
– Delimited ASCII files converted into XML before ingestion
– Ingested into MPS as “events”
• Generate Daily Schedule
– Automatic placement of sequences on schedule via MPS ILOG rules
ILOG rules created and tested by MOT prior to launch
ILOG rules key off ingested “events” (examples AOS/LOS times, ascending or
descending nodes)
– Manual insertion of sequences on schedule by MOT
As required by Approved Operation Activity Requests
– One schedule contain both ground (pass scripts) and Orbiter (ATS) sequences
• Resolve Conflicts on Schedule
– MOT must mitigate all conflicts before export of final schedule
– MOT can override conflicts; this is a last resort with LRO Project Authorization
Successfully Exercised During Mission Rehearsals 1, 2 and 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 106

ATS Load Description
• An ATS Can Have
– A Maximum of 2,500 commands
– A Maximum size of 80,000 bytes
• An ATS Will Nominally
– Span a 24 hour period
– Contain ~1100 commands per day
• There are two ATS buffers on LRO
– Will ping-pong between buffers
– A switch buffer command will be included at the end of each load
• Will use RTSs where possible to reduce ATS size
• Updates to ATS will require a reload
– depending on whether load is executing will determine if the load will either be
rebuilt for the same buffer or the opposite buffer
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 107

ATS and Pass Script Review & Signature
• Products are Reviewed and Signed
– ATS Load Report
– Pass Script Files (each file requires a separate review and signature)
• Products must be reviewed and signed by two Ops Engineers
– Constraint: Cannot include Ops Engineer who generated products
• Review process will be done both visually and by shell script
– Review process is driven by checklist
• Signing process is performed via Data Management System
– Once Signed products are released for use by other MOC systems and delivery
to external elements
Will be Exercised During Mission Rehearsals 3 & 5 and Upcoming Sims
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 108

Pass Script Example – Attended and
Automated Operations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 109

Operations Activity Requests
• Request specifying non-routine activity
• Can be submitted by SOCs, MOT, FDF, LRO Engineering Team, FSW
• Requests originating outside MOC are secure copied to RAS
– Fax will only be used if network connection is down
– Request will only be accepted from designated personnel identified in OA
– Nominally required to send minimum of 48 hours before execution
Could be longer if new STOL procedures or RTSs need to be developed and tested
Could be less if critical such as a misconfiguration on Orbiter
• DMS will notify MOT of new requests
– Email sent to initiator confirming receipt of request
• DMS signature by MOT indicates request has been approved
– Exception: Flight Segment configuration changes require LRO Project Approval
– Email sent to initiator informing of acceptance
• MOT will manually enter request on daily schedule
– Depending on the details of the request, can either be executed from ground
(pass scripts) or from stored command (ATS)
Partially Exercised During Mission Rehearsals and Simulations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 110

Real-Time Ops – Daily Operations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 111

Real-Time Operations Overview
• Nominal real-time contacts are automated
– Manned Operations for daily command loads, non-routine operations and all
maneuvers
• MOT present in the MOC performing analysis and planning duties during 8
AM to 6 PM
– All team members are cross-trained in real-time and off-line activities
• MOT follows pass script outlining planned activities
– Daily file loads, Operation Activity Requests
• All commanding performed using validated STOL procedures
Successfully Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 112

Daily Operations – Sample Pass Script
Interface
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 113

Orbiter Health & Safety Monitoring
• MOC performs real-time processing on telemetry
– Extract packets, decommutate and display HK data, generate/display event
messages, perform command verification
• Health and Safety Checking
– Performed via limit checking and configuration monitors with automated
notification
– Monitor file downlink processing
– Confirm uplink via noop command test
Successfully Exercised During Multiple Sims and Mission Rehearsals
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 114

Routine Operations Activities
• Orbiter Event Message Downlink
– Downlink of stored event messages from previous back orbit
– Downlinked as binary file
ITOS application will process and display on the ITOS event window
• Orbiter Directory Listing Downlink
– Downlink file list of all HK and Measurement data directories
– Downlinked as binary file
ASCII report generated with filename, size and timestamp of each file
– Directory listing is used by DMS to establish expectations for files
• Downlink HK and Measurement Data
– Downlink all closed data files
– File playback based on priority, up to 99 file downlinks active though expect less
than 10 at any given time
– Once file is verified as downlinked (CFDP Acknowledgement)
File is deleted from Orbiter
Successfully Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 115

Routine Operations Activities
• Clock Correlation
– Send any command (will be NOOP)
Time latched at station and time sent back to MOC in status packet
Time latched onboard Orbiter and downlinked in telemetry
Process requires no other ongoing command activity
– Calculate clock drift on ground
Calculation performed via STOL procedure
Operationally will keep clock within +/- 80 milliseconds of UTC; mission requirement is
+/- 100 milliseconds of UTC
Once clock is adjusted at launch; not expected clock will drift out of specification during
prime mission
– SOCs will be updated of clock drift and adjustments via the SPICE SCLK kernel
product
• Uplink Daily Load Files
– Daily ATS, State Vector Table, and Lunar Ephemeris Table
– Uplinked to Orbiter via MOC-DPS using Class-2 CFDP (Acknowledged mode)
Checksum verification on files is built into the CFDP Protocol
– Tables are loaded to RAM, validated, and activated onboard Orbiter
Successfully Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 116

HK & Science Data Downlink
• LRO Recorder is managed autonomously during CFDP Class 2 operations
• Three partitions on recorder
– LROC/Mini-RF sized to store ~12 orbits of data
– All other instruments sized to store ~13 orbits of data
– S/C partition sized to store ~14 orbits of data
• HK and Measurement files transferred to ground during WS1 Ka-Band
contacts
– Files are queued for downlink based on priority (1-8)
Priority scheme is intended to ensure larger files do not monopolize downlink
Priority 1 and 8 are used for critical file transfers
• Upon successful downlink via CFDP Class 2 files are deleted from recorder
by FSW
Successfully Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 117

HK & Science Data Downlink
• Recorder usage is monitored during each support
– Usage and directory listings will come down during each S-Band contacts
– Alarms will be configured if recorder reaches more than 65%
– If condition occurs, MOT will notify LROC SOC of possible problem
LROC SOC and MOT will agree whether to carry out further contingency procedures
• LROC Recorder Contingency Procedures:
– Each LROC image will be given a priority rate (1 to 5)
– LROC SOC assigns the priority and the information is passed to the MOC in the
LROC daily image timeline
– If agreed to by the MOT and LROC SOC, the MOT will delete lower priority
images to provide storage room for future higher priority images
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 118

Offline Engineering
• Trending & Data Analysis
• MOC Automation
• Lights Out Detection and Notification
• Data Processing and Archiving
• File Accountability and Tracking
• Product Authorization
• DMS Web Portal
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 119

Trending and Data Analysis
• MOT uses Integrated Trending and Plotting System (ITPS)
– Full Orbiter telemetry database ingested into ITPS (ITOS DBX format)
– Data is ingested as available within the MOC
– Processes Orbiter files and real-time telemetry stream from ITOS
– Prime and Backup Systems ingest the same data
– Entire mission is maintained in the database
– FDF products are ingested and used to correlate with other telemetry
• Trending is automated (ingest, LTT, plots and report generation)
– Special requests and anomaly investigations is performed manually by MOT
• Life-Time Trend Analysis
– Maintains Min./Max./Mean/Stan Dev on all mnemonics
• Report Capability
– Can create reports in ASCII format and Plots in PDF format
– Standard reports and plots will require MOT review and signature daily
– Subsystem Performance reports and plots distributed to LRO Project Team for review
• MOT has remote access to ITPS web client
– Will be used for anomaly investigation during off-shift hours
Data Ingest, Reporting and Plotting capabilities verified
Full Operational capabilities not verified due to existing SOARs
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 120

GMT
FDF Planning Aids
Ka-Band Passes
WS1 File Transfers
Playback Data Ingest
Station Data Ingest
ITPS Daily Production
Reports/Plots Availabile
DMS Review & Approval
Trending and Data Analysis
00:00
01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
• Plot illustrates a typical day in the monthly schedule
• Due to the variance in Ka-band support times, data will not always be available at
12:00z (~10 days out of 28 day cycle), when Daily Production is autonomously
invoked
• Previous day’s data should be completely downloaded following second Ka-band
support
• Reports and Plots generated will require review and signature approval via the DMS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 121
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00

MOC Automation
• Automation of real-time contacts accomplished using pass scripts
• Pass scripts content
– Ground station contact information: AOS, LOS, data rates, etc
– Contact type: automated or manned
– Pass activities: absolute time followed by STOL procedure or command
Activities are executed according to absolute time
• One pass script file for every contact (staffed and automated)
• Pass script read in using STOL procedure prior to AOS
– WOTIS schedule used to determine ground station AOS/LOS times
– STOL procedure coded to find latest version of WOTIS schedule and Pass Script
• Status of pass script activities written to log
– After LOS, log is transferred to MPS to update the Activity Plan
– Log messages also used by MAS to notify MOT of unsuccessful activities
Successfully Exercised Manual Execution of Pass Scripts during Mission Rehearsal 4
Automation controlled by same processes, Will be fully checked out during Commissioning
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 122

MOC Automation
• Automation contingencies
– No pass script found or error opening – Automation designed to run default set of
procedures and notify MOT
– No WOTIS schedule found – Notification sent to MOT, automation ceases until
new schedule is found
– ITOS server hangs – Notification sent to MOT, no automated failovers of realtime
system planned
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 123

Lights Out Detection and Notification
• MAS detects problems and notifies the MOT
– Monitors messages from ITOS (Orbiter telemetry, ground system configuration)
and DMS (system heartbeats, product arrivals) and notifies MOT in the event of
anomalous conditions (email or mobile device depending on severity)
– Detection capability in place during Mission Rehearsal #4
• Notification performed by mini scripts by sending messages to Project
mobile devices and email
– Scripts designed by MOT through MAS interface
– Notification is based on schedules defined in the MAS software
– MAS will continue to notify until acknowledged, if acknowledgement is not
received in defined time, system will escalate to additional MOT
Successfully Exercised During Mission Rehearsal 4 MAS ability to detect and notify of problems via email to team
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 124

Data Processing and Archiving
• Data processing is highly automated
– Files received at WS1 are sent to MOC based on Priority
• Orbiter Data Processing
– Orbiter HK
Ingested as available by ITPS
Processed by ITOS for events, limit violations, configuration alerts, SOC requested Orbiter telemetry
packets, and create AGS sequential print used for attitude verification
– Instrument HK
Ingested as available by ITPS
Processed by ITOS for limit violations and configuration alerts
– Instrument Science Files
LROC NAC images and Mini-RF science files are only files requiring processing to remove FSW
alignment data
All other instrument science files are passed through MOC with associated metadata file
• Data Archiving
– All MOC products are archived for the life of the mission
– Mass Storage System stores all products online
– Products include all digital information passing through the MOC or generated by the MOC
Partially Demonstrated During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 125

File Accountability and Tracking
• MOT will use the DMS for tracking and file accountability
– Orbiter files:
Track the flow of Orbiter files from the Orbiter to the ground to the MOC, etc
Verify all Orbiter generated data is received on the ground
– Ground system files:
Used to verify daily inputs from external and internal elements arrive when
expected
Verify daily command loads arrive on Orbiter
• DMS alerts MOT of anomalies via the MAS system
– Failure of Orbiter files to reach ground in expected time
– Transfer failure between two locations
– Failure of a ground system file to arrive in expected time
• DMS Web Portal provides ability to status current expectations
Partially Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 126

Product Authorization
• Electronic signature is used to provide accountability for products that require review
and authorization
• There are four levels of authorization
– Ops Engineer - Operations Engineers other than Shift Lead
– Ops Lead - Operations Shift Lead
– Project - System Engineer, Project Management, Subsystem Lead
– External - SOC Lead, FDF Lead
• Typical products requiring signature
– ATS Load Report and Pass Scripts (Ops Engineer, Ops Lead)
…with mission critical operations (Project)
…with instrument non-routine operations (Project, External)
– Pass Summary Reports (Ops Engineer, Ops Lead)
– Trending daily production reports and plots (Ops Engineer, Ops Lead)
– Activity Change Requests (Ops Engineer, Ops Lead)
…with mission critical operations or change to flight configuration (Project)
…with instrument operations (Project, External)
• Files to be sent to the Orbiter will not be available to the T&C system until they have
completed the authorization process
– Once approved, the files will be made available to the T&C for uplink to the Orbiter
Partially Exercised During Mission Rehearsal 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 127

DMS – Web Portal
• Web Portal for Retransmission Request
– DMS will receive request from the SOCs for file re-transmissions
• SOC Status Portal
– DMS provides a portal that allows the SOCs to ascertain the status of where files
are located at any given point in time
• Search capability
– DMS provides a centralized database for file data storage
– A searchable function allows the MOT to quickly determine a files status
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 128

Mission Planning – Other Normal Operations
• SCN Scheduling
• Weekly Planning Meetings
• Monthly Calibrations
• Station Keeping Maneuvers
• Delta-H and Yaw Maneuvers
• Mini-RF Operations
• Laser Ranging MOT Operations
• Lunar Retro-Reflector Avoidance Plan
• Solar Array Off-Pointing
• RTS Load Generation
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 129

SCN Scheduling
• Single schedule containing all WS1, USN, and DSN supports
• Generated by DSMC personnel using WOTIS
• Generic Scheduling document identifies nominal scheduling requirements
– Three types of schedules are received weekly each Thursday covering 4 weeks
• Types of schedules
– Strawman – 3 weeks into the future and spans 14 days
WS1, USN, and DSN will advise of any conflicts and station downtime
MOT submits special requests
WOTIS resolves conflicts and transmits to MOT and SCN stations
– Forecast –2 weeks into the future and spans 7 days
MOT and SCN stations submit project and site schedule changes
WOTIS resolves conflicts and transmits to MOT and SCN stations
– Operational
Final conflict free schedule
Transmitted to the MOC and the SCN stations the Thursday before the operations week
begins on Monday
Successfully demonstrated during MRT and now being used for ORT scheduling
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 130

SCN Scheduling
• DSN Long-Term Planning
– DSN works on 6 month planning cycle
– Once in mission orbit S/K maneuvers are known, MOT will submit request to
schedule DSN support for S/K maneuvers
• Emergency Requests
– All requests made through the DSMC by email, phone, or fax
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 131

Weekly Planning Meetings
• Expected Attendees
– MOT members
– Project personnel
– SOC personnel
– FDF personnel
– FSW Maintenance as required
– SCN personnel as required
• Held every Monday to discuss upcoming week
• Meeting Agenda
– Anomaly status, analysis, and resolution (both spacecraft and instruments)
– Current status of instruments and spacecraft subsystems
– Summarize previous week of spacecraft and instrument activities
– Discuss upcoming spacecraft and instrument activities
Work through forecast schedules of special activities such as calibrations, maneuvers,
Mini-RF operations resolving timing conflicts where needed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 132

Monthly Calibration Planning
• Monthly Calibrations are a subset of Cals used during Commissioning
phase
– Documented in 431-SPEC-002967 Instrument Calibration Specification
• Planning will begin 3-weeks prior to event
– SOCs submit Operation Activity Requests to MOT
– MOT develops initial timeline of events and distributes for review
– Initial timeline is reviewed during Weekly Planning Meeting
• MOT updates timeline based on review
– Sent to SOCs and Project personnel for review
– MOT incorporates additional requests, and iterates through review process until
concurrence from all SOCs and Project Personnel
– Once accepted, MOT generates ATS and tests sequence on FlatSat
• MOT distributes Final Sequence week before event
– Final Event Review held during weekly operations meeting prior to event
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 133

Monthly Calibrations
• During the Nominal Mission phase, instrument calibrations will be performed
in conjunction with the monthly SK maneuvers whenever possible
– SK maneuvers are predicted in advance so coordination with the instrument
teams will be possible
– The plan is to perform instrument calibration activities prior to the SK maneuver,
to allow the instruments to be placed into a safe configuration during the burns, if
necessary
• When possible, calibrations will be performed in parallel (e.g., off-nadir
slews)
• Additional calibration time can be requested; however it will increase
interruption to nominal measurement data collection
• Some calibrations will not be required during each monthly period, so they
will only be scheduled when deemed necessary by the instrument
operations teams
Calibration Sequences to be Exercised during Sims 13 & 22
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 134

Monthly Calibrations
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 135

Scenario 1
Station Keeping Maneuvers
• R-T coverage of the maneuvers will be
scheduled
• MOT will provide trending of relative data to
be used for computing the maneuver
planning file
• Four scenarios have been identified:
– ACS thrusters are located on -X axis of the Orbiter
Red = Direction of Flight
Blue = Yaw Maneuvers
• Flying +X Forward (Non Beta 0)
(+X) Delta-H, Delta-V, Yaw (-X), Delta-V, Yaw (+X)
Scenario 2
– Flying -X Forward (Non Beta 0)
(-X) Delta-H, Yaw (+X), Delta-V, Yaw (-X), Delta-V
SK #2
+1.5 Orbits
Scenario 2 Exercised During Simulation 18
View from Earth
Scenario 3 (Once per Year)
• Flying +X Forward (Beta 0)
(+X) Delta-H, Delta-V, Yaw (-X), Delta-V
SK #1
Scenario 4 (Once per Year)
• Flying -X Forward (Beta 0)
(-X) Delta-H, Yaw (+X), Delta-V, Yaw (-X), Delta-V, Yaw (+X)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 136

Station Keeping Implementation
• FDF Delivers Maneuver Planning Products (Maneuver Plan & Target Thruster Vector)
– 72 hours – Preliminary SK Maneuver received by MOC
– 24 hours – Final SK Maneuver received by MOC
• The planning file is incorporated into the Mission Planning Timeline, and will contain:
– Pre-burn attitude, Thrusters to be used for the burns, Maneuver start and stop times,
Duration of burns, Post-burn orbital elements
• MPS ingests the Maneuver Plan and AGS Slew Plan and create Orbiter commands
to execute the maneuvers
• Commands are included in the daily ATS load (next day’s load)
• Delta-V maneuver involves a cross communication between the ATS and RTSs
• ATS Implementation includes:
– Burn commands, as well as any required Yaw maneuver and Delta-H commands
– Commands to start the RTSs, which will configure the Orbiter for the burns
• RTS Implementation includes:
– Pre-Burn: Turn-on catalyst bed heaters, reset thruster counters, enable DV transition, enable
thruster firing, safe instruments and index SA and HGA
– Post-Burn: Turn-off catalyst bed heaters, disable thruster firing, disable RTSs (prevent
inadvertent execution)
• ATS Load will be uplinked and executed on FlatSat prior to loading to Orbiter
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 137

Delta-H & Yaw Maneuvers
• Momentum Unloading (Delta-H)
– A daily plot of the system momentum containing previous two weeks will be trended
If trend indicates Orbiter exceeding Flight Rule (110 Nms) an out of sequence Delta-H will be
scheduled
– Delta-H will always occur prior to the 180° yaw maneuvers
Not required prior to 2nd yaw maneuver following the Delta-V maneuver
– Orbiter will remain nadir pointing throughout the Delta-H maneuver
– Operation Activity Request will be received from FDF directing time to execute momentum
unload
– Momentum Unloading will take a maximum of 20 minutes
Successfully Exercised During Mission Rehearsal 4
• Seasonal 180° Yaw Maneuvers
– Maneuver must occur when the Sun is near the orbit plane (Beta 0° + 5°)
– The MOT will attempt to schedule the maneuver in conjunction with the Delta-V maneuvers
The Beta angle changes ~1° per day, which provides a 10 day window of opportunity
– Yaw maneuver will cause the Orbiter to reverse its orientation in the velocity direction
During the maneuver, the Orbiter will not sweep the instruments FOVs through the Sun
– Commands to be included into the daily ATS command load
– Yaw maneuver should be completed within 30 minutes
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 138

Mini-RF Operations
• Mini-RF operates on a non-interference basis with ongoing instrument
operations
• Data collection periods are planned in conjunction with the monthly stationkeeping
maneuvers and during high beta angle periods
• A Mini-RF Command Timeline is delivered to the MOT prior to all scheduled
observations
– Command files will be delivered by secured copy to the RAS
• Mini-RF data are normally collected while the Orbiter is pointing in the nadir
direction
– Periodically, Mini-RF may require off-nadir slews to perform observations
Slews will be limited to 20 minutes in duration and less than 20° from nadir pointing
Slews will be planned in advance and must not violate flight constraints
Exercised During Mission Rehearsals 1 & 4
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 139

Laser Ranging MOT Operations
• MOT sends products to CDDIS at Laser Ranging (LR) ground station
– WOTIS schedule
– SPICE SCLK file
– Go/No Go status file
• MOT receives LR schedule (firing times)
– LR done while Orbiter in view with WS1
• MOT control whether laser ranging is perform or not
– Done with Go/No Go status file
File sent once to flip state; not sent every contact if state remains same
LR ground station computers will read in file prior to every contact
– LR operations can be temporarily ceased due to Orbiter anomalies (example –
transition to Sun-Safe mode) or special activities (Lunar eclipses)
Successfully Exercised Go/No Go File during Engineering Test
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 140

Lunar Retro-Reflector Avoidance Plan
• Activity to prevent damaging the Laser Ranging Telescope built into the
HGA by ground based laser ranging stations
• LOLA SOC provides MOC predictive fly-over times
– Product ingested by MPS and commands to offset the HGA are added to the
daily schedule
• Expect short duration events, less than 30 seconds
• Will require pausing CFDP downlinks due to narrow Ka-Band beam width
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 141

RTS Load Generation
• Orbiter has 256 total RTSs
• RTSs Currently defined
– 82 Safing RTSs – Defined by LRO Project; stored in EEPROM
– 12 Normal Operations RTSs – Defined by MOT; Approved by Project; stored in
RAM
– 18 Maneuver RTSs – Defined by MOT; Approved by Project; stored in RAM
– 15 Calibration RTSs – Defined by MOT; Approved by Project; stored in RAM
• Maximum size in bytes – 300
• Built and managed using MPS
– MPS stores old and current version definitions
• On-orbit operations
– RTSs will be generated as needed
– Tested on FlatSat before uplink
– Operations RTS load report signed off by MOT using DMS prior to uplink
– Safing, Maneuver and Calibration RTSs approved by LRO Project prior to uplink
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 142

Summary of Operations RTS
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 2 - 143

• Maneuvers
R/T Ops – Other Normal Operations
– Orbiter Configuration During Maneuvers
• Solar Array Off-Pointing
• Memory Model Updates
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 144

Maneuvers
• MOC is staffed 16 hours during maneuver events
• Prior to maneuvers the following occurs:
– Maneuver RTS’ Enabled by validated STOL procedure – 2 orbits prior
– Spacecraft is configured via ATS
– Instruments are safed via ATS
• DSN Stations scheduled for all maneuver events
– 8 Kbps data rate via Omni antennas
• Project Engineers and MOT monitor maneuver in real-time
• At completion of the maneuver the following occurs:
– Propulsion system is safed via ATS
– SA and HGA Return to Track Mode via ATS
– Instruments are returned to normal operations by validated STOL procedures
• Post-Maneuver products generated and provided to FDF for analysis
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 145

• Spacecraft
Orbiter Configuration During Maneuvers
– HGA Antenna in index position (Delta-V maneuvers only)
– Solar Array in index position
• Instruments
– CRaTER: No changes, instrument will remain in the nominal configuration
– DLRE: Instrument is safed, but remains powered
– LAMP: High voltage reduced, outer doors closed
– LEND: Instrument is powered off
– LOLA: Instrument is powered, the laser firing is disabled
– LROC: Instrument is powered, but will not be taking images
– Mini-RF: Instrument is powered off
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 146

Solar Array Off-Pointing
• Required to lower maximum temperature of SAS harness
– Discovered during Thermal Vacuum testing
• Offsetting only the Z-Axis gimbal
• Offset is based on beta angle
• Activity is scheduled via MPS and added to the Pass Script
– Activity is executed via validated STOL procedure during attended support
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 147

Memory Model Updates
• Tracks load files currently loaded or previously loaded to spacecraft RAM
and/or EEPROM
– ATSs – FSW tasks and tables
– RTSs – LROC Initialization Files
• Following properties are compiled
– load file name
– onboard pathname location
– file type
– date/times of load operations (uplink, activation, copy, move, RTS enable,
dump/compare)
– checksum
– activation status
– enable status if RTS
– dumped and compare status
– comment box
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 148

Memory Model Updates
• Initial population of memory model with load file data accomplished by
ingesting file listings of onboard directories
– Complete
• Once initialized with launch image, properties populated in Memory Model
by ingesting messages from a feedback log from ITOS
– Complete
• Reporting function
– User can create custom reports and queries
• Main uses
– Can determine what was activated in RAM if power on reset of processor occurs
– Documents the differences between EEPROM Banks
– Account of what load files are loaded and which version is activated
Model initialized with flight version of EEPROM and updates made for safing RTS’
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 149

Memory Model – Sample Report
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day Slide 2 - 150

Contingency Operations
• MOT Response to On-Orbit anomaly
– Document state of Orbiter and ground system at time of anomaly
– Assess the health and safety of personnel, the Orbiter and ground system
– Alert LRO Project Mission System Engineer and Ground System and Operations
Lead of anomaly
– Response to anomalies will be documented in an Operation Activity Request
• SOARS Reporting
– All Orbiter (post-launch) and ground system anomalies documented in SOARS
system
– SOARS system used pre-launch by GS&O for documenting ground system and
operational related discrepancies
– Disposition of SOARS by LRO Project CCB
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 151

LRO FSW and Instrument FSW Updates
• FSW will be delivered to MOC tested and verified
– Operation Activity Request to accompany FSW delivery
– Change release to accompany FSW delivery
• MOT will perform the following:
– Review Operation Activity Request and gain approval from LRO Project
Personnel to proceed
– Modify Operational Products (in test Lab) as required to support update
– Verify FSW update by loading to FlatSat
Intent is to verify approved FSW loading procedures can perform update
Verify affected subsystem functions following update
Verify updated Operational Products
– Discuss update plans during Weekly Operations Meeting and gain
concurrence from SOCs, LRO Project and others as required
– Follow established Flight Procedure Document to execute FSW update
– Notify LRO Project and SOCs update has been executed
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 152

MOT Staffing – Launch through Nominal Ops
• MOC staffed 24x7 at launch
– Transition to 16x7 during commissioning phase
• Nominal MOC staffing is 8x7
– Reduced staffing on weekends
– MOC staffed 16 hours during all maneuvers
• Team rotates through positions on a weekly basis
– Requires all team members are certified as R/T Telemetry & Command, Mission Planner and Offline
Engineering
• On-Call staff available during unattended operations
– MAS System escalates messages not responded to in pre-defined time
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 153

Contingency Preparations
LRO Flight Operations Review – Section 13.0
NASA’s Goddard Space Flight Center
Martin B. Houghton
Mission Systems Engineering

Contingency Prep. On-Board (Safing)
• All On-Board Safing checks are defined in Safing Spec (431-SPEC-00498)
• Driven by internal telemetry “Watch Points” (e.g. Battery_Current < -0.2 A)
• Governed by “Action Point” logic equations (e.g. if [WP2 & WP9] then…)
• Trigger execution of On-Board Real-Time Sequences (451-SER-002747)
• All checks were verified on S/C (or FlatSat) as part of Safing Functional
• Bottom Line: In case of emergency, the Orbiter will take good care of itself.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 155

On-Board Safing Monitoring
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 156

Conting. Prep. On-Ground (Con-Procs)
• Yellow & Red Telemetry Limits and/or S/C Event Messages (including the
execution of any Safing RTS’s) alert the Ground that something is wrong
• Real-time Contingency Procedures exist to handle all Typical Anomalies
• Most typical and most critical Con-Procs were tested in Sims/Rehearsals
• All Con-Procs have been pulled together into 1 place (451-PROC-003508)
• Bottom Line: The Ground is ready to fully recover from typical anomalies.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 157

LRO Syst em Level Cont ingencies
Contingency Procedure List (1)
Procedure ID Contingency Description System Test/ Review Status
LRO-CDH-001 DSB EDAC multi-bit uncorrectable Activities to troubleshoot uncorrect able errors CDH Review ¦
errors
on the DSB
LRO-CDH-002 EEPROM checksum failure Received an event indicate EEPROM checksum
failure occurred
CDH Review ¦
LRO-CDH-003 Blabbermouth 1553 Bus RT Component on the 1553 bus is flooding the
bus wit h messages
CDH Review ¦
LRO-CDH-004 1553 Bus Errors 1553 bus faults CDH Review ¦
LRO-CDH-005 USO 95 00 Failure Recovery from USO 9 500 failure, switch to
USO 9600
CDH Review ¦
LRO-Comm-001 Negative Acquisition after
MOC does not receive telemetry after
Co m m Review ¦
Se par at ion
separat ion through TDRSS
LRO-Comm-002 Blind Acquisition Sequence of events required for performing
successful acquisition of LRO when transmitt er
is off and need t o perform an unscheduled
support
Co m m F/ S 3 / 2 8 / 0 9
LRO-Comm-003 Negative Acquisition (Nominal During scheduled support , ground station does Co m m Review ¦
Mission)
not acquire LRO
LRO-Comm-004 Loss of RF Commanding Loss of uplink commanding Comm Review PENDING
LRO-Comm-005 Bad quality RF communications Ident ify cause for when downlink is poor and
seeing large number of errors or low AGCs
Co m m Review PENDING
LRO-FSW-001 FSW Bus Errors Ident if y cause for soft ware Bus Errors FSW Review PENDING
LRO-FSW-002 CFDP Errors Ident ify and correct if during CFDP dumps,
syst em reports large number of CFDP retries
or errors
FSW Review PENDING
LRO-FSW-003 SSR Rebuild/ Re-initialize Procedure to reformat the SSR FSW F/ S 3/ 28/ 09
LRO-FSW-004 Recovery from a full SSR Partition Recovery steps to cleanup if a SSR fills FSW F/ S 3/ 28/ 09
LRO-GNC-001 Star Tracker Stuck in INIT Mode Activities to identify and load directly to RAM
instead of boot ing off EEPROM
GNC Review ¦
LRO-GNC-002 Kalman Filter Diverging Ident ify and determine correction if KF is
diverged
GNC Review ¦
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 158

LRO Syst em Level Cont ingencies
Contingency Procedure List (2)
Procedure ID Contingency Description System Test/ Review Status
LRO-GNC-003 Sun Acquisition Failure Sun-Safe failure following a transition into Sun- GNC SIM-28/ 24 ¦
Saf e
SIM-15
LRO-GNC-004 Sy stem Moment um Trending High Daily syst em momentum trending higher than
expect ed and may hit flight rule limits before
next scheduled Delt a-H
GNC Review PENDING
LRO-GNC-005 Failed Gyro during mission Gyro dat a failed during mission. Re-Plan
act ivities required.
GNC Review ¦
LRO-GNC-006 ST Invalid Data Activities to debug invalid star t racker dat a GNC Review ¦
LRO-GNC-007 Reaction Wheel Failure Ident ify cause of wheel failure and reconfigure
for 3 wheels
GNC SIM-2 8 / 2 4 ¦
LRO-GNC-008 High Rate De-Spin Activities to quickly de-spin from high rates
where wheels can not control the orbit er
GNC SIM-2 8 / 2 4 ¦
LRO-GNC-009 Thrust er 1-shot Problems List of possible problems and initial corrective
actions that could occur during thruster 1shot
which include: Thrust er Polarit y,
anomalous performing thrust er, etc
GNC SIM- 1 5 ¦
LRO-GNC-010 CSS Failure Recovery Ident ify and determine correction for failed
CSS
GNC Review ¦
LRO-GNC-011 Initial Star Tracker turn-on
Troubleshoot ing steps if t he ST output
GNC SIM- 2 4
¦
miscompare
quaternions are not correlat ed during the
initial turn-on
SIM-15
LRO-GS&O-00 1 Primary workstat ion failure St eps to configure and swit ch operations to GS&O SIM-26 5/13/ 09
backup workstat ion
MOC TEST
LRO-GS&O-00 2 Air Condition offline Facility primary air conditioning is offline GS&O Review ¦
LRO-GS&O-00 3 WS1 (White Sands) down, No Ka. Recovery steps if Ka passes are missed due to
st ation problems or weather
GS&O Review PENDING
LRO-GS&O-00 4 Switch to SDO-2 Backup Antenna St eps to request and configure for backup
SDO-2 Ant enna for Ka
GS&O Review PENDING
LRO-GS&O-00 5 Backup MOC operations St eps to transfer primary operat ions to the
backup MOC if the primary MOC is down for a
GS&O MOC ¦
NASA’s Goddard Space Flight Center
lengt h of time
LRO Flight Operations Review (FOR) Day 2 - 159

LRO Syst em Level Cont ingencies
Contingency Procedure List (3)
Procedure ID Cont ingency Description System Test / Review Stat us
LRO-MECH-001 HGA Deployment Failure HGA deployment can not be verified t hrough
HGA hinge angles readings in t elemet ry
MECH SIM-25/23 3/24/ 09
LRO-MECH-002 SA Deployment Failure Failed SA deployment can be t he result of a
failed release mechanism or outer panel failed
t o deploy and lock
MECH SIM-25/23 3/24/ 09
LRO-MECH-003 Solar Array Stuck Gimbal( s) Recovery from a stuck SA gimbal MECH Review PENDING
LRO-MECH-004 HGA Stuck Gimbal( s) Recovery from a stuck HGA gimbal MECH Review PENDING
LRO-PAYLOAD-00 1 LAMP LTS Failure Failure on the LTS requiring t he ATS to send
command to LAMP prior to crossing the
terminator
PAYLOAD Review PENDING
LRO-PAYLOAD-00 2 Diviner in Safe Mode Diviner entered safe mode unexpect edly PAYLOAD Review PENDING
LRO-PAYLOAD-00 3 LOLA Laser Failure Sy mptoms and activities of a failed laser and
plans t o swit ch t o other laser
PAYLOAD Review PENDING
LRO-PAYLOAD-004 DLRE Software Upload Activities to perform DLRE FSW load to RAM
or EEPROM
PAYLOAD I&T ¦
LRO-PAYLOAD-00 5 LOLA Soft ware Upload Activities t o perform LOLA FSW load to RAM
or EEPROM
PAYLOAD F/ S ¦
LRO-PAYLOAD-00 6 LROC Software Upload Activities t o load a new LROC INIT files or
addit ional INIT files
PAYLOAD I&T ¦
LRO-PAYLOAD-00 7 LAMP Software Upload Activities t o perform LAMP FSW load t o RAM
or EEPROM
PAYLOAD F/ S 3/ 28/ 09
LRO-PAYLOAD-00 8 Mini-RF Soft ware Upload Activities t o perform Mini-RF FSW load to RAM
or EEPROM
PAYLOAD F/ S ¦
LRO-PAYLOAD-00 9 LOLA Det ect or Failure Ident ificat ion, safing, and eventual recovery
from a failed det ect or on LOLA
PAYLOAD Review PENDING
LRO-POWER-001 Battery Charging Failure Ident ify and recovery if end of charging
current on successive orbits is trending
higher.
POWER Review PENDING
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 160

LRO Syst em Level Cont ingencies
Contingency Procedure List (4)
Procedure ID Contingency Description System Test / Review Status
LRO-PROPULSION-001 Pressure increase after HPLV is Temperat ure changes causes pressure to build PROPULSION Review PENDING
opened
after HPLV and pyro valves are opened before
LOI
LRO-PROPULSION-0 0 2 Propulsion Temperat ures too Hot Activit ies to respond t o propulsion
t emperat ur es heat ing up.
PROPULSION Review PENDING
LRO-SYSTEM-001 Missed SK maneuver Recovery steps from missing either SK1, SK2
or Both
SYSTEM Review ¦
LRO-SYSTEM-002 Detect ion of unauthorized
Detect ion and notification of unaut horized SYSTEM Review PENDING
commanding
command to the spacecraft
LRO-SYSTEM-003 Sun Safe Recovery Activities and sequence to reconfigure and
climb to observing (Nadir) pointing following a
sun-safe ent ry
SYSTEM SIM- 1 9 3 / 2 0 / 0 9
LRO-SYSTEM-004 LOI Rest art Cont ingency Restart LOI burn following unexpected burn SYSTEM SIM-1 4 / 2 1 ¦
terminat ion due to processor reset, attit ude
SIM-6
error, gyro failure or other thruster failure.
MR-5
LRO-SYSTEM-005 Recovery from a Processor Reset Activities to recovery from a warm reset
SYSTEM SIM- 1 9 3 / 2 0 / 0 9
(FSW Warm Reset)
(Processor Reset)
LRO-SYSTEM-006 Recovery from a Board Reset ( FSW Activities to recovery from a cold reset (Board SYSTEM SIM- 1 9 3 / 2 0 / 0 9
Cold rest art )
Re set )
LRO-SYSTEM-007 Recovery from C&DH Power Cycle Activities to recover from a C&DH power cycle
event
SYSTEM SIM- 1 9 3 / 2 0 / 0 9
LRO-SYSTEM-008 Missing LOI-1 Burn Failure to capture lunar orbit, act ivities for
deep space maneuver
SYSTEM Review PENDING
LRO-SYSTEM-009 Failed MCC-1 Burn Failure for MCC-1 Burn t o st art on t ime and/ or
re-plan act ivities for performing a MCC-1 makeup
burn
SYSTEM SIM- 1 5 ¦
55 Total: 26 Complete (47%) 18 in Review (33%) 11 to be Tested (20%)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 161

Start
Is the SC power
positive (onaverage
)?
N
Are we in
SSG?
N
System
Momentum
Changing ?
N
System
Momentum > 72
Nms?
N
Are RWAs
Working?
Y
Has the SA been
deployed or sequence
started ?
N
Is the SA Index
Override Flag
Enabled?
N
Enable SA Index
Sun Acquisition Failure
Y
Y
Y
Y
N
Y
Sun Acquisition Failure
No Problems
SSG Sun
Acquisition
Failure
Changing
Momentum
High Rate
Despin
Failed RWA
Is the SA at Index or
Moving Towards Index ?
Y
Is the SA At Index
Y
(CSS Failure Unkown OR fix
Y
>10 minutes )?
N
Y
FailedSunAcq
Š Observing
Mode
Transition
N
Stuck Array
Contingency
N
Failed CSS
Is the SC power
positive ?
Is the Sun Vector
sweeping the body
quickly ?
SSG Sun Acquisition Failure
NASA’s Override Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 162
Start
N
N
Are RWAs
Working ?
Y
Has the SA been
deployed or sequence
started ?
N
Is the SA Index
Override Flag
Enabled ?
N
Enable SA Index
Override
Y
N
Y
Y
No Problems
High Rate
Despin
Failed RWA
Is the SA at Index or
Moving Towards Index ?
Y
Is the SA At Index
Y
(CSS Failure Unkown OR fix
Y
>10 minutes )?
N
Y
FailedSunAcq
Š Observing
Mode
Transition
N
Stuck Array
Contingency
N
Failed CSS

LOI Restart Contingency
Loss of Comm
LOI Restart
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 163

LOI Robustness
• LOI-1 is ~ 4-5 days after launch and is Mission Critical
• Only need ~50% planned delta-V to capture into orbit
• Defends against prop failure and/or burn interruption
• We have re-start/plan capability in case of interruption
• Have developed recovery option for Missed/Partial LOI
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 164

1st Encounter
Possible Recovery from Missed LOI
LRO
Moon
2nd Encounter
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 165

Mission System & Operations Testing
LRO Flight Operations Review – Section 14.0
NASA’s Goddard Space Flight Center
Rick Saylor
Deputy Mission System Engineer

Mission System & Operations Topics
• Definitions of test types
• Test Summary
– RF Compatibility Testing
– Mission Simulations
– Mission Rehearsals
– Launch Countdown Exercises
– Operations Readiness Tests
• Test Bed
• Road to Launch
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 167

Test Definitions
Test Type Purpose & Objectives
RF Compatibility Testing Interface tests between the orbiter and the ground networks. Each ground
network performed separate testing (DSN, USN, WS1, and SN).
Mission Rehearsals Operations tests that provide training to the project team and MOT.
Rehearsals ensures team readiness for launch. Rehearsals are “dress
rehearsals” so teams and facilities are staffed according to the on-orbit
plans. Rehearsals include anomalies injected into the nominal timelines.
Mission Simulations Primarily are short simulations to provide training, prepare for mission
rehearsals and verify nominal sequences and flight procedures activities.
Mission simulations have targeted objectives and goals.
Operations Readiness
Tests
Test involving operations and ground network teams. Used to exercise
ground procedures and practice communications with the different networks.
Launch Countdown Test Launch countdown tests executes the pre-launch sequence leading up to
launch. Test include individual runs of the different pre-launch sequence
(Orbiter & Ground/Ops) leading up the integrated dress rehearsals with the
KSC launch vehicle team.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 168

RF Compatibility Testing
• RF Compatibility was performed with all ground networks
– Space Network
Conducted on 2/13/08 to 2/15/08
No issues or anomalies during RF testing
Included a end-to-end relay through the TDRS network with the orbiter
Test Results captured in NENS-CCE-CTR-0242
– Deep Space Network
Conducted on 4/21/08 to 4/26/08
End-to-end commanding problems and Command threshold discrepancy
Test Results captured in 872-0451
Performed re-test at KSC on 3/2/09 – 3/4/09
– End-to-end command was verified from the MOC
– Successful re-test of command threshold was performed
– Universal Space Network
Conducted on 3/5/08 to 3/8/08
Calculated lower than expected command threshold measurements, re-test was performed on 1/15/09.
– Retest showed all measurements were nominal.
Test Results captured in USN Test Report, 1A01113
– White Sands – WS1
Conducted on 4/27/08 to 5/02/08
No issues or anomalies during RF testing
Test Results captured in NENS-CCE-CTR-0242
Project Systems and Communications Engineers participated and reviewed final test result reports
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 169

Mission Simulations & Rehearsals
• Prior to Simulation or Rehearsal
– Systems Engineer Report (SER) is released outlining test objectives, configuration and setup,
planned activities, and timelines, as well as roles and responsibilities of each participant
– Procedures are developed that will be tested and checked-out during Sim or Rehearsal
• After each Sim or Rehearsal
– Test Summary is released providing test objectives summary, observations/notes, and
actions with associated lessons learned
– Info and actions are fed back into the “system” for incorporation for future work including
procedure update, ops systems updates, team training and upcoming Sims or Rehearsals
– Project Management and Senior Staff assess progress and ensure implementation of
lessons learned
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 170

Simulations and Rehearsals Test Matrix
• Mission Rehearsals and Simulations objectives were based on the following
priorities
1. Early Mission Activities (Leading up to and including LOI-1)
2. Exercising Contingency Procedures
3. Nominal Mission
4. Commissioning Activities
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 171

Mission Simulations Summary
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 172

Mission Rehearsal Summary
• Completed 252 hours of rehearsal testing
• Performed three mission rehearsals to date
– Nominal operations including performing a momentum unload
– Early Mission (Separation through end of LOI-1)
• All rehearsals had various anomalies injected for operations and engineering
team to detect and respond
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 173

Open Actions Summary
• Action items were captured in Simulation / Rehearsal Test Results
– Action items are collected into a single list and reviewed regularly
– Items are assessed for criticality and assigned to appropriate group
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 174

SIM‐24
SIM‐28
SIM‐15
Early Mission Contingency Simulations
Contingency Injected Impact
1 CSS Failure Bad performing Sun Acquisition
2 RW Failure Prior to 1‐shots Attitude Error and safing triggered Sun‐Safe
3 High Tip‐off Rates Failed Sun Acquisition
4 Star Tracker Miscompare (ST1 Phasing Error) ST1 Quaternion Output was bad
5 Tip‐off w/RW Failure (Spin Up) Bad performing Sun Acquisition
6 RW Failure (Spin Down) w/High System Momentum Bad performing Sun Acquisition
7 High Tip‐off Rate Bad performing Sun Acquisition
8 Star Tracker Miscompare (ST2 Phasing Error) ST2 Quaternion Output was bad
9 Bad thruster 1‐shots performance Thruster polarity or under performing thrusters
10 Late MCC Maneuver start MCC maneuver didn't start at expected time
Response
Transition to Observing Mode
Reconfigure for 3 wheel, continue timeline
Emergency De‐Spin after seperation
Compared output of ST1 & ST2, selected ST2
Reconfigure for 3 wheel
Perform Delta‐H and Reconfigure for 3 wheels
Emergency De‐Spin
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 175

SIM ‐ 14
SIM ‐ 21
LOI Contingency Simulations
Contingency Injected Burn Impact Response Results
1 Gyro Data Invalid Safing Aborted DV Burn ‐ Invalid Gyro LOI Restart Procedure Captured in Lunar Orbit
2 Failed AT Thruster Bank Safing Aborted DV burn ‐ Attitude Error LOI Restart Procedure Captured in Lunar Orbit
3 Large initial transient Safing Aborted DV burn ‐ Attitude Error LOI Restart Procedure Captured in Lunar Orbit
4 FSW Processor Reset Burn Aborted ‐ SunSafe LOI Restart Procedure Captured in Lunar Orbit
5 FSW Processor Reset Burn Aborted ‐ SunSafe LOI Restart Procedure Captured in Lunar Orbit
6 Failed thruster Safing Aborted DV burn ‐ Attitude Error LOI Restart Procedure Captured in Lunar Orbit
7 FSW Processor Reset Burn Aborted ‐ SunSafe with Trackers Occulted LOI Restart Procedure Captured in Lunar Orbit
• LOI-1 Contingencies Testing to Date
– Recoveries included the same LOI restart procedure
– All scenarios, LRO team captured into Lunar Orbit
– People were rotated into the different positions
– Exercised all the recovery aids (EEPROM ATS, Delta-H RTSs, LOI Restart
RTSs, Restart procedure)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 176

Launch Countdown Test Summary
• Three Separate Launch Countdown Sequences:
1. Ground System & Operations
2. Orbiter Launch Day Configuration
3. Atlas Launch Vehicle Countdown
• Countdown Testing
– Orbiter Launch Day Procedure
Procedure has been tested and the sequence verified separately
– Ground System & Operations Countdown
Sequence is in draft form, complete final steps based on actual launch date
Plan to test once to verify the flow and proper sequence timing
– Integrated orbiter launch day procedure and GS&O Countdown Testing
LRO Project Tests
Test to verify the sequence of the two countdown flows
– Participate in the Launch Vehicle Integrated Dress Rehearsals
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 177

Countdown
Type
Launch Countdown Testing Summary
Description Date
MOC
GSFC LRO Team
LRO KSC Team
Orbiter
Networks
ULA
Orbiter Launch Day Procedure used to power‐up and configure the orbiter Completed
Orbiter Launch Day Procedure used to power‐up and configure the orbiter Completed
Integrated Integrated exercise between the Orbiter Launch Day and GS&O Count 3/24/2009
Orbiter Launch Day Procedure used to power‐up and configure the orbiter 4/14/2009
Integrated ULA Integrated Dress Rehearsal 4/29/2009
Integrated Integrated exercise between the Orbiter Launch Day and GS&O Count 5/11/2009
Test events will provide training to personnel on the Launch Day Procedure, GS&O
Countdown Sequence, and Launch Vehicle Sequence
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 178

• Approach/Goals
Operations Readiness Tests
– Maintain operator proficiency
– Verify ground procedures and STOL PROCs
– Focus mostly on MOT and Ground Network interaction
– Test scripts are focused on the following scenarios
Initial Acquisition (Multiple Networks)
Station Handover (Multiple Stations/Networks)
LOI-1 Dual Station Coverage (DSN)
Nominal Mission Ground Support (All Networks, except Space Network)
– ORTs are scheduled by the GN Scheduling team per direction from the MOT lead
– Network Operations Manager (NOM) generates briefing messages and capture test
results
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 179

Operations Readiness Test Details
• Initial Acquisition Scenario
– Schedule SN, DSN and USN during ORT
Perform at least twice (more depending on results)
Exercise nominal initial acquisition procedures
Data flows come into the MOC at the same time
MOT directs stations (prime/backup) based on situation and directs change in data rate
• Station Handover Scenario
– Schedule DSN/USN or DSN/WS1 during ORT
Perform once with each combination (more depending on results)
Exercise the ability to receive multiple telemetry streams and execute the station handover procedures
– Handover procedures include prime and backup ops as well as beginning/end of track
• LOI Dual Coverage
– Schedule DSN (Goldstone site) during ORT
Schedule test at least once
Perform station sending data to BMOC and MOC
• Nominal Mission Scenario
– Schedule single station
Perform test once with selected stations
Simulate nominal station data rate
For WS1, simulate S and Ka
Simulate pre and post pass activities
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 180

ORT Testing Schedule
Start Date End Date Scenario/Stations TR Codes Test Configuration Notes
2/16/2009
(2009-047)
3/9/2009
(2009-068)
3/30/2009
(2009-089)
4/6/2009
(2009-096)
3/8/2009
(2009-067)
3/29/2009
(2009-088)
4/5/2009
(2009-095)
4/19/2009
(2009-109)
Nominal Ops:
DSN (DSS-34, DSS-24, DSS-54)
WS1 (WS1S & WS1K)
USN (USHS, USPS)
Early Mission Station Handover:
DSN (DSS-34, DSS-24, DSS-54)
WS1
USN (USHS, USPS, KU1S, WU2S)
Early Mission LOI Dual Coverage:
DSN (DSS-24 & DSS-27)
Early Mission Initial Acquisition:
DSN (DSS-34)
USPS
SN
S-Band
TR7
Ka-Band
TR1
TR30
TR53
TR34
No tests scheduled 2/20, 2/27 and 3/6 due to
Mission Sims & Rehearsals
MOT and ground station personnel will perform routine pre-pass
checks and MOT will perform pre-pass briefing
Schedule up to 2 supports per day with a minimum
MOT will execute nominal acquisition procedures
duration of 15 mins and maximum duration of 30
MOT and Ground Station will perform nominal post-pass activities mins. Please provide a minimum of 30 mins between
including all data transfers
supports. DSN & WS1 requires 1 hour prior and 15
Support termination will be performed in a nominal manner. mins post each support.
Two stations from list will be scheduled simulataneously.
MOT will configure and perform pass with station A
Near end of station A pass, MOT will configure for station B
Telemetry will be flow will be established between station B and
MOC
At scheduled handover time, MOT will direct Station A to drop
uplink and request Station B to enable uplink
Test will include MOC and LRO BMOC.
Connections will be established independently from both sites.
MOC -> DSS-24
BMOC -> DSS-27
MOC performs pre-pass briefing.
Perform simulated contact @ 8Kbps
Simulate ground station problem with DSS-24, switch to DSS-27
All three stations and KSC will be configured and connected to
MOC simultaneously.
MOC will perform pre-pass briefings with each ground network
Simulate launch vehicle separation with data online @ 2kbps
MOC determines good telemetry lock with either DSS-34 or USPS
and releases SN from support
Simulate switch to 128Kbps data rate, still receiving telemetry
from both stations
MOC directs switch of prime command station
If possible, schedule 2-3 supports with DSS-54.
No tests scheduled 3/18, 3/21 and 3/25
Schedule DSN and WS1 or DSN and USN with overlap
between each. Please schedule each combination of
DSN/WS1 and DSN/USN. It would be beneficial to
schedule the first 4 station pairs twice after the full
set is complete. This way in the event all the kinks
have not been worked out prior to the initial set of
events we will have the backup set to get clean runs.
No tests scheduled 3/31 due to Mission
Simulation
Schedule 2 supports with these stations with a
minimum of 2 days between.
No tests scheduled 4/6, 4/13, 4/18 due to
Mission Simulations
Schedule this event 3 times with all stations
simulatenously. In the event the first two runs are
successful, we may release the stations for the third
event.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 181

ORT Tests to Date
Event ID Description Date Station
LRO-ORT-001 Nominal Daily Operations 02/18/09 USHS
LRO-ORT-002 Nominal Daily Operations 02/18/09 WS1
LRO-ORT-003 Nominal Daily Operations 02/19/09 WS1
LRO-ORT-004 Nominal Daily Operations 02/19/09 USPS
LRO-ORT-005 Nominal Daily Operations 02/23/09 USPS
LRO-ORT-006 Nominal Daily Operations 02/23/09 WS1
LRO-ORT-007 Nominal Daily Operations 02/24/09 KU1S
LRO-ORT-008 Nominal Daily Operations 02/25/09 WS1
LRO-ORT-009 Nominal Daily Operations 02/25/09 USHS
LRO-ORT-010 Nominal Daily Operations 02/26/09 USPS
LRO-ORT-011 Nominal Daily Operations 03/02/09 DSS-45
LRO-ORT-012 Nominal Daily Operations 03/02/09 DSS-54
LRO-ORT-013 Nominal Daily Operations 03/03/09 DSS-54
LRO-ORT-014 Nominal Daily Operations 03/04/09 DSS-24
LRO-ORT-015 Nominal Daily Operations 03/04/09 DSS-65
LRO-ORT-016 Nominal Daily Operations 03/04/09 DSS-65
LRO-ORT-017 Nominal Daily Operations 03/05/09 WU1S
• Completed over 17 ORT Test Events to
date
All test to date have been nominal
mission
Test have been successful and
good learning/experience for the
networks and operations team
ORTs scheduled for the week of
March 9 th will include station
handover
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 182

Flatsat Test Platform
• System Engineering Report (451-SER-003439)
captures capabilities and differences for Flatsat
• SER captures includes the following information
– Overall design and physical construction of Flatsat
– Differences and limitations in detail for each component
– Performance differences from the flight system and
limitations of using flatsat for simulations
• Information captured in SER was based on:
– Experiences to date of the LRO team using Flatsat and the
flight system
– Execution of tests that were run against both flatsat and
the flight system
– Component documentation include drawings, design
documents, and user guides
Flatsat Capabilities and Differences are captured in a Project System Engineering Report
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 183

Flatsat Test Bed Diagram
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 184

Flatsat Operations Plan
• Flatsat Relocation Plan
– Test bed will remain in building 5 through launch and commissioning
– After nominal operations start, flatsat will be moved to building 32, near the MOC
– During the move of flatsat, the Sustaining Engineering Lab (CDH1) will act as
prime test bed
– Flatsat Re-certification after move
Plan to re-run all hardware functional on flatsat and FSW functional
– PDE, PSE, and C&DH
FSW sustaining engineering team will also re-run FSW acceptance tests
• Post-Launch Operations
– Operations test bed, used to verify updates to procedures, database, and nonroutine
activities
– Verify all maneuver loads prior to loading to the orbiter
– Verify FSW updates post launch
– Backup FSW sustaining engineering test bed
– Sustaining engineering support will be through project operations support tasks
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 185

Summary
• End-to-End testing performed and Space to Ground interfaces verified
• Completed over 400 hours of mission simulations and rehearsals to date
– Testing included nominal and contingency simulations
– Each test, the LRO team has improved and gained valuable experience
• Contingency simulations for critical activities (LOI and Initial Acquisition)
have been exercised
– Trained different personnel in the different roles, added to experience base within
the LRO team
• With remaining simulations and rehearsals, the team will continue to refine
their skills
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 186

FSW Sustaining Engineering
LRO Flight Operations Review – Section 15.0
NASA’s Goddard Space Flight Center
Mike Blau, LRO FSW Development
Scott Snell, LRO FSW Sustaining Engineering

FSW Status Update
• FSW Build Verification Testing is complete
• FSW System Testing is complete
• FSW Acceptance Testing is complete
– Acceptance Test Readiness Review was held 1/29/2009
• Requirements Verification Matrix is complete
• FSW User’s Guide is complete
• Launch-ready FSW (Build 4.3.3.2) is loaded on the orbiter
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 188

FSW Errata and Constraints
• Heater Control (HC) task uses the wrong AppID
– HC is using the wrong AppID for heater on/off commands to the PSE
– PSE can only handle 1 cmd/sec, but by using the wrong AppID the FSW may
sometimes send 2 cmds/sec
The 2nd command would come from the ground or an RTS
If two commands are sent to the PSE during the same cycle, one will not be executed
– Solution
Ops sends a “patch” command (already tested and delivered) to the FSW to change the
AppID to the correct value before enabling the HC task
• Added SSR partitions are lost after processor reset
– FSW includes a ground command to create additional partitions in the SSR
For use if large sections of DSB memory were to fail
– However, after a processor reset, the FSW will only restore the first 3 SSR
partitions
Because initialization always uses the default configuration table from EEPROM
– Solution
To create additional partitions, load a new EEPROM SSR configuration table file
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 189

FSW Errata and Constraints
• LEND Safing temperature limits wrong
– LEND flight spare has different thermistors than FU#1
– FSW Safing tables have limits for the original LEND unit
– Solution
Will have to monitor LEND temps from the ground until after LOI
Planned update to Safing Tables during commissioning phase
• FSW Constraints/Errata Document
– Total of 60 Constraints or Errata have been documented by FSW Development
team
– Most are too minor to discuss at this review
– Meeting was held on 2/11/2009 to review this document with the MOT
Confirmed MOT understanding of each issue and the workaround/response
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 190

Sustaining Engineering Resources
• Two FSW testbeds (FlatSat & CDH1)
– Includes capability to inject errors (e.g., memory bit errors), monitor bus traffic,
etc
• C&DH and GN&C FSW source code (written in C)
• Tools to create and analyze FSW products
• Experienced FSW Sustaining Engineering (FSSE) team
– Two FSSE engineers with a combined 23 years of experience across 8 missions
Also 5 years of mission operations experience
– Includes experience with LRO FSW legacy missions (SMEX, WMAP)
– Part of Multi-Mission FSSE Team
Colleagues having experience with other legacy missions (Swift-BAT, SDO, Triana,
EOS) are available for consultation and support
• FSW System and Build test suite
– Guards against delivering patches that may introduce regressions to FSW
function or performance
• Archive / CM methodology ensures accurate recovery of any previous FSW
version
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 191

• LRO FlatSat
Sustaining Engineering Facilities
– Primary operations simulator
Contains highest-fidelity components
– “Large” GDS
– Science-instrument simulators
– Maintained and operated by MOT
FSSE Team will maintain FlatSat image
– All FSSE upload products will be test-loaded to FlatSat prior to uplink
– Location: GSFC Building 5
Will be relocated to GSFC Building 32 (MOC) after orbiter commissioning phase is
complete
• LRO CDH1 (Flight Software Lab)
– Primary FSW simulator
– Redundant operations simulator
Will act as prime during FlatSat relocation and recertification
– Location: GSFC Building 1
Operational after relocation from GSFC Building 23
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 192

CDH1
S-Band
Tracking, Tlm,
& Cmd Sim
Ka-Band
Modulator
Sim
TWTA Sim
Ka-Band ITOS
lro-comm-scsim3
IP
Ka-Band FEP
cortex-xp-proto
Sustaining Engineering Facilities
Coax
S-Band
LAMP
Sim Sim
ethernet
Ka-Band
ASIST
Workstation
lro-cdh1-gse
IP
S-Band ITOS
lro-comm-scsim2
EDT Card
S-Band
BitSync
Coax
S-Band Card
Comm
Ka-Band CardsCard
Comm Cards
HK/IO
ETU
1PPS
Vx Works
Vx Host Works PC
lro-cdh1-host Host PC
GSE
UART
BAE
BOX
GSE
DSBs
(4)
RAD750
PCI
SpW Test Sim
Set (SWTS)
LROC Sim
Mini-RF
1553 BusMon
No RTsim
lro-cdh-1553
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 193
SpW
I/F
1553
I/F
1553
MAC
Card
ETU
Mini-RF
Sim
. . .
GDS #4 #1
Dynamic Sim
of all RTs
except MAC.
MAC analogs
1PPS
ethernet

• Pre-launch
FSSE Team Roles/Responsibilities
– Familiarization with FSW and test bed
– FSW Testing
– Operations Simulation / Mission Rehearsal support
– Thermal Vacuum Test support
– Plan and execute test bed relocation from development facility to SE facility
– Prepare Operations Interface Agreement and Sustaining Engineering Plan
– Verify FSW lab interface to MOC and other elements (e.g., AGS)
Conveying / Receiving FSW load and dump products
MOC command / telemetry connectivity to CDH1 (in case FlatSat is unavailable)
– Determine and test nominal patching methods
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 194

• Post-launch
FSSE Team Roles/Responsibilities
– Launch / Lunar Cruise / LOI / Commissioning Phase support
Prime FSW support is provided by development team
– Anomaly investigation / recovery
– Patch development / testing / installation support
– Configure / archive FSW and related products
– Maintain and operate CDH1
– Consultation with MOT on FSW-related questions
Development of operational workarounds for FSW-related problems
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 195

FSW Update Processes
Potential Enhancement / Unresolved Problem (SW bug / HW failure) /
Revised Mission Objective
Configuration Change Request (CCR)
Requirements Analysis
Review
Design
Review
Coding
Review
Testing
Review
Installation (w/ Removal Contingency)
Review
Delivery
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 196
If necessary

Transition Plan
• Allocation of duties during commissioning phase
– Joint (FSW Development and FSSE Teams) responsibilities
Patch design and development
Patch testing
– Lead role selection dependent on
Patch characteristics
Maturity of commissioning phase
– FSSE Team responsibilities
Creation and testing of patch uplink procedures
Support of MOT during patch uplink
Patch CM and archiving
• Handover process for
– Documentation
– Tools
– FSW lab and CM computer systems
Continuity of system administration
Continuity of ground system (ITOS/ASIST) and GDS support
– FSW oversight (to CCB)
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 197

• FSSE CCB
Transition Plan
– Authorizes, oversees, and tracks CCRs and WRs
– Comprises
Co-chairs
– LRO Project Representative (Mission Director)
– FSW Branch Multi-Mission FSSE Lead
FSSE Team
MOT
Orbiter Subsystem Engineers
– For extended mission phase, CCB co-chair will be SSMO Representative instead
of LRO Project Representative
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 198

Summary
• FSW Development and FSSE Teams have integrated
– Worked together during FSW testing, operations simulations, and thermalvacuum
testing
– Demonstrated good working relationship
Recent investigation of system events generated during connection of hot UART cable
showed good rapport between teams
Previous successful collaboration on TRACE mission
– Both teams are located at GSFC
• Unresolved issues
– None
• FSSE Team is ready to provide FSW products and services
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 199

Mission Assurance Assessment
LRO Flight Operations Review – Section 16.0
NASA’s Goddard Space Flight Center
Ron Kolecki
Systems Assurance Manager

LRO GS&O S&MA Activities
• Working to LRO Mission Assurance Requirements document which
includes problem reporting within the LRO CM system
• GSFC Gold Rules Compliant- no waivers
• Compliant to NPR 7150.2 SW Engineering Requirements
– LRO Ground Systems Development 431-PLAN-000046, 12/18/06
– LRO Mission Operations Center Configuration Management Plan 431-PLAN-
000083, 9/17/08
– LRO Ground System Integration Test Plan 431-PLAN-000402, 9/13/07
– LRO Mission Operations Test Plan 431-PLAN-000308, 10/3/07
– Test Plans for each subsystem in Ground System
– SW QAE receives current Problem Reports
SOARS and ECR Systems are being used
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 201

LRO GS&O Safety & Mission Assurance
• Identified requirements as basis of the GS&O development
• Requirements reviewed/analyzed to assure they were consistent, clear,
complete, compatible and testable
• Held a formal review of these baseline requirements
• Participated in engineering peer reviews
• Monitored the process to incorporate new requirements and interfaces
• Participated in design walkthroughs
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 202

LRO GS&O Safety & Mission Assurance (2)
• Traceability between architecture/components and requirements under
configuration management control
• Each build, delivery or release of GS&O documentation is under CM control
• All ground data systems procedures and test plans are reviewed by QA
prior to release.
• Test reports document validation of requirements
• QA and CM assures configuration control throughout all phases of the
mission
• Security program in place that meets the NASA requirements of NPR
2810.A
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 203

IV&V Summary
• IV&V conducted risk based assessment to prioritize IV&V analysis efforts
– Assessment resulted in IV&V efforts primarily focusing on flight software; limited
analysis on ground system software
• IV&V performed requirements traceability analysis
– Analysis focused on traceability between the Level 2 mission, Level 3 system,
and Level 4 software requirements for the following Ground System software
components: MOC (T&C and Trending), MOC (Attitude Determination) and FD
(Orbit Determination)
– Analysis identified 14 issues (8 Sev 3, 3 Sev 4, 3 Sev 5); All identified issues
have been closed/adequately addressed by the Project
• IV&V has no open risks associated with Ground System software
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 204

LRO GS&O Review Requirements
• LRO SQA has been involved with GS&O development activities since early
mission (mission SRR).
– Reviewed all Product Development Plans prior to release.
– On automatic distribution for all GS&O ECRs and SOARs (problem reports and
change requests).
– Monitored test activities (mission rehearsal & mission simulations).
– Conducted Product and Process Assessments and reported results to CSO and
Project Management.
– Generated GS&O Compliance Matrix for NPR 7150.2 Software Engineering
Requirements
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 205

LRO GS&O Review Requirements
• Assessments conducted:
– Project Planning Process
– Project Monitoring Process
– Requirements Management Process
– Risk Management Process
– Problem Reporting Process
– Configuration Management Plan
– Test Plan
No observations or findings were generated during these assessments.
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 206

Summary & Forward Plan
LRO Flight Operations Review – Section 17.0
NASA’s Goddard Space Flight Center
Cathy Peddie
Rick Saylor

LRO Readiness – PM Perspective
• The LRO TC\FLT
Controllers have been
operating the Orbiter
beginning with the
board level testing of
each of the LRO
subsystems.
• This table illustrates
the depth of
experience we have
with the critical
functions and
operations of the LRO
spacecraft.
• We have been honing
our skills in the
operation of LRO
throughout the entire
development and I&T
phase of our mission.
• LRO Project
Management is
completely confident
that we know how to fly
and operate LRO.
Mission Activity CPT 1 & 2 T‐Vac/Bal
LRO Mission Activity Mapping to Test Activities
Orbiter
Functional
& Payload
Functionals
Pop &
Catch
Tests
Sep
Test MRTs ORTs
LRO Orbiter Separation from Atlas X X X X X X
Space Network Telemetry Acquisition X X X X X X
AOS @ 2kbs ‐ DSN Goldstone X X X X
AOS WS1 X X X X
Post Sep Verification X X X X
Transition to 128kbps telemetry X X X X X X X
AOS @ DSN Madrid X X X X
SSR turn on X X X X X
PDE Inhibit Checks & Catbed turn on X X X X X X
AOS @ USN Weilheim X X X X
Solar Array Deployment X X X X
High Gain Deployment X X X X
Transition to Observing Mode X X X X X
Thruster 1‐shots X X X X X X
Delta‐H Momentum Unload X X X X X
Post Sep FDF Product Update X X
Generate Ephemeris & ATS Loads X X
Uplink Cruise Loads to Orbiter & Start ATS X X X X X
Transition to HGA Communications X X X X X
GNC KF Configuration X X X X X
Prelim MCC Maneuver Planning Verification X X
Final MCC Manuever Planning Verification X X
Load MCC‐E & MCC‐1 Manuever Plans X X
Pre‐MCC‐E Config Verification X X
MCC‐E Burn & Post Burn Activities X X X X
Pre MCC‐1 Config Verification X X
MCC‐1 Maneuver & post Burn Activities X X X X
CRaTER Instrument Turn‐on Activities X X X X X
LEND Instrument Turn‐on Activities X X X X X
Early Cruise Mini‐Gyro Calibration X X
LOI‐E & LOI‐1 Maneuver Plan Released & Tested X X
Pressurize Prop Sys ‐ Open HPLV & Fire Pyros X X X X X X
LOI Manuevers X X X X X
Spacecraft Commissioning X X
HGA Calibrations X X
Gyro & ST Calibrations X X
NASA’s Goddard Space Flight Center
Ka‐Band Checkout
S‐Band Rate Checkout
X X
LRO Flight Operations Review X (FOR) X
X
X
X
Day 2 X- 208
X
X
Instrument Commissioning X X X X
Nominal Mission X X X X X
Propulsion
System
Tests
Mission
SIMs
Mission
Rehearsals

FOR Summary
• MOC and LSR facilities and maintenance ready for launch
• BMOC exercised and ready for launch
• FDF ready to support mission
• SCN Network testing and certification (Space Network, DSN, USN, WS1, Network scheduling)
– Interface testing successfully conducted
– RF Compatibility testing successfully conducted
– Mission Readiness Testing successfully completed
– ORT testing underway
• Voice and data communication connections in place and verified
• Instrument SOCs ready to support mission
• Mission & Operations Systems Testing
– End-to-End testing performed and Space to Ground interfaces verified
– RF Compatibility Testing – all ground networks tested
– Mission Rehearsals – 3 out of 5 successfully conducted to date
– Mission Simulations – 21 out of 30 successfully conducted to date
Note: over 400 hours of Mission Simulation and Mission Rehearsal testing conducted
– Operational Readiness Testing – 17 successfully conducted to date
• Operations (Early Mission, Contingency, and Normal) – planned, understood, practiced in Mission
Sims and Mission Rehearsals
• FSW Sustaining Engineer – ready to support mission
LRO Project is ready to support our mission
NASA’s Goddard Space Flight Center LRO Flight Operations Review (FOR) Day 2 - 209