<!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>Knowledge-Based Support to Business Innovation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Francesco Taglino</string-name>
          <email>taglino@iasi.cnr.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fabrizio Smith</string-name>
          <email>smith@iasi.cnr.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maurizio Proietti</string-name>
          <email>proietti@iasi.cnr.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>National Research Council</institution>
          ,
          <addr-line>IASI “Antonio Ruberti” Viale Manzoni 30, 00185 Roma</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We address the problem of providing knowledge management support to business innovation. We consider the context of virtual enterprise environments, where knowledge is often fragmented and heterogeneous, and interoperability is a crucial requirement. We propose a knowledge repository and management infrastructure, called Production and Innovation Knowledge Repository (PIKR), to support open innovation in virtual enterprises. The PIKR provides a set of reference ontologies to semantically describe enterprise knowledge resources, and semantics-based services for accessing and reasoning over such descriptions. The proposal is being conceived in the framework of the BIVEE European project and adheres to the Linked Data approach.</p>
      </abstract>
      <kwd-group>
        <kwd>business innovation</kwd>
        <kwd>ontologies</kwd>
        <kwd>semantic description</kwd>
        <kwd>semantic services</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        In increasingly competitive environments, where new business practices and products
are regularly introduced, organizations need to solicit, support and ease innovation, as
it appears a critical factor for them to be successful. ICT solutions have facilitated the
creation of new kinds of business alliances, the so called Virtual Enterprises (VEs),
facilitating also the advent of the so called Open Innovation paradigm, which assumes
that “firms can and should use external ideas as well as internal ideas, and internal
and external paths to market, as the firms look to advance their technology” [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>In any case, innovation generation and development need the observation and
awareness of the reality around, both internally and externally to the enterprise. A
very interesting sort of observation-oriented approach to innovation is biomimetism,
which is defined as “the study of the structure and function of biological systems as
models for the design and engineering of materials and machines”1. It starts from the
assumption that there may be a good reason why nature has designed animal and
plants as they are. An example of application of this pattern is the design of the
Shinkansen, the innovative Japanese bullet train, which has been inspired by the study of
the kingfisher’s beak, which turns out to be supremely efficient at crossing the
airwater interface with the minimum amount of turbulence2.</p>
      <p>But, beyond very challenging and fascinating approaches, it is also very crucial the
observation and monitoring reality internal to the enterprise. This means to know how
production activities are actually performed, and how performing they are, what kinds
of resources (in terms of skills and expertise) the enterprise can count on, what
documental resources (e.g., market analysis, technical reports) have been produced or
acquired by the enterprise. But it is also very important to know how innovation-related
initiatives are carried on, e.g., what is the degree of participation of people to
brainstorming activities, how many relevant ideas have been collected in certain periods of
time, how many proposed ideas have been concretely exploited, and so on.</p>
      <p>According to the above considerations, innovation-related activities need a very
effective knowledge management and interoperability support, especially in virtual
enterprise environments and open innovation scenarios, where the landscape is more
fragmented, and heterogeneous.</p>
      <p>
        The purpose of this paper is to present a proposal of knowledge-based
infrastructure, named PIKR (Production and Innovation Knowledge Repository), to support
business innovation. This proposal is being conceived in the framework of the BIVEE
European project3, and adheres to the Linked Data approach [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
2 http://www.innovationexcellence.com/blog/2010/07/30/innovation-by-observation
3 http://bivee.eu
Following the Linked Data approach which recommends a set of best practices for
exposing, sharing, and connecting pieces of data, information, and knowledge by
using semantic web technologies, the PIKR will provide, on the one hand a set of
reference structures (i.e., ontologies) for semantically describe enterprise knowledge
resources, and on the other hand semantics-based services for accessing and reasoning
over such descriptions.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>PIKR Ontological Framework</title>
      <p>The mission of the PIKR is to create a semantics-based unified view of the
information and knowledge that flow within and across the Production Space (where all the
activities related to the core business take place), and the Innovation Space (mainly
characterised by creative units and cooperative interactions) of VEs. In particular,
these two spaces are seen through the following types of knowledge resources:
Processes, which describe actual production activities; Documents, which are concrete
footprints of any kind of activity, both at production and innovation level; Actors and
their competencies, which refer to the capabilities of the VE and its members; Key
Performance Indicators (KPIs), for monitoring both the Production and the
Innovation space.</p>
      <p>Then, the PIKR is organized into two layers (Fig. 1): the Intensional PIKR
(IPIKR), which contains a federation of ontologies to describe the enterprise resources,
and the Factual PIKR (F-PIKR), which contains the semantic representation
(Semantic Descriptors) of the actual enterprise resources in terms of the above ontologies.</p>
      <p>The ontologies in the I-PIKR are partitioned into Knowledge Resource Ontologies
(KROs), and Domain Specific Ontologies (DSOs). KROs are independent of any
application domain and declare what kind of information, links, constraints and business
rules, for each type of knowledge resource (i.e., Processes, Documents, Actors, and
KPIs), we intend to semantically represent (Semantic Descriptors Skeleton, SDS),
while DSOs allow Semantic Descriptors to be enriched with domain specific contents
(e.g., furniture domain).</p>
      <p>According to this vision, the I-PIKR contains four main KROs: ProcOnto,
DocOnto, ActorOnto, and KPIOnto, for describing processes, documents, actors, and
key performance indicators, respectively, and inter-connections between them.
Consequently, the Semantic Descriptors, which describe actual knowledge resources (e.g.,
the technical report realized in a specific project, or the process for producing a
certain product) will be instances of the KROs.</p>
      <p>Independently of their specificities, due to the different nature of the knowledge
resource types, the KROs will aim to catch certain categories of information so that the
Semantic Descriptor Skeletons will be characterized by a common structure organized
into the following sections:
 Header: collects information represented by traditional metadata like the ones
proposed by the Dublin Core Vocabulary4 (e.g., name, natural language
descrip4 http://dublincore.org
tion). This section also contains the link to the actual knowledge resources that is
assumed to be stored in a proprietary system, e.g., a document management system
or a business process (BP) management tool.
 Domain Specific Content: collects information about the content of the described
knowledge resource in terms of the DSOs. For instance, in this section one can say
that a given technical report is about the design of an innovative contour chair in
carbon fibre.
 Related Knowledge Resources: collects links to related Semantic Descriptors,
allowing the representation of semantic associations and dependencies among
resources (the input document of an activity, an indicator occurring in a formula
defining a KPI, the temporal dependency between a feasibility study and a project
proposal).
 External links: links to resources external to the VE and possibly available on the
internet (e.g., technical documentation, external policies or regulations, web-sites,
bibliographic references).
 Extended Representation: links to representations of the resource that will allow
the enactment of specific reasoning facilities (e.g., a mathematical representation
of a KPI, a machine processable representation of a business process).
Domain Specific Content and Related Knowledge Resources items can be enriched
with business rules which give the possibility to characterize the semantic descriptor
skeletons with respect to the particular reality of a virtual enterprise. These constraints
can depend, for instance, on the specific application domain, on the dimensions of the
VE, or on the VE internal policies. For example a feasibility study for justifying the
prototyping of a product needs financial information, if the expected cost is higher
than a certain amount (e.g., 300 Keuro). This means that for feasibility studies,
financial information is not always mandatory, even in the same VE.</p>
      <p>
        For the definition of the KROs we are following different approaches with respect
to the different kinds of resources. In the case of the DocOnto, we are considering
both production and innovation related documents. For the production documents
(e.g., invoices, bills of materials) there is plenty of literature and standards (e.g., UBL
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], RosettaNet [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), which describe information items and dependencies among such
documents. For the innovation documents (e.g., ideas, project proposals) we are
mainly eliciting needed information through the interaction with end users of the
BIVEE project. In particular, the BIVEE project has introduced a document-centric
vision of innovation, based on four waves: creativity, feasibility, prototyping and
engineering. We are then analysing how the BIVEE end users currently address
innovation generation with respect to these waves, what kinds of documents they produce,
which dependencies and constraints are among these documents.
      </p>
      <p>
        In the case of the ProcOnto, we refer to a logic-based language for representing
and reasoning with process knowledge. We proposed to adopt BPAL (Business
Process Abstract Language), which is a process ontology, strongly inspired to the
BPMN [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] notation. BPAL provides an explicit formalization of the meta-model and
of the execution semantics thus allowing advanced BP querying facilities [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] that take
into account both the structure (i.e., the workflow graph underlying the BPs) and the
behavior (i.e., the possible executions) of BPs. Thanks to its grounding into logic
programming, BPAL can be easily adopted in conjunction with rule-based ontology
languages (e.g., OWL-RL [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]) for the annotation of BP schemas with respect to
domain specific ontologies.
      </p>
      <p>
        In the case of the KPIOnto, we refer to existing classifications like the one in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]
which categorizes KPIs into Operative, Administrative and Strategic, and in
particular, to the Value Reference Model5 (VRM) which provides a standard classification of
KPIs both for production and innovation activities. Furthermore, we intend to address
also a formal representation of mathematical structures of KPIs in order to enable
some forms of reasoning on them, such as the ability to check semantic correctness
and redundancies of KPI definitions and the analysis of dependencies among KPIs
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Architecture and Semantic Services</title>
      <p>5 http://www.value-chain.org/en/cms/1960
6 http://www.smwplus.com
7 http://incubator.apache.org/jena/index.html</p>
      <p>On top of the Knowledge Repository, the PIKR Reasoner makes available four
main types of semantics-enabled services.</p>
      <p>
        Search. This module provides keyword-based search services, following an
interaction paradigm similar to traditional web information retrieval engines. The user
request is expressed as an ontology-based feature vector describing the criteria for the
selection of the resources of interest. The search engine returns a list of ranked results
by applying semantic similarity techniques (e.g., the SemSim metric [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]) to compute
the degree of matching between the concepts used to formulate the given request and
the ones used to describe the available resources. For instance, suppose that the user is
interested in finding all the documents which have been authored in the last two years
and concerning the initial stages of the design of a piece of furniture equipped with an
electronic device. The corresponding request should be then formulated by using
terms defined in the I-PIKR, e.g., {Resource:Document, Wave:Creativity,
Content:[Domotics, Furniture, Electronic_Device], Year&gt;2010}. Rather than simply
providing links from search results to the source documents in which the keywords are
textually mentioned, the engine will retrieve semantically related resources, such as
Proposed_Idea or Project_Proposal documents (which are assumed to be defined in
the DocOnto as specific types of Creativity Wave documents) about a Contour_Chair
with an embedded Media_Player (which are assumed to be defined in the DSO as
kinds of piece of furniture and electronic device, respectively).
      </p>
      <p>
        Query. This module provides services to retrieve pieces of knowledge which
exhibit some given properties. Queries are posed in terms of the vocabulary and semantic
relations provided by the PIKR ontologies, and the underlying reasoning engine
returns a list of answers that satisfy all specified properties. These answers may consist
of factual knowledge (semantic descriptors), conceptual knowledge (ontological
terms), or references to resources. The most prominent standard for querying
OWL/RDFS resources is the SPARQL (SPARQL Protocol and RDF Query
Language) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] standard, defined by the World Wide Web Consortium and widely
accepted in the semantic web community. SPARQL is in fact designed to query RDF
resources, that essentially are organized as directed and labeled graphs, by matching
graph patterns over RDF graphs. We are currently developing a query language based
on the SELECT-FROM-WHERE paradigm to extend the SPARQL language by
providing additional primitives to be used specifically for querying particular resource
kinds (e.g., BPs, KPIs) besides RDF models. The Query service can be useful, for
instance, in a scenario where there is the need of reengineering a process, as a
consequence of an alert emerged by the KPI-driven monitoring. In this case we may want
to retrieve all the documents related to the given process which have been defined in
the Engineering Wave. The query engine will return as answer a list of (links to)
documents specifying the procedures (e.g., Quality_Protocol or Assembling_Protocol
documents) implemented by the process itself.
      </p>
      <p>Consistency Checking. This module provides services for checking the
compliance of the factual knowledge captured in the semantic descriptors with respect to
business policies and internal regulations established for the whole VE or for
individual enterprises. Such compliance requirements are represented in the I-PIKR in terms
of business rules, i.e., statements that define or constrain some aspects of the business,
specifying the structure of the domain entities (structural constraints) and influencing
the way business operations are conducted (behavioral constraints). In our frame the
compliance check takes place by verifying the consistency between the assertions
contained in the F-PIKR and the axioms defined in the Knowledge Resource
Ontologies formalizing the business rules. An example of structural constraint is “Each
Innovation_Report needs to be composed by a Project_Proposal and a Market_Report”,
while an example of behavioral constraint is “A Monitoring_Sheet cannot be
produced unless a Gantt_Chart has been finalized before”.</p>
      <p>KPI Reasoning. This module provides inference services for supporting KPI
elicitation (i.e., the identification of the KPIs which are suitable for a given VE), by
analyzing KPIs from different perspectives (e.g., organization and time dimensions). This
module also supports the harmonization of the measures provided by VE member
which are needed for the evaluation of KPIs. Indeed, since measures can be originated
by different data sources (e.g., proprietary information systems) from different
enterprises in the VE, they need to land on a reference representation compliant with the
KPI formulas. Examples of heterogeneities between data definitions and required
input for KPI evaluation could be in terms of terminology (e.g.,
Customer_Requested_Date vs. Expected_Delivery_Date), or granularity (e.g., aggregated vs.
atomic data).
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusions and Future Works</title>
      <p>In this paper we presented a semantics-based infrastructure, called PIKR, aiming at
providing a unified view of different kinds of knowledge resources that are present in
a virtual enterprise context, for supporting both the production and innovation
development activities. This infrastructure is designed, according to the Linked Data
approach, by describing knowledge resources and their semantic relations in terms of a
federation of reference ontologies, which define production processes, documents,
actors and key performance indicators. While the actual knowledge resources are
stored at the premises of the respective owner companies in the virtual enterprise, the
PIKR maintains resource images in the form of semantic descriptors that can be
regarded as instances of the ontologies. On top of this descriptions, a set of semantic
services is offered for easing the navigation and the retrieval of such resources, along
with a set of facilities for reasoning over them.</p>
      <p>While in this paper we give an overview of the PIKR infrastructure, in the next
future we will address three main issues: the building of the specific reference
ontologies as illustrated in Section 2, the definition of the semantic services, and the full
implementation of the PIKR.</p>
      <p>Acknowledgments. This work has been partly funded by the European Commission through
the ICT Project BIVEE: Business Innovation and Virtual Enterprise Environment (No.
FoFICT-2011.7.3-285746). The authors wish to acknowledge the Commission for its support. We
also wish to acknowledge our gratitude and appreciation to all BIVEE project partners for their
contribution during the development of various ideas and concepts presented in this paper.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Chesbrough</surname>
          </string-name>
          , H.:
          <article-title>Open Innovation: The New Imperative for Creating and Profiting from Technology</article-title>
          , Boston Harvard Business School Press,
          <year>2003</year>
          , ISBN:
          <fpage>1</fpage>
          -
          <lpage>57851</lpage>
          -837-7.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bizer</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heath</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berners-Lee</surname>
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked Data - The Story So Far</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems</source>
          .
          <volume>5</volume>
          (
          <issue>3</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <source>Universal business language v2.1. Technical report, OASIS</source>
          ,
          <year>2011</year>
          , http://docs.oasisopen.org/ubl/UBL-2.1.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>RosettaNet</given-names>
            <surname>Program</surname>
          </string-name>
          <article-title>Office: Cluster, segments, and pips overview</article-title>
          .
          <source>Technical report</source>
          ,
          <year>2011</year>
          , http://www.rosettanet.org.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. OMG.
          <article-title>Business Process Model and Notation</article-title>
          . http://www.omg.org/spec/BPMN/2.0,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Missikoff</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proietti</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Querying Semantically Enriched Business Processes</article-title>
          .
          <source>Proc. of the 22st Int. Conf. on Database and Expert Systems Applications LNCS 6861</source>
          , pp.
          <fpage>294</fpage>
          -
          <lpage>302</lpage>
          , Springer,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krotzsch</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Rudolph</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>OWL 2 Web Ontology Language</article-title>
          .
          <source>W3C Recommendation</source>
          , http://www.w3.org/TR/owl2-primer/,
          <year>October 2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Eschenbaecher</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Glaser</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Managing and optimizing innovation processes in collaborative and value creating networks</article-title>
          .
          <source>International Journal of Innovation and Technology Management</source>
          .
          <volume>8</volume>
          (
          <issue>3</issue>
          ):
          <fpage>373</fpage>
          -
          <lpage>391</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Diamantini</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Potena</surname>
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Thinking Structurally Helps Business Intelligence</surname>
          </string-name>
          <article-title>Design</article-title>
          .
          <source>Proc. of the itAIS Conference. Naples (Italy)</source>
          ,
          <source>Oct. 8-9</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Formica</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Missikoff</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pourabbas</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taglino</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Semantic Search for Enterprises Competencies Management</article-title>
          .
          <source>Proc. of the 2nd Int. Conf. on Knowledge Engineering and Ontology Development (KEOD)</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Prud'hommeaux</surname>
          </string-name>
          , E., and
          <string-name>
            <surname>Seaborne</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>SPARQL Query Language for RDF</article-title>
          .
          <source>W3C Recommendation</source>
          , http://www.w3.org/TR/2007/WD-rdf
          <string-name>
            <surname>-</surname>
          </string-name>
          sparql-query-
          <volume>20070326</volume>
          /,
          <year>January 2008</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>