Federated Information Management with OWL/RDF/SPARQL

1. Federated Information Management with OWL/RDF/SPARQL Tony Vachino – tvachino@spryinc.com Todd Jones – tjones@spryinc.com

2. Information Federation Problem • Enterprises are made up of many domains within domains • Sales, Operations, R&D, Executive management, manufacturing, … • Logistics, HR, Finance, intelligence … • Each domain fields its own applications and creates its own information to execute its mission • It is often not possible to federate and integrate applications within domains • In many cases it is necessary to share data within domains and across domains • Enterprises will never meet information sharing needs until it first solves the INFORMATION federation problem

3. Federation Requires Description • Information discovery, reuse, and integration all depend on description • If we do not know what something is we cannot possibly know how to integrate it with other things or even how it should be used • If we describe everything well enough, we are in a position to have a knowledge-based web • Integrate and interoperate • Analyze any combination of information • Semantic technologies, RDF & OWL enable information federation • Both machines and people can understand the descriptions

4. Information Federation Solution • Enterprise Information Web • Any information from any system can be shared with any other system on the enterprise networks or the World Wide Web • Steps • Describe all of the terms and artifacts in each domain using the semantic technology standards OWL & RDF • We currently do this description work, but we do not use machine readable standards – Excel, Word, Powerpoint, Visio • The formal description of a domain is called a domain ontology • Describe how all of the information managed in each domain is related to the domain vocabulary use these descriptions to say how domains are related • Query the Domain vocabularies for any information • The result is an Enterprise Information Web that meets the goals of information sharing and analysis

5. Why Semantics? EIW solves the Information Federation Problem in Real Time • Real time information integration • Reporting and analysis • Drilldown capabilities • Leverages the natural federation and integration capabilities enabled by W3C semantic web standards.

6. Enterprise Analytics Improve customer’s product selection Improve soldier’s quality of life Variety of Products, Time to Restock, etc. Increase time at home Manufacturing, Shipping, Forecasting, Sales… Training, Mobilization/Deployment, Recoup, Strength Management Strength Projections, Available Members, Training, Recruiting, Retirement Product Tracking, Sales #, Manufacturing estimates,

7. Complexities within the DoD Strategic Initiatives Logistics Finance Dept. of Defense Equipment Human Resources Operations R&D Warfighter

8. Dwell Time in the Military Training IATS Deployment DTS BCS3 DTMS ATIA- LMS VIPS Eagle Cash TAPDB SPA ATRRS UTS DTAS Recoup DTS GFM ODSE IATS DTS SMS WWAS IPPS PRMS IATS eMilpo GCSS SIDPERS IGS

9. EIW Ontology Architecture Policy Ontology Metrics Ontology Enterprise Standards Discussion Ontology Community Ontology Human Resources Domain Ontology Process Ontology Analytics Ontology Relational Mapping Ontology Relational Mapping Ontology Source Ontology Source Ontology Data Source Data Source

10. Governed Ontology Development Governed, collaborative COI Bluto: Well, beer has an ingredient Chip: Agree. Beer also has turbidity Bluto: Agree, beer has a location Chip: I disagree. Beer has a Brewery and brewery has a location Turbidity Bluto: Agree. Beer has an Award Event Chip: And Award Even has an Award Ingredient Location Beer Award Brewery AwardEvent

11. Operational Governance • List of • discussion tasks • within a particular • subject • Includes status, • date assigned, and • Subject Matter • Expert • List of all ontology • development subjects • Includes Status of issue • and priority • List of all discussions within a particular subject

12. Spry Agile Delivery Methodology • Spry has delivered incremental capability every 90 days using an Agile Methodology • How? • Flexible Milestones • Outline three month plan, adapt to the Governments evolving requirements • Two Week Sprints • Priorities reviewed, tasks moved from backlog • Daily stand-ups • Team members on task, issues addressed within 24 hours • Jira • Web based bug, issue and project tracking • Requirements documentation, UI mockups, etc. • Stakeholder Engagement • Visibility into ‘real’ progress, not just updates on out of date MS Project Schedule • Significant experience implementing Agile on a large/complex DoD Project- we’re not just using buzzwords from a book

13. Popular Approaches • Hard coded and/or complex • models • Poor service discovery, • preventing reuse • Limited traceability • Process, Consumer, • Legacy Data • Difficult to manage and • validate ROI • ETL processes are difficult • to manage. • Proprietary in nature • Hard Coded • Complex Models • Costly • Require customizations • for “outside the box” • functionality • Customer Lock – In • Data Warehouse “Stacking” Data Warehouse Approach SOA Approach Data Warehouse Web Services Web Services ETL Legacy System Legacy System Legacy System Legacy System Legacy System Legacy System

14. The EIW Approach • Open Social Gadgets CHRIS Reference Ontology Community Ontology Discussion Ontology SPARQL • Domain Ontology • Mapping Ontology • Source Ontology • Analytic Ontology • Process Ontology Federator Human Resources Domain Ontology Process Ontology Analytics Ontology SPARQL SPARQL SPYDER SPYDER Relational Mapping Ontology Relational Mapping Ontology SQL SQL Source Ontology Source Ontology eMILPO ODSE • Relational Database • Authoritative Data Sources

15. Follow Spry…Twitter – Spry_IncFacebook – Spry, IncWebsite – www.spryinc.comTony VachinoEmail: tvachino@spryinc.comLinkedIn: http://www.linkedin.com/in/tonyvachino

16. Visibility and Understanding Visibility is only half the picture. Visibility and understanding is the complete picture