Integrations and Interfaces
PMWeb’s 100% web-based structure allows interfaces via hyperlink to any system which has similar capabilities. System interfaces can also be achieved by a number of other means. PMWeb has several options for integrating data from existing systems. The method used is determined by several factors such as the type of data being integrated; the frequency of data exchange; and the direction of the data exchange. These aspects apply to both any up-front migration and subsequent data exchanges:
- PMWeb’s “out of the box” integration with Excel includes field mapping for data exchanges
- PMWeb’s Integration Manager toolkit item
- The PMWeb API (Application Programming Interface)
- One way exports out of PMWeb can be accomplished using Microsoft SQL Reporting Services
- Microsoft SQL Server Integration Services (SSIS) allows for more complex integrations where data transformations and direct table manipulations are needed. We have found that SSIS has been able to address most complex integrations.
We always recommend that a Client look closely at the need for an API-based integration, as well as any need for PMWeb’s Integration Manager. These two tools have an inherent cost that may or may not be warranted according to the functionality to be used in the Client’s business. Just because an integration can be done does not mean that it should be done. Business needs should drive the integration approach. In major implementations for many major clients, integration was achieved by using SSIS packages to exchange information with other Enterprise systems – either directly or using client middleware. Each alternative should be explored on a cost/benefit basis.
Our integration experience includes:
- Oracle Financials
- Timberline/Sage 300
- HP DeskSite
- Oracle Primavera P6
- Microsoft Project
- AND MORE!
PMWeb – out of the box – is compatible with a wide range of third-party software systems – read more.