BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//The REUSE Company//INCOSE IS 2026//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-LIC-LOCATION:Asia/Tokyo
BEGIN:STANDARD
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:incose-trc-semantic-interoperability-architecture-models-20260615@reuse
 company.com
DTSTAMP:20260609T163555Z
DTSTART;TZID=Asia/Tokyo:20260615T143000
DTEND;TZID=Asia/Tokyo:20260615T145500
SUMMARY:INCOSE - The REUSE Company Presentation: Semantic Interoperability 
 of Architecture Models: An experience in the A&D sector
LOCATION:Yokohama\, Japan
DESCRIPTION:With the progressive deployment of MBSE in the (aerospace) indu
 stry come new challenges\, already identified and stated in the INCOSE Vis
 ion and other places. Among them is the digital continuity between OEMs an
 d their suppliers\, and especially the interoperability for architecture m
 odels between a system supplier and its customers.\n\nEven if standards ex
 ist for models in terms of language (SysML V2 is a great example)\, the av
 ailable tools have different implementations and little native exchange ca
 pabilities on top of the basic language. In addition to that\, the compani
 es use their own tailored methods. The consequence is that most of the com
 panies suffer to collaborate between different methods\, languages and too
 ls.\n\nTo exchange architecture models today\, both parties need to define
  an exchange protocol\, encompassing the language\, the modeling method\, 
 and a common data exchange format or tool. SysML V2 will arrive to help wi
 th the language part of the problem (which is good news). However\, the la
 nguage has recently become official\, few proper tools for SysML V2 are ye
 t available in the market\, the SysML V2 API has not the proper semantic l
 evel\, and as will be exposed in the paper\, many high level (human\, not 
 language) semantic interoperability problems remain.\n\nThe first and seco
 nd parts of this paper will develop the challenges in all these aspects\, 
 from an industrial supplier perspective\, with different interoperability 
 scenarios.\n\nThe third part will describe the infrastructure layers set u
 p to allow interoperability as per the framework described in part two\, a
 nd the industrial solutions for each layer to make it real.\n\nFinally\, t
 he fourth part of the paper will demonstrate feasibility and results in a 
 practical use case on architecture models transformation. The scenario is 
 from a supplier framework with a specific tool and a Domain Specific Langu
 age to a customer framework\, with a different tool\, a different language
  and a different modeling methodology.\n\nAs a conclusion\, the paper demo
 nstrates the capability to interoperate architecture models from completel
 y different frameworks with the appropriate methodology and tool.
STATUS:CONFIRMED
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR