Assignment

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 Assignment 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.. 3

1.1 Objective. 3

1.2 Scope. 3

1.2.1 Major Components. 3

1.2.2 Items within Scope. 4

1.2.3 Additions and Changes. 4

2 Business Process. 6

3 Schema Design. 8

3.1 Assignment 8

3.1.1 Schema Diagram.. 8

3.1.2 Data Dictionary. 8

3.2 Local Contract Requirements. 12

3.2.1 Schema Diagram.. 12

3.2.2 Data Dictionary. 13

3.3 Frame Agreement Information. 16

3.3.1 Schema Diagram.. 16

3.3.2 Data Dictionary. 17

4 Implementation Considerations. 18

4.1 Data Privacy. 18

5 Appendix A - Document Version History. 19

6 Appendix B – Related Documents. 19

7 Appendix C - Reference Examples. 20

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 an Assignment.

1.1 Objective

Within the framework of SIDES, the Assignment schema is used to describe the agreement between the staffing customer, staffing supplier and the staffing resource about the person(s) and conditions to fulfil the position as requested by the staffing customer.

The main purpose of the Assignment XML document is to send a confirmation from the staffing supplier to the staffing customer with all related information regarding the:

Staffing order or position in the staffing order that is filled by a person.
Specific customer requirements for the staffing order or position in the staffing order.
Rates of the staffing order or position in the staffing order.
StaffingShift or schedule required by the staffing order or position in the staffing order.

· StartDate and expected end date of the assignment.

At assignment end, the actual end date.
Contract information regarding the legal aspects of the assignment.

1.2 Scope

1.2.1 Major Components

The Major Components used in the Assignment process are listed below.

· AssignmentDateRange - defines the period agreed upon by staffing supplier and staffing customer for the Assignment. There is a StartDate, ExpectedEndDate and ActualEndDate for use when the Assignment is ended either naturally or by one of the parties. There also Flexible dates that capture information about employment contracts that have to be renewed at different times on a separate schedule from the assignment or position dates.

· ContractInformation - If an assignment is based on a contract between the parties, the information can be captured here. The type, status and ID of the contract as well as the legal information, version and version date can be described.

· FrameAgreement – Captures basic information about the overall staffing services agreement between the staffing supplier and the client including scope, dates and references to a full document with the terms and conditions of the agreement

· LocalContractRequirements – Some countries require employment contracts be in place in order for a company to employ a person. These employment contracts are heavily regulated and it is necessary to track the dates and other information to ensure compliance. LocalContractRequirements is used for this type of information

· ReferenceInformation – A group of id’s that allow the assignment to be associated to other documents such as Orders, Positions, Human Resources, etc.

· CustomerReportingRequirements – An extensible list of customer-specific reference or information pieces needed for tracking and reporting

· Rates – Contains information on bill rates, pay rates, special billing multipliers, references to rate cards and other information relating to the agreed upon charges in a staffing transaction

· StaffingShift - This section describes details of the scheduled days and hours associated with a particular person in a particular position. May also contain references to contractually named work periods or work rotation intervals.

1.2.2 Items within Scope

1. Confirmation of the HumanResource, ReferenceInformation, conditions (Rates, StaffingShift), DateRanges and other information by the staffing supplier to the staffing customer.

2. Ability to change the status of the assignment.

3. Ability to end an assignment by one of the parties and send information regarding who ended the assignment and why it is ended.

4. Ability to change the assignment conditions like work shift or rates.

5. Ability to monitor employment contract dates and to change the staus of those contracts

6. One assignment is always linked to one position, however one position can have one or more assignments on a sequential rather than concurrent basis.

7. Assignments may have one or more contracts associated with a person also on a sequential rather than concurrent basis.

1.2.3 Additions and Changes

Element path/name	Details
OrderId	Change Cardinality
IntermediaryId	Change Cardinality
AssignmentDateRange/FlexibilityMinDate	Add new component
AssignmentDateRange/FlexibilityMaxDate	Add new component
AssignmentDateRange/ProbationaryPeriod	Add new component
AssignmentDateRange/ProbationaryPeriod/unitOfMeasure	Add new component
AssignmentDateRange/SuspensionPeriod	Add new component
AssignmentDateRange/SuspensionPeriod/StartDate	Add new component
AssignmentDateRange/SuspensionPeriod/EndDate	Add new component
AssignmentDateRange/SuspensionPeriod/Comments	Add new component
ReferenceInformation/StaffingSupplierOrgUnitId	Add new component
ContractInformation/FrameAgreementInfo	Add new component
ContractInformation/FrameAgreementInfo/DocumentId	Add new component
ContractInformation/FrameAgreementInfo/DocumentVersion	Add new component
ContractInformation/FrameAgreementInfo/ValidityDateRange	Add new component
ContractInformation/FrameAgreementInfo/ValidityDateRange/StartDate	Add new component
ContractInformation/FrameAgreementInfo/ValidityDateRange/EndDate	Add new component
ContractInformation/FrameAgreementInfo/DocumentName	Add new component
ContractInformation/FrameAgreementInfo/DocumentType	Add new component
ContractInformation/FrameAgreementInfo/StaffingOrgContact	Add new component
ContractInformation/FrameAgreementInfo/StaffingOrgContact/type	Add new component
ContractInformation/LocalContractRequirements	Add new component
ContractInformation/LocalContractRequirements/WorkSite	Add new component
LocalContractRequirements/StartStaffingShiftId	Add new component
LocalContractRequirements/ContractLegalReason	Add new component
LocalContractRequirements/ContractLegalReason/ContractType	Add new component
LocalContractRequirements/ContractLegalReason/RecourseType	Add new component
LocalContractRequirements/ContractLegalReason/RecourseType/Code	Add new component
LocalContractRequirements/ContractLegalReason/RecourseType/Description	Add new component
LocalContractRequirements/ContractLegalReason/ContractReason	Add new component
LocalContractRequirements/ContractLegalReason/ReplacedPerson	Add new component
LocalContractRequirements/ContractLegalReason/ReplacedPerson/PersonName	Add new component
LocalContractRequirements/ContractLegalReason/ReplacedPerson/Position	Add new component
LocalContractRequirements/CompensationReference	Add new component
LocalContractRequirements/ CompensationReference/Code	Add new component
LocalContractRequirements/ CompensationReference/Description	Add new component
LocalContractRequirements/SentBy	Add new component
LocalContractRequirements/SentBy/WrittenBy	Add new component
LocalContractRequirements/SentBy/SignedBy	Add new component
LocalContractRequirements/ CustomerSignature	Add new component
LocalContractRequirements/ CustomerSignature/SignedBy	Add new component
LocalContractRequirements/ CustomerSignature/Date	Add new component
LocalContractRequirements/PositionCharacteristics	Add new component
LocalContractRequirements/PositionCharacteristics/PositionTitle	Add new component
LocalContractRequirements/PositionCharacteristics/PositionStatus	Add new component
LocalContractRequirements/PositionCharacteristics/PositionStatus/Code	Add new component
LocalContractRequirements/PositionCharacteristics/PositionStatus/Description	Add new component
LocalContractRequirements/PositionCharacteristics/Description	Add new component
LocalContractRequirements/PositionCharacteristics/PositionLevel	Add new component
LocalContractRequirements/PositionCharacteristics/PositionCoefficient	Add new component
LocalContractRequirements/PositionCharacteristics/PositionSpecificCondition	Add new component
LocalContractRequirements/PositionCharacteristics/PositionSpecificCondition/Code	Add new component
LocalContractRequirements/PositionCharacteristics/PositionSpecificCondition/Descrption	Add new component
LocalContractRequirements/PositionCharacteristics/PositionSpecificCondition/Value	Add new component

2 Business Process

The Assignment is a part of the fulfilment process and it follows the Submission & Selection process. Initially, the Assignment transaction will finalize and confirm the negotiation between staffing customer, staffing supplier and human resource. It confirms the deployment and conditions of the staffing resource by the staffing customer and staffing supplier. In general, the process is:

· If the staffing supplier, staffing customer and human resource have agreed upon the conditions of the position, the staffing supplier creates the Assignment document. (Create Assignment)

· The Assignment document is sent by the staffing supplier to the staffing customer in order to confirm the agreement and conditions.

· If the Assignment is sent by the staffing supplier, the Assignment conditions such as rates, shift, etc. will form the basis of the Extended TimeCard and Invoice documents.

· Depending on the date range or changes in the conditions an Assignment can be revised by the staffing supplier, if agreed to by the staffing customer.

· An assignment may be ended when the ActualEndDate is equal to the ExpectedEndDate and no extension of the assignment is required by one of the parties. In this case, the staffing supplier will send the Assignment document with a status change and ActualEndDate; recommended but optional is to send additional EndReasonInformation to the staffing customer.

· An assignment can be ended by one of the parties at any time before the ExpectedEndDate. In such case, the staffing supplier will send the Assignment with a status change and ActualEndDate, an option is to send additional EndReasonInformation to the StaffingCustomer.

· An assignment can be extended by the staffing customer by sending a StaffingAction document with a type of RequestAction and the type comment of e.g. “Extend ExpectedEndDate by 3 weeks”, in which case; the staffing supplier will change the ExpendedEndDate and send the Assignment document to the staffing customer with a status of revised.

3 Schema Design

3.1 Assignment

3.1.1 Schema Diagram

3.1.2 Data Dictionary

See Appendix B – Related Documents (SIDES Reusable Modules) for details on CustomerReportingRequirements, Rates, and StaffingShift.

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ Assignment	- AssignmentType - (1/1) xml:lang - - AssignmentId - EntityIdType - S (1/) ReferenceInformation - [complexType] - S (1/1) CustomerReportingRequirements - [see include/import] - S (1/1) Rates - [see include/import] - S (1/) StaffingShift - [see include/import] - S (1/) AssignmentDateRange - [complexType] - S (1/1) EndReasonComments - xsd:string - S (0/1) ContractInformation - [complexType] - S (0/) UserArea - [see include/import] - S (0/1)	The work assignment of a person, for which times and expenses may be reported.
/ [AssignmentType] / assignmentStatus	- AssignmentStatusType -	Current status of the assignment. [BusinessRule(s): Serves as an indicator for changes during the lifespan of an assignment. ] [Example(s): Active, Inactive, Cancelled ]
/ Assignment/ AssignmentId	- EntityIdType - S (1/*)	Identifier of the assignment eventually agreed to by the trading partners. [BusinessRule(s): SIDES: Post assignment revisions via a HumanResourceDocument ]
/ Assignment/ ReferenceInformation	StaffingCustomerId - EntityIdType - S (1/) StaffingCustomerOrgUnitId - EntityIdType - S (0/) OrderId - EntityIdType - S (0/) HumanResourceId - EntityIdType - S (1/) IntermediaryId - EntityIdType - S (0/) PositionId - EntityIdType - S (1/) StaffingSupplierId - EntityIdType - S (0/) BillToEntityId - EntityIdType - S (0/) StaffingSupplierOrgUnitId - EntityIdType - S (0/*)	Contains reference information (a group of id's) regarding other business entities or transactions.
/ Assignment/ ReferenceInformation/ StaffingCustomerId	- EntityIdType - S (1/*)	Unique id used to identify the staffing customer.
/ Assignment/ ReferenceInformation/ StaffingCustomerOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing customer.
/ Assignment/ ReferenceInformation/ OrderId	- EntityIdType - S (0/*)	Unique identifier for a staffing order.
/ Assignment/ ReferenceInformation/ HumanResourceId	- EntityIdType - S (1/*)	Reference to a specific HumanResource.
/ Assignment/ ReferenceInformation/ IntermediaryId	- EntityIdType - S (0/*)	Unique identifier for a Vendor Management System or 3rd party responsible for staffing management
/ Assignment/ ReferenceInformation/ PositionId	- EntityIdType - S (1/*)	Reference to a uniquely identifiable position.
/ Assignment/ ReferenceInformation/ StaffingSupplierId	- EntityIdType - S (0/*)	Unique id used to identify the staffing supplier.
/ Assignment/ ReferenceInformation/ BillToEntityId	- EntityIdType - S (0/*)	Unique id used to identify the billing information.
/ Assignment/ ReferenceInformation/ StaffingSupplierOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing supplier.
/ Assignment/ AssignmentDateRange	StartDate - AnyDateTimeType - S (1/1) ExpectedEndDate - AnyDateTimeNkType - S (0/1) ActualEndDate - AnyDateTimeNaType - S (0/1) FlexibilityMinDate - AnyDateTimeNaType - S (0/1) FlexibilityMaxDate - AnyDateTimeNaType - S (0/1) ProbationaryPeriod - xsd:decimal - S (0/) SuspensionPeriod - [complexType] - S (0/)	Container for period of time the assignment is expected to occur.
/ Assignment/ AssignmentDateRange/ StartDate	- AnyDateTimeType - 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. ]
/ Assignment/ AssignmentDateRange/ ExpectedEndDate	- AnyDateTimeNkType - S (0/1)	The date the assignment is expected to end. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ Assignment/ AssignmentDateRange/ ActualEndDate	- AnyDateTimeNaType - S (0/1)	The (inclusive) date that an event actually ends, versus an estimated or projected end date.
/ Assignment/ AssignmentDateRange/ FlexibilityMinDate	- AnyDateTimeNaType - S (0/1)	The earliest (inclusive) date the assignment can begin.
/ Assignment/ AssignmentDateRange/ FlexibilityMaxDate	- AnyDateTimeNaType - S (0/1)	The latest (inclusive) date the assignment needs to end.
/ Assignment/ AssignmentDateRange/ ProbationaryPeriod	xsd:extension base: xsd:decimal unitOfMeasure - xsd:string -	A specific interval of time named at the beginning of a contract indicating a trial or test period.
/ Assignment/ AssignmentDateRange/ ProbationaryPeriod/ unitOfMeasure	- xsd:string -	Unit in which the period is measured.
/ Assignment/ AssignmentDateRange/ SuspensionPeriod	StartDate - AnyDateTimeType - S (1/1) EndDate - AnyDateTimeNkType - S (1/1) Comments - xsd:string - S (0/1)	Contains information about the interval of time that both customer and supplier agree that a contract will be suspended or on hold.
/ Assignment/ AssignmentDateRange/ SuspensionPeriod/ StartDate	- AnyDateTimeType - 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. ]
/ Assignment/ AssignmentDateRange/ SuspensionPeriod/ EndDate	- AnyDateTimeNkType - S (1/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.]
/ Assignment/ AssignmentDateRange/ SuspensionPeriod/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.
/ Assignment/ EndReasonComments	- xsd:string - S (0/1)	Comments on the reason for ending the assignment.
/ Assignment/ ContractInformation	contractType - ContractType - required contractStatus - ContractStatus - required ContractId - EntityIdType - S (1/1) LegalInformation - xsd:string - S (1/1) ContractVersion - xsd:string - S (1/1) ContractVersionDate - AnyDateTimeNkNaType - S (1/1) StaffType - xsd:string - S (1/1) LocalContractRequirements - LocalContractRequirementsType - S (0/1) FrameAgreementInfo - FrameAgreementType - S (0/*)	Employment contract details for the assignment (typically used internationally).
/ Assignment/ ContractInformation/ contractType	- ContractType -	The type of contract. [BusinessRule(s): Used to specify to which entity the contract applies. ]
/ Assignment/ ContractInformation/ contractStatus	- ContractStatus -	The status of the contract.
/ Assignment/ ContractInformation/ ContractId	- EntityIdType - S (1/1)	Unique identifier for the contract.
/ Assignment/ ContractInformation/ LegalInformation	- xsd:string - S (1/1)	Generic legal information, terms and conditions, etc.
/ Assignment/ ContractInformation/ ContractVersion	- xsd:string - S (1/1)	The version number of the contract.
/ Assignment/ ContractInformation/ ContractVersionDate	- AnyDateTimeNkNaType - S (1/1)	The date the contract version was released.
/ Assignment/ ContractInformation/ StaffType	- xsd:string - S (1/1)	Indicates the type of status with which the person undertakes the assignment. [Example(s): 1099, Contract, Employee ]
/ Assignment/ ContractInformation/ LocalContractRequirements	- LocalContractRequirementsType - S (0/1)	Contains information about the employment contracts specific to localized regulatory requirements.
/ Assignment/ ContractInformation/ FrameAgreementInfo	- FrameAgreementType - S (0/*)	Contains information about an agreement between a customer and supplier that established the rules and conditions that apply to all staffing contracts between the two entities.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [AssignmentStatusType]	- [Union]: KnownAssignmentStatus, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [ContractStatus]	- [Union]: KnownContractStatus, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [ContractType]	- [Union]: KnownContractType, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [KnownAssignmentStatus]	xsd:restriction base: xsd:string [Enumerations]: active, inactive, suspended, pending, revised, cancelled, ended	Globally scoped data type. See element or attribute declaration for definition.
/ [KnownContractStatus]	xsd:restriction base: xsd:string [Enumerations]: signed, unsigned	Globally scoped data type. See element or attribute declaration for definition.
/ [KnownContractType]	xsd:restriction base: xsd:string [Enumerations]: human resource, staffing customer	Globally scoped data type. See element or attribute declaration for definition.

3.2 Local Contract Requirements

3.2.1 Schema Diagram

3.2.2 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ LocalContractRequirements	- LocalContractRequirementsType - S (0/1) xml:lang - - WorkSite - WorkSiteType - S (0/1) StartStaffingShiftId - EntityIdType - S (0/1) ContractLegalReason - [complexType] - S (0/1) CompensationReference - [complexType] - S (0/*) SupplierSignature - [complexType] - S (0/1) CustomerSignature - [complexType] - S (0/1) PositionCharacteristics - [complexType] - S (0/1) UserArea - [see include/import] - S (0/1)	Contains information about the employment contracts specific to localized regulatory requirements.
/ LocalContractRequirements/ WorkSite	- WorkSiteType - S (0/1)	Contains common Work Site information, including name, address travel directions, and parking instructions.
/ LocalContractRequirements/ StartStaffingShiftId	- EntityIdType - S (0/1)	Contains information about the interval of time that both customer and supplier agree that a contract will be suspended or on hold. Unique identifier specifying a particular contractual shift in effect at the beginning of the assignment.
/ LocalContractRequirements/ ContractLegalReason	LocalContractType - xsd:string - S (1/1) RecourseType - [complexType] - S (1/1) ContractReason - xsd:string - S (1/1) ReplacedPerson - [complexType] - S (0/1)	Contains information on the regulatory justification for creation of the contract.
/ LocalContractRequirements/ ContractLegalReason/ LocalContractType	- xsd:string - S (1/1)	Specifies the nature of the contract. [Example(s): Minimum Duration, Date to Date, etc. ]
/ LocalContractRequirements/ ContractLegalReason/ RecourseType	Code - xsd:string - S (1/1) Description - xsd:string - S (1/1)	Defines the high-level legal reason for the contract. [Example(s): Replacement, seasonal ramp up. ]
/ LocalContractRequirements/ ContractLegalReason/ RecourseType/ Code	- xsd:string - S (1/1)	A code to further describe the associated element. [Example(s): Position Status Code, Job Family Code, Recourse Code ]
/ LocalContractRequirements/ ContractLegalReason/ RecourseType/ Description	- xsd:string - S (1/1)	Describes the contextual information relating to a specific element. [Example(s): Description defining an Organization's mission or purpose. Description of stock plan. Description of payment terms and conditions. ]
/ LocalContractRequirements/ ContractLegalReason/ ContractReason	- xsd:string - S (1/1)	Defines the specific reasons or cause for the contract. [Example(s): Replacement for sick employee, temporarily increased need to clean up after a flood, etc. ]
/ LocalContractRequirements/ ContractLegalReason/ ReplacedPerson	PersonName - PersonNameType - S (1/1) Position - xsd:string - S (1/1)	Indicates a specific person that the contracted worker will replace.
/ LocalContractRequirements/ ContractLegalReason/ ReplacedPerson/ PersonName	- PersonNameType - S (1/1)	The name of a person.
/ LocalContractRequirements/ ContractLegalReason/ ReplacedPerson/ Position	- xsd:string - S (1/1)	A single or specific instance of a job. [BusinessRule(s): A change in PositionTitle or OrganizationalUnit usually marks the start of a new position ]
/ LocalContractRequirements/ CompensationReference	Code - xsd:string - S (1/1) Description - xsd:string - S (1/1)	Contains information about the remuneration information and rules associated with the contract.
/ LocalContractRequirements/ CompensationReference/ Code	- xsd:string - S (1/1)	A code to further describe the associated element. [Example(s): Position Status Code, Job Family Code, Recourse Code ]
/ LocalContractRequirements/ CompensationReference/ Description	- xsd:string - S (1/1)	Describes the contextual information relating to a specific element. [Example(s): Description defining an Organization's mission or purpose. Description of stock plan. Description of payment terms and conditions. ]
/ LocalContractRequirements/ SupplierSignature	WrittenBy - PersonNameType - S (1/1) SignedBy - PersonNameType - S (1/1) Date - LocalDateType - S (1/1)	Contains information on the supplier’s signature portion of the contract. [BusinessRule(s): May or may not be legally used as a form of digital signature ]
/ LocalContractRequirements/ SupplierSignature/ WrittenBy	- PersonNameType - S (1/1)	Specifies the person what wrote or drafted the referenced contract.
/ LocalContractRequirements/ SupplierSignature/ SignedBy	- PersonNameType - S (1/1)	Specifies the authorized person or persons that have sign the contract on behalf of the supplier.
/ LocalContractRequirements/ SupplierSignature/ Date	- LocalDateType - S (1/1)	A date within the given context. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ LocalContractRequirements/ CustomerSignature	SignedBy - PersonNameType - S (1/1) Date - LocalDateType - S (1/1)	Contains information on the customer’s signature portion of the contract. [BusinessRule(s): May or may not be legally used as a form of digital signature. ]
/ LocalContractRequirements/ CustomerSignature/ SignedBy	- PersonNameType - S (1/1)	Specifies the authorized person or persons that have sign the contract on behalf of the customer.
/ LocalContractRequirements/ CustomerSignature/ Date	- LocalDateType - S (1/1)	A date within the given context. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601.]
/ LocalContractRequirements/ PositionCharacteristics	PositionTitle - xsd:string - S (1/1) PositionStatus - [complexType] - S (0/1) Description - xsd:string - S (0/1) PositionLevel - xsd:string - S (0/1) PositionCoefficient - xsd:string - S (0/1) PositionSpecificCondition - [complexType] - S (0/*)	Contains contractually required details about the properties of the position.
/ LocalContractRequirements/ PositionCharacteristics/ PositionTitle	- xsd:string - S (1/1)	A short phrase describing the position the way it would be listed on a business card or in a company directory. [BusinessRule(s): This may be the position currently held by the person, or the contact person's position. ] [Example(s): Vice President of Operations, Chief Information Officer ]
/ LocalContractRequirements/ PositionCharacteristics/ PositionStatus	Code - xsd:string - S (1/1) Description - xsd:string - S (1/1)	The current state of the position. [Example(s): Position Filled, Position Active, Position Open ]
/ LocalContractRequirements/ PositionCharacteristics/ PositionStatus/ Code	- xsd:string - S (1/1)	A code to further describe the associated element. [Example(s): Position Status Code, Job Family Code, Recourse Code ]
/ LocalContractRequirements/ PositionCharacteristics/ PositionStatus/ Description	- xsd:string - S (1/1)	Describes the contextual information relating to a specific element. [Example(s): Description defining an Organization's mission or purpose. Description of stock plan. Description of payment terms and conditions. ]
/ LocalContractRequirements/ PositionCharacteristics/ 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. Description of payment terms and conditions. ]
/ LocalContractRequirements/ PositionCharacteristics/ PositionLevel	- xsd:string - S (0/1)	Official level of the position in the collective agreement being applied by the customer.
/ LocalContractRequirements/ PositionCharacteristics/ PositionCoefficient	- xsd:string - S (0/1)	Official index or measure of the position’s properties in the collective agreement applied by the customer.
/ LocalContractRequirements/ PositionCharacteristics/ PositionSpecificCondition	ConditionCode - xsd:string - S (0/1) ConditionDescription - xsd:string - S (0/1) ConditionValue - xsd:string - S (0/1)	Contains information about any factors that could impact on the risk evaluation or work environment of the position.
/ LocalContractRequirements/ PositionCharacteristics/ PositionSpecificCondition/ ConditionCode	- xsd:string - S (0/1)	A categorization or identifying code for a condition or requirement relating to a particular position.
/ LocalContractRequirements/ PositionCharacteristics/ PositionSpecificCondition/ ConditionDescription	- xsd:string - S (0/1)	Describes the category or classification of the condition/requirement associated with a particular position. [Example(s): Medical control mandatory, risk exposure, security training mandatory. ]
/ LocalContractRequirements/ PositionCharacteristics/ PositionSpecificCondition/ ConditionValue	- xsd:string - S (0/1)	Describes the actual condition/requirement associated with the position. ] [Example(s): Exposure to dust or chemicals or loud noises, etc. ]

3.3 Frame Agreement Information

3.3.1 Schema Diagram

3.3.2 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ FrameAgreementInfo	- FrameAgreementType - S (0/) DocumentId - EntityIdType - S (1/1) DocumentVersion - xsd:string - S (1/1) ValidityDateRange - [complexType] - S (1/1) DocumentName - xsd:string - S (1/1) DocumentType - DocumentTypeType - S (0/1) StaffingOrgContact - ContactInfoType - S (0/)	Contains information about an agreement between a customer and supplier that established the rules and conditions that apply to all staffing contracts between the two entities.
/ FrameAgreementInfo/ DocumentId	- EntityIdType - S (1/1)	Open Applications Group definition: Is the primary DocumentId of the document for the given context. For example, if a buyer is sending a Purchase Order to a Supplier the Purchase Order Id will be contained with in the DocumentId. Similarly, in the instance of a semantic name of a SalesOrderDocumentReference the DocumentId will carry the senders identifier for the SalesOrder in the DocumentId and the cross-references would be provided by using the other semantic DocumentIds. HR-XML usage definition: High level containter for the overall or master invoice number itself. In typical usage, each line item is also assigned an individual invoice number.
/ FrameAgreementInfo/ DocumentVersion	- xsd:string - S (1/1)	Specifies a particular instance or configuration of a document.
/ FrameAgreementInfo/ ValidityDateRange	StartDate - AnyDateTimeType - S (1/1) EndDate - AnyDateTimeNkType - S (1/1)	Contains the dates that a particular version of a particular agreement are in effect.
/ FrameAgreementInfo/ ValidityDateRange/ StartDate	- AnyDateTimeType - 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. ] [Example(s): Position start date, assignment start date, rate change, effective date ]
/ FrameAgreementInfo/ ValidityDateRange/ EndDate	- AnyDateTimeNkType - S (1/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. R&S: If omitted, one of the following may be assumed: the position was still held at the time the document was created; the seeker is certified or licensed and either the l ]
/ FrameAgreementInfo/ DocumentName	- xsd:string - S (1/1)	Describes the way a particular contract or agreement is referenced.
/ FrameAgreementInfo/ DocumentType	- DocumentTypeType - S (0/1)	Specifies the applicability or binding scope of a frame agreement or contract.
/ FrameAgreementInfo/ StaffingOrgContact	xsd:extension base: ContactInfoType typeOfOrganization - [Union]: xStringPatternExtensionType - - required	Contains contact information for the signers of the agreement or contract.
/ FrameAgreementInfo/ StaffingOrgContact/ typeOfOrganization	- [Union]: xStringPatternExtensionType	Specifies the role or context of the organization in the transaction. [2] Specifies whether the organization is a customer or supplier, in the context of the transaction. ] [Example(s): Customer, supplier, intermediary, administrator ]

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [DocumentTypes]	xsd:restriction base: xsd:string [Enumerations]: worldwide, europe, national, regional	Globally scoped data type. See element or attribute declaration for definition.
/ [DocumentTypeType]	- [Union]: DocumentTypes, 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 diagrams and overview section.
2004-04-07	Updated definition tables.
2004-05-12	Changed CustomerSignature and SupplierSignature Date to LocalDateType. The DateType required a time. Updated diagrams, tables and example.
2004-06-08	Added xml:lang to top level element. Added unitOfMeasure to ProbationaryPeriod.
2004-Aug-02	Approved by membership.
2006-Feb-28	Approved by Consortium

6 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

7 Appendix C - Reference Examples

</AssignmentId>

</StaffingCustomerId>

</StaffingCustomerOrgUnitId>

</OrderId>

</HumanResourceId>

</PositionId>

<IdValue name="Accounting"> Accounts Payable </IdValue>

</BillToEntityId>

</ReferenceInformation>

<SupervisorName>Howard Wilkes</SupervisorName>

<DepartmentName>Shipping and Receiving</DepartmentName>

<LocationName>Dunlop Distribution</LocationName>

</CustomerReportingRequirements>

</ExternalRateSetId>

<Class>Regular</Class>

</StaffingShiftId>

</Rates>

</Id>

<Name>Standard Day Shift</Name>

<TypeHours>Regular Hours</TypeHours>

<Comment>One hour lunch from 1200 to 1300</Comment>

<IdValue name="Central Locations">Warehouse</IdValue>

</ExternalStaffingShiftSetId>

</StaffingShift>

<Comments>Replaced person not leaving until the 13th</Comments>

</SuspensionPeriod>

</AssignmentDateRange>

<IdValue name="Employee Contract">Sanchez037</IdValue>

</ContractId>

<LegalInformation>Renewable as needed up to one year from Start date</LegalInformation>

<StaffType>Contract</StaffType>

<WorkSiteName>Dunlop Distribution</WorkSiteName>

</WorkSiteId>

<Details xml:lang="en-gb" type="String">String</Details>

<Region>Midlands</Region>

<Municipality>Leicester</Municipality>

<AddressLine>Dunlop Business Centre</AddressLine>

<StreetName>Evington Valley Road</StreetName>

</DeliveryAddress>

<FormattedName type="presentation">Howard Wilkes</FormattedName>

</PersonName>

<AdditionalText>office just inside loading dock 2</AdditionalText>

</Recipient>

</PostalAddress>

<TravelDirections xml:lang="en-gb"> From Jct 21, M1 and M69, turn onto A5460, at junction of A563, Ring Road South. Turn left and follow road, crossing roundabout onto A563, Ring Road North. Drive to next island, cross A50 roundabout onto A563, follow road to next roundabout, passing the Leicester Water Centre. At the next roundabout turn right onto Evington Valley Road and continue to the Dunlop Business Centre</TravelDirections>

<ParkingInstructions xml:lang="en-us">Employee car park on south side of warehouse</ParkingInstructions>

<EnvironmentName>Distribution Centre</EnvironmentName>

<IdValue name="Midlands DC">Warehouse</IdValue>

</EnvironmentId>

<Description xml:lang="en-us">32000 square foot building</Description>

<General>non air-conditioned warehouse</General>

<Physical>Narrow aisles for stock, open area for shipping and receiving</Physical>

<DressCode suppliedByOrganization="1">Business Casual</DressCode>

</Considerations>

</WorkSiteEnvironment>

</WorkSite>

</StartStaffingShiftId>

<LocalContractType>customer</LocalContractType>

<Description>Mid-Term sick leave</Description>

</RecourseType>

<ContractReason>Replacing individual who will be undergoing surgery and expects a 6-9 month recovery period</ContractReason>

<FormattedName type="presentation">Samuel Adams</FormattedName>

<PreferredGivenName>Sick Sammy</PreferredGivenName>

</PersonName>

<Position>Shipping and Receiving Clerk</Position>

</ReplacedPerson>

</ContractLegalReason>

<Description>May be eligible for ₤.50 per hour increase after probationary period with high performance marks</Description>

</CompensationReference>

<FormattedName type="presentation">Agatha Admin </FormattedName>

</WrittenBy>

<FormattedName type="presentation">Sally Supplier</FormattedName>

</SignedBy>

</SupplierSignature>

<FormattedName type="presentation">Cathy Customer</FormattedName>

</SignedBy>

</CustomerSignature>

<PositionTitle>Shipping Clerk</PositionTitle>

<Code>Active</Code>

<Description>Position active and open req is filled</Description>

</PositionStatus>

<PositionCoefficient>String</PositionCoefficient>

<ConditionDescription>Lifting Required</ConditionDescription>

</PositionSpecificCondition>

</PositionCharacteristics>

</LocalContractRequirements>

</DocumentId>

<DocumentVersion>Version 2.5</DocumentVersion>

</ValidityDateRange>

<DocumentName>XYZ@ABC Midlands DC</DocumentName>

<DocumentType>regional</DocumentType>

<FormattedName type="presentation">Cathy Customer</FormattedName>

</PersonName>

<Use>business</Use>

<Location>office</Location>

<WhenAvailable>Weekdays, business hours</WhenAvailable>

</Telephone>

<Fax>

</Fax>

<InternetEmailAddress>cathyc@dunlapcentre.co.uk</InternetEmailAddress>

<InternetWebAddress>http://dunlapcentre.co.uk</InternetWebAddress>

<Municipality>Manchester</Municipality>

<BuildingNumber>Jape One Business Centre</BuildingNumber>

<Unit>Office Suite F6</Unit>

</DeliveryAddress>

<FormattedName type="presentation">Cathy Customer</FormattedName>

</PersonName>

<AdditionalText>Billing contact</AdditionalText>

<OrganizationName>ABC Logistics</OrganizationName>

</Recipient>

</PostalAddress>

</ContactMethod>

</StaffingOrgContact>

</FrameAgreementInfo>

</ContractInformation>

</Assignment>