Integrating Your EA Tool: Penny wise or pound foolish?

Integrating Your EA Tool: Penny wise or pound foolish? 1024 392 ins·pi

STOP Integrating Your EA Tool

Top 5 Integration issues companies face today

The sales pitch sounds so appealing. “Pay for only what you need.” And then there’s the reassurance that “you can add any other capabilities whenever you need them.” But is going the integration route with your EA tool really the best approach?

Let’s take a look to the top 5 issues presented when integrating your EA tool with other apps. You may find that a unified approach, that includes planning and operational data across different disciplines contained within a single repository, just may prove more beneficial.


When you take the integration approach, you’re never completely done with installing, testing, and configuring your EA tool. Once you’ve identified a need for additional EA capabilities, the task of implementing the new integration has begun. Identifying the specific integration that meets your needs takes time. Identifying an integration professional to work with takes time. Getting the internal budget and approvals for the integration takes time. And the actual installation, testing, and integration all take time. You hope that the installation doesn’t disrupt operations, but inevitably it does. Then time must be spent on maintenance.

In contrast to this, turning on additional capabilities in our ServiceNow-native applications UPM·X and Designer takes considerably less time. There is no need to evaluate potential applications or contract with an installation professional. Less time is needed for planning and testing since you know there won’t be any compatibility issues between apps.


Integration is not simply about connecting one tool to another; more importantly it’s about enabling a new business processes or automating an existing one. For an integration to be successful, you must anticipate every potential scenario and interaction—including edge cases. You also have to consider data consistency as that data moves among the various applications in the integration. Mapping these relationships and testing them out requires significant planning and attention in order to ensure your EA tool continues to operate smoothly.

With UPM·X and Designer being native to ServiceNow there is no question that the new capabilities will work seamlessly with your installed base and current configuration.


You will probably have to coordinate your new integration between multiple systems and among many teams. Key questions like “Who owns what data?” and “Who can see the data that is being exchanged?” will come up and need to be resolved.

By adding functionality to your already-established EA tool via UPM·X and Designer you avoid disrupting relationships between systems and teams. Our solutions use ServiceNow’s authentication and authorization features keeping your access rights and ownership transparent and in-place.


After you’ve launched your new integration, what happens over time as systems and the API update? What happens when you add or change a field? Will your automated business processes break? How will you be able to maintain your EA tool’s functionality and data consistency? Perhaps more importantly, who will take care of maintaining your EA tools integrations?

With UPM·X and Designer there is no maintenance effort!


The money paid for the additional apps and installation are just two of the costs you bear when taking the integration approach. You will also have the costs associated with diverting operational resources and personnel so that they can work through the integration process. And then there’s the additional, ongoing cost of maintenance with each additional app integration and vendor.

Once all the associated costs are estimated, the true cost of the integration approach can look something like this:

Clearly, the integration approach is not as economical as it first appears.

The wisdom behind using a unified app approach

The integration approach to managing your EA tool presents a number of challenges that are easily overcome by installing a unified app like our ServiceNow-native applications UPM·X and Designer.

There may be cases where the benefits of an integrative app outweigh the challenges presented in its deployment. For the majority of instances this won’t be the case and the organization will end up needlessly spending their scarce and valuable resources on managing integrations, instead of driving enterprise change for their stakeholders.