Enabling a zero latency enterprise Number:6,757,689 from the United States Patent and Trademark Office (PTO) owispatent Methods are provided for enabling an enterprise to run as a zero latency enterprise (ZLE) and for running an enterprise as a ZLE. Such methods allow the enterprise to integrate its services, applications and data in real time. Namely, an enterprise equipped to run as a ZLE is capable of integrating, in real time, its enterprise-wide data, applications, business transactions, operations and values. Consequently, an enterprise conducting its business as a ZLE exhibits superior management of its resources, operations and customer care.<H enterprise, Enabling, Enabling, a, zero, 6757689.html, Patent, pto, 6757689

Title: Enabling a zero latency enterprise

Abstract: Methods are provided for enabling an enterprise to run as a zero latency enterprise (ZLE) and for running an enterprise as a ZLE. Such methods allow the enterprise to integrate its services, applications and data in real time. Namely, an enterprise equipped to run as a ZLE is capable of integrating, in real time, its enterprise-wide data, applications, business transactions, operations and values. Consequently, an enterprise conducting its business as a ZLE exhibits superior management of its resources, operations and customer care.

Patent Number: 6,757,689 Issued on 06/29/2004 to Battas, et al.

Inventors: Battas; Gregory (Indianapolis, IN), Zargham; Bahman (Sunnyvale, CA)
Assignee: Hewlett-Packard Development Company, L.P. (Houston, TX)

Appl. No.: 09/948,928

Filed: September 7, 2001

Current U.S. Class: 707/101 ; 709/202; 709/206; 709/207; 709/224; 717/102; 717/104; 719/318

Current International Class: G06Q 10/00 (20060101)

Field of Search: 709/202,207,318,224,206 705/10,17,26 707/101,104,103 717/102,104,103 345/733-759

References Cited [Referenced By]

U.S. Patent Documents


6314531	November 2001	Kram
6550057	April 2003	Bowman-Amuah
6591278	July 2003	Ernst
6601233	July 2003	Underwood

Other References

Maltzahn et al., "Performance isues of enterprise level web proxies", ACM, 1997, pp. 13-23.* .
Renato John Recio "Server I/O Networks past, present and future", ACM, 2003, pp. 163-178.* .
Dharma P. Argrawal, "Next generation enterprises- Virtual organizations and persavise/mobile technologies", ACM, pp. 20-24.* .
Nathan J. Muller, "Managing service level agreements", ACM 1999, pp. 155-166.* .
Zhao et al., "Data management issues for large scale, distributed workflow systems on the internet", ACM, vol. 29, no 4, Fall 1998, pp. 22-32.* .
Martin et al., "Decoupling performance and correctness", ACM.* .
Anonymous: "Compaq's Zero Latency Enterprise Initiative: Business at the Speed of Now," 24 .times.7 The Magazine of NonStop Computing by Compaq Computer Corporation, vol. 1, No. 2, Oct. 2000, pp. 1-25, XP002236415. .
Shannon, T. C.: "ZLE: When you have to have it NOW," Shannon Knows Compaq, Oct. 17, 1999, pp. 1-2, XP002236416. .
Voth, G. R. et al.: "Distributed application development for three-tier architectures: Microsoft on Windows DNA," IEEE Internet Computing, Mar.-Apr. 1998, vol. 2, No. 2, pp. 41-45, XP002236417. .
Chaudhuri S., et al.: "An Overview of Data Warehousing and OLAP Technology," Sigmod Record, vol. 26, No. 1, Mar. 1997, pp. 65-74, XP002193792. .
Halle D.: "A New Marketing Game Plan," Teradata Review, vol. 2, No. 3, 1999, pp. 21-22, 24-25, XP009002119. .
Sengul, S., et al.: "Building A Service Provisioning System Using The Enterprise Java Bean Framework," IEEE/IFIP Network Operations And Management Symposium The Networked Planet: Management Beyond 2000, Apr. 10-14, 2000, pp. 367-380, XP010376695. .
Den, Daas C.: "Gartner '98-The Zero Latency Enterprise," Informatie, Dec. 1998, Kluwer Bedrijfswetenschappen, vol. 40, spec. issue., pp. 60-65, XP009008657. .
Compaq Information Technologies Group, L.P., International Search Report mailed Apr. 24, 2003, Int'l. App. No. PCT/US01/28623, Int'l. Filing Date Sep. 13, 2001, pp. 1-6. .
Compaq Information Technologies Group, Inc., International Search Report mailed Apr. 11, 2003, Int'l. App. No. PCT/US01/28778, Int'l. Filing Date Sep. 13, 2001, pp. 1-6..

Primary Examiner: Corrielus; Jean M.

Parent Case Text

REFERENCE TO PRIOR APPLICATION

This application claims the benefit of and incorporates by reference U.S. Provisional Application No. 60/266,003 filed Feb. 2, 2001.

CROSS REFERENCE TO RELATED APPLICATION

This application is related to and incorporates by reference U.S. patent application Ser. No. 09/948,927 filed Sep. 7, 2001 entitled "Framework, Architecture, Method and System for Reducing Latency of Business Operations of an Enterprise," and Ser. No. 10/013,091 filed Dec. 7, 2001 entitled "Zero Latency Enterprise Enriched Publish/Subscribe."

Claims

What is claimed is:

1. A method for running an enterprise as a zero latency enterprise (ZLE), the enterprise experiencing a plurality of events occurring in association with business transactions conducted at a plurality of sites across the enterprise, the method comprising: Integrating, in real time, enterprise-wide data, applications, business transactions, operations and values, by capturing, in real time, an indicia of each of the plurality of events, each indicia being associated with information related to its respective event, aggregating, in real-time, the information related to the plurality of events in a central repository where the aggregated information can, in real-time, be accessible and available for extraction and analysis from across the enterprise, so as to provide a coherent view, in real time, of the aggregated information from across the enterprise and so that the enterprise can achieve enterprise-wide coherent and zero latency business transactions, and initiating, in real time, a process responsive to each event of the plurality of events which is founded on the coherent view of the aggregated information.

2. A method for running an enterprise as a zero latency enterprise (ZLE), the enterprise conducting its business and in association therewith experiencing a plurality of events occurring at a plurality of sites across the enterprise, comprising: capturing, in real time, an indicia of each of the plurality of events, each indicia being associated with information related to its respective event; aggregating, in real-time, the information related to the plurality of events in a central repository where the aggregated information can, in real-time, be accessible and available for extraction and analysis from across the enterprise, so as to provide a coherent view, in real time, of the aggregated information from across the enterprise and so that the enterprise can achieve enterprise-wide coherent and zero latency business transactions; and initiating a process responsive, in real time, to each event of the plurality of events which is founded on the coherent view of the aggregated information, the process including one or any combination of a rule-based analysis of the information related to that event, a process-flow coordination in response to that event, narrowcasting a notification associated with that event if the rule-based analysis of its information creates a notable-event that prompts the notification, creating feedback to that event creating a new event or cascade of events, and producing a value associated with that event unless, in real-time response to that event, the rule-based analysis of its information precludes production of the associated value.

3. The method for running an enterprise as a ZLE in accordance with claim 2, wherein creating the feedback includes offering or suggesting an action, in real time based on the information or any part thereof, to provide an additional value, if not precluded by the real-time rule-based analysis.

4. The method for running an enterprise as a ZLE in accordance with claim 1, wherein the aggregated information in the central repository includes a profile, and wherein the process further includes, in real time based on the profile, offering or taking an action to provide or suggesting an action to obtain an additional value, if not precluded by a result of the real-time analysis.

5. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the aggregated information in the central repository includes a customer profile, and wherein the process further includes offering, in real time based on the customer profile, to provide an additional value, if not precluded by a result of the real-time rule-based analysis.

6. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the customer profile includes one or any combination of customer attributes, preferences and an historic account of prior consumption.

7. The method for running an enterprise as a ZLE in accordance with claim 2, the feedback creation includes creating a model from data mining and the rule-based analysis that can guide current and future responses to that event and any subsequent events, respectively.

8. The method for running an enterprise as a ZLE in accordance with claim 7, the process further including offering, suggesting an action or taking the action in real-time based on the model, to provide an additional value.

9. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the aggregated information is relevant enterprise-wide and by which the method reduces operational inconsistencies of the enterprise.

10. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the information related to each of the plurality of events includes one or any combination of event data, one or more transaction states and lookup data.

11. The method for running an enterprise as a ZLE in accordance with claim 2, wherein each of the plurality of events represents commencement, state change or, completion of a business transaction.

12. The method for running an enterprise as a ZLE in accordance with claim 2, wherein an event associated with a business transaction includes one or any combination of event data entry, exchange and manipulation.

13. The method for running an enterprise as a ZLE in accordance with claim 2, wherein an event associated with a business transaction includes one or both of an inquiry and a result.

14. The method for running an enterprise as a ZLE in accordance with claim 2, wherein each indicia includes a detectable prompt, flag, notice, evidence or indication of its associated event.

15. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the real-time response to that event is a denial of service that precludes the production of the associated value.

16. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the indicia of each one of the plurality of events is respectively captured at one of the plurality of sites across the enterprise and each associated value, if not precluded, is respectively produced at one or more determined sites from among the plurality of sites.

17. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the indicia of each one of the plurality of events is respectively captured at one of the plurality of sites across the enterprise and, if prompted, each associated notification is narrowcasted to one or more determined sites from among of the plurality of sites.

18. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the new event or cascading events are created in real time.

19. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the enterprise business includes rule-based operations, and wherein the rule-based operations and rule-based analysis are founded on predefined, uniform enterprise-wide rules and policies for conducting business transactions.

20. The method for running an enterprise as a ZLE in accordance with claim 2, the process further including data mining, in real time, of the information related to that event; and conducting, in real-time, business intelligence and decision support using a result or a model produced by the data mining and rule-based analysis.

21. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the business conducted by the enterprise includes retail business with customer interactions via a plurality of customer interaction channels across the enterprise, the customer interactions include providing values based on the plurality of events experienced by the enterprise in association with its retail business.

22. The method for running an enterprise as a ZLE in accordance with claim 21, wherein each of the plurality of events represents commencement, change in state or completion of a respective retail business transaction, including one or a combination of product search, product order, product purchase, service request, product return, credit request, payment, inventory addition, inventory reduction, new enterprise partner indication, new enterprise resource indication, new customer indication, and new address indication, wherein the new event or cascading events represent change in state or completion of the respective retail business transaction or commencement of a new retail business transaction, including one or any combination of credit approval, cash refund, credit refund, receipt generation, invoice generation, invoice due date arrival, inventory-level change, resource-level change, a product manufacture phase reached, a product manufacture series of phases reached, product shipment, product delivery and service delivery.

23. The method for running an enterprise as a ZLE in accordance with claim 21, wherein the feedback includes an integrated marketing campaign tailored to a customer profile supported through multiple marketing channels across the enterprise.

24. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the feedback includes one or any combination of an offer to provide another value tailored to a customer profile, a denial of service as a result of business intelligence supported by the rule-based analysis, product availability information, product or service price information, and a product or service delivery date based on the customer profile and scheduling information.

25. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the rule-based analysis determines, in real-time, whether any one of the plurality of events is associated with a fraudulent business transaction or risk to the enterprise, in which case the notable event is a denial of service.

26. The method for running an enterprise as a ZLE in accordance with claim 2, wherein one of the plurality of events represents commencement of a business transaction with a customer via a first site, the customer being identified via the first site by a first customer identification (ID), another one of the plurality of events representing a continuation of the same business transaction with the same customer or commencement of a different business transaction with the same customer via a second site, the same customer being identified via the second site by a second customer ID, and wherein the process includes determining, in real time, that the first and second customer IDs belong to the same customer, even if the customer attempted anonymity.

27. The method of running an enterprise as a ZLE in accordance with claim 26, wherein the first site and second site are different sites, each of which being, although not simultaneously, one of a point of sale, call center, internet link, credit center, customer service center, product delivery center and gift registry center.

28. The method for running an enterprise as a ZLE in accordance with claim 26, wherein the first customer ID is a customer telephone number and the second customer ID is a cookie.

29. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the aggregated information includes an historic account of prior sessions of interaction with a customer, and wherein the process includes determining, in real time, whether that event is associated with that customer, even if that customer attempted anonymity.

30. The method for running an enterprise as a ZLE in accordance with claim 2, wherein the enterprise conducts business that includes providing the value, the plurality of events being experienced across the enterprise in association with its business.

31. The method for running an enterprise as a ZLE in accordance with claim 30, wherein one or more of the plurality of events include a request for the value.

32. The method for running an enterprise as a ZLE in accordance with claim 30, wherein the value includes a product, a service, and item for consumption, a creation, an enterprise resource or knowledge.

33. The method for running an enterprise as a ZLE in accordance with claim 30, wherein the value includes a bank account deposit or withdrawal, a credit ratings report, a price list, a production cost report, an inventory report, an insurance appraisal report, a medical exam report, a disaster or emergency response, an identification search report, stock or profitability analysis report, manufactured goods, agricultural product, manufacturing facility, manpower and knowledge.

34. A method for enabling an enterprise to run as a zero latency enterprise (ZLE), the enterprise conducting business and in association therewith experiencing a plurality of events, comprising: creating a ZLE framework that enables enterprise-wide coherent and zero latency business transactions, the ZLE framework being formed by merging enterprise application integration (EAI) functionality dynamic operational data store (ODS) functionality, transaction processing and monitoring functionality, data mining and analysis functionality, and automatic feedback functionality that, together, fashion a hybrid functionality of the ZLE framework; integrating ZLE core services in a core of the ZLE framework; tightly coupling clip-on application to the ZLE core services; loosely coupling enterprise applications to the ZLE core services, the enterprise applications being operatively interfaced via the EAI functionality and sharing access to information made available by the ODS functionality, the information being related to the enterprise, its business and the plurality of events and being dynamically aggregated via the ODS functionality so that from across the enterprise the aggregated information can, in real time, be accessible and available for the transaction processing and monitoring functionality and for the data mining and analysis functionality, and so that there is a coherent view, in real time, of the aggregated information from across the enterprise.

35. The method for enabling an enterprise to run as a ZLE in accordance with claim 34, wherein the ZLE is capable of eliminating operational inconsistencies.

36. The method for enabling an enterprise to run as a ZLE in accordance with claim 34, wherein the enterprise uses the ZLE framework to implement enterprise applications that include one or any combination of customer relationship management (CRM) facilitating real-time creation of values and services including customer care, business intelligence and marketing campaign; operations and resource management supporting real-time enterprise operations, productivity improvement and latency reduction; and applications supporting global value chain optimization, streamline in-time manufacturing inventory supplier management, inventory channel management and third-party solutions management.

37. A method as in claim 34 enabling the enterprise to integrate its services, applications, values and data in real time.

38. A method as in claim 34, wherein the ZLE is extensible and available, and wherein the ZLE framework, itself, is extensible and available.

39. A method as in claim 34, wherein the clip-on applications include an interaction manager, a narrowcaster, a campaign manager and a customer data manager.

40. A method as in claim 34, wherein by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise conducts retail business in relation to which the enterprise can perform business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship via real-time integration of business modes, including retail and e-business modes, and customer service support.

41. A method as in claim 34, wherein by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise conducts financial services business in relation to which the enterprise can perform risk management and business intelligence including via real-time client account and fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, portfolio assessment via real-time enterprise-wide account balance and asset value evaluation, asset management via intraday borrowing, valuation and transaction processing by real-time dynamic updating of customer accounts and assets, and customer relationship support via real-time integration of business modes, including retail and e-business modes, and customer service support.

42. A method as in claim 34, wherein by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise conducts transportation and shipping business in relation to which the enterprise can perform business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship support via real-time integration of value delivery scheduling, transportation and shipping modes and customer service support.

43. A method as in claim 34, wherein by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise conducts manufacturing business in relation to which the enterprise can perform risk management and business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship support via real-time integration of manufacturing scheduling, inventory and manufacturing resources management, and customer service support.

44. A method as in claim 34, wherein by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise conducts telecommunications business in relation to which the enterprise can perform business intelligence via real-time customer service response, profitability forecasting and risk management via real-time fraud pattern detection and management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, customer relationship support via real-time supply chain management, customer care management and customer service support, and cross-selling of bundled services via real-time profitability analysis by evaluation of route, product and call margins for every customer.

45. A method for enabling an enterprise to run as a zero latency enterprise (ZLE), comprising: creating a ZLE framework for conducting enterprise-wide coherent business transactions with substantially zero latencies by merging enterprise application integration (EAI) operational data warehousing, transaction processing and monitoring, data mining and analysis, and feedback

that, together, fashion a hybrid functionality of the ZLE framework; managing process-flow of the business transactions across the enterprise; transforming data and messages routed between disparate enterprise resources concerning the business transaction; applying enterprise-wide coherent business rules and policies for managing the business transactions; dynamically aggregating data relating to the enterprise and its business transactions from across the enterprise; providing real-time, consolidated view of the data and state of the business transactions from across the enterprise; and extracting bulk data for the business transactions.

46. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, wherein the process-flow management is rule driven.

47. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, wherein the ZLE framework provides an open integration platform for applications used by the enterprise.

48. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, wherein the enterprise coherent business rules can be pre-defined and re-defined.

49. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, wherein the enterprise-wide coherent business rules can be pre-determined, modified and applied by an operator via a user interface.

50. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, wherein the application of enterprise-wide coherent business rules and policies includes fraud detection and narrowcasting of any detected fraud.

51. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, further comprising: managing a real-time campaign that makes use of the real-time, consolidated view of the aggregated data.

52. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, further comprising: managing real-time customer interaction and customer profiling making use of the real-time, consolidated view of the aggregated data.

53. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, further comprising: providing, including in real time, feedback of results produced from the bulk data by the data mining and analysis.

54. The method for enabling an enterprise to run as a ZLE in accordance with claim 45, further comprising: publishing throughout the enterprise a plurality of events associated with its business transactions.

55. A method for enabling an enterprise to run as a zero latency enterprise (ZLE), comprising: creating a ZLE framework for conducting enterprise transactions pertaining to the enterprise with substantially zero latencies by merging enterprise application integration (EAI) operational data warehousing, transaction processing, data mining and analysis, and feedback

that, together, fashion the functionality of the ZLE framework which includes recognizing, in real time, events associated with the business transactions; triggering actions responsive in real-time to the events; and providing real-time, consolidated view of the enterprise and its business transactions from across the enterprise, eliminating operational inconsistencies.

56. The method for enabling an enterprise to run as a ZLE in accordance with claim 55, wherein the ZLE framework enables the enterprise to behave as a virtual enterprise.

57. The method for enabling an enterprise to run as a ZLE in accordance with claim 55, wherein the ZLE framework enables extensibility and availability of the enterprise.

58. The method for enabling an enterprise to run as a ZLE in accordance with claim 55, wherein the ZLE framework enables synchronization and routing of business transactions data to applications integrated through the EAI and enables the applications to be loosely coupled to the framework.

59. The method for enabling an enterprise to run as a ZLE in accordance with claim 55, wherein each of the applications can proceed with the transaction processing at its own pace.

60. The method for enabling an enterprise to run as a ZLE in accordance with claim 55, wherein the ZLE framework prevents a fault from cascading and disrupting transaction processing throughout the entire enterprise.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

This application relates to an information technology (IT) infrastructure of an enterprise, and specifically, an IT infrastructure that enables a zero latency enterprise (ZLE). The present invention enables the enterprise to integrate its services, applications and data in real time, hence the ZLE.

2. Background Art

Information technology (IT) allows valuable information to be distributed across organizations to groups of information consumers including remote employees, business partners and customers. However, organizations have large amounts of information located on disparate systems and platforms. For maintaining the desired comprehensive view of their operations, organizations need to integrate theirs systems. Then again, independent configuration for disparate industry standards and technologies makes systems integration requirements difficult to meet. Moreover, as the various business applications have diverse features and are tailored to suit the requirements of a particular domain, their integration requirements may be also difficult to meet. For example, there are significant integration requirements to make it work when integrating a customer relationship management (CRM) application to an existing system with other applications such as SAP's enterprise resource planning (ERP) software package, as the CRM is uniquely tailored to the customer care domain.

Notwithstanding, when addressing their critical information needs, organizations often resort to new best-of-the-breed applications (or solutions). To leverage their existing applications, organizations integrate their legacy applications with the new solutions, a practice known as enterprise application integration (EAI). To this end, software vendors have responded by building tools, known as EAI products, alas different tools by different vendors, to automate the integration process.

Deficiencies in integration and data sharing are indeed a difficult problem of IT environments for any enterprise. The inability of organizations to operate as one-organ, rather than separate parts, creates a challenge in information exchange and electronic commerce and results in economic inefficiencies.

With conventional solutions, organizations have been using some form of the EAI platform to integrate their application. And, they have been using a different platform for integrating their data into data warehouses. Data warehouses integrate data across an organization for reporting and data mining using business intelligence tools like SAS Institute tools.

The problems with these schemes are that there is no real-time connection and interaction between the EAI and data warehousing. Moreover, with relatively static data warehouses the data warehousing cloud is used for analysis but could not participate in the current transaction or events that are happening in the organization in real time. The organization still will end up with two disjointed infrastructures that cannot leverage each other in real-time (See: FIG. 1). Accordingly the present invention addresses these and related issues.

SUMMARY OF THE INVENTION

In accordance with the purpose of the invention, as embodied and broadly described herein, the invention relates to methods for enabling an enterprise to run as a zero latency enterprise (ZLE) and for running an enterprise as a ZLE. The present invention allows the enterprise to integrate its services, applications and data in real time. Namely, an enterprise equipped to run as a ZLE is capable of integrating, in real time, its enterprise-wide data, applications, business transactions, operations and values. Consequently, an enterprise conducting its business as a ZLE exhibits superior management of its resources, operations, supply chain and customer care.

Underpinning the superior characteristics of ZLE is an information technology (IT) infrastructure that is equipped with and using the hybrid functionality of a ZLE framework. This framework is not a single product or middle ware. Rather, it defines architecture with collection of products, tools, and services that enables, among others, the reduction of operational latencies in the enterprise. With such hybrid functionality, an enterprise running as a ZLE can route information across various enterprise applications using enterprise application integration technologies. Clearly, the ZLE framework is not just an enterprise integration platform as it can accomplish application and data integration across the enterprise. Using database extractors, database loaders and application adapters technologies, the ZLE can integrate data related to the real-time operations of an enterprise into a storage cache, also known as operational data store (ODS), and synchronize information across the enterprise using enterprise application integration (EAI) tools. Also, with rules and synchronization policies implemented in a ZLE hub with the ODS, any updates communicated to the ZLE hub from any application across the enterprise can, via the ZLE hub, bring about information synchronization in all other applications across the enterprise, including its legacy applications. Information and updates thereof are communicated from the applications to the ZLE hub by way of adapters. Furthermore, the ZLE can provide data to business intelligence applications for analysis, and it supports decision support systems (DSS) and data mart operations as well as transactional access to up to the minute data by multiple add-on new and legacy enterprise applications.

As noted, one embodiment of the present invention is a method for running an enterprise as a ZLE. In conducting its business, the enterprise is experiencing a plurality of events occurring in association with its business transactions. Its business is conducted at a plurality of sites across the enterprise. To reduce the unintended latency in enterprise operations to zero, all organs of the enterprise need to be made aware of business events as they occur, i.e., in real time. Thus, the method for running a ZLE includes integrating, in real time, its enterprise-wide data, applications, business transactions, operations and values. This is done by performing a combination of actions, one of which is capturing, in real time, an indicia of each of the plurality of events. Each indicia is associated with information related to its respective event. The actions also include aggregating, in real-time, the information related to the plurality of events in a central repository database (ODS) where the aggregated information can, in real-time, be accessible and available for loads, extractions, updates, queries and analysis from across the enterprise. As a consequence, a coherent view of the aggregated information is obtained, in real time, from across the enterprise, As a further consequence, the enterprise can achieve enterprise-wide coherent and zero latency business transactions. The actions further include initiating, in real time, a process responsive to each event of the plurality of events which is founded on the coherent view of the aggregated information.

The process includes one or any combination of: a rule-based analysis, in real-time, of the information related to that event; narrowcasting, in real time, a notification associated with that event if the rule-based analysis of its information creates a notable-event that prompts the notification; creating feedback to that event, in real time; creating a new event or cascade of events, and producing a value associated with that event unless, in real-time response to that event, the rule-based analysis of its information precludes production of the associated value. The process of creating the feedback includes offering, in real time based on any part of or the entire information, to provide an additional value, if not precluded by the real-time rule-based analysis. In a case where the aggregated information in the central repository includes a customer profile, the process further can include offering, in real time based on the customer profile, to provide an additional value. The offer is made if not precluded by a result of the real-time rule-based analysis.

As previously noted, another embodiment of the present invention is method for enabling an enterprise to run as ZLE. This method includes creating the ZLE framework that enables the enterprise to integrate its services, applications and data in real time. So enabled, the enterprise can achieve enterprise-wide coherent and zero latency business transactions. Moreover, the ZLE is extensible and available, and the ZLE framework, itself, is extensible and available.

The ZLE framework is formed by merging: enterprise application integration (EAI) functionality; dynamic operational data store (ODS) functionality; transaction processing and monitoring functionality, and data mining and analysis functionality and a feedback mechanism. Together, these functions fashion a hybrid functionality of the ZLE framework. The method further includes integrating ZLE core services, tightly coupling clip-on application to the ZLE core services, and loosely coupling enterprise applications to the ZLE core services. In the case of a ZLE with unified customer relationship management (CRM), the clip-on applications include an interaction manager, a narrowcaster, a campaign manager and a customer data manager. The enterprise applications are operatively interfaced via the EAI functionality and share access to information made available by the ODS functionality. The enterprise applications include one or any combination of: CRM facilitating real-time services including customer care, business intelligence and marketing campaign; operations and resource management supporting the real-time services and creating values that can be offered to one or more customers; and third-party solutions management supporting the ZLE operations and resource management.

The enterprise conducting its business is experiencing in association therewith a plurality of events. Accordingly, the information is related to the enterprise, its business and the plurality of events. The information is being dynamically aggregated via the ODS functionality. As a result, the aggregated information can, in real time, be accessible and available from across the enterprise for the transaction processing and monitoring functionality and for the data mining and analysis functionality. As a further result, there is a coherent view, in real time, of the aggregated information from across the enterprise. What is more, by enabling the enterprise to run as a ZLE, the enterprise is capable of eliminating operational inconsistencies.

There are many ways for implementing these methods in commerce, military, medical, government and other businesses. A number of simple examples of implementation in commerce are hereafter provided.

In one implementation of this method, by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise can conduct retail business. In relation to its retail business the enterprise can perform business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship via real-time integration of business modes, including retail and e-business modes, and customer service support.

In another implementation of this method, by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise can conduct financial services business. In relation to its financial services business, the enterprise can perform risk management and business intelligence including via real-time client account and fraud management, marketing campaign and profitability management via real-time supply chain and customer care management; profitability forecasting via real-time supply chain management, portfolio assessment via real-time enterprise-wide account balance and asset value evaluation, asset management via intraday borrowing; valuation and transaction processing by real-time dynamic updating of customer accounts and assets, and customer relationship via real-time integration of business modes, including retail and e-business modes, and customer service support.

In yet another implementation of this method, by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise can conduct transportation and shipping business. In relation to its transportation and shipping business, the enterprise can perform business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship via real-time integration of value delivery scheduling, transportation and shipping modes and customer service support.

In yet another implementation of this method, by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise can conduct manufacturing business. In relation to its manufacturing business, the enterprise can perform risk management and business intelligence via real-time fraud management, marketing campaign and profitability management via real-time supply chain and customer care management, profitability forecasting via real-time supply chain management, and customer relationship via real-time integration of manufacturing scheduling, inventory and manufacturing resources management, and customer service support.

In yet another implementation of this method, by means of the hybrid functionality, ZLE core services, clip-on applications and enterprise applications the enterprise can conduct telecommunications business. In relation to its telecommunications business, the enterprise can perform business intelligence via real-time customer service response, profitability forecasting and risk management via real-time fraud pattern detection and management, campaign and customer relationship via real-time chum management and customer service support management, profitability management and cross-selling of bundled services via real-time profitability analysis by evaluation of route, product and call margins for every customer.

Advantages of the invention will be understood by those skilled in the art, in part, from the description that follows. Advantages of the invention will be further realized and attained from practice of the invention disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and together with the description, serve to explain the principles of the invention. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like elements.

FIG. 1 shows two disjointed infrastructures that cannot leverage each other in real-time.

FIG. 2 illustrates the zero latency enterprise (ZLE) model.

FIG. 3 describes a commercial business with its associated service connections.

FIG. 4 shows the reality of latencies in operations and in interactions with and responses to consumers, which prompted enterprises to seek solutions for reducing latencies.

FIG. 5 illustrates how an enterprise, running as a ZLE, can conduct instant, personalized marketing (based on known or knowable customer preferences) scored and fine-tuned in real time while the customer is engaged.

FIG. 6 is an example of a retail organization.

FIG. 7 shows a ZLE with all its enterprise customer contact sites (including systems and applications) integrated, responsive and personal.

FIG. 8 illustrates the ZLE model as a blueprint for ZLE architecture.

FIG. 9 illustrates a ZLE framework that defines, in the preferred embodiment, a multilevel architecture (ZLE architecture) centered on a virtual hub.

FIG. 10 illustrates the core of the ZLE framework.

FIG. 11 illustrates a ZLE framework with a different application server that can be based on Tuxedo, CORBA or Java technologies.

FIGS. 12a-c illustrate lookup data that includes data not modified by transactions or interactions (i.e., an historic account of prior activity). FIG. 12a also illustrates how the interaction manager and rules engine can cooperate to produce a prompt or response in connection with a particular type of business.

FIGS. 13, and 13a-d illustrate clip-on applications such as for fraud detection, customer interaction and personalization, customer data management, narrowcasting, and so on. FIG. 13a further illustrates how the interaction manager and rules engine can cooperate to produce a prompt or response in connection with a particular type of business.

FIG. 14 shows bulk data (e.g., real-time customer data) retrieved and delivered from the operational data store (ODS) to the analysis applications.

FIG. 15 illustrates applications such as Broadvision or Siebel's customer relationship management (CRM) applications that are logically integrated into (docked) rather than being interfaced with the ZLE framework.

DETAILED DESCRIPTION OF THE INVENTION

The present invention relates to information technology (IT) and, specifically, to reducing latencies in an IT infrastructure to enables a zero latency enterprise (ZLE). As a functional and architectural strategy, the invention contemplates a ZLE framework with a hybrid functionality that is fashioned by the merger of enterprise application integration (EAI), dynamic real-time operational data warehousing, transaction processing and monitoring, data mining and analysis and feedback mechanism (See: FIG. 2 for the ZLE model). The invention further contemplates the ZLE architecture, a multilevel architecture that supports the ZLE framework. This scheme enables the enterprise to integrate its services, applications and data in real time. In other words, it enables the enterprise to run as a ZLE.

To enable one of ordinary skill in the art to make and use the invention, the description of the invention is presented herein in the context of a patent application and its requirements. Although the invention will be described in accordance with the shown embodiments, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the scope and spirit of the invention.

The meaning imparted to the terms below and throughout this paper is intended not as a limitation but merely to convey character or property relevant to the present invention. Where the terms have a special meaning or a meaning that is inapposite to accepted meaning in the art, the value of such meaning is not intended to be sacrificed to well-worn phrases or terms.

Enterprise--refers to any organization, including a business organization, its subsidiaries, departments, divisions, sections, sectors, groups, branches, channels or like parts; and it can include any partners, affiliates and associates of the organization. An organization includes its resources such as one or more people, systems, databases, policies and more.

Enterprise-wide or across the enterprise--refers, depending on the context, to anywhere within or about the enterprise, in all parts of the enterprise, all over the enterprise, all around the enterprise, across all enterprise products, services, and channels, between any sites of or associated with the enterprise, or at any site of or associated with the enterprise.

Extensible--refers to any one or the combination of scalable, extendable and expandable. Scalability relates to size, extendibility relates to volume and expandability relates to capacity. For example, the ZLE framework and architecture are extensible. With the ZLE framework and architecture, an enterprise is also extensible.

Scalable--refers to the ability to improve performance by extending the size of an enterprise, a system or an element thereof. Scalability of an enterprise enables it to run as a virtual enterprise (i.e., performing the functions of an entity beyond what is really there). For example, scalability allows an enterprise with exhausted manufacturing capacity to push production overflows to its partners or affiliates. Namely, running as a virtual enterprise, the enterprise can extend its existing capacity through manufacturing-on-demand by its business partners; and the partners have visibility to the enterprise so that they can stay informed and be prepared to respond. Scalability of a system involves adding components to the system. Scalability of the system allows sizing it for better performance when the volume of transactions increases.

Available--refers generally to an enterprise or system `being there` even in the face of failure or absence of a part thereof. For example, an enterprise is available when it continues to conduct its business unimpeded even if a part of the enterprise is shut down. A system is available when it continues processing transactions even if it suffers a component failure

Real-time--refers to immediately or almost immediately; or the actual time, nearly the actual time or within seconds from the actual time during which an event or a process transpires, or pertains to the performance of a computation or other action nearly or at the actual time of a related event or process so as to render an instantaneous, up-to-the-second or up-to-the-minute result therefrom.

Zero Latency--refers to real-time or substantially real time. In terms of a system, zero latency is substantially no delay between the desired and actual response time. In the context of an enterprise, zero latency is about real-time or near real-time operations, processing and application of information to achieve a competitive advantage, hence the term zero-latency enterprise (ZLE). As will become evident from the description herein, in the context of the present invention, the term `ZLE` defines a broader term than the conventional ZLE term. And, to properly distinguish it from the conventional term, one might use the term Compaq ZLE.TM. (the present invention was developed at Compaq Computer Corporation in Houston, Tex.). However, to simplify the discussion herein, the term `ZLE` is used instead.

Coherent view--refers to substantial congruity of the views from any part of the enterprise, or an enterprise-wide view of information, such as data, business transactions and their status, as well as an historic account thereof, that is consistent throughout the enterprise regardless from where in the enterprise the view is obtained. The View of information can include access for loads, extractions and queries.

Loosely coupled applications--refers to applications that can function as stand-alone applications and that when integrated with the ZLE framework are operationally independent and not relying on each other for obtaining information although they share that information. The information is accessible by the loosely coupled applications from a shared operational data store (ODS) so that data dependencies between requesting and responding applications are removed.

Tightly coupled applications--refers to applications that are not stand-alone and are tightly integrated into the ZLE framework. Tightly integrated functionality--e.g., event capture, data extraction, rules, workflow, message transports and transformations--becomes part of the ZLE core functionality.

Docking--refers to interfacing, integrating or adding (e.g., adding applications or solutions that extend the IT infrastructure functionality and, in turn, that of the enterprise).

Bulk data--refers to data in mass or at least in a cluster or block.

Customer--referred to also as consumer, client, visitor or guest, is any entity, individual, or organization that can receive and consume a value. In a system sense, a customer can be another system or application (e.g., an enterprise application is an `end-customer` of the ZLE core as will be explained below).

Value--refers to any service, item for consumption, resource, product, creation, knowledge, information, action, etc. produced by or in association with the enterprise, internally or externally. A value is typically produced for the benefit of the customer.

Business--refers to any character, undertaking or functionality of an organization, be it a commercial business or any other type of organization (e.g., a commercial conglomerate, global charitable organization, governmental agency, military organization, a local agency, such as law enforcement or emergency response, with affiliation to other local agencies, and more).

Business transaction--refers to any operation or process associated with the business. A business transaction can be one or a series of business transactions, discrete or related to each other. A business transaction can be single or multi-phased, short or ongoing.

Event--refers, depending on the context, to an event occurring anywhere across the enterprise in the course of conducting the business of the enterprise or an event occurring in any part of the IT infrastructure of the enterprise upon commencement, in response to, during or after completion of a business transaction. One type of event can produce the other or can occur in combination with the other. Namely, an event can be any commencement or completion of a business transaction, any state change of a business transaction, any data entry or data change associated with the business or business transaction, any inquiry or outcome associated with a business transaction and more. An event may produce a result, and the result, if any, may itself be an event. An event may unlock or prompt the commencement of one or more business transactions. An event may lock or prompt the ending of one or more business transactions. The locking or unlocking may also be events. An event may be a single occurrence or a series of events. Several examples can be provided to illustrate the above. In one example, an event can be a customer providing a new address or a `yes` answer to a query about a new address. In a second example, an event and a result, which is a `notable` event, can be the recording of a new prescription at a local pharmacy and prompting notification about a new drug interaction related to the prescription from somewhere else. A third example of an event involves an on-line order of a gift certificate somewhere in the country for a recipient that opened a gift registry account in a store somewhere else. In a fourth example involving a series of events a disaster alert is followed by hazardous chemicals data associated therewith. A fifth example involving a series of events can be an attempt to return merchandise almost immediately followed by a fraud alert or a credit status change. Finally, in a sixth example an event can be an inventory-level change for an item in a warehouse or production shop.

Indicia--refers to any detectable thing associated with an event, including any information related to the event. The information can contain one or a combination of data, transaction state(s), look-up data (an historic account) and the like. It is noted that the occurrence of an event can be detected by capturing the indicia of its occurrence.

Transaction--refers to a collection of operations on the state of an application. A transaction is typically triggered by a request or input message that prompts an operation. A transaction trigger may include one or any combination of event, condition and action resulting from the transaction (operation). An action can itself be an event or a cascade of events.

Application--refers to a program or software embodied in a computer readable medium and including computer readable program-code that causes a computer to perform a certain task. An application can spawn a transaction, and preferably a plurality of concurrent transactions.

Services--refers to, in one sense, to enterprise services provided in the course of conducting the enterprise business (See, e.g., FIG. 3 which describes a commercial business with its associated service connections). In terms of the IT infrastructure, the term `services` refers to any applications that enable the enterprise to run as a ZLE by adding functionality to the IT infrastructure. In the context of the ZLE architecture `services` can be one or any combination of applications that provide integration services, ZLE native services, core ISV services (ISV-independent solution providers), unified rules services, workflow services, message transformation services, extraction, transformation and load (ETL) service and the like. `ZLE services` are core services and capabilities, where core services include native services and core ISV services. Loosely coupled applications can be consumers or clients of such services.

Central repository--refers to a sharable unified capacity such as the operational data store (ODS) with a relational database management system (RDBMS) in the ZLE framework as defined herein. Although a central repository can be in a single physical device or located in a single physical location, the central repository may be configured in a distributed storage system that is nonetheless accessible from across the enterprise.

As mentioned, the present invention was developed at Compaq Computer Corporation of Houston, Tex., and it relates to enterprise information technology infrastructure. The present invention provides Compaq ZLE framework and architecture of an information system as well as methods for enabling an extensible zero-latency enterprise with an extensible information technology infrastructure.

Although it would be more accurate to use the term Compaq ZLE.TM., the term ZLE is used instead for simplicity. For further simplicity, a ZLE enterprise equipped with IT infrastructure configured in accordance with the present invention is referred to in short as ZLE or enterprise running as a ZLE.

ZLE: Overview

First, the vision--with zero latency, an enterprise can achieve coherent operations, efficient economics and competitive advantage. This is in view of the reality of e-commerce, that prompted enterprises to change their business models and to integrate e-commerce with other business models. Moreover, as shown in FIG. 4, the reality of latencies in operations and in interactions with and responses to consumers prompted enterprises to seek solutions for reducing latencies. Notably, what is true for a single system is also true for an enterprise--reduce latency to zero and you have an instant response. In an enterprise running as a ZLE, there can be enterprise-wide recognition and capturing of business events that can immediately trigger appropriate actions across all other parts of the enterprise and beyond. Along the way, the enterprise gains real-time access to a real-time, consolidated view of the its operations and data from anywhere across the enterprise, and operational inconsistencies are thus eliminated. The entire enterprise can become more responsive and competitive via a unified, up-to-the-second view of individual customer interactions with any part(s) of the enterprise, their transactions, and their behavior (See, again FIG. 3). Moreover, as FIG. 5 illustrates, an enterprise running as a ZLE and using its feedback mechanism can conduct instant, personalized marketing (based on known or knowable customer preferences 24) scored and fine-tuned in real time while the customer is engaged 20. This result is possible because of the real-time access to the customer's profile (e.g., 24) and enterprise-wide rules and policies 22 (while interacting with the customer 20). What is more, a ZLE achieves faster time to market for new products and services 26, reduced exposure to fraud, customer attrition, and other business risks. In addition, an enterprise running as a ZLE has the tools for managing its rapidly evolving resources (e.g., workforce) and business processes.

For example, in a retail organization such as the one shown in FIG. 6, the resources include people, systems, databases and policies. An enterprise running as a ZLE can improve its business and gain competitive edge by managing the evolution of its resources. As shown in FIG. 7, in a ZLE all enterprise customer contact sites (including systems and applications) are integrated, responsive and personal. Moreover, an enterprise running as a ZLE creates a view of customers data 30 that is consistent across the enterprise and available substantially simultaneously enterprise-wide.

Indeed, in a ZLE information becomes available everywhere across the enterprise in real-time. For example, suppose a clerk records a product shipment transaction into an enterprise resource at a particular enterprise site. Almost immedi