Show TOC

Component documentationData Consolidation for Mobile Applications

 

The consolidated database or CDB, is the logical overall database of CRM mobile. It is located on the CRM server, and contains all the data that is supposed to be distributed.

Implementation Considerations

For the external sales and service staff, the CDB is split into several partial datasets to allow them a degree of independence in their work. They do not work online on the overall database, but rather on the mobile sites (laptops) with local, geographically distributed, datasets. The logical overall database is said to be fragmented in this case.

The partial datasets of the CDB must correspond to the requirements of the employees in the field force. This means that each Remote employee is given access only to the data for which he or she is responsible. The employee then manages his or her data (for example, customers, contact persons, orders, or appointments) on a local database.

There is a degree of overlap between the various partial datasets into which the overall database is divided. This is known as replicated data storage, which means that there may be several different employees in the same system, who are all responsible for managing a given item of data and who could make changes to it.

This scenario, in which the same information content is maintained in more than one place, obviously has consequences for the functionality of such replicated database systems.

Features

  1. It must be possible to fragment the entire database down to the level of individual objects. Therefore, it must be possible, for example, to assign the management of customer A to employee X, while making employee Y responsible for customer B.

  2. Data that is administered and maintained in several locations must be regularly exchanged and brought into line with the other affected locations, so that the datasets remain consistent. This is automatic redundancy management, the automatic maintenance of lookup tables. For more information, see Modeling Realignment.

  3. Changes to the datasets on the local databases (for example through a change of responsibility) must be performed automatically (automatic fragmentation changes; that is, realignment).

  4. At any time it must be clear who is responsible for maintaining which item of data (transparency of fragmentation and replication).

To provide this function, CRM Middleware offers a number of mechanisms, maintenance tables, and fields.

Example

There are two employees with responsibility for a given sales area, but each of them sells a different product. If there is a customer who orders both products, each employee has this same customer’s details on his or her laptop. Other kinds of information, however, are specific to the individual employee (for example, prospective customers, personal calendar, activities, and so on).