KM - KNOWLEDGE Management Capability


A SMARTer way to digitalize your knowledge

KM – Knowledge Manager

KM - KNOWLEDGE Management

Knowledge is one of the most valuable assets in your organization. The key driver to success in any system or software project is to
reuse knowledge assets. These include engineers’ explicit and tacit knowledge, and guidelines defining the organizational know-how.

Knowledge should therefore be gathered from different sources, stored in secure repositories, and accessed by the appointed person at the appropriate time.

KM – KNOWLEDGE Management Capability allows you to manage knowledge from the systems engineering point of view and to store valuable information from requirements, models, system architectures, and other documents in a common System Knowledge Base.

Knowledge Manager


The more knowledge you manage in KM – KNOWLEDGE Management Capability, the more advanced analysis can be performed by SES ENGINEERING Studio’s different capabilities: RQA, V&V, RAT, TRACEABILITY, etc.


KM eases knowledge sharing and reuse activities among different engineering tools, allowing users to evolve and
update ontologies seamlessly.


Proper knowledge management is an asset for the organization that translates into earnings and savings.


Authoritative Source of Truth

KM – KNOWLEDGE Management Capability permits the creation of a specific ontology to address the full complexity of the project’s context and tackle any kind of semantic structure required.

A controlled vocabulary is a must to facilitate consistency across the different work products developed during the life cycle of a project.

Ontologies in KM help specific relationships between terms to fully represent a project’s context: synonyms, parent-child dependencies, subsystems, functional structures, etc.


The feature of creating patterns is a flexible solution to satisfy personalized preferences while writing requirements. It helps to optimize the editing process, standardize the writing approach and englobe any possible variations within the requirements specifications.

Interface with external sources

As your project knowledge can be stored in several different formats (e.g. SysML/ UML models, simulations, tables, external databases, …), KM – KNOWLEDGE Management Capability enables interfacing with several external sources so that the ontology includes multiple
sources of truth.

Managing Knowledge Repositories

KM – KNOWLEDGE Management Capability is designed to manage all the knowledge needed for your system or software intensive projects (breakdown structures, terms, acronyms, restrictions, etc.). Knowledge is stored within a System Knowledge Repository (SKR) and is organized in ontologies (called System Knowledge Base – SKB) and knowledge libraries. The Ontology and the libraries are used by the SES ENGINEERING Studio for quality analysis, Requirements, and textual work product authoring, to identify different types of link traces, transforming from requirements to models or test cases, identification of reusable products, etc.

KM – KNOWLEDGE Management Capability enables the management of the System Knowledge Repository, its System Knowledge Base, and all assets involved in the life cycle of your systems.

KM and Systems Engineering

KM – KNOWLEDGE Management Capability is the core tool for the Knowledge Centric Systems Engineering approach which aims to take advantage of all the knowledge developed during the System definition phase and thus make it available to subsequent projects.

Knowledge library

Our approach to knowledge management consists of 5 steps:


1. Fill your ontology with the domain-specific vocabulary on top of the already included generic vocabulary.

2. Build hierarchical structures and create relationships between the terms of your ontology.

3. Design the semantic structures, and patterns, that you can reuse while writing the requirements.

4. Formalize meaningful relationships between the semantic structures and the terms within them.

5. Add extra rules to facilitate the guided reasoning process within your ontology.

An example of the 5 steps put into practice can be observed on the following schema:

Ontology example

Textual patterns: standardize and rewrite requirements

Textual Patterns represent the grammatical structure that a natural language sentence needs to follow according to an organization’s policies and know-how. Textual patterns can also be used to enable text transformation. By setting up source and target patterns for a transformation, SES ENGINEERING Studio will detect requirements that match the pattern to execute the transformation to the target structure while maintaining the
semantic consistency.

KM sentence patterns

Semantic indexing and retrieval

Using Natural Language Processing tools and Artificial Intelligence algorithms, KM provides a semantic search engine that enables the search and reuse of all sorts of information based on its actual meaning.

KM semantic indexing


KM – KNOWLEDGE Management Capability provides the capability to use Knowledge Libraries: combinations of Knowledge items of different natures and levels of abstraction that can be reused in numerous projects. Knowledge management based on Libraries is the best way to blend knowledge flexibly. The REUSE Company provides a wide catalog of Libraries ready to plug and play. Our current set of libraries is:

  • INCOSE Knowledge Library: focuses on metrics defined as Quality rules in the INCOSE Guide for Writing Requirements.
  • EARS Knowledge Library: includes the catalog of patterns as defined in the Easy Approach to Requirements Syntax.
  • SOPHIST Master Patterns Library: includes all the patterns described by SOPHIST in its Master Catalogue plus 18 rules for Requirements Writing.
  • NASA Knowledge Library: includes the NASA Glossary plus the rules for writing requirements as described in the NASA Systems Engineering Handbook.
  • ECSS Knowledge Library: includes terms, patterns, and drafting rules defined by the European Cooperation for Space Standardization.
  • Requirements with Numbers Library: Including 17 metrics, dealing with the numbers used in textual requirements.
  • BABOK® Library: Including a set of Quality Metrics covering the subsequent RADD characteristics and a set of patterns applied to cover the nine RADD characteristics.


License Types

KM License Type
KM Lite
KM Full
Terminology layer:
- Terminology
- Term tags
- Languages
- Tokenization rules
- Normalization
- Disambiguation
- Advanced Import/export
Conceptual Model layer:
- Hierarchical views
- Semantic clusters
- Relationship taxonomy
- Suggestions
- Dashboards
- Advanced Import/export
Patterns layer:
- Sentences pattern
- Complex patterns
- Pattern groups
Formalization layer:
- Relationships
- Properties
Inference layer:
-Rule-Based Inference
Configuration management layer:
- Configuration management
- Changes federation
Extensibility layer:
- Import Libraries
- Generate Library
- Knowledge interfaces


Assets store layer:
- Artifacts
- Artifact types
- Artifact indexing
Settings layer:
- Users
- Active Directory integration
- Indexing
- Retrieval
Ontology Copy:
- Partial Copy
- Complete Copy