The car service automation program. Get service orders and excecute them. The customer put service call to company. The application handles all the process of car servicing, starting from the gate reception, to disassembling and disassembling. The incoming task emerges as "Activities to do" on the terminal of the assignee (user). After the user finishes the job he/she forwards the task, with any number and kind of attached documents to it. The "operations manager" can see at any time what tasks are running, their past history, users that have been assgned and assingment and finish time. All this information is important in order to evaluate every employee's contribution into the company. Every task assignment procedure is coordinated by an intellingent agent, named "SERVICE_MANAGER". The agent's action plan (process code) and cooperation with users (production code) are displayed in the Developer->Agent Prototypes. A flowchart is automaticaly created to show the workflow of the procedure but also the progress of a running procedure. In order the application to run in multi user mode, using 3 tier configuration, needs an Application Server (a low-priced one) and Clients (that can be freely downloaded). The application can be freely redesigned (forms, menu, database schema, agent code,...) by an application programmer. In order to modify, test and run the agent a special debuger exists. The debuger in the same machine runs debugged not only the action plan of the agent but also the code of the activities that are assigned to users (in other machines). This way the "agent bulding" becomes a trivial programming task. In the action plan of the agent can be applied wait states, parallel execution split, and joins, or joins, ad hoc parallel splits and subprocess execution.