Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Dennis Wisnowsky Presentation

on

  • 1,665 views

 

Statistics

Views

Total Views
1,665
Slideshare-icon Views on SlideShare
1,665
Embed Views
0

Actions

Likes
1
Downloads
44
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Dennis Wisnowsky Presentation Dennis Wisnowsky Presentation Presentation Transcript

    • Semantic Technology in the Department of Defense, Business Mission Area Dennis E. Wisnosky, DoD BMA CTO & November 17, 2010 Chief Architect in the Office of the Deputy Chief Management Officer
    • DCMO CTO/CA Missions of the DoD Warfighter Business Intel Mission Mission Mission Area Area Area Enterprise Information Environment Mission Area Dennis E. Wisnosky, DoD BMA CTO & Chief Architect in the Office of the Deputy Chief Management Officer (DCMO) 11/17/2010 DWiz DoD DCMO BMA CTO & CA 1
    • The Business Operating Environment Reach of the Business Mission Area "The Secretary of Defense is responsible for a half- trillion dollar enterprise that is roughly an order of magnitude larger than any commercial corporation that has ever existed. DoD estimates that business support activities—the Defense Agencies and the business support operations within the Military Departments— comprise 53% of the DoD enterprise.” Global Reach! 11/17/2010 DWiz DoD DCMO BMA CTO & CA 2
    • 57% of DoD I.T. Costs are in Infrastructure Challenges! Issue: Infrastructure SOURCE: http://www.whitehouse.gov/omb/e-gov/ DoD Contractors Build Separate Infrastructures Issue: Redundancy & Dictionaries DoD Projects Have Own Data Issue: Data 11/17/2010 DWiz DoD DCMO BMA CTO & CA 3
    • A Small Slice of the As-Is We Must Make Sense Out of This! 11/17/2010 DWiz DoD DCMO BMA CTO & CA 4
    • Game-Changing Innovations Common Vocabulary and Primitives  If we can precisely state requirements and precisely describe data/services, we will be able to find them and know how to use them to facilitate: – Integration and Interoperability  We must describe both the data/services and requirements with enough precision to accomplish the goal  We use: – BPMN/Primitives for business mission descriptions – OWL and RDF for domains, services, data, capabilities and requirements descriptions 11/17/2010 DWiz DoD DCMO BMA CTO & CA 5
    • To-Be State Dynamic, event-driven reconfiguration of services 11/17/2010 DWiz DoD DCMO BMA CTO & CA 6
    • Strategy and Roadmap for DoD Business Operations Transformation Past Present Future (BMA Federation Strategy version 2.4a) (BOE Execution Roadmap) (BMA Architecture Strategy version 3.0) DoD Strategic Mgmt. Plan (SMP) DCMO/CIO Policies BEA 3.0 Performance Measures CIO – DIEA, Segment Archi. CV & Primitives Initial BOE Data Sharing and Arch. Fed. Experience BI Enablement MDR Biz. Intelligence Federation Version BOE Vision Implementation Semantic 2.4a Plan Information Roadmap: BOE Service Data Integration Enterprise Architecture Stds. Governance Enablement Business Intelligence Socialization RDF Domains Common Vocabulary OWL Services (Ontologies) other Infrastructure HRM/ Med FM Execution Rules/Workflow Vision & Strategy Logistics DBSAE Planning & Roadmap RPILM SOA Security Imp. Infrastructure WSLM/ Strategy MSSM BEA 8.x Governance (BTI) NCES/CES CIO/DISA – Federal Cloud DBSMC/IRBs DCMO/DCIO; EGB; BECCM 11/17/2010 DWiz DoD DCMO BMA CTO & CA 7
    • Business Operations thru Semantic web Solutions  Semantic Web Initiative – Business IT development methodology 3-step pattern • Modeling the business capability to be deployed • Preparing and populating a modern information model and data store • Implementing the capability by deploying business services – “Model-Data-Implement” semantic web pattern is designed to field capabilities in 60-90 days; this supports the Departments goal to move away from monolithic systems that take years to deploy – Current application of this pattern to achieve high performing business operations: • Enterprise Information Web (EIW) • Performance Data Automation (PDA) – DCMO is preparing policy and instructions to fully instantiate the Semantic Web initiative and take advantage of W3C and OMG standards and semantic technologies that the commercial sector is widely deploying 11/17/2010 DWiz DoD DCMO BMA CTO & CA 8
    • Standards-based Architecture - Primitives Modeling the business capability to be deployed Standard Standards Modeling: Primitives! Architecture Primitives Symbols Best Practices Music Language and Symbols: influences informed Engineering Language Music Scale symbols by and Symbols: Resistor symbol Notes symbols Capacitor symbol Architecture Primitives PriMo This agreed upon representation Modeling Guide This agreed upon representation of electrical engineering allows a common understanding… of music allows a common foundation understanding… for PrOnto Ontology (Lexicon) •DoDAF 2.0 serves as the foundation for architecture input for primitives Standard •Use Cases being developed and used to drive pilots Language Different (terms and Frameworks 11/17/2010 DWiz DoD DCMO BMA CTO & CA definitions) 9
    • Architecture Primitives Series Modeling the business capability to be deployed Well Documented Intentions! DoD Architecture Framework Processes Best-Practice http://cio-nii.defense.gov/sites/dodaf20/journal_exp3.html 11/17/2010 DWiz DoD DCMO BMA CTO & CA 10
    • Primitives Lead to Patterns Modeling the business capability to be deployed  Provides basic definitions PriMo of the architecture model PrOnto  A style guide provides semantics subjective advice that will  Provides elementary rules ensure the design of high for the connectivity of quality products primitive constructs  A style guide advises on  Provides foundation – Choice of words building blocks for constructing architecture • Which constructs products are appropriate in a given  Caveat: A common situation vocabulary by itself does not guarantee high quality – Choice of grammar products • How to combine constructs to 11/17/2010 DWiz DoD DCMO BMA CTO & CA maximum effect 11
    • Primitives Lead to Patterns Modeling the business capability to be deployed NEWS FLASH! OMG Selects DoD Primitives  Provides basic definitions as a BPMN 2.0 PriMo semantics  Provides elementary rules Conformance Class! PrOnto of the architecture model  A style guide provides subjective advice that will ensure the design of high for the connectivity of quality products primitive constructs  A style guide advises on Will Industry Care?  Provides foundation – Choice of words building blocks for constructing architecture • Which constructs products are appropriate in a given  Caveat: A common situation vocabulary by itself does not guarantee high quality – Choice of grammar products • How to combine constructs to 11/17/2010 DWiz DoD DCMO BMA CTO & CA maximum effect 12
    • We Are Underway! Modeling the business capability to be deployed 11/17/2010 DWiz DoD DCMO BMA CTO & CA 13
    • BEA Solution Statement Modeling the business capability to be deployed • Visibility: pull & display (vice store!) enterprise information directly from the authoritative data sources • Agility: plug-and-play federated environment so new systems or analytical needs can come online and go offline without disrupting the overall environment • Access: build federation into the solution • Standards: leverage BPM and Semantic Web technology standards (RDF/OWL) developed by DARPA and approved by W3C and OMG • Savings: People readable Architecture, Machine readable Architecture, Executable Architecture, Long-term re-use of authoritative data RDF/ OWL BPMN 11/17/2010 DWiz DoD DCMO BMA CTO & CA 14
    • Interoperability (Federation) in BEA Approach Modeling the business capability to be deployed  Federation:  The Interstate highway system  The railroad system  The United States of America  DOD is a federation  Steps 1. Build Domain Vocabularies: describe all of the artifacts in each domain using RDF/OWL standards • DoD currently does this description work, but without standards – often in Excel, Word, Powerpoint, Visio, etc 2. Relate Domains: use RDF/OWL based descriptions to say how domains are related • This is the big missing piece of the current “standards” approaches 3. Relate domain data to Domain Vocabulary: Use RDF/OWL to say how all of the data in each domain is related to the Domain vocabulary 4. Query the Domain Vocabulary for any information  Result: BEA Enables Enterprise Information Web 11/17/2010 DWiz DoD DCMO BMA CTO & CA 15
    • Agility in the BEA Approach Preparing and populating a modern information model and data store  Agility in process:  “Agile” development method; quarterly “deliverables”; lessons learned influence next deliverable;  Agility in product:  Once assets are unambiguously described, whole environment becomes “plug and play”  Eg: New DCMO policy issued: • Today: additions/changes to relational environment very costly • BEA: RDF/OWL graph-based information model is infinitely extensible and inexpensive to change; just add concept to the graph and point to its authoritative data source (ADS)  Agility in query development  Queries are machine and human readable  Fast to develop across disparate ADSs NOTE: up-front time and labor cost of unambiguously describing assets is not trivial 11/17/2010 DWiz DoD DCMO BMA CTO & CA 16
    • Example Savings in this BEA Approach Preparing and populating a modern information model and data store  Flexibility & Data accuracy  Current “standards” approaches force rigid conformity in understanding and representation of data. Result: very painful and expensive retroactive coding.  Semantic approach allows for variation in Tank? understanding while prescribing conformity in representation. Result: flexibility at the instance level and accuracy at the enterprise level  Interface development  E.G.: 5 systems require interfaces to each other (20 interfaces). If each system’s information model is Svc Member semantically described, only have to describe 5 interfaces DV to  Portfolio Management Data Airman Concept Svc Mem System Pers Sys Arch?  Once information assets are unambiguously Soldier Svc Mem Pers Sys described, Domain vocabulary can assess gaps and Sailor Svc Mem Pers Sys redundancies in the portfolio and the architecture Lawyer Svc Mem Pers Sys based on factual assessments (notional depiction only) 11/17/2010 DWiz DoD DCMO BMA CTO & CA 17
    • DoD BEA Ontology Preparing and populating a modern information model and data store Analytic References Requirements Description of concepts in Enterprise Domain Shows which authoritative Models analytic requirements for the documents concepts have Domain Vocabulary and how they been extracted from Domain/ relate to the concepts in the Domain Common Vocabulary, including SPARQL queries Vocabulary Standards Process Ontologies Ontology ADS Translation of BPMs to OWL. Description of Standards – Mapping Activity/Message descriptions definitions, permitted values, Ontology include relationships to domain usage, business rules, reference vocabulary terms. documents, etc. Mapping of domain vocabulary terms to the physical data elements they represent in the Authoritative Data Sources (ADS) 11/17/2010 DWiz DoD DCMO BMA CTO & CA 18
    • Example SMP to End to End (E2E) Process Preparing and populating a modern Priority 5 – Strengthen DoD Financial Management information model and “Procure to Pay” (P2P) data store Level 1 E2E in the BEA SMP Metrics also to be rolled up to Level 1 SMP Metrics linked at Leaf Level (e.g., Level 2) Common Vocabulary is Necessary! “Perform Receipt Acceptance & Return” P2P Level 2 E2E in the BEA Leaf Level decomposition used to identify and define requirements “rolled up” to and visualized at Level 1 11/17/2010 DWiz DoD DCMO BMA CTO & CA 19
    • Common Vocabulary Development Preparing and populating a modern information model and data store  Identify information to communicate  Agree on terms and contextual use  Communicate 11/17/2010 DWiz DoD DCMO BMA CTO & CA 20
    • Building Common Vocabularies Preparing and populating a modern information model and data store What is the Which Which data/ Who/What architecture processes/ resources will will be supposed to activities will be consumed involved? achieve? provide the or produced? capabilities? Capability Activity Define Resource Define Performer Define Define Capabilities Vocabulary Activities Vocabulary Resources Vocabulary Performers Vocabulary Items: Items: • Objectives Items: Items: • Roles • Features • Verbs •Nouns • Systems • Services • Actors Capability Process Data & Process View View Rule View View 11/17/2010 DWiz DoD DCMO BMA CTO & CA DoD BMA Architecture Methodology 21
    • Preparing and populating a modern information model and data store Ontology – Based California University of Pennsylvania Information Representation hasName DoDAF Wizdom graduatedFrom DBpedia Dennis Wisnosky university hasName (Wikipedia) hasName hasTitle hasName Dataset University of Dayton book University of Pittsburgh writtenBy Graph1 person Who wrote “DoDAF Wizdom”? Common Vocabulary in Action! 11/17/2010 DWiz DoD DCMO BMA CTO & CA 22
    • Preparing and populating a modern information model and data store Ontology – Based Information Representation Where was Dennis Wisnosky born? Graph2 hasName person yearOfBirth 19XX DoD HR bornIn Dataset locatedIn Dennis Wisnosky Washington Pennsylvania 11/17/2010 DWiz DoD DCMO BMA CTO & CA 22
    • Preparing and populating a modern information model and data store Information Merging California University of Pennsylvania hasName DoDAF Wizdom graduatedFrom DBpedia Dennis Wisnosky university hasName (Wikipedia) hasName hasTitle hasName Dataset University of Dayton book University of Pittsburgh writtenBy hasName person yearOfBirth 19XX DoD HR Dataset Graph3 bornIn locatedIn Dennis Wisnosky Washington Pennsylvania Wikipedia Dataset:Who wrote “DoDAF Wizdom”? DoD HR Dataset: Where was Dennis Wisnosky born? Combined Dataset: Where was the person who wrote DoDAF Wisdom born? 11/17/2010 DWiz DoD DCMO BMA CTO & CA 23
    • HR Enterprise Information Web (EIW) Implementing the capability by deploying business services • Building an HR Common Vocabulary that will make future integration and development simpler • Building an executable information model to provide accurate and timely enterprise Personnel Visibility for the first time • Making “compliance” (eg: SFIS, IRB, BEA) exercises simpler, faster, meaningful, easier to maintain Crawl, Walk, Run - EIW 11/17/2010 DWiz DoD DCMO BMA CTO & CA 25
    • Multiple Sources Single View HR EIW Implementing the capability by DMDC Data Stores deploying business HR services HR Data Store Data Store HR The HR EIW is a mechanism for Data Store Common Vocabulary DoDI Personnel reaching into service applications to Data Store satisfy enterprise HR information Component needs. It accomplishes three things: Data Stores mashup – Reports real-time, authoritative HR Data Data Data Data StoreStore Store Store information on-demand. – Supports HR enterprise External Data Services information standards. 9/09 – Supports IT flexibility. 6/10 12/10 9/12 9/15 Phase 1 Phase 2 Phase 3 Sustainment Increment 1 Publish Stds Transition Map OSD HR to Service Ontologies Proofs of Delivery Modeling Increment 2 Publish Stds Compensate Federated Ontology Increment 3 Publish Stds Develop, etc DIMHRS & CHRIS Alignment Publish Stds Increment 4-n Modeling RDF Store Delivered 18 Dec 09 EIW Roadmap Process/Rules Mgt SME RDF Modeling 12/31 RDF Info Services 3/31 Adv Mash-ups SPARQL Federation Sustainment 6/30 9/12 11/17/2010 12/10 26 DWiz DoD DCMO BMA CTO & CA
    • HR Domain Ontology Implementing the capability by deploying business services  Information discovery, interoperation, 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, we are in a position to have a knowledge-based web – Rich analytics • Requirements gap analysis • Authoritative Data Source discovery • Answer any Personnel & Pay question – Integrate and interoperate  RDF & OWL are the technology used to describe “things” – both machines and people can understand the descriptions 11/17/2010 DWiz DoD DCMO BMA CTO & CA 27
    • BPM Methodology Implementing the capability by deploying business services Goal: Develop correct, consistent, human and machine readable, high quality business process models BPMN Systematically Designed Architecture Primitives Guidance Products Approach: SME Feedback Input Output Process Artifacts Initial Semantic Models Input Output Collaboration takes place in CommonVocabulary.mil BP Modeler Questions SME Feedback Input Output BPM Informs Ontology Benefits: • Machine readable (queryable) business • Consistent, semantically aligned (end- to- processes end HR) business processes • Perform gap analysis • Communicate effectively with the • Standards based models result in fewer errors Services during implementation 11/17/2010 DWiz DoD DCMO BMA CTO & CA 28
    • Community Workspace: www.Common Vocabulary.army.mil https://www.commonvocabulary.army.mil/ui/groups/HR_EIW Implementing the capability by deploying business services Collaboration 10/28/2010 DWiz DoD DCMO BMA CTO & CA 29 29 11/17/2010 DWiz DoD DCMO BMA CTO & CA 29
    • HR EIW and H2R E2E Implementing the capability by deploying business services Personnel Visibility not possible if DoD doesn’t understand the Enterprise H2R E2E processes, information flows, data sources, integration points, standards and exceptions Eg: how does Need to know: the “Pay” where in E2E, process work which ADS, across DoD in semantics the E2E? (meaning) of data, and access 30 11/17/2010 DWiz DoD DCMO BMA CTO & CA
    • Backend PoD1 Architecture Implementing the capability by deploying business services S3 S4 Target DIMHRS Database Objectives Achieved: ETL Data Virt Web Service D S1 S2 DKO CAC Authentication App App ETL Server Data Virtualization M Server Server DV Server ETL Process D Firewall DMDC MOU C P&R HR Ontology Models DIMHRS Reuse DMZ Proxy Server HTTPS Port 443 for web traffic SOAP/XML XML File EIW POD: Transition Voluntary Retirement Web Service Call (bind) HTTPS DKO Port 443 open for web (1/1/2008 – 11/1/2009)* traffic to DMDC HTML 11/17/2010 DWiz DoD DCMO BMA CTO & CA 90 Day Deliverables – POD 1 31
    • RDF Warehouse Architecture (POD2) NIPRNet / Internet Host Network Implementing the capability by deploying business services SPARQL SPARQL Data Access Business Logic Presentation & HTTPS Wiki Content SPARQL Modeling User Agent (Web Browser) Web / Application Server SPARQL API Endpoint  Model Driven Analytics  Triple Store Schema Triples RDF Triple Store RDF Load RDF/ Relational Mapping SQL ETL (Semantic DIMHRS – HRTS2 Mapping) Scrambled DB Real Time Interface Batch Process 90 Day Deliverables – POD 2 Relational Data Source  Model Driven ETL API 11/17/2010 DWiz DoD DCMO BMA CTO & CA 32
    • RDF Web Extensibility (POD3) Implementing the capability by deploying business services NIPRNet / Internet DMDC Network Real Time Interface User Agent Batch Process (Web Browser) API SPARQL SPARQL Business Logic Data Access Presentation & SPARQL Wiki Content HTTPS SPARQL Modeling API SPARQL POD3 Goals Endpoint Web / Application Server • Support multiple triple stores • Map/Load/Query multiple data sources • Army (DIMHRS), USMC (MCTFS) • Model based ETL with COTS • Increase analytic capability API • Army & USMC data from single query Ontology Triples • Drill down by Service/Component Triple Store • Expand Transition queries (TBD) • Compensation queries (TBD) SPARQL Endpoint • Demo at least one report (TBD) • Scenario based demo (scenarios TBD) OWL + Relational Mappings Manual File Transfer (No System Interface) USMC Records (Relational) MCTFS ODSE – Data Scramble // USMC Test Records Ontology Triple Store Triples Scrambled (No PII) USMC Records Army + USMC (Triples) (No PII Allowed) ETL (Model Based) Army + USMC (Triples) Identical data loaded into DIMHRS – both triple stores. MCTFS ODSE Army Test Records Army Records (Relational) (No PII) USMC Network 90 Day Deliverables – POD 3 11/17/2010 DWiz DoD DCMO BMA CTO & CA 33
    • RDF Service “SPARQLizer” (POD4) – Deployment View Amazon EC2 (possible: ADCF Test Network) - Virtual Machines Real Time Interface HTTPS SPARQL Dashboards (Fusion) Derby DBMS Batch Process SQL Dashboard Cache, Geographic & API SPARQL Language Information (Public Domain) User Agent (Web Browser) DWR Service API Web / Application Server (m1.small) SPARQL SPARQL SPARQL Knoodl SPARQL Endpoint Google Maps SPARQL Mapping SPARQL Presentation & Business Logic File Wiki Content Endpoint Endpoint (CII) NIPRNet / Internet SPARQLizer SPARQLizer Mapping Knoodl File Visualization (CII) (ODSE) (ODSE) API Modeling Application Server Application Server SQL SQL Web / App Server (m1.large) Oracle DBMS Oracle DBMS Mulgara Triple Store Test Data: Test Data: Army (DIMHRS) Triples USMC (ODSE) Ontology (No PII) (No PII) API Scrambled USMC MCTFS ODSE Records Manual File Transfer Server (m1.small) Server (m1.large) Server (m1.large) (No PII Allowed) 11/17/2010 DWiz DoD DCMO BMA CTO & CA 90 Day Deliverables – POD 4 34
    • Operations – Country View: User Defined Query Use Case! 11/17/2010 DWiz DoD DCMO BMA CTO & CA 35
    • Semantics is a Team Sport: EIW Extended Team • BTA: Developer of the EIW • OUSD (P&R): Functional sponsor and owner of the HRM Enterprise Standards (HRM ES) & Common Human Resource Information Standards (CHRIS) • Joint Staff, COCOMs, OSD analysts: Future User Community • DMDC: Future hosting site for the EIW • DCMO: Oversight • DFAS: Assessing HR-related pay requirements for the EIW Military Services: Identifying ADSs, providing functional SMEs, & validating modeling 11/17/2010 DWiz DoD DCMO BMA CTO & CA 36
    • HR EIW Technical Summary! Many DoD and Industry Participants, Learning! Makes full use of Business Process Models Built on BPMN (OMG) Standard! Built with Open Source Software and Open Standards (W3C)! Ad Hoc and Standard Displays use ADS! Implemented in the ‘Cloud’! 90 Day Deliverables! Built on a Shoe String! 11/17/2010 DWiz DoD DCMO BMA CTO & CA 37
    • EIW and the Direction of DoD Solution Architectures Uniformly described BP Legend: W3C Open Standards models Relationship described in OWL Data Data described described in RDF in RDF DoD Authoritative Data User executes Source BP Acq Domain BEA Log Domain Federated Business User Agent Vocabulary Enterprise (Web Browser) Vocabulary Architecture (BEA) queried directly for: BP executes via BEA Real Prop Domain directly Vocabulary • Enterprise analytics NIPRNet / Internet • Compliance Fin Domain Vocabulary • IRB/portfolio management HR Domain Svc Member Vocabulary OUID 11/17/2010 DWiz DoD DCMO BMA CTO & CA 38
    • DoD Business Operations Semantic Landscape Provide Enterprise semantic Standards Upper Ontology foundation Semantic Semantic and mappings Data Mediation & RDF, OWL, to drive data Pronto, etc. Foundation Transformation integration Common (mediation & Vocabulary transformation) Systems & Services Interoperability Business Rules (W3C Rules Interchange Format for standard exchange of rules) Domain Ontologies Provide Shape and Control the semantics-based Business Transformation facts (RDF) and Intelligence: connections to Common Data Sharing Vocabulary (Ontologies) and Reporting Rules for machine Ad Hoc Query Transactional Transform reasoning Knowledge Exploration Data Stores RDF Triple Stores Achieving Net-Centricity: 02 PPT EIW is first BI realization of this Data Sharing 11/17/2010 DWiz DoD DCMO BMA CTO & CA 39
    • Agile, Architecture-Driven, DoD Business Capability Delivery Governance Policy , Processes, Tiered Accountability Model Data Common Architecture Methodology Implement Authoritative Data Sources Phased Implementations Common Vocabulary Semantic Technologies Agile Business Services Delivery Standard Representation and Composition Primitives and Design Patterns Model to Guide Transformation Data to Improve Performance Implement to Deliver Capabilities 11/17/2010 DWiz DoD DCMO BMA CTO & CA The One Takeaway 40
    • Thank you! Questions? Dennis.Wisnosky@osd.mil 11/17/2010 DWiz DoD DCMO BMA CTO & CA 41