Expand +



Integrating SAP Solution Manager and ARIS Business Architect

by Scott Priest, Editorial Director

November 7, 2011

When I was at TechEd back in September, I had a great chat with D. Russell Sloan of IBM Global Business Services and Lori Sanders of Enowa Consulting. Russell is our most prolific author at Solution Manager Expert, and Lori is one of our technical advisors, helping shape the direction of our content.

One thing they emphasized to me was the popularity of synchronizing ARIS Business Architect with SAP Solution Manager. Despite how common it is in the marketplace, there wasn't much information on the process out there.

Luckily for us, Russell knows all the ins and outs of integrating the two solutions correctly. By making them function properly and share information, you can see more ROI out of both solutions. Russell takes you through the technical integration of the two in "Synchronize SAP Solution Manager with ARIS Business Architect to Empower Your Organization's Business Process Management." He mostly sticks to technical concepts, but he does look into process models a bit at the end. Here's an excerpt of that material, in which he describes a good group structure in the ARIS solution.

Group Structure in ARIS

The concept of groups in ARIS is synonymous with folders in Windows. You can have as many groups as you wish in the database structure in ARIS.

Groups are used as a filing system to separate content in the database and to control user access. They are used to hold objects and models used in describing your business processes. The hierarchy of these groups is used as the basis for controlling user access rights.

I recommend you build the following group structure at a minimum. Your project main group with the following subgroups:

  • Conventions: House the example models as defined by your project modeling standards. Conventions also contain a group for the object library. Only the administrator should have access to this group.
  • Processes: This is the project modeling group. It is accessed by the modelers to build process models. They can use content from the other groups, but this is the only group open for editing for process modeling.
  • Organization: Houses the business organization models
  • IT systems: Houses the IT system models. These models describe the enterprise technical infrastructure and application systems.
  • Data: Houses the enterprise data models
  • SOLMAN Sync: Group for housing objects brought fr om or to be sent to SAP Solution Manager. Only the administrators should have editing rights to this group.
  • BPR Reference Designs: Location for housing the BPR content that can be imported from SAP Solution Manager

The reason for this group structure is so you can better manage the object and model content in your ARIS database and reduce the opportunity for creating a nightmare when synchronizing with SAP Solution Manager. Key groups such as Conventions, SOLMAN Sync, and BPR Reference Designs should be read only for everyone except ARIS administrators. This helps enforce project standards and reduces the risk of object duplication and the need for a lot of cleanup.

For the complete article, Solution Manager Expert subscribers can go here. For more information about Solution Manager Expert, go here.

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!