Industrial-IoT Platform Separation Leader

The mandate

A divested equipment business shares device identity, telemetry ingestion, remote diagnostics, over-the-air delivery and customer administration with products remaining in the parent. The transaction agreement fixes a legal-close date and limits transition services, yet teams cannot identify which certificates, data streams and service workflows cross the perimeter. A temporary executive seat has been created because neither business’s platform leader can make neutral separation choices while protecting their future roadmap.

Across fourteen months, the interim leader will establish product and data boundaries, allocate shared capabilities, design transitional interfaces, migrate identities and tenants, and prove that both fleets remain observable and supportable. The separation must preserve remote-service safety, vulnerability response, customer entitlements, data rights, device update lineage and contractual uptime while preventing a transitional bridge from becoming indefinite mutual dependency.

Permanent platform leaders on both sides will be confirmed by month eight and jointly own the last separation rehearsal. Handover requires them to resolve a certificate-renewal conflict, chair a cross-company incident simulation and sign the closure evidence for one transition service. The interim leader transfers the boundary decisions, data lineage, customer exceptions, security materials, cost allocation and unresolved product obligations equally to both accountable organisations.

The seat may determine separation sequencing, stop a migration, approve bounded transitional patterns, direct funded teams, require customer-level evidence and recommend early closure of a transition service. It cannot amend transaction agreements, allocate intellectual property, approve customer contract changes, accept product-safety or cyber risk, revoke production device credentials, sign supplier novations or decide employee transfer matters.

The remit excludes leading the legal transaction, running normal fleet operations, acting as product security officer or selecting either company’s permanent cloud architecture. Completion requires independently operable fleets, separated privileged access, reconciled telemetry and entitlements, closed transition services and two leaders capable of managing remaining product evolution. The fixed term will not extend to compensate for decisions the steering committee postpones.

Why this seat is open

Shared-platform executives owe duties to future organisations with diverging commercial interests, making neutral boundary and investment choices structurally difficult. Legal close also arrives before a permanent operating model can mature. A fixed-term leader can use transaction authority to force evidence, protect both installed fleets, arbitrate transitional design and qualify the receiving leaders without becoming part of either side’s post-close hierarchy.

What you will own

• Map devices, identities, certificates, tenants, telemetry, remote commands, update channels, support tools and customer entitlements to the separation perimeter.
• Decide which shared capabilities duplicate, partition, remain temporarily served or expose bounded interfaces, with exit evidence for each choice.
• Govern migration of credentials, privileged access, data history and operational ownership without stranding installed equipment or responders.
• Define transition services with measurable inputs, capacity, control, incident duty, charging, change rights and firm closure conditions.
• Run rehearsals covering remote diagnosis, certificate rotation, vulnerability response, update rollback, data interruption and customer support.
• Present steering choices on schedule, cost, safety, security and mutual dependency with explicit consequences of delayed decisions.
• Transfer equivalent boundary records, exception inventories, economics and operational proof to permanent leaders on both sides.

Candidate qualifications

• Has separated a live industrial IoT or connected-product platform during a divestiture, carve-out or complex joint disentanglement.
• Understands device identity, certificates, telemetry, remote commands, over-the-air updates, entitlements and fleet support end to end.
• Has designed transition services whose exit conditions closed dependency rather than funding indefinite duplicate operations.
• Can protect installed-product safety and vulnerability response while corporate ownership, data rights and operating duties change.
• Has arbitrated shared-platform decisions neutrally between organisations with different roadmaps, economics and negotiating power.
• Demonstrates handover to leaders on both sides through exercised incident, security and transition-service closure decisions.

Non-negotiables

• Will follow the Chennai hybrid schedule, complete alternate-month product-site travel and attend legal-close command onsite.
• Must disclose relationships with either transaction party, industrial IoT suppliers, cloud providers, advisers and potential buyers.
• Brings connected-fleet separation experience; corporate IT carve-out or data-centre split alone is insufficient.
• Will not move production device credentials or customer data without approved custody, rollback and operational-support evidence.

1. 49 words maximum. Which shared device-identity dependency would you isolate before separating any customer tenant?
2. 49 words maximum. How would you prevent a platform transition service from becoming permanent mutual dependency?
3. 49 words maximum. What joint incident decision must both permanent leaders demonstrate before handover?