Information integration

In some companies the automation of processes took place very locally or stand alone. Each department and service had the freedom to choose those applications, that stood close to its own processes. This is an justifiable approach, viewed from the point of the processes. But from a corporate point of view, a patchwork arises of systems and applications, which cannot talk to each other or still more terrible, no integrated management information can be provided. This not only due to the differences in systems, but also to the difference in definitions of the terms used. The term “stand alone” or "island automation" is thus a well-known phenomenon.

What is the remedy for this phenomenon? In afterthought an information architecture, in which "loose coupled systems" have been identified and in which the most important definitions have been standardised, could have prevented the proliferation of systems. In such an architecture each application gets it’s place, within in advance determined requirements and interfaces.

What now when the small islands are already formed and the systems already have naturalised? In this case there are also solutions at hand. Coupling of systems by means of so called message brookers or otherwise said information integration software is possible. These connections not always give a structural solution. In many cases the way of the information architecture is always still recommend for the longer period.

Information integration software uses of technique of web services. A web service is an application which offer a number of functions, which are addressed by means of messages. These messages use the open standard XML (eXtensible Markup Language) according to fixed appointments. These appointments are platform- and programming language independent; every web service is therefore applicable on every type of platform (Unix, Linux, Windows, mainframe, Apple, etc.) and on every type of programming language (Java, Perl, C #, etc).

For those who are interested in technology, here are some of the used abbreviations: Web services have been based on open standard protocols, such as SOAP, HTTP and SMTP. Therefore everyone can join in. Moreover standard integration software is available, with which the technology disappears to the background.

XML (eXtensible Markup Language) An internet language for communication between computer applications through structure and data orientation.

HTTP (HyperText transfer protocol) the standard protocol for web pages on the Internet.

SMTP (Simple mail transfer protocol) the standard protocol for sending email messages.

SOAP (Simple object access protocol). SOAP is the means with which the effective communication takes place. It is a set of appointments concerning the messages to be sent, it determines therefore the way in which applications talk with each other.

Do you want more detailed information? Of course you can always make an appointment without engagement. An appointment for the exchange of ideas concerning possible support, second opinion or quick scan. In a quick scan we analyse your situation in a couple of days or weeks.

Or possibly you want to interest others for this within your organisation?