<!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>Using Lightweight Semantic Models to Assist Risk Management in a Large Enterprise</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shirin Sohrabi</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anton Riabov</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Octavian Udrea</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fang Yuan</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IBM T.J. Watson Research Center</string-name>
        </contrib>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>In this paper we summarize our experience and the initial results from
implementing and operating IBM Scenario Planning Advisor (SPA), a decision
support system that uses lightweight semantic models to assist nance organizations
in identifying and managing emerging risk, a category of risk associated with the
changes in the global or local economies, politics, technology, society, and others.</p>
      <p>
        SPA is designed to support the business process called \scenario planning"
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] that consists of preparing several future scenarios, followed by identifying
the implications for the business, and nally choosing the mitigation actions to
be taken. For example, prior to the Brexit referendum in 2016, an international
company operating in the UK could consider alternative future scenarios for
changes in trade and employment treaties assuming the majority voted to leave
the EU, identifying the implications for the company's nances and its ability to
hire, enabling the company to act immediately to minimize the negative impacts.
      </p>
      <p>The main functions of SPA are: 1) discovering active risk drivers by
aggregating relevant news from the Web and social media, and generating lists of
candidate observations corresponding to the detected risk drivers; 2)
generating multiple alternative future scenarios highlighting their business implications
and leading indicators, based on user-selected observations, and using domain
knowledge about driver relations, cascading e ects, and implications.</p>
      <p>A key design decision in SPA is that the system does not compute
probabilities for the generated scenarios. Instead, we recommend that the domain experts
assign probabilities to the nal 3-5 scenarios when necessary. In our experience
that approach delivers value to the users much faster and requires signi cantly
less work from the experts, compared to creating prediction models for over 200
often non-stationary risk drivers (e.g., oil prices or election results), and their
interactions, as would be required to derive scenario probabilities automatically.</p>
      <p>We have identi ed the following major challenges in developing SPA: 1)
capturing observations from news and social medial; 2) capturing the domain
knowledge about the risk drivers quickly and e ciently, while preventing con icts;
3) reasoning with incomplete and biased input to include su ciently complete
and minimally biased sets of risks and opportunities in generated scenarios.</p>
      <p>In the rest of the paper, we describe the components of the SPA system,
explaining their role in addressing the challenges, and highlighting the use of
semantic technologies throughout the SPA system. We then present some details
of the deployment that indicate our initial success in overcoming the challenges.</p>
      <p>Domain Knowledge Workflow</p>
      <p>Domain Experts
Local Experts</p>
      <p>InIHcnrciegraehsaiisnnignflgtartdaiodenbetdleefvieclstdeprCUeucSiradetoinolcnayragaTirnasptedLcoawshCeArodcnomtomseoesiCwdtihecoanrdltkieeffmnyograocinpnedgcoaerpntuivtnairilotanevmsatieEolnactibonlfnveooerasmtCtAbio&amp;cecntmdteoeexsercpolaiantntoeeds</p>
      <p>Mind Maps
Social Media,
RSS/Atom</p>
      <p>Customizations
AggNreewgsator InHflaigtihoWnEecaokneonminyg</p>
      <p>WIKIDATA Observations</p>
      <p>AI
Planning
The above gure shows the interactions between SPA components an d2 its users.</p>
      <p>
        Capturing Observations. The News Aggregator component aggregates
news from RSS and Atom feeds and social media posts, e.g., Twitter, in
multiple languages, by monitoring user-con gured keywords for each candidate
observation, for each country. To further re ne and lter the information, News
Aggregator uses the structured semantic knowledge available in Wikidata.
Country relevance is determined based on the mentions of the local people and
organizations found using Wikidata Query Service [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. News Aggregator also uses
Wikidata for source discovery. The end-users (local experts) then choose relevant
observations for scenario planning.
      </p>
      <p>
        Capturing Domain Knowledge. The Mind Maps and The
Customizations components store knowledge about risk drivers and business implications
elicited from the domain experts and the local country experts correspondingly.
While the reasoning engine in SPA supports a rich representation of risk drivers
as actions in Planning Domain Description Language (PDDL) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], the
knowledge representation used by domain experts is drastically simpli ed, to prevent
con icts and reduce overheads in knowledge elicitation and maintenance. The
domain experts use Mind Maps created in FreeMind [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] to capture directed graphs
of risk drivers and business implications, with edges having hidden semantics of
pairwise cause and e ect. The Customizations are elicited using generated
questionnaires that request country-speci c likelihood and impact for selected cause
and e ect pairs. Due to Customizations, the same observations may generate
di erent scenarios in di erent countries.
      </p>
      <p>Reasoning With Incomplete Knowledge. The AI Planning component
applies plan recognition and top-k planning techniques to reason with incomplete
knowledge and generate scenarios [4{6]. The scenarios are clusters of high-quality
plans that include a trajectory of cause-e ect transitions from the Mind Maps,
explaining the largest possible subset of observations (rather than achieving a
prede ned goal), and such that each plan ends with a business implication.
The scenarios, presented as generated text summaries and graphically, are then
reviewed and re ned by scenario planning teams.</p>
    </sec>
    <sec id="sec-2">
      <title>3 SPA Deployment</title>
      <p>The deployed system has over 30 active teams of users, 700 scenarios generated,
and is processing over 50,000 social media messages per hour. There are 230 risk
drivers and business implications and 382 edges between them in the lightweight
Mind Map representation of the domain knowledge used for scenario generation.
We thank Fang Yuan and Finn McCoole at IBM for providing the domain
expertise. We thank Nagui Halim and Edward Shay for their guidance and support. We
also thank our LAS collaborators. This material is based upon work supported in
whole or in part with funding from the Laboratory for Analytic Sciences (LAS).
Any opinions, ndings, conclusions, or recommendations expressed in this
material are those of the authors and do not necessarily re ect the views of the LAS
and/or any agency or entity of the United States Government.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>1. FreeMind: http://freemind.sourceforge.net</mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>McDermott</surname>
            ,
            <given-names>D.V.</given-names>
          </string-name>
          :
          <string-name>
            <surname>PDDL | The Planning Domain De nition Language</surname>
          </string-name>
          .
          <source>Tech. Rep</source>
          . TR-
          <volume>98</volume>
          -003/DCS TR-
          <volume>1165</volume>
          ,
          <article-title>Yale Center for Computational Vision</article-title>
          and Control (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Peterson</surname>
            ,
            <given-names>G.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cumming</surname>
            ,
            <given-names>G.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carpenter</surname>
            ,
            <given-names>S.R.</given-names>
          </string-name>
          :
          <article-title>Scenario planning: a tool for conservation in an uncertain world</article-title>
          .
          <source>Conservation biology 17(2)</source>
          ,
          <volume>358</volume>
          {
          <fpage>366</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Sohrabi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riabov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Udrea</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Plan recognition as planning revisited</article-title>
          .
          <source>In: Proceedings of the International Joint Conference on Arti cial Intelligence (IJCAI)</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Sohrabi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riabov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Udrea</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>State projection via AI planning</article-title>
          .
          <source>In: Proceedings of National Conference on Arti cial Intelligence (AAAI)</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Sohrabi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riabov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Udrea</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hassanzadeh</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Finding diverse high-quality plans for hypothesis generation</article-title>
          .
          <source>In: Proceedings of the 22nd European Conference on Arti cial Intelligence (ECAI)</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>7. Wikidata: https://query.wikidata.org/</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>