1 / 34

HR-XML: Standardizing HR Data Interchange for a Heterogeneous Environment

Learn about HR-XML, an independent organization that defines standard vocabularies to streamline HR data interchange. Discover the benefits of implementing HR-XML and how it can help overcome integration challenges in the HR industry.

mcglade
Download Presentation

HR-XML: Standardizing HR Data Interchange for a Heterogeneous Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Member Orientation January 30, 2003 Kim Bartkus

  2. Introduction • HR Problem Domain – Current and Future • What is XML? • What is HR-XML? • HR-XML Projects • CPO Overview • What’s Next?

  3. The best standards are the ones you take for granted…. Heterogeneous environments tied together by standards: Electricity. A common voltage and plug within most countries; known and standard means for converting voltages and adapting plugs when moving between countries. Air Traffic Control. A Spanish pilot arriving in Paris speaks English and uses a “controlled vocabulary” agreed to by international aviation authorities.

  4. Standards For HR? • Definitely a ‘heterogeneous’ environment • HR by-passed by EDI standardization (Purchasing, Insurance, Banking, Transportation where EDI had impact) • One one hand…HR costs, drive to outsource, and “fit” have driven rapid web enablement of HR functions • On the other…Because of the lack of standards, connecting different systems involves point-to-point, custom integration

  5. What Is Needed? • A Standard business vocabulary: • HR-XML, Vertical and cross-industry business vocabularies • Standard Implementation Frameworks • Web Services • SOAP • ebXML

  6. What is XML? • XML is a recommendation issued by the World Wide Web Consortium, February 1998 • A language for creating “markup” languages or “vocabularies” • Looks like HTML, but XML allows the definition of custom tags to describe information explicitly • XML Schema provides a flexible and powerful means of defining vocabularies

  7. What is HR-XML? • Independent, non-profit corporation (Dec 1999) • Define standard vocabularies to streamline HR data interchange • Open to vendors, consultants, standards bodies, employers and other end-users, and individuals • 110+ organizational members • International – Mission to produce specifications that are relevant and useful across many country contexts.

  8. What Does HR-XML Deliver? Transport (e.g. HTTP, FTP, SMTP) Protocol (e.g. XP, SOAP) HR-XML focuses on specifications for message payload, but aims to provide context and guidance to enable the entire exchange. Framework (e.g. ebXML, BizTalk) Payload (e.g. JobPositionSeeker) Payload Includes the information necessary to complete an interaction within a businessprocess.

  9. Who’s Driving HR-XML? Acord; Adecco Corporation*; ADP*; Aetna US Healthcare*; Allegis Group, Inc./Thingamajob.com*; American Background Information Services, Inc.; American Staffing Association; ARINSO International; Association of Test Publishers; Authoria*; BEA Systems, Inc.; Best Software; BP; BrassRing, Inc.; CareerBuilder; CDI Corp/MRI*; Ceridian*; Cisco Systems; CitiStreet*; CompuCorps Mentoring; Crestone International*; Cross Current Corporation; Cyborg Systems, Inc.*; Defense Finance and Accounting Service; Development Dimensions International; Dobbs Temporary Services, Inc.; eBenX*; Embrace Ltd*; Employease, Inc.*; Enrollcom; e-peopleserve ltd; esohXML.org; European Community Telework Forum; EVolve Software; ExecuTRACK Software GmbH; Fidelity Investments*; Fieldglass, Inc.; Great Plains*; Halcyon Internet plc; HayGroup; Hewitt Associates LLC*; Hewlett-Packard Co; Hire.com*; HireCheck*; HireRight, Inc.; HotJobs.com, Ltd.*; IBM*; International Association for Human Resource Information Management (IHRIM); Intuit*; iXmatch Inc.; J.D. Edwards*; Job Partners Ltd; JobScout24; Kadiri,Inc.*; Kelly Services*; Kenexa, Inc.*; Korn/Ferry International*; Kronos Incorporated; MagnaWare, Inc.; Manpower, Inc.*; MBH Solutions, Inc.; Microsoft HRIT; Minnesota Life; Modis Professional Services, Inc.*; Monster.com; MrTed; MSX International; National Resume Writers' Association; nextSource; Northrop Grumman Corporation; Object Management Group; Online Benefits, Inc.*; Oracle*; Peopleclick*; PeopleSoft*; Personic*; ProAct Technologies, Inc.*; ProBusiness Services, Inc.; Profile Up; Prudential Financial; Randstad Holding*; Recruitsoft, Inc.; Reed Business Information; RewardsPlus; Robert Half International, Inc.*; Rompetrol Refining -- Petromidia Complex; SAP*; Schlumberger; Shell Oil Company -- Shell People Services; Siemens Business Services oHG; Society for Human Resource Management; Spherion Corporation*; StepStone; Swedish National Labour Market Board; Synhrgy HR Technologies, Inc.; Tesseract Corporation*; The 401(k) Company; The Aviant Group; The People Business Network, Inc.; Towers Perrin*; Transcentive; Ultimate Software*; Unicru; Unifi Network; Vedior NV; Volt Services Group*; Watson Wyatt Worldwide*; William M. Mercer, Incorporated; Workscape, Inc.; and WOWemployers Network, Inc.

  10. Business SteeringCommittee Technical Steering Committee Organizational Structure Board of Directors Cross Process Object Payroll Benefits Enrollment Stock Recruiting & Staffing Competencies Time Reporting SIDES Other Projects

  11. New Projects • BSC requirements: • Proposal in standard template • 3 sponsor organizations • 8 participants • Resources identified for major roles

  12. Model Business Process • Describe general business process • Identify roles and responsibilities • Identify interaction points • Use a UML activity diagram • NOT a prescriptive standard for the business process!

  13. SEP’s JobPositionFeedback

  14. What Progress Has Been Made? • Approved Specs • Staffing Exchange Protocol (version 1) • Time/Expense Reporting • Time Card Configuration • Benefits Enrollment (version 1, 2) • Payroll Defined Contributions • Payroll Instructions • Staffing Industry Data Exchange Standard (SIDES) • Competencies (version 1) • Background Check (version 1) • Work Site and Environment (version 1) • Resume • Stock Options

  15. Approved CPO Standards • Person Name • Postal Address • DateTime Data Types • Effective Dating • Contact Method • Entity Identifiers

  16. The most commonly used attribute in HR transactions HR transactions in use today use many different schemas to represent names Many of these schemas today do a poor job of handling the many ways Name structure varies from country to country Person Name

  17. Schema

  18. Examples - Mexican Sr. Fernando Martínez Urrutia <PersonName> <GivenName>Fernando</GivenName> <FamilyName>Martinez Urrutia</FamilyName> <Affix type=”formOfAddress”>Sr.</Affix> </PersonName> <PersonName> <GivenName>Fernando</GivenName> <FamilyName primary=”false”>Martinez</FamilyName> <FamilyName primary=”true”>Urrutia</FamilyName> <Affix type=”formOfAddress”>Sr.</Affix> </PersonName>

  19. Postal Address • A container allowing business processes to pass address information reliably and completely, and in a format that can be efficiently processed • The container houses the various sections that make up a postal address as it is used from country to country, with a country code that enables formatting according to local postal rules

  20. Schema

  21. Examples - USA <PostalAddress> <CountryCode>US</CountryCode> <PostalCode>50493-1234</PostalCode> <Region>MN</Region> <Municipality>Minneapolis</Municipality> <DeliveryAddress> <StreetName>Euclid Ave</StreetName> <BuildingNumber>4982</BuildingNumber> </DeliveryAddress> <Recipient> <PersonName> <GivenName>Santhi</GivenName> <FamilyName>Mwanza</FamilyName> </PersonName> </Recipient> </PostalAddress> Santhi Mwanza 4982 Euclid Ave Minneapolis, MN 50493-1234

  22. DateTime Data Types • XML Schema has datetime data types, but these basic types needed extensions for use in HR • Extensions needed when we want to specify: • just a date vs. a date with a time, and sometimes a timezone specifier. Example - new hire date vs. an accident date and time. • open ended dates. Example - passing an employee termination date for an employee who is not terminated • Passing unknown dates. Example the hire date is not available.

  23. Examples

  24. Effective Dating • Provides guidelines for use of effective dating in HR-XML Consortium standards • When to use Transaction Date/Time vs. Effective Date/Time • How to determine the granularity required for effective dating • How to use Effective Dating with different types of processes, i.e. Inserts vs. Modifications • When to use the various types in the DateTime Data Types when applying effective and transaction dating

  25. Examples <EmploymentHistory> <HireDate>2001-06-01</HireDate> <TerminationDate>2002-02-16</TerminationDate> … </EmploymentHistory> <EmploymentHistory> <HireDate>2001-06-01</HireDate> <TerminationDate>notApplicable</TerminationDate> … </EmploymentHistory> <EmploymentHistory> <HireDate>2001-06-01</HireDate> <TerminationDate>notKnown</TerminationDate> … </EmploymentHistory>

  26. Contact Method • Many HR transactions need to pass contact information • Each contact person may have more than one method of contact –telephone, mobile phone, email address, fax, etc. • Methods have use – business, business direct, personal, etc. • Methods have location – office, car, home, etc. • Methods have times of availability – weekends, 24x7, etc.

  27. Schema

  28. Schema

  29. Entity Identifiers • HR transactions pass objects around • A subsequent transaction may need to refer to objects passed in an earlier transaction • Objects need identifiers for this to happen • Much like foreign keys in relational databases

  30. Schema

  31. Example <BenefitEnrollmentRequestList> … <RequestToEnrollEmployee> … <SenderEmplId validTo=“2003-01-01” idOwner=“Jobo Ltd”> <IdValue name=“SubsidiaryId”>KD49</IdValue> <IdValue name=“EmployeeId”>4853905</IdValue> </SenderEmplId> </ RequestToEnrollEmployee > …. </BenefitEnrollmentRequestList>

  32. Specifications up for Vote • Payroll Instructions • Screening (version 2) • Histories (version 2) • Organization (Legal Entity, Work Unit) • WorkSite and Environment (version 2) • CPO’s • Industry Code • Entity Reference • Internet Domain • Duns Number • ISO Utilities

  33. What Work is in Progress? • Competencies (version 2) • Employee Stock Purchase Plans • SEP (version 2) • SIDES (version 2) • Data Dictionary • Cross-process objects • Background Checking

  34. kim@hr-xml.org http://www.hr-xml.org

More Related