When engineering processes need clarity
Make project and engineering processes clearer, more structured and more useful through process architecture and practical MBSE guidance.
- Are roles, activities and expected outputs understood differently across your project?
- Are models being created, but not consistently used for reviews, decisions or delivery outputs?
- Is traceability between requirements, architecture models and engineering artefacts difficult to maintain?
- Are modelling conventions, templates and review expectations unclear?
- Is MBSE adoption focused on tools, but less clear on process, artefacts and delivery value?
If these questions are familiar, the issue may not only be modelling skill or tool configuration. The engineering process itself may need to be made more explicit.
I help organisations define and improve how engineering and architecture processes are performed using process architecture, modelling guidance, traceability and practical MBSE approaches.
What are you looking for?
| Process modelling | Getting started with MBSE Arcadia | Capella hands-on exercise |
|---|---|---|
| Make engineering processes clearer by modelling roles, activities, artefacts, responsibilities, traceability, reviews and toolchain support. Best for organisations, consultancies and teams trying to make engineering or architecture processes more explicit and reviewable. Best for: organisations, consultancies and teams trying to make engineering or architecture processes more explicit and reviewable. | Understand the Arcadia method and how it supports model-based systems engineering, from operational analysis towards system architecture. Best for engineers and practitioners learning how Arcadia structures MBSE thinking. Best for: engineers and practitioners learning how Arcadia structures MBSE thinking. | Learn Capella through practical examples that show how Arcadia concepts can be applied in a model-based engineering tool. Best for practitioners who want hands-on modelling examples in Capella. Best for: practitioners who want hands-on modelling examples in Capella. |
| Explore process modelling | Explore Arcadia guide | Try Capella exercise |
What makes process architecture different?
| It makes engineering work visible Clarifies roles, activities, artefacts, dependencies, review points and decision points. | It connects process and artefacts Shows how requirements, models, templates, decisions and delivery outputs relate to each other. |
| It supports MBSE beyond tools Defines modelling expectations, traceability, templates and review guidance. | It helps identify improvement opportunities Makes unclear handovers, duplicated information and toolchain gaps easier to see. |
From process documentation to process architecture
Engineering processes are often described in documents, spreadsheets, flowcharts or review templates. These are useful, but they do not always show how the process works as a connected system.
A model-based process architecture can make the process more explicit by showing:
- who performs the activities;
- which artefacts are produced or consumed;
- what information is exchanged;
- where review or update loops occur;
- which tools, repositories or resources support the work.
This helps move the discussion from “we have a process document” to “we understand how the process is performed, supported, reviewed and improved.”
From Process Documentation to Process Modelling: A Model-Based
How I can help
I can support organisations, consultancies and engineering teams that want to make MBSE adoption and engineering process development more practical, structured and useful.
| Process architecture | MBSE adoption |
|---|---|
| Structuring roles, activities, artefacts, dependencies, review points and delivery outputs so engineering and architecture processes are easier to communicate, review and improve. | Defining practical modelling approaches, reusable templates, modelling conventions and guidance that help teams apply MBSE consistently. |
| Traceability and model quality | Mentoring and guidance |
|---|---|
| Improving consistency between textual requirements, architecture models, model elements, reviews and decision-making. | Supporting engineers in understanding how model-based approaches can be applied in a practical, reviewable and delivery-focused way. |
A practical roadmap for model-based delivery
One of the challenges in MBSE is not only creating models, but creating models that are scoped, navigable, traceable and reviewable.
A practical MBSE roadmap can help teams understand:
- which activities are needed;
- which artefacts should be produced;
- how templates support modelling consistency;
- how modelling outputs are reviewed;
- how progress can be assessed;
- how architecture decisions can be made clearer.
A practical MBSE development built on templates for clear architecture decisions
Connecting process, artefacts and toolchain
Engineering processes are often documented separately from the tools that support them. This can create a gap between the defined process, the tools actually used, the artefacts produced, repositories where information is stored, and the roles responsible for creating, reviewing or maintaining that information.
A model-based approach can help connect:
- the process being followed;
- the roles involved;
- the artefacts produced and consumed;
- the information exchanged;
- the tools and repositories required;
- the physical resources that realise the toolchain.
This supports practical decision-making. For example, it can help ask whether the toolchain supports the process people are expected to follow, whether artefacts are captured in the right place, whether review loops are supported, and whether the process can scale across projects.
Practical resources and recognised work
I created the MBSE with Arcadia step-by-step guide to support practitioners moving from textual requirements towards system design using Arcadia and Capella.
I also developed the Simple Process for Architecture Development, which describes the flow between requirements engineering and system architecture, including roles, activities, artefacts and artefact relationships. This work was recognised by the Institute for Systems Engineering at ASEC 2025. These resources reflect my wider interest in making engineering and architecture processes more explicit, structured, traceable and useful for delivery.
| MBSE with Arcadia guide | Simple Process for Architecture Development | Blog articles |
|---|---|---|
| A practical guide for moving from textual requirements towards system design using Arcadia and Capella. | A structured view of the relationship between requirements engineering and system architecture, including roles, activities and artefacts. | Practical articles on process architecture, MBSE adoption, requirements traceability, modelling guidance and architecture development. |
| Link to guide | Link to SPAD | Link to blog |
Make engineering processes more explicit
If your organisation is adopting MBSE, improving engineering processes, or trying to make modelling outputs more structured, traceable and reviewable, I can help clarify the process around the modelling work.
If this is relevant to your organisation or project, feel free to contact me to discuss MBSE adoption, process architecture or engineering process support.