Skip to Content
Author's profile photo Stephen Millard

Hands on with Nakisa OrgHub for Mobile – Part 1

Today Nakisa formally launched their new OrgHub for Mobile application onto the Apple App Store.  It seems every man and his dog seem to be developing mobile applications to serve up corporate data and services, so how does this new application stack up?

In this post I aim to give you my thoughts and experiences of working hands-on with this application and to give you a view of the usability and features.  I’ve included an entire gallery of actual screen shots so you can get a feel for what is available in case you don’t have access to the necessary hardware to test run the application for yourself.  In fact there are so many screen shots used that I had to split this into two SCN posts.  I guess that’s what you get for working with visualization software!

The Basics

So what do you need to have in place in order to use the application?  Well you need the following things.

  1. An Apple iPad (running iOS 5 (or higher)).
  2. An OrgHub for Mobile enabled SOVN OrgChart installation.
  3. Network connectivity between your iPad and OrgChart system (e.g. an Internet connection over VPN).
  4. The OrgHub for Mobile application.

Fortunately Nakisa have been kind enough to provide a Demo system and the application itself is absolutely free (the cost of use is based on per user licensing on the target system), so all you probably need is an iPad.

The application is available on the Apple App Store, so you can follow the link below on your iPad to access the application.

00-app store 2.png

Once you have installed the application and open it you are presented with an option to connect to the Demo system or to connect to your own.

00-initial prompt.png

Unfortunately I don’t have a system of my own and at this moment in time very few people will.  In fact if you want to get started using your own version you’ll definitely need to contact Nakisa or a Nakisa Partner at this point.  So based on that I opted for the Demo system option.  Selecting this automatically logs you into the Nakisa Demo system.  However if by the time you read this you do happen to have access to your own system, then you can configure access to that from the iOS Settings application.


Notably this provides you with an auto logon option, so if you have access to sensitive information via the application you may wish to think before you enable that option.

Getting Started

When the application first opens it defaults to showing (as you might expect) an org structure chart.  The particular hierarchy will be the same as that specified in the OrgChart configuration.  In fact any configuration in the source OrgChart system (addition/removal of fields, defaults, caption changes, etc.) should be reflected in the OrgHub for Mobile application.

02-org structure-manager-standard.png

However I’m going to set aside digging any deeper into the chart functionality at this point to cover something important.  I’m very much the kind of individual who likes to research first rather than just jumping in blindly. So whilst I will admit that the application is very natural and easy to use I’d like to take a few moments to highlight a very special feature.  It’s known in IT circles as “Help”.

The application does include a handful of help screens.  They are accessed by tapping on the large question mark in the top right of the screen.

The first help screen provides a list of icon and box colouring definitions.  This is very similar to the one available in the desktop browser application but cut down to match the OrgHub for Mobile interface.

07-help 1.png

The list isn’t an exact match to the standard list I might expect to see in OrgChart, but then again it doesn’t need to be.  This is listing the items in use in the mobile application after all.

That being said occasionally when customising an OrgChart installation you need to do things like add additional icons.  So how do you get these into OrgHub for Mobile?  Well it’s a relatively straight forward task of amending an XSL file.

If you notice at the bottom of the screen, there are three dots.  One blue followed by two white.  These indicate what screen you are on and you’ll see these cropping up in other parts of the application too.  On the right of the screen you can see the OrgHub for Mobile logo.  This part of the screen is inert.  Only the help panel on the left of the screen is active, so if you swipe from right to left within this you’ll arrive at the second screen of help.

The second screen describes the gestures available in the application.  I found this useful as when I first came to use the application I had some incorrect preconceptions about how I expected the application to work.  I had imagined pinching and zooming would be the way you moved around a chart and pressing and dragging would manoeuvre the chart around.  In effect I was expecting something very similar to the sorts of mouse gestures I might employ in the desktop application.

However the navigation gestures and indeed the chart layout methods are a little different to the desktop browser version.  Now this isn’t a bad thing.  In fact I think it shows that Nakisa have given much more consideration to it than I had at the point at which I opened the application.  The application has been designed as a tactile mobile screen sized experience and hands-on … it seems to work pretty well.  So what are these gestures?

07-help 2.png

  • In a standard styling (more on stylings later) to make a box the root node of a chart swipe it up to the top of the screen.  This part of the screen is only ever occupied by one box.  If you have a vertical styling there isn’t really a top part of the screen, but swiping a box to the top ultimately has an equivalent effect.
  • Swiping a box at the top down will set its parent to be the root node.
  • Tapping once on a box will show its details panel.
  • Double tapping a box (in a non-assassin way) on a box in a vertical styling will “expand” the chart structure to reveal the boxes at the level beneath the box tapped.  Unlike the standard styling, this will actually leave all of the previously shown boxes visible.
  • The last gesture wasn’t one I think you would easily guess, but sometimes you can get listings column headings that are truncated by the column width.  If you’re not sure what they are, press and hold to display a little pop-up.

So that’s the navigation gestures they tell you about, but here’s some more that might be obvious and/or useful.

  • When a details panel is shown for a box or listing entry, tapping another box or item will load in the details for that object.  To hide the details panel tap on the dark grey application background.  This is easy for a chart as there is always lots of background visible.  On a listing, look just outside the edge of the listing itself.
  • When a details panel is shown you can swipe it closed by swiping the left edge of the panel to the right.  Now I did find this tricky and I know it isn’t just tapping a chart background first as I’ve actually done this over both org unit and position boxes.  To bring the panel back,  look on the very edge of the screen and you’ll see a glow (in charts) or a bar (in listings).  If you swipe this to the left the details panel for the last viewed object will be revealed.
  • When an org chart is vertically styled you can scroll the chart up and down by swiping up and down (respectively) on the chart background.
  • When an org chart is using the standard styling, the bottom two thirds of the chart can be scrolled up and down by swiping up and down (respectively) on the chart background.
  • In listings, swiping up, down, left and right will scroll and pan the listing to reveal more data (left/right) for the listing items or more listing items (up/down).  Twelve items are shown per screen so if you have big sets of search results you’ll do a lot of scrolling, but it uses a nice rebound scrolling effect and it is pretty effortless to do in the application.

The third help screen appears to be a little bit of a let down.  It simply states – “If you are experiencing any difficulties with the application, please contact your company’s IT department”.

07-help 3.png

As help text goes I think most people could figure that one out for themselves.  However you can modify this text to something more appropriate for your organisation.  It is simply a case of amending one of the captions within OrgChart (a relatively simple administrative task).

It would be really useful if this were cached locally upon a successful logon so that in the event of it being a connectivity issue the details could be put up instead of just a message about there being no connectivity.  In fact a little ‘diagnostic and technical assistance’ page would be even better!  I noted in an earlier App Store release of the application, there was a micro-bar chart that seemed to be measuring a heart beat back to the OrgChart server.  This sort of thing might be handy to have or log to a diagnostics page – but then again I’m probably not a typical user.

To exit out of the help just tap on the nice big (I’m sure that was smaller in the first App Store version) cross in the top right of the screen to be returned to the main application.

At the bottom of the main screen are two large buttons – OrgChart and Directory (a.k.a. Listings / Search).  So let’s start taking a look at the real functionality of this application.  Let’s look at some org charts.

Chart Run Down

The charting functionality in OrgHub for Mobile has familiar (for those of you who have used the OrgChart application) viewing options.  Three buttons adorn the top bar.  These buttons when tapped reveal drop down menus.

Active menu options are highlighted in blue.

There are two options under “Hierarchies” (on the Demo system); Organization Structure and Position Hierarchy.  The first option will chart the organisation as organisational units and the positions within those units.  The second option will display only positions in the reporting structure.  So the first option maps the way the organisation is structured whereas the position is maps the line reporting hierarchy.

02-org structure (menu).png

The second menu is Views.  Views determine what data is shown in each type of box of which there are three types: organisational units, positions and employees.

Out of the box, OrgChart includes an org structure with employees but it is quite common to disable this and just use the generally more meaningful org structure with positions.  This hierarchy doesn’t appear to be enabled on the Demo system, so if you do want to see the employee boxes and respective views you might want to detour to listings to do so (there’s a screen shot with them in later on though).

02-org structure-(menu) 1 & 2 cropped.png02-org structure-(menu) 3.png

Notably the views menu also has a sub menu of analytic based views.

02-org structure-(analytics menu) 1 & 2 cropped.png

The final menu is Styles and this determines the way in which the chart boxes are laid out.

02-org structure--(menu).png

The first option, standard, places the root node in the top third of the screen.  The nodes one level down in the hierarchy is then laid out in a grid in the bottom two thirds of the screen.  This bottom section may be scrolled up and down if there are too many nodes to be drawn on screen.

The second option, vertical, draws the boxes in a tree hierarchy (with connecting lines) and is able to be expanded to show multiple levels of the hierarchy.

The screen shots below show a variety of hierarchies, views and styles.

Standard style Org Structure hierarchy with cost centre view for org units and standard view for positions.

Vertical style for Org Structure hierarchy with manager view for org units and standard view for positions.

02-org structure-manager-vertical with expanded node.png

Standard style Org Structure hierarchy with cost centre view for org units and standard view for employees.

02-org structure-standard-standard (employee).png

Standard style Org Structure hierarchy with nationality analytics view for org units and standard view for positions.

02-org structure-analytics (nationality)-standard.png

Standard style Position hierarchy with country view for positions.

03-position hierarchy-country-standard.png

Standard style Position hierarchy with Detailed view for positions.

03-position hierarchy-detailed-standard.png

This last screen shot is particularly interesting as it shows the contact details for the position’s incumbent.  This includes both the telephone number and the e-mail address. 

Nakisa have certainly been active in tweaking this release in the past few days as the e-mail addresses are now “active”.  If you tap on an e-mail address anywhere in the application it will leave the OrgHub for Mobile application and open the Mail application; pre-populating the e-mail address with the one selected.

It would be good to see the addition of some way to trigger telephone calls added in the future (Skype is a VOIP application capable of this for example).  This may be keyed more towards any future iPhone development where there is a built in cellular app for making telephone calls.

There is of course a limit as to how much you can fit into a box in a chart and this is where the details panel comes in.  By selecting a box (or an item in a listing as you’ll see later), you can open a panel on the right hand side of the screen.

02-org unit details-details.png

The details panel has up to three separate sets of data each indicated by a button at the top of the panel.  These equate to the tabs you would see in OrgChart and so for the sake of parity I’ll refer to these as tabs (otherwise I’m going to start having to reuse terms like view or panel).

The Details tab provides basic details about the box selected.  The exact data content varies depending upon the type of object selected and of course any customisation that may have been carried out on the panel in OrgChart.  In the Nakisa Demo system the content is of course standard out of the box stuff.

In the screen shots above and below you can also see that data of related objects can be incorporated – e.g. the manager of the org unit and the incumbent in the position.

03-position details 1 & 2 cropped.png

In both instances you should also be able to make out a button in the top right corner that looks like a small org chart.  Clicking this will open the relevant hierarchy to view the object in-situ within the hierarchy.

The position details panel also includes an organizational silo report section which shows the position within a branch of the org hierarchy and down to the employee(s) holding the position.

If there are instances where there are multiple incumbents you’ll see dots just like we did in the help.  Swiping left and right will change the information shown.

02-org unit details multiple managers.png

The second and third tabs are available for org units and only to users who have the requisite permission to view them.  This might typically restricted to universal access to key HR staff and executive teams, and access to own org unit and below for managers.  The two tabs show Staffing and Demographic information for the org unit and the org units beneath it.

The Staffing tab gives details such as head count and full time equivalent (FTE) for the org unit and all org units from that point down in the structure.

02-org unit details-staffing.png

The Demographics tab offers a wide range of information about several demographic areas (including age, disability, equity, ethnicity, FTE, gender, nationality, position statistics and race).  To change the demographic view, tap on the Demographic button on the right of the demographics description and select a demographic from the drop down menu.

02-org unit-demographics (menu).png

Like the staffing information this is available both for the org unit and for the org unit and below – simply swipe the panel left/right to move between the two sets of information.

02-org unit details-demographics 1.png

02-org unit details-demographics 2.png

Demographics are displayed as charts (you can switch between bar and pie charts by taping on the chart symbol (see the first screen shot of the pair above)) and tables, with the exception of Equity which only uses tables.

02-org unit details-demographics-equity.png

Where a table is too large to fit on the panel, you can scroll left/right and up/down by swiping within the table area.  It isn’t always immediately obvious that the table has content that can be scrolled, but if you check the rows against the number of corresponding colour coded entries in the chart and review what is actually shown it’s usually immediately obvious.  However there is a better solution for this….

The Staffing and Demographics tabs can also be viewed full screen rather than in a details panel.  To enter full screen mode tap on the button next to the Demographic button.  It has two double-headed arrows on it in the shape of a cross.

02-org unit details-demographics-age bar (full).png

To exit the full screen mode tap on the button with four inward pointing arrows in the shape of a cross.

So at this point we have to temporarily draw a close, but don’t fear the second post will be immediately available.  So why not join me to find out about Directory, some important additional considerations and some final reflections in Hands on with Nakisa OrgHub for Mobile – Part 2 ?

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Luke Marson
      Luke Marson

      Hi Stephen,

      An interesting overview made all the more better by a large variety of screenshots. You definitely benefit from having availability to the application, which unfortunately wasn't yet available to partners when Nakisa and I worked on my Nakisa OrgHub™ for Mobile app blog last year. And until they release it on Android, I still won't have it 😉 .

      Customers can get more details about Nakisa 4.0 in my blog What's new in Visualization Solutions by Nakisa 4.0.

      Best regards,


      Author's profile photo Stephen Millard
      Stephen Millard
      Blog Post Author

      Thanks Luke.  The idea was to give the reader a real feel for the application.  I actually started formulating this post many weeks back when there was more of a soft launch and the first iteration appeared on the app store.  Since then I've seen one major update to the application and numerous tweaks on the demo system back end to the point where every few days I had to revise what I'd written.  When finishing the post yesterday it was a real flurry to get all the last tweaks and changes in ... I basically had to review everything and I guess there's a chance I still may have missed the odd thing.

      I'm also looking forward to seeing how Nakisa develop the application for other platforms.  With HTML5 as the core I expect there will be a lot of similarity.  However I'm intrigued as to how they will manage the variation in form factors.  From what I hear this app is intended for use on a full size iPad (rather than the iPad mini) and the variety of sizes available in Android hardware means that this will certainly be a significant challenge to create some sort of responsive design in the interface.

      Author's profile photo Luke Marson
      Luke Marson

      I don't know, my iPhone-owning friends call my Galaxy S3 an iPad 😉

      Author's profile photo J. Pazahanick
      J. Pazahanick

      Good job with this two part series Stephen and if I understand correctly the application has no additional cost which I think is a smart strategy by Nakisa.

      I noticed this application is not built on the Sybase Unwired Platform which I know SAP HIGHLY encourages their partners to build apps on. I can imagine there are many dynamics in play with the purchase of SuccessFactors there is no doubt not using SUP would have made some folks at SAP unhappy but I can definitely understand why Nakisa did it.

      It will be curious to get an update from either you or Luke 6 months from now on what the uptake on this offering is.

      Author's profile photo Stephen Millard
      Stephen Millard
      Blog Post Author

      Hi Jarret - thanks for taking the time to leave a comment.

      The application is free, but I believe there will be an additional nominal one off licence for each user.  I think the approach they have is *much* less expensive than SUP and I could only speculate as to the politics involved in this, but I would guess that the introduction of SuccessFactors into the mix might well have given Nakisa some "wriggle room" on things.  Hopefully this will just increase the adoption for end users.

      I know my colleague Stephen Burr has already had keen interest from one client, so whilst it's not a fantastic sample size (as you say six months might be a good point to review) I think it could be construed as a positive indication.

      Give me a nudge in six months and I'll try to give you an update 😉

      Author's profile photo Stephen Burr
      Stephen Burr

      Hi Jarret,

      The app is free to download from the App Store but requires a licence for each end user to use (customers should contact their local Nakisa rep for details).


      Author's profile photo J. Pazahanick
      J. Pazahanick

      Hi Stephen

      Is the license to use the mobile app an additional one for customers that already have a license to use Nakisa on a desktop/computer?



      Author's profile photo Luke Marson
      Luke Marson

      Hi Jarret,

      I covered the licensing in my blog Nakisa OrgHub™ for Mobile app last year and the answer is yes. Customers must license the use of the app at $10 per user in addition to the OrgChart license.

      Best regards,


      Author's profile photo J. Pazahanick
      J. Pazahanick

      Thanks Luke and is it $10 a year per user?

      Author's profile photo Luke Marson
      Luke Marson

      $10 per user in perpetuity

      Author's profile photo Stephen Burr
      Stephen Burr

      As Luke has already answered ... yes.

      Like you (I suspect), I was disappointed by this.  I believe Nakisa thought long and hard about it but I don't actually know the reasoning behind the decision to charge. 

      To me, how you access a service shouldn't matter in most cases.  In UK we have Sky TV for example and customers can use Sky Go service on 2 devices "free" (i.e. as part of their subscription for the TV service).

      Good news though is that it is there and 4.0 customers can benefit from it ... if they pay 😉 .



      Author's profile photo Luke Marson
      Luke Marson

      Nakisa believe $10 to be a low price-point and when evaluated against what it costs to user the SUP infrastructure it comes out at a low cost. They realize not many organizations will roll this out across the entire organization and even if so, the cost only becomes prohibitive for very large companies. And even in that scenario I would strongly guess that a discount would be available.