<!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>Leverage of OWL-DL axioms in a Contact Centre for Technical Product Support</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Dept. of Computer Science &amp; Applied Statistics, University of New Brunswick</institution>
          ,
          <country country="CA">Canada</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dept. of Computer Science &amp; Software Engineering, Concordia University</institution>
          ,
          <addr-line>Montreal</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Innovatia, Inc.</institution>
          ,
          <addr-line>Saint John</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Real-time access to complex knowledge is a business driver in the contact centre environment. In this paper we outline for the domain of telecom technical product support a knowledge sharing paradigm in which a desktop client annotates named entities in technical documents with canonical names, class names or relevant class axioms, derived from an ontology by means of a web services framework. We described the system and its core components; OWL-DL telecom hardware ontology, ontological-natural language processing pipeline, an ontology axiom‐extractor; and the semantic assistant framework.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic Assistant</kwd>
        <kwd>Telecommunications Hardware Ontology</kwd>
        <kwd>Natural Language Processing</kwd>
        <kwd>OWL Axiom Extraction</kwd>
        <kwd>Web Services</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        To respond to customer information requests in a timely manner, contact center
workers need to search through many types of knowledge resources including user
manuals, training, marketing, engineering, and case resolution databases. Companies
face increasing contact center costs as their products and information support services
evolve. Key drivers in this business process are the reduction in number of cases
escalated to more experienced workers and reducing time spent in resolving cases.
Training time must also be greatly reduced and workers with less knowledge should
be able to fill in for others on an ad hoc basis. A knowledge-based approach is
appropriate in this context. Moreover expressive features of the OWL language [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
that permit the richer specification of relationships between Telecom hardware, their
features, symptoms of hardware failure, and the suggested resolution of the technical
problem are required. We report a custom solution for a telecommunications original
equipment manufacturer (OEM) technical contact center involving development of
      </p>
    </sec>
    <sec id="sec-2">
      <title>Telecom Support System Architecture</title>
      <p>
        product‐specific OWL‐DL Ontologies that are consumed by a middleware
leverageing web services to push information to client side knowledge workers.
The system architecture for our knowledge sharing paradigm includes the following
core components: (i) Ontology; (ii) Ontological NLP pipeline; (iii) Ontology
Axiom‐extractor; (vi) Semantic Assistant Framework [2]. These components are
integrated into an online annotation workflow shown in Figure 1.
The scope of the ontology included hardware components that comprise the chassis of
a telecommunications switch and more specifically the compatibilities of different
hardware components therein [
        <xref ref-type="bibr" rid="ref2">3</xref>
        ]. Equivalent class axioms were used to conceptualize
which version of each chassis component was compatible with versions of the chassis
models. A total of 54 classes of hardware and 149 object and 68 data properties
specific to the hardware domain were represented and a further 20 axiom constraints
were applied across 13 hardware classes, namely; (i) three intersection or
consolidation axioms involving 17 classes were used to describe various component
Leverage of OWL-DL axioms in a Contact Centre for Technical Product Support
assemblies (chassis, cable management bracket kit, and dual back plane); (ii) two
disjunctions (consolidation axioms) involving 33 classes were used to ensure no
illogical inferences; (iii) 22 restrictions on data properties were defined describing the
maximum and minimum number of power supplies or line cards (modules) that can
physically be part of a chassis; (iv) two derivative axioms were established involving
four power supply classes to automatically populate legacy and replacement power
supply equipment from the main AC and DC power supply class categories. A total of
16 necessary conditions and 16 sufficient conditions were defined, and four cases of
joint necessary and sufficient conditions. A further 15 classes were introduced in a top
level literature specification for describing specific features of technical
documentation so that a corpus of 3,000 pages of user manuals could be text mined
using, and instantiated into, the ontology for checking the relevance manually curated
axioms. The ontology has a DL expressivity of SROIQ(D).
3.2
      </p>
      <sec id="sec-2-1">
        <title>Ontological NLP and Axiom Extractor</title>
        <p>
          The Ontological NLP pipeline is a text mining solution based on open source GATE
framework [4]. GATE included two main steps, firstly a GATE annotation pipeline
for recognizing named entities in source text and connecting them with canonical
names and semantic classes, and secondly JAPE rules [
          <xref ref-type="bibr" rid="ref3">5</xref>
          ] for the reformatting of
ANNIE1 annotations and calling the Ontology Axiom‐extractor (JAVA / OWL-API)
that enriches text annotations with relevant class axioms. The GATE pipeline was
wrapped in Java and integrated with Axiom‐extractor to facilitate batch processing.
3.3
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Semantic Assistant</title>
        <p>The Semantic Assistant Framework is a service‐oriented architecture used to enhance
existing end‐user clients, such Open Office Writer, with online Telecom related text
analysis capabilities provided as a set of web services. The Ontological NLP pipeline
links Telecom named entities occurring in a document opened on client side with
existing ontologies on server side (See Figure 1). The system annotates each named
entity with canonical name, class name and related class axioms providing annotation
for documents on the client side. Figure 2 demonstrates an example of client-side
annotated text2.1The proposed system is scalable and extensible allowing users to
easily customize the information to be delivered as annotations depending on the
availability of ontologies with defined axioms linked to canonical names for entities.
1 ANNIE Information Extraction system developed for GATE. http://gate.ac.uk/ie/annie.html
2 We used Open Source Writer integrated with the Semantic Assistant plug-in as a client-side
application. Our annotating web services is compatible with any other existing or proposed
client-side software that has web services client functionality.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Discussion</title>
      <p>When replacing unserviceable telecom hardware customers phoning a contact centre
for technical product support often have questions about which components are
compatible with their chassis. Older chassis models of a telecom switch may be
compatible with specific models of power supplies and incompatible with later
versions. By combining the Semantic Assistant with existing text mining and axiom
extraction pipelines we leverage the DL-axioms in our OWL ontology to great effect,
rapidly communicating hardware incompatibilities to contact centre agents through
their desktop applications. Installing incorrect power supplies can result in equipment
failure, injury to the installer, network downtime for tens of thousands of customers.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>OWL</given-names>
            <surname>Web Ontology Language Guide</surname>
          </string-name>
          http://www.w3.org/TR/owl-guide/ [2]
          <string-name>
            <surname>Witte</surname>
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gitzinger</surname>
            <given-names>T.</given-names>
          </string-name>
          , (
          <year>2008</year>
          ),
          <string-name>
            <surname>Witte</surname>
            <given-names>R</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gitzinger</surname>
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Semantic Assistants -</surname>
          </string-name>
          User-Centric
          <source>Natural Language Processing Services for Desktop Clients. 3rd Asian Semantic Web Conference, February 2-5</source>
          ,
          <year>2009</year>
          , Bangkok, Thailand Springer LNCS 5367, pp.
          <fpage>360</fpage>
          -
          <lpage>374</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Telephone</given-names>
            <surname>Exchange</surname>
          </string-name>
          http://en.wikipedia.org/wiki/Telephone_exchange [4]
          <string-name>
            <given-names>H.</given-names>
            <surname>Cunningham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Maynard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Bontcheva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Tablan</surname>
          </string-name>
          .
          <article-title>GATE: A Framework and Graphical Development Environment for Robust NLP Tools and Applications</article-title>
          .
          <source>Proc. 40th Ann. Meeting - Association for Computational Linguistics (ACL'02)</source>
          . Philadelphia,
          <year>July 2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>H.</given-names>
            <surname>Cunningham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Maynard</surname>
          </string-name>
          et al.
          <source>JAPE: Java Annotation Patterns Engine (2nd Edition)</source>
          .
          <source>Technical report CS-00-10</source>
          , University of Sheffield, Department of Computer Science, 2000
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>