Client-Server Solutions

CARM Server

(Available separately)

The CARM Server is an active server that maintains a library of knowledge modules for distribution to user all around the world.

The CARM Server works similar to a lending library where people can take out books ("knowledge modules" or "modules" for short) and the librarian writes down the name and address of every user and the modules they have taken home and the date of the loan.

Now suppose you have taken a thriller from the library and at the time you start reading it, the author of the thriller has come up with a new and much better ending.

This is where the analogy to a library breaks down; because with a library book, you are stuck. A new edition has to be printed, bought by the library and if you are lucky you somehow learn that this new edition exists and you can reread the book.

Not so with the CARM Server! The CARM Server notifies all clients that have downloaded a specific module of new versions of the module as soon as the new module arrives ¹. Once the client receives this notification, there are several options: the client can decide to replace his version of the module by the new version, or he can decide to keep the old version. The server can also be set up in such a way that replacement is automatic and the clients do not have any say in this process.

More specifically, here is a typical scenario for the CARM Server:

1. User A provides an initial analysis of a module in the usual way with the APIS client software.
2. User A now uploads this module to the server. Similar to the different departments in a library, the modules can be arranged in categories for easier reference. Also, the server can be configured so that the server administrator is able to manage the release process of modules.
   Figure 1 - Module upload
   Figure 2 - Services manager - process modules
3. Users B, C, D... download the current released version of the module into their own documents to integrate it into their analysis. The server remembers the users as well as the documents and structures where the modules were integrated.
   Figure 3 - Services manager - module usage
   Figure 4 - Properties dialog - module user
4. User A has come up with new ideas concerning the module and uploads a new version to the server.
5. The server informs all users of the module of the existence of the new version so that they can replace the existing old version by the new one ("pull").
6. Alternatively, the server can automatically replace old versions of the module by new ones in the client documents ("push"). This replacement process is customizable.
   
   Figure 5 - Services manager - update job

CARM NG

(Available separately)

The CARM NG server provides password protected web based action tracking and escalation management. The tasks tracked by the server usually are actions defined for failure causes, but the server is not restricted to these kind of tasks. Every task that arises during Life Cycle Engineering or in an audit can be tracked by the server.

The tasks are initially created with the client software; they have a description, a responsibility, a due date and context information (see below).

For centralized task management, these client data are uploaded to the server where they can be tracked and changed using a standard web browser. These changes can then be transferred back to the clients.

Predefined search filter, as well as a sophisticated search forms let the user easily find relevant tasks and their context information. These can then be viewed and changed in the browser. Change history management is also part of the CARM NG service.

The CARM NG server can also automatically notify responsible persons if a task is overdue; the time window for the notification can be defined by the administrator (e.g. seven days before deadline).