Human Resource
Recommendation, 2006 Feb 28
Editors:
Kim Bartkus, HR-XML Consortium
Kathi Dolan, Manpower
Gail Bubsey, Kelly Services
Tara Ryan, Adecco
Barbara Johnson, Adecco
Contributors:
Bruno Alcotte (Manpower), Ian Anson (Vedior), Rémy Bailly (Randstad), Kim Bartkus (HR-XML Consortium), Yves Berdah (VidiorBis), PJ Brunyks (Randstadt), Gail Bubsey (Kelly Services ), Georges Chaboud (Adia), John DeRoche (Manpower), Kathi Dolan (Manpower), Serguei Dounaevetski (Manpower), Keith Ensroth (Kelly Services), Anne-Cécile Fénech (Adecco), Barbara Johnson (Adecco), Paul Kiel (HR-XML Consortium), Ronald Kruegel (Adecco), Jonathon Mack (Adecco), Magali Munoz (Manpower), Doug Prittie (Manpower), Nicolas Poujols (Kelly Services), Tara Ryan (Adecco), Don Simonson (Robert Half International), Steven Huang (Staffing Industry Sponsors), Barbara Theissen (Manpower), Jean-Philippe Umber (Adecco), Morgan Vernoux (Adecco)
Copyright statement
©2006 HR-XML. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher.
Abstract
The HR-XML SIDES Workgroup has produced 7 major schemas and several reusable modules to allow for transmission of Staffing Industry information between trading partners. This document describes the Human Resource schema, its expected usage, and the business processes meant to be supported.
Status of this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Table of Contents
4 Implementation Considerations
5 Appendix A - Document Version History
6 Appendix B – Related Documents
7 Appendix C - Reference Examples
1 Overview
A detailed analysis of the Sides 1.0 modules and Cross Process Objects was conducted by a coalition of Staffing Companies in France. The purpose of the analysis was to take a regional implementation perspective and to evaluate how closely the global specifications met localized requirements. Module by module feedback was documented and requests for additions or cardinality changes were structured based on the need for backward compatibility.
These feedback documents were sent to the global Sides development team for evaluation of the applicability of the requested changes. If a requested change could be used in more than one country, then it was considered to be eligible for the global specification. It was found that at least 90% of what was requested by the French team was indeed, more widely applicable and so formed the basis of this Sides 1.1 release. The elements and/or attributes that were only applicable in France, will be documented locally and handled through HR-XML’s localization architecture.
Below is a summary of changes along with the original Sides 1.0 base information for the Human Resource module. Please note that the correction to the AvailabilityDate is non-backwards compatible.
1.1 Objective
Within the framework of SIDES, the HumanResource (HR) XML document is used to describe a staffing resource’s skills and experiences as they relate to the position opening(s) received via the StaffingOrder XML document. The HumanResource schema is flexible enough to be used in the case of permanent placements, or for “marketing” temporary employees (i.e. sending information spontaneously as opposed to a response to a request); however, for SIDES, its primary purpose is in response to a StaffingOrder XML document.
Changes in this release reflect the creation of new Supplier and Customer Organizational Unit Identifiers and the new CPO for Position. See 1.2.4 for additional information.
1.2 Scope
1.2.1 Major Components
The Major Components used in the HumanResource process are listed below.
· ResourceInformation - specific information about the staffing resource, i.e. name, contact information, address, employment status (independent contractor vs. payrolled employee vs. other), and availability dates. Usually, in the staffing services scenario, the staffing resource’s name will be sent, and the contact information will be that of the staffing supplier. Typically, no postal address is sent.
· Preferences - describes any special preferences or requirements of the staffing resource that may relate to the position. For example, relocation preferences and resume distribution restrictions are described here.
· Profile - the staffing resource’s skills and experience are described here through use of the Competency schema and the Resume schema.
· ReferenceInformation.
· Screening.
· Rates.
1.2.2 Items within Scope
· Submittal of staffing resource’s skills and experience in response to a specific order and position.
· Ability to express the quoted rate for the staffing resource in whatever terms are appropriate (ex. hourly bill rate, hourly pay rate, x markup percentage, flat fee).
· Ability to pass structured XML or text resume information about the staffing resource.
· Ability to communicate screening results (meets/does not meet position requirements).
1.2.3 Items Outside of Scope
· Enumeration for most elements.
· Specific process flows for permanent placements and marketing of resumes, although either can be accommodated by the flexibility of the SIDES schema.
· Skills taxonomy.
1.2.4 Additions and Changes
|
Element path/name |
Details |
|
ReferenceInformation/StaffingSupplierOrgUnitId |
Add new component |
|
ReferenceInformation/StaffingCustomerOrgUnitId |
Add new component |
|
Profile/PositionHeader |
Add new component |
|
ResourceInformation/AvailabilityDate |
The ‘choice’ has maxoccurs=unbounded. Change choice to sequence. Move unbounded to AvailabilityDate. Make end date optional. This is a non-backwards compatible bug fix. |
2 Business Process
The Submission and Selection Process generally follows the Order Process. A HumanResource transaction is typically sent in response to a StaffingOrder XML document, although there are exceptions to this chain of events, for example, the marketing of employees. However, for the purpose of SIDES, the focus will be on the HumanResource XML document as a response to a StaffingOrder XML document. General steps are as follows:
· The StaffingOrder document is received and the staffing supplier has decided to pursue attempting to fill the stated position(s).
· The staffing supplier conducts a candidate search and match to the skills and experiences specified in the position. This process is unique to each staffing supplier and there will be no attempt to standardize it. (Recruitment Process)
· A particular staffing resource is chosen, their information placed in the format of the HumanResource schema, and that document is sent to the staffing customer.
· The staffing customer reviews the staffing resource’s information and may request additional information, for example regarding their qualifications, using the StaffingAction XML document.
· A staffing supplier may update the staffing resource’s information for a variety of reasons, for example in response to a query about a specific skill, to modify availability, or to remove the staffing resource from consideration.
· The staffing customer makes a decision to either accept or reject the staffing resource. This decision is conveyed to the staffing supplier, leading to the next phase of SIDES, the Assignment phase.
3 Schema Design
3.1 Human Resource
3.1.1 Schema Diagram
3.1.2 Data Dictionary
See Appendix B – Related Documents (SIDES Reusable Modules) for details on Rates and Resource Screening.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- HumanResourceType - (1/1) |
A person
who presently does work for, may do work for, or has done work for the
organization. |
|
/
HumanResource/ |
- EntityIdType - S (1/*) |
Reference to a specific HumanResource. |
|
/
HumanResource/ |
status - StatusType - required |
Assigns a status to a candidate or human resource transaction in relation to a business process. |
|
/
HumanResource/ HumanResourceStatus/ |
- StatusType - |
The
status of the associated item. If the status isn't specified, the implementer
may place the record in whatever status seems appropriate given the context
of the data. |
|
/
HumanResource/ HumanResourceStatus/ |
- xsd:string - |
Comment
field to allow description of why the status change has occurred. |
|
/
HumanResource/ |
StaffingSupplierId
- EntityIdType - S
(1/*) |
Contains reference information (a group of id's) regarding other business entities or transactions. |
|
/ HumanResource/
ReferenceInformation/ |
- EntityIdType - S (1/*) |
Unique id used to identify the staffing supplier. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (1/*) |
Unique id used to identify the staffing customer. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a Vendor Management System or 3rd party responsible for staffing management |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a staffing order. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a uniquely identifiable position. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Identifier
of the assignment eventually agreed to by the trading partners. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique
id used to identify a particular organizational unit of the staffing
supplier. |
|
/
HumanResource/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing customer. |
|
/ HumanResource/ |
ResourceType
- [complexType] - S
(0/1) |
Container for contact, eligibility and availability information about the staffing resource. |
|
/
HumanResource/ ResourceInformation/ |
independentContractor - xsd:boolean - required |
Container
for optional descriptor of the staffing resource. |
|
/
HumanResource/ ResourceInformation/ ResourceType/ |
- xsd:boolean - |
Flag to indicate if this staffing resource is an independent contractor. |
|
/
HumanResource/ ResourceInformation/ ResourceType/ |
- xsd:boolean - |
Flag to indicate if this person is a payrolled employee, meaning the staffing company did not recruit the employee, they only pay them. |
|
/
HumanResource/ ResourceInformation/ |
AvailabilityStartDate
- AnyDateTimeNkType - S (1/1) |
The
earliest date that the person will be available to accept a new position or
assignment. |
|
/
HumanResource/ ResourceInformation/ AvailabilityDate/ |
- AnyDateTimeNkType - S (1/1) |
Date the
person is available to start work. |
|
/
HumanResource/ ResourceInformation/ AvailabilityDate/ |
- AnyDateTimeNkType - S (0/1) |
Date the
staffing resource is no longer available for work. |
|
/
HumanResource/ |
Competency
- [see include/import] - S (0/*) |
Context definition: Employment related information about a person, as well as the position attributes they desire. Profiles are generally used as an alternative to a resume and are more conducive to matching.For example, Desired Compensation, Desired Schedule, Desired Positi |
|
/
HumanResource/ |
DesiredShift
- [complexType] - S
(0/1) |
Container for information about the person's employment related preferences. |
|
/
HumanResource/ |
- xsd:string - S (0/1) |
Comments about the staffing resource in general. |
|
Global types |
ContentModel* |
Definition |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: new, revised, rejected, accepted, withdrawn, suspended, pending |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownStatusType, xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
3.2 Preferences
3.2.1 Schema Diagram
3.2.2 Data Dictionary
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/
HumanResource/ |
DesiredShift
- [complexType] - S
(0/1) |
Container for information about the person's employment related preferences. |
|
/
HumanResource/ Preferences/ |
ShiftName
- xsd:string - S
(0/1) |
Description of any work schedule or shift preferences of the staffing resource. |
|
/
HumanResource/ Preferences/ DesiredShift/ |
- xsd:string - S (0/1) |
name designation of the preferred shift. |
|
/
HumanResource/ Preferences/ DesiredShift/ |
- xsd:decimal - S (0/1) |
Hours of the preferred shift. |
|
/
HumanResource/ Preferences/ DesiredShift/ |
- LocalTimeNkNaType - S (0/1) |
Start time of the preferred shift. |
|
/
HumanResource/ Preferences/ DesiredShift/ |
- LocalTimeNkNaType - S (0/1) |
End time of the preferred shift. |
|
/
HumanResource/ Preferences/ DesiredShift/ |
- xsd:string - S (0/1) |
Further descriptive information related to the preferred shift. |
|
/
HumanResource/ Preferences/ |
willingToTravel - xsd:boolean - required |
Information regarding if the person is willing to travel or the position requires travel. |
|
/
HumanResource/ Preferences/ Travel/ |
- xsd:boolean - |
Flag to indicate the willingness of the resource to travel as part of the position in question. |
|
/
HumanResource/ Preferences/ Travel/ |
- xsd:string - S (0/1) |
Percentage of time the Resource is willing to travel. |
|
/
HumanResource/ Preferences/ Travel/ |
- xsd:string - S (0/1) |
Describes
any special travel considerations. |
|
/
HumanResource/ Preferences/ |
TimeMax - xsd:string
- S (0/1) |
Container
describing the person's commute preferences. |
|
/
HumanResource/ Preferences/ Commute/ |
- xsd:string - S (0/1) |
Maximum amount of time the person is willing to commute. |
|
/
HumanResource/ Preferences/ Commute/ |
- xsd:string - S (0/1) |
Maximum
amount of distance the staffing resource is willing to commute. |
|
/
HumanResource/ Preferences/ Commute/ |
- xsd:string - S (0/1) |
Comments about commuting preferences. |
|
/
HumanResource/ Preferences/ |
willingToRelocate - xsd:boolean - required |
Contains informtion on whether relocation is an option for the candidate or considered by the hiring company. |
|
/
HumanResource/ Preferences/ Relocation/ |
- xsd:boolean - |
Flag to indicate the willingness of the resource to relocate for the position in question. |
|
/
HumanResource/ Preferences/ Relocation/ |
- xsd:string - S (0/1) |
Comments about relocation preferences or restrictions. |
|
/
HumanResource/ Preferences/ |
DoNotDistributeTo - xsd:string - S (1/*) |
Allows a person to list employers or recruiters to which the resume or information should not be distributed. |
|
/
HumanResource/ Preferences/ DistributionRestrictions/ |
- xsd:string - S (1/*) |
Any company, person, organization, etc. to which the information should not be distributed. |
|
/
HumanResource/ Preferences/ |
CompensationAmount
- xsd:string - S
(1/1) |
Contains the staffing resource's compensation preferences. |
|
/
HumanResource/ Preferences/ DesiredCompensation/ |
xsd:extension base: xsd:string |
The
monetary amount of compensation the staffing resource desires (requires). |
|
/
HumanResource/ Preferences/ DesiredCompensation/ CompensationAmount/ |
xsd:restriction base: xsd:string |
A
three-letter code identifying the currency of a monetary amount. |
|
/
HumanResource/ Preferences/ DesiredCompensation/ CompensationAmount/ |
- AmountPeriodType - |
Time interval related to the desired
compensation amount. |
|
/
HumanResource/ Preferences/ DesiredCompensation/ |
- xsd:string - S (0/1) |
Comments about compensation preferences. |
4 Implementation Considerations
4.1 Data Privacy
Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.
The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, using any other type of data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law and codes of fair information practice.
For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 – PIPEDA); and U.S.-EU Safe Harbor Principles and FAQs (2000).
5 Appendix A - Document Version History
|
Date |
Description |
|
2004-03-01 |
Initial Draft |
|
2004-03-29 |
Updated definitions |
|
2004-06-09 |
Clarified that AvailabilityDate correction is non-backwards compatible. |
|
2004-Aug-02 |
Approved by membership. |
|
2006-Feb-28 |
Approved by Consortium |
6 Appendix B – Related Documents
7 Appendix C - Reference Examples
<HumanResource xmlns="http://ns.hr-xml.org/2006-02-28" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ns.hr-xml.org/2006-02-28
HumanResource.xsd">
<HumanResourceId validFrom="2002-01-01" validTo="2002-12-31" idOwner="Kelly">
<IdValue name="Employee ID">warddar</IdValue>
</HumanResourceId>
<HumanResourceStatus status="new"/>
<ReferenceInformation>
<StaffingSupplierId>
<IdValue>79001895</IdValue>
</StaffingSupplierId>
<StaffingCustomerId>
<IdValue>985PPE</IdValue>
</StaffingCustomerId>
<OrderId>
<IdValue>121</IdValue>
</OrderId>
<PositionId>
<IdValue>3</IdValue>
</PositionId>
</ReferenceInformation>
<ResourceInformation>
<ResourceType independentContractor="false" payrolledEmployee="false"/>
<PersonName>
<LegalName>Darren Ward</LegalName>
</PersonName>
<EntityContactInfo>
<EntityName>Kelly Services NY Branch</EntityName>
<PersonName>
<LegalName>Emily Black</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>2123851212</FormattedNumber>
</Telephone>
</ContactMethod>
</EntityContactInfo>
<AvailabilityDate>
<AvailabilityStartDate>2002-03-01</AvailabilityStartDate>
<AvailabilityEndDate>2002-03-31</AvailabilityEndDate>
</AvailabilityDate>
</ResourceInformation>
<Rates rateType="bill" rateStatus="agreed">
<Amount rateAmountPeriod="hourly" currency="USD">15.00</Amount>
<Class>regular</Class>
<StartDate>2002-01-01</StartDate>
</Rates>
<Profile/>
<Preferences>
<Travel willingToTravel="true">
<PercentageTravel>50%</PercentageTravel>
<TravelConsiderations>Will not fly</TravelConsiderations>
</Travel>
<Commute>
<TimeMax>1 hr</TimeMax>
<DistanceMax>20 miles</DistanceMax>
</Commute>
<Relocation willingToRelocate="true">
<RelocationComments>US and Canada only</RelocationComments>
</Relocation>
<DistributionRestrictions>
<DoNotDistributeTo>IBM</DoNotDistributeTo>
</DistributionRestrictions>
<DesiredCompensation>
<CompensationAmount currency="USD" amountPeriod="yearly">10000</CompensationAmount>
</DesiredCompensation>
</Preferences>
<HumanResourceComments>This is an experienced programer that will fit your needs</HumanResourceComments>
</HumanResource>