ERP (Enterprise Resource Planning) Integration

You can call enterprise Web Services from Archibus -- such as downloading lists of full-time employees from HR in PeopleSoft.   In this scenario, the organization has exposed certain services as Web Services, and Archibus calls them as a Web Services client.

Conversely, you can also call Archibus from a Web Service, such as uploading monthly rent charge-backs from Archibus’s Real Property application to SAP.

This kind of ERP integration is prevalent among organizations that have adopted service-oriented architecture (SOA) to integrate a variety of systems.   In this organization, the component systems are considered based solely on the services they contract to provide, without regard for their underlying platform.  Organizations can use this integration methodology to limit the impact of change or to integrate systems that were acquired at different times, that are in use by different lines of business, or that they have brought together through mergers and acquisitions.

Remote Device Integration

You can call Archibus from remote devices, such as building controls reporting temperature and room reservation touch-screens sitting beside conference rooms. In this scenario, the remote devices call Archibus as a Web Services server.

Microsoft .Net Rich Client Integration

You can call Archibus business logic event handlers from .Net rich-client programs written by your corporate developer.  In this scenario, the rich-client program calls Archibus as a Web Services server.  Here the corporate developer wants to use Visual Studio to create the interface, but wants to re-use the built-in Archibus business logic (such as, space chargeback calculations or preventive maintenance scheduling).

Integration with Business Logic written in Microsoft .Net

You can call .Net business logic written by your corporate developers from Archibus workflow rules.  In this scenario, the corporate developer is familiar with .Net but is not familiar with Archibus.  They write their logic as Web Services and host them on IIS.  Archibus then calls them as a Web Services client.