Metrics Interchange

Recommendation, 2007 April 15

Editor:

Chuck Allen, HR-XML Consortium, Inc.

Contributors:

Joanne Fritz, ADP; Scott Mitchell, ePredix Inc.; Kim Bartkus, HR-XML; Paul Kiel, HR-XML; Heather Hartmann, Human Capital Metrics Consortium; Nick Scobbo, Mitre; Bill Kerr, Oracle; Barbara Davison, Saratoga Institute/PriceWaterhouseCoopers; Dave Ingram, The Gallup Organization; Michelle Winston, The Gallup Organization

Abstract

This document describes the simple, yet flexible schema capable of supporting a wide variety of integration scenarios involving the exchange of HR metrics data.

Table of Contents

1 Overview.. 4

1.1 Objective. 4

1.1.1 Domain Issues. 4

1.1.2 Business Reasons. 4

1.1.3 Limitations / Risks. 5

1.2 Design Requirements. 5

1.3 Scope. 5

1.3.1 Major Components. 5

1.3.2 Items Outside of Design Scope. 6

1.4 Terminology. 6

1.4.1 Metrics Reporting Organization. 6

1.4.2 Source Organization. 6

1.4.3 Metrics Consumer 6

1.4.4 Metrics Consolidator 7

1.4.5 Metrics Template. 7

1.4.6 Instance Report 7

1.4.7 Summary Report 7

2 Supported Business Processes. 7

2.1 Metrics Interchange Business Process. 7

2.1.1 Business Process Scenarios. 7

3 Component Schemas and Dependencies. 9

3.1 Use Notes. 9

3.1.1 Organization.xsd. 9

3.1.2 PhysicalLocation.xsd. 10

3.2 Schema Elements Explained. 10

3.2.1 MetricsInterchange. 10

3.2.2 ReportedOrganization. 12

3.2.3 ReportedPerson. 18

3.2.4 DataElement 21

3.2.5 Global Types. 21

4 Implementation Considerations. 23

4.1 Data Privacy. 23

5 Appendix A - Document Version History. 23

6 Appendix B – Related Documents. 24

7 Appendix C – Reference Examples. 24

7.1 Template Requirements. 24

7.1.1 Example 1: Template To Implement Human Capital Metrics Consortium Benchmark Survey. 25

7.1.2 Example 1: Instance Implementing HCMC Template. 29

7.1.3 Example 2: Template To Implement Individual Performance Measures To Validate an Assessment 29

7.1.4 Example 2: Instance To Implement Individual Performance Measures To Validate an Assessment 36

1 Overview

1.1 Objective

The goal of this project is to develop a simple, yet flexible schema capable of supporting a wide variety of integration scenarios involving the exchange of HR metrics data.

1.1.1 Domain Issues

HR management transactions (interviews, hires, enrollments, payroll, terminations, promotions, etc.) result in a variety of source data that can be important for the generation of HR performance measures. The raw transactional data is usually organized or processed before they yield useful information. There are an increasing number of software applications and service providers that aim to discover, organize, and process relevant HR transactional data so that business managers can better understand organizational and individual performance.

Frequently, businesses want to organize their internal data so that they can be compared to benchmarking measures or other normative data. For example, a company might want to examine its employee turnover compared to other organizations within the same industry and / or region as measured by a survey undertaken by a metrics or benchmarking company.

To seamlessly access and compare internal performance data and external measures usually requires the acquisition of data from one or more systems. The HR-XML Consortium’s Metrics Interchange Schema enables these types of data exchanges. Because of the wide variety of performance data and integration scenarios, the HR-XML Consortium’s Metrics Interchange Schema provides a very generalized, flexible structure that usually would be accompanied with an implementer-defined template. The template would indicate how the schema is applied to the given data and integration scenario. Two of many possible scenarios are illustrated in Appendix C – Reference Examples.

1.1.2 Business Reasons

Solution Providers

The HR-XML Consortium’s Metrics Interchange standard will make it easier to automate the acquisition and transfer of HR metrics data between and among a wide variety of HR solution providers.

Example: The HR-XML Consortium’s Metrics Interchange standard will make it easier for HR research and benchmarking companies and providers of business intelligence tools to opportunistically partner with each other.

Example: The schema also will be helpful to assessment vendors. Providers of assessment services frequently want to acquire on-the-job performance data so that pre-employment assessment results can be validated as statistically relevant predictors of on-the-job performance. Today, such data is typically extracted from performance management systems on an ad hoc basis or the data is manually compiled and then sent to the assessment company in a proprietary format, such as a spreadsheet.

Employers

Employers have invested considerable sums into business intelligence (BI) tools and into reporting and human capital management solutions aimed at providing insight into organizational and individual performance. To have a basis against which to compare internal performance, many of the same organizations have invested significant amounts to sponsor the work of third-party research and benchmarking organizations. A flexible interchange mechanism for metrics will help employers maximize their return on both of these investments.

Today, internal measures and external benchmarking data are typically integrated using ad hoc or manual processes. For example, an HR manager might manually take data from a BI or HR reporting tool, copy it into paper or web-based survey questionnaires, wait for the next quarterly or annual survey report to be returned, and then perhaps manually integrate or compare the benchmarks against internal numbers.

If BI and HR solutions were well integrated with benchmarking and survey solution providers, little manual integration of data would be required. Data required for a particular survey could be extracted with little manual intervention and sent directly to the benchmarking organization. Likewise, results might be returned and integrated directly within the BI or HR solution so that internal performance could easily be compared against external measures.

1.1.3 Limitations / Risks

The goal of this project is the development of a flexible, generalized schema for the exchange of metrics data. The usefulness of the schema will likely depend on the quality of templates offered by implementing organizations.

1.2 Design Requirements

1.3 Scope

The goal of the project is to develop a format that can be used flexibly to exchange a wide variety of metrics information.

1.3.1 Major Components

The design approach is to use a single schema to define the format for both Instance Reports and Summary Reports (see Section 1.4, Terminology).

1.3.2 Items Outside of Design Scope

· Developing HR measures or benchmarks. Developing measures or benchmarks for HR performance or determining what metrics are relevant to HR performance are activities outside of the scope of this project.

· Metrics reporting that does not involve interchange between organizations or systems. There are many metrics reporting processes that are not dependent on the interchange of metrics data between systems or entities. For example, there are a variety of hosted, ASP-style HR services where the service provider simply processes and compiles transactional data and presents summary metrics reports back to the customer on a web page accessible by a customer login.

· Internal transfers/compilation of source data. For any organization, the source data from which metrics are compiled are likely to reside in multiple data stores (for example, databases underlying HR systems, data warehouses, payroll systems, recruiting systems, etc). There are a growing number of business intelligence tools designed to collect and mine data from disparate sources. It is possible that the HR-XML Consortium’s Metrics Interchange standard could be useful in enabling some of these transfers of metrics information from distributed source data. However, this specification was not designed to explicitly support these types of transfers.

· Developing templates or implementation guides for specific series of metrics. This work would generally fall to specific MROs (see Section 1.4, Terminology).

1.4 Terminology

The following definitions are useful in describing the scenarios supported by the HR-XML Consortium’s Metrics Interchange specification.

1.4.1 Metrics Reporting Organization

A Metrics Reporting Organization (MRO) is an organization that produces benchmarks, reports, or other normative data from surveys or other research.

1.4.2 Source Organization

A Source Organization is the respondent to an MRO survey or otherwise is the source for data compiled and analyzed by an MRO. The source organization supplies the survey responses or Instance Reports that the MRO compiles and analyzes in preparing its reports.

1.4.3 Metrics Consumer

A Metrics Consumer is an organization that receives, uses, and applies summary metrics information supplied by an MRO or a Metrics Consolidator. A Metrics Consumer in many cases will also be a Source Organization – but this is not always the case.

1.4.4 Metrics Consolidator

A Metrics Consolidator is a role taken by a core HR system, hosted solution, HR service provider, or other software package that analyzes and organizes transactional data according to a Metrics Template to produce Instance Reports. The role of the Metrics Consolidator is to apply Metrics Templates in software and/or service offerings so that data can then be extracted according to that template.

1.4.5 Metrics Template

This is the set of definitions and guidelines that define content and the format of the metrics to be provided. For example, the Human Capital Metrics Consortium - Recruiting Efficiency Ratio consists of a formula and definitions for formula components. A template also should indicate data constraint and validation information. In other words, the template should indicate for each data component the types of data that would be valid. For example, a metric might require the return of only a positive integer, the return of one of several pre-defined enumerated values, or the return of a text string.

1.4.6 Instance Report

The Instance Report refers to uncompiled data that might be submitted in response to an MRO survey or generated as an extract from the system of a Source Organization by a Metrics Consolidator. An Instance Report would usually pertain to a single Source Organization and would have a time period associated with it.

1.4.7 Summary Report

The Summary Report refers to compiled data provided by an MRO or an HR service provider to a Metrics Consumer. A Summary Report usually would reflect the combined results of many source organizations.

2 Supported Business Processes

2.1 Metrics Interchange Business Process

2.1.1 Business Process Scenarios

There is a wide range of scenarios that can be supported by the flexible, generalized metrics interchange schema developed by the HR-XML Consortium. The diagram below depicts a typical scenario:

Example: An employer (source organization) handles its human capital management system needs through a hosted or outsourced HCM solution. In the diagram above, the HCM solution would take the role of the Metrics Consolidator.

As part of the agreement between the HCM solution provider and the employer, the HCM solution provider will provide integrated views of benchmarks produced by the MRO Company. The MRO provides the HCM provider a template, which includes the semantics and format for MRO’s benchmarks. The HCM company builds support for those benchmarks within its system. The HCM solution provides views of client data against the MRO’s benchmarks to allow for comparison, gap analysis, and performance assessment. Periodically (or conceivably on a near-real time basis), the HCM company submits instance snapshots to the MRO company.

The MRO compiles the instance results with those of other participating employers. A summary metrics report is sent back to the HCM company. The employer is then able to log into the hosted HCM solution to see the industry-compiled benchmarks against its own data. The HCM systems provider can then build rich, value-added features that allow the employer to compare, perform gap analysis, and identify opportunities and requirements for corrective action.

3 Component Schemas and Dependencies

The HR-XML Consortium’s Metrics Interchange schema includes directly or indirectly a number of re-usable component schemas. These dependencies are presented in the table below:

Role	Name
Include	IdentifierTypes.xsd
Include	Organization.xsd
Include	PhysicalLocation.xsd
Indirect	ContactMethod.xsd
Indirect	DateTimeDataTypes.xsd
Indirect	EntityIdType.xsd
Indirect	ISOUtilities.xsd
Indirect	OnlineAddress.xsd
Indirect	PersonName.xsd
Indirect	PostalAddress.xsd
Indirect	TaxonomyTypes.xsd
Indirect	TelcomNumber.xsd
Indirect	UserArea.xsd
Indirect	WorkSite.xsd
Indirect	xml.xsd (maintained by W3C.org)
Indirect	xStringPatternExtensionType.xsd

For detailed information on the above-referenced schemas, see the associated documentation (Appendix B – Related Documents).

3.1 Use Notes

3.1.1 Organization.xsd

The Metrics Interchange Schema uses entire the OrganizationType within its PrincipalRespondentOrganization component. The PrincipalRespondentOrganization component typically would be a client of an MRO (the survey or research company). OrganizationType allows for a very comprehensive description of an Organization. For new clients, the OrganizationType provides a way to pass a complete set of “set-up information,” including tax and legal identifiers, contact information, organizational structure and relationship information, worksite locations, etc. In the case of existing clients that are known and set up on the MRO’s system, the OrganizationType is sufficiently flexible so that just an OrganizationId could be transferred within PrincipalRespondentOrganization.

3.1.2 PhysicalLocation.xsd

PhysicalLocation.xsd provides comprehensive and flexible options for identifying and describing a physical location. The Metrics Interchange schema uses a single type (LocationAreaType) from the PhysicalLocation schema.

Location information is commonly used to classify or qualify other survey or metrics data. The LocationAreaType is a flexible type that can be used to pass information identifying a country, state or province, municipality, or privately defined regions, such as “South Eastern Sales Territory”. LocationAreaType is available within the Metrics Interchange schema’s GeographicalScope component.

3.2 Schema Elements Explained

3.2.1 MetricsInterchange

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ MetricsInterchange	- MetricsInterchangeType - (1/1)	HR-XML Consortium's Metrics Interchange schema. The schema provides a flexible means for the exchange of metrics data and information about the organization or person to which metrics data pertain.
/ MetricsInterchange/ ReportingPeriod	- ReportingPeriodType - S (1/1)	The period of time for the data reported.
/ MetricsInterchange/ ReportingPeriod/ StartDate	- LocalDateType - S (0/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. ]
/ MetricsInterchang e/ ReportingPeriod/ EndDate	- LocalDateType - 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.]
/ MetricsInterchang e/ ReportDescription	Name - xsd:string - S (0/1) Description - xsd:string - S (0/1)	Contains the name and description of the particular report or metrics compilation.
/ MetricsInterchange/ ReportDescription/ Name	- xsd:string - S (0/1)	A descriptive identifier within the given context. [BusinessRule(s): If referencing a person, use person name. ]
/ MetricsInterchange/ ReportDescription/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ PrincipalRespondentOrganization	Organization - [see include/import] - S (1/1) AdditionalData - MetricsAdditionalDataType - S (0/*)	Information about the organization that is providing the data. [BusinessRule(s): A PrincipalRespondentOrganization would typically be the client of the organization receiving the data or otherwise a respondent to a survey or request for data. The PrincipalRespondentOrganization may or may not be the organization to which the metrics pertain. ]
/ MetricsInterchange/ PrincipalRespondentOrganization/ AdditionalData	- MetricsAdditionalDataType - S (0/*)	Allows trading partner specific structured information or extensions.
/ MetricsInterchange/ ReportedMetrics	- ReportedMetricsType - S (0/*)	Contains metrics data with respect to one or more organizations or persons.

3.2.2 ReportedOrganization

/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization	OrganizationName - xsd:string - S (0/1) OrganizationId - EntityIdType - S (0/1) RelatedReportedOrganization - RelatedReportedOrganizationType - S (0/1) IsRespondentOrganization - xsd:string - C (1/1) RelationshipToRespondent - xsd:string - C (1/1) ContactInfo - OrganizationContactType - S (0/) OrganizationDescriptors - xsd:string - S (1/1) ReportingData - ReportingDataType - S (1/)	An organization about which data is reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationName	- xsd:string - S (0/1)	The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationId	- EntityIdType - S (0/1)	Unique identifier for the organization. It may be an internal identifier assigned by the sender.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ RelatedReportedOrganization	- RelatedReportedOrganizationType - S (0/1)	Contains information identifying another reported organization that is related (For example, a parent, subsidiary, or division of a reported organization). [Synonym(s): RelatedOrganization, RelatedOrganizationlUnit ] [Example(s): ACME is the responsible organization; Oxford is related to ACME; Maddock is related to Oxford. This field could be Oxford or Maddock based on the transaction. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ RelatedReportedOrganization/ OrganizationName	- xsd:string - S (0/1)	The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ RelatedReportedOrganization/ OrganizationId	- EntityIdType - S (0/1)	Unique identifier for the organization. It may be an internal identifier assigned by the sender.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ IsRespondentOrganization	- xsd:string - C (1/1)	An indicator showing that the reported organization is identical to the responsible organization. [BusinessRule(s): The Metrics Interchange schema provides a choice between IsRespondentOrganization (with a fixed value of "true") and RelationshipToRespondent. The latter is used to describe the relationship of the ReportedOrganization to the PrincipalRespondentOrganization in cases where the two are not identical. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ RelationshipToRespondent	- xsd:string - C (1/1)	Specifies a relationship between a ReportedOrganization and the PrincipalRespondent organization where those organizations are not the same.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ContactInfo	- OrganizationContactType - S (0/*)	Contains information to contact a person or entity. [Example(s): Person Name, Organization Name, Contact Method ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors	GeographicalScope - [complexType] - S (0/1) OrganizationSize - xsd:string - S (0/1) IndustryCode - [see include/import] - S (0/) DataElement - DataElementType - S (0/)	Contains a contextual subset of descriptive information about an organization.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ GeographicalScope	- LocationAreaType - S (0/1)	Identifies the relevant geographical area.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ OrganizationSize	Headcount - xsd:string - S (0/1) FiscalSize - xsd:string - S (0/*)	Contains information about the size of the organization in terms of total number of employees or in terms of a fiscal measure, such as annual revenue.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ OrganizationSize/ Headcount	- xsd:string - S (0/1)	The number of persons working on a full or part-time basis in some capacity by a legally operating organization or enterprise. [BusinessRule(s): The inclusion of contract workers, volunteers, interns and alternative arrangements for workers is determined by trading partner agreement. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ OrganizationSize/ FiscalSize	xsd:extension base: xsd:string type - xsd:string -	A financial measure of the size of an organization. [BusinessRule(s): A type attribute is available to specify the particular financial measure used. ] [Example(s): For example, "Annual Revenue," "Total Assets," "Net Revenue," etc. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ OrganizationSize/ FiscalSize/ type	- xsd:string -	Further defines the associated element in the context provided. [BusinessRule(s): Additional values are permitted if preceded by an x: ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ DataElement	- DataElementType - S (0/*)	A flexible structure for the capture of a specific metric, demographic value, organizational descriptor, or other reported value. [BusinessRule(s): Functions much like a name-value pair, with the name of the particular metric, demographic, or descriptor going on the "type" attribute of data element and the value going within the appropriate value field. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ DataElement/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ DataElement/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ DataElement/ MonetaryValue	- MonetaryValueType - C (1/1)	Contains a monetary value.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors/ DataElement/ DataValue	- xsd:string - C (1/1)	A value or label of the associated element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ OrganizationDescriptors / DataElement/ DataElementSubType	- DataElementType - S (0/*)	A recursive structure that allows for multi-value, complex metrics or other data to be expressed.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData	- ReportingDataType - S (1/*)	Specific data required for reporting purposes.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ ReportingCategory	- xsd:string - S (0/1)	A description of the category of data reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ ReportingPeriod	- ReportingPeriodType - S (0/1)	The period of time for the data reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ ReportingPeriod/ StartDate	- LocalDateType - S (0/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. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ ReportingPeriod/ EndDate	- LocalDateType - 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.]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement	- DataElementType - S (1/*)	A flexible structure for the capture of a specific metric, demographic value, organizational descriptor, or other reported value. [BusinessRule(s): Functions much like a name-value pair, with the name of the particular metric, demographic, or descriptor going on the "type" attribute of data element and the value going within the appropriate value field. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ MonetaryValue	- MonetaryValueType - C (1/1)	Contains a monetary value.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataValue	- xsd:string - C (1/1)	A value or label of the associated element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataElementSubType	- DataElementType - S (0/*)	A recursive structure that allows for multi-value, complex metrics or other data to be expressed.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataElementSubType/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataElementSubType/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataElementSubType/ MonetaryValue	- MonetaryValueType - C (1/1)	Contains a monetary value.
/ MetricsInterchange/ ReportedMetrics/ ReportedOrganization/ ReportingData/ DataElement/ DataElementSubType/ DataValue	- xsd:string - C (1/1)	A value or label of the associated element.

3.2.3 ReportedPerson

/ MetricsInterchange/ ReportedMetrics/ ReportedPerson	ReportedPersonDetail - [complexType] - S (0/1) ReportingData - ReportingDataType - S (1/*)	A person about whom data is reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail	PersonName - [see include/import] - S (0/1) PersonId - EntityIdType - S (0/1) ContactInfo - ContactMethodType - S (0/) DataElement - DataElementType - S (0/)	Contains classifying information to identify or describe a person.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ PersonId	- EntityIdType - S (0/1)	A unique identifier for a person.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ ContactInfo	- ContactMethodType - S (0/*)	Contains information to contact a person or entity. [Example(s): Person Name, Organization Name, Contact Method ]
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement	- DataElementType - S (0/*)	A flexible structure for the capture of a specific metric, demographic value, organizational descriptor, or other reported value. [BusinessRule(s): Functions much like a name-value pair, with the name of the particular metric, demographic, or descriptor going on the "type" attribute of data element and the value going within the appropriate value field. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ MonetaryValue	- MonetaryValueType - C (1/1)	Contains a monetary value.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataValue	- xsd:string - C (1/1)	A value or label of the associated element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataElementSubType	- DataElementType - S (0/*)	A recursive structure that allows for multi-value, complex metrics or other data to be expressed.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataElementSubType/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataElementSubType/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataElementSubType/ MonetaryValue	- MonetaryValueType - C (1/1)	Contains a monetary value.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportedPersonDetail/ DataElement/ DataElementSubType/ DataValue	- xsd:string - C (1/1)	A value or label of the associated element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData	- ReportingDataType - S (1/*)	Specific data required for reporting purposes. [Synonym(s): CustomerReportingRequirements ] [BusinessRule(s): Definition of the pairs is done via agreement between business partners. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ ReportingCategory	- xsd:string - S (0/1)	A description of the category of data reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ ReportingPeriod	- ReportingPeriodType - S (0/1)	The period of time for the data reported.
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ ReportingPeriod/ StartDate	- LocalDateType - S (0/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. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ ReportingPeriod/ EndDate	- LocalDateType - 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. ]
/ MetricsInterchange/ ReportedMetrics/ ReportedPerson/ ReportingData/ DataElement	- DataElementType - S (1/*)	A flexible structure for the capture of a specific metric, demographic value, organizational descriptor, or other reported value. [BusinessRule(s): Functions much like a name-value pair, with the name of the particular metric, demographic, or descriptor going on the "type" attribute of data element and the value going within the appropriate value field. ]

3.2.4 DataElement

3.2.5 Global Types

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [DataElementType]	type - xsd:string - Id - EntityIdType - S (0/1) Description - xsd:string - S (0/1) MonetaryValue - MonetaryValueType - C (1/1) DataValue - xsd:string - C (1/1) DataElementSubType - DataElementType - S (0/*)	Globally scoped data type. See element or attribute declaration for definition.
/ [DataElementType] / type	- xsd:string -	Further defines the associated element in the context provided. [BusinessRule(s): Additional values are permitted if preceded by an x: ]
/ [MetricsAdditionalDataType]	xsd:extension base: xsd:string type - xsd:string -	Globally scoped data type. See element or attribute declaration for definition.
/ [MetricsAdditionalDataType] / type	- xsd:string -	Further defines the associated element in the context provided. [BusinessRule(s): Additional values are permitted if preceded by an x: ]
/ [MetricsInterchangeType]	xml:lang - - ReportingPeriod - ReportingPeriodType - S (1/1) ReportDescription - [complexType] - S (1/1) PrincipalRespondentOrganization - [complexType] - S (1/1) ReportedMetrics - ReportedMetricsType - S (0/*)	Globally scoped data type. See element or attribute declaration for definition.
/ [MonetaryValueType]	xsd:extension base: xsd:decimal currencyCode - CurrencyCodeType -	Globally scoped data type. See element or attribute declaration for definition.
/ [RelatedReportedOrganization Type]	relationship - OrganizationRelationshipType - OrganizationName - xsd:string - S (0/1) OrganizationId - EntityIdType - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [RelatedReportedOrganizationType] / relationship	- OrganizationRelationshipType -	Describes the nature of the relationship or connection between two elements or entities. [BusinessRule(s): Context 1: Between two organizations (parent company, subsidiary), Context 2: Between organizational units (parent, child, sibling) Context 3: Between a contact person and the context in which they are listed (Supplier contact: agent, Organization contact ] [Example(s): Subsidiary, Parent Company ]
/ [ReportedMetricsType]	ReportedOrganization - xsd:string - C (1/) ReportedPerson - [complexType] - C (1/)	Globally scoped data type. See element or attribute declaration for definition.
/ [ReportingDataType]	ReportingCategory - xsd:string - S (0/1) Description - xsd:string - S (0/1) ReportingPeriod - ReportingPeriodType - S (0/1) DataElement - DataElementType - S (1/*)	Globally scoped data type. See element or attribute declaration for definition.
/ [ReportingPeriodType]	StartDate - LocalDateType - S (0/1) EndDate - LocalDateType - S (0/1)	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. Implementers should consult with competent legal counsel on applicable privacy laws.

For information on protecting personal data, general references include: Organization for Economic Cooperation and Development (OECD) Privacy Guidelines (1980); 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-01-19	Draft submitted for workgroup approval.
2004-01-23	Made minor edits based on workgroup review and submitted to CPO/TSC review.
2004-04-28	Made edits recommended by TSC/CPO: · GeographicalScope to be of type LocationAreaType and remove extra Area layer. · Change RelationToRespondent to RelationshipToRespondent. · Clarified includes and use of types from Organization.xsd and PhysicalLocation. · Clarified “Summary” and “Instance” reports within Terminology. · Moved Global Element PrincipalRespondentOrganization up in the schema to conform to the style of keeping elements and types from being intermingled within a schema.
2004-07-06	An optional attribute xml:lang was added to the root element.
2006-02-28	Approved by Membership

6 Appendix B – Related Documents

Reference	Link
Contact Method	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/ContactMethod.html
Date/Time Data Types	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/DateTimeDataTypes.html
Identifier Types	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/IdentifierTypes.html
Organization	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Organization.html
Person Name	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/PersonName.html
Physical Location	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/PhysicalLocation.html
Postal Address	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/PostalAddress.html

7 Appendix C – Reference Examples

7.1 Template Requirements

The HR-XML Consortium’s Metrics Interchange specification does not specify the exact format of metrics templates. The template is the responsibility of the Metrics Reporting Organization to prepare. The template generally would consist of:

Definitions, formulas, and guidelines that define content and the format of the metrics to be provided;
The specification of time periods for the collection or the reporting of data;
Examples of the XML Instance Reports to be submitted by the Metrics Consolidator and examples of the Summary Report to be returned by the MRO; and
Transport and integration details. For instance, if the transfer of the data was accomplished as a web service, the integration details might include a formal service description using Web Services Description Language (WSDL).

The following sections include illustrative examples of what a template might look like.

7.1.1 Example 1: Template To Implement Human Capital Metrics Consortium Benchmark Survey

The example template presented below illustrates how the HR-XML Consortium’s Metrics Interchange specification might be useful in automating the acquisition data for the Human Capital Metrics Consortiums Standard Benchmark Survey. The template describes how data required for this survey instrument should be formatted using the HR-XML Consortium’s Metrics Interchange Specification.

Id refers to the survey question identifier assigned by HCMC

Field Name refers to the question or name of the question or field in the survey instrument.

Data Type refers to the data type or other type of constraints enforced by the survey. This is a compatible, but not necessarily the same data type enforced by the HR-XML Consortium metrics interchange schema. For instance, there are places where the schema might require only a string, but the survey instrument would require one of several pre-defined enumerations.

Required / Optional indicates whether the element is required or optional in the survey instrument.

Description / Markup Instructions includes definitions and instructions for the interface developer. Note that more detailed metrics definitions are contained in a separate document.

Schema contains the node within the HR-XML Consortium’s Metrics Interchange schema where the related data would be captured.

Id	Field Name	Data Type / Constraints	Required /Optional	Description / Markup Instructions	Schema
	Reporting Period Begin	Fixed	Required	Fixed value assigned by HCMC: 2999-01-01	MetricsInterchange / ReportingPeriod / StartDate
	Reporting Period End	Fixed	Required	Fixed value assigned by HCMC: 2999-21-31	MetricsInterchange / ReportingPeriod / EndDate
	Report Name	Fixed	Required	Fixed value assigned by HCMC: 200_ Recruiting Metrics and Performance Benchmark	MetricsInterchange / ReportDescription / Name
	Respondent Organization Name	String	Required	The name of the respondent organization.	PrincipalRespondentOrganization / Organization / OrganizationName
	Contact Given Name	String	Required	The given name of the individual to contact regarding report	PrincipalRespondentOrganization / Organization / ContactName / GivenName
	Contact Family Name	String	Required	The family name of the individual to contact regarding report	PrincipalRespondentOrganization / Organization / ContactName / FamilyName
14	Country	2 character string	Required	A two-letter code prescribed by ISO 3166-1, Codes for the representation of names of countries and their subdivisions.	ReportedOrganization / OrganizationDescriptors / GeographicalScope / Description
13	State / Province	string	Required	A two-letter code for the state or province. For instance in the US: AK; AL; AR; AS; AZ; CA; CO; CT; DC; DE; FL; FM; GA; GU; HI; IA; ID; IL; IN; KS; KY; LA; MA; MD; ME; MH; MI; MN; MO; MP; MS; MT; NC; ND; NE; NH; NJ; NM; NV; NY; OH; OK; OR; PA; PR; PW; RI; SC; SD; TN; TX; UT; VA; VI; VT; WA; WI; WV; WY. In Canada: AB; BC; MB; NB; NF; NS; NT; ON; PE; QC; SK; YN	ReportedOrganization / OrganizationDescriptors / GeographicalScope / Area / Description
10	Total Employees in Organization	enumeration	required	One of the following six enumerations: Less than 100 100 - 999 1,000 - 4,999 5,000 - 9,999 10,000 - 49,999 50,000+	ReportedOrganization / OrganizationDescriptors / OrganizationSize / Headcount
7	Referred By:	string	Optional	Name of a referring organization.	ReportedOrganization / OrganizationDescriptors / DataElement
9	Reporting for	enumeration	required	One of the following four enumerations: Team Department Enterprise Parent	ReportedOrganization / OrganizationDescriptors / DataElement
11	Organization Category	enumeration	Optional / Item 12, “Organization Category (Other)” must be provided if item 11 is not provided.	One of the enumerated organization categories below Aerospace and Defense Agriculture, Fishing Airlines Architecture, Engineering Arts, Entertainment, Recreation Banks, Commercial and Savings Beverages Building Materials, Glass Chemicals Computer & Data Services Computer Software Computers, Office Equipment Construction Consulting Diversified Financials Diversified Outsourcing Services Education, Colleges and Universities Education, Other Services Education, Primary and Secondary Electrical Equipment Electronics Energy Financial Services Food Food and Drug Stores Food Consumer Products Food Production Food Services Forest and Paper Products Forestry/Mining General Merchandisers Government, Local Government, National, Multi-National Government, Province or State Health Care, Hospitals Health Care, Long Term Care Health Care, Nursing and Specialty Services Health Products and Services Hospitality Household and Personal Products Independent Consultant Industrial and Farm Equipment Insurance Library Manufacturing (Durable Goods) Manufacturing (Non-Durable Goods) Media, Internet, Radio, Publishing, Television Metals and Mining Motor Vehicles and Parts Network and Other Communications Equipment Oil and Gas Oil and Gas Equipment, Services Outsourcing Pharmaceutical and Biotech Real Estate Retail Scientific, Photo, Control Equipment Securities Semiconductors and Other Electronic Components Services, Non-Profit Services, Profit Specialty Retailers Telecommunications Tobacco Trading Transportation, Package and Freight Transportation, Passenger Services Transportation, Rail, Ship, Trucking Utilities, Electric and Gas Wholesale	ReportedOrganization / OrganizationDescriptors / DataElement
12	Organization Category (Other)	string	Optional / Either item 11, “Organization Category” or item 12, “Organization Category (Other)” must be provided.	A user-defined string specified where enumerated categories are not sufficient to categorize the reported organization.	ReportedOrganization / OrganizationDescriptors / DataElement
16.1	Positions filled internally: Jan-Dec 200_	Integer	Optional	Number of positions filled internally by current employees.	ReportedOrganization / ReportingData / DataElement / DataValue
17.11	External New Hires: Total nonexempt: Jan-Dec 200_	Integer	(17.11 and 17.12) OR 17.13 are required.	Number of nonexempt (i.e., over-time eligible) external new hires.	ReportedOrganization / ReportingData / DataElement / DataValue
17.12	External New Hires: Total exempt: Jan-Dec 200_	Integer	(17.11 and 17.12) OR 17.13 are required.	Number of exempt external new hires.	ReportedOrganization / ReportingData / DataElement / DataValue
17.13	External New Hires: Total hires: Jan-Dec 200_	Integer	(17.11 and 17.12) OR 17.13 are required.	Number of external new hires.	ReportedOrganization / ReportingData / DataElement / DataValue
18.11	Compensation Recruited: Average New Hire: Jan-Dec 200_	Decimal	18.11 OR 18.12 is required.	Average annual starting compensation of external positions filled by staffing operations. For seasonal and part-time hires, this should be the total compensation they would be expected to earn in one year.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
18.12	Compensation Required: Total Compensation: Jan-Dec 200_	Decimal	18.11 OR 18.12 is required.	The sum of the base annual starting compensation of all external positions filled by staffing operations. For seasonal and part-time hires, this should be the total compensation they would be expected to earn in one year.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
19.11	Recruiting Costs: Internal: Jan-Dec 200_	Decimal	(19.11 and 19.12) OR 19:13 are required.	These are your fixed or "overhead" expenses, comprising everything from recruiter compensation and benefits to office and technology expenses. These operating expenses are defined as virtually all costs required to maintain a staffing operation.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
19.12	Recruiting Costs: External: Jan-Dec 200_	Decimal	(19.11 and 19.12) OR 19:13 are required.	These expenses are also referred to as sourcing costs and include advertising and agency and search fees, as well the costs associated with Internet postings. External recruiting costs include virtually all expenses involved in identifying and recruiting candidates. Sourcing costs are usually incurred for a specific position or positions, but they can also include general initiatives such as employer branding.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
19.13	Recruiting Costs: Total Costs: Jan-Dec 200_	Decimal	(19.11 and 19.12) OR 19:13 are required.	Total of internal and external recruiting costs.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
20.1	Cost-Per-Hire: Jan-Dec 200_	Decimal	Optional	Total recruiting costs divided by total positions recruited.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
21.1	Recruiting Efficiency Index: Jan-Dec 200_	Decimal	Optional	The Human Capital Metrics Consortium Recruiting Efficiency Ratio takes into account differences of geography, industry and job level by shifting its focus from numbers of recruits to compensation of recruits. The equation is simple: Total Recruiting Costs divided by Total Compensation Recruited.	ReportedOrganization / ReportingData / DataElement / DataValue
22.1	Signing Bonuses: Jan-Dec 200_	Decimal	Optional	Total amount of signing bonuses.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
23.1	Travel, Relocation, and Visa Expenses: Jan-Dec 200_	Decimal	Optional	Total amount of travel, relocation, and visa hiring expenses.	ReportedOrganization / ReportingData / DataElement / MonetaryValue
25.1	Average Time to Start: Jan-Dec 200_	Integer	Optional	Average time to start.	ReportedOrganization / ReportingData / DataElement / MonetaryValue

7.1.2 Example 1: Instance Implementing HCMC Template

An XML instance implementing the template above can be found at this location:

http://ns.hr-xml.org/2_5/HR-XML-2_5/Metrics/ExampleOfOrganizationMetrics.xml

7.1.3 Example 2: Template To Implement Individual Performance Measures To Validate an Assessment

Overview

The example below illustrates how the HR-XML Consortium’s Metrics Interchange specification might be useful in automating the acquisition and transfer of individual performance data by an assessment vendor.

Businesses rely on assessments to measure numerous individual and organizational characteristics. The assessment data of interest to businesses can be granular (responses to a single survey, test, or assessment instrument) or a statistical analysis of aggregated results. Today, the acquisition and transfer of assessment data typically is a lengthy and manual process.

In the example below, a vendor of assessment services wants to acquire data related to the performance of the workers in a call center who were the subjects of pre-employment assessments by the vendor. By obtaining and analyzing the performance data, the vendor can determine and demonstrate to the client that its assessments are valid predictors of on-the-job performance. Before automation the process would consist of the following steps:

1) Applicants undergo a pre-employment assessment

2) On a monthly basis reports are generated that report applicant assessment results (Test Score Data)

3) Assessment vendor receives a file from the client containing employee call center performance data (typically as a spreadsheet or other proprietary file format).

4) The assessment results and metrics data files are combined into a single report using a key field such as the SSN. (Combined Data)

5) Statistical analysis is performed on the combined data file to produce a validation report containing graphs derived from the analysis. (Graphs)

Having an agreed upon format for receiving metrics data makes it easier to automate the receipt of metrics data by the assessment vendor from the client. Instead of using a spreadsheet or proprietary format to receive call center performance data (step 3), a web service using HR-XML Metrics Interchange schema might be used to acquire the required performance data directly from the employer. The template below illustrates how the HR-XML Consortium Metrics schema may be useful in acquiring metrics data.

This is one possible scenario. This particular template pertains only to metrics for individual employee job performance. Other common scenarios related to assessments might require the use of both group-level and individual metrics.

Example Template

Id refers to the survey question identifier assigned by the assessment company

Field Name refers to the question or name of the question or field in the survey instrument.

Required / Optional indicates whether the element is required or optional in the survey instrument.

Description / Markup Instructions includes definitions and instructions for the interface developer. Note that more detailed metrics definitions are contained in a separate document.

Schema contains the node within the HR-XML Consortium’s Metrics Interchange schema where the related data would be captured.

Id	Field Name	Data Type / Constraints	Required /Optional	Description / Markup Instructions	Schema
	Metric Month (Begin Date)	Local Date: YYYY-MM-DD	Required	Beginning date of month for which performance data is reported.	MetricsInterchange / ReportingPeriod / StartDate
	Metric Month (End Date)	Local Date: YYYY-MM-DD	Required	End date of month for which performance data is reported.	MetricsInterchange / ReportingPeriod / EndDate
	Report Name	Fixed String	Required	Value is “Post-Assessment Client Solution.”	ConsolidatedMetrics / ReportDescription / Name
	Report Description	String	Optional	Value is “Monthly report (June 2003) from client showing applicant performance metrics. This report is used in validating assessment instrument as predictor of on-the-job performance.”	ConsolidatedMetrics / ReportDescription / Description
	Client Id	String	Required	A valid client Id.	ConsolidatedMetrics / PrincipalRespondentOrganization / Organization / OrganizationId / IdValue
	IdOwner	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ConsolidatedMetrics / PrincipalRespondentOrganization / Organization / OrganizationId / IdValue @ idOwner
	First Name	String	Required	Given name.	ReportedMetrics / ReportedPerson / PersonDemographicData / PersonName / GivenName
	Last Name	String	Required	Family name.	ReportedMetrics / ReportedPerson / PersonDemographicData / PersonName / FamilyName
	SSN	String	Required	Fixed value: “SSN”. Attribute identifying that the PersonId is a social security number	ReportedMetrics / ReportedPerson / PersonDemographicData PersonId @ idOwner
	SSN Value	A valid social security number: XXX-XX-XXXX	Required	The assessment subject’s Social Security Number.	ReportedMetrics / ReportedPerson / PersonDemographicData PersonId / IdValue
1.1	Identifier for “Division” Data Element	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id / IdValue
	Identifier Owner for “Division” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id @ IdOwner
	“Division” Data Element Description	String	Optional	Fixed value of “Division”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Description
	“Division” Data Element Value	String	Required	Valid values include: NBP, P4F, P4J, P4P, P4R, P4W, P4X, P4Y, P5A, P5B, P5C, P5D, P5J, P5K, P5L, P5M, P5U, P5W, P5X, P6A, PX5, PYA, PYB, PYC, PYG, PYI, PYJ, PYM, PYP, PYQ, PYT, Q1N, Q1P, Q1Q, Q1R, Q1T, Q1U, Q1V, Q1W, Q1Y, Q1Z, Q2A, Q2B, Q2D, Q2E, Q2N, Q2Q, Q2R, Q2T, Q3Q, Q3R, Q3T, Q3W, Q3X, Q4B, Q4C, Q4E, Q4F, Q4G, Q4I, Q4J, Q4K, Q4L, Q4P, Q4Q, Q4R, Q5I, Q5J, Q5L, Q5M, Q5P, Q5R, Q5T, Q5U, Q5V, Q5W, Q5X, Q5Y, Q5Z, Q6A, Q6B, Q7G, Q7H, QB1, QB3, QB5, QB6, QB7, QB9, QBB, QBC, QBD, QBE, QBF, QBI, QBK, QBM, QBX, QBY, QC1, QC2, QC4, QC5, QC8, QCA, QCU, QCV, QCW, QDA, QDB, QDC, QDD, QDE, QEU, QH4, QH5, QH6, QH7, QHZ, QIA, QIC, QID, QIE, QIF, QII, QIM, QIN, QIP, QIQ, QIS, QIX, QL3, QL6, QL8, QL9, QLI, QLK, QLM, QLN, QLZ, QMB, QMC, QNR, QR6, QR7, QR8, QS1, QS2, QS4, QS5, QS6, QS7, QS8, QS9, QSA, QSB, QSC, QSD, QSE, QSG, QSI, QSJ, QSN, QSQ, QSR, QSS, QSU, QSW, QSX, QSZ, QT9, QTR, QTT, QTU, QTX, QTY, QUB, QUC, QUD, QUF, QUH, QUJ, QUK, QUL, QUM, QUN, QUW, QUX, QVH, R5P, R5Q, R5T, R5U, R5X, R5Y, R5Z, R6A, RH1, RH2, RH3, RH4, RH5, RH9, RIB, RJ2, RJ3, RJ8, RJ9, RJU, RJW, RJY, RJZ, RKD, RKE, RKF, RKG, RKH, RKK, RKL, RKM, RKN, RLL, RLM, RLN, RLP, RLQ, RLR, and RLS.	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / DataValue
1.2	Identifier for “Hire Date” Data Element	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id / IdValue
	Identifier Owner for “Hire Date” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id @ IdOwner
	“Hire Date” Data Element Description	String	Optional	Fixed value of “Hire Date”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Description
	“Hire Date” Data Element Value	Local Date: YYYY-MM-DD	Required	The employee’s hire date.	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / DataValue
1.3	Identifier for “State” Data Element	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id / IdValue
	Identifier Owner for “State” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Id @ IdOwner
	“State” Data Element Description	String	Optional	Fixed value of “State”	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / Description
	“State” Data Element Value	String	Required	A two-letter code for the state or province in which the employee works. For instance in the US: AK; AL; AR; AS; AZ; CA; CO; CT; DC; DE; FL; FM; GA; GU; HI; IA; ID; IL; IN; KS; KY; LA; MA; MD; ME; MH; MI; MN; MO; MP; MS; MT; NC; ND; NE; NH; NJ; NM; NV; NY; OH; OK; OR; PA; PR; PW; RI; SC; SD; TN; TX; UT; VA; VI; VT; WA; WI; WV; WY. In Canada: AB; BC; MB; NB; NF; NS; NT; ON; PE; QC; SK; YN	ReportedMetrics / ReportedPerson / PersonDemographicData / DataElement / DataValue
2.1	Identifier for “Promises to Pay per call”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Promises to Pay per call” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Promises to Pay per call” Data Element Description	String	Optional	Fixed value of “Promises to Pay per call”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Promises to Pay per call” Data Element Value	Decimal	Required	Percentage of calls handled by the employee in which there were promises to pay.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue
2.2	Identifier for “Promises kept per call”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Promises to Pay per call” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Promises to Pay per call” Data Element Description	String	Optional	Fixed value of “Promises kept per call”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Promises kept per call” Data Element Value	Decimal	Required	Percentage of promises kept per call.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue
2.3	Identifier for “Dollars collected Per operating hour”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Dollars collected Per operating hour” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Dollars collected Per operating hour” Data Element Description	String	Optional	Fixed value of “Dollars collected Per operating hour”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Dollars collected Per operating hour” Data Element Value	Decimal	Required	Percentage of promises kept per call.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue
2.4	Identifier for “Collection per person percentage”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Collection per person percentage” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Collection per person percentage” Data Element Description	String	Optional	Fixed value of “Collection per person percentage”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Collection per person percentage” Data Element Value	Decimal	Required	Collection per person percentage.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue
2.5	Identifier for “Fee waived percentage.”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Fee waived percentage” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Fee waived percentage” Data Element Description	String	Optional	Fixed value of “Fee waived percentage”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Fee waived percentage” Data Element Value	Decimal	Required	Fee waived percentage.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue
2.6	Identifier for “Utilization percentage.”	Decimal	Required	Assessment Vendor identifier for the data element.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id / IdValue
	Identifier Owner for “Fee waived percentage” Data Element	String	Optional	Fixed value of “Acme Assessment Co. Ltd. Inc.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Id @ idOwner
	“Fee waived percentage” Data Element Description	String	Optional	Fixed value of “Fee waived percentage.”	ReportedMetrics / ReportedPerson / ReportingData / DataElement / Description
	“Fee waived percentage” Data Element Value	Decimal	Required	Fee waived percentage.	ReportedMetrics / ReportedPerson / ReportingData / DataElement / DataValue

7.1.4 Example 2: Instance To Implement Individual Performance Measures To Validate an Assessment

An XML instance implementing the template above can be found at this location:

http://ns.hr-xml.org/2_5/HR-XML-2_5/Metrics/ExampleOfIndividualMetrics.xml

Complex Metrics Example

In the MetricsInterchange schema, DataElement contains a DataElementSubType, which is a recursive structure that allows multi-value or complex metrics. The example below illustrates how it can be use.

The metric in this example is “time to start”. Time to start is calculated as “total days to start” divided by “total hires.” In the example below, “total days” and “total hires” are broken out using DataElement. These numbers are broken down further by internal and external hires using the DataElementSubType.

<?xml version="1.0" encoding="UTF-8"?>

</ReportingPeriod>

<Name>Time To Start - Total</Name>

<Description>Show the average number of calendar days between the receipt of a requisition and the data a new hire reports for work</Description>

</ReportDescription>

<OrganizationName>Acme Corporation</OrganizationName>

</Organization>

</PrincipalRespondentOrganization>

<ReportingCategory>Staffing and Hiring</ReportingCategory>

</ReportingPeriod>

<Description>Total number of employees hired or internal transfers within the period</Description>

<Description>Total number of external hires</Description>

</DataElementSubType>

<Description>Total number of internal hires</Description>

</DataElementSubType>

</DataElement>

<Description>Total number of days between job posting approval and date employees start</Description>

<Description>Total number of days to start for external hires</Description>

</DataElementSubType>

<Description>Total number of days to start for internal hires</Description>

</DataElementSubType>

</DataElement>

</ReportingData>

</ReportedOrganization>

</ReportedMetrics>

</MetricsInterchange>