We have been using ARIS Designer for two years. Now we have 1400 process model (including all support process, main process etc) , Organization library, IT System Library at our database. We are thinking about taking our procedures and work instructions, memorandums from ARIS. Is it reasonable? Is there anybody using ARIS for this purpose?
Thanks in advance
0
20.5k
5
by Runé Becker
Posted on Tue, 07/21/2015 - 15:43
Dear Ayca,
What do you mean by "taking our procedures [...] from ARIS"?
Where do you want to put them?
Are you using Publisher to grant read access to everyone in your organization to your process content?
In ARIS 9 you could also use ARIS Connect with more capabilities than Publisher, e.g. social collaboration for getting feedback next to the process models.
I mean, we are writing procedures, work instructions etc to explain how a work is done on WORD, EXCEL. But after we design all company process on ARIS, we want to take a report and use this report instead of our procedures. I want to ask that standard operation procedures are equal to an ARIS report which is taken from process models? Can this report cover all the information which is at procedures?
You could start with the report "Create process manual" on an high-level Value-added Chain Diagram or EPC.
However, by running any report you will always end up with single files, the report output. And due to the nature of connected models and objects in ARIS, it's difficult to walk through the whole ARIS database just "on paper".
So you need either to invest some report scripting to adapt a user-role and content specificoutput of your processes.
Or take a more lively approach, which is to have your "process viewers" accessing ARIS live content in a browser, either by a published ARIS database in ARIS Publisher, or by even skipping the publishing task using ARIS Connect.
In latter one your process viewers are accessing ARIS content with ARIS Connect Viewer licenses through an Internet browser and can instantly comment Facebook-like in a collaborative way.
Thanks Rune, you were quicker than I. Here is what I just came up with:
Hello Ayca,
indeed many customers use ARIS for Quality Management purposes. Isn't that the main point of it all? There are different approaches to this.
1. Have quality management sign off the ARIS models and leave everything on the server for everyone to see. Many companies take a lot of effort putting a sentence on Word documents or printed materials that reads something like: "Printed documentation only reflects the state at the time of printing. The only valid reference is maintained at https://...." You get the idea. So to avoid that, avoid printing in the first place and rather use versioning to create auditable accounted-for documentation. That is the way Rune pointed to. Possibly you create some Governance workflows to organize the electronic sign-off on the work products (ARIS Process Governance).
2. Some customers prefer to put some ink under a leaflet or book they can place in someone's cupboard for any auditors to look at. Those customers will undergo some effort to create a report that prints out everything they want to see in the documentation, taken from the models (with the above disclaimer). Some customers also take a look at a solution from Software AG Global Consulting Services in the Netherlands, who have created a neat report they are now selling. They call it "ProcHandbook report". It can be configured to export almost any model content (graphics and attributes in table form, also structured through drilling down in assignment hierarchies) using a Word template, no ARIS Scripting knowledge required. Also if you create that at regular intervals it may be something you place on some file server for anyone to access, who prefers a dumb Word document over an interactive collaborative environment like ARIS Connect. You see my bias. :-)
Thanks for your kind answers. My point was about Quality Management purposes and your answers are enough for me. Second approach is more suitable for us.
