The SDO development team is continuing the push towards both the 
subsystem-level and mission PDRs.  The systems team completed an update of 
the Mission Requirements Document (MRD) and is planning on submitting the 
MRD into the CM document baseline process next week.  The recent version of 
the MRD has been updated with recent configuration changes, including the 
incorporation of the AIA instrument.  Generation and review of critical 
documents required by PDR (as defined by the SDO document tree) are 
continuing via the SDO CM system.  Each of the subsystems is working to get 
their subsystem requirements and verification matrices into CM review prior 
to subsystem PDRs.  These requirements will populate a DOORS database, 
easing the task of tracing requirements from one level to another.

In other areas, the systems team has completed a re-evaluation of the mass 
and power budget and has released updated resource budgets along with 
margin (based on an assessment of subsystem maturity) to be carried and 
managed at the subsystem level, as well as still retaining margin at the 
system level for project reserves. The Subsystem Data Node (SDN) prototype 
is being used by the flight S/W team for developing diagnostic S/W, 
bootstrap/loader/monitor, and the board support package for the software 
bus.  Work is also continuing in addressing SDN parts 
selection/implementation issues, backplane design, and the common Power 
Converter Card (PCC) design.  Attitude Control Electronics (ACE) bread 
board development is progressing forward, folding in the comments from the 
recent ACE breadboard peer review process.  The High Gain Antenna (HGA) 
commanding interface is being further developed, as well as an assessment 
of the HGA system jitter budget and its effect on the overall spacecraft 
jitter budget.  The Observatory team continues to work schedule 
linkage/logic, critical path confirmation, control milestones for the 
subsystem leads, & phasing plans.  The reliability team is working with the 
subsystems to develop FMEAs, Fault Tree Analyses, and Reliability Block 
Diagrams in preparation for the subsystem PDRs, the Systems Engineering 
PDR, and the Mission PDR.

The SDO team held their first Launch Vehicle Technical Interchange Meeting 
with KSC this week.  KSC provided a launch service program overview, along 
with facility capabilities and a launch vehicle procurement schedule.  We 
also visited the Payload Processing Facility at Astrotech, as well as the 
Delta 4 and Atlas 5 launch provider facilities.  The SDO/KSC team started 
work on the SDO Launch Vehicle Interface Requirements Document, which is 
required for the Launch Service Task Order process.  A special thanks to 
Kevin Hughes (our L.V. I/F engineer) & the KSC team lead by Ron Mueller & 
Larry Craig for preparing & conducting a great meeting at KSC.

After the push last week to finalize the AIA Phase A/B contract, focus 
turned to finalizing the arrangements for the upcoming HMI and EVE 
PDRs.  We are working with the Code 300 System Review lead for SDO to 
refine the agenda and assemble the review panel for the instrument 
PDRs.  We are inviting a couple of SDO Independent Review Team members to 
participate on the GSFC panels.  We also worked with the HMI management 
team to coordinate the transfer of the e2v CCD contract from NRL to 
Stanford University.  e2v is currently contracted by PRAXIS and we will 
maintain this relationship through the development phase to prevent 
disruption of the e2v CCD development efforts.  PRAXIS has agreed to 
seamlessly transfer contract authority from NRL to Stanford for this 
work.  AIA conducted its initial Science Team meeting this week.  The SDO 
Project Scientist and AIA Instrument Manager attended.  Finally, we 
coordinated the EVE presentation package for a presentation to Headquarters 
outlining the rationale for the recommendation to remove the Optics Free 
Spectrometer (OFS) assembly from the EVE configuration.

The AIA team held its first science team meeting at Stanford University 
October 30-31.  The meeting focused heavily on the science requirements of 
the AIA and the path to PDR.  The Project Scientist met with the AIA 
science leads and began finalizing the full and minimum success science 
requirements.  Several topical Science Working Groups are being 
established, to stimulate discussion and collaboration between the SDO 
science teams.  Themes of the working groups include Space Weather and 
Geospace Connections.  The first SDO Science Workshop is in the planning 
stages. The workshop will take place March 22-26, 2004 in Boulder, CO, and 
will be hosted by the EVE team at the University of Colorado.  This 
workshop is open to all members of the international science community and 
will focus on the SDO investigation science goals and working group 
topics.  A website will be up soon, with registration and travel 
information.  A science organizing committee will establish the agenda for 
the meeting.

The HMI team concluded its series of internal reviews with the Telescope 
and Focal Plane Assembly Peer Review this week.  SDO subsystem members 
representing structures, thermal, and hardware QA participated in the 
review providing valuable insights.  In addition, GSFC has provided 
feedback to the HMI team on the HMI Concept Study Report.  Preparation has 
begun at both GSFC and Palo Alto for the HMI PDR on November 18 and 19, 2003.

The EVE team and the SDO project are reviewing impacts to the relocation of 
the EVE electronics box to alongside the instrument.  A slight FOV and 
glint issue is being looked at from the HMI telescope cover during 
deployment.  EVE also met with MIT Lincoln Labs for technical CCD 
discussions - a peer review on the CCD is planned for mid-November.  EVE 
PDR coordination is underway with a scheduled date of December 17-18 in 
Boulder, CO. A dry-run will be held November 12-13.

The Mission Assurance team is nearly complete with the final round of 
document/negotiation reviews associated with HMI's Performance and 
Assurance Implementation Plan (PAIP) and Lockheed Martin's internal 
workmanship standards per the requirements set forth in the SDO Mission 
Assurance Requirements (MAR).  The team also provided comments to the draft 
HMI Performance Verification Plan.  Software QA participated in the recent 
Software Bus (SB), Remote Terminal (RT) and Health & Safety (HS) reviews 
and will document/track actions.

The ground system performed a complete schedule, WBS, and budget overhaul 
this week at their three day retreat.  A completely revised and more 
accurate representation of ground system development has been prepared and 
is ready for Project  review.

In the area of CM & Project Support, the team: now has the capability to 
add and edit user information in our intranet/database; distributed CCR for 
review (SDO-CCR-021: Solar Array Sizing); coordinated changes received from 
the review of the Single Board Computer Spec. and SOW; updated monthly CM 
calendar showing dates as to when documents were distributed for review and 
when comments are due; provided assistance to a few SDO team members on how 
to generate templates for documents; continued DOORS training; worked with 
the systems team to update the document tree & prioritize documents for the 
PDR; received approvals for Bldg 29 360 office mods; submitted SDO 
purchasing requirements into the SAP or Bankcard system; & completed 
preparations for the SDO AETD Champion Team meeting next week.  In 
addition, we resolved an issue with the IFMP Help Desk concerning SDO's 
purchase request approval authority (known as Release Group Strategy) in 
SAP.  SDO's Release Group Strategy was incorrectly moved by the IFMP 
Support Group in the SAP system and this, in turn, would send our purchase 
requests to the wrong organization for approval.  We have been promised 
that this error will be corrected next week.


Thanks,
Ken