Requirements and architecture
Each requirement lists the parts that meet it, in a table and a diagram, saved as a standard SysML v2 model. Link tasks and risks to the same parts, and you can see what each one is for.
Working Requirements, the architecture diagram, and linking requirements to parts. Next Linking risks to requirements.
A part's work, float and milestones
Pick a part to see the work done, in progress and not started, and the float and milestones it affects. A new cost baseline needs a reason and an approver, and the old baseline is kept.
Shipping Work, float, milestones and baselines. Next Impact traced from a requirement, with its cost and the risks it changes.
Model changes, item by item
Renaming, moving and retyping an item show up as three separate changes, rather than one block of changed text. If the list of affected items is incomplete, the screen says so.
Shipping Uncommitted changes against the last commit, and any commit against the one before it.
Ask the AI assistant
Select a part and ask about it, or ask about the whole model. Each answer shows which AI wrote it, and says if any items were left out.
Next Turning it on from Settings.
IDs that stay with the file
Every item in the model gets a permanent ID, saved in the file in the standard format. Send the file to a supplier and each item is still recognized as the same one.
Shipping
Standard files and checked units
It reads all 94 files of the SysML v2 standard library published by OMG, the standards body. Every quantity in the model carries its unit, so meters can't be mistaken for seconds.
Shipping
An audit trail, always on
Nothing is overwritten. A baseline changes only through a reviewed change.
Shipping Commits, branches, protected branches and review records. Next Signed approvals with passkeys.
Inside your network
Install the same application inside your own network, even one with no internet connection. Editing, approving and exporting make no connection outside it, and a test checks that on every build.
Shipping
The tools you already run
Import your current schedule and requirements instead of starting over. Each connector moves data in one direction, so the same data is never synced both ways.
- Shipping Primavera P6 (XER) and Microsoft Project (XML) schedules
- Working Requirements from IBM DOORS over ReqIF, the standard requirements exchange format, from the command line
- In progress Teamcenter and Windchill over OSLC
- Next Jama Connect over ReqIF, ReqIF in the browser, Microsoft Planner, CSV
- Planned Excel, Jira, SysML v2 models, IPMDAR cost reports, and accounting actuals and rates