SIDES Reusable Modules

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)

©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

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

1 Overview.. 4

1.1 Objective. 4

1.2 Scope. 4

1.2.1 Major Components. 5

1.2.2 Additions and Changes. 5

2 Contact Info. 5

2.1 Overview.. 5

2.2 Schema Diagrams. 5

2.3 Data Dictionary. 6

2.4 ContactInfo Example. 6

2.5 EntityContactInfo Example. 7

3 Customer Reporting Requirements. 8

3.1 Overview.. 8

3.2 Schema Diagram.. 10

3.3 Data Dictionary. 11

3.4 Example. 13

4 Rates. 14

4.1 Overview.. 14

4.2 Schema Diagram.. 15

4.3 Data Dictionary. 15

4.4 Example. 17

5 Resource Screening. 17

5.1 Overview.. 17

5.2 Schema Diagram.. 18

5.3 Data Dictionary. 18

5.4 Example. 19

6 Staffing Shift 19

6.1 Overview.. 19

6.2 Schema Diagram.. 20

6.3 Data Dictionary. 20

6.4 Example. 22

7 Staffing Contact Type. 22

7.1 Overview.. 22

7.2 Data Dictionary. 22

8 Implementation Considerations. 23

8.1 Data Privacy. 23

9 Appendix A - Document Version History. 23

10 Appendix B – Related Documents. 23

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 each reusable module.

1.1 Objective

Several reusable modules are used to exchange details within the framework of SIDES. This document describes the purpose and details of each of the six reusable modules:

Contact Info, Entity Contact Info
Customer Reporting Requirements
Rates
Resource Screening
Staffing Shift
Staffing Contact Type

1.2 Scope

This document contains sections for all six reusable modules. However, only the following four modules were modified for SIDES version 1.1:

· Contact Info, Entity Contact Info (Section 2)

· Customer Reporting Requirements (Section 3)

· Rates (Section 4)

· Staffing Shift (Section 6)

Additional information for each of these schemas and the additions to the schemas will be found in the correlating sections.

1.2.1 Major Components

The six reusable modules will be divided into separate chapters, with an overview, diagram, and definitions for each chapter.

1.2.2 Additions and Changes

Contact Info, Entity Contact Info

Element path/name	Action
Contact Method	Changed to allow multiple contact methods

Customer Reporting Requirements

Element path/name	Action
PurchaseOrderLineItem	Add new element

Rates

Element path/name	Action
RatesId	Add new element
CustomerRateClassification	Add new element
BillingMultiplier	Add new element

Staffing Shift

Element path/name	Action
ExternalStaffingShiftSetId	Add new element

2 Contact Info

2.1 Overview

The ContactInfo schema contains two data types to allow for contacting an individual or an organization: ContactInfoType and EntityContactInfoType. The ContactInfoType incorporates the PersonName and ContactMethod. Whereas, the EntityContactInfo also includes an EntityName to allow for organization, company, department, etc. The ContactMethod schema provides for a variety of contact methods such as telephone, fax, e-mail, web, and postal address.

2.2 Schema Diagrams

2.3 Data Dictionary

Elements and Attributes

[Global types listed alphabetically in following table.]

ContentModel*
Data type
Occurrence:
Sequence | Choice | All (minOccurs/maxOccurs)
Attributes

Definition

/
ContactInfo

- ContactInfoType - (1/1)

PersonName - [see include/import] - S (1/1)
ContactMethod - ContactMethodType - S (1/*)

Contains information to contact a person or entity.
[Example(s): Person Name, Organization Name, Contact Method ]

/ ContactInfo/
ContactMethod

- ContactMethodType - S (1/*)

Defines the methods of contacting a person or organizations.
[Example(s): Postal Address, E-mail, Mobile Number, Fax Number, Business Telephone Number, Business Mobile Number ]

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ EntityContactInfo	- EntityContactInfoType - (1/1) EntityName - xsd:string - S (1/1) PersonName - [see include/import] - S (0/1) ContactMethod - ContactMethodType - S (1/*)	Container for entity contact information.
/ EntityContactInfo/ EntityName	- xsd:string - S (1/1)	Name of entity that is contacted. This would typically be the organization.
/ EntityContactInfo/ ContactMethod	- ContactMethodType - S (1/*)	Defines the methods of contacting a person or organizations. [Example(s): Postal Address, E-mail, Mobile Number, Fax Number, Business Telephone Number, Business Mobile Number ]

2.4 ContactInfo Example

<ContactInfo 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

ContactInfo.xsd">

<FormattedName type="presentation">Jon Smith</FormattedName>

</PersonName>

<Use>business</Use>

<Location>office</Location>

</Telephone>

<InternetEmailAddress> jon.smith@hotplace.com</InternetEmailAddress>

<AddressLine> 127 Forrest Ave</AddressLine>

</DeliveryAddress>

<FormattedName type="presentation">Jon Smith</FormattedName>

</PersonName>

</Recipient>

</PostalAddress>

</ContactMethod>

<Use>personal</Use>

</Telephone>

</ContactMethod>

</ContactInfo>

2.5 EntityContactInfo Example

<EntityContactInfo 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

ContactInfo.xsd">

<EntityName>Deutsch Bundesbank</EntityName>

<FormattedName type="presentation">Marcus Geller</FormattedName>

</PersonName>

<Use>business</Use>

<Location>office</Location>

<WhenAvailable>Weekdays</WhenAvailable>

</Telephone>

<Municipality>Tubingen</Municipality>

<StreetName>Universitat Strasse</StreetName>

</DeliveryAddress>

<FormattedName type="presentation">Marcus Geller</FormattedName>

</PersonName>

</Recipient>

</PostalAddress>

</ContactMethod>

<Use>business</Use>

<WhenAvailable>Evenings</WhenAvailable>

<Pager>

</Pager>

</ContactMethod>

</EntityContactInfo>

3 Customer Reporting Requirements

3.1 Overview

Staffing customers require specialized reporting and data tracking. For example, it is very common for customers to require purchase order numbers, supervisor names, or department numbers, etc. to appear on reports, invoicing, documents or correspondence. A list common customer requirements was developed to accommodate this requirement. Many of these fields may be used differently by each staffing customer and the list may not satisfy every situation. Research indicates that the CustomerReportingRequirements Module attributes satisfy 80% of common reporting situations.

In the list of data fields you will find "CostCenterCode" and "LocationCode". The specific use of these two codes is up to the staffing customer. One customer may require their cost center data to appear on a report and another customer may require their location code to appear on a report. Other staffing customers may have both fields. The analysis and research showed there were enough occurrences of each field to justify the existence of both.

It is assumed that there will be exceptions and extensions to the list and some customers will require additional data elements. Accordingly, an unbounded named value pair is provided for reporting requirements that do not fit into the predefined fields.

Why not just use generic additional data elements?

The question may be asked as to why a generic 'additional data' element with enumerated types is not used rather than a predefined list? The specification could be implemented this way, but this method would not provide a ‘mapable’ data tag for items such as PO#, Cost Center, Manager Name, etc. within the HR-XML SIDES Standard itself. Without the specific tags, suppliers are forced to build extensions to the schemas to accommodate this additional data. Since the data is intended to be reused within several of the SIDES schemas, the pre-defined tags will ensure consistency between schemas. The CustomerReportingRequirements Module is referenced within StaffingCustomer, Order, Position, Assignment, Extended Timecard and Invoice schemas.

Department Code versus Department Name

Within the list of CustomerReportingRequired fields, there is a difference between DepartmentCode and DepartmentName, LocationCode and LocationName, etc. These fields are independent and mutually exclusive. These fields should not be confused with lookup tables or named value pairs. One staffing customer may want to report on codes, whereas another customer may want to track descriptive names or text.

3.2 Schema Diagram

3.3 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ CustomerReportingRequirements	- CustomerReportingRequirementsType - (1/1) ManagerName - xsd:string - S (0/1) SupervisorName - xsd:string - S (0/1) ContactName - xsd:string - S (0/1) PurchaseOrderNumber - xsd:string - S (0/1) DepartmentCode - xsd:string - S (0/1) DepartmentName - xsd:string - S (0/1) LocationCode - xsd:string - S (0/1) LocationName - xsd:string - S (0/1) CostCenterCode - xsd:string - S (0/1) CostCenterName - xsd:string - S (0/1) CustomerJobCode - xsd:string - S (0/1) CustomerJobDescription - xsd:string - S (0/1) AccountCode - xsd:string - S (0/1) ProjectCode - xsd:string - S (0/1) ExternalOrderNumber - xsd:string - S (0/1) ExternalReqNumber - xsd:string - S (0/1) Entity - xsd:string - S (0/1) SubEntity - xsd:string - S (0/1) Shift - xsd:string - S (0/1) CustomerReferenceNumber - xsd:string - S (0/1) AdditionalRequirement - xsd:string - S (0/*) PurchaseOrderLineItem - xsd:string - S (0/1)	List of customer-wide reporting field requirements.
/ CustomerReportingRequirements/ ManagerName	- xsd:string - S (0/1)	Manager name. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ SupervisorName	- xsd:string - S (0/1)	Work assignment supervisor's name, used for reporting.
/ CustomerReportingRequirements/ ContactName	- xsd:string - S (0/1)	The name of the person to contact.
/ CustomerReportingRequirements/ PurchaseOrderNumber	- xsd:string - S (0/1)	Purchase order number. [BusinessRule(s): This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ DepartmentCode	- xsd:string - S (0/1)	A department code. [BusinessRule(s): SIDES: This is a customer defined label used for invoicing and reporting ]
/ CustomerReportingRequirements/ DepartmentName	- xsd:string - S (0/1)	A department name. [BusinessRule(s): SIDES: This is a customer defined label used for invoicing and reporting ]
/ CustomerReportingRequirements/ LocationCode	- xsd:string - S (0/1)	Location code. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ LocationName	- xsd:string - S (0/1)	Location name. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ CostCenterCode	- xsd:string - S (0/1)	Cost center code. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ CostCenterName	- xsd:string - S (0/1)	Cost center name. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ CustomerJobCode	- xsd:string - S (0/1)	Staffing customer job code. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ CustomerJobDescription	- xsd:string - S (0/1)	Job description. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ AccountCode	- xsd:string - S (0/1)	An account code or identifier. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ ProjectCode	- xsd:string - S (0/1)	A project code. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ ExternalOrderNumber	- xsd:string - S (0/1)	External order number. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ ExternalReqNumber	- xsd:string - S (0/1)	External request number. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ Entity	- xsd:string - S (0/1)	A person, company or other organization.
/ CustomerReportingRequirements/ SubEntity	- xsd:string - S (0/1)	Customer organizational designation. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ Shift	- xsd:string - S (0/1)	Work shift as it pertains to a particular work engagement .
/ CustomerReportingRequirements/ CustomerReferenceNumber	- xsd:string - S (0/1)	Reference number. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting. ]
/ CustomerReportingRequirements/ AdditionalRequirement	xsd:extension base: xsd:string requirementTitle - xsd:string - optional	Any other customer required item.
/ CustomerReportingRequirements/ AdditionalRequirement/ requirementTitle	- xsd:string -	Title or name used by the customer for the additional reporting requirement.
/ CustomerReportingRequirements/ PurchaseOrderLineItem	- xsd:string - S (0/1)	Purchase Order Line Item Number associated with the reporting requirement. [BusinessRule(s): SIDES - This is a customer defined label used for invoicing and reporting.

3.4 Example

Typically, a set of data would be tranmitted and not all fields would be filled in. For example, only information about the department may be exchanged. This example includes all elements, many with a ‘string’ value. A transaction would only send those elements that contained ‘true’ values.

<CustomerReportingRequirements 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

CustomerReportingRequirements.xsd">

<ManagerName>Marion Miller</ManagerName>

<SupervisorName>Bob Anzac</SupervisorName>

<ContactName>Bob Anzac</ContactName>

<PurchaseOrderNumber>String</PurchaseOrderNumber>

<DepartmentName>Procurement</DepartmentName>

<LocationCode>String</LocationCode>

<LocationName>Headquarters</LocationName>

<CostCenterCode>String</CostCenterCode>

<CostCenterName>String</CostCenterName>

<CustomerJobCode>String</CustomerJobCode>

<CustomerJobDescription>String</CustomerJobDescription>

<AccountCode>String</AccountCode>

<ProjectCode>String</ProjectCode>

<ExternalOrderNumber>String</ExternalOrderNumber>

<ExternalReqNumber>String</ExternalReqNumber>

<Entity>String</Entity>

<SubEntity>String</SubEntity>

<Shift>String</Shift>

<CustomerReferenceNumber>String</CustomerReferenceNumber>

<AdditionalRequirement requirementTitle="String">String</AdditionalRequirement>

<PurchaseOrderLineItem>Payrolled</PurchaseOrderLineItem>

</CustomerReportingRequirements>

4 Rates

4.1 Overview

The rates module is a flexible schema that allows for the transmission of a wide variety of pay, bill and expense rate structures. It provides for multiple instances of rates for a single assignment and can associate a shift with each rate. The Rates module is also used in the StaffingOrder schema to capture a customer-specified bill rate range, and in the HumanResource to capture a specific charge rate for an individual in relation to a particular position.

4.2 Schema Diagram

4.3 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ Rates	- RatesType - (1/1)	Container for rate information.
/ Rates/ ExternalRateSetId	- EntityIdType - S (0/1)	Reference to an external rate, or collection of contractual rates.
/ Rates/ Amount	xsd:extension base: xsd:decimal rateAmountPeriod - AmountPeriodType - required currency xsd:restriction base: xsd:string - - required	The monetary value of the associated item. [Example(s): Bill rate, invoice item, compensation, allowance. ]
/ Rates/ Amount/ rateAmountPeriod	- AmountPeriodType -	The time interval or other increment in which the rate is charged or paid. May extend to provide for bonus or commission payments.
/ Rates/ Amount/ currency	xsd:restriction base: xsd:string	A three-letter code identifying the currency of a monetary amount. [BusinessRule(s): Currency is represented in accordance with ISO 4217 ]
/ Rates/ Class	- xsd:string - S (1/1)	Classification or designation for the rate. [Example(s): Regular, Overtime, Doubletime ]
/ Rates/ StaffingShiftId	- EntityIdType - S (0/1)	Shift identifier with which the rate is associated.
/ Rates/ Multiplier	xsd:extension base: xsd:decimal percentIndicator - xsd:boolean - optional	A multiplier to be applied to the related amount, rate, or variable. [Example(s): Some staffing calculations require a multiplier for custom overtime or wage factor. ]
/ Rates/ Multiplier/ percentIndicator	- xsd:boolean -	Flag to indicate if the multiplier is being provided as a percentage of the original number.
/ Rates/ StartDate	- AnyDateTimeNaType - S (1/1)	Contains the (inclusive) date, period, or interval the event becomes active or begins. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ Rates/ EndDate	- AnyDateTimeNkType - S (0/1)	Contains the (inclusive) date, period, or interval the event becomes inactive or ends. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ Rates/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element. [Example(s): Description defining an Organization's mission or purpose. Description of stock plan. ]
/ Rates/ RatesId	- EntityIdType - S (0/1)	A unique identifier for an individual agreed upon rate.
/ Rates/ CustomerRateClassification	- EntityIdType - S (0/1)	Identifier allowing customer rates to be grouped for reporting purposes.
/ Rates/ BillingMultiplier	xsd:extension base: xsd:decimal percentIndicator - xsd:boolean - required	A multiplier specifically used to calculate the invoice amount using the paid amount.
/ Rates/ BillingMultiplier/ percentIndicator	- xsd:boolean -	Flag to indicate if the multiplier is being provided as a percentage of the original number.

4.4 Example

<Rates 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

Rates.xsd" rateType="bill" rateStatus="proposed">

<IdValue name="String">String</IdValue>

</ExternalRateSetId>

<Class> Regular</Class>

<IdValue>Day Shift</IdValue>

</StaffingShiftId>

<EndDate>notKnown</EndDate>

<IdValue>Standard Rate</IdValue>

</RatesId>

<IdValue name="String">String</IdValue>

</CustomerRateClassification>

</Rates>

5 Resource Screening

5.1 Overview

This reusable module allows staffing suppliers to report basic screening information pertaining to a staffing resource.

5.2 Schema Diagram

5.3 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]		ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ ResourceScreening		- ResourceScreeningType - (1/1) screeningType - xml:lang - - StaffingScreeningType - required ScreeningResultDate - AnyDateTimeType - S (1/1) ScreeningResult - xsd:string - S (1/1) ScreeningComments - xsd:string - S (0/1)	Container for screening or testing data about the candidate.
/ [ResourceScreeningType] / screeningType	- StaffingScreeningType -			Type of screening required and reported on.
/ ResourceScreening/ ScreeningResultDate		- AnyDateTimeType - S (1/1)	Date of the screening result being reported. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601 ]
/ ResourceScreening/ ScreeningResult		- xsd:string - S (1/1)	Result of the screening report. This is generally limited to noting if the requirement was met or not met.
/ ResourceScreening/ ScreeningComments		- xsd:string - S (0/1)	Comments regarding the report.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [KnownScreeningType]	xsd:restriction base: xsd:string [Enumerations]: abuse, address, awards, credit, criminal, drug, earnings, education, employment, license, name, phone, reference, workcomp	Globally scoped data type. See element or attribute declaration for definition.
/ [ResourceScreeningType]	screeningType - StaffingScreeningType - required ScreeningResultDate - AnyDateTimeType - S (1/1) ScreeningResult - xsd:string - S (1/1) ScreeningComments - xsd:string - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [StaffingScreeningType]	- [Union]: KnownScreeningType,xsd:string	Globally scoped data type. See element or attribute declaration for definition.

5.4 Example

<ResourceScreening 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

ResourceScreening.xsd" screeningType="drug">

<ScreeningComments>Candidate was using prescription steroid which did show up in the test.</ScreeningComments>

</ResourceScreening>

6 Staffing Shift

6.1 Overview

The StaffingShift schema provides a mechanism for exchanging information on shifts or specific working hours between trading partners and within internal applications. Staffing suppliers require shift information to describe position-specific requirements and rate related assignment information within an order.

6.2 Schema Diagram

6.3 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ StaffingShift	- StaffingShiftType - (1/1) shiftPeriod xsd:restriction base: xsd:string [Enumerations]: monthly, weekly, daily, 1, 2, 3, 4, 5, 6, 7 - - xml:lang - - Id - EntityIdType - S (1/1) Name - xsd:string - S (0/1) Hours - xsd:decimal - S (0/1) StartTime - LocalTimeNkNaType - S (0/1) EndTime - LocalTimeNkNaType - S (0/1) TypeHours - xsd:string - S (0/1) Comment - xsd:string - S (0/1) ExternalStaffingShiftSetId - EntityIdType - S (0/1)	A mechanism for exchanging information on shifts or specific working hours.
/ [StaffingShiftType] / shiftPeriod	xsd:restriction base: xsd:string [Enumerations]: monthly, weekly, daily, 1, 2, 3, 4, 5, 6, 7	The period the shift occurs. Annotation: Numeric values conform to: ISO 8601 2nd Edition; ISO8601:2000(E); pub 2000-12-15, Data elements and interchange formats, Information interchange, Representation of dates and times, http://www.iso.ch/cate/d26780.html/ 1 = Monday, 2 = Tuesday, 3 = Wednesday, 4 = Thursday, 5 = Friday, 6 = Saturday, 7 = Sunday [BusinessRule(s): Numeric values conform to: ISO 8601 2nd Edition. ]
/ StaffingShift/ Id	- EntityIdType - S (1/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element. [BusinessRule(s): SIDES: Open Applications Group definition: The identifier of the semantically named document. The position of the Id further defines it's context and meaning. HR-XML usage definition: In the Header's DocumentId context, Id will hold the overall Invoice Number for the transaction. ]
/ StaffingShift/ Name	- xsd:string - S (0/1)	A descriptive identifier within the given context. [BusinessRule(s): If referencing a person, use person name. ] [Example(s): name of shift, name of stock plan, name of competency ]
/ StaffingShift/ Hours	- xsd:decimal - S (0/1)	The number of hours specified for an event or work period.
/ StaffingShift/ StartTime	- LocalTimeNkNaType - S (0/1)	The time the interval or event started.
/ StaffingShift/ EndTime	- LocalTimeNkNaType - S (0/1)	The time the interval or event ended.
/ StaffingShift/ TypeHours	- xsd:string - S (0/1)	Specific type of work hours. [Example(s): Regular, Overtime, Doubletime, Special, Premium, Sick, Vacation ]
/ StaffingShift/ Comment	- xsd:string - S (0/1)	Allows for textual comments.
/ StaffingShift/ ExternalStaffingShiftSetId	- EntityIdType - S (0/1)	Allows a reference to an external staffing shift, or collection of contractual staffing shifts.

6.4 Example

<StaffingShift 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

StaffingShift.xsd" shiftPeriod="monthly">

<IdValue>Regular</IdValue>

</Id>

<Name> First</Name>

<TypeHours> Regular</TypeHours>

<Comment>String</Comment>

</ExternalStaffingShiftSetId>

</StaffingShift>

7 Staffing Contact Type

7.1 Overview

This module defines the type of contact information consistent across the Assignment, and StaffingAction modules. To ensure this consistency, a value list (enumerations) was created for use in those two modules. The enumerations are as follows:

Placed by
Placed on behalf of
Confirm to
Authorized by

· Interviewer

Supervisor
Time approver
Submitted by
Created by
Sent to

7.2 Data Dictionary

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [KnownContactType]	xsd:restriction base: xsd:string [Enumerations]: placed by, placed on behalf of, confirm to, authorized by, interviewer, supervisor, time approver, submitted by, created by, sent to	Globally scoped data type. See element or attribute declaration for definition.
/ [StaffingContactType]	- [Union]: KnownContactType,xsd:string	Globally scoped data type. See element or attribute declaration for definition.

8 Implementation Considerations

8.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).

9 Appendix A - Document Version History

Date	Description
2004-Mar-03	Initial Draft
2004-Mar-29	Updated tables, added info to overview/scope sections.
2004-Apr-07	Added reference examples.
2004-May-06	Changed percentage to percentIndicator
2004-Jun-08	Changed Contact Method to multiple occurrence. Added xml:lang to root of Rates, ResourceScreening, and StaffingShift.
2004-Aug-02	Approved by membership.
2006-Feb-28	Approved by Consortium

10 Appendix B – Related Documents

Reference	Link
SIDES schemas	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Assignment.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ContactInfo.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/CustomerReportingRequirements.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/HumanResource.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Rates.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ResourceScreening.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingAction.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingContactType.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrder.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrganization.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingPosition.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingShift.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingWorkSite.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/TimeCardAdditionalData.xsd
SIDES Documentation	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/SIDES.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Assignment.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/HumanResource.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingAction.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrder.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrganization.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/SIDESReusableModules.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingInvoice.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingWorkSite.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ExtendedTimeCard.html
OAGIS Invoice and instance	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Invoice.xsd (a stand alone version - see http://www.openapplications.org/ for the original) http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Invoice.xml
User Area	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/HRXMLExtension.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/UserArea.xsd
PersonName	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PersonName.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PersonName.xsd
PostalAddress	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PostalAddress.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PostalAddress.xsd
ContactMethod	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/ContactMethod.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/ContactMethod.xsd
PositionHeader	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/JobAndPositionHeader.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PositionHeader.xsd
DateTimeDataTypes	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/DateTimeDataTypes.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/DateTimeDataTypes.xsd
Resume	http://ns.hr-xml.org/2_4/HR-XML-2_4/SEP/Resume.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SEP/Resume.xsd
Competencies	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/Competencies.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/Competencies.xsd
TimeCard	http://ns.hr-xml.org/2_4/HR-XML-2_4/TimeCard/TimeCard.html http://ns.hr-xml.org/2_4/HR-XML-2_4/TimeCard/TimeCard.xsd