1 / 19

Presented by

Dipl. Ing. Dirk Hanke. C EO EAI One Integration - WWW.EAIONE.COM -. Berlin • Dresden • Hannover. Berlin • P hone +49 (0) 172 325 9879 • eM ail d irk_ hanke@ eaione.com. Presented by. History : 2 Years Siemens Development of High Speed Communication Systems,

kuper
Download Presentation

Presented by

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. Dipl. Ing. Dirk Hanke CEO EAI One Integration -WWW.EAIONE.COM- Berlin • Dresden • Hannover Berlin • Phone +49 (0) 172 325 9879 • eMail dirk_hanke@eaione.com Presented by History : 2 Years Siemens Development of High Speed Communication Systems, 16 Years IBM senior IT Architect Working for Five Different Verticals Setup EAIONE's Architecture and Development at IBM in 1995

  2. Typical customer environment SAP R/3 • FI • SD • MM • CO • ISU • ISH Poor , function oriented I/F techniques Communication Server / Links GUI WORKFLOW A WORKFLOW B+C+D

  3. SOURCE SOURCE SOURCE SOURCE DB1 DB2 DB3 DB4 DB5 DB6 DB7 A B D E The problem of final definition Portals ITV - Weather - Assets - Schedules - Financials - Patient Movement - Modeling ….. Visualization Tools TOOLA TOOLB TOOLC TOOLD TOOLE TOOLF TOOLG TOOLF TOOLG TOOLH Corporate Data Environment XML WORKFLOW B+C+D WORKFLOW A Databases and other sources DTS Migration systems, C2, Transportation Financial, Simulation /Modeling, and Administrative Databases

  4. SAP R/3 Patient Admin System Lab System Surgery System OutPatient System Radialogy System Controlling Billing Patient Finance Material Typical customer environment KIS System What is common over all Systems ?

  5. Individual, non standardized mappings Vendor solution or ? Competitors Workflow strategies Reusability ? , Efforts ? Transparency ? Complex or Complicated ? • Topology usually leads to: • Classical implementation approach • “per Interface”, • considering all 1:n possible relations • ... Creating the classical spaghetti...

  6. Application B Application A Technology related mapping & logic cross protocols Technology Layer Technology Layer Internet Application Http(s) Transport XML Protocol RFC Protocol SAP Application ACK ACK ACK EDIFACT Protocol Technology Layer ACK Insurance Application Competitors Business Process View ( Standard ? Re-Use ? ) Application C The central idea behind competitors products

  7. Conversion Conversion Protocol Protocol Protocol Protocol Conversion Application A Action Action Action Application 1 Application 2 Application X Single Information e.g. Name #ID 66 Single Information e.g. Name #ID 66 Single Information e.g. Name #ID 66 Single Information e.g. Name #ID 66 Default Default Default Effort : (Single Attribute + Referenced Attributes) *Protocol *Individual Logic *(n:n) Applications * Customers Single Activity (Mapping) Competitors neverending effort Process of one single attribute

  8. Goals for the Architecture ... • Workflow independent Interfaces • Customizable , no coding, generic adapter approach • Application dependent , not Interface dependent • Reusability : Customizing an application once, whenever it is used by an interface • Technical system (application) Interface : Online / bi-directional / functionless • „Release independent“ I/F technique, scalable , load balancing • Usage of a neutral Object Standard to cover all application communication standards • One runtime code for all business areas & countries • One skill to cover projects over multiple business areas • Open for all new technologies ( e.g. “.NET” , Java Beans ) • Minimum TCO on maximum ROI

  9. Application DB API Layer Protocol Layer e.g. Transport Outside world ( EAI World ) EAIONE ’s physical view of an application

  10. API Layer API Layer Application DB Application DB Protocol Layer Protocol Layer e.g. Transport e.g. Transport Outside world ( EAI World ) Outside world ( EAI World ) An application independent definition of single process must be defined to have a common business process definition What is common ? • No API have common structures • Protocol structures as framework are common (e.g XML) • Content of protocol depends mostly on single application, • (otherwise the applications are common, customizing ? ) EAIONE ’s logical view of interfacing

  11. Conversion OBJECT MATERIAL Conversion OBJECT MATERIAL Action Action Default Default Xfer no Mapping The central idea behind EAIONE (Object Layer) EAIONE Application SAP R/3 V4.6 EAIONE Application Navision Axapta OBJECT ORDER OBJECT ORDER OBJECT DEBTOR OBJECT DEBTOR Single Information e.g. Name #ID 66 CHARACTER LENGTH 35 DEFAULT LOGIC Single Information e.g. Name #ID 66 CHARACTER LENGTH 40 DEFAULT LOGIC Single Information e.g. Name #ID 66 Single Information e.g. Street #ID 67 Single Information e.g. City #ID 68 Single Information e.g. Zip Code #ID 69 Single Information e.g. Country #ID 70 Object Template

  12. Object Layer Technology Layer Standard Object Access (Method) RFC CHARACTER LENGTH 35 KNA1-NAME1 #ID 66 EAIONE SAP RFC Adapter Conversion OBJECT DEBTOR OBJECT DEBTOR Access (Method) IDOC Action Single Information e.g. Name #ID 66 NUMERIC LENGTH 35 E2KNA1M002::NAME1 #ID 66 EAIONE SAP IDOC Adapter Default #ID 67 #ID 68 EAIONE SAP BAPI Adapter Access (Method) BAPI Single Information e.g. Name #ID 66 CHARACTER LENGTH 35 DEFAULT LOGIC #ID 69 Access (Method) CAPI #ID 200 EAIONE SAP CAPI Adapter Preparing the object attributes to standard content with Conversion, Actions , Defaults Mapping once the physical attributes of a specific protocol to the standard object attributes The central idea behind EAIONE Sample : EAIONE's Application SAP R/3 V4.6

  13. Application B Application A Technology Layer Object Layer Technology Layer HANDLE Objects #ID 66 #ID 66 Internet Application Http(s) Transport XML Protocol RFC Protocol SAP Application HANDLE Objects HANDLE Objects ACK ACK ACK ACK ACK Gen. Adapter Behavior #ID 66 Gen. Adapter Behavior ACK (1) EDIFACT Protocol (2) (3) Multiple Threads (parallel processing) TCP/IP data (in) TCP/IP data (out) ACK Insurance Application EAIONE's database Application C Load Balancing,Fail over The central idea behind EAIONE Standard Objects

  14. Mapping Conversion Action Default DEBTOR .NET XML DEBTOR SQL EDI EDIFACT X12N MATERIAL HL7 RFC / IDOC DEBTOR MATERIAL ORDER ORDER ORDER ORDER DEBTOR MATERIAL MATERIAL ORDER BAPI SMTP File Http FTP ZIP SSL Architecture of EAIONE 1st Layer 2nd Layer Samples of Vendor Applications Transport & Protocol Adapter Standard Objects Customizing Module SAP CRM Axapta (Web Services) EAIONE’s Relational Database ( SQL Entry Level 92 )

  15. The Benefit structure of EAIONE Pre Built (Project entry) Standard development process versus Pre built scenarios starting at Final Test = TCO + ROI

  16. Total effort of project ** ** * The distribution based on own knowledgde , referenced to the knowledgde of customer / partner ** single effort cannot be referenced

  17. License Maintenance License Maintenance EAI One’s and competitors market area TCO Enterprise Market ( moving from expensive to medium/low cost ) • Services • Projects > min 6 weeks • Expensive Service Org • (IBM,HP,SIEMENS) • Programmer,Consultant • No Reuse SMB Market (low cost) • Services • Pre-Built • Only Consultant • “Five a Life” • SMB for SMB+Enterprise Big “5” Competitors TCO EAI One’s TCO

  18. Oracle based PPS System SAP R/3 Debtors Debtors Material Material ROUTING BOM BOM Invoice Delivery Part of current EAI ONE project Communication with EAI ONE ( totaly 15 – 20 different processes , SAP I/F IDOC , PPS I/F RMDBS with trigger / alerts)

  19. SAP R3 V4.6 BICEPS Technology Layer Object Layer Technology Layer HANDLE Objects #ID 66 #ID 66 BICEPS Application Trigger Transport SQL Protocol IDOC Protocol SAP Application HANDLE Objects ACK ACK ACK ACK ACK Gen. Adapter Behavior Gen. Adapter Behavior (1) (2) (3) Multiple Threads (parallel processing) TCP/IP data (in) TCP/IP data (out) EAIONE's database Load Balancing,Fail over The BICEPS <> SAP IF with EAIONE Standard Objects

More Related