Access Official Technical PDF

Share Summary:LinkedInEmail

An IT carve-out in manufacturing is more than separating servers and applications from a parent company. It requires coordinated changes to infrastructure, data, security, networks, end-user services, and operating processes—often while production and business functions continue. Hemlock Semiconductor (HSC), a high-purity polysilicon producer based in Michigan, faced this challenge after a change in ownership structure created the need to establish independent IT operations.

The objective was to complete the separation within the Transition Services Agreement (TSA) timeframe, avoid disruption to business operations, and prepare the new environment for ongoing management. The case illustrates how a carve-out can also become an opportunity to modernize infrastructure, provided transition risks and operational dependencies are managed together.

Why manufacturing IT carve-outs are complex

During a carve-out, the departing organization may depend on the parent company for technology services, data, applications, infrastructure, and support. A TSA provides a defined period for those services to continue while the new organization builds or transitions to its own environment. That window creates a firm delivery constraint: separation must progress without leaving the business unsupported when the agreement ends.

For HSC, the goal was not simply to reproduce the existing environment. The company sought a flexible, secure, and scalable operating model, with compliance and governance mechanisms in place and managed services available from Day 2. That meant planning for both the immediate separation and the longer-term environment the business would operate.

Two challenges made execution particularly demanding. Limited privileged access to the parent organization’s infrastructure reduced visibility into the systems being separated. At the same time, the program included a major technology shift, including a move to Microsoft Teams Voice across business and manufacturing environments. These conditions made risk assessment, sequencing, and coordination central to delivery.

Coordinating separation, transformation, and operations

The program took approximately eight months. A phased approach, aligned with an ITIL V3 framework, covered organizational change management, infrastructure migration, application and data transition, information security, and risk mitigation. This helped connect technical work with the procedures and operational readiness needed to support users and business functions.

The infrastructure portfolio included systems, processes, tools, software and hardware assets, warranties, and licenses. Application and data migration also had to be carried out within the TSA period. Treating these as connected workstreams helped the team address dependencies across the environment rather than viewing each technology move as an isolated task.

HSC’s application infrastructure was separated into business infrastructure and Process Control Networks (PCN) infrastructure. This distinction is important in an industrial setting: business IT and process-control environments have different operational roles, and their separation needs to be reflected in planning and architecture. The source case describes the segregation of these environments and the use of Veeam to facilitate migration of applications hosted in the business infrastructure.

Modernizing the infrastructure for a standalone environment

Alongside separation, the target environment was designed and built to support business, technology, and operational objectives. The transformation included a hybrid cloud model combining hyperconverged private cloud with Azure, Microsoft 365, and SAP cloud. The hyperconverged architecture was intended to provide centralized management and a platform for hosting and managing applications with greater flexibility and scalability.

Network changes included a move to Software-Defined Wide Area Networking (SD-WAN) and Software-Defined Networking (SDN). In the described design, SDN connected multiple cloud environments with the on-premises data center, while SD-WAN was used to automate network operations and support savings. Security transformation included Palo Alto firewalls.

Workplace services were modernized as well. The move from traditional VoIP to Microsoft Teams was intended to improve collaboration and the end-user experience. End-user computing changes included Azure and Microsoft 365 technologies such as Autopilot, Always-On VPN, virtual desktop infrastructure (VDI), and Intune, supporting a more automated and self-healing model.

Service management and monitoring were also part of the new operating model. The implementation used ServiceNow and Resolve (formerly FixStream) for analytics and infrastructure monitoring. Establishing these capabilities alongside the new infrastructure helped prepare the environment for ongoing service management rather than treating the carve-out as a one-time migration.

Reported outcomes and practical implications

The case reports that the separation and transformation were completed within the TSA timeframe, with no impact to business operations. HSC moved away from its dependency on the selling company’s IT infrastructure while transitioning to a modern hybrid cloud environment.

Reported results included infrastructure modernization savings of approximately 20% to 25%, and operating expenditure savings of 15% to 20% from an onsite and offshore automation service model. The engagement also reported continuous improvement of 5% to 10%. On the new platform, server provisioning was reduced to 60 minutes, while on-demand storage provisioning took under 30 minutes. These are outcomes reported for this engagement, not guarantees for other environments.

For manufacturers planning an IT carve-out, the practical lesson is to manage separation and future-state design as one coordinated program. Establish visibility into inherited assets and access constraints early; map dependencies across business IT and process-control networks; sequence migrations around operational requirements and TSA deadlines; and include security, governance, change management, monitoring, and Day 2 support in the plan.

A successful carve-out is measured not only by whether systems are separated on time, but also by whether the independent organization can operate and evolve its environment afterward. HSC’s experience shows how a disciplined transition can pair continuity during separation with a more scalable infrastructure for the next stage of operations.

Access Official Technical PDF

About The Author