# Presentation: 355073

## Subsystems and CSCIs:  DMS

**Data Management Subsystem (DMS)**
**Provides catalog interoperability between ECS and the V0 Information Management System (IMS) and between DAACs**
**Supplies gateway processes and information managers that forward requests from users to storage locations**
**Maintains a Data Dictionary that stores data collection information (i.e., collection metadata, attributes, valid keywords)**
**Data Dictionary contains collection attribute and keyword mappings between ECS and V0 to permit translation of requests**
**Uses several COTS tools:  RogueWave class libraries, Builder Xcessory (GUI builder tool), Sybase SQL Server (for Data Dictionary database search and update), Sybase Replication Server (for cross-DAAC distribution and consistency in Data Dictionary database information) **

## Subsystems and CSCIs:  DMS (Cont.)

**Data Dictionary (DDICT) CSCI**
**Manages definitions of data collections (including metadata, attributes, domains, and data locations)**
**Stored in a relational Database Management System (DBMS)**
**Four major components**
**Data Dictionary Server**** - provides DDICT client processes the ability to perform data searches, inserts, updates, or deletes to the DDICT database**
**Data Dictionary Maintenance Tool**** - provides a GUI to insert, update, or delete schema information held in the DDICT database, and allows operations staff to modify database attributes (e.g., valids, mapping)**
**Data Dictionary SQL Server**** - COTS database server**
**Data Dictionary Replication Server**** - COTS server at GSFC for consistent replication of DDICT across DAACs**

## Subsystems and CSCIs:  DMS (Cont.)DDICT Architecture and Interfaces

**Subsystems and CSCIs:  DMS (Cont.)****DDICT Architecture and Interfaces**

## Subsystems and CSCIs:  DMS (Cont.)

**Local Information Manager (LIMGR) CSCI**
**Provides access to data and services at a site**
**Accepts requests (e.g., search) and produces and executes the corresponding requests required for the data servers for the site**
**receives inventory search, browse, and acquire requests, matches them to data types identified in DDICT, and directs them to the appropriate server within a DAAC**

## Subsystems and CSCIs:  DMS (Cont.)LIMGR Architecture and Interfaces

**Subsystems and CSCIs:  DMS (Cont.)****LIMGR Architecture and Interfaces**

## Subsystems and CSCIs:  DMS (Cont.)

**Version Zero Gateway (V0 GTWY) CSCI**
**Provides access to data and services between the ECS Data Server and V0 IMS**
**Two components**
**V0 to ECS Gateway Server**** - allows use of the EOS Data Gateway Web Client to search and request data and services defined within ECS**
**ECS to V0 Gateway Server**** - allows transmission of Landsat 7 product requests to DORRAN billing and accounting system**

## Subsystems and CSCIs:  DMS (Cont.)V0 GTWY Architecture and Interfaces

**Subsystems and CSCIs:  DMS (Cont.)****V0 GTWY Architecture and Interfaces**

## Subsystems and CSCIs:  DMS (Cont.)

**Subsystems and CSCIs:  DMS (Cont.)**

## Subsystems and CSCIs:  IOS

**Interoperability Subsystem (IOS)**
**Maintains directories of Universal References**
**Maintains directories of ECS services**
**Uses several COTS tools:  RogueWave class libraries, Sybase SQL Server (for Advertising Service database search and update), Sybase Replication Server (for cross-DAAC distribution and consistency in Advertising database information)**

## Subsystems and CSCIs:  IOS (Cont.)

**Advertising Service (ADSRV) CSCI**
**Manages Earth Science related advertisements**
**Advertising data stored in a relational Database Management System (DBMS)**
**Consists of one major component**
**Advertising Server:  a background process that interacts with the DBMS for searching, inserting, and updating advertisements**

## Subsystems and CSCIs:  IOS (Cont.)

**Advertising Server Component**
**Three main processes**
**Advertising Server**** - provides clients with ability to search, insert, delete, and update advertisements**
**Advertising Service SQL Server**** - provides COTS relational database for the Advertising Service**
**Advertising Service Replication Server**** - COTS server at master site for consistent replication of ADSRV data across DAACs**

## Subsystems and CSCIs:  IOS (Cont.)ADSRV Architecture and Interfaces

**Subsystems and CSCIs:  IOS (Cont.)****ADSRV Architecture and Interfaces**

## Subsystems and CSCIs:  IOS (Cont.)

**Subsystems and CSCIs:  IOS (Cont.)**

## Subsystems and CSCIs:  PLS

**Planning Subsystem (PLS)**
**Allows operations staff to define data processing tasks to be performed at a site**
**Generates efficient plans for scheduling defined data processing tasks**
**Coordinates production with the Data Server and Data Processing subsystems to achieve a highly automated production system**
**Interfaces with the Algorithm Integration and Test Tools CSCI within DPS for information on Product Generation Executives (PGEs)**
**Permits entry of Production Requests and generates resulting Data Processing Requests (DPRs)**
**Uses a set of Raytheon-provided COTS libraries as a basis for its scheduling components (Resource Planning Workbench and Production Planning Workbench) **

## Subsystems and CSCIs:  PLS (Cont.)

**Production Planning (PLANG) CSCI**
**Seven major components**
**Data Store**** - handles insertion of data for planning and processing activities into the PDPS shared database**
**Resource Planning Workbench**** - GUIs for preparing a site resource schedule**
**Production Request Editor**** - GUI for submitting production requests that describe the data products to be produced; uses PGE descriptions to generate the DPRs necessary to meet the requests**
**Production Planning Workbench**** - GUIs for preparing a site production schedule**
**Planning Subscription Editor**** - command-line editor for manual submission of subscriptions to Data Server (backup for automatic submission by Production Request Editor)**
**Subscription Manager**** - server to manage receipt of subscription notifications from the Data Server**
**Production Strategies GUI**** - used to create a set of planning priorities to be applied to each DPR in a plan**

## Subsystems and CSCIs:  PLS (Cont.)PLANG Architecture and Interfaces

**Subsystems and CSCIs:  PLS (Cont.)****PLANG Architecture and Interfaces**

## Subsystems and CSCIs:  PLS (Cont.)

**Subsystems and CSCIs:  PLS (Cont.)**