Colt Telecom Improves Customer Experience With The Webmethods Esb


Colt Telecom Improves Customer Experience With The Webmethods Esb

COLT, one of the leading European providers of business communications, had deployed the same systems in several countries and all of them were operating independently. As a result, there were over 10 instances of each application — and each one containing its own silo of information. Customer information was recorded in several systems and there was no consolidated view of a customer across the whole company.

To resolve this problem, Colt linked systems together using the webMethods Enterprise Service Bus Platform. This provided reliable messaging between the applications at the three main centers in London, Paris and Frankfurt. It reduced the growing number of ad hoc links, data inconsistencies and errors, and sped up processes such as customer provisioning. Prior to this, a service order in three countries would go through three separate systems.

The second step was to centralize all information into one data center in London, with only one instance of each application.

Single view of the customer

COLT is now benefiting from a single view of the customer. This means COLT can respond more quickly and easily to customer issues, and can also analyze its customer base more easily. The company is also leveraging the powerful B2B capabilities of the webMethods ESB Platform to dramatically improve the provisioning of products with local telecom operators.

“Our first B2B project delivered an ROI in less than six months,” said Andy Roberts, Integration Services Manager at COLT. “Since then, we have implemented numerous additional B2B and internal interfaces, all of which are allowing us to stop points of failure where data was originally being manually transferred from one system to another. By automating the process, we have been able to completely eliminate errors that existed previously.”

SOA-enabling the future

COLT is progressively deploying a Service-Oriented Architecture (SOA), which has become a key enabler moving forward. “A key benefit of SOA is the ability to use and re-use the services provided by our systems without worrying about the business or functional logic that these systems contain,” Roberts said.

“We are particularly interested in a plug-and-play scenario, where we can seamlessly replace any system, such as a fault management application, with others providing similar services.”

The new SOA enables COLT to be more responsive to market changes, bring products to market faster and deliver more detailed information than before to its customers.

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

, , , ,

  1. #1 by lkeel75 on May 11th, 2010

    Your code is accessing a page it doesn't have rights to. Check the form authentication code you added.

  2. #2 by D D on May 11th, 2010

    My web service just has a generic method called "ExecuteStoredProcedure" that takes a string containing the name of the stored procedure to execute, and a DataSet with the parameters the stored procedure needs.

    In the web method itself, I just create a standard SqlCommand object, loop through my DataSet to assign Sql Parameters to it, and then execute it. There's no sense in writing a web method for EACH stored proedure, as this would be rather difficult to maintain.

  3. #3 by rainy gal on May 12th, 2010

    If (res == 0) test fails, you don't specify a return value. Need to do something like:

    if (res == 0)
    return r;
    else
    return …. some value …

  4. #4 by Protonova on May 12th, 2010

    I believe that File.Create returns a FileStream object, that must be closed after you are done with the file. Because you are not closing the file, the file remains open and locked.

  5. #5 by coreyog on May 12th, 2010

    Search on internet.I'm sure you find it

  6. #6 by akshay on May 13th, 2010

    Just add a reference to it, then (if local):

    Dim oWS As New localhost.WebServiceName()
    Messagebox.Show(oWS.connection)

(will not be published)
icon_wink.gif icon_neutral.gif icon_mad.gif icon_twisted.gif icon_smile.gif icon_eek.gif icon_sad.gif icon_rolleyes.gif icon_razz.gif icon_redface.gif icon_surprised.gif icon_mrgreen.gif icon_lol.gif icon_idea.gif icon_biggrin.gif icon_evil.gif icon_cry.gif icon_cool.gif icon_arrow.gif icon_confused.gif icon_question.gif icon_exclaim.gif 

  1. No trackbacks yet.