MBSE Adoption

Featured project

Client · Rieter

The ARISE MBSE Journey

A joint SysDICE and Rieter project that connects stakeholder needs, system use cases, system requirements, software use cases, software requirements, classes and activities inside one configurable MBSE solution — with people kept at the centre of adoption.

Client

Rieter

Industry

Textile machinery / industrial engineering

Engagement focus

Simplifying MBSE in the textile industry

Status

Completed project · publicly presented

Project context

Rieter and SysDICE partnered on the ARISE initiative to make MBSE genuinely usable in the textile machinery domain — not as a heavy methodology, but as a shared engineering language teams could adopt in day-to-day work.

PROJECT PRINCIPLE “Keep MBSE simple enough to be understood over a cup of coffee.”

The challenge

Textile machinery engineering spans mechanics, electronics and software with many variants. Without a connected backbone, stakeholder needs, use cases, requirements and software structures drift apart, and adoption stalls when the method feels too abstract or too costly for the engineers who have to live with it.

What SysDICE delivered

A practical MBSE method definition tailored to Rieter’s engineering reality.
A configurable MBSE solution linking stakeholder needs, system use cases, system requirements, software use cases, software requirements, classes and activities.
Guidance and enablement centered on people — engineers and managers as part of the solution, not just recipients of a rollout.
Explicit attention to adoption cost, so the approach stays proportionate to the value it creates.

Value created

Clearer, connected engineering information across the product lifecycle.
A simpler MBSE approach teams can actually understand and use.
Greater awareness of adoption cost as a first-class design constraint.
An approach that treats people as an intrinsic part of the MBSE solution.

Capabilities applied

MBSE strategy

Method development

SysML

Modeling governance

Tool configuration

Training and coaching

Discuss a similar project

Bring your challenge — we’ll help you shape a pragmatic MBSE and AI4MBSE path forward.

Project journey

How the project unfolded

A step-by-step view of the path from framing the problem to establishing a way forward.

01

Step 1

Understand information landscape

Map how needs, requirements, use cases and software artifacts flow across the Rieter engineering chain today.

02

Step 2

Define simplified method

Shape an MBSE method that stays understandable, cost-conscious and usable by engineering personnel.

03

Step 3

Configure connected solution

Set up a configurable MBSE solution that links stakeholder needs, system and software artifacts end-to-end.

04

Step 4

Enable personnel

Coach engineers and managers on real content so people become part of the solution, not spectators to it.

05

Step 5

Establish path forward

Agree how the approach continues to evolve inside Rieter after the project — with adoption cost kept in view.

Consulting · Implementation · Training

How this project connects to SysDICE's way of working

Every SysDICE engagement blends consulting, implementation and training. Here’s how those three modes came together on this project.

Consulting

Method definition, adoption planning and governance guidance for a simpler, connected MBSE approach.

Implementation

Configurable MBSE solution linking stakeholder needs, use cases, requirements and software artifacts.

Training

Enablement and coaching that treats engineers and managers as an intrinsic part of the solution.

Have a complex engineering project to discuss?

Start a conversation — no pitch deck required. Tell us where you are and where you want to go.