Web service interface - Introduction

A Web service enables a client (a (web-) application or component) to remotely (mostly using the internet) request a service from a server, e.g. to make a calculation, to deliver data, or to execute a task.

Asset Strategy Optimization offers an optional Web service through which external systems, such as an EAM (Enterprise Asset Management) system, can synchronize its stored assets with Asset Strategy Optimization. Once linked to Asset Strategy Optimization, each change in the EAM system (to a chosen set of assets) will automatically be applied to Asset Strategy Optimization as well.

Interface

As soon as the interface link has been established between Asset Strategy Optimization and the external (EAM) system, it is possible to synchronize selected asset-structures in certain ways, where the external system will be leading. I.e. a change in the asset structure in the external system will also be applied to corresponding objects in Asset Strategy Optimization, so the two systems will maintain synchronization. However, changes in the asset-hierarchy in Asset Strategy Optimization will not be reflected in the external (EAM) system. It is therefore a one-sided synchronization.

Before starting to use the Web service interface, it is important to understand its fundamentals. In this way, you may learn to predict its behavior as a result of changes that may occur in any of the systems (Asset Strategy Optimization or the external system).

Server

The technique behind the Web service will only work when there is a continuous connection between the two systems. After all, a change in the external system, delivered to Asset Strategy Optimization by means of the Web service interface, must be received for it to be processed. Since Asset Strategy Optimization is an application that may or may not be running on a user's PC, a PC is not the proper device to implement the Web service on. That is why a Web service interface is usually implemented in companies that already use a central service where multiple users store their Asset Strategy Optimization data (i.e. a 'client-server' set-up). This server will always be up-and-running, so this is a good place to also install the Web service interface on.

Timing

Although the technique of the Web service allows a change in the external system to be immediately processed in Asset Strategy Optimization, this is not necessarily so in all cases. An external system may be configured to collect all changes during a certain period and send one big change message through the Web service to Asset Strategy Optimization at night. The choice of configuration lies in the hands of the designers of the interface. Check with your IT-department to learn the local situation.