Demos
Watch it work
Short narrated recordings of OpenV at work on its sample product, a desktop CNC mill in fifteen projects, on a computer and on a phone. Each one has captions and a transcript.
Getting started: a new project, start to finish
A coolant system added to the Desktop CNC Mill: a project filed under the mill, its first requirement, the link to the mill requirement it refines, then the test, the plan and a baseline.
Transcript
This is OpenV. Each product, and each part of a product, is a project. Here is the Desktop CNC Mill: fifteen projects, from the whole machine down to its motors and its software.
A project opens on its overview: what the product is for, who it is for, the limits it has to work within, and how you will know it has succeeded.
In this video we add something the mill does not have yet: a coolant system, with a project of its own under the mill.
Create a project, and file it under the mill. Its requirements can then refine the mill's, and its test results will count toward them.
A line of description, and the project is ready.
Its first requirement. Each one is an artifact: a requirement, a user need, a design item, a hazard or a test case.
Give it a title and say what the system shall do, in a way somebody could test.
It gets a reference that never changes, R E Q one, and a wording score. One hundred: it uses shall, names a number, and has nothing vague in it.
Now link it to the mill requirement it refines. The search reaches the parent project, so pick the mill's requirement that keeps chips and coolant inside.
Add the link and save. The trace now shows one link up, to the mill's requirement number twelve, in the Desktop CNC Mill project.
And in the mill's project, that requirement now lists the coolant system's among the requirements that refine it. When the coolant tests pass, the mill's requirement will count them.
The next steps are the same in every project. Add a test case that verifies the requirement, and record its results in a test run on the V and V page.
Plan the work on the Gantt: tasks, milestones and the reviews they lead to, and link a task to the mill's plan where the mill is waiting for it.
And when the requirements are agreed, capture a baseline, so you can show later exactly what was agreed and what has changed since.
That is the whole loop: define, link, verify, plan and baseline. The short videos on the demos page go into each one in turn.
One feature at a time
Requirements and the project tree
The Desktop CNC Mill's requirements in OpenV: the table and the tree, a requirement with its reference, attributes and links, and the wording check.
Transcript
This is the Desktop CNC Mill, a sample product in OpenV. Its requirements, user needs, hazards, design items and tests all live in one project.
The line along the top counts them: how many are traced, how many are verified, and how many have a wording problem.
Open a user need, and the panel on the right shows its text, its reference, and every requirement that derives from it.
This requirement says how accurately the mill must position the tool. Its reference, R E Q two, stays the same however often the text changes.
Further down are its links: the need it comes from, the test that verifies it, and six requirements in the frame, motion and control projects that refine it.
The coloured score is the wording check. It reads each requirement against the shall convention and marks weak words and anything that cannot be tested.
Switch to the tree to see the same project as an outline, heading by heading.
Everything here is versioned, so you can see what each requirement said at any point, and compare two baselines of the whole project.
The plan, the Timeline and All projects
The Desktop CNC Mill's plan in OpenV: phases and milestones on the Gantt, the Timeline, and every project of the programme on one chart with the links between them.
Transcript
Every project in OpenV has a plan. This is the Desktop CNC Mill's: six phases, from the first requirements in January 2026 to the production release in December 2027.
The red line is today. The phases before it are done, the detailed design is part way through, and the bars show how far each task has got.
Each phase ends at a milestone. A milestone can wait for more than its tasks: the critical design review counts as met only when every requirement has a design item that satisfies it.
The Timeline draws the same plan as a line of phases, which is the view to show at a review.
The mill is one of fifteen projects. Its frame, motion, control, enclosure and safety system each have a project, and so do their parts. The workspace's Plan page puts every one of them on one chart.
A project that belongs under another is listed beneath it, so the chart reads as the product does: the mill, its assemblies, and their parts.
Choose a level of detail to show each project's tasks as well as its phases.
Below the chart are the links between projects. The motion project cannot integrate its parts until each motor and drive has been handed over, and the mill's alpha build waits for every assembly.
When a part slips, the link shows it in red, and you can see which assembly and which milestone it puts at risk.
Verification: test runs, coverage and flow-up
A test run recorded in the mill's control software project, and its failing result showing on the requirements of the control and of the mill above it.
Transcript
This is the V and V page of the mill's control software. It shows how many requirements are traced to a test, how many have passed, and what is still missing.
The software team runs its automated suites every night on a host build. Each night is a test run.
The run lists every test case of the project, with the requirements each one verifies and the version of the test that is being run.
The G-code conformance suite passed: four hundred programs, each parsed and planned as the reference says.
The planner's unit tests failed. A corner was cut more than three microns inside the programmed path.
Complete the run, and the page counts the result against the requirement it verifies. Look-ahead is now failing.
One level up, in the Mill control project, path accuracy is failing too. Its own contouring test has not been run yet, so its result comes from the requirement that refines it, and that one failed.
And at the top, the mill's own positioning accuracy requirement, and the one for running standard G-code, show the same failure, two projects away from the test that found it.
So a review of the mill sees a problem in the firmware as soon as the nightly run records it, and can follow it down to the test.
Baselines, changes and documents
A baseline of the Desktop CNC Mill before a review, a changed requirement and the links it flags, the comparison of the two, and a specification downloaded from the baseline.
Transcript
Before a design review, freeze the project as it stands, so everyone reviews the same thing and you can see later what changed.
That is a baseline: every requirement, link and attribute, as they were at that moment. Nobody can change it afterwards.
After the review, the noise limit comes down from seventy-five decibels to seventy-two.
The change flags every link from that requirement as suspect: the need it comes from, the enclosure and motion requirements that refine it, the design that meets it and the test that checks it. Someone confirms each one, or changes it to match.
The Baselines page compares the review's baseline with the project now: one requirement changed, its old and new wording side by side, and the links it left suspect.
The full comparison covers the whole project, artifacts, links and the plan, so a review can see exactly what moved since it last met.
A specification downloads as a PDF or a Word document, from the live project or from any baseline. JSON, CSV, Excel and ReqIF are there too, for a spreadsheet or another requirements tool.
Choose what goes in, such as which sections, artifact types and fields, then download it.
Every format is available on every plan. Your data is never behind a paywall.
On a phone
Reviewing, approving and following the plan with a thumb.
Review and approve from your phone
The Desktop CNC Mill's requirements on a phone: a requirement with its trace, sent for review, and approved from the review queue.
Transcript
OpenV works on a phone. This is the Desktop CNC Mill's requirements list, with each artifact's reference, status and trace.
Tap a requirement to read it in full, with its quality score and the requirements in other projects that refine it.
Its trace and its verification follow below, the same as on a computer.
When it is ready, send it for review. The reviewers are notified on their own phones.
The review queue lists everything waiting: requirements in review, links flagged as suspect, and changes since the last baseline.
Approve it with a thumb. The approval goes into the requirement's history with your name and the time.
Install OpenV from the browser to your home screen, and notifications arrive as pushes.
The plan and the board on your phone
The Desktop CNC Mill's plan on a phone: the milestones and their criteria, the schedule, the board column by column, and what needs you.
Transcript
The mill's plan on a phone: how far it has got, how many tasks are done, and how many are late.
Each milestone shows whether it is met. The first two reviews are, and the critical design review is a quarter of the way there.
The schedule lists every phase and task with its dates and progress, in order.
The board shows one column at a time.
Move along to the work in progress: the detailed design, the verification plan and the long-lead parts.
And Home lists what needs you across every project, so a review or a failing test is never more than a tap away.
Try it on your own project
A free account takes a minute. Import a ReqIF or JSON export, or start from a template and let the guided definition ask the questions.
