ARIS process and diagrams auto generate

Hello,

1. "just keying in some process descriptions" is a bit imprecise as a requirement. Do you expect some AI to understand your text? Designing a process usually is an interactive exercise between a group of stakeholders. The modelling helps them to reach a consensus, particularly considering the often ambiguous properties of human language.

2. Publishing the modelled content to some audience is the whole point: Yes. Ideally you will have the models as your reference and single point of truth. No more PDFs or documents that are outdated the day after you generated them. No more inconsistencies because you change something in one document and forget about another document mentioning the old state.

3. Look into the Know-How section for starters. There are lots and lots of video tutorials showing you use-cases.

4. With ARIS Elements you cannot generate models in the sense of generating new views on content already present in your repository. In Enterprise you definitely can. I'm not sure about Advanced.

Addendum: The platform can also support your process of reaching the consensus state for publishing, i. e. review and approval of the modelled content. It comes out-of-the-box with the simplest imaginable governance processes. In practice in most organizations such approvals are not that simple, so the Enterprise edition offers fully customizable workflows for your governance.

Dear M. Zschuckelt,

thanks for your prompt and kind response.

Just wanted to touch base on the below points. your kind advice would be very helpful.

1. what is aris repository?

2. how can we maintain it and who all can access it?

3. is aris repository available for elements version or for enterprice version only.

thanks in advance.

Regards.

Hello,

the ARIS repository is a database where ARIS stores all artefacts you create. Any object you create (such as a role, a process step, an application, ...) is stored in a database. Also the diagrams you create are stored in this repository. In diagrams you show representations of the objects and relate them to each other. E. g. in a process one step follows on the next. Those are two objects with a connection. In the diagram you have a representation of these objects with a symbol each and a line representing the logical link.

The whole point is, that the database of objects and their logical relationships (such as "follows", "decides on", "carries out", "supports", ...) exists independently of the representation in diagrams. Essentially you are using the diagrams to add "things" and their "releationships" to the database.

Everyone contributing diagrams contributes their view to the central repository. This way you can do evaluations of the relationships that answer questions reaching further than a single diagram view, because the same objects may occur in multiple diagrams, so their web of relationships reaches further than what you see in the single diagram.

This general concept applies to all ARIS editions (except ARIS Express). (Answering 3.)

You can maintain and view the repository via a web browser. There are different roles involved: Most importantly Designers and Viewers. Designers can contribute by creating diagrams and creating objects. Viewers are your "public" that you want to address with your content. Most customers have some Designer licences and sometimes enough Viewer licences to allow every employee access to the content. There is another licence type for administrators. They are concerned with running the system, defining the modelling method (what shall be modelled in which type of diagram), configuring the views (there are views on the content generated from the repository, addressing viewers who are not familiar with the model notations), defining the governance processes and a few tasks more.

Dear  M. Zschuckelt,

Really appreciate your quick response. thank you so much.

Regards,