1. Insights for Success - Ottawa, May 2013 David Webber, Information Architect, Oracle Public Sector - Information Transparency - Civic Engagement - Information Collaboration - Innovation

2. The following is intended to outline Oracle general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Disclaimer Notice Slide 2

3. © 2011/12/13 Oracle Corporation – Restricted Distribution3 Agenda Improving Transparency, Performance, and Enabling Civic Engagement Through Intergovernmental Collaboration and Innovative Technology – From the customers’ viewpoint, David will share recent NIEM* successes, along with the technical and political challenges along the way. Being both a strong proponent of open source and having developed a number of world leading solutions himself prior to joining Oracle, he presents an objective perspective of what it takes to effectively leverage SOA to achieve intergovernmental collaboration objectives and successfully roll out new services – Open Data; what you need to know – Open Source; what you can deliver today – Innovations; what we are working on What this all means: better services and economic opportunities for citizens *NIEM – National Information Exchange Model

4. © 2011/12/13 Oracle Corporation – Restricted Distribution4 Technology Landscape Open Data – Open Data Introduction, Solution Architecture and Tools Information Alignment – Dictionaries - Key Technology and Foundation Pillar NIEM Development Life Cycle – NIEM Concepts, Tools and Adoption, SOA Summary – Opportunities for Government *NIEM – National Information Exchange Model

5. © 2011/12/13 Oracle Corporation – Restricted Distribution5 5 Vision and Potential; EU and Japan 5 ◆ Not only further development of IT industry, initiatives seek to create… ① New business created by the integration of IT & data and existing industries ② New business created by the integration of different industries through IT & data As real world data is added, the amount of available information increases significantly Expanding into multiple industries and business areas New Business using IT & data New Business created by the integration of IT and existing industries New Industries created by the integration of different industries through IT and data Narrow IT Industry Automobiles Construction Equipment Medical Equipment Energy Retail Robots Healthcare Agriculture Energy×Automobiles ×Transportation System Healthcare×Agriculture Robots×Retail×City Planning Source: http://semanticommunity.info/@api/deki/files/21578/BrandNiemann02122013.pptx

6. © 2011/12/13 Oracle Corporation – Restricted Distribution6 Japan – DATA METI Plan As part of approach to develop “Leading-Edge Integrated Industries”, METI intends to actively release public data in formats that facilitate reuse under the clear set of reuse rules. ＜ Stimulate the Economy ＞ Provide Raw Data ・ Edit & Process the raw data →Create additional value ・ Develop Applications ・ Create useful Websites ・ Build business online systems ・ Develop Information Service Citizens Business Operator Revitalize economic and industrial activities METI Deliver Better Service Examples of Public Data Geological Map Economic Statistics Source: http://semanticommunity.info/@api/deki/files/21578/BrandNiemann02122013.pptx

7. USA - Background "Open Data is the new default… anywhere, anytime on any device, and everything should be APIs" Steven VanRoekel Federal CIO – Whitehouse Digital Strategy Architect Behind the hype and technology what is really being achieved? Along with its Open Data Policy, the White House unveiled May 9 Project Open Data, a GitHub-hosted tool kit it hopes will be the living, breathing implementation arm of its policyOpen Data Policy Project Open Data 7

8. © 2012/13 Oracle Corporation – Restricted Distribution8 Decoding the Digital Strategy What exactly are Open Data APIs? How can Oracle solutions support them? What does a solution architecture look like? How does this align with NIEM*? What technology pillars and tools are there? *NIEM – National Information Exchange Model

9. © 2012/13 Oracle Corporation – Restricted Distribution9 Open Data APIs explained A way, via the internet, to securely deliver information between entities and systems API – Application Programming Interface Security is supported along with roles and permissions for requestors, e.g. – Public information – such as road works, health services, voting – Private information – patient data, student data, company data

10. Example – Chicago Pharmacy Vaccines Search http://www.verifyxml.org 1.Socrata data extract 2.MySQL database 3.Glassfish 4.Open-XDX 5.Prime Faces 6.Hosting site Combines: rapid development paradigm; open data approach; open source tools; RESTful web services; community based resources and delivery; NIEM-aligned information feeds. 10

11. © 2012/13 Oracle Corporation – Restricted Distribution11 Oracle Open Data Solution – Open-XDX Open-XDX is an all new component designed to deliver rapid Open Data APIs Integrates into Oracle Fusion Middleware foundation and Database products Uses XML configuration templates and code-less methods and open source NIEM tools Allows plug-and-play delivery for Oracle customers and applications

12. © 2012/13 Oracle Corporation – Restricted Distribution12 Example – Military Applicant Onboarding Need to examine the applicants health history and particularly prescriptions 1 in 5 high schoolers today are abusing prescriptions Drug use leads to at-risk military personnel from in- theatre adverse reactions and post-traumatic stress Nationally States are looking to share pharmacy records to reduce prescription abuse, pill mills and rogue doctors In California 80% of prescriptions are for non-residents DOJ / BJA PMIX program – Prescription Medication Information eXchange – using NIEM

13. © 2012/13 Oracle Corporation – Restricted Distribution13 Requisite Onboarding Flow Process

14. © 2012/13 Oracle Corporation – Restricted Distribution14 Medical Authority Role Combines: SOA; BPM; Semantic tools; Secure web services; community based resources and delivery; NIEM-based information exchanges.

15. PMIX Background Scale of the exchange challenge 15

16. © 2012/13 Oracle Corporation – Restricted Distribution16 Integrated Location Intelligence Draw line around an area of interest and highlight all cases in area, and drill into details of a specific incidents. Location information integrated with BI to allow analysis of incident patterns, geographical hot spots.. Location information integrated with BI to allow analysis of incident patterns, geographical hot spots..

17. Example – Government Financial Transparency http://www.checkbooknyc.com/spending_landing/yeartype/B/year/114 Coming soon: PeopleSoft data integration via Open-XDX APIs… 17

18. Sharing Source Code - GitHub https://github.com/VerifyXML 18

19. © 2012/13 Oracle Corporation – Restricted Distribution19 Applicability to Government Challenges Cost of building information exchanges – Reduction of development sunk costs through minimizing coding tasks – Allowing rapid prototyping and proof of concepts (agile development) – Flexibility - dynamic adaptable templates instead of rigid fixed code – Reuse – templates for common systems / solutions easily shared and adapted Government transparency and public information sharing – Structured content from data stores – e.g. election results reporting, monthly cost reports, scheduled road maintenance; obvious metadata and semantics – Simple search requests on data – e.g. part numbers, codes, licenses lookup – Not intended for unstructured and textual content document delivery Practical real world data sharing anywhere – Direct simple tool with short learning curve and plug and play deployment

20. NIEM + INFORMATION ALIGNMENT Dictionaries - Key Technology and Foundation Pillar NIEM Past and NIEM Future Lessons Learned

21. © 2012/13 Oracle Corporation – Restricted Distribution21 Who steers NIEM currently? Founders and Voting Members Dept of Justice Dept of Homeland Security Dept of Health and Human Services Ex-Officio Members Global Justice Information Sharing Initiative Office of Management and Budget Program Manager, Information Sharing Environment (ISE) NASCIO Partners Terrorist Screening Center Dept of Defense / Dept of Navy Dept of State, Consular Affairs (invited)

22. DoD NIEM Adoption NIEM military domain “will support development of information exchange specifications across the full range of military operations.” NIEM will be used unless component can show compelling reasons DoD Chief Information Officer Teri Takai : Lt. Gen. Mark Bowman, Joint Chiefs of Staff CIO/J6 22

23. © 2012/13 Oracle Corporation – Restricted Distribution23 National Information Exchange Model (NIEM) Centralize - Joint DOJ / DHS / HHS program + DoD 11  Created a centralized organization to promote standardization of information exchange for cross jurisdictional information sharing.  NIEM’s governing structure is comprised of Federal, State, Local, Tribal and private organizations. NIEM is managed at an executive level by the Department of Homeland Security (DHS), Department of Justice (DOJ), and Department of Health and Human Services (HHS) + DoD

24. FEDERAL AGENCY COMMITMENTS 24 AGENCYUSE OF NIEM Department of AgricultureCommitted to Use Department of DefenseCommitted to Use Department of EducationCommitted to Use Department of EnergyCommitted to Use Department of Health and Human ServicesCommitted to Use Department of Homeland SecurityCommitted to Use Department of Housing and Urban DevelopmentCommitted to Use Department of JusticeCommitted to Use Department of LaborCommitted to Use Department of StateCommitted to Use Department of the InteriorCommitted to Use Department of the TreasuryCommitted to Use Department of TransportationCommitted to Use Department of Veterans AffairsCommitted to Use Environmental Protection AgencyFurther Evaluation Required General Services AdministrationCommitted to Use National Aeronautics and Space AdministrationFurther Evaluation Required National Archives and Records AdministrationCommitted to Use National Science FoundationCommitted to Use Nuclear Regulatory CommissionWill Not Use Office of the Director of National IntelligenceCommitted to Use Social Security AdministrationFurther Evaluation Required Geospatial Line of BusinessWill Not Use Grants Management Line of BusinessFurther Evaluation Required Financial Management Line of BusinessCommitted to Use Human Resources Line of BusinessCommitted to Use

25. The NIEM Framework NIEM connects communities of people who share a common need to exchange information in order to advance their missions, and provides a foundation for seamless information exchange between federal, state, local, and tribal agencies. Much more than a data model, NIEM offers an active user community as well as a technical and support framework. Formal Governance Processes Online Repositories Mission-Oriented Domains Self-Managing Domain Stewards Data Model XML Design Rules Development Methodology Predefined Deliverables (IEPD) Tools for Development and Discovery Established Training Program Implementation Support Help Desk & Knowledge Center

26. The NIEM Data Model NIEM’s data model is a set of common, controlled, and approved XML data structures and definitions vetted through the Federal, State, Local, Tribal and Private Sectors. Data elements are organized into core and domain-specific components Core components are used by multiple domains and can be described by structure, semantics, and definition universally Domain-specific components are continually updated by subject matter experts that are actual NIEM participants and industry experts for their particular domain NIEM Naming and Design Rules (NDR) specify how each of these components are defined and utilized

27. NIEM’s Domains View NEWEST DOMAINS NIEM Government Resource Management Domain NIEM Health Domain NIEM Human Services Domain DOMAINS IN PLANNING NIEM Agriculture NIEM Education NIEM Transportation 27

28. © 2012/13 Oracle Corporation – Restricted Distribution28 NIEM Past and Present Challenges Vertical domain vocabulary for DHS and DOJ One dozen domain dictionaries Technology limited - built using XSD schema Core components highly contextual to DHS/DOJ Surprisingly – no actual logical models of information! Gap with semantic technologies integration Limited data content rules and code lists Mapping automation support missing Multi-year development life cycles

29. © 2012/13 Oracle Corporation – Restricted Distribution29 SOA View - Information Sharing Stack and Rules Privacy and Policy Automation Identity and Access Management Routing / Process Flow Standardized Metadata Common Vocabulary Validation Rules Business Process, Enrichment, Routing Rules Identity, Access Control, Classifications Rules Privacy and Policy Automation Rules NIEM: rules important; not just data

30. © 2012/13 Oracle Corporation – Restricted Distribution30 NIEM is still improving… Collections of complex XML Schema Verbose components Embedded context in names Currently facing significant scaling challenges – Inconsistencies; too much manual management; slow lifecycles Dictionary technology incubating Enhanced code lists mechanism incubating UML profile is evolving initiative with OMG – Attempt to marry modelling techniques and XSD Schema syntax Policy and Security mechanisms incubating Need to embrace enabling tools for rapid expansion of domains and community collaboration

31. © 2012/13 Oracle Corporation – Restricted Distribution31 The 8 “D”s and NIEM Design Develop Deploy Document Dictionaries Discovery Differentiate Diagnose Repeatable, Reusable Process (Exchange Specification Lifecycle) NIEM IEPD Process *IEPD - Information Exchange Package Documentation

32. © 2012/13 Oracle Corporation – Restricted Distribution32 Integrating into your existing processes and control Critical to manage and steer use of NIEM Ensure business outcomes match requirements Lessons learned with NIEM – The earlier in the software development process that NIEM is introduced the better the overall outcomes – Each step has deliverables – business plan, delivery architecture, data model, alignment reports, schema, test results that can be monitored in your SDLC* – Monitoring products reinforces reuse as best practice – Tools essential in review processes Collaboration tools can coordinate artifacts across projects and participants Test bed tools and open APIs reduce integration alignment costs *SDLC – Software Development Life Cycle

33. Dictionaries: Key Pillar of Information Sharing Canonical XML Components Dictionary 1 1 Component Associations and Couplings 2 2 Exchange Templates and Rules 3 3 W3C Schema and Model Representations 4 4 Delivery Control, Messaging, Security 5 5 Presentation Collaboration Services Artefact relationships Implementation Artifacts and Examples 6 6 Navigation and Query Tools Domains Reuse Library Components Automatic Rendering Tools Deployment Environments and Middleware XML User Inserts Relationship Lookups Template Catalog Testing Workbench, Rules Engine, Data Samples, Integration ETL Schema XML Models Component s Canonical Dictionary Collections 33

34. © 2012/13 Oracle Corporation – Restricted Distribution34 Developing domain dictionaries (EIEM) Allows domains to manage their components libraries Provides consistency for project development teams – Sets of NIEM consistent XML exchange components – Aligned to enterprise data stores – Optimized for reuse and interoperability Save time and effort across the enterprise – Perennial question for developers – when should I use NIEM components, and when our own local ones? – Are there components already available for that purpose? Provide formal mechanisms and procedures to share components and collaborate across SDLC process Provide external parties consistent data views *EIEM – Enterprise Information Exchange Model

35. EIEM/BIEC Business Information Exchange Components (BIEC) – NIEM-conforming XML schema data component definition that meets a particular recurring business requirement for an enterprise Enterprise Information Exchange Model (EIEM) – NIEM-conforming schemas that define data components to be reused in IEPDs developed by an enterprise; collection of enterprise BIECs organized into a subset and one or more extension schemas

36. © 2012/13 Oracle Corporation – Restricted Distribution36 Available Dictionary Tools CAM toolkit provides a rich set of tools to create and manage dictionaries – Bottom up harvesting of existing information assets – Top down modelling and engineering – Reuse scoring and comparison reporting Dictionary aligned with UN/CEFACT CCTS work – Supports concepts and model – Component renamer supports NIEM Naming and Design Rules Practical solution - supports desktop tools – Support for Excel spreadsheet importing and exporting – Can generate UML models – Works with simple Mindmap rendering Dictionary Collections – Create collaborative shared sets of dictionaries

37. © 2012/13 Oracle Corporation – Restricted Distribution37 Dictionary Management / Acquisition

38. © 2012/13 Oracle Corporation – Restricted Distribution38 Value Proposition Allow business data analysts to focus on information needs and build data exchanges Aligns information with industry standards and enterprise information stores Ensures consistent usage and definitions using profile of syntax-neutral terms and constructs Components can be derived from existing domain schema and data structures Supports providing sharing and collaboration services Allows development of supporting analytics tools

39. The Vision NIEM Components in Neutral Dictionary Representation UML Technologies XML Technologies W3C Schema Tools Semantic Representations Rules Technologies HTML 5 rendering tools Security solutions Middleware solutions 39

40. NIEM DEVELOPMENT NIEM Concepts, Tools and Adoption Information Exchange Life Cycle (IEPD)

41. © 2012/13 Oracle Corporation – Restricted Distribution41 National Information Exchange Model (NIEM) Tools for enabling interoperability 11 Provides the tools for enabling interoperability at the data layer within and across systems supporting information sharing, while preserving investments in current technology and optimizing new technology development. COMPLEXITY multiple disconnected components + closed coded

42. © 2012/13 Oracle Corporation – Restricted Distribution42 CAM Toolkit (http://www.cameditor.org) Minimal learning curve for practitioners Provide technology neutral methods, tools and techniques Leverage visual metaphors – WYSIWYG Business Rule Validation Conformance Test Suites SQL data mapping / XML generation (code-free methods) Creates technical artifacts needed for a NIEM IEPD Deliver the NIEM domain and core component sets in format that can be quickly adapted and reused SIMPLICITY integrated components + visual metaphors + open source

43. CAMeditor.ORG Project Statistics SNAPSHOT OF PROJECT ACTIVITIES 130,000+ CAMeditor.org page visits to site 165+ countries have downloaded tools; 30% of visitors are from U.S.; 700+ downloads weekly 2000+ student views of online video training resources 8 languages now available www.cameditor.org www.niemtrainingvideos.org 43

44. GOVERNMENT OPPORTUNITIES Summary

45. © 2012/13 Oracle Corporation – Restricted Distribution45 Key Technology Needs Delivering on the Open Data Digital Strategy Vision for government Open Standards and Open Source based Plug and play with code-free templates and rapid development Supports NIEM and Open XML exchanges Leverages deployed technology today Workflow integration Dictionary component management Secure messaging delivery and partner management Delivered across-platform and device End-to-end security & governance

46. © 2012/13 Oracle Corporation – Restricted Distribution46 Opportunities / Challenges Open Data movement – delivering on promise of government transparency Enabling next generation digital economy and information sharing Providing improvements and efficiencies for intra- government information sharing Integration into SOA delivery stack International collaboration on information standards

47. ©2012 Oracle Corporation 47

48. ©2012 Oracle Corporation 48 TECHNOLOGY RESOURCES Addendum

49. ©2012 Oracle Corporation 49 Payload XML/JSON Data Exchange Open XDX - Conceptual Overview Existing Information Databases SQL Open Data XML Open-XDX SQL Rapid Deploy JDBC connection Control template contains information of the exchange structure design and DB mapping rules of data tables and columns Template Structure Rules DB Mappings Parameters Configuration Packaging Delivery Service API Send RESTful Webservice (WADL) or SOAP (WSDL)

50. © 2012/13 Oracle Corporation – Restricted Distribution50 NIEM IEPD Reports DictionariesDictionaries DiscoveryDiscovery NIEM IEPD / Exchange Delivery Lifecycle DiagnoseDiagnose DifferentiateDifferentiate DesignDesign DevelopDevelop Validated Templates / Schema Validated Templates / Schema XSD Schema XML Samples XMI / UML Models Production Results Production Results Requirements Updates Requirements Updates Document ation Drag and Drop Visual Designer DocumentDocument DeployDeploy Exchange Templates Exchange Templates 1 1 2 2 3 3 4 4 5 5 Required IEPD artifacts

51. © 2012/13 Oracle Corporation – Restricted Distribution51 IEPD Delivery Tasks / Tools Matrix CAMCAMV Open-XDX (OPX) Exchange Schema Development X Canonical Model Development / Generation X Exchange Schema Generation X NIEM Compliance Checking / Reporting X WSDL / JAXB Binding Generation X Operation Message Test Case Generation X Production Services Message Generation X SQL Schema Mapping XX NIEM IEPD Artifact Generation X - Cross-reference spreadsheet X - UML model X - Business Rules Report X - XSD schema package X Conformance Test Suite X Run time XML instance validation X In order to be NIEM-conformant, the IEPD must adhere to: 1.NIEM Conformance Document 2.NIEM Naming and Design Rules (NDR) v1.3 3.NIEM Model Package Description (MPD) Specification v1.0

52. © 2012/13 Oracle Corporation – Restricted Distribution52 XML Technology Components NIEM: need to manage complete aspects of exchange delivery, not just the structure and content data model

53. Swim Lane View UML Technologies XML Technologies W3C Schema This is what NIEM exchanges are delivered with on-the-wire! UML XMI XSD Namespace Enumerations XSLT XQuery XPath XML Patterns Associations Cardinality Stereotypes Inheritance Facets Elements Attributes Content Complex Types Audience: Data Modellers / Designers Audience: Software Developers and Middleware Engineers Audience: General content delivery and applications; content engineers; rules representation systems; multimedia delivery; geospatial systems Objects WebWeb HTML JavaScript JSON REST SQL SOAP Audience: Web application developers Open-XDX 53

54. © 2012/13 Oracle Corporation – Restricted Distribution54 Dictionaries Semantics Approach Abstract dictionary representations with strong semantics, rules and code lists support Schema, models, documentation are generated from dictionary definitions automatically Contextual mechanisms allow linear number of true core components – not exponential growth Easier for practitioners to leverage with more predictable and repeatable results Enable domain use horizontally across government ETL mapping automation support Continuous collaboration environment