1 / 34

EPR ( E lectronic PR ocesses)

EPR ( E lectronic PR ocesses). A new METHODOLOGY standard (abstraction technique) for Integration and coordination of internal processes and e-business in GOVERNMENTS. 21/10-2003 Hans A. Aanesen EPR-Forum. Focus Areas. The business objectives of EPR projects include:

jenna-jennings
Download Presentation

EPR ( E lectronic PR ocesses)

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. EPR( Electronic PRocesses) A new METHODOLOGY standard (abstraction technique) for Integration and coordination of internal processes and e-business in GOVERNMENTS 21/10-2003 Hans A. Aanesen EPR-Forum

  2. 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 http://www.unik.no/profor/ for videos of project examples)

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

  4. The EPR standardization work www.nts.nowww.standardnorge.no 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 • www.oasis-open.org • The realization of the EPR standard based on common international XML components:(www.w3c.orgwww.omg.org) • 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)

  5. EPR implementation pilots(Sector standardization organized through EPR-Forum) www.unik.no/profor 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

  6. EPR EPR is the road ahead to ”Open”, Including and Service organized collaboration in Real time without introduction of new Technology 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

  7. EPR Superstructure organisation • 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 !

  8. eprXML EPR’s Hybrid Portal technology based on a a Service Oriented Architecture organized by help of modern XML abstraction technique

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

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

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

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

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

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

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

  16. WS technology Stack (layers): UDDI, ebXML, WSIL, DISCO OSI stack Open System Interconnection WSDL, ebXML, RDF 7:Application SOAP: XML-RPC + XML-doc 6:Presentation 5:Session HTTP(S), SMTP, FTP etc 4:Transport 3:Network TCP/IP, UDP 2:Datalink Copper, Fiber, IR, RF etc 1:Physical No new Technology, Internet protocols run since beginning of the 90’s. Just a new way to organize existing XML technology. Layer: Protocols/Standards: Discovery Description Messaging Transport Network Physical

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

  18. Folder Container: Service Folder n Folder q Service n Folder 1 Folder m Service 1 Phase 1 Phase m Time Visualization ofEPR Folders

  19. Service Portals SERVICE PART Arbeidsmappe ( Opprettes når ny bruker eller ny process ) phase 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 Steering card Steering Cards: 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. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Steering Card functions 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 Workflow card Support to adm. working process in the business logic. (Often RuleControlled ProcessFlow) Job card (Service card) Def. of physical Instructions in a working process. Includes inspection and reports. EPR Folder’s Core ComponentsObject Models Organizing and Managing WS EPR Folder Container: Single Sign-On (PKI) portal: (Security Domains)

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

  21. A Seering Card’s organisation Steering Card’s function buttons EPR Styrekort( Her som et Dokumentkort )

  22. UML folder model

  23. UML Steering card model

  24. 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 EPR’s Document Card

  25. UML Document card model

  26. 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. EPR’s Workflow Card

  27. UML Workflow card model

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

  29. UML Instruction card model

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

  31. 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 makesstandardization/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

  32. 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 !

More Related