Topics
How the Washington State Report Calculates Data
XXXX refers to the Reporting Year selected when generating the report.
Deleted assemblies are excluded from all values shown in the report.
Assembly status (Active / Inactive) is evaluated differently depending on the reporting year:
For the current year, the assembly must be Active at the time the report is viewed.
For past years, the assembly must have been Active on December 31 at 11:59 PM, based on the organization’s time zone for that year.
Hazard Type is pulled from the Location, not the assembly.
The report uses the Location → Table 13 Hazard Type field.
The Assembly → Table 13 Hazard Type field is for internal tracking only and does not affect the report.
Bypass assemblies are linked to their main assemblies by serial number.
The report assumes serial numbers are unique.
If duplicate serial numbers exist, bypasses may not link correctly to their main assemblies, resulting in inaccurate report totals.
When table definitions use the word “currently”, this means:
The report checks the current value on the record, not the historical value during the reporting year.
The report does not reference audit logs or historical changes.
Warnings Shown at the Top of the State Report
Warnings Shown at the Top of the State Report
The Washington State Report will display warnings at the top of the page to highlight potential data issues.
📌Important:
These warnings include inactive assemblies.
The only assemblies excluded from warnings are those whose First Recorded On date is after January 1 of the reporting year (1/1/XXXX).
Possible Warning Messages
“No locations found.”
The organization has no locations, or
All locations have been deleted.
“No assemblies found.”
The organization has no assemblies with a First Recorded On date on or before 1/1/XXXX.
“Serial number ______ is used by multiple assemblies.”
Indicates that the same serial number exists on multiple assemblies.
The warning links to the assembly with Serial Number ______.
Assemblies where this serial number appears in the Serial Number of Bypassed Assembly field are not linked in the warning.
This can prevent bypass assemblies from correctly linking to their main assemblies.
“An assembly and its reported bypass are not in the same location.”
The warning links to the bypass assembly, not the main assembly.
Triggered when:
The Bypass checkbox is selected
First Recorded On ≤ 1/1/XXXX
The Serial Number of Bypassed Assembly matches another assembly
The bypass and main assembly are assigned to different locations
If the bypass has no location, this warning will not appear.
If the main assembly has no location, but the bypass does, the warning will appear.
“A bypass assembly's main assembly wasn't found.”
The warning links to the bypass assembly.
Triggered when:
Bypass is selected
First Recorded On ≤ 1/1/XXXX
The Serial Number of Bypassed Assembly does not match any other assembly’s serial number.
“A bypass assembly doesn't indicate which assembly it bypasses.”
The warning links to the affected assembly.
Triggered when:
Bypass is selected
Serial Number of Bypassed Assembly is empty
First Recorded On ≤ 1/1/XXXX
“An assembly has an unknown protection type: _______.”
The warning links to the affected assembly.
Triggered when an assembly has a Protection Type that is not one of the following:
Premises isolation
In-premise protection
Fixture
“An assembly has invalid exception-related value(s).”
Triggered when the report cannot parse one or more exception-related fields for an assembly with First Recorded On ≤ 1/1/XXXX.
These fields must follow the expected formatting to be included correctly in the report.
3️⃣ Reusable “Calculation Rules” Block for Columns B, C, D
⚠️ Column B – With Premises Isolation by AG or RP
⚠️ Column B – With Premises Isolation by AG or RP
How this value is calculated:
For each hazard row, the report counts assemblies that meet all of the following conditions:
First Recorded On ≤ 12/31/XXXX
Assembly is not deleted
Assembly is currently at a location with the matching Location Table 13 Hazard Type
Assembly Status was Active at the end of the reporting year
Protects Public Water Supply is checked
Bypass is not checked
Protection Type = “Premises isolation”
Type = “AirGap” or begins with “RP”
All hazard rows use this same logic.
The only difference between rows is the Location Table 13 Hazard Type value.
⚠️ Column C – AG Inspected or RP Tested
⚠️ Column C – AG Inspected or RP Tested
How this is calculated
How this is calculated
Starts with the assemblies counted in Column B
Counts assemblies that have:
A non-deleted
Accepted test report
Tested On date within the reporting year (XXXX)
Important bypass behavior
Column B does not include bypass assemblies, but the report preprocesses bypass relationships:
If both main and bypass were tested in XXXX → counted once
If only one was tested → not counted
If neither was tested → not counted
This logic ensures testing compliance is evaluated at the system level.
⚠️Column D – Granted Exception from Mandatory Premises Isolation
⚠️Column D – Granted Exception from Mandatory Premises Isolation
How this value is calculated:
For each hazard row, the report counts assemblies that meet all of the following:
First Recorded On ≤ 12/31/XXXX
Assembly is not deleted
Assembly is currently at a location with the matching Location Table 13 Hazard Type
Exception Granted On has a date
Exception Expires On is either:
Empty, or
Later than 12/31/XXXX
All hazard rows use the same logic.
The only difference is the Location Table 13 Hazard Type value.
⚠️ Device-Type Breakdown (Air Gap, RPBA, RPDA, DCVA, DCDA, PVBA, SVBA, AVB)
⚠️ Device-Type Breakdown (Air Gap, RPBA, RPDA, DCVA, DCDA, PVBA, SVBA, AVB)
This part of the report breaks certain totals down by device type. Each device column uses the same counting logic—the only difference is the Type condition (and one special rule for AVB).
Device column | Assembly field condition |
Air Gap | Type = “Air Gap” |
RPBA | Type = “RP” |
RPDA | Type = “RPDA” or “RPDA-II” |
DCVA | Type = “DC” |
DCDA | Type = “DCDA” or “DCDA-II” |
PVBA | Type = “PVB” |
SVBA | Type = “SVB” |
AVB | Type = “AVB” AND “Low Hazard Irrigation” is checked |
Shared filters (applies to all rows and device columns)
Each row below starts by filtering assemblies to those that are:
First Recorded On ≤ 12/31/XXXX
Not deleted
Protects Public Water Supply is checked
Bypass is not checked
Type matches the selected device column (see mapping above)
Premises Isolation rows
(Protection Type = “Premises isolation”)
1) In service at beginning of year
Count assemblies where:
First Recorded On < 1/1/XXXX OR Installed On is within XXXX
First Recorded On < 1/1/XXXX
Note: The overlap between conditions is intentional—it reflects how the report code currently pulls data.
2) Inspected and/or tested
Same as (1), plus:
Has a non-deleted, accepted test report with a Tested On date in XXXX
Bypass handling (testing): bypass assemblies aren’t counted directly, but they affect whether the main counts as tested:
Main + bypass both tested in XXXX → counted once
Main tested, bypass not tested → not counted
Bypass tested, main not tested → not counted
Neither tested → not counted
3) Failed inspection or test this year
Same as (2), but the test in XXXX must have:
Test Result = Fail OR
At least one compliance issue
Note: A test can have compliance issues even if Test Result is Pass (rules can override).
Bypass handling (failures):
If the bypass has a failed test or compliance issue, the main is treated as failed.
Main + bypass both fail in XXXX → counted once
Only one fails → counted once
Neither fails → not counted
4) New preventers installed
Count assemblies where:
First Recorded On < 1/1/XXXX OR Installed On is within XXXX
First Recorded On ≥ 1/1/XXXX AND Installed On is within XXXX
Note: The overlap is intentional—it reflects current report-code behavior.
5) Inspected and/or tested (new installs)
Same as (4), plus:
Has a non-deleted, accepted test report with Tested On in XXXX
(Uses the same bypass testing behavior described above.)
6) Failed inspection or test this year (new installs)
Same as (5), but the test in XXXX must have:
Test Result = Fail OR at least one compliance issue
(Uses the same bypass failure behavior described above.)
7) Preventers taken out of service this year
Count assemblies where:
Status was set to Inactive in XXXX and was not reactivated by end of XXXX
Premises Isolation Total at end of year
Count assemblies where:
Status was Active by end of XXXX
Note: This should equal #1 + #4 − #7, but the report calculates it directly (not by summing).
In-premise protection / fixture rows
(Protection Type = “In-premise protection” or “Fixture”)
Rows 8–14 mirror rows 1–7, but with Protection Type = “In-premise protection” or “Fixture”:
Row 8. In service at beginning of year → same logic as (1)
Row 9. Inspected and/or tested → same logic as (2)
Row 10. Failed inspection or test this year → same logic as (3)
Row 11. New preventers installed → same logic as (4)
Row 12. Inspected and/or tested (new installs) → same logic as (5)
Row 13. Failed inspection or test this year (new installs) → same logic as (6)
Row 14. Preventers taken out of service this year → same logic as (7)
In-Premises Protection Total at end of year
Same as “Premises Isolation Total at end of year”, but using the in-premise/fixture protection types.
Grand total at end of reporting year
For each device column:
Grand total =
In-Premises Protection Total at end of year + Premises Isolation Total at end of year
⚠️Hazard Type Mapping
⚠️Hazard Type Mapping
⚠️ Part 3C – Cross-Connection Control for Medical Premises Served by the PWS
⚠️ Part 3C – Cross-Connection Control for Medical Premises Served by the PWS
Part 3C of the Washington State Report summarizes cross-connection control data for medical and medical-related facilities served by a Public Water System (PWS).
Each row in Part 3C is determined by the Location Table 13 Hazard Type.
📌 Medical Facility Hazard Type Mapping
📌 Medical Facility Hazard Type Mapping
Hospitals (including psychiatric hospitals and alcohol and drug treatment centers)
Same day surgery centers
Out-patient clinics and offices
Alternative health out-patient clinics and offices
Psychiatric out-patient clinics and offices
Chiropractors
Hospice care centers
Childbirth centers
Kidney dialysis centers
Blood centers
Dental clinics and offices
Nursing homes
Boarding homes
Residential treatment centers
Mortuaries
Morgues and autopsy facilities (not in hospitals)
Veterinarian offices, clinics, and hospitals
Other Medical-Related High Hazard (3C)
Each of the above hazard types appears as a separate row in Part 3C of the report.
⚠️ Exceptions to High-Health Hazard Premises Isolation Requirements
⚠️ Exceptions to High-Health Hazard Premises Isolation Requirements
This section of the Washington State Report generates Green Forms for locations that have assemblies with documented exceptions to mandatory premises isolation.
When a Green Form is created
The report generates a Green Form for a location when all of the following are true:
The location is not deleted
The location has at least one assembly with:
First Recorded On < 1/1/XXXX, and
At least one exception-related field filled out
Each qualifying location receives one Green Form, which includes all assemblies at that location that meet the criteria above.
What appears on the Green Form
Each Green Form includes:
Location information
Location Name
Address (Street, City, State, Postal Code)
Location Table 13 Hazard Type
Assembly information
Assembly Make / Serial Number
Exception details
Exception Evaluated On
Exception Granted On
Exception Expires On
Exception Next Evaluation On
Exception Reason(s)
Exception fields considered by the report
An assembly is considered to have an exception if any of the following fields are populated:
Exception Evaluated On
Exception Granted On
Exception Expires On
Exception Next Eval On
Exception Reason(s)
The report checks the current values of these fields.
It does not evaluate historical changes or audit logs.
⚠️Important notes
Green Forms are generated per location, not per assembly.
Assemblies are included based on their current exception field values, regardless of when the exception was originally granted.
Deleted locations and deleted assemblies are excluded.
⚠️ Common confusion:
Removing values from exception fields will remove the assembly from future Green Forms, even if the exception existed during the reporting year.
Updated Recording with Introduction from Bill Bernier explaining WA ASR Requirements Recorded 02.22.23SwiftComply Specific State Report Training Begins at 56 minutes and 12 seconds
Original Recording: January 2022
