Model-Based Systems Engineering (MBSE)​

Occam’s Model Based Systems Engineering suite is the only solution of its kind.

Model-Based Systems Engineering (MBSE)​

Occam’s Model Based Systems Engineering suite is the only solution of its kind… 

Elegant Simplicity

Occam’s Razor, AKA the  “principle of parsimony”, asserts when attempting to explain a phenomena, “entities must not be multiplied beyond necessity”.  Most people hear Occam’s Razor expressed as: “The simplest explanation is usually the best one”.

Occam’s Systems Modeling tool is called “Razor” because it was designed with this tenant in mind. Because its design was driven by this principle, users find the following to be true of Razor:

  • maximizes the density of knowledge in systems models
  • maximizes the productivity of modelers
  • minimizes the effort required to learn the language 
  • minimizes the difficulty of accessing knowledge in systems models from other tools

Open Platform

In addition, to minimize operating cost, Razor is a 100% web-based client with cloud compatible infrastructure. To facilitate integrations, Razor stored models in GitHub/GitLab and serializes model content using W3C RDF Linked-Data.

Knowledge Re-Use

Razor was also designed from the ground-up to support “Pattern-Based Systems Engineering” (PBSE). Razor supports PBSE by allowing users to use it to effortlessly create and publish re-usable system model constructs (patterns) via the same user interface used do build systems models. Conversely, from this interface a user can browse and draw from the universe of patterns created via other Razor users. Last to ensure easy secure, easy access to models and patterns, Razor stores and version manages its models in GitHub/GitLab.

Elegant Simplicity

Occam’s Razor, AKA the  “principle of parsimony”, asserts when attempting to explain a phenomena, “entities must not be multiplied beyond necessity”.  Most people hear Occam’s Razor expressed as: “The simplest explanation is usually the best one”.

Occam’s Systems Modeling tool is called “Razor” because it was designed with this tenant in mind. Because its design was driven by this principle, users find the following to be true of Razor:

  • maximizes the density of knowledge in systems models
  • maximizes the productivity of modelers
  • minimizes the effort required to learn the language 
  • minimizes the difficulty of accessing knowledge in systems models from other tools

Open Platform

In addition, to minimize operating cost, Razor is a 100% web-based client with cloud compatible infrastructure. To facilitate integrations, Razor stored models in GitHub/GitLab and serializes model content using W3C RDF Linked-Data.

Knowledge Re-Use

Razor was also designed from the ground-up to support “Pattern-Based Systems Engineering” (PBSE). Razor supports PBSE by allowing users to use it to effortlessly create and publish re-usable system model constructs (patterns) via the same user interface used do build systems models. Conversely, from this interface a user can browse and draw from the universe of patterns created via other Razor users. Last to ensure easy secure, easy access to models and patterns, Razor stores and version manages its models in GitHub/GitLab.

System Modeling

Systems Modeling via completely web-based tool that automates a novel modeling language called Systems Fractal Notation (SysFN). SysFN is already beyond where the next-generation SysML 2.0 wants to be.​
Learn More

Navigating Threads​ of Knowledge

Let the modeling tool automatically layout the system model diagram (as you model). With just a few clicks… collapse or expend areas of a systems model diagram, create a diagram of an entire system, reduce a diagram to path of causality, and much more.​
Learn More

Requirements Management

Take “Pattern-Based Systems Engineering” (PBSE) to the next level by asking the toolset to “Auto-Allocate” system roles to a library of real-life assets. Then ask the toolset to generate an end-to-end simulation based on use of those (or other permutations) of assets. ​
Learn More