1	Zero Latency Enterprise Enterprise System Integration Enterprise-Wide Acceleration ! Speed, Agility and Quality are more important than size EnterpriseSystemIntegrating.com © Larry Hartweg 1992 - 2007 All international rights reserved Lean ESI ZLE Outperforms Big & Bulky
2	Zero Latency Enterprise (ZLE) Latency is the time it takes for a system or enterprise to respond to a business event, such as an order, a business object state change, a problem report, etc.
3	Zero Latency Enterprise (ZLE) A zero-latency strategy implies: The enterprise is able to respond as a whole to business events, as soon as they are known by ANY part
4	Many ESI ZLE Benefits Reduce delay in notification of all systems and people with a need to know about business events Share Information in real time Reintegrate autonomous units, improve information consistency and accelerate the entire enterprise Reduce unnecessary functional redundancy in business units Simplify most business processes and the software systems that support them Eliminate cumbersome papers
5	ZLE Benefits: Revenue Revenue Opportunity: After we master ZLE rapid implementation internally, we can sell our knowledge of ESI ZLE to the fast growing e-commerce community (and to the struggling, ineffective, Federal Enterprise Architecture projects)
6	Fundamental ESI ZLE Requirements A formal system development methodology, supported by high-quality, high-productivity, well orchestrated, integrated tool sets
7	More ESI ZLE Requirements Ability to send and selectively receive information through the event-message infrastructure, in a timely (zero latency) fashion Business-event-notification tools Industry-standard interface tools Message Brokers, Web Browsers Business Rules Engines Application Servers Service Oriented Architecture Enterprise Service Bus
8
9	ESI ZLE Technology Components Message Oriented Middleware (MOM) Multiple approaches (object request brokers, location transparency / object mobility, guaranteed-delivery queuing services, etc.)
10	More ESI ZLE Technology Components Event-Oriented Publish / Subscribe Mechanism Reusable Rules Engine for Subscription Selectivity
11	OMG Meta Object Facility, Common Warehouse Metamodel Object Management Group www.omg.org/mof/ World’s largest software consortium – MOF contributions from BEA Systems, Cooperative Research Centre for Distributed Systems Technology, Data Access, Digital Equipment, Electronic Data Systems, Hewlett-Packard, IBM, International Computers, MicroFocus, Objectivity, Oracle, Platinum Technology, Rational Software, System Software Associates, Unisys OMG Model-Driven Architecture (MDA) Standards Transportable methodology-independent (UML, RUP + others) Enterprise Model self-defining Meta-Metadata Standard Repository & heterogeneous interface transition mapping Open-ended technology-independent Enterprise Model with platform-specific integrated code generation concepts Four-Layer Metamodel Architecture: (1) User Object Layer (data instances), (2) Model Layer (metadata, Classes, Tables, etc.), (3) Metamodel Layer (Metadata structure & semantics – Modeling languages), (4) Meta-Metamodel Layer (Semantics of metamodeling languages) Other competing standards & proprietary repository metadata formats
12	New Interface Development Cost
13	Agile Business Object Abstractions
14	Enabled ESI Business Opportunities Zero Latency Yields Enhanced Agility, Responsiveness and Growth Potential Streamline and optimize service delivery Facilitate and accelerate order fulfillment Simplify processes & workflows - Enhance productivity Reduce time and cost to deliver new applications
15	More ESI Business Opportunities Accelerate new product and market introductions Integrate /coordinate diverse international operations Simplify partnering, mergers and acquisitions Enable business-to-business real-time event notification (for customers and business partners)
16	Specific ESI Business Cases Usage-based, on-demand, e-service billing Real-time business object status checking Real-time trend analysis / OLAP / data mining Discover marketing opportunities, ERP, business optimization Fraud detection / usage pattern exceptions Reduce OSS uptime dependency (and costs) 7 x 24 fault tolerant, non-stop, synchronized, object cache(s)
17	More ESI Business Cases Reduce load on non-scalable back end systems Extend the usable life span of legacy systems Enhance system lifecycle collaboration & reuse All development, test, training and production environments Speed up OSS re-engineering & enhancement Simplify data warehouse development & growth Exploit Service-Oriented Architecture and Enterprise Service Bus innovations
18	New ESI ZLE Skill Specializations Messaging - Push and Pull - Multiple Protocols Object Caching and Information Transformation Exploit new throughput / response time opportunities Simplified data mapping with new design patterns Significant reduction in relational / object mapping Enterprise Publication / Selective Subscriptions Rules-Driven Notification / Workflow Engine Enterprise Event-and-Object Model Repository Many Reusable Infrastructure Components Portal Tools for Methodology Automation
19	ESI Organization Requirements An enterprise-wide strategy that leverages fast stimulus / response to achieve real business benefits
20	ESI Organization Requirements An agile, growth-oriented organization capable of rapidly implementing and integrating new concepts, business processes and strategic policies that are engineered for zero latency The structure and function of workgroups, workflows, business processes and departments will need to evolve rapidly ZLE can improve most business activities, from marketing and customer support, through engineering and senior executives orchestrating aggressive competitive innovations IT funding, requirements & resources will change considerably
21	ESI ZLE Proof Of Concept Goals Demonstrate fundamental ZLE concepts and components Develop a plan for enterprise- wide ZLE scalability Gather metadata for event notification types Synchronize high-performance object cache with representative back-end systems
22	POC Steps Toward Our ZLE Future Narrow Proof Of Concept, with a broad vision (iterative incremental risk mitigation - eliminate unknowns) Collect event message “metadata” including: Business event types Message sources & protocols Message content Selectivity criteria Current-and-predicted message volumes, etc.
23	More Proof Of Concept Steps Publish enterprise metadata on Intranet Promote understanding and future reuse Incorporate into an Enterprise Repository based on standards like Meta Object Facility Document redundant publish and subscribe mechanisms Develop the business case and large economic justification for an enterprise-wide ZLE solution (infrastructure, methodology & integrated tools)
24	Next Steps Analyze underlying business requirements Security, publication sources, subscriber criteria, notification protocols, network issues, application concerns, tools, methods, time constraints, budgets, skills, environment transition, etc. Evaluate ESI ZLE POC technologies for possible enterprise-wide application, based on business requirements we discover