San Diego

Accessibility Tools

  • Check if your spelling is correct, or try removing filters.
  • Remove quotes around phrases to match each word individually: "blue drop" will match less than blue drop.
  • You can require or exclude terms using + and -: big +blue drop will require a match on blue while big blue -drop will exclude results that contain drop.

The Compliance Engine

The San Diego Fire-Rescue Department has instituted a new process for service providers who inspect and test fire protection systems.  Effective 04/15/2020 all compliant and non-compliant fire protection system test reports are required to be electronically submitted to the San Diego Fire-Rescue Department online via The Compliance Engine at www.thecomplianceengine.com.

The San Diego Fire-Rescue Department is dedicated to 100% compliance with the California Fire Code.  This web-based service will aggregate, track and streamline the collection of compliance data of our jurisdiction’s systems.  Property owners will receive timely proactive notifications of their testing requirements and the San Diego Fire-Rescue Department will gain the ability to better mitigate the risk in our community by improving public safety to our citizens. 

All service providers who inspect or test fire protection systems within the city of San Diego jurisdiction are required to register and submit all inspection, test and maintenance (ITM) reports via The Compliance Engine.  All reports must be submitted in accordance with the testing schedule and requirements outlined in the California Fire Code. 

This proven process requires the service provider to pay a nominal filing fee at the time of report submittal; repair reports do not incur a submittal fee. There is no fee to register your company with The Compliance Engine. Once registered, pricing is viewable under AHJ icon. If you are a licensed fire protection system contractor and are not currently registered with Brycer, please register at www.thecomplianceengine.com.

We look forward to partnering with you to better protect and serve our community.  We are confident this will benefit us ALL.

The ITM of the following systems must be submitted utilizing the following form/standard and the frequencies listed in the table below.

Report Type 6-Month Annual 5-Year Form/Standard
Fire Alarm System     NFPA 72
Automatic Fire Sprinkler Systems   CSFM-AES 2
Standpipe   CSFM-AES 3
Fire Pump     CSFM-AES 5
Special Suppression System/Clean Agent/CO2     CSFM-AES 22
Spray Booth     CSFM-AES 7
Private Fire Service Main   CSFM-AES 4
Water Storage Tank   * CSFM - AES 6
Kitchen Hood Suppression System     CSFM-AES 20
Dry Chemical System     CSFM-AES 21
Active Smoke Control System     NFPA 92
Emergency Power Standy System     NFPA 110
Fire Escape     NFPA 80
Fire Doors     NFPA 80
Emergency Responder Radio Coverage System     Manufacturer Specifications

*5-year report may be submitted as an attachment to the annual report on AES 6

Section 1 - General Report Preparation Guidelines

1.1 The table above includes the reports and reporting intervals required to be submitted to SDFD. It does not include all inspection and testing required by the applicable codes and standards
1.2 All reports must be submitted within 14 days of the inspection, testing, or maintenance completion

ITM reports that do not reflect inspection and testing results for all applicable components and devices, in conflict with the corresponding governing code or standard are considered incomplete and shall be categorized as "Deficient", both on the ITM and TCE's digital intake form


Do not submit multiple PDFs for the same ITM report. All pages for the same report, including the cover sheet (i.e. AES 1) shall be provided within the same PDF file 


Multiple fire sprinkler, alarm systems, or hood systems within the same premises/address shall each have a separate ITM report that assigns a system number to each individual system (e.g., Sprinkler Riser #1 or Kitchen Hood #1)


Systems within a complex or campus, sharing the same general street address shall be issued their own ITM report and identified by the number of the building (premise) it serves (444 Broadway; Building # 1)


All forms shall be completed thoroughly and signed by all required parties

1.8 All data fields on the forms shall be completed. No data fields should be left blank

Any data fields that are not applicable to the system being tested / inspected shall be filled with “Not applicable” or “N/A” after being verified


Contractors shall gather and provide all applicable premise contact information on the corresponding TCE contact data entry fields, to ensure proper notifications are generated and delivered to responsible parties

1.11 All deficiencies on ITM forms shall also be entered into TCE deficiencies data fields

All ITM reports that have been rejected by the AHJ shall be revised and re-submitted within 14 days of the rejection date on TCE

1.13 When submitting a deficiency repair report, a file containing repair documentation shall be uploaded by clicking on the "Attach Proof" button. It must be a PDF file. The file must be in the required form.  AES 10 for fire suppression systems

Section 2 - Fire Suppression System Report Preparation Guidelines


Each system and system type shall have their own and separate ITM report. Do not combine multiple system types within the same report (except when using AES forms 2.1, 2.2, 3 & 3.1)

2.2 All corrections and repairs to systems reported on AES forms shall be documented and submitted on an AES 10 form only
2.3 Job numbers on all initial AES inspection and testing forms shall match the job number on the corresponding AES 10 form and vice versa
2.4 ITM reports may be submitted as "Compliant" only when they do not contain any deficiencies

ITM reports listing deficiencies may only be submitted as "Compliant" if/when accompanied by the corresponding "Corrective Action and Repairs Performed" form (AES 10), reflecting all deficiencies as corrected (repaired). The initial ITM report and the AES 10 form shall be uploaded as one PDF file. The AES 10 form reflecting the deficiencies repaired shall be attached as the last page of the uploaded PDF file

Section 3 - Fire Alarm System Report Preparation Guidelines


All fire alarm system inspection and testing reports shall be prepared in the current version of the NFPA 72 form

3.2 All system component tests that document a visual inspection and/or a functional test performed shall also indicate the outcome of the component test (Passed/Failed, etc.). "N/A" comments are not applicable when inspection(s) and/or test(s) are performed or required. "N/A" is only applicable if/when the system test is not required due to the nature of the system and NFPA 72 requirements

Section 4 - Kitchen Fire Suppression System Report Preparation Guidelines

4.1 ITM reports are only accepted on CSFM's AES 20 and AES 10 forms
4.2 ITM reports shall be prepared and submitted separately

Section 5 - System Impairment Reporting


All system impairments shall be reported to the San Diego Fire-Rescue Department immediately. When system impairments are found during inspection or testing, they shall be reported via TCE. When impairments are found outside of periodic inspection and testing, they shall be reported by emailing related information and documentation to THojsack@sandiego.gov

5.2 System impairments are conditions that will prevent a system from activating and /or performing its main function. Please refrain from submitting system impairment reports for conditions that do not actually constitute a system impairment. 

For questions related to the submission of fire system ITM reports to the San Diego Fire-Rescue Department, please call The Compliance Engine Support line at 630-413-9511. Additionally, much of the information needed to accomplish this can be found in the contractors “HELP” section of the TCE website. TCE provides free weekly webinar-style trainings. For questions regarding the guidelines listed above, please contact Tammy Hojsack, Deputy Fire Marshal, The Compliance Engine Manager, at 619-533-4414 or email THojsack@sandiego.gov.