HR-XML 3.0 Standards, 2009  September  23.

Menu: [ Home  |  Guidelines  |  BODs  |  Nouns  |  Global elements  |  WSDL  |  Packages  |  Code Lists  |  Master Index ]

Trace back: » ch45 | ch04 | ch02 | ch05 | ch28 »

Chapter 28. Staffing Scenarios

Staffing: Overview

HR-XML released a set of specifications in 2002 that it branded as Staffing Industry Data Exchange Standards (SIDES). The equivalent set of "nouns" is carried forward within the HR-XML 3.0 generation of specifications, with the exception of StaffingAction and StaffingOrganization. The prior SIDES specifications also included a set of component schemas shared among the set of SIDES schemas. Within the HR-XML 3.0 architecture, the vast majority of components are shared globally across the entire library. Consequently, the separate component schemas in the prior SIDES specifications have either been rolled into those globally shared base of components or replaced with suitable components from that shared base.

The four key staffing schemas in the HR-XML 3.0 library are:

StaffingOrder. Contains a set of information sufficient to place and manage an order with a staffng supplier. Can also be used in "request for quote" (RFQ) operations underwhich a customer seeks pricing and offer information from a supplier in connection with a "requisition." A staffing requisition (a statement of staffing resource requirements) is a component of an order.

StaffingResource. Contains information relating to a person proposed, or with which a staffing customer has contracted, to fulfill a staffed position or role.

StaffingAssignment. A staffing assignment conveys the set of terms and conditions related to the placement of a staffing resource with a staffing customer. A staffing assignment document may reference or constitute the contractual agreement between a staffing customer and staffing supplier with respect to the staffing placement. The StaffingAssignment document brings together information about the resource requirements to be filled (the requisition or position referenced in a StaffingOrder), with the resource selected to fill that position (previously described and communicated using the StaffingResource), and the various agreed upon terms (pay rates, start date, and expected end date among other details).

TimeCard. Contains a record of time worked and/or associated expenses to be reimbursed.

Staffing suppliers and intermediary systems might also use the Candidate and PositionOpening nouns. For further information, see the separate documentation available for those components.

Staffing: Actors

Actors commonly involved within supported staffing scenarios are:

  • Staffing Supplier. A staffing supplier or "staffing agency" identifies and provides human resources to fill service requirements defined by a customer organization. Staffing companies typically maintain an employment relationship with the resources supplied to the customer. Typically, customers turn to staffing agencies to fill project-based, temporary, or so-called "contingent" staffing needs. Some customers also may use a resource's assignment under a staffing arrangement to evaluate the resource's fit for direct employment within the customer organization. Staffing suppliers typically assume legal and payroll tax obligations with repect to the resource whereas the customer merely pays the supplier a set rate (and possibly expenses) to the staffing supplier.

  • Staffing Customer. A staffing customer is a party that procures the services of contract or temporary workers or similar resources through a staffing agency. The customer may work directly with a specific supplier or may work with one or more suppliers through an intermediary staffing vendor management service.

  • Master Vendor (MV). Manages the contingent labor needs of a client giving first preference always to their own inventory of temporary employees.

  • Vendor on Premise (VOP). A Master Vendor who manages the client's labor need onsite. This presence makes the relationship between vendor and client closer, leading to better understanding and quality of service. This is a somewhat archaic term since this practice is now more common for accounts of any size.

  • Vendor Management System (VMS). The system, generically known as an eProcurement Tool, which supports several different business models: Vendor Managed Services, Managed Services Provider (MSP), Master Vendor (MV), etc. The use of the system should not imply the exact transactional business model in place.

  • eProcurement Tool. The application used by a Managed Service Provider (MSP), Vendor on Premise (VOP), Master Vendor (MV), Vendor Managed Service, etc. to help provide their service.

Other possible actors include applicant tracking systems (some ATS systems may also have certain VMS capabilities), job boards, and a variety of other intermediary or third-party recruitment service providers.

Of course, the candidate or human resource is the other actor involved in staffing scenarios. However, HR-XML specifications do not specifically address direct interactions with candidates.

Comment on this Component


Use the form below to submit your question or comment about "ch28"

By submitting you indicate that you are accepting HR-XML's Feedback Policy


  * = required field
First/Given Name: *
Last/Family Name: *
Position Title:
Organization:
Country:
Website:
E-mail: *
Topic:

  Please use the area below to write your comment or question: