Confidential mandate

Mission-Critical Service-Parts Merger Architecture Director — Electronics

Planned Hiring / New

Mission-Critical Service-Parts Merger Architecture Director mandate in Tel Aviv, Israel · Mission-Critical Electronics Service Logistics

A Tel Aviv electronics group commissions a ten-month integration architecture after an acquisition created overlapping depots, incompatible service promises and disputed ownership of scarce mission-critical spares.

The mandate

The acquired and acquiring businesses both promise rapid field restoration, but define critical part, usable stock, repair ownership and customer entitlement differently. Duplicate depots conceal shortages because one ledger includes quarantined and cannibalised units while the other excludes stock reserved by contract. Early integration savings propose warehouse closure before export licences, reverse loops and engineering substitutions can support the surviving fulfilment path.

The deliverable is a Mission-Critical Service-Parts Merger Architecture specifying inventory truth, contract segmentation, reservation hierarchy, field-failure intake, part substitution, depot roles, repair routing, export-control gates, emergency transport, ownership and cost allocation. It must distinguish Day-One continuity from later network convergence and show where legal-entity or product approvals prevent common stock, process or provider use.

Fourteen service journeys are accepted as the first milestone in week three; two inventory reconciliations and the contract-promise baseline form a distinct second gate in week five. Day-One decisions are locked at week nine, and stock and reservation rules reach the combined team in week fifteen. Depot design is accepted in week nineteen and repair design in week twenty-two, before convergence waves close at week thirty. Two live recoveries provide the eighth proof point in week thirty-four and the remaining three close the ninth in week thirty-seven; a three-week close produces the tenth milestone—the accepted architecture, closure gates and implementation backlog.

Acceptance requires the integrated team to resolve an unseen customer outage involving a scarce part shown differently in both ledgers, a denied export route, an incomplete repair record and two contractual priority claims. Teams must identify lawful usable stock, choose and evidence the service decision, recover the failed unit and allocate cost without consultant interpretation or hidden degradation of either promise.

The client will provide transaction-level inventory, installed-base criticality, service contracts, entitlement rules, parts supersession, repair histories, export-control classifications, quality states, depot costs, legal-entity constraints and empowered regional owners. Exclusions include ERP consolidation, product engineering, export-control opinion, contract amendment, customer negotiation, tax restructuring, depot closure execution, vendor selection and command of live service incidents.

Why this is external work

Each legacy team can defend its own service model and integration finance can quantify apparent duplication, yet neither is neutral on which depot, definition or inventory survives. An external service-parts operator can design evidence-led convergence while preserving engineering, trade-control, customer and executive decision rights.

What you will own

  • Trace fourteen field-service journeys from failure identification through entitlement, reservation, pick, export, delivery, swap, return, repair and usable-stock reinstatement.
  • Reconcile stock by serial, condition, legal owner, customer reservation, location, export eligibility, supersession and verified physical availability.
  • Define priority logic for safety, installed-base consequence, contractual entitlement, restoration clock, alternative repair and scarce-parts fairness.
  • Separate Day-One continuity controls from depot consolidation, inventory pooling, provider harmonisation and later systems convergence decisions.
  • Design reverse loops that preserve failed-unit custody, warranty evidence, repair disposition, core value and replacement-stock accountability.
  • Rehearse five compound outages involving ledger conflict, export denial, depot loss, substitution dispute and simultaneous priority customers.
  • Deliver the architecture, inventory truth model, decision matrix, integration waves, trial evidence and accepted closure-gate backlog.

Candidate qualifications

  • Designed or led post-merger integration of global service-parts networks supporting mission-critical electronics or capital equipment.
  • Governed serialised inventory, reservation, repair loops, substitution and emergency fulfilment across depots and legal entities.
  • Distinguished accounting stock from physically usable, quality-released, export-eligible and contractually available inventory.
  • Balanced depot synergy with service continuity, installed-base risk and country-level trade or product constraints.
  • Facilitated integration choices between legacy executives without becoming advocate for either organisation, platform or logistics provider.
  • Transferred merger architecture through client-led outage trials involving scarce stock, denied routes and competing customer entitlements.

Non-negotiables

  • Can lead ten integration laboratories and five physical recovery trials within ten months.
  • Direct electronics or capital-equipment service-parts integration experience is required; generic merger programme management is insufficient.
  • Will disclose both legacy firms, logistics providers, repair depots, technology vendors, advisers and investors.
  • Will not give export opinion, approve engineering substitutions, amend contracts, choose vendors or command live customer incidents.
  1. 49 words maximum. Describe a merger where inventory appeared duplicate but was not operationally interchangeable.
  2. 49 words maximum. How would you protect Day-One service while testing a depot-consolidation thesis?
  3. 49 words maximum. Which contract, inventory, repair and export-control evidence must the client provide by week five?

This mandate is confidential. The client is named only under a mutual NDA, and your own record is never listed, sold or shown to a company under your name until you release it for this specific mandate.