Skip to Content


In November 2012 Nakisa released the latest version (4.0) of their visualization product suite and with it a number of changes to the availability of modules, nomenclature and licensing.  In this post I’m going to outline some of the importance of these changes in an attempt to try to help translate between versions for anyone who might be considering upgrading  or applying unused existing licenses (shelf-ware).

EDIT: In April 2013 Nakisa released 4.0 SP1.  This included a name change for OrgManager (to TeamManager).  A set of updated diagrams reflecting this can be found in the 4.0 SP1 addendum document for this blog post.


The diagram below shows the modules available in SAP Visualization Solutions by Nakisa 3.0 and 4.0.

VSN 3.0 to VSN 4.0.png

I’m going to start at the bottom of the diagram with the STVN modules.  The 3.0 modules have now been consolidated into three “TalentHub” modules.  Each of these modules is aligned to a particular role – employees, HR/executives and managers.  This alignment makes it much easier to see who particular modules are targeted at and in the case of TalentFramework and SuccessionPlanning brings them together into a single module. 

TalentDashboard however has in effect been decommissioned as a result of this consolidation. The advances in the other modules however I think reasonably address this deprecation.

Within SOVN there are also two notable differences.  The first is the introduction of OrgHub for Mobile , a new sub-module within the OrgChart module.  This is significant not only in the fact that it is the first mobile solution offered by Nakisa, but also in that it is the first to be pre-fixed with “OrgHub”.  Unlike the STVN modules, the SOVN modules have not been consolidated and aligned to particular roles.  But from references to “OrgHub” in a recent 4.0 delta training course  and the change to STVN in mind it seems almost a certainty that we’ll see some sort of “OrgHub ification” of the SOVN modules occurring in the not too distant future.  For now though “OrgHub” is not seeing as much use as “TalentHub” as a collective term for a set of VSN modules.

The second difference within SOVN is the renaming of the DataQualityConsole module to OrgAudit.  I’m unsure as to any particular significance to this renaming other than it probably conveys the purpose of the module a little better and changes it from something that to me sounds a little more action driven (auditing) rather than something that sounded perhaps more passive.  If Nakisa are moving to the use of “OrgHub” I’m surprised they made the effort to rename this module at this point, but perhaps it just makes better marketing sense?


Along with the change in the modules there have been some changes in the licensing.  In 4.0 there are five licences that organisations can opt to take up.

module licensing (compact).png

The licensing around the TalentHub modules is a simple one to one relationship though OrgModeler is bundled with the Talent Planning licence.  On the organisational side of things all of the applications are available under Org Planning, but OrgChart is also available under its own separate OrgChart license as well.  So all in all a nice simple model.

Comparing this 4.0 licensing back to the module and licensing in place for 3.0 we can see that there have been a number of changes.

Licensing .png

  1. There are some simple reflections of module changes.
    1. DataQualityConsole renamed to OrgAudit in Org Planning.
    2. TalentFramework and SuccessionPlanning are merged into TalentHub for HR & Executives under Talent Planning
    3. TalentDashboard is no longer available under Talent Planning
    4. CareerPlanning has become TalentHub for Employees.
  2. SuccessionPlanning for Managers has been transferred to a different license as TalentHub for Managers under Talent Viewing.

This second point should make it much easier to meet the licensing needs of managers without going overkill on licensing for other modules which managers would not typically be given access to.

So how should you work out the 4.0 licensing requirements?  Well the diagram below tries to show how you might review your requirements based on the roles, licensing and available modules.

role module licensing.png

The faded roles indicate where there is some flexibility in what you might actually consider…

  • In the case of OrgChart, you could just get OrgChart licensing for all roles; however if you are purchasing Org Planning licences, you can reduce the number of licences accordingly as OrgChart is bundled in with that licence.
  • The same might be said of OrgModeler for Executives and HR since this is available under both Org Planning and Talent Planning.  In this case however both of those licences include more than just OrgModeler and you would likely be opting for that licence to gain access to the other applications as well – so there could be some duplication here.  It may simply be best to just consider OrgModeler as a bonus application in terms of costing into the licences.
  • Managers for most organisations covers a wide range of responsibility and so whilst some managers might get good use from some of the applications in Org Planning it is unlikely that you would wish to purchase licences for all managers.

Of course overall you may not wish to obtain licensing for every application.  Perhaps you just wish to deliver structure charts to managers or give HR some extra tools to improve data quality?  Maybe your focus is entirely on Talent Management?  Whatever the scenario simply mix and match the modules to the roles and derive your licensing from that.

There is of course one notable exception to this licensing that some of you may have picked up on.  OrgHub for Mobile is not currently included in any of these licences.  The licensing for this sub-module is achieved through a nominal one off fee per user with a pre-requisite being that you would have the equivalent licensing for OrgChart in place as well.  OrgHub for Mobile is an additional access channel with an additional access channel licence cost.

To licence and enable OrgHub for Mobile simply contact Nakisa  or one of Nakisa’s implementation partners to discuss your requirements.


In addition to the new functionality, 4.0 has brought with it a number of interesting changes around the structuring of the modules.  There is an emergent approach to rationalise and align the modules to end user roles which should make it easier for organisations to quickly identify the licensing they require to meet their organisational and talent visualisation requirements.  Whilst the licensing options have in fact increased from version 3.0 to version 4.0, this has been in an effort to simplify selection and provide an improved match (i.e. fewer licences) to typical sets of requirements.

Further Reading

I recommend the following resources for anyone looking to upgrade any existing pre-4.0 VSN modules.

To report this post you need to login first.


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

  1. Andy Silvey

    Hi Stephen,

    thank you for the blog, talk about timing (again), we’ve just had Nakisa in here today and we were talking about moving from Nakisa 3.0 to 4.0 !



  2. Luke Marson

    Hi Stephen,

    This is a nice blog covering the license model. Licensing is important, although it is not usually of interest to the front-line business (they are interested in having the solution rather than procuring it 🙂 ).

    I wanted to point out that no applications have been renamed – both the previous and “new” name are used. For example, DataQualityConsole and has not been renamed, rather it is also called OrgAudit. DataQualityConsole is how it will appear on the SAP Master Price List although from SOVN5.0 it should be re-branded as OrgAudit by SAP and Nakisa. This is the likely case with TalentHub too, which should align with the introduction of a TalentHub for Mobile application.

    The detail on all of the application names, along with the new 4.0 features in the application, can be found in the blog What’s new in Visualization Solutions by Nakisa 4.0. Customers can also get some details on licensing and roadmap for OrgHub for Mobile in the Nakisa OrgHub™ for Mobile app blog that was released last year.

    Best regards,


    1. Stephen Millard Post author

      Hi Luke.

      That’s an interesting statement you’ve made about naming…

      I would suggest that the applications have in effect been renamed.  You’ve noted that the names remain on the SAP Master Price List.  I agree that this is a “Master” list but I would imagine that it is just out of date and that it is the processes that generate this list that are perhaps lagging behind.

      The new names have been used in official Nakisa press releases, all of the various technical and supporting documentation, the Nakisa web site, the Nakisa demonstration videos, web casts from Nakisa, correspondence from Nakisa, Nakisa 4.0 training courses, in social media by Nakisa staff and in the application names on the SAP Service Marketplace.  I’ve even heard Nakisa staff refer (for example) to ‘DataQualityConsole is the old name for OrgAudit’.

      The only other place I’ve seen older names still retained is in the Nakisa Sales App.  I had assumed that this was just so that it did align to the SAP Master Price list for SAP to keep things simple for sales folk.

      It may be that there’s other documentation I haven’t had access to or that I’ve missed some reference in the documents I do have, but to me the evidence heavily weighs on the side of the naming being ‘renames’ rather than what would be a more confusing ‘also named’ scenario.  I just don’t see the benefits Nakisa would gain from doubling up on naming.  I just see a negative side in that it would only serve to confuse clients and that would then potentially reflect in a similar way upon Nakisa and their products.

      I had also already linked to one of your posts that you commented about in the further reading section at the end of the post and isn’t the OrgHub for Mobile roadmap still being firmed up?  That’s certainly the impression I got from Nakisa a couple of weeks ago when following up a few queries for my OrgHub for Mobile blog post.  There was limited future roadmap information that they could confirm for use in a public forum.

      — Stephen.

      1. Luke Marson

        Hi Stephen,

        My information comes from Nakisa, from both Marketing and the executive responsible for this overall area at Nakisa. Nakisa and I have already spoken today and someone will post a comment on your blog in due course to confirm this. As you know, I work extremely closely with Nakisa and SAP on a number of initiatives so I have access to this type of information. Also, my blog on 4.0 specifies this information and was confirmed by Nakisa prior to publication. Therefore if in doubt in future you can reach out to Nakisa or myself.

        And yes, the roadmap information is limited publicly but there is some information there. That blog also contains information provided by Nakisa.

        Best regards,


  3. Melloney Jewell

    Hi Luke & Stephen,

    Thanks for your blog contributions on Nakisa 4.0. Both your blog here Stephen and Luke’s blog:  What’s new in Visualization Solutions by Nakisa 4.0 give comprehensive and honest accounts and are a great way for readers to find out more about the latest features in Nakisa 4.0.

    Nakisa 4.0 brought with it many new features, functionality and improved performance. Along with this, Nakisa has put a particular focus on the users of the Nakisa applications and the business challenges that the Nakisa solutions help them to solve. To better communicate this to our audience we took the decision to realign our product names with this value proposition. For example, the decision to update the name of our Data Management tool from DataQualityConsole to OrgAudit was taken to better reflect the wider capabilities of the tool that stretch beyond the correction of data errors. Similarly, we have updated the names of our talent management applications to reflect the consolidation of the modules within the talent management suite, based on the user. The decision to unify the functionality in our talent management solution is representative of our overall strategic direction for both our org and talent management suites.

    Nakisa products have been official SAP solution extensions for several years. As SAP solution extensions, Nakisa products are sold by SAP on the SAP Master Price list under brand names that were chosen by SAP and Nakisa. Currently, there are no plans for SAP to change the names of the Nakisa solutions as listed in the Master Price list. SAP Organizational Visualization by Nakisa (SOVN) and SAP Talent Visualization by Nakisa (STVN), and their accompanying modules such as DataQualityConsole, are simply the names by which SAP chooses to market and sell Nakisa solutions. This is why you will still see SAP and Nakisa joint marketing materials using the SAP brand names. As you point out in your blog Stephen, the Nakisa Sales App retains these brand names as this is primarily targeted at SAP sales representatives and partners and must align with the SAP Master Price list.

    Nakisa continues to build innovative solutions for Organization and Talent Management and it is the needs of our customers that drive our value proposition and the way in which we package and market our solutions. If anyone has any questions regarding the naming conventions for the Nakisa solutions or would like to know more about the functionality in Nakisa 4.0 and the Nakisa roadmap, I would be happy to answer these and can be reached at


Leave a Reply