170 likes | 181 Views
Environmental Data Cube Support System (EDCSS) METOC Support to NCTE/FST. Steve Lowe (AER) Steve.Lowe@aer.com Mark Horn (AgileSrc) Mark.Horn@agilesrc.com Mark Webb (ASNE) stephen.webb.ctr@jfcom.mil. Environment Representation in M&S. DoD Modeling & Simulation (M&S)
E N D
Environmental Data Cube Support System (EDCSS)METOC Support to NCTE/FST Steve Lowe (AER) Steve.Lowe@aer.com Mark Horn (AgileSrc) Mark.Horn@agilesrc.com Mark Webb (ASNE) stephen.webb.ctr@jfcom.mil
Environment Representation in M&S • DoD Modeling & Simulation (M&S) • Environment Representation defined as key success criteria • Support focused on Training, Acquisition, Analysis, and T&E • Training: Joint (JNTC), AF (DMO), Navy (FST), Army (FCS) • M&S Executive Agents • Air and Space Natural Environment (ASNE) - USAF/A30-W • Ocean – USN/CNMOC • Terrain – NGA • Technology Development • M&S CO (former DMSO) funded through MSEA endorsement • Emphasis on critical enabling technology (standards-based) • In general everything you see here is DoD owned • DATA and MODEL resources separated from technology
Space Atmos Ocean Terrain Environmental Data Cube Support System (EDCSS) National Repositories • DoD Ops/R&D Centers • NOAA Data Centers • Other Domain CoE Project Definition Scenario Search Simulation Integrated Environment Representation Production White Cell or Analyst Product Generation Distribution COP (C4ISR) Integration
Environmental Scenario Generator https://esg.afccc.af.mil
Project When Where Who Products Spatial Resolution/Projection Available Increments Effects Generation Service IR Hypercube Text METAR Image TAF Weather Graphics Synthetic Satellite EDCSS Requirements Data Model * Components JCATS AWSIM White Cell JET JSAF * Data OASES GRIB JLVC CSV
Consistent Integrated Representation EDCSS EDCSS Correlated Products FTUS80 KWBC 110300 RKJK TAF 110303 04006KT 9999 SKC QNH3005INS BECMG 1107/1109 35007KT 9999 SKC QNH2988INS BECMG 1113/1115 09010KT 9999 SKC QNH2991INS BECMG 1119/1121 04009KT 9999 SKC QNH2986INS BECMG 1201/1203 03011G25KT 9999 SCT270 QNH2969INS BECMG 1207/1209 33017G37KT 9999 SKC QNH2967INS METAR RCMQ 110300Z 31016KT 10SM BKN140 30/25 Q0970
The Details “ScenarioSearch” AF Atmos EDCSS Production Site Synthetic Satellite Navy Atmos JMB Data Standards Data Hypercube Effects COSINE Product Generation Imagery Navy Ocean Graphics (KML) Messages METAR/TAF http req/res System Impacts Ad- Hoc Sources Mineable Databases EDCSS Distributor Product-Based Web Services HTML Event Support Site • Atmos • Ocean • Space • Space Weather • Terrain Data • JIT Modeling http req/res EDCSS Runtime Integration Module (RIM) Local Product Cache Data Cache EDC Dist. Client EDC RIM API Data Files Simulation / C4I Application JMB = Joint METOC Board COSINE = Common Open Services for Integrated Natural Environment
EDCSS – JBUS Integration EDCSS Distributor Product-Based Web Services HTML Event Support Site EDCSS Runtime Integration Module (RIM) Managing dynamic population of local caches. http req/res Local Product Cache EDC Data Cache EDC RIM API EDC Dist. Client Local Cron 2 JBUS EDC Plug-in EDC to CDD Mapping 3 1 Time Plug-in CDD CDD to METOC BOM 4 NCTE-Wx HLA
CNMOC FY-09 Funded Tasking • CNMOC Database Integration • Add EDCSS support for WaveWatchIII, NCOM, and COAMPS • One region (SEUS), Five years, Four months per year • Convert to mineable databases to enable ESG searches • Add EDCSS/JBUS support for GDEM Climatology files • EDCSS Support Products • Synthetic BT messages from NCOM archives • Simulated Satellite/Radar imagery from COAMPS • Basic Forecast Graphics (PNG/KML) for ocean domain • FST Event Support • Deploy EDCSS Distributor to DCTL (Meet IA requirements!) • Ensure integration with JBUS and NITES • Technical support throughout event cycle
Motivation for Generalized CDD Model • Separation of JBUS CDD from METOC BOM • Inheritance (used in METOC BOM) not supported in CDD • Thematic classes defined in METOC BOM specific to NCTE • Specific content definitions tied to specific dimensions • prefer generality in CDD • Separation allows for support of other METOC BOM’s • Backward compatibility allows for progress! • JBUS CDD METOC Definition • Generalized 2D Spatial structure (grid or points) • “0D” supported by single-point spatial extent • “3D” is a collection of 2D grids with common vertical axis • Can support 2D spatial construct as a set of irregular points • Support for multiple projections and scan modes • Includes concept of a time stamp on any environment object • Leverages current SEDRIS EDCS terminology (V4.1) • Can define broad list of parameters and levels so that CDD remains static
METOC BOM Classes vs Data Type Climate “Live” or Historic • Open_Ocean_Observer • Surface Temp/Salinity • U, V Currents • Sea State • Primary Hgt, Per, Dirn • Wind Wave Hgt, Per, Dirn • Swell Hgt, Per, Dirn • Ocn_Surface_Layer_GDC • Surface Temp/Salinity • U, V Currents • Tide Level • Acoustic Boundary Loss • Ocn_Wave_Spectrum_GDC • Sea State • Primary Hgt, Per, Dirn • Wind Wave Hgt, Per, Dirn • Swell Hgt, Per, Dirn VS. +
App App App Environment Support Concept Model Obs climate Historical Record “NOW” T+/-3hrs synoptic mesoscale micro- scale Analysis Scenarios vs. “Climo” Ground Truth Forecasts Consistent Integrated Representation 4D Cube Tactical Decision Aids &/or Simulations
Questions / Recommendations • Is the separation of Climo from Live/Historical a good idea? • Was it driven by available data sources? (OAML vs FNMOC vs MEL) • Making Federates have to know which objects to subscribe to based on what source data is being played seems like too much burden on the consumer. • Is Time important? If so, what time? • “Observers” are only objects that include any time reference • Historical/Ephemeris time included in data model, but not in specific classes • Recommendations: • Focus METOC BOM data model on content organization rather than type of source data. Federates subscribe to content they require, period. • A reference time stamp associated with each domain of the environment could be useful to the federates, but historical time reference is not.
Summary • EDCSS offers technology for METOC support in NCTE • One framework for Climo, Historical, Live • Excels with relevant analysis/training scenarios • One framework for Simulation, White Cell, and C4I domains • Data Source agnostic (but not magic) • EDCSS JBUS Plug-in nearly complete • Tied to EDCSS Distributor, makes NCTE integration seamless • Replaces aging OASES technology with no impact to Federates • Generalized CDD METOC model will support multiple BOM’s • Federate Developers – provide feedback on METOC • Report on how you use METOC internally (independent of BOM) • Report on what you consume from the BOM (now or planned) • …and any “transforming” you do before using it