Skip to Content

If you have read my blog about “How Enterprise Architecture can help me improving User Experience” you will probably have noticed that we’re planning to extend the content of SAP UX Explorer beyond UX.


In this blog, I would like to explain what exactly this means for the SAP UX Explorer.


Let me start with a flashback to where we are coming from, first. After that, I will share with you what we have changed today and what our plans are for the next few months.


From the initial idea to a well-accepted source of information


What many people don’t know is that SAP UX Explorer has a history that goes back to 2010. This was when the idea was born to help customers interested in user experience improvements by providing them with structured information about their improvement options. This was accompanied by the idea of having a self-service at the end that would enable customers and partners to get the information they need fast and at one place.


We started working on an information structure that ended up in a pre-version of the SAP UX Explorer, based on a PPT document using the Solution Map concept. You can still find the outcome in the web on a fileserver of the German SAP User Group – DSAG. It’s a kind of historic document.

A certain amount of time passed before we were able to define and build a tool that would serve up the information in an appetizing manner. A large number of customer meetings brought us to the realization that customers were searching for a single source – at least as a starting point – to explore which topics might be of interest at all and which not. The intention was not to replace other sources at SAP. Many customers said that the content of all these SAP sources was good but simply too detailed to do anything with. The aim therefore was to provide an information hub providing quick and condensed information about the topic in question.


We also noticed that many people had difficulties understanding the relationship between all the different components, technologies, and concepts. Fortunately, I told a colleague of mine called Peer Hilgers about our findings. Peer was working a lot on semantic networks and immediately recognized the benefit of building a semantic network as a foundation for our tool.


In late 2012, we started to define and develop the first version of SAP UX Explorer, a tool to provide a quick summary and more details if needed.



Drawing.jpg


The picture above shows an early stage where we were evaluating the different relation types that would exist in our semantic network.


In May 2013, during SAPPHIRE 2013, we went live with the SAP UX Explorer deployed to the SAP HANA Cloud Platform.



UXE1.0.png


This first version included about 100 UX-related topics with a maximum of 10 facets available per topic. In the meantime, we have more than 200 topics with more than 20 facets available, depending on the topic in question.


Since then, we have made a lot of enhancements to the tool and the content which we have documented in an SCN blog. The most visible one was the update of our user interface in order to make it compliant with SAP’s “One Digital Experience” program.


UXE2.0.png

The content will grow far beyond UX


Talking to customers and partners about SAP UX Explorer  over the past two years, the most significant feedback we have received is as follows:


  1. “The Explorer is very helpful, but UX is not the only topic I have to tackle in my enterprise. Couldn’t you add additional aspects besides UX?”
  2. “While the Explorer can help me to learn more about my options, I would like to have more guidance on how to combine and use these options.”


During the same period, our team has evaluated a way of providing a new structure that is not UX-specific but relevant to everybody. We have identified Enterprise Architecture as a great framework, providing a structure that we can work with in order to grow our content organically beyond UX. So we started – again – to build an idea and execution plan.


As a result, we have been working on new UX content that fits the Enterprise Architecture structure. Since August this year, we were also preparing content for a focus area called “Landscape Architecture”. The last weeks, we have merged the new content from a sandbox environment into our productive content development environment. Today, we went live with SAP UX Explorer 3.0.


Obviously, this is just the beginning of a longer journey of adding new focus areas. Hopefully, we will soon continue with “IoT” as another area.

On the way to a SAP Enterprise Architecture Explorer


New content and new tool features


As we went live with version 3.0 today, we have also switched the Semantic Viewer from a closed beta phase to an open beta. From now on, you will therefore be able to find already a lot of new information, together with a great new functionality to explore the information based on a graphical tool.


New content structure


We have kept our well-received information structure, which defines how a topic is described by summary, features, benefits and other facets.


The content structure, which defines the overall categories where topics are sorted in, has been modified however. If you make regular use of the Browse Topics page, you will see a change there. The following categories represent the new content structure.


IT Focus Areas

  • User Experience
  • Landscape Architecture
  • (More to come in 2016)


Enterprise Architecture

  • Concerns
  • Transition Paths
  • Architecture Viewpoints
  • Architecture Patterns
  • Goals (planned for Q1/2016)
  • IT Capabilities (planned for Q1/2016)
  • Strategies & Methods


Offerings

  • SAP Products & Services
  • SAP Technology Components & Application Functions
  • SAP Assisting Services
  • SAP Rapid Deployment Solutions (RDS)
  • Third Party Products & Functions

If you are using the SAP UX Explorer mainly via the search function at the top and the relations within the topics, you will hardly notice this structure and can continue working as before. You will see a brief description however at the top of each topic, indicating the related categories in the content structure. Even this is a small enhancement it has very positive influence to the way you can navigate through the network of topics.



Header.png


A new name: SAP Enterprise Architecture Explorer (SAP EA Explorer)


We do not change the name of the SAP UX Explorer immediately. There has to be a change soon however, in order to clearly indicate that the Explorer contains more than just UX. I guess we will wait until we have received enough feedback to understand how the new content and the structure changes are accepted. Nevertheless, I wanted to provide you with advance warning of this name change.


So please don’t be surprised if you access our page and encounter a “SAP Enterprise Architecture Explorer”. In fact, the redirect http://sap.com/eaexplorer is already working and can be used already.

Summary – What can you expect?


Let me close by answering the question of what you can expect from the Explorer today and in the coming weeks and months.


Timeline_V3.png


  • The Explorer becomes an information platform for new areas of information beyond UX, now.
  • The Explorer has a new content structure that will align us more with Enterprise Architecture.
  • All users who work primarily with the search, or by navigating from topic to topic, might not see huge changes immediately.
  • The changes are there though and will provide new insights and viewpoints to the content.
  • We have integrated the Semantic Viewer as Open Beta into the Explorer.
  • The Explorer will soon be renamed to SAP Enterprise Architecture Explorer
  • New focus areas will be added to the Explorer soon.


I hope that you are as excited about these developments as our team is. Let us know what you think and leave comments below.


-JJ (@JJComment)

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Wilko Sattler

    Dear Jürgen, I am happy to see you evolving the UX Explorer towards Enterprise Architecture. Your materials and thoughts will definitely help our customers to link Business with IT and thus help me to do my job as an acount manager. Looking forward to updates from you and guys like Dirk Anthony. Best regards, Wilko

    (0) 
    1. Jürgen Jakowski Post author

      Hi Dario,

      Thank you for your response.

      I guess you already have a certain concern in mind for which you would like to have a method for. So probably my answer might not exactly hit the point for your. But let me try to answer in a more generic way.

      In fact we are highly interested in providing methods. Depending on the case, a method might have a different scope and output.

      In the context of UX for example, we already have a couple of things already like

      In the case of the concern approach, we have one case currently described:

      More will follow soon.

      The “getting started” sections of the concern and transition mentioned above provide steps. The transition and the assigned architecture viewpoints can be seen as outputs. Also the viewpoints relate to the products and functions that are related in the relation section (see relation section in the viewpoint).

      Another example is the “Example flow of a UX improvement project” which you can find in the document section of the Enterprise UX Strategy topic. It provides a flow (steps), links to related topics, blogs and videos, mentions deliverables and names the documents and content that is output in the several steps.

      Besides the UX context, there are other things we are currently working on.

      • One is that we are currently collecting IT capabilities in the context of our IT focus areas (UX and Landscape Architecture). Once we are going to make them public, we will also have here relations between business goals, capabilities and products.
      • The other one is that our team is working on reference architectures which are modeled with the SAP PowerDesigner. If you were thinking into this direction, of course these models would include inputs and outputs.

      If this doesn’t hit your point exactly, please let me know. You probably need to help me with more information on what you would expecting, then. 😉

      With regards,

      JJ

      (0) 
      1. Hernan Dario Rodriguez

        Hello Juergen.

        Thanks a lot for this valuable information.

        I was thinking more in a general method: I saw the video about Enterprise Architecture concept and I imagined a framework for enterprise architecture layers, not only for UX context. Anyway, the current focus is really interesting.

        Then, I saw you were talking about other topics you are working on: IT focus areas, reference architectures, and I imagine in this topics can have an enterprise architecture process (inputs and outputs). I was thinking some similar to the ADM of TOGAF.

        Kind Regards

        Dario Rodriguez.

        (0) 

Leave a Reply