Touchstone
MBSE Consulting CATIA Magic Resource to formalize an engineering framework and keep models true to it. Touchstone implements the MB²SE method, Model-Based Model-Based Systems Engineering, by Dominique Ernadote (MB²SE: A Theoretical Foundation for Systems Engineering, habilitation à diriger des recherches, Université Paris-Saclay, 2020).
A touchstone is the stone on which an assayer rubs a metal and reads the streak against a standard alloy. The framework you formalize is the standard; the model's maturity is the streak.
It ships the Touchstone Profile and its customization, and a plugin that keeps a model consistent with the method while it is being built.
Who it is for
Touchstone serves engineers who formalize an engineering framework as an Enabler in CATIA Magic, and the modellers who build models under that framework.
Where to start
A project adds Touchstone with Declare the dependency. A project built on version 3 of the method reads Migrating from MB2SE 3.
Touchstone builds on two other products, and the pages here state only what Touchstone adds. Forge builds and publishes the resource, and its documentation lives at https://www.mbseconsulting.com/docs/forge/latest/. Anvil supplies the auto-stereotyping engine, the event trace and the logging the plugin relies on, and its documentation lives at https://www.mbseconsulting.com/docs/anvil/latest/.
What the plugin does
A modeller draws ordinary UML, and the plugin applies the Touchstone stereotype the model already implies. The method then holds without anyone having to remember it.
| A | owned by | referring to | receives |
|---|---|---|---|
Property | a «Concept» | a UML PrimitiveType or an Enumeration | «Attribute» |
Property | a «Concept» | a «Concept» | «Relation» |
CallBehaviorAction | a «Step» | a «Step» | «StepAction» |
All three read ownership, not how the element was drawn. An association end that the tool leaves on the source Concept is a property that Concept owns, so it qualifies — which is how a SysML part property is built. The far end, owned by the Association, does not: a directed association says the opposite end has no such feature, and the rule does not assert what the modeller declined to.
The rules only ever add. Removing «Concept» from a Class never removes «Attribute» or «Relation» from its properties, because withdrawing a stereotype can destroy work done by hand.
Each rule has a switch in Options → Project → Touchstone, enabled by default and present only in projects carrying the Touchstone Profile. See Control the auto-stereotyping rules.
From an Enabler's context menu, Tools › Generate Maturity Report… writes a self-contained HTML page with the engineering findings and the modeling completeness of the model against that Enabler.
The Touchstone Validation library adds 38 validation rules, in five suites, that check a model against the MB²SE method. See Check an Enabler.
What the profile carries
A framework is formalized as one «Enabler», or several, each holding four packages:
| Package | Holds |
|---|---|
| «ObjectivePackage» | «Objective»s, each Approved, Postponed or Rejected, with a rationale and a priority |
| «OntologyPackage» | «Concept»s with their «Attribute»s and «Relation»s, each traced to an Objective by «JustifiedBy», and the «ModelingRule»s and «EngineeringRule»s constraining them, and computes each Concept's individuals from its mappings |
| «ImplementationPackage» | «ConceptMapping», «AttributeMapping» and «RelationMapping», which bind the ontology to UML or SysML, and «MaturityRuleImplementation», which binds a rule to a tool validation rule, each linked by «Implements» |
| «ProcessPackage» | «Step»s, the method's modeling activities, calling one another through «StepAction»s |
The Touchstone Profile states every stereotype, tag and derived property. Touchstone and the MB²SE foundation says why the profile is shaped this way.
The method in brief
Objectives: What problems does the framework need to solve? What must engineers be able to do, produce, communicate, and verify? Everything starts here, not with a tool or a language, but with your engineering reality.
Ontology: What are the concepts, relationships, and rules that define your engineering reality? How do you model it in a way that is consistent, complete, and unambiguous? This is the foundation of your methodology. The common vocabulary of concepts, relationships, and semantics that your organization will need to achieve objectives. This is what gives the framework its coherence, every team, every project, speaking the same language. Every concept in the ontology traces back to an objective. If it doesn't, it's out of scope, because a concept that serves no engineering objective is modeling effort that produces no value.
Maturity: A model is not a static artifact, it evolves alongside the system development, growing in depth and completeness as engineering progresses.
Maturity rules are defined at the ontological level. Modeling rules must hold for every individual before a model counts as complete; engineering rules yield a ratio, such as a coverage, that is read as a finding. Each rule is written in the Touchstone expression language over the ontology's Concepts, Attributes and Relations, and shows passing, failing and score in the tool. Together they let your projects assess where the model stands at any point in time: what's been defined, what's missing, and what's consistent. Not a binary pass/fail, but a graduated view that tracks model quality as a proxy for system development progress.
Implementation: Where the framework becomes real in the tool. The ontology maps to the language and customizations, maturity rules become validation rules, and the modeling experience is shaped through automations and UI customization. Every implementation choice opens or closes doors: it determines what your engineers can express, how they navigate the model, and how intuitive the daily experience feels. A poor mapping can make the right thing hard to do and the wrong thing easy. This is where framework design becomes craft, each decision weighed against the objectives to ensure models produce value, not friction.
Processes: The practical guide for your engineers: how to perform each supported SE activity in a model-based environment, using the tool artifacts produced by Implementation, customization, automations, templates that make the framework tangible in daily work. All traced to your internal processes and Systems Engineering standards.