<!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>Importance of IS in Mergers and Acquisitions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ksenija Lace</string-name>
          <email>ksenija.lace@cs.rtu.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marite Kirikova</string-name>
          <email>marite.kirikova@cs.rtu.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>PMI Strategies</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Riga Technical University</institution>
          ,
          <country country="LV">Latvia</country>
        </aff>
      </contrib-group>
      <fpage>127</fpage>
      <lpage>132</lpage>
      <abstract>
        <p>With the growing competition, many companies are merging together to get competive advantage [1]. Post-merger integration (PMI) is the process of integrating two or more organizations together in a scope of Merger &amp; Acquisition (M&amp;A) initiative. Current PMI research can be divided in two main parallel streams - PMI of strategy and organizational structure, and PMI of information systems (IS). However, each organization is a complex system, which should be viewed from different interrelated aspects, such as personnel, culture, infrastructure, product portfolio, processes, etc. With this, it sounds reasonable to research PMI as a holistic integration of several socio-cyberphysical systems (SCPS). This paper focuses on the existing PMI and IS PMI research literature review to summarize existing knowledge in these areas, as well as to state main questions for the future SCPS PMI research.</p>
      </abstract>
      <kwd-group>
        <kwd>mergers</kwd>
        <kwd>acquisitions</kwd>
        <kwd>post-merger integration</kwd>
        <kwd>PMI</kwd>
        <kwd>M&amp;A</kwd>
        <kwd>IS PMI</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Company and market share grows
Resource and process base strength
Expansion of product portfolio
Reserch and design (R&amp;D)</p>
      <p>Industry convergence
•
•
•
•
•</p>
      <p>
        What is the integration scope – what are system parts that should be integrated:
resources, lines of products, business units, target top management teams,
systems, etc. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
For each of parts selected for integration – what is the integration approach:
absorption, symbiosis, preservation, holding [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        As one of the main success criteria for PMI is defined the integration of involved
systems, with a quality and scope leading to the synergy [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. But synergy can be
treated in many different ways and there is no easy way how to measure it.
      </p>
      <p>So, future research could elaborate more on PMI goal linkage to M&amp;A goals,
structuring them into all three perspectives: cyber, physical and socio, as well as PMI
goal decomposition and result evaluation for each of listed perspectives.</p>
      <p>
        Besides M&amp;A strategic goals, PMI strategy is also impacted by the context in
which it is executed, and PMI decisions depend on the different contextual factors [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]:
      </p>
      <p>Organizations size and structure
Time limitations
Organization industry sectors
Level of equality between merging partners</p>
      <p>Degree of previous collaboration between merging partners</p>
      <p>Future research could focus on more detailed model of influencing factors and
related decision making process, leading to the specific PMI characteristics.
2</p>
    </sec>
    <sec id="sec-2">
      <title>IS Integration Role in PMI</title>
      <p>
        As already mentioned in Section 1, PMI is the crucial part of each M&amp;A initiative.
And major part of identified problems in M&amp;A are linked directly to information
systems (IS) PMI [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Despite this, PMI research is still primarily focused on
strategy and organization PMI, not IS/IT.
      </p>
      <p>There should be more attention to IS PMI due to several reasons:
•
•
•
•</p>
      <p>
        IS integration is a complex process, which requires time and extensive resources
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
Nowadays IS is the central part of any business process. Organizations literally
depend on the quality and accessibility of information in IS [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
Such enterprise systems as ERP, SCM, CRM are the key elements in
organization functions [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
IS is a crucial for customer services, all problems in IS (like errors and lost data)
could lead to customer loses [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
      </p>
      <p>
        So, IS PMI should be the integral part of PMI process. But, yet again, IS PMI
should not be treated as a separate activity, but rather as a cyber part of SCP system
PMI. We may need additional research in the areas how to incorporate IS integration
part into strategic/structural integration:
Include IS integration activities into each step in overall PMI process, starting
with planning and ending with result evaluation, so that IS PMI support effective
and efficient M&amp;A [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
Link high level M&amp;A and PMI goals with IS PMI goals to align all three
integration aspects [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
      </p>
      <p>
        Here we could come to one more challenge for IS PMI, as merger related
discussions are often not public [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and there could be required special approach how
to involve IS into overall M&amp;A without sharing all information, but sufficient data.
      </p>
      <p>Additionally, if properly managed, IS PMI can significantly improve organizations
competitive state and enable execution of new business strategies. This can be done
through:</p>
      <p>
        Raising IS competence, IS maintenance efficiency and quality of end-user
support [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
Creating synergy through combination of resources [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
Improving IS integration into organizational processes, enhancing IS integration
between organizational units [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
      </p>
      <p>
        Introducing new technologies and attracting high-end IT professionals [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
This area of research also could be investigated more properly in order to come up
with the comprehensive model of so called “side-effect” M&amp;A strategic goals, which
are achievable through IS PMI.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Why IS Integration is Difficult</title>
      <p>At the same time, IS PMI tends to be complicated and complex process, due to
several reasons:</p>
      <p>
        There are quite many IS in each of merging organizations [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
These IS quite often are old systems, different versions of systems, heavily
customized variations of systems, or several copies of the same system, that
makes the integration much more difficult [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
Quite often systems are geographically distributed [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
      </p>
      <p>
        There also quite often is a dependency on external vendors [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>This list is still high-level types of potential difficulties, which in future research
could be elaborated in more details, as well as accompanied by related risk and
problem management activities, which can be taken from existing best practices
mentioned in generic PMI research:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•</p>
      <p>
        Detailed audit of current situation [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
Proper planning [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
Realistic goals [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
Focus on best value for minimum resources [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
Keeping organization functional also during transformational process [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
Ability to learn and recover from integration mistakes
      </p>
      <p>
        Additionally, IS PMI is linked to changes in other areas in merging organizations,
like internal process execution and customer facing services, which requires
management of human factor related risks like emotional traumas, learning
challenges, and expectation mismatch [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Some of already mentioned practices
should be turned into more detailed guidelines:
•
•
•
      </p>
      <p>
        End user involvement [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
Extensive and open communication [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
      </p>
      <p>
        Alignment between stakeholders [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
      </p>
      <p>
        One more aspect in IS PMI is related to the fact, that it leads to some unneeded IS
resources, that should be reconfigured or delaminated [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Currently, there is a lack of
a proper model for capturing such resources, as well as defining required
reconfiguration activities, so that in the end new resource structure operates in the
most efficient way.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>IS PMI Research Perspectives</title>
      <p>
        There is as well a tendency, that current research takes the perspective of one of the
following stakeholders – acquire organization, target organization or future
organization. However, there are more participants involved in the PMI process – like
sellers and consultancies, and their perspective should be taken into account. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
      </p>
      <p>
        Also, major part of existing research is focused on the production industry case
studies, which have own specifics. With growing amount of mergers in IT sector,
current PMI models should be reviewed and adopted to the IT specifics [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. But
before that, IT specifics impacting PMI process, should be identified and described.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>IS PMI, IS Architecture and IT Strategy</title>
      <p>
        IS Architecture could be useful for linking together enterprise architecture and
specific IT systems. As IS architecture usually serves as an intermediate level
between organizational processes and IT systems supporting these processes, it is
important and valuable step in combining PMI of enterprise business models and
related IT systems. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]
      </p>
      <p>
        IS Architecture also helps to plan in details IS integration, as it covers all three
aspects – information architecture, application architecture and technological
infrastructure. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]
      </p>
      <p>
        With looking on IS PMI through IS Architecture perspective, it makes sense to go
even further and integrate PMI into IT Strategy. IT strategy helps us focus on final
goals for PMI and link all planned activities to them yet again. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]
      </p>
      <p>Integrating IS architecture and IT strategy into PMI would mean to execute the
following activities:
•</p>
      <p>Create for all merging enterprises IS Architectures, clearly stating which
business goals and processes are supported by IS from information, application
and technology perspective</p>
      <p>Create merged enterprise IS Architecture, based on the enterprise architecture
for new enterprise
Define IT Strategy to implement IS Architecture created on the previous step</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>In the current PMI and IS PMI research there is a place for SCPS perspective, which
would combine both streams together. SCPS PMI research could become
comprehensive methodology, covering all three dimensions of integrated
organizations – socio, cyber and physical:
•
•
•
•</p>
      <p>M&amp;A strategic goals and linked PMI goals, with clearly defined measurable
success criteria
Impacting contextual factors and related decisions about PMI strategy
Selected PMI strategy with identified integration scope and approach
PMI process framework and best practices</p>
      <p>This methodology would include different stakeholder perspectives, as well as
would take into account different industries specifics. This methodology potentially
could reuse and incorporate some of existing IS Architecture and IT Strategy
approaches.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Wijnhovena</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spila</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stegweea</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>A Fa</surname>
          </string-name>
          , R.T.:
          <article-title>Post-merger IT integration strategies- An IT alignment perspective</article-title>
          .
          <source>Journal of Strategic Information Systems</source>
          <volume>15</volume>
          ,
          <fpage>5</fpage>
          -
          <lpage>28</lpage>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Lohrkea</surname>
            ,
            <given-names>F.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frownfelter-Lohrkea</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ketchen</surname>
          </string-name>
          , Jr.D.J.:
          <article-title>The role of information technology systems in the performance of mergers and acquisitions</article-title>
          .
          <source>Business Horizons</source>
          <volume>59</volume>
          (
          <issue>1</issue>
          ),
          <fpage>7</fpage>
          -
          <lpage>12</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Hwang</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Integrating Enterprise Systems in Mergers and Acquisitions</article-title>
          .
          <source>In: 10th Americas Conference on Information Systems, AMCIS</source>
          <year>2004</year>
          , New York, USA,
          <year>August</year>
          6-
          <issue>8</issue>
          ,
          <year>2004</year>
          , vol.
          <volume>12</volume>
          , pp.
          <fpage>62</fpage>
          -
          <lpage>66</lpage>
          (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bodner</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Capron</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Post-merger integration</article-title>
          .
          <source>Journal of Organization Design</source>
          <volume>7</volume>
          (
          <issue>3</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>20</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Hedman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sarker</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>Information system integration in mergers and acquisitions: research ahead</article-title>
          .
          <source>European Journal of Information Systems</source>
          <volume>24</volume>
          (
          <issue>2</issue>
          ),
          <fpage>117</fpage>
          -
          <lpage>120</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Robbins</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stylianou</surname>
            ,
            <given-names>A.C.</given-names>
          </string-name>
          :
          <article-title>Post-merger systems integration: the impact on IS capabilities</article-title>
          .
          <source>Information &amp; Management</source>
          <volume>36</volume>
          ,
          <fpage>205</fpage>
          -
          <lpage>212</lpage>
          (
          <year>1999</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ravikumar</surname>
          </string-name>
          , N.:
          <string-name>
            <surname>Post-Merger IS</surname>
          </string-name>
          <article-title>Integration: Influence of Process Level Business-IT Alignment on IT-based Business Value</article-title>
          .
          <source>In: Proceedings of the 2017 ACM SIGMIS Conference on Computers and People Research</source>
          , pp.
          <fpage>195</fpage>
          -
          <lpage>196</lpage>
          , June 21-23,
          <year>2017</year>
          , Bangalore, India (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Vasconcelos</surname>
            , André &amp; Sousa, Pedro &amp; Tribolet,
            <given-names>José.</given-names>
          </string-name>
          (
          <year>2003</year>
          ).
          <article-title>Information System Architectures: Representation, Planning and Evaluation</article-title>
          .
          <source>Journal of Systemics, Cybernetics and Informatics</source>
          .
          <volume>1</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Georges</surname>
            ,
            <given-names>P. J.</given-names>
          </string-name>
          (
          <year>1996</year>
          ).
          <article-title>Are your business and your IT strategy in phase ? BT - Implementing Systems for Supporting Management Decisions: Concepts, methods and</article-title>
          <string-name>
            <surname>experiences (P. Humphreys</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Bannon</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>McCosh</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Migliarese</surname>
          </string-name>
          , &amp; J.-C. Pomerol, eds.). https://doi.org/10.1007/978-0-
          <fpage>387</fpage>
          -34967-1_
          <fpage>13</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Tapandjieva</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchetti</surname>
            ,
            <given-names>D. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rychkova</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Wegmann</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2013</year>
          ).
          <article-title>Towards the Definition, Implementation and Communication of an IT Strategy: The Case of IT Strategy at EPFL</article-title>
          . In X. Franch &amp; P. Soffer (Eds.),
          <source>Advanced Information Systems Engineering Workshops</source>
          (pp.
          <fpage>99</fpage>
          -
          <lpage>110</lpage>
          ). Berlin, Heidelberg: Springer Berlin Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Coltman</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Queiroz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2016</year>
          ).
          <article-title>Information Technology and Strategy</article-title>
          . In M. Augier &amp;
          <string-name>
            <surname>D. J. Teece</surname>
          </string-name>
          (Eds.),
          <source>The Palgrave Encyclopedia of Strategic Management</source>
          (pp.
          <fpage>1</fpage>
          -
          <lpage>3</lpage>
          ). https://doi.org/10.1057/978-1-
          <fpage>349</fpage>
          -94848-2_
          <fpage>487</fpage>
          -
          <lpage>1</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>