Skip to content

Foam System Testing

Total Group provides foam system testing for industrial fire protection systems. The service assesses system performance, concentration and overall system integrity, helping facility, maintenance and HSE teams plan testing around operating conditions, shutdowns and turnaround work.

What foam system testing assesses

Foam systems combine stored concentrate, proportioning equipment, piping, discharge devices and other controls. Testing is planned around the installed system and the question the owner needs answered. The agreed scope may address whether the system operates as intended, whether the foam solution or concentrate condition is suitable for the planned assessment, and whether the system remains intact as a whole.

These are different from a visual inspection, a repair, a new-system commissioning activity or a foam changeover project. A test can identify a concern, but the required corrective work and any acceptance decision remain separate questions. Share the system configuration, foam product and reason for testing so the team can define the work boundary rather than treating every foam-system request as the same test.

Testing methods and PlanitSafe

Total Group also offers PlanitSafe testing as an option for sites that want to retain their existing foam concentrate. PlanitSafe’s manufacturer describes its surrogate-liquid programme as a method intended to avoid releasing foam solution during performance testing. That option may be useful where discharge, collection or environmental controls affect the test plan.

A surrogate or dry approach does not automatically replace every wet test, acceptance test, commissioning requirement or authority, insurer or manufacturer condition. The suitable method depends on the system, the purpose of the test, the applicable requirements and the records the owner needs. Confirm those points before selecting the test approach.

Standards and jurisdiction

NFPA 11 is a consensus standard covering the design, installation, operation, testing and maintenance of low-, medium- and high-expansion foam systems for fixed, semi-fixed and portable applications. It provides a recognised technical framework, but the standard name alone does not establish which edition or provisions are legally adopted at a particular site.

Canadian requirements can vary by province, territory, municipality, facility type and project documents. An authority having jurisdiction, insurer, manufacturer or owner programme may set additional requirements. Confirm the adopted code, referenced standard edition, system listing or approval conditions and any required qualifications before the work is scheduled. Total Group’s testing discussion can then be aligned with the site’s governing requirements without treating a general Canadian explanation as a universal legal rule.

Foam, PFAS and test planning

Identify the foam product before testing. The Government of Canada notes that not all firefighting foams contain PFAS, and that product labels and safety data sheets may not fully identify the chemistry. The federal guidance also states that, from June 30, 2026, certain C8 AFFF system-testing releases must be contained and disposed of in an environmentally sound manner. Provincial and territorial authorities control approval, licensing and monitoring of waste-management operations, so the disposal route depends on the site jurisdiction, product history and waste classification.

For that reason, do not assume that test liquid, rinsate, residual concentrate or collected foam can be discharged to a drain or managed as ordinary waste. Identify containment, collection, handling and disposal responsibilities in the work plan. Foam transition or firefighting foam disposal is a separate scope discussion from system testing.

When to discuss testing

Bring foam system testing into planned maintenance, shutdown or turnaround planning when the system’s condition, records or operating status need to be assessed. It may also be appropriate after a system change, a concern about performance, a change in foam product or a requirement from an authority, insurer or project specification. The correct timing and frequency depend on the applicable code, adopted standard, manufacturer information and site programme. This page does not set a universal interval.

Before work begins, the owner or site team should identify who will arrange access, permits, notifications, isolation, impairment controls, restoration and any required collection or waste arrangements. Agree the expected system status after testing and how findings will be recorded. Testing should not leave the protected system in an unplanned status.

What to prepare for an enquiry

Send the information available, even if the records are incomplete:

  • System details: site location, protected area, system type, drawings, equipment information, foam product name, manufacturer and available safety data sheet.
  • Reason for testing: routine planning, a system change, a performance concern, a project requirement or a request to retain existing concentrate.
  • History: previous inspection or test records, known deficiencies, recent repairs, changes to the system and current operating status.
  • Site arrangements: access restrictions, permit requirements, preferred work window, operations and HSE contacts, and any monitoring or authority notifications.
  • Environmental planning: whether the proposed work may involve discharge, isolation, collection, handling or disposal, and who owns each arrangement.

If drawings, product information or previous records are missing, identify the gap at the start of the enquiry. That allows the test scope and documentation needs to be discussed honestly.

Discuss foam-system testing requirements

Tell Total Group which foam system needs testing, what prompted the request, what records are available and your preferred work window. The team can discuss the service scope and site arrangements for the installation. For related industrial fire protection support, visit our Fire Services hub.

Sources

Discuss foam-system testing requirements