Buying a Connected Used Crane: Handover Checks for Contractors, Dealers and Rental Fleets
Check fault support, resale commitments and hirer permissions before valuing connected services

Tower crane components pictured for context. Connected services must be confirmed for the actual serial number.
Contractors need fault-response readiness; dealers need defensible resale promises; rental fleets need controlled hirer access. Confirm digital-service entitlements and handover responsibilities before pricing a used crane's connected features.
To save a copy, select “Save as PDF” in your browser’s print dialog.
Start with the buyer's operating problem
OEM platforms increasingly combine machine data, documents and service workflows. In a used purchase, the useful question is whether that combination supports your job, resale or hire model. A gateway or dashboard alone does not establish who can use which functions after the transaction.
| Buyer | Pain | Evidence to request | Decision boundary |
|---|---|---|---|
| Builder / contractor | Faults leave scheduled lifts waiting | Named responder, remote scope, response window and on-site fallback | Confirm support before counting possible schedule benefits |
| Equipment dealer | Resale promises exceed the next owner's rights | Written eligibility for the serial, buyer and destination | Separate fitted hardware from unconfirmed digital entitlements |
| Rental fleet | Hirers retain access or see other customers' records | Permitted roles, access start/end process and data visibility | Confirm hire and site-change conditions; assume no automatic portability |
- SANY's 26 December 2023 migration notice S1 announced GCP/EVI retirement for 15 January 2024, with an India exception. Platform transitions and regional differences were already procurement issues at the beginning of this period.
- Zoomlion's 2024 interim report S2 records tower-crane intelligent command-centre technology among its digital applications. This indicates development, not availability on every exported used tower crane.
- Manitowoc's 27 January 2025 Potain CONNECT article S3 illustrates documentation, remote information and fleet-service workflows. Its use cases help identify questions; they do not quantify savings for your purchase.

Read OEM developments as procurement signals
My assessment is that OEM service integration is advancing, while resale handover remains uneven. Contractors need a fault-response route; dealers need defensible customer commitments; rental managers need repeatable user changes. These are reasons to investigate connectivity, not proof of adoption or savings.
There is also counterevidence to the idea that digital services are permanent. Tadano's current HELLO-NET page S4 states that its previous version closed on 31 August 2026. Treat platform lifecycle, consent and registration as live dependencies. Confidence is moderate in the procurement implication, but low in any universal resale-premium forecast.
Turn connectivity claims into quotation evidence
Identify the hardware
Know what is actually fitted
- Record the serial and options
- Do not infer service rights
Confirm the users
Match the business and destination
- Identify owner and permitted hirer roles
- Obtain applicable written terms
Assign the support
Plan beyond the first login
- Name fault and access contacts
- Define records and user changes
Manitowoc's publicly linked CONNECT terms S6 state that the existing owner's agreement and access end when the crane is sold. That is a specific reason to seek current written terms for the new buyer; it does not establish another OEM's policy or your activation price.
Liebherr's current mobile/crawler Performance page S5 separates suitable hardware, supported crane types, registration and a licence through a sales partner. Keep those layers distinct for any offered machine; do not transfer its conditions to another range.
Qualify project support, resale promises and hirer access; identify unconfirmed scope.
| Offer layer | Evidence to request | Business decision |
|---|---|---|
| Physical equipment | Serial-linked gateway, options and software/version record | Do not sell a hardware description as a software entitlement |
| Company and users | Buyer-company registration and permitted owner/hirer roles | Rental firms need approved user turnover, not a shared login |
| Digital entitlement | Functions, term, renewal/cancellation basis and destination eligibility | Dealers must identify unconfirmed access in their resale scope |
| History and records | Permitted exports, time coverage and gaps | Define which records may pass to a buyer or hirer |
| Service continuity | Named service partner, remote scope, escalation and offline support | Contractors must know who acts when remote help is insufficient |
Agree fault, access and user-handover responsibilities
- 1
Identify
Unit, buyer and intended use
- 2
Confirm
OEM service and user eligibility
- 3
Allocate
Fault, access and cost responsibilities
- 4
Handover
Approved accounts and records
- 5
Continue
Hire changes, sites and support
- 1. Identify the unit and use. Record serial, gateway, options, buyer entity, destination and contractor/resale/rental use.
- 2. Confirm eligibility. Obtain OEM or authorised-partner terms for the serial, country, functions and intended users; record missing answers.
- 3. Allocate responsibilities. Name first-fault, escalation, on-site and account contacts. Separate subscription, upgrade and training costs.
- 4. Complete authorised handover. Confirm buyer access against the project/resale deadline and the approved hirer start/end process. Do not pass seller passwords.
- 5. Preserve continuity. Obtain permitted history, document versions and offline support. Record required checks when the hirer, site or country changes.
Complete any separate OEM owner/contact update, but keep it distinct from a service agreement or licence. A dealer should pass the confirmed terms and open items to the next buyer; a rental firm should agree permitted data visibility without assuming every hirer can access fleet-wide records. Mechanical condition and local acceptance remain separate checks.
Three procurement scenarios for 2026–2028
These are conditional planning cases, not adoption forecasts.
| Scenario and condition | Early indicator | Buyer response |
|---|---|---|
| Base: platforms expand, but resale eligibility stays model- and region-specific | Different quotations require different registration or hardware checks | Confirm access before assigning a digital premium |
| Upside: dealers routinely provide serial-specific handover packages | Written feature lists, responsibilities and buyer-account milestones arrive with offers | Make documented digital readiness a tender comparison field |
| Downside: migrations, network limits or unresolved permissions delay access | Unclear renewal terms, closure notices or missing destination support | Budget separately for remediation; assess the confirmed offline service position |
Track readiness through sale and hire changes
- Before deposit: unresolved entitlements and destination support for the intended serial and business model.
- Before project start or resale: buyer-access readiness and the named fault-response route.
- At hire changes: permitted hirer access removal, record coverage and the next user's eligibility.
- After purchase: support performance against the agreed scope, renewals and platform-retirement notices.
Feature counts do not prove shorter waits or higher resale value. Recheck changes to buyer, hire arrangements, country or package.
Send a brief matched to your business

We are [contractor/dealer/rental firm] reviewing crane [model/serial] for [country/site/start or handover date]. Intended users are [buyer/hirer pattern]. Identify the gateway and software options. Obtain written confirmation of connected functions, user eligibility, destination restrictions, subscription terms and required changes. Name the fault-response, escalation and on-site support contacts. Define buyer/hirer access setup and removal, permitted history export and offline support. Assign each handover item, deadline and cost; separate confirmed scope from quoted extras and unresolved conditions.
Request a role-specific handover file
Compare used tower cranes or truck cranes. Contractors can send the site and start date; dealers the intended buyer and country; rental firms the hirer and site-change pattern. Send these details with the model and serial to request available information. Confirm digital-service eligibility with the relevant OEM or authorised partner.
Video explanation

POTAIN CONNECT - GROVE CONNECT
Publisher: Manitowoc Cranes
Official Manitowoc overview, originally published in 2022 and referenced by its January 2025 article. Product illustration only; not evidence of features or eligibility on a particular used crane.
Watch on YouTubeFrequently asked questions
Will remote service prevent a contractor's lifting delays?
It may help diagnosis, but no uptime guarantee follows from a modem. Request the named response route, supported information, escalation arrangements and what still needs on-site attendance before planning around shorter waits.
Can a dealer advertise software access as included with the crane?
Only describe the confirmed scope. Obtain applicable written terms for the serial, next buyer and destination, and disclose unresolved access. Hardware ownership and an owner-record update do not establish transferable software or service rights.
Can a rental fleet give successive hirers the same owner login?
Do not plan around shared credentials. Ask which owner and hirer roles are permitted, how access starts and ends, and what records each user may see. Use the approved process rather than assuming unlimited accounts or users.
Will history and service access follow every hirer or site change?
Do not assume so. Confirm permitted exports, time coverage, gaps and data restrictions, then ask which changes require renewed eligibility checks. Fleet records should not be treated as automatically available to every hirer.
What should we check if the cloud service becomes unavailable?
Obtain the responsible service team's documented offline capabilities, local diagnostics and support route. Do not infer permission to operate or bypass requirements from a lost connection; keep unresolved support costs separate when valuing connected features.
Sources and further reading
- Offline Notification of GCP and EVI2023-12-26
- 2024 Interim ReportUndated; checked 2026-10-19
- How to streamline, save, and succeed with Potain CONNECT2025-01-27
- HELLO-NET — US/CanadaUndated; checked 2026-10-19
- Performance — fleet data management for mobile and crawler cranesUndated; checked 2026-10-19
- GROVE CONNECT / POTAIN CONNECT — Terms and Conditions of UseUndated; checked 2026-10-19
