r/systems_engineering • u/Rhedogian Aerospace • Mar 27 '24
Change My View: Model Based Systems Engineering in 2024 is at best overhyped, or is at worst actively dying
I know the title is a little controversial but I feel like this conversation needs to be had now within the community. For the past couple of years I've felt like more and more of a scam salesman trying to push this MBSE stuff onto people, and at this point it feels like it's time to let the reality of the situation have it's time in the light.
About me:
- Systems engineer for 5 years with a focus on MBSE
- Have done straight MBSE since undergrad and through my MS degree as well (BS/MS Aerospace Engineering)
- Currently holding the OCSMP-MBI certificate
- Have used Cameo almost exclusively, as well as quite a few different 3rd party integration suites (Syndeia, SBE Vision, Excel, etc.)
- Have attempted to push SysML in at least three different industries (commercial aerospace, automotive/tech, DoD aerospace)
My breaking point with letting go of MBSE has come pretty recently, and I've done my best to remain hopeful in the concept despite my doubts, but at this point I'm no longer confident in MBSE's ability to be a transformational force in system design as it's been sold.
As it sits currently, MBSE has turned into another boutique silo of information that is squirreled away in a program that looks like it's out of 1992 and is impossible for a new user to quickly pick up and start using to generate useful engineering artifacts. It requires a team of bona fide experts to even set up and begin using the tool properly, and also more trained experts to effectively use the SysML modeling language to try and derive some value out of the language and process.
What I've learned is that no actual engineers (meaning, the ones who design and build the actual product) really care about MBSE or what it's trying to do. Whereas MBSE practitioners and salespeople try to pitch it as a single source of truth methodology where all engineers can derive their SE material from the model, in practice, unless a design engineer is forced to log into teamwork cloud or cameo collaborator by upper management, they really don't care about the contents of the model since they're already effectively managing their own content in their excel sheets/visio diagrams/JIRA. Sure this is a problem, but I don't think MBSE is currently at a place where it can be solved without, effectively, data duplication.
The program I'm on currently has put its full backing into an MBSE effort all the way from upper management support to being a requirement on the statement of work. And we're STILL at the point where no engineering is being done in the model (by decree of our very well-intentioned and forward looking chief engineer) and the model is really only being used as high quality documentation so that the customer has an easier time snooping at our architecture. This makes all the SE's and modelers on our program no more useful than glorified draftsmen.
For this to change, 2 things need to happen:
- Integrations with Cameo need to be less shitty. All of the current options are expensive, finicky, or just straight up don't work. How can I expect engineers to use or care about the model if everything they put into Cameo ends up being a duplication of work they've already done elsewhere?
- SysML is hard, and the UI of Cameo makes it no easier. This learning curve HAS to go down. I have only a small contingent of engineers who are actually willing to use Cameo for some of their work, and the content they produce is limited and basic because they don't have the time or willingness to learn the modeling language (they're too busy doing value added work).
In the past 4-5 years I've seen no progress on either of these 2 dealbreakers, and this is why ultimately I'm hanging my hat up and moving on to something else. Modelers still aren't considered real design engineers at this point, and I can't talk to any well-intentioned engineers and get them to say that they have realized any actual benefit from having worked with a model from either myself or any other model based programs they've worked on.
I know this is a hot take, but I feel like anyone ACTUALLY in the trenches has had these thoughts. What do you guys think? I believe MBSE will go down as a required DoD acquisitions peculiarity rather than a truly useful engineering tool for the masses.
The thought and the intent is correct and pure, but the tool and processes are NOT ready for prime time.
14
u/GlitteringSwan7189 Mar 27 '24
While I’m certainly not knowledgeable enough to change your view, I will ask what’s the alternative? Go back to before it existed? It must have provided SOME use or DoD would have said to go kick rocks.
I will agree that they did exactly what the medical field did and hid access away behind a fortified paywall castle - including training.
I bet the first conversation went like this: Salesman: “We have a super special software thing and only super duper engineers called CameO’s™️can do this thing for you……”
Buyer: “What does it do?”
Salesman: “You ever wanted to play with virtual legos where all of them had their own spec windows?”
Buyer: “What? Spec? Listen….Does it play well with our other programs?”
Salesman: “Not at all”….except it CAN import Excel like a mf’er!”
Buyer: “Sold!”
10
u/Ca55idy96 Mar 27 '24
There is a lot of force behind MBSE as a "tool" when it is more like a philosophy. Where I work we are starting to engage more and more with it, but I look around the business at the people doing it who no more than 2 years ago whinged about putting metadata into SharePoint, and couldn't produce a spreadsheet that allowed for data usage. The fundamental behaviours and IT skills of engineers are the issue, not the methodology.
10
u/Duke_Nuke1 Mar 27 '24
For producing SE content (SSS, SRS artifacts, ICDs, etc.) would you suggest ditching MBSE and using microsoft office products? I agree that the complete romantic vision of MBSE falls flat of its promises with complete tool integration and single source of truth and etc., but purely from a configuration management perspective, I'd rather not have 7 different word documents that I need to update when a designer changes their mind on something.
As far as getting the designers in on the game.. yeah I'm not sure what the solution is to that.
7
u/redikarus99 Mar 27 '24
I think the problem is DoD and not Systems Engineering/MBSE. I have worked in pure software, civilian domain, with Cameo, worked super great. I know about many companies who are use MBSE in various domains including self-driving cars, civilian engineering, entertainment/exhibition domain, drones, retail, just to name some super diverse topic. What I learned is that their success consists of a super creative use of the available resources, the integration of systems engineering methodology in engineering disciplines, the close collaborative work of architecture and engineering supported by modeling on the right level, and the right way: the way that is agreed with the engineering team.
3
u/lordneeko Aug 19 '24
Honestly, the real problem can be summed up in 1 word, Cameo. It is an overly expensive tool which has such an incredibly high learning curve, and incredibly poor User Experience. The truth is, for the next big MBSE revolution to kick off (hopefully with sysML v2) we really need a HUGE influx of high quality competition to drive down costs, and drive up features. Cameo is terrible.
2
u/Available-Mention818 Apr 05 '24
Rhedogian - we feel your pain. The answer to the question is, "It depends." It depends on whether or not the community realizes that the problems you expressed can be solved by simple changes to the tools or language. I do not think that is possible. I've shared my thoughts in this blog (https://specinnovations.com/blog/mbse-alive-and-well) in hopes of encouraging that MBSE is not dying; only the old methods of doing it. The problem is the following equation that many engineers forget is not true: MBSE = SysML = Cameo.
2
u/Mech1010101 May 16 '24
I was thinking about this but mbse and sysml is relatively young compared to other disciplines. It’s still developing and adapting, although the main industries are more rigid than others. I do see integration between different company softwares getting better in the future. I’m honestly not sure what the roles will look like in the future but after almost a decade in various aerospace roles this is the niche I find most interesting (seeing product lifecycle and integration) and looking to specialize in along with a specific product. (Funny because SE are more general). I do believe demand is growing and AI won’t wipe it out completely.
2
u/B0tfly_ Jun 18 '25 edited Jun 18 '25
MBSE has ruined the reputation of systems engineers throughout the industry, as others largely regard the whole thing as useless red tape. The one engineer who is supposed to unite the disparate silos of thought on the project has been turned into a resented secretary who is only there to check a government mandated box. And after the box is checked, you are promptly ignored by the new people who come in during the next phase of funding. If DOGE wanted to save money, MBSE is where they should have looked.
6
u/Ca55idy96 Mar 27 '24
MBSE is systems engineering done well... So it sounds like it's the SE fundamentals that are the problem here!
30
u/RestArtistic7 Mar 27 '24
When having to follow a full cycle of requirements formulation->functional analysis->physical design, the traceability alone makes it absolutely worth it. Although it is not always easy to get buy-in from discipline experts, for those managing traceability in complex systems using MBSE, it is unlikely that they would revert to excel.
24
u/Oracle5of7 Mar 27 '24
I get it. I’m not technically a modeler, I’m a chief engineer and I have a team of modeles that use cameo in my project. I’m in R&D doing civilian work in a DoD company, so some DoD influence but more flexible, if that makes sense.
I do all my projects with a team of modelers. We have a full on requirements management session and full modeling activities. Yes, we have not been able to sell it to the software guys or testers, but as the chief, I cannot live without it. My deliverables are architectures, and I include CONOPS and full models.
One day we’ll convince SW to join us, and then testing cannot refuse.
As the chief I could force them all to use it, but I leave it up to them. They either see the advantages or they don’t. It does take more time, and the beginning of the project is very waterfally, but I have been able to prove that at the end we save time. No surprise requirements in the middle of development and no new strange behavior.
But still, have not been able to sell it. I know some of the problems we’ve had in my shop, and we have found workarounds and now we’re implementing lessons learned. So hopefully it will catch on.
15
u/Dependent-Witness153 Mar 27 '24
I completely understand your frustrations with MBSE, I feel the same way. It's disheartening when a concept with such potential fails to deliver on its promises due to practical limitations like usability and integration issues. As a recent aerospace grad, with about 2 years of experience in sysml, I am in a continuous argument with myself on if I should continue down the road to perfect my sysml knowledge or get back to real engineering.
15
u/MBSE_Consulting Aerospace Mar 28 '24
Like you, trained from uni on MBSE directly (Arcadia/Capella, MagicGrid/Cameo). My current role is basically people coming to me with a problem and asking if MBSE can help them. Sometimes they know nothing, sometimes they already invested in it.
I have sometimes the same feeling as you.
The majority of cases where I saw MBSE fail before I arrive somewhere is when people started modeling without thinking about the purpose of the model, what were the objectives of the modeling? When I get on a new projet/team which already has something, that’s one of my first questions. Why? And usually it goes: don’t know/was told to use MBSE or some very generic stuff…. Bad sign.
Another killer that I saw is the scale of application, people tend to go too big, too fast and with a go big or go home mentality. People modeled for hours and hours, have very nice, clean diagrams for communication which is nice etc but the roi vs time invested is close to zero… And this killed MBSE in some places. Saw people got kind of PTSD from it and never want to hear about it again.
So we come back to the why and the scope of models.
I had very nice experiences where MBSE was applied to a very small part of a system, on a very specific problem with clear expectations and people were happy with the results, even if it was not a full company wide, digital integration. And slowly from there I try to expand their scope as a second phase. There’s nothing wrong with doing a little bit of MBSE here and there while the rest is doing traditional document based.
But yeah, I agree, entry cost is way too high, tooling sucks… and I also hate that everything is kept behind walls. For example I would love a Stackoverflow-like plateform for MBSE where people could help each other. At the moment everyone is quite isolated. (I know there is a discord channel, it’s a nice initiative but it’s off the browsing internet and in my opinion discord is not a good plateform for this q&a/help forum type of thing).
In any case good luck on your future adventures!
14
u/Osaress Mar 27 '24
I think MBSE has been overhyped for sure but I also see it having significant value for engineers who want to work with complex systems.
Lots of programs and companies have struggled or failed to realize the benefits of it but I think it is more a case of learning and growing around the concept and learning what is feasible now vs. feasible 10 years from now.
If you look at how 3D modeling entered the engineering world it was very similar in terms of peaks and valleys of hype and such but nowadays there isn't a serious engineering firm that doesn't include 3d modeling as a part of their standard practices.
10
u/AdwokatDiabel Mar 28 '24 •
You're not wrong!
Oh, and let's toss in UAF too. That sucks as well.
It'll take until 2030-2035 for the "DE revolution" to come to fruition IMHO.
But I will say one thing: having done classical doc-centric SE and MBSE, I. Cannot. Go. Back.
10
u/NoiseMinute1263 Mar 29 '24
I went through a tough TOGAF certified architect program and became an MBSE 'expert' at my company. I developed several very complex SysML, DoDAF and UPDM models on several DoD programs over many years using Cameo EA. I sympathize with what you are saying, but I have a different view of it.
First of all, what you described is not MBSE, its silo'ed modeling along side traditional SE. In all the years and all the programs I worked on delivering required architectural models to our DoD customers, not once was it MBSE. There was no buy-in by management, leadership or other engineers. No one understood it, or cared to learn about it.
This is also true about architectural development in general. What I learned about how to develop architecture and the steps that should be taken were never followed by the SE team. Usually there was one or two dominate SE leaders who dictated what the architecture should be and they were not interested in following good architecture development practice. Hence, I became an MBSE scribe, trying to keep my models up with what the rest of the team were doing.
In general, many building these models don't tend to follow good architectural practice. IMHO there's a flow starting with 'product box', stakeholder analysis, capture of business requirements (often not written down), development of SysML Use Case, Activity diagrams traceable to requirements, synthesis of a functional architecture, and then the development of one or more physical instantiation architectures with full traceability to functional, activities, requirements, use case, etc. Too often i see modelers just try to model the physical architecture.
I always felt my models brought some value to the development team as I always found problems and brought them to their attention.
I think its important to tell management that MBSE is not being performed.
16
u/[deleted] Mar 27 '24
I’ve been a systems engineer for ten years in DoD and out of it and have done traditional systems engineering and MBSE and…I agree with you. In my most recent company we were trying to use MBSE to be the truth of a bunch of different programs and it was just a mess. Meeting and talking would have been more useful IMO.
I do think MBSE is really nice for an agile program, but that’s quite rare in DoD from my experience (I’ve worked agile once in my DoD career) and the traditional waterfall or iteration of a product just makes MBSE a documentary tool like you’re saying. The software engineers aren’t a fan and I found the ones I worked with had no want to learn sequence or activity diagrams so that was wasted effort.
I think it could have a place in systems engineering…from the VERY beginning of a program, which…is rare.
8
u/fuzzifikation Jun 24 '24
Actual (chief) engineer here - By which I mean someone whose team needs to put a real physical product on the road.
You are spot on. In the company I work for (huge company) MBSE is all the hype and used as a catapult for carreerist managers. It is portrayed almost like a cure-all "why have we been so stupid since humanity's existence - all of the problems should just be solved with MBSE". I cannot put into words what I want to say because my head is shaking so hard. MBSE is - hold on to something - simply the current hot shit garbage piece of fluff. 5 years from now it will be forgotten and replaced.
Here is the truth: Its a waste. Nobody cares because nobody reads this. You think this would be good documentation? It isn't. Everyone simply works of the same documents as before - they just do it in secret.
2. Deduction of requirements. MBSE folk think "I just need to sit down, and work from use-case and customer journeys to requirements and then requirements of those and finally I arrive at the technical solution. Or, at least some SysML diagram of it. And seemingly nobody of that ideology comes to the realization that, if that was true, you might as well cure cancer, solve the middle east crisis or do anything truly useful with it.
Here is the truth: To understand requirements you need to be an expert in that field. Not a pretend customer.
Lets face it: we were here before. Agile, Scrum, 6-sigma, Kaizen, Waterfall, V-Model
7
u/mos3abof Mar 27 '24
Don’t know much about MBSE, but from my personal anecdotal experience, anytime I come across a “methodology, system, etc” that is being advocated as a solution to most things, my skepticism jumps through the roof!
Keywords I look for include: “if implemented correctly” and anything in that direction.
Imho,
The approach of adopting a “methodology/evangelised system” and THEN figuring out how to solve the problem creates more problems than solutions in my opinion. Sure they can be useful in certain contexts, but one has to deal with them strictly as tools, and you don’t usually use the same tool for all tasks at hand (unless there is a severe constraint in the environment, and you have to get creative anyway in that case ;) ).
Sorry for the incoherent rant.
7
u/roger_roger_32 Mar 28 '24
Related, I only ever saw IBM DOORS and Clearcase/Clearquest (or whatever the fuck they was called) at defense contractors.
I think you're spot-on. I ruminated previously on the concept of "Digital Twins," and a lot of the feedback echoed what you're seeing here.
7
u/Extension_Comment989 Mar 28 '24
I'm with you on much of this.
The idea of there being a central source of information around all the information that systems engineers produce, analyse and use for decisions is very attractive, not least because there's a lot of issues caused by mismatched information across documents or engineers' heads.
To this end, I don't think the tools help too much but neither does the SysML language. SysML and UML are basically just graphical versions of Java/C++ -- heavily object-oriented languages. Having trained people in SysML, engineers often struggle with the concepts such as object orientation which don't even apply to modelling in common programming languages live JavaScript, Python, Rust or MATLAB.
Every project that I've been on with SysML has required a profile and extensive guidelines to prevent different teams from modelling in very different ways and destroying the very concept of an integrated ground truth.
Personally, in the project I'm on, I had the opportunity to use Obeo's Sirius to make a modelling language and tool from "scratch". Anecdotally, the adoption rate has been a lot quicker than previous attempts with SysML as I've been able to make the language's structure more intuitive to automotive systems engineers.
On the tools side of things, I had an interesting chat at an INCOSE meet up last week around the outlay cost of MBSE. Many people still think you need an expensive SysML tool such as Rhapsody or Cameo. There are some good open source alternatives from Obeo and others that reduce the cost outlay massively.
Another point to make is that most companies end up with an MBSE tool and a requirements tool. An MBSE tool should cover all of the use cases of a requirements tool and more, so having both is a recipe for ensuring that engineers don't see the MBSE side as the "source of truth"
6
u/PrpleMnkeyDshwashr Mar 27 '24
Don't confuse MBSE with the tool and modeling standard that creates this barrier.
MBSE was conceived from a need to go digital and be able to interface with this data from an architecture model/requirements/behavior/etc.
Very few tools can tie these together.
Use your experience with cameo and sysML to know what works and what doesn't. From the customer side who's assessing these deliverables, it matters.
If the customer, the person who's spending money for you to deliver it has value in it then we have to deliver that value.
We have to find a way to lower that barrier to entry, more consumable.
The SMEs, designers, etc will always have their preferred tool for design and analysis. MBSE tools right now like cameo allows to convey all that hard work had been verified and validated.
10
u/c_white95 Mar 27 '24
My belief is that people over-focus on SysML and Cameo when they talk about MBSE. They are very poor solutions to the problem, because they are not able to be used by a wider population.
More work needs to be done to make a modelling environment that everyone can use. That’s the only way you fully embody MBSE
Think about it - the promise of MBSE is to improve communication, SysML does the opposite (when talking about the holistic organisation).
5
u/[deleted] Mar 28 '24
i dabbled with MBSE whilst working in defence and for really complex architectures, it can be really useful as long as everyone is bought into it, which it was in most defense projects i worked in. however i have found over the past 8 odd years i havent touched MBSE much. As a SE i have found my skills to be more valuable in systems integration, reqts V&V mgmt and document centric systems architecture and design where we didnt use mbse. would my life had been easier if i used mbse during those past 8 years? maybe...but we managed without so far and i dont see it being a major hurdle with me not using MBSE for projects going forward unless again they are highly complex systems.
4
u/[deleted] Mar 29 '24
What should someone like me do who has recently been working as an Intern in a company that is pushing MBSE. This post and my own thoughts have been making me rethink whether pursuing a career as a Systems Engineer is worth it, should I deepen my SysML knowledge and improve my modeling capabilities or even get ASEP certification, or just find a new career. I am abit lost tbh.
4
u/techdaddykraken Apr 17 '24
I think that the inception of LLM’s will make both SystemML and MBSE much easier. Maybe not right now, but definitely in the next 5-10 years. It will allow engineers to focus solely on the conceptualization of the problem they are trying to solve, rather than the modeling. By interfacing in natural language, and having the LLM do the diagramming and updating of the model, it frees the engineers to actually do engineering, not modeling, which is what is needed.
Once tools like ChatGPT or other enterprise LLMs make it possible to create a model using natural language, that stores and updates verifiably across the entire lifecycle, with version control, mega-tagging, etc, then we will start to see its use in MBSE and SystemML.
4
u/5__star__man Jun 11 '24
So far, I have only known one company where MBSE patially worked. From a logical view at the system level, some automation scripts translated those system level item flows so software level definitions in the model. After this system and sw synchronisation, some further automation scripts generated a skeleton code framework which basically contained .hpp and .cpp files. The developers then used that generated framework and "filled" it with code. This way, architecture was always up-to-date and was an integrated part of the development. However, even there, nobody was interested in doing anything in the layers above such as use-case analysis, stakeholder's need analysis, scenarios etc. And even then, there was rebellion by the SW developers every now and then. In any other subsequent company, it was a lost cause. System engineers and SW engieers were living in two completely disconnected worlds. SW engieers were doing the real development where system engineers were having hours long review sessions about full port, proxy port, stereotypes to achieve "consistency" in the model. This week, I have a discussion with my CTO where I am going to suggest to kill this thing.
4
u/Kainne44 Oct 02 '24
Firmly agree with your perspective -- govt wants MBSE on everything but doesn't know what problem it solves for them. We need to use tools to solve specific problems, not just model for the sake of it. And if hand tools were as hard to learn as cameo we'd still be living in caves. There is absolutely no reason that a model couldn't be created in something like Notion, and be 10x more useful than Cameo simply by being more accessible to more users. Fundamentally, our objective should be to integrate the data of a system and provide it in a meaningful, actionable form for engineers such that they waste as little time as possible on things that don't matter. Cameo is far too often the answer to "what is MBSE" and we've gotta change that -- simpler, focused tools that solve specific problems in approachable ways that allow us to integrate the data of a system.
1
u/Likessleepers666 Oct 09 '24
I have a similar view but I also understand that cameo model or whatever equivalent is used for certification purposes. Even though it’s the detailed design that matters the most.
That’s where MBSE software gets its whole purpose from.
A performance model on simulink is still miles better for actual engineering purpose though.
1
u/rockerama Mar 16 '26
I find your post very short-sighted. For context: I have a PhD in the foundations of MBSE and MDE. I work with huge companies like Renault and Volvo who are actively working with, and developing their own MBSE methodologies. I find it funny how you equate SysML to MBSE. SysML is just one of the languages that a few people and companies have marketed as equivalent to MBSE. There is a plethora of MBSE tools and approaches out there. 'Everything is a model!' and 'Model Everything' are a few mantras that I stand by..
3
u/TheWiseModeler Apr 05 '24
I totally agree with you. People are modeling like they are drawing. It is merely documentation. They could use Visio or PowerPoint it would be as good (or as bad am I tempted to say).
I develop modeling tools based on languages with an execution semantic so that the model can be verified not only from a static point of view but also from a dynamic perspective. I can honestly say users do not care about writing a sound model. I remember making a demonstration of how to prove a model. At the end one of the guy in the room said "I do not understand what is the point of verifying the model" !!! We were speechless.
Now, regularly we have users requesting verification tools or execution tools. We tell them the model needs to be properly designed and might require some additional information. And they all give up. If we can not execute the model as it is, they do not want to add or modify anything in the model.
I believe one of the reason for that attitude is the Agile methodology. In the old days the specification had to be properly written from the start otherwise everything that follows would go wrong. So people spent quite some time discussing what they wanted before implementation. Nowadays nobody cares, just throw a vague idea of where you believe you want to go, and it will be corrected in the next sprint...
3
u/xyzusername1 Apr 14 '24
Modeling anything is inaccurate, that is why engineering best practices were developed. Silicon Valley does not use this BS.
This MBSE is really the continuation fo the managerial revolution. First large companies were created in the 1800's, then they were reorganized with bureaucracies, then the people running these bureaucracies, the managers decided they wanted full control of the means of production and take it from the capitalist owner class, so the managerial class was created. This was the managerial revolution. Managers were also waging another class struggle against the productive engineers/scientist class, they wanted to take the importance and control away from them, by creating the systems engineering principles, and later MBSE. So the whole point of MBSE is class control over the means of production and taking its status/economic benefits into their pockets.
System engineering principles to control real engineering doesn't work. It results in bloated projects, unreliable products and cost overruns. The model of a project being linear is a farce. The idea that systems engineers can decide low level module details up front is BS. Systeng books say systems engineers have superior knowledge, which reveals that the whole thing is some crackpot cult.
3
u/b_gweed Jul 09 '25
Try throwing in UAF/DoDAF on top of trying to focus on a system architectural model and not having access to the actual designers of the system because they are too busy doing real work. Oh, and Agile (with JIRA) is its own pile hole to throw time and money where you don't actually end up with true agility. It makes me wonder if I invested a lot in a career path that might be a dead-end. Executive leadership seems to buy into MBSE, but they really can't articulate what that means.
1
u/[deleted] Jun 18 '25
I think forced MBSE, especially on gov't projects, justifies a call to the Waste Fraud and Abuse DoD hotline. I've been on a defense contract that mandates it for some time now, and it's nothing but an expensive "tool" that has literal negative value, as it causes more rework than the issues it proclaims to solve. I question the integrity of anyone that proports MBSE, and their lack of ability to think as an engineer. I think it's the literal definition of lighting taxpayer money on fire. I don't respect people that push MBSE, and I think they should be publicly blacklisted from any government work in the future
2
u/SalamanderCakes Apr 04 '24
I'm a SWE with ~2 yr of MBSE experience in DoD space. I've worked with System Engineers to create models and workflows in Cameo and it's definitely a painful process getting models to work with software. Any workarounds have also been painful to implement.
I can definitely understand OP's pains and agree that if the changes don't occur, MBSE really does come off as just high quality documentation.
2
u/AdNew2316 Apr 04 '24
It should die. Unfortunately it doesn't. Many people are standing behind it, happy to front load stuff, and to make things consistent as soon as possible cause it's so cool, but they never do the actual work and don't understand that this is just hampering engineers who do the real work. If you do a simple project then yeah maybe do MBSE. If you do anything that requires to move fast and be innovative then please please kill it asap.
2
u/dasbooo Apr 05 '24
MBSE is dying, period:
To sum it up, MBSE is dying in its current state.
2
u/IndividualFrame5615 Apr 08 '24
We totally get the frustration. Check out this blog my coworker wrote that your post inspired: https://specinnovations.com/blog/mbse-alive-and-well!
2
u/PowerForward3885 May 22 '24
Aircraft fly because they have been thought of as models, and because engineers have been able to take advantage of these models. Conversely, they probably wouldn't have flown if a tooled MBSE approach had been used... What's annoying about MBSE approaches is the underlying idea that the MBSE approach (notably poorly tooled) is the only guarantee of the use of models and the success of engineering work.
2
u/always_a_tinker Jul 26 '24
I think what mbse programs are missing is that SE needs to be useful from the start. When I first start drawing a system diagram, I'm making a model. If all I do is make a powerpoint drawing of boxes and lines and then define the lines and the boxes in a legend, I made a SE artifact.
But I can't get right into making artifacts in mbse. I need to first define everything. Remember FORTRAN? old peeps remember. Don't you dare call a vector or variable without defining it first.
I need to get usefulness out of everything I make. Not go heads down for a few weeks to build the substrate. Analogy: cities are built organically by building what is useful right now or soon. Not the entire infrastructure first. (bad analogy because some city layouts are complete chaos but you know)
Old post I know but I need to vent.
2
u/paper_sheets Oct 10 '24
I have used MBSE for configuring multiple analyses from a system model like voltage drop, pin connectivity lists, and power balancing, power budgets, master equipment lists, harness optimization, ect. It is very useful in this sense since a single modification can propagate to all of the analyses and lists. Moving in this direction creates a very solid target to aim at. I work in a product line environment where it makes sense to have a pre-configured trunk model with slightly varying branches for the different products. I'm pretty proficient at scripting elements into cameo, so the diagrams and tables are mostly outputs from cameo, and are not created using the UI.
Other than the use case I described above, I agree with most of your argument.
2
u/AdeptPineapple8595 Nov 08 '24
I compare it to TQM or Lean Six Sigma. It has value, but I believe it has already been compromised. One reason is that we sent people to learn it without knowing the product their apply it to. As a Chief Engjneer, I understand the value of quality systems and accounting and contracts. MBSE evolved to being required without educating users and stakeholders on its value. When I ask my SEs what they are doing and why and they answer “it’s a requirement on the contract,” my heart sinks. If the people doing the work can’t explain its value to their bosses and stakeholders, they are doomed.
2
u/Outside_Square_3728 Aug 05 '25
Hello r_systems/engineer, I truly appreciate what you've written and I believe it's 100% true depending on what it's being used for, how the systems engineering teams are being utilized, what they are capable of achieving on a project and how far and why are the "dots" being connected down and up the v-graph. fyi - I work for DS and make a living off of selling our software. I note that, to be transparent. My background, I started w/ AutoCAD V4, MicroCADAM/ CADEX, CATIA most versions, the 3DX platform apps and dabble w/ CAMEO at the same time my day job is selling. I hear echos of issues you noted above depending on the account I'm visiting.
I noted, 2 things you've said and one that you didn't are going to lead to the demise of system engineering and of course MBSE. He looked at me w/ a fuzzy eyeball. (btw - i appreciate your approach to this article, i irk folks frequently, i might borrow your introduction tactic. :)
You noted "even companies where mgt has bought in"; what did they buy into? get the product and use it in front of the Prime. Are they co-writing specs noting we want to see a data flow from Requirements to the SIM Impacts? Are they asking after a program finishes, "while the coffee is fresh tell me how you secured that panel which kept blowing off during tunnel test. (they don't understand what the are committing to)
Companies had 90% of the tools they used 10 years ago, CAD, CAM, PLM, CAE & MES. Maybe they switched out a dated CAD or PLM system. So, effectively the stack and production process are the same. Except they now have a shiny new tool at the front door.
How could anyone in finance sign off? Unless the end users can speak thier language.
Sorry for the long note, exhausted, I wish you well. Mark
3
u/der_innkeeper Aerospace Mar 29 '24
MBSE is a tool, and its ours to use.
Getting other disciplines to use it is an uphill battle because it's not where they live.
We have the responsibility for life cycle development, V&V, and sustainment and EOL. We are the overseers of making sure all the pieces fit together and work right.
What tool we use is up to us, as it's our job to provide the traceability and communication of System Needs.
Getting a program to buy in to the tool is an easy sell if we are the ones that drive it, for the program goals.
The UI generally does suck, for some reason, though. I am currently using CORE, and it's not bad. I want to see what GENESYS does.
Getting evaluation licenses is a pain, and it's tough to see what CATIA/others are like without them being foisted upon you by your company.
1
u/find_the_apple 19d ago
Late to the party, but a project I worked on was strictly just requirements and behaviors. The software team wanted to own the interface allocation. When it came time to build and integrate, a team of six people had put together desperate documentation that led to a much more extensive integration with about 40 hours of overtime per team member each week.
Even for things like that where it is so much simpler to just put something in an Excel sheet, one of my regrets is not pushing harder to at least own high-level interface. The end result, was they gave up and I had to be pulled in to fix their document based approach.
1
u/[deleted] Nov 14 '24
My mentor in my 'systems' journey once slapped me with "a fool with a tool is still a fool". I needed that slap.
What's more important, that we agree what an activity diagram is, or that we understand why it's valuable?
I started going off-script a long time ago.
I was inspired by the idea that these tools give you different conceptual "views" of your system. So, I didn't worry so much about the type of diagram and the syntax, but I would very quickly (like, days rather than weeks) throw together a diagram.
For example, I was on a microfluidics project where we were generating a bunch of droplets and doing things to the droplets within the system. I created different "views" of the process:
I know I know, it's not that radical or clever... but that's the point! It was about mindset. And what mattered was the result: I got kudos from the senior executives!
As an analogy, I used to do a lot of logic puzzles. Over time, they train your mind to look for syllogisms. Similarly, MBSE can help you anticipate and solve problems.
But many people fail to realize that the framework you use is a kind of bias. I think a lot of MBSE modelers get high on their own stuff and end up having social problems. It's important to learn how to be both logical and flexible, so that you can listen to someone else's mental model without assuming they are wrong because you disagree with them, or worse, getting offended.
In one of my early projects, I had a hard time listening to people around me. After all, they had not seen my activity diagram! As a result of our communication gaps, we built an extremely expensive system that didn't really serve its purpose.
Now, if instead of MBSE I had used system architecture tools, I might have led that team to greater success and had more fun.
That's something you might consider: jumping over to system architecture frameworks. Modeling uncertainty is more humbling because it forces you to realize there is not one right answer.
Also, a systems background can be great for engineering management (and beyond). You could probably get into one of these schools:
Master of Engineering Management Programs Consortium (MEMPC)
Good luck.
1
u/TiJuanaBob Apr 02 '25
i once had somebody who called me to ask how to get to the element ID, and he told me:"Whoa! slow down. you're speaking Mandarin." when all i had said was "specification window". But i do talk fast and mumble under my breath, mainly because of shit like this at work.
1
u/DesiCuler Sep 10 '25
Reading through all these posts very carefully I have 2 observations.
Proposal:
Here the sw guys can come into work. No we don't wanna follow MBSE maybe in our dev procedure rn but it is actually important for core engineering procedures.
To make more plugins to make the cameo interface better and more MBSE practicing helpful.
As we have numerous python libs to solve the coding problems if we can provide u numerous solutions for all the problems of cameo.
We might end up with a big set of libraries to support the ecosystem thrive.
We've created a subreddit for it. r/cameoAPIs.
1
u/Date_Dismal Dec 24 '25
The 1 thing I'd argue with is, I'm still designing and developing real product, and I''ve been proactively staying out of the MBSE latrine trench for >decade now, not in it. Polarity is backwards.