1. SE Core Database Development Process
ITEC 2011
Make Clear:
My pleasure to present the
SE Core is an Army Program of Record. SE core does not generate requirements TCM-V is SE Core’s Combat Developer and I receive my requirements from TCM-V.
Again, I am providing an Information Brief on SE Core, so you will know what we are doing.
We are from PEO STRI, and work in the PM ConSim organization.
Mark Johnson
Strong Point Research
Supporting PEOSTRI – SE Core
Orlando, FL USA

2. Authors Robert Cox Connie Perry PEO STRI, PM CONSIM
Mark Johnson
Strong Point Research
Guillermo Flores
Connie Perry
PEO STRI, PM CONSIM
Dolores Lowe
Strong Point Research
October 2010

3. SE Core Vision
One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment.
One fight involving multiple simulators, using one SAF, on a common terrain database, resulting in a fair fight environment.
One simulator cannot have an inherent advantage over an other simulator and the SAF cannot have an advantage either. Cannot be unrealistic.
Example – mismatch of ammunition capabilities, ranges not compatible with the weapon system, not being able to see through or fire through tree/buildings.
This moves us forward in the ability to train soldiers within and across domains.
SE Core is an enabler. The ITE cannot function without SE Core. That is why the program is so important. It is not just that SE Core will save the Army money, it is the enabling capability for training the soldiers.
SE Core is going to provide a persistent training capability. Programs will be able to conduct interoperable training on a persistent and repeatable basis.
Fort Benning to Fort Rucker, “ We are conducting a training exercise on Wednesday at 1500 using scenario XYZ (ver 1) on database 123 (ver 2). You want to play?”

4. CONSIM Strategic Priorities
Army Integrated Training Environment
CCTT Manned Module
Embedded OneSAF Entity
AVCATT Manned Module
Virtual Systems
SE CORE Integration
SE Core plays an important role in the ConsSim Strategic priorities as we move to the Integrated Training Environment. SE Core is a foundational element of the Integrating Architecture.
Moving around the ITE graphic on the left, SE Core is meeting the needs of CCTT and AVCATT in order to make those sims interoperable. Both are already using SE Core terrain and models. Both are actively integrating OneSAF.
SE Core provides terrain and models to many TADSS, both system and non-system TADSS, today. Programs such as the CFFT, CDT, COFT SA, and NCM3.
The Centers of Excellence play an important role with SE Core. SMEs from the CoEs provide the detailed requirements to SE Core needed to meet training requirements.
Training Areas are rendered in a higher fidelity than the rest of the TDB. This is the primary training areas used by the CCTT system. SE Core is working with HITS to adequately meet their needs to interact with the virtual systems.
SE Core pays close attention to ranges. CCTT and AVCATT both conduct
Unified Constructive Architecture
“Supporting the Warfighter”

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
These bullets should look familiar to many.
1 – There are multiple types of source data needed to meet the needs of the training environment.
2 – Source data is not correlated . This continues to be labor intensive. Automated tools has only gotten us so far.
3 – Standards are used by SE Core. We don’t want to develop a unique format that limits the use of our data.
4 – the legacy systems use specific runtime databases. These sims are our primary target; however, we wanted our architecture to be robust enough to reuse what we process for many different simulators and simulations. They legacy systems are the toughest for us. We cannot degrade the current training capability yet we can’t use latest technology. Getting legacy systems ready for interoperability is a challenge.
POINT IS SE Core IS MEETING THESE CHALLENGES.

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
High resolution for Army Mission Rehearsal takes time. Define Mission Rehearsal: The definition of Mission Rehearsal for us is not the same for others. We are providing Terrain for use in collective simulators. A Rehearsal of a river crossing is different than mission rehearsal for a small special tactics unit. Our rehearsal areas are generally larger than a point target, we have over 500 moving models, but also a very large library of static models, but spo specific and geo typical.
Sharing data through web-based repositories is a challenge . We are doing pretty well with sharing with hard drives. SE Core is sharing data with the Air Force and Navy.
Moving into these agreements to take advantage of what they are doing. Lots of allies use our contractors and we want the goodness.

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
This is a complex problem. The Army recognize d this and funded a program to tackle these challenges. SE Core is meeting the requirements of Legacy Systems, and expanding to newer systems.
SE Core is funded.
We want to use industry solutions, but we also want to drive industry to meet our requirements.
Two way street: We want to use other services, but we also want other services to use our products. But, we are learning how to be a good customer. We need to articulate what we need from other services.
SE Core has a well defined requirement set. SE Core is now working with our second approval requirement document. TCM-V is my requirements provider.
TCM-V gives SE Core the requirements.

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
As other programs see the goodness of SE Core ,they have come with resources. We always, like programs who come with resources.
Examples of programs coming to SE Core: CDT, CFFT, COFT SA, AGTS
We use a good bit of different formats.
I want to ingest data of all types rapidly. This is being a good customer to the data providers by telling them what we want from them.

9. SE Core Architecture Overview

10. SE Core Data Formats
Program Needs
Plug-in
Subsystem Use
Plug-in Status
CCTT
AVCATT
LVC-IA
CFFT
LCT
Gaming
COFT-SA
Stryker
EPX 50
Image Generator P X
OTF
OneSAF
CCTT PVD
Plan View Display
TIREM
Radio Communications
CIB
Mission Planning
Geo Database
Electronic and Paper Map
Environment Manager
N/A
CADRG / Digital Maps
Electronic Maps(FBCB2/PFPS)
Contour Line
ShapeFile
Industry Standard Format
DTED
CTDB
SAF
OpenFlight
Typically Image Generation
GRID ASCII
Similar to DTED
Auto Doc
DB Design Doc
SEDRIS
Interchange Format
SAGE
S2 Focus
Validation
Quality Check
FID View
Working
Constructive
SAF (OneSAF/WARSIM)
ITEMS
VBS2
EP8000
AAcuity
Future
EP5000
MMRS
Radar
VRSG  X
X-IG
Vital 9
Aechelon
Medallion
Note: the programs listed are a sample and for instance CACCTUS uses OTF and thus can be supported)
List of current output formats:
Format / plug-in down the right
Program used across the top
Status in the middle
= complete and in use
Working = Someone has funded the effort and the development has began
Future = Programs/people have expressed interest by no work is on delivery
What kills me, changes without notification (OneSAF)

11. Database Request Process
Database is determined to be needed, the extents, priority, zones, and unique requirements are defined.
Unique data such as navigational aids, new mobile mout sites (Ft Campbell)
This is captured in our DBRR and this documents becomes the “Job Packet” for the TDB. It is our agreement with TCM-V Confederates are consulted on this, but this is a TCM-V SE Core agreement.
The process on the previous slide. An important part.
TDB is provided for integration by the programs. We still help in this.
THIS PROCESS WORK TOO!

12. SE Core Tools Lots of tools in use today. Will share GPR tools. ESRI
QA Toolbar
Conductor
VAZER
Google Earth Sync Tool
Go Tos
Create Buffers
MADV
Buffered Linears
ESRI
Conductor (in VAZER)
MDB Exporter
EDM ArcMap Plugin
AOO Tool
DVED Attribution Helpers Plugin
Adaptive Build Fixer
ArcSDE Sync
CADRG Tool (Generator)
MDB Importer
CM2 CCDS Tool
CM2 FID SMC Tool
Reskeletor
Multigen Creator
MDB Admin Tool
CM2 IR Poly Tool
MDB Tools
CM2 View
Skeletor
PVD Plug-in
EDM Editor
ERDAS
EDM Tools
Metadata Tool
Validator
Grid Ascii Plug-in
Production Viewer
Our tool set is made up of the usual tools used by almost all of VSE.
Out of these tools we create many others tools.
POINT OUT:
VAZER Vector Analizer
CADRG Tool Generator
OpenFlight Plug-in*
Shapefile Plug-in*
DTED Plug-in *
* THESE PRODUCE THE FORMATS USED BY SYSTEMS
The Attributor
AutoDoc Plug-in
Environment Manager Plug-in
Openflight Plug-in
Radio Plug-in
Shapefile Plug-in
Terra Vista
Defect KML Generator
Photoshop
Validation Plug-in
SEDRIS Plug-in
Supervisor
GDB (AutoMap) Plug-in
XML Plug-in
Light Control
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
CIB Plug-in
EPX<-> Shape Converter
Deterministic Scatter Plug-in 12
Task List

13. SE Core Tools
From the toolbox we produce products used by various organizations
Terrain
Models
From those created tools we support many organizations with Terrain, models, and Plug-ins.
Plug-ins
Industry Partners 13

14. SE Core Can Share Geo-Spatial Content at 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
Not all customer are equal. Some want a lot, some are happy with what you give them.
Simple data / Documentation
Refined Source Data = Existing TDB in the MDB with exiting plug-in. Extraction of standard format
Full 3D geometry processing
New MDB content required. Must go through steps shown earlier
Complete production: Interop with legacy system
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.
These show legacy and new TDBs
Yellow are TDB build by SE Core, but also a legacy TDB within CCTT. We are at least double the size of the TDBs
POINT OUT: Hood, Riley, and Bliss
Afgan East & Hawaii are Both New

16. Cost Effectiveness of SE Core Databases
SE Core databases produced at significant savings over legacy efforts
(Normalized to a 100km x 100km area. )
The TDBs have been normalized to 100kwx100kw
Not only are we making TDBs large, but also saving $s
Not only saving $ per program, but Xs the number of programs using the TDB 16

17. SE Core Map Products JOG-A Map Sample SE Core DVED Map Types Comments
CIB
1meter, 5meter, 10meter available (Controlled Image Base)
JOG A
1:250K (Joint Operations Graphic Aeronautical)
TLM100
1:100K (Topographic Line Map)
TLM50
1:50K (Topographic Line Map)
CADRG
Compressed ARC Digitized Raster Format Distribution Option
Maps how exactly what is in the Simulation Database
JOG-A Map Sample
SE Core DVED

18. Common Moving Models
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
Blue Prints: Bliss
SMEs
TCM-V Blesses these models
Different levels of fidelity
Detect
Indelity
Recognize
CM2 is a process to meet program requirements
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

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)
Already collecting data on all these locations.
Paul Dillman collects specific data. Nav aids jump towers checker board water tower
Helps to level on what you are building.
* LVC ITE
** LVC ITE Update
# Update (not LVCITE)

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
Good Customers;
Know what we need
Know what you produce
Help you help me!

21. How to Get SE Core Products
Databases
Common Moving Models (CM2)
Processed Data
Software
Distribution Agreement/Database Request
Mr. Leonard Hobbs, Deputy APM
Phone:

22. Don’t Be Left Out in the Cold