RIEDP PDG Telecon10 – 21 May 2015 Summary of RIEDP DM Foundations Document informal Review Référence – Date : E2Cxxxx du 10-03-2013 RIEDP-PDG - Telecon9.

Présentation au sujet: "RIEDP PDG Telecon10 – 21 May 2015 Summary of RIEDP DM Foundations Document informal Review Référence – Date : E2Cxxxx du 10-03-2013 RIEDP-PDG - Telecon9."— Transcription de la présentation:

1 RIEDP PDG Telecon10 – 21 May 2015 Summary of RIEDP DM Foundations Document informal Review Référence – Date : E2Cxxxx du 10-03-2013 RIEDP-PDG - Telecon9

2 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.  Introduction  Members and Quorum  Summary of Previous Meeting(s)  Approval of Telecon 9 notes  Technical Exchange Meeting with SE Core  Technical Work  Summary of Main Results, Motions, …  Review of Lance’s Glossary  Status of the Review of RIEDP DM Foundations Document  RADM  AOB  Conclusion Agenda RIEDP-PDG - Telecon9 1

3 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Web connection information  Thursday, 21 May 2015  5 PM France, 4 PM UK, 11 AM ET, 8 AM PT (change)  https://join.me/853-386-692 https://join.me/853-386-692  Tel  Germany: +49.69.3329.6380  France: +33.1 82 88 35 90  Netherlands: +31.20.262.0571  United Kingdom: +44.33.0088.2634  United States: +1.860.970.0010  Connection code: 853-386-692#  Phone numbers for other countries are also available  https://join.me/intphone/781337013/0 https://join.me/intphone/781337013/0 Introduction Web connection information RIEDP-PDG - Telecon9 2

4 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. DG principles Check Consistency Find PDG Consensus Approve within PDG Towards Balloting - Reference Doc - Copyrights Define for Doc1 & 2 : - Doc Headlines - Sections principles - Guidances - Wording by DGM - Cross Reviews - Wording by DGM - Cross Reviews Identify Use Draft Doc1 Draft Doc2 Recommandations V0 Doc1 & 2 for PDG approval V1 Doc1 & 2 for balloting § allocation § wording - Flesh out Doc 1 - Find DGM consensus - Align with Doc 2 - Flesh out Doc 2 - Find DGM consensus - Align with Doc 1 § allocation § wording Doc 1 = RIEDP Data Model Foundations (RPM+RADM) Doc 2 = RIEDP Detailled Features Description 3

5 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Introduction DG2 members - Attendance - Quorum RIEDP-PDG - Telecon9 4 NomPrénomOrganismeSISO StatusDG2AttendingVoting BAILEYGrant UK MoD Current SISO Member Yes CASTANERGilbert SOGITEC Current SISO Member Yes COGMANJack DATASIM Current SISO Member Yes COXRob PEO STRI / RDG YesNo ENOCHIANDavid USAF Not a SISO Member YesNo FAULKMark LEIDOS unclearNo FOLEYPaul DOD Terrain MSEA NGA Current MemberYes HOPKINSONBill MSCO unclearNo HUMPHRIESRoland XPI Simulation Expired Membership 2014 YesNo IGARZAJean-Louis Antycip Simulation France Current SISO Member Yes MACCHIWarren ABAMIS YesNo MAMAGHANIFarid Self Expired Membership 2013 YesNo MARROULance LEIDOS Current SISO Member Yes MOORERonald LEIDOS Expired in 2014YesNo PEELEGreg ARA Expired in 2014YesNo REIFAndreas BwB Current SISO Member Yes ROBBINSBruce US Army/PEO STRI/OneSAF Expired in 2012YesNo SCRUDDERRoy Univ Texas Current SISO Member Yes SIEGFRIEDRobert ADITERNA Current SISO Member Yes TABOURETYann TT&S Current SISO Member Yes GOUGEATJean-Louis SOGITEC Current SISO Member PDG ChairNo

6 Summary of Previous Telecons RIEDP-PDG - Telecon9

7 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Current status Summary of past meetings Previous DG2 Meetings  Telecon9 04/05/2015  Approval of Notes Additional Meeting  Technical Exchange Meeting with SE Core  Discussions still on-going All Notes posted on RIEDP Library RIEDP-PDG - Telecon9 XL Notes 6

8 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Main results  Scope of RIEDP :  Initially Aircrew COI + future extensions  Guidance vs Specification – Shall or Should :  Judicious and Appropriate use of Shall and Should is allowed by SISO in a Guidance  Data may be available from all stages  RIEDP complaint Data Exchange reserved for stages 2 through 7/8  Data from Source and Runtime stages for cataloging only  Storage vs Exchange  RIEDP cares about Data Exchange, not users’ internal format storage  RIEDP Conformance formats :  Restricted list of agreed formats with specific requirements  Any additional formats shall conform to explicitly defined requirements (to be specified) Summary of Main Results, Motions … RIEDP-PDG - Telecon9 7

9 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Motions Main results and Motions from Telecon 8 RIEDP-PDG - Telecon9 MotionsMeetingResult Object Motion 1Telecon8OK Guidance document’s specified formats apply only to external data exchange, not to internal storage Motion 2Telecon8OK To comply with RIEDP data exchange (at output of any of the stages), the data provider should be compliant with a specific list of RIEDP identified formats (TBD formats). If other formats are to be used by the data provider for external data exchange, a specific set of requirements (TBD) for those additional formats shall be followed/abided Motion2 Reworded Telecon9 If other formats are to be used by the data provider for RIEDP data exchange, these formats shall comply with a specific set of requirements (TBD) 8

10 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.  SE Core uses OpenFlight and FilmBox for internal storage and external data sharing.  SE Core evaluated COLLADA for model sharing, but determined that exporting to COLLADA was not worth the cost. OpenFlight supports a complex simulation- centric model hierarchy using defined organization nodes, whereas, COLLADA would require defining these organization nodes. Reading and writing to OpenFlight is supported by all of the Modeling and Simulation (M&S) applications used by SE Core, reading and writing to COLLADA would require developing extensions and plug-in to some of the SE Core M&S applications. COLLADA does provide a more flexible data organization, but would require developing a specification to facilitate consistent reading, writing and sharing. COLLADA is maintained by the Khronos Group, a member-funded industry consortium. OpenFlight is maintained by Presagis. SE Core uses Creator for 3D modeling. Creator is owned by Presagis.Khronos Group  Additionally, SE Core uses Maya and 3D Studio Max for 3D modeling. FilmBox, provides the most complete storage of these Maya and Max complex models, and is easily exported to OpenFlight.  To keep SE Core 3D model production as simple as possible, FilmBox and OpenFlight are used for internal storage, and for no-conversion sharing. SE Core Update OpenFlight – FilmBox - RIEDP-PDG - Telecon9 9

11 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.  Use of FilmBox size (FBX) is actually a practical choice and completely justified for the exchange of complex models between Maya and 3ds max, both published by Autodesk that owns the format in question.  My reluctance on the FBX are:  That the support for this format is conditioned to use the Autodesk SDK, and relies on the goodwill of a community of users to benefit from an unofficial format specification (http: // code.blender.org / 2013/08 / FBX-binary-file-format-specification /). The open source SDK is an individual initiative whose sustainability is uncertain at best.blender.org  That this poses problems of distribution of our own SDK, which can only include the FBX SDK.  That this SDK imposes de facto technological guidance in terms of language and type of information exchanged.  We use the FBX rather as a graphic interchange format, not as an exchange format simulation data. Yann Update TT&S Use of FBX RIEDP-PDG - Telecon9 10

12 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.  My arguments for the COLLADA  Supported by a strong and representative consortium, which remains agnostic. It does not promote a software publisher using COLLADA.  With Open Flight or FBX, a blank check is made to a Canadian publisher or American publisher respectively, relying on these publishers to make technological developments available.  Supported also by Autodesk through the same plugin as for FBX for Maya and 3DS Max.  The format is designed to be easily extensible. The corollary is that extensions for exchange must be agreed upon in the community.  Relies on XML, so from a technical point of view, is easily assimilated.  Already extended by Thales to support simulation specific features (georeferencing, LOD DOF, switch, characterization, IR / NVG data, materials animations....) and we have a SDK. This is our exchange format for data simulation environment. They have also been exploited by third parties.  I hope these elements will help develop the solution to a set of recommendations whose spirit is to facilitate the exchange limiting the constraints of use of specific Tools. Yann Update COLLADA vs FBX and OpenFlight RIEDP-PDG - Telecon9 11

13 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Comments from Telecon participants  Identified Reviewers  Warren MacchiTelecon6  Jack CogmanTelecon6  Roy21 April  Lance23 April  Paul Foley24 April  Yann Tabouret27 April  Greg Enochian27 April  Andreas Reif19 May  Ron?  David Graham?  NAVAIR ? Informal Reviews of RIEDP DM Foundations RIEDP-PDG - Telecon9 Doc as posted Doc as posted Roy+ WM+ JC Roy+ WM+ JC Lance Yann (commented) Yann (commented) 12 All Comments All Comments

14 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Editorial  Warren, Jack, Roy, Paul, Lance  intro, Titles depth, inconsistency Diagr vs text, position of RPM detailed view, General  Warren, Roy, Paul, Lance  Shall vs Should ; Guidance vs Specification ; Conformance  Roy, Lance  Scope of RIEDP (> Air) ; Scope of RPM (incl. Runtime? incl Specialized? )  Paul  Production vs generation ; Database vs representation  Lance  Targeted audience / Level of detail for explanations / Ref to 2 nd product;  Andreas  Guidance + shall and should is OK Technical  Next slide Review of comments and contributions RIEDP-PDG - Telecon9 Preview of latest RADM Preview of latest RADM 13

15 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Technical  Warren  Which Library ; Gaming area ;  Roy  Library (Shared or not); Catalog (one vs multiple); RIEDP Formats;  Additional Data to be aligned; Intensification vs Additional Data;  Same formats in all stages; RIEDP Profile; dataset and database;  changes to RADM; Data product; TINs excluded  Lance  RIEDP Formats / Internal vs export formats; Additional Data & Base line;  List of input formats, Ref to EDS; 3D moving models not in scope ;  Sub tasks in parallel or not; Restrictive Attribute dictionary,  Intensification; feature mapping,  procedural generation; RTP - run from source systems  Yann  OpenFlight vs Collada  Feature coding  Additional data after Align data – Additional data in intensification stage  Exchange of data vs Exchange of Algorithm (Off line and On line)  (Additional comments to be explained) Review of comments and contributions RIEDP-PDG - Telecon9 14

16 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Technical (Cont)  Andreas  Suggestion of a short list with appropriate formats.  Civil standards: GML3, CityGML + UtilityNetworkADE, IFC, ArcGis  Simulation standards: SEDRIS, Open Flight, Terra Page, p3d (VBS)  A further topic:weather-data in the simulation.  If you consider environment-data in the simulation thus you have to consider terrain-data and weather- data as well. Regarding to the Reference Abstract Model (always shown on the last page of the reflector) should we insert a new column "weather" additional to Elevation, Terrain Imagery and Feature Instances? Review of comments and contributions RIEDP-PDG - Telecon9 15

17 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Conclude Review of RPM comments Glossary of terms provided by Lance Preview of ongoing work on RADM Further discussion topics RIEDP-PDG - Telecon9 Preview of latest RADM Document (§ 4.3) Preview of latest RADM Document (§ 4.3) 16 RADM Visio Document RADM Visio Document

18 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. RPM with Import/Export Stage RIEDP-PDG - Telecon9 17

19 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Initiated by Lance Reviewed by Core Team  (Cleaned, Added … to be Aligned before Intensification !!) Review of Lance’s Glossary RIEDP-PDG - Telecon9 18 Glossary

20 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. RADM RIEDP-PDG - Telecon9 19

21 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Datasharing View RIEDP-PDG - Telecon9 20

22 RIEDP Detailed Features Description RIEDP-PDG - Telecon9

23 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. RIEDP Detailed Features Description Approach  During Telecon2, it was agreed that it was currently difficult to go into high detail on DG3 (Attribution subject) before the RADM is sufficiently stabilized.  However, preliminary discussion was held during Telecon3 to analyze possible approaches.  Core Team work current results :  DG3 has now an impact on DG2  Attribution RIEDP-PDG - Telecon9 22

24 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. RIEDP Detailed Features Description Approach Process  Assess available Dictionaries and select the most suitable as the RIEDP reference dictionary  Check what is available and what is missing in these dictionnaries  Identify required extensions or additions to the dictionary  Identify the required collection of Features (classes) and Attributes needed for RIEDP  Define what is mandatory and what is optional  Define how this collection can be described with the reference dictionary  Identify mappings between RIEDP Attributions and those used by the initiatives/users  This process will be incremental (for initialization and as for updates), it is important to define a flexible way of characterizing the underlying “Data model” of the attribution Features and Attributes. RIEDP-PDG - Telecon9 23

25 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. RIEDP Detailed Features Description Next step Initialization of the RIEDP DFD  Based on  ???  Who ?  DG 3  Volunteers ?  Schedule  End of 2014  Status during IITSEC RIEDP-PDG - Telecon9 24

26 Next Events RIEDP-PDG - Telecon9

27 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Next Events Telecon 11  To be held during Week ?Date to be agreed Target for Foundations document finalization RIEDP-PDG - Telecon9 26

28 Action Items RIEDP-PDG - Telecon9

29 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Action Items Attendance RIEDP-PDG - Telecon9 28

30 AOB RIEDP-PDG - Telecon9

31 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. AOB ?? RIEDP-PDG - Telecon9 30

32 Conclusion RIEDP-PDG - Telecon9

33 Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data. Conclusion During Session RIEDP-PDG - Telecon9 32

34 Backup RIEDP-PDG - Telecon9