Port-Community System Separation Authority — Container Gateway

The mandate

The technology joint venture operating the port-community platform will dissolve after its shareholders failed to agree renewal terms. Vessel calls, manifests, gate appointments, customs status, payments and release events continue under a fourteen-month transition agreement, but identity, source code, keys, partner onboarding and operating knowledge remain shared. No port executive currently holds authority across separation and live maritime continuity.

The interim must start in Chennai within four weeks for fourteen months, spanning asset discovery, sovereign build, partner migration, two seasonal peaks and successor induction. A permanent search begins in month seven after the target operating model is proven. Eight weeks of overlap are reserved; the fixed term ends with the transition agreement even if optional partner features or archive rationalisation continue.

Handover requires critical services to run under port-controlled identity, keys, monitoring, code custody and support; all priority community members must complete migrated journeys; the former venture must lose privilege without operational interruption; and two peak exercises must pass. The successor will chair final exit certification and accept residual partner, legacy-message and archive obligations.

The interim may stop migration waves, set service and evidence thresholds, direct the sanctioned ₹360 crore separation and appoint temporary workstream leaders. Customs policy, physical port movement, permanent appointment, long-term partner commercial terms and spending above budget require authorised port or government approval. The seat cannot clear cargo, direct vessels or override statutory agencies.

Terminal automation, customs-system replacement and redesign of shipping-line commercial services are outside this assignment. The authority may require dependable interfaces and witnessed cutovers but does not own crane operations, border decisions or historic cleansing without legal, operational or migration need. Separation must retire joint-venture dependence without centralising decisions that belong to community members.

Why this seat is open

Joint-venture dissolution created a hard contractual clock around a platform supporting every major cargo and vessel journey. Existing teams either report to one shareholder or own only local operations. A temporary executive must arbitrate clean separation, preserve community trust and leave a permanent port leader with demonstrable control before shared access is revoked.

What you will own

• Establish an exit ledger covering code, data, message schemas, identities, keys, licences, infrastructure, support, archives and community obligations.
• Decide service migration waves using vessel and cargo consequence, statutory interface, recoverability, peak calendar and partner readiness.
• Define port-controlled administration, source custody, cyber monitoring, change governance and incident command across target environments.
• Direct end-to-end trials for vessel call, manifest, gate, payment, customs response and cargo release through partner outages.
• Verify removal of former-venture privileges, hidden support dependencies and unlicensed components through witnessed client operation.
• Govern separation investment against retired dependency, community adoption, peak resilience and internal operating capability.
• Transfer authority through two seasonal peaks, a revoked-access exercise and successor acceptance of partner and archive debt.

Candidate qualifications

• Held executive platform authority for a port community, airport, trade, logistics or comparably multi-party infrastructure ecosystem.
• Completed a joint-venture or provider separation spanning code, identity, keys, partner interfaces and operating knowledge.
• Governed vessel, cargo, customs and payment journeys without assuming statutory or physical operations authority.
• Directed partner migration where shipping lines, terminals, agents and agencies had different systems and cutover constraints.
• Proved privileged-access removal and service continuity under a non-negotiable contractual exit date.
• Handed permanent leadership client-controlled operations after peak exercises and transparent residual obligations.

Non-negotiables

• Available within four weeks for exclusive Chennai service, including port presence during cutovers and peak vessel operations.
• Has carried separation authority in a live multi-party logistics platform; generic IT carve-out leadership is insufficient.
• No undisclosed relationship with joint-venture shareholders, terminal operators, shipping platforms or replacement bidders.
• Will preserve customs, harbour-master, terminal and vessel authority throughout technology separation.

1. 49 words maximum. State your Chennai availability and one live infrastructure joint venture you separated without operational interruption.
2. 49 words maximum. Which hidden code, identity or support dependency is most likely to survive a port-platform asset inventory?
3. 49 words maximum. What evidence would you require before revoking the former operator’s privileged access?