Joe McKendrick, ebizQ's SOA in Action Blogger, is a nationally published author and consultant
with deep knowledge and insights regarding trends and developments in
the technology industry. He is a contributing editor to a number of
national and international publications and Websites including
Database Trends & Applications, ZDNet, and Webservices.Org. He also
serves as analyst for Evans Data Corp., and is lead analyst for Evans'
Web services and enterprise development management issues surveys.
SOA in Action Blog
|
May 10, 2008
Event Driven: What Enterprises Can Learn from Zebras Behold the zebra in the wild savanna -- when a it senses the presence of a lion, it knows to run away, as fast as it can. When it senses food supplies, it knows to act. Do today's companies have this much situational awareness, and an ability to act quickly to survive and thrive? Not yet, but thanks to new approaches such as complex event processing, they're getting there, according to Gartner VP Roy Schulte. "We can teach computers to do what a zebra does," Roy said. "To collect and process event data to respond quickly and effectively." In his keynote kicking off ebizQ's recent Event Processing virtual conference, Schulte broke down the essential pieces of complex event processing, and describing how businesses can leverage CEP, or being able to act, in real time, on multiple streams of event data flowing in from different parts of the enterprise. "The value of complex event processing, overall, can be summarized as improving situation awareness. Simply put, that is just knowing what is going on, so you can figure out what to do." The benefits of complex event processing, Schulte said, include better decision quality, faster response times, reduced information glut, and reduced costs. Schulte defined a business event as a "meaningful change in a state that is something that is relevant to the business. Examples include depositing or withdrawing money from a bank, submitting a purchase order, or hiring an employee." There is also a second term, "event object," that describes how the event is packaged for processing, typically as an XML document these days. "We have to record events using event objects so computers can receive them and do computations on those events," Schulte said. However, while all companies have always been event driven -- with millions, if not billions, of events in a single day, most events are still handled manually, by people, not computers. "At any one second, a large company has on its network anywhere from 10,000 to 10 billion business events," Schulte explained. "At the low end, that's almost a billion events per day -- at the high end, that’s almost a trillion events per day." The challenge is that most of the stovepiped and legacy applications that power enterprises are not yet event driven, Schulte observes. But there's great practicality in automating the ability to capture and make decisions on multiple event streams coming into the core business systems, Schulte says. "For example, you can have a complex event that says, ‘this mornings sales were 30% above our daily average.' That of course is much easier to digest and act on than sending a person 500 detailed sales records, and making the person compute what happened that day manually." The growing array of sensors, such as RFID tags, combined with front-end systems such as business activity monitoring (BAM) dashboards make complex event processing a reality with today's technology, Schulte points out. "In many cases, the complex event processing system Is just a front end being used for decision support. The output of the CEP engine is sent to a person through a BAM dashboard, or through an alert such as email or SMA or an Atom or RSS feed. in this case, we have a two-stage computation. In the first stage we’re using a computer to narrow down the data. And in the second stage, we still have a person involved to do the final analysis. However, things could get interesting as CEP systems develop, Schulte added. Namely, the need for human processing could be taken out of the equation all together. "We can bypass that person entirely; we can build enough smarts into the complex event processing engine to determine the specific response that is needed." Schulte provided a working example of complex event processing in action within the airline industry: "In large airlines, there is an event oriented middleware that... acts as an enterprise nervous system. Information from hundreds of sources, including sensors on board the aircraft, information coming in from the FAA, and information coming in from standard systems is sent to the enterprise nervous system, and is temporarily stored in event databases. It helps to create the data, the outgoing alerts and notifications that is sent to hundreds of applications on the consuming side to respond to threat and opportunity situations as they emerge. By having information quickly, each of these systems in their respective departments can respond faster. ...Information helps the fueling and maintenance management applications to change their schedules and so forth. By using an event based system, the turnaround time of each plane can be shortened… Fewer airplanes are needed to handle the same schedule." ______________________________________________________________________ Posted by joemckendrick in Business Process Management • Data Management • Event Processing • Management • SOA • SOA Events • SOA Research and Analyst Reports | Permalink | Comments (0) | TrackBacks (0) May 09, 2008SOA on the Move Oracle's Dave Chappell has always done a great job of linking SOA efforts to measurable business results, and he recently posted an account of a busy online service that was able to integrate its widespread base of customer systems into a well-integrated service layer. Move Inc., a growing online real estate provider, had what Oracle's Dave deemed a "tall order:" consolidating disparate applications across two business units into an enterprise CRM solution that could provide a single, accurate view of customer data to improve efficiencies and automate auditing, billing and fulfillment processes. Move Inc. (formerly Homestore, Inc.) provides information on real estate property listings (homes and apartments), moving, home and garden and home finance through its network of online sites, which includes www.realtor.com, www.welcomewagon.com, and www.moving.com. Tall order indeed. As Dave describes it, Move had systems and touchpoints all over the map. CRM applications were built on .NET, and there were numerous disparate systems and manual touchpoints built to support various business functions for CRM. The company developed a SOA that focused on re-usability of services, with business processes were at least as efficient if not better than what the current systems offered. Using standard WSDL interfaces, Oracle BPEL PM and Oracle ESB were used to extend the reach and normalize the integration across Siebel CRM, PeopleSoft Enterprise Financial Management and other systems both internal and external The consolidated customer database is intended to provide support for existing sales activities, order capture, integration with fulfillment systems, integration of customer usage from Web sites into Siebel, and integration to PeopleSoft Billing. The solution involves the use of BPEL, Web services, ESB Mediation, application adapters, and canonical data models. The project took six months to implement and deploy, Dave reports -- actually, pretty good timing for such an effort. Move was able to achieve both quicker and real-time integration across these systems, and saw a reduction in cost of ownership on existing applications. "It's always great to hear about successful adoption of SOA, and its particularly exciting when its being used for what you'd think," Dave remarked. ______________________________________________________________________ Posted by joemckendrick in Case Study • Management • SOA | Permalink | Comments (0) | TrackBacks (0) |



















