<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Ontology-Based Linking of Social, Open, and Enterprise Data for Business Intelligence</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tope Omitola</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>John Davies</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alistair Duke</string-name>
          <email>alistair.dukeg@bt.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hugh Glaser</string-name>
          <email>hugh.glaser@seme4.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nigel Shadbolt</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>British Telecommunicatons</institution>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Electronics and Computer Science University of Southampton</institution>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Seme4 Ltd.</institution>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>We are at the cusp of two major revolutions impacting the world of work
and commerce. These are the rise of social media and the rise of Big Data. Data
is everywhere. Each phone call, email, chat request, or person-to-person
interaction between a customer and a brand provides organisations with invaluable
information. This wealth of data can yield valuable information, such as
revealing precious insight into customers' needs and desires, allowing companies to
personalise their services accordingly. A business revolves around its customers
and their social connections. These social connections are valuable data that can
useful for enterprises.</p>
      <p>For a company to thrive in this new world, these data need to be used to
identify opportunities in new sectors, support employees, customers, and other
external partners. These data can also be used to create a more intelligent
understanding of customers, and to help predict future customer behaviour. This
paper (and talk) will describe how we apply Linked Data to enable BT, in
particular BT Business (BTB), a division of BT, to take advantage of this Data
revolution. We use Linked Data technology to integrate internal and external
datasets, including structured, unstructured, and social data. We describe (and
shall expand on these in the talk) how this integration allows new and insightful
information to be derived.</p>
      <p>BTB, the UK's leading provider of business communications services with
over one million small and medium sized enterprise customers, would especially
like to use Linked Data to solve these business challenges (amongst others):
{ To manage and extract value from its disparate, isolated data,
{ To take advantage of information from external, non-enterprise, and other
social data in order to provide new, exciting, and useful services that create
value for customers,</p>
      <p>Tope Omitola, John Davies, Alistair Duke, Hugh Glaser, and Nigel Shadbolt
{ To identify trends and issues that are speci c to circumstances such as
competitor activity, products o ered, industrial sector of the customer, and
proles of members of sales teams.
2</p>
    </sec>
    <sec id="sec-2">
      <title>System Operation</title>
      <p>Ontology-based data access and management (OBDM) is a methodology that
is used to access, integrate, and manage data in big enterprises. It consists of
a three-level architecture constituting an ontology, the data sources, and the
mapping between the two. We have applied the ideas of OBDM for our data
integration process. Our systems consists of a Uni ed Ontology, and using this
ontology to guide us to transform the datasets of four systems, into Linked Data.
a. The Uni ed Ontology: This consists of entities such as the concepts of a BT
employee (BTEmployee), of a BT employee (EmployeeSocialMediaUser) that is
also a member of a social network, of sales team members (SalesForceUser), of
client companies (Account), and industrial sectors (SICCode). (We will expand
on this in the talk).
b. Four di erent systems are involved in the process: (1) Public information
of clients of BTB as derived from OpenCorporates; (2) Members' social
connections as derived from LinedIn; (3) an LDAP-backed General Employee Data
store; and the BTB Win-Loss system (which stores a collection of CSV les of
companies that clients of BTB). We transform most of the data in these systems
into RDF, linking them together using appropriate class and data instances'
URIs.</p>
      <p>Data Consumption The linked data platform that is constructed allows
us to make very exible Sparql queries, which we shall describe further in our
talk at the Workshop.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Conclusions</title>
      <p>This paper described how we linked social, open, and enterprise data for Business
Intelligence, and how this has been applied in a telecommunications company.
Some of the challenges we found include (a) the establishment of a strong
business case and the availability of a 'data champion' to help bring the
stakeholders together; (b) Data Discovery and Provenance. Discovering the appropriate
datasets with the right provenance criteria can be time-consuming but very
important; (c) Data Cleaning and Interlinking. Many of the discovered datasets
may not be in the appropriate format to be useful, so they need to be \cleaned".
The choice of URIs to use for interlinking datasets is application-speci c. This
choice should be guided by the business case; and (e) Data Modelling. A goal of
integration is to have a uni ed view of the data from the disparate sources.
Having a uni ed ontology helps towards this. Future data integration tasks need to
think of these challenges and provide the appropriate solutions. We shall provide
more details of these challenges in the talk.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>