Staffing Action
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 Staffing Action 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 staffing action module.
1.1 Objective
Within the framework of SIDES, the StaffingAction schema describes mainly iterative actions between a staffing supplier, staffing customer and/or intermediary without the need to send complete schemas such as the HumanResource schema, back and forth. The French Coalition found the need to add the following StaffingAction XML document can be used to:
- Staffing Supplier Org Unit Id, OrgUnitId, TimeCardId and InvoiceID
- StaffingActionReason
- Action Reason/ ReasonCode
- Action Reason/Action Subject
These additions are described in further detail later in this document.
1.2 Scope
1.2.1 Major Components
The Major Components used in the StaffingAction schema are listed below.
· ReferenceInformation.
· StaffingAction Information – describes the staffing action, such as the kind of action (request/response) and additional comments.
· Effective Dating Information – defines who created the staffing action request or the person to whom the request should be sent.
· StaffingActionSchedule - used for planning when a StaffingAction request/response is required by one of the parties.
· StaffingActionResult - used to indicate the result of a previous StaffingAction request/response.
1.2.2 Items within Scope
· Ability to send and receive additional data regarding processes between parties.
· Ability to create a request for information, communication or action to be taken by one of the parties.
· Ability to create a response to the request for information, or action taken by one of the parties.
1.2.3 Items Outside of Scope
· StaffingAction is not intended to provide an alternative method to communicate changes in previously transmitted transactions, or changes to status of previously sent transactions; for example, closing an assignment or cancelling a staffing order or position should be either done with the Assignment, or StaffingOrder schemas themselves.
1.2.4 Additions and Changes
|
Element path/name |
Details |
|
ReferenceInformation/StaffingSupplierOrgUnitId |
Add new component |
|
ReferenceInformation/StaffingCustomerOrgUnitId |
Add new component |
|
ReferenceInformation/TimeCardId |
Add new component |
|
ReferenceInformation/InvoiceId |
Add new component |
|
StaffingActionInfo/ActionReason |
Add new component |
|
ActionReason/ActionReasonCode |
Add new component |
|
ActionReason/ActionSubject |
Add new component |
2 Business Process
The staffing supplier, the staffing customer and/or the intermediary may initiate the StaffingAction transaction. It is designed and provided for ongoing communication and can be used for fine-tuning information and data from other schemas and processes. It is essentially a messaging mechanism and the open enumerated element StaffingActionType provides for five actions, but will accept any other actions as may be required.
 |
3 Schema Design
3.1 Staffing Action
3.1.1 Schema Diagram
3.1.2 Data Dictionary
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- StaffingActionType
- (1/1) |
Intended to be a messaging tool. In most cases the content will be displayed in text format, rather than fully parsed into individual data elements. An auditable alternative to email or telephone contact. |
|
/ StaffingAction/ |
- EntityIdType - S (1/*) |
Unique identifier for a staffing action. |
|
/
StaffingAction/ |
ActionType
- StaffingActionByType - S (1/1) |
Contains information about the StaffingAction based on type. |
|
/
StaffingAction/ StaffingActionInfo/ |
- StaffingActionByType - S (1/1) |
Conveys the nature of the staffing communication or action. |
|
/
StaffingAction/ StaffingActionInfo/ |
- xsd:string - S (0/1) |
Free form comment to relay details about the staffing action type. For example, customer wants to extend an assignment; intermediary wants to schedule an interview. |
|
/
StaffingAction/ StaffingActionInfo/ |
ActionReasonCode
- StaffingActionReasonCodeType - S (1/1) |
Contains the reason for and nature of a particular staffing action. |
|
/
StaffingAction/ StaffingActionInfo/ ActionReason/ |
- StaffingActionReasonCodeType - S (1/1) |
A code
defining the reason of a particular staffing action. |
|
/
StaffingAction/ StaffingActionInfo/ ActionReason/ |
- StaffingActionSubjectType - S (1/1) |
Idenifies
which of the SIDES modules is being referred to in this staffing action. |
|
/ StaffingAction/ |
HumanResourceId - EntityIdType - S (0/*) |
Contains reference information (a group of id's) regarding other business entities or transactions. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a specific HumanResource. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a staffing order. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a uniquely identifiable position. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Identifier of the assignment
eventually agreed to by the trading partners. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a Vendor Management System or 3rd party responsible for staffing management |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing supplier. |
|
/ StaffingAction/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing customer. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing supplier. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing customer. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the time card. |
|
/ StaffingAction/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the Invoice. |
|
/ StaffingAction/ |
contactType - StaffingContactType
- required |
Contains contact information about the initiators of or the respondents to the StaffingAction. |
|
/ StaffingAction/ StaffingActionContact/ |
- StaffingContactType - |
The role of the contact as it
relates to the organization. |
|
/ StaffingAction/
StaffingActionContact/ |
StaffingSupplierId - xsd:string - C (1/*) |
Contains reference information (a group of id's) regarding other business entities or transactions. |
|
/ StaffingAction/
StaffingActionContact/ ReferenceInformation/ |
- xsd:string - C (1/*) |
Unique id used to identify the staffing supplier. |
|
/ StaffingAction/
StaffingActionContact/ ReferenceInformation/ |
- xsd:string - C (0/*) |
Unique identifier for a Vendor Management System or 3rd party responsible for staffing management |
|
/ StaffingAction/
StaffingActionContact/ ReferenceInformation/ |
- xsd:string - C (1/*) |
Unique id used to identify the staffing customer. |
|
/ StaffingAction/ |
ContactPerson - ContactInfoType - S (1/*) |
Details about the StaffingAction's schedule or timing if appropriate. |
|
/ StaffingAction/ ActionSchedule/ |
- ContactInfoType - S (1/*) |
Contains information for the contact person. |
|
/ StaffingAction/ ActionSchedule/ |
StartDateTime - AnyDateTimeNaType - S
(0/1) |
The interval when the contact occurs or is scheduled to occur. |
|
/ StaffingAction/ ActionSchedule/
ContactPeriod/ |
- AnyDateTimeNaType - S (0/1) |
Defines the start date, and if
applicable, start time of the interval, period, or event being reported. |
|
/ StaffingAction/ ActionSchedule/
ContactPeriod/ |
- AnyDateTimeNaType - S (0/1) |
Defines the end date, and if
applicable, end time of the interval, period, or event being reported. |
|
/ StaffingAction/ ActionSchedule/ |
- xsd:string - S (0/*) |
Any unique needs of the parties
in order to fulfill a schedule-related StaffingAction. |
|
Global
types |
ContentModel* |
Definition |
|
|
xsd:restriction base: xsd:string [Enumerations]: request info, request action, request communication, response info, response action |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownStaffingActionByType,xsd:string |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Acknowledgement, Confirmation, Contract Extension, Contract Modification, Contract Expiration, Assignment Extension, Assignment Modification |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: StaffingActionReasonCodes, xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Order, Position, Assignment, Staffing Supplier, Staffing Customer, Timecard, Invoice, Contract, Human Resource |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: StaffingActionReasonSubjects, xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
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-Apr-08 |
Updated example. |
|
2004-Jun-08 |
Added prefix ‘staffing’ to global action types. |
|
2004-Aug-02 |
Approved by membership. |
|
2006-Feb-28 |
Approved by Consortium |
6 Appendix B – Related Documents
7 Appendix C - Reference Examples
<StaffingAction 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
StaffingAction.xsd">
<StaffingActionId validFrom="2002-01-26" validTo="2002-01-30" idOwner="IBM">
<IdValue>SA1235</IdValue>
</StaffingActionId>
<StaffingActionInfo>
<ActionType>request info</ActionType>
<ActionReason>
<ActionReasonCode>x:Interview</ActionReasonCode>
<ActionSubject>Position</ActionSubject>
</ActionReason>
</StaffingActionInfo>
<ReferenceInformation>
<HumanResourceId idOwner="Kelly">
<IdValue>hr3456</IdValue>
</HumanResourceId>
<PositionId idOwner="IBM">
<IdValue>p2345</IdValue>
</PositionId>
</ReferenceInformation>
<StaffingActionContact contactType="created by">
<EntityContactInfo>
<EntityName>IBM</EntityName>
<PersonName>
<LegalName>Rick Carter</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>7709865437</FormattedNumber>
</Telephone>
</ContactMethod>
</EntityContactInfo>
</StaffingActionContact>
<ActionSchedule>
<ContactPerson>
<PersonName>
<LegalName>Tina Tuner</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>2143213452</FormattedNumber>
</Telephone>
</ContactMethod>
</ContactPerson>
<SpecialRequirements>Bring in Cadidate for an interview between 01-27 and 01-30</SpecialRequirements>
</ActionSchedule>
</StaffingAction>