kosmos BOS - Software Products

The appointments automation into a facillity. Coordinate appointments with customers. Keep the procedure progress from "appointment call", to reception, to the therapist until to payment. 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 "APPOINTMENT_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.

Keywords: bpm bam workflow programming tool intelligent agents automation agent framework 3 tier middle tier tcp/ip document management operations management process coordination coordinator iso iso automation rs 485

AutoTasks

The Task assignment automation into a company.You can assign tasks to users, by name or by position into the company or organization. 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 "TASK_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.

Easy-CSS

For Easy Customer Service and Support. This software manages the customer requsets, based on a contract base or not. Customer requests may be serviced via phone, using the help desk, or by thechnicians. An Outlook like calendar helps all the scheduling. The appointments that can be scheduled are not strictly technical, but of a wider nature. i.e. visit to a bank, appointment with a new client....The appointments are displayed by technician. The steps required for a successfull use of the program are the follows (Step 1) Define your Technicians, Customers and Contracts. Define as a technician any person in your company that is capable of dealing with customers problems. (Step 2) Setup your Help Desk Knowledge Base. Information is power. Dont let this power stay only into your head. Multiply it by sharing it with others. How? Write down all of your technical knowledge. (Step 3) Start Receiving Customer Requests. Start up your engine! Receive calls from your customers. Check immediately the status of your customer. Is he in a contract? (Step 4) Put Customer Requests and Technicians on Scheduler. See your schedule in a time table. See all of your appointments (strictly technical or of any other nature). Examine the schedule totally or separately for any of your technicians. (Step 5) Complete the Customer Requests. Now that everything is put on schedule, all that has to be done is to give each of your technicians his daily schedule. By the end of the day, set all of the completed requests as completed to your books.

Keywords: customer technician customer service customer request schedule appointment knowledge base crm contract help desk phone calendar customer service and support easy five steps crm software small business crm call center window titles

AutoServices

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.

AutoOrders

The incoming order automation into a company. Put orders and execute them.The order along with the products goes to the production lines. There every product starts to manifactured at the same time. 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 "ORDER_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.

3 tier FrontEnd for MS-Access

The 3tier FrontEnd for any MS-Access database. Its based entirely on the n-tier technology. One at least application server must be istalled near the MS-Access database. The clients can be installed anywere in the Internet. Firstly the server installation gets all the database schema i.e. tables, fields, indexes, foreign keys and views. After that browsing and editing forms are created. The clients then are setuped automaticaly. In one single pass connects with any of the application servers and copies all the resources (forms, reports, menus). The user, once logged from a remote client has the ability to browse, sort and filter (using composite filtering) all the tables and views of the database. New records of can be added (using edit form) to any table, modified or deleted. The data from any browser can be exported to MS-Excel. One additional tool included in every client, the Remote SQL Executor. The Remote SQL Executor accepts any kind of SQL (select, delete, create, update...etc). The SQL then can be send for execution to the application server and the results are returning. The results can be presented to a browser form or as a report. The SQL queries used can be saved as *.sql files and recalled later for execution. Another important feature of the kosmos FrontEnd for MS-Access is the ability to install any number of application servers (n-tire model) against a specific database. Then the clients are connected to any of these application servers.

Keywords: front end frontend 3 tier application server client msaccess ms access access microsoft middle tier middle layer back-end backend back end hardware drivers

Search for: