ASYST by STREaMLiNE
Start free

AI-enhanced MBSE

Your engineers are writing requirements, not engineering.

ASYST reads a project brief and produces the system model behind it: ISO 29148 requirements, functional and physical architecture, a scored risk register, a V&V matrix and an end-to-end traceability chain. Hours, not weeks.

Start free See how it works
Abstract visualisation of many traced links fanning out from a single point across a dense technical grid of charts and identifiers.

The problem

Currently, the engineers are working for the tool. They feed it, format it and cross-reference it, instead of deciding what the system should be.

Senior engineers doing mechanical work

Writing, formatting and cross-referencing hundreds of artefacts is the most expensive time on the programme, spent on the least valuable task.

Early errors propagate silently

A misread requirement or an unverified constraint travels through the whole model and costs orders of magnitude more to fix later.

Your tools store, they do not generate

Cameo, Capella and DOORS are strong repositories. They hold what engineers create. The bottleneck was never the repository.

That is backwards. The engineers deserve a tool that works for them.

The Solution

Brief in, a complete system model out. Each artefact is derived from the one before it and every link is recorded, so what comes back is not an outline: it is nine artefacts that reference each other, ready for an engineer to review and own.

  1. 01

    Upload the brief

    A project brief, a statement of work, or a concept description. Written or uploaded.

  2. 02

    The agent runs the pipeline

    Nine stages, each validated before the next begins, each artefact linked to the last.

  3. 03

    Review and export

    Every artefact is browsable and traceable. Export the Need Analysis document when it is right.

See every stage in detail

What nothing else does

Change one requirement. The model changes with it.

Edit a requirement and ASYST propagates the impact across every artefact derived from it. Gaps are flagged, not silently inherited.

Impact propagation from one requirement Requirement REQ-014 on the left, connected by five labelled edges to FUNC-021 satisfied by, FUNC-022 satisfied by, COMP-007 allocated to, VV-014 verified by, and RISK-009 drives. Changing REQ-014 marks all five as affected. satisfied by satisfied by allocated to verified by drives REQ-014 Timestamp accuracy FUNC-021 Acquire time reference FUNC-022 Stamp the record COMP-007 Onboard computing VV-014 Drift test, 45 min RISK-009 Clock drift on long patrol
One edit, five downstream artefacts flagged. The edge type is what makes the chain queryable rather than narrative.

How the agent works

Start with the brief you have open right now.

Free to start. One project, the full pipeline, every artefact, and the chain between them. Bring a brief you have already scoped by hand and see what comes back.

Start free
Next 01The Workflow

All nine stages in order, from the brief to the Need Analysis document.