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

The standard is structured around a small set of technical concepts that determine compliance obligations for designers, manufacturers and technical services. Each concept is defined in the instrument or is used consistently with ADR practice.

• Vehicle category and applicability. The ADR applies to specified ADR vehicle categories (MB, MC, MD, ME, NA, NB, NC, LEG and others listed in the Applicability Table) with staged commencement dates: new models from 1 November 2015 (cl 2.1), categories MB/MC from 1 November 2016 (cl 2.2) and LEG/MD/ME/NA/NB/NC from 1 November 2017 (cl 2.3). A “new model” is defined by date of manufacture (cl 2.4). The table cross-references UNECE category codes (Applicability Table).

• Service Brake System. A central requirement is a Service Brake System operable on all road wheels via a single “Control” reachable from the normal driving position (cl 4.1.1). The rule includes detailed performance expectations for service brake retardation as a function of input control signals and loading (cl 4.1.9, Figures 1 and 2).

• Secondary Brake System and Parking Brake. Vehicles must have a Secondary Brake System and a Parking Brake System meeting mechanical retention, actuation and performance conditions (cl 4.5, cl 4.3). The Secondary Brake can utilise service-brake elements but must be operable via its own control, with minimum stored-energy capacity rules where stored-energy devices are used (cl 4.5.6, cl 4.7).

• Antilock, ESC and BAS. Vehicles in certain categories must be equipped with ABS (Appendix 1), and MB/MC/NA categories must have ESC and Brake Assist Systems meeting Appendix 2 (cl 4.1.1.1, cl 4.1.5, Appendix 1 and Appendix 2). The appendices contain functional definitions, equipment, performance tests, and documentation requirements (Appendix 1, Appendix 2 and Attachments).

• Indicators and labelling. The standard sets precise conditions for “Visible Indicators” that must signal service brake failure, including trigger thresholds (hydraulic failures, reservoir levels, supply-line pressure drop thresholds at 450 kPa, and absence detection at 35 kPa) and check routines on ignition (cl 4.2.1-4.2.6, cl 4.2.4-4.2.4.2). Labels and telltales must use specified words or ISO symbols and minimum dimensions (cl 4.2.10-4.2.12).

• Test regime and metrics. Performance compliance is demonstrated through testing set out in Table 1 and further specified in parts 6 and 7. Tests cover Service Brake Effectiveness lightly laden and laden, Secondary Brake tests, Partial Failure tests, Service Brake Fade and Fade Effectiveness Check, Parking Brake tests on an 18 per cent gradient, Actuation Time and Service Brake Compatibility with trailers (cl 5; parts 6 and 7; Table 1). Numerical pass criteria and constants are provided (Table 3; Figure 1 and Figure 2; cl 7.9 etc).

• Equivalence and alternative standards. The ADR allows conformity to certain UNECE regulations and EC instruments to be treated as equivalent, subject to specified conditions (cl 8.1-8.7). This provides an acceptance route for vehicles certified to particular UNECE Regulation No.13 versions or Global technical regulation No.8 for ESC.

These concepts interact. For example, requirements for ABS/ESC/BAS (Appendices) impose both design and testing obligations that feed into the performance tests (parts 5-7) and documentation obligations under the Administrator’s approval processes (cl 4.1.10.2, Appendix 2 paras 3.7 and Attachments). The standard mixes prescriptive design features (reservoir capacities, indicator locations, plumbing connectors cl 4.6.2-4.6.4, cl 4.1.8) with performance-based tests that require instrumentation, data processing and repeated test runs (parts 6-7; Appendix 2 Attachments on filtering and sampling).

The ADR imposes duties and creates costs primarily for vehicle manufacturers and type‑approval holders, but it also affects suppliers, test houses, importers, regulators and, indirectly, fleet operators and repairers.

• Manufacturers and type-approval holders. They are the primary actors required to design, produce, certify and document compliance. The standard repeatedly uses the term ‘Manufacturer’ and contemplates manufacturer-supplied documentation to the ‘Administrator’ (cl 4.1.10.2, Appendix 2 paras 3.7.1-3.7.4). Manufacturers must plan for category-based roll-out dates (cl 2.1-2.3), fit mandatory subsystems for specified categories (ESC/BAS for MB/MC/NA; ABS for a range of categories; see cl 4.1.1.1 and cl 4.1.5), and perform or commission the performance and durability tests in parts 5-7 and Appendices (cl 5-7, Appendix 1, Appendix 2).

• Suppliers of braking, ABS, ESC and BAS components. The ADR requires component-level conformity to recognized international standards or parts thereof (cl 4.1.6). Suppliers to manufacturers will face specification requirements for reservoirs, valves, quick couplings (must comply with AS 4945-2000, cl 4.1.8), pressure gauges, and electrical connectors for antilock/trailer ABS (Appendix 1 clauses 1.3.1-1.3.2, Appendix 1 Annex 1).

• Testing and certification bodies (technical services). The rule demands specific test setups, instruments, sampling rates and data processing procedures (Appendix 2 Attachments 4-6). Technical services will need capability for Sine-with-Dwell ESC tests (Appendix 2 para 5.9), brake fade sequences (cl 7.9), actuation-time tests with specified 2.5 m, 13 mm ID pipes (cl 7.12.6.1), and service brake compatibility tests (cl 7.13). Where simulation is used for ESC, validation of the simulation tool and submission of tool test reports are required (Appendix 2 Attachment 1-3).

• Administrators and regulators. The Administrator is the reference authority for approvals and accepts documentation, approved calculations and alternative standards in specific circumstances (cl 4.1.9.4, cl 4.1.10.2, cl 8). Regulators must assess conformity of production and accept some Annexes via conformity assessment (cl 8.1.2).

• Importers, distributors and fleet owners. Vehicles entering the Australian market must meet the ADR at the relevant dates. Importers and fleet owners must ensure that the vehicle’s certification covers the ADR or its accepted equivalent (cl 8). Where a vehicle is a variant of a previously tested vehicle, the ADR permits ‘Approved’ calculations to demonstrate compliance, which may affect small-scale modifiers or upfitters (cl 4.1.9.4; cl 4.1.10.3).

• Repairers, maintenance technicians and inspectors. The ADR sets minimum reservoir capacities, labelling that must be permanent and visible (cl 4.6.3-4.6.4), drain valve requirements for air reservoirs (cl 4.1.12), and performance expectations for stored energy systems that will affect servicing and inspection procedures.

Who pays. The visible, measurable costs fall on manufacturers and technical services: redesign, component specification, testing, instrumentation, labelling, documentation and possibly rework. Where vehicles exceed towing thresholds or have complex configurations (retractable axles, road trains), additional testing or data provision is required (cl 4.1.9-4.1.10, cl 6.14, cl 7.13).

Who decides. The Administrator (as referenced throughout) determines acceptance of alternative evidence, approved calculations and equivalence to foreign regulations (cl 4.1.9.4, cl 4.1.10.2, cl 8). Technical services decide and perform the tests according to the procedures in parts 6-7 and the Appendices; manufacturers decide whether to adopt UNECE equivalent standards or to demonstrate compliance via ADR tests and data (cl 8).

The standard creates concrete duties for manufacturers and technical services and grants limited administrative discretion to the Administrator.

Key duties (with source clauses):

• Fit a Service Brake System operable on all road wheels via a single Control located for driver use (cl 4.1.1).
• Fit ESC and Brake Assist for vehicles of category MB and MC, and for NA category vehicles the same functions where specified, meeting Appendix 2 (cl 4.1.1.1).
• Fit ABS where applicable and meet Appendix 1 provisions; certain categories (MD4, ME, NB, NC) must have ABS meeting Appendix 1 and cl 4.1.5.1 (cl 4.1.5; cl 4.1.5.1).
• Provide Service Brake failure ‘Visible Indicators’ and, if applicable, an audible indicator when a single Brake Power Unit is used (cl 4.1.2; cl 4.1.11; cl 4.2).
• Ensure reservoirs, drain valves and labelling meet the sizes, locations and labelling requirements in cl 4.6 (cl 4.1.12; cl 4.6.2-4.6.4).
• Provide a Secondary Brake System with specified control properties and stored-energy requirements for spring brake systems and other back-up arrangements (cl 4.5, cl 4.7).
• Meet performance tests summarised in Table 1 and follow general and particular test conditions (cl 5; parts 6 and 7).
• Where vehicles tow trailers, demonstrate service brake compatibility and meet specified “Established Retardation Coefficient” (ERC) performance across control signal ranges or supply administrative data to the Administrator for modelling if Rated Towing Capacity exceeds 4.5 tonnes (cl 4.1.9; cl 4.1.10; cl 7.13).

Administrative rights and discretions:

• The Administrator may accept ‘Approved’ calculations or documentation rather than full re-testing where the vehicle is a variant of a previously tested vehicle (cl 4.1.9.4; cl 4.1.10.3).
• The Administrator accepts certain UNECE, GTR or EC regulations as equivalent provided specified conditions are met (cl 8.1-8.7).
• Manufacturers have the option of alternative test procedures and burnishing options where allowed (cl 7.2; cl 7.14).

Obligations about warnings, labelling and human interface:

• Visible indicators must meet specified trigger levels and check behaviour on ignition; labelling must use “BRAKE” or ISO symbols with minimum letter heights and colours (cl 4.2.1-4.2.12).
• Parking brake controls must be separate and retain engagement (cl 4.3.1-4.3.4). Parking Brake Indicator lamp and its label must satisfy location and size requirements (cl 4.4).

Documentation and technical submissions:

• ESC/BAS require system diagrams, operational descriptions, logic diagrams and understeer information to be provided to Administrators as part of confirmation of compliance (Appendix 2 para 3.7).
• For ABS and ESC trailer interconnection, electrical connector functions and pin capacities are specified (Appendix 1 paras 1.3.1-1.3.3 and Annex 1 for MD4/ME/NB/NC).

Rights to equivalence and alternative conformity:

• Manufacturers may rely on UNECE Regulation No.13 (particular amendment series) and other UNECE/EC instruments as equivalent technical evidence, subject to Australia-specific provisos (cl 8.1-8.7). This creates an administrative right to streamline type approval where vehicles already meet recognised international standards.

The text gives procedural rights to manufacturers to request use of calculations and simulation for variants (cl 4.1.9.4; Appendix 2 Attachment 1-3) and allows some optional testing permutations but binds users to precise numeric trigger values, test setups and data-processing requirements (Appendix 2 Attachments 4-6).

The ADR itself sets technical requirements and test procedures but does not specify monetary fines or criminal penalties within its text. It is a Vehicle Standard made under the Motor Vehicle Standards Act 1989 (header), and enforcement/penalty mechanisms are therefore those established under the Act and the broader administrative framework for vehicle standards and type approval. The ADR repeatedly references an ‘Administrator’ who performs acceptance and approval functions (for example cl 4.1.10.2, cl 4.1.9.4 and cl 8), implying that non-compliant vehicles will be refused certification or denied admittance to the Australian market via the type-approval process.

What the standard requires of enforcement agents and how compliance will be determined:

• The standard provides objective, measurable pass/fail criteria and specific test procedures: the Administrator and technical services are to apply the tests in parts 6-7 and the appendices to determine compliance (cl 5-7, Appendix 1 and Appendix 2). This technical specificity reduces the need for subjective interpretation in enforcement.
• The Administrator is empowered to accept documentation, approved calculations and equivalence to UNECE/EC rules in some circumstances (cl 4.1.9.4, cl 4.1.10.2, cl 8.1-8.7). That acceptance is an administrative discretion which functions as a compliance pathway; refusal of equivalence would require the manufacturer to provide ADR-specific evidence.

Where the ADR is silent or defers:

• The instrument does not contain an enforcement or penalty schedule. It therefore defers to the Motor Vehicle Standards Act 1989 for legal force and any penalty provisions or enforcement processes. Because the ADR is a regulatory technical standard, enforcement typically occurs at type-approval, importation, registration and roadworthiness testing stages rather than through sanctions specified in the ADR text itself.

Practical enforcement implications:

• Failure to obtain Administrator acceptance or to demonstrate compliance via the prescribed tests (or accepted equivalents) will prevent vehicles from being certified as compliant with the ADR, which in practice prevents lawful supply or registration in Australia for vehicles in the covered categories.
• Technical non-conformity detected during ADR-specified tests (for example failure of fade tests, actuation time tests, or ESC dynamic tests) results in a failing outcome under the ADR test protocol; the manufacturer must redesign or present further acceptable evidence to the Administrator.

In short, the ADR prescribes the technical correctness tests and the Administrator has scope to accept or reject certification and to require additional evidence; any penalties for supplying non-compliant vehicles are those available under the Motor Vehicle Standards Act 1989 and associated administrative or criminal provisions outside the text of this ADR.

The ADR is an instrument made under the Motor Vehicle Standards Act 1989 and forms part of the statutory type-approval and vehicle importation/registration architecture. The text explicitly cross-references and accepts certain international instruments as equivalent, and it references other ADRs and Australian standards.

Interaction points set out in the instrument:

• Enabling Act. The ADR is “Made under the Motor Vehicle Standards Act 1989” (header). The ADR therefore sits within the statutory regulatory framework that governs type approval, importation and supply of motor vehicles. The ADR itself delegates administrative functions to an ‘Administrator’ and anticipates the Administrator’s acceptance of documentation and calculations (cl 4.1.10.2; cl 4.1.9.4).
• Other ADRs. The standard cross-references other ADRs and prior acceptable rules. For instance, vehicles of category MB, MC or NA complying with ADR 31/... will be accepted as complying with this standard (cl 2.5). Vehicles certified to ADR 35/06 or later need not comply with this rule (cl 2.9). It also refers to the Vehicle Standard (Australian Design Rule Definitions and Vehicle Categories) 2005 for categories and definitions (cl 3.2).
• Australian standards and international standards. Component-level requirements may be satisfied by recognized international, national or association standards, including SA, SAE, BS, JIS, DIN, ISO and UNECE standards (cl 4.1.6). Quick couplings must comply with AS 4945-2000 (cl 4.1.8).
• UNECE and EU instruments. The ADR allows equivalence to UNECE Regulation No.13 (cl 8.1-8.7), UNECE Global technical regulation No.8 for ESC (cl 8.4) and selected provisions of EC Regulation No.631/2009 for Brake Assist in pedestrian protection (cl 8.5). Equivalence is conditional: for example, MD4/ME/NB/NC vehicles must be fitted with ABS when relying on UNECE R13 equivalence (cl 8.1 and cl 8.1.1), and ESC/BAS equivalence has specified exemptions (cl 8.4.1).
• Roadworthiness and state/territory registration law. The ADR sets type-approval and design/performance standards that influence national and state/territory registration and safety checks, but it does not replace those regimes. State-based roadworthiness inspections and registrations will use ADR compliance as a reference point for acceptance.
• Testing and measurement standards. The ADR incorporates or references testing methods and measurement standards (for example ISO 3583, ISO 11992, ISO 2575; Appendix 1 and cl 4.1.9.5). Appendix 2 includes detailed requirements for data acquisition and filtering consistent with ISO 15037 and other ISO standards (Appendix 2 Attachments 4-6).

Tensions and practical interfaces:

• Equivalence acceptance reduces duplication where vehicles already meet UNECE/EC standards; however, the ADR imposes Australia‑specific provisos (for example for road-train vehicles and ESC/BAS scope) so equivalence is not entirely substitutive (cl 8.1, cl 8.4).
• The ADR requires the Administrator to accept approved calculations or simulation for vehicle variants (cl 4.1.9.4, Appendix 2 Attachment 1-3). That introduces an interface between engineering documentation submitted by manufacturers and the administrative approval process under the Act.

In sum, the ADR is a technical standard in a layered regulatory system: it is implemented through statutory type-approval and administrative processes under the Motor Vehicle Standards Act 1989, it defers to and incorporates international technical standards where appropriate, and it interacts with state and national vehicle registration and roadworthiness regimes that rely on ADR compliance as a threshold for market access.

The compilation header included with the instrument records the name, compilation number and date and lists two amendments. The document’s “Table of Instruments” shows:

• Vehicle Standard (Australian Design Rule 35/05 - Commercial Vehicle Brake Systems) 2013, registered 29/10/2013 and commenced 30/10/2013 (Table of Instruments).
• Amendment 1 registered 16/09/2014, commenced 17/09/2014.
• Amendment 2 registered 29/05/2018, commenced 30/05/2018.

The Table of Amendments identifies clauses affected by amendment actions:

• Clauses amended by Amendment 1 include 4.1.5.2.1, 4.1.5.2.3 and 4.1.5.2.5 (listed as “amended” in the Table of Amendments).
• Clause 2.9 was added by Amendment 2 (the Table of Amendments shows 2.9 with notation “ad” for added or inserted).

Concrete outcomes of amendments reflected in the text:

• Clause 2.9 as now drafted states: “Vehicles certified to ADR 35/06 or a later version need not comply with this rule.” That was introduced by Amendment 2 and creates an express exemption for vehicles already certified to a later iteration of ADR 35 (cl 2.9). Practically this avoids duplication and clarifies the transitional treatment of vehicles already approved to an updated ADR version.
• The amendments to cl 4.1.5.2.x (Amendment 1) relate to manual devices that permit disconnecting or changing the control mode of the Antilock System on NB/NC vehicles and the specific operational and warning obligations that apply where such devices are fitted (cl 4.1.5.2 and subclauses). Those subclauses require, for example, that the vehicle with ABS disconnected must still satisfy the relevant requirements in clause 7, that an optical warning must inform the driver, and that the ABS shall automatically be reconnected on ignition cycle or specified conditions; these show detailed operational constraints following the amendment.

What the amendment history implies operationally:

• The ADR has been updated at least twice since initial registration to incorporate clarifications, exemptions and operational details. The addition of cl 2.9 formalises forward compatibility with later ADR versions and reduces potential conflict when new ADRs are introduced.
• Amendment 1’s changes to the ABS manual disconnect provisions (cl 4.1.5.2 and subclauses) clarify the conditions and warnings when a manual ABS disconnect is present for NB/NC vehicles, indicating a policy choice to permit limited manual override subject to explicit safeguards.

Record-keeping and retrieval. The compilation reportedly includes all instruments in the Table of Instruments and a Table of Amendments providing a history of clauses changed, inserted or deleted. The compilation date is 30 May 2018 and it is labelled Compilation 2 (header and notes).

No further amendment history, legislative debates or explanatory memoranda are included in the text provided. The Table of Amendments is the only explicit amendment record within the instrument text.

The instrument as supplied does not include any litigation history, judicial interpretations or named cases. The ADR text and compilation notes do not record judicial decisions or administrative appeal outcomes. The only historical record provided is the Table of Amendments and Table of Instruments, which list the registration and commencement dates and the clauses amended or inserted (Notes; Table of Instruments; Table of Amendments).

Implications for practitioners:

• There are no case citations or reported judicial constructions within the ADR document itself. Any litigation or administrative challenges concerning this ADR would arise under the Motor Vehicle Standards Act 1989 or through disputes over type-approval decisions by the Administrator, but such outcomes are not recorded in this instrument.
• For legal or compliance advice that requires precedential interpretation, practitioners must consult external sources: decisions under the Motor Vehicle Standards Act 1989, administrative records from the Administrator, tribunal or court decisions, or regulatory determinations that are not contained in the ADR text. The ADR provides the technical baseline and administrative pathways but leaves enforcement and dispute resolution to the enabling Act and administrative processes.

What the absence of litigation history in the instrument means in practice:

• The ADR is a technical standard. Challenges likely focus on adequacy of test evidence, acceptance of calculated/simulated data for variants, or the Administrator’s exercise of discretion in accepting equivalence to UNECE or EC regulations. Those are administrative and technical disputes rather than statutory unconstitutionality or high‑level judicial interpretation matters.
• If an entity requires precedent about how the Administrator exercises discretion,for example, when to accept “Approved” calculations for vehicle variants,external administrative rulings and tribunal decisions will be the source of guidance, but none are included in the ADR text provided.

In short, no litigation history is documented within this ADR text; practitioners should look beyond the instrument to administrative and judicial records for interpretive guidance.

This ADR contains numerous technical thresholds, prescriptive measurement setups, and conditional administrative routes that tend to create practical compliance risks. The following is a list of concrete pitfalls that frequently surface in compliance work and the clauses that create them.

1. Applicability timing and “new model” definition (cl 2.1-2.5).

• “New model” is defined by date of manufacture (cl 2.4). Manufacturers who change components but not model designation must be careful: a variant first produced on or after the new‑model date can trigger the requirement to comply immediately. Misclassifying a model as an existing model rather than a new model may cause non-compliance.

2. Variant testing vs approved calculations (cl 4.1.9.4; cl 4.1.10.3).

• The ADR allows ‘Approved’ calculations for variants where tests on a complete vehicle, component or sub‑assembly have established the effect on braking performance (cl 4.1.9.4; cl 4.1.10.3). The Administrator must accept those calculations. Experience shows disputes arise over the sufficiency of calculation methods and validation data; the ADR does not detail what constitutes “Approved” calculations beyond the Administrator’s acceptance.

3. Trailer compatibility and towing thresholds (cl 4.1.9-4.1.10; cl 7.13).

• For vehicles with Rated Towing Capacity > 4.5 tonnes the manufacturer must either provide certification for trailer brakes using air at positive pressure or supply sufficient data for Administrator modelling (cl 4.1.10.1-4.1.10.2). This creates a decision: expensive trailer-brake certification testing vs preparation and submission of detailed test data for modelling. The service brake compatibility test has specific control signal increments and ERC computation (cl 7.13.1-7.13.3), including the use of 2.5 m pipes for actuation-time tests (cl 7.12.6.1).

4. Manual ABS disconnect on heavy vehicles (cl 4.1.5.2).

• The ADR permits a manual device to disconnect or change ABS control mode for NB/NC vehicles under conditions: the vehicle must still meet clause 7 when ABS is disconnected or its control mode changed; an optical warning must inform the driver; the ABS must reconnect automatically on ignition restart or under specified drivetrain conditions; and the user manual must warn about consequences (cl 4.1.5.2.1-4.1.5.2.4). In practice, this produces compliance traps: the re‑engagement logic must be validated, the warning lamp behaviour must meet Appendix 1 requirements, and conformity in clause 7 tests must be demonstrated in both modes.

5. Indicator thresholds and absence detection (cl 4.2.1-4.2.6; cl 4.2.4.2).

• The visible indicator must operate at specific pressure thresholds: brake power unit drops to ≤65% of Average Operating Pressure (cl 4.2.3) and trailer supply line drop to ≤450 kPa (cl 4.2.4). It must also not operate when no trailer is connected, determined by supply line ≤35 kPa (cl 4.2.4.2). Poorly designed detection logic can cause nuisance warnings or fail to illuminate when required.

6. Location and labelling requirements (cl 4.2.10-4.2.12; cl 4.4).

• Visible and parking brake indicator lamps must be within a tightly prescribed cockpit envelope (cl 4.2.12) and labels must meet font height and colour requirements (cl 4.2.10.1-4.2.10.3, cl 4.4.5). These are easily missed during interior redesigns or when toggling between combined and separate lamps.

7. Stored energy and reservoir capacity math (cl 4.6.2-4.7.6).

• Reservoir capacity and stored-energy device sizing rules are prescriptive: reservoir volumes must accommodate piston travel between new and fully‑worn linings (cl 4.6.2), and stored energy volumes and charging time formulas reference “Brake Power Unit test capacity” and multipliers (cl 4.7.2-4.7.4). Compliance requires accurate component specifications and conservative calculations.

8. Actuation time and pipe geometry (cl 7.12.6.1-7.12.6.2).

• The service brake actuation time test for vehicles towing trailers requires a 2.5 m long pipe with internal diameter 13 mm attached to the Control Line coupling head and demanding pressure attainment within 400 ms (cl 7.12.6.1). In road‑train hauling vehicles, release timing is specified with tight millisecond targets (cl 7.12.6.2). Small differences in coupling design or pipeline inner diameter can produce non‑compliant time responses.

9. ESC and BAS documentation and simulation validation (Appendix 2 paras 3.7, Attachment 1-3).

• ESC compliance can be demonstrated by validated simulation tools, but the tool validation procedure is detailed and requires a simulator test report and documentation tying the simulation to physical validation runs (Appendix 2 Attachment 1-3). Inadequate validation or missing simulation reports will be rejected.

10. Equivalence conditions and Australia‑specific provisos (cl 8).

• Accepting UNECE/EC/Global technical regulations as equivalent is conditional. For example, for ESC using GTR No.8, various clauses are exempted (cl 8.4.1). Manufacturers relying on equivalence must map every proviso to ensure no gap in requirements for the Australian market.

Each of these “gotchas” maps to precise textual requirements in the ADR. Compliance requires careful engineering, well-documented test evidence, and early engagement with the Administrator about whether calculations, simulations or equivalence routes are acceptable.

Compliance is a project of specification, verification and documentation. The ADR prescribes both prescriptive construction requirements and objective test procedures. The following practical roadmap, grounded in the ADR text, identifies steps manufacturers, technical services and compliance officers should take.

1. Map scope and timing (cl 2.1-2.5, Applicability Table).

• Identify the vehicle’s ADR category (refer to Vehicle Standard Definitions and Vehicle Categories 2005 per cl 3.2). Determine whether the vehicle is a “new model” (cl 2.4). Confirm applicable commencement date: 1 November 2015 for new models, 1 November 2016 for MB/MC, and 1 November 2017 for LEG/MD/ME/NA/NB/NC (cl 2.1-2.3; Applicability Table). If the vehicle is certified to ADR 35/06 or later, cl 2.9 provides an exemption.

2. Design to meet prescriptive clauses (cl 4.1-4.7).

• Ensure a Service Brake System operable on all road wheels by a single Control (cl 4.1.1).
• If vehicle category requires ESC and BAS (MB, MC, NA as specified), design those systems to meet Appendix 2; for ABS, comply with Appendix 1 where required (cl 4.1.1.1; cl 4.1.5).
• Fit visible and audible failure indicators that comply with trigger thresholds and check routines (cl 4.2.1-4.2.6; cl 4.2.10).
• Design parking brake controls to meet mechanical retention and labelling requirements (cl 4.3-4.4).
• For air systems: include manual condensate drains at the lowest point of each air reservoir (cl 4.1.12); ensure brake line couplings are non-interchangeable and polarized and meet AS 4945-2000 (cl 4.1.8).

3. Prepare reservoirs, stored energy and component sizing calculations (cl 4.6, cl 4.7).

• Size master cylinder and reservoir capacity to account for full stroke and fully-worn lining movement following cl 4.6.2 and cl 4.6.3.
• For stored energy devices and Brake Power Units, calculate required combined volumes and charging times using formulas in cl 4.7.2-4.7.6 and model the charging capacity in the worst-case scenarios including trailer allowances (cl 4.7.4).

4. Plan test programme and test mass configurations (cl 5; parts 6 and 7; Table 1; cl 6.14).

• Identify which Table 1 items apply and schedule tests in logical grouped sequences (cl 5.2). Determine test masses: Lightly Loaded Test Mass (LLTM), Maximum Loaded Test Mass (MLTM) or GVM and group axle limits per Table 2 (cl 7.13; Table 2).
• For vehicles with retractable axles, demonstrate compliance in each configuration, and note which requirements are excepted (cl 6.14).

5. Arrange and document instrumentation, sampling and data processing (parts 6; Appendix 2 Attachments).

• Ensure tyre choice, inflation, friction elements and ambient test conditions follow parts 6 and 7 (cl 6.1-6.6).
• For ESC/BAS tests, adhere to the instrument and sampling rate, filtering and processing requirements described in Appendix 2 Attachments 4-6, including data acquisition at ≥500 Hz where specified (Appendix 2, B paras 2.2.3; Attachment 5-6).

6. Vendor and supply chain conformance (cl 4.1.6; cl 4.1.8).

• Obtain supplier declarations or certificates that key components meet recognized standards (ISO, SAE, AS, DIN, UNECE) as permitted by cl 4.1.6. For couplings, ensure AS 4945-2000 compliance (cl 4.1.8). For trailer ABS electrical connectors and pin supplies, implement wiring per Appendix 1 1.3.2 pin allocations and capacities.

7. Address towing and trailer compatibility early (cl 4.1.9-4.1.10; cl 7.13).

• If Rated Towing Capacity > 4.5 t, decide whether to provide certification for trailer brakes using air at positive pressure (cl 4.1.10.1) or to prepare the extensive dataset for Administrator modelling (cl 4.1.10.2 and cl 7.13.2). The compatibility test (cl 7.13) requires stopping runs from 60 km/h with incremental control signal increases and ERC calculations per cl 7.13.3. Prepare test rigs with the 2.5 m, 13 mm ID pipe geometry where actuation time is measured (cl 7.12.6.1).

8. Prepare ESC/BAS documentation and simulation evidence if used (Appendix 2 paras 3.7, Attachment 1-3).

• For ESC, prepare system diagrams, operating descriptions, logic diagrams and understeer information (Appendix 2 para 3.7.1-3.7.4). If relying on dynamic simulation, follow validation requirements in Attachment 2 and produce a simulator test report per Attachment 3.

9. Test to Table 1 items and maintain conformity of production (cl 5-7; cl 8.1.2).

• Perform tests per the sequence and groupings in cl 5.2. Record and retain raw data and processed outputs. For conformity of production applicable to some Annexes under UNECE equivalence, be prepared to demonstrate ongoing manufacturing control (cl 8.1.2).

10. Engage the Administrator early on equivalence, calculations and acceptance (cl 4.1.9.4; cl 4.1.10.2; cl 8).

• Where intending to rely on Approved calculations, simulation, or UNECE/EC equivalence, confirm the Administrator’s acceptance criteria up front. Provide documentation that maps international standards to ADR requirements, and for any exemptions listed under cl 8.4.1, demonstrate how the omitted provisions are otherwise satisfied.

11. Labelling, user information and handbook inclusions (cl 4.1.5.2.4; cl 4.6.4; cl 4.2.10).

• Include the required warning and operating statements in the user handbook, including warnings about manual ABS disconnection’s consequences (cl 4.1.5.2.4). Affix fluid type and “Clean filler cap” warnings with minimum 3 mm letters near brake reservoirs (cl 4.6.4).

12. Archive test evidence and supply documentation for type approval.

• Maintain test data, simulation validation, component standards references, and conformity-of-production procedures so that the Administrator can evaluate the submission. Where Annexes are deemed equivalent (cl 8), maintain conformity evidence for production assessments (cl 8.1.2).

Checklist items to verify before application for acceptance:

• Category and commencement date alignment (cl 2).
• Presence and labelling of visible indicators and parking brake lamp in the required cockpit envelope (cl 4.2.12; cl 4.4.6).
• Reservoir and stored-energy calculations and drain valves (cl 4.6.1-4.6.4; cl 4.1.12).
• ABS/ESC/BAS functional tests and tell-tale behaviours (Appendix 1 and Appendix 2).
• Service brake compatibility testing (cl 7.13) and actuation-time measurements (cl 7.12).
• Documentation pack for ESC/BAS if present (Appendix 2 para 3.7) and simulator validation report if used (Attachment 3).

Following this roadmap aligns the engineering, testing and documentary outputs with the ADR’s prescriptive language and objective test procedures. Early interaction with the Administrator around acceptance of calculations, simulation validation and equivalence reduces the risk of later refusals based on administrative discretion cited in the ADR (cl 4.1.9.4; cl 8).