I've been doing a lot of blogging lately, and I don't just mean posting a bunch of stories. I've been posting stories and digging and stumbling and all kinds of crazy things. Despite all of this, most of my hits are still on that one HR-XML article I wrote last year.
That brings up a few thoughts. First, if so many people are looking for information on HR-XML so consistently, they must be actively accepting it or rejecting it, and I'd like to know which and why. Second, I'd like to know who is doing what with HR-XML.
So, when you finish reading this post, I'd really appreciate your comments. What have you decided to do with HR-XML? What led you to this decision? What solutions have you already implemented with HR-XML to date?
My company has been evaluating HR-XML for several months, but we haven't yet implemented an HR-XML solution. We produce several components of an HR suite of software and we have integrated with a number of applications including background check vendors, HRMS, and ATS, but not one vendor has had an HR-XML integration solution (even one particular vendor which purports to be nearing an HR-XML integration solution).
We've been waiting for a partner to be HR-XML capable before we develop our own HR-XML integration. The problem is, I think everybody else is doing the same thing. Well, we're in a good position because the more customers we get and the more applications we have, the more we need our own internal applications.
So, we have decided to take the initiative to develop an HR-XML integration with all of our applications. This will give us a common and standard format with which to transfer data not only among our own applications, but with other applications and vendors as well. Future integrations will go through an "HR-XML layer," including custom integrations. By that, I mean rather than developing integrations to read from spreadsheets and CSV files and then to write directly to our databases, they will first be reformatted to HR-XML and will then be consumed by our HR-XML import engines.
Exports will be handled similarly. This gives our developers and our partners' developers a contract on which to map any imported or exported data without having to know anything about our internal data structures. We're hoping that as we integrate with more and more vendors, that they will also adopt HR-XML allowing all companies which provide human resources software and services to work harmoniously and interchangeably together throughout the entire employee life cycle.