Technology > Configuration

The Prognostic Report configuration process:

Given the great diversity of industrial assets and operations scenarios across the different industries, an advanced computational solution per se can never be a guarantee for accurate prognostic results in practice. A large portion of our technological strength must lie in the process of configuring our prognostic solution for different types of industrial assets, malfunction modes, and condition parameters. In fact, every Prognostic Report has its own configuration that is determined once at the outset of the first reporting period.


The formulation of condition parameters in the beginning of the configuration process is more an art than a science, possibly involving extensive discussions with resident internal and seasoned external condition experts. Yet, for standard asset types, we can provide a limited catalogue of specified and validated condition parameters to be considered. This typically allows us to provide 80% of the input for the configuration process up front, and to engage in-house experts of the operator only to a very reasonable extent.

How do we configure the solution to your needs? Contact Us

The configuration process for the Cassantec solution consists of five steps:

  • Step 1: Specify condition data
  • Step 2: Define malfunction modes
  • Step 3: Configure solution
  • Step 4: Automate data transfer
  • Step 5: Use forecasts

In the first step of the configuration process, we check whether asset units and components are truly mission-critical, and whether an advanced Prognostic Report is truly needed. We furthermore specify what kind of condition and process data is needed and make sure that the data is available.

In the second step, we define the malfunction modes most relevant for the asset, and prioritize them according to their likelihood and impact. Furthermore, we correlate the specified condition parameters to the defined malfunction modes. This step oftentimes generates immediate benefits by uncovering existing yet hidden flaws in the asset's condition.

In the third step, we configure the web-based front-end of our solution. We may use our evolving industry standards, or apply operator-specific front-end guidelines, blending the front-end into operators' in-house toolkits and IT-landscape.

In the fourth step, we automate the periodical data transfer and consolidation necessary for daily, weekly, monthly or on-demand updates of the Prognostic Reports and we set up configurations and tests.

In step five, our customers use the periodical Prognostic Reports as forecasts at asset component, unit and fleet levels. At the asset component level, forecasts support the scheduling, scoping, and efficient preparation of maintenance tasks. At the asset unit level, the forecasts are considered in life cycle and retrofit decisions. At the fleet level, the forecasts help to streamline commercial decisions.

The configuration process to adjust a Prognostic Report to operators needs: