HAA: okt 2003 EPR ( E lectronic PR ocesses) A new METHODOLOGY standard (abstraction technique) for Integration and coordination of internal processes and e-business in GOVERNMENTS 21/ Hans A. Aanesen EPR-Forum

HAA: okt 2003 Focus Areas The business objectives of EPR projects include: Enhanced data capture quality Quality in customer service and documentation of work done Efficiency and quality in administrative work, with reuse of information Effective cooperation and interoperation within an organization and between organizations Data support that benefits all employees Integration of legacy systems and overall presentation for the users Electronic supervision of services and delivery (see for videos of project examples)

HAA: okt 2003 Goals The aim of this standard is to describe how application solutions can be organized in a unified way. The standard describes how: information is presented to the users tools and supporting materials are implemented communication with legacy systems will take place roles, processes and routines will be organized general functions can be standardized and shared

HAA: okt 2003 The EPR standardization work EPR Basic standardization NTS Secretariat of IT-standards => CEN /ISO organized by NTS NTS-K 189 committee in Norwegian Technology standardization The EPR superstructures Abstraction and Metaphor fundaments The realization of the EPR standard based on common international XML components: ( - Choice Points for e-Business (Agent: Linking & Switching ) - Web Services (National-UDDI, WSDL, SOAP) - ebXML (UN/CEFACT, EDI etc) OASIS Business-Centric Methodology TC OASIS e-Government TC eprXML: EPR - engine specification ( eGov Freeware) (The Superstructure implementation)

HAA: okt 2003 EPR implementation pilots (Sector standardization organized through EPR-Forum) ProFor: Innovation Program in Governmental sector ( Blue light program) 2 Pilots : - Home based Health & Care services ( Integrated planning and reporting inside its COI) - Digital Building & Construction Office for service handling ( electronic co-operation inside its COI ) COI = Community Of Interest

HAA: okt 2003 EPR is the road ahead to ”Open”, Including and Service organized collaboration in Real time without introduction of new Technology EPR The EPR superstructure opens up quite new Methods in the way to integrate different legacy systems and construction of generic linked and switched e-Business processes

HAA: okt 2003 Construction and Integration of Business processes and logic By help of Folder structure metaphors NB ! EPR methodology is setting the specification requirement in how to integrate Legacy Systems. Done on EPR terms and not on Legacy System terms EPR is based on FREEWARE ! EPR Superstructure organisation

HAA: okt 2003 eprXML EPR’s Hybrid Portal technology based on a a Service Oriented Architecture organized by help of modern a Service Oriented Architecture organized by help of modern XML abstraction technique

HAA: okt 2003 Hybrid Portal technology: Content Management (competing frameworks) : Apache SOAP:Open Source.NET Microsoft ONE O pen N et E nvironment Sun WebSphere IBM WebLogic BEA MySAP SAP.MAC Apple etc Portal role assignment by help of PKI PRESENTATION: HTML PORTAL: Portal superstructure Service Oriented Architecture (SOA) with Web Services UDDI WSDL SOAP Common Mapping (Abstraction) META Object modeling EPR content organization: XML ROLES LEGACY SYSTEMS

HAA: okt 2003 “Locked” System integration “Locked” System integration Integrated on legacy systems terms IT organized structure ( HW+SW+ Infrastructure ) Bottom Up Approach Ministry X Ministry A Company 3 Ministry C Ministry B Company m E-Gov LOCAL administration E-Gov REGIONAL administration E-Gov CENTRAL administration Company 1 Company 2

HAA: okt 2003 Hybrid SOA integration Hybrid SOA integration : Open Integration based on EPR organized mapping Service organized structure (Users + ServiceProviders) Top Down Approach Ministry X Ministry A Company 3 Ministry C Ministry B Company m E-Gov LOCAL administration E-Gov REGIONAL administration E-Gov CENTRAL administration Company 1 Company 2 Intranet/Internet SOAP -messages XML EPR Folder System UDDI Service Interpretation Center ServiceCatalog: EPR Folder Structure WSDL Interface WS n WSDL Interface WS 1 WSDL Interface WS 2 WSDL Interface WS 3 WSDL Interface WS 5 WSDL Interface WS 4 EPR integration module:

HAA: okt 2003 Breaking up Today’s Proprietary Data Systems and enabling Object Modeling Integration ( Technology & Platform independent mapping ) by help of WS: ”THIN” Clients: Intranett/Ethernet Internet – Accountancy – Salary – Payment – Order – Invoicing – Inventory – Purchase – Sale – Logistic – Transport – etc – Reporting – Control/Supervision – Custom – Tax – VAT – Transport – Fleet management – Bank services – etc INTERNAL BUSINESS PROCESSES: EXTERNAL BUSINESS PROCESSES : Service Part with Business logic: - ebXML - ”eprXML” Mapping : - Data variables - Methods - Scenarios SOAP/XML HTML / XML Catalog Services Business Processes:( WSs’ ) - Account- Reports - Salary- Control - Payment- Custom - Order- Tax - Invoicing- VAT - etc- etc HTML / XML HTML WSDL META model WS 1 WSDL META model WS 2 WSDL META model WS 3 WSDL META model WS 4 WSDL META model WS 5 WSDL META model WS 6 WSDL META model WS n UDDI Database- server: Application- server: Database- server: Application- server: Service Portal WSDL META model WS X WSDL META model WS F WSDL META model WS E WSDL META model WS D WSDL META model WS C WSDL META model WS B WSDL META model WS A.NET,ONE,SAP,WEBSphere.. !

HAA: okt 2003 EPR Portal Server Integration module: e-Government Co-operation Methodology as “driver” WEB Services: (XML) UDDI = Service Catalog WSDL = Connection SOAP = Message exchange Service Portal: Info.part & Service part HTML XML Legacy system 1 Legacy system n Closed Net XML Web Server Process Server 1 Web Server Refridge/Freeze- devices LightingControl SecuritySystems Process Control LANs EL meter Node 1 Node 2 Node 3 Node i HVAC Node 4 Service Part: Employees working folder with information and help tools HTML Intranet/Internet SOAP -messages XML EPR Folder System UDDI Service Interpretation Center ServiceCatalog: EPR Folder Structure WSDL Interface WS n WSDL Interface WS 1 WSDL Interface WS 2 WSDL Interface WS 3 WSDL Interface WS 5 WSDL Interface WS 4

HAA: okt 2003 HTML 1: Citizens and Customers/Suppliers: Info. Part &Service Part BROWSERS: XML WS in Legacy Systems with different Business logic ( Security Domains ) SERVICE PORTALS: ( TCP/IP networkig ) ”eprXML” Core Components UDDI Service Catalog WSDL Connection SOAP Message Exchange e-Governments User Roles in EPR organized Service Portals 2: Adm. and Service workers: Work Folders with info.and Help Tools Service Part HTML 3: Folder Constructors: Construction of new folder employments Generate Folder Container Template/structur with roles Service Part HTML 4: Portal & System- developers: Programming of Portal- and Legacy Systems with WS interfacing (WSDL modeling) New WS’s WSDL META model spesifications.NET, ONE, WEBSphere, mySAP.. !

HAA: okt 2003 NB ! WS no New Technology, but a new way to organize ”old” and well tested technology XML WEB-Services: (XML) UDDI = ServiceCatalog WSDL = Connection SOAP = Message exchange WS Technology Overview

HAA: okt 2003 Layer: Protocols/Standards: Discovery Description Messaging No new Technology, Internet protocols run since beginning of the 90’s. Just a new way to organize existing XML technology. WS technology Stack (layers): Transport Network UDDI, ebXML, WSIL, DISCOWSDL, ebXML, RDFSOAP: XML-RPC + XML-docHTTP(S), SMTP, FTP etcTCP/IP, UDP Physical Copper, Fiber, IR, RF etc 4:Transport 3:Network 2:Datalink 1:Physical 5:Session 6:Presentation 7:Application OSI stack O pen S ystem I nterconnection

HAA: ITI Juli 2003

Simple Complex If-then-do Decision Agents Implementation Choice Pt.

HAA: okt 2003 Visualization of EPR Folders Folder Container: Time Service Phase 1Phase m Service 1 Service n Folder 1Folder m Folder n Folder q

HAA: okt 2003 EPR Folder’s Core Components Object Models Organizing and Managing WS Service Portals SERVICE PART EPR Folder Container: Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Document card Handles all the Documents in the folder. WS linking Steering Card functions Workflow card Support to adm. working process in the business logic. (Often RuleControlled ProcessFlow) Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Job card (Service card) Def. of physical Instructions in a working process. Includes inspection and reports. Steering Cards: Arbeidsmappe ( Opprettes når ny bruker eller ny process ) Arbeidsmappe ( Opprettes når ny bruker eller ny process ) Working Folder Contain everything a user needs in work. All Working Folders are divided into phases Related to progress. Role Service + UsererID phase Steering card Single Sign-On (PKI) portal: (Security Domains)

HAA: okt 2003 EPR Working Folder handling: - Documents ( also Drawings and Data collections ) - Workflows - Job instructions Folders Phases (life cycle ) Folder’s Key information Folder’s Steering Cards

HAA: okt 2003 EPR Styrekort ( Her som et Dokumentkort ) Steering Card’s function buttons A Seering Card’s organisation

HAA: okt 2003 UML folder model

HAA: okt 2003 UML Steering card model

HAA: okt 2003 EPR’s Document Card Name on steering card belonging to Folders: - Folder 1 - Folder 2. - Folder n CONTENTS: - Group 1 - Document 1. - Document n - Group n - Document 1. - Document n Linking & Switching to corresponding WSs’(ebXMLs’). Function buttons helps to Administrate and work with the Different belonging Documents and Drawings. Connection to the Legacy server systems done by WSDL interfacing

HAA: okt 2003 UML Document card model

HAA: okt 2003 EPR’s Workflow Card Name on steering card belonging to Folders: - Folder 1 - Folder 2. - Folder n CONTENTS: - Group 1 - Routine 1. - Routine n - Group n - Routine 1. - Routine n Linking & Switching to corresponding WSs’(ebXMLs’). Function buttons helps to Administrate and work with Routines and enter physical Instructions. Connection to the Legacy server systems done by WSDL interfacing.

HAA: okt 2003 UML Workflow card model

HAA: okt 2003 EPR’s Job Instruction Card Name on steering card belonging to Folders: - Folder 1 - Folder 2. - Folder n CONTENTS: - Group 1 - Instruction 1. - Instruction n - Group n - Instruction 1. - Instruction n Linking & Switching to corresponding WSs’(ebXMLs’). Function buttons helps to Administrate and work with Physical Instructions and reports. Connection to the Legacy server systems done by WSDL interfacing.

HAA: okt 2003 UML Instruction card model

HAA: okt 2003 Future work items Integration of BCM Choice Point technology to provide flow control and linking and switching for EPR. Create BPSS of discrete workflow components – especially intra-enterprise exchanges. Create BCM contract and CPA templates for EPR participant roles and agreements. Look at applicability of CAM templates for formalizing information quality control and context rules.

HAA: okt 2003 Open Infrastructure & Platform Independence Thanks to WS, proprietary solutions belongs to the past ! Achieve USER controlled and non expensive data solutions ( HW & SW independence is a must ) Interoperable solutions makes standardization/digitalization even more important INTEGRATORS becomes the users and e-Governments “right hand” Network solutions will by help of WS open up and create new ways of user applications ( As EPR’s “Folder” structure ) Minimize the amount of physical devices with multifunctional logical (SW =>WS) units

HAA: okt 2003 EPR- Forum EPR Forum defines the frames for e-Gov SECTOR STANDARDISATION: - Health and Care - Building and Construction - Oil & Gas -.. We must act Not talk !