1 / 18

Waterfeld Customer Information Integration Solution

Efficiently integrate customer information from various sources with Waterfeld's Semantic Information Integrator. Overcome data heterogeneity, legacy systems, and manual processes with automatic mapping and integration. Enhance customer support, sales, and management with access to complete and accurate customer information.

jkell
Download Presentation

Waterfeld Customer Information Integration Solution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Content • Semantic Information Integration • crossvision Information Integrator • Use Case Customer Information • Experiences Waterfeld

  2. Getting Information customer sales Support Management existing manual needed Legacy CRM ERP SFA logistics Waterfeld

  3. Information heterogeneity • Heterogenous data sources • Technical heterogeneity • Different formats • Incomplete data • Redundant data • Different access system • Different user interfaces • Different Semantic Waterfeld

  4. Semantic Information Integration • Current technologies • EAI • ETL (data warehouse) • Information Integration • Direct access • Integrated information model • Semantic Information Integration • Ontologies as integrated information modell Ontologies Mapping Mapping Mapping Waterfeld

  5. views manual mappings automatic mappings <article> <articleid>a-5634</articleid> <category>printer</category> <name>hp81</name> <price currency=‘USD’>500</price> <producer>hp</producer> <resolution>1960 dpi</resolution> <type>laser</type> …. </article> sources Layered Ontology Approach integration ontology source ontologies Waterfeld

  6. crossvision Information Integrator Studio (Eclipse-based) Web Service Semantic Server CentraSite Repository Query Queries Load Ontologies Ontologies Mapping Metadata User Security WebDAV JAXR UDDI XML ADA WSDL Tables Waterfeld

  7. Usage Information Integrator Query Builder Application Deploy Web Service End Web Service Integrator Studio Integration Ontology Semantic Server Source Ontology Mapping to Source Ontologies Import Metadata Start Metadata Waterfeld

  8. SQL Support Information System Adabas Customer Information System Use Case: Customer Information Gateway Does a customer raising a support issue for a specific product have a valid maintenance contract for that product? What is a customer‘s experience with our products? • client • contact information • contract • customer • contact information • support case Waterfeld

  9. Class „CUSTOMER“ property „cid“ type integer … Class „CASE“ property „desc“ type string property „cust “ type integer property „belongsTo“ type „CUSTOMER“ … Class „File151“ property „AA“ type integer property „AB“ type date property „AC“ type date property „AD“ type string … Class „File87“ … Customer Information Gateway – Source ontologies Support Information System (SQL) Customer Information System (Adabas) File 151 Fields „AA“, „AB“, „AC“, „AE“ File 87 Fields „AA“, „AB“, „AC“ Table „CUSTOMER“ Table „CASE“ Waterfeld

  10. Automatic Source ontology mapping FORALL X,Y c(“FILE151”, X):FILE151_CONTRACT[FILE151_AA->X; FILE151_AE->Y] <- accessToSource(connectionInfo, “FILE151”, “AA”, X, “AE”, Y)@Source151. FORALL X, Y, Z c(“FILE152”, X):FILE152_CLIENT [FILE152_AA->X; FILE152_AB->Y; FILE152_AC->Z] <- accessToSource(connectionInfo, “FILE152”, “AA”, X, “AB”, Y, “AC”, Z) @Source152. FORALL X, Y, Z c(“CUSTOMER”, X):CUSTOMER[id->X; name->Y; addr->Z] <- accessToSource(connectionInfo, “CUSTOMER”, “id”, X, “name”, Y, “addr”, Z) ]@SourceSQL. FORALL X,Y,Z c(“CASE”, X):CASE[caseId->X; status->Y; customerId -> Z] <- accessToSource(connectionInfo, ”CASE”, “caseId”, X, “status”, Y; “customerId”, Z) ]@SourceSQL. Waterfeld

  11. Class „File151“ Class „File 87“ Class „CUSTOMER“ Class „CASE“ Adabas SQL Integration Ontology Class Customer Class Contract property id property contractId property name property contractEndDate property address property contractor Class SupportRequest property id property status property issuedBy File 151 -> Contract AA -> contractId AB -> contractStartDate AC -> contractEndDate AD -> contractStatus File 87 -> Client … Waterfeld

  12. Integration Ontology Mapping • Class and property mapping FORALL X, Y, Z X:Contract[contractId->Y; endOfContract->Z]@Business <- X:FILE151_CONTRACT[ FILE151_AA->Y; FILE151_AE->Z]@Source151. • Object property mapping FORALL X, Y, Z1, Z2 X:SupportRequest[issuedBy->c(“Customer”, Z1, Z2)]@Business <- X:CASE[forCustomer->Y]@SourceSQL and c(“CUSTOMER”,Y)[name->Z1; addr->Z2]@SourceSQL. Waterfeld

  13. Customer Information Gateway - Mapping Class Customer Class Contract property id property contractId property name property contractEndDate property address property contractor Class SupportRequest property id property status property issuedBy • Object identity • Data type transformations • Encoding of values • Generation of object references • Generation of inverse references • N:M relations Class „File151“ Class „File 87“ Class „CUSTOMER“ Class „CASE“ Waterfeld

  14. Mapping tool Waterfeld

  15. Customer Information Gateway - Queries For given SupportRequest search for the corresponding Contract Class Customer Class Contract property id property contractId property name property contractEndDate property address property contractor Class SupportRequest property id property status property issuedBy Waterfeld

  16. Experiences: Problems • F-Logic functionality • Basic datatypes (primitive XML Schema types) • Mapping F-Logic to XML • Processing of nested hierarchical lists in F-Logic • order • Null values • User adoption • No rule language standard • F-Logic syntax too cryptic, not keyword-oriented • Only possible via tools e.g. graphical rules editor • No accepted ontology and rule model API • Utilizing query capabilities of data sources Waterfeld

  17. Benefits • Query language as sublanguage of rule language • High expressiveness of rule language for ontology mapping • Adding additional knowledge to integration ontology • Ontologies as executable models for information integration Waterfeld

More Related