Presentation on theme: "SE Core Database Development Process"— Presentation transcript:
1SE Core Database Development Process ITEC 2011Make Clear:My pleasure to present theSE 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 JohnsonStrong Point ResearchSupporting PEOSTRI – SE CoreOrlando, FL USA
2Authors Robert Cox Connie Perry PEO STRI, PM CONSIM Mark JohnsonStrong Point ResearchGuillermo FloresConnie PerryPEO STRI, PM CONSIMDolores LoweStrong Point ResearchOctober 2010
3SE Core VisionOne 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?”
4CONSIM Strategic Priorities Army Integrated Training EnvironmentCCTT Manned ModuleEmbedded OneSAF EntityAVCATT Manned ModuleVirtual SystemsSE CORE IntegrationSE 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 conductUnified Constructive Architecture“Supporting the Warfighter”
5Challenges SE Core is Solving Multiple types of terrain source data required to support training enterpriseTerrain Database requirements for LVC Simulations varied & complexSource data provided is uncorrelatedCorrelation of source data is labor intensiveSE Core has a process established to minimize correlation issuesUse of approved standards for terrain dataSE 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 simulationSE Core provides not only industry standard formats, but runtime formats, tooSE Core has developed interoperable databases between AVCATT and CCTTSE Core supports legacy IGsThese 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.
6Challenges SE Core is Solving High Resolution Mission Rehearsal Terrain DBs with geo-specific structures and vegetation still require months to createSE Core has developed a process that reduces the time to create terrain databasesSE Core has created a model library that is over 500 common moving modelsLack of web-based repositories for users to share and re-use existing terrain databasesSE Core is working with AMSO to share our products through their web resourcesSE Core is working with the USAF and Navy to exchange our data in common formatsSE Core is entering into exchange agreements with Coalition AlliesHigh 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.
7SE Core StrategyEffective solutions to terrain problems are complex and sometimes costlySE Core is a funded PORLeveraging industry solutions (market for capability)Leverage Service investments by entering into data sharing agreementsHave establish requirements pedigree from TRADOC Capabilities Manager – Virtual (TCM-V)SE Core requirements set by out TCM-VTCM-V socialize with stakeholdersIncludes all requirements for LVCTCM-V is proponent and has established a solid resourcing streamNew SE Core contract in source selectionThis 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.
8SE Core Strategy (Continued) Further resources coming as others embrace SE CoreProgramsIndustryServicesBe able to ingest data from in all common formatsDTED, CIB, OpenFlight, IFSAR,VMAP, Buckeye, etcSE Core has a list of over 160 data products from a variety of data providers that are available for each databaseAs 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, AGTSWe 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.
10SE Core Data FormatsProgram NeedsPlug-inSubsystem UsePlug-in StatusCCTTAVCATTLVC-IACFFTLCTGamingCOFT-SAStrykerEPX 50Image GeneratorPXOTFOneSAFCCTT PVDPlan View DisplayTIREMRadio CommunicationsCIBMission PlanningGeo DatabaseElectronic and Paper MapEnvironment ManagerN/ACADRG / Digital MapsElectronic Maps(FBCB2/PFPS)Contour LineShapeFileIndustry Standard FormatDTEDCTDBSAFOpenFlightTypically Image GenerationGRID ASCIISimilar to DTEDAuto DocDB Design DocSEDRISInterchange FormatSAGES2 FocusValidationQuality CheckFID ViewWorkingConstructiveSAF (OneSAF/WARSIM)ITEMSVBS2EP8000AAcuityFutureEP5000MMRSRadarVRSG XX-IGVital 9AechelonMedallionNote: 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 rightProgram used across the topStatus in the middle= complete and in useWorking = Someone has funded the effort and the development has beganFuture = Programs/people have expressed interest by no work is on deliveryWhat kills me, changes without notification (OneSAF)
11Database 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!
12SE Core Tools Lots of tools in use today. Will share GPR tools. ESRI QA ToolbarConductorVAZERGoogle Earth Sync ToolGo TosCreate BuffersMADVBuffered LinearsESRIConductor (in VAZER)MDB ExporterEDM ArcMap PluginAOO ToolDVED Attribution Helpers PluginAdaptive Build FixerArcSDE SyncCADRG Tool (Generator)MDB ImporterCM2 CCDS ToolCM2 FID SMC ToolReskeletorMultigen CreatorMDB Admin ToolCM2 IR Poly ToolMDB ToolsCM2 ViewSkeletorPVD Plug-inEDM EditorERDASEDM ToolsMetadata ToolValidatorGrid Ascii Plug-inProduction ViewerOur 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 AnalizerCADRG Tool GeneratorOpenFlight Plug-in*Shapefile Plug-in*DTED Plug-in ** THESE PRODUCE THE FORMATS USED BY SYSTEMSThe AttributorAutoDoc Plug-inEnvironment Manager Plug-inOpenflight Plug-inRadio Plug-inShapefile Plug-inTerra VistaDefect KML GeneratorPhotoshopValidation Plug-inSEDRIS Plug-inSupervisorGDB (AutoMap) Plug-inXML Plug-inLight ControlEPX Plug-inCCDS Control InterfaceCTDB Plug-inOn-demand Feature Integration Plug-inMDB Tools Terra Vista Plug-inDTED Plug-inEmbankment Plug inCIB Plug-inEPX<-> Shape ConverterDeterministic Scatter Plug-in12Task List
13SE Core ToolsFrom the toolbox we produce products used by various organizationsTerrainModelsFrom those created tools we support many organizations with Terrain, models, and Plug-ins.Plug-insIndustry Partners13
14SE Core Can Share Geo-Spatial Content at Various Levels of Fidelity 3D Scene Data: Existing MDB Database Full MDB Geometry processing to Standard Format3D Scene Data: New MDB Database Full MDB Geometry processing to Standard FormatSource Data: Existing MDB Database extraction to Standard FormatComplex Production: Confederate Capability Analysis, Database IntegrationSimple Data: Existing Database DocumentationNot all customer are equal. Some want a lot, some are happy with what you give them.Simple data / DocumentationRefined Source Data = Existing TDB in the MDB with exiting plug-in. Extraction of standard formatFull 3D geometry processingNew MDB content required. Must go through steps shown earlierComplete production: Interop with legacy systemCurrent support and future user trend is growing14
15Successes of SE Core Databases SE Core has produced databases covering a larger area than those current CCTT terrain databases.These show legacy and new TDBsYellow are TDB build by SE Core, but also a legacy TDB within CCTT. We are at least double the size of the TDBsPOINT OUT: Hood, Riley, and BlissAfgan East & Hawaii are Both New
16Cost 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 100kwx100kwNot only are we making TDBs large, but also saving $sNot only saving $ per program, but Xs the number of programs using the TDB16
17SE Core Map Products JOG-A Map Sample SE Core DVED Map Types Comments CIB1meter, 5meter, 10meter available (Controlled Image Base)JOG A1:250K (Joint Operations Graphic Aeronautical)TLM1001:100K (Topographic Line Map)TLM501:50K (Topographic Line Map)CADRGCompressed ARC Digitized Raster Format Distribution OptionMaps how exactly what is in the Simulation DatabaseJOG-A Map SampleSE Core DVED
18Common Moving ModelsOver 450 models produced, CAE led the SE Core CM2 architecture developmentWorked collaboratively to define and refine the CM2 modification and production processes supporting SE Core - programs such as CCTT, AVCATT, CDT, GCTTBlue Prints: BlissSMEsTCM-V Blesses these modelsDifferent levels of fidelityDetectIndelityRecognizeCM2 is a process to meet program requirementsA participant and technology contributor to common sensor model capabilities for the U.S. ArmySkilled in development and use of models for simulated sensor systems including infrared, RADAR, SONOR, and night vision
19SE Core Terrain Database Production Plan Future Terrain Database Production OrderFt Hood**Korea*Ft Campbell**FT Drum*FT Stewart**Ft Riley**Ft Carson**Ft Lewis/ Yakima*Ft Bragg*Germany*Ft Polk/ JRTCFt KnoxFt Benning #Ft Bliss (BCT Mod)Already collecting data on all these locations.Paul Dillman collects specific data. Nav aids jump towers checker board water towerHelps to level on what you are building.* LVC ITE** LVC ITE Update# Update (not LVCITE)
20Path Forward Outward Focus Sharing Data Increased Fidelity Increased capability to use of ImageryInternational distributionCompatibility with legacy systemsInward FocusSource data ingestion into the MDBMore automation in TDB developmentCommunication with programsGood Customers;Know what we needKnow what you produceHelp you help me!
21How to Get SE Core Products DatabasesCommon Moving Models (CM2)Processed DataSoftwareDistribution Agreement/Database RequestMr. Leonard Hobbs, Deputy APMPhone: