OASIS Customer Information Quality Technical Committee Overview

Скачать презентацию OASIS Customer Information Quality Technical Committee Overview

44102f1fc461b264080f68fe4548958d.ppt

Количество слайдов: 42

OASIS Customer Information Quality Technical Committee – Overview n n Ram Kumar Founding Chairman http: //www. oasis-open. org/committees/ciq kumar. sydney@gmail. com October 2008 Copyright © OASIS, 2000 Onwards

OASIS Customer Information Quality Technical Committee (OASIS CIQ TC) The Name “Customer Information Quality” is just the operating name of the Technical Committee. The scope of the TC is much broader than “Customer Information”. This Committee concentrates on developing global and generic industry specifications for “Party Centric Information”. “Customer” is a type of “Party”. Copyright © OASIS, 2000 Onwards

Background about CIQ TC n n n “Officially” founded at XML 2000 Conference in Washington DC, USA Technical Committee Members from Asia. Pacific, Europe, UK, and USA Founding Members l l l Ram Kumar, Mastersoft, Australia (Chairman) Vincent Buller, AND Data Solutions, The Netherlands John Bennett, Parlo. com, USA Copyright © OASIS, 2000 Onwards

Why was CIQ TC formed? n n In a customer driven world, party information is the “key piece of data” used in any business transaction and in particular, global ebusiness However, there were no XML industry standards or groups in year 2000 that concentrated on defining standards for consistent representation of party data and for sharing party data between the groups, processes, and applications/systems involved in business transactions associated with a party Therefore, it was decided to fill this gap through CIQ TC that would focus on developing XML industry specifications for party centric data representation and exchange A group called Customer Profile Exchange (CPExchange) under IDE Alliance commenced similar work in 2000, but the committee was closed down in 2001 -02 Copyright © OASIS, 2000 Onwards

CIQ TC Goals/Objectives n n n Develop global party specifications to represent party data Application independent specifications Platform independent specifications Vendor neutral specifications Industry neutral specifications Truly “open” specifications, meaning l l l n n n free of royalties free of patents free of licenses free of Intellectual Property Rights (IPRs) freely available for public to download and implement the specifications without any restrictions Specifications developed in an open process environment Specifications independent of language, cultural and geographical boundaries Specifications have the ability and flexibility to represent global party data Copyright © OASIS, 2000 Onwards

Out of Scope activities of CIQ TC n n n n n Data Privacy Data Security Message Structure Data Transport Data Routing Data Formatting International Name and Address Templates Data Transformation Transactional "party information" such as recent purchases, payment history, etc. Not a quality enhancing process as commonly understood or akin to a certificate of test results against some objective specification Copyright © OASIS, 2000 Onwards

CIQ TC Mission Statement Delivering royalty free, open, international, industry and application neutral XML specifications for representing, interoperating, and managing Party (Person/Organisation) Centric Information (Name, Address, Party Profile and Party Relationships) Open Industry Specifications developed by the Public for the Public Copyright © OASIS, 2000 Onwards

Why CIQ Standards – An Example Line of Business Silo’s Deposits Loans Mortgage Credit Cards Brokerage Insurance CIF Delivery Channels Where’s the Party (customer)? What do I know about the Party (customer)? n n n If there are many business systems in a organisation, party data are often captured in each of these systems independently with different formats, contexts, and quality. This leads to serious party data integration issues and therefore, poor visibility of the party and the dealings with the party within the enterprise. As a result, Party oriented initiatives becomes a challenge. If “standards” are introduced for different domains such as billing, sales, marketing, loans, insurance, etc, often you end up defining party models for each of these standards independently as advocated by these domain models (e. g. IAA, ACORD, x. BRL). CIQ provides a common base specification to represent party data in a consistent way across the organisation, and this can then be extended to support specific business requirements Copyright © OASIS, 2000 Onwards Source: Acxiom Corporation 2001

CIQ TC’s definition of Interoperability n “Get the right data to the right place at the right time in the right format, with the right quality, in the right context, and with the right governance” for processing by processes, applications and users. ” Copyright © OASIS, 2000 Onwards

CIQ TC’s Data Interoperability Success Formula n Data Interoperability = l l l l Open Data Architecture + Open Data Integration + Open Data Standards + Data Quality + Data Semantics + Data Security + Data Governance Copyright © OASIS, 2000 Onwards

What is special about CIQ TC and its Specifications? n n The “only standards group in industry” that is dedicated to developing XML specifications for representing Party Centric Data that is truly international and is open, independent of specific application or industry, and is vendor neutral The “only set of international specifications in industry” that concentrates exclusively on defining Party information specifications without any specific industry or applications or any geographic location or culture in mind Copyright © OASIS, 2000 Onwards

CIQ Specifications – Who developed them? n n Developed by experts dealing with “international party data” (includes international names and addresses) for use in various applications for over a decade Developed by experts with XML and XML based interoperability expertise Developed by experts dealing with data quality, data integration and interoperability of party centric data for many years Developed by experts who have implemented Information and Data Management Strategies in many organisations Copyright © OASIS, 2000 Onwards

CIQ TC Party Information Specifications n n n Extensible Name and Address Language (x. NAL) l Extensible Name Language (x. NL) to define a Party’s name (person/company) l Extensible Address Language (x. AL) to define a party’s address(es) Extensible Party Information Language (x. PIL) for defining a Party’s unique information (tel, e-mail, account, URL, identification cards, etc. in addition to name and address) Extensible Party Relationships Language (x. PRL) to define party relationships namely, person(s) to person(s), person(s) to organisation(s) and organisation(s) to organisation(s) relationships Copyright © OASIS, 2000 Onwards

Name and Address: What is the big deal about it? n n n The most complex “party” data, but the most important data for party identification and for any business dealing with parties (person/organizations) Can be represented in many ways, but still could mean the same Very volatile - names and addresses change often Often cluttered when recorded Varies from country to country as it is closely associated with the geographical location, culture, race, religion and language l Addresses of 241+ Countries l Represented in 5, 000+ languages l With about 130+ Address Formats l With about 36+ Personal Name formats Copyright © OASIS, 2000 Onwards

x. NAL Goals n n “Global” international specifications capable of handling any party names and addresses of the world Flexibility in design to help any simple application (e. g. Simple user registration using address lines 1, 2, 3, etc) to complex application (e. g. Name and Address parsing and validation by breaking name and address into atomic elements) to use x. NAL to represent party name and address data Follow and adopt W 3 C XML industry standards and ensure it is 100% open Open, global, application, industry and vendor neutral Copyright © OASIS, 2000 Onwards

x. NAL: Application and Industry Independency n n The CIQ specifications will not be specific to any application/domain or industry, say, Postal services, Mailing, CRM, Party Profile, Address Validation, etc The CIQ Specifications will provide the party data in a standard model that can be used by any application to do further work with the data Any domain specific standard group, say, Postal services, can use CIQ specifications and build their own standards by extending it to make it specific to its postal business Any domain specific application can use CIQ specifications and build applications around it that meets its business requirements Copyright © OASIS, 2000 Onwards

x. NAL: “Global” Specification n The objective is to provide the ability to handle the following: l l n Addresses of 241+ Countries Represented in 5, 000+ languages With about 130+ Address Formats With about 36+ Personal Name formats and at the same time, should be application independent, industry independent, open and vendor neutral Copyright © OASIS, 2000 Onwards

x. NAL: Design Approach/Methodology n n n Designed by people with several years of experience in International Name and Address data management and its applications (Postal services, Party Relationships Management, Parsing, matching, validation, DW, DM, Single Party View, Party Information Systems, etc) Collected and used valuable inputs from other name and address standard initiatives around the world Collected and used inputs from real world users, applications and experts of name and address data Conducted a detailed analysis and modeling of international name and address data The development of original x. NAL (ver. 1. 0) took about 2+ years Copyright © OASIS, 2000 Onwards

x. NAL: How different is it from other similar efforts? n n n Other efforts in defining name and address standards are part of application or industry domain specific models (e. g. Postal services, specific to a country’s names and addresses, Health, Human Resources, etc) x. NAL is the world’s first global, open, vendor neutral and application/domain, and industry independent specification for name and address language First and the only international standards committee dedicated to developing global XML specifications for name and address x. NAL can be used in any application/domain such as user registration, postal services, name and address parsing, name and address matching, name and address validation, etc. x. NAL is well set to meet the current business challenges of conducting businesses globally Copyright © OASIS, 2000 Onwards

An Open Challenge to existing groups that develop Person Name Models in Industry Can existing party models in industry other than OASIS x. NL V 3. 0 be able to represent the following name of a living person? Full Name : William Street Rajan United States Virginia Indian n Name used to address the person : WRUVI First Name, Middle Name, Last Name categorisation of the above name is invalid (they only represent the position of the name in a name string) as each name has a meaning associated with it that has to be preserved. This person’s cultural background does not have the concept for first name, given name, surname, family name, Christian name, last name, etc: n William Street : Name of the street where the person was born n Rajan : The person’s father’s name at birth n United States : Country where the person was born n Virginia : State where the person was born n Indian : Country of origin of the person n OASIS x. NL Specification can represent the above name as it provides capability to users to add “semantics” to a name string that helps to preserve the exact meaning of a name. Copyright © OASIS, 2000 Onwards

x. AL: Types of addresses covered Airport, Business/commercial parks, Caravan parks, Community Developments, Dual (Primary and Secondary), Educational institutions, Entertainment/ Recreation Parks, Hospitals, Large Mail Users, Marinas, Military, Ports, Retirement Villages, Resorts, Royal Highness, Rural(with land, air and water access), Sporting Venues, Territories, Tribal, Simple Urban, Complex Urban, Utility Urban, Ranged Urban, Villages, Location Based References, Vacant Lands, Hills, Banks, Canals, Rivers, etc Copyright © OASIS, 2000 Onwards

x. PIL (formerly called as “x. CIL”) n n n n Represents Other Party Information – extends x. NAL Party : A Person or an Organization (Organization: Company, not for profit, Consortiums, Groups, Government, Clubs, Institutions, etc) Only concentrates on party-centric information that helps to uniquely identify a party Application independent Open, application, industry, and vendor neutral Global Flexibility for simple representation of data to detailed representation of the data depending upon the need Copyright © OASIS, 2000 Onwards

x. PIL : Supported Party-Centric Information - Name details - Address details - Customer Identifier - Organization details - Birth details - Age details - Passport details - Religion/Ethnicity details - Telephone/Fax/Mobile/Pager details - E-mail/URL details - Gender - Account details - Marital Status - Identification card details - Physical Characteristics - Income/tax details - Language details - Vehicle details - Nationality details - Parent/Spouse/Child details - Visa details - Relationship details - Habits - Qualification details - Occupation details - Hobbies - Preferences - Key Events - Membership details Copyright © OASIS, 2000 Onwards

x. PRL (formerly called as “x. CRL”) n n n n Extends x. PIL and x. NAL by defining relationships and associated contextual roles between two or more parties First XML Specification in industry for managing Party Relationships with supporting roles Helps ease existing complex integration between Party information systems/software (e. g. CRM) and with backend systems Only concentrates on Party to Party Relationships and associated party roles Open, Application, industry and vendor neutral Global Flexibility for simple representation of data to detailed representation of the data depending upon the need Copyright © OASIS, 2000 Onwards

x. PRL – Types of Relationships • Person(s) to Person(s) Relationships Household relationships, Contact/Account Management, Personal and Business relationships, Organisation structure, etc • Person(s) to Organisation(s)/Group(s) Relationships Business relationships (e. g. “Doing Business As”, member of, employee-employer, business contacts, etc) • Organisation(s)/Group(s) to Organisation(s)/Group(s) Relationships Parent-Subsidiary relationships, Head office-Branch relationships, Partnership relationships (e. g. Alliance, Channel, Dealer, Supplier, etc), “member of” relationships, “Trading As”, “In Trade for” type relationships, etc Copyright © OASIS, 2000 Onwards

Status of CIQ Specifications (As of October 2008) n n n V 3. 0 -CS 02 of Name (x. NL) V 3. 0 -CS 02 of Address (x. AL) V 3. 0 -CS 02 of Name and Address (x. NAL) V 3. 0 -CS 02 of Party Information (x. PIL) V 3. 0 of Party Relationships (x. PRL) Copyright © OASIS, 2000 Onwards

Open Industry Specifications used by CIQ Specifications V 3. 0 n x. Link from W 3 C (Jointly implemented with x. BRL Group to enable interoperability between CIQ and x. BRL) n n n n Geo. RSS/GML Profile from OGC Schematron from ISO Code List Representation (Genericode) from OASIS Context Value Association Methodology from OASIS XML Schema from W 3 C x. Path from W 3 C XSL from W 3 C Copyright © OASIS, 2000 Onwards

Key Features of CIQ V 3. 0 n n n n Allows users to define semantics to the data that reflect their business requirements Allows users to apply constraint on CIQ XML Schemas (e. g. only using the elements they want to meet their business requirements) without changing the CIQ XML Schemas Allows users to add/delete/change code list values without changing the CIQ XML Schemas Can perform one pass validation (structure and code list value validation) of CIQ XML document instances against the CIQ XML Schemas if the code lists are defined as part of CIQ XML Schemas Can perform two pass validation (pass 1 – structure validation and pass 2 – code list value validation and business rules validation) of CIQ XML document instances against the CIQ XML Schemas by defining code lists outside of the CIQ XML Schemas More international address examples represented in CIQ Option to use x. Link from W 3 C or key reference to link parties Option to use Geo. RSS from OGC to represent address locations Copyright © OASIS, 2000 Onwards

CIQ Specifications (Adoption by Industry Types - Sample) n n n n Governments, including e-Government Insurance Companies Banks Solution providers Telecommunication companies Product Vendors Retail companies Standard Bodies/Groups/Consortiums (e. g. OGC) OASIS Technical committees (e. g. DITA, Tax, Emergency, Election) Open Source Communities Postal Companies Manufacturing companies Financial Service Providers (e. g. credit cards) Automotive industry Justice Sector Health Copyright © OASIS, 2000 Onwards

CIQ Specifications (Industry Applications - Sample) n n n n Single Party View Party Recognition/Identification Enterprise Party Data Management Data Quality (e. g. parsing, matching, de-duping, verification, validation and enhancement) Party Profiling Purchase orders, invoicing and shipping Party Relationships Management Party Services Postal Services Election Services Justice, Legal and Corrective Services Business Intelligence Party Data Interoperability Frameworks Front End Data Quality Capture Emergency Management Geospatial (e. g. Google Earth/Map) Copyright © OASIS, 2000 Onwards

CIQ Specifications – Restrictions to Use n Any Intellectual Property Rights? l n Any Licensing agreements/terms/conditions? l n NONE Any restrictions (e. g. cost) to implement? l n NONE Any restrictions (e. g. cost and user registration) to download? l n NONE Any Patents? l n NONE Any Royalties? l n NONE Any restrictions (e. g. cost) to modify? l NONE CIQ Specifications are developed by the Public for the Public Copyright © OASIS, 2000 Onwards

Interested to contribute/contact CIQ TC? n n CIQ TC is constantly looking for more members to join this important committee If you are interested to contribute or provide feedback, please contact l Ram Kumar, Chair, OASIS CIQ TC n kumar. sydney@gmail. com Copyright © OASIS, 2000 Onwards