KosmosBOS Technologies > AutoOrders overview

This application is about a "tailor made goods company". The requirement on the application is to automate the "procedure" of "customer's order". This means that the successive "steps" of the procedure are automatically forwarded from one employee to another without any kind of "manager" intervention. At any time the manager has the ability to see on what tasks (steps) the employs are engaged. After a certain period of time the manager has a complete report on what tasks each employee has been assigned, when has started and when has finished the tasks.

The requirements, put on the application from the supposed "tailor made goods company" owner, are the following:

"Every employee can put "orders" from customers. The "order" contains the customer's name and a number of products, that are only tailor made and not ready on the selves. The construction of goods starts (all at the same time) but its obvious that are completed at different times. As soon as the last good constructed the "order" is packaged and shipped to the customer. That's all."

All of the above requirements are put on a coordinator agent. The action_code of the agent's is the following:

start_action

call bpm_setprocedureowner(__activation_user) {.....set the procedure owner}

{(1)....any user can put a new customer order}

callwait bpm_assign_job ( "new order" , __activation_user , "" , 0)

ord_id = bpm_getrecid(1,__au_step) {......get the record id of the service request}

customer = LookUp("ORDER","ORDER",ord_id,"CUSTOMER","")

call bpm_setprocedurecomment(customer) {.....set the procedures comment}

{...................................put all product in array variables}

start_sql "_DAT" "KOSMOS"

SELECT PRODUCT.*

FROM PRODUCT

WHERE (PRODUCT.ORDER = :P)

end_sql

call RunEmbSQL("_DAT",ord_id)

q = QueryByName("_DAT")

count = TRecordCount(q) ;

call TFirst(q)

for i = 1 to count

prod_id[i] = TGetFld(q;"PRODUCT")

prod = TGetFld(q;"PRODUCT_NAME")

quant = TGetFld(q;"QUANTITY")

comm[i] = strcat("PROD=", prod, " Q=", quant )

call TNext(q)

call FreeEmbSQL("_DAT")

{..................................start the production of products (all start at the same time}

split_for i = 1 to count

{(2)....construct every product requested ...parallel split}

call bpm_setstepcomment(comm[i])

callwait bpm_assign_job ( "construct product" , "" , "PRODUCTION" , 0 , prod_id[i] )

next_branch

{(3)....when all products have been constructed then ship the order}

callwait bpm_assign_job ( "ship order" , "" , "TRANSPORTATION" , 0 , ord_id )

end_action

We can see the callwait or split_for keywords. Those keywords give the opportunity to the agent to wait (until a job has been finished) or to have parallel code execution (notice the ad hoc conditions here where the number of parallel splits are not known in advance!). Those are capabilities that are not presented every day in a programming language (ok script!). Notice that the callwait "calls" the user's activity as it would be a "program's subroutine". Notice also the mixing of conventional code (database handling, for loops) with process management code.

We have to admit that the effect (coordination and historic data collection of the order procedure) is far too big for the lines of code that are written by the application programmer. To be precise the code is a little bigger (the agent contains the code that "describes" the task (activities) assigned to employees). The complete agent (code and declarations) is given bellow:

{-----------------------------------------------------------------------

' procedure for the order manager

'----------------------------------------------------------------------------------}

{....................................AGENT INFO..............................................}

start_agent_info

AgentName = "ORDER_MANAGER"

AgentDescr = ""

AgentLanguage = ""

__timer_interval = 0

__is_registered = 1

__delete_on_termination = 0

end_agent_info

{....................................PRODUCTION CODE..................................................}

{..............................................................................new order}

start_bpm_activity "new order"

start_bpm_subactivity "Order elements"

rec = bpm_getrecid()

if (rec = 0) then

call OpenForm("ptAppend","ORD_E01.FM","WORK.ORDER",1,"?=ORDER")

else

expr = strcat(rec,"=ORDER")

call OpenForm("ptEdit","ORD_E01.FM","WORK.ORDER",1,expr)

endif

end_bpm_subactivity

end_bpm_activity

{..................................................................................construct product}

start_bpm_activity "construct product"

start_bpm_subactivity "Product"

rec = __params[1]

expr = strcat(rec,"=PRODUCT")

call OpenForm("ptEdit","PROD_E01.FM","WORK.PRODUCT",1,expr)

end_bpm_subactivity

end_bpm_activity

{..................................................................................ship order}

start_bpm_activity "ship order"

start_bpm_subactivity "Order to ship"

rec = __params[1]

expr = strcat(rec,"=ORDER")

call OpenForm("ptEdit","ORD_E01.FM","WORK.ORDER",1,expr)

end_bpm_subactivity

end_bpm_activity

{.....................................CONTROL CODE......................................................}

{.................................ACTION CODE................................................

This agent has as job to coordinate (that' why we call it a coordinator agent) the activities of

a "luxury cars service facility".

The salesmen (any user) can put an order

All the products of the order must be constructed

All the products start constructing at the same time (parallel split with an undefined number of splits!)

After all products are finished then shipment can be follow

At any time the salesman (__activation_user) can see the progress of the order and can keep informed the customer

The agent follows the events in real time (at the time that they are happen!)

}

start_action

{ press F8 for next step }

call bpm_setprocedureowner(__activation_user) {.....set the procedure owner}

{(1)....any user can put a new customer order}

callwait bpm_assign_job ( "new order" , __activation_user , "" , 0)

ord_id = bpm_getrecid(1,__au_step) {......get the record id of the service request}

customer = LookUp("ORDER","ORDER",ord_id,"CUSTOMER","")

call bpm_setprocedurecomment(customer) {.....set the procedures comment}

{...................................put all product in array variables}

start_sql "_DAT" "KOSMOS"

SELECT PRODUCT.*

FROM PRODUCT

WHERE (PRODUCT.ORDER = :P)

end_sql

call RunEmbSQL("_DAT",ord_id)

q = QueryByName("_DAT")

count = TRecordCount(q) ;

call TFirst(q)

for i = 1 to count

prod_id[i] = TGetFld(q;"PRODUCT")

prod = TGetFld(q;"PRODUCT_NAME")

quant = TGetFld(q;"QUANTITY")

comm[i] = strcat("PROD=", prod, " Q=", quant )

call TNext(q)

call FreeEmbSQL("_DAT")

{..................................start the production of products (all start at the same time}

split_for i = 1 to count

{(2)....construct every product requested ...parallel split}

call bpm_setstepcomment(comm[i])

callwait bpm_assign_job ( "construct product" , "" , "PRODUCTION" , 0 , prod_id[i] )

next_branch

{(3)....when all products have been constructed then ship the order}

callwait bpm_assign_job ( "ship order" , "" , "TRANSPORTATION" , 0 , ord_id )

{------------------------------------ end of procedure ---------------------------------------------}

end_action

The agent (agent prototype precisely) can be viewd form Right Mouse Click on Application's Background->Popup Menu->Developer->Resources->Agent Prototypes. The system creates, for every "order" requested, a new "alive" agent that starts to execute his action_code.

Another issue is that the jobs are assigned to users (employees) not only by name but also (and mainly) by their roles into the company. The users and roles as they are defined into the application can be found at Menu->System->Users/Positions.

A "new therapy appointment" can be activated on the application from Menu->Files->NEW ORDER. In order the users see the activities (jobs) that are assigned to them exit the demo application and logon as the user in question. The same can be run in debug mode from Menu->Files->NEW ORDER (DEBUG). The programmer has to press (F8) in order the agent continues the execution. In debug mode also the activities are not forwarded to the employees (users) but are presented to the programmer in order to complete the forms with data and forward them to the next step.

Every user has the "incoming activities" window. This window refreshes itself every 30 seconds (it can be changed) and contains all the activities that the agent has assigned to the user either directly (by user name) or (frequently) indirectly (by role that the user has). Notice that the same activity is send to all users that happen to have the same role into the company or organization. When the user "completes" the data that the activity required, he/she "forwards" the completed activity to the next step. Then the activity disappears from the window.

In order a user to see activities that assigned to him for today or are uncompleted from yesterday he/she has to activate Menu->Personal Secr->Activities for today. For activities that are assigned to user for future time (for example pending appointments) the user has to activate Menu->Personal Secr->Activities that Pending.

By activating Menu->Personal Secr->Activities In Progress we see every activity (job) that is assigned at the time and is in phase of completion, i.e. presented to users "incoming activities" and are worked by them.

Every window that presents "user activities" has a button captioned as "History". By activating it we see the steps that have completed (with date and time data) by user and role. The steps that are "finished" are flagged by (1) while those that are unfinished by (0). Near the button "History" there is the button "Flowchart". By activating it we have automatically a picture as below. By "red" are colored the finished activities, by "green" the activities that are assigned and worked now and by "blue" the activities that are going to follow as next steps.

When we activate Menu->System->Users we can see a button captioned "Have Done". By activating it we get all the activities that the user (employee) has finished and by witch role. The time of staring and completing for each activity is also available. This way the real effort that the user has given to the company can be estimated.

The demo application comes with "Developer" capabilities. That means we have the opportunity to change the database schema (Right Click->Developer->Resources->Database Manager->Edit Schema). We can also change the forms (Right Click over a form->Designing).

We described above that to "emulate" multi user behavior we have to exit and login the application with a different user name. In order to run the application in real multi user configuration (over TCP/IP breaking thus the barriers of the local area network) we have to replace the "kosmos.exe" with a real multi user server (starting from 3 users). For this reason see the "Products" page in our site. We have also to install clients (any number). For this reason see the "Downloads" page in our site.