Standalone Knowledge Management Is Dead With Oracle's Announcement To Acquire InQuira

Kate Leggett

Its exciting news to see Oracle announce its intention to acquire InQuira. We have been waiting for this news for a long time. The reasons are multifold:

  • Today’s contact center ecosystem is complex, and comprised of multiple vendors who provide the critical software components. Read my blog post on what these critical software components are. Customers are looking for a simpler technology ecosystem to manage from both a systems perspective and a contractual perspective.
  • Suite solutions, available from unified communications (UC), CRM, and workforce optimization (WFO) vendors, are evolving and include comprehensive feature sets. These vendors have either built these capabilities out or acquired them via M&A activity. And we expect more M&A to happen.
Read more

Agile Business Intelligence Solution Centers Are More Than Just Competency Centers

Boris Evelson

By Boris Evelson and Rob Karel

Our latest BI solution center (BISC, which in our definition is more than a BICC/BI COE) report is now live on the Forrester website. Here’s a brief summary.

Forrester firmly believes that tried and true best practices for enterprise software development and support just don’t work for business intelligence (BI). Earlier-generation BI support centers — organized along the same lines as support centers for all other enterprise software — fall short when it comes to taking BI’s peculiarities into account. These unique BI requirements include less reliance on the traditional software development life cycle (SDLC) and project planning and more emphasis on reacting to the constant change of business requirements. Forrester recommends structuring your BISC along somewhat different lines than traditional technical support organizations.

Earlier-generation BI support organizations are less than effective because they often

  • Put IT in charge
  • Remain IT-centric
  • Continue to be mostly project-based
  • Focus too much on functional reporting capabilities but ignore the data
Read more

Verint + Vovici: Another Example Of Market Consolidation In The Contact Center Space

Kate Leggett

Contact centers for customer service are a nightmare in terms of the complexity of the technologies. At a high level, to serve your customers, you need to:

  1. Capture the inquiry, which can come in over the phone, electronically via email, chat, or SMS, and over social channels, like Twitter, Facebook, or an interaction escalated from a discussion forum.
  2. Route the inquiry to the right customer agent pool to address it.
  3. Create a case for the inquiry that contains its details and associate it with the customer record.
  4. Find the answer to the inquiry; this can involve digging through different information sources like knowledge bases, billing systems, and ordering databases.
  5. Communicate the answer to the inquiry to the customer.
  6. Append case notes to the case summarizing its resolution, and close the case.

You want to make sure that your agents deliver answers in a consistent way and to make it easy for your customers to find answers themselves. To do this, you need to invest in:

  • A knowledge base for your agents. You also need to then expose a subset of the content to your customers via a web self-service portal.
  • A discussion forum where your customers can share information and escalate issues to a customer service agent.
  • Some type of process guidance to lead agents through complicated scripts so that they deliver service in a reproducible way.

You also need to understand what expectations your customer base has regarding your service offering by:

  • Surveying your customers
  • Listening to their sentiments on social media sites
Read more

A Consistent Customer Experience Requires Consistency In Managing Voice, Electronic, And Social Interactions

Kate Leggett

Customers expect the same experience every time they interact with a company — whether it be when researching a product, completing a sales transaction, or getting customer service — over all the communication channels that a company offers. They also expect companies to have an understanding of their past purchase history and prior interactions. Finally, customers further expect that each interaction with a company adds value to their prior interactions so that, for example, they do not have to repeat themselves to a customer service agent when being transferred or when migrating from one communication channel to another during a multistep interaction.

How many companies can deliver a consistent service experience in this scenario?

Three fundamental elements are needed to deliver a consistent customer experience across all communication channels:

  • A unified communications model. Companies need to queue, route, and work on every interaction over all communication channels in the same manner, following the company business processes that uphold its brand.
  • A unified view of the customer. Each agent needs to have a full view of all interactions that a customer has had over all supported communication channels so that the agent can build on the information and experience that has already been communicated to the customer.
  • Unified knowledge and data. Agents need to have access to the same knowledge and the same data across all communication channels so that they can communicate the same story to their customers.
Read more

Stop Wasting Money On WebLogic, WebSphere, And JBoss Application Servers

Mike Gualtieri

Use Apache Tomcat. It is free.

I don’t understand why firms spend millions of dollars on Java application servers like Oracle Weblogic or IBM WebSphere Application Server. I get why firms spend money on Red Hat JBoss -- they want to spend less on application servers. But, why spend anything at all? Apache Tomcat will satisfy the deployment requirements of most Java web applications.

Your Java Web Applications Need A Safe, Fast Place To Run

Most Java applications don’t need a fancy container that has umpteen features. Do you want to pay for a car that has windshield wipers on the headlights? (I wish I could afford it.) Most Java applications do not need these luxuriant features or can be designed not to need them. Many firms do, in fact, deploy enterprise-class Java web applications on Apache Tomcat. It works. It is cheap. It can save tons of dough.

Expensive Java Application Servers Sometimes Add Value

There is a need for luxury. But, you probably don’t need it to provide reliable, performant, and scalable Java web applications. Application server vendors will argue that:

  • You need an application container that supports EJBs. EJB3 fixed the original EJB debacle, but why bother? Use Spring, and you don’t need an EJB-compliant container. Many applications don’t even need Spring. EJBs are not needed to create scalable or reliable applications.
Read more

Future Of Business Rules Platforms: Events And Decision Management

John R. Rymer

Business rules platforms are a mature technology for automating decision and policy logic and for managing fast changes to that logic to keep up with business changes. Now customers are seeking more: capabilities allowing them to employ business rules to help detect and respond to business events hiding in streams of data and to automate decision life cycles. This research reveals how well vendors are responding to these new requirements.

Application development and delivery (AD&D) pros are taking business rules platforms in two new directions. The technology's future will be determined in large part by whether or not customers can successfully apply it to business event processing and decision life-cycle management.

Business event processing applications answer the question "What activities are happening in the business now that I need to know about?" by searching for patterns and values within several streams of actively flowing data. The streams almost always represent information about the real world, such as customer activity in a casino, stock prices fluctuating in real time, or the location of transportation vehicles and the goods they carry. AD&D professionals often build business-events applications using complex event processing (CEP) platforms — some of which use rules to define event patterns. Other AD&D professionals use business rules platforms to build business-events applications. These overlapping uses set the stage for the convergence of CEP and business rules platforms.

Read more

Business Rules Platforms 2011: 3 Vendors Have Strongest Positions

John R. Rymer

After two years of vendor consolidation, which are the best business rules platforms for application development and delivery professionals to consider? In our judgment, based on growth rates, market presence, strength of product, and client interest, three vendors have risen to the leadership positions in this market, with two others coming on strong. IBM's ILOG has the strongest market position, but a surprising new alternative has gained strong initiative, and a one-time leader has lost momentum.

Although many application development and delivery (AD&D) professionals have experience implementing business rules platforms, Forrester's AD&D team has been receiving a continual flow of inquiries on this topic that suggests that clients want to know how the vendor landscape is changing and how those changes affect product choices. In fact, before evaluating a vendor's product features, clients consider the vendor's market momentum and the size of its customer base.

Our conclusion: The choices in business rules products have in fact changed, because the vendors have consolidated, expanded, and/or retrenched. Here is a picture of those changes:

As a result, the number of leading products has declined since we last evaluated business rules platforms. Some business rules vendors have expanded into other product categories. As a result, the decision to choose these vendors for a business rules product is more complex because business rules management is no longer their primary focus or their product sets include additional capabilities not directly related to business rules management. Within this category, there are:

Read more

Do We Need A Hydrocarbon Smart Grid?

Holger Kisker

The Oil And Gas Information Technology Innovation Dilemma

The hydrocarbon logistics chain of natural gas and crude oil connects globally distributed exploration and production sites with industrial and private consumers via pipelines, tankers, rail cars, and trucks with massive intermediate buffering storage and conversion facilities (tank farms, refineries, gas plants); it is the lifeblood of our energy supply chain today and for the coming decades.

 

More than 75 million barrels of oil and 300 billion cubic feet of natural gas are produced, transported, and consumed all over the globe — every day. Along the complex transportation chain, these special bulk products, both liquids and gases, are transferred between the different modes of transportation, resulting in a number of challenges based on complex measurements of product volumes and masses:

  • Measurement accuracy. In an ideal world, we would always determine the mass of crude oil and natural gas at each measurement point; however, due to the large quantities involved, weighing is possible only at the very end of the logistics chain. Consequently, we have to live with measurement data that typically carries an uncertainty of 0.1% to 0.5 %, depending on the measurement devices’ intrinsic accuracy.
Read more

RFQ For BI Software Pricing Research

Boris Evelson

On my Q3 research agenda is a document reviewing typical BI software pricing configurations. Unfortunately, I find that just asking vendors whether they have this or that pricing policy (by number of named users, number of concurrent users, server type, etc.) usually just gets me “Yes, we have it all” or “It depends” answers. Not really useful. So this time I plan to nail down the vendors to three specific quotes given three very specific configurations. Here’s my first cut at the RFQ. I plan to send it out to:

Read more

DevOps Is About Collaboration; NoOps Is About Automation

Mike Gualtieri

NoOps Is The Peak Of DevOps.

DevOps is a noble and necessary movement for immature organizations. Mature organizations have DevOps down pat. They aspire to automate to speed release increments. 

NoOps will not replace DevOps; rather, it is an evolution of the release management aspects of DevOps. NoOps is the goal of DevOps.

DevOps Versus NoOps

Are you ready to shoot for NoOps?

Categories: