How to Choose a Control System Supplier for Aerial Work Platforms
A control system quote for an aerial work platform usually shows one price for the electrical cabinet or control board. What decides whether the project reaches volume production sits in the technical agreement: whether development scope, interface ownership, acceptance criteria and revision terms are written down. The control system drives the machine's movement logic, so a wrong supplier surfaces during prototyping and small-batch builds rather than at the quotation stage. This guide covers supplier tiers, agreement clauses, prototype validation and delivery terms.
1. Identify the Supplier Tier
| Supplier type | What it delivers | Responsibility it can carry | What to check |
|---|---|---|---|
| Whole-machine solution provider | Controller, display, remote handset, harness definition, machine control program | Machine movement logic and integration | Whether a control logic specification and fault code list are available |
| Electrical control supplier | Controller, drive module, some sensors | Control loop and drive matching | Whether the host communication protocol is open |
| Hydraulic and lower-control integrator | Valve blocks, joysticks, lower control boxes | Component performance and interface consistency | Who defines the interface to the upper control |
Tier decides where responsibility stops. Handing the machine control system to a solution provider means that party owns the logic for travel, steering, limits, load protection and fault diagnosis as a whole. A supplier that delivers only electrical components stops at the interface, and when integration fails the argument moves between program responsibility and hardware responsibility. Establish which category a supplier belongs to before comparing totals on quotes.
2. Four Clauses the Agreement Must Settle
- Development scope: controller hardware, control program, display interface and remote handset pairing, each assigned to supplier or machine builder
- Interfaces and protocols: CAN frame definitions, fault code list, upper and lower control communication, and whether second-party development is allowed
- Acceptance criteria: function list, environmental testing (temperature, vibration, ingress protection) and EMC test items with pass limits
- Ownership and IP: whether source or object code is transferred, revision fees, and the process and pricing for post-volume changes
Protocol openness is the clause most often skipped. A control system that exposes only a closed frame set forces the machine builder back to the supplier when connecting an in-house platform or building remote diagnostics, and by then a revision fee applies. Obtain the data point list and frame definitions at the agreement stage.
Remote management and condition data can sit alongside the control system rather than inside it. In JGY's approach, the CAN inclinometer JGYTS-1B and JGYTS-2B capture platform tilt and boom attitude, while the T-BOX handles CAN data backhaul and positioning through a standard interface. Control system selection decides whether machine movement is reliable; terminal selection decides whether operating data is available. Both are assessed separately, and the terminal checklist is covered in choosing a T-BOX supplier.
3. Validate Prototypes in Three Stages
| Stage | What is verified | Pass criteria | Responsible party |
|---|---|---|---|
| Bench integration | Signal mapping across controller, drive, sensors and display | Every function item passes, no spurious alarms | Supplier revises program, builder supports harness |
| Machine installation | Movement, limits and load protection on the real model | Continuous operation without runaway or false trips | Builder supports structure, supplier revises logic |
| Small batch | Consistency, assembly process, failure rate | Sampling tests pass, issues closed out | Supplier owns process and test fixtures |
Write the responsibility for each stage into the agreement. A program issue at bench stage is the supplier's to fix, structural interference during installation is resolved with builder support, and consistency at small batch is the supplier's process and tooling responsibility. Projects with vague responsibility often look fine during prototyping and only expose consistency problems at small batch, where rework is measured in months.
4. Pre-Quote Checklist
- Which tier the supplier occupies: whole-machine solution, electrical control or component integrator
- Whether the technical agreement covers development scope, interface definition, acceptance criteria and IP
- Whether CAN frames and the fault code list are deliverable, and whether second-party development is permitted
- Test items, pass criteria and cost bearer for environmental and EMC testing
- Lead times, prototype quantity and revision charges for bench, installation and small batch
- Volume MOQ, lead time, and supply lead time for controller chips and displays
- Post-volume change process, pricing and minimum change quantity
- After-sales response time, spare parts supply and on-site support scope
Assessing a control system supplier through the technical agreement and validation process is more reliable than reading marketing material. Machine builders planning remote management and condition data alongside the control system can review the aerial work platform IoT approach, and interface or terminal questions can be raised through contact.
FAQ
What categories of control system suppliers exist for aerial work platforms?
Three are common: whole-machine control solution providers that deliver controllers, displays, remote handsets and the machine control program; electrical control suppliers that deliver the controller and drive modules and own the control loop and drive matching; and hydraulic or lower-control component integrators that deliver valve blocks, joysticks and lower control boxes. The category defines where responsibility stops.
What belongs in a control system technical agreement?
Four blocks: development scope, covering whether controller hardware, program, display interface and remote handset pairing logic are supplied; interfaces and protocols, covering CAN frame definitions, fault code lists and whether second-party development is permitted; acceptance criteria, covering the function list, environmental tests and EMC requirements; and ownership, covering program rights, revision fees and the volume change process.
Why split prototype validation into three stages?
Bench integration verifies the signal mapping between controller, drive and sensors; machine installation verifies movement, limits and load protection on the real model; small batch verifies consistency and assembly process. Mixing the three makes it hard to tell whether a fault sits in software, structure or process, and responsibilities shift between parties.
What happens if the CAN interface stays closed?
The machine builder is blocked when connecting its own management platform or building remote diagnostics. A closed frame set exposes only the fields the supplier chose, so condition data, fault codes and remote management cannot be built, and neither devices nor data can move when changing platforms. Obtain the data point list and frame definitions during the agreement stage.