1 General Goals

The general goal of the PAID system is to provide a powerful, extensible architecture for fast and efficient information exchange. This platform for active information dissemination should be fast and stable to meet its main requirement: intelligent worldwide distribution of most used information, i.e. DaimlerChrysler service, parts and vehicle data, provided by a common architecture. Data access should be transparent while the information itself is always up-to-date. The system should be scalable to accommodate a network of 6000 clients internationally. PAID should also function on several types of computing devices, such as desktop computers, laptop computers, and personal digital assistants (PDAs). The system should have the capability to take advantage of progresses in computer hardware as well as improvements in network technology and bandwidth. The architecture of PAID should allow for the addition of new data and functionality without the need for a complete system redesign. To provide this extensibility, the PAID system is subdivided into the following subsystems, with their own individual goals:

1.1 Authentication and Security

The PAID Authentication and Security subsystem has to ensure secure access to client and DaimlerChrysler parts information across all viable media in the PAID system. A PAID-wide user model is to be provided by the Authentication and Security Team. Within this user model, access rights are assigned to all users and/or user groups; besides, unauthorized access has to be prevented. Critical data is to be encrypted when sent over insecure or not trustworthy mains.

1.2 Database

The purpose of the PAID Database Subsystem is to provide efficient access to the Aftersales Database and persistent storage. This is to be achieved by replication of the database to the worldwide DaimlerChrysler sales organization.

This includes dividing the aftersales data into replicable database subsets, remote query invocation if a database query cannot be answered locally, query caching and management of other data, such as user data.

1.3 Learning and Adaption

The subsystem monitors the network and database activity and stores information about these activities. The subsystem then analyzes the data to expedite the decision making process of the PAID system. First, it will deal with a large number of clients (over 6000). Second, it will utilize machine learning and other intelligent algorithms in its data analyzation process. Third, it will investigate existing monitoring and diagnosis tools. Finally, it will provide reports of its analyzation with a graphical user interface.

1.4 Network and Event Services

The goals of the network subsystem are to reliably transmit messages and data between Daimler-Benz after-sales database servers and dealer machines running the PAID system. The information should be accurate and delivered in a timely manner. The communication between PAID-subsystems will also be provided.

All updates to the database should be pushed to dealers who are using the information using a multi-cast distribution policy.

1.5 User Interface and STAR NETWORK Integration

The User Interface and Star Network Integration subsystem provides user access to the PAID functionality and ensures a proper co-operation of PAID and Star Network.

The interface that the user will see is to be fully integrated into the Star Network interface. One of the main goals is to keep the interface of PAID really small, so that the user can focus his tasks on the data itself instead of getting the data.

From the point of view of the user interface the current system is the actual user interface of the Star Network client. It represents the frontend to the whole Star Network functionality, which could be for an end user from interest. The user has the possibility to access the different parts catalogues, after-sales information, etc., but at the moment he does not have any influence on the manner like the requested data being gotten and held up to date. To remove this last restriction, the PAID subsystem was designed.

While currently the Star Network client sends his requests to the Star Network server, which accesses his database directly and tries to respond to the requests, in the User Interface and STAR NETWORK Integration system model the Star Network server will not have his own database. The Star Network server will be modified so that all database requests will be forwarded to a PAID server. The answer will be passed back to the Star Network server, which then transfers the data to the Star Network client.

In fact the Star Network integration consists of helping develop and providing a translation module for communication between the Star Network server and the PAID server. The main goal concerning this aspect of the subsystem is to make as little changes to Star Network as possible, to allow for the further development of Star Network.

To sum it up it can be said, the current user interface of the Star Network client has to be extended by the components needed by the PAID functionality.