Vehicle Standard (Australian Design Rule 35/04 – Commercial Vehicle Brake Systems) 2013

The standard organises around a small number of core concepts and technical metrics that govern both design and test work.

• Service Brake System and single control requirement. Every vehicle must have a service brake system operable on all road wheels through a single control reachable from the normal driving position (clause 4.1.1). Each Service Brake System must include wear compensation devices (clause 4.1.4). Where antilock braking is fitted, Appendix 1 applies (clause 4.1.5).

• Visible and audible indicators. Service brake failures must be signalled by one or more visible indicators meeting clause 4.2; a single Brake Power Unit must also have an audible indicator when the visible indicator operates (clause 4.1.11). Visible indicator design is prescriptive: text or ISO symbol, minimum letter heights (3 mm or 10 mm for mechanical devices), colours (red for lamp or labelling), and precise instrument-panel location boundaries (clause 4.2.10-4.2.12).

• Parking Brake System. A parking brake retained by mechanical means with frictional braking is required (clause 4.3). The parking brake control must be separate from the service brake control, must be able to be retained in the “brake on” position and designed to minimise inadvertent release (clause 4.3.2). For vehicles towing trailers with positive-pressure air systems, the parking brake operation must reduce the trailer supply line pressure below 35 kPa (clause 4.3.5-4.3.7).

• Secondary Brake System. A separate secondary brake system is mandated (clause 4.5.1). If hydraulic service brakes are used, they must be split service systems (clause 4.5.2). Secondary brakes must be operable by a separate control and be capable of application and release from the driver’s normal position (clause 4.5.4-4.5.5). Spring brake and stored-energy requirements are detailed (clauses 4.5.6 and 4.7).

• Stored energy and Brake Power Units. Where stored energy (compressed air, vacuum, hydraulic accumulators) or Brake Power Units are used, the ADR specifies sizing, replenishment and monitoring requirements: minimum combined volume relating to service brake chamber displacement (clause 4.7.2), recharge times relative to capacity (clause 4.7.3-4.7.4), gauges visible to the driver accurate to within 7% (clause 4.7.5.1) and pressure test connections (clause 4.7.5.2-.3).

• Compatibility with trailers and towing operation. The ADR sets performance envelopes for vehicles intended to tow trailers that use positive-pressure air, including the requirement that ‘Established Retardation Coefficients’ measured per part 6/7 fall within boundaries shown in Figures 1 and 2 (clause 4.1.9) and that special tests (Service Brake Compatibility Test clause 7.13) be performed. For vehicles with rated towing capacity > 4.5 t, the manufacturer must either certify operation of trailer brakes using positive-pressure air per clause 4.1.9 or supply sufficient data to allow the Administrator to model the service brake response (clause 4.1.10).

• Antilock Braking Systems (ABS) and ESC. Vehicles in certain categories must have ABS per Appendix 1; vehicles of categories MB or MC must be equipped with ESC that meets Appendix 2 (clause 4.1.1.1 and 4.1.5). Appendix 1 prescribes wheel-lock behaviour tests, diagnostic lights and trailer electrical connection pinouts for ABS (Appendix 1, clauses 1.1-1.3). Appendix 2 defines ESC operational and performance tests, the Sine-with-Dwell test, required tell-tales and the option to use validated simulation tools for ESC demonstration (Appendix 2, paragraphs 2-5 and Attachments 1-3).

• Test regime and performance metrics. Compliance is shown through a suite of tests in Table 1, including Service Brake effectiveness (lightly laden and laden), secondary brake tests, partial failure tests, fade and fade-effectiveness checks, parking brake and actuation time tests. The ADR defines constants and formulae for average deceleration (Table 3 and clause 6.8), and prescribes specific data processing (Appendix 2, paragraph 5.11) for ESC tests.

• International equivalence. The ADR allows UNECE Regulation No.13 (R13) and GTR No.8 to be treated as equivalent provided stated conditions and exemptions are met (clause 8.1-8.3). Equivalence is conditional and includes specific exclusions and additional requirements (for example, ESC requirements for certain vehicles, R13 annex compliance during conformity of production, and exemptions listed at 8.3.1).

These concepts function as both design prescriptions and testables. They create compliance paths based on either direct testing to the ADR’s parts 6-7 and appendices or through accepted international approvals, validated simulations, and ‘Approved’ calculations where explicitly permitted (clauses 4.1.9.4, 4.1.10.3, Appendix 2 Attachment 1-3).

Primary economic actors affected are vehicle manufacturers (OEMs), component suppliers (brake hardware, sensors, valves, connectors), technical services and laboratories performing type approval testing, and regulatory administrators who accept compliance evidence.

• Manufacturers: The ADR places primary obligations on the vehicle Manufacturer to design and supply vehicles that meet the technical and test requirements (see clauses 4.1.10, 4.6.2-4.6.4, 3.1-3.3 referencing ADR definitions). Manufacturers must provide documentation (Appendix 2 paragraphs 3.7.1-3.7.4) for ESC-equipped vehicles, may have to supply the Administrator with modeling data for vehicles with rated towing capacity > 4.5 tonnes (clause 4.1.10.2), and must ensure labelling, fluid specifications and component standards (clause 4.6.4; clause 4.1.6).

• Component suppliers and system integrators: Brake power units, valves, sensors, couplings and electrical connectors must meet designated standards (clause 4.1.6; clause 4.1.8; Appendix 1 clause 1.3.2). Examples: brake line couplings must comply with AS 4945-2000 (clause 4.1.8); connectors for ABS/ESC trailer supply must conform to DIN 72570 or ISO/DIN 7638 variants and pin ratings are specified (Appendix 1 clause 1.3.1-1.3.2 and Appendix 1 - Annex 1).

• Test houses and technical services: The ADR relies on measured performance (Parts 6-7) and permits validated simulations for ESC (Appendix 2 Attachments 1-3). Accredited testing facilities must be able to perform complex dynamic tests (Sine-with-Dwell), brake fade regimes, service brake compatibility tests and data processing per Appendix 2 paragraph 5.11. The ADR requires specific instrumentation checks, filtering and zeroing procedures for ESC data processing.

• Administrators and approval authorities: The ADR refers to an ‘Administrator’ who accepts certification and modeling data (clause 4.1.10). Administrators (or authorised technical services) will adjudicate whether ‘Approved’ calculations are acceptable (4.1.9.4, 4.1.10.3) and whether equivalence to international standards (clause 8) is accepted. The ADR does not itself contain enforcement or penalties (see “Penalties and enforcement” below), so operational enforcement depends on enabling legislation and administrative practice.

• Fleet operators and dealers: Indirectly affected through the need to source vehicles that have passed ADR compliance. Time-to-market and supply-chain cost changes borne by manufacturers may translate to price impacts on purchase or retrofit costs; the ADR’s staged applicability (new model vs all vehicles, clauses 2.1-2.3) forces manufacturers to prioritise model updates.

• Standards bodies and suppliers of test equipment: The ADR references multiple international and Australian standards (ISO, UNECE, AS, SAE, BS, JIS, DIN), leading to increased demand for compliant parts and conformity assessment (clause 4.1.6; clause 8 references UNECE regulations).

Notable affected vehicle categories. The applicability table and clauses identify which ADR category codes are covered and the dates from which particular categories are captured (clause 2 and the Applicability Table). Specific categories referenced for ABS/ESC requirements include MD4, ME, NB, NC (ABS must be fitted to MD4, ME, NB or NC with not more than four axles , clause 4.1.5.1) and MB/MC (ESC required , clause 4.1.1.1). The ADR clarifies that vehicles certified to ADR 35/05 or a later version need not comply with this ADR (clause 2.8).

Who pays and who decides. Manufacturers fund development, testing, simulation validation and documentation. The Administrator (and/or delegated technical services) decides acceptance of certificates, approved calculations and simulation results (clauses 4.1.9.4, 4.1.10.3, Appendix 2 Attachment 1-3). The ADR also allows reliance on UNECE approvals for equivalence, which can limit duplicated test expenditure (clause 8.1-8.3).

This section summarises the principal obligations the ADR places on manufacturers and the rights or options it grants them, referencing the clauses that create those duties or options.

Duties (manufacturer-facing)

• Equip the vehicle with a service brake system operable on all road wheels via a single control reachable from the normal driving position (clause 4.1.1). For MB/MC vehicles, fit an ESC that meets Appendix 2 (clause 4.1.1.1).

• Provide service brake failure visible indicators that meet clause 4.2 conditions and, where a single Brake Power Unit is used, an audible indicator that operates whenever the visible indicator does (clauses 4.1.2, 4.1.11, 4.2).

• Prevent cross-actuation when separate methods of actuation are provided, and include means to compensate for wear in service brake systems (clauses 4.1.3-4.1.4).

• Where fitted, ensure Antilock Systems meet Appendix 1, and comply with additional requirements for MD4, ME, NB or NC categories (clauses 4.1.5-4.1.5.2).

• Fit brake line couplings that are polarized and comply with AS 4945-2000 (clause 4.1.8).

• For vehicles designed to tow trailers using positive air pressure, ensure service brake established retardation coefficients lie within the boundaries described at clause 4.1.9 (and Figures 1 and 2), and where towing capacity exceeds 4.5 tonnes either provide certification for trailer brakes per clause 4.1.9 or supply sufficient test data to the Administrator for modelling (clause 4.1.10). Approved calculations may be accepted for variants (4.1.9.4, 4.1.10.3).

• Provide reservoirs, condensate drains and fluid labelling as set out: condensate drain valves at lowest points (4.1.12), reservoir capacities sized to permit displacement to fully-worn fully-applied positions (4.6.2-4.6.3), permanent fluid-type and “Clean filler cap” warning in letters not less than 3 mm (4.6.4).

• Fit and size Stored Energy devices and Brake Power Units according to clauses 4.7.2-4.7.5 (volumetric multiples, recharge time, gauges and test connections).

• Equip vehicles with a Parking Brake System operating by mechanical retention and conforming to design details (clause 4.3 and 4.4; parking brake indicator lamp labelling, clause 4.4.1-4.4.6).

• Provide a Secondary Brake System with defined functionality and stored-energy capabilities if spring brakes are used (clause 4.5).

• Meet the performance tests in Table 1 and the test conditions of Parts 6-7 (clause 5.1).

• For ESC-equipped vehicles, supply system diagram, operational description, logic diagram and understeer information to confirm the ESC meets Appendix 2 (Appendix 2, paragraph 3.7).

Rights, options and permissible pathways

• Equivalence route: The manufacturer may rely on UNECE Regulation No.13 (R13) or GTR No.8 where those international instruments’ technical requirements are deemed equivalent under Part 8, subject to listed conditions and exemptions (clause 8.1-8.3).

• Approved calculations and simulation: For vehicle variants where effects on braking are demonstrable by test on components or sub-assemblies, 'Approved' calculations may be used instead of full vehicle testing (clauses 4.1.9.4 and 4.1.10.3). Appendix 2 permits a validated computer simulation to substitute for physical ESC testing, provided the simulation is validated and documented (Appendix 2 Attachments 1-3).

• Manual disconnection of ABS: On NB and NC vehicles a manual device may be fitted to disconnect/change ABS control mode; the ADR prescribes conditions for this device (optical warning, auto-reconnect on ignition, driver handbook warning, and performance when disconnected must still meet clause 7.13 requirements) (clause 4.1.5.2).

• Optional forms of indicators and combined lamps: Visible indicators may be lamps or mechanical signalling devices, may be combined with parking brake indicators, and may be common with other service failure lamps provided the labelling and location requirements are met (clauses 4.2.9-4.2.12, 4.4.1-4.4.5).

Who decides acceptance and what constitutes compliance

• Administrator and technical services: The ADR refers to an Administrator as the recipient of certification data and the entity to which manufacturers may present modelling or test data (clauses 4.1.10 and 4.1.10.2). ‘Approved’ calculations and tests are to be accepted by the approving authority (clauses 4.1.9.4, 4.1.10.3).

• Performance demonstrated by test: Compliance is principally determined by whether the vehicle meets the test performance requirements in Table 1 under the general (Part 6) and particular (Part 7) conditions. Where ESC is involved, Appendix 2 sets out specific post-processing and acceptance criteria (appendix 2 paragraphs 3.1-3.4 and 5.11).

Compliance outputs required from manufacturers therefore include design documentation, test records, simulation validation reports (if simulation used), and where appropriate electrical connection conformity for trailer ABS/ESC (Appendix 1).

The text of this ADR does not itself specify criminal, civil or administrative penalties or an enforcement mechanism expressed in penalty terms. The instrument is framed as a technical standard: it sets mandatory technical requirements, tests and documentation obligations but does not include express sanctions or enforcement procedures within its clauses.

What the ADR does include that bears on enforcement:

• References to Administrator acceptance. The ADR contemplates administrative approval, certification, modelling evidence and acceptance of ‘Approved’ calculations (clauses 4.1.9.4; 4.1.10.2-.3). This implies an administrative decision-making role for an approving authority, but the ADR does not specify the statutory basis or sanctions for non-compliance.

• Test-based compliance gate. Compliance is determined by meeting the test results set out in Table 1 under the general (Part 6) and particular (Part 7) test conditions (clause 5.1). Practically, this establishes a technical enforcement gate,vehicles not meeting the tests cannot, by definition of the ADR, be certified to it without alternative accepted evidence (equivalence, approved calculations, validated simulations).

• Documentation and certification requirements. For ESC the ADR requires manufacturers to furnish system diagrams, logic descriptions and understeer information as part of the confirmation that ESC meets the Appendix (Appendix 2, paragraph 3.7). Failure to provide the required documentation would impede acceptance.

What the ADR does not cover and therefore requires the reader to check elsewhere:

• The ADR is silent on who may inspect, revoke approval, impose fines, suspend registration or order recalls. Those powers are typically vested in enabling legislation and administrative instruments outside the ADR itself. The ADR’s text therefore must be read in conjunction with the Motor Vehicle Standards Act and relevant administrative regulations and enforcement policies to determine statutory penalties and enforcement processes. The ADR itself does not create or state specific sanctions, infringement regimes or court processes.

Practical consequence for manufacturers and legal advisors:

• Compliance with the ADR is a technical precondition for regulatory approval and market entry in Australia; however the consequences of non-compliance (civil or criminal penalties, deregistration, recall obligations) are not set out in the ADR text and must be identified in the relevant enabling or enforcement instruments. The ADR therefore allocates the technical standard-setting function to the ADR while leaving enforcement mechanisms to other instruments and agencies.

The ADR cross-references and relies on both other ADRs and international standards. It does not operate in isolation; interplay with other regulatory instruments and referenced standards shapes compliance options and technical choices.

Cross-reference to other ADRs and categories

• Definitions and categories. The ADR directs users to Vehicle Standard (Australian Design Rule Definitions and Vehicle Categories) 2005 for vehicle categories and definitions (clause 3.1-3.2). It also references other ADRs as acceptable prior rules (clause 2.4, 2.5) and states that vehicles certified to ADR 35/05 or later need not comply with this rule (clause 2.8).

• Specific ADR interactions. The ADR accepts earlier ADRs for specific vehicle categories (for example, vehicles of category MB, MC or NA complying with ADR 31/... will be accepted as complying with this standard; clause 2.4). It says LEG vehicles with single foot pedals must comply with this standard (clause 2.5) while other LEG vehicles must comply with ADR 33/… (clause 2.5).

Interaction with international regulatory texts and standards

• UNECE Regulation No. 13 equivalence. Clause 8.1 deems the technical requirements of UNECE R13 (braking) to be equivalent for categories M, N and O for specified series of amendments, subject to some additional requirements (e.g. clause 7.12.6.2 for road trains and the requirement for ABS on specified categories). Clause 8.1.2 further allows certain annexes to be satisfied via conformity of production.

• ESC equivalence. Clause 8.2 and 8.3 provide equivalence pathways for ESC using UNECE R13 Annex 21 and GTR No.8, with explicit exemptions listed at 8.3.1. Those exemptions identify specific paragraphs of the international texts that are not adopted verbatim under the ADR.

• International standards and component standards. Clause 4.1.6 requires components and devices in the Brake System to meet at least one appropriate recognized international, national or association standard where such standards exist (examples listed: SA, SAE, BS, JIS, DIN, ISO standards and UNECE standards). The ADR therefore imports the technical substance of those standards without reprinting them.

Administrative and approval interfaces

• Administrator role. Where the ADR allows modelling rather than direct brake certification (clause 4.1.10), it requires the Manufacturer to “supply to the ‘Administrator’ sufficient data to allow the vehicle’s ‘Service Brake System’ to be modelled.” The ADR therefore presumes an existing administrative process and a technical capacity within the Administrator to accept modelling data.

• Technical services. Appendix 2 Attachments refer to validation and verification work that may be performed by “technical services” or “the Technical Service conducting the test” (Appendix 2 Attachments 2 and 3). This points to an interface between manufacturers and accredited technical bodies for type-approval testing.

What the ADR does not do but implies

• It does not repeal or replace enabling legislation or registration laws. The ADR sets technical requirements for vehicle approval; registration, enforcement, penalties, import approvals and recall powers remain a function of separate statutory instruments and administrative rules, which must be consulted to understand the full legal effect of non-compliance.

• It leaves conformity-of-production and ongoing surveillance to be handled under other instruments. Clause 8.1.2 mentions conformity of production as a basis for meeting certain UNECE annexes, indicating that ongoing production conformity is part of the broader compliance architecture though the ADR does not itself prescribe those surveillance mechanisms.

Practical interaction risks and compliance planning

• Manufacturers relying on equivalence must confirm the ADR’s specific exemptions and additional requirements (clauses 8.1-8.3). For example, an R13 approval that does not address a clause the ADR requires (e.g. Appendix 1 trailer pin assignments or the trailer parking pressure behaviour) will not, on its own, satisfy the ADR.

• Where the ADR requires Administrator acceptance of modelling (clause 4.1.10), manufacturers must plan the data package and ensure it meets the Administrator’s expectations; the ADR does not specify the precise data format or administrative procedure.

• The ADR’s references to multiple international standards imply a supply-chain coordination duty: components must meet a recognized standard (clause 4.1.6), connectors must meet AS or ISO pinouts (Appendix 1), and tubing/pressure test connections must meet ISO 3583 (clause 4.7.5.2-.3). Manufacturers must work across those standards and the ADR to secure conformance.

In short, the ADR is a technical node in a wider regulatory network that includes other ADRs, UNECE regulations, ISO standards and national electrical/mechanical standards. A complete compliance strategy must map the instrument’s cross-references and the Administrator’s procedural expectations.

Document-level metadata and changes are recorded in the ADR itself. The compilation and amending instruments are set out at the end of the text.

• Instruments and registration. The original ADR was registered as Vehicle Standard (Australian Design Rule 35/04 - Commercial Vehicle Brake Systems) 2013 on 13/08/2013 and commenced on 14/08/2013 (Table of Instruments). Amendment 1 to the ADR was registered on 16/09/2014 and commenced 17/09/2014 (Table of Instruments). The compilation date shown at the head is 1 (up to and including ADR 35/04 Amendment 1) with Prepared Date 19/09/2014.

• Clauses affected. The Table of Amendments shows clause 2.8 was added or inserted by Amendment 1 (Table of Amendments, clause affected 2.8 , “ad” means added or inserted). Clause 2.8 declares that vehicles certified to ADR 35/05 or a later version need not comply with this rule.

• Compilation note. The final Notes indicate the compilation includes the instruments set out in the Table of Instruments and provides a Table of Amendments recording clauses amended, inserted or deleted.

Practical reading of the amendment history

• The principal substantive change recorded in the Table of Amendments is the insertion of clause 2.8. That clause provides an explicit grandfathering or equivalence for vehicles certified to ADR 35/05 or later, thereby creating a clear transition/relief for manufacturers or models already certified under a later ADR. This is a narrow but operationally important amendment because it affects which technical standard applies to particular model variants at particular times.

• Users should pay attention to the commencement dates in clauses 2.1-2.3, the dates in the applicability table for specific categories, and the added clause 2.8. Because ADRs are often amended by later instruments, readers must check the consolidated ADR registry and the Administrator’s list of current ADR versions and amendments before relying on compliance statements.

• The ADR’s Notes explicitly state the Table of Amendments provides the history of clauses amended, inserted or deleted. For any unresolved questions about historical versions or validity for particular models, the official legislative register or the Administrator should be consulted.

What the ADR does not include in its amendment table

• The table does not list any other substantive changes, which suggests that Amendment 1 was limited in scope. It does not, for example, record any post-2014 changes in this text. Users should confirm in official consolidated instrument registers whether later amendments or superseding ADRs exist, particularly as ADR 35/04 interacts closely with ADR 35/05 and subsequent revisions.

The ADR text itself does not contain any case citations, litigation references, or judicial interpretations. It names no court decisions and does not reference administrative decisions or appeals. The only legal-historical material in the ADR is the Table of Instruments and Table of Amendments recording the registration and commencement dates for the instrument and its single Amendment 1.

Practical implications for legal research

• There is no litigation history recorded within the instrument. Any litigation or administrative appeals arising from application or enforcement of this ADR must be sought from external sources: judicial databases, tribunal records, administrative appeal logs, or agency records concerning decisions by the Administrator or by state/territory registration authorities.

• Legal practitioners advising manufacturers, importers, technical services or fleets should not assume enforcement practice or judicial interpretation from the ADR text alone. Instead, they must consult administrative guidance from the national Administrator, records of technical service approvals, and any tribunal or court decisions that interpret how the ADR is applied in practice.

• Because the ADR references conformity routes (UNECE R13, GTR No.8) and Administrator acceptance of modelling and ‘Approved’ calculations, real-world disputes are most likely to arise around the adequacy of submitted technical evidence and the Administrator’s acceptance or rejection of modelling/simulation/approved calculations. Those disputes will be governed by the administrative appeal avenues in the enabling statutes or direct judicial review procedures, none of which are described in the ADR text.

In short, the ADR provides no litigation history; to investigate cases that applied, interpreted or challenged these technical requirements the researcher must consult external legal and administrative decision databases.

This ADR is technical and detailed; certain provisions are easy to misread or to overlook in compliance planning. The following points are concrete “watch-outs” that arise directly from the text and that can have practical compliance consequences.

1. New-model vs all-vehicle dates and “new model” definition. Clauses 2.1-2.3 set a two-step roll-out: new models from 1 July 2014 and all vehicles from 1 January 2015. The ADR defines “new model” in clause 2.3 as a vehicle model first produced with a ‘Date of manufacture’ on or after the agreed date. Manufacturers must therefore be careful how they record model manufacture dates and to which models the “new model” date applies.

2. Vehicles certified to ADR 35/05 need not comply with this rule. Clause 2.8 (inserted by Amendment 1) exempts vehicles certified to ADR 35/05 or later. This can lead to model-by-model variability in applicable standards; a vehicle certified under a later ADR need not be altered to meet 35/04. Verify which ADR version a particular model was certified to.

3. “Does not apply to combinations of drawing vehicle and trailer” (clause 2.6) versus extensive towing requirements elsewhere. Clause 2.6 states the standard does not apply to combinations, but many clauses (4.1.9, 4.3.5, 4.5.8, 7.13, Appendix 1) set out requirements for vehicles equipped to tow trailers using air at positive pressure. The practical implication: while the ADR does not apply to the combination as a single “vehicle”, it imposes design and test obligations on individual towing vehicles when they are intended to tow trailers. Manufacturers must not misread clause 2.6 to assume towing-related obligations are absent.

4. Manual ABS disconnection permitted under strict conditions. Clause 4.1.5.2 allows a manual device to disconnect/change ABS mode on NB and NC vehicles, but requires that the vehicle still satisfy relevant partial-failure test requirements (clause 4.1.5.2.1), must display optical warning when ABS is disconnected (4.1.5.2.2), must automatically reconnect under ignition or drive mode conditions (4.1.5.2.3), and the handbook should warn drivers (4.1.5.2.4). In other words, limited flexibility is tightly constrained; failure to observe the auto-reconnect or warning rules will breach the ADR.

5. Several precise pressure thresholds are critical. The ADR uses exact figures for trailer supply line behaviour and indicator activation: e.g. supply line pressure thresholds of 450 kPa for visible indicator activation (4.2.4), 35 kPa to detect trailer absence and avoid false indicators (4.2.4.2), and 35 kPa/350 kPa/420 kPa thresholds for other protections (for example 4.5.8.1-4.5.8.2). Component suppliers, test houses and engineers must implement instrumentation and control logic that meet those exact thresholds.

6. Labels and instrument location are prescriptive. The text prescribes exact minimum sizes for labels (3 mm letters for lamps, 10 mm for mechanical devices), colours and the geometric space within which the failure lamp must be situated (clause 4.2.10-4.2.12). Non-conforming labelling or location will be non-compliant even if the braking performance is satisfactory.

7. ESC simulation and validation burdens. Appendix 2 allows use of validated computer simulation to demonstrate ESC performance (Attachment 1), but requires simulator validation against actual vehicle tests and retention of simulator test reports (Attachment 2-3). Validation is exacting (Appendix 2 Attachment 2 paragraphs 2.1-2.3) and requires recording specific motion variables. Relying on simulation requires explicit validation activity and documentation.

8. Component standards and connector pinouts are exact. The ADR requires brake line couplings to comply with AS 4945-2000 (clause 4.1.8) and gives specific connector pin current ratings and wiring functions for ABS/ESC trailer electrical connectors (Appendix 1 clause 1.3.2). Using incorrect connectors or wiring will create a compliance gap.

9. Reservoir sizing linked to fully-worn pad/lining. Reservoir capacity must at minimum accommodate fluid displacement from fully retracted to fully-worn fully-applied positions, with detailed criteria for “fully-worn” depending on bonded linings and nominal thickness (clause 4.6.2 and the lining table). Designers must adopt minimum reservoir volumes based on worst-case lining wear, not on typical service intervals.

10. “Approved” calculations and partial testing allowed only where effects of changes are known. Clauses 4.1.9.4 and 4.1.10.3 permit approved calculations for variants where test evidence on a complete vehicle, component or sub-assembly shows the effects on braking. However, the ADR requires those calculations to be ‘Approved’,the text does not define the approval process, so pre-agreement with the Administrator or technical service is advisable.

11. Test environment constraints. Part 6 contains multiple conditions (ambient temperature 0-40°C, tyre specifications, gradient limitations, wind limits in 6.6, track surface gradient allowances in 6.5) that can cause otherwise successful brakes to fail a given test if the test venue or procedures are inadequate. Testing houses must control environmental parameters tightly.

12. Parking brake force and gradient test specifics. The Parking Brake Test requires an 18% gradient and specifies maximum actuation forces and timings (clause 7.11.1-7.11.3). It allows for a limited number of re-applications in order to hold the vehicle. If a parking brake design cannot achieve the specified single-application force, the ADR permits a series of applications to reach the required force, but this must be embedded in test procedures.

Each of these “gotchas” is drawn from the ADR’s text and can produce non-obvious non-compliance risks if not specifically addressed in design, supplier selection, or testing plans.

This section provides a practical, clause-referenced checklist for manufacturers and technical advisers preparing for ADR 35/04 compliance testing and certification.

1. Confirm applicability and applicable ADR version. Determine whether the vehicle is a “new model” (clause 2.3) and whether it is captured by the ADR’s staged dates (clause 2.1-2.2). Check whether the model has been certified to ADR 35/05 or later, in which case clause 2.8 exempts it from 35/04.

2. Map vehicle category to obligations. Consult the Applicability Table and clauses 2.4-2.7 to identify category-specific obligations (for example MB/MC require ESC per clause 4.1.1.1; MD4/ME/NB/NC have ABS requirements in Appendix 1 and Appendix 1-Annex 1).

3. Design the Service Brake System to the single-control, wear-compensation and fail-indicator requirements. Ensure the service brake acts on all road wheels via a single control (clause 4.1.1), incorporate wear compensation devices and confirm visible indicators meeting 4.2 will actuate under the specified pressure or fluid-loss conditions (4.2.1-4.2.4). If the vehicle uses a single Brake Power Unit, add an audible indicator (4.1.11).

4. Configure Parking and Secondary Brake Systems to ADR prescriptions. Install a parking brake retained mechanically, separate from the service brake control, and capable of meeting the parking test (clause 4.3 and 7.11). Ensure secondary brake design (split system, spring brakes, stored energy sizing) satisfies clauses 4.5 and 4.7 (including stored-energy capacity tests in 4.5.6 and 4.7.6).

5. Satisfy hydraulic and reservoir sizing rules. For hydraulic systems, size reservoirs per clause 4.6.2 and ensure any master-cylinder reservoir remains above minimum designated levels where Condition B applies (4.2.2). Place fluid-type labelling and “Clean filler cap” warnings as required (4.6.4).

6. Install ABS/ESC and meet appendices where required. If an Antilock System is fitted, verify the vehicle meets Appendix 1 tests (wheel-lock behaviour, lamp functions, trailer electrical pinouts and lamp signals). For MB/MC vehicles and others mandated in the Applicability Table, fit ESC and prepare the documentation required by Appendix 2 paragraph 3.7 (system diagram, operational description, logic diagram, understeer information) and, if using simulation, validate the simulation tool per Appendix 2 Attachment 2.

7. Prepare trailer-towing interfaces if relevant. For vehicles intended to tow trailers with positive-pressure air, verify supply line and control line behaviour per clauses 4.1.9 and 7.13, and ensure couplings are polarized and comply with AS 4945-2000 (clause 4.1.8). If rated towing capacity exceeds 4.5 tonnes, choose whether to provide trailer-brake certification (clause 4.1.10.1) or supply sufficient test data for Administrator modelling (clause 4.1.10.2).

8. Plan testing programme and test venue. Create a testing plan that follows the sequencing in clause 5.2 and Table 1. Secure test tracks and facilities that meet the general test conditions (clause 6) , temperature, track gradient, wind, tyre type, inflation and friction surfaces , and confirm instrumentation and data acquisition meet Appendix 2 post-processing requirements where ESC is being tested.

9. Conduct pre-test conditioning and calibration. Follow pre-test instrument checks (clause 7.1), burnishing procedures if used (7.2), brake conditioning and tyre conditioning (Appendix 2 paragraphs 5.4-5.5), and ensure ABS/ESC tell-tales check functions per clauses 4.2.6 and Appendix 2 paragraph 5.2-5.3.

10. Record and process data to ADR-specified methods. Use the ADR’s formulae for average deceleration (clause 6.8 and Table 3), ERC calculations (clause 7.13.3), and ESC post-processing filters, zeroing ranges and interpolation methods (Appendix 2 paragraph 5.11). Ensure calculations incorporate TR (actuation response time) measured per clause 7.12.

11. Prepare documentation for submission to Administrator/technical service. Include full test reports, instrumentation checks, ESC simulation validation reports (if simulation used), diagrams and logic descriptions for ESC per Appendix 2 paragraph 3.7, and any ‘Approved’ calculation reports for variants per clauses 4.1.9.4 and 4.1.10.3.

12. Exploit equivalence routes where appropriate. If the vehicle has UNECE R13 or GTR No.8 approvals that correspond to ADR requirements, prepare to submit those approvals alongside evidence demonstrating that exemptions listed at clause 8.3.1 do not apply or have been addressed. Clause 8.1.2 allows certain annexes to be satisfied through conformity of production; check whether your production regime and conformity processes meet those expectations.

13. Ensure supply-chain and production-line alignment. Source couplings, valves and connectors that comply with the standards cited (AS 4945, ISO 3583, ISO 11992, ISO 7638), and ensure component labeling, reservoir caps and drain valves are included in production documentation (clause 4.6.4; clause 4.1.12; clause 4.7.5.2-4.7.5.3).

14. Anticipate reviewer queries. Be ready to explain and demonstrate: the effect of any vehicle variant changes on braking performance (for approved calculation arguments), the validation of any ESC simulation tool (Appendix 2 Attachment 2), and the reasons for any optional design choices (manual ABS disconnect device design and auto-reconnect logic , clause 4.1.5.2).

15. Maintain records for conformity and post-market checks. Keep simulator test reports, ESC documentation, test data and FMEA/FSA materials (Appendix 2 Attachment 3 and Appendix 2 Attachment 4) available for review by the Administrator and technical services.

Checklist summary (items to confirm before submission)

• Applicability date and ADR version for the model (clauses 2.1-2.3, 2.8).
• Service, parking and secondary brake architectures comply (clauses 4.1, 4.3, 4.5).
• Visible/audible indicators, labelling, and instrument panel location conform (clause 4.2, 4.4, 4.2.12).
• Reservoir volumes, condensate drains, fluid warnings present (clause 4.6).
• Stored energy devices sized and gauges fitted (clause 4.7).
• ABS and ESC fitted and tested/documented as required (Appendix 1; Appendix 2 3.7).
• Trailer supply/control behaviour validated and data supplied if rated towing >4.5 t (clause 4.1.9-4.1.10).
• All tests in Table 1 achieved under Part 6 and Part 7 conditions, with required instrumentation and processing (clause 5.1; Parts 6-7; Appendix 2 paragraph 5.11).
• Component standards and connectors conform to the cited standards (clause 4.1.6, 4.1.8; Appendix 1 clause 1.3.2).
• If using equivalence, ensure UNECE/GTR approvals explicitly meet ADR conditions and exemptions (Part 8).

Following this stepwise plan and cross-referencing clauses cited above will establish a defensible path to demonstrating compliance to the Administrator or accredited technical services.