Archive for the 'Business Rules' Category

Gratitude and Shameless Commerce All Together in a Single Post

Tuesday, January 9th, 2007

(Posted by guest blogger and ersatz technology evangelist, Ian Turvill.)

James's "likelihood to blog score" rates very low today, so it's up to me again. As I was casting around today for things to comment on, a press release arrived in my inbox from Fair Isaac's public relations department.

"IDG’s InfoWorld has honored Fair Isaac with the 2007 Technology of the Year Award for Best Business Rules Management System," it said. Cool, I said to myself, causing everyone in the cubes around to me to wonder what was going on this time, I bet that's something James's readers will want to know about. So, at the risk of a shameless plug for Fair Isaac's technology, here's some bullet points from the release:

  • InfoWorld’s annual Technology of the Year Awards recognize the top technologies that made the greatest impact on enterprise IT strategies during the past year.

  • "Blaze Advisor has always been one of the most friendly of the BRMS tools to business users, providing pleasant graphical development environments and understandable rule flow charts, decision tables, rules trees, and object models. Version 6.1, thanks to the incorporation of Rete III, now moves Blaze into the front of the pack in performance."

Complete details on InfoWorld’s 2007 Technology of the Year Awards can be found at http://www.infoworld.com/4841 and the January 1 print edition of InfoWorld. The awards encompass a number of areas that will be of interest to our blog's more technologically-oriented readers, including:

  • Application development, including business rules management, AJAX toolkits, Java test tools, and more
  • Applications, including Exchange management tools, and portals
  • Data Management, including enterprise search, RSS management, and more
  • Hardware, including workstations, servers, and systems management tools
  • Networking, including WAN accelerator, 10 Gigabit Ethernet switches, network analysis applications, and more
  • Platforms, including Linux desktops, servers, and application virtualization
  • Security, including anti-spam tools, data leak preventers, UTM appliances, and more
  • Storage, including e-mail archiving, tape libraries, and networked storage

The awards are selected by InfoWorld's Test Center editors and reviewers, but Blaze Advisor's performance rests on the hard work and innovation of our talented development staff, and (more importantly) on the feedback from our clients who use it to power high-volume operational decision automation applications in insurance, financial services, retail, and elsewhere. So, thanks to you!

Technorati Tags: , , , ,

Congratulations to the Blaze Advisor team

Tuesday, January 9th, 2007

Just a quick post today to congratulate my colleagues in the Blaze Advisor team for taking this year's InfoWorld Technology of the Year Award for Business Rules Management System prize. The full review of Blaze Advisor, and of ILOG JRules, was published by InfoWorld here.

I think this is good news for two reaons. Firstly I work in the same building as most of the Blaze Advisor team and they're a great bunch. Secondly I am glad that InfoWorld thinks Business Rules Management Systems deserve to be a category. Far too many projects are still going on where business logic is buried in code instead of managed as business rules. More visibility for the category can only help. You can read the Fair Isaac press release here

Technorati Tags: , , ,

Some more business rules predictions for 2007

Friday, January 5th, 2007

I got a couple of late entries for business rules predictions I thought I would share:

First Krzysztof Karski of Artemis Alliance (who sometimes blogs here)

  • Business Analysts, and companies as a whole, are realizing that they need to keep track of rules and so any software that enables their business users to do so will be big in 2007.
    • Managing business rules is becoming important (this would include both operational rules and other) not just executing them.
    • I think a trend that was clearly seen at this year's BR Forum is the increased focus on the business part of business rules.
    • Many rule engine vendors are moving towards even more business friendly versions of rule engines and quite a few vendors of pure rule management software have sprung up.
  • I also think this year is the first that open source business rules will really hit the spotlight and traditional BRE vendors will start seeing serious competition from project such as JBoss Rules. Tech savvy IT departments are seeing a lot of value in open source and so moving that philosophy to rule engines will be a natural especially since the quality of their Rules IDE is moving very close to many vendor offerings.
  • Overall, I think 2006 was a rules momentum building year, 2007 will be the year business rules really go mainstream.

Secondly Dan Selman of ILOG who administers the JavaRules.Org site:

  • Overall I believe this year will be one of incremental improvement and refinement, not revolution
  • The use of Business Rules Management Systems will continue to slowly but surely to grown within successful SOA and BPM deployments.
  • The focus on governance for SOA and BPM will drives new customers into the BRMS market segment.
    Customers that are keen to realize many of the benefits of transparency afforded by business rules.
  • There will be some painful BRMS project failures as companies new to the technology apply it poorly with little consideration for performance or long term rule maintenance and governance.
  • Major Systems Integrators will establish centers of excellence and best practices for BRMS technology.
  • Increasing numbers of application architects will understand the role of a BRMS within the overall application stack.
    A small but vocal group of architects will help evangelize the technology to their peers.
  • BRMS vendors will continue to refine their product offerings, making them easier to use, accessible, and scalable for general purpose usage.
  • The first tentative fruits of standardization efforts start to emerge.
    Naturally they will be less than hoped for by the wider community.
  • Within the largest and most mature BRMS deployments deep personalization, repository federation and delegated administration start to become relevant
  • Some consolidation amongst BRMS vendors occurs
  • The relationship between BRMS rule management user interface and end-user application user interface continues to be a challenge for vendors.
    BRMS users push for flexible integration options that span a broad range of technologies, including Swing, SWT, JSP, AJAX , ASP, WSRP, portlets.

Interesting points and both Dan and Krzysztof see the same trends I do - SOA/BPMS are driving demand for rules as is a general desire on the part of the business to take control of their rules.

Technorati Tags: ,

Some predictions for 2007

Thursday, January 4th, 2007

Towards the end of last year I asked various people to make some predictions for 2007. Here, in no particular order, is what they said. Interestingly pricing and customer-centricity both came up more than once.

Bruce Richardson, Chief Research Officer of AMR Research sent me this one (though I am not sure he is serious)

  • EDM will revolutionize professional sports, particularly baseball and football. Take football, especially this week’s Wild Card match up between the Patriots and the Jets.
    • As the Pats coach breaks down game film, he enters data on how the quarterback responded to the defense (or vice versa) depending upon which down, yardage needed to first down, field position, score, time left in the half or game, field conditions, etc.
    • All of this gets coded and entered into a computer.
    • All of the data is stored and analyzed, and rules are generated - If 3rd and 15 with plenty of time and only one blocker in the backfield, the defense should...
    • Rather than consult those plastic-coated charts with plays on them, the coaches watching from the skybox enter the formations into a handheld or laptop.
    • The computer responds with a series of probabilities based on the best historical matches as well as input from the team’s head coach.
    • These results in the new rules.
    • Eventually, self-learning robots replace players...

Mike Schoeffler, President of Profitdesk Software had this to say:

  • A nomination for the next big decision automation in an industry: bank loan and deposit pricing. Behind the scenes, one industry after another has automated pricing of their products - airlines, clothing stores, supermarkets. Bank pricing is equally broken. It is often guided by C-level executives, who rely upon their intuition and art because the tools have not been available. The changes this year will be invisible to customers if implemented properly, but will noticeably expand bank profits, even in an inverted yield curve.

David Raab of Client X Client had a couple of hot trends:

  • Complex event processing: the notion of linking and finding patterns in multiple customer activities and using these to guide customer treatments. No different from normal customer management, except that it requires more sophisticated technology and richer data, including customer activities, customer profiles, environmental inputs (location, competitor behavior, weather, economic news, etc.) and business situation (products, inventory, etc.) Yes, it's yet another perfect application for EDM.
  • Marketing mix modeling: part of underlying marketing ROI and optimizing marketing investments as a result. It's becoming a feature of marketing resource management systems, which are a logical home because they have all the information on marketing programs to begin with. But you need to add more information on results and more sophisticated analytics to make it the mix modeling possible.
  • Both trends build on the wider accessibility of customer data, both as captured in enterprise warehouses and as visible in place through service oriented architecture, and on customer data integration technologies that make it easier to assemble the data from different sources and relate it to individual customers. Both also point to a need for over-arching management of the customer experience across all interactions (their specialty at Client X Client).

Barb von Halle and Larry Goldberg of KPI had a couple:

  • There will be at least one, maybe two, new business-friendly software products available by 2Q2007 through which business-focused (not technology-focused) rule authors can write rules independent of a BRMS. Possibly with generation into 1 or 2 BRMS products
  • There will emerge a business rule formalism that we believe will enable business rules and Enterprise Decision Management to integrate well in an SOA world by 3Q2007.

Henry Morris of IDC said

  • In 2007, we will see delivery of more industry-specific composite applications that combine transactional, analytic, and collaborative decision-making tasks. Pricing decisions (which have a distinct vertical flavor) will be a popular subject area for these applications -- monitor changes to demand, analyze new trends, adjust the price in the transactional system, monitor, etc. Some will be packaged; many will be custom-built. The packaged applications will require extensive on-site customization. Providing an interface for model-based configuration and customization (at a level of abstraction suitable for business analysts) will be a differentiator for the packaged composite applications.

Sandy Kemsley, my fellow blogger over on ebizQ, had a piece on 2007 trends here and highlighted this one:

  • There are two more Web 2.0 characteristics that I think we're going to start seeing in BPM in 2007: tagging and process syndication. Tagging would allow anyone to add free form keywords to a process instance (for example, one that required special handling) to make it easier to find that instance in the future by searching on the keywords. Process event syndication would allow internal and external process participants to "subscribe" to a process, and feed that process' events into a standard feed reader in order to monitor the process, thereby improving visibility into the process through the use of existing feed technologies such as RSS (Really Simple Syndication).

Ian Turvill, the other regular blogger on this blog, had a couple too:

  • Increasingly, retailers will see Enterprise Decision Management as a key way in which they can drive customer centricity across the organization. A "Customer Centric" enterprise is one that delivers marketing, sales, and service to strategically distinct segments in very different ways so as to maximize the overall customer portfolio value. Customer Centricity is an approach which has been used by leading retailers, such as Best Buy and Tesco, as well as other recognized consumer service organizations, such as Harrah’s and Royal Bank of Canada, to achieve substantially superior financial performance. Customer Centricity involves five key steps:
    • Understanding the current and potential lifetime value of customer relationships
    • Explicitly choosing and focusing on a select set of customer segments
    • Understand those customers in depth, including how to build larger relationships with them
    • Engineering a "winning" value proposition across these customers’ entire shopping experience, including marketing, sales, and service
    • Aligning the enterprise around delivering that proposition
  • Insurance companies will adopt Decision Services to get better Decision-Making across the board. Insurers are recognizing that the benefits of predictive analytics and decision automation that they have seen in personal lines underwriting can also be realized in other functions and in other lines of business. They will respond by creating a separate decision-making capability an inherent part of their overall information technology architecture through the creation of "decision services". A similar prediction has been made before. In a July 2005 report, Karen Pauli, a Senior Analyst at TowerGroup, stated that: "The insurers that will survive this competitive environment are those that leverage technology to advance their business and operations. . . . One of the primary ways insurers are transforming their infrastructure is by supporting the insurance value chain in a modular way, such that applications are not all in one and can decouple and share some core components. . . .". What makes 2007 different is the rapid and widespread adoption of Service Oriented Architectures, which make it now possible to deploy the applications which exploit the SOA approach.

Craig Dillon, who heads up our ScoreNet business here at Fair Isaac, had another (he and I presented on Decision Service Providers recently).

  • Technologies that control business rules will enable companies to increasingly move key decision points outside their four walls, enabling new classes of business process outsourcing. This will enable a new class of business – BPO networks with embedded business rules running at the hub.

As for yours truly, I have a couple:

  • Every BI vendor will talk about having predictive analytics as a core component of their technology. Few of them will actually manage this.
  • Every BPM vendor with long term prospects will partner with a major BRMS vendor and multiple integrated solutions will start to emerge.
  • The idea of decisioning and decision services as a class of development will become mainstream or at least more mainstream.
  • BRMS vendors will devote much of 2007 to improving the ability of business users to test, check and manage business rules
  • Predictive Analytic workbench vendors will focus more and more on deployment of the models, not just development of them
  • Some useful standards will be published and increasingly adopted in business rules and analytics, increasing the speed of adoption
  • A really great book will get published on EDM and all the readers of this blog will buy multiple copies for their friends and family enabling the authors to take well-earned vacations in paradise.

One more thing. There was a nice 2007 Trends article over on Intelligent Enterprise about which I blogged here.

Technorati Tags: , , , , , , , , , , , , , , ,

Using business rules to write maintainable code

Thursday, December 28th, 2006

Reddit pointed me to this post on "Writing Maintainable Code" by Jeremy D. Miller over on CodeBetter.com. It's a nice article and I look forward to reading the rest of his posts on this topic.There's lots of good stuff but a number of his comments led me to dig up some of my posts on maintainability and agility:

"Enable Change or Else!" because "Change is a constant in an enterprise software system"

Regular readers will know how much I agree with this. I have written before about how rules can help you love change and construct dynamic applications built with change in mind. Using business rules for core business logic can also help you respond to changing requirements. This is sometimes called business agility and I wrote some notes on agility based on some Gartner research on this topic.

"single most important quality for an enterprise software system is maintainability"

I recently posted on using rules to avoid "write only" code and on using rules to improve the application maintenance process.

Jeremy has "a strong preference for creating maintainable code throughout the codebase" rather than building in points of extensibility.

While I think he is right, I also think that the reality is that some parts of an application will have change driven by business users and some by more technical requirements.. Jeremy asks the question "where should this code go" and I think there should be a follow-up question of "what kind of code should this be". Assuming that everything in an application should be code is a risk as there is a problem with (our expectations of) programmers. After all you have to remember the different perspectives of programmers and business people.

Jeremy then lists some great questions along with proposed approaches to address them. Some of them seem to me to relate very strongly to business rules:

  • Can I find the code related to the problem or the requested change?
    And once I find it can someone who understands the change also read the code?
  • Can I understand the code?
    And who am "I"? A programmer or someone who runs the business?
  • Is it easy to change the code?
    Can I change the "rules" and put new rules into production without downtime?
  • Can I quickly verify my changes in isolation?
  • Can I make the change with a low risk of breaking existing features?
  • Will I know if and why something is broken?

All these points lead to me repeat some of my thoughts on why business rules can be better than code and on business user rule maintenance secrets.

Lastly he has a very strong focus on the value of layering and separation of concerns. He identifies one layer as "Business logic, rules, domain model". Could not agree more.

As an aside he also talks about agile methods. I have posted a virtual conversation with Scott Ambler on rules and agile approaches and an article on the same topic if you are interested.

Technorati Tags: , , , , , , , , ,

Here’s a way to take advantage of mobile devices

Thursday, December 21st, 2006

I saw this post by David Raab over on his blog - Business Intelligence on Smart Phones: Not Just Humbug. Like the author of the original article to which David refers (Power Of A Data Warehouse In The Palm Of Your Hand by Elena Malykhina) I am cynical. Her comment that "It remains to be seen how many mobile professionals actually need to slice and dice data from handheld devices" really struck a chord with me. I don't see even weary road warriors wanting to do "traditional" BI on a smartphone. But as David correctly points out the follow-up question is interesting:

The more intriguing question is what new business intelligence functions a smart phone platform would make possible

Now substitute the works "decision management" for "business intelligence" and I think you are on to something. One of the the differences between BI and EDM is the focus on taking action using insight gained from data rather than showing someone the data and helping them gain some insight. I would say that David's examples are all, in fact, EDM examples. They use the information the phone has (position), insight from the data the company has (fraud likelihood, wait times) to take an action (dispatch the person with the phone to a particular place, tell them to do or not do something). I don't see traditional BI vendors having much to offer here - the whole reporting/OLAP infrastructure they have developed is predicated on knowledge workers doing analysis. If you want to take advantage of mobile devices you need to think about automating decisions for the person holding the device. For instance:

  • Use mobile phones held by maintenance engineers to track their location and then use analytics to predict which pieces of equipment are most likely to fail soon and rules to assign the nearest, qualified engineer before sending the directions on where to go to the engineers phone.
    • Don't show them reliability graphs or travel times, tell them where to go to make best use of their time
  • Use the mobile phone of a real estate appraiser to find out which risk zones a property is in and what the predicted difference is between a house inside and outside that risk zone
    • Don't show them a picture of the risk zones
  • Use a doctor's mobile phone to route them to the most useful hospital during an emergency based on predictions of patient load, the hospitals they know and their specialties
    • Don't show them graphs of wait times and pie charts of specialties needed
  • Use a customer's mobile phone to make them an offer at a store that is nearby having predicted that they are likely to buy it, checked that is in stock there and estimated that they are more likely to respond in person than to an email promotion to the website

And so on. Automate decisions and use mobile devices to provide context for those decisions and to deliver decisions to people out and about. Don't send them reports. Please.

I have blogged before about the value of location information in automation of decisions and on location intelligence with EDM and wrote an article in BI Journal (subscription required) with Ed Gandorf of MapInfo "Driving Decision Automation with Location Intelligence".

P.S. An extreme example of this might be something like pay-as-you-drive insurance as described by my colleague Ian.

Technorati Tags: , , , , , , , , , , ,

A media story

Saturday, December 16th, 2006

Some time ago I posted a comparison of how a bank operated with how an EDM process might work (A banking story). Thanks to a friend I have another example is this genre - this time from the news media.

Old Way

A former subscriber to the Wall Street Journal (WSJ) she received an offer in the mail designed to entice her back - the offer included both the print edition and the online wsj.com. The offer came in a personalized letter and had various codes identifying it. The offer came from "The Wall Street Journal. Print & Online".

  • Deciding to pay online she found a different set of offers with no apparent way to enter any of the codes from the offer letter. Nevertheless one seemed to match and so she signed up for it.
  • The first print issue arrived promptly but no information was forthcoming on the online subscription
  • A short email conversation ensured which, in the end, yielded an acknowledgment of the deal and instructions for signing up online
  • She tried to follow the email instructions but they didn’t work. When it asked for the print account number she got an error message “account already in use” on page 1 of the create account pages
  • She called the WSJ online and got a long menu of options which kept repeating what she could do online but otherwise was not helpful. After a long wait she got a Customer Service Rep (CSR). The CSR was confused by the offer but then the CSR said that she had an old account (my friend's a lapsed subscriber remember) and the CSR said it was fixed it right then, My friend tried it and sure enough the error “account already in use” went away
  • Having got past page 1 of the process (there are 4), she got to Page 3 which asked which billing period she would prefer. Of course she had already paid so she called back (same long menu, same repeated instructions, some long wait). This time she got another CSR who was also confused by the offer. After reading the notes this CSR said that “print didn’t set up a combo account” and told my friend she had to call them. The CSR transferred her but then she went back in the queue (same long menu, same repeated instructions, another long wait).
  • She then got a print CSR who said the system showed that my friend had been a print customer since 2004 and the offer was only available to new subscribers.
  • Through gritted teeth my friend explained that the offer was explicitly sent to lapsed subscribers and that it was good for anyone who had not been a subscriber in the last 180 days and furthermore that sheI had been doing this now for 30’ or more and was going to get very cranky. The new CSR read all the (now very long) notes and emails, put her on hold twice, then eventually popped on and said you now have a combo account, wait 24 hours then call online or try again.
  • 9 hours later she received an email from the online part of WSJ with instructions to set up the account and it worked.

A long-winded, customer-hostile process that damaged their brand, annoyed a customer and cost them a ton of money in CSR time (while also increasing the delays for everyone else trying to get a CSR with a knock-on customer service impact). How could this have been done better?

EDM way

  • The online environment would have had the ability to ask for offer codes or address so as to identify the customer initially
  • The online form would have shown the same offer as the offline and created the account the right way the first time
  • Even if the customer had lost the code and signed up for the wrong offer online, the CSRs would all have seen the same offers available to the customer as the system would run the eligibility rules and display those for which the customer was eligible. The systems the CSR used would have allowed them all to trigger the allowed decisions, there would be no transferring to different CSRs.
  • When signing up for the online service the re-use of the account number would have caused a sensible decision (like questions to see if this person is the same as the one who has the account in the system) not an error message.
  • Similarly when it got to the billing part if would have checked the account and seen that a fee had been paid that made the customer eligible for both online and print editions (it would know she was a returning customer who had been gone more than 180 days and who was therefore eligible for the combined service offer and that she had paid the amount associated with that offer). It would then have displayed the existing billing data, confirming the included online subscription and carried on with the rest of the process

Why is this a better process?

Well it's way more consistent - the online and offline experiences are coordinated and the decisions that need to be taken to sign customers up whether they mail in orders, use the web or talk to a CSR are all automated correctly. CSRs are empowered to focus on the customer because the system knows what decisions are allowed for each and tells the CSRs so that they can execute them quickly and easily and without the risk that they will approve something they should not. The online environment would have run rules at each step to see if additional data was required so that it did not repeat questions or get confused. Some kind of smart form would have been displayed that responded intelligently at each in the process.

Technorati Tags: , , , , ,

Marketing to (and with) algorithms with EDM

Saturday, December 16th, 2006

Ian, my fellow blogger here at edmblog.com, pointed me to this article You Must Market To Algorithms, Not Just People. The article nicely summarized the growing role of algorithms in marketing and, as predictive analytics and even rules can be considered a form of algorithm, it made me want to talk about enterprise decision management or EDM in this context. Let's start with the key concept:

As more human behaviors emit trails of digital residue, the more opportunities reside for algorithms to harness those human-induced data and become information intermediaries

Absolutely right. And these data are available in such volume that reporting on them is not going to help anyone - you have to build insight from the data so that you can use it, not just report on it with BI. This means building predictive analytic models based on the data that can be embedded into your operations - algorithms in other words. In reality you must also combine rules - about the user's preferences so as to maximize the customer's influence on decisions and about policy and regulation to ensure compliance. This is particularly true for any business subject to the Long Tail. Automating decisions in this way can let you improve the customer experience and scale 1:1, personalized communication to thousands or millions of customers.

As Max says, "all behaviors .. create halos of metadata, which algorithms process, mediate and disperse to others" and you need to account for all this information in your decisioning. Max gave some examples of algorithms and I thought it would be fun to show how EDM-like some of them were:

  • Restaurant recommendation
    Well you could use predictive algorithms to segment people by the kind of restaurants they like/use and to build recommendations by comparing to other people. The customer can set rules for price, location etc as well and the combination comes up with restaurants.
  • Real-estate
    Looks like this one was just rules - rules from the customer about properties in which they are interested
  • Travel
    More preference rules plus models predicting occupancy and handling dynamic pricing as a result
  • Music playlists
    Rules and predictions for like and dislike
  • Fraud
    Rules and analytics, a classic EDM one.

Technorati Tags: , , , , , , , , , , , , ,

Book Review: The World Is Flat

Friday, December 15th, 2006

I have just finished reading "The World Is Flat" by Thomas Friedman. Firstly a health warning - it's a REALLY long book. Even skimming some sections it took me a long while to read it. Overall it is a good if somewhat long winded read. As someone working in technology I found it a little patronizing in places but that could just be a function of its target audience not working day to day with some of the technologies he's discussing. The book lays out a series of trends and technologies that have, in his phrase, flattened the world by making it more interconnected than ever before. He goes on to discuss how this fits with globalization, how companies are reinventing themselves in the face of these changes, some of the problems and risks and what kinds of political and public policy impacts it might all have.

I was reading this in the context of Enterprise Decision Management, EDM, and several concepts introduced in the book resonated with me.

The first is the idea that deciding where to source work is becoming more complex. There are more options with advantages and disadvantages than ever thanks to the overall increase in interconnectedness. For instance, Thomas discussed how JetBlue reservations use "homesourcing" and are 30% more productive in terms of bookings made and how other companies are outsourcing call centers, for example:

"There are currently about 245,000 Indians answering phones from all over the world or dialing out to solicit people for credit cards or cell phone bargains or overdue bills"

Thomas points out that

"Homesourcing to Salt Lake City and outsourcing to Bangalore were just flip sides of the same coin - sourcing."

or as Thomas Koulopoulos called it when I heard him speak recently, Smartsourcing. Thomas K. also gave a presentation called The road to Agra that touched on these same topics. Thomas F. explains that the work that will go where it can be done most effectively and that increasingly only "creative, complex strategies" will be done in developed world if it is possible to say "I am getting the grunt work done efficiently far away. " Now this last phrase made me think about EDM in this context. Why would I have the "grunt work" done far away if I could automate it and control it locally? Much of what EDM delivers is the automation of grunt work, decisions in workaday transactions that do not really require intelligence to make - just the application of rules and analytic insight. So when considering sourcing the various pieces of your process you should consider if you need a person at all - perhaps you can use an EDM approach and automate a step rather than outsourcing it. Even if you decide that a piece of the process should be outsourced or homesourced or moonsourced or what ever then you still have to think about how you can control this sourced process. Will you just rely on policy manuals and training? Will you assume that the folks making decisions on your behalf can interpret data correctly from their reports and apply your business strategy to what that data tells them? Perhaps you should automate those decisions so that you can control the logic in them even though they are sourced and so your unique data can be used to go beyond BI and actually inform how they work. In the case of the homesourced booking agents, wouldn't you want to make sure they offered your best travelers upgrades when they could and knew how to prioritize customers that needed re-routing as well as what upsell to make to whom? What about the 245,000 phone operators? Would it help if they had an automated system for approving credit or for telling what kid of collections strategy would work? Of course it would. And think about the legal issues here - who's on the hook for the legality of the behavior of these folks? Not the Indian outsourcer but you. Can you show that the decisions they took were legal, compliant, unbiased etc? Not if the decision is manual. Let's make this concrete using one of Mr. Friedman's own examples. Here's what he says:

"In the coming phase of work flow, here is how you will make a dentist appointment: First, there will be a common standard for making dental appointments with any dentist. You will instruct your computer by voice to make an appointment. Your computer will automatically translate your voice into a digital instruction. It will automatically check your calendar against the available dates on your dentist's calendar and offer you three choices. you will click on the preferred date and hour. The week before your appointment, your dentist's calendar will automatically send you an e-mail reminding you of the appointment. The night before, you will get a computer-generated voice message by phone, also reminding you of your appointment".

Now leaving aside Thomas' belief in the growth of standards to cover everything, let's think about this scenario with EDM:

  • You will instruct your computer by voice to make an appointment.
  • Your computer will automatically translate your voice into a digital instruction.
  • It will automatically check your calendar against the available dates on your dentist's calendar and offer you three choices. you will click on the preferred date and hour.
    • In an EDM enabled process it would use your rules and predictions of when you are likely to want an appointment to make the three selections
    • In theory the dentist might have rules constraining appointments (new patients, cleaning only etc) and these would be included in the decision-making
    • A prediction for the length of time you would be at the dentist, given the kind of appointment and previous experience with you and patients like you, and the likelihood of a follow-up might constrain these choices further and even, perhaps, suggest pre-booking of the follow-up appointment
    • Information about your choice would be used to improve the model of your preferred slot
  • The week before your appointment, your dentist's calendar will automatically send you an e-mail reminding you of the appointment.
    • You would have set rules both for when you wanted to be reminded and how so that this decision was personalized
    • A model predicting the likelihood of you being late or missing the appointment might cause additional activities such as a live call if you are a high risk for missing it
  • The night before, you will get a computer-generated voice message by phone, also reminding you of your appointment.
    • Similarly this would be customized to suit you
    • The system that called you would give you various options (confirm attendance, say you might be late, cancel) and these options might reflect your particular coverage (yours might say "Cancel and pay a cancellation fee" for instance)
    • If you cancel your session an automated conversation would be started to capture a new booking time and a decision would be taken as to who to call and offer the short-notice visit to (given the length of appointment etc).
    • Staffing and scheduling of people and equipment for the actual visit might be dynamically altered based on the results of all this

Lots of decisioning making the process more personalized, more efficient and more agile.

Another area of interest highlighted in the book was that of global, dynamic supply chains. In particular the Walmart supply chain and its immediate responsiveness was discussed alot. The move to real-time or just-in-time manufacturing and delivery was highlighted in the phrase

"[coordinate] disruption-prone supply with hard-to-predict demand"

Thomas describes a number of scenarios where companies are making rules-based decisions to keep these automated supply chains moving. However, he also talks about sharing data as a critical aspect of these supply chains. I don't have a problem with that, per se, but it seems to me what companies need in these circumstances is not data but insight from that data, Is it more useful for me to tell you I just sold one of your items or to tell you that I am predicting to run out of them next Thursday? As we add RFID and generate yet more data I believe the value of insight will exceed the value of raw data by an ever increasing margin and that automation of decisions that take advantage of that insight will be key. As Thomas quotes in the book:

"In this world a smart and fast global supply chain is becoming one of the most important ways for a company to distinguish itself"

Note the use of "smart" here. I might say "smart enough" - there's no need to try and embed artificial intelligence or anything in them to make progress.

The need for business agility came up again and again. For instance supply chain problems were highlighted as being

"exacerbated by the short life cycle of product today... Innovation is happening much faster, and so products go in and out of fashion much faster"

and the example of Spanish retailer who works on the basis that it is more profitable to have shortages and then respond REALLY fast to them. This company is taking customer preferences and feeding them into a rapid turnaround system to meet new demand. Clearly customer preferences can be expressed as rules and used to do this but, again, I could not help feeling that predictive analytics might both improve the decision and act as an early warning that a decision is needed.

There were also a couple of nice examples of what I would consider EDM applications. There was a story about UPS developing a system that allows US Customs to specify rules for inspection. This shows what I mean by outsourcers having to allow customer some control over the rules in their system. But what about prediction? As data on contraband and other issues is gathered it should be possible to have the system predict the risk of certain packages being problematic and routing them for inspection even though they don't fail any of the specific rules. The combination of explicit rules and data-driven analytics has proven enormously successful in fraud detection, it would work here too. Similarly in the story about embedding intelligence into Rolls Royce engines to allow for remote diagnostics to see, for example, what to do about a lightning strike, there are clearly rules but there could also usefully be analytics.

A few final thoughts:

  • "But first you need your own customers - your own distinctive competency for your company"
    and if you are going to run a distributed and largely automated company, you had better be able to embed that distinctive competency into your systems
  • "digital, mobile, virtual and personal"
    Carly Fiorina's comment on the future still stands and EDM matters because personalization across mobile channels requires the kind of deep personalization only an EDM approach can deliver
  • there is social pressure on the global supply chain
    Not all compliance issues are about external regulations, some of them are about ethical compliance and self-regulation. Are your automated systems behaving ethically?

 

 

You can buy the book here.

Technorati Tags: , , , , , , , , , , , , , , , , ,

Using EDM to deliver competitive productivity

Thursday, December 14th, 2006

A friend (Hi Ken) referred me to this post about search by David Berlind. Now while I think unstructured text in decision automation and Enterprise Decision Management or EDM is going to be more and more important and while I realize I have not blogged much about unstructured text analysis (note to self, write post on this), I actually wanted to drill down in David's phrase "competitive productivity". Here's how he introduced it:

To businesses with a lot of information workers, any technological advancements that can whittle that 25 percent [time spent searching for information] down to 20, 15, 10 or even 5 percent means that respectively, those workers can be spending 5, 10, 15 or event 20 percent more of their time on tasks that contribute more directly (more directly than searching) to competitive advantage. In fact, freeing up time to focus on those activities that contribute to competitive advantage — long-hand for what I'm going to start calling "competitive productivity" (versus plain ole' "productivity")

This is a great concept and highly relevant to anyone thinking about EDM. EDM is about automating and improving decisions, particularly those that require some expert judgment or for which some data exists that could be used to make or improve the decision. Clearly these decisions are often those taken by information workers - underwriters in insurance, loan officers, ad pricing managers, materials master designers, supply chain managers, staffing schedulers, diagnostic engineers, eligibility managers and so on. If I can automate these decisions, at least the most common 85-90-95%, then I likewise free up their time to work on more complex, high-value tasks.

Now some of this is going to overlap - some of the 25% of time spent searching for information is going to be included in the time saved by not having to make the decision manually because it is information being sought to make a decision. I suspect, however, that most of the benefit is additive. The time spent searching for information is probably in support of the most complex decisions and those therefore most likely to be in the small percentage still referred for manual review. The process of automation will free up some of this time though because you will get a lot more context for the referred decision and this will make it easier to search for information. For instance, a referred policy that needs manual underwriting will say why it is being referred and that will focus the need to search for information down to just the information that will resolve that issue.

Each of the case studies above shows how different decisions can be automated and how they free up information worker time for "competitive productivity".

Technorati Tags: , , , , , , , , ,


American Flags  |  Mortgage Calculator  |  Internet Advertising  |  Actress  |  Personal Loan