Telcordia is now part of Ericsson
Read more >

Network Operations

Data Reconciliation & Analysis

Service delivery -- accomplished as quickly and accurately as possible -- is the "bottom line" for every service provider. Data "consistency" among provisioning OSSs is essential to that goal.

That is, customer, network, and service information may be represented differently from one system to another, but successful processing requires agreement on data ownership and accurate values. Disagreements in the way names are spelled or in the length of copper wire can lead to fallout, stranded inventory, runaway costs, and unhappy customers.

Telcordia is using expert analysis and innovative tools to uncover data inconsistencies within and between the most complex operational environments -- and saving clients millions of dollars in the process.

Innovation in Action

  • To support our data federation analyses, Telcordia created a groundbreaking data processing software tool. This proprietary tool allows us to rapidly construct customized data federation flows for each client's environment. Common data processing constructs and intelligent reconciliation capabilities can easily be combined to solve any data transformation problem.

    This tool has dramatically accelerated our ability to analyze large batches of data and catch both inaccuracies and system-to-system mismatches.

    Using the tool, our experts have successfully:

    • Analyzed inter-carrier billing records and network routes, and recommended changes to reduce cross-carrier costs
    • Reconciled and cleansed DSL inventory data for large-scale data migration and system consolidation
    • Correlated error conditions during ordering of triple-play services for semi-automated exception handling.

Innovation on the Horizon

  • We are now working to turn data reconciliation into an automated capability that can correct exceptions as they occur and provide a unified and consistent view of data in disparate operations systems.
  • We are also developing a way to analyze service order fallout for a new service, and install the "fix" directly into the ordering process, so systems can handle exceptions as they occur.