DesignationISO 22343-1:2023/PRF Amd 1
Stage50.00, FDIS registered
Planning date, an estimate15 Feb 2027
Published todayISO 22343-1:2023
1Clause
The frame of the standard

Scope

ISO 22343-1:2023, Clause 1Amends ISO 22343-1:2023Retrieved 20 October 2026

The standard rates a barrier against one unmanned vehicle impact and stops at 25 metres of penetration. It is not a design guide, a certification scheme or a blast standard.

Basis. The public preview carries this clause. The clause number and defined terms are the standard's; the explanation is our own.

What clause 1 asks

The document states what a barrier must achieve on impact, how to run the test, and how the result is rated. The test is one hit from a vehicle that nobody drives. It applies where penetration beyond the datum line does not exceed 25 metres. It is written for manufacturers and procurers who use a barrier to protect people in public or private places from a vehicle attack. It excludes slow approaches, gentle nudges and repeated ramming, explosions, bullets, attackers on foot working with or without tools, electrical tampering, and any attack on the controls. It also excludes design guidance, operational suitability and other impact test methods.

Why it matters

The scope decides the claim. A buyer who reads the title and assumes the standard covers every vehicle attack will over-claim to a customer, an insurer or a planning authority. The exclusions are as important as the inclusions: a barrier rated under this document has not been tested for a blast, a ballistic round, a group of attackers on foot or a cyber takeover of its controls. The 25 metre limit is a hard edge. A result beyond it is a data point, not a rating.

What good looks like

Write a scope note for every barrier in the estate. Name the edition relied on, the threat vehicle, the impact conditions, the site and the exclusions the buyer is not claiming. Put the note in the tender file and in the assurance statement. Where a customer asks for a capability the standard excludes, say so and point to the standard that does cover it rather than stretching this one.

Evidence an assessor asks for

An assessor or a customer will ask what the rating does not cover. If the scope note cannot answer in one line, the claim is wider than the evidence.

  • Scope note A dated note per barrier naming the edition, the threat basis, the site and the exclusions not claimed
  • Claim register The exact wording used with customers, insurers and planners, checked against the scope
  • Exclusion list The standard's exclusions reproduced as a checklist, with a named owner for any capability that needs another standard
  • Edition log The edition cited in each live specification and contract, with the date it was checked

Where it commonly fails

  • A blast-rated product is presented as meeting this standard because it also has a vehicle rating
  • A test report from IWA 14-1:2013 is described as an ISO 22343-1 rating without a new test
  • A penetration result beyond 25 metres is quoted as if a rating had been awarded
  • A movable barrier is described as stopping a vehicle without a statement about its closed and locked state

What to do before the amendment publishes

List every barrier and the exact claim made for it. Strike any claim the scope does not support before the next customer conversation.

Read across

← D Post-impact foundation and VSB measurements2 Normative references →

Full register / The dates / Free scope check