Missing Object - Process Interface

Hi Dennis,

we left it out by intention. Process interfaces are often confusing entry users and ARIS Express is meant for users starting BPM. We hope to lower the learning curve by that.

Regards,

Sebastian

I would like to see the process interface allowed, even without the ability to create assignments.  We teach and use the Process Interface as a 'Black Box'.  For example while modeling an engineering process it goes out to a Marketing process.  I can get my engineers to keep on modeling by using the PI as a black box, to be visited later by marketing.

rgds

donald

Agreed.  The process interface is an object used frequently, and critical to understanding how processes hang together.

Regards

Dieter

Agreed as well concerning the need of a Process Interface symbol. I do not believe that entry users will be confused by such a symbol and they will very quickly used it as soon as they map processes linked to each others.

Regards,

Serge  

Hi all,

last days I had a view on ARIS Express and I was so enthusiastic, until I tried to find a process interface (Prozessschnittstelle, Prozesswegweiser, Sub-Prozess)....unfortunately it isn't available.

I'm sorry, but this great tool(;-)) is not supporting BPModeling in that way it should -> process interface/sub-process is a main object in modeling; and I can't understand the argumentation that this object can confuse somebody.

With regards,

Tomasz Kowalik

Hi Tomasz,

please have a look at the following post:

http://www.ariscommunity.com/users/weerakhan/2009-10-15-how-use-process-interface-properly

I think that makes clear why the concept of process interface is not so easily to understand :)

Regards

Jens

I just started evaluating ARIS Express a few days ago and came to the same conclusion as the previous users.  Where is the process interface?  In the early 1990s I used the full function product for about 3 years.  When I was refered to the Express Version, my reaction was what a great way to introduce people to a product before a major commitment, especially at a department level.  

With that said, Are there any recommendations on how to represent reuseable subprocesses. My current example is a repair process for several different types of equipment that all need to use a common process for requesting the parts they need.  All the different areas have different ways for troubleshooting the problem, some long, some short but a common point is when they determine the parts they need, they need to use a common requestion process ( with about 10 functions and some decisons based on approval levels) to request those parts.  In my case it is not a very hard concept to understand, use the common process to order parts or you won't get them.

When using Express what is the recommended to make this model somewhat compatable with the process elements in the future.   I tried to use some of the other elements like the activity and recolor it or just add some other graphic symbol with no luck.  

By the way the I am assuming the Activty is equivalent to the Function that I was used to since it is still showing up in some of the examples refered to,

Some limitations are expected on a starter product, especially free, but reuse is so important to the concept of reducing time and cost in the BPM world I hope there is some way to introduce the concept using Express.  Also I don't want to do a lot of rework and training later in the life cycle.

Thanks, Arnie.

Hi Arnie,

yes, reuse would be great, but it is not going to be part of ARIS Express. Also, other free-of-charge modeling tools or even Microsoft Visio don't support reuse. That is a feature you only get if you got a database beneath the tool, which is not the case for ARIS Express.

Activity = function -> we just named it activity in ARIS Express, because it seems to be the more common term nowadays.

Hi All,

I do agree with all the peers who ask for the Process interface as a separate object in the ARIS Express. MS Visio has it in their tool and when I import a visio model in ARIS Express, the import works perfect, but the Visio object 'Process interface' is translated in ARIS Express as an 'activity', but with a different shade of green. So the readability towards the user is not that marvelous.