To the first page:     £

Language choice:     en│ ru

To write to us:     *

According to forecast by ARC Advisory Group the EAM market will grow from 2011’ $2.17B to $3B in 2016, which represents CAGR of 6.7%. As compared to 2010, the growth represents 17.2%.

Since the market for EAM is trailing the SCM market, the majority of existing EAM clients are the ones with a large number of assets. Therefore, more than 50% of companies currently utilizing EAM are the potential clients for this product.

In 2009-2010, Gartner releases a review of EAM systems for 3 markets: Manufacturing, Power Generation, and Utilities Delivery. None of the products presented by Gartner, provide the functionality of the product being developed:

  1. They don’t solve the problem of Optimal Budget Allocation towards development of new assets and maintenance of the existing ones as well as proper allocation of such budget.
  2. They don’t contain methods of Optimal Enterprise Management through proper budget allocation towards development and asset maintenance.
  3. They don’t use large computer clusters for resource intensive calculations of imitational models of asset lifecycle.

In other words, current EAM systems represent more of maintenance execution tools. Tools of imitational modeling that are used for identification of best set of parameters for organization of Technical Support and Maintenance, although in use since 80s, are still not integrated into EAM packages. On contrary, the product being developed is a strategic management system. It performs operations of imitational modeling and optimization, and resembles more an APS product rather then EAM. However, it solves non-APS-like tasks of optimal asset management and not Supply Chain tasks.

Optimization tools represent the next level in functionality of EAM systems ahead of imitational modeling. Similar to imitational modeling, optimization methods are not packaged with standard EAM systems. If for APS modules the proposed model of combining imitational modeling and optimization techniques is long known, for Technical Support and Maintenance systems such approach is not executed.