Staffing Action
Recommendation, 2007 April 15
Editors:
Kim Bartkus, HR-XML Consortium
Contributors:
Gail Bubsey (Kelly Services ), Kim Bartkus (HR-XML Consortium), Barbara Johnson (Adecco NA), Tara Ryan (Adecco), Kazuko Sugamura (Manpower Japan), Takahiro Fujiwara (EAST Co., Ltd.), Magali Munoz (Manpower France), Bruno Alcotte (Manpower France), Rémy Bailly (Randstad), Yves Berdah (VidiorBis), Serguei Dounaevetski (Manpower France), Patrice Aranega (Adecco France)
Copyright © 2007 HR-XML Consortium, Inc.
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.
Table of Contents
4 Implementation Considerations
5 Appendix A - Document Version History
6 Appendix B – Related Documents
1 Overview
Changes were made to the base SIDES specification based on feedback from the European and Japanese Chapters. If available, localized items are documented in section 4 Implementation Considerations or in individual country documentation. Refer to Appendix A - Document Version History for details.
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.
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.
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/*) StaffingOrganizationId - 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/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the billing information. |
|
/
StaffingAction/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a master order or project. Used to link multiple orders. |
|
/
StaffingAction/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing organization. |
|
/ StaffingAction/ |
contactType - StaffingContactType
- required |
Contains contact information about the initiators of or the respondents to the StaffingAction. |
|
/ StaffingAction/
StaffingActionContact/ |
- StaffingContactType - |
Describes the relationship of the contact person to the associated element. |
|
/ 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, Modification, Request, Cancelled |
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, Reporting |
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 |
|
2006-Mar-01 |
Added Reference Id's to match other SIDES schemas: BillToEntityId, MasterOrderId and StaffingOrganizationId. Added 'Modification', 'Cancelled', 'Request' enumerations to StaffingActionReasonCode. Added 'Reporting' enumeration to StaffingActionReasonSubjects. |
|
2007-Apr-15 |
Approved by Consortium |
6 Appendix B – Related Documents