1 / 31

Smart Lean Government Life Events

Smart Lean Government Life Events. Rick Smith Cory Casanave. Agenda. Outline of the elusive Data Issue Concept of Life Events I2F Exchange Patterns with Life Events Ontology Life Event Fit with ISE I2F Secure Information Exchange Gateway with Life Events Life Events Benefit Summary

mimis
Télécharger la présentation

Smart Lean Government Life Events

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Smart Lean Government Life Events Rick Smith Cory Casanave

  2. Agenda • Outline of the elusive Data Issue • Concept of Life Events • I2F Exchange Patterns with Life Events Ontology • Life Event Fit with ISE I2F • Secure Information Exchange Gateway with Life Events • Life Events Benefit Summary • Appendix One – Linked Open Data proposal example for Architectures and Data • Appendix Two – EU OnestopegovReference Documentation

  3. The Requirement • Data continues to be the unsolved problem because services have been harder to create, implement, and deliver and data is the service provider’s problem • Success in providing Mobile computing is: • Understanding the User Experience with the device and their activities • Capturing the data required • Identify and isolate it in the legacy environment • If not found create it • Design a life cycle storage, usage, and aggregation to fit the citizen/business Life Events requirements • For data services: • Understand the citizen/business needs • Identify the data required • Find it locally • Create what’s missing (crowd sourcing, demonstrate the value to the individual, etc. • Organize the resulting data/information • Provide an exchange capability/facility so that all 5 tiers of government can access and provide the required services without regard to programs or other artificial boundaries

  4. Our Solution: Life Events

  5. Life Events Definition • A Life Event (LE) is a common registration/request incident for a citizen or business that requires interaction with government Community of Services (COS)s, such as giving birth, registering for school, obtaining a business license, or registering to lobby Congress. A Life Event can trigger responses within a wide spectrum of government and non-government entities and once triggered, key information obtained during submission or review is migrated to all subsequent relevant forms and records. These Life Events can be collectively be considered a life cycle of events which form a permanent record(s) until formally closed. The majority of Life Events are created at the local level of government and are referenced, compiled, combined, or divided up for further use by higher level government entities

  6. Principles for LE • Citizen/Business as focus for LE • Proactive support for Citizen, Business gathering all relevant possibilities for the ontology • Anticipatory in nature – government making citizens /business aware of : • services and opportunities based on dates, needs, conditions • Inform the requestor of status of event actions • Focused on the Request for service not the current government delivery capability • Cross bureaucratic/program sharing or/ exchanging of information • Developed from the ontology specifics gathered by detailed focus on service request requirements • Use a Salesforce.com like tool to crowd source data • Citizen/Business can manage and control pervasiveness. • As well as using SaaS to develop services on the fly • Private and Secure • Uses Semantic Web exchange where Life Events can be generated real-time through metadata • My Government.com • Multi-channel outreach

  7. Life Event using Passports as Example Request Passport from State authorizing Life Event usage State requests Life Events from all Life Event holders State issues / denies passport and updates Life Events Life Events for Life Events for State processes Life Events through Passport “filters” State completes or rejects Passport Current Process Target Process

  8. Life Event Fit with ISE I2F – Positioning Life Events within I2F

  9. Inside I2F Components • Mission Space • Operational Capabilities: references “Current State” Implementations of functional and technical services coupled with the appropriate policy, process, training, outreach, and other infrastructure components • Common Practice and Terms • Technical Standards: specific to the development and implementation of information sharing capabilities into ISE systems • Technical Capabilities: detailed technical descriptions such as data and metadata that enable the efficient, secure, and trusted application of the ISE business processes and information flows to share information • Exchange Patterns: repeatable sets of tasks that help accomplish a commonly occurring need for exchange of data or information between two or more partners • Reuse and Shared Capability • Exchange Specifications: is the instantiation of an exchange pattern, and once implemented correctly enables interoperability Build Life Events Profiles from EU models

  10. New Exchange Patterns are created from Life Events enhanced SIM Life Events “Exchange” Alerts, Broadcast and Notifications Query Response A B A C D Workflow Life Events Exchange becomes the workflow and aggregation of the Local data and repository for the Life time of the citizen/business built by a SIM created from I2F Choreography and Coordination

  11. Modified I2F Table for Reference Architectures

  12. I2F Use – Building Interoperability into Mission-Based Reference Architecture(s) • Coordinate interoperability artifact descriptions • Identify artifacts relevant to interoperability and information sharing • Ex., Data Domain - builds on the operational context and defines why information needs to be exchanged. Technical standards are enablers that provide the vocabularies for sharing to assure that the semantic meaning and the context of the data is not lost during transition and transformation. Technical capabilities provide the architectural context within which the exchange is executed. All of these components focus on the interoperability framework. The actual data constructs define the data exchange content model and includes: • Mechanism for identifying and categorizing candidate assets for sharing • Framework for capturing data elements and the relationship between them (semantics) • How the data is structured, what standards are used, and how data/information can be exchanged so users are able to both have access to and use the data/information • Technical standards to design and implement information sharing capabilities into ISE systems • Approach for documenting exchange patterns • Data/information flow to include the tagging of the data, discovery, and retrieval • Principles, roles, and responsibilities for data management and stewardship

  13. I2F Integrated Landscape View w/ Life Events Life Events Ontology

  14. Secure Information Exchange Gateway with Life Events • Diagrams

  15. Example Gateway Configurations Information Provider Provider’s Gateway Trusted Space Web Browser Gatelet Life Events Application Interface API Gatelet Online User Mapping Inerpol Gatelet others Workflow GANG Data SQL DBMS SQL Gatelet NIEM/Global Gatelet GANG IEPD Port Rules Policies & Models GANG DataExchange Consumer’s Gateway Consumer System Life Events NIEM/Global Gatelet Trusted Space GANG IEPD Port Mapping CSV File Exchange CSV Gatelet GANG Data Workflow NLET IEPD Port Rules others Policies & Models

  16. System Specific Data Structures User Life Event Reference Concept System A DBMS “Passport ID: String” Mapping Unified View Passport Number System B NIEM IdentificationType: PassportIDText Mapping

  17. Live Event Model Information Ontology Secure Information Sharing Gateway Data Mapping Drives Workflow Runtime Infrastructure Federated Repository Business Rules Portal Security & Privacy

  18. Life Event has same Audience as ISE • Life Events because of their discrete nature and ability to be combined as ongoing services representing different functions of government (Justice, Law Enforcement, Travel, Taxing, etc. across all 5 tiers of government) allow all LE producers (Government managers, program executives, local government data records, etc.) and all individuals and organizations (consumers) to create/utilize services with integrated LEs (passport, SEC registrations, Interpol, etc.). • Next slide is an example of Passport issuance which serves a single life with an unknown number of Life Event checks to provide data.

  19. Life Events Benefits: • Life Events become the organizing criteria for data gathered about citizens and businesses • Instead of siloed programs focus, Life Events aggregate all data relevant to the event and store it as connected to the citizen/business as well as the program • Primary benefits, other than speed, accuracy, and availability from building government services using LEs will be derived from having a well-defined LE governance process across public sector boundaries (tribal, local, state, and federal), a minimum LE common format, availability for LE life cycle access and line of sight by all responsible agencies, elimination of duplicate government record keepers and administrative overhead and faster turnaround from application to delivery of government services to all. LE combined with COS and SIM should allow for realization of the promise of e-Gov.

  20. Life Events Way Ahead • Growing demand by government for integrated Education, Economic, Public Health, Public Safety information to understand future for planning purposes • Need citizen/business focus granularity to properly plan • Need for a citizen or business to have unique record(s) of all their activities • Focused on citizen/business cumulative activity not collection of singular events • Organized with common vocabulary/ontology • Cross jurisdictional • Integrated with geospatial, social media, web 2.0 etc. • Becomes an open source repository that will prevent $ 30 B EHRS because data captured represents the consumer not the program servicer • They have different needs and desired outcomes • Need for Community of Service across 5 tiers with access to LEs • Access, create, modify, inform LEs • Communicate through data exchanges to linked LEs • This will provide real service!!!

  21. Summary • Recommendation is to: • Do a small pilot with IJIS and New Jersey to create 2- 3 Life Events, go after the local data to create Life Event using material in D 13 • Build the CoS workflow from D 13 • Test

  22. Appendix 1 • EU Resource Repository

  23. OneStopGovPublic Deliverables

  24. OneStopGov Publications

  25. OneStopGov Restricted Documents

  26. European Union (2002- 2008) Created Life Events (citizen and business) eGOV • Definition of Citizen and Business Life Events data models • Can be built from existing local data • Organized using GOVml an XML based vocabulary/ontology of Life Events • GOVml is XML so there is no translation needed • EU crated LE but focused on portal processes which we recommend be networked • We can create data exchange linkages • Using NIEM with meta data extensions for LE additions • Create up front Ontology maps for LEs that are part of CoS • Can also used Semantic Web linked data inputs • Allow local and state interchange with Federal services • Must redefine services from Agency Program dictates to Citizen/Business life event needs • Local data must be examined to verify tha it has all data needed for LE and CoS • Crowd sourcing or some systems needs to be put in place to get accurate and up-to-date data • Standard eGov portal connection can be networked • Use OneStopGov reference library to create a working model or subset for USA • Reference Models • Use Cases • Ontologies • Workflow • Platform and network Architecture

  27. EU Requirements to Model Life events • EU hierarchy • Life Event • Public service • Document (input and output) • Citizen or business as the main actor or user • User Profile • USA Hierarchy • User Profile • Citizen/Business as main actor • LE documents • Cross government sourcing • Produce LE

  28. Appendix 2 Team We have the opportunity to bring together a world class team of known experts to achieve these goals 29

  29. Technical Team Resources Cory Casanave – Thought leader in architecture, meta modeling, open source, standards and semantic integration– experienced tool developer who will lead the effort Ed Seidewitz – World class architect and expert in UML, Executable UML, meta modeling, standards and development who will be the chief architect of the future modeling capability Tom Digre – World class architect and developer focused on knowledge integration and provisioning who will lead the development of core capabilities Jim Logan – World class modeler/architect, UML authority and Data/Information expert who will bring together diverse viewpoints into a common model Elisa Kendall – World class Ontologist and tool developer who will provide the semantic integrity for the solution Rick Smith – Thought Leader, business solution architect, and co-lead of the IAC Smart Lean Government project to provide a new methodogy for 5 tier government shared services for citizens and business Others… 30

  30. Team Availability These world class experts are available now and motivated to take on a challenge like this today, however, availabilitycan not be guaranteed in the future without sponsorship. Other highly qualified potential team members are also available. 31

More Related