<!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>Semantic Cloud System for Scaling Data Science Solutions for Welding at Bosch</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Zhuoxun Zheng</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Baifan Zhou</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Zhipeng Tan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ognjen Savkovic</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Diego Rincon-Yanez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nikolay Nikolov</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dumitru Roman</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ahmet Soylu</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Evgeny Kharlamov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Bosch Center for AI</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Computer Science, Oslo Metropolitan University</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Department of Informatics, University of Oslo</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Free University of Bozen-Bolzano</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>RWTH Aachen University</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>SINTEF AS</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff6">
          <label>6</label>
          <institution>Universidad de Santander</institution>
          ,
          <addr-line>Cucuta</addr-line>
          ,
          <country country="CO">Colombia</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <abstract>
        <p>Background and Challenges. Industry 4.0 focuses on smart factories that rely on IoT technology for automation. This produces massive amounts of production data, increasing the demand for data-driven solutions and cloud technology. Yet, users of these solutions and cloud technology are often not cloud experts, such as domain experts and data scientists (Fig. 1.1). In a standard setting of a data science project, the team requires extensive assistance from cloud experts, whenever they want to deploy solutions or make small changes to their solutions deployed on the cloud. To facilitate the adoption of cloud systems careful planing to balance cost and benefits is required. Scaling data science solutions presents challenges of handling high data volume and enabling a broader users which are non-cloud experts to use cloud systems. SemCloud for Distributed ETL and Use Case. In industry, large amount of data collected from diferent resources are integrated and analysed in parallel to optimise the following production. Due to the large volume of data, cloud technology is used to enable distributed ETL. Here, cloud configuration plays an important role in achieving optimal performance, which is however non-trivial for non-cloud experts. To address the scalability challenges and democratising cloud systems for more users, we propose SemCloud [1], a semantics-enhanced cloud system, that scales semantic ETL pipeline on the cloud, and allows non-cloud experts to deploy their solutions. We showcase SemCloud in our welding use case. SemCloud for Automated Cloud Configuration. SemCloud achieves optimised cloud adoption [2] for ETL automatically by breaking down the ETL into pipelines of four steps: retrieve, slice, prepare, and store (Fig. 1.2), where data is first retrieved from databases or online streams, and then split into subsets (e.g. each belong to one welding machine) by slice to achieve parallel processing and storage in the following prepare and store. A rough description of the application of SemCloud is as follows: (a) non-cloud experts create knowledge graphs (KG) that represent ETL-Pipelines on a cloud system, where attributes of cloud resource configuration is under-specified; (b) Datalog ML rules execute in three steps, where the rules contain external</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Sensor
expert
ML
expert
!</p>
      <p>Data
manager</p>
    </sec>
    <sec id="sec-2">
      <title>Slice</title>
    </sec>
    <sec id="sec-3">
      <title>Prepare</title>
    </sec>
    <sec id="sec-4">
      <title>Prepare</title>
    </sec>
    <sec id="sec-5">
      <title>Prepare</title>
    </sec>
    <sec id="sec-6">
      <title>Prepare</title>
      <p>Welding
expert
Knowledge
engineer</p>
    </sec>
    <sec id="sec-7">
      <title>Store</title>
      <sec id="sec-7-1">
        <title>Moving direction</title>
      </sec>
      <sec id="sec-7-2">
        <title>Car body</title>
        <p>"</p>
      </sec>
      <sec id="sec-7-3">
        <title>Welding Spot</title>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>Cloud</title>
      <p>storage</p>
    </sec>
    <sec id="sec-9">
      <title>Datalog ML Rules</title>
    </sec>
    <sec id="sec-10">
      <title>Graph Extraction rules</title>
    </sec>
    <sec id="sec-11">
      <title>Resource Estimation Rules</title>
    </sec>
    <sec id="sec-12">
      <title>Resource Configuration Rules</title>
    </sec>
    <sec id="sec-13">
      <title>Automated Cloud Configuration</title>
      <p>functions obtained by (c) rule parameter learning with ML; (d) automated cloud configuration.
SemCloud Ontology and KG for ETL Pipelines. SemCloud provides the users an ontology
to construct semantic ETL pipelines and encode them into knowledge graphs. The ontology is
written in OWL 2, and consists of 20 classes and 165 axioms. For these data, the users construct
KG for ETL pipelines with four layers (via GUI), which will be used for rule-based reasoning.
Datalog ML Rules. Obtaining an optimised cloud configuration is not trivial. Cloud experts
typically try diferent configurations by testing the system with various settings and use
heuristics to manually decide on the configurations. To this end, SemCloud uses adaptive rules
in Datalog with aggregation and calls to external predicates learned by ML . In particular,
we consider non-recursive rules of the form  ← 1, . . . , , where  is a head of rule
(the consequence of the rule application) and 1, . . . ,  are either predicates that apply join,
aggregate function that filters out the results or the expression of the form Var = @FUNCT(Vars).
Rule Parameter Learning with ML. The functions in the adaptive rules are in the form
of ML models. The resource estimation rules are selected from the best model resulting from
training three ML methods and the pilot running statistics. We selected three representative
classic ML methods: Polynomial Regression (PolyR), Multilayer Percetron (MLP), and K-Nearest
Neighbours (KNN). The resource configuration rules are trained with the three ML methods and
with optimisation techniques, such as Bayesian optimisation or grid search.
User Feedback and Business Impact. SemCloud helps non-cloud experts who know little
about cloud and cannot use cloud system to find the optimal allocation of cloud resources in
various industrial tasks. To verify the time eficiency of SemCloud, we run SemCloud repeatedly
3562 times and gather pilot running statistics. With SemCloud, the Bosch semantic ETL is speed
up to at least twice faster, the optimisation time of cloud configuration is speeded up to 1.12s.
Additionally SemCloud helps more users to use cloud systems, which greatly reduce time and
cost for personnel training and data processing, benefiting data science solution at Bosch.
References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>B.</given-names>
            <surname>Zhou</surname>
          </string-name>
          , et al.,
          <article-title>Scaling data science solutions with semantics and ML</article-title>
          , in: ISWC,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Savkovic</surname>
          </string-name>
          , et al.,
          <article-title>Datalog with external machine learning functions for automated cloud resource configuration</article-title>
          ,
          <source>in: ISWC</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>