New Member Orientation Dallas, October 2003 Kim Bartkus

1. New Member OrientationDallas, October 2003 Kim Bartkus

2. Introduction • The HR Problem Domain • What is XML? • What is HR-XML? • Project Methodology • Tools of the Trade • Accomplishments • Cross Process Objects • Continuing Work

3. Imagine going shopping for a toaster… • You find the one meets all your requirements. • Powerful • Easy-to-clean • Guaranteed to never burn you toast

4. However, when you get it home, you find that there is one problem... This terrific toaster doesn’t have a standard electrical plug, and you’re not really sure what type of voltage it requires.

5. What is XML? • eXtensible Markup Languageis a language for creating “markup” languages or “vocabularies”. • Looks like HTML, but XML allows the definition of custom tags to describe information explicitly. • XML is a recommendation issued by the World Wide Web Consortium, February 1998

6. How XML Works… Program Asks for Data Returns XML defining what is being sent: <Employee> <First>John</First> <Last>Smith</Last> </Employee> First: John Last: Smith An XML document defines what the data is, not how it is displayed. Programs “parse” this XML data.

7. What is HR-XML? • Independent, non-profit corporation (Dec 1999) • Define standard vocabularies to streamline HR data interchange • Open to vendors, consultants, standards bodies, employers and other end-users, and individuals • 100+ organizational members • International – Mission to produce specifications that are relevant and useful across many country contexts.

8. What Does HR-XML Deliver? Transport (e.g. HTTP, FTP, SMTP) Protocol (e.g. XP, SOAP) HR-XML focuses on specifications for message payload, but aims to provide context and guidance to enable the entire exchange. Framework (e.g. ebXML, BizTalk) Payload (e.g. Enrollment) Payload Includes the information necessary to complete an interaction within a businessprocess.

9. Business SteeringCommittee (BSC) Technical Steering Committee (TSC) OrganizationalStructure Board of Directors Cross Process Object (CPO) Payroll Benefits Enrollment Stock Recruiting & Staffing Screening Time Reporting SIDES Other Projects Data Dictionary Committee

10. Project Team • Team lead is responsible for determining the schedule and facilitating the project. • Secretary records all decisions and posts minutes to team web page. • Schema editor makes schema changes and provides graphical illustrations. • Document editor responsible for consolidating documentation. • Domain experts share knowledge of the business process, enabling team to build a comprehensive standard.

11. Project Methodology

12. Model a Business Process

13. Tools of the Trade

14. Create or Update Your Personal Profile • Go to Profile Tool on main members page • Select your name from the company participant list • Enter your contact information • Sign up for workgroup e-mail lists

15. Document Management • TIBCO’s “XMLCanon” repository to store all documents in a central location. • Administrator gives access to team members based on their roles, following the consortium security procedures. • Files checked in and out of repository, ensuring most current files are available to team members. • All members have access to view and download files.

16. Schema Development • Schema editors free to use most any XML editor. • Typically, XML Spy and Turbo XML used. • All schemas validated against: • XML Spy, TurboXML, MSXML, Stylus Studio, Oracle, and Xerces XML tools

17. A square line connector indicates that the elements must occur in the specified sequence. • An angled line connector specifies that only one of the elements may exist. Graphical Notation • Elements displayed as rectangles, attributes as round-edged rectangles. • Lines connecting the elements represent the relationships between elements.

18. Ind icator Definition Related Example None Element must appear once and only once. Required_ One_Occurrence + Element must appear one or more times. Element required to appear at least once, but multiple consecutive occurrences may be present. Required_ Multiple_Occurrence ? Element may appear zero or one time. Element optional, but only allowed to appear once. Optional_ One_Occurrence * Element may appear zero or more times. Element may appear as many times consecutively as needed, or even zero times. Optional_ One_Occurrence Cardinality

19. Approved Workgroup Standards • Staffing Exchange Protocol (version 1) • Time/Expense Reporting • Time Card Configuration • Benefits Enrollment (version 1, 2) • Payroll Defined Contributions • Payroll Instructions • Staffing Industry Data Exchange Standard (SIDES) • Competencies • Background Check • Resume (version 2) • Employee Stock Plan Interface

20. Competencies Contact Method Date Time Data Types Education History Effective Dating Employment History Identifier Types ISO Utilities Job & Position Header Military History Organization Person Name Postal Address Schema Extension Taxonomy Types Work Site Approved CPO Standards

21. Standard: Person Name • Most commonly used in component in HR transactions • Design Issues • Multiple last names • Different names for different situations (stage names, aliases, etc.) • Initials • Hyphenated names • People with a single name (e.g. Prince, Madonna) • Maiden names • Legal names vs. informal names • Prefix and Affix (aristocratic titles, forms of address, qualifications, generations)

22. Schema

23. Netherlands Mevr. Maria de Wit <PersonName> <GivenName>Maria</GivenName> <FamilyName prefix=“de”>Wit</FamilyName> <Affix type=”formOfAddress”>Mevr.</Affix> </PersonName> <PersonName> <FormattedName>Mevr. Maria de Wit</FormattedName> </PersonName>

24. Mexico Sr. Fernando Martínez Urrutia <PersonName> <GivenName>Fernando</GivenName> <FamilyName>Martinez Urrutia</FamilyName> <Affix type=”formOfAddress”>Sr.</Affix> </PersonName> <PersonName> <GivenName>Fernando</GivenName> <FamilyName primary=”false”>Martinez</FamilyName> <FamilyName primary=”true”>Urrutia</FamilyName> <Affix type=”formOfAddress”>Sr.</Affix> </PersonName>

25. Standard: Competencies • Definition: A specific, identifiable, and measurable knowledge, skill, ability and/or other deployment-related characteristic (e.g. attitude, behavior, physical ability) which a human resource may possess and which is necessary for the performance of an activity within a specific business context. • Flexible schema to exchange competency information within a variety of business contexts. • Intended as a fragment to be used within broader, process-specific schema.

26. Standard: Contact Method Used to pass contact information within HR transactions • Contact Methods • Telephone • Fax • Mobile • Pager • Email • Web Address • Use • Business, Personal • Location • Office, Car, Home • Availability • Weekends, Evenings

27. Standard: Dates • Date/Time data type extensions • Guidelines for effective dating <EmploymentHistory> <HireDate>2001-06-01</HireDate> <TerminationDate>notKnown</TerminationDate> </EmploymentHistory>

28. EntityIdType EntityReferenceType DunsNumberType InternetDomainNameType Standard: Identifier Types Common identifiers for use in HR-XML specifications

29. Standard: ISO Utilities • HR-XML specifications use a set of agreed-upon XML schema types to represent ISO codes • Guidelines document the use of these types and formalizes their adoption as Cross-Process Objects • Currency Code • Country Code • Gender Code • Language Code

30. Name ID TaxID LegalID DunsNumber InternetDomainName DoingBusinessAs LegalClassification IndustryCode Headcount Description WorkSite ContactInfo RelatedOrganization OrganizationalUnit Standard: Organization Defines companies, subsidiaries, governments, etc.

31. Organizational Unit • Defines departments, business units, project teams • Contains information useful in org chart creation • Name and Id • Description • Organization Id • Industry Code • Accounting Code • Work Site • Related Organizational Unit • Person Member (name, id, role, contact info) • Relationship (child, parent) • Role (functional, logical)

32. Standard: Postal Address • Pass postal address information reliably and completely, and in a format that can be efficiently processed • Elements make up a postal address as used from country to country, with a country code that enables formatting according to local postal rules • Supports both structured and unstructured information

33. Standard: Schema Extension (User Area) • Document that provides guidance regarding the extension of XML Schemas • Allows trading partners to exchange information not handled by the standards

34. Standard: Taxonomy Types • A taxonomy is a structure for classifying or categorizing information into a hierarchy • Currently includes schema pattern for Industry Code taxonomies such as SIC, NAICS, and UNSPSC. • Specification only includes structure for passing taxonomy, no code sets • Possible future taxonomies: • Occupational • Competency

35. Standard: WorkSite • Work Site Environment Includes • Name, Id • Description • General and Physical Considerations • Safety Equipment Requirements • Dress Code Work Site Includes • Name, Id • Details • Address • Travel Directions • Parking Instructions • WorkSiteEnvironment

36. Physical Location Specifying a physical location may be necessary for: • Space planning/utilization • Mail/package delivery • Emergency response • Assignment tracking • Close or divest plants, factories, or other locations • Search based on geo code • Identify multiple work locations for time cards • Screening • Privacy laws

37. Physical Location Example <TemporaryAssignment> <Id> <IdValue>123456789</IdValue> </Id> <Name>Midwest Distribution Center</Name> <SpatialLocation> <Latitude>+37.37.08.4</Latitude> <Longitude>+122.22.0.0</Longitude> </SpatialLocation> <TravelDirections>Take I-94 north to exit 356</TravelDirections> <Area type="countrycode"> <Value>CA</Value> <Area type="postalcode"> <Value>T5G</Value> </Area> </Area> <Comments>Mr. Sisk must sign all timecards</Comments> </TemporaryAssignment>

38. Specifications up for Vote • Specifications currently in Membership Review • Review closes October 24 • Online Vote open October 27 - 31 • Assessments 1.0 • Staffing Exchange Protocol 2.0 • Person Descriptors 1.0 • Physical Location (CPO)

39. Continuing Work… • Benefits Enrollment • Assessments • Background Check • Metrics • Competencies • Data Dictionary • Other Possibilities: Payroll, HRIS Bridge, Performance Evaluation, SIDES

40. Questions? Chuck Allen, Director, chucka@hr-xml.orgKim Bartkus, Deputy Director, kim@hr-xml.org Paul Kiel, Chief Architect, paul@hr-xml.org www.hr-xml.org