When to Consider Semantic Technology for Your Enterprise


Published on

This presentation, When to Consider Semantic Technology for Your Enterprise, was presented by Mike Delaney and David Read at the 2013 Semantic Technology and Business Conference.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Start from scratch?Layer on top of existing stack?Critical problem?Consultants, hire from outside or train up?What are the pieces that I need to get started?OntologyReasonerTriple StoreCan we suggest Open Source solutions to get started with and highlight the vendor independence of the space? That way when they’re ready to productionalize they can choose the best vendor for them.
  • When to Consider Semantic Technology for Your Enterprise

    1. 1. © Blue Slate Solutions 2013When to Consider Semantic Technology forYour EnterpriseMichael Delaney, Senior Consulting Software EngineerDavid Read, CTOSemantic Technology and Business ConferenceSan Francisco, CA, USJune 3, 2013
    2. 2. HowWhy Not
    3. 3. Who are Dave and Mike?• Architecture• Security• Innovation• Solution engineering• Integration• ETLDavid Read Michael Delaney
    4. 4. © Blue Slate Solutions 2013Who is Blue Slate?3About Driven by a total commitment to customers, company,colleagues and community 30+ consultants – operations, strategy, technology andindustry experts Founded in 2000, headquartered in Albany, NYClients Industry Leaders seeking to drive value forshareholders and end customers Include ten Blues organizations and four commercialpayers Innovators looking to grow beyond their core markets
    5. 5. © Blue Slate Solutions 2013What?4Let’s give semantic technology some context
    6. 6. © Blue Slate Solutions 2013What is Semantic Technology?Semantics≡ meaningSemantic Technology≡ machine-readable meaning5
    7. 7. © Blue Slate Solutions 2013What Makes Up Semantic Technology (in this talk)?• Standards → RDF/RDFS/OWL/SPARQL• Definitions → Ontologies• Storage → Triple Stores• Inferencing → Reasoners• Data Access → SPARQL• APIs → Jena, Sesame6
    8. 8. © Blue Slate Solutions 2013Semantic Technology is a Team Player in an Architecture• Integrates• Federates• Adapts• Extends7
    9. 9. © Blue Slate Solutions 2013What Is Different About Semantic Technology?• Structure is (mostly) logical not physical– Triple– Directed Graph• Federation is assumed– SPARQL• Web is the natural platform– URI– HTTP8SubjectPredicateObject
    10. 10. © Blue Slate Solutions 2013Directed Graph Example9DavidbioFatherOfSarahLisabioMotherOffullSiblingOfMichaelSarahBfriendOffriendOfCarlspouseOfBlue SlateSolutionsemployeeOffavoriteSportBowlingbioFatherOf fullSiblingOf
    11. 11. © Blue Slate Solutions 2013The Physical Structure is Flexible by Design• Triples are an extreme form of normalization• Any data can be related without the need forforeign keys• Relationships can be added or removed asthey are found, explored, accepted ordiscredited10LisabioMotherOfMichaelfriendOfCarlfavoriteSportBowling
    12. 12. © Blue Slate Solutions 2013The Logical Structure is Built to Relate and Define• Directed graph relatesdata• RDF, RDFS and OWLdefine data• Reasoners build modelson the fly• Relationships areflexible:– Groups can use differentrelationship rules11
    13. 13. © Blue Slate Solutions 2013What’s New?Let’s compare semantic and other technologies12
    14. 14. © Blue Slate Solutions 2013Storage13Relational Efficient Use of SpaceNoSQLDocument Stores(Key-Value Pairs)SemanticSingle, standardized schema(the triple)
    15. 15. © Blue Slate Solutions 2013Relationships14RelationalRelationships conveymeaning through table namesor data valuesNoSQL NoSemanticRelationships conveymeaning in their definition
    16. 16. © Blue Slate Solutions 2013Query Language15RelationalStandardized Language(ISO: SQL)NoSQL No Language StandardizationSemanticStandardized Language(SPARQL)
    17. 17. © Blue Slate Solutions 2013Schema Maintenance16Relational Rigid SchemaNoSQL Data is unstructuredSemanticRelationships conveymeaning in their definition
    18. 18. © Blue Slate Solutions 2013Maturity17RelationalWell established(30+ years old)NoSQLComing Along(10+ years old)SemanticRelatively Young(5+ years old)
    19. 19. © Blue Slate Solutions 2013Indexing18RelationalIndexing can be complicated,but is vital to scalabilityNoSQLIndexing can be complicated,but is vital to scalabilitySemantic Indexing can be automatic
    20. 20. © Blue Slate Solutions 2013Optional Relationships19RelationalOptional relationships can bedifficult(NULL’s or Dummy Values)NoSQL NoneSemanticAll relationships are optionalby default, but can beenforced if needed
    21. 21. © Blue Slate Solutions 2013Ecosystem20RelationalVery rich developmentecosystem, solid toolingNoSQLRich developmentecosystem, limited toolingSemanticImmature ecosystem,nascent tools
    22. 22. © Blue Slate Solutions 2013OntologyOWLSemantic Technology: Cool Solution Looking for a Problem?21TripleGraph SPARQLReasonerTriple StoreRDFTurtleObjectPredicateSubject
    23. 23. © Blue Slate Solutions 2013Where?22Is this technology really being used?
    24. 24. © Blue Slate Solutions 2013Where is Semantic Technology Today?• Maturing standards and practices• Expanding ecosystem• Big and small players• Diverse offerings– Products and services• Real-world usage23
    25. 25. © Blue Slate Solutions 2013Consider Relational Database Adoption241 2 3 4 5 71. Edgar Codd begins relational data research2. Codd publishes, “Relational Model of Data for Large Shared Data Banks”3. Oracle v2 released (marketing gimmick, no v1)4. DB2 announced5. Sybase released6. DB2 released7. Sybase forked to MS SQL Server6
    26. 26. © Blue Slate Solutions 2013Data and Analytic Diversity Continue to Expand25• Evolving Interactions• Data Diversity
    27. 27. © Blue Slate Solutions 2013Where has it been deployed successfully?26• BBC– World Cup– Olympics• data.gov• Facebook’s Graph Search• Best Buy Product Catalog• Cleveland Clinic• Amazon• …
    28. 28. © Blue Slate Solutions 2013Why?Why do enterprises use semantic technology?27
    29. 29. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Integrates diversedata sources28
    30. 30. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Provides consistent meaningacross systems29
    31. 31. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Federates and integratesin real-time30
    32. 32. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Supports multiple logical modelswithout ETL and warehouses31
    33. 33. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Extends data and relationshipswithout refactoring databases32
    34. 34. © Blue Slate Solutions 2013How Does Semantic Technology Benefit an Enterprise?Augments Analytics33
    35. 35. © Blue Slate Solutions 2013Volume, Velocity, Variability, Variety• Triple stores do well with volume and velocity– Commercial products scale to billions of triples• Directed graphs simplify variability– Nodes and vertices can come and go• URIs support variety– Addressable ≡ accessible34
    36. 36. © Blue Slate Solutions 201335When?Recognizing good opportunities forintroducing semantic technology
    37. 37. © Blue Slate Solutions 2013When should you consider Semantic Technology?HeterogeneousData36
    38. 38. © Blue Slate Solutions 2013When should you consider Semantic Technology?37EvolvingDataStructures
    39. 39. © Blue Slate Solutions 2013When should you consider Semantic Technology?38Rule-baseddatainteractions
    40. 40. © Blue Slate Solutions 2013When should you consider Semantic Technology?39LanguageFlexibility
    41. 41. © Blue Slate Solutions 2013When should you consider Semantic Technology?40VendorIndependence
    42. 42. © Blue Slate Solutions 2013When should you consider Semantic Technology?41AugmentingCurrentSystems
    43. 43. © Blue Slate Solutions 2013When Not?42Avoid the round hole, square peg syndrome
    44. 44. © Blue Slate Solutions 2013When Won’t Introducing Semantics Make a Splash?• Common and well-defined systems– Claims Processing– Order Entry– ERP– Payroll– CRM43
    45. 45. © Blue Slate Solutions 2013Semantic Technology is Not “The” AnswerNot a dessert topping, enginelubricant, elixir-of-life, handsoap andcloud solutionall-in-one!44
    46. 46. © Blue Slate Solutions 2013When is Semantic Technology a bad fit?Transactional,high volume45
    47. 47. © Blue Slate Solutions 2013When is Semantic Technology a bad fit?46Homogeneousor containeddata
    48. 48. © Blue Slate Solutions 2013When is Semantic Technology a bad fit?Problems that have alreadybeen solved/abstracted47
    49. 49. © Blue Slate Solutions 201348When is Semantic Technology a bad fit?Very largedata stores
    50. 50. © Blue Slate Solutions 2013Case Study49We’re giving you the story first hand
    51. 51. © Blue Slate Solutions 2013Case Study: Client• Medicare Administrative Contractor• Struggling with key metrics• Competitive landscape (15  10  ~7)50
    52. 52. © Blue Slate Solutions 2013Case Study: Challenge• Poor medical review focus– Only denying ~30% of reviewed claims• Slow reaction to reviewoutcomes• High repeat defects fromproviders• Struggling to implementmeaningful analytics51
    53. 53. © Blue Slate Solutions 2013Case Study: Root Causes• Manual “copying”between systems• Lack of agilityaround reviewchecklists• Review details notcaptured• Providers mystifiedregarding denial reasons• Multiple systems with parts of the story52
    54. 54. © Blue Slate Solutions 2013Case Study: Semantic Focus• Agile checklist support• Flexible data classifications for denials• Immediate aggregation and feedback of reviews• Legacy integration53• Detailed associationof denials andprovider education• Integration of claimdata and reviews foranalytics
    55. 55. © Blue Slate Solutions 2013• Details supporttargeted data mining• Ontology easilyupdated to addressidentified risks• Semantic reasonerleverages rulesdiscovered throughanalytics• Flexible classifications provide agility dealing withchanging healthcare payer issues (errors, fraud,abuse, waste…)Case Study: Outcomes54
    56. 56. © Blue Slate Solutions 2013How?55Make it so!
    57. 57. © Blue Slate Solutions 2013How do I know when to take the leap?56
    58. 58. © Blue Slate Solutions 2013How do I start?Picking a projectStaffingTechnologyScheduling57
    59. 59. © Blue Slate Solutions 2013Questions + Contact Info58Thank you for attending our session.Feel free to contact us if you havequestions:Michael.Delaney@blueslate.netDavid.Read@blueslate.netwww.blueslate.net