1 / 5

Infusing MBSE @ Ford

Infusing MBSE @ Ford. G.Walley (gwalley2@ford.com). Infusing MBSE @ Ford. What is the nature of the organization for which your are infusing MBSE? (e.g. size, function, discipline, product)

randylwilliams
Download Presentation

Infusing MBSE @ Ford

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Infusing MBSE @ Ford G.Walley (gwalley2@ford.com)

  2. Infusing MBSE @ Ford What is the nature of the organization for which your are infusing MBSE?(e.g. size, function, discipline, product) Primary target (for interest/complexity/value reasons) is teams involved with developing electronics, controls, & software Functional groups most active (in relative order of decreasing activity) : Powertrain, electrical, chassis, IT Typically not much attention from traditional CAD/CAE teams - but this is starting to change

  3. Infusing MBSE @ Ford What enablers and barriers in your environment Enablers : Having authority for architecture decisions (ideally across vehicle programs and platforms) Having authority (explicit or understood) to change corporate processes and tools Formation of a Ford SE Council has helped this Bite-sized but steady and pragmatic deployment... Don't forget still being able to do the basics (FMEAs, boundary diagrams, interface matrices, etc) First follower focus - encourage and protect first adopters New employees Frustrated but passionate employees Shared model repositories User community / tech clubs for informal support Readily available and consistent training Barriers: Legacy data, people, and past failed/perceived failed attempts Too much OTHER modeling experience Functions as a starting point for physical parts and assemblies Tool interoperability and data exchange gaps Internal policies governing new tools Lack of granularity, traceability, or documented existence of requirements and architectural decisions for existing systems Mix of in-house and supplier-delivered solutions

  4. Infusing MBSE @ Ford What primary MBSE value do you communicate to for your stakeholders to obtain their involvement/commitment? Being able to quickly generate and REgenerate current reports and work products Being able to generate and seed known values into these work products progressively more and more as team expand in their use of a model-based approach New views /reports previously too hard or slow to build to be valuable Improved feature compatibility assessments earlier in development to spend time testing functionality not basic integration compatibility (without simply having to talk to everyone you can find) Do you try to measure this value? Not yet

  5. Infusing MBSE @ Ford How do you measure infusion progress? Not much implemented yet License usage patterns, duration, and growth New gateway review criteria for quality, format, and completeness Time metric systems # of current pilots vs. teams trained

More Related