INDEX | ORGANISATION | TIME LINE | PEOPLE | STORY | RESEARCH METHOD | COMMENTARY | FINDINGS | HELP | BOTTOM

What affected the choice of systems architecture?: X needed to operate as a global company

In phase I functionality focused on underwriting and claims information with accounting continuing to be carried out on host countries' mainframe installations (00238). The quotation part of the system recorded high level details of every presentation made by X offices world-wide. Once a quotation was accepted by client the status of the quotation changed to "Accepted" and the system automatically generated a programme (00300). Additional information relating to the programme would then be added by an underwriter including the countries where the programme was active. From this the system would automatically generate a policy record for each country (00301) converting currencies as required. Once the policy information had been updated the system generated policy notifications for servicing offices in each country involved (00302). The local office would add local details and issue the policy. The system did not generate policies but contained all the information necessary to generate a policy (00989). Reinsurance information was stored about each programme and policy and a limited amount information was held about locations of risk (00304).

The system consisted of distributed databases with each database containing information on programmes controlled locally and business serviced locally (00246). It was possible from London to view any database (for example to look at activity) but there is little evidence that senior management did this (00276). For system offices information was transmitted electronically overnight so that each database was updated nightly (00246). For non-system offices policy details were faxed and the details returned to Essex for entry into the system (00989). Following the installation of the Unix servers they planned to replace the nightly transfer of data with the Sybase Replication technology.

Although information about Multinational policies was held in the host country mainframes a decision was taken to load the data into both systems independently. The reason for this was that the amount of data involved was relatively small and it would be difficult to drive all the different mainframe systems from the Multinational system (00246). In contrast claims data was downloaded from the mainframe system in the country of claim, attached to the policy, additional information added by X staff and transferred overnight to the controlling office (00246, 00303).

Social influence:
Technical influence:
System characteristics: Functionality

Commentary
Social influence
Technical influence

INDEX | ORGANISATION | TIME LINE | PEOPLE | STORY | RESEARCH METHOD | COMMENTARY | FINDINGS | HELP | TOP

© Clare Tagg 2000