Fixed-price pilot
Your system, modelled in SysML v2, in two weeks.
Send us what you have. We use MBEstudio and its agents to turn it into a checked SysML v2 model with traced requirements and a safety analysis, and we hand it to your team ready to use. One system, one fixed price, ten working days.
What you get
Six things, on day 10
Architecture
Your system broken down into parts, ports and typed interfaces, with mass, power and cost budgets that roll up and check themselves.
Requirements, traced
Requirements written in EARS form, each linked to the part that satisfies it and the check that verifies it. Exported to ReqIF for DOORS.
Safety analysis
An STPA pass on the model: losses, hazards, control structure and unsafe control actions, with the constraints written back into the model.
3D view and diagrams
The model shown as a 3D layout plus the diagrams reviewers expect: block, internal block, activity, sequence and state.
Review pack
A PDF report with the budgets, open issues and violated constraints, generated from the model, so it matches it.
Your files
The SysML v2 source in your Git repository, plus Cameo XMI and ReqIF exports. You own all of it.
How it runs
Two weeks, three calls
Day 1
A 60 minute kickoff. We agree the scope in writing: which system, which level, what done means.
Week 1
We build the architecture and budgets from what you sent and show it to you on a 30 minute call by day 5. You tell us what is wrong.
Week 2
Requirements, traceability and the STPA pass. We fix what you flagged and run the checks.
Day 10
A 60 minute handover: the model, the review pack, and a walk through how your team keeps it up to date.
The pilot
Fixed price. Half when we agree the scope, half on delivery.
- One system or subsystem, scoped in writing on day 1
- Ten working days from kickoff to handover
- Three calls: kickoff, day 5 review, handover
- You own the model and every file
A good fit if
- Your requirements live in documents and spreadsheets, and nobody can say which part each one lands on
- You are moving to SysML v2 and want one real model to judge it by, not a vendor demo
- You need a safety analysis that stays tied to the design as it changes
- You want to see what AI agents can do on your own system before you buy seats
Not sure yet? See it on our own models first: the sixth-generation fighter, the electric vehicle or the full demo.
FAQ
Common questions
What do you need from us?
A short description of the system and whatever you already have: a spec, a spreadsheet of parts and budgets, an interface list, an old Cameo or SysML v1 model, or CAD exports. Nothing has to be clean or complete. We need about two hours of an engineer's time across the two weeks.
Do we have to buy MBEstudio afterwards?
No. You own the model and every file we deliver. It is plain SysML v2 text in a Git repository, so it opens in any SysML v2 tool.
Can you work with export-controlled or proprietary data?
Yes. We can run MBEstudio on your own machine or network, offline, with a local model, so nothing leaves your site. Tell us on the scoping call and we will set it up that way before any data moves.
How is it paid?
Half when we agree the scope, half on delivery. We invoice, so a purchase order or a card both work.
What if our system is bigger than two weeks?
We pick one subsystem or one level of the architecture that matters most, model it properly, and show you what the rest would take. Most teams start with the part that has the most open questions.
Start with a 30 minute call
Tell us about the system. We will tell you what the pilot would cover and whether it is worth doing. The scoping call is free.