1 / 23

SE Core Database Development Process

SE Core Database Development Process. ITEC 2011. Mark Johnson mark.doyle.johnson@us.army.mil Strong Point Research Supporting PEOSTRI – SE Core Orlando, FL US A. Authors. Connie Perry PEO STRI, PM CONSIM connie.perry@us.army.mil Dolores Lowe PEO STRI, PM CONSIM

vanna
Télécharger la présentation

SE Core Database Development Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SE Core Database Development Process ITEC 2011 Mark Johnson mark.doyle.johnson@us.army.mil Strong Point Research Supporting PEOSTRI – SE Core Orlando, FL USA

  2. Authors Connie Perry PEO STRI, PM CONSIM connie.perry@us.army.mil Dolores Lowe PEO STRI, PM CONSIM Strong Point Research dolores.g.lowe@us.army.mil Robert Cox PEO STRI, PM CONSIM rob.m.cox@us.army.mil Mark Johnson PEO STRI, PM CONSIM Strong Point Research mark.doyle.johnson@us.army.mil Guillermo Flores PEO STRI, PM CONSIM memo.flores@us.army.mil

  3. SE Core Vision One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment.

  4. CONSIM Strategic Priorities AVCATT Manned Module Virtual Systems SE CORE Integration Embedded OneSAF Entity CCTT Manned Module Unified Constructive Architecture “Supporting the Warfighter” Army Integrated Training Environment

  5. Challenges SE Core is Solving • Multiple types of terrain source data required to support training enterprise • Terrain Database requirements for LVC Simulations varied & complex • Source data provided is uncorrelated • Correlation of source data is labor intensive • SE Core has a process established to minimize correlation issues • Use of approved standards for terrain data • SE Core is standards based (ISO 191xx and ISO/IEC 180xx) • SE Core uses industry standards (Shape Files, OpenFlight, etc) • Most simulations utilize an application specific runtime database compiled and optimized for the target simulation • SE Core provides not only industry standard formats, but runtime formats, too • SE Core has developed interoperable databases between AVCATT and CCTT • SE Core supports legacy IGs

  6. Challenges SE Core is Solving • High Resolution Mission Rehearsal Terrain DBs with geo-specific structures and vegetation still require months to create • SE Core has developed a process that reduces the time to create terrain databases • SE Core has created a model library that is over 500 common moving models • Lack of web-based repositories for users to share and re-use existing terrain databases • SE Core is working with AMSO to share our products through their web resources • SE Core is working with the USAF and Navy to exchange our data in common formats • SE Core is entering into exchange agreements with Coalition Allies

  7. SE Core Strategy • Effective solutions to terrain problems are complex and sometimes costly • SE Core is a funded POR • Leveraging industry solutions (market for capability) • Leverage Service investments by entering into data sharing agreements • Have establish requirements pedigree from TRADOC Capabilities Manager – Virtual (TCM-V) • SE Core requirements set by out TCM-V • TCM-V socialize with stakeholders • Includes all requirements for LVC • TCM-V is proponent and has established a solid resourcing stream • New SE Core contract in source selection

  8. SE Core Strategy (Continued) • Further resources coming as others embrace SE Core • Programs • Industry • Services • Be able to ingest data from in all common formats • DTED, CIB, OpenFlight, IFSAR,VMAP, Buckeye, etc • SE Core has a list of over 160 data products from a variety of data providers that are available for each database

  9. SE Core Architecture Overview

  10. SE Core Data Formats

  11. Database Request Process

  12. SE Core Tools Lots of tools in use today. Will share GPR tools. Conductor QA Toolbar VAZER Go Tos Google Earth Sync Tool Create Buffers Buffered Linears MADV ESRI Conductor (in VAZER) MDB Exporter EDM ArcMap Plugin AOO Tool DVED Attribution Helpers Plugin Adaptive Build Fixer ArcSDE Sync MDB Importer CADRG Tool (Generator) CM2 FID SMC Tool CM2 CCDS Tool Reskeletor MDB Tools CM2 IR Poly Tool MDB Admin Tool Multigen Creator CM2 View Skeletor PVD Plug-in EDM Editor Metadata Tool EDM Tools ERDAS Validator Grid Ascii Plug-in Production Viewer The Attributor AutoDoc Plug-in Openflight Plug-in Environment Manager Plug-in Radio Plug-in Shapefile Plug-in Defect KML Generator Photoshop Terra Vista Validation Plug-in SEDRIS Plug-in GDB (AutoMap) Plug-in Supervisor Light Control XML Plug-in EPX Plug-in CCDS Control Interface CTDB Plug-in On-demand Feature Integration Plug-in MDB Tools Terra Vista Plug-in DTED Plug-in Embankment Plug in EPX<-> Shape Converter CIB Plug-in Deterministic Scatter Plug-in Task List 12

  13. SE Core Tools From the toolbox we produce products used by various organizations Terrain Models Plug-ins Industry Partners 13

  14. SE Core Can Share Geo-Spatial Contentat Various Levels of Fidelity 3D Scene Data: Existing MDB Database  Full MDB Geometry processing to Standard Format 3D Scene Data: New MDB Database  Full MDB Geometry processing to Standard Format Source Data: Existing MDB Database extraction to Standard Format Complex Production: Confederate Capability Analysis, Database Integration Simple Data: Existing Database Documentation Current support and future user trend is growing 14

  15. Successes of SE Core Databases SE Core has produced databases covering a larger area than those current CCTT terrain databases.

  16. Cost Effectiveness of SE Core Databases SE Core databases produced at significant savings over legacy efforts (Normalized to a 100km x 100km area. ) 16

  17. SE Core Map Products JOG-A Map Sample SE Core DVED

  18. Common Moving Models • A participant and technology contributor to common sensor model capabilities for the U.S. Army • Skilled in development and use of models for simulated sensor systems including infrared, RADAR, SONOR, and night vision • Over 450 models produced, CAE led the SE Core CM2 architecture development • Worked collaboratively to define and refine the CM2 modification and production processes supporting SE Core - programs such as CCTT, AVCATT, CDT, GCTT

  19. SE Core Terrain Database Production Plan Future Terrain Database Production Order Ft Hood** Korea* Ft Campbell** FT Drum* FT Stewart** Ft Riley** Ft Carson** Ft Lewis/ Yakima* Ft Bragg* Germany* Ft Polk/ JRTC Ft Knox Ft Benning # Ft Bliss (BCT Mod)

  20. Path Forward • Outward Focus • Sharing Data • Increased Fidelity • Increased capability to use of Imagery • International distribution • Compatibility with legacy systems • Inward Focus • Source data ingestion into the MDB • More automation in TDB development • Communication with programs

  21. How to Get SE Core Products • Products • Databases • Common Moving Models (CM2) • Processed Data • Software • Distribution Agreement/Database Request Mr. Leonard Hobbs, Deputy APM e-mail: leonard.hobbs@us.army.mil Phone: 407-382-5553

  22. Don’t Be Left Out in the Cold

More Related