<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>M&#38;A Blog &#187; TSA</title>
	<atom:link href="http://www.beaconintegration.com/resources/merger-blog/tag/tsa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.beaconintegration.com/resources/merger-blog</link>
	<description>This blog is dedicated to technology aspects of Mergers &#38; Acquisitions</description>
	<lastBuildDate>Sun, 24 Jan 2010 22:52:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Input into the Divestiture Asset Purchase Agreement (aka educating the Deal Team)</title>
		<link>http://www.beaconintegration.com/resources/merger-blog/2010/01/input-into-the-divestiture-asset-purchase-agreement-aka-educating-the-deal-team/</link>
		<comments>http://www.beaconintegration.com/resources/merger-blog/2010/01/input-into-the-divestiture-asset-purchase-agreement-aka-educating-the-deal-team/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 22:47:48 +0000</pubDate>
		<dc:creator>Jill Blanchar</dc:creator>
				<category><![CDATA[Divestitures]]></category>
		<category><![CDATA[Due Diligence]]></category>
		<category><![CDATA[M&A Strategy]]></category>
		<category><![CDATA[APA]]></category>
		<category><![CDATA[Asset Purchase Agreement]]></category>
		<category><![CDATA[Deal]]></category>
		<category><![CDATA[TSA]]></category>

		<guid isPermaLink="false">http://www.beaconintegration.com/resources/merger-blog/?p=240</guid>
		<description><![CDATA[The process of finding a buyer for a business unit and negotiating the terms of the purchase agreement is done by seemingly a mysterious group of executives and attorneys. As to be expected, the Deal Team is looking at the large corporate picture with certain financial goals and a somewhat defined scope as outlined the [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;">The process of finding a buyer for a business unit and negotiating the terms of the purchase agreement is done by seemingly a mysterious group of executives and attorneys. As to be expected, the Deal Team is looking at the large corporate picture with certain financial goals and a somewhat defined scope as outlined the divestiture Due Diligence. In large companies, several hundreds of millions or even billions of dollars are at stake and the Deal Team often expects that the details will be worked out at a later date. Those details are usually left to different group of people that have to determine the intent of the purchase agreement and manage through the devil that always exists in the details. The Asset Purchase Agreement (APA) most likely will include some type of technology whether it is infrastructure, applications, data, or a combination of such. It is important that the Deal Team be educated on certain aspects of technology that may either affect the bottom line of the deal or affect the timeline between the deal signing and the targeted Legal Day 1 date. If not, the technology organizations will feel the pain if the APA is written such that it conflicts with the ability of their organization to meet the timelines or included assets that may be cumbersome or costly to separate. This article is intended to provide the reader information on ensuring the Deal Team negotiates a deal that protects the interests of the seller from a technology perspective.</p>
<p>Before technologists can educate – they must be educated themselves. If no in-house Divestiture experience exists, hire an expert on your staff or hire a consulting company to help guide you through the process. The benefits will far outweigh the cost.</p>
<p>Topics technology organizations need to be at a minimum knowledgeable in:</p>
<p>1) Divestitures in general and the potential impact to technology resources<br />
2) Legal, Compliance, Regulatory, Risk and Information Security requirements as related to separating the business unit<br />
3) Divestiture Due Diligence process<br />
4) Transition Service Agreement (TSA)<br />
5) Licensing Agreements</p>
<p>Once technology organizations have been educated on the above topics, the below areas need to be in place or documented prior to approaching the Deal Team:</p>
<p>1) <strong>Executive Sponsorship</strong><br />
It is important that technology organizations have the appropriate executive sponsorship and involvement that can provide the Deal Team with guidance on contractual obligations being considered in the APA.<br />
2) <strong>TSA Services</strong><br />
Prepare of list of TSA services that are typically included and excluded in a divestiture and brief rationalization or impact. The excluded services may include electronic mail, mobile phones, and desktops.<br />
3) <strong>Licensing<br />
</strong>Hardware and software licensing can be a considerable expense if included in the deal and can have real impact to the bottom line of the deal. There is a distinct difference between a Right to Use license versus transfer of a license.<br />
4) <strong>Technology Assets</strong><br />
Prepare a list of infrastructure and/or application assets that cannot be included in the deal. These assets may include computers that are leased or applications that span other areas of the company that must remain behind to support the remaining business.<br />
5) <strong>Timelines required to complete separation</strong><br />
Depending on the requirements from Legal, Compliance, Regulatory, and Information Security, there may be significant amount of work required to separate the business unit prior to the Closing Date. Activities may include movement of people, application logical or physical separation, and data/voice network installations.</p>
<p>In closing, it is important that the team that is negotiating the Deal with the buyer must understand the implications from a monetary as well as timing perspective prior to signing the Asset Purchase Agreement. It is the responsibility of the Technology leadership to understand the scope of the Divestiture in terms of people and technology, and weigh in on the impacts on the ability to execute the pre-LD1 activities.  Not to do so, may result in increased expense to the selling company and inability to meet the contractual obligations.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.beaconintegration.com/resources/merger-blog/2010/01/input-into-the-divestiture-asset-purchase-agreement-aka-educating-the-deal-team/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Overcoming Divesture Issues for Email Transfer</title>
		<link>http://www.beaconintegration.com/resources/merger-blog/2009/05/overcoming-divesture-issues-for-email-transfer/</link>
		<comments>http://www.beaconintegration.com/resources/merger-blog/2009/05/overcoming-divesture-issues-for-email-transfer/#comments</comments>
		<pubDate>Wed, 27 May 2009 21:51:44 +0000</pubDate>
		<dc:creator>Alexander</dc:creator>
				<category><![CDATA[Divestitures]]></category>
		<category><![CDATA[Carve-Out]]></category>
		<category><![CDATA[Carve-outs]]></category>
		<category><![CDATA[divest]]></category>
		<category><![CDATA[Due Diligence]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Merger]]></category>
		<category><![CDATA[Merger Issues]]></category>
		<category><![CDATA[restructuring]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[TSA]]></category>

		<guid isPermaLink="false">http://www.beaconintegration.com/resources/merger-blog/?p=123</guid>
		<description><![CDATA[Many technology challenges exist when a company makes the decision to divest (carve-out) a business unit.   One area that requires special attention is electronic communication in the form of email. ]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;">Many technology challenges exist when a company makes the decision to <a href="http://www.beaconintegration.com/service.htm" target="_self">divest (carve-out)</a> a business unit. <span style="mso-spacerun: yes;">  </span>One area that requires special attention is electronic communication in the form of email.<span style="mso-spacerun: yes;">  </span>Often an acquiring company will request current or historical email of divested employees to maintain business functionality, or to provide customer relationship continuity after the close.<span style="mso-spacerun: yes;">  </span>However, to the divesting company, current and archived email may possess proprietary information that would be inappropriate to release to the acquirer.<span style="mso-spacerun: yes;">  </span>A solution to this problem is called email redaction. This is a process of editing emails prior to transfer of the emails to the acquirer.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;">Redaction has been traditionally practiced on paper documents, with black markers or correction tape. <span style="mso-spacerun: yes;"> </span>In electronic documents, specific words may be deleted or blocked by changing fonts or background colors.<span style="mso-spacerun: yes;">   </span>In the case of email redaction, complete emails may be removed from the divested employees’ email files.<span style="mso-spacerun: yes;">  </span>A sound policy with clear objectives must be defined by business leaders and legal counsel prior to engaging the technology staff. Ideally, this will be defined during the <a href="http://www.beaconintegration.com/resources/merger-blog/2009/02/technology-due-diligence-series-introduction/" target="_blank">due diligence</a></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small;"><span style="font-family: Arial;">One objective may be to remove specific emails related to any legal or compliance topic, This objective may be difficult to achieve in organizations that have large number of employees involved in the transaction and/or large email files.<span style="mso-spacerun: yes;">  </span>To address this complexity, often the objective is broadened in scope and emails that include specific people are removed in their entirety.<span style="mso-spacerun: yes;">  </span>Examples of employees’ correspondence that may be removed are compliance officers, attorneys, supply chain managers, and other key employees that have participated in activities whose correspondence, if disclosed<span style="color: black;">, may provide a competitive advantage to the acquiring company unrelated to the business unit being purchased.<span style="mso-spacerun: yes;">  </span>The divesting company typically creates a policy that is conservative in nature to protect their interests.</span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small;"><span style="font-family: Arial;"><span style="color: black;">Once a redaction policy has been created, technology teams must plan their execution strategy by performing investigation of all possible email sources. Divested employee emails exist on active email servers but also in other locations such as on user desktops or laptops, file shares, and third-party archival services.<span style="mso-spacerun: yes;">  </span>The scope of </span>the redaction should exclude third-party archival services as those emails typically are not included as part of the divested assets and are only made available to the acquirer in the event of future legal inquiries.<span style="mso-spacerun: yes;">  </span>The other locations require extensive inventory scanning of file shares and desktops prior to beginning the redaction process.<span style="mso-spacerun: yes;">  </span>Investigation of these sources may result in the discovery that terabytes of storage has been dedicated to email files depending on the number of divested employees and the strictness of the divesting company’s email policies on size and retention. <span style="mso-spacerun: yes;"> </span>Sufficient storage is required to make copies of the original email files to process the redaction policy.<span style="mso-spacerun: yes;">  </span>The technical execution of the redaction may focus on the removal of any email with a specified list of people in the “To”, “From”, or “cc” fields.<span style="mso-spacerun: yes;">  </span>Embedded emails within an email must also be redacted.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small;"><span style="font-family: Arial;">Timing of the redaction is critical.<span style="mso-spacerun: yes;">  </span>Assuming the acquirer provides email services to the divested employees on <a href="http://www.beaconintegration.com/workshops.htm" target="_self">Legal Day 1</a>, redaction of an email must occur at that time or shortly thereafter.<span style="mso-spacerun: yes;">  </span>Redaction of the current server-based email is usually the fastest and processing this source first allows immediate transfer of current email to the acquirer.<span style="mso-spacerun: yes;">  </span>If email files on file shares and desktops are too large to redact immediately, they must be restricted such that employees may not modify them, or remove employee access completely.<span style="mso-spacerun: yes;">  </span>Once redaction has occurred, the newly redacted email files may be transferred to the acquirer for employees to have access at the new company.<span style="mso-spacerun: yes;">  </span>Original email files may be retained by the seller if required per a  <a href="http://www.beaconintegration.com/merger-services.htm" target="_self">(TSA).</a><span style="mso-spacerun: yes;">  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;">The divesting company must inform the acquiring company of the redaction and the high level strategy applied.<span style="mso-spacerun: yes;">  </span>However, it is strongly recommended that the redaction is kept confidential among those who are negotiating the terms of the transaction or TSA.<span style="mso-spacerun: yes;">  </span>Confidentiality is required to assure that employees that are part of the transaction do not make attempts to print or save the emails to an unknown destination (e.g. outside of the company).<span style="mso-spacerun: yes;">  </span>Redaction may have <span style="color: black;">implications on a TSA</span> which would require the divesting company to provide redacted emails upon request.<span style="mso-spacerun: yes;">  </span>These requests are legitimate if they include information which maintains the best interest of divesting company and<span style="color: green;"> </span>are relevant to the divested business unit.<span style="mso-spacerun: yes;">  </span>However, fulfilling the request to provide the redacted email may be time-consuming and manual process. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;">Email redaction is a complex solution but acceptable for any company that is divesting of a business unit.<span style="mso-spacerun: yes;">  </span>However, companies involved in a <a href="http://www.beaconintegration.com/" target="_self">divestiture </a>considering this solution to protect their proprietary information<span style="mso-spacerun: yes;">  </span>must be aware of the potential longer term responsibilities related to the redaction as well as the significant time and resources to perform the redaction itself.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-size: x-small; font-family: Arial;"> </span><span style="font-size: x-small; font-family: Arial;">JB</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.beaconintegration.com/resources/merger-blog/2009/05/overcoming-divesture-issues-for-email-transfer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Divestiture and Business Carve-out Technology Considerations</title>
		<link>http://www.beaconintegration.com/resources/merger-blog/2009/04/divestiture-and-business-carve-out-technology-considerations/</link>
		<comments>http://www.beaconintegration.com/resources/merger-blog/2009/04/divestiture-and-business-carve-out-technology-considerations/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 02:01:34 +0000</pubDate>
		<dc:creator>Alexander</dc:creator>
				<category><![CDATA[Divestitures]]></category>
		<category><![CDATA[Acquisition]]></category>
		<category><![CDATA[Acquisitions]]></category>
		<category><![CDATA[Carve-Out]]></category>
		<category><![CDATA[Carve-outs]]></category>
		<category><![CDATA[Due Diligence]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[M&A]]></category>
		<category><![CDATA[Merger]]></category>
		<category><![CDATA[Mergers]]></category>
		<category><![CDATA[Private Equity]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[TSA]]></category>

		<guid isPermaLink="false">http://www.beaconintegration.com/resources/merger-blog/?p=120</guid>
		<description><![CDATA[How often have you seen a merger or acquisition that made perfect sense not pan out? In many cases, deal makers are simply ignoring the increasing role of information technology and paying the price.]]></description>
			<content:encoded><![CDATA[<p>Mergers and acquisitions continue to be prominent in today&#8217;s public corporate and private equity space. A significant challenge to most organizations that are in the market to acquire or divest a business unit is how to address the Information Technology requirements. Unlike an acquisition whereby the entire company is being acquired, an acquisition of an individual business unit(s) poses unique challenges particularly in the case where it resides in a well-integrated, efficient technical environment. Rarely can a business unit be turned over to the purchasing organization on Legal Day 1, but instead a Transition Services Agreement (TSA) must be developed between the two organizations which stipulates the seller to continue providing the computing environment for a period of time while the buyer executes the plan for integration into their own environment.</p>
<p>With increasing focus on individual privacy, and threats from malicious sources to gain access to individual&#8217;s information or corporate proprietary information, the importance of planning technology isolation during the TSA period has increased exponentially. This isolation is equally important to the organization that is selling the business unit as to the organization that is acquiring the unit to protect the interests of both parties and is required in regulated industries.</p>
<p>The most important, yet often challenging, step to a successful divestiture and impending acquisition of a business unit is to have a clear understanding of what encompasses the transaction. It is critical to have the application disposition defined, detailed inventory of the technology assets included sale, and the physical locations of the employees affected by the sale to develop an isolation strategy. Once the environment that is proposed to be sold has been defined, a crucial next step is to assess the applications and computing environment to garner an understanding of their dependencies on the selling organization, and the larger organization&#8217;s dependencies on them.</p>
<p>Technology organizations must work closely with real estate management divisions to develop a human resource strategy to isolate both physically and logically those employees that will be sold to the acquirer. Often this strategy involves the consolidation of employees and applications to designated sites, and the implementation of dedicated network and security infrastructure. Such isolation will assure that post-Legal Day 1, the individuals that became employees of the purchasing organization no longer have access to seller&#8217;s network and proprietary information. This task becomes more complex when seconded individuals exist which require access to both companies.</p>
<p>Investment by the seller is required to support the isolation of the business unit prior to its being sold. The IT component which potentially includes the purchase of new equipment and resource hours may be significant and should be considered prior to agreement on the deal. The amount of consolidation and number of employee affected may reduce costs, however, the seller needs to expect a minimal amount of activity to perform the isolation regardless of the size of the business unit, particularly if the industry is highly regulated. Aggressive timelines to complete the transaction may also significantly increase costs and need to be considered. A Forward Looking Due Diligence® assessment prior to finalizing the deal by an experienced team can uncover additional costs and provide the selling organization an accurate estimation of the cost involved to achieve the isolation thus providing the appropriate environment to assure their business is protected from malicious or unintentional damage from a business unit no longer part of their company.</p>
<p>For organizations that that don&#8217;t have the internal expertise to work through technology disentanglement, a professional M&amp;A due diligence technology assessment consultancy such as Beacon Integration LLC, http://beaconintegration.com, can be engaged to orchestrate technology aspects of the transaction.</p>
<p>J. B.  is a seasoned technology executive with over 10 years of planning the technology aspects of mergers, acquisitions, and divestitures for Fortune 100 companies.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.beaconintegration.com/resources/merger-blog/2009/04/divestiture-and-business-carve-out-technology-considerations/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
