STATUS/ACCOMPLISHMENTS
The systems team released the draft SDO Mission Requirements Document
(MRD) for general review by Instrument and spacecraft subsystem teams.
The MRD captures the SDO level 2 requirements and provides traceability
back to the Level 1 Science Requirements document.  The initial MRD
release & review is in preparation for the SDO Systems Requirements
Retreat (SRR) next month, which is intended to be a detailed review and
validation of the SDO level 2 requirements before they are brought under
configuration control.  The systems team also released a draft document
tree for the SDO team to review.  This document tree details the work
products that will need to be generated in the coming months and also
acts as a road map for our future work.  We continue to work and focus
on two different spacecraft/instrument module mechanical configurations
and accommodation issues in preparation for the System Concept Review.
We developed a package highlighting the SDO/Launch Vehicle accommodation
challenges which was briefed to the GSFC program today.  Next week, we
will complete the GSFC review & finalize the presentation so that we can
brief NASA Code S on 1/24/03.

We continue to work the grassroots cost estimates.  This week we had
meetings with the mechanical team to go over structure/deployables/MSGE
development, the common Subsystem Data Node team to discuss schedule &
status, and we had discussions relating to the I&T flow & EGSE costs.
Our plan is to have all the subsystem schedules created and linked to
the spacecraft integration flow by 2/10/03.  From the last 2 weeks of
meetings, we learned more about budget/schedule risks, so I our risk
management coordinator has started to meet with all the leads in order
to update the project risk list.  The SDO business team attended the
very informative IFMP meeting & completed tools for the upcoming budget
process.

In the area of Instruments, we prepared and released an Instrument
Interface Requirements Checklist which captures in some significant
detail candidate requirement items for the SDO spacecraft to instruments
interface requirements documentation.  In addition, we developed an
agenda for the upcoming Instrument Systems Requirements Review which
will be held at the Instrumenters facility following our internal SDO
Systems Requirements Retreat.  Our Contracting Officer created a
time-line for the preparation and generation of the required Instrument
Phase B/C/D/E contract documentation and we generated a couple of
content outlines for the Instrument Performance Specifications.  The HMI
team participated in several telecons and other discussions this week to
exchange information in preparation for our internal SRR.  The team is
working to provide updates or new information regarding pointing and
alignment needs, mass properties, a top level FEM, radiator loads, a top
level thermal math model, limb tracking needs and electrical interface
data.  We introduced the HMI team to Steve Merrihew for ICD development,
Tom Manson for System Reliability, and Steve Schumacher for C&DH
information.  The HMI Instrument System Requirements Review is scheduled
for March 13, 2003 at Lockheed Martin Palo Alto.  The GFSC Instrument
team & Flight Assurance Mgr. will be traveling to Boulder CO for an
interchange meeting & site visit with the EVE LASP team.

We completed our GSFC housing requirements through FY07 which includes
all personnel supporting SDO on-site (civil servant or contractor) and
submitted the information to our LWS program office.  We are currently
working SDO's housing requirements in Bldg. 29/Room 360 and with the
launch of ICESat, SDO should be able to occupy the GLAS cubicles within
the next 90 days.

The ground system team revised antenna link margin design parameters,
updated the Detailed Mission Requirements with level-2 requirements, and
started a draft of the Operations Concept.  We received and started
reviewing the preliminary "Rain Study" analysis for the White Sands
ground station.  The Flight Assurance team began development of the SDO
Software QA Plan and updated the SDO System Safety Program Plan for review.


Thanks & sorry for being late with this report,
Ken

"The purpose of the Formulation subprocess is to refine mission concepts
in order to define an affordable program and plan to meet mission
objectives or technology goals specified in the NASA and SSE Strategic
Plans.  The Formulation subprocess includes developing advanced
concepts, conducting trade studies, defining technology development
goals, exploring implementation options, establishing internal
management control functions, performing cost and performance analyses
on concepts deemed to have a high degree of technical and operational
feasibility, and identifying reserves associated with program risk
management and other estimated project reserves."

Space Science Enterprise Management Handbook