StaffingOrder
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 Order schema, its expected usage, and the business processes meant to be supported.
Status of this Document
2006-Feb-28: Default values have been removed from the StaffingOrder schema in accordance with the Technical Steering Committee's (TSC) Schema Design Guidelines.
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 order.
1.1 Objective
Within the framework of SIDES, the StaffingOrder schema is used to describe the position(s) a staffing customer is requesting be filled by a staffing supplier, either directly or through an intermediary. The StaffingOrder schema design should be flexible enough to be used by any staffing supplier.
Many of the additions and changes for this version of SIDES are to ensure the global usability of the schema. There are changes included to address issues that arose during implementation and changes to accomodate the new Organization CPO.
1.2 Scope
1.2.1 Major Components
The Major Components used in the Quote/Order process are listed below.
- Position Information describes the position, such as position title, rates, and worksite.
- ReferenceInformation
- CustomerReportingRequirements
1.2.2 Items Within Scope
- The ability to exchange a basic quote between a staffing supplier and a staffing customer or their intermediary.
- The ability to exchange an order between a staffing supplier and a staffing customer or their intermediary.
- The ability to exchange a StaffingAction between a staffing supplier and a staffing customer or their intermediary.
1.2.3 Additions and Changes
Staffing Order
|
Element path/name |
Details |
|
BillToAttention |
Change to optional occurrence |
|
ReferenceInformation/StaffingSupplierOrgUnitId |
Add new element |
Staffing Position
|
Element path/name |
Details |
|
ReportToPerson |
Change to optional occurrence |
|
PositionDateRange/MaxNeedEndDate |
Add new element |
|
PositionDateRange/MaxStartDate |
Add new element |
|
PositionDateRange/StartAsSoonAsPossible |
Add new Boolean element |
2 Business Process
The StaffingOrder schema moves from the staffing customer to the staffing supplier, sometimes by way of an intermediary. This transmission marks the beginning of the business process addressed by SIDES. The Quote/Order process is used to send information describing a customer’s servicing needs, e.g. position description, start and end dates, estimated bill rate. The Quote/Order process is iterative. The Quote process is optional. The basic Quote process is described here.
· The staffing customer submits an XML document to a staffing supplier and/or intermediary with a status that changes for each step leading up to a qualified order.
- RFQ (a request for quotation sent to the intermediary and/or staffing supplier).
- Order (either an acceptance of a quote, or a direct and authorized command to supply).
- Unapproved Order (sometimes the staffing customer makes a direct command to supply, but it is pending authorization).
· The staffing supplier sends a response to the XML document. Possible status changes are:
- RFQ (rejection of RFQ – declining to quote).
- Quote (acceptance of and response to the RFQ from the staffing customer).
· Unapproved Order (acceptance of unapproved order).
- Order (acceptance of an order).
Recommendations for Use
It is recommended that the position type, regardless of quantity, remain the same within an order and that the information within the position remains constant. If position elements vary by any substantial degree, it is recommended a different order be created.
3 Schema Design
3.1 Staffing Order
3.1.1 Schema Diagram
3.1.2 Data Dictionary
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition
|
|
/ |
- StaffingOrderType
- (1/1) |
Transaction used to submit an order or quote from a customer (or intermediary) to a staffing company. |
|
/ StaffingOrder/ |
- EntityIdType - S (1/1) |
Unique identifier for a staffing order. |
|
/ StaffingOrder/ |
MasterOrderId - EntityIdType - S (0/*) |
Contains reference information (a group of id's) regarding other business entities or transactions. |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a master order or project. Used to link multiple orders. |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing customer. |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing customer. |
|
/ StaffingOrder/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a Vendor Management System or 3rd party responsible for staffing management |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing supplier. |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the billing information. |
|
/ StaffingOrder/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing supplier. |
|
/ StaffingOrder/ |
orderType - OrderType
- required |
Contains classification information about the order. |
|
/ StaffingOrder/
OrderClassification/ |
- OrderType - |
Indicator of what type the order
is or what stage the order process is in. |
|
/ StaffingOrder/
OrderClassification/ |
- OrderStatusType - |
Indicates the status of the
order. |
|
/ StaffingOrder/ |
ContactInfo - [see include/import] - S (1/1) |
Describes contact information for billing purposes. |
|
/ StaffingOrder/ |
contactType - StaffingContactType
- required |
Contains the contact information for the overall order. |
|
/ StaffingOrder/ OrderContact/ |
- StaffingContactType - |
The role of the contact as it
relates to the organization. |
|
/ StaffingOrder/ |
- AnyDateTimeNaType - S (0/1) |
The date that the staffing supplier must contact the staffing customer with an order status. |
|
/ StaffingOrder/ |
- xsd:string - S (0/*) |
Field for comments about the
order. |
|
/ StaffingOrder/ |
- xsd:integer - S (1/1) |
The number of positions attached to this order. |
|
/ StaffingOrder/ |
- xsd:integer - S (0/1) |
The number of positions on the
order that still need to be filled. |
|
/ StaffingOrder/ |
- xsd:boolean - S (1/1) |
Indicates whether this order was distributed to multiple vendors.
|
|
Global
types |
ContentModel* |
Definition ** |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: new, revised, reopened, cancelled, closed, accepted, rejected |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: quote, order, unapproved order, RFQ |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownOrderStatus,xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownOrderType,xsd:string |
Globally scoped data type. See element or attribute declaration for definition. |
3.2 Staffing Position
3.2.1 Schema Diagram
3.2.2
Data Dictionary
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition
|
|
/ |
- StaffingPositionType
- (1/1) |
Details about the position(s) attached to the staffing order. |
|
/ StaffingPosition/ |
- xsd:string - S (0/1) |
Name of the department for which
this position is intended. |
|
/ StaffingPosition/ |
- xsd:string - S (0/1) |
The reason the position is being
generated. |
|
/ StaffingPosition/ |
StartDate - AnyDateTimeType - S (1/1) |
Container for period of time the assignment is expected to occur. |
|
/ StaffingPosition/
PositionDateRange/ |
- AnyDateTimeType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes active or begins. |
|
/ StaffingPosition/
PositionDateRange/ |
- AnyDateTimeNkType - S (0/1) |
The date the position,
assignment, or contract is expected to end. |
|
/ StaffingPosition/
PositionDateRange/ |
- AnyDateTimeNaType - S (0/1) |
The (inclusive) date that an event actually ends, versus an estimated or projected end date. |
|
/ StaffingPosition/
PositionDateRange/ |
- FlexibleDatesType - S (0/1) |
The maximum start date that a person can begin work at this position. |
|
/ StaffingPosition/
PositionDateRange/ |
- xsd:boolean - S (0/1) |
Indicates an immediate need to have a position filled. |
|
/ StaffingPosition/
PositionDateRange/ |
- FlexibleDatesType - S (0/1) |
The maximum date the position, assignment, or contract is expected to end. |
|
/ StaffingPosition/ |
ContactInfo - [see include/import] - S (1/1) |
Container for the contact information of the person that the assigned staffing resource is to report to. |
|
/ StaffingPosition/ |
contactType - StaffingContactType
- optional |
Contains the contact information for the position. May vary from the order or from position to position on the order. |
|
/ StaffingPosition/
PositionContact/ |
- StaffingContactType - |
The role of the contact as it
relates to the organization. |
|
/ StaffingPosition/ |
- StaffingWorkSiteType - S (1/1) |
Contains common Work Site information, including name, address travel directions, and parking instructions. |
|
/ StaffingPosition/ |
- StaffingWorkSiteEnvironmentType - S (0/*) |
Contains common Work Site Environment information, including description, physical considerations, dress code, and safety equipment. |
|
/ StaffingPosition/ |
resumeRequired - xsd:boolean
- required |
Details about unique requirements for the position. |
|
/ StaffingPosition/ PositionRequirements/ |
- xsd:boolean - |
Indicates if a resume is required for this position. |
|
/ StaffingPosition/
PositionRequirements/ |
- xsd:boolean - |
Indicated if an interview is required for this position. |
|
/ StaffingPosition/ PositionRequirements/ |
screeningType - StaffingScreeningType - optional |
Container for the various screening checks the customer requires for all staffing resources. |
|
/ StaffingPosition/
PositionRequirements/ ScreeningRequirements/ |
- StaffingScreeningType - |
Type of screening required and reported on. |
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-08 |
Deprecated ‘false’ default for MulitVendorDistribution. |
|
2004-Aug-02 |
Approved by membership. |
|
2006-Feb-28 |
Approved by Consortium |
6 Appendix B – Related Documents
7 Appendix C - Reference Examples
<StaffingOrder 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
StaffingOrder.xsd">
<OrderId validFrom="2002-01-01" validTo="2002-12-31" idOwner="IBM">
<IdValue>PO123789</IdValue>
</OrderId>
<ReferenceInformation>
<StaffingCustomerId>
<IdValue>445123</IdValue>
</StaffingCustomerId>
<StaffingSupplierId>
<IdValue>676773</IdValue>
</StaffingSupplierId>
<BillToEntityId>
<IdValue>1445123</IdValue>
</BillToEntityId>
</ReferenceInformation>
<CustomerReportingRequirements/>
<OrderClassification orderType="order" orderStatus="new"/>
<BillToAttention>
<ContactInfo>
<PersonName>
<LegalName>Joe Brown</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>6318447124</FormattedNumber>
</Telephone>
</ContactMethod>
</ContactInfo>
</BillToAttention>
<OrderContact contactType="placedBy">
<ContactInfo>
<PersonName>
<LegalName>Mary Smith</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>6318447224</FormattedNumber>
</Telephone>
</ContactMethod>
</ContactInfo>
</OrderContact>
<RequiredResponseDate>2002-02-07</RequiredResponseDate>
<PositionQuantity>1</PositionQuantity>
<PositionQuantityOpen>1</PositionQuantityOpen>
<MultiVendorDistribution>false</MultiVendorDistribution>
<StaffingPosition>
<PositionHeader>
<PositionId>
<Id>Pos1287</Id>
</PositionId>
<PositionTitle>Business Analyst</PositionTitle>
</PositionHeader>
<CustomerReportingRequirements/>
<DepartmentName>Sales</DepartmentName>
<PositionReason>Overload</PositionReason>
<PositionDateRange>
<StartDate>2002-01-01</StartDate>
<ExpectedEndDate>2002-07-07</ExpectedEndDate>
<MaxStartDate>
<AnyDate>2002-01-15</AnyDate>
</MaxStartDate>
<StartAsSoonAsPossible>true</StartAsSoonAsPossible>
<MaxNeedEndDate>
<AnyDate>notKnown</AnyDate>
</MaxNeedEndDate>
</PositionDateRange>
<ReportToPerson>
<ContactInfo>
<PersonName>
<LegalName>Mike Jone</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>6318447726</FormattedNumber>
</Telephone>
</ContactMethod>
</ContactInfo>
</ReportToPerson>
<PositionContact contactType="supervisor">
<ContactInfo>
<PersonName>
<LegalName>Mike Jones</LegalName>
</PersonName>
<ContactMethod>
<Telephone>
<FormattedNumber>6318447726</FormattedNumber>
</Telephone>
</ContactMethod>
</ContactInfo>
</PositionContact>
<WorkSite>
<WorkSiteId>
<Id>124</Id>
</WorkSiteId>
<WorkSiteName>IBM Vermont</WorkSiteName>
</WorkSite>
<StaffingShift>
<Id>
<IdValue>regular</IdValue>
</Id>
</StaffingShift>
<PositionRequirements resumeRequired="false" interviewRequired="false">
<ScreeningRequirements screeningType="drug"/>
</PositionRequirements>
</StaffingPosition>
</StaffingOrder>