Insights for Success - Ottawa, May 2013

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

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. DisclaimerNotice

3. 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. 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. Vision and Potential; EU and Japan • ◆ Not only further development of IT industry, initiatives seek tocreate… • ① New business created by the integration of IT & data and existing industries • ② New business created by the integration of different industries through IT & data New Business using IT & data NarrowIT Industry As real world data is added, the amount of available information increases significantly New Business created by the integration of IT and existing industries Expanding into multiple industries and business areas Construction Equipment Energy Agriculture Automobiles Robots Medical Equipment Healthcare Retail New Industries created by the integration of different industries through IT and data Energy×Automobiles×Transportation System Healthcare×Agriculture Robots×Retail×City Planning 5 Source: http://semanticommunity.info/@api/deki/files/21578/BrandNiemann02122013.pptx

6. Japan – DATAMETIPlan 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. Examples ofPublic Data ＜Stimulate the Economy＞ Revitalize economic and industrial activities ・Develop Information Service Deliver Better Service ・Edit & Process the raw data 　　　　　　　　　　　　　　→Create additional value Citizens Geological Map Economic Statistics ・Develop Applications ・Create useful Websites ・Build business online systems Business Operator ProvideRaw Data METI 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 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 policy Behind the hype and technology what is really being achieved? 7

8. 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. 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 Socrata data extract MySQL database Glassfish Open-XDX Prime Faces 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. 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. 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. Requisite Onboarding Flow Process

14. 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. Integrated Location Intelligence Location information integrated with BI to allow analysis of incident patterns, geographical hot spots. . Draw line around an area of interest and highlight all cases in area, and drill into details of a specific incidents.

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

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

19. 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. Dictionaries - Key Technology and Foundation Pillar NIEM Past and NIEM Future Lessons Learned NIEM + Information Alignment

21. 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. 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 NIEM Adoption DoD Chief Information Officer Teri Takai : Lt. Gen. Mark Bowman, Joint Chiefs of Staff CIO/J6 22

23. National Information Exchange Model (NIEM) Centralize - Joint DOJ / DHS / HHS program + DoD • 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 1

24. FEDERAL AGENCY COMMITMENTS

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. Community Technical Framework Support Framework Formal Governance Processes Data Model Tools for Development and Discovery Established Training Program Online Repositories XML Design Rules Mission-Oriented Domains Implementation Support Development Methodology Predefined Deliverables (IEPD) Self-Managing Domain Stewards 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 DOMAINSNIEM Government ResourceManagement Domain • NIEM Health Domain • NIEM Human Services Domain • DOMAINS IN PLANNINGNIEM Agriculture • NIEM Education • NIEM Transportation 27

28. 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. SOA View - Information Sharing Stack and Rules • NIEM: rules important; not just data Privacy and Policy Automation Privacy and Policy Automation Rules Identity and Access Management Business Process, Enrichment, Routing Rules Routing / Process Flow Standardized Metadata Identity, Access Control, Classifications Rules Common Vocabulary Validation Rules

30. 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. The 8 “D”s and NIEM NIEM IEPD Process • Design • Develop • Deploy • Document • Dictionaries • Discovery • Differentiate • Diagnose Repeatable, Reusable Process (Exchange Specification Lifecycle) *IEPD - Information Exchange Package Documentation

32. 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 Components Canonical Dictionary Collections Canonical XML Components Dictionary 1 XML User Inserts Navigation and Query Tools Relationship Lookups Component Associations and Couplings 2 Domains Reuse Library Exchange Templates and Rules 3 Artefact relationships Catalog Template Presentation Automatic Rendering Tools W3C Schema and Model Representations 4 Collaboration Services XML Schema Components Models Delivery Control, Messaging, Security Deployment Environments and Middleware 5 Testing Workbench, Rules Engine, Data Samples, Integration ETL Implementation Artifacts and Examples 6 33

34. 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 IEPDsdeveloped by an enterprise; collection of enterprise BIECs organized into a subset and one or more extension schemas

36. 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. Dictionary Management / Acquisition

38. 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 XML Technologies UML Technologies NIEM Components in Neutral Dictionary Representation Rules Technologies W3C Schema Tools HTML 5 rendering tools Semantic Representations Security solutions Middleware solutions 39

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

41. National Information Exchange Model (NIEM) Toolsfor enabling interoperability 1 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. 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 ACTIVITIES130,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 43 www.niemtrainingvideos.org

44. Summary Government Opportunities

45. 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. 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

48. Addendum Technology Resources

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

50. NIEM IEPD / Exchange Delivery Lifecycle Dictionaries Discovery Requirements Updates Design Drag and Drop Visual Designer Diagnose Develop XML Samples Exchange Templates Differentiate 1 Production Results XSD Schema Deploy Document 2 NIEM IEPD Reports 3 Validated Templates / Schema XMI / UML Models 4 Required IEPD artifacts Documentation 5