Support MES Quality Commander® (MQC)

What is MQC?

MES Quality Commander® is a monitoring and management tool for the comprehensive quality assessment of model-based software development. User-friendly visualizations, evaluations, and data capturing assist the user to assess the current quality of artifacts and provide a status overview of the overall project quality. In addition, MQC shows the quality trend, which provides information about the progress of the project. MQC can be seamlessly integrated into any development environment or Continuous Integration.

Highlights in MES Quality Commander® (MQC) v.5.0

MQC supports GIT as a source of data. Custom filter options can be used to preselect relevant data.

Differences in the quality and availability of data between revisions are calculated and shown in the new “Diff” view.

Quality bins are user-configurable in name, number, thresholds, and color-scheme for convenient adaptation.


MQC v.4.5

Highlights in MES Quality Commander® (MQC) v.4.5

Get your quick project overview via the new dashboard.
Configurable tiles show you exactly the information you need for a first yet thorough impression.

Action priorities with multi-level dependencies to quality properties are calculated with the help of fuzzy rules.

Additional tool adapters are available.

MQC v.4.4

Highlights in MES Quality Commander® (MQC) v.4.4

MQC now recommends actions to resolve quality deficits within a project via action lists. The new action list is sorted according to priorities to help you identify the most urgent actions to be taken next. You can find an overview of these actions on the new action list page.

Profit from the usability improvement of reports in MQC. You can open the reports which were used to import the data, directly with MQC. In addition, you have access to a human-readable report (e.g. HTML or PDF), if available.

MQC v.4.3

Highlights in MES Quality Commander® (MQC) v.4.3

A generic tool adapter API allows easy custom adapter implementation using C# or Python. Templates for adapters reading common report formats like xml, html, and xls are available. The existing pool of adapters has been further extended by adapter for Danlaw MxSuite, Testwell CTC++, and Helix QAC.

MQC v.4.2

Highlights in MES Quality Commander® (MQC) v.4.2

Significant reduction in import time and memory usage
The reduction is especially notable when dealing with very large sets of data. It applies to the import of data directories, as well as the live monitoring and reimport of updated data.

Improvement of import time in MES Quality Commander

Improved user experience
Selections and markings relate in a more intuitive matter. They allow the smart adaptation of views with simple one-click actions.

MQC v.4.1

Highlights in MES Quality Commander® (MQC) v.4.1

Improved Configuration Dialogs
MQC settings dialogs have been redesigned for better usability, and are available in MQC editor as well as MQC web viewer.

Fine grained configuration of Context Categories
Context categories define the relations between artifacts and data sources, measurements, and base measures. They help to define and focus on the artifact-relevant data from the available data pool.

MQC v.4.0

Highlights in MES Quality Commander® (MQC) v.4.1

Report generation project status
The new status report in html format documents all details of an MQC project, including graphics and context-specific tables to structure the information. The structure and extent of the report is configurable.

Configure expected data via context categories

Improved tool adapter and tool page for Polyspace (The Mathworks)

Extended tool adapter for TPT (Piketec)



MQC Editor:

  • Extract the MQC zip file ( into a target folder with write access.
  • Navigate to the …\TIB_sfire-analyst_7.11.0_win\Products\TIBCO Spotfire Installer\ directory
  • Execute the setup file (.exe)
  • Follow the installation instructions provided by the MQC User Guide.


Update to the Latest Version

MQC Editor:

  • On startup choose to login to the MQC Server instead of working offline.
  • In case of available updates, you will be automatically prompted to update.
  • Confirming the update will install the latest version of MQC.

For further information, please, check the installation instructions provided by the MQC User Guide.

System Requirements

The following system requirements must be in place to use MQC:

MQC Editor:

  • Windows (7 + 8 + 10 - 64-bit versions)
  • Microsoft .NET Framework 4.6 (or higher)
  • Microsoft Office 2010 (or higher)

Read more about detailed hardware requirements in the MQC User Guide.

Quick Start

The MQC User Guide includes a Quick Start Guide, which gives you an introduction into the functionality of the MES Quality Commander®. It shows you how to use MQC to analyse your project quality and data. In detail you are guided, how to:

  • Create a new analysis
  • Load your data into MQC
  • Configure MQC according to your project needs
  • Check trend and status of your project KPIs and quality
  • Identify root causes of insufficient quality

The data used for the Quick Start Guide can be downloaded as MQC sample data (zip file).


If you have any suggestions to help us improve the MES Quality Commander® (MQC), please do not hesitate to contact us:

User Instruction

User Guide

The MQC User Guide presents clear instructions on how to work with the MES Quality Commander® (MQC). It provides users with information about getting started and working with MQC.

MQC User Guide

You can easily call the User Guide (PDF format) by clicking on “Help” > “User Guide for MES Quality Commander” in the menu.

Additionally, by clicking on any of the “Help” icons within the tool you will be directly lead into specific chapters resp. sections of the User Guide (HTML format) (see image).

MQC Related Videos


Release Notes - MQC v.5.0 (March 2021)

Git as Source for Data (Beta)

  • MQC can use Git as a direct source for data files. By configuring the Git server, user, and repository now all commits are available as a source for data files.
  • Filters are available for commits, tags, author, directories, and files. These filters can be include or exclude. Simple text pattern up to full regular expressions can be used for defining the filters.
  • An option in settings allows the user to use the commit date and time of data files instead of the date inside the report file. The report date and time is set as default.
  • Employing the current functionality all data files can be directly taken from the version control system. In addition, the analysis by MQC can be constrained to a defined set of commits, directories, files depending on the project and what is needed.
  • MQC detects updates in the Git repository. The user is notified to refresh the data. If configured, the refresh happens automatically. Depending on the update setting these changes are employed automatically or by manual trigger.

Calculation and Visualization of Quality Differences

  • MQC now directly calculates and visualizes the changes/differences in quality and availability between revisions. The comparison base can be selected and separate Diff pages are available to visualize quality and availability changes/differences.
  • Diffs can be calculated in comparison to the previous revision or previous milestone. It is also possible to compare all revisions with a specific revision.
  • Separate Diff pages are available with difference specific visualization adaptions. These pages use percentage points to make the kind of changes clear. There is differentiation between positive (+) and negative (-) changes/differences. The titles of the visualizations describe the nature of the visualized data.
  • A Diff page is shown for a specific page (e.g. Quality Status page), when choosing "Show Diff View" in the Action Panel. Diff pages can also be managed via the "Manage Pages" menu.
  • The difference calculations and visualizations depend on the filter panel selection.

Quality Bin Configuration

  • The quality bins used on quality pages of MQC can be configured by name, color, and the used quality boundaries/thresholds. The number of bins is flexible. In this way a project might use specific names instead of good/acceptable/bad and the respective colors green/yellow/red.
  • An optional new sheet to define the parameters of bins is available in the Quality Model configuration. These parameters are used throughout all quality pages. The previously used configuration is still the default configuration in MQC.

Tool Adapter for TPT HTML Report Added

  • A TPT tool adapter for the TPT HTML overview report was added. The TPT HTML adapter produces the same measures as the XML adapter (on the same project).
  • The (structural) coverage (model coverage or code coverage) information is taken directly from the HTML overview file (if available).
  • The Requirements Status and Requirements Count are read from the HTML file, if a requirements section is available (requirements.html). The requirements covered by test cases (Testable Requirements with Test Cases) and assesslets (Testable Requirements with Assesslets) are counted.
  • The provided Quality Model for TPT was extended to refelect the new measures and quality properties.

Tool Adapter for TargetLink Code Coverage HTML Report Added

  • The TL Code Coverage adapters reads the base coverage measures (total/reached/unreached branches) and the already calculated code coverage measure for statement and branch/decision coverage. Only the overall values of each HTML report are read.
  • The TL Code Coverage Quality Model contains quality properties for the supported code coverages.

Tool Adapter for Simulink Design Verifier HTML Report Added

  • The Objectives Count results can be read from the SL Design Verifier HTML report.
  • A quality property SL Design Verifier Compliance is contained in the SL Design Verifier Quality Model taking into account the number of Passed and Failed objectives.

Tool Adapter for MXAM Excel Report Files Extended

  • If the report contains data of multiple subsystems of the same artifact, then these are aggregated. Possible measurements (documents or objectives) are taken into account.

Extended Quality Model Suggestions

  • The provided Quality Models for TPT, Embedded Tester, and MTest were extended to be as similar and comparable by quality properties as possible.
  • The provided Quality Model for PolySpace was extended by more measures and the accompanying quality properties.

User Experience

  • The Report Generation was extended to contain an artifact specific quality heat map (in the complete variant). This provides artifact specific sub/characteristics and overall quality at the same time.
  • The Project Quality Heat Map in the Report output was improved with more labels inside the tiles and a more even scaling of the tiles to enhance readability.
  • On the Dashboard the Project Information tile now includes the number of artifacts. The layout of this tile was optimized to improve readability on smaller screens.
  • The Setup Configuration includes the new settings (use Git report time, diff revision base, and the Git data sources including filters and patterns).