They\u2019ve researched\/monitor a number of system complexity metrics, like this one measuring system complexity based on software source lines of code (SLOC)<\/a>: <\/p>\n\n\n \u2026along with some interesting\ndescriptive quotes: <\/p>\n\n\n\n \u201cDevelopment effort, which increases exponentially with SLOC, is increasing at an alarming rate.For example, the F35 has approximately 175 times the number of SLOC as the F16. But, it is estimated to have required 300 times the development effort\u201d <\/p>\n<\/blockquote>\n\n\n\n \u2026which claim we reached the\nlimits of our existing serial processes. This means the classic way of building\naircraft: spec, integrate, and repeat is no longer affordable. So, what do we\ndo differently? <\/p>\n\n\n\n MBSE solutions produce the\nproduct architecture\/blueprints that drive today’s complex product development\nprocesses. Product architecture\u2019s purpose is to communicate what to do and how\nto do it to all disciplines to drive an integrated solution; or put another way\narchitecture needs to be integrated with the suppliers which are delivering\nmajor parts of the product. <\/p>\n\n\n\n For many years the lack of standard systems modeling language (like the software or electronics industry has) has hampered these efforts, but with the arrival of SysML v1<\/a>, we finally have a standard graphical language with which to communicate. The problem is that the language is so flexible it allows describing the same solution in many different ways along with the inability to isolate subsystems so OEM\u2019s can share subsystem content with suppliers without providing whole system model (i.e. IP problems). <\/p>\n\n\n\n Back in Jan. 2019, the Aerospace & Defense PLM Action Group<\/a> released a MBSE Data Interoperability problem statement & assessment<\/a> describing this supplier integration issue and requesting input from MBSE tool suppliers on how to address this SysML OEM-Supplier data exchange problem.They executed eight sample package exchanges with suppliers resulting in a successful digital exchange of less than 50% of the time with the ability to interpret the design intent less than 20% of the time.They concluded, \u201cit was not yet feasible to exchange MBSE system architecture & requirements with current tools\u201d\u2014i.e. the current standard language and exchange mechanisms cannot support the start integrated, stay integrated paradigm change. <\/p>\n\n\n\n Luckily, this issue along with other shortcomings have been recognized and is being addressed by the next generation SysML language\u2014SysML v2<\/a>.SysML v2 recognizes the role of Product Lifecycle Management (PLM) and the necessity of integrating system architecture with PLM for this type of supplier collaboration.<\/p>\n\n\n\n Siemens is not only participating on SysML v2 standard development teams but also actively working with existing SysML tool suppliers to integrate product architecture with the product lifecycle (which already does the job of supplier integration\/data exchange for other disciplines)<\/p>\n\n\n\n Back in 2018, we announced a partnership\/integration with Obeo\u2019s open source Capella solution<\/a> which includes an integrated ISO15288 standard process methodology ARCADIA to enable this supply chain collaboration.We have since launched a Teamcenter PLM integrated solution called System Modeling Workbench (SMW) that allows organizations and their supply chain to collaborate around a streamlined SysML language extending MBSE into the supply chain, creating what we call a Model-Based Design Chain (MBDC).We\u2019ll be talking more about MBDC in future blogs.<\/p>\n\n\n\n If you\u2019d like to learn more about this, you can watch MBSE webinar to learn how Siemens\u2019 System Modeling Workbench (SMW) integrates system modeling\/product architecture with Teamcenter PLM<\/a> and an OOTB standard based methodology to guide users to create product architectures to not only drive design inside your organization but through your entire supply chain creating a Model Based Design Chain to support a closed-loop product development process\u2014so you can start integrated, stay integrated.<\/p>\n\n\n\n Learn more by watching Extending MBSE into your Supply Chain!<\/a><\/p>\n\n\n\n![\"Extending](\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/14\/2019\/11\/MBSE_complexity.png\")
\n
Standard Language to Communicate<\/h2>\n\n\n\n
Register Now, and Join Us!<\/h2>\n\n\n\n