1. SOWG Meeting January 18-19 2007 Agenda (09 January 2007)

2. Thursday 18 January (Afternoon)
Time Items for discussion Lead Participants
01:30 Gather at Bldg 14 door (North)
01:30 Introduction, Agenda Review
02:00 Calibration maneuvers scheduling and HGA blockage Defazio
HGA Blockage: operational overview, timing constraints Hashmall
Impact on cal maneuvers: scenarios and scheduling
03:30 GT calibration maneuver scenarios Larduinat, Shulman
04:00 Instrument commissioning Gonzales
Review existing timeline
Gather updates from instrument teams
04:30 Tour of MOC facility Tann, Silva
Mission Operations Room, and Science Operations Room
SOC input on layout of Science Operations Room
05:00 Adjourn

3. Friday 19 January (Morning)
Time Items for discussion Lead Participants
08:30 Gather at B14 door
08:45 Demonstrations
08:45 MOC trending system (ITPS)- web interface for SOCs Brumer
10:00 MOC Planning tool and scheduling timeline Sapper
10:30 Review schedule of activities for 2007
Ground System schedule and milestones Silva
SOC planned involvement and support
SOC Interface Testing Larduinat
MOC product server
Updates on planned tests for 2007
12:00 Adjourn

4. Tentative as of 09 January 2007
Attendance List
Tentative as of 09 January 2007
Brumer, Haim
Defazio, Bob
Gonzales, Peter
Hashmall, Joe
Jacobson, Rob
Sapper, Brett
Shulman, Seth
Silva, Chris
Sonti, Vijaya
Starin, Scott
Tann, Hun
VanDyke, Chris
Vess, Melissa
Weikel, Craig
Wofford, George
Bryant, Karen
Bush, Rock
Gregory, Sarah
Heyman, Gary
Myers, Dawn
Pesnell, Dean
Scherrer, Phil
Schou, Jesper
Tate, Gail
Wolfson, Jake
Woodraska, Don

5. Time and Location
Meeting in Room E280, Building 14 (same as last SOWG at GSFC)
Meeting times: Thursday January 18, 1:30PM to 5:00PM, following IFWG meeting and Friday January 19, 8:30AM to 12:00PM
Come to the Building 14 door as indicated on the map. Somebody will meet you there since you need a keycard to enter the building
The conference room is on the second floor, right above the door where we meet.

6. Notes on Trending and Analysis SDO SOWG - January 18-19, 2007 Purpose/Goal:
Confirm understanding of planned use of planning tools by the FOT and the SOCs.
Quoted material from Instrument PERs.

7. General understanding (1 of 2)
ITPS is primarily used in the MOC by the FOT for trending spacecraft health and safety parameters
ITPS needs the TLM database definition (RDL files) for all HK telemetry packets containing parameters to be trended.
A copy of ITPS is accessible from the Web and is available for use by the SOCs
Each SOC has its own trending system, in support of which:
All HK telemetry packets (spacecraft and instruments) are available for distribution to the SOCs
SOCs are responsible for ingesting that telemetry into the SOC trending system
TLM database definition for all spacecraft HK telemetry is available to SOCs as RDL files
SOCs are responsible for translating the RDL files into the native format needed by the SOC trending system

8. General understanding (2 of 2)
SOCs are likely to use ITPS
Trending and analysis of spacecraft parameters for which the SOC
has not imported the TLM database definitions
Has not archived the s/c HK telemetry for long trend analysis
Envisioned on an as needed basis in support of routine operations or for troubleshooting and anomaly investigation

9. AIA Trending (From PER)
A preliminary list of items that will be trended throughout I&T and orbital operations (when practical) has been established
Spin time for filterwheels, shutter, and aperture selector
Focus mechanism end points and center locations
Mechanism delay time ranges (an internal parameter)
Voltages (primary and secondary) and currents
Key temperatures
HOPA times until doors release (especially as a function of temperature)
Best focus position
Camera System linearity, gain, offset, dark current, bright pixels, etc
Alignments (see next presentation)
Various Software Error Counters

10. HMI Trending (From PER) (1 of 2)
Trending Purpose
Throughout HMI I&T at LMSAL and GSFC, and throughout the mission as appropriate, a subset of instrument parameters are trended to continually evaluate the health and performance of the HMI instrument
Trending Philosophy
Parameter selected for trending are either critical to function or performance
Trending analysis is carried out to establish nominal limits for each parameter
Parameters that exceed their nominal limits are investigated and dispositioned
Out-of-family conditions are monitored. An out-of-family condition is one where a parameter maintains a certain range for a period of time, and then deviates noticeably from the previous stable condition while still r4emaining within nominal limits. These situations are investigated to be sure the out-of-family condition does not develop into a problem

11. HMI Trending (From PER) (2 of 2)
Preliminary list of items to be trended:
Instrument current/power
Alignment between HOP alignment cube and the boresight
Focus
CCD co-alignment
Spin time for filter wheels, focus wheels and shutters
Mechanism delay time ranges (HMI internal parameter)
Key temperatures
Camera system responsivity, linearity, gain, offset, dark current, bright pixels, etc,
Contamination and vigneting
Front window and blocker fringes
Birefringence (Stress)

12. MOC Product Server SDO SOWG - January 18-19, 2007 Purpose/Goal:
Provide as-implemented MOC Product Server directory structure and files names in preparation for upcoming MOC-SOC tests.
Collect information from SOCs on desired set-up for testing (which machine do you want to use? when do you want to start testing? what products are available?)

13. One sudirectory labeled moc/lzp/yyyy_ddd for: All APIDs for that DOY
Product
Directory name
File name
Retension time
Comments
MOC to SOC
Level 0 Data
moc/lzp/yyyy_ddd
apid_yyyy_ddd_ver.hkt
apid_yyyy_ddd_ver.xml
7 days
One sudirectory labeled moc/lzp/yyyy_ddd for:
All APIDs for that DOY
Both .hkt and .xml files
All file versions
FDS Short Term
moc/fds/shortterm
See MOC/SOC ICD Table 5.1
Example: ECLIPSE_yyyyddd.Snn
2 product cycles:
One single directory for
All sets of short term products (current and previous)
FDS Long Term
moc/fds/longterm
Example: ECLIPSE_yyyyddd.Lnn
2 product cycles
Same as for short term products
MOC Status Report
moc/reports/status
moc_status_yyyyddd_type_vnn.rpt
Life of mission
Suggest adding “userfield” to file name: this is a free field that could further specify the type of report.
Examples: weekly, monthly, sim#1, etc
Meeting Mins
moc/reports/minutes
minutes_yyyyddd_type_vnn.rpt
Suggest adding “userfield” to file name.
Examples: weekly, quarterly, etc
SData Accounting
moc/reports/sdata_accounting
account_yyyyddd_vnn.rpt
One file per day for Life Of Mission, all in same directory:
(We may want to keep less than LOM on the DMZ server)
Integrated Print
moc/integratedprint
IP_loadtype_yyyyddd_vnn.rpt
21 days
Loadtype represents the kind of ATS load.
Examples: ECLIPSE, EVEFOV, etc
Command History
moc/cmdhistory
cmdhist_yyyyddd_vnn.rpt
One file per day, all files in same directory

14. Product
Directory name
File name
Retension time
Comments
SOC to MOC
Status Report
soc/status
ins_status_yyyyddd_vnn.rpt
Life of mission
ins is AIA, HMI or EVE
Science Uplink Plan
soc/science_uplink
ins_uplink_yyyyddd_vnn.rpt
21 days
Planning Timelines are shown as jpg files on the MOC Product Server in the MOC-SOC. Instead, we suggest using web access.