Solar Dynamics Observatory (SDO) Project
Database Format Control Document
(DFCD)
464-GS-PLAN-0042
Revision - A
Effective Date: 06/20/200503/23/2006
Expiration Date: 03/23/201106/20/2010
Prepared By: Maureen Suckling/Code 452
CHECK THE SDO MIS AT
TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.
464-GS-PLAN-0042
Revision A
CM FOREWORD
This document is a Solar Dynamics Observatory Project controlled document. Changes to this document require prior approval of the SDO Project Configuration Control Board (CCB) Chairperson. Proposed changes shall be submitted to the SDO Project Configuration Management Office (CMO), along with supportive material justifying the proposed change.
Questions or comments concerning this document should be addressed to:
SDO Configuration Management Office
Mail Stop 464
GoddardSpaceFlightCenter (GSFC)
Greenbelt, Maryland20771
1
March 23, 2006
464-GS-PLAN-0042
Revision A
Reviewed By
Hollys Allen
Dave Amason
Tom Anderson
Tom Bialas
EJ Bickley
Bob Calvo
Harry Culver
Bob DeFazio
Paula Everson
Cindy Firman
Mike Garner
Pete Gonzales
Amri Hernandez-Pelle
Dennis Hewitt
Steve Himes
Rich Hollenhorst
Kevin Hughes
Tom Kenney
Denney Keys
Michelle Lacombe
Eliane Larduinat
Stephen Leake
Maria Lecha
Leo McConville
Marco Midon
Wendy Morgenstern
Son Ngo
Daniel Nguyen
Ray Pages
Dean Pesnell
Bill Potter
Mike Powers
Brent Robertson
John Ruffa
Chad Salo
Brett Sapper
Joe Schepis
Michael Scott
Frank Scoville
Chris Silva
Vijayasree Sonti
Scott Starin
Hun Tann
Barbara Thompson
John VanBlarcom
Mark Walters
Dave Ward
Jim Wiedman
Craig Weikel
Mike Xapsos
1
March 23, 2006
464-GS-PLAN-0042
Revision A
Solar Dynamics Observatory Project Database Format Control Document
DOCUMENT CHANGE RECORD
REV/ VERLEVEL / DESCRIPTION OF CHANGE / APPROVED
BY / DATE
APPROVED
-
A / Baseline release of document per the approval of SDO-CCR-0298
Updated following approval of SDO-CCR-0505 / R. Lilly
R. Lilly / 06/20/05
03/23/06
1
March 23, 2006
464-GS-PLAN-0042
Revision A
Table of Contents
1.0Introduction......
1.1Purpose......
1.2Scope......
1.3References......
1.4Telemetry and Command Database Abstract......
1.5Instrument Database Responsibilities......
2.0T&C Systems and Project Database Development......
2.1Facilities Using a T&C System......
2.2Project Database Development......
3.0ASIST RDL Guidelines......
3.1ASIST RDL File Naming Convention......
3.2Flight Software System Table RDL Files......
3.3RDL File Preamble......
4.0Telemetry Mnemonic Naming Convention......
4.1Observatory Telemetry Mnemonics......
4.2SDO GSE and Ground System Telemetry Mnemonics......
4.3Pseudo Telemetry Mnemonics......
4.4Flight Software System Table Mnemonics......
5.0Command Mnemonic Naming Convention......
5.1Observatory Command Mnemonics......
5.2GSE and Ground System Directive Mnemonics......
6.0ASIST Telemetry Display Pages......
7.0STOL Procedures......
7.1STOL Procedure Development Philosophy......
7.2STOL Procedure Development Guidelines......
7.3STOL Procedure Naming Convention......
7.4STOL Procedure Preamble......
8.0Configuration Management and Distribution of the Project Database......
8.1Project Database Lifecycle......
8.1.1Component Development......
8.1.2Observatory I&T......
8.1.3Flight Operations......
8.2Project Database CM and Distribution Process......
8.2.1MOC File Transfer Gateway......
8.2.2File Transfer Gateway Implementation......
8.2.3File Transfer Gateway Directories......
8.2.4Project Database Validation......
8.2.5Project Database Central Repository......
APPENDIX A: Recommended Abbreviations and Acronyms for RDL, Telemetry, and Command Names
APPENDIX B: Telemetry RDL Preamble......
APPENDIX C: Command RDL Preamble......
APPENDIX D: FSW System Table RDL File Preamble
APPENDIX E: STOL Procedure Example and Guidelines
APPENDIX F: Contact List for Component Development
APPENDIX G: Contact List for Observatory I&T
APPENDIX H: Database Release Milestones
APPENDIX I: ASIST Database Directory Description
APPENDIX J: Acronyms
1
March 23, 2006
464-GS-PLAN-0042
Revision A
List of Figures
Figure 81 Initial Project Database Build
Figure 82 Database Flow during Observatory I&T
Figure 83 Database Flow during Flight Operations
Figure 84 Project Database CM and Distribution
Figure 85 File Transfer Gateway Login
Figure 86 File Transfer Gateway Home Directory
Figure 87 Database Distribution Directory Structure
List of Tables
Table 31 RDL File Name Values
Table 41 Observatory Telemetry Mnemonic Name Values
Table 42 GSE Telemetry Mnemonic Name Values
Table 51 Observatory Command Mnemonic Name Values
Table 52 Directive Mnemonic Name Values
Table 71 Procedure Field Naming Convention Guidelines
Table 81 Telemetry and Command Database Files
1
March 23, 2006
464-GS-PLAN-0042
Revision A
List of TBDs/TBRs
Item No. / Location / Summary / Ind./Org. / Due Date1
March 23, 2006
464-GS-PLAN-0042
Revision A
1.0Introduction
This Database Format Control Document (DFCD) defines the specific requirements for creation and maintenance of the ground system Project Database for the Solar Dynamics Observatory (SDO) mission.
1.1Purpose
The purpose of this DFCD is to provide the basic rules of convention, construction, and style for the SDO Project Database. Additionally, it defines the rules of exchange of the Project Database between Telemetry and Command (T&C) systems and the Project Database repository at GSFC.
The construction of the Project Database begins during the development phase of the SDO instruments and spacecraft hardware and software components., The Project database continues to mature throughout Observatory Integration and Test (I&T) and ultimately becomes the database used during Flight Operations.
The T&C system used for development, I&T, and Flight Operations in the Mission Operations Center (MOC) is the Advanced Spacecraft Integration and System Test (ASIST). Each Science Operations Center (SOC) uses its own T&C system, which interfaces with the MOC ASIST T&C system. Therefore, portions of this document will extend to the Project Database elements that reside in the SOC T&C systems, including the Extreme Ultraviolet Variability Experiment (EVE), Atmospheric Imaging Assembly (AIA), and Helioseismic and Magnetic Imager (HMI). The extent to which this DFCD applies to the SOCs is summarized in Section 1.5.
Also included in this document are guidelines for Spacecraft Test and Operations Language (STOL) procedure development, guidelines for telemetry display page development, and the Project Database Configuration Management (CM) process that will be applied at the various stages of mission development.
1.2Scope
This DFCD is intended for use by anyone directly using or interfacing with the SDO MOC T&C System and is of particular use during the early stages of the Project Database creation.
The scope of this document extends to the databases used by external T&C systems that interface with the MOC T&C system. This DFCD specifies conventions that apply to elements of these external T&C databases that must be compatible and exchangeable with the Project Database. The SOCs’ remote T&C systems are important examples of this extension in scope. All subsets of the SOCs local databases that will be provided for use by the MOC T&C system as well as all subsets of the Project Database that will be provided to the SOCs for use by their own T&C systems will adhere to the conventions defined in this document.
In addition to supporting the MOC, ASIST will be the central T&C system supporting pre-launch spacecraft development and I&T activities at GSFC in the Flight Software Development Lab and the Attitude Control Electronics (ACE), Power System Electronics (PSE), Gimbal Control Electronics (GCE), and Command & Data Handling (C&DH) hardware component development labs. The ASIST T&C system is also integrated with the Spacecraft Simulator (SSIM) that is provided to the instrument development labs.
Project Database elements covered in this document include the following:
a)Observatory Telemetry Database – Includes all spacecraft housekeeping telemetry definitions and a subset of the instrument housekeeping telemetry.
NOTE: Instrument science telemetry format is outside the scope of this document.
b)Ground Support Equipment (GSE) Status Database – Includes definition of status telemetry for all I&T Electrical Ground Support Equipment (EGSE), Instrument Ground Support Equipment (IGSE), and Ground System elements such as the SDO Ground Station (SDOGS), the Data Distribution System (DDS), and the DDS and SDOGS Integrated Manager (DSIM).
c)Pseudo Telemetry Database – All pseudo-telemetry for spacecraft, GSE, Ground System, and a subset for the instruments. Pseudo-telemetry includes data points that are computed, constructed, or otherwise derived from one or more telemetry items.
d)Observatory Command Database – Includes all spacecraft command definitions and a subset of the instrument command databases.
e)GSE and Ground System Directive Database - Includes definition of directives to control I&T EGSE, IGSE, and all ground system components, including the MOC, SDOGS, and DDS, that can receive directives from ASIST.
f)Procedure Database – Includes STOL procedures that contain a sequence of steps to command, configure, control, test and/or monitor the Observatory, I&T GSE, and ground system components.
g)Flight Software (FSW) System Table Definitions - Includes definitions for the real-time interpretation and display of system tables used by the spacecraft flight software and downlinked in the spacecraft housekeeping telemetry stream.
h)ASIST Display Page Database – Includes page displays used to evaluate and monitor the Observatory, I&T GSE, and Ground System components.
1.3References
The following documents are applicable to this DFCD and changes in these documents take precedence over this document :
- SDO Detailed Mission Requirements (DMR) Document, 464-GS-REQ-005, GSFC
- SDO CCSDS Implementation Document, 464-SYS-SPEC-0033
- Interface Control Document (ICD) Between the SDOMissionOperationsCenter (MOC) and the ScienceOperationsCenters (SOC), 464-GS-ICD-0001
- SDO Project CM Procedures Document, 464-PROJ-PROC-0010
- SDO Project Problem Reporting (PR) Procedure, 464-SA-PROC-0029.
The following document is for reference only, providing additional useful information related to this DFCD:
- ASIST Workstation Users Guide, GSFC, Release 9.4 or higher (GSFC onsite access available online at “
1.4Telemetry and Command Database Abstract
During the SDO component and instrument development effort and prior to the start of the SDO Observatory I&T activity, it is essential that the Observatory Command Database and Observatory Telemetry Database be constructed. Each telemetry and command definition includes a mnemonic. A unique alphanumeric mnemonic is given to each command function and each telemetry item. Each command mnemonic contains the information needed to generate the binary commands acceptable by the spacecraft. Each telemetry mnemonic contains the information needed to interpret the binary packets received from the spacecraft.
The IGSE (including the instrument T&C systems) may have T&C systems that are different from ASIST, and it may not be possible to have "ASIST-like" mnemonics within an IGSE. However, the goal is to establish mnemonics that are compliant with this DFCD where practical. In all cases where adherence to this DFCD is not possible, a clear mechanism for mnemonic translation will be defined.
1.5Instrument Database Responsibilities
Section 6.5 of the MOC-to-SOC ICD, Reference 3, defines the high level agreements for the exchange of database files between the MOC and the SOCs. These agreements can be summarized as follows:
- The SOCs define the instrument commands that may be used by the MOC and I&T Control Center in real-time command procedures and spacecraft stored command sequences (absolute time sequences and relative time sequences).
- The SOCs define the instrument housekeeping telemetry packets containing data points that the MOC and I&T Control Center may monitor on behalf of the instrument teams.
- The MOC provides each SOC the definition of all spacecraft telemetry packets containing data points that the SOC may want to monitor
- All telemetry and command definition exchanges will be in ASIST Record Definition Language (RDL) format.
- All Instrument STOL procedures resident in the MOC will follow the STOL conventions defined in this DFCD.
The portions of this document that are applicable to the instruments include:
1)Section 2.0T&C Systems and Project Database DevelopmentT&C Systems and Project Database Development - describes the T&C systems being used and gives an overview the Project Database development
2)Section 3.0ASIST RDL GuidelinesASIST RDL Guidelines- This applies to the subset of the command and telemetry databases that is exchanged between the SOCs and the MOC.
3)Sections 4.0Telemetry Mnemonic Naming ConventionTelemetry Mnemonic Naming Convention and Section 5.0Command Mnemonic Naming ConventionCommand Mnemonic Naming Convention - These sections defines the rules for generating mnemonics. The EVE T&C system, the Operations and Science Instrument Support – Command and Control (OASIS-CC), does not accommodate the mnemonic naming convention defined in this DFCD. The EVE instrument team shall provide the translation from the OASIS-CC telemetry and command mnemonics to the ASIST command mnemonics as needed for the subset of the EVE T&C database provided to the Project Database. The in-house T&C system used by HMI and AIA accommodates the mnemonic naming conventions defined in this DFCD.
4)Section 6.0ASIST Telemetry Display PagesASIST Telemetry Display Pages- The instrument telemetry data points that are to be viewed in the MOC will adhere to the guidelines laid out for telemetry display pages. The Flight Operations Team (FOT) will work with the instrument teams to develop all required instrument display pages for the MOC.
5)Section 7.0STOL ProceduresSTOL Procedures - This section provides guidelines for developing STOL procedures. All instrument STOL procedures residing on an ASIST T&C system in the MOC or I&T Control Center are required to follow the procedure template defined in this DFCD, including the defined preamble and naming convention
6)Section 8.0DatabaseDatabase CM - This section describes the CM process applicable to the Project Database. This CM process also applies to all instrument database information that is incorporated into the Project Database. It is not the intent to impose any specific CM policy or procedure on the instrument teams with regard to their systems. However, the instrument teams are responsible for implementing an appropriate CM process, which incorporates the essential elements of configuration control and assures that the accuracy, availability, and overall integrity of the T&C database are preserved.
1
March 23, 2006
464-GS-PLAN-0042
Revision A
2.0T&C Systems and Project Database Development
This section describes the various facilities developing and using the Project Database as well as a description of the Project Database development.
2.1Facilities Using a T&C System
T&C systems will be used during the multiple mission phases and in multiple facilities. The following list details the T&C systems for each of the mission phases.
1)Component Development:
- Flight Software Development Lab, GSFC (ASIST)
- ACE, C&DH, GCE and PSE Hardware labs, GSFC (ASIST)
- HMI Development Lab, Lockheed-Martin Solar and Astrophysics Laboratory (LMSAL) (HMI/AIA T&C System)
- AIA Development Lab, LMSAL (HMI/AIA T&C System)
- EVE Development Lab, Laboratory For Atmospheric and Space Physics (LASP) (OASIS-CC)
Note: each Instrument Development Lab includes SSIM (ASIST)
2)Integration and Test:
- SDO I&T ControlCenter, GSFC Bldg-7 (ASIST)
- AIA I&T System, I&T ControlCenter, GSFC (HMI/AIA T&C System)
- HMI I&T System, I&T ControlCenter, GSFC (HMI/AIA T&C System)
- EVE I&T System, I&T ControlCenter, GSFC (OASIS-CC)
- SDO MOC (GSFC Bldg-14) (ASIST)
- DDS/ DSIM Development Lab, GSFC Bldg-11 (ASIST)
- FSW Development Labe (including FlatSat), GSFC Bldg-1 (ASIST)
3)Launch Site Operations:
- All T&C systems from the I&T Control Center at GSFC will be relocated to Kennedy Space Center and Cape Canaveral Air Station (KSC/CCAS) to support launch site operations
4)Flight Operations:
- SDO MOC, GSFC Bldg-14 (ASIST)
- AIA SOC, LMSAL (HMI/AIA T&C System)
- HMI SOC, LMSAL (HMI/AIA T&C System)
- EVE SOC, LASP (OASIS-CC)
- SDO "Mini-MOC", White Sands Complex (WSC) (ASIST)
- AIA T&C System, GSFC MOC Science Operations Support (SOS) room (HMI/AIA T&C System)
- HMI T&C System, GSFC MOC SOS (HMI/AIA T&C System)
- EVE T&C System, GSFC MOC SOS (OASIS-CC)
- FSW Maintenance Lab (including FlatSat), GSFC Bldg-1 (ASIST)
Note: each SOC includes SSIM (ASIST)
2.2Project Database Development
The Project Database will evolve starting initially at the component level in the FSW and hardware development labs, through observatory-level tests, then maturing to its final form to support Flight Operations.
When a spacecraft hardware or software component is delivered for observatory integration, its associated database and procedures are also delivered and added to the master Project Database. As the spacecraft evolves, so does the Project Database. Similarly, as instruments and their GSE are brought to GSFC, their associated T&C systems that include their database and procedures will accompany them. The instrument T&C system and supporting GSE are maintained independent from the Observatory T&C system. However, for critical commanding and health and safety purposes, some subset of the instrument command and telemetry database is required to be incorporated and maintained within the ASIST T&C system. Specific identification of the instrument T&C database subset is coordinated between the Project Database Administrator (DBA) and each instrument’s on-site GSFC Instrument Manager. Since the database and procedures are constantly being developed, updated and/or are running on numerous workstations in numerous locations for both the spacecraft and instruments, careful database coordination is crucial.
Configuration control of the database at the various site locations is defined and managed by the Product Development Leads (PDLs) or their designate. Database configuration in a lab or facility would be consistent with the function of the lab or facility, the integration level of the component or observatory, and the mission phase. Project Database CM is discussed in Section 8 of this document.
1
March 23, 2006
464-GS-PLAN-0042
Revision A
3.0ASIST RDL Guidelines
Observatory telemetry and ground support equipment status information are received by the ASIST system as CCSDS packets encapsulated into Standard Formatted Data Units (SFDU’s). These packets are processed to produce useful information utilizing the telemetry packet definitions in the Project Database. The detailed composition of a telemetry packet is defined in ASIST using RDL, a database structure language. A unique Application ID (APID) defines each packet. The packet definition contains all the information necessary for the dissemination of the packet into individual telemetry parameters and conversion into useable information.