01■ Validate
The platform still earns its place
Is it stable, useful and aligned with the network plan?
Review criticality, service role, capacity headroom, known defects and planned retirement date.
● Coverage 24/7 or 8/5 by contract | P1 / P2 / P3London · Lisbon · Recife · Bogotá · Hanoi
● Lifecycle control for live networks
Keep the network. Take back the decision.
Independent support separates operational continuity from the manufacturer’s replacement timetable.
Decision 01OEM-led
Keep the manufacturer in the lead.
Use the OEM-led route when current software entitlement, proprietary code access or a mandated manufacturer relationship is central to the operational risk.
Decision signals
- Current feature roadmap is required
- Official software releases are critical
- Contract or regulation specifies OEM support
Independent support can complement this route, but it should not misrepresent proprietary rights it does not own.
Decision 02Control regained
Add an accountable support layer.
Use independent support when the platform remains operationally valuable but senior expertise, cross-vendor ownership, spares access or commercial flexibility has weakened.
Decision signals
- Stable platform still carries live service
- Multiple vendors share the incident path
- Renewal cost no longer matches operational demand
This route is valid only when its technical and commercial boundaries can be written into the contract.
Decision 03Migration justified
Replace when the engineering case wins.
Replace when capacity, security, architectural limits, energy use or supportability risk make continued operation less credible than a controlled migration.
Decision signals
- Risk cannot be contained by scope
- Required capability is unavailable
- Replacement economics are stronger
Independence is not an argument for keeping every platform. It protects the operator’s right to replace for the right reason and at the right time.
No route is assumed. The assessment can confirm, narrow or reject it.
The independence test
Four gates determine whether continued operation remains credible.
Independent support is only defensible when the operating boundary can be proven before contract. If a gate cannot be validated, the scope narrows or migration becomes the better decision.
02■ Validate
Senior expertise can be assigned
Can the required vendor and domain knowledge be mapped to the live environment?
Confirm platform family, software release, fault domains, escalation depth and delivery window.
03■ Validate
Hardware continuity has a route
Can failed parts be sourced, repaired or held as planned spares?
Validate compatibility, condition, warranty route, lead time and the risk of scarce components.
04■ Validate
The software boundary is explicit
Which rights and updates remain with the manufacturer?
Document licences, official software entitlement, proprietary dependencies and excluded work.
The control boundary
Separate the rights, the work and the decision.
A credible independent model does not pretend the OEM has no role. It makes each party’s authority explicit.
Manufacturer
The OEM retains
- Proprietary software ownership
- Official releases and entitlements
- Vendor-only engineering changes
- Product roadmap authority
Support layer
Independence adds
- Senior diagnosis and case ownership
- Cross-vendor incident coordination
- Configuration guidance and workarounds
- Hardware sourcing and spares planning
Operator
You keep control of
- Support OPEX and renewal strategy
- Migration CAPEX and timing
- Operational risk acceptance
- Long-term vendor strategy
Commercial logic
Price the risk you actually carry.
A support proposal should be built from network evidence and compared against both recurring support OPEX and the cost, risk and timing of migration CAPEX.
Input 01
Installed scope
Vendors, platform families, software releases, locations and criticality.
Input 02
Incident history
Case volume, severity mix, recurring fault patterns and escalation demand.
Input 03
Coverage window
24/7 or 8/5 by contract, response expectations and operational dependencies.
Input 04
Hardware exposure
Spares availability, repair routes, lead times and the impact of component scarcity.
Commercial output
A scoped support model with stated assumptions, exclusions and escalation paths.
The operating change
What changes when support is designed around the network.
The value is not simply a lower renewal price. It is a clearer operating boundary and fewer places for responsibility to disappear.
| OEM-led model | Independent support layer | ||
|---|---|---|---|
| Scope basis | Defined by each manufacturer’s commercial offer and product lifecycle | → | Defined by the assessed network, required service window and agreed exclusions |
| Case ownership | Separate process and escalation route for each manufacturer | → | One accountable case owner across the contracted multivendor scope |
| Senior access | Escalation depth follows the manufacturer’s support workflow | → | Senior L2/L3 ownership and domain-lead escalation defined in the service model |
| Lifecycle timing | Support availability follows the manufacturer’s published lifecycle | → | Coverage can extend a stable platform while replacement remains an operator decision |
| Hardware route | Availability follows the manufacturer’s active channel and inventory | → | New, refurbished, repair and planned-spares routes assessed by compatibility and risk |
This is a decision framework, not a universal claim. Final coverage depends on vendor, platform, software release, hardware state, access model, region and contracted SLA scope.
Due diligence
The objections should be answered before procurement.
01
What must remain with the OEM?
Software licences, official releases, proprietary code changes and vendor-only entitlements remain with the manufacturer where required. The independent scope is written around that boundary rather than obscuring it.
02
How is capability confirmed?
We assess the vendor, platform family, software release, technical domains, hardware condition, geography, access method and required service window before confirming coverage or response targets.
03
How is operational access controlled?
Access remains customer-controlled. No standing access is assumed unless agreed, and access actions, status updates and engineering decisions are captured in the incident record.
04
What if independent support is not the safe answer?
We narrow the scope, retain the OEM for the dependency, or recommend migration. Extending a platform without a credible expertise, hardware or software boundary is not lifecycle control; it is deferred risk.
Make the decision from evidence
Bring us the network before you bring us the renewal quote.
We will map what can be supported, what must remain with the manufacturer and where replacement is the stronger engineering decision.