Bear Instruments - Requirements Management

Streamline Your Requirements Management

Bear Instruments provides a modern, collaborative platform for managing requirements, specifications, and project documentation with powerful linking, versioning, and team features.

Try Demo

Four Pillars of BRMS

BRMS is structured around authoring quality requirements, governing controlled change, verifying evidence and coverage, and integrating with external toolchains.

Author

Create Structured Requirements

Capture and refine work items in a controlled, collaborative workspace.

Work item authoring with history, comments, and watch status
Relationship linking and traceability browsing across specs and work items
Project/variant context to support multi-product engineering

Govern

Control Change and Access

Define how work flows and who can approve, edit, and administer each area.

Configurable ontology: types, groups, statuses, transitions, and allowed links
Roles, permissions, and user groups with project-scoped controls
Baselines for snapshot and locked-view governance

Verify

Prove Readiness with Evidence

Surface coverage and impact signals so teams can make release decisions with confidence.

Verification coverage, change impact, and evidence dashboards
Artifact review workflows with revision comments and status transitions
Historical artifact restore and commit log visibility

Integrate

Exchange Data Across Toolchains

Move information in and out without losing structure or review context.

Excel and ReqIF import/export with preview and validation
Round-trip import support including revised import files
Local and Microsoft sign-in options for organization-managed access

Simple Pricing

Every person who uses the BRMS needs a license (a seat) at the time they use the software. There are no separate editor, reviewer or approver licence tiers. Licenses can be assigned to users as needed by administrators. A BRMS instance can have as many users as needed simultaneously but, only users with licenses assigned to them can view and change engineering data. Administrators assign licenses to users. Licenses can be assigned, de-assigned and re-assigned to other users as needed without limits. When a license is removed from a user there is a cooldown period of 7 days before a license can be reassigned to another user to avoid repeated re-assignments of a small number of licenses among a large number of users.

SaaS Monthly

Hosted BRMS

£49.95 per seat / month

For teams that want a managed service with automatic updates and no hosting overhead.

Automatic Updates
Switch to annual pricing at any time
Monthly and Annual licensing can be mixed on the same BRMS instance
Unlimited service accounts
Unlimited support

SaaS Annual

Hosted BRMS

£495 per seat / year

A lower annual SaaS rate for teams that already know BRMS will be part of their core toolchain for the subscription term.

Automatic updates
Equivalent to just over two months free versus monthly pricing
Monthly and Annual licensing can be mixed on the same BRMS instance
Unlimited service accounts
Unlimited support

On-Premises

On-Premises (Self-Hosted) BRMS

£695 per seat / year

For organizations that want the same subscription model deployed inside their own environment rather than hosted in the cloud.

Updates supplied for deployment periodically
Run the BRMS on your own infrastructure and inside your own control boundary
Unlimited service accounts included
Unlimited support
Multiple deployment options available e.g. for different security levels or different business units, licenses can not be shared across deployments, however.

What counts as a seat?

A seat is needed by a person who signs in to perform work on engineering data held in the system. It does not matter whether that person mainly authors, reviews, approves, or does a mixture of those activities. One person uses one seat. Administrators can create as many users as needed but only users with licenses (a seat) assigned to them can sign in. Licenses can be reassigned to other users as needed. There is a cooldown period of 7 days before a license can be reassigned to another user.

A service account is an account used for administrative setup and platform management tasks such as creating user accounts, roles, user groups, projects, ontologies, and variants. Customers can create as many service accounts as they need. Service accounts are free of charge.

Service accounts are not for day-to-day engineering work. They cannot view or edit work items, change work item status, create links between work items, or view or edit documents and other engineering data within a project.

Demo Information

Use the demo as freely as you need for evaluation.

You can create as many demo accounts as you want at the same time, whether for different users or for one evaluator to simulate several roles.
You can also create as many demo accounts one after another as you want, so you can keep extending your evaluation if needed.
We will not pester you with emails.
The demo BRMS instance includes part of an automotive traction inverter developed following MBSE principles.
Any data you put into the demo should be treated as public.
The demo server is reset to its original state at midnight UTC each day and no demo data is retained.
Demo accounts are automatically deleted after 30 days.
Demo users can create their own projects, ontologies, variants, baselines, work item types, work items, documents, drawings, status models, transitions, and linkage rules, and can otherwise exercise the software much like a paid user.
There are no feature limits on demo accounts apart from user and access administration: demo users cannot view the user list, access the user-management menu, create, edit or delete users. Demo users can not edit or delete existing roles or user groups.

Try Demo

Talk To Us

If you want to discuss licensing, deployment options, or a commercial rollout, contact Bear Instruments directly.

Contact Bear Instruments