r/systems_engineering • • 1d ago

Career & Education Feeling stuck in MBSE, and just got an offer for a 45% increase for Training Systems work, any thoughts?

13 Upvotes

So I been working as a SE for almost 5 years now with a MS and I’m an L2. I been mainly doing systems architecture work but I have turned into just an experienced MBSE engineer. The tool complexity is fun, but I am starting to find that I no longer feel like an engineer and I’m unsure if I will have the skills to compete at higher SE roles in 4-5 years. Another caveat is that after speaking with my manager he has no real plan for me to progress on my team. So from my read he’s expecting me to take on more ownership in the new year when I’m already operating well above my level. I would essentially be responsible for integrating the data architecture of a flagship program and becoming a low level “SME” on our team for all of the protocols and standards for our structured messages and interfaces then guiding the IPTs on how to develop their integration models. While this sounds really cool…. I wouldn’t be able to be promoted until March 2028 while operating at a much higher level than my role due to our team size.

Anyway, I was offered a senior role in NoVA at a prime, this would be moving from the midwest to the NoVA which is where I want to be in the long run due to the wealth of industry. However, it would be an upgrade site for legacy training systems mainly integrating them in our modernized C2 and targeting systems. It’s better pay even after the cost of adjustment and in a nicer area of the country. I would have more ownership and exposure to the test side of the industry.

Would moving from supporting flag ship programs to upgrading training systems be a bad move? Or should I stay in my current role?


r/systems_engineering • • 1d ago

Career & Education I Almost Gave Up on System Design. Then I Found These 12 Patterns.

Thumbnail
javarevisited.substack.com
0 Upvotes

r/systems_engineering • • 2d ago

Discussion Where should i move? Europe?

0 Upvotes

Where should I go? Europe?

I'm planning on moving abroad, since I don't feel like my future is meant to be in Argentina. I'm currently 18 years old, about to finish high school, and I have Spanish nationality. I'll receive a Food Technology Technician Degree when I graduate from high school since I attend to a technical school. I'm also attending an English institute at the moment, penultimate year.

I'll be a systems engineering after university, and I'm also planning on studying another language while on the second/third year of uni (that'd be the language of the country I will move to). I'll probably work as an engineer for a year or so until I gather some money to move abroad.

By the age of, let's say, 25 years old, I'll have this in my portfolio: Systems Engineering degree, B2-C1 English, Food Technology Technician Degree, and a B1-B2 level of the language of the country I'll be moving to.

I consider = good salary, a nice and safe city to build my future on, with a good quality of life, etc, etc. My goal is to gain a good amount of money monthly and to have enough money to travel, buy things, etc.

Thoughts? I was thinking on Munich, or maybe the Netherlands.


r/systems_engineering • • 2d ago

Career & Education How to get job with Systems Engineering Degree GraingerUIUC?

0 Upvotes

Hi everyone, I’m a senior studying systems engineering at UIUC. I’ve had previous internships and Co Ops in Electrical System Layout, Mechanical Design, R&D, and then some experience with Patent and IP of my design project. I also am interested in defense/gov jobs as I have ROTC connection.

Applying to jobs I’m getting what I feel like auto rejected from roles i thought would be perfect, and even have the name systems engineering, but list majors as Mechanical, ECE, or even chemical engineering.

Does anyone have any advice for companies to apply for? Should I throw a line in my resume saying Systems Engineering major is Equivalent to Mechanical/ECE?? I don’t want to lie but I’m kind of sick of getting auto rejected for jobs that are perfect for me. If anyone has an advice, companies, or people even that understand Systems Degree, I’d love to hear it. Thank you.


r/systems_engineering • • 2d ago

MBSE Hi Everyone, can someone help me, how I can get a licence key for IBM Rational Rhapsody, i downloaded the trial version but unable to get the licence key, i already contacted IBM support but no response 😕

0 Upvotes

r/systems_engineering • • 3d ago

Resources SysML v2 Lesson 25: State Definitions & Transitions (Actions Unified)

Thumbnail
youtu.be
3 Upvotes

Hir/systems_engineering,

We are back with Lesson 25 of our technical deep dive into the SysML v2 standard.

In Lesson 24, we connected system parts together using unified flows and messages. But our system components still didn't have operational modes, states, or lifecycles. Today, we look at state machines and state definitions, seeing how SysML v2 simplifies behavioral modeling by treating a State Definition as a specialized kind of Action Definition, allowing the exact same control patterns we used for actions (first, then, and exhibit) to govern states and transitions.

1. The SysML v1 State Machine Disconnect

In SysML v1 and UML, state machines were governed by a separate metamodel from activities. Relating a StateMachine to a structural Block relied on classifierBehavior or ownedBehavior—a different mechanism than the ActivityPartition swimlanes used for activities. That split created separate mental models where discrete states felt like a completely different category of thing than actions or processes.

2. The v2 Shift: States Are Actions (And exhibit Works Like perform)

SysML v2 unifies this cleanly:

  • StateDefinition is a kind of ActionDefinition: Because states share that foundation, they inherit the same execution model—meaning a state isn't just a passive label and can execute work during its lifecycle using sub-behaviors (such as entry, do, and exit actions).
  • exhibit state**:** Just as perform action links a structural part to an action, exhibit state states that a part exhibits a given set of operational modes—one unified pattern with two clean spellings (perform and exhibit).

3. Modeling States, Triggers, and Transitions

Transitions in SysML v2 build on the succession logic (first and then) from Lesson 22, paired with event triggers (accept) and guards to handle mode changes:

Code snippet

package ClimateControlSystem {
    item def StartSignal;
    item def StopSignal;
    
    action def RegulateTemperature;

    state def ClimateControlStates {
        // Initial state specified via 'entry'
        entry;
        then state Idle;
        
        state Idle;
        state Heating {
            // A state can perform actions while active
            do action regulate: RegulateTemperature;
        }
        
        // Transitions triggered by incoming signals/events
        transition from Idle to Heating accept StartSignal;
        transition from Heating to Idle accept StopSignal;
    }
    
    part def ClimateController {
        // 'exhibit state' links the part to its operational modes
        exhibit state controlModes: ClimateControlStates;
    }
}

4. SysML v1 vs. SysML v2

Modeling ConceptSysML v1SysML v2
State MetaclassDistinct metamodel separate from activities.StateDefinition is a specialized kind of ActionDefinition.
Hardware BindingclassifierBehavior or ownedBehavior property on a Block.exhibit state, matching the pattern of perform action.
Transition LogicHandled via specialized transition triggers and guard syntax.Unified with first, then, and event accept successions.
Architecture ConsistencySeparate mental models for discrete states vs. continuous flows/actions.Consistent definition-and-usage pattern applied across behavior types.

Next lesson, we will explore how constraints and validation rules keep these behaviors within safe operational boundaries.


r/systems_engineering • • 2d ago

Discussion The Tree of Structural Intelligence: A Framework for Understanding Stability, Drift, Adaptation, and Evolution

0 Upvotes

I've been developing a conceptual framework called the Tree of Structural Intelligence to explore a simple question:

Why do some structures remain stable while others drift, adapt, fail, or evolve?

The model begins with the idea that every system exists under pressure:

  • organizations
  • institutions
  • ecosystems
  • technologies
  • economies
  • individuals

The Tree maps a progression:

Plain Text

Structure

↓

Pressure

↓

Observation

↓

Analysis

↓

Drift

↓

Decision

↓

Preservation or Extraction

↓

Outcomes

↓

Survival or Failure

↓

Evolution

One of the central ideas is that the same structural knowledge used to strengthen and preserve a system can also be used to exploit it.

I refer to this as the Structural Intelligence Paradox.

Another observation that led to the framework:

Every mystery humanity faces is really just structure we haven't mapped yet: a pattern we haven't recognized, a system we haven't decoded, a relationship we haven't understood, a behavior we haven't modeled, or a force we haven't contextualized.

The Tree is intended as a visual model for analyzing structural behavior across disciplines rather than focusing on any single field.

I'd be interested in hearing thoughts from people interested in:

  • systems thinking
  • organizational design
  • complexity science
  • network theory
  • engineering
  • philosophy of systems
  • knowledge architecture

What parts of the model seem useful? What would you add, remove, or challenge?

Visual Tree:

https://structuralintelligence.llc/universal-tree.png

Framework:

https://structuralintelligence.llc/structural-intelligence


r/systems_engineering • • 2d ago

Resources Some Things to Think About

0 Upvotes

When autonomous weapons can sense, decide, and act, what must our requirements make clear?

What can the system do? What is it authorized to do? Which decisions remain with people? Who is accountable for what happens?

These are just a few of the new questions autonomous weapons requirements need to answer.
https://awsdframework.com/NewWorld.html


r/systems_engineering • • 3d ago

Discussion Our AI worker retried a subscription limit 900 times. Here's what we learned.

Thumbnail reddit.com
0 Upvotes

r/systems_engineering • • 4d ago

MBSE How many Reference Architectures (RA) are out there?

9 Upvotes

Are there publically accessable MBSE RAs? By RAs, I mean is a reusable, standardized architectural framework that defines the structure, definitions, modeling patterns, conventions, and relationships accross a subject domain. RAs are basically common libraries for MBSE models.

The one I know of is the INCOSE smart parking lot RA. There should be more based on how much everyone seems to talk about MBSE.

Or if not RAs, example models? It seems everyone keeps their cards close to their chests. I always wonder if I am modeling similar to anyone else and it sometimes feels like I am flying blind.


r/systems_engineering • • 4d ago

Career & Education Is software engineering seriously undervalued at semiconductor equipment companies, or is it just my workplace?

Thumbnail reddit.com
2 Upvotes

r/systems_engineering • • 5d ago

Career & Education Interview Tips as an ME

6 Upvotes

Hello! I'm a sophomore ME student, and I have a interview next week for a systems engineering internship with Northrop Grumman. I've been a machinist at NG for a few years, and all my coursework has been general stem + foundational ME classes so far. So basically all manufacturing and mechanics. So this is going to be way out of my wheel house, which I'm honestly super excited for. Manufacturing is pretty boring, so I'm stoked to have the opportunity to learn some completely new stuff. But, I have to get this first, and I really have no idea what to prepare. From some light googling, seems like I need to understand some of the principals of systems engineering, V&V, I'll definitely need to brush up some EE basics, but I figured it's best to ask some systems engineers too. Any advise for what to study, how to present myself, etc, would be great appreciated. Thank you!!


r/systems_engineering • • 5d ago

Standards & Compliance System Safety Engineer hazard

2 Upvotes

I have a school project that is asking the following: what hazards can occur if a requirement is "radar, track, flight plan and weather data transmitted from a to b shall support one way communication"


r/systems_engineering • • 7d ago

MBSE SE books and stuff

Post image
25 Upvotes

Hi everyone.

I recently came across MBSE4U and saw that they publish a number of books on MBSE and SysML. Has anyone here read any of them?

I’m especially interested in The SysML v2 Book, but the price is relatively high, so I wanted to ask for opinions before buying it. With all the AI-generated content around lately, I’ve seen a lot of trash books in programming field, so I just want to make sure it’s actually worth the money and not AI slop.

Would appreciate any feedback.


r/systems_engineering • • 7d ago

Career & Education Need help

5 Upvotes

I am a wiring harness design engineer at a OEM. But i don’t feel like I am learning anything at this job. I want to transition into some other role but don’t know where do I start. Some seniors suggested system engineer is a good role. Can you please suggest me good roles and also tell me it system engineering is a good role?

BD- electrical and electronics engineering
Current experience-4years


r/systems_engineering • • 9d ago

Career & Education Junior systems engineer

6 Upvotes

I finally made it into systems engineer! I got a position as a Junior and I’ll start in a few months.

My university studies were in Software Engineering. I want to prepare myself a little bit and start learning some things on my own before starting the job.

If you had to start over as a systems engineer, what would you focus on and start learning asap?


r/systems_engineering • • 8d ago

Discussion What is a Centralized Digital Thread? Understanding the hub-based approach

Post image
0 Upvotes

A product's lifecycle involves multiple teams, processes and software systems. Engineering teams work with product designs, development teams manage requirements, manufacturing teams handle production, and quality teams maintain testing and inspection records.

Each system generates valuable information, but bringing all this information together in a meaningful way can be challenging.

One architectural approach to addressing this is a Centralized Digital Thread.

A Centralized Digital Thread uses a central platform or repository as the primary point for bringing together and managing product-related information from different systems across the lifecycle.

Think of it as a central hub that connects information generated by different teams and applications.

How does it work?

Consider an organization using different systems throughout its product lifecycle:

  • PLM (Product Lifecycle Management): Manages product design and engineering data.
  • ALM (Application Lifecycle Management): Manages requirements and software development information.
  • ERP (Enterprise Resource Planning): Handles production planning and resource information.
  • MES (Manufacturing Execution System): Manages manufacturing operations.
  • QMS (Quality Management System): Maintains quality, inspection, and testing information.

In a centralized approach, relevant information from these systems is brought together or made accessible through a central platform.

For example:

  1. Engineering creates and updates product designs in the PLM system.
  2. Requirements and development information are maintained in the ALM system.
  3. Manufacturing data is generated through MES and ERP systems.
  4. Quality and testing information is recorded in the QMS.
  5. The central platform brings these different data sources together, helping establish connections and provide a consolidated view of the product.

Key characteristics of a Centralized Digital Thread

  • Central point of access: Relevant product information can be accessed through a common platform.
  • Consolidated visibility: Data from different lifecycle stages can be viewed in relation to one another.
  • Consistent data management: Centralized governance can help maintain consistency in how information is organized and managed.
  • Traceability: Relationships between requirements, designs, manufacturing records, and quality results can be established and tracked.

Potential benefits and considerations

A centralized approach can improve visibility into product information, simplify data access, support consistent governance, and make lifecycle traceability easier to manage.

However, it also brings certain considerations. A central platform needs to handle information from multiple systems, formats, and departments. Integrating these sources, maintaining data accuracy, managing access, and scaling the platform as the organization grows can require significant planning.

In simple terms, a Centralized Digital Thread brings relevant product lifecycle information together around a central point, making it easier to access, manage, and trace information across the organization.


r/systems_engineering • • 9d ago

Career & Education Worried about career options

4 Upvotes

I'm studying Systems Engineering in undergrad in college right now, specializing in Computer Science. I am pretty worried about my career opportunities after college, since I don't really want to do a masters. I was wondering if any one of you guys were in the same boat as me and how your career panned out. And also whether you were able to get internships in college, since I'm currently in my 2nd year and have not landed any.


r/systems_engineering • • 9d ago

Discussion "We hate red tape. Want to go faster."

14 Upvotes

BLUF: Companies want to go faster. I think the biggest way is to reduce workload, allowing faster progression through SE processes.

While studying for the CSEP exam I was reminded of a conversation I had during an interview recently. The company in question is younger. Part of their culture is to "go faster" and "we want to avoid all the red tape that slows down development in the government agency we work with".
I can appreciate wanting to move faster, more efficiently.

While studying for this exam I'm reviewing Configuration Management and Change Control principles. This feel like what they are talking about. The instructor in the review course said something like "this is not bureaucracy, this is ensuring complex systems can be developed without chaos".

So, how to balance the two perspectives? Adding processes = more time but ignoring processes = failure/rework/etc. Maybe my real question is "where can we really get efficiency?" Is it by choosing not to follow a change control process? (or other SE processes) Or something else? How to talk about it to companies who are fixated on "avoiding the red tape"?

So far this is my take:

  1. Processes are not inherently bad.
  2. Invest significant time & energy upfront in tailoring
  3. Stay flexible, re-tailoring if needed.
  4. The most effective efficiency can be gained by not drawing out each step.

I think #4 is the one I've not heard much about. I think it relates back to employee & team workload management and planning. While at my previous org, there was very little of that. The situation was that nearly every person & team had a multitude of "things to do". Since every team/person had this vast portfolio, AND every other team/person was involved in many other things, but not usually the same things, SCHEDULING became hard. Which led to processes taking FOREVER to complete.

An example is in Change Control. The steps are Request, Impact Analysis, Approval, Implementation, and Verification & Update. If I were to Request a change in a system, I'd present that request at a meeting.. then wait until the next meeting to start the Impact Analysis, then wait until we got appropriate SMEs all in the same room (probably sometime later in the month). Then we could get approval. Why the hell can't that process have taken a day (assuming simple impact analysis)? The biggest time suck here is the time between meetings. Not the process. It's the scheduling of personnel.

Well, I feel like I've either ranted enough, or shared useful insight... either way: please share your thoughts. I'd love to hear a story where this was recognized and addressed. OR a story of an example proving why the long lead times is actually a good thing. OR share something you think I'm just missing here.


r/systems_engineering • • 9d ago

Discussion Career options from a software validation perspective

5 Upvotes

Career options from a software validation perspective

I’m currently a software validation engineer in automotive field with almost 5YOE, have experience with requirement analysis, test scope design, test case derivative, automation, execution, defect analysis etc etc. I always try to get a good understanding of the product I work on.

I kind a feel stuck, I like my job in a way, I feel it’s a important role to be able to make sure our product is safe blah blah but I sometimes don’t understand the future of this role.

I’m starting to implement more automation with python, learning and working towards using ai agent for log Analysis and make validation results much efficient .

But what else should I be doing to make sure I stay relevant ? And I don’t think AI is anytime going to replace this role, it can change it but not eliminate it…am I being delusional here

If not, what other roles can I grow into? I’m not a great programmer so dev might not be an option

It’s a rant but also appreciate any advice from professionals in the industry! TIA


r/systems_engineering • • 10d ago

Career & Education Got my ASEP, next steps

7 Upvotes

I was wondering if anyone knew of any REASONABLE courses to learn sysml/cameo. I want to be a systems engineer but need direction in pursuit of where I should learn. Anyone have any advice, course recommendations, practice free software etc, please let me know, thanks!

PS. I don't want to spend 1k on a course.


r/systems_engineering • • 9d ago

Resources Autonomous Weapons and the Center of Gravity

0 Upvotes

The biggest changes and/or additions to Requirements Analysis occurs when autonomous weapons are added to the mix. In classic systems design, everything begins at the center. In autonomous weapons systems, the edge defines the system.
https://awsdframework.com/CenterOfGravity.html


r/systems_engineering • • 10d ago

MBSE SysML v2 Deep Dive: Lesson 24 - Flows and Messages (Sequence Diagrams in Text)

4 Upvotes

Hi r/systems_engineering,

We are back with Lesson 24 of our technical deep dive into the SysML v2 standard.

In our previous lesson, we used perform to say which part carries out which action. Our subsystems finally knew what they did, but they still couldn't send each other anything. Today, we fix that with flows and messages. We will explore how SysML v2 eliminates one of the biggest sync issues in v1 by unifying data, commands, and physical items across both structural architecture and behavioral interactions.

You can watch the full video lesson on YouTube here: https://youtu.be/37fV9tD-KLk

1. The SysML v1 Fragmentation Problem

SysML v1 was actually quite strong in this area, but it suffered from fragmentation. If you wanted to model movement, you used an ObjectFlow inside an activity, an ItemFlow across a connector in an Internal Block Diagram (IBD), and a Message between lifelines in a sequence diagram. Because these were three completely separate metamodel constructs, keeping your structural connections, activity data flows, and interaction scenarios consistent required manual allocations, strict modeling discipline, or custom tool validation.

2. The v2 Shift: Unification under FlowUsage

SysML v2 fixes this by unifying all three under a single foundational concept: FlowUsage (which is based on a KerML Transfer).

Instead of disconnected constructs across different diagram types, SysML v2 provides three specialized forms:

  • flow (Streaming Flow): Used for transfers between parts or actions. It explicitly names the source output and target input. The transfer can be ongoing while both the source and target are still operating (e.g., fuel moving from a tank to an engine).
  • succession flow**:** Combines a streaming flow with temporal ordering. It asserts that the source action must complete before the transfer begins, and the transfer must complete before the target action can start.
  • message**:**Used for abstract interactions (like sequence scenarios). It asserts that a transfer happens between two occurrences or events without forcing you to specify the exact port payload mechanics.

3. Sequence Diagrams as Text (Views That Cannot Drift)

Because messages and flows are unified, you can write a sequence diagram entirely in text. More importantly, a single message declaration can generate both an interconnection view and a sequence view. Your structure and your behavior can no longer disagree.

Code snippet

package CommandUplinkScenario {
    item def Command;
    item def Acknowledgement;
    item def TelemetryPacket;
    
    part def GroundStation;
    part def Spacecraft;
    
    occurrence def CommandUplink {
        ref part ground: GroundStation {
            event occurrence cmdSent;
            event occurrence ackReceived;
            event occurrence resultReceived;
        }
        ref part spacecraft: Spacecraft {
            event occurrence cmdReceived;
            event occurrence ackSent;
            event occurrence resultSent;
        }
        
        // Define the transfers (Messages)
        message ack of Acknowledgement from spacecraft.ackSent to ground.ackReceived;
        message cmd of Command from ground.cmdSent to spacecraft.cmdReceived;
        message result of TelemetryPacket from spacecraft.resultSent to ground.resultReceived;
        
        // Define the temporal sequence
        succession first cmd then ack;
        succession first ack then result;
    }
}

4. Deep Dive: Three Practical Nuances

As you start writing flows in v2, keep these three details in mind:

  • send and accept**:** Flows connect structure. But whenyou are inside a specific behavioral action, you use the send and accept keywords to push and pull payloads directly through your structural ports (e.g., accept cmd: Command via spacecraft.cmdIn;). This creates an explicit, queryable link between your behavior and your structural interfaces.
  • Sequencing is NOT flow: It is easy to mix these up. first A then B means B happens after A, but nothing actually moves (pure control). A plain flow means something moves, but adds no temporal ordering (pure data). A succession flowdoes both. SysML v2 strictly separatescontrol from data.
  • Where v1 Was Actually Better (Combined Fragments): Let's be honest—UML Sequence Diagrams had beautifully compact visual boxes for loops (loop), options (opt), and alternatives (alt). SysML v2 doesn't have a direct equivalent in the standard sequence view; you have to model that logic using decide and loop actions, which makes the text much more verbose. You will want to rely on an Action Flow view to visualize that logic clearly.

5. SysML v1 vs. SysML v2

Modeling ConceptSysML v1SysML v2
Transfer ConstructsObjectFlow, ItemFlow, and Message were three separate constructs.Unified as Flow usages (message, flow, or succession flow).
Diagram SynchronizationItem flows on IBDs and messages on Sequence Diagrams easily drifted.A single message declaration generates both an interconnection view and a sequence view.
Temporal SemanticsObjectFlow combined transfer/ordering, but ItemFlow carried no temporal semantics.flow (streaming) and succession flow (ordered) are applied uniformly between parts or actions.
Authoring InteractionsNo standard text notation; interactions were manually drawn.Messages and successions authored in text, enabling standard Git diffs and merges.
Combined FragmentsCompact, readable alt, opt, and loop visual boxes.Textually verbose using decide and loop actions (best visualized in an Action Flow view).

Next lesson, we will cover state definitions and transitions, where a state turns out to be an action, and the exhibit keyword works exactly like perform.


r/systems_engineering • • 11d ago

Discussion SAIC vs STC/Arcfield Systems Engineering

6 Upvotes

I received a remote offer to work on the Mach TB (Multi Service Capability Hypersonics Test Bed) team for SAIC. I also received a remote offer to work for STC (acquired a few years ago by Arcfield) to work as a systems engineer, but program(s) yet to be terminated. SAIC is asking 25% travel (a few times per month) where STC hasn't mentioned any travel. Which offer would you go for given same salary (STC is giving a 5K hiring bonus which will be much smaller after taxes), very similar 401K matching, very similar PTO/accrual?