Assignment
Recommendation, 2007 April 15
Editors:
Kim Bartkus, HR-XML Consortium
Contributors:
Gail Bubsey (Kelly Services ), Kim Bartkus (HR-XML Consortium), Barbara Johnson (Adecco NA), Tara Ryan (Adecco), Kazuko Sugamura (Manpower Japan), Takahiro Fujiwara (EAST Co., Ltd.), Magali Munoz (Manpower France), Bruno Alcotte (Manpower France), Rémy Bailly (Randstad), Yves Berdah (VidiorBis), Serguei Dounaevetski (Manpower France), Patrice Aranega (Adecco France)
Copyright © 2007 HR-XML Consortium, Inc.
Abstract
The HR-XML SIDES Workgroup has produced 7 major schemas and several reusable modules to allow for transmission of Staffing Industry information between trading partners. This document describes the Assignment schema, its expected usage, and the business processes meant to be supported.
Table of Contents
3.3 Frame Agreement Information
4 Implementation Considerations
5 Appendix A - Document Version History
6 Appendix B – Related Documents
1 Overview
Changes were made to the base SIDES specification based on feedback from the European and Japanese Chapters. If available, localized items are documented in section 4 Implementation Considerations or in individual country documentation. Refer to Appendix A - Document Version History for details.
1.1 Objective
Within the framework of SIDES, the 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
· 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.
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* |
Definition |
|
/ |
- AssignmentType - (1/1) |
The work assignment of a person, for which times and expenses may be reported. |
|
/
[AssignmentType] / |
- AssignmentStatusType - |
Current
status of the assignment. |
|
/ Assignment/ |
- EntityIdType - S (1/*) |
Identifier of the assignment
eventually agreed to by the trading partners. |
|
/ Assignment/ |
StaffingCustomerId - EntityIdType - S (1/*) StaffingOrganizationId - EntityIdType - S (0/*) |
Contains reference information (a group of id's) regarding other business entities or transactions. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (1/*) |
Unique id used to identify the staffing customer. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing customer. |
|
/ Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a staffing order. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (1/*) |
Reference to a specific HumanResource. |
|
/ Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique identifier for a Vendor Management System or 3rd party responsible for staffing management |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (1/*) |
Reference to a uniquely identifiable position. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing supplier. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the billing information. |
|
/ Assignment/
ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify a particular organizational unit of the staffing supplier. |
|
/
Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Reference to a master order or project. Used to link multiple orders. |
|
/
Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the time card. |
|
/
Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the Invoice. |
|
/
Assignment/ ReferenceInformation/ |
- EntityIdType - S (0/*) |
Unique id used to identify the staffing organization. |
|
/ Assignment/ |
StartDate - AnyDateTimeType - S (1/1) EffectiveDate - AnyDateTimeType – S (0/1) |
Container for period of time the assignment is expected to occur. |
|
/ Assignment/
AssignmentDateRange/ |
- AnyDateTimeType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes active or begins. |
|
/ Assignment/
AssignmentDateRange/ |
- AnyDateTimeNkType - S (0/1) |
The date the assignment is
expected to end. |
|
/ Assignment/
AssignmentDateRange/ |
- AnyDateTimeNaType - S (0/1) |
The date that an event actually ends, versus an estimated or projected end date. |
|
/ Assignment/
AssignmentDateRange/ |
- AnyDateTimeNaType - S (0/1) |
The earliest (inclusive) date the assignment contract can begin. |
|
/ Assignment/
AssignmentDateRange/ |
- AnyDateTimeNaType - S (0/1) |
The latest (inclusive) date the assignment contract needs to end. |
|
/ Assignment/ AssignmentDateRange/ |
xsd:extension base: xsd:decimal |
A specific interval of time named at the beginning of a contract indicating a trial or test period. |
|
/ Assignment/ AssignmentDateRange/
ProbationaryPeriod/ |
- xsd:string - |
Unit in which the quantity is
measured. |
|
/ Assignment/
AssignmentDateRange/ |
StartDate - AnyDateTimeType - S (1/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/ |
- AnyDateTimeType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes active or begins. |
|
/ Assignment/ AssignmentDateRange/
SuspensionPeriod/ |
- AnyDateTimeNkType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes inactive or ends. |
|
/ Assignment/
AssignmentDateRange/ SuspensionPeriod/ |
- xsd:string - S (0/1) |
Describes the contextual information relating to a group of elements. |
|
/ Assignment/ |
- AnyDateTimeType - S (0/1) |
Date or time interval on or
during which information or events are effective. |
|
/ Assignment/ |
- xsd:string - S (0/1) |
Comments on the reason for ending the assignment. |
|
Global
types |
ContentModel* |
Definition |
|
/ |
- [Union]: KnownAssignmentStatus,xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: active, inactive, suspended, pending, revised, cancelled, ended |
Globally scoped data type. See element or attribute declaration for definition. |
3.2 ContractInformation
3.2.1 Schema Diagram
3.2.2 Data Dictionary
|
/ Assignment/ |
contractType - ContractType
- required |
Employment contract details for the assignment (typically used internationally). |
|
/ Assignment/
ContractInformation/ |
- ContractType - |
The type of contract. |
|
/ Assignment/
ContractInformation/ |
- ContractStatus - |
The status of the contract. |
|
/ Assignment/
ContractInformation/ |
- EntityIdType - S (1/1) |
Unique identifier for the contract. |
|
/ Assignment/
ContractInformation/ |
- xsd:string - S (1/1) |
Generic legal information, terms and conditions, etc. |
|
/ Assignment/
ContractInformation/ |
- xsd:string - S (1/1) |
The version number of the contract. |
|
/ Assignment/
ContractInformation/ |
- AnyDateTimeNkNaType - S (1/1) |
The date the contract version was released. |
|
/ Assignment/
ContractInformation/ |
- xsd:string - S (1/1) |
Indicates the type of status with
which the person undertakes the assignment. |
|
/ Assignment/
ContractInformation/ |
- LocalContractRequirementsType - S (0/1) |
Contains information about the employment contracts specific to localized regulatory requirements. |
|
Global
types |
ContentModel* |
Definition |
|
/ |
- [Union]: KnownContractStatus,xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: KnownContractType,xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: signed, unsigned |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: human resource, staffing customer |
Globally scoped data type. See element or attribute declaration for definition. |
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* |
Definition |
|
/ |
- 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. |
|
/ FrameAgreementInfo/ |
- 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/ |
- xsd:string - S (1/1) |
Specifies a particular instance or configuration of a document. |
|
/ FrameAgreementInfo/ |
StartDate - AnyDateTimeType - S (1/1) |
Contains the dates that a particular version of a particular agreement are in effect. |
|
/ FrameAgreementInfo/
ValidityDateRange/ |
- AnyDateTimeType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes active or begins. |
|
/ FrameAgreementInfo/
ValidityDateRange/ |
- AnyDateTimeNkType - S (1/1) |
Contains the (inclusive) date,
period, or interval the event becomes inactive or ends. |
|
/ FrameAgreementInfo/ |
- xsd:string - S (1/1) |
Describes the way a particular contract or agreement is referenced. |
|
/ FrameAgreementInfo/ |
- DocumentTypeType - S (0/1) |
Specifies the applicability or binding scope of a frame agreement or contract. |
|
/ FrameAgreementInfo/ |
xsd:extension base: ContactInfoType |
Contains contact information for the signers of the agreement or contract. |
|
/ FrameAgreementInfo/
StaffingOrgContact/ |
- [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. ] |
|
Global
types |
ContentModel* |
Definition |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: worldwide, europe, national, regional |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [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).
4.2 Use of Effective Date
The purpose of the EffectiveDate was to define the effective date of the contract or contract extension. This field was originally added to the ContractInformation. However, the effective date is also contingent on several of the dates within the AssignmentDateRange. Therefore, the EffectiveDate was moved to the AssignmentDateRange. There is still concern that this might not be the appropriate place for this field. One consideration is that the ContractInformation is repeatable, whereas the AssignmentDateRange is not. This requires that the EffectiveDate refer to all contracts within the Assignment transaction.
The workgroup will address this issue in a future release. The use of the fields may be clarified or it may be deprecated. Another option is to clarify the purpose of the existing date and add a ContractEffectiveDate to the ContractInformation. In the meantime, the AssignmentDateRange/EffectiveDate will be used to define the effective date of the contract or contract extension.
4.3 LocalContractRequirements
The structure contains the base French Contract Requirements extended by the Japanese Contract Requirements.
Data Dictionary
|
Global
types |
ContentModel* |
Definition ** |
|
/ |
FRContractRequirements - [see include/import] - C
(0/1) |
Globally scoped data type. See element or attribute declaration for definition. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
xml:lang - - |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ [FRContractRequirementsType]/ |
- WorkSiteType - S (0/1) |
Contains common Work Site information, including name, address travel directions, and parking instructions. |
|
/ [FRContractRequirementsType]/ |
- EntityIdType - S (0/1) |
Unique identifier specifying a particular contractual shift in effect at the beginning of the assignment. |
|
/ [FRContractRequirementsType]/ |
LocalContractType - xsd:string - S (1/1) |
Contains information on the regulatory justification for creation of the contract. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ |
- xsd:string - S (1/1) |
Specifies the nature of the
contract. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ |
Code - xsd:string
- S (1/1) |
Defines the high-level legal
reason for the assignment contract. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ RecourseType/ |
- xsd:string - S (1/1) |
A code to further describe the
associated element. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ RecourseType/ |
- xsd:string - S (1/1) |
Describes the contextual
information relating to a specific element. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ |
- xsd:string - S (1/1) |
Defines the specific reasons or
cause for the contract. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ |
PersonName - PersonNameType - S (1/1) |
Indicates a specific person whom the contracted worker will replace. [2] Specific person whom the contracted worker will replace. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ ReplacedPerson/ |
- PersonNameType - S (1/1) |
The name of a person. |
|
/ [FRContractRequirementsType]/
ContractLegalReason/ ReplacedPerson/ |
- xsd:string - S (1/1) |
A single or specific instance of
a job. |
|
/ [FRContractRequirementsType]/ |
Code - xsd:string
- S (1/1) |
Contains information about the remuneration information and rules associated with the contract. |
|
/ [FRContractRequirementsType]/
CompensationReference/ |
- xsd:string - S (1/1) |
A code to further describe the
associated element. |
|
/ [FRContractRequirementsType]/
CompensationReference/ |
- xsd:string - S (1/1) |
Describes the contextual
information relating to a specific element. |
|
/ [FRContractRequirementsType]/ |
WrittenBy - PersonNameType - S (1/1) |
Contains information on the
supplier’s signature portion of the contract. |
|
/ [FRContractRequirementsType]/
SupplierSignature/ |
- PersonNameType - S (1/1) |
Specifies the person what wrote or drafted the referenced contract. |
|
/ [FRContractRequirementsType]/
SupplierSignature/ |
- PersonNameType - S (1/1) |
Specifies the authorized person or persons that have signed the contract on behalf of the supplier or customer. |
|
/ [FRContractRequirementsType]/
SupplierSignature/ |
- LocalDateType - S (1/1) |
A date within the given context. |
|
/ [FRContractRequirementsType]/ |
SignedBy - PersonNameType - S (1/1) |
Contains information on the
customer’s signature portion of the contract. |
|
/ [FRContractRequirementsType]/
CustomerSignature/ |
- PersonNameType - S (1/1) |
Specifies the authorized person or persons that have signed the contract on behalf of the supplier or customer. |
|
/ [FRContractRequirementsType]/
CustomerSignature/ |
- LocalDateType - S (1/1) |
A date within the given context. |
|
/ [FRContractRequirementsType]/ |
PositionTitle - xsd:string - S (1/1) |
Contains contractually required details about the properties of the position. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
- 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. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
Code - xsd:string
- S (1/1) |
The current state of the
position. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ PositionStatus/ |
- xsd:string - S (1/1) |
A code to further describe the
associated element. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ PositionStatus/ |
- xsd:string - S (1/1) |
Describes the contextual
information relating to a specific element. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
- xsd:string - S (0/1) |
Describes the contextual
information relating to a specific element. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
- xsd:string - S (0/1) |
Official level of the position in the collective agreement being applied by the customer. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
- xsd:string - S (0/1) |
Official index or measure of the position’s properties in the collective agreement applied by the customer. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ |
ConditionCode - xsd:string - S (0/1) |
Contains information about any factors that could impact on the risk evaluation or work environment of the position. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ PositionSpecificCondition/ |
- xsd:string - S (0/1) |
A categorization or identifying code for a condition or requirement relating to a particular position. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ PositionSpecificCondition/ |
- xsd:string - S (0/1) |
Describes the category or
classification of the condition/requirement associated with a particular
position. |
|
/ [FRContractRequirementsType]/
PositionCharacteristics/ PositionSpecificCondition/ |
- xsd:string - S (0/1) |
Describes the actual
condition/requirement associated with the position. |
Sample xml
See Assignment.xml for sample French data (Appendix B – Related Documents).
4.3.1 Japanese Localization
In Japan, the Temporary Services Law requires relevant details to be described in legal format in the following cases.
1. When a staffing supplier receives complaints from a staffing resource, the supplier must record in legal format the date, details, and how the complaint was handled.
2. Each contract must describe in legal format a contract cancellation policy based on the Standard Labor Laws.
3. In the case of a temporary-to-permanent contract, the contractual details must be described in legal format base on the Temporary Services Law.
Data Dictionary
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- JPContractRequirementsType - (1/1) |
Contains Japanese localization
information for contractual requirements. |
|
/ JPContractRequirements/ |
- xsd:string - S (0/1) |
Details of complaints received
from staffing resources for recording in legal format. |
|
/ JPContractRequirements/ |
- xsd:string - S (0/1) |
Contract cancellation policy
based on the Standard Labor Laws. |
|
/ JPContractRequirements/ |
PlacementTiming - xsd:string - S (1/1) |
Contractual details in legal
format for becoming permanent staff in a temporary-to-permanent contract. |
|
/ JPContractRequirements/ PlacementNotification/ |
- xsd:string - S (1/1) |
Start date of permanent
placement. |
|
/ JPContractRequirements/
PlacementNotification/ |
- xsd:string - S (1/1) |
Job description of permanent
placement. |
|
/ JPContractRequirements/
PlacementNotification/ |
- xsd:string - S (1/1) |
Specifies if the permanent
placement is successful or not. |
|
/ JPContractRequirements/
PlacementNotification/ |
- xsd:string - S (1/1) |
Reason for unsuccessful closing
of contract. |
Sample xml
<JPContractRequirements>
<!-- The example where the temporary service assignment started from January 10, 2006 did not go to the permanent placement due to the candidate’s unacceptable entrance test result. -->
<!-- ComplaintProcedure - How to process complaints and contact process-->
<!--The example for <ComplaintProcedure> is not included in this XML sample. -->
<PlacementNotification>
<PlacementTiming>no employment </PlacementTiming>
<PlacementContent>entrance examination</PlacementContent>
<Result>no employment</Result>
<ReasonOfReject>The test result did not make the passing mark.</ReasonOfReject>
</PlacementNotification>
</JPContractRequirements>
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. |
|
2006-Mar-01 |
Added Reference Id's to match other SIDES schemas: MasterOrderId, TimeCardId, InvoiceId and StaffingOrganizationId. Added EffectiveDate to ContractInformation. Changed LocalContractRequirements to localized structure. Added JPContractRequirements. See Implementation Guidelines and/or Japanese documentation for details. |
|
2007-Jan-25 |
Moved EffectiveDate element from ContractInformation to AssignmentDateRange based on feedback from French SIDES group. See section 4.2 for implementation guidelines. |
|
2007-Apr-15 |
Approved by Consortium |
6 Appendix B – Related Documents