Richmond City Council
July 7, 2026

July 7, 2026
Library and Community Services
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: LaShonda White, Deputy City Manager – Community
Services
Subject: Fiscal Year 2026-27 North Richmond Waste and
Recovery Mitigation Fee Expenditure Plan
FINANCIAL IMPACT: The proposed action will not have an impact on the City’s General Fund. Mitigation Fee revenue is used to cover
the costs incurred by the City and County for activities authorized under the North Richmond Waste and
Recovery Mitigation Fee Expenditure Plan. Funding is
available within the North Richmond Waste Mitigation
Fee Contingency Fund (Fund 1010).

PREVIOUS COUNCIL
ACTION:

June 2025

STATEMENT OF THE
ISSUE:

The North Richmond Waste and Recovery Mitigation Fee
Expenditure Plan requires approval by the Richmond City Council and the Contra Costa County Board of
Supervisors. The plan prioritizes the proposed activities, program services, and the projected revenues derived
from the collection of the Mitigation Fee, to support
efforts of blight reduction and cleanliness in incorporated and unincorporated North Richmond.

RECOMMENDED ACTION: APPROVE the Fiscal Year 2026-2027 North Richmond Waste and Recovery Mitigation Fee Expenditure Plan
identifying the activities authorized to be funded with Mitigation Fee revenue and respective funding
allocations for the period of July 1, 2026, through June 30, 2027, as recommended by the North Richmond
Waste and Recovery Mitigation Fee Joint Expenditure
Planning Committee – Community Services Department
(LaShonda White 510-620-6828).

AGENDA
REPORT
393

July 7, 2026
DISCUSSION:

The North Richmond Waste and Recovery Mitigation Fee Joint Expenditure Planning Committee (Mitigation Committee) was formed for the specific purpose of preparing a North Richmond Waste and Recovery Mitigation Fee Expenditure Plan (Expenditure Plan) to assist the City and County with the administration of funds for the benefit of North Richmond. In accordance with the Memorandum of Understanding, all proposed projects and activities included in the Expenditure Plan require authorization by the Richmond City Council and County Board of Supervisors for consistency with the purpose of mitigation fund use.

New Expenditure Plans and modifications to existing Expenditure Plans must be approved by both the County Board of Supervisors and Richmond City Council to officially authorize the use of North Richmond Waste and Recovery Mitigation Fee funding. The purpose of the North Richmond Waste and Recovery Mitigation Fee is to mitigate designated impacts resulting from the County and City-approved land use permits for the expanded Bulk Material Processing Center located in North Richmond.

At the Mitigation Committee meeting on May 22, 2026, the Mitigation Committee voted to recommend that the County Board of Supervisors and Richmond City Council approve a Fiscal Year 2026-27 Expenditure Plan that allocates funding from July 1, 2026, through June 30, 2027 (Attachment 1).

The recommended FY 2026-27 Expenditure Plan incorporated the following changes:
 Decrease funding for Strategy 2 - Neighborhood Clean-ups  Decrease contingency funding
 All other strategies remained unchanged
All proposed projects were evaluated based on projected outcomes, contributions to the North Richmond community, fiscal management, diversity, and collaboration. The next Mitigation Committee meeting is scheduled for October 16, 2026.

Each new Expenditure Plan must receive final approval from the County Board of Supervisors and Richmond City Council. Expenditure Plans and any associated amendments recommended or approved by the Mitigation Committee only take effect when approved by the County Board of Supervisors and Richmond City Council.

Therefore, approval of the Fiscal Year 2026-27 Expenditure Plan would allow City and County staff to implement programs and projects without interruption. The County Board of Supervisors reviewed and approved the Fiscal Year 2026-27 Expenditure Plan for its June 23, 2026, meeting.

DOCUMENTS ATTACHED:

Attachment 1 – North Richmond Waste & Recovery Mitigation Fee FY 2026-27 Expenditure Plan
394
North Richmond Waste & Recovery Mitigation Fee
2026/2027 Expenditure Plan
The Waste & Recovery Mitigation Fee was established as a result of the Environmental Impact Report (EIR) certified in July 2004 for the WCCSL Bulk Materials Processing Center (BMPC) and Related Actions (Project). The Project involved new and expanded processing and resource recovery operations on both the incorporated and unincorporated area of the Project site, which the EIR concluded would impact the host community. To mitigate this impact Mitigation Measure 4-5 called for a Mitigation Fee to benefit the host community, described as follows:
“Mitigation Fee. The facility operator shall pay a Mitigation Fee of an amount to be determined by the applicable permitting authority(ies) to defray annual costs associated with collection and disposal of illegally dumped waste and associated impacts in North Richmond and adjacent areas. The mitigation fee should be subject to the joint-control of the City and County and should be collected on all solid waste and processible materials received at the facility consistent with the existing mitigation fee collected at the Central IRRF.”
In July 2004, the City of Richmond and Contra Costa County entered into a Memorandum of Understanding (MOU) agreeing to jointly administer Mitigation Fee monies collected from the BMPC for the benefit of the incorporated and unincorporated North Richmond area. This North Richmond Waste & Recovery Mitigation Fee Joint Expenditure Planning Committee (Committee) was formed pursuant to the terms of the MOU for the specific purpose of preparing a recommended Expenditure Plan. This Expenditure Plan provides a means to jointly administer the Mitigation Fee funding for the benefit of the host community, as described in the EIR. The Expenditure Plan is subject to final approval of the Richmond City Council and the Contra Costa County Board of Supervisors.

By approving this Expenditure Plan, the City Council and Board of Supervisors authorize the use of Mitigation Fee funding for only the purposes and in the amounts specified herein. The City and County have each designated their respective staff persons responsible for administering the development and implementation of the approved Expenditure Plan, which includes responsibility for drafting and interpreting Expenditure Plan language. However, the City and County have not delegated to the Committee or to staff the authority to expend funding for purposes not clearly identified in the Expenditure Plan document officially approved by their respective decision-making bodies.

Activities which can be funded in this Expenditure Plan period with the Mitigation Fee amounts specified within this Expenditure Plan are described herein as “Strategies” or “Staff Costs”.

Strategies are categorized as either “Core Services” or “Supplemental Enhancements”. Core Services includes the higher funding priority strategies that most directly address the intended purpose of this City/County approved Mitigation Fee, “to defray annual costs associated with collection and disposal of illegally dumped waste and associated impacts in North Richmond”.

All references to the “Mitigation Fee Primary Funding Area” or “Mitigation Fee Funding Area” pertain to the geographic area shown in the attached map (Attachment 5).

Expenditure Plan Period: July 1, 2026 - June 30, 2027
(unless otherwise specified herein)
395
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 2 of 13 -
BUDGET
The funding allocation amounts included in this document apply to the Expenditure Plan Period specified on the first page unless otherwise specified herein. The total amount of funding allocated in the Expenditure Plan Budget is based on revenue projections provided by the BMPC operator, Republic Service, which are dependent upon multiple variables (e.g. number of tons of recovered materials vs. solid waste, per ton gate rate charged and amount of CPIadjusted per ton Mitigation Fee). Actual Mitigation Fee revenue may deviate from revenue projections provided by Republic and used to prepare this Budget. A “Contingency” line item is included in the Budget to help accommodate variations between projected and actual revenue.

Excess funding allocated to strategies and not expended by the end of each Expenditure Plan period is treated as “roll-over” funding for reallocation in a subsequent Expenditure Plan period.

The Budget includes some line items that are based on fixed costs, however there are other line items which are scalable and/or dependent on utilization thereby providing flexibility to reallocate amounts if and when a significant need is identified. Allocated funding may remain unspent due to under-utilization of a particular program. If the amount allocated to a particular line item is determined to exceed needs based upon usage, the remaining funding can only be reallocated by officially amending the Expenditure Plan. This Expenditure Plan may only be adjusted upon official action taken by both the City and County. Although there has been some interest in allowing flexibility for staff to adjust funding allocations under specific circumstances, the authority to approve or modify the Expenditure Plan rests solely with the City Council and Board of Supervisors.

Annual fiscal year Expenditure Plan cycle is expected to reduce margin of error of Mitigation Fee revenue projections, streamline financial reconciliation/budgeting process and minimize need to amend Expenditure Plans mid-cycle. Amending Expenditure Plans involve administrative burden and costs due to the joint approval needed from both the Richmond City Council and County Board of Supervisors. In order to minimize the amount of funding needed to cover staff costs incurred to amend the Expenditure Plan, staff will only recommend changes to the Expenditure Plan when necessary to address a significant or time-sensitive need. 396
# Expenditure Plan (EP) Strategy
Budget
Allocations
for 2026/2027
1 Bulky Item Pick-ups & Disposal Vouchers $ 2,500.00
2 Neighborhood Clean-ups $ 35,000.00
3 Prevention Services Coordinator $ 50,726.75

4.A. City/County Right-of-Way Pick-ups & Tagging Abatement $ 60,000.00

4.B. City/County Right-of-Way Pick-ups $ 5,000.00
5 Code Enforcement Staff - County $ 91,850.60
6 Illegal Dumping Law Enforcement $ 175,814.30
7 Surveillance Cameras $ -
8 Code Enforcement Staff - City $ 13,000.00
9 Community Services Coordinator $ 90,909.09
10 Community Clean-Up Projects (See Attachment 2) $ 87,000.00 11 North Richmond Green Community Service Programs $ 21,042.00 12 North Richmond Green Campaign $ 24,500.00
13 Garden Projects (See Attachment 4) $ 28,062.13
14 Mobile Tool Lending Library $ 35,540.00
Contingency (10% of Projected Revenue) $ 80,808.44
Subtotal (without Committee Staffing) $ 801,753.31
X Committee Administration/Staffing $ 90,000.00
Total Projected Revenue in 2026/2027 (July 1, 2026 thru June 30, 2027) $ 808,084.39 $ 83,668.92
$ 891,753.31
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee

BUDGET TABLE
Core Services Supplemental Enhancements
Roll-over Funding from Prior EP Cycle(s)
Total 2026/2027 Expenditure Plan Budget
- Page 3 of 13 - 397
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 4 of 13 -

DESCRIPTION OF STRATEGIES RECOMMENDED FOR FUNDING
Funding allocation amounts for each strategy are specified in the Budget table on page

3. The following Strategies describe the activities allowed to be funded with the amounts allocated to each in the Budget (associated allowable agency staff costs are described in the Staff Costs section). Strategies are grouped based on relative funding priority levels and the “Core Services” category contains higher priority Strategies than the “Supplemental Enhancements” category. Higher funding priority Strategies are those which best address the Fee’s intended purpose, “to defray annual costs associated with collection and disposal of illegally dumped waste and associated impacts in North Richmond”).

Level 1 Priority - PRIMARY CORE SERVICES STRATEGIES
• 1 - Bulky Item Pick-ups & Disposal Vouchers
• 2 - Neighborhood Clean-ups
• 4.A. - City/County Right-of-Way Pick-ups & Tagging Abatement • 4.B. - City/County Right-of-Way Pick-ups
• 5 - Code Enforcement Staff – County
• 6 – Illegal Dumping Law Enforcement
• 8 – Code Enforcement Staff – City
Level 2 Priority - SECONDARY CORE SERVICES STRATEGIES
• 3 - Prevention Services Coordinator
• 7 - Surveillance Cameras
Level 3 Priority - PRIMARY SUPPLEMENTAL ENHANCEMENTS STRATEGIES • 9 - Community Services Coordinator
• 10 - Community Clean-up Projects
• 11 - North Richmond Green Community Services Programs • 12 - North Richmond Green Campaign
• 13 - Garden Projects
• 14 - Mobile Tool Lending Library

CORE SERVICES

1. Bulky Item Pick-ups & Disposal Vouchers
Provide residents in the Mitigation Fee Primary Funding Area, who prove eligibility consistent with City/County procedures, with the option of choosing to:
o Request up to one on-call pick-up service per household per calendar year for bulky items that are not accepted in the current on-call clean-ups through Richmond Sanitary Service (RSS), only available to those with an active account with RSS; or
o Request up to twenty four $5 vouchers per household for disposal at Republic’s transfer station on Parr Blvd. per calendar year (vouchers expire 398
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 5 of 13 -
1 Administering agency contracting charge applies ($3,000 per contract) after six months, Mitigation Fees only pay for vouchers that are actually redeemed).
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: City of Richmond
Implementing Entity(ies):

Community Housing Development Corporation (processes requests and issues Disposal Vouchers/arranges Bulky Item Pick-ups)
Republic Services - Golden Bear Transfer Station & Richmond Sanitary Service (reimbursed for Disposal Vouchers redeemed and Bulky Item Pick-ups provided) Reporting/Payment Requirements: Effective July 1, 2012, CHDC and Republic Services shall provide required data pertinent to Strategy 1 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments.

2. Neighborhood Clean-ups
Provide at least one neighborhood and/or creek clean-up event in the Mitigation Fee Funding Area; additional clean-up event may be scheduled as funding allows. [See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: City of Richmond
Implementing Entity(ies):

City Manager’s Office (coordinates scheduling of clean-up dates and associated arrangements in conjunction with partner entities)
Republic Services - Richmond Sanitary Service (reimbursed for providing/servicing clean-up boxes and disposing of debris placed in clean-up boxes) Reporting/Payment Requirements: Effective July 1, 2012, the City Manager’s Office and Republic Services shall provide required data pertinent to Strategy 2 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments (funding transfers).

3. Prevention Services Coordinator
Fund at least a portion of a Prevention Services Coordinator (PSC) position (including salary/benefits/overhead and administering agency contracting charge1) on a contract basis to assist the City and County in implementing Strategy 1 as the point of contact for community members interested in claiming Disposal Vouchers or Bulky-Item Pick ups. Assist community members interested in reporting illegal dumping and seeking referral/resources. Track and report data related to illegally dumped waste collected by Republic Services Hot Spot Crew and handle 399
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 6 of 13 -
associated referrals to applicable public agencies, including right-of-way referrals for Strategy 4. The PSC may also assist City and County with administering funding allocated to selected non-profit organizations under Strategies 10 and 13. [See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: Community Housing Development Corporation (CHDC) (reimbursed actual cost for part-time position that issues Disposal Vouchers/arranges Bulky Item Pick-ups)
Reporting/Payment Requirements: Effective July 1, 2012, CHDC shall provide required data pertinent to Strategy 1 and Strategy 3 based upon the strategyspecific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments.

4.A. City/County Right-of-Way Pick-ups & Tagging Abatement Fund consolidated pick-up program (including personnel, mileage, equipment rental and administrative costs) for removal of illegal dumping and tagging abatement in the public right-of-way located within the unincorporated & incorporated Mitigation Fee Primary Funding Area. Additional tasks would include identifying potential sites for Strategy 10 Clean-Up Projects. Funding is intended to pay for removal of illegal dumping that occurs as a result of referrals from the Prevention Services Coordinator for items/debris not collected by the designated Republic Services Hot Spot Route crew.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: City of Richmond
Implementing Entity: Richmond Public Works Department’s Abatement Division Reporting/Payment Requirements: Effective July 1, 2012, the Richmond Public Works Department’s Abatement Division shall provide required data pertinent to Strategy 4.A. based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMFfunded payments (funding transfers).

4.B. City/County Right-of-Way Pick-ups
Fund consolidated pick-up program (including personnel, mileage, equipment rental and administrative costs) for removal of illegal dumping in the public right-ofway located within the unincorporated & incorporated Mitigation Fee Primary Funding Area. Additional tasks would include identifying potential sites for Strategy 10 Clean-Up Projects. Funding is intended to pay for removal of illegal dumping that occurs as a result of referrals from the Prevention Services Coordinator for items/debris not collected by the designated Republic Services Hot Spot Route crew.
400
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 7 of 13 -
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: Republic Services
Reporting/Payment Requirements: Effective July 1, 2022, Contra Costa County’s Department of Public Works shall provide required data pertinent to Strategy 4.B. based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments (funding transfers).

5. Code Enforcement Staff - County
Fund at least a portion of County code enforcement position (including salary/benefits and related vehicle and equipment costs), to assist with vacant/ abandoned lot abatements and fencing as well as other health/building/zoning violations related to illegal dumping and blight throughout the unincorporated Mitigation Funding Area. Additional tasks would include identifying potential sites for Strategy 10 Clean-Up Projects.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: County Department of Conservation & Development’s Building Inspection Division
Reporting/Payment Requirements: Effective July 1, 2012, the County Department of Conservation & Development’s Building Inspection Division shall provide required data pertinent to Strategy 5 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments (funding transfers).

6. Illegal Dumping Law Enforcement
Fund majority of a full-time Sheriff Deputy (between approximately 90-100% of salary/benefits, overtime, uniform and related cell phone, equipment, and vehicle costs) to assist with law enforcement investigations and patrols to combat illegal dumping within the Mitigation Fee Primary Funding Area. Additional tasks would include identifying potential sites for Strategy 10 Clean-Up Projects. [See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: County Sheriff’s Office
Reporting/Payment Requirements: Effective July 1, 2012, the County Sheriff’s Office shall provide required data pertinent to this Strategy based upon the 401
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 8 of 13 -
strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments (funding transfers).

7. Surveillance Cameras
Fund the cost of cameras, camera infrastructure, camera signage and costs related to monitoring, maintenance, warranty, repair & relocation of surveillance camera system equipment within the Mitigation Fee Primary Funding Area.

Cameras will be used to assist the dedicated Illegal Dumping Law Enforcement officer prevent dumping in targeting specific locations where illegal dumping occurs most regularly.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity(ies):

Richmond Police Department (operate, move and maintain eight Pan-Tilt-Zoom wireless video surveillance cameras and associated camera system infrastructure throughout NR -AND- install/clean/move FlashCam cameras located within the incorporated NR area if funding is available)
County Sheriff’s Department (coordinate monitoring of FlashCams or other camera systems located throughout NR and identify/request relocation of surveillance cameras throughout NR as needed)
County Public Works Department (install/clean/move FlashCam or other camera systems cameras located within the unincorporated NR area upon request if funding is available)
Reporting/Payment Requirements: Effective July 1, 2012, each Implementing Entity shall provide required data pertinent to each entity’s applicable Strategy 7 responsibilities based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMFfunded payments (funding transfers) now or in the future.

8. Code Enforcement Staff - City
Fund at least a portion of City code enforcement position (including salary/benefits and related vehicle and equipment costs), to assist with vacant/ abandoned lot abatements and fencing as well as other health/building/zoning violations related to illegal dumping and blight throughout the incorporated Mitigation Funding Area.

Additional tasks would include identifying potential sites for Strategy 10 Clean-Up Projects.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: City of Richmond
Implementing Entity: City Department of Infrastructure Maintenance & Operations 402
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 9 of 13 -
Reporting/Payment Requirements: Effective July 1, 2020, the City Department of Infrastructure Maintenance & Operations shall provide required data pertinent to Strategy 8 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMFfunded payments (funding transfers).

SUPPLEMENTAL ENHANCEMENTS

9. Community Services Coordinator
Fund at least a portion of a Community Services Coordinator (CSC) position to be staffed on a contract basis (including salary/benefits/overhead and administering agency contracting charge2). The CSC shall:
• serve as a link between the community of North Richmond, the City of Richmond, and Contra Costa County for issues related to beautification, illegal dumping, and blight using referral process identified by the City and County;
• coordinate outreach activities related to illegal dumping and beautification within the Primary Funding area, as specified by the City/County, including North Richmond Green community service programs and outreach activities described under Strategies 11 & 12; and
• Identifying potential sites for Strategy 10 Clean-Up Projects. • be bilingual in order to assist with Spanish translation as needed. [See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: Community Housing Development Corporation (CHDC).

Reporting/Payment Requirements: CHDC shall provide required data pertinent to Strategies 9, 11 & 12 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments.

10. Community Clean-up Projects
Fund the implementation, oversight and administering agency contracting charges3 of community clean-up projects with specific focus on reducing blight. Community clean-up projects may involve the removal of debris and/or landscaping maintenance. Sites to be cleaned shall be in the Mitigation Fee Funding area and designated by the Administering Agency. The number of sites to be cleaned will be determined by the amount of funding allocated.
2 Administering agency contracting charge is $3,000 per contract. 3 Administering agency contracting charge is $3,000 per contract entered into by the County and up to 20% of the per project funding allocation (as described in the “Administering Agency” section). 403
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 10 of 13 - 4 Administering agency contracting charge applies ($3,000 per contract) A breakdown of contracting costs and amount awarded to the Implementing Entity is contained in the Community Clean-up Project Table included as Attachment 2.

Up to 15% of the Implementing Entity’s Award Amount in Attachment 2 may be used for a fiscal sponsor or administrative oversight.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County. Community Housing Development Corporation (CHDC) may under contract with the County as an Administering Agency, administer Community Clean-Up Project contracts funded under this Strategy. CHDC shall use no more than twenty (20) percent (%) of the total amount awarded to Community Clean-Up Projects (after subtracting City/County contracting cost) listed in Attachment 2 to oversee implementation, including facilitating review/assessment of reports’ and deliverables. Payments to Implementing Entities for Community Clean-Up Projects shall not be issued by CHDC without the written approval of City and County Committee Staff.

Implementing Entity: See Community Clean-up Projects Table in Attachment 2 Reporting/Payment Requirements: Any Community Clean-Up Projects shall be subject to the Reporting & Invoicing Requirements specified in the template Memorandum of Understanding included in Attachment 1. Attachment 1 only applies to Community Clean-Up Project contracts with the Implementing Entities.

The County will issue advance payments to CHDC, as needed, to ensure there is adequate funding available for payments requested by Implementing Entities if and when authorized by City and County Staff. Additionally, CHDC would be subject to contractual payment and reporting provisions that differ from those in Attachment 1 due to the nature of the services to be provided.

11. North Richmond Green Community Services Programs
Fund the following North Richmond Green programs on a contract basis4 to the extent the specific details submitted are determined to align with the purpose of the Mitigation Fee and Expenditure Plan:
• NR Little League Baseball Program - Includes cost of registration and uniforms with customized North Richmond Green patches for up to 5-6 teams, season kick-off event/parade, equipment, stipends for game monitoring and oversight, food and transportation.
• NR Youth Twilight Basketball Program - Includes cost of registration and uniforms with North Richmond Green patches for up to 5-6 teams, equipment, stipends for game monitoring and oversight, food and transportation. • NR Youth Soccer Program - Includes cost of registration and uniforms with North Richmond Green patches for up to 5-6 teams, equipment, stipends for game monitoring and oversight, food and transportation. • NR Eco Workshops & Beautification Projects – Eco Workshops and Beautification Projects include school gardens, recycling efforts, beach/creek/neighborhood cleanups and ecological field trips. May fund the cost of materials, transportation and fees 404
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 11 of 13 -
5 Administering agency contracting charge applies ($3,000 per contract) associated with pre-approved community beautification projects such landscaping and murals.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: Community Housing Development Corporation (CHDC) Reporting/Payment Requirements: CHDC shall provide required data pertinent to Strategies 9, 11 & 12 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments.

12. North Richmond Green Campaign
Fund the design, printing and/or distribution of education and outreach materials on a contract basis5 which must align with the purpose of the Mitigation Fee and Expenditure Plan and be pre-approved by Committee Staff. Outreach materials must include “Jointly funded by City of Richmond & Contra Costa County” unless otherwise specified herein. Outreach materials may be any of the types specified below, however must clearly intend to directly:
• Inform the community about Mitigation Fee funded programs/efforts, • Increase participation in Mitigation funded programs/efforts, • Reduce illegal dumping and blight in the Mitigation Fee Funding Area, and/or • Promote beautification in the Mitigation Fee Funding Area.

The following type of outreach material expenditures may be funded if reviewed and pre-approved by Committee Staff:
• STIPENDS – Pay local community members (youth and adults) to distribute printed outreach materials door-to-door to promote mitigation-funded strategies (Jointly Funded text not applicable to stipend expenses, only materials) • HANDOUTS/MAILERS – Newsletters, flyers, brochures or other documents intended to be handed out or mailed to local residents/organizations. • T-SHIRTS - Shirts shall include the NRGreen.org website to encourage people to learn more about Mitigation funded programs/efforts (local phone number should also be included when possible, however inclusion of Jointly Funded text may not be required)
• NR GREEN FESTIVAL – Event held once per year and generally include information booths to raise awareness about mitigation-funded efforts and other local beautification efforts as well as fun activities for kids and food.

Materials promoting the event shall include the NRGreen.org website as well as a local phone number.
• SIGNAGE – Printed or manufactured signage, which includes promotional banners for local events/parades, which should include the NRGreen.org website for Community members to learn more about Mitigation funded programs/efforts. Repair, replacement and removal of NRMF-funded Light Pole Banners.
405
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 12 of 13 -
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agency: Contra Costa County
Implementing Entity: Community Housing Development Corporation (CHDC) Reporting/Payment Requirements: CHDC shall provide required data pertinent to Strategies 9, 11 & 12 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments.

13. Garden Projects
Fund the implementation, oversight and administering agency contracting charges6 of Garden Projects as further described below.

Community Garden Projects: Fund on-going maintenance and up-keep of existing community gardens within the Primary Funding Area. The projects selected under this Strategy have been funded on an on-going basis.

Details, including recommended allocation amounts, for Projects are included in Attachment 4. Up to 15% of the Non-Profit Implementer Award Amount specified in Attachment 4 may be used for administrative oversite.
[See “Staff Costs” section for agency activities that may also be funded under this Strategy.] Administering Agencies: Contra Costa County. Community Housing Development Corporation (CHDC) may under contract with the County as the Administering Agency, administer Garden Project contracts funded under this Strategy. CHDC shall use no more than twenty (20) percent (%) of the total amount awarded to Projects (after subtracting City/County contracting cost) to oversee implementation, including facilitating review/assessment of reports and deliverables. Payments to Implementing Entities for Garden Projects shall not be issued by CHDC without the written approval of both City and County Committee Staff.

Implementing Entity: See Garden Projects Table in Attachment 4 Reporting/Payment Requirements: Any Garden Project contracts issued or amended by the City/County shall incorporate Reporting & Invoicing Requirements equivalent with those shown in Attachment 3. Garden Project contracts being administered by CHDC on behalf of the County shall also incorporate Reporting & Invoicing Requirements equivalent with those shown in Attachment 3. Attachment 3 only applies to the Garden Project contracts with the Implementing Entities.

CHDC would be subject to contractual payment and reporting provisions that differ 6 Administering agency contracting charge is $3,000 per contract entered into by the County and up to 20% of the per project funding allocation (as described in the “Administering Agency” section). 406
2026/2027 Expenditure Plan - North Richmond Waste & Recovery Mitigation Fee - Page 13 of 13 -
from those in Attachment 3 due to the nature of the services to be provided. The County will issue advance payments to CHDC, as needed, to ensure there is adequate funding available to payments requested by Implementing Entities if and when authorized by City and County Staff.

14. Mobile Tool Lending Library
Fund the development, implementation, and on-going maintenance of a mobile tool lending library that is accessible to the public within the Mitigation Fee Primary Funding Area at least once a week. Funding is intended to pay for the purchase of educational material, tools, a cell phone for the library, costs related to the tool lending system & trailer/tool maintenance, and personnel/labor.

Administering Agency: City of Richmond
Implementing Entity: City of Richmond Community Services Department Reporting/Payment Requirements: Effective July 1, 2020, the City of Richmond Community Services Department shall provide required data pertinent to Strategy 14 based upon the strategy-specific invoicing/reporting requirements and schedule developed/maintained by Committee Staff in order to receive NRMF-funded payments (funding transfers).

STAFF COSTS
Committee Administration/Staffing Funding: The funding allocated for Committee Administration/Staffing may not be adequate to cover the full cost of staff time necessary for jointly staffing the North Richmond Waste & Recovery Mitigation Fee Joint Expenditure Planning Committee as well as developing, administering and overseeing this Expenditure Plan for the specified period. Supplemental funding allocation may be necessary upon determining actual costs exceed the amount budgeted to cover the intended City/County costs for joint staffing.

Strategy-Specific Funding: The cost of City/County staff time spent providing direct implementation assistance and/or coordination for specific Strategies may be covered with a portion of the NRMF funding budgeted for each applicable Strategy. Additionally, a portion of the NRMF funding budgeted for Strategies will be used to pay fixed administering agency contracting charge for each applicable contract (Currently $3,000 per contract. An additional $3,000 may be added to a contract amendment to add additional funding or nonprofits to a contract during an existing contract cycle) unless otherwise specified herein.

G:\Conservation\Deidra\Illegal Dumping\BMPC Mitigation Fee Committee\_EPs\2025-2026\2025-26 EP_Clean.doc 407

TEMPLATE MEMORANDUM OF UNDERSTANDING BETWEEN
AND

COMMUNITY HOUSING DEVELOPMENT CORPORATION
This is an agreement made and executed on _______ between Community Housing Development Corporation (CHDC) and _______ (Contractor). This contract will remain in effect for the time period identified in the TERM section of the agreement.

OVERVIEW:

The _________ North Richmond Mitigation Fee (NRMF) Expenditure Plan approved by the Board of Supervisors in ______ and Richmond City Council in _______ allocates a total of $_______to the Contractor for the disbursement of funds within Strategy 10 to complete Clean-Up Project(s) in the North Richmond Mitigation Area.

TERM: The term of this agreement begins on _______ and ends on _______. Contractor will complete all work performed under this agreement not later than ________. Invoices submitted for work performed before or after this specified term and invoices submitted after _______will not be paid.

I. Contractor’s Obligations
The Contractor shall administer the _________, as described herein for an amount not to exceed $_____involving the following activities:

A. Recruit and Hire up to four (4) workers

1. Contractor will develop and publicize the job announcements. Job announcements shall contain, “Jointly funded by The City of Richmond & Contra Costa County” language.

2. Contractor will interview, select and hire up to four workers.

3. Contractor will host training for new hires that discusses the proper procedures of disposal of hazardous waste (televisions, phones, batteries, tires, paint etc.).

Task A - Deliverables:

1. Documentation of publicized job announcement in English/Spanish with required jointly funded language.

2. Documentation of hiring papers.

B. Clean up to _____(_) North Richmond Sites Approved by the County

1. Contractor shall select North Richmond addresses provided by the County or City to be cleaned during each clean up. Community clean-up projects may involve the removal of debris and/or landscaping maintenance.
a. Addresses provided by the County or City will include a description of debris for removal and/or landscaping needs.
b. Addresses provided by the County or City shall only be selected once for clean-up unless directed otherwise by County Staff.

2. Contractor will confirm with the County the address for cleanup one week and provide clear written procedures for the proper disposal of all waste types previously described at each clean-up site, including Attachment 1
408

waste that is recyclable, hazardous or requires special handling. Procedures shall be submitted and approved by the County before the site is cleaned up.

3. Contractor shall make arrangements in advance with the appropriate partners for the proper removal, recycling, composting or disposal of the debris identified in the area to be cleaned, including materials that require special handling such as tires, hazardous/universal wastes, appliances, and medical sharps/waste.

4. Contractor shall document approximate quantities (count, volume or weight) of each type of material/debris removed from the area during clean-up, using a log or other method agreed upon in advance.

5. Contractor shall demonstrate how the materials/debris removed during the clean-up were transported and where each type was properly recycled, composted or disposed.

Task B - Deliverables:

1. Documentation of disposal procedures approved by the County for each confirmed clean-up address.

2. Before photos of the entire site before the material/debris has been cleaned up.

3. Completed Contractor’s Log identifying the types and amount of material/debris removed.

4. After photos of the entire site after it has been cleaned up. Contractor shall strive to take After photos from the same vantage points as the Before photos.

5. Documentation demonstrating that the material/debris removed was properly disposed or recycled. If debris removed during the clean-up is disposed of in existing containers that are routinely serviced by Republic Services, Contractor shall submit copy of an invoice or letter from Republic Services confirming what collection services were being provided at the disposal location during the applicable timeframe.

For any in-kind hauling/disposal service offered by partner organizations or agencies, contractor may submit written communication identifying what was picked up by whom and where it was taken (e.g. email message from the Parks District confirming that yard debris that was placed in tarps and set-out at agreed upon location was placed in designated green waste bin on the District’s property or transported to a specified compost facility). Alternatively, if disposal services are provided in the form of debris box donation(s) from Republic Services, contractor may submit written communication confirming donation.

C. Attend Community Meetings and Events

1. Attend one North Richmond Green meeting(s) per quarter (quarterly periods end on December 31st, March 31st and June 30th).
a. No portion of the Quarterly Meeting Attendance budget line item will be paid to Contractor unless Contractor submits written evidence proving Contractor representative attended at least one monthly North Richmond Green Meeting during the applicable quarter.

Task C - Deliverables:

1. Documented attendance via minutes or copies of sign-in sheets of North Richmond Green meetings D. Reporting & Invoicing

1. Submit invoices and the required supporting documentation (including applicable required Deliverables and completed Progress Reports as specified in Section III. Payment Provisions) for each calendar month, and not later than 30 days after the end of the applicable monthly period. The Reporting and Invoicing budget line items are intended to ensure timely submittal of invoices and required supporting 409

documentation. No portion of the Invoicing budget line item will be paid to Contractor for invoices submitted late, or without the required documentation or completed Progress Report.

Task D- Deliverables:

1. Complete monthly invoices on time for all tasks completed, accompanied by all required deliverables (including completed Progress Report or Final Progress Report). If Contractor does not provide a timely and complete invoice with all deliverables required for applicable tasks outlined on the invoice, as specified herein, no later than 30 days after the end of the applicable monthly period, the Contractor shall forfeit the $100 allocated for each applicable invoice period. Contractor may not use any funding specifically allocated for Reporting and Invoicing for any other purpose

2. Completed Progress Report addressing activities that occurred during the corresponding invoice period (except for the final invoice) consistent with Section III.3.a.

3. Completed Final Progress Report addressing the entire project to be submitted with the final invoice consistent with Section III.3.a.
410

E. Eligible Costs:

Eligible costs consistent with the below table can only be reimbursed if included on invoices in conformance with the payment provisions and submitted prior to _______.

Budget Line Items by
Task/Deliverable Quantity Payment
per Unit
Total
Payments Budget Amount
A. Recruit and hire up to four (4) workers $ 1,750
Deliverable 1 - Recruitment
Documentation 1 each $350 $350
Deliverable 2 - Hiring
Documentation 4 each $350 $1,400
B. Clean-up up to _____(_) designated locations in the
NRMF Funding Area $ _______
Deliverable 1 - Procedures _ each $200 $1600-
Deliverable 2 - Before
Photos _ each $300 $2,400-
Deliverable 3 - Contractors
Log _ each $400 $3,200-
Deliverable 4 - After Photos _ each $300 $2,400-
Deliverable 5 - Disposal
Documentation _ each $600 $4,800-
C. Attend North Richmond Green Meetings $ 750
Deliverable 1 - NR Green
Meetings 3 each $250 $750
D. Reporting and Invoicing $ 2,500
Deliverable 1 - Timely &
Complete Invoice 9 each $100 $900
Deliverable 2 - Progress
Reports
8 each $150 $1,200
Deliverable 3 - Final
Progress Report 1 each $400 $400
SUBTOTAL $ ______
Fiscal Agent (10% of amount
invoiced) $0

TOTAL BUDGET &
ALLOWABLE PAYMENTS $ ______
II. CHDC’s Obligations
411

Subject to the payment limit of $______CHDC shall reimburse Contractor for eligible costs described in the previous section where such are incurred in the performance of work under the contract, subject to the below Payment Provisions. CHDC will disburse Contractor funds only after receiving written approval by County authorizing the disbursement of the Contractor grant funds based on approved budget, approved advance and request for reimbursement.

III. Payment Provisions
Contractor shall submit invoices and required deliverables on a monthly basis consistent with the amounts and frequency specified in Section I.E -Eligible Costs, which together may not total more than $______. Contractor will only receive payment for eligible costs incurred for work performed during the term of this contract which are itemized on invoices substantiated with adequate supporting documentation. Invoices submitted after July 30, - _______ will not be paid.

1. Advanced Payments: In order to receive any potential advance payment, such must be authorized for the specified project in Attachment ____ of the Expenditure Plan approved by the Board of Supervisors and The City of Richmond. Advance payment is limited to no more than ten (10) percent (%) of the approved implemented Entity Award for the Project. Contractor shall submit a written request to CHDC for approval by City and County Committee staff detailing the reason(s) advance payment is necessary and itemizing each specific cost that the requested advance payment amount would pay for and how such costs will aid in the completion of each applicable required task. Advance payment requests must be submitted prior to any other invoice. If an advance payment is issued, Contractor shall not be eligible for an additional payment until enough required deliverables have been approved to offset the amount paid in advance.

2. Partial Payments: The Contracting entity (City of County) may authorize partial payment to Contractor for submittal of incomplete deliverables if solely incomplete due to unusual and unforeseen circumstances beyond the control of the Contractor. Contractor must submit written request asking to receive payment for incomplete deliverable containing an explanation as to what factors beyond the Contractor’s control specifically precluded the Contractor from submitting the completed deliverable and why such could not have been foreseen or avoided by Contractor.

3. Invoices: Invoices shall be submitted monthly, no later than 30 days after the end of the applicable monthly period and contain the following information in sufficient detail and be submitted in a form which adequately demonstrates consistency with this contract. Invoices shall be accompanied by the applicable deliverables.
a. Itemization of any tasks completed during the applicable calendar month for which completed deliverables are submitted and associated payment is being requested.

4. Supported Documentation: The following required supporting documentation must be submitted with invoices when applicable as described below.
412

a. Every invoice must be accompanied by a Progress Report, with the exception of the final invoice which must be accompanied by a Final Report. Both types of Reports must contain all of the information specified in the City/County provided Report templates, as well as any applicable details specified above in Section I. Contractor’s Obligations.
b. All applicable Deliverables associated with the tasks and requested payment amounts itemized on each monthly invoice.

SIGNATURES: Executed on the dates and by the persons named below.

Date: ____________________________ Date: _________________________________

By: _________________________________ By: ___________________________________ Name: _______________________________ Name: ________________________________ IV. Conflict of Interest
By signing below, Contractor agrees not to employ, subcontract with, or make payment to any person (employees and stipend recipients), for the purpose of implementing this Project, that is at the same time employed by Contra Costa County, the City of Richmond or any entity that receives NRMF funding from the County or the City of Richmond, or serves on the NRMF Committee, except upon written approval by the Department of Conservation and Development Director or his designee.

Signature:________________________________________________________________ Name: __________________________________________________________________ Title: ___________________________________________________________________ Date: ___________________________
G:\Conservation\Deidra\Illegal Dumping\BMPC Mitigation Fee Committee\_EPs\2021-2022 Exp Plan\Attachment 1_Clean_V2.doc 413
Implementing Entity /
Fiscal Sponsor
(if applicable)
Project Title
Advance
Payment
Allowed
(Up to 10% of
Implementer
Award Amount)
Requested
Amount
Total Award
Amount
County
Contracting
Costs2
CHDC
Contracting
Cost (20%) to
Manage NonProfits2
Non-Profit
Implementer
Award Amount
for Project
Notes
Social Progress Inc. Brighter Beginnings in North
Richmond Yes $ 29,999.76 $ 25,250.00 $ 1,000.00 $ 4,850.00 $ 19,400.00 SOS! Richmond SOS! Richmond Yes $ 75,000.00 $ 36,500.00 $ 1,000.00 $ 7,100.00 $ 28,400.00 Men & Women of Valor Community Working Together Yes $ 20,000.00 $ 25,250.00 $ 1,000.00 $ 4,850.00 $ 19,400.00 Total Funding Requested/Allocated $ 124,999.76 $ 87,000.00 $ 3,000.00 $ 16,800.00 $ 67,200.00 1 Funding Request Proposal released on February 9, 2018 by Committee Staff and Proposals submitted by eligible non-profit organizations and Agencies on March 6, 2018. Funding Proposal Application received by Men & Women of Valor was the wrong application. At their meeting on March 23, 2018, the NRMF Committee gave Men & Women of Valor 30 days to re-submit their application to the NRMF Committee using the correct application and submittal requirements. On April 22, Committee staff received the correct Funding Proposal application. The Men & Women of Valor Proposal application was considered at the NRMF Committee Meeting on June 8th and selected for funding.
2 Costs to have 3rd party organization (CHDC) manage and oversee contracts with Organizations selected for funding is up to twenty (20) percent (%) of award amount after first taking out City/County Contracting cost for $3,000 for City/County to contract directly with CHDC to have CHDC administer non-profit contracts.

Attachment 2 - Community Clean-up Projects Table (Strategy 10) 2026/27 Expenditure Plan Funding Allocations for Projects recommended for City/County approval by the North Richmond Mitigation Fee Committee A total of $87,000.00 is recommended to be allocated in the 2026/2027 Expenditure Plan for Community Clean-up Projects (Strategy 10). Two of the three entities below were previously selected by the Committee based on a Funding Request Proposal process conducted in 2018.1 The third entity, SOS! Richmond, was added per Committee direction at the October 16, 2020 meeting.

Community Clean-up Projects Recommended for Funding in 2026/2027 414

Garden Project Reporting and Invoicing Requirements
Substantially equivalent language to be included in all NRMF-funded Community Project Agreements/Amendments
Agreements providing for payments using funding allocated for Community Projects must include provisions that address the requirements contained herein. Contractor shall submit Progress Reports covering each invoice period, using a City/County provided template in conjunction with each monthly invoice in order to be eligible for payment. Contractor shall monitor, document, and report all Project activities associated with the tasks and deliverables described in the agreement and any eligible Project costs for which reimbursement will be requested. Upon completion of work or the end of the contract’s term, Contractor shall submit a Final Report, using a City/County provided template similar to the attached, in conjunction with the final invoice.

Task Deliverables
The agreement shall assign a dollar amount for each deliverable within each task. Contractor shall only be paid for completed deliverables submitted with all associated supporting documentation. The agreement may include assignment of one dollar amount to multiple deliverables for a specific task when appropriate to substantiate completion of the required task.

The Contracting entity (City of County) may authorize partial payment to Contractor for submittal of incomplete deliverables if solely incomplete due to unusual and unforeseen circumstances beyond the control of the Contractor. Contractor must submit written request asking to receive payment for incomplete deliverable containing an explanation as to what factors beyond the Contractor’s control specifically precluded the Contractor from submitting the completed deliverable and why such could not have been foreseen or avoided by Contractor.

Timely Submittal of Invoices
A separate Reporting & Invoicing budget line item shall be included in the agreement to facilitate timely submittal of invoices, progress reports and other deliverables. Submittal of monthly invoices shall be included as a deliverable and the exact amount that is payable upon timely submittal of each invoice complete with all required supporting documentation shall be specified.

The agreement shall provide that no portion of the Reporting & Invoicing budget line item be paid to Contractor for invoices submitted beyond 30 days of any monthly invoice period, or without the required documentation including completed Progress Reports.

Pre-approval Required for Supplies and Materials
Unless the exact supplies and materials are specified as preauthorized in the Agreement, Contractor shall obtain pre-approval from the Contracting entity (City or County) prior to incurring supplies and materials expenses for which reimbursement will be requested. To request pre-approval, contractor shall provide written request identifying all proposed supplies and materials as well as an explanation demonstrating its reasonable cost and how said items will aid in the completion of each applicable required task.

Attendance of Community Meetings and Events
Contractor shall attend one North Richmond Green meeting per quarter during the contract period. Documentation substantiating attendance of required meetings shall be included as a deliverable for this task and be included with all applicable monthly invoice(s).

Acknowledgment Required on Outreach & Promotional Materials Attachment 3
415

Any printed outreach materials or promotional items must include “Jointly funded by City of Richmond & Contra Costa County”, with the exception of T-Shirts, which Contractor may request Contracting entity pre-approve to include only the NRGreen.org website address.

Authorized Advance Payments
In order to receive any potential payment in advance, such must be authorized for the specified Project in Attachment 2 or Attachment 3 of the Expenditure Plan approved by both the County Board of Supervisors and Richmond City Council. No Contractor authorized for advance payment may receive more than ten (10) percent (%) of the approved Implementing Entity Award for this Project. In order to receive any advance payment(s) provided for in the City and County approved Expenditure Plan, the Contractor shall submit a written request to both the City and County Committee Staff detailing the reason(s) advance payment is necessary and itemizing each specific cost that the requested advance payment amount (not to exceed 10% of total award) would pay for and how such costs will aid in the completion of each applicable required task.

Conflict of Interest Provisions
Contractor shall not employ, subcontract with, or make payment to any person, for the purpose of implementing a specified Project in Attachment 2 or Attachment 3 of the Expenditure Plan that is at the same time employed by Contra Costa County, City of Richmond or any entity that receives Expenditure Plan funding from the County or the City of Richmond, except upon written approval by the Contracting entity (either City or County).

Payment Provisions
Contractor shall submit invoices and required deliverables on a monthly basis consistent with the amounts and frequency contained in the “Eligible Costs” Section, which together may not total more than $ (enter applicable contract amount). Contractor will only receive payment for eligible costs if such amounts are included on invoices adequately substantiated with required supporting documentation that are all submitted to the Contracting entity on or before July 30th.

Invoices or portions thereof for which required supporting documentation has not been submitted by July 30th (or 30 days after any contract end date prior to June 30th) shall not be eligible for payment.

1. Invoices: Invoices shall be submitted monthly and contain the following information in sufficient detail and be submitted in a form, which adequately demonstrates consistency with the “Service Plan” specified in the contract. Invoices shall be accompanied by the applicable deliverables.
a. Itemization of any tasks partially or fully completed during the applicable calendar month for which completed deliverables are submitted and associated deliverable payment amount is being requested.

2. Supporting Documentation: The following required supporting documentation must be submitted with invoices when applicable as described below. a. Every invoice must be accompanied by a Progress Report, with the exception of the final invoice, which must be accompanied by a Final Report. Both types of Reports must contain all of the information specified in the City/County provided Report templates, as well as any applicable details specified in the Service Plan as a Contractor’s Obligation.
416

b. All applicable required deliverables associated with the requested payment amounts itemized on each monthly invoice.

City/County shall review submitted invoices and supporting documentation within a reasonable period of time and remit payment to Contractor promptly upon determining the purpose and amount of payment requested are authorized under the Agreement.

G:\Conservation\Deidra\Illegal Dumping\BMPC Mitigation Fee Committee\_EPs\2021-2022 Exp Plan\Attachment 3.doc 417
Implementing Entity /
Fiscal Sponsor
(if applicable)
Project Title
Advance Payment
Allowed
(Up to 10% of
Implementer Award
Amount)
Requested
Amount
Total Award
Amount
County
Contracting
Costs2
CHDC
Contracting
Cost (20%) to
Manage NonProfits2
Non-Profit
Implementer
Award
Amount for
Project
Notes
Watershed Project Shields Reid Habitat Garden No $ 29,986.25 $ 28,062.13 $ 3,000.00 $ 5,012.43 $ 20,049.70 Communities United Restoring Mother
Earth (CURME) /
Greater Richmond Interfaith Program
Lots of Crops No $ 15,092.00 $ - $ - $ - $ -
Total Funding Requested/Allocation Recommended $ 45,078.25 $ 28,062.13 3,000.00 5,012.43 $ 20,049.70 1 Funding Request Proposal released on February 9, 2018 by Committee Staff and Proposals submitted by eligible non-profit organizations and Agencies on March 6, 2018.

Attachment 4 - Garden Projects (Strategy 13)
2026/2027 Funding Allocations for Garden Projects
recommended for City/County approval by the North Richmond Mitigation Fee Committee A total allocation of $28,062.13 is recommended to be allocated in the 2026/2027 Expenditure Plan for Garden Projects.The following entities were previously selected by the Committee based on a Funding Request Proposal process conducted in 2018.1 Garden Projects Recommended for Funding in 2026/2027
2 Costs to have 3rd party organization (CHDC) manage and oversee contracts with Organizations selected for funding is up to twenty (20) percent (%) of award amount after first taking out City/County Contracting cost of $3,000 for City/County to contract directly with CHDC to have CHDC administer non-profit contracts. 418
Southern boundary

shown on back side Attachment 5
419
Hens el y St
Garrard
Blvd
Richmond Pkwy
7th St
Hensley St
Duboce Ave
Sanford Ave
t S ht 8
Willard Ave
t S ht 9
t Skr oY
Vernon Ave
t Str ebli F
Lincoln Ave
t Syr ett aB
Factory S
N
t
Castro St
t Syesl eK
t S ht 6
Triangle Ct
t S oeL
t S ht 01
Ams at n Ln
t Syrr eh C
Lucas Ave
Presco Ln
Joy Ave
Enterprise Ave
Fac ot
yr St
Committee Approved Additions to Primary Mitigation Funding Area Market Ave
Chesley Ave
d
vl Bllir muR
Legend
July 2006 Additiion to Mitigatin Funding Area
Primary Mitigation Funding Area
² 0 130 260 390 520 65
Feet
420

July 7, 2026
Fire Department
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: Aaron Osorio, Fire Chief
Rico Rinco, Deputy Fire Chief
Den Mark Marcelo, Administrative Services Coordinator
Subject: Contract with Definitive Networks, Inc. for Emergency Medical Services Data Management Support
FINANCIAL IMPACT: The proposed three-year not-to-exceed cost of $216,834 is funded through the General Fund and the Fire
Department’s Emergency Medical Services Fund
(Measure H). Funding is included within the approved
Fiscal Year 2025-2026 Fire Department budget and will
be budgeted accordingly in subsequent fiscal years
(Account Strings: 01204022-400201;
11702022-400201-2A102; 10706022-400201).

PREVIOUS COUNCIL
ACTION:

None.

STATEMENT OF THE
ISSUE:

The Emergency Medical Care Personnel Act requires the
Richmond Fire Department (“Department”) to establish
procedures for documenting, collecting, and accurately
reporting patient care information to Contra Costa
Emergency Medical Services Agency (“CCEMSA”). In
addition, CCEMSA requires the Department, as a
prehospital emergency medical first responder, to
maintain an active Quality Improvement (QI) program
and electronically capture patient care data in compliance with local, state, and federal regulations. Currently, the Department lacks both the qualified personnel and the
technological infrastructure necessary to meet the QI,
data review, analysis, and system integration.

AGENDA
REPORT
421

July 7, 2026
Furthermore, with the implementation of the National
Emergency Response Information System (NERIS)
beginning in January 2026, the Department requires
assistance with setting up the new records management
system, ImageTrend, and providing administrative
support to fulfill the Department’s National Emergency
Medical Services Information System (NEMSIS) and
NERIS requirements.

RECOMMENDED ACTION: APPROVE and RATIFY a sole-source contract with Definitive Networks, Inc. for Emergency Medical Services data reporting and records management compliance
support, in an amount not to exceed $216,834, for a term effective July 1, 2025, through June 30, 2028, with two one-year extension options in an amount not to exceed
$63,917 per year – Fire Department (Chief Aaron Osorio
510-307-8021/Chief Rico Rincon 510-307-8041/Den
Mark Marcelo 510-307-8038).

DISCUSSION:

Emergency Medical Services Data
The Emergency Medical Services and Prehospital Emergency Medical Care Personnel Act, which governs local Emergency Medical Services (“EMS”) systems, requires agencies to establish procedures for documenting, collecting, and accurately reporting patient care information to the designated Emergency Medical Services Authority. In Contra Costa County, this authority is the Contra Costa Emergency Medical Services Agency (“CCEMSA”).

As the designated authority, CCEMSA requires local EMS agencies such as the Richmond Fire Department (“Department”), in its role as a prehospital emergency medical first responder, to maintain an active Quality Improvement (QI) program and to electronically capture patient care data in accordance with local, state, and federal regulations. The data collected, along with the analysis conducted through QI efforts, is vital to the development and refinement of field treatment guidelines that improve patient outcomes. Accurate data collection, combined with independent review and ongoing QI processes, helps identify trends and opportunities for improvement, supporting continuous advancements in patient care both locally and nationally.

To comply with CCEMSA agreements and regulations, local EMS agencies must designate a staff member such as a medical director, nurse, or qualified paramedic who is responsible for overseeing the QI program. This individual must be capable of reviewing performance indicators, evaluating prehospital core metrics, and engaging field personnel in improvement activities. In addition, local EMS agencies are also required to provide CCEMSA with reliable access to patient care and response time data, ensure that their systems comply with CCEMSA, state, and National EMS Data Exchange Standards (“NEMSIS”).
422

July 7, 2026
Fire and All-Hazards Emergency Post-Incident Data
In January 2026, the United State Fire Administration transitioned all fire and allhazards emergency post-incident data reporting to National Emergency Response Information System (“NERIS”). To comply with the new reporting requirements, the Department acquired a new records management system, ImageTrend, capable of supporting NERIS reporting standards.

While NERIS participation is voluntary, fire departments eligibility to receive federal funding through the Assistance to Firefighters Grant (“AFG”) program must comply with incident reporting requirements as a condition of award. These funding sources are critical to supporting emergency response operations, equipment acquisition, training, and staffing.

Definitive Networks, Inc.

The Department currently lacks qualified personnel and the technological infrastructure necessary to meet the quality improvement (QI), data review, analysis, and system integration requirements established by Contra Costa EMS (CCEMSA). In addition, Department staff do not have the capacity to implement the new records management system required to comply with reporting standards established by the U.S. Fire Administration. Contracting with a qualified firm such as Definitive Networks, Inc. (DNI), which employs staff who meet the required qualifications and are able to deliver services in a timely manner, is a significantly more cost-effective solution than hiring additional personnel and acquiring the necessary infrastructure to provide these services in-house.

Since 2015, the City of Richmond has contracted DNI to provide electronic Patient Care Report (“ePCR”) review, quality improvement services, standardized reporting metrics, and essential software modifications, including customization of “close call” rules to align with evolving EMS policies and procedures. In addition, DNI currently holds the contract to host the ePCR server for Contra Costa County and provides technical expertise in ePCR system configuration and management for all fire agencies within the County. Furthermore, DNI has already developed the programming necessary to align with the National Emergency Response Information System (NERIS), effective January 2026.

Sole Source Justification
The contract meets the requirements of Richmond Municipal Code (RMC) Section

2.52.326. Following extensive research and a good-faith review, the Department has determined that there is no other vendor capable of providing ePCR review and Continuous Quality Improvement (CQI) services without requiring the purchase and implementation of a proprietary records management system (Attachment 1 – Sole Source).

In addition, the Department’s determination to contract DNI is based on the vendor’s role as the host of the Contra Costa County ePCR server. The County owns, maintains, 423

July 7, 2026
and administers the ZOLL ePCR licenses and server environment used by the Department. Contracting services from another vendor would require the acquisition and implementation of a separate records management system, as well as significant integration with County-owned systems and servers that are not controlled by the Department. Such an approach could result in additional costs and technical challenges.

Recommendation
City staff request approval and ratification of the sole-source contract with Definitive Networks, Inc. in the amount of $216,834 (Attachment 2 – Standard Contract). Approval of this request is imperative, as the Department currently lacks the internal staffing and technological capacity to meet Contra Costa Emergency Medical Services Authority (CCEMSA) mandated requirements for electronic patient care data collection, quality improvement, system integration, and reporting requirements associated with the National Emergency Response Information System (NERIS). Contracting with DNI provides an immediate and cost-effective solution that ensures compliance with applicable requirements, supports ongoing clinical oversight, enhances patient care outcomes, and improves the accuracy and reliability of data reporting.

SYNERGISTIC POLICIES:

The service contract with DNI aligns with the City Council’s goals and priorities to improve public safety and increase operational efficiency by ensuring regulatory compliance, supporting ongoing clinical oversight, enhancing patient care outcomes, and improving the accuracy and reliability of data reporting.

DOCUMENTS ATTACHED:

Attachment 1 – Sole Source
Attachment 2 – Standard Contract
424
425
426
6 01 2026
427

CITY OF RICHMOND

STANDARD CONTRACT
Department: City Project Manager:

City Project Manager E-mail: City Project Manager Phone No:

Vendor No: Contract No:

Description of Services:

The parties to this STANDARD CONTRACT do mutually agree and promise as follows:

1. Parties. The parties to this Contract are the City of Richmond, a municipal corporation (“the City”), and the following named Contractor:

Contractor Name:

Street Address:

City, State, Zip Code:

Contact Person:

Telephone: Email:

Business License No:
☐ A California corporation, ☐ limited liability corporation ☐ general partnership, ☐ limited partnership, ☐ individual, ☐ non-profit corporation, ☐ individual dba as [specify:] ____________________ ☐ other [specify:] _______________________________

2. Term. The effective date of this Contract is _______________________ and terminates _________________ unless terminated earlier as set forth herein.

3. Payment Limit. City’s total payments to Contractor under this Contract shall not exceed $______________ (“Contract Payment Limit”) unless a Contract Amendment has been approved by the City Council or City Manager. If this amount includes a contingency, Contractor acknowledges that any use of such contingency shall be for work beyond the original scope of services and requires prior written authorization by the City. If noted below, Compensation for work done under this Contract, shall not exceed as follows:

FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________

4. Contractor’s Obligations. Contractor agrees to perform all work at its own cost and expense, to furnish all labor, tools, equipment, materials, except as otherwise specified, in accordance with the Service Plan set forth in Exhibit A, attached hereto and incorporated herein.

5. City Obligations. City shall make payments to the Contractor in accordance with the Payment Provisions set forth in Exhibit B, attached hereto and incorporated herein.

FIRE Aaron Osorio [email protected] (510) 307-8041 11226 Vendor will provide CQI review services for reports authored in Zoll ePCR; set up and provide administrative support services for ImageTrend; provide designated Richmond Fire CQI Reviewers with access to the CQI Module of the FireGauge Operations Support Platform for CQI and Compliance Reporting. Definitive Networks Inc. 4309 Hacienda Drive, Suite 170 Pleasanton, CA 94588 [email protected] (925) 271-0634 [email protected] 40050725 July 1, 2025 June 30, 2028 216,834.00 25-26 89,000.00 26-27 63,917.00 27-28 63,917.00 428

6. Authorized Representatives and Notices. This Contract is subject to the Authorized Representatives and Notices Provisions (Exhibit C), attached hereto and incorporated herein.

7. General Conditions. This Contract is subject to the General Conditions (Exhibit D), which are attached hereto and incorporated herein.

8. Special Conditions. This Contract is subject to the Special Conditions (Exhibit E) (if any), which are attached hereto and incorporated herein.

9. Insurance Provisions. This Contract is subject to the Insurance Provisions (Exhibit F), which are attached hereto and incorporated herein.

10. Sanctuary City Compliance Statement. This Contract is subject to the Sanctuary City Compliance Statement (Exhibit G), which is attached hereto and incorporated herein.

11. Signatures. These signatures attest the parties' agreement hereto:

CITY OF RICHMOND,
a municipal corporation [BUSINESS NAME]
(* The Corporation Chairperson of the Board, President, or Vice President should sign below)
By: _________________________ By: ___________________________ Title: ________________________ Title: __________________________ Date Signed: _________________ Date Signed: ___________________ I hereby certify that this Contract (* The Corporation Chief Financial Officer or Assistant has been approved by City Council Treasurer, or Secretary or Assistant Secretary should or the City Manager. sign below)
By: _________________________ By: ___________________________ City Clerk Title: __________________________
Date Signed: ____________________
Approved as to form:
(NOTE: Pursuant to California Corporations Code Section By: _________________________ 313, if Contractor is a corporation or nonprofit organization, City Attorney this Contract (1) must be signed by (a) the Chairperson of the Board, President, or Vice-President and (b) the
Chief Financial Officer or Assistant Treasurer, or
Secretary or Assistant Secretary)
LIST OF ATTACHMENTS:

Service Plan Exhibit A
Payment Provisions Exhibit B
Authorized Representatives and Notices Exhibit C
General Conditions Exhibit D
Special Conditions Exhibit E
Insurance Provisions Exhibit F
Sanctuary City Compliance Statement Exhibit G
Definitive Networks Inc.
429
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT A

SERVICE PLAN
Contractor shall, to the satisfaction of the Project Manager (set forth in Exhibit B), perform the following services and be compensated as outlined below [or attach service plan if necessary]:

Definitive Networks Inc.

Definitive Networks, Inc. (DNI), to the satisfaction of the project manager, shall perform the services outlined in the DNI Addendum Overview, attached hereto. See Exhibit A-1 for details. 430

ADDENDUM OVERVIEW
Definitive Networks, Inc. (DNI), to the satisfaction of the Richmond Fire EMS and Training Division, shall perform the following services and be compensated as outlined below:

DNI will
• Provide CQI review services for reports authored in Zoll ePCR. • Set Up and Provide Administrative Support Services for ImageTrend, a reporting platform used by Richmond Fire to fulfill its NEMSIS and NERIS reporting requirements. • Provide designated Richmond Fire CQI Reviewers with access to the Continuous Quality Improvement Module (CQI) of the FireGauge Operations Support Platform for CQI and Compliance Reporting.

Exhibit A-1
431

EXHIBIT A

CQI REVIEW SERVICES
• Review ePCRs authored in Zoll EPCR for Richmond Fire BLS First Responders. ⎯ Provide a cursory Zoll ePCR review for completeness and general quality based on prescribed County EMS Protocols and Richmond Fire Policies.
⎯ Flag questionable Zoll ePCR Records and forward to RFD EMS Division personnel for further review and follow up with crews. Note: RFD EMS Division will make the determination if improper documentation practices were performed and take action as required. DNI personnel will not provide counseling or any other related interactions with Richmond Fire field personnel. • Establish workflow needs and parameters and forward to the application administrator for implementation.
• Add or adjust closed-call rules to improve documentation quality, and forward them to the application administrator for implementation.
• Assist Richmond Fire EMS Division with the development of Department Policies and Procedures appropriate for the unique operating practices of Richmond Fire. • Provide general communication with EMS Division Personnel as directed.

End-User Support Services
• Provide end-user support to Richmond Fire Crews (BLS Agency) ⎯ Address general application issues and end-user support ⎯ Provide remote support services via phone and/or interactive computer application ⎯ Provide liaison services to vendors as directed by Richmond Fire ⎯ Forward any advanced support requests to ePCR system administrator • Training Support
⎯ Provide semi-annual Zoll ePCR/CQI training classes
⎯ Provide remedial coaching/training as required
⎯ Provide Administrative Training as required for
 QA / CQI Personnel
 EMS Division Personnel
Analytics
• Provide analytic reports and dashboards required to support CQI Program • Provide analytic information for response data contained in the Zoll ePCR Database Exhibit A-1
432

EXHIBIT B

IMAGETREND & REPORTING
DNI will assist Richmond Fire as it transitions from Zoll ePCR and NFIRS RMS to ImageTrend NERIS & EMS (PCR) Modules. That support is limited to working with the Richmond Fire’s ImageTrend Program Manager and Designated Personnel. DNI’s deliverables follow:
1) Work with ImageTrend’s Implementation Specialist, Richmond Fire’s ImageTrend Program Manager, and Designated Personnel to configure ImageTrend NERIS & EMS (PCR) Forms, Validation Rules, and other Functionality to comply with NEMSIS 3.5 and NERIS 1.0 Validation Rules and any local reporting requirements applicable to Richmond Fire. a) Review the go-live timeline with Richmond Fire Admin Personnel at the “kick-oƯ” meeting once the CAD and UKG interfaces are active and stable. b) Deploy NERIS Form on a pre-determined date.
c) Deploy the EMS (PCR) Form approximately 60 days after the NERIS Form to provide Suppression Personnel ample opportunity to become familiar with the new platform’s basic workflow.
2) Set up and host the ImageTrend Datamart.
3) Work with UKG Telestaff and ImageTrend Technical Personnel to connect Roster Data to autopopulate ImageTrend NERIS & EMS (PCR) Modules. DNI’s role is limited to connectivity and data-feed validation.
4) Work with Mark43 & ImageTrend Technical Personnel to establish connectivity between CAD and ImageTrend using the Mark43 CAD Interface. DNI’s role is limited to connectivity and datafeed validation. 5) Create a Training Video to be used to train Richmond Firefighters on the Basic Use of the NERIS & EMS (PCR) Forms.
6) Provide reporting support to assist Richmond Fire in meeting reporting requirements for NERIS, NEMSIS, and City Council Reports.
7) Create up to 20 custom reports, as directed by Richmond Fire Command Staff, using the ImageTrend Datamart. If additional reports are required, Richmond Fire can petition DNI to produce them. If additional funding is required, DNI will notify Richmond Fire Command Staff in advance of performing the work.
8) Participate in quarterly review sessions with the Richmond Fire ImageTrend Program Manager to assess ImageTrend performance and identify opportunities for improvement. Other meetings can be scheduled with 10 days’ advance notice.

Exhibit A-1
433

EXHIBIT C

FIREGAUGE CQI
DNI will provide designated Richmond Fire CQI Reviewers with online access to the Continuous Quality Improvement Module (CQI) of the FireGauge Operations Support Platform. Designated Richmond Fire CQI Reviewers will use the FireGauge CQI Module to assess Electronic Patient Care Reports (EPCR) authored by Richmond Firefighters. DNI will provide end-user support as required to ensure that Richmond Fire CQI Reviewers can:

1. Review submitted reports

2. Assess compliance with the Reporting Standards set by Contra Costa EMS and Richmond Fire

3. Provide feedback to EPCR Authors as required.

Note that Richmond Fire retains sole control and responsibility for Report Escalations and for the content of policies governing CQI review.

DNI also agrees to provide quarterly, online training to Richmond Fire CQI Reviewers.

DNI will also provide Richmond Fire CQI Reviewers with support and feedback regarding the

1. Interpretation of NEMSIS and NERIS reporting standards that apply to Richmond Fire Reporting Policies

2. Complex items related to an individual report authored by a Richmond Fire EPCR Author That support is provided through quarterly meetings for Policy-related items and via a helpdesk ticket for a specific question about a report.

Exhibit A-1
434

EXHIBIT D

FIREGAUGE CQI MODULE IMPLEMENTATION
DNI will assist Richmond Fire in implementing the FireGauge CQI Module by working closely with the Richmond Fire Training Division to prepare designated Richmond Fire CQI Reviewers for its use.

DNI will follow the implementation methodology defined in “FireGauge PCR Review Module Implementation Outline 4.22.26,” which is an Attachment to this Addendum. DNI’s role in training Richmond Fire CQI Reviewers is limited to
• Conducting three one-hour classes online for designated CQI Reviewers • Providing three hours of individual coaching for each designated CQI Reviewer • Responding to questions submitted by the Richmond Fire EMS Division • Auditing CQI performance and providing feedback as appropriate Exhibit A-1
435

TERM
Start Date: 1 Jul 2025
End Date: 30 Jun 2028
Option to Extend Beyond Initial Term: Yes (2 Years)
Exhibit A-1
436

EXHIBIT E

PRICING
Initial Term Option to Extend
Item Year 1 Year 2 Year 3 Year 4 Year 5
Zoll ePCR Support Services $89,000 - - - -
ImageTrend Setup & Support - $49,917 $49,917 $49,917 $49,917 FireGauge CQI Module & PCR Support - $14,000 $14,000 $14,000 $14,000

Total $89,000 $63,917 $63,917 $63,917 $63,917

Not To Exceed $216,834 $127,834
Note: A request to change the Scope of Exhibits may incur additional costs.

Exhibit A-1
437

PCR REVIEW MODULE
Implementation Plan
Juliet Henshaw
[email protected]
Abstract
This document outlines the transition plan for Richmond Fire to complete Patient Care Record Reviews using the FireGauge PCR Review Module Exhibit A-1
438
1 Table of Contents
FIREGAUGE PCR REVIEW MODULE — IN-HOUSE TRANSITION PLAN........................................2 SECTION 1: PROGRAM GOVERNANCE & OWNERSHIP.............................................................2 SECTION 2: REVIEWER RECRUITMENT & CREDENTIALING ......................................................3 SECTION 3: DOCUMENTATION STANDARDS............................................................................4 SECTION 4: FIREGAUGE SYSTEM TRAINING & ORIENTATION....................................................6 SECTION 5: PCR REVIEW WORKFLOW ....................................................................................7 SECTION 6: QUALITY METRICS & REPORTING .........................................................................9 SECTION 7: 90-DAY TRANSITION TIMELINE .............................................................................9 SECTION 8: POLICY & SOG DEVELOPMENT CHECKLIST.........................................................10 Exhibit A-1
439
2 FireGauge PCR Review Module — In-House Transition Plan Implementation Plan date: 2026-04-22
Overview
This document outlines the transition plan for Richmond Fire to assume full ownership of the PCR (Patient Care Report) review process within the FireGauge PCR Review module.

Previously managed by FireGauge staff, the review process will be transferred to agency personnel within a 90-day window. The primary focus of all reviews is NEMSIS Data completion and accuracy and clinical care quality, with 100% of PCRs reviewed each month.

A dedicated EMS Officer will own and manage this process. All reviewers must hold a minimum certification of EMT-Basic (EMT-B) or Paramedic.

Section 1: Program Governance & Ownership

1.1 Designate the EMS Officer
• Formally assign or hire a dedicated EMS Officer responsible for overseeing the entire PCR review program.
• Define the role in writing with clear authority, accountability, and reporting structure (e.g., reports to Deputy Chief of Operations).
• The EMS Officer serves as the primary point of contact with FireGauge for system access, configuration, and support.

EMS Officer Core Responsibilities:

Responsibility Description
Program
Ownership
Manages all aspects of the in-house PCR review process
Reviewer
Oversight
Assigns PCRs, monitors reviewer activity, and ensures timely completion if the agency utilizes a team of reviewers.

Issue Resolution Manages the workflow for PCRs flagged with identified issues Exhibit A-1
440
3 Responsibility Description
Reporting Produces monthly QA/QI summary reports for agency leadership Policy
Maintenance
Authors, updates, and enforces all QA/QI documentation standards FireGauge
Liaison
Coordinates with FireGauge support for system updates and training Section 2: Reviewer Recruitment & Credentialing

2.1 Reviewer Eligibility Requirements
All PCR reviewers must meet the following minimum qualifications:
• Active certification as an EMT-Basic (EMT-B) or Paramedic in the applicable state • Current, unencumbered licensure with no active disciplinary actions • Minimum of 1 year of field experience recommended
• Completion of agency-required reviewer orientation (see Section 4) NOTE: Paramedic-level reviewers are strongly preferred for clinical review of ALS calls.

Consider assigning BLS and ALS call reviews based on reviewer certification level.

2.2 Reviewer Selection Process

1. Issue an internal announcement or job posting for PCR reviewer positions.

2. Screen candidates against the eligibility requirements in Section 2.1.

3. Conduct a brief structured interview or skills assessment focused on clinical documentation knowledge.

4. Select reviewers and obtain written acknowledgment of role responsibilities and confidentiality obligations.

5. Document all selected reviewers in a Reviewer Registry maintained by the EMS Officer.

Exhibit A-1
441
4 2.3 Reviewer Registry
Maintain a current registry including:
• Full name and certification level (EMT-B / Paramedic) • State certification number and expiration date
• FireGauge system username
• Date of reviewer orientation completion
• Review assignment scope (BLS, ALS, or both)
Section 3: Documentation Standards

3.1 PCR Review Documentation Policy
The agency must establish a formal, written PCR Review Policy prior to go-live. At minimum, the policy must address:
• Purpose and scope of the QA/QI program
• Review frequency and volume (100% of PCRs monthly)
• Reviewer eligibility and certification requirements
• Confidentiality and peer review protections (consult agency legal counsel regarding applicable state peer review statutes)
• Retention requirements for review records and issue documentation • Escalation and corrective action procedures
COMPLIANCE: PCR data contains Protected Health Information (PHI) under HIPAA.

Ensure all reviewers complete HIPAA training and sign a confidentiality agreement prior to accessing patient records. Review records must be stored and transmitted in accordance with agency HIPAA policies.

3.2 Review Scoring & Documentation Standards
Define and document clear, objective criteria for what constitutes a compliant vs. deficient PCR. Standards should cover:

Exhibit A-1
442
5 • Patient assessment documentation (chief complaint, history, physical exam findings)
• Treatment and intervention documentation (medications, procedures, times) • Protocol adherence (appropriate treatment based on presentation and local protocols)
• Vital sign documentation (frequency, completeness)
• Narrative quality (accurate, legible, complete, chronological) • Signature and certification fields (provider signature, crew information) Use the FireGauge review scoring framework as the baseline and customize criteria to align with the agency's local EMS protocols and Medical Director expectations.

3.3 Issue Classification
Establish standardized issue categories to ensure consistent documentation of deficiencies:

Category Examples
Documentation
Not completed, incomplete and/or inaccurate. (Missing vitals, incomplete narrative, unsigned PCR, wrong patient demographics, incorrect incident number, etc.)
Clinical
Treatments are not completed, incomplete or inaccurate. (Medication error, incorrect dosage documented, Etc.)
Advisement Excellent clinical care, High Risk/liability issue for agency or city.

Exhibit A-1
443
6 Section 4: FireGauge System Training & Orientation

4.1 FireGauge Transition Coordination

1. Contact FireGauge account representative to formally initiate the transition.

2. Confirm the timeline for transferring review responsibilities from FireGauge staff to agency reviewers.

3. Request a system walkthrough or training session for the EMS Officer and designated reviewers.

4. Confirm user account setup for all reviewers within the FireGauge PCR Review module.

4.2 Reviewer Orientation Curriculum
Prior to conducting independent reviews, all reviewers must complete orientation covering:

1. FireGauge PCR Review module navigation and interface

2. Accessing assigned PCRs and the review queue

3. Completing a review — scoring, comments, and submission

4. Escalating a PCR with an identified issue

5. Documentation standards and issue classification (Section 3.3)

6. Confidentiality obligations and HIPAA requirements

7. The issue resolution workflow (Section 5)

8. Escalation procedures and when to involve the EMS Officer VERIFICATION: Each reviewer must complete at least 5 supervised practice reviews evaluated by the EMS Officer before conducting independent reviews.

Exhibit A-1
444
7 Section 5: PCR Review Workflow

5.1 Standard Review Workflow (No Issues Identified)
PCR Submitted by Field Provider
↓
PCR Appears in FireGauge Review Queue
↓
EMS Officer Assigns PCR to Reviewer
↓
Reviewer Completes Review in FireGauge Module
↓
Review Marked Complete — No Issues Identified
↓
PCR sent to author for direct review and acknowledgment of feedback. ↓
Archived / Review Record Retained
• Target review turnaround: Within 7 days of PCR submission • Reviewer documents score, comments, and attestation in FireGauge

5.2 Issue Resolution Workflow (Issue Identified)
Reviewer Identifies Issue During Review
↓
Reviewer Documents Issue in FireGauge
(Category, description, specific deficiency)
↓
PCR Flagged — EMS Officer Notified
↓
Exhibit A-1
445
8 EMS Officer Reviews Flag & Validates Issue
↓
├── Issue Confirmed
│ ↓
│ Supervisor of Record Notified
│ ↓
│ Decide on resolution
│ ↓
│ Complete resolution steps
│ ↓
│ Resolved → Issue Closed & Documented
│ Unresolved → Escalate (see Section 5.3)
│
└── Issue Not Confirmed
↓
Reviewer Given Feedback
PCR Closed — No Further Action

5.3 Escalation Procedure
Escalate to agency leadership (EMS Director/Chief) when:
• A clinical concern suggests potential patient harm
• A pattern of repeated deficiencies is identified for the same provider • The issue involves a potential protocol violation requiring Medical Director review Exhibit A-1
446
9 Section 6: Quality Metrics & Reporting
The EMS Officer will produce a monthly summary report for agency leadership including:
• Total PCRs reviewed
• Overall compliance/pass rate
• Number and category of issues identified
• Number of PCRs flagged and resolved
• Number of PCRs pending resubmission
• Provider-level trends (aggregate, de-identified where appropriate for staff-wide sharing)
• Reviewer activity and turnaround times
Section 7: 90-Day Transition Timeline
Phase Timeframe Key Activities
Phase 1 —
Foundation Days 1–30
Formally appoint EMS Officer; coordinate with FireGauge on transition; draft and approve PCR Review Policy; establish Reviewer Registry template; identify reviewer candidates Phase 2 —
Build
Days 15–
45 Select and onboard reviewers; complete FireGauge system training; finalize documentation standards and issue
classification system; configure FireGauge user accounts; complete supervised practice reviews
Phase 3 —
Parallel
Operations
Days 30–
60 Agency reviewers conduct reviews alongside or shadowing FireGauge staff; QA/QI Officer validates review quality; refine workflows based on real-world experience
Phase 4 — GoLiveDays 60–
90 Agency assumes 100% of review responsibility; FireGauge transitions to support-only role; QA/QI Officer produces first independent monthly summary report
NOTE: Overlap during Phase 3 is strongly recommended. Request that FireGauge staff remain available for consultation during the first full independent review cycle.

Exhibit A-1
447
10 Section 8: Policy & SOG Development Checklist
Since the agency is starting from scratch, the following documents must be created prior to go-live:
• [ ] PCR Quality Assurance & Improvement Policy
• [ ] Reviewer Eligibility & Selection SOG (If reviewer committee will be utilized) • [ ] PCR Review Confidentiality & HIPAA Acknowledgment Form (if reviewer committee will be utilized)
• [ ] PCR Issue Notification & Correction Procedure
• [ ] Provider Notification Template (written notice of identified deficiency) • [ ] Supervisor Notification Procedure
• [ ] Monthly QA/QI Report Template
• [ ] Reviewer Orientation Completion Log
Appendix: Key Roles Summary
Role Responsibility
EMS Officer
Owns the program; assigns reviews; manages issue resolution; produces reports; maintains all policy documents
PCR Reviewer (EMTB / Paramedic)Completes assigned PCR reviews in FireGauge; documents findings; flags issues for QA/QI Officer
Field Provider
Submits PCRs; acknowledges receipt of PCR review comments; corrects and resubmits flagged PCRs if agency decides to correct a deficient PCR.

Supervisor of
Record
Notified when a provider's PCR is flagged; responsible for provider follow-up and coaching
Deputy Chief of
Operations
Receives monthly summary reports; reviews escalated issues and patterns
Exhibit A-1
448
11 Role Responsibility
Medical Director
Consulted on clinical concerns and protocol violations; receives immediate notification of patient safety concerns
FireGauge Support
Provides system training, technical support, and consultation during transition
Exhibit A-1
449
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT B

PAYMENT PROVISIONS

1. COMPENSATION TO CONTRACTOR:
a. Provided Contractor is not in default under this Contract, Contractor shall be compensated in the manner set forth herein.
b. All payments made pursuant to this Contract shall be subject to the Contract Payment Limit. The Payment Limit includes expenses (phones, photocopying, meals and travel, etc.). Invoices shall be adequately detailed, based on accurate records, and be in a form reasonably satisfactory to the City. Contractor may be required to provide back-up material upon request. c. All City vendors receiving new contracts shall sign up to receive electronic payments through the City’s Automated Clearinghouse (ACH) payments service/provider.

2. SUBMISSION OF INVOICES:

Contractor shall submit timely invoices by email to
[email protected] and/or to the following address:

Attention: City of Richmond Finance/Account Payable
Project Manager: _______________________
P.O. Box 4046
Richmond, CA 94804

3. All invoices that are submitted by Contractor shall be subject to the approval of the City Project Manager, _______________________, before payments shall be authorized.
a. The City will pay invoice(s) within 45 days after completion of services to the City’s satisfaction. The City shall not pay late fees or interest.
b. All appropriate permits, certificates, and licenses, including a City business license shall be obtained and maintained for the duration of this Contract before any payment is authorized.

4. All insurance coverage required by this Contract shall be provided by the Contractor before this Contract is executed by the City. The insurance coverage required by this Contract shall be maintained by Contractor for the duration of this Contract and must be in place before any payment is authorized.

Aaron Osorio Aaron Osorio Definitive Networks Inc.
450
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT C

AUTHORIZED REPRESENTATIVES AND NOTICES

1. All required written notices shall be delivered: (i) by hand; or (ii) sent by registered, express, or certified mail, with return receipt requested or with delivery confirmation requested from the U.S. postal service; or (iii) sent by overnight or same day courier service at the party’s respective address listed in this Section.

2. Each notice shall be deemed to have been received on the earlier to occur of:
actual delivery or the date on which delivery is refused; or three (3) days after notice is deposited in the U.S. mail or with a courier service in the manner described above (Sundays and City holidays excepted).

3. Either party may, at any time, change its notice address (other than to a post office box address) by giving the other party three (3) days prior written notice of the new address.

4. All notices, demands, requests, or approvals from Contractor to the City shall be addressed to the City at:

City of Richmond
450 Civic Center Plaza
Richmond, CA 94804
Email: ________________________________________________

5. All notices, demands, requests, or approvals from the City to Contractor shall be addressed to Contractor at:

Attn:

Email: ________________________________________________ Aaron Osorio [email protected] Networks Inc. Definitive Networks Inc. 4309 Hacienda Drive, Suite 170 Pleasanton, CA 94588 [email protected] 451
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT D

GENERAL CONDITIONS

1. INDEPENDENT PARTIES:

Contractor hereby declares that Contractor is engaged as an independent business and Contractor agrees to perform the services as an independent contractor.

The manner and means of conducting the services and tasks are under the control of Contractor except to the extent they are limited by statute, rule or regulation and the express terms of this Contract. No civil service status or other right of employment will be acquired by virtue of Contractor’s services. None of the benefits provided by the City to its employees, including but not limited to unemployment insurance, workers’ compensation plans, vacation and sick leave, are available from the City to Contractor, its employees or agents. Deductions shall not be made for any state or federal taxes, FICA payments, PERS payments, or other purposes normally associated with an employer-employee relationship from any compensation due to Contractor. Payments of the above items, if required, are the responsibility of Contractor.

2. TIME IS OF THE ESSENCE:

Contractor and the City agree that time is of the essence regarding the performance of this Contract.

3. STANDARD OF CARE:

Contractor agrees to perform all services hereunder in a manner commensurate with the prevailing standards of like professionals or service Contractors, as applicable, in the San Francisco Bay Area and agrees that all services shall be performed by qualified and experienced personnel who are not employed by the City.

4. IMMIGRATION REFORM AND CONTROL ACT (IRCA):

Contractor assumes all responsibility for verifying the identity and employment authorization of all of its employees performing work hereunder, pursuant to all applicable IRCA or other federal, or state rules and regulations. Contractor shall indemnify, defend, and hold the City harmless from and against any loss, damage, liability, costs or expenses arising from any noncompliance of this provision by Contractor.

5. NON-DISCRIMINATION:

Consistent with the City’s policy and state and federal law that harassment and discrimination are unacceptable conduct, Contractor and its employees, contractors, and agents shall not harass or discriminate against any job applicant, City employee, or any other person on the basis of any kind of any statutorily (federal, state or local) protected class, including but not limited to: race, religious creed, color, national origin, ancestry, Definitive Networks Inc.
452
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
disability (both mental and physical) including HIV and AIDS, medical condition (e.g. cancer), genetic information, marital status, sex, gender, gender identity, gender expression, age, sexual orientation, pregnancy, political affiliation, military and veteran status or legitimate union activities. Contractor agrees that any violation of this provision shall constitute a material breach of this Contract.

6. CITY PROPERTY:
a. Each and every report, draft, work product, map, record, applicable plans, drawings, calculation, data, specification, video, graphic, or any other material or document produced, prepared or caused to be prepared by Contractor pursuant to or in connection with this Contract shall be the exclusive property of the City. b. Notwithstanding the foregoing, Contractor shall not be obligated to provide to City proprietary software or data which Contractor has developed or had developed for Contractor's own use; provided, however, that Contractor shall, pursuant to Section 11 below, indemnify, defend and hold the City harmless from and against any discovery or Public Records Act request seeking the disclosure of such proprietary software or data. c. No report, information or other data given to or prepared or assembled by Contractor pursuant to this Contract shall be made available to any individual or organization by Contractor without prior approval of the City Manager or their designee. d. Contractor shall, at such time and in such form as City Manager or their designee may require, furnish reports concerning the status of services and tasks required under this Contract.

7. RECORDS:
a. Contractor shall maintain complete and accurate records with respect to the services, tasks, work, documents and data in sufficient detail to permit an evaluation of Contractor’s performance under the Contract, as well as maintain books and records related to sales, costs, expenses, receipts and other such information required by the City that relate to the performance of the services and tasks under this Contract (collectively the “Records”).
b. All Records shall be maintained in accordance with generally accepted accounting principles and shall be clearly identified and readily accessible. Contractor shall provide free access to the Records to the representatives of the City or its designees during regular business hours upon reasonable prior notice. The City has the right to examine and audit the Records, and to make copies or transcripts therefrom as necessary, and to allow inspection of all proceedings and activities related to this Contract. Such Records, together with supporting documents, shall be kept separate from other documents and records and shall be maintained by Contractor for a period of five (5) years after receipt of final payment.

Definitive Networks Inc.
453
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. If supplemental examination or audit of the Records is necessary due to concerns raised by the City’s preliminary examination or audit of records, and the City’s supplemental examination or audit of the records discloses a failure to adhere to appropriate internal financial controls, or other breach of this Contract or failure to act in good faith, then Contractor shall reimburse the City for all reasonable costs and expenses associated with the supplemental examination or audit.

8. PERMITS AND LICENSES:

Contractor, at its sole expense, shall obtain and maintain during the term of this Contract, all appropriate permits, certificates and licenses, including a City business license, required in connection with the performance of the services and tasks hereunder.

The failure to obtain such permits and licenses shall be a material breach of this Contract and grounds for immediate termination by City; provided, however, that City may waive the business license requirement in writing under unusual or extraordinary circumstances without necessitating any modification of this Contract to reflect such waiver.

9. TERMINATION:
a. Termination Without Default. Notwithstanding any provision herein to the contrary, the City may, in its sole and absolute discretion and without cause, terminate this Contract at any time prior to completion by Contractor of the project or services hereunder immediately upon transmission of written notice to Contractor as provided in Exhibit C “Authorized Representatives and Notices”.
b. Termination in the Event of Default. Should Contractor fail to perform any of its obligations hereunder, within the time and in the manner provided or otherwise violate any of the terms of this Contract, City may immediately terminate this Contract by giving written notice of such termination, stating the reasons for such termination. Contractor shall be compensated as provided in Exhibit B; provided, however, there shall be deducted from such amount the amount of damage, including attorney's fees, expert witness fees and costs, if any, sustained by City by virtue of Contractor's breach of this Contract. Additionally, in the event of such termination, the City may proceed with the work in any reasonable manner it chooses.

10. CONFLICT OF INTEREST:

Contractor acknowledges, represents and warrants that Contractor shall avoid all conflicts of interest (as defined under any federal, state or local statute, rule or regulation, or at common law) with respect to this Contract. Contractor further acknowledges, represents and warrants that no City official or employee has any economic interest, as defined in Title 2, California Code of Regulations §§ 18703.1 through 18703.5, with Contractor that would invalidate this Contract. Contractor acknowledges that in the event that Contractor shall be found by any judicial or administrative body to have any conflict of interest (as defined above) with respect to this Contract, all consideration received under Definitive Networks Inc.
454
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
this Contract shall be forfeited and returned to City forthwith. This provision shall survive the termination of this Contract for one (1) year.

11. HOLD HARMLESS:
a. To the fullest extent permitted by law, Contractor shall indemnify, defend (with counsel acceptable to the City) and hold harmless the City, its City Council, boards, commissions, officials, employees, agents and volunteers (“Indemnitees”) from and against any and all loss, damages, liability, obligations, claims, suits, judgments, costs and expenses whatsoever, including attorney’s fees and costs of litigation (“Claims”), arising from or in any manner connected to Contractor’s performance of its obligations under this Contract or failure to comply with any of its obligations under this Contract or out of the operations conducted by Contractor even if the City is found to have been negligent. If the Claims filed against Indemnitees allege negligence, recklessness or willful misconduct on the part of Contractor, Contractor shall have no right of reimbursement against Indemnitees for the costs of defense even if negligence, recklessness or willful misconduct is not found on the part of Contractor. Contractor shall not have any obligations to indemnify Indemnitees if the loss or damage is found to have resulted solely from the negligence or the willful misconduct of the City. The defense and indemnification obligations of this Contract are undertaken in addition to, and shall not in any way be limited by, the insurance obligations contained in this Contract. b. This indemnification obligation shall survive this Contract and shall not be limited by any term of any insurance policy required under this Contract; provided however, that if this Contract is for design professional services, this indemnity provision is limited to claims that arise out of, pertain to, or relate to the negligence, recklessness, or willful misconduct of the design professional (as defined in California Civil Code section 2782.8).

12. LIMITATIONS UPON SUBCONTRACTING AND ASSIGNMENT:
a. This Contract binds the heirs, successors, assigns and representatives of Contractor. The Contractor shall not enter into subcontracts for any work contemplated under this Contract and shall not assign this Contract, nor any portion hereof or monies due or to become due, without the prior written consent of the City Council or its designee.
b. Contractor shall not assign, sublease, hypothecate, or transfer this Contract, or any interest therein, directly or indirectly, by operation of law or otherwise, without prior written consent of the City Manager. Contractor shall submit a written request for consent to transfer to the City Manager at least thirty (30) days in advance of the desired transfer.

The City Manager or their designee may consent or reject such request in their sole and absolute discretion. Any attempt to do so without said consent shall be null and void, and any assignee, sublessee, hypothecate or transferee shall acquire no right or interest by reason of such attempted assignment, hypothecation or transfer. However, claims for Definitive Networks Inc.
455
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
money against the City under this Contract may be assigned by Contractor to a bank, trust company or other financial institution without prior written consent. c. The sale, assignment, transfer or other disposition of any of the issued and outstanding capital stock of Contractor (if applicable), or of the interest of any general partner or joint venturer or syndicate member if Contractor is a partnership or jointventure or syndicate, which shall result in a change of control of Contractor, shall be deemed an assignment. For this purpose, control shall mean fifty percent or more of the voting power or twenty-five percent or more of the assets of the corporation, partnership or joint-venture.
d. Only those persons and/or businesses whose names and resumés are attached to this Contract shall be used in the performance of this Contract. However, if after the start of this Contract, Contractor wishes to use sub-contractors, at no additional costs to the City, then Contractor shall submit a written request for consent to add subcontractors including the names of the sub-contractors and the reasons for the request to the City Manager at least five (5) days in advance. The City Manager may consent or reject such requests in their sole and absolute discretion. e. Each sub-contractor shall be required to furnish proof of workers’ compensation insurance and shall also be required to carry general, automobile and professional liability insurance (as applicable) in reasonable conformity to the insurance carried by Contractor.
f. In addition, any tasks or services performed by sub-contractors shall be subject to each provision of this Contract. Contractor shall include the following language in their Contract with any sub-contractor: “Sub-Contractors hired by Contractor agree to be bound to Contractor and the City in the same manner and to the same extent as Contractor is bound to the City.”
g. The requirements in this Section 12 shall not apply to persons who are merely providing materials, supplies, data or information that Contractor then analyzes and incorporates into its work product.

13. SAFETY:
a. Contractor acknowledges that the City is committed to the highest standards of workplace safety. Contractor will be solely and completely responsible for conditions of all vehicles owned or operated by Contractor, including the safety of all persons and property during performance of the services and tasks under this Contract.

Contractor shall assume sole and complete responsibility for the safety of Contractor's employees and any of subcontractor's employees This requirement will apply continuously and not be limited to normal working hours. In addition, Contractor will comply with all safety provisions in conformance with U.S. Department of Labor Occupational Safety and Health Act, any equivalent state law, and all other applicable Definitive Networks Inc.
456
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
federal, state, county and local laws, ordinances, codes, and any regulations that may be detailed in other parts of the Contract. Where any of these are in conflict, the more stringent requirements will be followed. Contractor’s failure to thoroughly familiarize itself with the aforementioned safety provisions will not relieve it from compliance with the obligations and penalties set forth herein.
b. Contractor will immediately notify the City (in no event less than 24 hours) of any incident of death, serious personal injury or substantial property damage that occurs in connection with the performance of this Contract. Contractor will promptly submit to the City a written report of all incidents that occur in connection with this Contract. This report must include the following information: (i) name and address of injured or deceased person(s); (ii) name and address of Contractor’s employee(s) involved in the incident; (iii) name and address of Contractor’s liability insurance carrier; (iv) a detailed description of the incident; and (v) a police report.
c. Contractor acknowledges that the City shall have the right to impose, at the City’s sole discretion, requirements that it deems are necessary to protect the health and safety of the City employees, residents, and visitors. Contractor agrees to comply with all such requirements, including, but not limited to, mandatory vaccinations, the use of personal protective equipment (e.g. masks), physical distancing, and health screenings.

Contractor also agrees to make available to the City, at the City’s request, records to demonstrate Contractor’s compliance with this Section.

14. INSURANCE:

Insurance requirements are set forth in Exhibit F to this Contract. Contractor shall abide by the insurance requirements set forth in said Exhibit F.

15. COMPLIANCE WITH ALL APPLICABLE LAWS:
a. During the term of this Contract, Contractor shall keep fully informed of all existing and future state and federal laws and all municipal ordinances and regulations of the City of Richmond which affect the manner in which the services or tasks are to be performed by Contractor, as well as all such orders and decrees of bodies or tribunals having any jurisdiction or authority over the same. Contractor shall comply with all applicable laws, state and federal and all ordinances, rules and regulations enacted or issued by the City. Compliance under this provision includes compliance with all provisions of the Richmond Municipal Code ("Municipal Code"), including Chapters 2.50,

2.52, 2.56, and 2.60, if applicable.
b. Contractor acknowledges that under § 2.60.070 of the Municipal Code ("Living Wage Ordinance"), Contractor is required to provide the City with documents and information verifying its compliance with the Living Wage Ordinance. Contractor shall notify each of its affected employees with regards to the wages that are required to be paid pursuant to the Living Wage Ordinance as prescribed in § 2.60.070 of the Municipal Code.

Definitive Networks Inc.
457
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. Contractor shall comply with § 2.28.030 of the Municipal Code, obligating every Contractor or sub-Contractor under an agreement or sub-agreement with the City for public works, goods or services to refrain from discriminatory employment or practices on the basis of race, color, sex, sexual orientation, religious creed, national origin or ancestry of any employee, any applicant for employment or any potential sub-contractor. d. Contractor acknowledges that the City’s Drug Free Workplace Policy, Violence in the Workplace Policy and the Policy Against Workplace Harassment, are available on the City’s website at http://www.ci.richmond.ca.us/workplacepolicies.

Contractor agrees to abide by the terms and conditions of said policies.

16. INTEGRATED CONTRACT:

The Recitals and exhibits are a material part of this Contract and are expressly incorporated herein. This Contract represents the full and complete understanding of every kind or nature whatsoever between the parties hereto, and all preliminary negotiations and agreements of whatsoever kind or nature are merged herein. No verbal agreement or implied covenant shall be held to vary the provisions hereof. Any modification of this Contract will be effective only by written execution signed by both the City and Contractor.

17. CONFLICTING PROVISIONS:

In the event of a conflict between these General Conditions and those of any Exhibit or attachment hereto, these General Conditions shall prevail; provided, however, that any Special Condition as set forth in Exhibit E shall prevail over these General Conditions. In the event of a conflict between the terms and conditions of any two or more Exhibits or attachments hereto, those prepared by City shall prevail over those prepared by the Contractor, and the terms and conditions preferred by the City shall prevail over those preferred by the Contractor.

18. FORCE MAJEURE:

Neither party hereto shall be considered in default in the performance of its obligations hereunder to the extent that the performance of such an obligation is prevented or delayed by reason of acts of God, strikes, boycotts, lock-outs, inability to procure materials not related to the price thereof, failure of power, restrictive governmental laws and regulations enacted after the date of this Contract, riots, civil unrest, acts of terrorism, insurrection, war, declaration of a state or national emergency or other reasons of a like nature not within the reasonable control of such party.

19. CONFLICT OF LAW:

This Contract shall be interpreted under, and enforced by the laws of the State of Definitive Networks Inc.
458
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
California without regard to any choice of law rules which may direct the application of laws of another jurisdiction. The Contract and obligations of the parties are subject to all valid laws, orders, rules, and regulations of the authorities having jurisdiction over this Contract (or the successors of those authorities). Any suits brought pursuant to this Contract shall be filed with the courts of the County of Contra Costa, State of California.

20. CLAIMS:

Any claim by Contractor against City hereunder shall be subject to Government Code §§ 800 et seq. The claims presentation provisions of said Act are hereby modified such that the presentation of all claims hereunder to the City shall be waived if not made within six months after accrual of the cause of action.

21. INTERPRETATION:

This Contract shall be interpreted as if drafted by both parties.

22. WARRANTY:

If any product is be provided to the City as part of this Contract, Contractor warrants as follows: Contractor possesses good title to the product and the right to transfer the product to City; the product shall be delivered to the City free from any security interest or other lien; the product meets any specifications contained herein; the product shall be free from material defects in materials and workmanship under normal use for a period of one (1) year from the date of delivery; and the product shall be fit for its intended purpose(s). Notwithstanding the foregoing, consumable and maintenance items (such as light bulbs and batteries) shall be warranted for a period of one hundred and eighty (180) days from the date of delivery. All repairs during the warranty period shall be promptly performed by Contractor, at Contractor's expense, including shipping.

23. SEVERABILITY:

In the event that any of the provisions or portions or applications thereof of this Contract are held to be unenforceable or invalid by any court of competent jurisdiction, City and Contractor shall negotiate an equitable adjustment in the provisions of the Contract with a view toward effecting the purpose of this Contract, and the validity and enforceability of the remaining provisions or portions or applications thereof, shall not be affected thereby.

24. AUTHORITY:

City warrants and represents that the signatory hereto (the Mayor of the City of Richmond or the City Manager) is duly authorized to enter into and execute this Contract on behalf of City. The party signing on behalf of Contractor warrants and represents that they are duly authorized to enter into and execute this Contract on behalf of Contractor, Definitive Networks Inc.
459
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
and shall be personally liable to City if they are not duly authorized to enter into and execute this Contract on behalf of Contractor.

25. WAIVER:

The waiver by City of any breach of any term or provision of this Contract shall not be construed as a waiver of any subsequent breach. Inspections or approvals, or statements by any officer, agent or employee of the City relating to the Contractor’s performance, or payment therefore, or any combination of these acts, shall not relieve the Contractor’s obligation to fulfill this Contract as prescribed; nor shall the City be thereby stopped from bringing any action for damages or enforcement arising from any failure to comply with any of the terms and conditions of this Contract.

26. COUNTERPARTS:

This Contract may be executed in any number of counterparts (including by fax, PDF, DocuSign, or other electronic means), each of which shall be deemed an original, but all of which shall constitute one and the same instrument.

27. SANCTUARY CITY CONTRACTING ORDINANCE (SCCO):

The Richmond Sanctuary City Contracting Ordinance No. 12-18 prohibits the City from granting and or retaining contracts with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor must submit the Sanctuary City Compliance Statement, attached hereto as Exhibit G.

Definitive Networks Inc.
460
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT E

SPECIAL CONDITIONS
The General Conditions are hereby amended to include the following modifications and/or provisions (if applicable, otherwise please state “NONE”):

Definitive Networks Inc.

The contract is eligible for up to two (2) additional one (1) year extensions at the mutual option of the parties if it is deemed to be in the best interests of the City, as stipulated in Richmond Municipal Code Section 2.52.370(b). Each extension shall not to exceed an additional $63,917 per year for the extended term.
461
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT F

INSURANCE PROVISIONS
☐ CHECK HERE IF RISK MANAGEMENT HAS APPROVED WAIVING INSURANCE REQUIREMENTS FOR THIS CONTRACT.

1. CERTIFICATES: Before the commencement of the terms of this Contract, and during the entire term of this Contract and any extension or modification thereof, Contractor shall furnish the City’s Risk Manager with certificates showing the type, amount, class of operations covered, effective dates and dates of expiration of insurance coverage in compliance with coverage requirements set forth by the City and incorporated herein.

Such certificates, which do not limit Contractor’s indemnification, shall also contain substantially the following statement:
“Should any of the above insurance covered by this certificate be canceled or coverage reduced before the expiration date thereof, the insurer affording coverage shall provide thirty (30) days’ advance written notice to the City of Richmond.

Attention: Risk Manager.”
Contractor shall maintain in force at all times during the performance of this Contract all appropriate coverage of insurance required by this Contract with an insurance company licensed to offer insurance business in the State of California with a current A.M. Best’s rating of no less than A:VII or Standard & Poor’s Rating (if rated) of at least BBB unless otherwise acceptable to the City. Contractor shall deliver updated insurance certificates to the City at the address set forth in Exhibit C prior to the expiration of the existing insurance certificate for the duration of the term of Contract.

Endorsements naming the City, its City Council, boards, commissions, officials, employees, agents, and volunteers as additional insured shall be submitted with the insurance certificates.

2. COVERAGE REQUIREMENTS: The City’s insurance requirements depend upon the type of service being provided and/or the provider. The City’s insurance requirements will fall into one of the following categories (unless otherwise provided by the City):

Consultants and Contractors – Type 1
Professional Services – Type 2
Environmental Risk/Hazardous Waste Material – Type 3
Lease of City Property – Type 4
Vendors, Suppliers, Small Grant Recipients & Nonprofit Organizations – Type 5 Transportation Providers – Type 6
Professional Services Pyrotechnics – Type 7
Cyber and I.T. Risks – Type 8
Definitive Networks Inc.
462
___ Exhibit F
___ Section 8
City of Richmond - Insurance Requirements - Type 2:

Professional Services
Type 2 – Page 1 of 3
Revised: September 2011
In all instances where CONTRACTOR or its representatives will provide professional services (architects, engineers, construction management, counselors, medical professionals, hospitals, clinics, attorneys, consultants, accountants, etc.) to the City of Richmond (City), the City requires the following MINIMUM insurance requirements and limits.

CONTRACTOR shall procure and maintain for the duration of the contract, agreement, or other order for work, services or supplies, insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the work hereunder and the results of that work by the CONTRACTOR, its agents, representatives, employees or subcontractors. Maintenance of proper insurance coverage is a material element of the contract. Failure to maintain or renew coverage or to provide evidence of renewal may be treated by the City as a material breach of contract.

CONTRACTOR agrees that in the event of loss due to any of the perils for which it has agreed to provide Commercial General Liability insurance, CONTRACTOR shall look solely to its insurance for recovery.

CONTRACTOR hereby grants to CITY, on behalf of any insurer providing Commercial General Liability insurance to either CONTRACTOR or CITY with respect to the services of CONSULTANT herein, a waiver of any right to subrogation which any such insurer of said CONTRACTOR may acquire against the CITY by virtue of the payment of any loss under such insurance.

Original, signed certificates and original, separate policy endorsements, naming the City as an additional insured for general liability coverage, as well as a waiver of subrogation for Workers’ Compensation insurance, shall be received and approved by the City before any work may begin. However, failure to do so shall not operate as a waiver of these insurance requirements.

City reserves the right to modify or require additional coverages for specific risk exposures depending on scope of CONTRACTORS work.

Minimum coverage is detailed below. The policy limits of coverage shall be made available to the full limits of the policy. The minimum limits stated herein shall not serve to reduce the policy limits of coverage of CONTRACTOR.

Minimum Scope of Insurance – the following forms shall be provided and coverage shall be at least as broad as the following:

1. Insurance Services Office Commercial General Liability coverage (ISO Occurrence Form CG 0001), and including coverage for bodily and personal injury, property damage, and products and completed operations (if applicable).

2. Insurance Services Office Automobile Liability coverage (ISO Form CA 0001, Code 1, Any Auto).

3. Original and Separate Additional Insured Endorsement for General Liability (ISO Form CG 20 10 11/85 or its equivalent) with primary and non-contributory language.

4. Workers’ Compensation Insurance as required by the State of California including Employer’s Liability coverage.

5. Original and Separate Waiver of Subrogation for Workers’ Compensation insurance.

6. Professional Liability or Errors & Omissions Liability Insurance appropriate to the CONTRACTOR’s profession (if required.)
Required Coverage Minimum Limits
Workers’ Compensation and
Employers’ Liability
Statutory limits as required by the State of California including $1 million Employers’ Liability per accident, per employee for bodily injury or disease.

If CONTRACTOR is self-insured, provide a certificate of Permission to SelfInsure, signed by the California Department of Industrial Relations and SelfInsurance. If contractor is a sole proprietor (has no employees) than contractor must sign “Contractor Release of Liability” found at:
http://www.ci.richmond.ca.us/index.aspx?nid=61.

General Liability
(primary and excess limits
combined)
$2,000,000 per occurrence for bodily injury, personal injury and property damage. If the policy includes a general aggregate, either the general aggregate shall apply separately to this project, service or location or the minimum required aggregate limit shall be twice the per occurrence limit ($4 million aggregate limit).

Policy shall be endorsed to name the City of Richmond as an additional insured per the conditions detailed below.
463
___ Exhibit F
___ Section 8
City of Richmond - Insurance Requirements - Type 2:

Professional Services
Type 2 – Page 2 of 3
Revised: September 2011
Automobile Liability $1,000,000 per occurrence for bodily injury and property damage.

PROJECT COST REQUIRED LIMIT
$0 - $1 million $1 million p/o
$1 million - $5 million $2 million p/o
Over $5 million $5 million p/o

Professional Liability or Errors &
Omissions Liability –
Required for all professionals
including architects, engineers,
consultants, construction
management, counselors, medical
professionals, hospitals, clinics,
attorneys and accountants, & other
consultants as may be required by
the City.

Required Policy Conditions
Additional Insured Endorsement Applicable to General Liability coverage.

The City of Richmond, its officers, officials, employees, agents and volunteers are to be named as additional insureds for all liability arising out of the operations by or on behalf of the named insured including bodily injury, deaths and property damage or destruction arising in any respect directly or indirectly in the performance of this contract.

ISO form CG 20 10 (11/85) or its equivalent is required. If the Contractor is supplying their product or providing a service then the endorsement must not exclude products and completed operations coverage. If it does, then CG 20 37 (10/01) is also required.

SAMPLE Endorsements can be found at
http://www.ci.richmond.ca.us/index.aspx?nid=61.

Primary and Noncontributory The contractor’s insurance coverage must be primary coverage as it pertains to the City, its officers, officials, employees, agents and volunteers. Any insurance or self insurance maintained by the City is wholly separate from the insurance of the contractor and in no way relieves the contractor from its responsibility to provide insurance.

Waiver of Subrogation
Endorsement Form
Contractor’s insurer will provide a Waiver of Subrogation in favor of the City for Workers’ Compensation Insurance during the life of this contract.

SAMPLE Endorsements can be found at
http://www.ci.richmond.ca.us/index.aspx?nid=61.

Deductibles and Self-Insured
Retentions
Any deductible or self-insured retention must be declared to and approved by the City. At the option of the City either the insurer shall reduce or eliminate such deductibles or self-insured retention as respects the City or the CONTRACTOR shall procure a financial guarantee in an amount equal to the deductible or self-insured retention guaranteeing payment of losses and related investigations, claims administration and defense expenses.

Contractor is responsible for satisfaction of the deductible and/or self-insured retention for each loss.

A. M. Best Rating A:VII or Better. If the A.M. Best Rating falls below the required rating, CONTRACTOR must replace coverage immediately and provide notice to City.

Umbrella/Excess Liability Policies
If an Umbrella or Excess Liability Policy is used to meet the liability limits, coverage shall be as broad as specified for underlying coverage’s and cover those insured in the underlying policies. 464
___ Exhibit F
___ Section 8
City of Richmond - Insurance Requirements - Type 2:

Professional Services
Type 2 – Page 3 of 3
Revised: September 2011
Claims-Made Policies
If any insurance policy is written on a claims-made form: 1) the retroactive date must be shown, and must be before the date of the contract or the beginning of contract work. 2) Insurance must be maintained and evidence of insurance must be provided for at least five (5) years after completion of the contract of work. 3) If coverage is canceled or non-renewed, and not replaced with another claims-made policy form with a retroactive date prior to the contract effective date, the Contractor must purchase an extended period coverage for a minimum of five (5) years after completion of contract work.

Subcontractors
CONTRACTOR shall include all subcontractors as insured under its policies or shall furnish to the City for review and approval, separate certificates and endorsements for each subcontractor. All coverage for subcontractors shall be subject to all of the requirements stated herein.

CONTRACTOR agrees to defend and indemnify the City of Richmond for any damage resulting to it from failure of either CONTRACTOR or any subcontractor to take out or maintain the required insurance policies. The fact that insurance is obtained by CONTRACTOR, and/or CONTRACTOR’s subcontractors, will not be deemed to release or diminish the liability of CONTRACTOR, including, without limitation, liability under the indemnity provisions of this contract. Damages recoverable by CITY from CONTRACTOR or any third party will not be limited by the amount of the required insurance coverage.

Verification of Coverage
All original certificates and endorsements shall be received and approved by the City before work may begin.

The City of Richmond reserves the right to require complete, certified copies of all required insurance policies including endorsements affecting the coverage at any time.

Original insurance certificates and required policy endorsements shall be mailed or delivered to the Designated Project Manager for the City of Richmond.

Insurance certificates and endorsements may be faxed to the Designated Project Manger. However, CONTRACTOR must mail the original certificates and endorsements to Designated Project Manager once faxed.

Continuous Coverage
CONTRACTOR shall maintain the required insurance for the life of the contract. Should the CONTRACTOR cease to have insurance as required during this time, all work by the CONTRACTOR pursuant to this agreement shall cease until insurance acceptable to the City is provided. In the event that CONTRACTOR fails to comply with the City’s insurance requirements, the City may take such action as it deems necessary to protect the City’s interests. Such action may include but is not limited to termination of the contract, withholding of payments, or other actions as the City deems appropriate.

If services or the scope of work extend beyond the expiration dates of the required insurance policies initially approved by the City, CONTRACTOR must provide updated certificates and endorsements indicating that the required coverage, terms and conditions are still in place. Renewal certificates and updated endorsements shall be mailed to the Designated Project Manager.

Cancellation
CONTRACTOR shall ensure that coverage shall not be cancelled, reduced or otherwise materially changed except after thirty (30) days’ prior written notice has been given to the City.

Reporting Requirements
Any failure to comply with reporting or other provisions of the policies including breaches of warranties shall not affect coverage provided to the City, its officers, officials, employees or volunteers.

Consistent with Public Policy
The insuring provisions, insofar as they may be judged to be against public policy shall be void and unenforceable only to the minimum extent necessary so that the remaining terms and provisions herein may be consistent with public policy and thus enforceable.
465
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
The insurance requirements classification applicable to this Contract shall be attached to this Exhibit F and made a part hereof.

3. FAILURE TO SECURE: If Contractor at any time during the term hereof should fail to secure or maintain the foregoing insurance, the City shall be permitted to obtain such insurance in Contractor’s name or as an agent of Contractor and shall be compensated by Contractor for the costs of the insurance premiums at the maximum rate permitted by law and computed from the date written notice is received that the premiums have not been paid.

4. SUFFICIENCY OF INSURANCE: The insurance limits required by the City are not represented as being sufficient to protect Contractor. Contractor is advised to consult Contractor’s insurance broker to determine adequate coverage for Contractor. The coverage and limits shall be (1) the minimum coverage and limits specified in this Contract; or (2) the broader coverage and maximum limits of the coverage carried by or available to Contractor; whichever is greater.

INSERT INSURANCE REQUIREMENTS CLASSIFICATION APPLICABLE TO THIS CONTRACT: (IF NECESSARY, CONFIRM WITH RISK MANAGER)
Definitive Networks Inc.
466
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT G

SANCTUARY CITY COMPLIANCE STATEMENT
The undersigned, (hereafter "Contractor"), has had an opportunity to review the requirements of City of Richmond Ordinance 12-18 (hereafter "Sanctuary City Contracting Ordinance" or “SCCO”).

Contractor understands and agrees that the City may choose with whom it will maintain business relations and may refrain from contracting with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor understands the meaning of the following terms used in the SCCO:
a. "Data Broker” means either of the following:
i. The collection of information, including personal information about consumers, from a wide variety of sources for the purposes of reselling such information to their customers, which include both private-sector business and government agencies;
ii. The aggregation of data that was collected for another purpose from that for which it is ultimately used.
b. “Extreme Vetting” means data mining, threat modeling, predictive risk analysis, or other similar services."
Contractor understands that it is not eligible to receive or retain a City contract if at the time the Contract is executed, or at any time during the term of the Contract, it provides Data Broker or Extreme Vetting services to ICE.

Contractor further understands and agrees that Contractor's failure to comply with the SCCO shall constitute a material default of the Contract and the City Manager may terminate the Contract and bar Contractor from bidding on future contracts with the City for five (5) years from the effective date of the contract termination.

By executing this statement, Contractor certifies that it complies with the requirements of the SCCO and that if at any time during the term of the Contract it ceases to comply, Contractor will promptly notify the City Manager in writing. Any person or entity who knowingly or willingly supplies false information in violation of the SCCO shall be guilty of a misdemeanor and subject to a $1,000 fine.

Based on the foregoing, the undersigned declares under penalty of perjury under the laws of the State of California that the foregoing is true and correct.

Printed Name: Title:

Signed: Date:

Business Entity:

Definitive Networks Inc.
467

July 7, 2026
Mayor's Office
DATE: July 7, 2026
TO: Members of the City Council
FROM: Mayor Martinez
Subject: Appointment of Gage Eda to the Richmond Youth
Council)
FINANCIAL IMPACT: There is no financial impact.

PREVIOUS COUNCIL
ACTION:

None.

STATEMENT OF THE
ISSUE:

Gage Eda is applying to serve on the Richmond Youth
Council.

RECOMMENDED ACTION: APPOINT Gage Eda to the Richmond Youth Council to a vacant seat with a new term ending December 31, 2027
– Mayor’s Office (Mayor Eduardo Martinez 510-620-
6503).

DISCUSSION:

Gage Eda is seeking appointment to the Richmond Youth Council. Through his volunteer work with Victory Outreach Richmond Unhoused, San Francisco Coptic Orthodox Feeding Service, Pinole Valley Night, Reimagine Richmond Tiny Homes, and the Greater Richmond Interfaith Program shelter, Gage has demonstrated compassion for Richmond residents and an ability to commit to a program and see it through. These attributes make Gage a strong candidate for the Richmond Youth Council.

DOCUMENTS ATTACHED:

Attachment 1 – Gage Eda’s redacted application
AGENDA
REPORT
468
469
470
471

July 7, 2026
Mayor's Office
DATE: July 7, 2026
TO: Members of the City Council
FROM: Mayor Martinez
Subject: Appointment of Samuel Goldheim to the Richmond Youth Council
FINANCIAL IMPACT: There is no financial impact.

PREVIOUS COUNCIL
ACTION:

None.

STATEMENT OF THE
ISSUE:

Samuel Goldheim is applying to serve on the Richmond
Youth Council.

RECOMMENDED ACTION: APPOINT Samuel Goldheim to the Richmond Youth Council to a vacant seat with a new term ending October 1, 2027 – Mayor’s Office (Mayor Eduardo Martinez 510-
620-6503).

DISCUSSION:

Samuel Goldheim is seeking application to the Richmond Youth Council. Samuel is a lifelong Richmond resident who is passionate about public service and ensuring that the city's youth have the opportunity to succeed and thrive. Through volunteering at community events such as Valley View Elementary School’s Fall Festival and the Pinole Hercules Little League Closing Ceremony, he has developed a strong commitment to giving back and supporting other youth. He is actively involved in numerous school AGENDA
REPORT
472

July 7, 2026
clubs and has consistently earned recognition on the Honor Roll and Principal’s List each quarter. He is eager to contribute his ideas, enthusiasm, and dedication to serving the community and representing the voices of Richmond's youth.

DOCUMENTS ATTACHED:

Attachment 1 – Samuel Goldheim’s redacted application
473
474
475

July 7, 2026
Police Department
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: Timothy Simmons, Chief of Police
Lina Velasco, Community Development Director
Jesus Morales, Housing Manager
Michelle Milam, Crime Prevention Manager
Subject: Contract with Contra Costa County’s Coordinated Outreach, Referral, and Engagement (CORE) for
Homeless Outreach Services
FINANCIAL IMPACT: The first‑ year expenditure of $528,239 is included within the proposed Fiscal Year 2026-2027 Police Department
and Community Services budgets, and funding for the
remaining two years of the contract term will be budgeted accordingly in subsequent fiscal years. The total
not-to-exceed amount for the three-year contract is
$1,660,150 (Account String: 01193021‑ 400201).

PREVIOUS COUNCIL
ACTION:

December 18, 2018
July 2, 2019
December 7, 2021
October 18, 2022
May 2, 2023
July 11, 2023
April 1, 2025

STATEMENT OF THE
ISSUE:

The City of Richmond is seeking approval to renew and
restructure its Coordinated Outreach, Referral, and
Engagement (CORE) Homeless Outreach Services
contract with Contra Costa County for a new and revised three-year term.

The current service model provides limited outreach
coverage and does not meet the growing demand for
homelessness services within the City. In addition,
AGENDA
REPORT
476

July 7, 2026
temporary funding sources supporting emergency
housing interventions are set to expire.

The proposed contract addresses these gaps by
maintaining existing services originally established in 2018, fulfilling grant obligations, and expanding outreach capacity to better align with regional standards and
community need.

RECOMMENDED ACTION: APPROVE a contract with Contra Costa County for Coordinated Outreach, Referral, and Engagement
(CORE) Homeless Outreach Services, including the
expansion of outreach coverage to six days per week
and the addition of housing stability resources, for a total amount not to exceed $1,660,150, for the term of July 1, 2026, through June 30, 2029 – Richmond Police
Department and Community Development Department
(Chief Timothy Simmons 510-621-1802/Lina Velasco
510-620-6841).

DISCUSSION:

Since 2017, the City of Richmond has operated under a camping ordinance that requires the City to offer services to unhoused individuals before conducting any encampment abatement activities. To meet this obligation, the City established a partnership with Contra Costa County to provide Coordinated Outreach, Referral, and Engagement (CORE) services. This partnership was approved by the City Council on December 18, 2018, with services beginning October 1, 2018, through June 30, 2019.

The initial model aligned with other jurisdictions in Contra Costa County, including the City of San Pablo, and ensured that individuals residing in encampments were connected to services prior to abatement.

CORE functions as Contra Costa County’s primary field‑ based outreach system, connecting unsheltered individuals with the broader coordinated entry system. Referrals are initiated through the 2-1-1 referral system and coordinated in partnership with existing City staff from Crime Prevention, Housing and Community Development, and the community crisis response program’s Reach Out with Compassion and Kindness (ROCK) Team. CORE teams provide transportation to shelters and appointments and maintain ongoing service coverage throughout West County, including Richmond. In July 2023, City Council approved the use of the second round of Encampment Resolution Funding (ERF2), which expanded resources available for CORE services.

However, the additional funding was insufficient to meet all encampment‑ related needs. On June 16, 2026, the City Council approved separating ERF2 into a standalone contract to provide the City with greater flexibility in addressing community priorities using its general fund money included in the proposed 2026-2027 Fiscal Year budgets of the Richmond Police and Community Services Departments. 477

July 7, 2026
Homelessness in Richmond: Data Overview
Homelessness within Richmond is monitored primarily through the Point‑ in‑ Time Count and the Homeless Management Information System (HMIS). For the purposes of this report, HMIS data reflects CORE All Teams’ activities in Richmond between April 1, 2025, and March 31, 2026. During this period, CORE conducted 3,855 contacts with 1,153 unduplicated clients, serving 927 individuals and 86 families. Most households consisted of single adults, who represented more than 80 percent of all contacts. The demographic breakdown shows that 59.76 percent identified as male and 39.72 percent as female, with a small percentage identifying as transgender. Adults aged 25 to 61 comprised more than 74 percent of those served, with minors, transition‑ aged youth, and seniors making up the remainder. Racial demographics reflect longstanding disproportionalities in homelessness with 43.45 percent identified as Black or African American, followed by 18.73 percent identifying as White and 17.61 percent as Hispanic/Latino.

The data also indicates that 27.23 percent of individuals experienced homelessness over five years. A significant majority—61.67 percent—reported a disabling condition.

Mental health, physical health, and chronic medical issues were frequently reported, appearing in 510, 298, and 278 cases respectively. Across all clients, CORE delivered 14,523 services, including housing navigation, healthcare coordination, shelter referrals, and basic needs support. The data demonstrates the high level of complexity among those served and the need for sustained and intensive outreach.

A more targeted effort is reflected in the ERF2 CORE team’s work with encampment populations. During the same reporting period, ERF2 teams completed 652 contacts with 165 unduplicated clients, serving 133 individuals and 20 families. Household and demographic patterns were similar to the general CORE population, with single adults constituting more than 80 percent of households. Nearly half of those served reported homelessness lasting more than five years, and more than half reported a disabling condition. ERF2 teams delivered 3,429 services, focusing heavily on housing navigation, healthcare coordination, shelter placements, and stabilization supports. This data confirms that encampment residents generally present with more acute needs and require higher‑ intensity engagement.

Current Contract Structure
The existing CORE services structure, created in 2018 and extended through June 30, 2026, is a shared partnership between Richmond and San Pablo. The model was designed as a cost‑ sharing measure in which a single CORE team operates eight hours per day, three days per week in Richmond—Monday, Wednesday, and Friday— with San Pablo utilizing the team the remaining days. In 2023, ERF2 resources were integrated into this structure, supplementing the original funding model. While this arrangement has provided consistent outreach over the years, it limits the City’s ability to offer daily engagement or maintain continuity of services for residents with urgent or time‑ sensitive needs.
478

July 7, 2026
Proposed Contract Structure
The proposed three‑ year contract maintains the existing Richmond‑San Pablo partnership while expanding the City’s overall outreach capacity through three integrated components. First, the contract preserves the shared CORE team and the cost‑ sharing structure. Second, it adds a supplemental team that will operate on Tuesday, Thursday, and Saturday, effectively doubling service availability from three to six days per week. Richmond is currently the only large city in Contra Costa County without full‑ time CORE coverage, and this expansion will bring the City into alignment with regional best practices.

Finally, the contract includes the addition of a full‑ time Care Navigator, whose role will focus on coordination between CORE, the ROCK Team, service providers, and emergency shelter programs. The Care Navigator will manage follow‑ up on placements, support long‑ term housing transitions, and provide the level of case management needed for high‑ acuity clients. At present, these functions are being absorbed informally by Police Department staff, which is not sustainable.

The proposal also establishes a $100,000 annual Housing Stability Fund that will allow outreach teams to address barriers that prevent individuals from accessing emergency shelter or interim housing. This flexible fund may be used for emergency motel stays, vehicle buybacks, rental deposits, food support, and other stabilization needs. The fund replaces expiring American Rescue Plan Act (ARPA) dollars and ensures that the City can continue providing rapid‑ response assistance.

CORE’s Fiscal Year 2026-2029 Cost Schedule outlines the quarterly invoice amounts and annual expenses that the City of Richmond is responsible for paying and includes a total three-year contract not-to-exceed amount of $1,660,150 (Attachment 2).

Operational Need for Expansion
The City’s current Monday‑Wednesday‑ Friday outreach schedule creates substantial service gaps that limit residents’ ability to access shelter or support on days when outreach is unavailable. These gaps disrupt continuity, delay interventions, and result in inconsistent engagement at encampments. At the same time, many emergency shelters regularly operate at or near capacity, and individuals living in vehicles, RVs, or with pets face additional constraints related to shelter admission. Expanding service frequency, adding a second team, and establishing a flexible Housing Stability Fund will significantly improve the City’s ability to respond quickly and effectively to community needs. These enhancements will strengthen coordination with the ROCK Team, allow for more consistent case conferencing, and improve outcomes for individuals with high and persistent needs.

Conclusion
The proposed contract represents an important evolution of the City’s homelessness response system. It maintains key regional partnerships, fulfills prior grant obligations, and expands the City’s capacity to provide timely, consistent, and responsive services.

By clarifying available funding and moving ERF2 resources into a separate contract, the 479

July 7, 2026
City will be better positioned to address City-wide needs without restrictive funding limitations. Together, these changes strengthen the City’s ability to coordinate outreach, connect residents to shelter, and respond more effectively to the needs of Richmond’s unhoused community.

DOCUMENTS ATTACHED:

Attachment 1 – Standard Contract
Attachment 2 – CORE FY26-29 Cost Schedule
Attachment 3 – HMIS Data Summary (April 2025 – March 2026) 480

CITY OF RICHMOND

STANDARD CONTRACT
Department: City Project Manager:

City Project Manager E-mail: City Project Manager Phone No:

Vendor No: Contract No:

Description of Services:

The parties to this STANDARD CONTRACT do mutually agree and promise as follows:

1. Parties. The parties to this Contract are the City of Richmond, a municipal corporation (“the City”), and the following named Contractor:

Contractor Name:

Street Address:

City, State, Zip Code:

Contact Person:

Telephone: Email:

Business License No:
☐ A California corporation, ☐ limited liability corporation ☐ general partnership, ☐ limited partnership, ☐ individual, ☐ non-profit corporation, ☐ individual dba as [specify:] ____________________ ☐ other [specify:] _______________________________

2. Term. The effective date of this Contract is _______________________ and terminates _________________ unless terminated earlier as set forth herein.

3. Payment Limit. City’s total payments to Contractor under this Contract shall not exceed $______________ (“Contract Payment Limit”) unless a Contract Amendment has been approved by the City Council or City Manager. If this amount includes a contingency, Contractor acknowledges that any use of such contingency shall be for work beyond the original scope of services and requires prior written authorization by the City. If noted below, Compensation for work done under this Contract, shall not exceed as follows:

FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________

4. Contractor’s Obligations. Contractor agrees to perform all work at its own cost and expense, to furnish all labor, tools, equipment, materials, except as otherwise specified, in accordance with the Service Plan set forth in Exhibit A, attached hereto and incorporated herein.

5. City Obligations. City shall make payments to the Contractor in accordance with the Payment Provisions set forth in Exhibit B, attached hereto and incorporated herein.

POLICE MICHELLE MILAM [email protected] (510) 620-6546 8251 8021 Contra Costa County Health, Community Response Division will provide outreach, transportation, and case management services to the City of Richmond's unsheltered populati Contra Costa County Health Services Department, Community Response Division 2400 Bisso Lane Suite D 2nd Floor Concord, CA 94520 Jenny Robbins (925) 608-6713 [email protected] N/A Government Agency July 1, 2026 June 30, 2029 1,660,150.00 481

6. Authorized Representatives and Notices. This Contract is subject to the Authorized Representatives and Notices Provisions (Exhibit C), attached hereto and incorporated herein.

7. General Conditions. This Contract is subject to the General Conditions (Exhibit D), which are attached hereto and incorporated herein.

8. Special Conditions. This Contract is subject to the Special Conditions (Exhibit E) (if any), which are attached hereto and incorporated herein.

9. Insurance Provisions. This Contract is subject to the Insurance Provisions (Exhibit F), which are attached hereto and incorporated herein.

10. Sanctuary City Compliance Statement. This Contract is subject to the Sanctuary City Compliance Statement (Exhibit G), which is attached hereto and incorporated herein.

11. Signatures. These signatures attest the parties' agreement hereto:

CITY OF RICHMOND,
a municipal corporation [BUSINESS NAME]
(* The Corporation Chairperson of the Board, President, or Vice President should sign below)
By: _________________________ By: ___________________________ Title: ________________________ Title: __________________________ Date Signed: _________________ Date Signed: ___________________ I hereby certify that this Contract (* The Corporation Chief Financial Officer or Assistant has been approved by City Council Treasurer, or Secretary or Assistant Secretary should or the City Manager. sign below)
By: _________________________ By: ___________________________ City Clerk Title: __________________________
Date Signed: ____________________
Approved as to form:
(NOTE: Pursuant to California Corporations Code Section By: _________________________ 313, if Contractor is a corporation or nonprofit organization, City Attorney this Contract (1) must be signed by (a) the Chairperson of the Board, President, or Vice-President and (b) the
Chief Financial Officer or Assistant Treasurer, or
Secretary or Assistant Secretary)
LIST OF ATTACHMENTS:

Service Plan Exhibit A
Payment Provisions Exhibit B
Authorized Representatives and Notices Exhibit C
General Conditions Exhibit D
Special Conditions Exhibit E
Insurance Provisions Exhibit F
Sanctuary City Compliance Statement Exhibit G
Contra Costa County Health Services Department, Community R 482
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT A

SERVICE PLAN
Contractor shall, to the satisfaction of the Project Manager (set forth in Exhibit B), perform the following services and be compensated as outlined below [or attach service plan if necessary]:
8021 Contra Costa County Health Services Department, C
See Attached Service Plan.
483

EXHIBIT A - SERVICE PLAN
Contra Costa County Health, Community Response Division Contract No. 8021/Vendor No. 8251

1. Identify and initiate contacts with homeless individuals living on the streets, assess their housing and transportation needs, and facilitate connections to shelter, benefits, behavioral health and primary healthcare services and other resources. CONTRACTOR will provide culturally competent services to the homeless community, and encourage Richmond-based local hiring efforts.

2. Respond to calls for outreach and engagement from the CITY’s employees, including, but not limited to, Public Safety, Community Services, Parks Staff, and ROCK. At the commencement of the term of this AGREEMENT, CONTRACTOR shall provide to CITY a list of the names of persons (and their contact information) who will be assigned to respond to such calls.

Conduct a standardized intake and needs assessment assuring all homeless individuals contacted are entered into the Homeless Management Information System used by the CONTRACTOR.

3. Conduct VI-SPDAT (Vulnerability Index-Service Prioritization Assistance Tool), a housing assessment tool, assuring that homeless individuals who are provided services hereunder are entered into the Coordinated Entry system for prioritizing their needs for longer term housing.

4. Partner with assigned CITY officer(s) during CORE Team work shifts throughout the week as needed and as determined by the CITY coordinator. Connect homeless individuals, also designated as “homeless clients”, via phone or in person with other points in the homeless service continuum including, but not limited to, interim housing, substance abuse treatment and mental health counseling, and benefits, etc.

5. Perform special assignments to include, but not limited to, homeless counts, Homeless Connect and presentations. The number and nature of said assignments shall be determined by the CITY coordinator who shall timely inform CONTRACTOR of CONTRACTOR’s obligation to perform them. Conduct routine canvassing of strategic areas within the CITY’s limit on foot and via vehicle as designated by the CITY coordinator.

6. Observe and report threats to the health and/or safety of homeless individuals (or threats by homeless individuals to the health or safety of others) encountered in the field and determine the need to summon uniformed police, fire or other emergency personnel. Maintain communications with the CITY’s Police Department to report crime.

7. CORE Team supervisors and outreach workers will participate in monthly meetings with the CITY’s Police Management, as well as, with public and private partners as deemed appropriate by the CITY coordinator.

8. In addition, CONTRACTOR will provide quantitative and qualitative service impact reports to the CITY at intervals determined and required by the CITY. The reports will assist the CITY in evaluating outcomes of this AGREEMENT.
484

EXHIBIT A - SERVICE PLAN
Contra Costa County Health, Community Response Division Contract No. 8021/Vendor No. 8251

9. CONTRACTOR will provide intensive services as directed including, but not limited to, parks, public property, commercial business corridors, and the Department of Infrastructure and Maintenance, and encampments. CONTRACTOR will assist on an as needed basis with coordination of the City’s homeless efforts, including the City’s Taskforce on Homelessness and support for the City's encampment resolution efforts. 485
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT B

PAYMENT PROVISIONS

1. COMPENSATION TO CONTRACTOR:
a. Provided Contractor is not in default under this Contract, Contractor shall be compensated in the manner set forth herein.
b. All payments made pursuant to this Contract shall be subject to the Contract Payment Limit. The Payment Limit includes expenses (phones, photocopying, meals and travel, etc.). Invoices shall be adequately detailed, based on accurate records, and be in a form reasonably satisfactory to the City. Contractor may be required to provide back-up material upon request. c. All City vendors receiving new contracts shall sign up to receive electronic payments through the City’s Automated Clearinghouse (ACH) payments service/provider.

2. SUBMISSION OF INVOICES:

Contractor shall submit timely invoices by email to
[email protected] and/or to the following address:

Attention: City of Richmond Finance/Account Payable
Project Manager: _______________________
P.O. Box 4046
Richmond, CA 94804

3. All invoices that are submitted by Contractor shall be subject to the approval of the City Project Manager, _______________________, before payments shall be authorized.
a. The City will pay invoice(s) within 45 days after completion of services to the City’s satisfaction. The City shall not pay late fees or interest.
b. All appropriate permits, certificates, and licenses, including a City business license shall be obtained and maintained for the duration of this Contract before any payment is authorized.

4. All insurance coverage required by this Contract shall be provided by the Contractor before this Contract is executed by the City. The insurance coverage required by this Contract shall be maintained by Contractor for the duration of this Contract and must be in place before any payment is authorized.

MICHELLE MILAM MICHELLE MILAM 8021 Contra Costa County Health Services Department, C 486
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT C

AUTHORIZED REPRESENTATIVES AND NOTICES

1. All required written notices shall be delivered: (i) by hand; or (ii) sent by registered, express, or certified mail, with return receipt requested or with delivery confirmation requested from the U.S. postal service; or (iii) sent by overnight or same day courier service at the party’s respective address listed in this Section.

2. Each notice shall be deemed to have been received on the earlier to occur of:
actual delivery or the date on which delivery is refused; or three (3) days after notice is deposited in the U.S. mail or with a courier service in the manner described above (Sundays and City holidays excepted).

3. Either party may, at any time, change its notice address (other than to a post office box address) by giving the other party three (3) days prior written notice of the new address.

4. All notices, demands, requests, or approvals from Contractor to the City shall be addressed to the City at:

City of Richmond
450 Civic Center Plaza
Richmond, CA 94804
Email: ________________________________________________

5. All notices, demands, requests, or approvals from the City to Contractor shall be addressed to Contractor at:

Attn:

Email: ________________________________________________ MICHELLE MILAM [email protected] 8021 Contra Costa County Health Services Department, C Contra Costa County Health Services Department, Community Response Division 2400 Bisso Lane Suite D 2nd Floor Concord, CA 94520 [email protected] 487
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT D

GENERAL CONDITIONS

1. INDEPENDENT PARTIES:

Contractor hereby declares that Contractor is engaged as an independent business and Contractor agrees to perform the services as an independent contractor.

The manner and means of conducting the services and tasks are under the control of Contractor except to the extent they are limited by statute, rule or regulation and the express terms of this Contract. No civil service status or other right of employment will be acquired by virtue of Contractor’s services. None of the benefits provided by the City to its employees, including but not limited to unemployment insurance, workers’ compensation plans, vacation and sick leave, are available from the City to Contractor, its employees or agents. Deductions shall not be made for any state or federal taxes, FICA payments, PERS payments, or other purposes normally associated with an employer-employee relationship from any compensation due to Contractor. Payments of the above items, if required, are the responsibility of Contractor.

2. TIME IS OF THE ESSENCE:

Contractor and the City agree that time is of the essence regarding the performance of this Contract.

3. STANDARD OF CARE:

Contractor agrees to perform all services hereunder in a manner commensurate with the prevailing standards of like professionals or service Contractors, as applicable, in the San Francisco Bay Area and agrees that all services shall be performed by qualified and experienced personnel who are not employed by the City.

4. IMMIGRATION REFORM AND CONTROL ACT (IRCA):

Contractor assumes all responsibility for verifying the identity and employment authorization of all of its employees performing work hereunder, pursuant to all applicable IRCA or other federal, or state rules and regulations. Contractor shall indemnify, defend, and hold the City harmless from and against any loss, damage, liability, costs or expenses arising from any noncompliance of this provision by Contractor.

5. NON-DISCRIMINATION:

Consistent with the City’s policy and state and federal law that harassment and discrimination are unacceptable conduct, Contractor and its employees, contractors, and agents shall not harass or discriminate against any job applicant, City employee, or any other person on the basis of any kind of any statutorily (federal, state or local) protected class, including but not limited to: race, religious creed, color, national origin, ancestry, 8021 Contra Costa County Health Services Department, C
488
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
disability (both mental and physical) including HIV and AIDS, medical condition (e.g. cancer), genetic information, marital status, sex, gender, gender identity, gender expression, age, sexual orientation, pregnancy, political affiliation, military and veteran status or legitimate union activities. Contractor agrees that any violation of this provision shall constitute a material breach of this Contract.

6. CITY PROPERTY:
a. Each and every report, draft, work product, map, record, applicable plans, drawings, calculation, data, specification, video, graphic, or any other material or document produced, prepared or caused to be prepared by Contractor pursuant to or in connection with this Contract shall be the exclusive property of the City. b. Notwithstanding the foregoing, Contractor shall not be obligated to provide to City proprietary software or data which Contractor has developed or had developed for Contractor's own use; provided, however, that Contractor shall, pursuant to Section 11 below, indemnify, defend and hold the City harmless from and against any discovery or Public Records Act request seeking the disclosure of such proprietary software or data. c. No report, information or other data given to or prepared or assembled by Contractor pursuant to this Contract shall be made available to any individual or organization by Contractor without prior approval of the City Manager or their designee. d. Contractor shall, at such time and in such form as City Manager or their designee may require, furnish reports concerning the status of services and tasks required under this Contract.

7. RECORDS:
a. Contractor shall maintain complete and accurate records with respect to the services, tasks, work, documents and data in sufficient detail to permit an evaluation of Contractor’s performance under the Contract, as well as maintain books and records related to sales, costs, expenses, receipts and other such information required by the City that relate to the performance of the services and tasks under this Contract (collectively the “Records”).
b. All Records shall be maintained in accordance with generally accepted accounting principles and shall be clearly identified and readily accessible. Contractor shall provide free access to the Records to the representatives of the City or its designees during regular business hours upon reasonable prior notice. The City has the right to examine and audit the Records, and to make copies or transcripts therefrom as necessary, and to allow inspection of all proceedings and activities related to this Contract. Such Records, together with supporting documents, shall be kept separate from other documents and records and shall be maintained by Contractor for a period of five (5) years after receipt of final payment.
8021 Contra Costa County Health Services Department, C
489
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. If supplemental examination or audit of the Records is necessary due to concerns raised by the City’s preliminary examination or audit of records, and the City’s supplemental examination or audit of the records discloses a failure to adhere to appropriate internal financial controls, or other breach of this Contract or failure to act in good faith, then Contractor shall reimburse the City for all reasonable costs and expenses associated with the supplemental examination or audit.

8. PERMITS AND LICENSES:

Contractor, at its sole expense, shall obtain and maintain during the term of this Contract, all appropriate permits, certificates and licenses, including a City business license, required in connection with the performance of the services and tasks hereunder.

The failure to obtain such permits and licenses shall be a material breach of this Contract and grounds for immediate termination by City; provided, however, that City may waive the business license requirement in writing under unusual or extraordinary circumstances without necessitating any modification of this Contract to reflect such waiver.

9. TERMINATION:
a. Termination Without Default. Notwithstanding any provision herein to the contrary, the City may, in its sole and absolute discretion and without cause, terminate this Contract at any time prior to completion by Contractor of the project or services hereunder immediately upon transmission of written notice to Contractor as provided in Exhibit C “Authorized Representatives and Notices”.
b. Termination in the Event of Default. Should Contractor fail to perform any of its obligations hereunder, within the time and in the manner provided or otherwise violate any of the terms of this Contract, City may immediately terminate this Contract by giving written notice of such termination, stating the reasons for such termination. Contractor shall be compensated as provided in Exhibit B; provided, however, there shall be deducted from such amount the amount of damage, including attorney's fees, expert witness fees and costs, if any, sustained by City by virtue of Contractor's breach of this Contract. Additionally, in the event of such termination, the City may proceed with the work in any reasonable manner it chooses.

10. CONFLICT OF INTEREST:

Contractor acknowledges, represents and warrants that Contractor shall avoid all conflicts of interest (as defined under any federal, state or local statute, rule or regulation, or at common law) with respect to this Contract. Contractor further acknowledges, represents and warrants that no City official or employee has any economic interest, as defined in Title 2, California Code of Regulations §§ 18703.1 through 18703.5, with Contractor that would invalidate this Contract. Contractor acknowledges that in the event that Contractor shall be found by any judicial or administrative body to have any conflict of interest (as defined above) with respect to this Contract, all consideration received under 8021 Contra Costa County Health Services Department, C
490
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
this Contract shall be forfeited and returned to City forthwith. This provision shall survive the termination of this Contract for one (1) year.

11. HOLD HARMLESS:
a. To the fullest extent permitted by law, Contractor shall indemnify, defend (with counsel acceptable to the City) and hold harmless the City, its City Council, boards, commissions, officials, employees, agents and volunteers (“Indemnitees”) from and against any and all loss, damages, liability, obligations, claims, suits, judgments, costs and expenses whatsoever, including attorney’s fees and costs of litigation (“Claims”), arising from or in any manner connected to Contractor’s performance of its obligations under this Contract or failure to comply with any of its obligations under this Contract or out of the operations conducted by Contractor even if the City is found to have been negligent. If the Claims filed against Indemnitees allege negligence, recklessness or willful misconduct on the part of Contractor, Contractor shall have no right of reimbursement against Indemnitees for the costs of defense even if negligence, recklessness or willful misconduct is not found on the part of Contractor. Contractor shall not have any obligations to indemnify Indemnitees if the loss or damage is found to have resulted solely from the negligence or the willful misconduct of the City. The defense and indemnification obligations of this Contract are undertaken in addition to, and shall not in any way be limited by, the insurance obligations contained in this Contract. b. This indemnification obligation shall survive this Contract and shall not be limited by any term of any insurance policy required under this Contract; provided however, that if this Contract is for design professional services, this indemnity provision is limited to claims that arise out of, pertain to, or relate to the negligence, recklessness, or willful misconduct of the design professional (as defined in California Civil Code section 2782.8).

12. LIMITATIONS UPON SUBCONTRACTING AND ASSIGNMENT:
a. This Contract binds the heirs, successors, assigns and representatives of Contractor. The Contractor shall not enter into subcontracts for any work contemplated under this Contract and shall not assign this Contract, nor any portion hereof or monies due or to become due, without the prior written consent of the City Council or its designee.
b. Contractor shall not assign, sublease, hypothecate, or transfer this Contract, or any interest therein, directly or indirectly, by operation of law or otherwise, without prior written consent of the City Manager. Contractor shall submit a written request for consent to transfer to the City Manager at least thirty (30) days in advance of the desired transfer.

The City Manager or their designee may consent or reject such request in their sole and absolute discretion. Any attempt to do so without said consent shall be null and void, and any assignee, sublessee, hypothecate or transferee shall acquire no right or interest by reason of such attempted assignment, hypothecation or transfer. However, claims for 8021 Contra Costa County Health Services Department, C
491
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
money against the City under this Contract may be assigned by Contractor to a bank, trust company or other financial institution without prior written consent. c. The sale, assignment, transfer or other disposition of any of the issued and outstanding capital stock of Contractor (if applicable), or of the interest of any general partner or joint venturer or syndicate member if Contractor is a partnership or jointventure or syndicate, which shall result in a change of control of Contractor, shall be deemed an assignment. For this purpose, control shall mean fifty percent or more of the voting power or twenty-five percent or more of the assets of the corporation, partnership or joint-venture.
d. Only those persons and/or businesses whose names and resumés are attached to this Contract shall be used in the performance of this Contract. However, if after the start of this Contract, Contractor wishes to use sub-contractors, at no additional costs to the City, then Contractor shall submit a written request for consent to add subcontractors including the names of the sub-contractors and the reasons for the request to the City Manager at least five (5) days in advance. The City Manager may consent or reject such requests in their sole and absolute discretion. e. Each sub-contractor shall be required to furnish proof of workers’ compensation insurance and shall also be required to carry general, automobile and professional liability insurance (as applicable) in reasonable conformity to the insurance carried by Contractor.
f. In addition, any tasks or services performed by sub-contractors shall be subject to each provision of this Contract. Contractor shall include the following language in their Contract with any sub-contractor: “Sub-Contractors hired by Contractor agree to be bound to Contractor and the City in the same manner and to the same extent as Contractor is bound to the City.”
g. The requirements in this Section 12 shall not apply to persons who are merely providing materials, supplies, data or information that Contractor then analyzes and incorporates into its work product.

13. SAFETY:
a. Contractor acknowledges that the City is committed to the highest standards of workplace safety. Contractor will be solely and completely responsible for conditions of all vehicles owned or operated by Contractor, including the safety of all persons and property during performance of the services and tasks under this Contract.

Contractor shall assume sole and complete responsibility for the safety of Contractor's employees and any of subcontractor's employees This requirement will apply continuously and not be limited to normal working hours. In addition, Contractor will comply with all safety provisions in conformance with U.S. Department of Labor Occupational Safety and Health Act, any equivalent state law, and all other applicable 8021 Contra Costa County Health Services Department, C
492
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
federal, state, county and local laws, ordinances, codes, and any regulations that may be detailed in other parts of the Contract. Where any of these are in conflict, the more stringent requirements will be followed. Contractor’s failure to thoroughly familiarize itself with the aforementioned safety provisions will not relieve it from compliance with the obligations and penalties set forth herein.
b. Contractor will immediately notify the City (in no event less than 24 hours) of any incident of death, serious personal injury or substantial property damage that occurs in connection with the performance of this Contract. Contractor will promptly submit to the City a written report of all incidents that occur in connection with this Contract. This report must include the following information: (i) name and address of injured or deceased person(s); (ii) name and address of Contractor’s employee(s) involved in the incident; (iii) name and address of Contractor’s liability insurance carrier; (iv) a detailed description of the incident; and (v) a police report.
c. Contractor acknowledges that the City shall have the right to impose, at the City’s sole discretion, requirements that it deems are necessary to protect the health and safety of the City employees, residents, and visitors. Contractor agrees to comply with all such requirements, including, but not limited to, mandatory vaccinations, the use of personal protective equipment (e.g. masks), physical distancing, and health screenings.

Contractor also agrees to make available to the City, at the City’s request, records to demonstrate Contractor’s compliance with this Section.

14. INSURANCE:

Insurance requirements are set forth in Exhibit F to this Contract. Contractor shall abide by the insurance requirements set forth in said Exhibit F.

15. COMPLIANCE WITH ALL APPLICABLE LAWS:
a. During the term of this Contract, Contractor shall keep fully informed of all existing and future state and federal laws and all municipal ordinances and regulations of the City of Richmond which affect the manner in which the services or tasks are to be performed by Contractor, as well as all such orders and decrees of bodies or tribunals having any jurisdiction or authority over the same. Contractor shall comply with all applicable laws, state and federal and all ordinances, rules and regulations enacted or issued by the City. Compliance under this provision includes compliance with all provisions of the Richmond Municipal Code ("Municipal Code"), including Chapters 2.50,

2.52, 2.56, and 2.60, if applicable.
b. Contractor acknowledges that under § 2.60.070 of the Municipal Code ("Living Wage Ordinance"), Contractor is required to provide the City with documents and information verifying its compliance with the Living Wage Ordinance. Contractor shall notify each of its affected employees with regards to the wages that are required to be paid pursuant to the Living Wage Ordinance as prescribed in § 2.60.070 of the Municipal Code.
8021 Contra Costa County Health Services Department, C
493
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. Contractor shall comply with § 2.28.030 of the Municipal Code, obligating every Contractor or sub-Contractor under an agreement or sub-agreement with the City for public works, goods or services to refrain from discriminatory employment or practices on the basis of race, color, sex, sexual orientation, religious creed, national origin or ancestry of any employee, any applicant for employment or any potential sub-contractor. d. Contractor acknowledges that the City’s Drug Free Workplace Policy, Violence in the Workplace Policy and the Policy Against Workplace Harassment, are available on the City’s website at http://www.ci.richmond.ca.us/workplacepolicies.

Contractor agrees to abide by the terms and conditions of said policies.

16. INTEGRATED CONTRACT:

The Recitals and exhibits are a material part of this Contract and are expressly incorporated herein. This Contract represents the full and complete understanding of every kind or nature whatsoever between the parties hereto, and all preliminary negotiations and agreements of whatsoever kind or nature are merged herein. No verbal agreement or implied covenant shall be held to vary the provisions hereof. Any modification of this Contract will be effective only by written execution signed by both the City and Contractor.

17. CONFLICTING PROVISIONS:

In the event of a conflict between these General Conditions and those of any Exhibit or attachment hereto, these General Conditions shall prevail; provided, however, that any Special Condition as set forth in Exhibit E shall prevail over these General Conditions. In the event of a conflict between the terms and conditions of any two or more Exhibits or attachments hereto, those prepared by City shall prevail over those prepared by the Contractor, and the terms and conditions preferred by the City shall prevail over those preferred by the Contractor.

18. FORCE MAJEURE:

Neither party hereto shall be considered in default in the performance of its obligations hereunder to the extent that the performance of such an obligation is prevented or delayed by reason of acts of God, strikes, boycotts, lock-outs, inability to procure materials not related to the price thereof, failure of power, restrictive governmental laws and regulations enacted after the date of this Contract, riots, civil unrest, acts of terrorism, insurrection, war, declaration of a state or national emergency or other reasons of a like nature not within the reasonable control of such party.

19. CONFLICT OF LAW:

This Contract shall be interpreted under, and enforced by the laws of the State of 8021 Contra Costa County Health Services Department, C
494
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
California without regard to any choice of law rules which may direct the application of laws of another jurisdiction. The Contract and obligations of the parties are subject to all valid laws, orders, rules, and regulations of the authorities having jurisdiction over this Contract (or the successors of those authorities). Any suits brought pursuant to this Contract shall be filed with the courts of the County of Contra Costa, State of California.

20. CLAIMS:

Any claim by Contractor against City hereunder shall be subject to Government Code §§ 800 et seq. The claims presentation provisions of said Act are hereby modified such that the presentation of all claims hereunder to the City shall be waived if not made within six months after accrual of the cause of action.

21. INTERPRETATION:

This Contract shall be interpreted as if drafted by both parties.

22. WARRANTY:

If any product is be provided to the City as part of this Contract, Contractor warrants as follows: Contractor possesses good title to the product and the right to transfer the product to City; the product shall be delivered to the City free from any security interest or other lien; the product meets any specifications contained herein; the product shall be free from material defects in materials and workmanship under normal use for a period of one (1) year from the date of delivery; and the product shall be fit for its intended purpose(s). Notwithstanding the foregoing, consumable and maintenance items (such as light bulbs and batteries) shall be warranted for a period of one hundred and eighty (180) days from the date of delivery. All repairs during the warranty period shall be promptly performed by Contractor, at Contractor's expense, including shipping.

23. SEVERABILITY:

In the event that any of the provisions or portions or applications thereof of this Contract are held to be unenforceable or invalid by any court of competent jurisdiction, City and Contractor shall negotiate an equitable adjustment in the provisions of the Contract with a view toward effecting the purpose of this Contract, and the validity and enforceability of the remaining provisions or portions or applications thereof, shall not be affected thereby.

24. AUTHORITY:

City warrants and represents that the signatory hereto (the Mayor of the City of Richmond or the City Manager) is duly authorized to enter into and execute this Contract on behalf of City. The party signing on behalf of Contractor warrants and represents that they are duly authorized to enter into and execute this Contract on behalf of Contractor, 8021 Contra Costa County Health Services Department, C
495
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
and shall be personally liable to City if they are not duly authorized to enter into and execute this Contract on behalf of Contractor.

25. WAIVER:

The waiver by City of any breach of any term or provision of this Contract shall not be construed as a waiver of any subsequent breach. Inspections or approvals, or statements by any officer, agent or employee of the City relating to the Contractor’s performance, or payment therefore, or any combination of these acts, shall not relieve the Contractor’s obligation to fulfill this Contract as prescribed; nor shall the City be thereby stopped from bringing any action for damages or enforcement arising from any failure to comply with any of the terms and conditions of this Contract.

26. COUNTERPARTS:

This Contract may be executed in any number of counterparts (including by fax, PDF, DocuSign, or other electronic means), each of which shall be deemed an original, but all of which shall constitute one and the same instrument.

27. SANCTUARY CITY CONTRACTING ORDINANCE (SCCO):

The Richmond Sanctuary City Contracting Ordinance No. 12-18 prohibits the City from granting and or retaining contracts with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor must submit the Sanctuary City Compliance Statement, attached hereto as Exhibit G. 8021 Contra Costa County Health Services Department, C
496
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT E

SPECIAL CONDITIONS
The General Conditions are hereby amended to include the following modifications and/or provisions (if applicable, otherwise please state “NONE”):
8021 Contra Costa County Health Services Department, C
Section 11a and 11b of Exhibit D "General Conditions" are hereby replaced by the following Mutual Indemnification clause:
a. The Contractor shall defend, save and hold harmless and indemnify the City and its officers, agents and employees from all liabilities and claims for damages for death, sickness or injury to persons or property, including without limitation, all consequential damages, from any cause whatsoever arising from or connected with the operations or the services of the Contractor hereunder, resulting from the conduct, negligent or otherwise, of the Contractor, its agents or employees. b. The City shall defend, save and hold harmless and indemnify the Contractor and its officers, agents and employees from all liabilities and claims for damages for death, sickness or injury to persons or property, including without limitation, all consequential damages, from any cause whatsoever arising from or connected with the operations or the services of the County, resulting from the conduct, negligent or otherwise, of the County or its employees.

Section 27. Contractor is exempt from the Sanctuary City Contracting Ordinance No. 12-18 ("SCCO") pursuant to SCCO Section 2 paragraph 5.
497
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT F

INSURANCE PROVISIONS
☐ CHECK HERE IF RISK MANAGEMENT HAS APPROVED WAIVING INSURANCE REQUIREMENTS FOR THIS CONTRACT.

1. CERTIFICATES: Before the commencement of the terms of this Contract, and during the entire term of this Contract and any extension or modification thereof, Contractor shall furnish the City’s Risk Manager with certificates showing the type, amount, class of operations covered, effective dates and dates of expiration of insurance coverage in compliance with coverage requirements set forth by the City and incorporated herein.

Such certificates, which do not limit Contractor’s indemnification, shall also contain substantially the following statement:
“Should any of the above insurance covered by this certificate be canceled or coverage reduced before the expiration date thereof, the insurer affording coverage shall provide thirty (30) days’ advance written notice to the City of Richmond.

Attention: Risk Manager.”
Contractor shall maintain in force at all times during the performance of this Contract all appropriate coverage of insurance required by this Contract with an insurance company licensed to offer insurance business in the State of California with a current A.M. Best’s rating of no less than A:VII or Standard & Poor’s Rating (if rated) of at least BBB unless otherwise acceptable to the City. Contractor shall deliver updated insurance certificates to the City at the address set forth in Exhibit C prior to the expiration of the existing insurance certificate for the duration of the term of Contract.

Endorsements naming the City, its City Council, boards, commissions, officials, employees, agents, and volunteers as additional insured shall be submitted with the insurance certificates.

2. COVERAGE REQUIREMENTS: The City’s insurance requirements depend upon the type of service being provided and/or the provider. The City’s insurance requirements will fall into one of the following categories (unless otherwise provided by the City):

Consultants and Contractors – Type 1
Professional Services – Type 2
Environmental Risk/Hazardous Waste Material – Type 3
Lease of City Property – Type 4
Vendors, Suppliers, Small Grant Recipients & Nonprofit Organizations – Type 5 Transportation Providers – Type 6
Professional Services Pyrotechnics – Type 7
Cyber and I.T. Risks – Type 8
8021 Contra Costa County Health Services Department, C
498
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
The insurance requirements classification applicable to this Contract shall be attached to this Exhibit F and made a part hereof.

3. FAILURE TO SECURE: If Contractor at any time during the term hereof should fail to secure or maintain the foregoing insurance, the City shall be permitted to obtain such insurance in Contractor’s name or as an agent of Contractor and shall be compensated by Contractor for the costs of the insurance premiums at the maximum rate permitted by law and computed from the date written notice is received that the premiums have not been paid.

4. SUFFICIENCY OF INSURANCE: The insurance limits required by the City are not represented as being sufficient to protect Contractor. Contractor is advised to consult Contractor’s insurance broker to determine adequate coverage for Contractor. The coverage and limits shall be (1) the minimum coverage and limits specified in this Contract; or (2) the broader coverage and maximum limits of the coverage carried by or available to Contractor; whichever is greater.

INSERT INSURANCE REQUIREMENTS CLASSIFICATION APPLICABLE TO THIS CONTRACT: (IF NECESSARY, CONFIRM WITH RISK MANAGER)
8021 Contra Costa County Health Services Department, C
499
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT G

SANCTUARY CITY COMPLIANCE STATEMENT
The undersigned, (hereafter "Contractor"), has had an opportunity to review the requirements of City of Richmond Ordinance 12-18 (hereafter "Sanctuary City Contracting Ordinance" or “SCCO”).

Contractor understands and agrees that the City may choose with whom it will maintain business relations and may refrain from contracting with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor understands the meaning of the following terms used in the SCCO:
a. "Data Broker” means either of the following:
i. The collection of information, including personal information about consumers, from a wide variety of sources for the purposes of reselling such information to their customers, which include both private-sector business and government agencies;
ii. The aggregation of data that was collected for another purpose from that for which it is ultimately used.
b. “Extreme Vetting” means data mining, threat modeling, predictive risk analysis, or other similar services."
Contractor understands that it is not eligible to receive or retain a City contract if at the time the Contract is executed, or at any time during the term of the Contract, it provides Data Broker or Extreme Vetting services to ICE.

Contractor further understands and agrees that Contractor's failure to comply with the SCCO shall constitute a material default of the Contract and the City Manager may terminate the Contract and bar Contractor from bidding on future contracts with the City for five (5) years from the effective date of the contract termination.

By executing this statement, Contractor certifies that it complies with the requirements of the SCCO and that if at any time during the term of the Contract it ceases to comply, Contractor will promptly notify the City Manager in writing. Any person or entity who knowingly or willingly supplies false information in violation of the SCCO shall be guilty of a misdemeanor and subject to a $1,000 fine.

Based on the foregoing, the undersigned declares under penalty of perjury under the laws of the State of California that the foregoing is true and correct.

Printed Name: Title:

Signed: Date:

Business Entity:
8021 Contra Costa County Health Services Department, C
500

Team Name:

Contract Term: 7/1/2026 - 6/30/2029
Funding source(s)
Contract Total
Year 1 Richmond Contract Total Year 2 Richmond Contract Total Year 3 Richmond Funding Amount $ 1,660,150
Option Code(s)
CFDA Number
Federal, State, or Local Funding
Position Titles FY24-25 Salary FTE Salaries FTE TOTAL TOTAL TOTAL TOTAL Care Coordinator 83,350 $ 1.00 83,350 $ 1.00 83,350 $ 83,350 $ $87,518 $87,518 $91,894 $91,894 Dispatch 63,664 $ 0.00 0.00
HMIS Data Analyst 74,138 $ 0.00 0.00
Outreach Specialist 63,664 $ 1.00 63,664 $ 1.00 63,664 $ 63,664 $ $66,847 $66,847 $70,190 $70,190 Outreach Specialist 63,664 $ 2.00 127,328 $ 2.00 127,328 $ 76,397 $ $133,694 $80,217 $140,379 $84,227 Program Coordinator $ 0.25 $23,151 0.25 23,150.68 92,599 $ 13,890 $ $24,308 $14,585 $25,524 $15,314 Program Director $ 0.00 0.00 129,176
Program Manager 101,887 $ 0.10 $10,189 0.10 $10,189 $6,113 $10,698 $6,419 $11,233 $6,740 Overtime 0.02 $2,547 0.02 $2,547 $1,528 $2,674 $1,604 $2,808 $1,685 Doubletime 0.01 $1,141 0.01 $1,141 $685 $1,198 $719 $1,258 $755

4.35 $311,369 4.35 $311,369 $245,627 $326,938 $257,909 $343,285 $270,805

12.3% 12.3%

38.7% $120,624 38.7% $120,624 $95,156 $126,656 $99,914 $132,988 $104,910 $431,994 $431,994 $340,783 $453,594 $357,823 $476,273 $375,714 $22,180 $22,180 $13,308 $22,180 $13,308 $22,180 $13,308 $4,040 $4,040 $2,424 $4,040 $2,424 $4,040 $2,424
$720 $720 $432 $720 $432 $720 $720
$4,870 $4,870 $2,922 $4,870 $2,922 $4,870 $2,922
$31,810 $31,810 $19,086 $31,810 $19,086 $31,810 $19,374 $463,804 $463,804 $359,869 $485,404 $376,909 $508,083 $395,088 9% $41,742 $41,742 $32,388 $52,199 $40,532 $54,247 $42,182 10% $46,373 $46,373 $35,981 $48,540 $37,691 $50,808 $39,509 $551,920 $551,920 $428,239 $586,143 $455,132 $613,138 $476,780 $100,000 $100,000 $100,000 $100,000 $100,000 $100,000
$551,920 $651,920 $528,239 $ 686,143 $555,132 $ 713,138 $ 576,780 Quarterly Invoice $137,980 $162,980
FY26-27 FY 27-28 FY 28-29
$ 138,783 132,059.75 $ 178,284.50 171,535.75 $ $ 144,195 $ Subtotal Direct Expenses
Heluna F&A
Admin Indirect Expense

TOTAL CORE PROGRAM DIRECT EXPENSES
Housing Security Fund (HSF)

TOTAL PROGRAM EXPENSES
Phone & IT Expenses
Client Expenses (Transit tickets, water, food, emergency supplies, etc.)
Other Costs (office supplies, employee uniforms, storage unit etc.)
Subtotal Operating Expenses
Vehicle expenses (rental, gas, etc.)
Personnel Expenses
Total FTE & Total Salaries
PT Fringe Benefits
FT Fringe Benefits
Subtotal Personnel Expenses
Operating Expenses
Richmond/San Pablo
Full Team Cost
Richmond/San Pablo
5% COLA 5% COLA 5% COLA

CORE Program Summary (HMIS4912)
Purpose: For distribition of data related to the Core Outreach program Reporting Period between 4/1/2025 and 3/31/2026
CORE Program(s): CORE Mobile Outreach, CORE Aftercare or Non-Homeless Contacted by Which Team(s): CORE + Team,CORE All County Central/East Team,CORE All County West Team,CORE Antioch Team,CORE Antioch Team ERF3,CORE BART Team,CORE CalWORKS! Team,CORE Concord Team,CORE Contra Costa Team ERF3,CORE El Cerrito/San Pablo Team (discontinued after 7/1/25),CORE HDAP Team (discontinued after 7/1/25),CORE HMIOT Team,CORE Martinez Team,CORE Martinez/Pleasant Hill Team (discontinued after 7/1/25),CORE Night Team 1,CORE Night Team 2,CORE Pittsburg Team,CORE Pleasant Hill Team,CORE Pleasant Hill/ReEntry Team,CORE Pleasant Hill/Walnut Creek Team,CORE Public Works Team,CORE Quad City Team,CORE Richmond San Pablo Team,CORE Richmond Team,CORE TAY Team,CORE Team - Education Team,CORE Team - Re-Entry Team,CORE Team J,CORE Walnut Creek Team,CORE Walnut C Demographics
Total Contacts Made: 3,855; Unduplicated clients contacted: 1,153 Total Individuals: 927; Total Families: 86
Household Configuration Total %
People in Families 233 20.21%
Single 927 80.40%
Total 1,153 100%
Race Ethnicity Total %
American Indian, Alaska Native, or Indigenous 8 0.69%
American Indian, Alaska Native, or Indigenous||Asian
or Asian American||Black, African American, or
African||White||Hispanic/Latina/o
1 0.09%
American Indian, Alaska Native, or Indigenous||Black,
African American, or African
14 1.21%
American Indian, Alaska Native, or Indigenous||Black,
African American, or African||Hispanic/Latina/o
1 0.09%
American Indian, Alaska Native, or Indigenous||Black,
African American, or African||Native Hawaiian or
Pacific Islander
1 0.09%
American Indian, Alaska Native, or Indigenous||Black,
African American, or African||White
1 0.09%
American Indian, Alaska Native, or Indigenous||
Hispanic/Latina/o
39 3.38%
American Indian, Alaska Native, or Indigenous||
Hispanic/Latina/o
12 1.04%
American Indian, Alaska Native, or Indigenous||Native
Hawaiian or Pacific Islander||White
1 0.09%
American Indian, Alaska Native, or Indigenous||White 4 0.35% American Indian, Alaska Native, or Indigenous||
White||Hispanic/Latina/o
2 0.17%
American Indian, Alaska Native, or Indigenous||
White||Hispanic/Latina/o
1 0.09%
Asian or Asian American 32 2.78%
Asian or Asian American||Black, African American, or
African
4 0.35%
Asian or Asian American||Hispanic/Latina/o 2 0.17%
Asian or Asian American||Middle Eastern or North
African
1 0.09%
Asian or Asian American||Native Hawaiian or Pacific
Islander
1 0.09%
Asian or Asian American||White||Hispanic/Latina/o 1 0.09% Black, African American, or African 501 43.45%
Black, African American, or African||Hispanic/Latina/o 10 0.87% Black, African American, or African||Hispanic/Latina/o 7 0.61% Black, African American, or African||Native Hawaiian or Pacific Islander
1 0.09%
Black, African American, or African||White 14 1.21%
Black, African American, or African||White||
Hispanic/Latina/o
4 0.35%
Run date 04/30/2026 03:36 PM. 502 Page 1 of 5
CORE Program Summary (HMIS4912)
Purpose: For distribition of data related to the Core Outreach program Reporting Period between 4/1/2025 and 3/31/2026
CORE Program(s): CORE Mobile Outreach, CORE Aftercare or Non-Homeless Contacted by Which Team(s): CORE + Team,CORE All County Central/East Team,CORE All County West Team,CORE Antioch Team,CORE Antioch Team ERF3,CORE BART Team,CORE CalWORKS! Team,CORE Concord Team,CORE Contra Costa Team ERF3,CORE El Cerrito/San Pablo Team (discontinued after 7/1/25),CORE HDAP Team (discontinued after 7/1/25),CORE HMIOT Team,CORE Martinez Team,CORE Martinez/Pleasant Hill Team (discontinued after 7/1/25),CORE Night Team 1,CORE Night Team 2,CORE Pittsburg Team,CORE Pleasant Hill Team,CORE Pleasant Hill/ReEntry Team,CORE Pleasant Hill/Walnut Creek Team,CORE Public Works Team,CORE Quad City Team,CORE Richmond San Pablo Team,CORE Richmond Team,CORE TAY Team,CORE Team - Education Team,CORE Team - Re-Entry Team,CORE Team J,CORE Walnut Creek Team,CORE Walnut C Gender Total %
Man (Boy, if child) 689 59.76%
Man (Boy, if child)/ Transgender 1 0.09%
Transgender 3 0.26%
Woman (Girl, if child) 458 39.72%
Woman (Girl, if child)/ Transgender 2 0.17%
Total 1,153 100%
Total Months Homeless In Lifetime Total %
0-6 360 31.22%
07-12 117 10.15%
13-24 162 14.05%
25-36 130 11.27%
37-48 70 6.07%
49-60 67 5.81%
Over 5 Years 314 27.23%
Total 1,153 100%
Contact City Total %
Richmond 1,153 100.00%
NOTE: Each row represents a unique client count, however a client may have had contact(s) in multiple cities. Thus, adding up these rows may NOT equal the unique no. of clients contacted during the report period. Percent column reflects the no. of clients out of the total unique clients contacted, so this may also not total to 100%.

Race Ethnicity Total %
Client doesn?t know 1 0.09%
Client prefers not to answer 7 0.61%
Hispanic/Latina/o 203 17.61%
Middle Eastern or North African 2 0.17%
Native Hawaiian or Pacific Islander 14 1.21%
Native Hawaiian or Pacific Islander||Hispanic/Latina/o 1 0.09% Native Hawaiian or Pacific Islander||White 1 0.09%
Native Hawaiian or Pacific Islander||White||
Hispanic/Latina/o
1 0.09%
White 216 18.73%
White||Hispanic/Latina/o 26 2.25%
White||Hispanic/Latina/o 17 1.47%
White||Hispanic/Latina/o||Middle Eastern or North
African
1 0.09%
Total 1,153 100%
Run date 04/30/2026 03:36 PM. 503 Page 2 of 5
CORE Program Summary (HMIS4912)
Purpose: For distribition of data related to the Core Outreach program Reporting Period between 4/1/2025 and 3/31/2026
CORE Program(s): CORE Mobile Outreach, CORE Aftercare or Non-Homeless Contacted by Which Team(s): CORE + Team,CORE All County Central/East Team,CORE All County West Team,CORE Antioch Team,CORE Antioch Team ERF3,CORE BART Team,CORE CalWORKS! Team,CORE Concord Team,CORE Contra Costa Team ERF3,CORE El Cerrito/San Pablo Team (discontinued after 7/1/25),CORE HDAP Team (discontinued after 7/1/25),CORE HMIOT Team,CORE Martinez Team,CORE Martinez/Pleasant Hill Team (discontinued after 7/1/25),CORE Night Team 1,CORE Night Team 2,CORE Pittsburg Team,CORE Pleasant Hill Team,CORE Pleasant Hill/ReEntry Team,CORE Pleasant Hill/Walnut Creek Team,CORE Public Works Team,CORE Quad City Team,CORE Richmond San Pablo Team,CORE Richmond Team,CORE TAY Team,CORE Team - Education Team,CORE Team - Re-Entry Team,CORE Team J,CORE Walnut Creek Team,CORE Walnut C City Where You Lost Housing Total %
Antioch 78 6.76%
Bay Point 7 0.61%
Brentwood 7 0.61%
Clayton 1 0.09%
Concord 50 4.34%
Crockett 1 0.09%
Danville 1 0.09%
Discovery Bay 1 0.09%
Don't know/Refused/Not Collected/Null 4 0.35%
El Cerrito 8 0.69%
El Sobrante 15 1.30%
Hercules 4 0.35%
Martinez 15 1.30%
North Richmond 6 0.52%
Oakley 9 0.78%
Other part of Contra Costa 2 0.17%
Outside of Contra Costa 228 19.77%
Pinole 11 0.95%
Pittsburg 41 3.56%
Pleasant Hill 2 0.17%
Port Costa 1 0.09%
Richmond 605 52.47%
Rodeo 12 1.04%
San Pablo 58 5.03%
Walnut Creek 10 0.87%
Total 1,153 100%
Health Indicators Total
Substance Use Disorder 0
Chronic Health Condition (HUD) 278
Developmental (HUD) 151
HIV/AIDS (HUD) 25
Mental Health Problem (HUD) 510
Physical (HUD) 298
NOTE: This total will not match intake total if 1 or more clients have more than 1 disability.

Age At Intake Total %
Minors (0-17) 118 10.23%
Transition Aged Youth (18-24) 81 7.03%
Adults (25-61) 857 74.33%
Seniors (62+) 103 8.93%
Total 1,153 100%
Run date 04/30/2026 03:36 PM. 504 Page 3 of 5
CORE Program Summary (HMIS4912)
Purpose: For distribition of data related to the Core Outreach program Reporting Period between 4/1/2025 and 3/31/2026
CORE Program(s): CORE Mobile Outreach, CORE Aftercare or Non-Homeless Contacted by Which Team(s): CORE + Team,CORE All County Central/East Team,CORE All County West Team,CORE Antioch Team,CORE Antioch Team ERF3,CORE BART Team,CORE CalWORKS! Team,CORE Concord Team,CORE Contra Costa Team ERF3,CORE El Cerrito/San Pablo Team (discontinued after 7/1/25),CORE HDAP Team (discontinued after 7/1/25),CORE HMIOT Team,CORE Martinez Team,CORE Martinez/Pleasant Hill Team (discontinued after 7/1/25),CORE Night Team 1,CORE Night Team 2,CORE Pittsburg Team,CORE Pleasant Hill Team,CORE Pleasant Hill/ReEntry Team,CORE Pleasant Hill/Walnut Creek Team,CORE Public Works Team,CORE Quad City Team,CORE Richmond San Pablo Team,CORE Richmond Team,CORE TAY Team,CORE Team - Education Team,CORE Team - Re-Entry Team,CORE Team J,CORE Walnut Creek Team,CORE Walnut C Do You Have a Disabling Condition? Total %
No 461 39.98%
Yes 711 61.67%
Total 1,153 100%
Ever been involved in Criminal Justice System?
(Adults Only)
Total %
Don't know/Refused/Not Collected/Null 12 1.16%
No 795 76.74%
Yes 244 23.55%
Total 1,036 100%
Currently fleeing domestic violence?
(Adults Only, Women)
Total %
Don't know/Refused/Not Collected/Null 226 58.25%
No 101 26.03%
Yes 66 17.01%
Total 388 100%
Veteran Status (Adults Only) Total %
No 1,018 98.26%
Yes 18 1.74%
Total 1,036 100%
First Time Homeless? (Adults Only) Total %
Don't know/Refused/Not Collected/Null 1 0.10%
No 527 50.87%
Yes 532 51.35%
Total 1,036 100%
Currently fleeing domestic violence?
(Adults Only, Man)
Total %
Don't know/Refused/Not Collected/Null 625 96.90%
No 16 2.48%
Yes 7 1.09%
Total 645 100%
Currently fleeing domestic violence?
(Adults Only, All Gender)
Total %
Don't know/Refused/Not Collected/Null 854 82.43%
No 117 11.29%
Yes 73 7.05%
Total 1,036 100%
Run date 04/30/2026 03:36 PM. 505 Page 4 of 5
CORE Program Summary (HMIS4912)
Purpose: For distribition of data related to the Core Outreach program Reporting Period between 4/1/2025 and 3/31/2026
CORE Program(s): CORE Mobile Outreach, CORE Aftercare or Non-Homeless Contacted by Which Team(s): CORE + Team,CORE All County Central/East Team,CORE All County West Team,CORE Antioch Team,CORE Antioch Team ERF3,CORE BART Team,CORE CalWORKS! Team,CORE Concord Team,CORE Contra Costa Team ERF3,CORE El Cerrito/San Pablo Team (discontinued after 7/1/25),CORE HDAP Team (discontinued after 7/1/25),CORE HMIOT Team,CORE Martinez Team,CORE Martinez/Pleasant Hill Team (discontinued after 7/1/25),CORE Night Team 1,CORE Night Team 2,CORE Pittsburg Team,CORE Pleasant Hill Team,CORE Pleasant Hill/ReEntry Team,CORE Pleasant Hill/Walnut Creek Team,CORE Public Works Team,CORE Quad City Team,CORE Richmond San Pablo Team,CORE Richmond Team,CORE TAY Team,CORE Team - Education Team,CORE Team - Re-Entry Team,CORE Team J,CORE Walnut Creek Team,CORE Walnut C Service Summary
Service Category Total % Unduplicated Clients %
[CalAIM] Housing Deposits 3 0.02% 2 0.19%
[Outreach] Housing Financial Services 11 0.08% 7 0.68%
CalAIM Housing Navigation Service 1,134 7.81% 105 10.19% CalAIM Housing Tenancy Service 2 0.01% 1 0.10%
CARE Center Coordination 1 0.01% 1 0.10%
Healthcare Coordination 467 3.22% 207 20.10%
Other Services (Soft Referrals, DMV, Bus Tickets, etc.) 11,978 82.48% 1,029 99.90% Public Works Garbage bags distributed 15 0.10% 10 0.97% Shelter Bed Coordination 90 0.62% 86 8.35%
Warming Center Coordination 822 5.66% 81 7.86%
Total 14,523 100% 1,030 100%
NOTE: This table reflects all services provided by any CORE Team to the 1,153 clients contacted. Total contacted may not equal total receiving service.

Exit destinations for those who exited during the reported period Destination Total %
Deceased 2 0.23%
Don't know/Refused/Data not collected, Other) 23 2.69%
Emergency shelter 127 14.84%
Medical care (short-term or long-term, substance treatment, residential care, etc.) 183 21.38% Permanent Housing 69 8.06%
Place not meant for habitation 469 54.79%
Short-term housing (transitional, with family or friends, foster care) 12 1.40% Total 856 100%
Run date 04/30/2026 03:36 PM. 506 Page 5 of 5

July 7, 2026
Police Department
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: Tim Simmons, Chief of Police
Subject: Monthly Crime Report for May 2026
FINANCIAL IMPACT: There is no fiscal impact for receiving this item.

PREVIOUS COUNCIL
ACTION:

None.

STATEMENT OF THE
ISSUE:

City staff are requesting that the City Council receive the Police Department's monthly Crime Report for May 2026.

RECOMMENDED ACTION: RECEIVE the monthly Crime Report from the Richmond Police Department for May 2026 – Police Department
(Chief Timothy Simmons 510-621-1802).

DISCUSSION:

Chief Tim Simmons will present statistical data regarding violent crimes, property crimes, calls for service, parking enforcement efforts and some significant incidents from May 2026.

AGENDA
REPORT
507

July 7, 2026
DOCUMENTS ATTACHED:

Attachment 1 – Monthly Crime Report, July 2026
508
Richmond Police Department Crime Report
Council Report May 2026
Mayor Martinez, Council, and Community,
The Richmond Police Department's crime statistics for May 2026 show an increase in total violent crime and slight decrease in total property crime compared to April 2026.

Violent Crime
In the month of May, there was a decrease by 50% in the number of homicides, from 2 to 1. Aggravated assaults increased by 48%, from 52 to 77 incidents. The number of Robberies remained unchanged, with 16 incidents. Sexual assaults decreased by 8%, from 12 to 11 incidents. Overall, the total number of violent crimes increased by 28%, from 82 to 105 incidents.

Property Crime
There was a decrease in burglaries (excluding auto burglaries), by 21% from 24 to 19 incidents. Thefts, including auto burglaries, slightly increased by 3%, from 125 to 129 incidents. Vehicle thefts decreased by 8%, from 98 to 90 incidents. Arson increased by 20%, from 5 to 6 incidents. Overall, the total number of property crimes decreased by 3%, from 252 to 244 incidents.

Reports / Calls for Service
There was an 4% increase in vehicle impounds, from 242 to 252. Collision-related calls for service increased by 13%, from 144 to 162 incidents. DUI-related traffic collisions increased 20%, from 5 to 6 incidents. DUI reports decreased by 14%, from 28 to 24 incidents. Sideshow-related calls for service increased by 100%, from 1 to 2 incidents.

The total number of firearms recovered decreased by 50%, from 22 to 11.

ShotSpotter Report
A review of shots-fired activity indicates that May 2026 experienced increases compared with the previous month but remained below levels observed during the same month last year. Calls for service related to shots fired rose from 12 in April to 16 in May, an increase of 33%, while ShotSpotter activations increased from 18 to 25, representing a 39% increase. Despite these month-over-month increases, May 2026 recorded fewer incidents than May 2025, with calls for service declining by 36% (25 to 16) and ShotSpotter activations decreasing by 22% (32 to 25). Year-to-date data through May 31, 2026, further reflects this trend, with 71 shots-fired calls for service compared to 110 during the same period in 2025, a 35% reduction. Conversely, ShotSpotter activations increased from 156 to 172 year-to-date, a 10% rise. 509
Analysis of ShotSpotter activation locations identified several recurring areas of activity, with concentrations observed near the 7th Street and Pennsylvania Avenue corridor, within the Iron Triangle neighborhood, and in the vicinity of Cutting Boulevard and 23rd Street.

Parking Enforcement
The Parking Enforcement Unit towed 126 vehicles for being abandoned, overparked, or having expired registration, up from 125 in April, an increase of less than 1%. They issued 2,070 parking citations, compared to 5,239 in March, a decrease of 60%. The sudden decrease was due to employee vacations and/or other forms of leave. The Parking Unit responded to 321 citizen complaints regarding abandoned vehicles, compared to 365 in April. In May, 189 of these vehicles were cited or tagged with 72- hour notices, and 101 vehicles were eventually towed.

Traffic Enforcement
Officers issued approximately 117 misdemeanor and infraction traffic-related citations.

The number of citations reported for this month-long period may be lower than the actual number issued. This is due to processing and data-entry timelines, as citations are not always immediately entered into the system. Accordingly, the figures provided should be considered an estimate.

Illegal Dumping Citations
None.

Tobacco Enforcement Citations
None.

Staffing
The month of May brought a reallocation of personnel and promotions as patrol staffing continues to improve. RPD promoted two sergeants to the rank of lieutenant and three officers to the rank of sergeant. RPD assigned another detective to the Contra Costa County Major Crimes Task Force, replacing a detective whom was promoted to sergeant. The department continues to work toward bolstering patrol numbers and restoring the Community Violence Reduction Team, Bravo Unit, Traffic Unit, and other specialty assignments.

Authorized sworn positions: 147
Current sworn staff: 129 (including nine trainees in the academy) Authorized full-time professional staff: 71
Current professional staff: 59
Council District Statistics
• District 1 experienced a 25% increase in total calls for service, from 1,283 to 1,605. 510
• District 2 experienced a 14% increase in total calls for service, from 1,208 to 1,378. • District 3 experienced a 7% increase in total calls for service, from 1,578 to 1,695. • District 4 experienced a 25% increase in total calls for service, from 627 to 785. • District 5 experienced a 5% increase in total calls for service, from 1,367 to 1,436. • District 6 experienced a 9% increase in total calls for service, from 1,016 to 1,111.

These statistics offer a snapshot of crime trends in Richmond for May 2026, highlighting areas of concern and notable improvements. Additional statistical data and historical data can be found on our website under the Crime Analysis page. https://www.ci.richmond.ca.us/1023/Crime-Analysis
Police District Summary
Central District Crime and Community Issues
Several ongoing community concerns continue to receive attention throughout the district.

Increased complaints regarding neighborhood disputes, loud music, and parking issues have been reported near 5th Street and Bissell Avenue. The ROCK team is working with residents to address these concerns.

In the 400 block of Macdonald Avenue, officers continue addressing loitering complaints while a trespass authorization letter is being finalized. Additional patrols will remain in place until the process is completed.

Encampments and unhoused-related concerns persist at the Richmond BART station, 22nd Street and Carlson Boulevard, and near Richmond Parkway and Hensley Street.

Outreach partners, including CORE, SOS, City Services, and other involved agencies, have been notified and continue to coordinate response efforts.

Parking Enforcement personnel remain active along the 23rd Street corridor, focusing on time-limit enforcement and parking violations that impact pedestrian and vehicle safety, particularly during weekend vendor activities.

The 23rd Street Merchant Association has requested additional patrols during school commute hours and continue to support efforts aimed at improving corridor safety.

Northern District Crime and Community Issues
Northern District personnel continued addressing quality-of-life and public safety concerns throughout the district. Officers coordinated with Planet Fitness management regarding RVs and unhoused individuals occupying the business's parking lot. In partnership with Crime Prevention personnel, management obtained and posted the necessary signage to support future enforcement and trespassing efforts. Officers also responded to ongoing concerns involving unhoused individuals in the 3500–3700 blocks of Macdonald Avenue and within the parking lot of Target. 511
To address community concerns, officers worked special-assignment overtime focused on prostitution-related activity and other quality-of-life issues in the areas surrounding 23rd Street and 24th Street.

The Westridge Apartments remain a priority focus area for officers assigned to Beat 8.

Property management has made substantial progress in improving conditions at the complex, including the removal of most unauthorized occupants and trespassers.

Management recently installed a network of security cameras provided by Flock Safety and is working to provide the Richmond Police Department with access to the system.

Officers have continued proactive patrols and enforcement efforts aimed at deterring criminal activity and preventing the return of trespassers and squatters.

Officers also conducted traffic enforcement operations through overtime deployments in response to neighborhood concerns regarding speeding and other traffic-related issues.

Additionally, Lieutenant Dean, Lieutenant Patchin, and Sergeant Ramos participated in an evacuation drill conducted within the beat area to support emergency preparedness and response readiness.

Southern District Crime and Community Issues
Southern District personnel continued to address quality-of-life concerns throughout the district, with a focus on homeless encampments and oversized vehicle enforcement along Hall Avenue, Wright Avenue, and Meeker Avenue. Officers conducted directed patrols, engaged individuals experiencing homelessness, coordinated with partner agencies, and addressed issues related to unauthorized camping, abandoned vehicles, and recreational vehicles creating public safety and accessibility concerns. These efforts were aimed at improving neighborhood conditions, maintaining access to public roadways, and connecting individuals with available resources when appropriate.

During the Memorial Day weekend, the Richmond Police Department partnered with Code Enforcement and 4LEAF to provide enhanced enforcement and education efforts in the Point Richmond area related to illegal vending activity. Personnel conducted highvisibility patrols and worked collaboratively to engage vendors, educate them regarding applicable regulations, and encourage voluntary compliance. The coordinated effort also focused on mitigating traffic congestion, preventing blocked roadways and access points, and ensuring the safe movement of residents, visitors, and emergency vehicles during the holiday weekend.

Additional Significant Incidents from May 2026:

May 3, 2026 City of Richmond Cinco de Mayo Festival Community Event The annual city of Richmond Cinco de Mayo Festival was held along the 23rd Street corridor. The event was well attended and no significant incidents occurred during the festival.

May 7, 2026 2nd Street and Silver Avenue Drug Sales Arrest Officers were patrolling in the listed area, after numerous reports of drug sales activity in the area. Officers contacted the suspect during a traffic enforcement stop. After being asked for his identification, the suspect removed his identification from his pants pocket.

At the same time, officers observed a plastic baggie with suspected cocaine protruding 512
from the suspect’s pants pocket. Officers ultimately arrested the suspect. Incident to arrest, officers located 16.6 grams of methamphetamine, 6.1 grams of cocaine salt, 15 grams of cocaine base, a digital scale, and additional packaging and paraphernalia. The suspect was later booked into the Richmond Police Department jail.

May 14, 2026 3500 block of El Portal Drive Attempted Murder/Suicide Officers responded to a request of an emergency cover (Code 3) request for AMR personnel. AMR personnel located a victim of domestic violence who had an electrical cord wrapped around their neck and trauma to their head, from being struck with a hammer. The victim was rushed to a local hospital for treatment. While on scene, officers developed information of the suspect’s whereabouts and conducted a protective sweep of the suspect’s residence. Officers found the suspect had committed suicide inside their residence and the suspect was pronounced deceased. The victim received medical treatment and was listed in stable condition.

May 15, 2026 1300 block of Canal Boulevard Fatal Vehicle Collision Officers responded to a report of a body floating on the shoreline at the listed location.

Officers located the deceased subject in the water and found this subject had their vehicle keys and identification in both of their hands. Homicide Investigators conducted follow-up by utilizing FLOCK (Automated License Plate Reader) and discovered the subject was driving in the area about 12 hours before locating the subject. Investigators located video surveillance showing the subject drove their vehicle off the roadway and into the bay. After getting this video surveillance, Richmond Police Marine Unit coordinated a multi-agency response to search for the subject’s vehicle and any other potential victims. With the assistance of the San Francisco Police Department, the Oakland Police Department, and the Alameda County Sheriff’s Office, divers located the subject’s vehicle submerged near where the subject was located. The subject’s vehicle was removed from the waterway and no other victims were located.

May 20, 2026 Special Event
Officers participated in the 2026 Special Olympics Torch Run. Richmond Police staff received the torch from the San Pablo Police Department and ran through the streets of Richmond, ultimately handing the torch off to the El Cerrito Police Department.

Richmond Police staff raised approximately $1200 in donations for this special event.

This event promotes community engagement and supports athletes participating in the Special Olympics.

May 22, 2026 3100 block of Pullman Avenue Gun Arrest
Officers responded to a report of a large group loitering the in the area. Officers responded and made contact with two suspects. Officers located a loaded firearm in the possession of one of the suspects. After being arrested, the other suspect admitted the firearm was actually theirs and was also subsequently arrested. The suspects were transported and booked into the Richmond Police Department jail.

May 25, 2026 8th Street/Maple Avenue Gun/Drug Arrest
Officers conducted a traffic enforcement stop at the listed area. Officers made contact with the suspect who admitted to possessing a loaded firearm on his person. Officers detained the suspect and removed the loaded firearm from the suspect’s waistband.

The suspect was also in possession of methamphetamine. The suspect was arrested and booked into the Richmond Police Department jail.
513
May 29, 2026 200 block of West Nevin Avenue Homicide
Officers responded to a report of a shooting at the listed location. Officers arrived on scene and located the victim suffering from a gunshot wound. Life-saving measures were immediately initiated; however, the victim succumbed to his injuries and was pronounced deceased on scene. Homicide Investigators responded to the scene and began working leads, to include utilizing FLOCK (Automated License Plate Reader).

Investigators were able to locate a suspect vehicle and get that information out to surrounding agencies. A few hours later, Concord Police notified the Richmond Police Department they had located the suspect and his vehicle. The suspect was placed under arrest and subsequently booked into the Martinez Detention Facility.

May 30, 2026 Evacuation Drill Special Event
Officers participated in a multi-agency evacuation drill with the Richmond Fire Department and the Office of Emergency Services. The purpose of this drill was to test emergency warning systems, evaluate evacuation routes, and increase community awareness of wildfire risks.

Tim Simmons
Chief of Police
Richmond Police Department
514

July 7, 2026
Police Department
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: Timothy Simmons, Chief of Police
Subject: Contract with Richmond Rod and Gun Club for Shooting Range Facility Rental
FINANCIAL IMPACT: The proposed expenditure of $25,000, for a total amount not to exceed $75,000 for the three-year term, is included in the Police Department’s proposed Fiscal Year 2026–
2027 operating budget and will be budgeted accordingly
in subsequent fiscal years (Account String:
01191021-400301).

PREVIOUS COUNCIL
ACTION:

None.

STATEMENT OF THE
ISSUE:

Richmond Rod and Gun Club offers shooting range
facilities that the Richmond Police Department rents on an as-needed basis to allow for regular training, special teams training, and new hire onboarding required training and qualification testing.

RECOMMENDED ACTION: APPROVE a three-year sole-source contract with Richmond Rod and Gun Club for shooting range facility
rentals in an amount not to exceed $25,000 annually, for a total not to exceed $75,000, for the term July 1, 2026, through June 30, 2029, with two one-year extension
options at $25,000 per year – Police Department (Chief
Timothy Simmons 510-621-1802).

AGENDA
REPORT
515

July 7, 2026
DISCUSSION:

The Richmond Police Department (RPD) requests approval for a sole source contract with the Richmond Rod and Gun Club (RRGC), the only facility that meets the City’s sole source procurement criteria. Following the loss of the department’s former range and the closure of The Halo Group facility, RRGC is the only viable firearms training range within a reasonable distance. It also provides the full range of required training amenities, including pistol, rifle, and action shooting areas, offers operating hours that accommodate swing and graveyard officers without overtime, and provides a government rate lower than regional competitors outside the City. In accordance with the City of Richmond’s Sole Source Procurement Policy, RRGC is the only practical, cost-effective, and operationally suitable provider for mandatory firearms training, making a three-year contract with optional extensions the most efficient and responsible solution for maintaining training continuity and meeting Peace Officer Standards and Training (POST) requirements.

RPD staff is seeking approval for a new three-year contract, with two one-year extensions for an amount up to $25,000 for each extension year, to continue renting range shooting lanes for new hire on-boarding, regular/mandated training, special teams training, and qualification shooting.

RRGC not only provides the closest proximity for our officers but has also consistently offered the most competitive rates for range rentals to governmental agencies. Even without nearby competition, the facility offered the department a “government” rate that was lower than other competing ranges outside of the city.

Moreover, RRGC boasts a range of amenities essential for RDP training needs, including a 25-yard pistol range, 100-yard and 200-yard rifle ranges, and an action shooting training area. The latter is crucial as it is mandatory for almost all RPD range training activities.

One significant advantage of RRGC is its extended operating hours, a feature unmatched by other facilities. This allows officers on swing and graveyard shifts to undergo essential training without incurring overtime costs, thereby optimizing both resources and personnel.

Based on these considerations, RPD staff proposes a three-year contract not to exceed $75,000 for the period of June 30, 2026, through June 30, 2029, with two one-year extensions at $25,000 annually, for a total not to exceed $125,000 through June 30, 2031.

Richmond Police Department staff believe that entering into this contract agreement with RRGC will not only address the immediate need to satisfy continued training but also establish a reliable and cost-effective solution for the foreseeable future. 516

July 7, 2026
DOCUMENTS ATTACHED:

Attachment 1 – Original Contract
Attachment 2 – Executed Sole Source Justification
517

CITY OF RICHMOND

STANDARD CONTRACT
Department: City Project Manager:

City Project Manager E-mail: City Project Manager Phone No:

Vendor No: Contract No:

Description of Services:

The parties to this STANDARD CONTRACT do mutually agree and promise as follows:

1. Parties. The parties to this Contract are the City of Richmond, a municipal corporation (“the City”), and the following named Contractor:

Contractor Name:

Street Address:

City, State, Zip Code:

Contact Person:

Telephone: Email:

Business License No:
☐ A California corporation, ☐ limited liability corporation ☐ general partnership, ☐ limited partnership, ☐ individual, ☐ non-profit corporation, ☐ individual dba as [specify:] ____________________ ☐ other [specify:] _______________________________

2. Term. The effective date of this Contract is _______________________ and terminates _________________ unless terminated earlier as set forth herein.

3. Payment Limit. City’s total payments to Contractor under this Contract shall not exceed $______________ (“Contract Payment Limit”) unless a Contract Amendment has been approved by the City Council or City Manager. If this amount includes a contingency, Contractor acknowledges that any use of such contingency shall be for work beyond the original scope of services and requires prior written authorization by the City. If noted below, Compensation for work done under this Contract, shall not exceed as follows:

FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________ FY _________ total compensation shall not exceed $_________________

4. Contractor’s Obligations. Contractor agrees to perform all work at its own cost and expense, to furnish all labor, tools, equipment, materials, except as otherwise specified, in accordance with the Service Plan set forth in Exhibit A, attached hereto and incorporated herein.

5. City Obligations. City shall make payments to the Contractor in accordance with the Payment Provisions set forth in Exhibit B, attached hereto and incorporated herein.

Police Sgt. F Rivera [email protected] (510) 620-6668 5897 7866 Shooting facility rental required police training.

Richmond Rod and Gun Club 3155 Goodrick Avenue Richmond, CA 94801 Edward Tung (510) 621-3120 [email protected] 4000-0506 July 1, 2026 June 30, 2029 75,000.00 518

6. Authorized Representatives and Notices. This Contract is subject to the Authorized Representatives and Notices Provisions (Exhibit C), attached hereto and incorporated herein.

7. General Conditions. This Contract is subject to the General Conditions (Exhibit D), which are attached hereto and incorporated herein.

8. Special Conditions. This Contract is subject to the Special Conditions (Exhibit E) (if any), which are attached hereto and incorporated herein.

9. Insurance Provisions. This Contract is subject to the Insurance Provisions (Exhibit F), which are attached hereto and incorporated herein.

10. Sanctuary City Compliance Statement. This Contract is subject to the Sanctuary City Compliance Statement (Exhibit G), which is attached hereto and incorporated herein.

11. Signatures. These signatures attest the parties' agreement hereto:

CITY OF RICHMOND,
a municipal corporation [BUSINESS NAME]
(* The Corporation Chairperson of the Board, President, or Vice President should sign below)
By: _________________________ By: ___________________________ Title: ________________________ Title: __________________________ Date Signed: _________________ Date Signed: ___________________ I hereby certify that this Contract (* The Corporation Chief Financial Officer or Assistant has been approved by City Council Treasurer, or Secretary or Assistant Secretary should or the City Manager. sign below)
By: _________________________ By: ___________________________ City Clerk Title: __________________________
Date Signed: ____________________
Approved as to form:
(NOTE: Pursuant to California Corporations Code Section By: _________________________ 313, if Contractor is a corporation or nonprofit organization, City Attorney this Contract (1) must be signed by (a) the Chairperson of the Board, President, or Vice-President and (b) the
Chief Financial Officer or Assistant Treasurer, or
Secretary or Assistant Secretary)
LIST OF ATTACHMENTS:

Service Plan Exhibit A
Payment Provisions Exhibit B
Authorized Representatives and Notices Exhibit C
General Conditions Exhibit D
Special Conditions Exhibit E
Insurance Provisions Exhibit F
Sanctuary City Compliance Statement Exhibit G
Richmond Rod and Gun Club
519
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT A

SERVICE PLAN
Contractor shall, to the satisfaction of the Project Manager (set forth in Exhibit B), perform the following services and be compensated as outlined below [or attach service plan if necessary]:
7866 Richmond Rod and Gun Club
Provide training facility rental for RPD staff use on arranged dates and times at the government rate.
520
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT B

PAYMENT PROVISIONS

1. COMPENSATION TO CONTRACTOR:
a. Provided Contractor is not in default under this Contract, Contractor shall be compensated in the manner set forth herein.
b. All payments made pursuant to this Contract shall be subject to the Contract Payment Limit. The Payment Limit includes expenses (phones, photocopying, meals and travel, etc.). Invoices shall be adequately detailed, based on accurate records, and be in a form reasonably satisfactory to the City. Contractor may be required to provide back-up material upon request. c. All City vendors receiving new contracts shall sign up to receive electronic payments through the City’s Automated Clearinghouse (ACH) payments service/provider.

2. SUBMISSION OF INVOICES:

Contractor shall submit timely invoices by email to
[email protected] and/or to the following address:

Attention: City of Richmond Finance/Account Payable
Project Manager: _______________________
P.O. Box 4046
Richmond, CA 94804

3. All invoices that are submitted by Contractor shall be subject to the approval of the City Project Manager, _______________________, before payments shall be authorized.
a. The City will pay invoice(s) within 45 days after completion of services to the City’s satisfaction. The City shall not pay late fees or interest.
b. All appropriate permits, certificates, and licenses, including a City business license shall be obtained and maintained for the duration of this Contract before any payment is authorized.

4. All insurance coverage required by this Contract shall be provided by the Contractor before this Contract is executed by the City. The insurance coverage required by this Contract shall be maintained by Contractor for the duration of this Contract and must be in place before any payment is authorized.

Sgt. F Rivera Sgt. F Rivera 7866 Richmond Rod and Gun Club 521
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT C

AUTHORIZED REPRESENTATIVES AND NOTICES

1. All required written notices shall be delivered: (i) by hand; or (ii) sent by registered, express, or certified mail, with return receipt requested or with delivery confirmation requested from the U.S. postal service; or (iii) sent by overnight or same day courier service at the party’s respective address listed in this Section.

2. Each notice shall be deemed to have been received on the earlier to occur of:
actual delivery or the date on which delivery is refused; or three (3) days after notice is deposited in the U.S. mail or with a courier service in the manner described above (Sundays and City holidays excepted).

3. Either party may, at any time, change its notice address (other than to a post office box address) by giving the other party three (3) days prior written notice of the new address.

4. All notices, demands, requests, or approvals from Contractor to the City shall be addressed to the City at:

City of Richmond
450 Civic Center Plaza
Richmond, CA 94804
Email: ________________________________________________

5. All notices, demands, requests, or approvals from the City to Contractor shall be addressed to Contractor at:

Attn:

Email: ________________________________________________ Sgt. F Rivera [email protected] 7866 Richmond Rod and Gun Club Richmond Rod and Gun Club 3155 Goodrick Avenue Richmond, CA 94801 [email protected] Edward Tung 522
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT D

GENERAL CONDITIONS

1. INDEPENDENT PARTIES:

Contractor hereby declares that Contractor is engaged as an independent business and Contractor agrees to perform the services as an independent contractor.

The manner and means of conducting the services and tasks are under the control of Contractor except to the extent they are limited by statute, rule or regulation and the express terms of this Contract. No civil service status or other right of employment will be acquired by virtue of Contractor’s services. None of the benefits provided by the City to its employees, including but not limited to unemployment insurance, workers’ compensation plans, vacation and sick leave, are available from the City to Contractor, its employees or agents. Deductions shall not be made for any state or federal taxes, FICA payments, PERS payments, or other purposes normally associated with an employer-employee relationship from any compensation due to Contractor. Payments of the above items, if required, are the responsibility of Contractor.

2. TIME IS OF THE ESSENCE:

Contractor and the City agree that time is of the essence regarding the performance of this Contract.

3. STANDARD OF CARE:

Contractor agrees to perform all services hereunder in a manner commensurate with the prevailing standards of like professionals or service Contractors, as applicable, in the San Francisco Bay Area and agrees that all services shall be performed by qualified and experienced personnel who are not employed by the City.

4. IMMIGRATION REFORM AND CONTROL ACT (IRCA):

Contractor assumes all responsibility for verifying the identity and employment authorization of all of its employees performing work hereunder, pursuant to all applicable IRCA or other federal, or state rules and regulations. Contractor shall indemnify, defend, and hold the City harmless from and against any loss, damage, liability, costs or expenses arising from any noncompliance of this provision by Contractor.

5. NON-DISCRIMINATION:

Consistent with the City’s policy and state and federal law that harassment and discrimination are unacceptable conduct, Contractor and its employees, contractors, and agents shall not harass or discriminate against any job applicant, City employee, or any other person on the basis of any kind of any statutorily (federal, state or local) protected class, including but not limited to: race, religious creed, color, national origin, ancestry, 7866 Richmond Rod and Gun Club
523
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
disability (both mental and physical) including HIV and AIDS, medical condition (e.g. cancer), genetic information, marital status, sex, gender, gender identity, gender expression, age, sexual orientation, pregnancy, political affiliation, military and veteran status or legitimate union activities. Contractor agrees that any violation of this provision shall constitute a material breach of this Contract.

6. CITY PROPERTY:
a. Each and every report, draft, work product, map, record, applicable plans, drawings, calculation, data, specification, video, graphic, or any other material or document produced, prepared or caused to be prepared by Contractor pursuant to or in connection with this Contract shall be the exclusive property of the City. b. Notwithstanding the foregoing, Contractor shall not be obligated to provide to City proprietary software or data which Contractor has developed or had developed for Contractor's own use; provided, however, that Contractor shall, pursuant to Section 11 below, indemnify, defend and hold the City harmless from and against any discovery or Public Records Act request seeking the disclosure of such proprietary software or data. c. No report, information or other data given to or prepared or assembled by Contractor pursuant to this Contract shall be made available to any individual or organization by Contractor without prior approval of the City Manager or their designee. d. Contractor shall, at such time and in such form as City Manager or their designee may require, furnish reports concerning the status of services and tasks required under this Contract.

7. RECORDS:
a. Contractor shall maintain complete and accurate records with respect to the services, tasks, work, documents and data in sufficient detail to permit an evaluation of Contractor’s performance under the Contract, as well as maintain books and records related to sales, costs, expenses, receipts and other such information required by the City that relate to the performance of the services and tasks under this Contract (collectively the “Records”).
b. All Records shall be maintained in accordance with generally accepted accounting principles and shall be clearly identified and readily accessible. Contractor shall provide free access to the Records to the representatives of the City or its designees during regular business hours upon reasonable prior notice. The City has the right to examine and audit the Records, and to make copies or transcripts therefrom as necessary, and to allow inspection of all proceedings and activities related to this Contract. Such Records, together with supporting documents, shall be kept separate from other documents and records and shall be maintained by Contractor for a period of five (5) years after receipt of final payment.
7866 Richmond Rod and Gun Club
524
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. If supplemental examination or audit of the Records is necessary due to concerns raised by the City’s preliminary examination or audit of records, and the City’s supplemental examination or audit of the records discloses a failure to adhere to appropriate internal financial controls, or other breach of this Contract or failure to act in good faith, then Contractor shall reimburse the City for all reasonable costs and expenses associated with the supplemental examination or audit.

8. PERMITS AND LICENSES:

Contractor, at its sole expense, shall obtain and maintain during the term of this Contract, all appropriate permits, certificates and licenses, including a City business license, required in connection with the performance of the services and tasks hereunder.

The failure to obtain such permits and licenses shall be a material breach of this Contract and grounds for immediate termination by City; provided, however, that City may waive the business license requirement in writing under unusual or extraordinary circumstances without necessitating any modification of this Contract to reflect such waiver.

9. TERMINATION:
a. Termination Without Default. Notwithstanding any provision herein to the contrary, the City may, in its sole and absolute discretion and without cause, terminate this Contract at any time prior to completion by Contractor of the project or services hereunder immediately upon transmission of written notice to Contractor as provided in Exhibit C “Authorized Representatives and Notices”.
b. Termination in the Event of Default. Should Contractor fail to perform any of its obligations hereunder, within the time and in the manner provided or otherwise violate any of the terms of this Contract, City may immediately terminate this Contract by giving written notice of such termination, stating the reasons for such termination. Contractor shall be compensated as provided in Exhibit B; provided, however, there shall be deducted from such amount the amount of damage, including attorney's fees, expert witness fees and costs, if any, sustained by City by virtue of Contractor's breach of this Contract. Additionally, in the event of such termination, the City may proceed with the work in any reasonable manner it chooses.

10. CONFLICT OF INTEREST:

Contractor acknowledges, represents and warrants that Contractor shall avoid all conflicts of interest (as defined under any federal, state or local statute, rule or regulation, or at common law) with respect to this Contract. Contractor further acknowledges, represents and warrants that no City official or employee has any economic interest, as defined in Title 2, California Code of Regulations §§ 18703.1 through 18703.5, with Contractor that would invalidate this Contract. Contractor acknowledges that in the event that Contractor shall be found by any judicial or administrative body to have any conflict of interest (as defined above) with respect to this Contract, all consideration received under 7866 Richmond Rod and Gun Club
525
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
this Contract shall be forfeited and returned to City forthwith. This provision shall survive the termination of this Contract for one (1) year.

11. HOLD HARMLESS:
a. To the fullest extent permitted by law, Contractor shall indemnify, defend (with counsel acceptable to the City) and hold harmless the City, its City Council, boards, commissions, officials, employees, agents and volunteers (“Indemnitees”) from and against any and all loss, damages, liability, obligations, claims, suits, judgments, costs and expenses whatsoever, including attorney’s fees and costs of litigation (“Claims”), arising from or in any manner connected to Contractor’s performance of its obligations under this Contract or failure to comply with any of its obligations under this Contract or out of the operations conducted by Contractor even if the City is found to have been negligent. If the Claims filed against Indemnitees allege negligence, recklessness or willful misconduct on the part of Contractor, Contractor shall have no right of reimbursement against Indemnitees for the costs of defense even if negligence, recklessness or willful misconduct is not found on the part of Contractor. Contractor shall not have any obligations to indemnify Indemnitees if the loss or damage is found to have resulted solely from the negligence or the willful misconduct of the City. The defense and indemnification obligations of this Contract are undertaken in addition to, and shall not in any way be limited by, the insurance obligations contained in this Contract. b. This indemnification obligation shall survive this Contract and shall not be limited by any term of any insurance policy required under this Contract; provided however, that if this Contract is for design professional services, this indemnity provision is limited to claims that arise out of, pertain to, or relate to the negligence, recklessness, or willful misconduct of the design professional (as defined in California Civil Code section 2782.8).

12. LIMITATIONS UPON SUBCONTRACTING AND ASSIGNMENT:
a. This Contract binds the heirs, successors, assigns and representatives of Contractor. The Contractor shall not enter into subcontracts for any work contemplated under this Contract and shall not assign this Contract, nor any portion hereof or monies due or to become due, without the prior written consent of the City Council or its designee.
b. Contractor shall not assign, sublease, hypothecate, or transfer this Contract, or any interest therein, directly or indirectly, by operation of law or otherwise, without prior written consent of the City Manager. Contractor shall submit a written request for consent to transfer to the City Manager at least thirty (30) days in advance of the desired transfer.

The City Manager or their designee may consent or reject such request in their sole and absolute discretion. Any attempt to do so without said consent shall be null and void, and any assignee, sublessee, hypothecate or transferee shall acquire no right or interest by reason of such attempted assignment, hypothecation or transfer. However, claims for 7866 Richmond Rod and Gun Club
526
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
money against the City under this Contract may be assigned by Contractor to a bank, trust company or other financial institution without prior written consent. c. The sale, assignment, transfer or other disposition of any of the issued and outstanding capital stock of Contractor (if applicable), or of the interest of any general partner or joint venturer or syndicate member if Contractor is a partnership or jointventure or syndicate, which shall result in a change of control of Contractor, shall be deemed an assignment. For this purpose, control shall mean fifty percent or more of the voting power or twenty-five percent or more of the assets of the corporation, partnership or joint-venture.
d. Only those persons and/or businesses whose names and resumés are attached to this Contract shall be used in the performance of this Contract. However, if after the start of this Contract, Contractor wishes to use sub-contractors, at no additional costs to the City, then Contractor shall submit a written request for consent to add subcontractors including the names of the sub-contractors and the reasons for the request to the City Manager at least five (5) days in advance. The City Manager may consent or reject such requests in their sole and absolute discretion. e. Each sub-contractor shall be required to furnish proof of workers’ compensation insurance and shall also be required to carry general, automobile and professional liability insurance (as applicable) in reasonable conformity to the insurance carried by Contractor.
f. In addition, any tasks or services performed by sub-contractors shall be subject to each provision of this Contract. Contractor shall include the following language in their Contract with any sub-contractor: “Sub-Contractors hired by Contractor agree to be bound to Contractor and the City in the same manner and to the same extent as Contractor is bound to the City.”
g. The requirements in this Section 12 shall not apply to persons who are merely providing materials, supplies, data or information that Contractor then analyzes and incorporates into its work product.

13. SAFETY:
a. Contractor acknowledges that the City is committed to the highest standards of workplace safety. Contractor will be solely and completely responsible for conditions of all vehicles owned or operated by Contractor, including the safety of all persons and property during performance of the services and tasks under this Contract.

Contractor shall assume sole and complete responsibility for the safety of Contractor's employees and any of subcontractor's employees This requirement will apply continuously and not be limited to normal working hours. In addition, Contractor will comply with all safety provisions in conformance with U.S. Department of Labor Occupational Safety and Health Act, any equivalent state law, and all other applicable 7866 Richmond Rod and Gun Club
527
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
federal, state, county and local laws, ordinances, codes, and any regulations that may be detailed in other parts of the Contract. Where any of these are in conflict, the more stringent requirements will be followed. Contractor’s failure to thoroughly familiarize itself with the aforementioned safety provisions will not relieve it from compliance with the obligations and penalties set forth herein.
b. Contractor will immediately notify the City (in no event less than 24 hours) of any incident of death, serious personal injury or substantial property damage that occurs in connection with the performance of this Contract. Contractor will promptly submit to the City a written report of all incidents that occur in connection with this Contract. This report must include the following information: (i) name and address of injured or deceased person(s); (ii) name and address of Contractor’s employee(s) involved in the incident; (iii) name and address of Contractor’s liability insurance carrier; (iv) a detailed description of the incident; and (v) a police report.
c. Contractor acknowledges that the City shall have the right to impose, at the City’s sole discretion, requirements that it deems are necessary to protect the health and safety of the City employees, residents, and visitors. Contractor agrees to comply with all such requirements, including, but not limited to, mandatory vaccinations, the use of personal protective equipment (e.g. masks), physical distancing, and health screenings.

Contractor also agrees to make available to the City, at the City’s request, records to demonstrate Contractor’s compliance with this Section.

14. INSURANCE:

Insurance requirements are set forth in Exhibit F to this Contract. Contractor shall abide by the insurance requirements set forth in said Exhibit F.

15. COMPLIANCE WITH ALL APPLICABLE LAWS:
a. During the term of this Contract, Contractor shall keep fully informed of all existing and future state and federal laws and all municipal ordinances and regulations of the City of Richmond which affect the manner in which the services or tasks are to be performed by Contractor, as well as all such orders and decrees of bodies or tribunals having any jurisdiction or authority over the same. Contractor shall comply with all applicable laws, state and federal and all ordinances, rules and regulations enacted or issued by the City. Compliance under this provision includes compliance with all provisions of the Richmond Municipal Code ("Municipal Code"), including Chapters 2.50,

2.52, 2.56, and 2.60, if applicable.
b. Contractor acknowledges that under § 2.60.070 of the Municipal Code ("Living Wage Ordinance"), Contractor is required to provide the City with documents and information verifying its compliance with the Living Wage Ordinance. Contractor shall notify each of its affected employees with regards to the wages that are required to be paid pursuant to the Living Wage Ordinance as prescribed in § 2.60.070 of the Municipal Code.
7866 Richmond Rod and Gun Club
528
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
c. Contractor shall comply with § 2.28.030 of the Municipal Code, obligating every Contractor or sub-Contractor under an agreement or sub-agreement with the City for public works, goods or services to refrain from discriminatory employment or practices on the basis of race, color, sex, sexual orientation, religious creed, national origin or ancestry of any employee, any applicant for employment or any potential sub-contractor. d. Contractor acknowledges that the City’s Drug Free Workplace Policy, Violence in the Workplace Policy and the Policy Against Workplace Harassment, are available on the City’s website at http://www.ci.richmond.ca.us/workplacepolicies.

Contractor agrees to abide by the terms and conditions of said policies.

16. INTEGRATED CONTRACT:

The Recitals and exhibits are a material part of this Contract and are expressly incorporated herein. This Contract represents the full and complete understanding of every kind or nature whatsoever between the parties hereto, and all preliminary negotiations and agreements of whatsoever kind or nature are merged herein. No verbal agreement or implied covenant shall be held to vary the provisions hereof. Any modification of this Contract will be effective only by written execution signed by both the City and Contractor.

17. CONFLICTING PROVISIONS:

In the event of a conflict between these General Conditions and those of any Exhibit or attachment hereto, these General Conditions shall prevail; provided, however, that any Special Condition as set forth in Exhibit E shall prevail over these General Conditions. In the event of a conflict between the terms and conditions of any two or more Exhibits or attachments hereto, those prepared by City shall prevail over those prepared by the Contractor, and the terms and conditions preferred by the City shall prevail over those preferred by the Contractor.

18. FORCE MAJEURE:

Neither party hereto shall be considered in default in the performance of its obligations hereunder to the extent that the performance of such an obligation is prevented or delayed by reason of acts of God, strikes, boycotts, lock-outs, inability to procure materials not related to the price thereof, failure of power, restrictive governmental laws and regulations enacted after the date of this Contract, riots, civil unrest, acts of terrorism, insurrection, war, declaration of a state or national emergency or other reasons of a like nature not within the reasonable control of such party.

19. CONFLICT OF LAW:

This Contract shall be interpreted under, and enforced by the laws of the State of 7866 Richmond Rod and Gun Club
529
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
California without regard to any choice of law rules which may direct the application of laws of another jurisdiction. The Contract and obligations of the parties are subject to all valid laws, orders, rules, and regulations of the authorities having jurisdiction over this Contract (or the successors of those authorities). Any suits brought pursuant to this Contract shall be filed with the courts of the County of Contra Costa, State of California.

20. CLAIMS:

Any claim by Contractor against City hereunder shall be subject to Government Code §§ 800 et seq. The claims presentation provisions of said Act are hereby modified such that the presentation of all claims hereunder to the City shall be waived if not made within six months after accrual of the cause of action.

21. INTERPRETATION:

This Contract shall be interpreted as if drafted by both parties.

22. WARRANTY:

If any product is be provided to the City as part of this Contract, Contractor warrants as follows: Contractor possesses good title to the product and the right to transfer the product to City; the product shall be delivered to the City free from any security interest or other lien; the product meets any specifications contained herein; the product shall be free from material defects in materials and workmanship under normal use for a period of one (1) year from the date of delivery; and the product shall be fit for its intended purpose(s). Notwithstanding the foregoing, consumable and maintenance items (such as light bulbs and batteries) shall be warranted for a period of one hundred and eighty (180) days from the date of delivery. All repairs during the warranty period shall be promptly performed by Contractor, at Contractor's expense, including shipping.

23. SEVERABILITY:

In the event that any of the provisions or portions or applications thereof of this Contract are held to be unenforceable or invalid by any court of competent jurisdiction, City and Contractor shall negotiate an equitable adjustment in the provisions of the Contract with a view toward effecting the purpose of this Contract, and the validity and enforceability of the remaining provisions or portions or applications thereof, shall not be affected thereby.

24. AUTHORITY:

City warrants and represents that the signatory hereto (the Mayor of the City of Richmond or the City Manager) is duly authorized to enter into and execute this Contract on behalf of City. The party signing on behalf of Contractor warrants and represents that they are duly authorized to enter into and execute this Contract on behalf of Contractor, 7866 Richmond Rod and Gun Club
530
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
and shall be personally liable to City if they are not duly authorized to enter into and execute this Contract on behalf of Contractor.

25. WAIVER:

The waiver by City of any breach of any term or provision of this Contract shall not be construed as a waiver of any subsequent breach. Inspections or approvals, or statements by any officer, agent or employee of the City relating to the Contractor’s performance, or payment therefore, or any combination of these acts, shall not relieve the Contractor’s obligation to fulfill this Contract as prescribed; nor shall the City be thereby stopped from bringing any action for damages or enforcement arising from any failure to comply with any of the terms and conditions of this Contract.

26. COUNTERPARTS:

This Contract may be executed in any number of counterparts (including by fax, PDF, DocuSign, or other electronic means), each of which shall be deemed an original, but all of which shall constitute one and the same instrument.

27. SANCTUARY CITY CONTRACTING ORDINANCE (SCCO):

The Richmond Sanctuary City Contracting Ordinance No. 12-18 prohibits the City from granting and or retaining contracts with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor must submit the Sanctuary City Compliance Statement, attached hereto as Exhibit G. 7866 Richmond Rod and Gun Club
531
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT E

SPECIAL CONDITIONS
The General Conditions are hereby amended to include the following modifications and/or provisions (if applicable, otherwise please state “NONE”):
7866 Richmond Rod and Gun Club
Exhibit F is hereby replaced by Exhibit F-1.
532
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT F

INSURANCE PROVISIONS
☐ CHECK HERE IF RISK MANAGEMENT HAS APPROVED WAIVING INSURANCE REQUIREMENTS FOR THIS CONTRACT.

1. CERTIFICATES: Before the commencement of the terms of this Contract, and during the entire term of this Contract and any extension or modification thereof, Contractor shall furnish the City’s Risk Manager with certificates showing the type, amount, class of operations covered, effective dates and dates of expiration of insurance coverage in compliance with coverage requirements set forth by the City and incorporated herein.

Such certificates, which do not limit Contractor’s indemnification, shall also contain substantially the following statement:
“Should any of the above insurance covered by this certificate be canceled or coverage reduced before the expiration date thereof, the insurer affording coverage shall provide thirty (30) days’ advance written notice to the City of Richmond.

Attention: Risk Manager.”
Contractor shall maintain in force at all times during the performance of this Contract all appropriate coverage of insurance required by this Contract with an insurance company licensed to offer insurance business in the State of California with a current A.M. Best’s rating of no less than A:VII or Standard & Poor’s Rating (if rated) of at least BBB unless otherwise acceptable to the City. Contractor shall deliver updated insurance certificates to the City at the address set forth in Exhibit C prior to the expiration of the existing insurance certificate for the duration of the term of Contract.

Endorsements naming the City, its City Council, boards, commissions, officials, employees, agents, and volunteers as additional insured shall be submitted with the insurance certificates.

2. COVERAGE REQUIREMENTS: The City’s insurance requirements depend upon the type of service being provided and/or the provider. The City’s insurance requirements will fall into one of the following categories (unless otherwise provided by the City):

Consultants and Contractors – Type 1
Professional Services – Type 2
Environmental Risk/Hazardous Waste Material – Type 3
Lease of City Property – Type 4
Vendors, Suppliers, Small Grant Recipients & Nonprofit Organizations – Type 5 Transportation Providers – Type 6
Professional Services Pyrotechnics – Type 7
Cyber and I.T. Risks – Type 8
7866 Richmond Rod and Gun Club
533
Contract No: ________ For the Contract between the City of Richmond and
_____________________________
The insurance requirements classification applicable to this Contract shall be attached to this Exhibit F and made a part hereof.

3. FAILURE TO SECURE: If Contractor at any time during the term hereof should fail to secure or maintain the foregoing insurance, the City shall be permitted to obtain such insurance in Contractor’s name or as an agent of Contractor and shall be compensated by Contractor for the costs of the insurance premiums at the maximum rate permitted by law and computed from the date written notice is received that the premiums have not been paid.

4. SUFFICIENCY OF INSURANCE: The insurance limits required by the City are not represented as being sufficient to protect Contractor. Contractor is advised to consult Contractor’s insurance broker to determine adequate coverage for Contractor. The coverage and limits shall be (1) the minimum coverage and limits specified in this Contract; or (2) the broader coverage and maximum limits of the coverage carried by or available to Contractor; whichever is greater.

INSERT INSURANCE REQUIREMENTS CLASSIFICATION APPLICABLE TO THIS CONTRACT: (IF NECESSARY, CONFIRM WITH RISK MANAGER)
7866 Richmond Rod and Gun Club
534
For the Contract between the City of
Richmond and
Short Form Contract Insurance Provisions/EJ/TE 11-30-07 EXHIBIT F-1

INSURANCE PROVISIONS

1. Insurance Requirements – During the Term of this Contract, the City’s Insurance Requirements are hereby waived.

2. Waiver of Liability – As a condition of this Contract, the Contractor, its officers, agents and employees, hereby waive any and all rights to seek recovery for loss or damages of any kind against the City of Richmond, its officers, agents, and employees arising out of the goods or services provided under this Contract. This waiver of liability shall survive the expiration or termination of this Contract.
535
Contract No: ________ For the Contract between the City of Richmond and
_____________________________

EXHIBIT G

SANCTUARY CITY COMPLIANCE STATEMENT
The undersigned, (hereafter "Contractor"), has had an opportunity to review the requirements of City of Richmond Ordinance 12-18 (hereafter "Sanctuary City Contracting Ordinance" or “SCCO”).

Contractor understands and agrees that the City may choose with whom it will maintain business relations and may refrain from contracting with any person or entity that provides Data Broker or Extreme Vetting services to the U.S. Immigration and Customs Enforcement Division of the United States Department of Homeland Security (“ICE”). Contractor understands the meaning of the following terms used in the SCCO:
a. "Data Broker” means either of the following:
i. The collection of information, including personal information about consumers, from a wide variety of sources for the purposes of reselling such information to their customers, which include both private-sector business and government agencies;
ii. The aggregation of data that was collected for another purpose from that for which it is ultimately used.
b. “Extreme Vetting” means data mining, threat modeling, predictive risk analysis, or other similar services."
Contractor understands that it is not eligible to receive or retain a City contract if at the time the Contract is executed, or at any time during the term of the Contract, it provides Data Broker or Extreme Vetting services to ICE.

Contractor further understands and agrees that Contractor's failure to comply with the SCCO shall constitute a material default of the Contract and the City Manager may terminate the Contract and bar Contractor from bidding on future contracts with the City for five (5) years from the effective date of the contract termination.

By executing this statement, Contractor certifies that it complies with the requirements of the SCCO and that if at any time during the term of the Contract it ceases to comply, Contractor will promptly notify the City Manager in writing. Any person or entity who knowingly or willingly supplies false information in violation of the SCCO shall be guilty of a misdemeanor and subject to a $1,000 fine.

Based on the foregoing, the undersigned declares under penalty of perjury under the laws of the State of California that the foregoing is true and correct.

Printed Name: Title:

Signed: Date:

Business Entity:
7866 Richmond Rod and Gun Club
536
537
538
Emily
Combs
Digitally signed
by Emily Combs
Date:
2026.03.13
18:25:37 -07'00'
539

July 7, 2026
Public Works
DATE: July 7, 2026
TO: Mayor Martinez and Members of the City Council
FROM: Daniel Chavarria, PE, Director of Public Works
Tawfic N. Halaby, PE, Deputy Director of Public Works
Subject: Re-Certification of the Updated Sewer System
Management Plan
FINANCIAL IMPACT: There is no financial impact associated with adopting this resolution.

PREVIOUS COUNCIL
ACTION:

March 20, 2012
October 15, 2013
July 18, 2017

STATEMENT OF THE
ISSUE:

The State Water Resources Control Board requires
public entities that own or operate sanitary sewer
systems to prepare, implement, and periodically update a Sewer System Management Plan, which guides the
proper and efficient management, operation, and
maintenance of the system. Order Number 2022-0103-
DWQ requires governing bodies to re-certify updated
plans that reflect current requirements and evolving best management practices. City Council action is required to re-certify the City of Richmond’s updated plan and
maintain compliance with State requirements.

RECOMMENDED ACTION: ADOPT a resolution approving and re-certifying the updated Sewer System Management Plan for the City of
Richmond sanitary sewer collection system to maintain
compliance with State Water Resources Control Board
requirements - Public Works Department (Tawfic Halaby
510-620-5482).

AGENDA
REPORT
540

July 7, 2026
DISCUSSION:

Background and Purpose of the Sewer System Management Plan The City of Richmond owns and is responsible for the sanitary sewer collection system, which includes the pipes, manholes, pump stations, and related infrastructure that move wastewater through the City’s wastewater system. Proper management of this system is essential to protecting public health, preventing sewage releases, protecting local waterways, and maintaining reliable wastewater service for residents and businesses.

A Sewer System Management Plan is a State-required document that functions as the City’s management, operations, maintenance, and compliance plan for the sewer collection system. The plan is intended to ensure that the City has clear procedures and documented practices for operating and maintaining the system, preventing sanitary sewer overflows, responding to emergencies, training personnel, identifying system risks, prioritizing repairs, and planning for long-term infrastructure needs.

For members of the public, the practical purpose of the Sewer System Management Plan is straightforward: it explains how the City manages its sewer system to reduce spills, protect neighborhoods and waterways, and keep the wastewater collection system functioning safely and reliably.

Original State Requirements
On May 2, 2006, the State Water Resources Control Board adopted Order Number 2006-0003-DWQ, establishing statewide waste discharge requirements for sanitary sewer systems. The Order required public entities that own or operate sanitary sewer systems to comply with statewide requirements intended to reduce and eliminate sanitary sewer overflows.

As part of the 2006 Order, public agencies were required to prepare and implement a Sewer System Management Plan. The plan was required to address proper management, operation, and maintenance of the sanitary sewer system, along with risk management, system reliability, emergency response, and protection of public health and water quality.

The State Water Resources Control Board amended the original Order in 2013. In response, City staff reviewed and updated the City’s Sewer System Management Plan to remove outdated information and reflect then-current practices. The Richmond City Council adopted the updated plan in October 2013. In 2017, City staff, in coordination with Veolia, conducted another review and update of the plan, which was subsequently re-certified by the City Council.

Updated State Requirements
In December 2022, the State Water Resources Control Board issued Order Number 2022-0103-DWQ, which updated and modernized the statewide requirements for sanitary sewer systems. The updated Order reflects lessons learned from more than sixteen years of implementation and places greater emphasis on proactive system 541

July 7, 2026
management, aging infrastructure, climate change impacts, asset management, rehabilitation planning, and clearer regulatory oversight.

The updated Order also changed the Sewer System Management Plan update cycle from every five years to every six years. Under the updated requirements, agencies must update their plans, obtain approval and re-certification from their governing bodies, and submit the re-certified plan to the State Water Resources Control Board.

City Update and Need for Council Action
City staff and the City’s consultant updated the Sewer System Management Plan to reflect current operational procedures, staffing strategies, maintenance practices, emergency response procedures, and wastewater collection system management practices. The updated plan is intended to align the City’s practices with the current State Order and support the continued effective management of the City’s sanitary sewer collection system.

Although the plan updates were completed prior to the State’s deadline, formal City Council approval and re-certification did not occur at that time. City Council action is now needed to formally approve and re-certify the updated Sewer System Management Plan.

Adoption of the resolution does not approve a construction project, create a new program, or authorize new spending. Rather, it formally confirms that the City Council has reviewed and re-certified the updated plan required by the State. This action supports regulatory compliance and provides the required governing body approval for the City’s current sewer system management practices.

Recommendation
City staff recommend that the City Council adopt a resolution approving and recertifying the updated Sewer System Management Plan. Re-certification will maintain compliance with State Water Resources Control Board requirements and support the City’s continued efforts to properly manage, operate, maintain, and plan for the longterm reliability of the sanitary sewer collection system.

DOCUMENTS ATTACHED:

Attachment 1 – Resolution
Attachment 2 – Conformed Resolution 90-17
Attachment 3 – 2026 Sewer System Management Plan
542
Attachment 1
RESOLUTION NO. ___________
A RESOLUTION OF THE COUNCIL OF THE CITY OF RICHMOND, CALIFORNIA, RECERTIFYING THE UPDATED SEWER SYSTEM MANAGEMENT PLAN (SSMP)

WHEREAS, on May 2, 2006, the State Water Resources Control Board (SWRCB) adopted Order No. 2006-0003-DWQ establishing Statewide General Waste Discharge Requirements for Sanitary Sewer Systems; and
WHEREAS, the 2006 Order requires public entities that own or operate sanitary sewer systems to prepare and implement a Sewer System Management Plan (SSMP) to ensure proper management, operation, maintenance, and protection of public health and water quality; and WHEREAS, the Order requires periodic review and updates of each SSMP to ensure it reflects current operational practices and regulatory requirements; and WHEREAS, in 2017, City staff, in coordination with Veolia, conducted an additional review and update of the SSMP, which was re-certified by the City Council; and WHEREAS, in December 2022, the SWRCB issued Order WQO-2022-0103-DWQ modernizing the original 2006 Order and emphasizing asset management, climate resilience, rehabilitation prioritization, and clearer regulatory oversight; and WHEREAS, the 2022 Order changed the SSMP update cycle from every five years to every six years, and requires governing board recertification and submission to the SWRCB by August 2, 2025; and
WHEREAS, City staff and the City’s consultant have completed updates to the SSMP to reflect current operational procedures, staffing strategies, and wastewater collection system management practices; and
WHEREAS, although these updates were completed prior to the State’s deadline, formal City Council approval and re-certification remain necessary to maintain compliance with SWRCB requirements.

NOW, THEREFORE, BE IT RESOLVED that the Council of the City of Richmond hereby recertifies the updated Sewer System Management Plan attached hereto, pursuant to California Water Code 13263, contained in Division 7 of such code and regulations. ---------------------------
543
Attachment 1
I certify that the foregoing resolution was passed and adopted by the Council of the City of Richmond at a special meeting thereof held on July XX, 2026, by the following vote:

AYES:

NOES:

ABSTENTIONS:

ABSENT:
_________________________________

CLERK OF THE CITY OF RICHMOND
(seal)
APPROVED:
_________________________
Mayor
APPROVED AS TO FORM:
_________________________
City Attorney
544
545
546

SEWER SYSTEM

MANAGEMENT PLAN
Richmond Municipal Sewer District

Veolia Water operates, maintains and manages the RMSD Sewer Collection, Storm Water and Wastewater Treatment systems by contract to the City of Richmond This document, amended in April 2017, has been assembled to present the City of Richmond’s Sewer System Management Plan (SSMP), which has been prepared pursuant to the Bay Regional Water Quality Control Board’s (RWQCB) SSMP Development Guide (September 2015).

All components of the management plan are currently in place in well The SSMP describes the City’s and Veolia’s goals, organizational stru response plan (OERP), Fats, Oils, and Grease (FOG) control program, legal authority, measures and activities, design and construction standards, capacity management, sanitary sewer overflows (SSO) monitoring, measurement and progr
Certified by: ______________________________
Ryan Smith
Water Resource Recovery Director
City of Richmond

SEWER SYSTEM

MANAGEMENT PLAN
Richmond Municipal Sewer District
Updated May 2017
Veolia Water operates, maintains and manages the RMSD Sewer Collection, Storm Water and Wastewater Treatment systems by contract to the City of Richmond.

This document, amended in April 2017, has been assembled to present the City of Richmond’s Sewer System Management Plan (SSMP), which has been prepared pursuant to the (updated Bay Regional Water Quality Control Board’s (RWQCB) SSMP Development Guide (September 2015).

All components of the management plan are currently in place in well-established programs.

The SSMP describes the City’s and Veolia’s goals, organizational structure, emergency overflow , Fats, Oils, and Grease (FOG) control program, legal authority, measures and activities, design and construction standards, capacity management, sanitary sewer overflows (SSO) monitoring, measurement and program modifications, and audits.

Certified by: ______________________________ Certified by: ______________________________ Aaron Winer
Project Manager
Veolia Water North America
Veolia Water operates, maintains and manages the RMSD Sewer Collection, Storm Water and This document, amended in April 2017, has been assembled to present the City of Richmond’s Sewer updated) San Francisco
Bay Regional Water Quality Control Board’s (RWQCB) SSMP Development Guide (September 2015). established programs.
cture, emergency overflow
, Fats, Oils, and Grease (FOG) control program, legal authority, measures and activities, design and construction standards, capacity management, sanitary sewer overflows (SSO) Certified by: ______________________________
547
This page left intentionally blank
548
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 1
Table of Contents
LIST OF ACRONYMS .......................................................................................................................... i LIST OF TERMS ................................................................................................................................. iii ELEMENT 1 - GOALS ......................................................................................................................... 1

1.1 RWQCB and SWRCB SSMP Requirements ....................................................................... 1-1

1.1.1 RWQCB Requirement ........................................................................................................ 1-1

1.1.2 SWRCB Requirement......................................................................................................... 1-1

1.2 Richmond Municipal Sewer District Goals ......................................................................... 1-1 ELEMENT 2 - ORGANIZATION ....................................................................................................... 2-1

2.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 2-1

2.1.1 RWQCB Requirement ........................................................................................................ 2-1

2.1.2 SWRCB Requirement......................................................................................................... 2-1

2.2 Organization Chart and SSMP Responsibilities................................................................. 2-1 City Council. ............................................................................................................................. 2-2

2.3 Chain of Communication for Reporting .............................................................................. 2-9

2.3.1 During Normal Business Hours .......................................................................................... 2-9

2.3.2 During Non-Business Hours ............................................................................................... 2-9

2.3.3 Regulatory Reporting ......................................................................................................... 2-9 ELEMENT 3 - LEGAL AUTHORITY ................................................................................................ 3-1

3.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 3-1

3.1.1 RWQCB Requirement: ....................................................................................................... 3-1

3.1.2 SWRCB Requirement: ....................................................................................................... 3-1

3.2 Legal Authority to Enforce SSMP Requirements ............................................................... 3-1

3.2.1 Prevention of Illicit Discharges ........................................................................................... 3-2

3.2.2 Proper Design and Construction of Sewers and Connections ........................................... 3-5 549
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 2

3.2.3 Responsibility for Private Laterals ...................................................................................... 3-5

3.2.4 Access for Maintenance, Inspection & Repairs .................................................................. 3-6

3.2.5 Limit Discharge of Fats, Oils & Grease and Debris ............................................................ 3-7

3.2.6 Enforcement Measures ...................................................................................................... 3-7

3.3 Interagency Agreements and Satellite Systems ................................................................ 3-8 ELEMENT 4 - OPERATION AND MAINTENANCE PROGRAM ..................................................... 4-1

4.1 SSMP Requirement for Collection System Maps ............................................................... 4-1

4.1.1 RWQCB Requirement ........................................................................................................ 4-1

4.1.2 SWRCB Requirement......................................................................................................... 4-1

4.1.3 RMSD Collection System Mapping Description ................................................................. 4-1

4.2 SSMP Requirement for Resources and Budget ................................................................. 4-2

4.2.1 RWQCB Requirement ........................................................................................................ 4-2

4.2.2 SWRCB Requirement......................................................................................................... 4-2

4.2.3 RMSD Resources and Budget for Sewer System Management ....................................... 4-2

4.3 SSMP Requirement for Prioritized Preventative Maintenance ......................................... 4-2

4.3.1 RWQCB Requirement ........................................................................................................ 4-2

4.3.2 SWRCB Requirement......................................................................................................... 4-3

4.3.3 Prioritized Preventive Maintenance Activities .................................................................... 4-3

4.4 SSMP Requirements for Inspections, Condition Assessment and Rehabilitation......... 4-4

4.4.1 RWQCB Requirement ........................................................................................................ 4-4

4.4.2 SWRCB Requirement......................................................................................................... 4-4

4.4.3 CCTV Inspection Program ................................................................................................. 4-4

4.5 SSMP Requirement for Training .......................................................................................... 4-5

4.5.1 RWQCB Requirement ........................................................................................................ 4-5

4.5.2 SWRCB Requirement......................................................................................................... 4-5 550
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 3

4.5.3 Training of City Personnel and Contractors ....................................................................... 4-5

4.6 SSMP Requirement for Contingency Equipment ............................................................... 4-6

4.6.1 RWQCB Requirement ........................................................................................................ 4-6

4.6.2 SWRCB Requirement......................................................................................................... 4-6

4.7 Contingency Equipment and Replacement Inventories .................................................... 4-6

4.8 Critical Replacement Parts ................................................................................................... 4-6 ELEMENT 5 - DESIGN AND PERFORMANCE PROVISIONS ....................................................... 5-1

5.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 5-1

5.1.1 RWQCB Requirement ........................................................................................................ 5-1

5.1.2 SWRCB Requirement......................................................................................................... 5-1

5.2 Design and Construction Standards for Installation, Rehabilitation and Repair ........... 5-1

5.3 Procedures and Standards for Inspection, Testing, Rehabilitation and Repair ............. 5-2 ELEMENT 6 - OVERFLOW EMERGENCY RESPONSE PLAN ...................................................... 6-1

6.1 RWQCB and SWRCB SSMP Requirement .......................................................................... 6-1

6.1.1 RWQCB Requirement: ....................................................................................................... 6-1

6.1.2 SWRCB Requirement: ....................................................................................................... 6-1

6.2 OERP Goals ........................................................................................................................... 6-2

6.3 SSO Categories ..................................................................................................................... 6-2

6.4 SSO Notification Procedures ............................................................................................... 6-3

6.4.1 Normal Working Hours ....................................................................................................... 6-4

6.4.2 After Normal Working Hours .............................................................................................. 6-5

6.4.3 Notification from Pump Station SCADA Alarms ................................................................. 6-5

6.5 Staff and Contractor Training .............................................................................................. 6-5

6.6 Response Program ............................................................................................................... 6-5

6.6.1 First Responder Priorities ................................................................................................... 6-7

6.6.2 Initial Response .................................................................................................................. 6-7 551
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 4

6.6.3 External SSO Response .................................................................................................... 6-8

6.6.4 Internal SSO Response (Residential Sewage Backup) ..................................................... 6-9

6.6.5 Pump Station SSO Response ............................................................................................. 10

6.6.6 Recovery and Cleanup ..................................................................................................... 6-10

6.7 Impact to Waters of the United States .............................................................................. 6-12

6.7.1 Water Quality Sampling .................................................................................................... 6-12

6.7.2 Water Quality Monitoring Plan .......................................................................................... 6-12

6.7.3 SSO Technical Report ...................................................................................................... 6-13

6.8 Containment or Bypass ...................................................................................................... 6-13

6.9 SSO Notification Signage ................................................................................................... 6-14

6.10 Traffic and Crowd Control .................................................................................................. 6-14

6.11 SSO Failure Analysis .......................................................................................................... 6-15

6.12 SSO Documentation and Reporting .................................................................................. 6-15

6.12.1 Regulatory Reporting ...................................................................................................... 6-16

6.12.2 Technical Report ............................................................................................................. 6-18

6.13 Equipment .............................................................................................................................. 6-22

6.14 Contractors Working On City Sewer Facilities................................................................. 6-22

6.15 Training ................................................................................................................................ 6-22

6.15.1Initial and Annual Refresher Training ............................................................................... 6-22

6.15.2SSO Response Drills ........................................................................................................ 6-23

6.15.3SSO Training Record Keeping ......................................................................................... 6-23 ELEMENT 7 - FOG CONTROL PROGRAM .................................................................................... 7-1

7.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 7-1

7.1.1 RWQCB Requirement: ....................................................................................................... 7-1

7.1.2 SWRCB Requirement: ....................................................................................................... 7-1

7.2 Public Education Outreach Plan .......................................................................................... 7-2 552
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 5

7.3 FOG Disposal Plan ................................................................................................................ 7-2

7.4 Legal Authority to Prohibit SSOs and Blockages Caused by FOG Discharge ............... 7-3

7.5 Requirements and Design Standards for Installation of Grease Removal Devices ....... 7-4

7.6 Device Maintenance Requirements ..................................................................................... 7-8

7.7 BMP Requirements, Recordkeeping and Reporting ........................................................... 79

7.8 Authority to Inspect Grease Producing Facilities and Enforce Requirements ............. 7-10

7.9 Sewer Sections Subject to FOG Blockages ..................................................................... 7-11 ELEMENT 8 - SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN ............................ 8-1

8.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 8-1

8.1.1 RWQCB Requirement ........................................................................................................ 8-1

8.1.2 SWRCB Requirement......................................................................................................... 8-1

8.2 System Evaluation and Capacity Assurance Plan ............................................................. 8-1

8.2.1 Pipeline Capacity Assessment and Capital Improvement Plan ......................................... 8-2

8.2.2 Pump Station Capacity Assessment and Capital Improvement Plan ................................ 8-3

8.3 Design Criteria ....................................................................................................................... 8-3

8.4 Capacity Enhancement Measures ....................................................................................... 8-3

8.5 Capital Improvement Program Budget and Schedule ....................................................... 8-3 ELEMENT 9 - MONITORING, MEASUREMENT AND PROGRAM MODIFICATIONS .................. 9-1

9.1 RWQCB and SWRCB SSMP Requirements ........................................................................ 9-1

9.1.1 RWQCB Requirement ........................................................................................................ 9-1

9.1.2 SWRCB Requirement......................................................................................................... 9-1

9.2 Maintenance of Relevant Data ............................................................................................. 9-1

9.3 Monitoring and Assessment ................................................................................................ 9-1

9.4 Utility Metrics to Measure Progress and Prioritize Activities ........................................... 9-2

9.5 Performance Monitoring and Program and Modifications ................................................ 9-3

9.6 SSO Trends – Frequency, Location and Volume ............................................................... 9-3 553
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 6

9.7 Appendix H – Element 9 Documents ................................................................................... 9-4 ELEMENT 10 - SSMP PROGRAM AUDITS .................................................................................. 10-1

10.1 RWQCB and SWRCB SSMP Requirements ...................................................................... 10-1

10.1.1RWQCB Requirement ...................................................................................................... 10-1

10.1.2SWRCB Requirement10- ................................................................................................. 10-1

10.2 Audit Procedures, Roles and Responsibilities ................................................................ 10-1

10.3 SSMP Program Modification/Update Process .................................................................. 10-1 ELEMENT 11 - COMMUNICATION PLAN .................................................................................... 11-1

11.1 RWQCB and SWRCB SSMP Requirements ...................................................................... 11-1

11.1.1RWQCB Requirement ...................................................................................................... 11-1

11.1.2SWRCB Requirement....................................................................................................... 11-1

11.2 Communication Plan ........................................................................................................... 11-1 TABLES
Table ES-1. SSMP Objectives
Table 2-1. SSMP Responsibilities
Table 6-1 Regulatory Reporting Requirements
Table 7-1. SSOs due to Fats, Oils and Grease (2011 and 2012) Table 8-1. RMSD Pump Station Capacities
Table 9-1. Success Factors and Metrics
Table 9-2. Summary of SSOs from 2001 through December 23, 2012

FIGURES
Figure ES-1. Richmond Municipal Sewer District Service Area Figure 2-1. RMSD Sewer Collection System Organization Chart Figure 2-2. Chain of Communication
Figure 6-1. SSO Notification Process (same as Figure 2-2)

APPENDICES
554
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 7
Appendix A. Element 2 (Organization) Supporting Documents Appendix B. Element 3 (Legal Authority) Supporting Documents Appendix C. Element 4 (Operations and Maintenance Program) Supporting Documents Appendix D. Element 5 (Design and Construction Standard) Supporting Documents Appendix E. Element 6 (Overflow Emergency Response Plan) Supporting Documents Appendix F. Element 7 (FOG Control Program) Supporting Documents Appendix G. Element 8 (System Evaluation and Capacity Assurance) Supporting Documents Appendix H. Element 9 (Monitoring, Measurement and Program Modifications) Placeholder for Future Supporting Documents
Appendix I. Element 10 (SSMP Program Audits) Supporting Documents Appendix J. Element 11 (Communication Plan) Placeholder for Future Supporting Documents

555
Sewer System Management Plan

TABLE OF CONTENTS
Richmond Municipal Sewer District Page TOC- 8
This page left intentionally blank
556
Sewer System Management Plan

LIST OF ACRONYMS
Richmond Municipal Sewer District Page i

LIST OF ACRONYMS
BACWA Bay Area Clean Water Agencies
BMP Best Management Practice
CCCFCD Contra Costa County Flood Control District
CCTV Closed-Circuit Television
CFR Code of Federal Regulations
CIP Capital Improvement Project
CIWQS California Integrated Water Quality System
CMMS Computerized Maintenance Management System
CDFW California Department of Fish and Wildlife
EHS Environmental Health Services
FHF Food Handling Facility
FOG Fats, Oils and Grease
FSE Food Service Establishment
GIS Geographical Information System
GPM Gallons per Minute
I/I or I&I Inflow & Infiltration
LRGP Lateral Replacement Grant Program
LRO Legally Responsible Official
MGD Million Gallons per Day
MRP Monitoring and Reporting Program
NASSCO National Association of Sewer System Companies
NPDES National Pollution Discharge Elimination System
OERP Overflow Emergency Response Plan
OES Office of Emergency Services (formerly California Emergency Management Agency)
PACP Pipeline Assessment and Certification Program
POTW Publicly-Owned Treatment Works
RMSD Richmond Municipal Sewer District (also referenced as “City”) RWQCB Regional Water Quality Control Board
SSMP Sewer System Management Plan
557
Sewer System Management Plan

LIST OF ACRONYMS
Richmond Municipal Sewer District Page ii
SSO Sanitary Sewer Overflow
SWRCB State Water Resources Control Board
WDR General Waste Discharge Requirements
WPCP Water Pollution Control Plant (also known as the Wastewater Treatment Plant) WWTP Wastewater Treatment Plant
558
Sewer System Management Plan

LIST OF TERMS
Richmond Municipal Sewer District Page iii

LIST OF TERMS
Bay Area Clean Water Association (BACWA) – Association comprised of Bay Area wastewater treatment and collection system agencies. BACWA represents the interests of public wastewater agencies in regulatory matters and to support the exchange of information.

Website: http://www.bacwa.org
Blockage – An object that partially or fully hinders flow through a sewer pipeline. The blockage can be caused by debris in the sewer, grease buildup, root intrusion, or a partial or full collapse of the pipeline. Also known as a stoppage.

California Association of Sanitation Agencies (CASA) - A non-profit, statewide association representing public agencies that provide wastewater collection, treatment, disposal, and/or water reclamation services to California agencies. Website: http://www.casaweb.org California Integrated Water Quality System (CIWQS) – A computer system used by the State and Regional Water Quality Control Boards to track information about SSOs, among other information.

CIWQS is the tool used for online submittal of SSO details, which are then made available to the public. Website: http://www.waterboards.ca.gov/ciwqs/
California Water Environment Association (CWEA) – The statewide association of wastewater professionals that trains and certifies wastewater professionals, disseminates technical information and promotes policies to protect and enhance the environment.

Website: http://www.cwea.org
Enrollee – The legal public entity that owns a sanitary sewer system, as defined by the Statewide WDR. Also known as a sewer system agency or wastewater collection system agency.

FOG Control Program –Program implemented at the discretion of the agency, based on the identified causes of sewer overflows, to reduce the discharge of fats, oils and grease into the sewer system.

Geographical Information System (GIS) – A database linked with mapping that records sewer system information. The GIS database could include sewer features such as pipe location, diameter, material, condition, or last date cleaned or repaired. GIS maps also typically contain base information such as streets and parcels.

Governing Board – Richmond City Council.

Groundwater Induced Infiltration (GWI) – Infiltration attributed to groundwater entering the sewer system.
559
Sewer System Management Plan

LIST OF TERMS
Richmond Municipal Sewer District Page iv
Infiltration – The seepage of groundwater into a sewer system, including service connections. Seepage frequently occurs through defective or cracked pipes, pipe joints, connections or manhole walls and joints.

Inflow – Water discharged into a sewer system from such sources as roof leaders, cellars, yard and area drains, foundation drains, through holes in manhole covers, cross connections from the storm system or street wash waters. Inflow differs from infiltration in that it is a direct discharge into the sewer rather than a leak through defects in the sewer.

Lateral or Private Lateral – The privately-owned sewer pipeline that conveys wastewater from the premises of a user to the City’s sewer system. The upper lateral extends from the building to property line (or easement line). The lower lateral extends from the property or easement line to the connection to the pipe.

Monitoring and Reporting Program - The program used by the City to monitor, maintain records, report issues and complete needed public notifications.

Overflow Emergency Response Plan (OERP) – This document identifies measures that are needed to respond to sanitary sewer overflows in a way that maximizes the protection of public health and the environment.

Preventive maintenance (PM) – Regularly scheduled servicing of machinery, infrastructure or other equipment using appropriate tools, tests, and lubricants.

R-Value – The amount of rainfall that reaches the collection system via infiltration and inflow. This value is typically expressed as a percentage of total rainfall volume that reaches the collection system.

Rainfall Dependent Infiltration and Inflow – Infiltration and Inflow that is attributed directly to rainfall R-Value.

Rehabilitation and Replacement Plan (also referred to as a Capital Improvement Plan) – Identifies and prioritizes system deficiencies and implements short-term and long-term rehabilitation actions to address each deficiency.

San Francisco Bay Regional Water Quality Control Board – Also known as Region 2 or RWQCB.

This regulatory agency preserves, enhances and restores the quality of California's water resources, and ensures their proper allocation and efficient use for the benefit of present and future generations.

Website: http://www.waterboards.ca.gov/sanfranciscobay
Sanitary Sewer Overflow (SSO) – Any overflow, spill, release, discharge or diversion of untreated or partially treated wastewater from a sanitary sewer system, including overflows or releases that reach 560
Sewer System Management Plan

LIST OF TERMS
Richmond Municipal Sewer District Page v
waters of the United States, overflows or releases that do not reach water of the United States, and backups into buildings and/or private property caused by conditions within the publicly owned portion of the sewer system.

Sanitary Sewer System – Any system of pipes, pump stations, sewer lines, or other conveyances, upstream of a wastewater treatment plant head works used to collect and convey wastewater to the wastewater treatment plant.

Satellite Collection System – The portion, if any, of a sanitary sewer system that is owned or operated by a different public agency or user.

Sewer System Management Plan (SSMP) – A series of written programs that address how a collection system owner/operator conducts daily business. Each SSMP is unique for an individual discharger.

The plan includes provisions to provide proper and efficient management, operation, and maintenance of sanitary sewer systems, while taking into consideration risk management and cost benefit.

State Water Resources Control Board – Also called the State Board. This agency developed and passed the Statewide Waste Discharge Requirements for collection systems and maintains the SSO reporting web site.

System Evaluation and Capacity Assurance Plan – A required component of an agency’s SSMP that provides hydraulic capacity of key sanitary sewer system elements for dry weather peak flow conditions, as well as the appropriate design storm or wet weather event.

Statewide Waste Discharge Requirements – The Statewide General Waste Discharge Requirements for Sanitary Sewer Systems was adopted by the SWCRB in 2006 (Order No. 2006-0003-DWQ) to provide a structure and guidance for SSMP development. It was amended in 2013 (Order No 2013-0058- EXEC).

Veolia Water – Contract operator for the RMSD sanitary sewer and stormwater collection systems and wastewater treatment plant.

Wastewater Collection System – See Sanitary Sewer System. 561
Sewer System Management Plan

LIST OF TERMS
Richmond Municipal Sewer District Page vi
This page left intentionally blank
562
Sewer System Management Plan
GOALS
Richmond Municipal Sewer District Page 1-1
ELEMENT 1 - GOALS
The purpose of this section is to identify the goals that the RMSD has established for sewer collection system maintenance and the SSMP. These goals are intended to define a program that promotes continuous improvement in RMSD and its contract operator Veolia Water’s existing wastewater collection system management and maintenance processes.

1.1 RWQCB and SWRCB SSMP Requirements
Requirements for the Goals element of the SSMP are described in the RWQCB SSMP Guidelines and SWRCB Statewide WDR as follows:

1.1.1 RWQCB Requirement
The RMSD must develop goals to manage, operate, and maintain all parts of its collection system. The goals should address the provision of adequate capacity to convey peak wastewater flows, as well as a reduction in the frequency of SSOs and the mitigation of their impacts.

1.1.2 SWRCB Requirement
The RMSD must provide a plan and schedule to properly manage, operate, and maintain all parts of its wastewater collection system in order to reduce and prevent SSOs, as well as to mitigate any SSOs that occur.

1.2 Richmond Municipal Sewer District Goals
The goals of the RMSD and its contract operator, Veolia Water, are to accomplish the following:
• To properly manage, operate, and maintain all parts of the wastewater collection system, so as to preserve and protect the public’s investment in that system • To provide adequate capacity to convey peak flows to the WWTP • To minimize the frequency and duration of SSOs, including implementing regular, proactive maintenance of the system to remove issues that may cause sewer backups or SSOs
• To mitigate the impact of SSOs on public health and the environment • To respond quickly and respectfully to public notifications of SSOs or other collection system issues
• To collect complete and accurate information regarding SSOs for reporting to the appropriate regulatory agencies
563
Sewer System Management Plan
GOALS
Richmond Municipal Sewer District Page 1-2
• To uphold the City’s standards and specifications on newly constructed public and private sewers
• To provide a safe working environment for City and Veolia employees • To provide City and Veolia employees with the tools and training needed to perform their work effectively and achieve the RMSD goals
564
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-1
ELEMENT 2 - ORGANIZATION
The purpose of this section is to identify City and Veolia staff responsible for implementing this SSMP, responding to SSO events and meeting the SSO reporting requirements. This section also includes the designation of the Legally Responsible Official (LRO) or Authorized Representative to meet RWQCB and Statewide WDR requirements for completing and certifying spill reports.

2.1 RWQCB and SWRCB SSMP Requirements
The requirements for the Organization element of the SSMP are described in the RWQCB SSMP Guidelines and SWRCB Statewide WDR as follows:

2.1.1 RWQCB Requirement
The RMSD SSMP must identify staff, including names and phone numbers, who are responsible for implementing measures outlined in the SSMP, including management, administration, and maintenance positions. The SSMP must identify the chain of communication for reporting and responding to SSOs.

2.1.2 SWRCB Requirement
The RMSD SSMP must identify:
• The name of the legally responsible or authorized representative. • The names and telephone numbers for management, administrative, and maintenance positions responsible for implementing specific measures in the SSMP program. Include lines of authority as shown in an organization chart or similar document with a narrative explanation.
• The chain of communication for reporting SSOs, from receipt of a complaint or other information, including the person responsible for reporting SSOs to the State and Regional Water Board and other agencies if applicable (such as County Health Officer, County Environmental Health Agency, RWQCB, and/or California Office of Emergency Services (Cal OES)).

2.2 Organization Chart and SSMP Responsibilities
The RMSD sewer collection system is operated and maintained by contractor Veolia Water.

Veolia is responsible for all sanitary sewer, storm water, and treatment plant operations, maintenance and management, and responds to sewer emergencies including SSOs. Veolia reports each SSO to the Regional Board through CIWQS, and makes all reports to the City, SWRCB, RWQCB, County, Department of Environmental Health Services (EHS), Contra Costa 565
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-2
County Flood Control District (CCCFCD), California Department of Fish and Wildlife (CDFW), and OES as appropriate. The City Water Resource Recovery Director is the Legally Responsible Official (LRO) for certifying SSOs. The City Senior Administrative Analyst is the “back-up” Legally Responsible Official (LRO).

Roles and responsibilities of key personnel involved in managing the wastewater collection system are as follows:

City Council. The Richmond City Council consists of six (6) Council Members who are elected at large, and a separately elected Mayor. The City Council appoints the City Manager. The current City Council Members, as of January 2017, include:
• Mr. Tom Butt – Mayor
• Ms. Jovanka Beckles – Vice Mayor
• Mr. Melvin Willis – Member
• Ms. Gayle McLaughlin – Member
• Mr. Eduardo Martinez – Member
• Mr. Jael Myrick – Member
• Mr. Ben Choi – Member
The City Council Chambers are located at: 440 Civic Center Plaza, Richmond, California.

The main telephone number is: (510) 620-6581.

City Clerk. The City Clerk, Ms. Pamela Christian, supports the City Council and manages specific business functions for the City. Related to this SSMP, the City Clerk receives claims from private property owners for damage to private property that is allegedly the result of City sewer operations.

The City Clerk’s office is located at: 450 Civic Center Plaza, Richmond, California. The contact number is (510) 620-6513.

City Manager. The City Manager is responsible for implementing City Council policy, directing departments and the City’s administrative functions, and for providing day-to-day leadership in policy development and implementation.

Mr. Bill Lindsay, Richmond City Manager, has signatory and certification authority for all applications, reports, or information related to the sewer system..

The City Manager’s office is located at: 450 Civic Center Plaza, Richmond, California. The main telephone number is: (510) 620-6512.

Water Resource Recovery Director. The City’s Water Resource Recovery Director, Mr.

Ryan Smith, ensures compliance with applicable federal, state and local laws and regulations, oversees source control, provides reports on SSO events, and manages the City’s contract operator, Veolia Water.
566
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-3
Mr. Smith is also the General Manager of the Richmond Municipal Sewer district and a Legally Responsible Official. The Director’s office is located at: 450 Civic Center Plaza, Richmond, California. The main telephone number is: (510) 620-5486.

City Source Control Superintendent. The City Source Control Superintendent, Ms. Joanne Le, works directly with the Water Resource Recovery Director. This position is responsible for enforcement of the City’s FOG Control Program and the environmental compliance component of the SSO WDR. Ms. Le is also a data submitter for reporting SSOs into the California Integrated Water Quality System (CIWQS).

The Source Control Superintendent’s office is located at: 450 Civic Center Plaza, Richmond, California. The main telephone number is: (510) 620-6540.

Senior Administrative Analyst. The City Senior Administrative Analyst, Ms. Mary Phelps, is responsible for ensuring all data entered into CIWQS is accurate. Ms. Phelps is the primary LRO for certifying all SSOs entered into the California Integrated Water Quality System.

The Senior Administrative Analyst’s office is located at: 450 Civic Center Plaza, Richmond, CA. The main telephone number is (510) 621-1269.

Project Coordinator. The City’s Project Coordinator, Ms. Gina DeLaTorre, is responsible for the Lateral Inspection Program. Ms. DeLaTorre is also responsible for the public outreach to Plumbers and Contractors to ensure compliance with the Sewer System Management Plan.

The Project Coordinator’s office is located at 450 Civic Center Plaza, Richmond, CA. The main number is (510) 620-6594.

City Risk Manager. The City’s Risk Manager, Ms. Kimberly Greer, is responsible for managing all aspects of risk for the City, including addressing claims related to SSOs.

The City Risk Manager’s office is located at: 450 Civic Center Plaza, Richmond, California.

The Risk Management Division’s telephone number is: (510) 620-6810.

Veolia Project Manager. Veolia Water’s Project Manager, Mr. Aaron Winer, is responsible for managing operations and maintenance of the WWTP and sanitary sewer and stormwater collection systems. Mr. Winer is registered as a data submitter for reporting SSO into CIWQS if necessary. He also serves as the primary contact between Veolia Water and the City’s Water Resource Recovery Director.

The Project Manager is located at the WWTP at 601 Canal Blvd., Richmond, CA. The WWTP main telephone number is (510) 412-2001.
567
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-4
Veolia Underground Asset Management Group. Veolia Water’s Underground Asset Management Group provides overall management of the collection system.

The Underground Asset Management Group is located at Veolia Headquarters at 2300 Contra Costa Blvd, Suite 350, Pleasant Hill, CA. The main office telephone number is (925) 681-2304.

Veolia Capital Program Manager. Veolia Water’s Capital Program Manager, Mr. Fadi Alabbas, manages the implementation of all phases of capital improvement plans for the collection system and wastewater treatment plant.

The Capital Program Manager is located at Veolia Headquarters at 2300 Contra Costa Blvd, Suite 350, Pleasant Hill, CA. The main office telephone number is (925) 681-2304.

Veolia Collection System Manager. Veolia Water’s Collection System Manager, Mr. Tim O’Connor, oversees field operations and maintenance activities, provides relevant information to Veolia Water’s management team, prepares and implements contingency plans, leads emergency responses, investigates , and trains field crews. The Collection System Manager makes all reports to the City, SWRCB, RWQCB, County Department of Environmental Health Services (EHS), Contra Costa County Flood Control District (CCCFCD), California Department of Fish and Wildlife (CDFW) and OES as appropriate.

Mr. O’Connor is a data submitter and is the secondary person responsible for entering SSOs into CIWQS.

The Collection System Manager is located at the WWTP at 601 Canal Blvd., Richmond, CA.

The WWTP main telephone number is (510) 412-2001.

Veolia Collection System Supervisor. Veolia Water’s Collection System Supervisor, Mr.

Wayne Madison, supervises field operations and maintenance activities, provides relevant information to Veolia Water’s management team, prepares and implements contingency plans, leads emergency responses, investigates and reports SSOs to the City, and trains field crews. Mr. Madison is registered as a data submitter and is capable of reporting SSOs in CIWQS.

The Collection System Supervisor is located at the WWTP at 601 Canal Blvd., Richmond, CA. The WWTP main telephone number is (510) 412-2001.

Veolia Collection System Planner/Scheduler. Veolia Water’s Collection System Planner/Scheduler, Ms. Marie Hernandez, works directly with the Underground Asset 568
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-5
Management Group and Field Supervisor to plan, estimate, and prioritize operation and maintenance tasks and project work based on the established performance measurements and benchmarks. She also coordinates emergency response work with the Field Supervisor. Ms.

Hernandez is registered as a data submitter and is the main person responsible for reporting SSOs in CIWQS.

The Collection System Planner/Scheduler is located at the WWTP at 601 Canal Blvd., Richmond, CA. The WWTP main telephone number is (510) 412-2001.

Veolia Collection System Field Crew. Veolia Water’s Field Crew performs preventive maintenance activities, and mobilizes and responds to blockages and SSOs. The Field Crew operates the inspection and sewer cleaning equipment, bypass pumping equipment, portable generators, and other equipment used to maintain the collection system.

The structure of the City and Veolia Water team for RMSD is shown in Figure 2-1. This organization chart also identifies the reporting lines between Veolia and the City of Richmond, and between Veolia, the City, and regulatory agencies.

569
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-6
Figure 2-1. RMSD Sewer Collection System Organization Chart Table 2-1 on the following page presents individual responsibilities for each section of the SSMP.
570
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-7

571
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-8
Table 2-1. SSMP Responsibilities
SSMP Element Responsible Position

1. Goals • The City Manager leads staff in the implementation of the City’s goals.

2. Organization • The Water Resource Recovery Director updates the organizational structure, manages SSMP implementation assignments, and amends SSO response and reporting chains of communication, as needed.

3. Legal Authority • The City Manager upholds the City Ordinance and drafts new ordinances as needed.

4. Operations &
Maintenance
• The Water Resource Recovery Director manages the City’s resources and budget.
• The Project Coordinator manages outreach to plumbers and building contractors.
• The Veolia Project Manager manages Veolia’s resources and budget, preventive maintenance, contingency equipment and replacement inventories, training, collection system map, project inspections, and condition assessments.

5. Design and
Performance
Provisions
• The Water Resource Recovery Directors reviews design and construction documents to ensure that all construction projects meet the City’s standards. The Director also updates standards for installation, rehabilitation and repair, as needed.

6. Overflow
Emergency
Response Plan
• The Veolia Collection System Manager implements the Overflow Emergency Response Plan, makes revisions to the plan, and conducts regular training for maintenance crew members.

7. FOG Control
Program
• The Veolia Collection System Supervisor and the Collection System Planner/Scheduler identify grease hot spots and maintain an effective cleaning program for grease problem sewers. The City Source Control Superintendent inspects grease interceptors/traps that have been installed at non-residential locations and enforces discharge regulations, as needed.

8. System Evaluation
and Capacity
Assurance
• The Water Resource Recovery Director establishes and assesses capacity requirements for the RMSD collection system and manages implementation of the System Evaluation and Capacity Assurance Plan that was completed by Veolia. The Water Resource Recovery Director also endorses the City’s long-term Capital Improvement Plan as developed by Veolia, including updating City CIP budgets and schedules.

9. Monitoring,
Measurement and
Program
Modifications
• The Water Resource Recovery Directory and Veolia Project Manager monitor implementation and assess success of the SSMP program elements, including identifying trends in SSOs, and reporting progress to the City Manager.

10. SSMP Audits • The Water Resource Recovery Director oversees annual SSMP audits.

11. Communication Plan • The Water Resource Recovery Director, City Manager and Veolia Project Manager communicate with the public and nearby agencies regarding the RMSD SSMP.
572
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-9

2.3 Chain of Communication for Reporting
The following chain of communication is also shown in the diagram on Figure 2-2.

2.3.1 During Normal Business Hours
• During normal business hours, telephone calls reporting SSOs are received at Veolia Water’s office, either directly or via the City or 9-1-1. Calls are dispatched by the Collection System Planner/Scheduler to the Field Crew.
• The Field Crew responds to the SSO site within a target range of 30 minutes to one hour and evaluates the severity of the SSO.
• The Field Crew relays the information to the Collection System Manager and/or the Collection System Supervisor, who in turn immediately determines if OES should be notified.
• The Collection System Manager or Collection System Supervisor communicates SSO details to the Collection Planner/ Scheduler as soon as possible after arrival on site and regularly during the SSO response. Information is recorded electronically on the Veolia handheld field devices, and conveyed to the City via a combination of telephone and email communication.

2.3.2 During Non-Business Hours
• After normal business hours, the Field Crew receives SSO calls from the Veolia Water office answering service and responds to the SSO site within one hour. • The Field Crew designee relays the information to the Collection System Manager or the Collection System Supervisor, who immediately determines if OES should be notified.
• The Collection System Manager or the Collection System Supervisor communicates SSO details to the Collection System Planner/Scheduler as described in 2.3.1, above.

2.3.3 Regulatory Reporting
The Collection System Planner/Scheduler is the primary data submitter responsible for SSO reporting.
• Within two hours of becoming aware of any Category 1 SSO greater than or equal to 1,000 gallons discharged to surface water or spilled in a location where it probably will be discharged to surface water, the Veolia Collection System Manager, Collection System Supervisor or the Collections System Planner/Scheduler will notify the California Office of Emergency Services (Cal OES) and obtain a 573
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-10
notification control number.
• Category 1 SSO: Veolia Collection System Planner/Scheduler submits draft report in CIWQS within three days of becoming aware of the SSO and Richmond’s LRO will certify within 15 calendar days of SSO end date.
• Category 2 SSO: Veolia Collection System Planner/Scheduler submits draft report within 3 business days of becoming aware of the SSO and Richmond’s LRO will certify within 15 calendar days of the SSO end date.
• Category 3 SSO: Veolia Collection System Planner/Scheduler submits report within 15 calendar days of the end of month in which SSO the occurred. Richmond LRO will certify within 30 calendar days of the end of the month in which the SSO occurred.
• SSO Technical Report: Richmond’s LRO submits certified report within 45 calendar days after the end date of any Category 1 SSO in which 50,000 gallons or greater are spilled to surface waters.
• “No Spill” Certification: Richmond’s LRO will certify that no SSOs occurred within 30 calendar days of the end of the month or, if reporting quarterly, the quarter in which no SSOs occurred.
• Collection System Questionnaire: Richmond’s LRO will update and certify every 12 months.

Figure 2-2 shows the Veolia and RMSD Chain of Communication for responding to and reporting overflows.

574
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-11
Figure 2-2. Chain of Communication
575
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-12
Appendix A – Element 2 Documents
Appendix A includes the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix A may have been superseded. Please contact the City Water Resource Recovery Director for the most recent updates to the Appendix A documents.
• City Staff First Responder and Contract Responder Names and Contact Numbers • Emergency Contact List

576
Sewer System Management Plan

ORGANIZATION
Richmond Municipal Sewer District Page 2-13
This page left intentionally blank

577
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-1
ELEMENT 3 - LEGAL AUTHORITY
This element of the SSMP discusses the City’s Legal Authority provided through the Richmond Municipal Code (RMC). This section fulfills the Legal Authority requirement for the RWQCB (Element 5) and the SWRCB (Element 3).

3.1 RWQCB and SWRCB SSMP Requirements

3.1.1 RWQCB Requirement:

The RMSD must demonstrate that it has the legal authority (through ordinances, service agreements, and other binding procedures) to control infiltration and inflow (I&I) from satellite collection systems and private service laterals; require proper design, construction, installation, testing, and inspection of new and rehabilitated sewers and laterals; and enforce violation of ordinances.

The SSMP should describe specific applicable legal mechanisms, with citations of names and code numbers of ordinances. If legal authority does not currently exist for a required element, the SSMP should indicate a schedule of activities to obtain the proper legal authority.

3.1.2 SWRCB Requirement:

The RMSD must demonstrate, through collection system use ordinances, service agreements, or other legally binding procedures, that it possesses the necessary legal authority to:
• Prevent illicit discharges into its wastewater collection system (examples may include infiltration and inflow (I&I), storm water, chemical dumping, unauthorized debris and cut roots, etc.)
• Require that sewers and connections be properly designed and constructed • Limit the discharge of fats, oils, grease, and other debris that may cause blockages • Enforce any violation of its sewer ordinances

3.2 Legal Authority to Enforce SSMP Requirements
The RMSD is regulated by several agencies of the United States Government and the State of California, pursuant to the provisions of Federal and State Law. Federal and State Laws including, but not limited to the following, grant to the City the authority to regulate and/or prohibit, by the adoption of an ordinance and by issuance of control mechanisms, the discharge of any waste, directly or indirectly, to the Richmond Municipal Sewer District sewerage facilities.
578
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-2
1) Federal Water Pollution Control Act, commonly known as the Clean Water Act (33 U.S.C. Section 1251 et seq.);
2) California Porter Cologne Water Quality Act (California Water Code Section 13000 et seq.);
3) California Health & Safety Code Sections 25100 to 25250; 4) Resource Conservation and Recovery Act of 1976 (42 U.S.C. Section 6901 et seq.); and
5) California Government Code, Sections 54739-54740.

Through the RMC, the City possesses the necessary legal authority. The relevant RMC Chapters are included in Appendix B. The City’s legal authority is further described below.

3.2.1 Prevention of Illicit Discharges
The City’s Sewer Use Ordinance comprises RMC Article XII, Chapter 12.18, “Discharges to the Wastewater Treatment System” and RMC Article XII, Chapter 12.17, “Sanitary Sewer Connections.” RMC Chapter 12.18 establishes the City’s authority related to the prevention of illicit discharges to the sewer system. Also, Article XII, Chapter 12.22, “Stormwater Management and Discharge Control” addresses stormwater discharges to the sewer system as noted below.

RMC Section 12.18.020.1 “Prohibited Discharge Standards” A. General Prohibitions. No user shall introduce or cause to be introduced into the WPCP any pollutant or wastewater which causes pass through or interference. These general prohibitions apply to all users of the WPCP whether or not they are subject to Categorical Pretreatment Standards or any other Federal, State, or local Pretreatment Standards or Requirements.

B. Specific Prohibitions. No user shall introduce or cause to be introduced into the WPCP the following pollutants, substances, or wastewater:
(1) Pollutants which create a fire or explosive hazard in the WPCP, including, but not limited to, waste streams with a closed-cup flashpoint of less than 140 degrees F (60 degrees C) using the test methods specified in 40 CFR Part 261.21. Closed-cup flashpoint values may be found in the National Institute of Occupational Safety and Health (NIOSH) Pocket Guide to Chemical Hazards;
579
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-3
(2) Wastewater having a pH less than 6.0 or more than 10.0, or otherwise causing corrosive structural damage to the POTW or equipment;
(3) Solid or viscous substances, such as, but not limited to, grease, garbage with particles greater than one-half (0.5) inch in any dimension, animal guts or tissues, paunch manure, bones, hair, hides or fleshing, entrails, whole blood, feathers, ashes, cinders, sands, spent lime, stone or marble dust, metal, glass, straw, shavings, grass clippings, rags spent grains, spent hops, waste paper, wood, plastics, gas, tar, asphalt residues, residues from refining or processing of fuel or lubricating oil, mud, glass grindings, or polishing wastes, in amounts which will cause obstruction of the flow in the WPCP resulting in interference;
(4) Pollutants, including oxygen-demanding pollutants (BOD, etc.), released in a discharge at a flow rate and/or pollutant concentration which, either singly or by interaction with other pollutants, will cause interference with the WPCP; (5) Wastewater having a temperature greater than 140 degrees F (60 degrees C), or which will inhibit biological activity in the treatment plant resulting in interference, but in no case wastewater which causes the temperature at the introduction into the treatment plant to exceed 104 degrees F (40 degrees C); (6) Petroleum oil, non-biodegradable cutting oil, or products of mineral origin, in amounts that will cause interference or pass through;
(7) Pollutants which result in the presence of toxic gases, vapors, or fumes within the WPCP in a quantity that may cause acute worker health and safety problems; (8) Trucked or hauled pollutants, except at discharge points designated by the City Manager in accordance with Section 12.18.030.5 of this ordinance; (9) Noxious or malodorous liquids, gases, solids, or other wastewater which, either singly or by interaction with other wastes, are sufficient to create a public nuisance or a hazard to life, or to prevent entry into the sewers for maintenance or repair; (10) Pollutants that impart color, which cannot be removed by the treatment process, such as, but not limited to, dye wastes and vegetable tanning solutions. (11) Wastewater containing any radioactive wastes or isotopes except in compliance with applicable State or Federal regulations;
(12) Storm water, surface water, groundwater, artesian well water, roof runoff, subsurface drainage, swimming pool drainage, condensate, deionized water, non-contact cooling 580
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-4
water, and unpolluted wastewater, unless specifically authorized by the City Manager;
(13) Sludges, screenings, or other residue from the pretreatment of industrial wastes; (14) Medical wastes, except as specifically authorized by the City Manager in a wastewater discharge permit;
(15) Wastewater causing, alone or in conjunction with other sources, the treatment plant’s effluent to fail toxicity test;
(16) Detergents, surface-active agents, or other substances that might cause excessive foaming in the WPCP;
(17) Wastewater causing two readings on an explosion hazard meter at the point of discharge into the sanitary sewer system, or at any point in the WPCP, of more than five percent (5%) as hexane or any single reading over ten percent (10%) of the Lower Explosive Limit (LEL) of the meter. LEL values may be found in the NIOSH Pocket Guide to Chemical Hazards. Prohibited materials include, but are not limited to, gasoline, kerosene, naphtha, ethers, alcohols, ketones, aldehydes, peroxides, chlorates, perchlorates, bromates, carbides, hydrides, and sulfides.

Pollutants, substances, or wastewater prohibited by this Section shall not be processed or stored in such a manner that they could be discharged to the WPCP.

RMC 12.22.060 “Prohibited Discharges”.

A. The release of non-stormwater discharges to the City stormwater system is prohibited.

B. The discharge of stormwater from premises or an activity that causes or contributes to a violation of receiving water limitations in the City's NPDES permit is prohibited.

C. The following discharges are exempt from the prohibition set forth in subsection (a) above:
(1) Any discharge in compliance with a NPDES permit issued to the discharger; (2) Flows from riparian habitats and wetlands, diverted stream flows, springs, rising groundwater and uncontaminated groundwater infiltration.

D. The following discharges are exempt from the prohibitions set forth in subsection (a) above if the Regional Water Quality Control Board approves the exempted category under Section C. 11. of the City's NPDES permit: uncontaminated pumped groundwater, foundation drains, water from crawl space pumps, footing drains, air 581
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-5
conditioning condensate, irrigation water, landscape irrigation, lawn or garden watering, planned and unplanned discharges from potable water sources, water line and hydrant flushing, individual residential car washing, discharges or flows from emergency fire-fighting activities, and dechlorinated swimming pool discharges.

3.2.2 Proper Design and Construction of Sewers and Connections The following Sections of the RMC establish the requirement that sewers and connections must be properly designed and constructed.

RMC 12.16.010 “Sewer and Water Pipe Connections Required” All property owners owning or controlling property facing upon any of the streets or avenues of the City of Richmond shall lay or cause to be laid all necessary sewer and water pipe connections with the mains before said streets or avenues are bituminized, macadamized, or otherwise permanently improved.

RMC 12.16.020 “Connections Required Every Separate Lot” Every separate lot of twenty-five feet or more or any two lots adjoining shall be connected with the mains as provided in Section 12.16.010.

RMC 12.17.020 “Sewer Connections Required”
Property owners shall provide connections to the sanitary sewer system in accordance with Richmond Municipal Code Sections 12.16.010 and 12.16.020, as those Sections may be amended from time to time.

In addition, the City has developed standard design standards and specifications for sewer pipelines, appurtenances, connections, trenches, and other details. These standards are available on the City’s website and are discussed further in Element 5 of this SSMP.

3.2.3 Responsibility for Private Laterals
RMC Chapter 12.17 establishes the property owner’s responsibility for the sewer lateral, which is privately-owned up to and including the connection to the City’s sewer system. 582
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-6
RMC 12.17.040 “Standards for Sewer Laterals and Appurtenant Facilities” A. Every property owner shall perform all required maintenance and keep the lateral(s) and private sewer main(s), if any, connecting the premises on his or her property to the City's sanitary sewer system in good condition.

B. Every lateral shall meet the following minimum requirements:
(1) It shall be kept free from roots, grease deposits, and other solids which may impede the flow or obstruct the transmission of waste.
(2) All joints shall be tight and all pipes shall be sound and free from structural defects, cracks, breaks, openings, and missing portions to prevent ex-filtration by waste or infiltration by groundwater or stormwater.
(3) The grade of every lateral shall be uniform without sags or offsets. (4) It shall have a two-way cleanout located at or near the property line or at or near the sewer main easement. All cleanouts shall be securely capped at all times. (5) It shall be equipped with a backflow valve or overflow device. (6) In conjunction with a lateral serving a structure in which there are plumbing fixtures at an elevation too low to permit drainage by gravity from the fixtures to the sewer main, the property owner shall install and maintain a pump or other appropriate device or devices to lift the contents of the sewer lateral to the City's sanitary sewer system. Such devices shall be installed and maintained in accordance with the Uniform Building and Plumbing Codes and all applicable provisions of the Richmond Municipal Code, and shall be subject to testing, repair and replacement under the provisions of this Section governing sewer laterals.

3.2.4 Access for Maintenance, Inspection & Repairs
The Sewer Use Ordinance establishes the City’s authority to enter buildings and property for the purpose of protecting the public sewer system and enforcing provisions of the Municipal Code:

RMC 12.17.120 “Right of entry”
The City Manager, or his or her designee, may enter, inspect, collect wastewater samples, and test any buildings, structures, or premises to secure compliance or prevent a violation of any portion of this Section. Unless there is an emergency threatening the public health, safety or welfare, the City Manager shall provide at least ten (10) business days notice to the property 583
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-7
owner of intent to enter upon property. The City Manager may also request that a property owner provide all written records of lateral inspection, maintenance, repair and replacement at the time of inspection or within ten (10) or more business days after receipt of the request.

3.2.5 Limit Discharge of Fats, Oils & Grease and Debris The City’s authority to limit Fats, Oils and Grease (FOG) disposal to the sewer collection system is established in the Sections described above, and more specifically addressed in RMC Section

12.18.030.2, “Fats, Oils, and Grease.” This Section establishes the City’s FOG Program, which comprises the following:
• Requirements for fats, oils, and grease interceptors
• FOG Management Program permit which enables City staff right of entry to inspect the facility
• Parameters warranting inspection
• Responsibility for overflow
The City’s FOG management program is discussed further in Section 7.

3.2.6 Enforcement Measures
The Sewer Use Ordinance describes the various enforcement measures available to the City to enforce the terms of the RMC.

RMC 12.18.100 “Administrative Enforcement Remedies” et. seq RMC Section 12.18.100 describes the administrative enforcement remedies for non-compliance with the RMC, beginning with Section 12.18.100.1Notification of Violation, which states:

When the City Manager finds that a user has violated, or continues to violate, any provision of this Section, a wastewater discharge permit, or order issued hereunder, or any other Pretreatment Standard or Requirement, the City Manager may serve upon that user a written Notice of Violation. Within fourteen (14) days of the receipt of such notice, an explanation of the violation and a plan for the satisfactory correction and prevention thereof, to include specific required actions, shall be submitted by the user to the City Manager. Submission of such a plan in no way relieves the user of liability for any violations occurring before or after receipt of the Notice of Violation. Nothing in this section shall limit the authority of the City Manager to take any action, including emergency actions or any other enforcement actions, without first issuing a Notice of Violation.
584
Sewer System Management Plan

LEGAL AUTHORITY
Richmond Municipal Sewer District Page 3-8
RMC Section 12.18.110 describes judicial enforcement remedies and RMC Section 12.18.120 describes supplemental enforcement actions such as fines and penalties.

RMC Section 12.18.030.2 “Fats, Oils & Grease, ” establishes the City’s authority to enforce the FOG program.

RMC 12.18.030.2 “Fats, Oils & Grease ”, Section H
Pursuant of this Section and/or lawful direction from the City, any user who fails to maintain a grease interceptor or grease trap shall be subject to enforcement procedures set forth in Sections

12.18.100, 12.18.110, and/or 12.18.120 of this Section. Enforcement actions may be initiated if the user fails to maintain, pump, and/or institute a proper grease or flammable substance reduction program and/or providing appropriate employee training.

This Section also provides the City with the power to disconnect the individual user from the RMSD system, and to require the user to deposit the cost of disconnection and reconnection with the City before the service is reconnected.

3.3 Interagency Agreements and Satellite Systems
The RMSD does not collect wastewater from satellite systems, and therefore does not have any agreements with satellite sewer collection agencies.

Appendix B – Element 3 Documents
Appendix B includes the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix B may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the Appendix B documents.
• Richmond Municipal Code Applicable Sections from Article VI, Building Regulations and Article XII, Public Works
585
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-1
ELEMENT 4 - OPERATION AND MAINTENANCE PROGRAM
This section of the SSMP discusses the RMSD mapping, operations, preventive maintenance, inspection, training and outreach activities. This section fulfills the Operation and Maintenance Program SSMP requirement for the SWRCB (Element 4) and the Measures and Activities SSMP requirement for the RWQCB (Element 6).

The requirements and RMSD’s plan for the Operations and Maintenance element of the SSMP are summarized in each category below. Since requirements for this SSMP element contain multiple categories, this summary is organized by category, with SWRCB and RWQCB requirements described for each category as applicable.

The categories that are addressed in Element 4 include:
• Collection System Mapping
• Resources and Budget
• Prioritized Preventive Maintenance
• Scheduled Inspections, Condition Assessments and Replacement Planning • Critical Equipment and Spare Parts
• Training

4.1 SSMP Requirement for Collection System Maps

4.1.1 RWQCB Requirement
The RMSD must maintain current maps of its collection system facilities.

4.1.2 SWRCB Requirement
The RMSD must maintain an up-to-date map of the sanitary sewer system, showing all gravity line segments, manholes, pumping facilities, pressure pipes, valves and applicable stormwater conveyance facilities.

4.1.3 RMSD Collection System Mapping Description
Veolia and the RMSD currently use Geographic Information System (GIS) software to create and maintain maps of the sewer collection system facilities. The GIS geodatabase includes pipe, 586
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-2
manhole, and pump station asset information, and records pipe length, direction of flow, manhole numbers, most pipe diameters, rim and invert elevations, and some materials.

The RMSD sewer map grid system, which accompanies the RMSD sewer map book, is included in Appendix C. The map books contain individual map sheets printed at 1”=300’ scale. Maps are updated regularly within GIS by Veolia, and updates are transferred approximately monthly to the City’s GIS department.

The City and Veolia are completing a project to document stormwater facilities in GIS. The known facilities are included as a separate layer in the RMSD maps described above.

4.2 SSMP Requirement for Resources and Budget

4.2.1 RWQCB Requirement
The RMSD must demonstrate that adequate resources are allocated for the operation, maintenance and repair of the RMSD collection system.

4.2.2 SWRCB Requirement
The Statewide WDR includes no requirement for resources and budget.

4.2.3 RMSD Resources and Budget for Sewer System Management The City prepares an annual budget and CIP. The current fiscal year adopted budget for the Wastewater Enterprise is included in Appendix C. Veolia Water is required by contract to fulfill all contractual requirements for operations and maintenance, including but not limited to SSO compliance related to sewer system maintenance, using this budget.

The capital improvement budget is earmarked for sewer collection system improvements to reduce inflow and infiltration and address capacity needs. Capital improvement needs for the sewer collection system were identified and prioritized through an updated sewer collection system master plan that is discussed in Element 8.

4.3 SSMP Requirement for Prioritized Preventative Maintenance

4.3.1 RWQCB Requirement
The SSMP must demonstrate that prioritized maintenance activities are performed by the RMSD. 587
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-3

4.3.2 SWRCB Requirement
The SSMP must describe routine preventive operation and maintenance activities by staff and contractors, including a system for scheduling regular maintenance and cleaning of the sanitary sewer system with more frequent cleaning and maintenance targeted at known problem areas.

The Preventive Maintenance (PM) program should have a system to document scheduled and conducted activities, such as work orders.

4.3.3 Prioritized Preventive Maintenance Activities
The City’s contract with Veolia requires cleaning all parts of the sewer collection system on a four-year cycle. Veolia must also develop and maintain a Hot Spots list for areas requiring more frequent maintenance. Pipeline maintenance is planned according this schedule, and prioritized through field experience. The City’s contract with Veolia requires the development of a System Cleaning Plan. This plan must be updated every three years in order to incorporate new information. Veolia maintains internal documentation on maintenance activities and prioritization plans, and is developing a formal summary document for presentation to the City in 2014.

Veolia uses hydro-cleaning and other methods to clean the sanitary sewer system, and herbicide chemical treatment application (via contract) and cutting to manage root intrusions. Pipes with known SSOs are placed on a one-year hot spot list. If recurring SSOs occur, this segment is elevated to a more frequent cleaning schedule (1-, 3-, 6- or 9-month schedule). Appendix C includes a map showing Veolia’s cleaning schedule and a second map showing the segments on the current Hot Spot list.

Veolia conducts emergency repairs to the sewer system when failure appears imminent, in situations that may involve public and employee health and/or safety issues, and in situations that may involve property or liability damages. These repairs are discussed with the City in advance of completing the work. All other repairs must be prioritized by Veolia and pre-authorized by the City. Veolia is also required to inspect manholes and include the inspection results as an integral part of the system documentation.

Veolia currently inspects manholes as part of the CCTV inspection process. Photo and video documentation are taken from the street level into the manhole, and from the pipeline up and out of the manhole. Structural defects are noted during the visual inspection. Veolia documents manhole inspections using an electronic form on their field tablet. This form is included in Appendix C.

To supplement pipeline assessment, repair and replacement, Veolia’s maintenance program includes hydrogen sulfide monitoring and control, easement maintenance at lift stations, and 588
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-4
electronic monitoring of lift stations through the use of the plant SCADA. Weekly lift station checks are conducted to determine the physical condition of equipment. If authorized, Veolia also provides temporary repairs to landscaping, driveways, and final roads including grading, seeding, and sod replacement after pipe repairs.

Gravity pipeline maintenance assets and activities are included in Veolia’s computerized maintenance management system (CMMS), which uses Innovyze® InfoNet™ CMMS software.

Pump station data is maintained in a separate CMMS system named Oracle Work and Asset Management (OWAM). InfoNet™ and OWAM generate work orders for sewer system and pump station preventive maintenance, respectively, and store the resulting findings and recommendations.

4.4 SSMP Requirements for Inspections, Condition Assessment and Rehabilitation

4.4.1 RWQCB Requirement
The RMSD must identify and prioritize structural deficiencies and implement a program of prioritized short-term and long-term actions to address them.

4.4.2 SWRCB Requirement
The RMSD must develop a rehabilitation and replacement plan to identify and prioritize system deficiencies and implement short-term and long-term rehabilitation actions to address each deficiency. The program should include regular visual and TV inspections of manholes and sewer pipes, and a system for ranking the condition of sewer pipes and scheduling rehabilitation.

Rehabilitation and replacement should focus on sewer pipes that are at risk of collapse or prone to more frequent blockages due to pipe defects. Finally, the rehabilitation and replacement plan should include a capital improvement plan (CIP) that addresses proper management and protection of the infrastructure assets. The plan shall include a time schedule for implementing the short and long-term plans plus a schedule for developing the funds needed for the capital improvement plan.

4.4.3 CCTV Inspection Program
Veolia conducts all CCTV inspections for the RMSD system. CCTV data is collected in digital format with fully equipped CCTV vehicles, using pan-and-tilt cameras. Veolia’s inspection program uses the National Association of Sewer Service Companies (NASSCO) Pipeline Assessment and Certification Program (PACP)) defect rating systems. In addition to evaluating each defect, the program assigns a PACP “Quick Rating” for each pipe segment. The quick rating indicates the number of occurrences for the two highest severity grades for each pipe segment for either maintenance or structural defects.
589
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-5
The contract with Veolia requires the completion of CCTV inspection every ten years, and the development of a plan to identify areas requiring CCTV inspection on a more frequent basis. The inspection results must be fully documented so that they support the development of a prioritized CIP. Veolia must then work with the City to prepare annual budgets for repairing the Collection System.

CCTV inspection activities are prioritized through field experience and recorded in InfoNet.

Veolia is currently developing a formal summary document for presentation to the City in 2014.

Appendix C includes a map showing Veolia’s 10-year CCTV inspection schedule. This map also delineates segments to have been inspected in 2013.

4.5 SSMP Requirement for Training

4.5.1 RWQCB Requirement
The RMSD must provide training on a regular basis for its collection system operations, maintenance, and monitoring staff.

4.5.2 SWRCB Requirement
The RMSD must provide training on a regular basis for staff in sanitary sewer system operations, maintenance, and require contractors to be appropriately trained.

4.5.3 Training of City Personnel and Contractors
Veolia provides sewer maintenance and customer service training to its employees, through either classroom or on-the-job exercises. Veolia also provides monthly safety training based on an established schedule.

The City and Veolia has recently (2017) expanded this training to include the contents of the SSMP and the Overflow Emergency Response Plan. Recipients also include City employees that are responsible for implementing the various elements of this SSMP.

Records are kept of all training that is provided by Veolia in support of the SSMP. The records include the date, time, place, content, name of trainer(s) and names of attendees. 590
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-6

4.6 SSMP Requirement for Contingency Equipment

4.6.1 RWQCB Requirement
The RMSD must demonstrate that contingency equipment is provided to handle emergencies, and that spare parts are available to minimize equipment/facility downtime during emergencies.

4.6.2 SWRCB Requirement
The RMSD must provide equipment and replacement part inventories, including identification of critical replacement parts.

4.7 Contingency Equipment and Replacement Inventories
The current collection systems equipment inventory, as maintained by Veolia, is listed below. • Three (3) Vacuum and Jetter Trucks; two of these trucks are provided by the City as part of the contract between the City and Veolia.
• One (1) Rodder Truck
• Three (3) Video Trucks
• Two (2) Traffic Utility Trucks
• One (1) Small Gas Generator
• One (1) 6” Portable Bypass Pump
• One (1) 3” Honda Portable Pump

4.8 Critical Replacement Parts
The inventory of critical replacement parts is stored in a CMMS named Oracle Work and Asset Management (OWAM) and is published as a component of Appendix C.

Appendix C – Element 4 Documents
Appendix C includes the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix C may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the Appendix C documents.
591
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-7
• Richmond Municipal Sewer District Sewer Map Grid
• Current Fiscal Year Sewer Related Budget
• Maps Showing Cleaning Schedule, Hot Spot Preventive Maintenance Program, and CCTV Inspection Plan
• Manhole Inspection Form

592
Sewer System Management Plan

OPERATION AND MAINTENANCE PROGRAM
Richmond Municipal Sewer District Page 4-8
This page left intentionally blank
593
Sewer System Management Plan

DESIGN AND PERFORMANCE PROVISIONS
Richmond Municipal Sewer District Page 5-1
ELEMENT 5 - DESIGN AND PERFORMANCE PROVISIONS
This section of the SSMP discusses the City’s design and construction standards.

5.1 RWQCB and SWRCB SSMP Requirements

5.1.1 RWQCB Requirement
RMSD shall demonstrate that minimum design and construction standards and specifications are in place for the installation of new sewer systems and for the rehabilitation and repair of existing sewer systems.

5.1.2 SWRCB Requirement
RMSD must have design and construction standards and specifications for the installation of new sewer systems, pump stations and other appurtenances; and for the rehabilitation and repair of existing sewer systems.

RMSD must have procedures and standards for inspecting and testing the installation of new sewers, pumps, and other appurtenances and for rehabilitation and repair projects.

5.2 Design and Construction Standards for Installation, Rehabilitation and Repair The City of Richmond standards for the design and construction for the installation of sewer system components and for rehabilitation and repair of existing are specified in part in the Richmond Municipal Code, Article VI Building Regulations Chapters 6.02, 6.04, 6.20 and 6.28 reference the appropriate electrical, mechanical, building and other adopted codes and standards that apply to City construction. RMC Chapters 12.24, 12.28, 12.30, 12.32, 12.36, 12.44 and

12.48 describe standards for public works construction including roads, sidewalks, utilities, pipes, earthwork and other related construction. Legal authority for enforcing the design and construction standards is provided by City Chapter 1.04 Adoption of Code – Construction of Provisions – Enforcement.

In addition to the RMC requirements, the City Engineering Services Division is developing standalone design and construction standards for pipeline projects. The design criteria includes pipe materials, minimum sizes, minimum cover, strength, minimum slope, trench and backfill requirements, structure standards and other factors
The Municipal Code Sections are included as part of Element 3, in Appendix B. The City’s design and construction standards are included in Appendix D. 594
Sewer System Management Plan

DESIGN AND PERFORMANCE PROVISIONS
Richmond Municipal Sewer District Page 5-2

5.3 Procedures and Standards for Inspection, Testing, Rehabilitation and Repair City of Richmond design standards will establish the standards that the City follows when inspecting and testing new or rehabilitated sewers, pump stations, and other appurtenances. For small maintenance projects, inspections are provided by Veolia staff. For larger projects, inspection services may be provided through a joint effort from the City’s engineering consultant and Veolia or by other persons(s) appointed by the City. Testing is normally conducted by the contractor, with the inspector observing to verify that all requirements are met.

Appendix D – Element 5 Documents
Appendix D includes the City of Richmond Design and Construction Standards. The information in this document will change from time to time, and the document in Appendix D may have been superseded. If the information in this section has been updated, it will be noted in the beginning pages of the SSMP under “Changes to SSMP”. 595
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-1
ELEMENT 6 - OVERFLOW EMERGENCY RESPONSE PLAN
This section of the SSMP provides a summary of the Overflow Emergency Response Plan that was developed and is maintained by Veolia, and fulfills the Overflow Emergency Response Plan requirements for both the RWQCB and the SWRCB. The OERP that is included in Appendix E is also maintained by Veolia as a stand-alone document as required by the RWQCB. This document will be updated as necessary.

6.1 RWQCB and SWRCB SSMP Requirement
The summarized requirements for the Overflow Emergency Response Plan element of the SSMP are as follows:

6.1.1 RWQCB Requirement:

The RMSD must develop an overflow emergency response plan that provides procedures for SSO notification, response, reporting, and impact mitigation. The response plan should be developed as a stand-alone document and summarized in the SSMP.

6.1.2 SWRCB Requirement:

The RMSD shall develop and implement an overflow emergency response plan that identifies measures to protect public health and the environment. At a minimum, this plan must include the following:
• Proper notification procedures so that the primary responders and regulatory agencies are informed of all SSOs in a timely manner
• A program to ensure appropriate response to all overflows • Procedures to ensure prompt notification to appropriate regulatory agencies and other potentially affected entities (e.g. health agencies, regional water boards, water suppliers, etc.) of all SSOs that potentially affect public health or reach the waters of the State in accordance with the Statewide Monitoring and Reporting Program (MRP). All SSOs shall be reported in accordance with this MRP, the California Water Code, other State Law, and other applicable Regional Water Board WDR or NPDES permit requirements.

The SSMP should identify the officials who will receive immediate notification • Procedures to ensure that appropriate staff and contractor personnel are aware of and follow the emergency response plan and are appropriately trained • Procedures to address emergency operations, such as traffic and crowd control and other necessary response activities
596
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-2
• A program to ensure that all reasonable steps are taken to contain and prevent discharge of untreated and partially treated wastewater to waters of the United States and minimize or correct any adverse impact on the environment resulting from the SSOs, including such accelerated or additional monitoring as may be necessary to determine the nature and impact of the discharge.

6.2 OERP Goals
The purpose of the Overflow Emergency Response Plan (OERP) is to support an orderly and effective response to Sanitary Sewer Overflows (SSOs). The OERP provides guidelines for City staff to follow in responding to, cleaning up, and reporting SSOs that may occur within the City’s service area.

The City’s goals with respect to responding to SSOs are:
• Respond quickly to minimize the volume of the SSO
• Eliminate the cause of the SSO
• Contain the spilled wastewater to the extent feasible • Minimize public contact with the spilled wastewater
• Mitigate the impact of the SSO
• Meet regulatory reporting requirements

6.3 SSO Categories
The responsibilities of the SSO Response Team depend on the volume and location of an incident. Three categories of SSOs are defined by the SWRCB:
• Category 1 SSO: Discharges of untreated or partially treated wastewater of any volume resulting from the RMSD’s sanitary sewer system failure or flow condition that:
− Reach surface water and/or reach a drainage channel tributary to a surface water; or − Reach a municipal separate storm sewer system and are not fully captured and returned to the sanitary sewer system or not otherwise captured and disposed of properly. Any volume of wastewater not recovered from the municipal separate storm sewer system is considered to have reached surface water unless the storm drain system discharges to a dedicated storm water or ground water infiltration basin (e.g., infiltration pit, percolation pond).
• Category 2 SSO: Discharges of untreated or partially treated wastewater of 1,000 gallons or greater resulting from the RMSD’s sanitary sewer system failure or flow condition that do not reach surface water, a drainage channel, or a municipal separate storm sewer system unless the entire SSO discharged to the storm drain system is fully recovered and disposed of properly.
• Category 3 SSO: All other discharges of untreated or partially treated wastewater resulting from the RMSD’s sanitary sewer system failure or flow condition. 597
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-3

6.4 SSO Notification Procedures
The City is most often notified of an SSO by Veolia staff. However, on occasion, SSOs are called into a particular City department in which case Veolia staff is contacted to execute a response. Veolia learns of the SSO through its crews, contractors, or a member of the public.

When a member of the public notices an overflow or blockage, they report this occurrence to the Veolia SSO hotline. The hotline is answered by Veolia staff at the WWTP (601 Canal Boulevard, Richmond, CA). The Veolia number for reporting SSOs is (510) 412-2001.

The Veolia hotline is included in the telephone book and on the City’s website, which can be accessed through the url: http://www.ci.richmond.ca.us under the “Wastewater” tab.

Figure 6-1 on the following page provides a notification and response flow chart procedure for an SSO occurrence. This is the same chart that is provided in Section 2, Organization.

The Veolia Field Crew, which includes the First Responder, arrives at the spill site within 30 minutes to one hour to perform an initial evaluation of the impact of the overflow. The First Responder selects an approach that will result in the least environmental damage – deciding between clearing the blockage first or initiating spill containment measures. The First Responder reports the severity of the overflow to both the Veolia Collection System Manager, Field Supervisor and Veolia Underground Asset Management Group.

The Field Crew takes and sends pictures to the Manager, Field Supervisor and Underground Asset Management Group. The Field Crew is responsible for calling for back-up support if a large volume of spill has the potential to reach the storm drain system and/or the San Francisco Bay.

The Veolia Manager or Field Supervisor records the overflow start time, and provides update as soon as flow is restored and the clean-up procedure begins. Immediate notification is a priority if the spill appears to be over 1,000 gallons, in a sensitive area, may imminently and substantially endanger human health, results in fish kills, if there is doubt regarding the extent, impact, or how to proceed, or if additional help is needed for line cleaning or repair, containment, recovery, lab analysis, and/or site cleanup.

Veolia staff makes all reports to the regulatory agencies.

598
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-4
Figure 6-1. SSO Notification Process

6.4.1 Normal Working Hours
Normal business hours are Monday through Friday from 7:00 AM to 4:00 PM. Service calls received during normal business hours are taken immediately by the Veolia Collection System Planner/Scheduler who fills out the service call report form and then dispatches the call to the Veolia Field Crew who will respond within 30 minutes to one hour of an SSO event. 599
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-5
Upon arrival, the crew makes assessment, mitigates exposure and notifies the field supervisor of all facts related to the SSO. The Field Crew remains in close communication with the Veolia Collection System Manager and/or Field Supervisor

6.4.2 After Normal Working Hours
After normal business hours, service calls are taken by the Veolia Water Answering Service Center which relays the information to the Veolia Field Crew on-call representative, who responds within a one hour time frame. The Veolia operator completes a standardized form available through the Infonet® mobile tablet that records start time of the incident and other information related to the SSO.

All other communications procedures are similar to that of an SSO during normal working hours.

6.4.3 Notification from Pump Station SCADA Alarms
Any overflows associated with a lift station are detected and reported through the SCADA remove monitoring and Mission alarm system to the Veolia Field on call staff. Pump or equipment failure and high wet well levels produce alarms which may require a response depending on the circumstances. The on-call person would initiate a support response by the field crew as necessary. A lift station overflow may also be relayed by the public to Veolia and addressed as described above.

In a non-emergency response situation, a Work Order to address the issue is provided through the plant CMMS program.

6.5 Staff and Contractor Training
All Veolia personnel and contractor employees who may have a role in responding to, reporting and/or mitigating a sewer system overflow receive training on the contents of the OERP. All new employees receive training before they are placed in a position where they may have to respond.

Current employees receive annual refresher training on this plan and the procedures to be followed.

Records are kept of all training that is provided in support of this plan. The records for all scheduled training courses and for each overflow emergency response training event include date, time, place, content, name of trainer(s) and names of attendees.

6.6 Response Program
Names and contact information for the Veolia SSO responders are as listed below, or as otherwise updated in the OERP:
600
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-6
• Veolia Hotline: (510) 412-2001
• Veolia Project Manager - Aaron Winer Cell: (510) 385-6482 • Veolia Underground Asset Management Group - (925) 681-2304 • Veolia Collection System Manager – Tim O’Connor Cell: (510) 426-0008 • Veolia Sewer Crew Supervisor - Wayne Madison Cell: (510) 542-3247 • Veolia Field Crew Cell Numbers:
o Armstrong, Ronnie (510) 812-2776
o Roos, Jason (510) 812-1173
o Wallis, David (510) 447-0220
o Lewis, Kenny (510) 932-1242
o Madison, Wayne (510)542-3247
o Hill, Arlee (510) 829-2108
o Hendricks, Mitchell (510) 660-7942
o Mendoza, Rafael (510) 334-4924
• In Case of Emergency: 911
• City Police Dispatch: (510) 233-1214
• Office of Emergency Services: (800) 852-7550
• City Manager: (510) 620-6512
• City Water Resource Recovery Director Cell: (510) 932-5014 • City Source Control Superintendent Cell: (510) 290-9149 • City Senior Administrative Analyst Cell: (510) 685-0820 • Contractors:
o BayHawk, Inc.: (510) 776-5886
o Ghilloti Brothers: (415) 454-7011
601
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-7
o W.R. Forde : (510) 215-9338
o TMB, LLC: (707) 252-5480
o Sierra Pacific Loss Management (Bruce Burnett – Interior Cleaning): (707) 479-1375 o Rain for Rent (bypass pumping): (925) 679-2803
o DW Pumps: (510) 633-2040
• Regulatory Agencies:
o California Regional Water Quality Control Board: (510) 622-2369 o California Department of Fish and Games - Bay Delta Region : (707) 944-5500 o East Bay Regional Park District: (510) 633-0460
o Contra Costa County Health Services: (925) 692-2500
o California Office of Emergency Services : (916) 845-8506 / (800) 852-7550 • U.S. Coast Guard : (510) 437-3073

6.6.1 First Responder Priorities
The First Responder’s priorities are as follows:
• To follow safe work practices, including those related to traffic control, confined space, and employee and public safety.
• To respond promptly with the appropriate equipment.
• To evaluate the cause of spill and determine responsibility. • To restore the flow as soon as possible.
• To contain the spill whenever feasible.
• To minimize public access to and/or contact with the spilled sewage.

6.6.2 Initial Response
The First Responder must report to the SSO location within 30 minutes to one hour of the initial SSO report during business hours, and within one hour during non-business hours. The objective of the response is to minimize and/or eliminate the overflow. The appropriate response measure 602
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-8
will vary based on the circumstances and nature of the SSO and the information provided by the caller. Actions related to external and internal SSOs are summarized below.

Veolia uses a computerized form to document the contact and response for each SSO that occurs.

Separate forms are used for SSO response and customer issues. These forms are included in Appendix E.

Veolia has a variety of equipment available for clearing blockages and impact mitigation and cleanup activities, including the following:
• Three (3) Combination Sewer Cleaning Trucks (vacuum and jetter/hydroflush); two of these trucks are provided by the City as part of the contract between the City and Veolia. • One (1) Rodder Truck
• Two (2) CCTV Trucks
• Two (2) Traffic Utility Trucks
• One (1) 3” Honda Portable Pump
• One (1) 6” Portable by-pass pump, trailer mounted

6.6.3 External SSO Response
Upon arrival at the site, the First Responder should complete the following:
• Note notification time, crew arrival time, SSO start time and SSO end time and cleaning completion time; Crew completes the report through the use of Infonet® mobile tablet. • Verify the existence of the SSO
• Field verify the address and nearest cross street, and confirm that the SSO is part of the RMSD sewer/conveyance system
• Conduct visual monitoring to determine immediate actions, starting with documentation of SSO volume using the methods included in the OERP
• Identify and clearly assess the affected area and extent of spill, including possible impacts on surface water. Where it is safe and practical, visually inspect surface water in the vicinity of the SSO and record observations on the Infonet mobile tablet. Signs of receiving water impacts include clear signs of sewage (solids, grease, and paper), abnormal color, fish kills, etc.
603
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-9
• Estimate spill volume using SSO reporting guidelines in Appendix E. • Contain, mitigate, and minimize impacts from the SSO. If the SSO is the result of a blockage, and the blockage cannot be cleared expeditiously via hydro-cleaning from the downstream manhole, then clearing and vacuuming the blockage from the pipe, containment and/or bypass pumping must be initiated.
• If several efforts to clear blockage have failed, the Manager or Field Supervisor must be immediately informed, who will in turn call up other employees and local contractors to initiate emergency repair to restore flow and also provide assistance to initiate spill containment or bypass pumping.
• In the event the SSO should exceed 50,000, text and e-mail the City Source Control Superintendent, so the City can activate their Water Quality Monitoring Plan.Comply with all safety precautions (traffic, confined space, etc.). • Contact caller. Identify SSO cause, including conducting CCTV inspection as appropriate.
• Document all activities through photos and written documentation.

6.6.4 Internal SSO Response (Residential Sewage Backup) Upon arrival at the location of a spill into a house or a building, the First Responder should evaluate and determine if the spill was caused by a blockage in the lateral or in the RMSDowned sewer main. If a blockage is found in a property owner’s lateral, it should be clearly communicated to the homeowner that response and repair of private laterals is not the City’s responsibility. Additionally, Veolia’s Collection System Manager, Collection System Supervisor and the Veolia Richmond Project Manager are notified immediately if a sewage back up impacts a home or business owner within the dwelling. The homeowner is responsible for clearing any blockage or addressing a failure in the home's plumbing system or private lateral and for any resulting flood damage to the structure.

As a courtesy, Veolia crews will assist the homeowner in coordinating for the repair. However, Veolia and/or the City are not authorized to repair the private lateral at the City’s cost.

If a backup in the main line is found to have caused the SSO in a house or building, the First Responder should take steps to address the issue as described above. An independent contractor hired by the City follows the steps below:
• Keep all family members and pets away from the affected area. 604
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-10
• Place towels, rags, blankets, etc. between areas that have been affected and areas that have not been affected, and move any uncontaminated property away from the overflow area.
• Move any uncontaminated property away from the overflow area. Do not remove any contaminated items.
• Turn off the HVAC system.

The First Responder should follow the following steps to assist the homeowner:
• Gather information and fill out the electronic form on the Infonet® mobile tablets. A hard copy is included in the OERP
• Call a restoration company as described below (contact numbers are included in the emergency response list), and wait for the restoration firm to arrive • Forward incident reports and related documents to Collection System Supervisor

6.6.5 Pump Station SSO Response
The First Responder to a potential pump station or force main failure should determine whether flow can be restored within a reasonable time. If it appears that flow cannot be restored within a reasonable time or if the conveyance system facility requires construction and/or repairs, then the First Responder should employ a plan covering containment, bypass pumping and contractor assistance. Veolia uses DW Pumps for bypass pumping services. The pump stations in the service area will be evaluated in 2017. A formalized emergency contingency plan for each pump station will be developed. The individual plans will become an integral part of the OERP and incorporated into a master pump station emergency contingency plan by July 2018.

In addition, response activities discussed above should be implemented where applicable.

6.6.6 Recovery and Cleanup
The recovery and clean up phase must begin when the flow has been restored and the spilled sewage has been contained to the extent possible. Spilled sewage shall be vacuumed or pumped and discharged to the extent possible back into the sanitary sewer system. 605
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-11
Estimate and Recover the Volume of Spilled Sewage
Use the methods outlined in the OERP in Appendix E to estimate the volume of the spilled sewage. Wherever possible, document the estimate using photos of the SSO site before and during the recovery operation.

Spilled sewage shall be vacuumed or pumped and discharged to the extent possible back into the sanitary sewer system.

Clean Up and Disinfection
Clean up and disinfection procedures must be implemented to reduce the potential for human health issues and adverse environmental impacts that are associated with an SSO event. The procedures described are for dry weather conditions and should be modified as required for wet weather conditions. Clean up should proceed quickly in order to minimize negative impact. Any water that is used in the cleanup process should be de-chlorinated prior to use.

Where cleanup is beyond the capabilities of Veolia staff, Veolia contacts a cleanup contractor to complete the work. Phone numbers are provided in the emergency response list.

Spills inside houses or buildings should be cleaned by a professional cleaning company as discussed above. Contact information for professional cleaning companies can be found in the “Water Damage Restoration” section of the Yellow Pages and is also provided in the OERP.

Claims by homeowners should be forwarded to the City Risk Manager.

In the event of an SSO occurrence during night time hours, the incident must be re-inspected as soon as possible the following day. The site shall be inspected for any signs of sewer related debris/material that may warrant additional cleanup activities.

Guidelines for Cleanup
On hard surface areas, collect all signs of sewage solids and sewage-related material either by hand or with the use of rakes and brooms. Take reasonable steps to contain and vacuum up the wastewater.. Repeat the process if additional cleaning is required.

On landscaped or unpaved areas, collect all signs of sewage solids and sewage-related material either by hand or with the use of rakes and brooms. Allow the area to dry. Repeat the process if additional cleaning is required.

If the SSO has reached the storm drain system, the combination sewer cleaning truck should be used to vacuum/pump out the catch basin and any other portion of the storm drain that may contain sewage. In the event that an overflow occurs at night, the location should be re-inspected 606
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-12
as soon as possible the following day. The operator should look for any signs of sewage solids and sewage-related material that may warrant additional cleanup activities.

6.7 Impact to Waters of the United States
If an SSO is confirmed to have entered waters of the United States1, the Sewer System Coordinator is immediately notified. The response team then proceeds with the following additional activities:
• Determine the extent of the SSO by investigating downstream until there is no evidence of sewage or debris along the creek or water body
• If the SSO is 50,000 gallons or greater, e-mail and text the Source Control Superintendent so the City may activate their Water Quality Monitoring Plan (see Appendix D). • Immediately post contaminated water sign(s) and protect the waterbody from public access on all sides.
• Photograph sign placement and evidence of the overflow in and around the waterbody to the farthest point reached by the sewage
• If feasible, block the waterbody downstream of the affected area in a location that is safe to enter and is accessible to set up a pump or utilize other sewer cleaning equipment • To the extent feasible, recover and return contaminated water to the collection system

6.7.1 Water Quality Sampling
Water quality sampling and testing is required only when the spilled sewage enters a water body is greater than or equal to 50,000 gallons. The purpose of testing is to determine the extent and impact of the SSO. The City Source Control Superintendent will activate their Water Quality Monitoring Plan for any spills that are greater than or equal to 50,000 gallons (see Appendix D).

6.7.2 Water Quality Monitoring Plan
A Water Quality Monitoring Plan must be implemented immediately upon discovery of any Category 1 SSO of 50,000 gallons or more in order to assess impacts from SSOs to surface waters. Water quality testing must be completed within 48 hours of the City becoming aware of the SSO.

The City’s SSO Water Quality Monitoring Program is included in Appendix D, and includes the following:

1 40 CFR 230.3(s) defines the term “waters of the United States.” This term includes all lakes, rivers, streams (including intermittent streams), mudflats, sandflats, wetlands, sloughs, or natural ponds, or waters that could be used for recreational or other purposes.
607
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-13
• Protocols for water quality monitoring
• Account for spill travel time in the surface water and scenarios where monitoring may not be possible (e.g. safety, access restrictions, etc.)
• Requirement for water quality analyses for ammonia and bacterial indicators to be performed by an accredited or certified laboratory
• Requirement for monitoring instruments and devices used to implement the SSO Water Quality Monitoring Program to be properly maintained and calibrated, including any records to document maintenance and calibration, as necessary, to ensure their continued accuracy

6.7.3 SSO Technical Report
If 50,000 gallons or greater from an SSO reaches surface waters, an SSO Technical Report must be prepared and submitted to the CIWQS online SSO database and certified within 45 calendar days of the SSO end date. The SSO Technical Report must include, at a minimum, the following:

1. Causes and Circumstances of the SSOs

2. Complete and detailed explanation of how and when the SSO was discovered

3. Diagram showing the SSO failure point, appearance point(s), and final destination(s)

4. Detailed description of the causes(s) of the SSO

5. Copies of the original field crew records used to document the SSO

6. Historical maintenance records for the failure location

7. Response to SSO:

8. Chronological narrative description of all actions taken to terminate the SSO

9. Explanation of how the OERP was implemented to respond to and mitigate the SSO

10. Final corrective action(s) completed and/or planned to be completed, including a schedule or actions not yet completed

11. Water Quality Monitoring:

12. Description of all water quality sampling activities conducted including analytical results and evaluation of the results

13. Detailed location map illustrating all water quality sampling points The Water Resource Recovery Director, in conjunction with Veolia, are responsible for the development and certification of the SSO Technical Report.

6.8 Containment or Bypass
The first responder should attempt to contain as much of the spilled sewage as possible using the following steps:
• Determine the immediate destination of the overflowing sewage. • Plug storm drain manholes, catch basins, inlets and culverts using available equipment and materials, including sandbags, air plugs and plastic mats to contain the spill, where 608
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-14
feasible. If spilled sewage has made contact with the storm drainage system, attempt to contain the spilled sewage by plugging downstream storm drainage facilities. • Contain/direct the spilled sewage using dike/dam or sandbags. • Pump around the blockage or pipe failure, or vacuum up flow from upstream of the blockage and dispose of downstream of the blockage to prevent further overflow. • If an SSO reaches a water body, follow the requirements below for posting and SSO notification signage. Also conduct water quality sampling if the spill is greater than or equal to 50,000 gallons.

6.9 SSO Notification Signage
Veolia supplies notification signage, which is posted by Veolia staff and the Source Control Superintendent and/or other City staff. Barriers are installed where required to prevent the public from having contact with the sewage. Signs are posted along with barricades with yellow flashing lights to keep vehicles and pedestrians away from contact with spilled sewage. “Closed” signs should be posted at the outfall of streams and a minimum of 100 feet upstream and 100 feet downstream of the discharge. If there is a large volume of sewage, more signs must be posted downstream.

Signs must remain in place until the risk of contamination has subsided to acceptable levels.

Warning signs should be checked every day in order to ensure that they are still in place.

A sample warning sign is included in the OERP.

6.10 Traffic and Crowd Control
Traffic and crowd control measures vary based on the size and potential impact of the overflow event. When appropriate, local police, fire department, and City contacts must be notified to aide in addressing traffic and crowd control issues.

General steps in implementing traffic and crowd control include the following:
• Contact impacted agencies, local law enforcement and fire/sheriff as needed • Set up barriers and delineation directing human and vehicular traffic around spill area, including closing any entrances or exits from adjacent facilities • Establish signage including signs protecting public health and safety • Use staff personnel to control traffic and pedestrians 609
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-15

6.11 SSO Failure Analysis
For each SSO event greater than 250 gallons, all participants involved in the response – from the person who received the call to the last person to leave the site – should meet, as soon as feasible, after the event to review and evaluate the incident and the City response procedures.

The objective of the Post-SSO Debrief is to determine actions necessary, if any, to reduce the recurrence and better mitigate the effects of SSOs.

It is the responsibility of the Veolia Collection System Manager to investigate an SSO and to ensure that the procedures in the OERP are followed or modified as a result of the incident failure analysis. The failure analysis is intended to determine if additional maintenance, repair/replacement or other follow-up actions or response procedures changes are needed to reduce or eliminate the likelihood of future SSOs. The procedures for investigating an SSO are as follows:
• Reviewing and completing the Sewer Overflow Report
• Reviewing the incident timeline and other documentation regarding the incident • Review actions by all persons involved in the response, including the initial recipient of the complaint
• Reviewing communications with the all reporting parties, and witnesses • Review volume estimate, volume recovered estimate, volume estimation assumptions and • associated drawings
• Reviewing available photographs
• Interviewing staff that responded to the spill
• Reviewing past maintenance records of all affected manholes and pipe segments • Reviewing past CCTV records
• Conducting a CCTV inspection to determine the condition of the line segment immediately following the SSO and reviewing the video and logs • Reviewing any FOG related information or results
• Identify any changes or additions needed to the OERP and SSMP following the event The product of the failure analysis investigation should be the determination of the root cause and identification of the corrective actions. The Collection System Failure Analysis Form in Appendix E should be used to document the investigation.

6.12 SSO Documentation and Reporting
In accordance with the WDR, the City maintains records for each sanitary sewer overflow.

Records include:
• Documentation of response steps and/or remedial actions • Photographic evidence to document the extent of the SSO, field crew response operations • Site conditions after field crew SSO response operations have been completed • The date, time, location, and direction of photographs taken will be documented 610
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-16
• Documentation of how any estimations of the volume of discharged and/or recovered overflow were calculated
The records are maintained at the Wastewater Treatment Plant office and are also entered into Veolia’s CMMS system.

Veolia also maintains records of complaints received, even if the complaint does not relate to a City SSO.

6.12.1 Regulatory Reporting
Table 6-1 summarizes the regulatory reporting requirements that are also described in the paragraphs following the table.

Multiple Appearance Points – Single SSO
For reporting purposes, if one SSO event of whatever category results in multiple appearance points in a sewer system, a single SSO report is required in CIWQS which includes the GPS coordinates for the location of the SSO appearance point closest to the failure point, blockage or location of the flow condition that caused the SSO, and descriptions of the locations of all other discharge points associated with the single SSO event.
2-Hour Notification to Regulatory Agencies of SSOs
Cal OES is only to be notified of a Category 1 SSO greater than or equal to 1,000 gallons discharged to surface water or spilled in a location where it probably will be discharged to surface water. The First Responder is responsible for reviewing field data for reporting to regulatory agencies. If it is determined that the criteria for OES notification was met, than the First Responder must notify OES of the event no later than two (2) hours after:

1. Veolia has knowledge of the SSO;

2. Notification is possible; and

3. Notification can be provided without substantially impeding cleanup or other emergency measures.

The OES phone number is (800) 852-7550. The First Responder is responsible for obtaining an OES Control number, call time, and the name of the OES operator taking the call. Following the initial notification to OES and until the SSO report is certified in the SWRCB online SSO Database, the LRO will provide updates (or provide direction for updates to be provided) to OES regarding substantial changes to estimated volume of untreated or partially treated sewage discharged and any substantial changes to known impact(s). 611
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-17
Detailed Reporting Requirements
Table 6-1 provides detail on the City’s regulatory reporting process, which is also described below.

SSO Reporting for Category 1 SSOs
Cal OES shall receive notification of Category 1 SSOs greater than or equal to 1,000 gallons, as stated earlier in this Section.

The Data Submitter must then submit the initial draft report to the SWRCB’s CIWQS Online SSO database @ http://ciwqs.waterboards.ca.gov/ciwqs within 3 business days of becoming aware of the SSO.

An e-vite is sent to the City’s LRO’s calendar inviting them to certify the Category 1 SSO thirteen (13) days after the date of the SSO. This is to prevent any Category 1 SSO from being delayed in certifying within the fifteen (15) day requirement.

Within 15 calendar days of the SSO end date, the LRO must review and certify the report in the CWIQS Online SSO database @ http://ciwqs.waterboards.ca.gov/ciwqs SSO Reporting for Category 2 SSOs
Within 3 business days of becoming aware if the SSO, the Collection System Planner/Scheduler shall submit the initial report to the SWRCB’s CWIQS Online SSO database @ http://ciwqs.waterboards.ca.gov/ciwqs.

An e-vite is sent to the City’s LRO’s calendar inviting them to certify the Category 2 SSO thirteen (13) days after the date of the SSO. This is to prevent any Category 2 SSO from being delayed in certifying within the fifteen (15) day requirement.

Within 15 calendar days of the SSO end date, the LRO must review and certify the report in the CWIQS Online SSO database @ http://ciwqs.waterboards.ca.gov/ciwqs.

SSO Reporting for Category 3 SSOs
Within 30 calendar days of the end of the calendar month in which the SSO occurred, the LRO must submit and certify a report to the SWRCB's CWIQS Online SSO database @ http://ciwqs.waterboards.ca.gov/ciwqs.

Every LRO has an “event” on their calendar on the 28
th and 30th day of each month to check the
CIWQS system for any Category 3 SSO events that need to be certified. This will help prevent any Category 3 SSO from being certified past the due date. 612
Sewer System Management Plan

OVERFLOW EMERGENCY REPONSE PLAN
Richmond Municipal Sewer District Page 6-18
No Spill Certification (Monthly)
Within 30 calendar days of the end of a calendar month that there are no SSO’s, the LRO must submit and certify a “No Spill” certification to the CIWQS online SSO database.

Every LRO has an “event” on their calendar on the 1st and 3rd day of each month to check the CIWQS system for any SSOs that occurred the previous month. If there are no SSOs, they are to submit a “No Spill” certification to the CIWQS online SSO database at that time.

CIWQS Not Available
In the event that the CIWQS online SSO database is not available, the LRO will fax or all required information to the RWQCB office at (510) 622-2460 in accordance with the time schedules identified above. In such an event, the City will submit the appropriate reports using the CIWQS online SSO database when the database becomes available. A copy of all documents that certify the submittal in fulfillment of this section shall be retained in the SSO document file.

Amending SSO Reports
The LRO is responsible for amending SSO reports. Certified SSO reports may be updated by amending the report or adding an attachment to the SSO report within 120 calendar days after the SSO end date. After 120 days, the City must contact the State SSO Program Manager to request to amend an SSO report along with a justification for why the additional information was not available prior to the end of the 120 days. The SWRCB SSO Program Manager contact information is as follows:

Russell Norman, P.E.

State Water Resources Control Board
Division of Water Quality
1001 I Street 15th Floor
Sacramento, CA 95814
E-mail: [email protected]
Phone: (916) 323-5598

6.12.2 Technical Report
If 50,000 gallons or greater from an SSO reaches surface waters, an SSO Technical Report must be prepared and submitted to the CIWQS online SSO database within 45 calendar days of the SSO end date. The LRO is response for submitting the Technical Report, which is described in further detail earlier in this Section.
613
Sewer System Management Plan

DESIGN AND PERFORMANCE PROVISIONS
Richmond Municipal Sewer District Page 6-21
Table 6.1. Regulatory Reporting Requirements
Element Requirement Method
NOTIFICATION Within two hours of becoming aware of any Category 1 SSO greater than or equal to 1,000 gallons discharged to surface water or spilled in a location where it probably will be discharged to surface water, the City will notify the California Office of Emergency Services (CalOES) and obtain a notification control number.

Call Cal OES at: (800) 852-7550
REPORTING • Category 1 SSO: Veolia will submit draft report within three business days of becoming aware of the SSO and the City certify within 15 calendar days of SSO end date. • Category 2 SSO: Veolia will submit draft report within 3 business days of becoming aware of the SSO and the City certify within 15 calendar days of the SSO end date. • Category 3 SSO: Veolia will submit the report and the City will certify the report within 30 calendar days of the end of month in which SSO the occurred.
• SSO Technical Report: The City will submit within 45 calendar days after the end date of any Category 1 SSO in which 50,000 gallons or greater are spilled to surface waters. • “No Spill” Certification: The City will certify that no SSOs occurred within 30 calendar days of the end of the month or, if reporting quarterly, the quarter in which no SSOs occurred. • Collection System Questionnaire: The City will update and certify every 12 months • Enter data into the CIWQS Online SSO Database (http://ciwqs.waterboards.ca.gov/), certified by the Legally Responsible Official(s).
• All information required by CIWQS will be captured in the Sanitary Sewer Overflow Report.• Certified SSO reports may be updated by amending the report or adding an attachment to the SSO report within 120 calendar days after the SSO end date. After 120 days, the State SSO Program Manager must be contacted to request to amend an SSO report along with a justification for why the additional information was not available prior to the end of the 120 days.

WATER QUALITY MONITORING
• The City will conduct water quality sampling within 48 hours after initial SSO notification for Category 1 SSOs in which 50,000 gallons or greater are spilled to surface waters.

Water quality results will be uploaded into CIWQS for Category 1 SSOs in which 50,000 gallons or greater are spilled to surface waters.

RECORD KEEPING
Veolia will maintain the following records on behalf of the City:
• SSO event records.
• Records documenting Sanitary Sewer Management Plan (SSMP) implementation and changes/updates to the SSMP.
• Records to document Water Quality Monitoring for SSOs of 50,000 gallons or greater spilled to surface waters.
• Collection system telemetry records if relied upon to document and/or estimate SSO Volume.

Self-maintained records shall be available during inspections or upon request. 614
Sewer System Management Plan

OVERFLOW EMERGENCY RESPONSE PLAN
Richmond Municipal Sewer District Page 6-22

6.13 Equipment
This section provides a list of specialized equipment that is required to support this Overflow Emergency Response Plan.

Closed Circuit Television (CCTV) Inspection Unit – A CCTV Inspection Unit is required to determine the root cause for all SSOs from gravity sewers.

Camera – A digital or disposable camera is required to record the conditions upon arrival, during clean up, and upon departure.

Emergency Response Trucks -- A utility body pickup truck, or open bed is required to store and transport the equipment needed to effectively respond to sewer emergencies. The equipment and tools should include containment and clean up materials.

Portable Generators, Portable Pumps, Piping, and Hoses – Equipment used to bypass pump, divert, or power equipment to mitigate an SSO.

Combination Sewer Cleaning Trucks -- Combination high velocity sewer cleaning trucks with vacuum tanks are required to clear blockages in gravity sewers, vacuum spilled sewage, and wash down the impacted area following the SSO event.

6.14 Contractors Working On City Sewer Facilities
All contractors working on City sewer facilities will be trained in the City’s OERP and will be required to follow the OERP in the event that they cause or observe an SSO.

6.15 Training
This section provides information on the training that is required to support this Overflow Emergency Response Plan.

6.15.1 Initial and Annual Refresher Training
All City personnel who may have a role in responding to, reporting, and/or mitigating a sewer system overflow should receive training on the contents of this OERP. All new employees should receive training before they are placed in a position where they may have to respond.

Current employees should receive annual refresher training on this plan and the procedures to be followed. Affected employees will receive annual training on the following topics, at a minimum, by knowledgeable trainers:
• The City’s Overflow Emergency Response Plan
• SSO Volume Estimation Techniques
615
Sewer System Management Plan

OVERFLOW EMERGENCY RESPONSE PLAN
Richmond Municipal Sewer District Page 6-23
• Impacted Surface Waters: Response Procedures
The City will verify that annual safety training requirements are current for each employee, and that employees are competent in the performance of all core competencies. The City will address, through additional training/instruction, any identified gaps in required core competencies.

6.15.2 SSO Response Drills
Periodic training drills should be held to ensure that employees are up to date on these procedures, equipment is in working order, and the required materials are readily available. The training drills will cover scenarios typically observed during sewer related emergencies (e.g. mainline blockage, mainline failure, force main failure, pump station failure, and lateral blockage). The results and the observations during the drills will be recorded and action items should be tracked to ensure completion.

6.15.3 SSO Training Record Keeping
Records should be kept of all training that is provided in support of this plan. The records for all scheduled training courses and for each overflow emergency response training event and will include date, time, place, content, name of trainer(s), and names of attendees.

Appendix E – Overflow Emergency Response Plan Documents Appendix E includes a full copy of the Veolia Emergency Overflow Response Plan. The information in this document will change from time to time, and the OERP may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the OERP.
• Veolia Emergency Overflow Response Plan
• Hard Copies of Veolia Field Forms
616
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-1
ELEMENT 7 - FOG CONTROL PROGRAM
The purpose of this section is to evaluate the extent and nature of SSOs related to Fats, Oils and Grease (FOG), to determine the need for a FOG Control Program, and to outline the elements of the RMSD FOG Control Program.

The City of Richmond’s FOG Control Plan was initiated in 2003. A field survey identified all food service facilities with and without grease control devices. Periodic inspection of food service facilities began in 2004.

In 2006, the City of Richmond Municipal Code was revised to require that new Food Handling Facilities (FHFs) install grease pretreatment devices that conform to the current version of the Uniform Plumbing Code (UPC). Additionally, one component of the 2006 settlement agreement between the City and San Francisco Baykeeper required the City to increase the inspection frequency of FHFs, and improve the public education and outreach program.

The RMC provides legal authority to prevent the introduction of FOG into the Sanitary Sewer System. In addition, the City’s FOG Control Plan has developed tools for tracking, inspecting, and grading FOG dischargers, as well as developed documents for education and outreach on FOG disposal.

7.1 RWQCB and SWRCB SSMP Requirements

7.1.1 RWQCB Requirement:

The RMSD must evaluate its service area to determine whether a FOG control program is needed. If needed, a FOG control program shall be developed as part of the SSMP. If the RMSD determines that a FOG program is unnecessary, proper justification must be provided.

7.1.2 SWRCB Requirement:

The RMSD shall evaluate its service area to determine whether a FOG control program is needed. If the RMSD determines that a FOG program is not needed, justification must be provided for why it is not needed. If FOG is found to be a problem, the RMSD must prepare and implement a FOG source control program to reduce the amount of these substances discharged to the sanitary sewer system. The FOG source control program shall include the following as appropriate:
• An implementation plan and schedule for a public education outreach program that promotes proper disposal of FOG.
• A plan and schedule for the disposal of FOG generated within the sanitary sewer system service area. This may include a list of acceptable disposal facilities and/or additional 617
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-2
facilities needed to adequately dispose of FOG generated within a sanitary sewer system service area.
• The legal authority to prohibit discharges to the system and identify measures to prevent SSOs and blockages caused by FOG.
• Requirements to install grease removal devices (such as traps or interceptors), design standards for the grease removal devices, maintenance requirements, BMP requirements, record keeping and reporting requirements
• Authority to inspect grease producing facilities, enforce requirements, and determine whether the RMSD has sufficient staff to inspect and enforce the FOG ordinance. • An identification of sewer system sections subject to FOG blockages and the establishment of a cleaning maintenance schedule for each section. • Development and implementation of source control measures, for all sources of FOG discharged to the sewer system, for each sewer system section identified as subject to blockages.

7.2 Public Education Outreach Plan
The City has developed a public outreach program to inform residents about the impacts of FOG waste on the sewer system. The program begins with information provided on the City website, which discusses the sources of FOG and the impact of FOG on the sewer system, and provides links to fact sheets for grease traps, grease interceptors, and mechanical grease removal devices.

These fact sheets are also included in Appendix F.

When a residential FOG-related SSO occurs, the City’s source control staff distribute brochures, door hangers, and educational pot scrapers to the residents upstream of the SSO location to inform these residents of proper FOG control. This program may be updated/modified annually by the Source Control Superintendent based on departmental staffing. A copy of this program and example handout materials are included in Appendix F.

The City has approximately 115 food service establishments (FSE). The outreach program includes a component designed to educate the City’s FSE owners and employees about minimizing FOG disposal into the sewer system, including information about best management practices for minimizing FOG. The City’s program was based on materials developed by the TriTAC CalFOG workgroup. Program information is included in Appendix F.

7.3 FOG Disposal Plan
The requirement for proper FOG disposal is provided in RMC Section 12.18.030.2. 618
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-3
RMC 12.18.030.2 “Fats, Oils & Grease”
D. Best Management Practices.
(1) Drain Screen. After March 1, 2006, drain screens shall be installed on all drainage pipes for all new food services establishments deemed by the City Manager to generate FOG.
(2) Waste FOG:
(a) All waste FOG shall be collected and stored properly in recycling barrels, drums, or bins.
(b) Such recycling barrels, drums, or bins shall be maintained appropriately to ensure they do not leak or enter the City's stormwater collection system by direct discharge or by commingling with stormwater.
(c) A licensed collection service must be used to dispose of waste FOG.

Currently, grease haulers dispose of grease pumped from interceptors at a grease collection facility outside of the RMSD service area. At this time, there does not appear to be a need for additional grease disposal facilities to collect grease from the City’s service area. However, the City may choose to evaluate this need further, should the need for additional grease disposal facilities become an issue in the future.

7.4 Legal Authority to Prohibit SSOs and Blockages Caused by FOG Discharge Section 3, Legal Authority, discusses the City’s authority to enforce sewer-related issues.

Specifically, Richmond Municipal Code Section 12.18.020.1. B prohibits the discharge of fats, oils and grease. Only the specific subsections relevant to this requirement are listed.

RMC Section 12.18.020.1 “Prohibited Discharge Standards” B. Specific Prohibitions. No User shall introduce or cause to be introduced into the WPCP the following pollutants, substances, or wastewater:
(3) Solid or viscous substances, such as, but not limited to, grease, garbage with particles greater than one-half (0.5) inch in any dimension, animal guts or tissues, paunch manure, bones, hair, hides or fleshing, entrails, whole blood, feathers, ashes, cinders, sands, spent lime, stone or marble dust, metal, glass, straw, shavings, grass clippings, rags spent grains, spent hops, waste paper, wood, plastics, gas, tar, asphalt residues, residues from refining or processing of fuel or lubricating oil, mud, glass grindings, or 619
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-4
polishing wastes, in amounts which will cause obstruction of the flow in the WPCP resulting in interference.
(6) Petroleum oil, non-biodegradable cutting oil, or products of mineral origin, in amounts that will cause interference or pass through.

7.5 Requirements and Design Standards for Installation of Grease Removal Devices RMC Section 12.18.030.02 includes requirements for the installation of grease removal devices, including design standards and approvals. Specific subsections are called out below.

RMC 12.18.030.2 “Fats, Oils & Grease”
A. Fats, Oils, and Grease Program.
(1) Fats, oils, and grease interceptors:
(a) FOG separators and grease interceptors shall be provided, at the user's expense, where, in the opinion of the City Manager, they are necessary for proper handling of wastes containing these substances in excessive amounts, or any flammable wastes or harmful ingredients. All grease interceptors shall be of a type and capacity approved by the City Manager, and shall be located so it is readily and easily accessible for inspection and cleaning. (5) A grease collection service shall be required for all facilities that generate FOG.

B. Administration of FOG Program. The City shall administer a FOG program, which is intended to prevent fats, oils, and grease, and other substances that are likely to block or create a hazard within the sewer system from entering the system through use of grease interceptors or grease traps. The City may require any non-domestic user to install a grease interceptor or grease trap according to the guidelines set for in the City's Standard Specifications or other program prior to or at any time after connection to the WPCP if the City discovers or determines subsequent to the connection of the facility, the user produces a waste with characteristics that would require installation of a grease interceptor or grease trap pursuant of this chapter.

The installation of a proper grease interceptor or grease trap device shall be the responsibility of the user that applies for the connection or wastewater discharge permit.

The City shall determine whether a grease interceptor, grease trap, or other interceptor is required on a case-by-case basis based on an evaluation of the following criteria including, but not limited to:
620
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-5
(1) The type of facility (restaurant, bakery, cheese factory, yogurt shop, gas station, lube facility, etc.);
(2) The volume of the user's business or operation (number of meals served, number of seats, hours of operation, etc.);
(3) Size and nature of facilities (including kitchen facilities) based on size, type, number of fixtures, and types of processing and/or cooking equipment used; (4) The type of service provided or operation undertaken (such as dine-in meal service versus carry-out meal service);
(5) The type of foods and other materials used in the cooking, processing, or manufacturing operations carried on within the user's facility; (6) The overall potential for grease-laden, flammable, or sand-laden discharges; and (7) The existence of devices, procedures, or processes which are designed to minimize the amount of grease, sand, oil, or other flammable liquids from entering the sewer system.

The design, location, and procedures for operation of a required grease interceptor or grease trap shall be approved by the City. Such approval shall be obtained prior to the user's connection of the facility to the WPCP, in the event of new construction or remodeling. In instances where a user has already connected and the City determines that a grease interceptor or grease trap must be installed, the user shall promptly provide for the installation of the device, including providing such design and operational plans as may be required. The installation of a grease interceptor or grease trap as required by this chapter on an existing user facility shall occur within a reasonable time not to exceed one hundred (100) days after the user has been provided notice that a grease interceptor or grease trap must be installed. This time limit may only be extended by the City in a written agreement.

E. Grease Separators (Traps) for Treating FOG Wastes.
(1) Facilities that have FOG, but are not required to have a grease interceptor, must have an adequate-sized grease trap as determined by the City Manager. (2) Required connections to grease traps: all three compartment sinks, scullery (preparation) sinks, and pre-wash sinks at dishwashing stations. (3) Prohibited connections or additives to grease traps:
621
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-6
(a) Final rinse discharge from automatic dishwashers/sanitizers shall not be connected to the grease trap.
(b) Chemical additives, such as chlorinated solvents, or any other additives that causes the emulsification of grease, are strictly prohibited from use in any grease trap.

F. Grease Interceptors for Treating FOG Wastes.
(1) Grease interceptors shall be required for new food handling facilities constructed after March 1, 2006.
(2) Grease interceptors are required for food handling facilities that generate FOG when there is remodeling, additions, alterations, or repairs valued at or greater than what is specified in the City's fee schedule.
(3) Effective March 1, 2006, those food handling facilities operating without a grease interceptor shall, within six (6) months of written notification by the City Manager, be required to install a grease interceptor if the City Manager determines that the food service establishment is not adhering to the BMPS set forth in Section 12.18.030.2(D) of this chapter, or that the food service establishment has caused or contributed to a sewer system blockage resulting in maintenance requirements and/or sewage spills. (4) All new grease interceptors shall be designed, constructed, and installed in accordance with the current City of Richmond Building and Plumbing Codes, and shall be subject to approval by the Building Regulations Department. (5) All submitted drawings shall be prepared by a licensed and registered professional engineer. Any false information or misleading calculations submitted shall be the responsibility of the user.
(6) All grease interceptors shall be located such that they are readily and easily accessible for cleaning, inspection, and removal of intercepted waste. (7) A common grease interceptor shared by multiple businesses can be utilized if specifically authorized by the City Manager upon evidence of legal operating and maintenance agreements between the involved users.
(8) All grease interceptors shall include an effluent sample box and a sanitary tee located on the discharge side of the sample box of a type and size approved by the City. 622
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-7
(9) Inspection by the City of installed grease interceptors and piping prior to backfilling is required. Piping shall meet the requirements of the City of Richmond Building and Plumbing Code.
(10) Grease interceptors shall have a clean-out installed after the sample box on the private lateral as required by the City of Richmond Building and Plumbing Code. (11) Required connections to grease interceptors: all three compartment sinks, scullery (preparation) sinks, floor drains and mop sinks along the cook line, pre-wash sinks at dishwashing stations, and all other fixtures that contribute grease into the sewer system.
(12) No food service establishment or other identified user shall construct, remodel, or convert a grease interceptor without approval by the City. (13) Prohibited connections or additives to grease interceptors:
(a) Final rinse discharge from automatic dishwashers/sanitizers shall not be connected to the grease interceptor.
(b) The use of any additive such as surfactants or chemicals shall not be connected to any type of grease interceptor. Chemical additives, such as chlorinated solvents, or another other additives that cause the emulsification of grease, are strictly prohibited from use in any type of grease interceptor.

G. Waivers for Treating FOG Wastes.
(3) A grease interceptor or grease trap may not be required for business types listed below:
(a) Facilities only serving beverages;
(b) Facilities serving beverages and/or ready-to-eat, packaged, or unpackaged items;
(c) Ice cream parlors without any baking or other food preparation; (d) Snack bars with no food preparation other than food warming; (e) Bakeries with no food preparation other than food warming; or (f) Other facilities serving only ready-to-eat foods with or without food warming. 623
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-8

7.6 Device Maintenance Requirements
RMC Section 12.18.030.02 includes requirements for the maintenance of grease removal devices. Only the specific subsections relevant to this requirement are listed.

RMC 12.18.030.2 “Fats, Oils & Grease”
A. Fats, Oils, and Grease Program.
(1) Fats, oils, and grease interceptors:
(c) Where installed, all FOG separators or grease interceptors shall be maintained and in continuous efficient operation at all times.
(6) If significant grease accumulation (e.g., a partial blockage) is found downstream or if significant grease wicking is found upstream of the process of concern, an Authorized Inspector and/or the City Manager may inspect the facility. The inspection will include a review of the grease management program, treatment system, waste storage area, and drains not flowing to the treatment system. BMPs not in place, hauler receipts for the prior three (3) years not available, and/or training documents not current may result in future inspections with an assessed fee as published in the City's fee schedule (see Section 12.18.140).
(7) If a business is shown to be the cause of a grease-related sewer overflow, the user will be responsible for the cost of clean-up as set forth in Section 12.18.140 C. Grease Interceptor Maintenance Procedures and Program. Any user, required by the City and/or this chapter to install and/or operate a grease interceptor or grease trap, shall adequately maintain the device so that the device is in proper working order at all times.

Grease and oil interceptors shall be cleaned by a licensed and permitted waste hauler on a periodic basis to assure that the grease interceptor will operated as designed at all times.

Any user, required to install or have in operation a grease interceptor or grease trap pursuant of this chapter, shall have a plan of operation or program for their facility that is intended to ensure that the grease interceptor or grease trap operates as designed to prevent grease, oil, sand, or other harmful constituents from entering the sewer system. These procedures may be include adoption of kitchen practices to minimize grease-laden garbage, which may ultimately enter the facility's drains and floor traps and/or other such procedures as may be required for proper operation of the grease interceptors. (1) Grease interceptors shall be cleaned out completely by a FOG collection service as necessary to assure that the grease interceptor will operate as designed at all times or as otherwise specified by the City.
624
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-9
(2) Decanting or discharging of removed waste back into the grease interceptor, for the purpose of reducing the volume to be hauled, is prohibited. (3) The use of additives, directly or indirectly to the plumbing or sewer system, to emulsify grease and/or oil, is specifically prohibited. (4) The use of biological additives as a supplement to grease interceptor maintenance, including the addition of microorganisms, may be authorized by the City Manager.

Approval shall be obtained (in writing) prior to use of such additives. (5) Maintenance records indicating date of service, volume pumped, name of waste hauler, and waste disposal location for each pumping of the grease interceptor must be kept for a minimum of three (3) years. The records must be provided to the City Manager when requested during normal business hours.
(6) All waste removed from a grease interceptor must be disposed of at a facility permitted by Contra Costa County or other applicable regulatory agencies to receive such waste. Pumped out FOG shall not be returned to the sewer system, nor any private wastewater system, nor storm drains.
(7) Any fixture connected to a grease interceptor shall have a non-removable, secured food strainer of such integrity so as to withstand daily operational usage.

E. Grease Separators (Traps) for Treating FOG Wastes.
(6) A maintenance log for the grease trap must be kept for a minimum of three (3) years and must be provided at the request of the City.

F. Grease Interceptors for Treating FOG Wastes.
(6) All grease interceptors shall be located such that they are readily and easily accessible for cleaning, inspection, and removal of intercepted waste.

7.7 BMP Requirements, Recordkeeping and Reporting
BMP requirements are included in the following section of the RMC:

RMC 12.18.030.2 D “Best Management Practices”
(1) Drain Screen. After March 1, 2006, drain screens shall be installed on all drainage pipes for all new food services establishments deemed by the City Manager to generate FOG. (2) Waste FOG:
625
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-10
(a) All waste FOG shall be collected and stored properly in recycling barrels, drums, or bins.
(b) Such recycling barrels, drums, or bins shall be maintained appropriately to ensure they do not leak or enter the City's stormwater collection system by direct discharge or by commingling with stormwater.
(c) A licensed collection service must be used to dispose of waste FOG. (3) Food Waste. All food waste shall be disposed of directly into the trash or garbage and not in sinks.
(4) Employee Training:
(a) Employees of food service establishments shall be trained within three (3) months after the effective date of this chapter, and two (2) times each calendar year thereafter, on the following subjects:
(i) How to "dry wipe" pots, pans, dishware, and work areas before washing to remove FOG.
(ii) How to properly dispose of food waste and solids in enclosed plastic bags prior to disposal in trash bins or containers to prevent leaking and odors. (iii) The location and use of absorption products to clean under fryers and other locations where grease may be spilled or dripped.
(b) Training shall be documented and employee signatures retained, indicating each employee's attendance and understanding of the practices. (c) Training records shall be available for review at any reasonable time by an Authorized Inspector and/or the City Manager.
(5) Kitchen exhaust filters shall be cleaned as frequently as necessary in order to maintain good operating condition.
(6) All BMPs shall be posted conspicuously in the food preparation and dishwashing areas and process areas at all times.

7.8 Authority to Inspect Grease Producing Facilities and Enforce Requirements The following sections of the RMC provide authority to inspect facilities and enforce requirements. Only the specific subsections relevant to this requirement are listed. 626
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-11
RMC 12.18.030.2 “Fats, Oils & Grease”
A. Fats, Oils, and Grease Program.
(2) These facilities must have a FOG Management Program Permit. An Authorized Inspector and/or the City Manager shall have right of entry as described in Section

12.18.070.1 of this chapter.
(3) Fees, charges, and penalties are pursuant of Section 12.18.140 of this chapter. (6) If significant grease accumulation (e.g., a partial blockage) is found downstream, or if significant grease wicking is found upstream of the process of concern, an Authorized Inspector and/or the City Manager may inspect the facility. The inspection will include a review of the grease management program, treatment system, waste storage area, and drains not flowing to the treatment system. BMPs not in place, hauler receipts for the prior three (3) years not available, and/or training documents not current may result in future inspections with an assessed fee as published in the City's fee schedule (see Section 12.18.140).

E. Grease Separators (Traps) for Treating FOG Wastes.
(6) A maintenance log for the grease trap must be kept for a minimum of three (3) years and must be provided at the request of the City.

F. Grease Interceptors for Treating FOG Wastes.
(4) All new grease interceptors shall be designed, constructed, and installed in accordance with the current City of Richmond Building and Plumbing Codes, and shall be subject to approval by the Building Regulations Department. (9) Inspection by the City of installed grease interceptors and piping prior to backfilling is required. Piping shall meet the requirements of the City of Richmond Building and Plumbing Code.
(12) No food service establishment or other identified user shall construct, remodel, or convert a grease interceptor without approval by the City.

7.9 Sewer Sections Subject to FOG Blockages
SSOs due to FOG are reported in CIWQS. Appendix F contains a table with locations of FOGrelated SSOs from 2014 to present. 627
Sewer System Management Plan

FOG CONTROL PROGRAM
Richmond Municipal Sewer District Page 7-12
The City’s Source Control Superintendent manages response, outreach activities, and maintains records of the response activities for FOG-related SSOs. This information is updated annually.

Appendix F – Element 7 Documents
Appendix F includes the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix F may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the Appendix F documents.
• Fats, Oils and Grease Policy (RMC §12.18.020.2)
• FOG Control Program Including City Handouts and Public Outreach Materials • FOG Related SSOs reported in CIWQS and Source Control Activities tables 2014 – Present.
628
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-1
ELEMENT 8 - SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN This section of the SSMP discusses the RMSD’s activities related to capacity management. This section fulfills the Capacity Management requirements for the RWQCB and the SWRCB elements.

8.1 RWQCB and SWRCB SSMP Requirements

8.1.1 RWQCB Requirement
The RMSD must prepare a CIP to provide hydraulic capacity of key collection system elements under peak flow conditions.

8.1.2 SWRCB Requirement
The RMSD must prepare and implement a capital improvement plan (CIP) that will provide hydraulic capacity of key sanitary sewer system elements from dry weather peak flow conditions, as well as the appropriate design storm or wet weather event. At a minimum, the plan must include:
• Evaluation: Actions needed to evaluate those portions of the sanitary sewer system that are experiencing or contributing to an SSO discharge caused my hydraulic deficiency.

The evaluation must provide estimates of peak flows (including flows from SSOs that escape from the system) associated with conditions similar to those causing overflow events, estimates of the capacity of key system components, hydraulic deficiencies (including components of the system with limiting capacity) and the major sources that contribute to the peak flows associates with overflow events; • Design Criteria: Where design criteria do not exist or are deficient, undertake the evaluation identified in (a) above to establish appropriate design criteria; and • Capacity Enhancement Measures: The steps needed to establish a short- and long-term CIP to address identified hydraulic deficiencies, including prioritization, alternatives analysis, and schedules. The CIP may include increases in pipe size, I/I reduction programs, increases and redundancy in pumping capacity, and storage facilities. The CIP shall include an implementation schedule and shall identify sources of funding. • Schedule: The Enrollee shall develop a schedule of completion dates for all portions of the capital improvement program developed in (a)-(c) above. This schedule shall be reviewed and updated consistent with the Sewer System Management Plan (SSMP) review and update requirements as described in Section D. 14.

8.2 System Evaluation and Capacity Assurance Plan
629
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-2

8.2.1 Pipeline Capacity Assessment and Capital Improvement Plan The contract between the City and Veolia required Veolia to complete a capacity assurance plan and establish a prioritized CIP to address capacity needs in the sewer collection system. In 2010, Veolia Water completed an updated Sewer Collection System Master Plan (Master Plan) that addressed pipeline capacity issues. The Master Plan was adopted by City Council in 2011, and used a calibrated fully dynamic hydraulic model developed in Innovyze® Infoworks ™ CS. The hydraulic model can be used to evaluate future pipeline capacity issues, and to further evaluate collection system pump station performance.

The hydraulic model was used to predict sewer system pipelines that would have capacity constraints leading to SSOs during a 10-year, 24-hour design storm. The model also predicts peak hourly system flow that would be conveyed by the system during the design storm, provided the predicted SSOs are addressed.

The predicted SSO locations are in areas of the system that have known SSOs. However, because recorded SSO data is related to storm events that are not identical to the theoretical design storm event in magnitude, intensity, and rainfall distribution, there is some difference between predicted and actual system behavior.

The Master Plan includes a description of the RMSD 2009/10 flow monitoring program and two subsequent flow monitoring projects that were conducted by Veolia for the City. The results from these projects were collectively used to estimate the proportion of inflow and infiltration (I&I) that enters the sewer system during a wet weather event. The flow monitoring program identified various sources of I&I, including groundwater, tidal influence, and permitted dry weather industrial stormwater discharges (this program is being discontinued by the City). The Master Plan also establishes design criteria for use in evaluating system capacity, and for sizing new pipelines.

The Master Plan includes a short- (one to five year) and long-term (10 year) capital improvement plan (CIP) to address predicted pipeline hydraulic deficiencies under the design storm event.

The CIP evaluates, assigns costs, and prioritizes recommended projects. The CIP implementation schedule is focused on maximizing the success in achieving the capacity-related SSO reduction requirements of the settlement agreement between the City and San Francisco Baykeeper.

The CIP includes recommended capacity increases, pipeline rehabilitation and replacement to reduce system-wide I&I, and wet weather relief and storage. The CIP is used to help provide justification for, and subsequently receive funding from the City’s bond funds and sewer service charges.
630
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-3
Figure 8-1 is found at the end of this section. This figure reproduces the CIP presented in Table 9-1 of the Master Plan. The CIP is in the process of being updated as part of the City’s annual budgeting process.

8.2.2 Pump Station Capacity Assessment and Capital Improvement Plan Flows generated by the system hydraulic model were compared to firm pump station capacity (i.e., with the largest pump out of service) as listed in the City’s 2006 master plan report and confirmed by Veolia. Based on this information, all of the modeled pump stations have sufficient capacity to convey flows from the 10-year, 24-hour design storm, as shown in Table 8-1.

Table 8-1. RMSD Pump Station Capacities
Pump Station Firm Capacity from 2006 Master Plan
(gpm)
Design Storm Flow (gpm)
Keller Beach 780 174
Ferry Point 450 331
ICI 440 245
Marina Bay Cove 440 46
Marina Bay Parkway 4200 2646

8.3 Design Criteria
The City uses a 10-year, 24-hour design storm, using National Oceanographic and Atmospheric Administration (NOAA) precipitation data and a SCS-1A rainfall distribution curve. Pipes were considered under-capacity if the hydraulic model predicted an SSO under this design storm.

Pump stations were considered under-capacity if they were unable to convey peak flows from this storm with the largest pump out of service.

8.4 Capacity Enhancement Measures
The recommended capacity improvement projects are included in the previously described CIP.

These improvements include specific projects to upsize pipelines and the addition of wet weather storage.

8.5 Capital Improvement Program Budget and Schedule
The City’s fiscal year 2017/18 budget and schedule are included in the City’s annual budget, the relevant pages of which are provided in Appendix G.
631
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-4
Appendix G – Element 8 Documents
Appendix G includes the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix G may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the Appendix G documents.
• Master Plan Executive Summary
632
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-5
This page left intentionally blank
633
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-5
Figure 8-1. Capital Improvement Program
(From Sewer Collection System Master Plan Table 9-1)
634
Sewer System Management Plan

SYSTEM EVALUATION AND CAPACITY ASSURANCE PLAN
Richmond Municipal Sewer District Page 8-6
635
Sewer System Management Plan

MONITORING, MEASUREMENT, & MODIFICATIONS
Richmond Municipal Sewer District Page 9-1
ELEMENT 9 - MONITORING, MEASUREMENT AND PROGRAM MODIFICATIONS This section of the SSMP discusses the RMSD Monitoring, Measurement, and Program Modifications. This section fulfills the Monitoring, Measurement, and Program Modifications requirements for the RWQCB and the SWRCB elements.

9.1 RWQCB and SWRCB SSMP Requirements
The requirements for the Monitoring, Measurement, and Program Modifications element of the SSMP are summarized below.

9.1.1 RWQCB Requirement
The RMSD must monitor the effectiveness of each SSMP element and update and modify SSMP elements to keep them current, accurate, and available for audit as appropriate.

9.1.2 SWRCB Requirement
The RMSD shall:
• Maintain relevant information that can be used to establish and prioritize appropriate SSMP activities.
• Monitor the implementation and, where appropriate, measure the effectiveness of each element of the SSMP.
• Assess the success of the preventative maintenance program. • Update program elements, as appropriate, based on monitoring or performance evaluations.
• Identify and illustrate SSO trends, including SSO frequency, location, and volume.

9.2 Maintenance of Relevant Data
The RMSD maintains complaint and blockage records in electronic format, maintains electronic logs of cleaning, repairs, other preventive maintenance activities, and records problems (e.g., excessive debris, observed manhole defects) identified through regular sewer maintenance activities on special report forms within the CMMS. This information is used to establish and prioritize appropriate SSMP activities.

9.3 Monitoring and Assessment
The RMSD tracks the following parameters with which to measure the effectiveness of the SSMP and its effectiveness in reducing SSOs:
636
Sewer System Management Plan

MONITORING, MEASUREMENT, & MODIFICATIONS
Richmond Municipal Sewer District Page 9-2
• Number of SSOs per year
• Volume of SSOs per year
• Number of SSOs per year by cause
• Number of dry weather SSOs per year
• Response time to SSOs and other service calls (time from call received to time First Responder arrived on site)
• Length of gravity sewers cleaned annually (at least one time and in total) • Length of gravity sewers CCTV inspected annually (at least one time and in total) • Record of pump station maintenance work orders completed annually • Footage of sewer mainlines rehabilitation
The SSMP will be audited as described in Element 10 SSMP Audits, based on this performance data.

9.4 Utility Metrics to Measure Progress and Prioritize Activities The RMSD has established the preventive maintenance sewer metrics that are shown in Table 9- 1 for the City and Veolia’s use in monitoring, measuring and adjusting sewer maintenance activities. The City’s responsibilities pertain to source control and claims, and Veolia is responsible for monitoring and measuring progress in sewer system performance. 637
Sewer System Management Plan

MONITORING, MEASUREMENT, & MODIFICATIONS
Richmond Municipal Sewer District Page 9-3
Table 9-1. Success Factors and Metrics
Sewer Maintenance
Success Factor
Metric
• System Pipes • Miles
• Sewer Maintenance Field
Staff
• Full Time Equivalents (FTE)
• Pipes Initially Cleaned • Miles/Year
• Pipes Re-cleaned • Miles/Year
• Pipe Inspected (CCTV) • Miles/Year
• Manholes Inspected • Miles/Year
• Hot Spots Cleaned • Number by Underlying Cause (Roots, Debris, FOG, Structural) • SSOs • Number by Underlying Cause per 100 Miles
• Repeat SSOs • Number by Address
• Response Time • Minutes per SSO after Notification
• Pump Station Overflows • Number by Cause
• Odor Complaints • Number
• FSE Inspections • #/Year
• Laterals Replaced (LRGP) • #/Year
• Pipe Replaced • Miles/Year
• Claims • #/Year and $/Year/Incident

9.5 Performance Monitoring and Program and Modifications The City will evaluate the performance of its SSMP on a biennial basis using the performance indicators noted in Section 9.3. Any operational changes that are made to improve specific performance indicators will be documented in the SSMP Audit and reflected in the revised language of the SSMP. Element 10 discusses the SSMP Audit process in detail.

9.6 SSO Trends – Frequency, Location and Volume
Table 9-2 summarizes the nature of reported SSOs from 2011 – 2016. Between 2011 and 2012, SSOs decreased in number and volume. Most of the volume reported was discharged through the City’s two engineered overflow structures. The City completed construction of a five (5) million gallon wet weather storage facility in October 2015. This was to in order to cease the use of the overflow structures (weirs) during wet weather events with a magnitude less than the design 638
Sewer System Management Plan

MONITORING, MEASUREMENT, & MODIFICATIONS
Richmond Municipal Sewer District Page 9-4
storm. The wet weather facility went on line early 2016. The overflow weirs were not used in 2016.

Table 9-2. Summary of SSOs from 2011 through 2017
Year Roots FOG Debris Structural &
Other
Capacity Total (#) Recovered Vol
(gal)
Lost Volume
(gal)
Total Volume
(gal)
2011 3 7 7 5 27 49 1911 14,644,544 14,657,455
2012 8 6 7 5 20 46 4,844 7,425,826 7,430,670
2013 4 7 9 9 0 29 28,975 68,755 97,730
2014 5 10 9 2 8 34 16,095 2,827,137 2,843,359
2015 6 8 3 4 0 21 5,684 3,405 9,142
2016 6 6 5 3 26 46 2,382 644,632 647,654
Appendix H – Element 9 Documents
There are no Appendix documents to accompany Section IX. However, this Appendix H is included as a placeholder for future documents.

This page left intentionally blank
639
Sewer System Management Plan

SSMP PROGRAM AUDITS
Richmond Municipal Sewer District Page 10-1
ELEMENT 10 - SSMP PROGRAM AUDITS
This section of the SSMP discusses plans for required self-audits of the SSMP. This section fulfills the SSMP Audit requirement for the RWQCB and the SWRCB elements.

10.1 RWQCB and SWRCB SSMP Requirements
The requirements for the SSMP Audits element of the SSMP are summarized below:

10.1.1 RWQCB Requirement
The RMSD must conduct a biannual audit of the SSMP that includes any deficiencies and steps to correct them that are appropriate to the size of the RMSD system and the number of overflows. The RMSD must submit a report of its biannual audit, as described in the updated SSMP audit requirements issued in October 2012.

10.1.2 SWRCB Requirement
The RMSD shall conduct periodic internal audits, appropriate to the size of the system and the number of SSOs. At a minimum, these audits must occur every two years and a report must be prepared and kept on file. This audit shall focus on evaluating the effectiveness of the SSMP and the RMSD’s compliance with the SSMP requirements, including identification of any deficiencies in the SSMP and steps to correct them.

10.2 Audit Procedures, Roles and Responsibilities
The RMSD will prepare a biannual SSMP audit to keep on file. The proposed audit format is included in Appendix I.

10.3 SSMP Program Modification/Update Process
If the biannual audit identifies significant changes to be made to the SSMP, then the SSMP will be updated by September 30th . However, it is anticipated that the main SSMP document will remain generally unchanged, and that any changes will be recorded in the SSMP Change Log, which is included in Appendix I.

Appendix I – SSMP Program Audit Documents
Appendix I include the following documents related to this section. The information in these documents will change from time to time, and the documents in Appendix I may have been superseded. Please contact the Water Resource Recovery Director for the most recent updates to the Appendix I documents.
• Audit Form
640
Sewer System Management Plan

SSMP PROGRAM AUDITS
Richmond Municipal Sewer District Page 10-2
• SSMP Change Log
• Completed audits
641
Sewer System Management Plan

COMMUNICATION PLAN
Richmond Municipal Sewer District Page 11-1
ELEMENT 11 - COMMUNICATION PLAN
This section of the SSMP discusses the City’s Communication plan. This section fulfills the Communication Plan requirements for the SWRCB element. There is no requirement in the RWQCB guidelines.

11.1 RWQCB and SWRCB SSMP Requirements
The requirements for the Communication Plan element of the SSMP are summarized below:

11.1.1 RWQCB Requirement
No requirement.

11.1.2 SWRCB Requirement
The City shall communicate on a regular basis with the public on the development, implementation, and performance of its SSMP. The communication system shall provide the public the opportunity to provide input to the City as the program is developed and implemented.

The City shall also create a plan of communication with systems that are tributary and/or satellite to the sanitary sewer system.

11.2 Communication Plan
The City does not currently have a formal communication plan in place for the communication of SSMP elements, performance, or updates. However, the City has a comprehensive library of documents that are available to the public through the “Wastewater” page of the City website.

The SSMP will be added to this library for access by the public, and a clear link to the document will be provided on the website to facilitate access to the document. The public has the opportunity to comment on the SSMP at Council meetings, which are open to the public and held at least twice per month.

Appendix J – Communication Plan Documents
There are no Appendix documents to accompany Section IX. However, this Appendix J is included as a placeholder for future documents.
642
Sewer System Management Plan

APPENDICES
Appendix A
Element 2 (Organization) Supporting Documents
643
644
Contact Names and Phone Numbers
Appendix A
H\002RI-12-01\WP\SSMP
Names and contact information for the Veolia SSO responders (First Responder) and responsible City employees are as listed below:
• Veolia Hotline: 510-412-2001
• Veolia Project Manager - Aaron Winer Cell: 510-385-6482 • Veolia Sewer Collection Manager - 7LP2
&RQQRU&HOO

• Veolia Sewer Field Supervisor - Wayne Madison Cell: 510-542-3247 • Veolia Field Crew Cell Numbers:
o$UPVWURQJ.HQQ\ 510-812-
o Roos, Jason 510-812-1173
o Wallis, David 510-447-0220
o Lewis, Kenny 510-932-1242
o 0DGLVRQ:D\QH 510-542-3247
o +LOO$UOHH 510-

o +HQGULFNV0LWFKHOO 510-

o Mendoza, Rafael 510-

• In Case of Emergency: 911
• City Police Dispatch: 510-233-1214
• OES: 800-852-7550
• City Manager: 510-620-6512
• City Interim Engineering Services Director Cell: 510-435-4340 • City 6RXUFH&RQWURO6XSHULQWHQGHQW&HOO




• Contractors
o BayHawk, Inc.: 510-776-5886
o Roto-Rooter: 804-794-7474 TMB, LLC: 707-252-5480
645
Contact Names and Phone Numbers
Appendix A
H\002RI-12-01\WP\SSMP
o Sierra Pacific Loss Management (Bruce Burnett – Interior Cleaning): 707-479- 1375
o DW Pumps- 916-559-2054
• California Regional Water Quality Control Board: 510-622-2369 • California Department of Fish and Games - Bay Delta Region : 707-944-5500 • East Bay Regional Park District: 510-633-0460
• Contra Costa County Health Services: 925-692-2500
• California Office of Emergency Services :  • U.S. Coast Guard : 510-437-3073
646
Sewer System Management Plan

APPENDICES
Appendix B
Element 3 (Legal Authority) Supporting Documents
647
648
Richmond, California, Code of Ordinances >> Article VI - BUILDING REGULATIONS >> Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE >>
Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Sections:

6.02.010 - Title.

6.02.020 - Definitions.

6.02.030 - Purpose.

6.02.040 - Scope.

6.02.050 - Existing buildings, structures and equipment.

6.02.060 - Conflicting provisions.

6.02.070 - Alternate materials and methods of construction.

6.02.080 - Modifications.

6.02.090 - Tests.

6.02.100 - Authority.

6.02.110 - Powers and duties of Building Official.

6.02.120 - Unsafe buildings, structures or equipment.

6.02.130 - Board of Appeals.

6.02.140 - Violations—Penalties.

6.02.150 - Permits.

6.02.160 - Application for permit.

6.02.170 - Permits issuance.

6.02.180 - Fees.

6.02.190 - Inspections.

6.02.210 - Special inspections.

6.02.220 - Engineering or architect requirements.

6.02.230 - Connection to utilities.

6.02.240 - Certificate of Occupancy.

6.02.250 - Adoption of technical codes.

6.02.010 - Title.

These regulations shall be known as the "Building Regulations Administrative Code," may be cited as such and will be referred to herein as "this chapter."

6.02.020 - Definitions.

General. For the purpose of this chapter, certain terms, phrases, words and their derivatives shall be construed as specified in this section.

Where terms are not defined, they shall have their ordinarily accepted meanings within the context with which they are used. Webster's Third New International Dictionary of the English Language, Unabridged, Copyright 1961, shall be considered as providing ordinarily accepted meanings.

Words used in the singular include the plural and the plural the singular. Words used in the masculine gender include the feminine and the feminine the masculine.
"Accepted for construction," means as to materials, types of construction, equipment and systems, refers to the acceptance by the Building Official as the result of investigation and/or tests conducted by him, or by reason of accepted principles or tests by recognized authorities, technical or scientific organizations.
"Addition" means an extension or increase in floor area or height of a building or structure. "Alter" or "alteration" means any change or modification in construction or building service equipment. "Approved agency" means an established and recognized agency regularly engaged in conducting tests or furnishing inspection services, when such agency has been approved by the Building Official. "Building" means any structure used or intended for supporting or sheltering and use or occupancy. "Building Code" or "Building Standards Code" means the California Building Standards Code as published by the California Building Standards Commission and promulgated in Title 24 of the California Code of Regulations (including any interim amendments thereto), and adopted in this Code herein by reference.
"Building Official" means the person charged with the administration and enforcement of this chapter and the Building Code, or the duly authorized representative of the Building Official. All references to Building Official in Article VI of this Code shall include the Building Official's designee, if any.
"Building service equipment" means it refers to the plumbing, mechanical, electrical and elevator equipment including piping, wiring, fixtures and other accessories which provide sanitation, lighting, heating, ventilation, cooling, refrigeration, firefighting and transportation facilities essential for the habitable occupancy of the building or structure for its designated use and occupancy.

Building, Existing. "Existing building" means a building erected prior to the adoption of this chapter, or one for which a legal building permit has been issued.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 1 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 649
CABO One and Two-Family Dwelling Code. This jointly sponsored code is intended to eliminate conflicts and duplications among the model codes to achieve national uniformity.

CABO Model Energy Code. This Code sets forth minimum requirements for the effective use of energy in the design of new buildings and structures and additions to existing buildings and is adopted by reference in the Uniform Building Code. "Chief Building, Electrical, Mechanical, Plumbing Inspector, Plans Examiner" means the person providing expertise for the Building Official in the designated technical code.
"Concrete Inspection Manual" means a publication on concrete to be used for reference or as a text on concrete inspection. "Dangerous Building Code" means the Uniform Building Code for the Abatement of Dangerous Buildings promulgated by the International Conference of Building Officials, as adopted by the City of Richmond in Chapter 6.10. "Electrical Code" means the National Electrical Code promulgated by the National Fire Protection Association, as adopted by the City of Richmond in Chapter 6.16. "Engineer of Record" means an engineer licensed by the State of California to practice as such and who is responsible for the preparation of plans, specifications, engineering calculations and other data submitted to the City of Richmond for the purpose of obtaining a permit under the provisions of this chapter. "Fire Code" means the California Fire Code and Fire Code Standards as published in the Building Standards Code and Title 24 of the California Code of Regulations, and adopted in this Code herein by reference. "Jurisdiction," as used in this chapter and technical codes, means the City of Richmond, California. "Listed" and "Listing" mean terms referring to equipment and materials which are shown in a list published by an approved testing agency, qualified and equipped for experimental testing and maintaining an adequate periodic inspection of current productions and whose listing states that the equipment complies with recognized safety standards. "Mechanical Code" means the California Mechanical Code as published in the Building Standards Code and Title 24 of the California Code of Regulations, and adopted in this Code herein by reference. "Occupancy" means the purpose for which a building, or part thereof, is used or intended to be used. The term "occupancy" as used in this chapter shall include the building or part thereof housing such use. "Occupant" means the person, agent, firm or corporation occupying a building or part thereof. "Owner" means any person, agent, firm or corporation having a legal or equitable interest in the property interest. "Permit" means an official document or certificate issued by the Building Official authorizing performance of a specific activity. "Person" means a natural person, his heirs, executors, administrators or assigns, and also includes a firm, partnership or corporation, its or their successors or assigns, or the agent of any of the aforesaid. "Plumbing Code" means the California Plumbing Code as published in the Building Standards Code and Title 24 of the California Code of Regulations, and adopted in this Code herein by reference. "Process equipment" means equipment used in the production or development of manufactured products. Process equipment includes the following production or research equipment: pressure vessels, heat exchangers, pumps, compressors, boilers and furnaces. Process equipment shall be designed and fabricated in conformance with nationally established and recognized industry codes and standards and is to be certified as such. Process equipment also includes its installation but does not include foundations or structures around this equipment or the connection to utility sources.
"Repair" means the reconstruction or renewal of any part of an existing building, structure or building service equipment for the purpose of its maintenance.
"Shall," as used in this chapter, means mandatory.
"Stamped plans" and/or "specifications" mean the plans and/or specifications which have been "accepted for construction" as the official plans and/or specifications to be followed on the job site. Such plans and/or specifications are to be stamped by the Building Official with the official stamp of the City of Richmond's Building Regulations Division and signed by the Building Official authorizing the issuance of a permit(s) for work to proceed.
"Structure" means that which is built or constructed, an edifice or building of any kind, or any piece of work artificially built up or composed of parts joined together in some definite manner.
"Technical Codes" means it refer to those codes adopted by the City of Richmond containing the provisions for design, construction, alteration, addition, repair, removal, demolition, use, location, occupancy and maintenance of all buildings and structures and building service equipment as herein defined.
"Uniform Building Code" means it covers the fire, life and structural safety aspects of all building and related structures. "Uniform Building Code Standards" means it presents in a compact and concise manner national test, material and special design standards referred to as the Uniform Building Code. U.B.C. STANDARDS is the Uniform Building Code Standards promulgated by the International Conference of Building Officials, as adopted by the City of Richmond in Chapter 6.04 "Uniform Building Security Code" means it establishes minimum standards to make dwelling units resistance to unlawful entry. It regulates swinging doors, sliding doors, windows and hardware in connection with dwelling units of apartment houses or one- and two-family dwellings. The code gives consideration to the concerns of police, fire and Building Officials in establishing requirements for resistance to burglary which are compatible with fire and life safety.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 2 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 650
(A)
(B)

1. 2.

3. 4.

5. 6.

7. 8.
(C)
(D)
"Uniform Code for the Abatement of Dangerous Buildings" means it sets forth orderly procedures for remedying dangerous buildings. This Code covers all structures and may be used to supplement the Building Code and State Housing Code. "Uniform Fire Code and Uniform Fire Code Standards" means it sets out provisions necessary for fire prevention while achieving uniformity in terms and requirements with other codes published by the conference. The Code is sponsored jointly by the Western Fire Chiefs Association and the International Conference of Building Officials, as adopted by the City of Richmond in Chapter 8.16 of this Code. "Uniform Housing Code" means it provides for the conservation and rehabilitation of housing compatible with the Uniform Building Code; meets Federal Workable Program requirements and is sponsored by the International Conference of Building Officials, as adopted by the City of Richmond in Chapter 6.24. "Uniform Mechanical Code" means it contains requirements for the installation and maintenance of heating, ventilating, cooling and refrigeration systems. This publication is sponsored jointly by the International Conference of Building Officials and the International Association of Plumbing and Mechanical Officials.
"Uniform Plumbing Code," means published by the International Association of Plumbing and Mechanical Officials, the Uniform Plumbing Code covers all aspects of plumbing, including requirements for plumbing materials, and IAPMO installation standards. It is endorsed by the ICBO. "Uniform Sign Code" means dedicated to the development of better sign regulation. Its requirements pertain to all signs and sign construction attached to buildings and is sponsored by the International Conference of Building Officials, as adopted by the City of Richmond in Chapter 4.04 of this Code.
"Valuation" or "value of buildings," means as applied to a building and its building service equipment, shall be the established cost to replace the building and its building service equipment in kind, based on current replacement costs. "Valuation" or "value of structures," means as applied to a structure and its process and/or service equipment, shall be the estimated cost to replace the structure and its process and service equipment in kind, based on current replacement costs. (Amended by Ordinance Nos. 11-94 N.S., 4-06 N.S. and 18-06 N.S.)

6.02.030 - Purpose.

The purpose of this chapter is to provide for the administration and enforcement of the technical codes adopted by the City of Richmond and to provide for and promote the health, safety and welfare of the general public, and not to create or otherwise establish or designate any particular class or group of persons who will or should be especially protected or benefitted by the terms of this chapter of the technical codes.

6.02.040 - Scope.

The provisions of this chapter shall serve as the administrative, organizational and enforcement rules and regulations for the technical codes which regulate the site preparation, construction, alteration, moving, demolition, repair, use and occupancy of buildings, structures and building service equipment within the City of Richmond.

6.02.050 - Existing buildings, structures and equipment.

General. Buildings, structures and their building service equipment to which additions, alterations or repairs are made shall comply with all the requirements of the technical codes for new facilities, except as specifically provided in this section.

Additions, Alterations or Repairs.

Additions, alterations or repairs may be made to any building or structure without requiring the existing building or structure to comply with all the requirements of this chapter, provided the addition, alteration or repair conforms to that required for a new building or structure, and the capability of the existing building or structure to resist all lateral forces to which it may be subjected has been demonstrated.

Additions or alterations shall not be made to an existing building or structure which will cause the existing building or structure to be in violation of any of the provisions of this chapter nor shall such additions or alterations cause the existing building or structure to become unsafe. An unsafe condition shall be deemed to have been created if an addition or alteration will cause the existing building or structure to become structurally unsafe or overloaded; will not provide adequate egress in compliance with the provisions of this chapter or will obstruct existing exits; will create a fire hazard; will reduce required fire resistance or will otherwise create conditions dangerous to human life.

Any altered building which involves a change in use or occupancy, shall not exceed the height, number of stories and the area permitted for new buildings.

Any new building plus additions shall not exceed the height, number of stories and area specified for new buildings.

Additions or alterations shall not be made to an existing building or structure when such existing building or structure is not in full compliance with the provisions of this chapter except when such addition or alteration will result in the existing building or structure being no more hazardous based on safety and sanitation, than before such additions or alterations are undertaken.

Alterations or repairs to an existing building or structure which are nonstructural and do not adversely affect any structural member or any part of the building or structure having required fire resistance may be made with the same materials of which the building or structure is constructed. The installation or replacement of glass shall be as required for new installations.

Minor additions, alterations and repairs to existing building service equipment installations may be made in accordance with the technical code in effect at the time the original installation was made, subject to the approval of the Building Official, and provided such additions, alterations and repairs will not cause the existing building service equipment to become unsafe, unsanitary or overloaded.

Structural alterations intended to improve the resistance to lateral forces due to earthquakes in existing building may be made without full compliance with the provisions for earthquake-resistant design as specified in the technical codes.

Existing Installations. Building service equipment lawfully in existence at the time of the adoption of the technical codes may have their use, maintenance or repair continued if the use, maintenance or repair is in accordance with the original design and no hazard to life, health or property has been created by such building service equipment.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 3 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 651
(E)
(F)
(G)

1. 2.

3. (1)
(2)
(3)
(4)
(5)
(A)
(B)
(C)
(A)

1. 2.

Existing Occupancy. Buildings in existence at the time of the adoption of the Building Code may have their existing use or occupancy continued if such use or occupancy was legal at the time of the adoption of the Building Code, provided such continued use is not dangerous to life, health and safety. Any change of use, occupant or occupancy of any existing building or structure shall comply with the provisions of Section 6.02.240 of this chapter and the Building Code.

Maintenance. All buildings, structures and building service equipment, existing and new, and all parts thereof shall be maintained in a safe and sanitary condition. All devices or safeguards which are required by the technical codes shall be maintained in conformance with the technical code under which installed. The owner or his designated agent shall be responsible for the maintenance of buildings, structures and their building service equipment. To determine compliance with this subsection, the Building Official may cause any structure to be reinspected.

Moved Buildings and Temporary Buildings. Buildings, structures and their building service equipment moved into or within the City of Richmond shall comply with the provisions of the technical codes for buildings or structures and their building service equipment.

Temporary structures such as reviewing stands and other miscellaneous structures, sheds, canopies or fences used for the protection of the public around and in conjunction with construction work may be erected by special permit from the Building Official for a limited period of time. Such buildings or structures need not comply with the type of construction or fire-resistive time periods required by the Building Code. Temporary buildings or structures shall be completely removed upon the expiration of the time limit stated in the permit.

Historic Buildings. Repairs, alterations and additions necessary for the preservation, restoration, rehabilitation or continued use of a building structure, or its building service equipment may be made without conformance to all the requirements of the technical codes when authorized by the Building Official, provided:

The building or structure has been designated by official action of the City Council as having special historical or architectural significance.

Any unsafe conditions as described in this chapter are corrected.

The restored building or structure and its building service equipment will be no more hazardous based on safety and sanitation than the existing building.

6.02.060 - Conflicting provisions.

Wherever conflicting provisions or requirements occur between this chapter and the technical codes; or between the technical codes; or between any other municipal code section, the following shall apply:

This Administrative Code shall prevail in the administration of all codes relating to construction within the City of Richmond.

The various technical codes shall prevail in their technical field (i.e., the California Building Code shall prevail over other codes in the area of occupancies, types of construction, quality and design of the materials and methods of construction of buildings and structures, and permit requirements. The National Electric Code shall prevail over other codes as relating to electrical work, etc.).

Where conflicts occur within a technical code, those provisions providing the greater safety shall govern. In other conflicts where safety or sanitation are not involved, the most restrictive provisions shall govern.

Where in any specific case, different sections within any of the technical codes specify different materials, methods of construction or other requirements, the most restrictive shall govern. Where there is a conflict between a general requirement and a specific requirement, the specific requirement shall be applicable.

Changes, additions and deletions to any technical code can only occur within that particular code which governs the technical field which is being changed, added to or deleted from.
(Amended by Ordinance No. 18-06 N.S.)

6.02.070 - Alternate materials and methods of construction.

The provisions of the technical codes are not intended to prevent the use of any material or method of construction not specifically prescribed by the technical codes, provided any alternate has been approved and its use authorized by the Building Official.

The Building Official may approve any alternate, provided he finds that the proposed design is satisfactory and complies with the provisions of the technical codes and that the material, method or work offered is, for the purpose intended, at least the equivalent of that prescribed in the technical codes in suitability, strength, effectiveness, fire resistance, durability, safety and sanitation.

The Building Official shall require that sufficient evidence or proof be submitted to substantiate any claims that may be made regarding its use. The details of any action granting approval of an alternate shall be recorded and entered in the files of the code enforcement agency.

6.02.080 - Modifications.

Whenever there are practical difficulties involved in carrying out the provisions of the technical codes, the Building Official may grant modifications for individual cases, provided he shall first find that a special individual reason makes the strict letter of the technical code impractical and the modification is in conformity with the intent and purpose of the technical code, and that such modification does not lessen safety or health requirements or any degree of structural integrity. The details of actions granting modifications shall be recorded and entered in the files of the code enforcement agency.

6.02.090 - Tests.

Whenever there is insufficient evidence of compliance with any of the provisions of the technical codes or evidence that materials or construction do not conform to the requirements of the technical codes, the Building Official may require tests as evidence of compliance to be made at no expense to the City of Richmond.

Test methods shall be as specified by the technical codes or by other recognized test standards. In the absence of recognized and accepted test methods for the proposed alternate, the Building Official shall determine test procedures.

All tests shall be made by an approved agency. Reports of such tests shall be retained by the Building Official for the period required for the retention of public records.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 4 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 652
(A)
(B)
(a)
(b)
(c)
(d)
(e)
(f)
(g)
(h)
(i)
(j)

6.02.100 - Authority.

Creation of Enforcement Agency. There is established in the City of Richmond a code enforcement agency which shall be under the administration and operational control of the Building Official.

General. Whenever the term or title "administrative authority," "responsible official," "Building Official," "Chief Inspector," "Code Enforcement Officer," "Superintendent of Inspection Services," or other similar designation is used herein or in any of the technical codes or in any other law, ordinance or regulation, it shall be construed to mean the Building Official as designated by the Director of Public Works of the City of Richmond.

6.02.110 - Powers and duties of Building Official.

General. The Building Official is authorized and directed to enforce all the provisions of this chapter and the referenced technical codes.

The Building Official shall have the power to render interpretations of this chapter and the referenced technical codes, and to adopt and enforce rules and regulations supplemental to this chapter as he may deem necessary in order to clarify the application of the provisions of this chapter and the technical codes. Such interpretations, rules and regulations shall be in conformity with the intent and purpose of this chapter and the technical codes.

Deputies. In accordance with prescribed procedures and with the approval of the appointing authority, the Building Official may appoint such number of technical officers and inspectors and other employees as shall be authorized from time to time. He may deputize such inspectors or employees as may be necessary to carry out the functions of the code enforcement agency.

Right-of-Entry. Whenever necessary to make an inspection to enforce any of the provisions of this chapter and the technical codes, or whenever the Building Official or his authorized representative has reasonable cause to believe that there exists in any building or upon any premises any condition or code violation which makes such building or premises unsafe, dangerous or hazardous, the Building Official or his authorized representative may enter such building or premises at all reasonable times to inspect the same or to perform any duty imposed upon the Building Official by such codes, provided that if such building or premises be occupied, he shall first present proper credentials and request entry; and if such building or premises be unoccupied, he shall first make a reasonable effort to locate the owner or other persons having charge or control of the building or premises and request entry. Should entry be refused, the Building Official or his authorized representative shall have recourse to every remedy provided by law to secure entry.

Stop Orders. Whenever any work is being done contrary to the provisions of this chapter and the technical codes, the Building Official may order the work stopped by notice in writing served on any persons engaged in the doing or causing such work to be done, and any such persons shall forthwith stop such work until authorized by the Building Official to proceed with the work.

Occupancy Violations. Whenever any building or structure or building service equipment therein regulated by this chapter and the technical codes are being used contrary to the provisions of such codes, the Building Official may order such use discontinued and utility service disconnected by written notice served on any person causing such use to be continued. Such person shall discontinue the use within the time prescribed by the Building Official after receipt of such notice to make the structure, or portion thereof, comply with the requirements of such codes. Utility disconnection authorized by this section shall be pursuant to the provisions of subsection (f) of this section.

Authority to Disconnect Utilities. The Building Official or his authorized representative shall have the authority to order the disconnection and/or to disconnect any utility service or energy supplied to the building, structure or building service equipment therein regulated by this chapter or the technical codes in case of emergency where necessary to eliminate an immediate hazard to life or property. The Building Official shall notify the City Attorney and the utility company prior to disconnection and whenever possible notify the owner or occupant of the building, structure or building service equipment, in writing, of such disconnection prior to disconnect.

Authority to Condemn Building Service Equipment. Whenever the Building Official ascertains that any building service equipment regulated in the technical codes has become hazardous to life, health, property or becomes unsanitary, he shall order in writing that such equipment either be removed or restored to a safe or sanitary condition, whichever is appropriate.

The written notice itself shall fix a time limit for compliance with such order. No person shall use or maintain defective building service equipment after receiving such notice.

When such equipment or installation is to be disconnected, a written notice of such disconnection and causes therefore shall be given within 24 hours to the serving utility, the owner and occupant of such building, structure or premises. Utility disconnection authorized by this section shall be pursuant to the provisions of subsection (f) of this section.

When any building service equipment is maintained in violation of the technical codes and in violation of any notice issued pursuant to the provisions of this section, the Building Official shall institute any appropriate action to prevent, restrain, correct or abate such violation.

Connection After Order to Disconnect. No person shall make connections from any energy, fuel or power supply nor supply energy or fuel to any building service equipment which has been disconnected or ordered to be disconnected by the Building Official or the use of which has been ordered to be discontinued by the Building Official until the Building Official authorizes the reconnection and use of such equipment.

Liability. The Building Official, or his authorized representative charged with the enforcement of this chapter and the technical codes, acting in good faith and without malice in the discharge of his duties, shall not thereby render himself personally liable for any damage that may accrue to persons or property as a result of any act or by reason of any act or omission in the discharge of his duties. Any suit brought against the Building Official or employee because of such act or omission performed by him in the enforcement of any provision of such codes shall be defended by the City of Richmond until final termination of such proceedings, and any judgment resulting therefrom shall be assumed by the City of Richmond.

This chapter, the technical codes and other laws shall not be construed to relieve from or lessen the responsibility of any person owning, operating or controlling any building, structure or building service equipment therein for any damages to persons or property caused by defects, nor shall the Public Works Department or its parent jurisdiction, the City of Richmond be held as assuming any such liability by reason of the inspections authorized by such laws or approvals issued under such laws.

Cooperation of Other Officials and Officers. The Building Official may request, and shall receive so far as is required in the discharge of his duties, the assistance and cooperation of other officials of the City of Richmond. (Amended by Ordinance No. 18-06 N.S.)
Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 5 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 653
(a)
(b)
(c)
(d)
(a)
(b)
(c)
(d)
(e)
(a)
(b)
(a)
(b)
(1)
(A)
(B)
(C)
(D)
(E)
(F)
(G)

6.02.120 - Unsafe buildings, structures or equipment.

All buildings or structures regulated by this chapter and the technical codes which are structurally inadequate or have inadequate egress, or which constitute a fire hazard, or are otherwise dangerous to human life are, for the purpose of this section, unsafe.

Building service equipment regulated by such codes, which constitutes a fire, electrical or health hazard, or insanitary condition, or is otherwise dangerous to human life is, for the purpose of this section, unsafe. Any use of buildings, structures or building service equipment constituting a hazard to safety, health or public welfare by reason of inadequate maintenance, dilapidation, obsolescence, fire hazard, disaster, damage or abandonment is, for the purpose of this section, an unsafe use.

Parapet walls, cornices, spires, towers, tanks, statuary and other appendages or structural members which are supported by, attached to, or a part of a building and which are in deteriorated condition or otherwise unable to sustain the design loads which are specified in the Building Code are hereby designated as unsafe building appendages.

All unsafe buildings, structures or appendages and building service equipment are hereby declared to be public nuisances and shall be abated by repair, rehabilitation, demolition or removal in accordance with the procedures set forth in the Dangerous Buildings Code or such alternative procedure as may be adopted by the City of Richmond. As an alternative, the Building Official or other employee or official of the City of Richmond as designated by the City Council, may institute any other appropriate action to prevent, restrain, correct or abate the violation.

6.02.130 - Board of Appeals.

General. There is created a Board of Appeals to hear appeals of decisions, orders or determinations of the Building Official, or his or her designee, regarding the application and interpretations of the technical codes, as well as the soundness or habitability of all new or existing buildings, dwellings and structures, including all alterations, additions, repair, demolition, and moving thereof. The Board shall also hear appeals of all notices and orders issued by the Building Official, or his or her designee.

Board Members. The Board shall consist of five members who are qualified by experience and training to pass upon matters pertaining to building construction in conformance with the California Building Standards Code and applicable local ordinances, including the Uniform Code for Abatement of Dangerous Buildings. Board members shall not be City employees and shall be appointed by and serve at the pleasure of the City Manager. A quorum for the conduct of business shall be three.

Appeals. Except as otherwise provided by law, any person, firm, or corporation adversely affected by a decision, order, or determination by the Building Official, or his or her designee, relating to the application of building standards published in the California Building Standards Code, the Uniform Code for Abatement of Dangerous Buildings, or any lawfully enacted City ordinance, may appeal the issue for resolution to the Board of Appeals.

Form of Appeal. Appeals of notice, orders and determinations of the Building Official, or his or her designee, shall follow the requirements set forth in Chapter 5 (Appeal) of the Uniform Code for Abatement of Dangerous Buildings. All appeals shall be filed within thirty (30) days from the date of the service of such order or action of the Building Official; provided, however, that if the building or structure is in such condition as to make it immediately dangerous to the life, limb, property or safety of the public or adjacent property and is ordered vacated, such appeal shall be filed within ten (10) days from the date of service of the notice, order or determination of the Building Official, or his or her designee.

Decisions of the Board may be challenged only through the courts. Failure to comply with the appeal deadline acts as a waiver of all appeal rights and constitutes a failure to exhaust administrative remedies.

Hearing on Appeal. The Board of Appeals shall conduct a hearing within sixty (60) days from the date the appeal is filed. The Board shall render a written decision within fifteen (15) business days from the date the hearing is closed. (Amended by Ordinance No. 9-06 N.S.; Ord. No. 14-10 N.S., § 1, 4-6-2010)

6.02.140 - Violations—Penalties.

It is unlawful and a misdemeanor for any person, firm or corporation to erect, construct, enlarge, alter, repair, move, improve, remove, convert, demolish, equip, use, occupy or maintain any building, structure or building service equipment, or to cause, suffer or permit the same to be done, in violation of any provision of state or local law, including the California Building Standards Code, the Uniform Code for Abatement of Dangerous Buildings or the Richmond Municipal Code.

Cumulative Remedies. The rights and remedies provided herein are cumulative and in addition to any other rights and remedies provided by law.
(Amended by Ordinance No. 11-94 N.S.; Ord. No. 14-10 N.S., § 1, 4-6-2010)

6.02.150 - Permits.

Permits Required. Except as specified in subsection (b) of this section, no building, structure or service equipment regulated by this chapter and the technical codes shall be erected, constructed, enlarged, altered, repaired, moved, improved, removed, converted or demolished unless a separate, appropriate permit for each building, structure or service equipment has first been obtained from the Building Official.

Exempted Work:

Building Permits. A building permit shall not be required for the following:

One-story detached accessory buildings used as tool and storage sheds, playhouses and similar uses, provided the projected roof area does not exceed 120 square feet;
Fences not over 6 feet high;
Oil derricks;
Movable cases, counters and partitions not over 5 feet high; Retaining walls which are not over 4 feet in height measured from the bottom of the footing to the top of the wall, unless supporting a surcharge or impounding flammable liquids; Water tanks supported directly upon grade if the capacity does not exceed 5,000 gallons and the ratio of height to diameter or width does not exceed two to one;
Platforms, walks and driveways not more than 30 inches above grade and not over any basement or story below; Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 6 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 654
(H)
(I)
(J)
(K)
(L)
(2)
(A)
(B)
(C)
(3)
(A)
(B)
(C)
(D)
(E)
(F)
(G)
(H)
(I)
(J)
(K)
(L)
(M)
(N)
(O)
(4)
(A)
(B)
(C)
(D)
(E)
(F)
(G)
(H)
(I)
(A)

1. 2.

3. 4.

5. 6.

7. 8.
(B)
Painting, papering and similar finish work;
Temporary motion picture, television and theater stage sets and scenery; Window awnings supported by an exterior wall of Group R, Division 3, and Group M occupancies when projecting not more than 54 inches;
Prefabricated swimming pools accessory to a Group R, Division 3 occupancy in which the pool walls are entirely above the adjacent grade and if the capacity does not exceed 5,000 gallons; The replacement of any window with another window of the same shape and size.

Plumbing Permits. A plumbing permit shall not be required for the following:

The stopping of leaks in drains, soil, waste or vent pipe, provided, however, that should any concealed trap, drainpipe, soil, waste or vent pipe become defective and it becomes necessary to remove and replace the same with new material, the same shall be considered as new work and a permit shall be procured and inspection made as provided in this chapter; The clearing of stoppages or the repairing of leaks in pipes, valves or fixtures, nor for the removal and reinstallation of water closets, provided such repairs do not involve or require the replacement or rearrangement of valves, pipes or fixtures; Equipment and/or appliances not connected directly or indirectly to utility service.

Electrical Permits. An electrical permit shall not be required for the following:

Portable motors or other portable appliances energized by means of a cord or cable having an attachment plug end to be connected to an approved receptacle when that cord or cable is permitted by the Electrical Code; Repair or replacement of fixed motors, transformers or fixed approved appliances of the same type and rating in the same location;
Temporary decorative lighting;
Repair or replacement of current-carrying parts of any switch, contractor or control device; Reinstallation of attachment plug receptacles, but not the outlets therefor; Repair or replacement of any overcurrent device of the required capacity in the same location; Repair or replacement of electrodes or transformers of the same size and capacity for signs or gas tube systems; Taping joints;
Removal of electrical wiring;
Temporary wiring for experimental purposes is suitable experimental laboratories; The wiring for temporary theater, motion picture of television stage sets; Electrical wiring, devices, appliances, apparatus or equipment operating at less than 25 volts and not capable of supplying more than 50 watts of energy;
Low-energy power, control and signal circuits of Classes II and III as defined in the Electrical Code; The installation, alteration or repair of electrical wiring, apparatus or equipment or the generation, transmission, distribution or metering of electrical energy or in the operation of signals or the transmission of intelligence by a public or private utility in the exercise of its function as a serving utility;
Equipment and/or appliances not connected directly or indirectly to utility service.

Mechanical Permits. A mechanical permit shall not be required for the following:

Any portable heating appliance;
Any portable ventilating equipment;
Any portable cooling unit;
Any portable evaporative cooler;
Any closed system of steam, hot or cold water piping within any heating or cooling equipment regulated by the Mechanical Code;
Replacement of any component part of assembly of an appliance which does not alter its original approval and complies with other applicable requirements of the technical codes;
Any refrigerating equipment which is part of the equipment for which a permit has been issued pursuant to the requirements of the technical codes;
Any unit refrigerating system as defined in the Mechanical Code; Equipment and/or appliances not connected directly or indirectly to utility service. (Amended by Ordinance Nos. 11-94 N.S. and 4-06 N.S.)

6.02.160 - Application for permit.

Application. To obtain a permit, the applicant shall first file an application therefor in writing on a form furnished by the Public Works Department for that purpose. Every such application shall:

Identify and describe the work to be covered by the permit for which application is made.

Describe the land on which the proposed work is to be done by legal description, street ad-dress or similar description that will readily identify and definitely locate the proposed building or work.

Indicate the use or occupancy for which the proposed work is intended.

Be accompanied by plans and diagrams, computations and specifications and other data as required in subsection (B) of this section.

State the valuation of any new building or structure or any addition, remodeling or alteration to an existing building.

Be signed by permittee, or his authorized agent.

Give such other data and information as may be required by the Building Official.

Be accompanied by a plat of the survey of the land as required in subsection (D) of this section.

Plans and Specifications. Plans, engineering calculations, diagrams and other data shall be submitted in three or more sets with each application for a permit. The Building Official may require plans, computations and specifications to be prepared and designed by an engineer or architect licensed by the state to practice as such.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 7 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 655
(C)
(D)

1. 2.

3. 4.

5. 6.

7. 1.

2. (E)
(a)
(b)
(c)
(d)
Exception: The Building Official may waive the submission of plans, calculations, etc., if he finds that the nature of the work applied for is such that reviewing of plans is not necessary to obtain compliance with this chapter or the work is being done under Section 6.02.200 "Certified Inspection Program" and Section 6.02.220 "Engineer or Architect Requirements." Information on Plans and Specifications. Plans and specifications shall be drawn to scape upon substantial paper and shall be of sufficient clarity to indicate the location, nature and extent of the work proposed and show in detail that it will conform to the provisions of the technical codes and all relevant laws, ordinances, rules and regulations.

Plans for buildings more than two stories in height of other than Groups R, Division 3 and M Occupancies shall indicate how required structural and fire-resistive integrity will be maintained where a penetration will be made for electrical, mechanical, plumbing and communication conduits, pipes and similar systems.

Plat of a Property Survey. With each application for a building permit, three copies of a plat of a survey of the property shall be submitted. The survey upon which the plat is based shall have been made by a licensed land surveyor or registered civil engineer of the State of California and shall be signed by him and endorsed with his license or certificate number. Elevations shown thereon shall be to the Mean Sea Level Datum of 1929 established by the U.S. Coast and Geodetic Survey unless the nearest City of Richmond bench mark is more than five hundred feet (500ƍ) from the property or to such other datum as is approved by the City Engineer.

The plat shall show the following information:

The exterior lines of said property to be improved defined by appropriate stakes or marks.

The elevations of such stakes or marks.

The location of said exterior lines by map or deed distance to the nearest intersecting street.

Ties to existing permanent monuments.

Contours of not more than two-foot (2ƍ) intervals except that five-foot (5ƍ) intervals may be used when the slope of lot exceeds one foot (1ƍ) in five (5) in any direction. Such contours shall extend to the center of the street when said street is unimproved.

The location of every existing building or structure on the property.

The location of reserves and the location and elevation of existing curbs, sidewalks, center line of pavement, main sewers, waterways, drains and culverts, affecting the property.

Exceptions: When authorized by the Building Official, plats of surveys need not be submitted for the following:

Minor additions and alterations to existing structures or minor detached accessory buildings.

Areas located more than sixty feet (60ƍ) beyond the proposed work for land zones M-2 or M-3 and under one ownership.

Expiration of Plan Review. Applications for which no permit is issued within 180 days following the date of application shall expire by limitation, and plans and other data submitted for review may thereafter be returned to the applicant or destroyed by the Building Official. The Building Official may extend the time for action by the applicant for a period not exceeding 180 days upon request by the applicant showing that circumstances beyond the control of the applicant have prevented action from being taken. No application shall be extended more than twice. In order to renew action on an application after expiration, the applicant shall resubmit plans and pay a new plan review fee.

6.02.170 - Permits issuance.

Issuance. The application, plans and specifications, and other data, filed by an applicant for permit shall be reviewed by the Building Official.

Such plans may be reviewed by other departments of this jurisdiction to verify compliance with any applicable laws under their jurisdiction. If the Building Official finds that the work described in an application for a permit and the plans, specifications and other data filed therewith conform to the requirements of this chapter and the technical codes and other pertinent laws and ordinances, and that the fees specified in the City's adopted fee schedule have been paid, he shall issue a permit therefor to the applicant.

When the Building Official issues the permit where plans are required, he shall endorse in writing and stamp the plans and specifications "ACCEPTED, City of Richmond, by ____________." Such stamped plans and specifications shall not be changed, modified or altered without authorization from the Building Official, and all work shall be done in accordance with the stamped plans.

The Building Official may issue a permit for the construction of part of a building, structure or building service equipment before the entire plans and specifications for the whole building, structure or building service equipment have been submitted or approved, provided, adequate information and detailed statements have been filed complying with all pertinent requirements of the technical codes. The holder of such permit shall proceed at his own risk without assurance that the permit for the entire building, structure or building service will be granted.

Retention of Plans. One set of stamped plans and specifications shall be returned to the applicant and shall be kept on the site of the building or work at all times during which the work authorized thereby is in progress. One set of stamped plans, specifications and computations shall be retained by the Building Official for at least ninety (90) days after final approval and inspection of the work. After the retention period the Building Official shall cause to be delivered to the address of the permitted work or to the owner of such plans, specifications and records which are not required by law to be kept as official records.

Validity of Permit. The issuance of a permit or approval of plans and specifications shall not be construed to be a permit for, or an approval of, any violation of any of the provisions of this chapter or the technical codes, or of any other ordinance of the jurisdiction.

No permit presuming to give authority to violate or cancel the provisions of these laws shall be valid.

The issuance of a permit based upon plans, specifications and other data shall not prevent the Building Official from thereafter requiring the correction of errors in said plans, specifications and other data, or from preventing building operations being carried on thereunder when in violation of these Codes or of any other ordinances of this jurisdiction.

Expiration. Every permit issued by the Building Official under the provisions of the technical codes shall expire by limitation and become null and void; if the work is not completed within 365 days; or if the building or work authorized by such permit is not commenced within 180 days from the date of such permit; or if the building or work authorized by such permit has not had a satisfactory inspection after the work has commenced for a period of 180 days. Before such work can be recommenced, a new permit shall be first obtained and the fee for such new Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 8 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 656
(e)
(f)
(A)
(B)
(C)
(D)

1. 2.
(E)

1. 2.

3. (F)
(A)
(B)
(C)
permit shall be one-half the amount required for a new permit for such work, provided no changes have been made or will be made in the original plans and specifications for such work; and provided further that such suspension or abandonment has not exceeded one year.

Any permittee holding an unexpired permit may apply for an extension of the time within which he may commence or complete work under that permit when he is unable to commence or complete work within the time required by this section for good and satisfactory reasons. The Building Official may extend the time for action by the permittee for a period not exceeding 180 days upon written request by the permittee showing that circumstances beyond the control of the permittee have prevented action from being taken. No permit shall be extended more than twice once. In order to renew action on a permit after expiration, the permittee shall pay a new full permit fee.

Utility Service. Until all work and inspections are completed and during the course of construction all utility service to the property shall be temporary construction utility service and/or temporary occupancy utility service. Temporary utility service is at the discretion of the Building Official.

Suspension or Revocation. The Building Official may, in writing, suspend or revoke a permit issued under the provisions of this chapter and the technical codes whenever the permit is issued in error or on the basis of incorrect information supplied, or in violation of any ordinance, regulation or any of the provisions of law.
(Amended by Ordinance No. 9-06 N.S.)

6.02.180 - Fees.

General. Fees shall be assessed in accordance with the provisions set forth in the fee schedule adopted by resolution by the City of Richmond.

Permit Fees. The fee for each permit shall be as set forth in City's adopted fee schedule.

For fee based on valuation the determination of value or valuation under any of the provisions of these Codes shall be made by the Building Official. The value to be used in computing the building permit and building plan review fees shall be the total value of all construction work for which the permit is issued as well as all finish work, painting, roofing, electrical, plumbing, heating, air-conditioning, elevators, fire-extinguishing systems and any other permanent equipment.

Plan Review Fees. When a plan or other data are required to be submitted by subsection (B) of Section 6.02.160 a plan review fee shall be paid at the time of submitting plans and specifications for review. Said plan review fee for buildings or structures shall be as adopted in the City's fee schedule.

Where plans are incomplete or changed so as to require additional plan review, an additional plan review fee shall be charged at the rate adopted in the City's fee schedule.

The plan review fees specified in this subsection are separate from any permit fees specified in subsection (B) and are in addition to the permit fees.

Work Without a Permit:

Investigation. Whenever any work for which a permit is required by this chapter has been commenced without first obtaining said permit, a special investigation shall be made before a permit may be issued for such work.

Fee. An investigation fee, in addition to the permit fee, shall be collected whether or not a permit is then or subsequently issued. The investigation fee shall be equal to the amount of the permit fee required by this chapter. The minimum investigation fee shall be the same as the minimum fee set forth in the City's adopted fee schedule. The payment of such investigation fee shall not exempt any person from compliance with all other provisions of either this chapter or the technical codes nor from any penalty prescribed by law.

Fee Refunds. The Building Official shall not authorize the refunding of any fee paid except upon written application filed by the original permittee not later than 180 days after the date of fee payment.

The Building Official may authorize the refunding of any fee paid hereunder which was erroneously paid or collected.

The Building Official may authorize the refunding of not more than 80 percent of the permit fee paid when no work has been done under a permit issued in accordance with this chapter.

The Building Official may authorize the refunding of not more than 80 percent of the plan review fee paid when an application for a permit for which a plan review fee has been paid is withdrawn or canceled before any plan checking is done.

Transfer of Permit. The Building Official may authorize the transferring of a permit upon written request of the owner and the permit applicant.

Permit transfers shall be charged a filing fee plus a fee of ten percent (10%) of the original permit fee including plan check fees.

6.02.190 - Inspections.

General. All construction or work for which a permit is required shall be subject to inspection by the Building Official and all such construction or work shall remain accessible and exposed for inspection purposes until approved by the Building Official. In addition, certain types of construction shall have special inspection by special inspectors as specified in Section 6.02.210 It shall be the duty of the permit applicant to cause the work to remain accessible and exposed for inspection purposes. Neither the Building Official nor his jurisdiction shall be liable for expense entailed in the removal or replacement of any material required to allow inspection.

A survey of the lot may be required by the Building Official to verify that the structure is located in accordance with stamped plans.

Inspection Record Card. Work requiring a building permit shall not be commenced until the permit holder or his agent shall have posted or otherwise made available the inspection record card such as to allow the Building Official to conveniently make the required entries thereon regarding inspection of the work. This card shall be maintained available by the permit holder until final approval has been issued by the Building Official.

Inspection Requests. It shall be the duty of the person doing the work authorized by a permit to notify the Building Official that such work is ready for inspection. The Building Official may require that every request for inspection be filed at least one working day before such inspection is desired. Such request may be in writing or by telephone at the option of the Building Official.

It shall be the duty of the person requesting any inspections required either by this chapter or the technical codes to provide access to and means for inspection of such work.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 9 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 657
(D)
(E)

1. 2.

3. 4.

5. (F)

1. 2.
(G)
(H)

1. 2.

3. 4.

5. (A)

1. 1.

2. 3.

4. 2.

3. 4.

Approval Required. No work shall be done beyond the point indicated in each successive inspection without first obtaining the approval of the Building Official. The Building Official, upon notification, shall make the requested inspections and shall either indicate that portion of the construction is satisfactory as completed or shall notify the permit holder or his agent wherein the same fails to comply with this chapter or the technical codes. Any portions which do not comply shall be corrected and such portion shall not be covered or concealed until authorized by the Building Official.

There shall be a final inspection and approval of all buildings and building service equipment when completed and ready for occupancy or use.

Required Building Inspections. Reinforcing steel or structural framework of any part of any building or structure shall not be covered or concealed without first obtaining the approval of the Building Official.

The Building Official, upon notification, shall make the following inspections:

Foundation Inspection: To be made after excavations for footings are complete and any required reinforcing steel is in place. For concrete foundations, any required forms shall be in place prior to inspection. All materials for the foundation shall be on the job, except where concrete is ready mixed in accordance with U.B.C. Standard No. 26-13, the concrete need not be on the job. Where the foundation is to be constructed of approved treated wood, additional inspections may be required by the Building Official.

Concrete Slab or Under-Floor Inspection: To be made after all in-slab or under-floor building service equipment, conduit, piping accessories, insulation and other ancillary equipment items are in place but before any concrete is placed or floor sheathing installed, including the subfloor.

Frame Inspection: To be made after the roof, all framing, fire blocking and bracing are in place and all pipes, chimneys and vents are complete and the rough electrical, plumbing, and heating wires, pipes, and ducts are approved.

Lath and/or Wallboard Inspection: To be made after all lathing and wallboard, interior and exterior, is in place but before any plastering is applied or before wallboard joints and fasteners are taped and finished.

Final Inspection: To be made after finish grading and the building is completed and ready for occupancy.

Required Building Service Equipment Inspections:

General. All building service equipment for which a permit is required by this chapter shall be inspected by the Building Official. No portion of any building service equipment intended to be concealed by any permanent portion of the building shall be concealed until inspected and approved. When the installation of any building service equipment is complete, an additional and final inspection shall be made. Building service equipment regulated by the technical codes shall not be connected to the water, fuel or power supply or sewer system until authorized by the Building Official.

Operation of Building Service Equipment. The requirements of this section shall not be considered to prohibit the operation of any building service equipment installed to replace existing building service equipment serving an occupied portion of the building in the event a request for inspection of such building service equipment has been filed with the Building Official not more than 48 hours after such replacement work is completed, and before any portion of such building service equipment is concealed by any permanent portion of the building.

Other Inspections. In addition to the required inspections specified above, the Building Official may make or require other inspections of any construction work to ascertain compliance with the provisions of this chapter or technical codes and other laws which are enforced by the code enforcement agency.

Reinspections:

A reinspection fee may be assessed for each inspection or reinspection when such portion of work for which inspection is called is not complete or when corrections called for are not made.

This subsection is not to be interpreted as requiring reinspection fees the first time a job is rejected for failure to comply with the requirements of the technical codes, but as controlling the practice of calling for inspections before the job is ready for such inspection or reinspection.

Reinspection fees may be assessed when the permit card is not properly posted on the work site; when the stamped plans are not readily available to the inspector for failure to provide access on the date for which inspection is requested; or for deviating from plans requiring the approval of the Building Official.

To obtain a reinspection, the applicant shall file an application therefor in writing upon a form furnished for that purpose, and pay the reinspection fee in accordance with the fee schedule adopted by the City of Richmond.

In instances where reinspection fees have been assessed, no additional inspection of the work will be performed until the required fees have been paid.

6.02.210 - Special inspections.

General. In addition to the inspections required by Section 6.02.190 the owner shall employ one or more special inspectors who shall provide continuous inspection during construction on the following types of work:

Concrete: During the taking of test specimens and placing of all reinforced concrete and pneumatically placed concrete.

Exceptions:

Concrete for foundations conforming to the minimum requirements of Table No. 29-A of the Building Code or for Group R, Division 3 or Group M, Division 1 Occupancies, provided the Building Official finds that a special hazard does not exist.

For foundation concrete when the structural design is based on f'c no greater than 2500 psi.

Nonstructural slabs on grade, including prestressed slabs on grade when effective prestress in concrete is less than 150 pounds per square inch.

Site work concrete fully supported on earth and concrete where no special hazard exists.

Bolts Installed in Concrete: During installation of bolts and placing of concrete around such bolts when stress increases permitted by Table No. 26-G are utilized.

Ductile Moment-Resisting Concrete Frame: As required by Section 2626(h) of the Building Code.

Reinforcing Steel and Prestressing Steel:

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 10 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 658
(a)
(b)

5. (a)
(b)

1. 2.

6. 1.
(i)
(ii)

2. 7.
(1)
(2)

8. 9.

10. 11.

12. 13.
(B)
(C)

1. 2.
(D)

1. 2.

3. (E)
(F)
During all stressing and grouting of prestressed concrete.

During placing of reinforcing steel, placing of tendons and prestressing steel for all concrete required to have special inspection by Item No. 1.

Exception: The special inspector need not be present during entire reinforcing steel and prestressing steel placing operations, provided he has inspected for conformance with the stamped plans, prior to the closing of forms or the delivery of concrete to the jobsite.

Welding:

Ductile moment-resisting steel frames. As required by Section 2272(f) of the Building Code.

All structural welding, including welding of reinforcing steel.

Exceptions:

When welding is done in an approved fabricator's shop.

When approved by the Building Official, single pass fillet welds when stressed to less than 50 percent of the allowable stresses and floor and roof deck welding and welded studs when used for structural diaphragm or composite systems may have periodic inspections in accordance with Section 6.02.210(E) of this chapter. For periodic inspection, the inspector shall check qualifications of welders at the start of work and then make final inspection of all welds for compliance prior to completion of welding.

High-Strength Bolting: During all bolt installations and tightening operations.

Exceptions:

The special inspector need not be present during the entire installation and tightening operation, provided he has:

Inspected the surfaces and bolt type for conformance to plans and specifications prior to start of bolting:

And will, upon completion of all bolting, verify the minimum specified bolt tension for 10 percent of the bolts for each connection with a minimum of two bolts per connection.

In bearing-type connections when threads are not required by design to be excluded from the shear plane, inspection prior to or during installation will not be required.

Structural Masonry: During preparation of masonry wall prisms, sampling and placing of all masonry units, placement of reinforcement, inspection of grout space, immediately prior to closing of cleanouts, and during all grouting operations. Where the f'm is less than 2600 psi and special inspection stresses are used, test specimens may consist of either one prism test for each 5000 square feet of wall area or a series of tests based on both grout and mortar for the first three consecutive days and each third day thereafter.

Exceptions:

Special inspection will not be required for structures designed in accordance with the values in appropriate tables for noncontinuous inspection.

The special inspector need not provide continuous inspection during the placement of masonry units or reinforcement, provided the special inspector has inspected for conformance with the stamped plans prior to any grouting.

Reinforced Gypsum Concrete: When cast-in-place Class B gypsum concrete is mixed and placed.

Insulating Concrete Fill: During the application of insulating concrete fill when used as part of a structural system.

Exception: The special inspections may be limited to an initial inspection to check the deck surface and placement of reinforcing. The special inspector shall supervise the preparation of compression test specimens during this initial inspection.

Sprayed-On Fireproofing: As required by U.B.C. Standard No. 43-9.

Piling, Drilled Piers and Caissons: During driving and resting of piles and construction of cast-in-place drilled piles or caissons. See Items Nos. 1 and 3 for concrete and reinforcing steel inspection.

Special Grading, Excavation and Filling: During earthwork excavations, grading and filling operations inspection to satisfy requirements of Chapter 29 and Chapter 70 (Appendix) of the Building Code.

Special Cases: Work which, in the opinion of the Building Official, involves unusual hazards or conditions.

Number of Special Inspectors. There shall be a sufficient number of special inspectors present for each particular type of construction or operation to adequately perform the inspection.

Special Inspectors:

Special inspectors shall be individuals who are qualified for inspection of the particular type of construction or operation requiring special inspection.

Special inspectors shall be approved by and shall be responsible to the engineer or architect of record.

Duties and Responsibilities of the Special Inspector:

Special inspectors shall observe the work assigned for conformance with the stamped plans and specifications.

The special inspector shall furnish inspection reports to the Building Official, the engineer or architect of record, and other designated persons. All discrepancies shall be brought to the immediate attention of the builder for correction, then, if uncorrected, to the proper design authority and to the Building Official.

Special inspectors shall submit a final signed report stating that whether the work required special inspection was, to the best of their knowledge, in substantial conformance with the stamped plans and specifications.

PERIODIC SPECIAL INSPECTION. Some inspections may be made on a periodic basis and satisfy the requirements of continuous inspection, provided this periodic scheduled inspection is performed as outlined in the project plans and specifications and approved by the Building Official.

APPROVED FABRICATORS. Special inspections required by this section and elsewhere in this Code or in the technical codes shall not be required where the work is done on the premises of a fabricator registered and approved by the Building Official to perform such work without special inspection. The certificate of registration shall be subject to revocation by the Building Official if it is found that any work done pursuant to the approval is in violation of the technical codes. The approved fabricator shall submit a Certificate of Compliance that the work was Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 11 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 659

1. 2.

3. 4.
(G)
(A)

1. 2.

3. (B)
(C)
(A)
(B)
(C)
(D)
(E)
(A)

1. 2.
(B)
(C)

1. 2.

3. 4.

5. performed in accordance with the stamped plans and specifications to the Building Official and to the engineer or architect of record. The approved fabricator's qualifications shall be contingent on compliance with the following:

The fabricator has developed and submitted a detailed fabrication procedural manual reflecting key quality control procedures which will provide a basis for inspection control of workmanship at the fabricator plant.

Verification of the fabricator's quality control capabilities, plant and personnel as outlined in the fabrication procedural manual shall be by an approved agency.

Periodic plant inspections shall be conducted by an approved inspection or quality control agency to monitor the effectiveness of the quality control program.

It shall be the responsibility of the inspection or quality control agency to notify the approving authority in writing of any change to the procedural manual. Any fabricator approval may be revoked for just cause. Reapproval of the fabricator shall be contingent on compliance with quality control procedures during the past year.

WAIVER of SPECIAL INSPECTION. The Building Official may waive the requirement that special inspectors be employed if he finds that the construction is of a minor nature.

6.02.220 - Engineering or architect requirements.

GENERAL. In addition to the inspections required in Section 6.02.190 on work designed by a professional engineer or architect the following shall also apply:

Worksite Visits. During the construction or installation of work designed by a professional engineer or architect, the Building Official may require the engineer or architect of record responsible for the design, or such approved authorized representative of the engineer or architect, to make visits at the worksite to observe general compliance with the stamped plans, specifications and approved change orders. The engineer or architect of record shall submit a statement in writing to the Building Official stating that such engineer or architect knows from personal knowledge that the site visits have been made and that any discrepancies have been reported to the Building Official and the builder.

Required Worksite Visits. Worksite visits by the engineer or architect of record or such approved authorized representative shall be required for projects in which a special inspector and/or registered deputy inspector is required during construction as stated in this Code or the technical codes.

Such observation and statement shall not be relied upon by others as acceptance of the work, nor shall it be construed to relieve the builder in any way of its obligations and responsibilities.

SUPERVISION of SPECIAL INSPECTORS. When any work requires special inspection, the engineer or architect of record shall be responsible for supervising the work of the special inspectors.

CERTIFICATION BY ENGINEER OR ARCHITECT. Prior to the issuance of a Certificate of Occupancy, the engineer or architect of record shall state in writing to the Building Official that to the best of his knowledge, information and belief while exercising reasonable professional judgment, those portions of the work which required special inspection were construed in substantial conformity with the stamped plans and specifications.

6.02.230 - Connection to utilities.

ENERGY CONNECTIONS. No person shall make connections from a source of energy, fuel or power to any building service equipment which is regulated by the technical codes and for which a permit is required by this Code, until approved by the Building Official.

TEMPORARY CONNECTIONS. If the Building Official finds no substantial hazard will result he may authorize the temporary connection of the building service equipment to the source of energy, fuel or power for the purpose of testing building service equipment, or for use under a temporary Certificate of Occupancy.

TEMPORARY CONSTRUCTION UTILITY SERVICE. The Building Official may authorize the temporary connection of temporary construction service equipment to the source of energy, fuel or power for various approved construction activities.

COMPLIANCE WITH ENERGY STANDARDS. The servicing utility company providing energy, fuel or power shall determine that the buildings and structures meet local, state or federal energy resource allocation standards prior to the installation of new permanent utility service. The servicing utility company shall develop a pan to be approved by the City Council of the City of Richmond for dealing with buildings and structures which do not comply with the standards. This Section 6.02.230(D) shall not take effect until December 1, 1986.

REVOCATION. The Building Official may, in writing, suspend or revoke utility connection clearance issued under the provisions of this Code whenever an unsafe condition exists as a result of the clearance, the clearance is being used illegally to occupy the premises or when the energized system is being used for purposes other than those stated on the Certificate of Occupancy. Any utility disconnection or any revocation or suspension of utility connection clearance authorized by this section shall be performed pursuant to the provisions of Section

6.02.110(F).

6.02.240 - Certificate of Occupancy.

USE and OCCUPANCY:

No building or structure shall be used or occupied, and no change in the existing occupancy classification of a building or structure or portion thereof shall be made until the Building Official has issued a Certificate of Occupancy therefor as provided herein.

A Certificate of Occupancy shall not be issued until the Building Official has accepted all required inspection certifications.

CHANGE IN USE. Changes in the character or use of a building shall not be made except as specified in the Building Code.

CERTIFICATE ISSUED. After final inspection when it is found that the building or structure complies with the provisions of this Code and the technical codes, the Building Official shall issue a Certificate of Occupancy which shall contain the following:

The building permit number.

The address of the building.

The name and address of the owner.

A description of that portion of the building for which the certificate was issued.

Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 12 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 660

6. (D)
(E)
(F)

1. 2.

3. (a)
(b)
A statement that the described portion of the building complies with the requirements of this Code and the technical codes for the group and division of occupancy and the use for which the proposed occupancy is classified.

The name of the Building Official.

TEMPORARY CERTIFICATE. If the Building Official finds that no substantial hazard will result from occupancy of any building or portion thereof before the same is completed, he may issue a temporary Certificate of Occupancy for the use on a portion or portions of a building or structure prior to the completion of the entire building or structure.

POSTING. The Certificate of Occupancy shall be posted in a conspicuous place on the premises and shall not be removed except by the Building Official.

EXCEPTION: Group R, Division 3, and M Occupancies Certificate need not be posted in a conspicuous place, however, it must be posted in an accessible location.

REVOCATION:

The Building Official may, in writing, revoke or suspend a Certificate of Occupancy issued under the provisions of this chapter, whenever the certificate is issued in error or on the basis of incorrect information supplied, or when the Building Official has determined that the building or structure or portion thereof is in violation of any ordinance or regulation or any of the provisions of this chapter.

The Building Official shall issue the written notice suspending or revoking the certificate and direct a copy to the record owner of the property by certified mail, return receipt requested at the address shown on the last equalized assessment roll of the county and direct a copy to the occupant(s) of the building or structure by certified mail, return receipt requested at the address of the building or structure. The notice shall contain the street address and sufficient legal description of the property on which the structure is located, a statement of whether the certificate is being suspended or revoked, the basis for the revocation or suspension, and the time within which the use and occupancy of the building or structure be discontinued and the building or structure vacated.

Any party aggrieved by the determination of the Building Official to suspend or revoke the certificate may appeal said determination to the Board of appeals by filing a written request for appeal with the Building Official within the time period in which the Building Official has ordered the use to be discontinued. Failure of any person to file an appeal shall constitute a waiver of the right to an administrative hearing and adjudication of the notice suspending or revoking the certificate or any portion thereof. (Amended by Ordinance No. 11-94 N.S.)

6.02.250 - Adoption of technical codes.

Where any of the technical codes of the City of Richmond are adopted by reference, the effective dates of such codes shall be as follows:

Any new edition of the Uniform Housing Code, the Uniform Building Code, the Uniform Plumbing Code, the Uniform Mechanical Code, and the National Electric Code shall become effective 90 days after publication of said codes in the State Building Standards Code.

Any new edition of any other technical code shall become effective 90 days after the publication date of the new edition. (Amended by Ordinance No. 11-94 N.S. Source: Ordinance No. 20-86 N.S.) Chapter 6.02 - BUILDING REGULATIONS ADMINISTRATIVE CODE Page 13 of 13 http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.02BUREADCO.html 1/9/2013 661
(A)
(B)
(C)
(D)
(E)
(F)
(G)
Richmond, California, Code of Ordinances >> Article VI - BUILDING REGULATIONS >> Chapter 6.04 - BUILDING CODE* >> Chapter 6.04 - BUILDING CODE*
Sections:

6.04.010 - Administration.

6.04.020 - Adoption by reference.

6.04.030 - Copies on file.

6.04.040 - Amendments, additions and deletions.

6.04.010 - Administration.

These regulations shall be known as the "Building Code," and may be cited as such, and will be referred to herein as "this chapter." This Code is one of the technical codes of Building Regulations and is administered under Chapter 6.02 of the Municipal Code of the City of Richmond as such.

6.04.020 - Adoption by reference.

The most recent edition of the Uniform Building Code, published by the International Conference of Building Officials, including all appendix chapters thereto, except as specifically deleted by Section 6.04.040 of this chapter, is adopted by this reference and incorporated herein the same as though fully set forth in this chapter, subject to the amendments, additions and deletions specified in Section 6.04.040 of this chapter. Any new edition of the Uniform Building Code shall be adopted and shall become effective 90 days after publication of said code in the State Building Standards Code.
(Amended by Ordinance No. 12-94 N.S.)

6.04.030 - Copies on file.

Three copies of the Uniform Building Code and Appendix as adopted by Section 6.04.020, and all amendments thereto, shall be kept on file in the office of the city clerk for inspection by the public.

6.04.040 - Amendments, additions and deletions.

The following amendments, additions and deletions are made to the Uniform Building Code as adopted by Section 6.04.020 of this chapter:

Addition — Chapter 1, Sec. 103 — Revise the Scope to add the following as an additional paragraph to Sec. 103:
"Sec. 103. . . .The Administrative part of this chapter is in addition to the City of Richmond's Building Regulations Administrative Code, Chapter 6.02 of the Municipal Code. Where conflicts occur between this chapter and Chapter 6.02 of the Municipal Code the provisions of Chapter 6.02 of the Municipal Code shall govern." Amendment — Section 204 — Revise Section 204(a) of the Uniform Building Code to read as follows:
"Sec. 204.(a) General. Appeals of orders, decisions or determinations made by the Building Official relative to the application and interpretation of this code shall be heard and decided by the Board of Appeals, the body created by Richmond Municipal Code Section 6.02.130."
Amendment — Section 409 — HABITABLE SPACE (ROOM). Revise the definition of HABITABLE SPACE (ROOM) to read as follows:
"Sec. 409. HABITABLE SPACE (ROOM) is space in a structure for living, sleeping, eating or cooking. Bathrooms, toilet compartments, closets, halls, storage or utility space, greenhouses, and similar areas are not considered habitable space." Addition — Section 420 — Swimming pool. The following definition is added to the Uniform Building Code Section 420, to read as follows:
"Swimming Pool: Any outside body of water created by artificial means, which is designed or used for swimming or immersion purposes, any portion of which exceeds eighteen inches (18Ǝ) in depth except portable swimming pools." Amendment — Section 1101 — Fences. Division 2 of the Uniform Building Code Section 1101 is amended to read as follows:
"Division 2: Fences over six feet (6ƍ) high, tanks, towers, and swimming pools." Addition — Section 1107 — Swimming pools. Section 1107 is added to the Uniform Building Code to read as follows:
"(1) To be enclosed. Every swimming pool shall be completely enclosed by a wall, fence or other substantial structure not less than four feet (4ƍ) in height measured on the outside of the enclosure. No openings other than doors and gates with any dimension greater than four inches (4Ǝ) shall be permitted therein except that a picket fence may be erected or maintained having horizontal spacing between pickets not more than four inches (4Ǝ). All gates or door openings through such enclosures shall be equipped with self-closing and self-latching devices designed to keep and are capable of keeping such door or gate securely closed at all times when not in actual use; provided, however, that the door of any dwelling occupied by human beings and forming any part of the enclosure hereinabove required need not be so equipped. Any self-latching device accessible from the outside of the pool enclosure shall be located at least four feet (4ƍ) above the ground or otherwise equally inaccessible to small children." "(2) Existing Pools. Existing swimming pools as well as those hereafter constructed shall be enclosed in accordance with the requirements of this section."
Deletion — Appendix Chapter 12. Delete Appendix Chapter 12, "REQUIREMENTS FOR GROUP R, DIVISION 3 OCCUPANCIES." Chapter 6.04 - BUILDING CODE* Page 1 of 2
http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.04BUCO.html 1/9/2013 662
(H)
(I)
(J)
Amendment — Appendix Chapter 51, Sec. 5110 (b) — Revise the EXCEPTION: to read as follows:
"EXCEPTION: Certificates of inspection shall not be required of conveyances if inspected and certified by the State of California."
Deletion — Appendix Chapter 53. Delete Appendix Chapter 53 "ENERGY CONSERVATION IN NEW BUILDING CONSTRUCTION." Addition — Appendix Chapter 70, Sec. 7002 — Revise the scope to add the following as a second paragraph to Sec. 7002:
"Sec. 7002. . . .This chapter is in addition to the City of Richmond's Excavation and Grading Ordinance. Where conflicts occur between this chapter and the city's ordinance the most restrictive shall govern." (Amended by Ordinance No. 12-94 N.S.; Source: Ordinance No. 20-86 N.S.) Chapter 6.04 - BUILDING CODE* Page 2 of 2
http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.04BUCO.html 1/9/2013 663
(A)
(B)
Richmond, California, Code of Ordinances >> Article VI - BUILDING REGULATIONS >> Chapter 6.20 - MECHANICAL CODE* >> Chapter 6.20 - MECHANICAL CODE*
Sections:

6.20.010 - Administration.

6.20.020 - Adoption by reference.

6.20.030 - Copies on file.

6.20.040 - Amendments, additions and deletions.

6.20.010 - Administration.

These regulations shall be known as the "Mechanical Code," may be cited as such, and will be referred to herein as "this chapter." This code is one of the technical codes of Building Regulations and is administered under Chapter 6.02 of the Municipal Code of the City of Richmond as such.

6.20.020 - Adoption by reference.

The most recent edition of the Uniform Mechanical Code, jointly sponsored by the International Association of Plumbing and Mechanical Officials and the International Conference of Building Officials, including all appendix chapters thereto, except as specifically deleted by Section

6.20.040 of this chapter, is adopted by this reference and incorporated herein the same as though fully set forth in this chapter, subject to the amendments, additions and deletions specified in Section 6.04.040 of this chapter. Any new edition of the Uniform Mechanical Code shall be adopted and shall become effective 90 days after publication of said code in the State Building Standards Code. (Amended by Ordinance No. 15-94 N.S.)

6.20.030 - Copies on file.

Three copies of the Uniform Mechanical Code and Appendix as adopted by Section 6.20.020, and all amendments thereto, shall be kept on file in the office of the city clerk for inspection by the public.

6.20.040 - Amendments, additions and deletions.

The following amendments, additions and deletions are made to the Uniform Mechanical Code as adopted by Section 6.20.020 of this chapter:

Addition — Chapter 1, Sec. 103 — Revise the Scope to add the following as an additional paragraph to Sec. 103:
"Sec. 103. . . The Administrative part of this chapter is in addition to the City of Richmond's Building Regulations Administrative Code, Chapter 6.02 of the Municipal Code. Where conflicts occur between this chapter and Chapter 6.02 of the Municipal Code, the provisions of Chapter 6.02 of the Municipal Code shall govern." Amendment — Section 203 — Revise Section 203(a) of the Uniform Mechanical Code to read as follows:
"Sec. 203.(a) General. Appeals of orders, decisions, or determinations made by the Building Official relative to the application and interpretation of this code shall be heard and decided by the Board of Appeals, the body created by Richmond Municipal Code Section 6.02.130."
(Amended by Ordinance No. 15-94 N.S. Source: Ordinance No. 20-86 N.S.) Chapter 6.20 - MECHANICAL CODE* Page 1 of 1
http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.20MECO.html 1/9/2013 664
(A)
Richmond, California, Code of Ordinances >> Article VI - BUILDING REGULATIONS >> Chapter 6.28 - PLUMBING CODE* >> Chapter 6.28 - PLUMBING CODE*
Sections:

6.28.010 - Administration.

6.28.020 - Adoption by reference.

6.28.030 - Copies on file.

6.28.040 - Amendments, additions and deletions.

6.28.010 - Administration.

These regulations shall be known as the "Plumbing Code," may be cited as such, and will be referred to herein as "this chapter." This code is one of the technical codes of Building Regulations and is administered under Chapter 6.02 of the Municipal Code of the City of Richmond as such.

6.28.020 - Adoption by reference.

The most recent edition of the Uniform Plumbing Code, published by the International Association of Plumbing and Mechanical Officials, including all appendix chapters thereto and the "IAPMO Installation Standards" appended thereto, except as specifically deleted by Section 6.20.040 of this chapter, is adopted by this reference and incorporated herein the same as though fully set forth in this chapter, subject to the amendments, additions and deletions specified in Section 6.28.040 of this chapter. Any new edition of the Uniform Plumbing Code shall be adopted and shall become effective 90 days after publication of said code in the State Building Standards Code. (Amended by Ordinance No. 17-94 N.S.)

6.28.030 - Copies on file.

Three copies of the Uniform Plumbing Code and Standards as adopted by Section 6.28.020, and all amendments thereto, shall be kept on file in the office of the City Clerk for inspection by the public.

6.28.040 - Amendments, additions and deletions.

Addition — Chapter 1, Paragraph 10.3 — Revise the Scope to add the following as an additional paragraph to Paragraph 10.3:
"10.3 . . . The Administrative part of this chapter is in addition to the City of Richmond's Building Regulations Administrative Code Chapter 6.02 of the Municipal Code. Where conflicts occur between this chapter and Chapter 6.02 of the Municipal Code the provisions of Chapter 6.02 of the Municipal Code shall govern."
(Source: Ordinance No. 20-86 N.S.)
Chapter 6.28 - PLUMBING CODE* Page 1 of 1
http://library.municode.com/HTML/16579/level2/ARTVIBURE_CH6.28PLCO.html 1/9/2013 665
Richmond, California, Code of Ordinances >> Article XII - PUBLIC WORKS >> Chapter 12.17 - SANITARY SEWER CONNECTIONS* >> Chapter 12.17 - SANITARY SEWER CONNECTIONS*
Sections:

12.17.010 - Definitions.

12.17.020 - Sewer connections required.

12.17.030 - Connections to be made without damage to streets.

12.17.040 - Standards for sewer laterals and appurtenant facilities.

12.17.050 - Lateral testing requirements.

12.17.060 - Failure of test.

12.17.070 - Lateral certification.

12.17.080 - Notices to correct violations.

12.17.090 - Persons authorized to perform work.

12.17.100 - Other regulatory considerations.

12.17.110 - Nuisance conditions.

12.17.120 - Right of entry.

12.17.130 - Citation penalties.

12.17.010 - Definitions.

The following definitions apply to this chapter. Terms not defined in this section shall have their ordinary and common meaning or, if applicable, the meaning set forth in the Uniform Plumbing Code:
"Backflow valve" means a valve that is opened by the flow of sewage exiting a structure but closes when the flow reverses, preventing sewage from backing into the structure. All backflow valves shall conform to the specifications set forth in the Uniform Plumbing Code and all guidelines and policies established by the City Engineer to implement this chapter. "Building sewer" shall have the same meaning as "lateral," defined below. "Certificate of lateral compliance" means the certificate issued by the City Engineer certifying that a lateral complies with the standards set forth in this chapter. A fee for a certificate of compliance shall be charged in accordance with the City's rate and fee schedule. A certificate of compliance is valid only for the lateral at the address specified in the certificate and for a period of fifteen (15) years. "City authorized representative" means the City Engineer or his or her designee. "City of Richmond" or "City" means the City of Richmond and shall include Richmond Municipal Sewer District Number 1. "City's fee and rate schedule" means a list of all City of Richmond service, penalty, interest, and permit fees, and hourly personnel and equipment rates, as amended from time to time.
"Cleanout" means a segment of pipe connected to a sewer lateral and rising to the surface, providing access to the lateral for purposes of inspection and removal of obstructions. (See also "two-way cleanout," defined below.) "Commercial building" means any building designed for use as or used for commercial purposes. "Lateral," "building sewer," or "service lateral" means the sewer pipeline conveying wastewater from the premises of a user to the City's sewer system.
"Main" or "sewer main" means any sewer pipe within a public or private street or right-of-way receiving or intended to receive the discharges of one or more sewer lateral(s). No sewer main constructed after the effective date of this chapter shall be less than eight inches (8") in diameter nor be laid or constructed in any City street, easement or right-of-way under the control of the City, except to the lines, grades, and specifications approved by the City Engineer.
"Maintenance" means routine flushing or rodding of a sewer to maintain a free flowing condition. "Overflow device" means a device designed to relieve the pressure created when a gravity sewer is flowing full. All overflow devices require the approval of the City Engineer for proper application before their installation. "Person" means any individual, partnership, firm, company, corporation, association, joint stock company, trust, estate, governmental entity or any other legal entity, or their legal representative, agents or assigns. The masculine gender shall include the feminine, the singular shall include the plural where indicated by context.
"Plumbing fixtures" means sinks, baths, showers, toilets, bidets, and all fixtures and appliances, such as dishwashers and washing machines, from which water or wastewater are discharged.
"Private sewer main" means a main on private property that connects to the City's sanitary sewer system. A private sewer main shall meet the same standards as a lateral and is subject to all lateral testing, certification and enforcement provisions of this chapter. "Repair" means physical exposure of a section of pipe and/or appurtenances for the purpose of resuming proper operating condition. "Replacement" means removal and replacement of existing pipe and/or appurtenances. "Sanitary sewer system" shall have the same meaning as "publicly owned treatment works" as that term is defined at Richmond Municipal Code Section 12.18.020.

Chapter 12.17 - SANITARY SEWER CONNECTIONS* Page 1 of 3 http://library.municode.com/HTML/16579/level2/ARTXIIPUWO_CH12.17SASECO.html 1/9/2013 666
(a)
(b)
(1)
(2)
(3)
(4)
(5)
(6)
(a)
(b)
(c)
(1)
(2)
(3)
(d)
"Service lateral" shall have the same meaning as "lateral," defined above. "Sewage" means water carrying wastes from residences, business buildings, institutions and industrial establishments, together with such other waters as may be present, or any combination of such wastes and water. "Sewer facilities" means and includes the sanitary and storm sewage collection systems owned and operated by the City, all appurtenances thereto, and all portions thereof.
"Storm sewer" or "storm drain" means a pipe or conduit which carries storm and surface waters and drainage, but excludes sewage and polluted industrial wastes.
"Subdivider" means to cause land to be divided into separate developed or developable lots that are or may be owned by different persons. "Two-way cleanout" means a "Y"- or "V"-shaped segment of pipe connected to a sewer lateral and rising to the surface, providing access to the lateral in both directions for purposes of inspection and removal of obstructions. "User" means and includes any person who causes or permits a discharge of sewage into the City's sanitary sewer system. "Wastewater" shall have the meaning set forth at Richmond Municipal Code Section 12.18.020.

12.17.020 - Sewer connections required.

Property owners shall provide connections to the sanitary sewer system in accordance with Richmond Municipal Code Sections 12.16.010 and 12.16.020, as those sections may be amended from time to time.

12.17.030 - Connections to be made without damage to streets.

All connections to the City's sanitary sewer system shall be laid without damaging the surface of any improved street unless the City Engineer grants a permit to remove and replace street paving. To obtain such a permit, the applicant shall furnish the City Engineer with a bond with two sufficient sureties in an amount set forth in the City's fee and rate schedule. The bond shall guarantee that the permit holder will restore the street surface to a serviceable condition as good or better than the condition of the street prior to resurfacing.

12.17.040 - Standards for sewer laterals and appurtenant facilities.

Every property owner shall perform all required maintenance and keep the lateral(s) and private sewer main(s), if any, connecting the premises on his or her property to the City's sanitary sewer system in good condition.

Every lateral shall meet the following minimum requirements:

It shall be kept free from roots, grease deposits, and other solids which may impede the flow or obstruct the transmission of waste.

All joints shall be tight and all pipes shall be sound and free from structural defects, cracks, breaks, openings, and missing portions to prevent ex-filtration by waste or infiltration by ground water or storm water.

The grade of every lateral shall be uniform without sags or offsets.

It shall have a two-way cleanout located at or near the property line or at or near the sewer main easement. All cleanouts shall be securely capped at all times.

It shall be equipped with a backflow valve or overflow device.

In conjunction with a lateral serving a structure in which there are plumbing fixtures at an elevation too low to permit drainage by gravity from the fixtures to the sewer main, the property owner shall install and maintain a pump or other appropriate device or devices to lift the contents of the sewer lateral to the City's sanitary sewer system. Such devices shall be installed and maintained in accordance with the Uniform Building and Plumbing Codes and all applicable provisions of the Richmond Municipal Code, and shall be subject to testing, repair and replacement under the provisions of this chapter governing sewer laterals.

12.17.050 - Lateral testing requirements.

All testing procedures must be approved by the City Engineer, or his or her designee, and performed in accordance with approved procedures. Results of all lateral tests shall be filed with the City Engineer. If, after testing, a property owner agrees to undertake specific repairs or replacements to bring a lateral into compliance with the provisions of this chapter, the statement of test results shall specify the repairs or replacements to be completed before retesting; shall state, "The property owner agrees to complete the above repairs and/or replacements and retest the subject lateral(s) in accordance with Richmond Municipal Code Chapter 12.17"; and shall be signed by the property owner.

Laterals for all multi-unit residential buildings, all commercial buildings and all industrial facilities in the City of Richmond and all private sewer mains that connect to the City's sanitary sewer system shall be tested within one (1) year of the effective date of this chapter and shall be repaired or replaced as necessary to ensure compliance with the standards set forth in this chapter.

Whenever title to property located in the City of Richmond is transferred, and the property includes buildings or structures that discharge into a sanitary sewer system, the sewer lateral(s) to the property shall be tested for compliance with the standards set forth in this chapter. Before title is transferred, all repairs or replacements necessary to bring a lateral into compliance shall be performed. A seller shall disclose to prospective purchasers the requirements of this chapter and the compliance status of the subject property. This subsection shall not apply to transfer of title to:

An individual unit in a multi-unit building served by a single lateral; A property for which there is a valid certificate of lateral compliance; A property located in the City of Richmond but served by a sanitary sewer service provider that has a lateral maintenance, inspection and repair program in place.

Whenever property located in the City of Richmond and containing one or more structures is subdivided, the sewer lateral(s) serving the property shall be tested. Before the subdivision is approved, all repairs or replacements necessary to bring a lateral into compliance shall be Chapter 12.17 - SANITARY SEWER CONNECTIONS* Page 2 of 3 http://library.municode.com/HTML/16579/level2/ARTXIIPUWO_CH12.17SASECO.html 1/9/2013 667
(e)
(f)
(a)
(b)
(c)
performed. If the subdivision of land causes structures served by a single lateral to be separated onto different lots, laterals for each lot on which there is a structure shall be constructed in accordance with the Uniform Building and Plumbing Codes and all applicable provisions of the Richmond Municipal Code.

Whenever property located in the City of Richmond is remodeled to include the addition of two or more plumbing fixtures that discharge into a sanitary sewer system, the sewer lateral(s) to the property shall be tested. Before final building inspection, all repairs or replacements necessary to bring a lateral into compliance shall be performed.

The City Engineer reserves the right to notify any owner of property for which there is not a valid certificate of lateral compliance on file that the City shall conduct a random test of the property's sewer lateral in accordance with Richmond Municipal Code Section 12.17.120 and shall notify the property owner of and require the property owner to correct any conditions that do not comply with this chapter.

12.17.060 - Failure of test.

Should a lateral fail the test, the lateral shall be repaired or replaced, as necessary and in accordance with the Uniform Building and Plumbing Codes and all applicable provisions of the Richmond Municipal Code, then retested. This process shall continue until the lateral passes the required test.

12.17.070 - Lateral certification.

Once the lateral has passed the testing procedure and upon payment of the appropriate fee as published in the City's fee and rate schedule, the City Engineer, or his or her designee, shall issue a signed certificate of lateral compliance to the property owner specifying the address of the property served by the subject lateral. A certificate of lateral compliance shall be valid for fifteen (15) years and shall be valid only for the lateral at the address specified in the certificate. The City Engineer shall maintain records of all certificates of lateral compliance issued.

12.17.080 - Notices to correct violations.

If the City Engineer receives notice that a lateral does not meet the standards set forth in this chapter and the property owner has not agreed in writing to perform the repairs or replacements necessary to bring the lateral into compliance, then the City Engineer shall give written notice to the property owner of any conditions that violate this chapter. Such notice shall specify the repair or replacement necessary to correct the condition and the time in which to make the correction, and shall advise the property owner of the enforcement provisions of this chapter.

12.17.090 - Persons authorized to perform work.

Only contractors licensed by the state shall be authorized to construct or repair laterals and mains.

12.17.100 - Other regulatory considerations.

The Uniform Building and Plumbing Codes and other applicable regulations adopted by the City of Richmond shall govern the construction and repair of laterals and mains.

The City Engineer shall establish guidelines and policies for implementing and enforcing this chapter.

If property located in the City of Richmond is served by a sanitary sewer service provider other than the City of Richmond and that service provider has a lateral maintenance, inspection and repair program in place, the property shall be subject to the regulations and standards of the service provider. If property located in the City of Richmond is served by a sanitary sewer service provider that does not have a lateral maintenance, inspection and repair program in place, the property is subject to the requirements of this chapter.

12.17.110 - Nuisance conditions.

All sewer laterals or sewer clean-outs which contain leaks or breaks; uncapped or improperly capped sewer clean-outs; sump pumps; down spouts or yard drains which discharge into the City's sanitary sewer system; and all other sources of accidental, negligent or intended introduction of storm water run off or similar waters into the sanitary sewer system are hereby declared to be a public nuisance, subject to abatement in accordance with Richmond Municipal Code Chapter 9.22 if, after being notified of the nuisance condition, the property owner fails to correct the condition. If the City of Richmond abates a sewer-related public nuisance, the costs of such abatement shall be assessed against the subject property owner and may result in a lien against the subject property in accordance with Richmond Municipal Code Sections 12.16.050 and 12.16.060.

12.17.120 - Right of entry.

The City Engineer, or his or her designee, may enter, inspect, collect wastewater samples, and test any buildings, structures, or premises to secure compliance or prevent a violation of any portion of this chapter. Unless there is an emergency threatening the public health, safety or welfare, the City Engineer shall provide at least ten (10) business days notice to the property owner of intent to enter upon property. The City Engineer may also request that a property owner provide all written records of lateral inspection, maintenance, repair and replacement at the time of inspection or within ten (10) or more business days after receipt of the request.

12.17.130 - Citation penalties.

In addition to, or in lieu of, the remedies set forth in this chapter, any violation of this chapter may result in the issuance of an administrative citation pursuant to Richmond Municipal Code Chapter 2.62. (Source: Ordinance No. 61-06 N.S.)
Chapter 12.17 - SANITARY SEWER CONNECTIONS* Page 3 of 3 http://library.municode.com/HTML/16579/level2/ARTXIIPUWO_CH12.17SASECO.html 1/9/2013 668
Richmond, California, Code of Ordinances >> Article XII - PUBLIC WORKS >> Chapter 12.18 - DISCHARGES TO THE WASTEWATER TREATMENT SYSTEM >>
Chapter 12.18 - DISCHARGES TO THE WASTEWATER TREATMENT SYSTEM [15] Sections:

12.18.010 - General provisions.

12.18.010.1 - Purpose and policy.

12.18.010.2 - Administration.

12.18.010.3 - Definitions.

12.18.020 - General sewer use requirements.

12.18.020.1 - Prohibited discharge standards.

12.18.020.2 - National Categorical Pretreatment Standards.

12.18.020.3 - State Pretreatment Standards.

12.18.020.4 - Local limits.

12.18.020.5 - Right to revision.

12.18.020.6 - Dilution.

12.18.030 - Pretreatment of wastewater.

12.18.030.1 - Pretreatment facilities.

12.18.030.2 - Fats, oils, and grease.

12.18.030.3 - Additional pretreatment measures.

12.18.030.4 - Accidental discharge/slug discharge control plan.

12.18.030.5 - Hauled wastewater.

12.18.040 - Wastewater discharge permits.

12.18.040.1 - Wastewater analysis.

12.18.040.2 - Wastewater discharge permit requirement.

12.18.040.3 - Wastewater discharge permitting: Existing connections.

12.18.040.4 - Wastewater discharge permitting: New connections.

12.18.040.5 - Wastewater discharge permit application contents.

12.18.040.6 - Wastewater discharge permitting: General permits.

12.18.040.7 - Application signatories and certifications.

12.18.040.8 - Wastewater discharge permit decisions.

12.18.050 - Wastewater discharge permit issuance.

12.18.050.1 - Wastewater discharge permit duration.

12.18.050.2 - Wastewater discharge permit contents.

12.18.050.3 - Permit appeals.

12.18.050.4 - Permit modification.

12.18.050.5 - Wastewater discharge permit transfer.

12.18.050.6 - Wastewater discharge permit revocation.

12.18.050.7 - Wastewater discharge permit reissuance.

12.18.050.8 - Regulation of waste received from other jurisdictions.

12.18.060 - Reporting requirements.

12.18.060.1 - Baseline monitoring reports.

12.18.060.2 - Compliance schedule progress reports.

12.18.060.3 - Reports on compliance with Categorical Pretreatment Standard deadline.

12.18.060.4 - Periodic compliance reports.

12.18.060.5 - Reports of changed conditions.

12.18.060.6 - Reports of potential problems.

12.18.060.7 - Reports from unpermitted users.

12.18.060.8 - Notice of violation/repeat sampling and reporting.

12.18.060.9 - Notification of the discharge of hazardous waste.

12.18.060.10 - Analytical requirements.

12.18.060.11 - Sample collection.

12.18.060.12 - Date of receipt of reports.

12.18.060.13 - Recordkeeping.

12.18.060.14 - Certification statements.

12.18.070 - Compliance monitoring.

12.18.070.1 - Right of entry: Inspection and sampling.

12.18.070.2 - Search warrants.

12.18.080 - Confidential information.

12.18.090 - Publication of users in significant noncompliance.

12.18.100 - Administrative enforcement remedies.

12.18.100.1 - Notification of violation.

12.18.100.2 - Consent orders.

12.18.100.3 - Show cause hearing.

12.18.100.4 - Compliance orders.

12.18.100.5 - Cease and desist orders.

12.18.100.6 - Administrative fines.

12.18.100.7 - Emergency suspension.

12.18.100.8 - Termination of discharge.

12.18.110 - Judicial enforcement remedies.

12.18.110.1 - Injunctive relief.

Chapter 12.18 - DISCHARGES TO THE WASTEWATER TREATMENT SYSTEM Page 1 of 26 http://library.municode.com/HTML/16579/level2/ARTXIIPUWO_CH12.18DIWATRSY.ht... 1/9/2013 669
A.

B.

C.

D.

E.

F.

G.

H.

A.

B.

C.

D.

E.
(1)
(a)
(b)

12.18.110.2 - Civil penalties.

12.18.110.3 - Criminal prosecution.

12.18.110.4 - Remedies nonexclusive.

12.18.120 - Supplemental enforcement action.

12.18.120.1 - Penalties for late reports.

12.18.120.2 - Performance bonds.

12.18.120.3 - Liability insurance.

12.18.120.4 - Payment of outstanding fees and penalties.

12.18.120.5 - Water supply severance.

12.18.120.6 - Public nuisances.

12.18.120.7 - Contractor listing.

12.18.130 - Affirmative defenses to discharge violations.

12.18.130.1 - Upset.

12.18.130.2 - Prohibited discharge standards.

12.18.130.3 - Bypass.

12.18.140 - Wastewater treatment rates.

12.18.140.1 - Fees and charges.

12.18.010 - General provisions.

12.18.010.1 - Purpose and policy.

This ordinance sets forth the requirements of users of the Richmond Municipal Sewer District Water Pollution Control Plant and its collection system (collectively, called the WPCP in this ordinance) for the City of Richmond (City), and enables the City to comply with all applicable State and Federal laws, including the Clean Water Act (Title 33 of the United States Code [USC] Section 1251 et seq.) and the General Pretreatment Regulations (Title 40 of the Code of Federal Regulations [CFR] Part 403). The objectives of this chapter are:

To prevent the introduction of pollutants into the WPCP that will interfere with its operations; To prevent the introduction of pollutants into the WPCP that will pass through the WPCP, inadequately treated, into receiving waters or atmosphere, or otherwise be incompatible with the WPCP; To protect both WPCP personnel who may be affected by wastewater and sludge in the course of their employment and the general public;
To promote reuse and recycling of wastewater, sludge, gases, and other byproducts from the WPCP; To provide for fees for the equitable distribution of the cost of operation, maintenance, and improvement of the WPCP; To prevent sanitary sewage overflows as a result of grease obstructions that subject the City and the public to adverse health risks, State Water Resources Control Board penalties, and civil lawsuits, impact service continuance, and diminish stormwater quality; To comply with San Francisco Bay Regional Water Quality Control Board regulations for establishing a Sanitary Sewer Overflow Plan that also includes a Fats, Oils, and Grease Control Plan; To enable the City to comply with its National Pollutant Discharge Elimination System (NPDES) permit conditions, sludge use and disposal requirements, and any other Federal or State laws to which the WPCP is subject.

This chapter shall apply to all users of the WPCP. The chapter authorizes the issuance of individual and general wastewater discharge permits; provides for monitoring, compliance, and enforcement activities; establishes administrative review procedures; requires user reporting; and provides for the setting of fees for equitable distribution of costs resulting from the program established herein. (Ord. No. 18-11 N.S., § I, 7-26-2011)

12.18.010.2 - Administration.

Except as otherwise provided herein, the City Engineer shall administer, implement, and enforce the provisions of this chapter. Any powers granted to or duties imposed upon the City Engineer may be delegated by the City Engineer to a duly authorized City employee. (Ord. No. 18-11 N.S., § I, 7-26-2011)

12.18.010.3 - Definitions.

Unless a provision explicitly states otherwise, the following terms and phrases, as used in this chapter, shall have the meanings hereinafter designated.
"Act" or "the Act." The Federal Water Pollution Control Act, also known as the Clean Water Act, as amended, 33 USC Section 1251 et seq.
"Administrator." The EPA Administrator or their designee. "Applicant." Any person who applies for an individual or coverage under a wastewater discharge permit. "Approval Authority." The San Francisco Bay Regional Water Quality Control Board. "Authorized" or "Duly Authorized Representative of the user." If the user is a corporation:

The president, secretary, treasurer, or a vice-president of the corporation in charge of a principal business function, or any other person who performs similar policy or decision-making functions for the corporation; or The manager of one or more manufacturing, production, or operating facilities, provided the manager is authorized to make management decisions that govern the operation of the regulated facility including having the explicit or implicit duty of making major capital investment recommendations, and initiate and direct other comprehensive measures to Chapter 12.18 - DISCHARGES TO THE WASTEWATER TREATMENT SYSTEM Page 2 of 26 http://library.municode.com/HTML/16579/level2/ARTXIIPUWO_CH12.18DIWATRSY.ht... 1/9/2013 670
(2)
(3)
(4)
F.