Internal Social Network Analysis

Following yesterday’s post on future recruiting technology, which looking back should have read future talent management technology, here is an example of thing I am seeing in the market.

SAP has built a Social Network Analyzer prototype for inside the organisation. (Hat tip James Governor.)

It aggregates existing enterprise data to display and discover organizational relationships. It provides the missing link between social networking platforms and enterprise information systems, by letting organizations leveraging data available in corporate information systems.

SNA helps jump-start social networking within the organization by letting you import and aggregate all the corporate relationships between people that are already recorded in your business applications, such as:

  • Management hierarchies from your human resources system
  • Data on who worked on which deals from your sales force automation system
  • Partner, customer, and partner supplier contacts along your supply chain
  • People who work on similar transactions within your operational systems

The early images show a product user interface that is very different to anything I have seen from the German Giant.

The tool bring data from disparate systems across the enterprise into a single view to see who is interacting with whom via relationships there can be significant talent management benefits, other than collaboration:

  • Look at the interaction of at risk high performers, are their other high performers that also might be at risk due to social relationships?
  • Top talent referrers, who else do they interact with and are they providing referrals, if not why?
  • Do poor performers interact together?
  • Do top performers interact together?

The tool can import any data that describes a relationship between two people or objects you can uncover relationships between individuals, groups and departments that do not appear in the traditional organisation structure.

Now what if we added into the mix information about external social networks??

Let’s not forget the privacy issues, to quote James:

I thought it was kind of funny, though obviously not surprising, that one of the reasons SAP has been slow to turn the prototype into product is European data protection law. While American firms would consider metadata about employee interactions to be company property, under German law that is certainly not the case – no, in Germany it would be called spying.

Will this product see the light of day? Will it be deployed in many organisations? What would trade unions think of the tool? All these questions and more will ultimately determine the future of this particular technology.

Cloud/Grid/Utility Computing what is it & must you have it?

Today I want to discuss the latest hype in the HR technology space, Cloud/Grid/Utility Computing. Now the terms utility computing and grid computing have been around for a while now, however cloud computing is areasonable new term.

First up they are not the same thing! They can be related but they are not the same.

Let me start with utility computing. According to Wikipedia the first real reference of utility computing goes back to 1961!

If computers of the kind I have advocated become the computers of the future, then computing may someday be organized as a public utility just as the telephone system is a public utility… The computer utility could become the basis of a new and important industry. – John McCarthy, MIT Centennial in 1961

So utility computing is:
  • Pre-packaged resources
  • Low or no initial cost for hardware
  • Typically rented
  • Rapid growth of capacity
  • Always on like electricity or water

Grid computing on the other hand is completely different:

  • Applying the resources of many computers in a network to a single problem at the same time
  • A form of distributed computing
  • Usually based on open standards
  • High levels of reliability

Finally we get to cloud computing, again from Wikipedia we get this quote:

According to a 2008  paper published by IEEE Internet Computing “Cloud Computing is a paradigm in which information is permanently stored in servers on the Internet and cached temporarily on clients that include desktops, entertainment centers, table computers, notebooks, wall computers, handhelds, sensors, monitors, etc.”

So attributes of cloud computing are:

  • Customer do not own the infrastructure
  • Access is usually based on rental
  • Can be based on the utilitiy model
  • Delivered as a service with data stored in the cloud

Now this is very confusing as how do all these terms different from “Software as a Service” (SaaS) or Application Service Provider (ASP) models for software delivery?

I see things in a rather simple fashion. To some degree ASP has become SaaS with some addtional features, which is now moving towardds cloud computing but not always as there are other pieces to cloud computing. All can be done with a grid or utility model again not always. Now some technology architects will disagree with this simplified model but I feel it works.

Marketing folks will repackaging existing tools to use the new buzz words. For example Taleo back in September at Taleo World annouced “The Talent Grid, built on Taleo’s on-demand application platform, will deliver the infrastructure and resources to power organizations’ future talent needs”. Based on the press release it is not a grid computing model but using the name gives the average person the wrong sort of messages. They are certainly moving towards a cloud model but if they are not really doing grid are they really doing cloud or is it just marketing? To be honest I have not seen the details of all their products so I cannot answer the question.

I would suggest Taleo are not doing cloud 100%. Why? Review these 15 items by James Governor from MonkChips to get the general idea, some are a bit tongue in cheek but should give you a starting point.

If you peel back the label and its says “Grid” or “OGSA” underneath… its not a cloud.

If you need to send a 40 page requirements document to the vendor then… it is not cloud.

If you can’t buy it on your personal credit card… it is not a cloud

If they are trying to sell you hardware… its not a cloud.

If there is no API… its not a cloud.

If you need to rearchitect your systems for it… Its not a cloud.

If it takes more than ten minutes to provision… its not a cloud.

If you can’t deprovision in less than ten minutes… its not a cloud.

If you know where the machines are… its not a cloud.

If there is a consultant in the room… its not a cloud.

If you need to specify the number of machines you want upfront… its not a cloud.

If it only runs one operating system… its not a cloud.

If you can’t connect to it from your own machine… its not a cloud.

If you need to install software to use it… its not a cloud.

If you own all the hardware… its not a cloud.

Am I wrong? Thoughts, comments?