Work Site
Recommendation, 2007 April 15
Editors:
Kim Bartkus, HR-XML Consortium, Inc.
Contributors:
Members of the Cross-Process Object work group
Members of the Recruiting & Staffing work group
Members of the Screening work group
Copyright © 2007 HR-XML Consortium, Inc.
Abstract
The document defines the work site and worksite environment information, which may be used for a variety of business processes such as a temporary staffing order or posting a position.
Table of Contents
1.2 Relationship to Business Processes
3 Implementation Considerations
4 Appendix A - Revision History
5 Appendix B - Related Documents. 10
1 Overview
1.1 Objective
Update the WorkSite and WorkSiteEnvironment schemas to use existing CPO’s, convert to global complex types, remove locally scoped prefixes, and combine the two schemas. The functionality of the schemas will not change. However, the schemas will not be backwards compatible with previous work site versions.
Details of the modifications include:
§ Combine WorkSiteEnvironment schema into WorkSite schema file. This will eliminate the need for two similar schema files.
§ Convert WorkSite and WorkSiteEnvironment schemas to a complex type element.
- Use CPO EntityIdType, LanguageDependentTextType where appropriate.
- Remove locally scoped prefixes. For example, WorkSiteName was change to Name.
- Change Detail’s attribute to ‘type’ to eliminate a conflict of using the name ‘WorkSiteType’ for both an attribute and complex type element.
- Restructure Consideration element/attributes to allow for SafetyEquipment and DressCode to have thier own attribute.
- Include WorkSiteEnvironment within WorkSite schema as an optional module.
- Added user areas.
- Added WorkSiteId to the WorkSiteEnvironment schema.
1.2 Relationship to Business Processes
Recruiting - recruiters use job and position data for hiring purposes. Postings may be created for jobs or positions.
Temporary Staffing - work areas are manned to meet production needs on the basis of the jobs that need to be done.
1.3 Scope
The WorkSite and WorkSiteEnvironment Schemas are cross-process objects that will be used within other HR-XML Schemas. They will contain:
· Information pertaining to the site or location of a job or position.
· Information pertaining to the environment of a job or position.
General Considerations
Physical Considerations
Safety Equipment
Dress Code
1.4 Design Requirements
· Syntax must be self-documenting
· Deployable in existing HR-XML Schemas
· Easy to understand and use
· Use approved CPO standards
· Designed for easy reuse
· Must take into consideration global requirements
2 Schema/DTD Design
2.1 WorkSite
2.1.1 Schema Graphic
2.1.2 Schema Elements and Data Types Explained
|
Component Name [Global types listed at the end of the table.] |
ContentModel* |
Definition |
|
/ |
WorkSiteType - (1/1)
WorkSiteName
- xsd:string - S
(0/1) |
Contains common Work Site information to be used within other HR-XML Schemas. |
|
/
WorkSite/ |
- xsd:string - S (0/1) |
Contains a name or brief description of the worksite. For example, Office, Warehouse, Fieldwork |
|
/
WorkSite/ |
- EntityIdType - S (0/1) |
Unique Id to define the worksite |
|
/
WorkSite/ |
xsd:extension base: LanguageDependentTextType |
Describes any information not previously defined. For example, when a specific postal address isn't provided, then a brief description may be defined here, such as: Report to 4th floor mailroom. |
|
/ WorkSite/
Details/ |
- xsd:string - |
Further describes the type or purpose of the worksite details. For example, Report to first day, Report to permanently, Virtual worksite, Report for training. |
|
/
WorkSite/ |
- PostalAddressType - S (0/1) |
CPO's PostalAddress 1.2 version. Defines the mailing address of the worksite. |
|
/
WorkSite/ |
- LanguageDependentTextType - S (0/*) |
Provides directions to the site. These could include directions by bus, air, car, walking, etc. |
|
/
WorkSite/ |
- LanguageDependentTextType - S (0/*) |
Provides instructions for parking, including fees. E.g. parking is available on upper level of parking structure. Fees are $70 per month. |
|
/
WorkSite/ |
- WorkSiteEnvironmentType - S (0/*) |
Contains common Work Site Environment information, including description, physical considerations, dress code, and safety equipment. |
2.2 WorkSiteEnvironment
2.2.1 Schema
2.2.2 Schema Elements and Data Types Explained
|
Component Name [Global types listed at the end of the table.] |
ContentModel* (minOccurs/maxOccurs) |
Definition |
|
|
- WorkSiteEnvironmentType - S (0/*) |
Contains common Work Site Environment information, including description, physical considerations, dress code, and safety equipment. |
|
WorkSiteEnvironment/ |
- xsd:string - S (0/1) |
Contains a name or brief description of the worksite environment. For example, Laboratory, Warehouse, Fieldwork. |
|
WorkSiteEnvironment/ |
- EntityIdType - S (0/1) |
Unique Id to define the worksite environment. |
|
WorkSiteEnvironment/ |
- EntityIdType - S (0/1) |
Unique Id to define the worksite. |
|
WorkSiteEnvironment/ |
xsd:extension base: xsd:string |
Describes any work site environment information not previously defined. For example, square footage of work area. |
|
WorkSiteEnvironment/ |
General
- xsd:string - S
(0/*) |
Describes any special considerations for the environment. For example, Safety Equipment and Dress Code. |
|
WorkSiteEnvironment/
Considerations/ |
- xsd:string - S (0/*) |
Additional information on the work environment, which may be useful to both the Staffing Supplier and Human Resource. For example, lunch facility, smoke free. |
|
WorkSiteEnvironment/
Considerations/ |
- xsd:string - S (0/*) |
Description of physical aspects of the environment, which may influence the Staffing Supplier or the Human Resource when the position or assignment is offered. For example, wheelchair accessible, no elevator, climate control, dust level, bio-hazardous material. |
|
WorkSiteEnvironment/
Considerations/ |
SafetyEquipmentType - S (0/*)
xsd:extension base: xsd:string |
Defines any safety equipment required for the work site environment. For example, hard Hat, safety glasses, steel-toed shoes. |
|
/
[SafetyEquipmentType] / |
- xsd:boolean - |
Specifies whether the safety equipment is provided by the organization. For example, safety glasses, uniforms, etc. |
|
WorkSiteEnvironment/
Considerations/ |
DressCodeType - S (0/*)
xsd:extension base: DressCodeContentTypes |
Defines any dress code requirements for the environment. For example, tie, suit, business casual. |
|
/
[DressCodeType] / |
- xsd:boolean - |
Specifies whether the safety equipment is provided by the organization. For example, safety glasses, uniforms, etc. |
|
Global simpleTypes: |
|
|
|
/ |
- [Union]: DressCodeContentType,xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Professional, Business, Business Casual, Uniform |
Globally scoped data type. See element or attribute declaration for definition. |
3 Implementation Considerations
All elements in the schemas are optional; this provides the maximum flexibility for reuse. Receiving systems must perform their own integrity checking and validation.
WorkSiteEnvironmentType may be used independent of WorkSite in a variety of transactions. An example might be the addition of a new environment, i.e. an additional shop floor or new laboratory. Pricing, risk assessment, and recruiting might be different for a person working in the office versus the shop floor.
Elements defined with the xml:lang attribute allow for multiple occurrences. This SHOULD only be used for multiple language support.
4 Appendix A - Revision History
|
Date |
Description |
|
2002-Sep-24 |
Draft |
|
2002-Oct-31 |
Updated graphics, definition tables |
|
2002-Dec-12 |
Removed locally scoped prefixes, combined schemas into one file, restructured Consideration into elements. |
|
2002-Dec-13 |
Changed Considerations child elements, ParkingInstructions, and TravelDirections to multiple occurrences. Added UserArea, Added WorkSiteId to WorkSiteEnvironment. Added attribute to DressCode. |
|
2003-Jan-08 |
Added language attribute to Description, Details, and Considerations. |
|
2003-Jan-23 |
Made SafetyEquipment and DressCode complex types. Added enumeration list to DressCode. Reordered elements with Id’s near top of structure. |
|
2003-Feb-26 |
Approved recommendation by HR-XML Consortium. The default and targetNamespaces of all HR-XML schemas have been standardized. This recommendation is available as part of the HR-XML 2_4 architecture. |
|
2007-Apr-15 |
Approved by Consortium |
5 Appendix B - Related Documents
|
Link |
|
|
Entity Identifiers |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EntityIdentifiers.html |
|
Postal Address |
6 Appendix C – Schema Example
The following example describes a research facility. A laboratory environment is included within the work site. However, the laboratory information may also be transmitted without the work site wrapper information.
<WorkSite>
<WorkSiteName>Research Facility</WorkSiteName>
<WorkSiteId idOwner="Staffing Company">
<IdValue>RF21</IdValue>
</WorkSiteId>
<Details type="Report to Permanently">2nd floor of Research Wing</Details>
<PostalAddress>
<CountryCode>US</CountryCode>
<PostalCode>60187</PostalCode>
<Region>IL</Region>
<Municipality>Wheaton</Municipality>
<DeliveryAddress>
<AddressLine>455</AddressLine>
<StreetName>Meadow Parkway</StreetName>
</DeliveryAddress>
</PostalAddress>
<TravelDirections>Take Interstate 405 to Interstate 5. Take exit 6 south. Go to 2nd traffic light and make a left turn onto Meadow Parkway. First building on right side.</TravelDirections>
<ParkingInstructions>Park in lot south of building.</ParkingInstructions>
<WorkSiteEnvironment>
<EnvironmentName>Laboratory</EnvironmentName>
<EnvironmentId idOwner="Staffing Company">
<IdValue>LA21</IdValue>
</EnvironmentId>
<Description>Clean Room</Description>
<Considerations>
<General>Lunch Room Facilities</General>
<Physical>Wheelchair Accessible</Physical>
<SafetyEquipment suppliedByOrganization="true">Protective clothing required in Clean Room</SafetyEquipment>
<DressCode suppliedByOrganization="false">Business Casual</DressCode>
</Considerations>
</WorkSiteEnvironment>
</WorkSite>