County of San Diego - RCS AgreementNextGen RCS Agreement Page 1 of 19 December 3, 2013
Agreement
Between and Among the County of San Diego
and
Participating Cities and Jurisdictions
Regarding the Next Generation Regional Communication System
Providing Communication Services to Public Safety and Public Service Agencies
Operating in San Diego County and Imperial County
NextGen RCS Agreement”)
1. THE 1995 RCS AGREEMENT; TRANSITION TO NEXT GENERATION RCS
1.1 The 1995 RCS Agreement. Effective March 7, 1995, the County of San Diego
County”) and certain local governments and agencies entered into an agreement entitled the
San Diego County – Imperial County Regional Communications System Agreement Between
the County of San Diego and Participating Cities and Jurisdictions Regarding the
Implementation, Governance, Method of Funding and Costs of a Regional Radio System
Providing Communication Services to Public Safety and Public Service Agencies Operating in San
Diego County and Imperial County” (referred to as the “1995 RCS Agreement,” a copy of which
is attached as Exhibit A. Additional local governments and agencies signed onto the 1995 RCS
Agreement, and all original and additional signatories (referred to as “1995 RCS Parties”) are
listed in Exhibit B. The 1995 RCS Agreement provides for the operation of a regional
communication system by the County through its Sheriff’s Department with the financial
contribution of the 1995 RCS Parties. Other agencies and entities (“Customers”) are allowed to
use the RCS, upon recommendation by the RCS Board of Directors, through contracts with the
County wherein a Customer pays fees as approved by the Board of Directors, with the revenues
from such contracts flowing to the RCS Operating Account and RCS Trust Fund maintained by
the County.
1.2 1995 RCS Governance. The 1995 RCS Agreement establishes a governance
structure wherein the County, through the Sheriff’s Department Wireless Services Division,
operates and maintains the RCS with other County departments providing additional
administrative support, and the County Board of Supervisors having ultimate fiscal and
operational control over the RCS. The 1995 RCS Agreement establishes an RCS Board of
Directors to make recommendations to the Board of Supervisors.
NextGen RCS Agreement Page 2 of 19 December 3, 2013
1.3 1995 RCS Fiscal Components. There are three basic fiscal components to RCS
Party participation in the 1995 RCS Agreement and use of the RCS: (1) contribution to the
construction of the RCS “backbone”, (2) monthly operating charges, and (3) each RCS Party’s
own equipment and certain infrastructure costs. 1995 RCS Parties have paid or are paying their
contribution to the backbone construction through several fiscal vehicles, including financing
provided by the County and County Service Area (CSA) 135, formed pursuant to Government
Code section 25210 et. seq. Relevant actions pertaining to CSA 135 include, but may not be
limited to the following: In Fiscal Years 1995-1996 and 1996-1997, pursuant to Government
Code section 25210.77a (repealed 2009), the County levied parcel charges for CSA 135. On June
2, 1998, voters in three cities approved special taxes without sunset dates to replace the parcel
charges as follows: The City of Poway (CSA 135 Zone F) - Proposition J; The City of Del Mar (CSA
135 Zone B) -Proposition F; The City of Solana Beach (CSA 135 Zone H) - Proposition L.
1.4 1995 RCS Agreement Extensions. On May 5, 2009 (Minute Order No. 2) on
recommendation of the RCS Board of Directors, the County Board of Supervisors approved the
extension of the RCS Agreement to March 31, 2013. On August 7, 2012 (Minute Order No. 1),
again on recommendation of the RCS Board of Directors, the County Board of Supervisors
approved the extension of the 1995 RCS Agreement to March 31, 2016 in order to allow
sufficient time to transition to a new or “next generation” (“NextGen RCS”) replacement
regional communication system and to develop a new participating agency agreement
governing the new system.
1.5 Next Generation Regional Communication System (“NextGen RCS”). The
transition from the existing RCS to the NextGen RCS is to be implemented and facilitated by this
NextGen RCS Agreement and will occur over the course of approximately five years as follows:
The County intends to issue the Request for Proposals for the NextGen RCS (“NextGen RFP”)
near the middle of calendar year 2014, close NextGen RFP responses by end of calendar year
2014, and award the NextGen RCS Contract in mid-2015. It is further anticipated that while
performance on the NextGen RCS Contract will begin shortly thereafter, infrastructure and
equipment replacement of the RCS by the NextGen RCS will begin in early 2016. It is
anticipated that NextGen RCS installation will be completed in late 2018.
1.6 NextGen RCS Agreement; Purpose. The purpose of this NextGen RCS Agreement
is to establish a degree of certainty among all Parties to the 1995 RCS Agreement and additional
parties as to participation and partnership in the NextGen RCS. Such degree of certainty is
necessary because the County, as the contracting and administering entity, must issue the
Request For Proposals (“NextGen RCS RFP”) in 2014, and the scope of work, funding and
financing discussions require a framework for participation be in place. This NextGen RCS
Agreement also provides incentive for 1995 RCS Parties to execute this NextGen RCS
NextGen RCS Agreement Page 3 of 19 December 3, 2013
Agreement and become NextGen RCS Parties, indicating their good faith intention to
participate, by establishing late joining penalties as set forth in section 3 of this NextGen RCS
Agreement.
1.7 Transition from 1995 RCS Agreement. The purposes of this NextGen RCS
Agreement include establishing participation in the sharing of NextGen RCS Shared Backbone
Infrastructure costs and NextGen RCS governance. Given that the transition from the RCS to the
NextGen RCS will occur in stages and over time, the NextGen RCS Parties agree that the 1995
RCS Agreement shall continue to be operative and govern the operation, maintenance,
governance and administration of the RCS system until such time as the 1995 RCS Agreement
expires in 2016, except as follows: This NextGen RCS Agreement will govern with respect to
matters pertaining to setting NextGen RCS performance objectives, NextGen RCS
implementation planning, and other matters that may relate to the NextGen RCS after
transition from the RCS is complete. Upon expiration of the 1995 RCS Agreement, this NextGen
RCS Agreement shall govern the RCS as it evolves to the NextGen RCS. Thus, from the execution
of this NextGen RCS Agreement to the expiration of the 1995 RCS Agreement, there will be, to
the extent required by the foregoing, dual governance structures, including dual boards of
directors, which may or may not have members in common.
1.8 NextGen RCS Agreement; Authority. On December 3, 2013 (Item No. 6), the
Board of Supervisors authorized the Clerk of the Board to execute this NextGen RCS Agreement
on behalf of the County. Each other NextGen RCS Party was authorized to enter into this
NextGen RCS Agreement as indicated on their individual signature page.
2. NEXTGEN RCS OVERVIEW
2.1 1995 RCS. The RCS replaced the participating public service and public safety
agencies' existing radio communication systems throughout San Diego and Imperial counties
with what was at the time a modern, trunked radio system.
2.2 NextGen RCS. The NextGen RCS will replace, modernize and update the RCS and
shall provide effective and reliable voice radio communications for routine intra- and inter-
agency operations as well as inter-agency communications throughout the region during
mutual aid and disaster operations. The NextGen RCS will include the following subsystems: a
new trunked voice system, new microwave backhaul network, and a conventional voice system.
2.2.1 Trunked Voice System Description. The Trunked Radio System consists of
the radio transmission equipment located at remote radio sites and the centralized system
networking and management equipment necessary to provide voice radio services to the
participating agencies in the RCS service area.
NextGen RCS Agreement Page 4 of 19 December 3, 2013
2.2.2 Microwave Backhaul Network Description. The Microwave Backhaul
Network consists of the point-to-point radio and data switching equipment necessary to
interconnect the sites where components of the trunked radio system and conventional radio
systems (network hub and remote radio sites) are located.
2.2.3 Conventional Voice System Description. The Conventional Voice System
consists of non-trunked ("conventional") radio base station equipment installed at remote radio
sites to support voice radio communications between users of the RCS trunked radio system
and non-RCS user agencies as required in day-to-day, mutual aid and disaster operations. The
conventional voice system also provides limited backup voice communications capability in the
event of a trunked system failure.
2.3 “Public Safety” and “Public Service” Agencies Defined
2.3.1 Public Safety agencies include all public law enforcement, fire service, EMS
and disaster preparedness agencies in San Diego County and Imperial County.
2.3.2 Public Service agencies includes the State of California Department of
Transportation (Caltrans) District 11 and other participating public agencies in the counties of
San Diego and Imperial whose primary responsibility is providing citizens with services other
than law enforcement, fire service, EMS, and disaster preparedness. Public Service agencies
may also include Private-Non-Profit agencies operating under an agreement with a public
agency.
2.4 Mutual Aid Communications. All law enforcement, fire service, EMS, disaster
preparedness and participating public service agencies in San Diego County and Imperial County
shall have access to mutual aid communications capabilities.
3. NEXTGEN RCS PARTICIPATION PARAMETERS AND CONTINGENCIES
3.1 Time Is Of The Essence. Due to the aging of the RCS, time is of the essence in the
deployment of the NextGen RCS. Due to the anticipated construction time, the County intends
to issue the NextGen RFP near the middle of calendar year 2014, close NextGen RFP responses
by the end of 2014, and award the NextGen Contract in mid-2015. In order to provide a
measure of confidence that there will be a certain level of participation and sharing in the
NextGen RCS Shared Infrastructure Cost (See section 11.2), and to provide a minimal degree of
certainty to the County of San Diego before it undertakes the extensive task of preparing and
issuing a request for proposals or other form of solicitation to potential vendors of the NextGen
RCS, the County has asked, and the NextGen RCS Parties have agreed to the participation
parameters herein.
NextGen RCS Agreement Page 5 of 19 December 3, 2013
3.2 Signing Deadline. 1995 RCS Parties and other local governments and agencies
that desire to be NextGen Parties must sign this NextGen RCS Agreement no later than March
31, 2014.
3.3 Late Signers; Penalties. 1995 RCS Parties or other local governments or agencies
who have not signed the NextGen RCS Agreement by March 31, 2014 will be allowed to later
sign onto the NextGen RCS Agreement and become NextGen RCS Parties during the period April
1, 2014 to July 31, 2014; however, such late-joining NextGen RCS Parties (“late signers”) will pay
their NextGen RCS Shared Infrastructure Cost they would have paid had they executed this
NextGen RCS Agreement by March 31, 2014, plus a late penalty amounting to 15% of the
original participation share. Penalty fees will be handled according to Section 3.5.
3.3.1 1995 RCS Parties or other local governments or agencies who have not
signed the NextGen RCS Agreement by July 31, 2014, will be allowed to sign onto the NextGen
RCS Agreement and become NextGen RCS Parties until January 1, 2015; however, such late-
joining NextGen RCS Parties (also “late signers”) will pay the NextGen RCS Shared Infrastructure
Cost they would have paid had they executed this NextGen RCS Agreement by March 31, 2014,
plus a late penalty amounting to 25% of the original participation share.
3.4 Final Cut Off. No 1995 RCS Parties or other local governments or agencies will be
allowed to sign onto the NextGen RCS Agreement and become NextGen RCS Parties after
January 1, 2015.
3.5 Disposition of Penalties Collected. Late penalties will be deposited to the
NextGen RCS Trust Fund.
3.6 Financing. For NextGen RCS Parties that choose not to pay their share of the
total NextGen RCS Shared Infrastructure Cost in total within sixty days of the issuance of the
revised Exhibit C and prior to contract award, which is anticipated to occur in the spring or
summer of 2015, a financing mechanism will be determined and made available by the County.
Nothing in this section prohibits any NextGen RCS Parties from pursuing and obtaining their
own financing. Payment and financing agreements will be separate and apart from this
NextGen RCS Agreement. Financing mechanisms will not be available to pay for late signing
penalties.
3.7 Contingencies. To facilitate the execution of this NextGen RCS Agreement, it is
understood that a NextGen RCS Party may choose to be excused from performing under this
NextGen RCS Agreement if any of the following contingencies are not met:
3.7.1 Vendor Contract – A contract must be awarded pursuant to the County’s
NextGen RCS RFP or other solicitation.
NextGen RCS Agreement Page 6 of 19 December 3, 2013
3.7.2 County Funding. Funds for the County to undertake the NextGen RCS
project must exist.
3.7.3 Actual Shared Infrastructure Costs. The total NextGen RCS Shared
Infrastructure Costs, as determined by the vendor contract, does not exceed the budgetary
estimate in Exhibit C by more than 10 percent (10%).
4. SCOPE OF AGREEMENT; CERTAIN REQUIREMENTS
4.1 NextGen RCS Parties. The purpose of the NextGen RCS and NextGen RCS
Agreement is to provide a next generation communications system that provides optimum
service to the NextGen RCS Parties. To that end, the NextGen RCS will be designed to provide
optimum required service. Additionally, the NextGen RCS Parties, while executing this NextGen
RCS Agreement, do not intend to cede any of their constitutional or statutory autonomy.
4.2 Frequency Licensing Or Transfer. NextGen RCS Parties shall co-license or
transfer their currently allocated 800 MHz frequencies to the County of San Diego for use in the
NextGen RCS.
5. NEW NEXTGEN PARTIES
5.1 “New Parties” are defined as public safety and public service agencies that are
not "1995 RCS Parties". New Parties will be allowed to participate in this agreement and
become a NextGen RCS Party.
5.2 If participation by a New Party requires enhancement or expansion of coverage
beyond what is provided by the existing RCS on the effective date of this NextGen RCS
Agreement, the New Party shall pay the costs associated with such enhancement or expansion,
separate and apart from the financial responsibilities addressed in this NextGen RCS
Agreement.
5.3 For informational purposes only that may be of benefit to the 1995 Parties, the
County has identified potential New Parties and they are listed in Exhibit D.
6. NEXTGEN RCS PERFORMANCE REQUIREMENTS
6.1 Reliability. The NextGen RCS shall be designed to provide a high level of
redundancy and reliability to support mission critical public safety communications. The overall
system availability design objective shall be 99.999%. (Note: 99.999% system availability is the
public safety "best practice" design objective; it is not a formally adopted standard.)
NextGen RCS Agreement Page 7 of 19 December 3, 2013
6.2 Design Objectives. The NextGen RCS design objectives for the performance of
portable and mobile voice and the quality of coverage provided shall be determined by the
NextGen RCS Board of Directors and appropriate County of San Diego staff.
6.3 Loading Requirements. The NextGen RCS shall be designed to meet the loading
requirements of the anticipated busiest hour for all planned users over the life of the system.
6.4 Coverage Plan. The goal of the NextGen RCS is to provide the same general
coverage footprint as is provided by the existing RCS and to correct existing deficiencies where
practicable. The actual NextGen RCS radio service coverage plan shall be determined by a
NextGen RCS Project Management Office to be created by the Sheriff’s Department and with
the consultation of the NextGen RCS Board of Directors.
7. NEXTGEN RCS ACCESS PRIORITIES
7.1 User Prioritization. In the event that all radio channels in the RCS are busy, users
wanting to speak shall be prioritized as follows, regardless of how long they have been waiting:
7.1.1 Priority One - Emergency Identification. An Emergency Identification is
defined as the message received when a public safety member calls for immediate assistance
by activating an emergency button or switch on the user radio equipment.
7.1.2 Priority Two - Public Safety
7.1.2.1 - Public Safety includes the normal daily radio transmissions of
law enforcement, fire service, paramedic providers and disaster preparedness personnel using
the RCS.
7.1.2.2 - Public Safety also includes RCS users whose normal lower
priorities have been temporarily changed to resolve an unusual occurrence or large scale
disaster.
7.1.3 Priority Three - Non-Public Safety, Special Event. Non-Public Safety,
Special Event includes planned events involving public service agency participants that are
beyond the scope of their normal daily operations.
7.1.4 Priority Four - Non-Public Safety, Regular. Non-Public Safety, Regular
includes the normal daily radio transmissions of public service agencies using the system.
8. NEXTGEN RCS GOVERNANCE; CONTINUED RCS GOVERNANCE
8.1 . Limited Period Of Concurrent Governance. It is the intent of the NextGen RCS
Parties that there shall be concurrent operation of, and governance by, this NextGen RCS
NextGen RCS Agreement Page 8 of 19 December 3, 2013
Agreement and the 1995 RCS Agreement during the construction of the NextGen RCS, as set
forth in Section 1.7 above.
8.2 General NextGen RCS Governance Structure. The County of San Diego Sheriff’s
Department will operate and maintain the NextGen RCS. Other departments of the County of
San Diego will provide support as necessary. As the governing body for the County, the Board of
Supervisors shall have ultimate fiscal and operational control over the NextGen RCS and shall be
ultimately responsible for the overall administration and direction of the RCS through
interaction with the NextGen RCS Board of Directors, the assigned San Diego County staff and
the NextGen RCS Parties.
9. NEXTGEN RCS BOARD OF DIRECTORS
9.1 Representation. There shall be a NextGen RCS Board of Directors, subject to the
Ralph M. Brown Act (California’s Open Meeting Law), that shall be the advisory body to the
Board of Supervisors with respect to matters concerning the NextGen RCS, and shall make
recommendations to the Board of Supervisors that serve the interest of all NextGen RCS
Parties.
Except as noted below, the Board of Directors shall be composed of 10 (ten) directors
representing public safety and public service agencies as outlined below:
County of San Diego (ONE)
City Manager (ONE)
San Diego County Sheriff's Department (ONE)
San Diego County Municipal Police Department (ONE)
San Diego County Fire Agencies (TWO)
Imperial Valley Emergency Communications Authority (TWO)
State of California Department of Transportation (ONE)
Schools Group (ONE)(Schools Group membership on the Board requires that at least
four school districts are NextGen RCS Parties)
9.2 Members. Members of the NextGen RCS Board of Directors shall be determined
in the following manner, according to the type of agency.
NextGen RCS Agreement Page 9 of 19 December 3, 2013
9.2.1 County of San Diego. The representative for the County of San Diego
shall be the Deputy Chief Administrative Officer for Public Safety or his/her designee, preferably
the Director of the Office of Emergency Services.
9.2.2 City Manager. The City Manager representative shall be a City Manager
of a NextGen RCS agency selected by the San Diego City/County Managers Association.
9.2.3 Sheriff’s Department. The delegate from the San Diego Sheriff's
Department shall be the Sheriff or the Sheriff's designee.
9.2.4 Police. The municipal police representative shall be a police chief or
designate from a NextGen Party municipal police department who shall be selected by the San
Diego County Police Chiefs' and Sheriff's Association.
9.2.5 Fire. The two fire service representatives shall be fire chiefs or designees
from NextGen RCS Party fire departments or fire services who shall be selected by the San
Diego County Fire Chiefs' Association.
9.2.6 Imperial Valley Emergency Communications Authority (“IVECA”). IVECA
shall designate two members of its Board of Directors to serve on the NextGen RCS Board of
Directors.
9.2.7 Caltrans. The representative for Caltrans shall be selected by appropriate
state authority.
9.2.8 Schools Group. The representative from the RCS Schools Group shall be
selected by mutual agreement (or majority vote) of the superintendents of the member school
districts.
9.3 Responsibilities of the NextGen RCS Board of Directors. Responsibilities shall
include but not be limited to:
Adopting by-laws to govern the NextGen RCS Board of Director's internal
operations, consistent with the provisions of this Agreement.
Meeting quarterly or more frequently, if necessary.
Developing and approving NextGen RCS operating policies and procedures.
Identifying participating agency needs and requirements.
Addressing concerns of participating agencies.
NextGen RCS Agreement Page 10 of 19 December 3, 2013
Reviewing and adopting recommendations regarding the establishment of
system priorities and talk groups.
Establishing subcommittees as necessary to ensure the interests and
concerns of NextGen RCS Parties are represented and to ensure technical
issues are thoroughly researched.
Formulating the annual budget and submitting it to the County Board of
Supervisors, via the Sheriff's Department, for approval.
Monitoring the implementation of the NextGen RCS.
Conducting programmatic reviews.
Overseeing the establishment of long range plans.
Making recommendations to the County Board of Supervisors.
Making recommendations concerning the approval of customer contracts
and rates for NextGen RCS services.
9.3.1 Board Transition. As set forth in Section 1.6 and 1.7, upon expiration of
the 1995 RCS Agreement, the NextGen RCS Board of Directors shall have all the responsibilities
set forth in this section also with respect to the RCS as it transitions to the NextGen RCS.
9.4 NextGen RCS Board of Directors Terms and Qualifications
9.4.1 Written Designation. Members of the NextGen RCS Board of Directors
NextGen RCS Directors”) shall be designated in a writing submitted to the Sheriff’s
Department by their respective NextGen RCS Party appointing authority. The term for each
NextGen RCS Director shall be determined by her or his respective appointing authority
provided, however, that each NextGen RCS Director shall at all times be an incumbent of a
NextGen RCS Party. All NextGen RCS Directors serve at the pleasure of their appointing
authority.
9.4.2 Alternates. The NextGen RCS Party appointing authority shall also select
an alternate to the NextGen RCS Directors. Alternate members are encouraged to attend
NextGen RCS Agreement Page 11 of 19 December 3, 2013
regular Board of Directors meetings, but shall vote only in the absence of the primary NextGen
RCS Director. No proxy voting is allowed.
9.4.3 Chairperson and Vice-Chairperson. The Chairperson and a Vice
Chairperson of the NextGen RCS Board of Directors shall be biennially elected by a majority
vote of the NextGen RCS Directors. The Chairperson and Vice Chairperson shall serve at the
discretion of a majority of the NextGen RCS Directors, i.e., they may be replaced at any time by
a majority vote of the NextGen RCS Directors. The Chairperson and Vice-Chairperson shall be
selected from members representing NextGen RCS Parties other than IVECA, Caltrans and the
Schools Group. For a NextGen RCS Board of Directors meeting to occur, either the Chairperson
or Vice-Chairperson, and not their alternates, must be present.
9.5 Attendance at NextGen RCS Board of Directors meetings
9.5.1 NextGen RCS Directors are expected to attend all possible meetings to
represent their group interests and to help conduct NextGen RCS business. Arrangements
should be made for the alternate to attend in the absence of the primary representative.
9.5.2 The NextGen Board of Directors shall develop and promulgate a policy
relating to attendance and absences by Directors and alternates.
9.5.3 Resignation from the NextGen RCS Board of Directors shall be submitted in
writing to the chairperson and to the appointing authority.
9.6 NextGen RCS Board of Directors Voting
9.6.1 Members of the NextGen RCS Board of Directors and committees formed
by NextGen RCS Board of Directors (“committees”) shall vote on all items on the basis of one
vote per member.
9.6.2 A quorum for the conduct of business exists when six (6) of the members
are present at NextGen RCS Board of Directors meetings and three (3) of the six present
represent NextGen RCS Parties other than IVECA, Caltrans or the Schools Group.
9.6.3 For any action to be taken by the Board of Directors, the vote in favor of
the action must be a majority vote of the members of the Board of Directors present.
10. SHERIFF’S DEPARTMENT; WIRELESS SERVICES DIVISION
10.1 Sheriff's Wireless Services Division (“WSD”) staff shall serve as advisors and staff
to the NextGen RCS Board of Directors. The Manager of the WSD shall serve as the NextGen
RCS Manager.
NextGen RCS Agreement Page 12 of 19 December 3, 2013
10.2 WSD staff shall manage the day-to-day operation and maintenance of the
NextGen RCS subject to direction from and review by the NextGen RCS Board of Directors.
10.3 WSD staff shall provide support as necessary, but shall not have a voting right on
any business before the NextGen RCS Board of Directors.
10.4 WSD staff shall perform the functions necessary to ensure that specific system
performance guarantees are maintained throughout the term of the agreement.
10.5 WSD Manager. As the manager and operator of the NextGen RCS, the Sheriff's
Department, and more specifically the WSD manager and staff, shall have the responsibility to:
10.5.1 Implement the NextGen RCS.
10.5.2 Seek NextGen RCS Board of Directors approval of major policy decisions.
10.5.3 Develop contracts with vendors.
10.5.4 Provide appropriate staff support to the NextGen RCS Board of Directors.
10.5.5 Retain employees and agents.
10.5.6 As authorized and limited by the County, acquire, hold or dispose of
property necessary to operate the NextGen RCS.
10.5.7 Charge participating agencies for expenses incurred in ongoing
maintenance and operation of the NextGen RCS.
10.5.8 Implement policy a set by the County, the Sheriff and the NextGen RCS
Board of Directors.
10.5.9 Monitor and maintain NextGen RCS performance.
10.5.10 In conjunction with the NextGen RCS Board of Directors, develop and
recommend the annual NextGen RCS budget to the County Board of Supervisors.
10.5.11 Reassign NextGen RCS priorities in extraordinary circumstances and
make emergency repairs as required.
10.5.12 Provide information and support as necessary to the NextGen RCS Board
of Directors.
10.5.13 Provide operating reports and technical information as necessary to
assist the NextGen RCS Board of Directors.
NextGen RCS Agreement Page 13 of 19 December 3, 2013
10.5.14 Establish and maintain accounts and records, including personnel,
property, financial, programmatic and other records deemed necessary by the NextGen RCS
Board of Directors to ensure proper accounting for all ongoing operations and maintenance
costs.
10.5.15 Use the records to justify any recommended adjustments to agency
monthly operating charges.
10.6 Notice of WSD Staff Changes. The Sheriff's Department shall provide the
NextGen RCS Board of Directors timely advance notice of impending personnel changes
affecting any management staff assigned NextGen RCS responsibilities.
11. INFRASTRUCTURE, EQUIPMENT, SERVICES AND FISCAL ELEMENTS
11.1 Infrastructure. The NextGen RCS shall be divided into two infrastructure
components: (a) the “shared backbone infrastructure" and (b) the participating agencies’
infrastructure and equipment. These two parts are divided by a “line of demarcation” at the
NextGen RCS network connection, which is the microwave network or common carrier
termination point(s) used to interconnect the agency's radio consoles and other electronic
communications devices to the RCS network.
11.2 NextGen RCS Shared Backbone Infrastructure Costs. The NextGen RCS Shared
Backbone Infrastructure Cost is defined as the total cost of the equipment and services
required to plan, design, procure and implement a P25 Trunked Voice Land Mobile Radio
System, Microwave Transport Network, and Mutual Aid Conventional Radio System. NextGen
RCS Shared Backbone Infrastructure costs shall not include agency equipment or services used
to connect to the NextGen RCS (such as agency owned microwave transport or leased
commercial connectivity), dispatch center equipment, and subscriber radios (mobile, portable,
control stations) and ancillary devices.
11.3 NextGen RCS Shared Backbone Infrastructure Cost Apportionment – Imperial
County Agencies. The NextGen RCS shall support NextGen Parties in both San Diego County
and Imperial County. In 1995, local government entities in Imperial County formed the
Imperial Valley Emergency Communications Authority (IVECA). IVECA was formed as a Joint
Powers Authority to provide public safety communications services to the residents of the
County of Imperial and its constituent cities. NextGen RCS Backbone Infrastructure costs for
Imperial County sites, except as noted in 11.3.2, shall be the responsibility of IVECA.
11.3.1 IVECA shall bear the full cost of and retain ownership of all infrastructure
installed in Imperial County which primarily supports IVECA agencies. IVECA shall also bear the
NextGen RCS Agreement Page 14 of 19 December 3, 2013
cost for any software and licenses required to operate the IVECA infrastructure on the NextGen
RCS.
11.3.2 Costs for infrastructure installed at the two NextGen RCS sites that
border the two counties, Hendrix Peak and Superstition Mountain, will be apportioned
between San Diego County infrastructure costs and IVECA infrastructure costs based on talk
group usage ratio calculated for calendar year 2013.
11.3.3 IVECA shall be responsible for paying a proportional cost of the "RCS
Core" infrastructure equipment. The “RCS Core” is comprised of the computers networking
devices that manage and control the NextGen RCS. The proportion shall be based on the same
formula used to determine proportional costs for all SD County participating agencies (the
average number of subscriber radios each participating agency had active on the RCS on
September 1, 2013 and July 1, 2014 based on RCS billing invoices. The average number of
radios on the system on those dates will be measured against the total number of all
participating agency subscriber radios.)
11.3.4 The Request for Proposals issued by the County shall require responding
vendors to include a proposal for separate vendor financing for IVECA.
11.3.5 IVECA may be excused from performance under this NextGen RCS
Agreement if IVECA is unable to obtain financing on terms acceptable to IVECA.
11.4 San Diego County Agencies; Cost apportionment. NextGen RCS Shared
Backbone Infrastructure costs for San Diego County governments and agencies that are
NextGen RCS Parties but that are not members of the Imperial Valley Emergency
Communications Authority are as follows:
11.4.1 The NextGen RCS Parties agree that they must pay a proportional cost of
the NextGen RCS Shared Backbone Infrastructure costs.
11.4.2 NextGen RCS Parties further agree that they shall be responsible for
paying their one-time NextGen RCS Shared Backbone Infrastructure Cost as determined by the
apportionment model in Exhibit C, including any penalties for late signing, and any financing
cost.
11.4.3 Total cost for the NextGen RCS Shared Backbone Infrastructure
supporting San Diego County will be divided among all San Diego County NextGen RCS Parties.
The portion of the total cost allocated to each NextGen RCS Party will be based on the number
of radios each NextGen RCS Party has on the RCS, i.e., the “Radio Inventory Method” (“RIM”).
In order to provide NextGen RCS Parties a pre-RIM calculation opportunity to make bona fide
NextGen RCS Agreement Page 15 of 19 December 3, 2013
adjustments to their radio inventories based on their respective individual agency
requirements, the RIM calculation will be done as follows:
Each NextGen RCS Party’s radio inventory for purposes of the RIM calculation will be an
average of the number of subscriber radios each NextGen RCS Party had on the
RCS on September 1, 2013 and July 1, 2014. The average number of radios over
those two dates will be measured against the total number of all participating
agency subscriber radios.
If two or more agencies consolidate, the active radio quantities will be combined
from each agency for the two dates listed above.
For New Parties that did not have radios on the RCS prior to or on September 1,
2013, their radio inventory for purposes of the RIM calculation will be
determined by a review of the New Party's requirements for radio
communications services on the NextGen RCS in the future. The review shall be
conducted by County staff and presented to the RCS Board of Directors for
approval.
11.4.4 Subscriber Radio Inventory Reductions. Radios deactivated from the
RCS between May 1, 2013, and July 1, 2014, will be permanently deprogrammed from the RCS
and will not allowed to be reactivated for use on the RCS or NextGen RCS except as direct one-
to-one replacements for radios that are lost or become nonfunctional.
11.5 Final Cost Apportionment Totals. After all NextGen Parties have signed the
agreement and after the final contract amount for the NextGen system has been determined,
the County will issue an amendment to this agreement to update Exhibit C. (See section 14.3.)
The amended Exhibit C will provide the final cost apportioned to each NextGen Party for shared
infrastructure costs based on the final contract cost and total number of radios (to calculate the
cost per radio). Exhibit C will include the September 1, 2013 and July 1, 2014 radio inventory
totals for each agency and the final average.
11.6 Connection Costs; Maintenance. All NextGen RCS Parties, including both San
Diego County and IVECA agencies, are responsible for all costs associated with procuring and
installing the equipment necessary to connect to the NextGen RCS network and infrastructure
and ongoing costs of connecting to the NextGen RCS. This shall not include maintenance of
agency-owned microwave equipment used to connect to the NextGen RCS network which will
be performed by the Sheriff's Department as a component of the NextGen RCS microwave
network (supported by the NextGen RCS monthly operating fees).
NextGen RCS Agreement Page 16 of 19 December 3, 2013
11.6.1 Maintenance and other costs associated with the provision of primary
and back up electrical power and other facility related costs in support of agency owned
equipment shall be the responsibility of the agency.
11.7 Agency Subscriber and Dispatch Equipment. Subscriber and dispatch equipment
are not part of the backbone infrastructure. The costs of purchasing, operating, and
maintaining P25 compatible radio equipment, P25-compatible dispatch equipment, and any
ancillary agency equipment is the sole responsibility of NextGen Parties.
11.8 Monthly Operating Fees
11.8.1 The costs of ongoing operations and maintenance of the trunked voice
radio system, microwave network, and conventional radio systems shall be allocated to the
participating agencies on a per radio basis.
11.8.2 The cost per radio shall be limited to those radios used on the NextGen
RCS during normal operations.
11.8.3 Radios temporarily added by an agency to handle a disaster or emergency
shall not be a part of determining the agency's ongoing NextGen RCS costs unless the radios are
retained for normal operations following resolution of the disaster or emergency.
11.8.4 The monthly per-radio network operating fee shall be in effect for a
period of one year and shall be adjusted annually to reflect actual costs.
11.9 Other Fees. User fees for as-needed services such as programing and de-
programing radios, training, or other services may be implemented by the NextGen RCS Board
of Directors as required.
11.10 NextGen RCS Reserve “Trust Fund"
11.11.1 The RCS TRUST FUND was established by the Board of Supervisors on
June 19, 2001 (14) for the purpose of having funds available for contingencies and future RCS
upgrades, enhancements and eventual replacement.
11.12.2 Reserve funds, including interest, shall be maintained in the RCS Trust
Fund.
11.13.3 All excess monthly operating fee revenue shall be transferred to the RCS
Trust Fund at the close of each fiscal year.
NextGen RCS Agreement Page 17 of 19 December 3, 2013
11.14.4 Other revenue from non-parties shall either be used for NextGen RCS
operations or may be directed to the RCS Trust Fund upon recommendation of the NextGen
RCS Board of Directors and approval of the Board of Supervisors.
11.15.5 The NextGen RCS Board of Directors shall recommend to the Board of
Supervisors the disbursement of money from the RCS Trust Fund as required.
12. PURCHASE OF NEXTGEN COMPATIBLE EQUIPMENT BY NEXTGEN PARTIES
12.1 Compatibility of Equipment Purchased By NextGen RCS Parties. It is the
responsibility of each NextGen RCS Party to ensure that when purchasing equipment to connect
to the NextGen RCS that such equipment is compatible. The NextGen RCS will be a "standards
based" P25 system which is compatible with subscriber radios and dispatch consoles from
numerous manufacturers provided the equipment has been tested and certified as being P25
compliant. NextGen RCS Parties may submit the specifications of equipment they intend to
purchase to the WSD for back up verification of compatibility. However, the County bears no
responsibility for the purchase of incompatible equipment.
12.2 Contract “Piggybacking”. The County agrees that it will endeavor to include a
piggyback clause” in contracts into which it enters that involve NextGen RCS equipment. For
purposes of this NextGen RCS Agreement, a “piggyback clause” means written permission for
other government agencies to enter into contracts with the vendor on equally favorable or
better terms and conditions.
13. TERM OF AGREEMENT
13.1 The term of the Agreement is for twenty (20) years from the date of this
Agreement.
14. AGREEMENT MODIFICATION; ENTIRE AGREEMENT
14.1. Except as otherwise provided herein, all changes to the NextGen RCS Agreement
may only be amended in writing with the approval of the governing bodies of all parties to this
NextGen RCS Agreement. Prior to processing an amendment, a recommendation shall be
requested from the NextGen RCS Board of Directors.
14.2. Except as otherwise provided herein, this NextGen RCS Agreement constitutes the
entire agreement of the parties and any previous oral or written agreements are superseded by
this NextGen RCS Agreement except as provided for in this NextGen RCS Agreement, except to
the extent that (1) State or Federal agencies may require standard form contracts incorporating
the terms of this NextGen RCS Agreement, (2) supplemental agreements may be required
NextGen RCS Agreement Page 18 of 19 December 3, 2013
relating to IVECA, and (3) separate agreements may be required related to financing and
frequency licensing or transfer.
14.3 Exhibit C Revisions. Notwithstanding any other provision of this NextGen RCS
Agreement, including but not limited to section 14.1, the NextGen Parties agree that, when
final system costs are known, the County is authorized by the NextGen RCS Parties to amend
Exhibit C of this NextGen RCS Agreement to reflect the final system costs in accordance with
the cost apportionment method described in section 11. The NextGen Parties agree that the
final Exhibit C as amended by the County and in accordance with the apportionment method
described in section 11 (see, in particular, section 11.5) shall be the legally-binding Exhibit C to
this NextGen RCS Agreement without further approval by the NextGen RCS Parties. The County
shall distribute the amended final Exhibit C to the NextGen RCS Parties.
15. TERMINATION BY A NEXTGEN RCS PARTY OF ITS PARTICIPATION
15.1 Notice. In order to terminate participation prior to the end of the TWENTY year
term, the withdrawing agency must provide to the NextGen RCS Board of Directors and the
Sheriff’s Department no less than a one year written notice of intent to terminate participation.
In the event there are extensions to the NextGen RCS Agreement, written notice of termination
must be given no less than 120 days prior to the end of the extension.
15.2 Conditions of Termination. A NextGen RCS Party may terminate pursuant to
Section 15.1 on the following conditions:
15.2.1 The terminating NextGen RCS Party must return to the Sheriff’s
Department all County-purchased equipment unless the Sheriff’s Department determines
otherwise.
15.2.2 The terminating NextGen RCS Party is responsible for any and all NextGen
RCS debts attributable to that NextGen RCS Party, regardless of extra-contractual consequences
of termination, including but not limited to breach by the terminating NextGen Party of its own
financing obligations or CSA 135 obligations.
15.2.3 If a terminating NextGen RCS Party brought frequencies to the NextGen
RCS, the terminating NextGen Party and the NextGen RCS Board of Directors shall negotiate in
good faith a settlement that either returns the same or equivalent operable frequencies to the
terminating NextGen Party, or provides equitable compensation if frequencies are left with the
NextGen RCS.
NextGen RCS Agreement Page 19 of 19 December 3, 2013
16. GOVERNING LAW
This NextGen RCS Agreement shall be governed, interpreted, construed and enforced in
accordance with the laws of the State of California.
17. DISPUTE RESOLUTION
NextGen RCS Parties shall meet, confer and attempt in good faith to resolve any disputes
involving performance under this NextGen RCS Agreement. Disputes that are not resolved by the
NextGen RCS Parties shall, upon written request by any one of the NextGen RCS Parties involved in the
dispute, be submitted to non-binding mediation by a mediator agreed upon by the NextGen RCS Parties
involved in the dispute. If the NextGen RCS Parties involved in the dispute cannot agree on a mediator,
they shall ask the American Arbitration Association to appoint a mediator. Each party shall bear its own
costs of participating in the mediation.
18. SIGNATURE PAGES
Each signature page shall include a description and reference to the source of authority
for the person who is signing to execute contracts on behalf of their NextGen RCS Party. This
NextGen RCS Agreement may be executed in several counterparts, each of which shall be
deemed an original and all of which shall constitute but one and the same agreement.
Signature Page to NextGen RCS Agreement
Name of Party:
Party Authorization and Acceptance
On ______________ (Date), Item or Agenda No. _______,
the _____________________________________________
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Signature of Authorized Party Official:
Date of Signature:
NextGen RCS Agreement December 3, 2013
Exhibit A San Diego County-Imperial County Regional Communications System Agreement of March 7,
1995
Exhibit B 1995 RCS Parties
Exhibit C Estimated RCS NextGen System Cost. (Includes Exhibit C-1, C-2, and C-3)
Exhibit C-1 Cost Apportionment for San Diego County Shared Infrastructure Per Party
Exhibit C-2 Cost Apportionment for RCS NextGen Core (Portion of the Shared Infrastructure Cost)
Exhibit C-3 Cost Apportionment for the Combined Infrastructure and RCS NextGen Core
Exhibit D Potential New RCS NextGen Parties
List of Exhibits
NextGen RCS Agreement December 3, 2013
San Diego County-Imperial County Regional Communications System
Agreement of March 7, 1995"
Exhibit A
San Diego County – Imperial County
Regional Communications System
Agreement
Between the County of San Diego and Participating Cities and
Jurisdictions Regarding the Implementation, Governance, Method
of Funding and Costs of a Regional Radio System Providing
Communication Services to Public Safety and Public Service
Agencies Operating in San Diego County and Imperial County.
March 7, 1995
Sr,tr9ltgo
San Diego County - lmperial County
REGI O N AL CO MilI U N ICATIOA'S S YSrE'r AGREEM ENT
Table of Contents
sEcno¡Y SUHHARY PAGE
Purpose and Intent of Agrænnnt
l:""
Reg to n a I Cg ry l u ! ¡ g lt! I lr.: Syr fem (R C S) Ouerubw
4g r*fçIl ç9lilllsenc ìes
Rcs eimgrpaiys
flliïgf .a
t P a rttc Ipa nfs
Pefio rm a n ce Requ I rcm9?ts
RC€ Access Prlorltles
Rç.s 9grgry."?ce .
ßgP1 .? lld Respon stbit ifies
îC,9 liømber Bgard
Çi eoira l g¡o"1";-
Fgpn:?llQugf 9¡r lttg Rcs_ Board 9f lireclors
RCS Board of Dl¡ecto¡s Te¡ms and Qualtftcations
Atten dançg ?.?.q. earuci ptauin oy: uìi i i o ni
RCS Votíng Reguircmg?É
p9e.1nm9nt .o!.l.qformatlon Sentces Suppo ¡t Statî Rote
gil.t 9f..Den.1rc1tlon - Ræponstbtttty of EquÍpment
1lr;I?u o! lcs cinpa4nø equrgiirt
Term of Agreen.9q.t¡ Enttrc Agrcement
lg,æn??1 u9i¡¡¡9"uini
Terml n atlorl o| Ag reement
Filrllllg.Ànnnt¡on
srþnafuros Authorizíng slgnaturcs oî Govemlng pafties
E ûip¡!,,Àl i1,ttà toi tn. Àjr*^.ntt
EtlllPr! iB'l Es-tlnated Agencv on*i¡,rnco¡rs ¡vo¡ci "id
o"t"¡
Etlllptt "C" EximBte ot e"tlrateA e9g Agrcement Stañ-upcosfs
Exhtbít "D" RCS Govemance Structure frcn Charl
15 - rg
1
San Diego County- Imperial County
REG I O N AL C O M M U N I CAr/OruS S YSTEM
Participating Agency Agreement
Purpose and lntent of Agreement
1 .1 . This Mernorandum of Agreement dated as of March 7, 1ggs, betweeh the
parties narned in Exhibit'Aland the county of san-Diego, a political
subdivision of the state of. califomia' provides for the development and
operation of a Regional. communications system lRcs/ benefiting the
radio' communication needs of public'safety and public service agencies
operating in the counties.of San Diego and f mperial.
1.2. Nothing'in thisAgreement is intended to lessen participating mernber
jurisdictions' authority over and responsibility for events occuning within
their jurisdiction.
1.3. ln order to províde an alternate source of funding for agencies participating
in the RCS, the county of san Diego has formed county seruice Area
rcsÁJ 135 pursuant to Government code (GC) section 25210.1'et. seq.
1.4. For participating agencies deciding to use csA 13s to fund their system
costs, the county intends to levy parcel charges according to benefit per
25210.77a GC,.
NOW THEREFORE, THE PARTIES HERETO AGREE AS FOLLOWS
Regional Communications System IRCS) Overview
2.1. The RCS will replace the partícipating public seruice and public safety
agencies'existíng radio communication systems throughout San Diego and
lmperial counties with a modem, trunked radio system.
2-2. The RCS will include a separate Mobile Data system (MDS) that wiil be
used to transmit data for regional public safety and public service users
over 800 MHz radio frequencies dedicated to that purpose. Participation in
the MDS is not mandatory, and the MDS coverage area will be subject to
agency participation.
2.3. The RCS shall provide effective and reliable radio communications for
routine intra-agency operations as well as inter-agency communications
throughout the region during mutual aid and disaster operatÍons. Public
safety and public seruice agencies throughout the counties of san Diego
and lmperial will have the opportunity to join the RCS.
2.4. For the purposes of this Agreement, pubtic safety and pubtic servíce
agencies are defined to include:
2.
Participatlng Agency Agreement
fu ü4o Cortro¡. hp.ùl CollrÞ
R¡dñl Caürû¡túGrt¡dt q/ttâñ
3.
4.
5.
2-4'1. Public Safefyincludes alllaw enforcement, fire service, EMS and
disaster preparedness agencies in San Diego County and
lmperialCoung.
2.4.2. Public Serulce includes the State of Califomia Department of
Transportalion (CALTRAIVS) District 11 and other participating
agencies in the counties of San Diego and lmperialwhose
primary responsibilþ is providing citizens with services otherthan
law enforcement, fire service and disaster preparedness.
2-5- All law enforcement, fira service, disaster preparedness and participating
public service agencies in San Diæo County and lmperialCounty shall
have access to mutualaid communications capabilities.
2.6. Communications with agencies that have installed theiroryn 800 MHz radio
systems shall be facllitated via interfaces to the RGS.
Agreement Contin gencies
This agreement is void unlees llnancing forthe radio system inf¡:asfr¡dure is
approved by the san Diego county Board of supervisors and the necessary
ffnancing closes. As to the County of lmperlal, this Agreement shall termináte if a
CSA or other funding mechanism for communications purposes is not established
within two years of the date of this Agreement.
RCS Participants
4.1- The RCS shall be designed to support the requirements of San Diego and
lmperial coun$ public safety and designated public service participants.
4.2. CALTRANS radio requirements shall be supported throrghout Distrid 11,
which íncludes the counties of San Diego and lmperial in their entirety.
4.3. Allparticipants shallreceive equitabte representation on the Regional
communicatlons system Member Board lRcs Mq¡¡ber Board) as set
forth in this Agreement.
4.4. As part of implementing this agreement, participating agencies shallco-
license or transfer their cunenüy allocated 800 MHz frequencies to the
County of San Diego for use in the RCS.
4.5. No actions by the RCS Board of Directors, by the county of san Diego or
by the county of lmperial may be so broad in nature that they negatively
affect or impact the operationat or tegal integrity of its individual membei
açncies.
Additional Participants
5.1. As system capacity permits, the RCS Board of Directors may approve
other agencies joining the RCS on a case{y-case basis aflerthe date of
this Agreement.
5.2. Prionrty consideration shail be grven to agencies with licensed, public
safety/public service E00 MHz fequencies that can be coJicensed or trans-
March 7, 1995
Page2
srlrOlôgo
Parllclpatlng Agency Agreement
6
ferred to the RCS, if such action can result in enhanced radio
communications capabilities for all paft icipants.
Performance Requ i rcment¡
6.1. The RCS shall be designed to provide a high levelof service and
responsiveness, wiür region-wide coverage and capacity for all planned
users throughout the term of this Agreement.
6.2. The RCS design objec{ives for the performance of portable and mobile
voice and data radio equipment, and the quality of coverage provided shall
be determined by the RCS Board of Directors and appropriate Gounty of
San Diego staff.
6.3. The RCS shall be desþned to meet the loading requirements of the
anticipated busiest hour for all planned users¡ over the life of the system.
6.4. The actual RCS coverage plan shall be determined by the RCS Board of
Directors.
RGS Access Priorities
7.1. ln the event thEt all radio channels in the RCS are busy, users wanting to
speak shall be prioritized as follows, regardless of how long they have been
waiting.
7.1.1. Priority One- Emergcncy ldentifrcation.
An Emergency ldentification is defined as the message received
when a public safety member calls for immediate assistance by
activating en emergency button or switch on the user radio
equipment.
7.1.2. Priority Two- Public Safety
7.1.2.1. Public Safety includes the normal daity radio
transmissions of law enforcement, fire service,
paramedic providers and disaster preparedness
perconnelusing the RCS.
7.1.2.2. Public Safety also includes RCS users whose normal
lower pñoritles have been temporarily changed to
resolve an unusual occurenoe or largo scale disaster.
7.1.3. Priority Three - Non-Publlc Safety, Special Event
Non-Public Safety, Special Event includes planned events
involving public service agency participants that are beyond the
scope of their normaldaily operations.
7.1.4. Priority Four - Non-Publtc Safety, Regulan
Non-Public Safety, Regular includes the normaldaily radio
transmissions of public service agencies using the system.
RGS Governance
Cou'ty
7
March 7, 1995
Page 3
8.
g',Ãgl.ao C'¡r''lÞJ
Pañlcipatlng Agency Agreement
8'1. The overall goal in govem¡ng the RCS shall be to establish an operational
and management structure that will provide authorfi to participants during
the RCS's development and in the subsequent ongoing administration anà
manag€mentthroughout the term of this agreement. Exhibit "D" depicts an
RGS govemance llowchart.
8.2- The RCS Member Board and the RCS Board of Directors are established
by this Agreement, the duties and responsibilities of which are set forthingl0andg1l.
8.3. The govemance objectives include:
8.3.1. Provide a structure which retains administration and fiscal
responsibility of the system in the control of the participating
agencies.
8.3.2. Allow the use of a CSA tunding mechanism.
8.3.3, Establish an organization whictr facilitates decision maklng.
8.3.4. Leverage resources where appropriate.
8.3.5. Develop an organizafon which will remain flexible and meet the
neede of the partícipants over tha term of the agreement.
9. Rolee and Responsfbllifeg
As required by the Califomia CSA law, the San Diego County Board of Supervisors
shall have ultimate legal and fiscal control overthe RCS. Subject to such ultimate
control, the Board of Supervisons shalldelegate the fiscal control and operational
administration of the RCS to the RCS Board of Directors.
10. RCS tUlember Board
10.1 . Each of the parties to this Agreement desires to participate in the
govemanoe of the RCS as a member of the Regional Communications
System Member Board to be formed underthe provisions of this
Agreement.
10.2. The RegionalCommunications System Member Board shall have re-
sponsibility for, and shall provlde administration of components of the RCS
that are common to allparticipating agencies.
10.3. Each participating agency shall appoint one representative to serve on the
RCS Member Board. Representatives to the RCS Member Board shall
serve at the pleasure of thelr rcspective appointing authority.
10.4' A participating jurisdiction with multiple agencies whose public saÍety and
service radio communication needs are being met by the RCS shall be
entitled to one representative on the RCS Member Board for each type of
agency. (1. E., a participating city whose police and fire departmente use
the RCS shall have a RCS Member Board representative from each
department.)
March 7, 1995
Page 4
å/rtdi
Partlclpatlng Agency Agrcement
g.t94,rocÃ!y-
Cilr!'¡rür¡CoÈ glËtat
11.
10.5, The RCS Member Board shall be respons¡ble for recommending
operational changes and for participating in other comm¡ttees, or in other
ways deemed appropriate by the RCS Board of Direc{ors.
10.6. The Rcs Member Board shall be responsible for approving the annual
budget.
RCS Board of Dircctors
11.1. The RCS Board of Directors shall be composed of RCS representatives of
each type of participating public safety/public service agency.
11-2. Members of the RCS Board of Directors shallbe determined in the
following manner, according to the type of agcncy.
11.2.1. San Diego County:
11.2.1.1. The delegate from the San Diego Sheritrs Department
shall be the Sheritrorthe Sheriffs designate.
11.2.1.2. The representative forthe Coung of San Diego shall
be the Chief Adminisbative Officer (CAO) orthe CAO's
designate, preferably fom the Office of Disagter
Preparedness.
11.2.1.3. The municipalpolice representative shallbe a police
chief or designate from RCS member agencies who
shallbe selec{ed by the San Diego County Police
Chieß and Sheriffs Association.
11.2.1.4. The municipal fire representative shall be a fire chief or
desþnate from RCS member agencies who shall be
selected by the San Diego County Fire ChieÊ
Association.
11.2.1.5. The fire dlstrict representative shall be a fire chief or
designate fom RCS member agencies who shallbe
selected by the San Diego County Chapter, Fire
Districts Association of Califomia.
11.2.1.6. The North County Dispatch Joint Powers Authority
JPA) representative shall be a fire chief or designate
from RCS member agencies who shall be selected by
the North County Dispatch JPA goveming body.
11.2.1,7. The Heartland Communications Facility JpA (HCFA)
representatives shall be designates from RCS member
agencies who shall be selected by the HCFA goveming
body.
11.2.2. lmperial County:
11.2.2.1. The delegate from the lmperialCounty SherifFs Ofüce
shall be the Sherifi or a desþnate.
Merch 7, 1995
Page 5
Pañicipating Agency Agreement
SrhDfq¿ Córrllùy-
Cdiíüdêaf¡oil qÉtå|ü
11.3.
11.4.
11,2.2.2. The representat¡ve for the County of lmperial shall be
the CAO or a designate.
11,2.2.3. The municipal police representative shall be a police
chief ordesignate from RCS member agencies who
shall be seleded by the lmperial County Police Chiefs
Association.
11.2.2.4. The municipal fire representative shall be a fire chief or
designate from RCS member agencies who shall be
selected by the lmperialCounty Fire Chiefs
Association.
11.2.2.5. The fire district representative shall be a fire chlef or
designate from RCS mamber agencies who shall be
x'r"$,""l,H|?"Jïåîil.tou*chapter'F'eDistricts
11.2.3. The representative for CALTRANS shall be a designate selected
by appropriate state authority.
11.2.4. This Agreement provides forthe addition of two public service
members of th€ RCS Board of Directors, to be added when public
service agencies join üre RCS.
The RCS Board of Directors shall be responsible for the overall
administration and direction of the Rcs through interaction with the San
Diego County Board of Supervisors, the assigned San Diego County staff
and the RCS Member Board.
Specific responsibilities of the RCS Board of Dírectors shallinclude:
11.4.1. Formulating the annual budget and submitting it to the RCS
Member Board for approval.
11.4.2.
11.4.3.
11.4.4.
11.4.5.
ldentifying participating agency needs and requirements.
Establishing subcommittees as necessary to ensure the
interests and concems of each user agencT are represented
and to ensure technical issues are thoroughly researched.
11.4.3.1. The RCS Board of Directors shalt establish a
committee of MDS user agencíes to adminíeter the
MDS and to make appropriate recommendations.
11.4.3.2. lf all RCS user agencies are MDS participants,
administratlon of the MDS shallrevert to the RGS
Board of Directors.
Monitoring the implementation of the RCS.
Reviewing and adopting recommendations regarding the
establlshment of system priorities and talk groups.
Developing and approving RCS operating policies and proce-
dures.
11.4.6
March 7, 1995
Page 6
ataD'tTo 6or¡îry- hçrt ¡ ør¡rtt
Partlclpatlng Agency Agrrement
11.4.7. Overseeing the establishment of long ltrnge plans.
11.4.8. Overseeing scheduled system reviews at intervals determined
by the RCS Board sf Directors, but not to exceed three years.
11.4.9. Budgeting and approving the disbursement of money from alt
CSA 135 funds.
11.4.10. Making recommendations to the San Diego County Board of
Directors regarding the inclusion of additional RCS participants.
11.4.11. Addressing concems of participating agencies.
11.4.'12. Adopting appropriate actions to adjust RCS policies or
procedures.
11.4.13. Adopting by-laws to govem the RCS Board of Directo¡,s
intemal operations.
11.4.14. Meeting quarterly or more frequenfly, if necessary.
11.4.15. Appointing a new Chairperson annually.
11.4.16. Conduciing an annual fiscal audit.
11.4.17. Conducting periodic RCS audits.
11.4.18. Discharging otherduties as required by statute.
12. Repmsentaüon on the RCS Board of Dircctorc
12.1. As of the date of this Agreement, the following tyæs of agencies shall be
represented by appointment to thE RCS Board of Directors:
12.1.1. San Diego County:
12.1.1.1. Sheriffs Department
12.1.1.2. County Reprcsantative (Offce of Disaster
Preparedness)
12.1.1.3. Munlcipal Police
12.1.1.4. Municipal Fire
12.1.1.5. Fire Dietricts
12.1.1.6. North County Dispatch Joint Povvers Authority
12.'1.1.7. Heartland Communications Facility Joint Powers
Authority
12.1.2. lmperialCounty:
12.1.2.1. Sheriffs Department
12.1.2.2. County Representative
12.1.2.3. Municipal Police
12.1.2.4. Municipal Fire
March 7, 1995
Page 7
Participatlng Agency Agruement
âtltDlogo h!îE Coonl
ß.t¡ord Cf, tf, ¡tricttoil gyrtaûr
12.1.2.5. Fire Districts
12,1.3, CALTRANS
12.1-4. Public Service agencíes shallseled two delegates at large.
13. RCS Board of Directop Tems and eualifications
13.'1. Terms for members of the RGS Board of Directors shall be determined by
their appointing authority. Allmembers of the Board of Directors serve at
the pleasure of their respective appointing authority.
13'2. The appointing authority shallalso select an altemate to the RCS Board of
Direc'tors. Altemate members are encouraged to attend regular Board of
Directors meetings, but shallvote only in the absence of the regular
member.
13.3, Only representatives of agencies participating in the RCS may be selected
to the RGS Board of Directors.
13.4. The Chairperson and a Vice Chairperson of the RCS Board of Directors
shall be biannually elected by a majorfi vote of the Directors. During their
term, the Chairperson and Vice Chairperson Ehallserve at the discretion of
a majorig of the Directors.
13.5. Attendance at Board of Directors meetings:
13.5.1. Members of the Board of Directors arc expected to attend all
possible meetings to represent their group interests and to help
conduc{ RCS business. Anangements should be made forthe
altemate to attend in the absence of the primary representative.
13.5.2. To remain on the Board of Directors, a director may not exceed
more than three absences from regularly scheduled Board of
Directors meetings during a County of San Diego fiscalyear
July I through June 30).
13.5.3. lf a director exceeds more than the allowable three absences in
a fiscal year, the Board of Directors shall request a replacement
from the appointing authority unless, bEcause of extraordínary
circumstances, the Board of Direclors votes to allow one
additional absence.
13.5.4. Altemate directors shall be subject to the same requirements for
all meetings they are required to attend.
13.5.5. An absence by both the primary director and the altemate
director representing the same appointing arfhority shall be
counted against both parties.
13.5.6. By vote of the Board of Directors, a leave of absence may be
granted to a primary or altemate directorfor no more than 1g0
days. Only one leave of absence may be granted in any twelve
month period.
March 7, 1995
Page I
n9',$Colff,ìt
Partlclpatlng Agency Agreement
13.5.7. Resignation from the Board of Directors shall be submitted in
writing to the chairperson and to the appolnting authority.
14. Attendance and Participaüon by the public
14.1. Ralph ill. Brcwn Act. All meetings of the RCS Board of Directors and
RCS Member Board shall be noticed and conduded in accordance with the
provisions of the Ratph M. Brown Act (GC SS49S0 et. seq.).
14-2. Local, state and federal representatives of public safety or service agencies
who are not parties to this Agreement may participate in RCS BoardofID¡redors, Member Board orcommittee meetings as members of the public,
but shallnot have voting rights.
14.3. Representatives frorn non-participating agencies may not serve in any
official capacity ín respect to RCS administration, management or
operation.
15. RGS Voüng Requirements
15.1. Members of the RCS Member Board, Board of Directors and committees
shall vote on all items on the basis of one vote per member.
15.2. A quorum for the conduct of business exists when a majority of the
members are present at Board of Directors, Member Board and other
committee meetings.
15.3. Actions on all boards and commfiees shallbe determined by a majority
vote of memberc present at a meeting when a quorum exists.
15.4. An agency may not designate another agency to be its proxy.
15.5. In the case of RCS Board of Diredore actions, the altemate delegate shall
only have a voting right in the absence of the rcgular delegate.
16. Gounty of San Diego, Department of lnformaüon Seruices (DlS)
Support Staff Role
16.1. DIS staff shallserve as an advÍsory and staff functlon to the RCS Member
Board and RCS Board of Directors.
16.2. DIS staff shall manage the day-today operation of the RCS subject to
direction from and review by the RCS Board of Directors .
16.3. DIS staff shall provide support as neoessary, but shall not have a votlng
right on any business before the RCS Member Board, the RCS Board of
Directors, or eny committees.
16.4. DIS staff shall perfurm the func-tions nêcessary to ensure that specific
system performance guarantees are maintained throughout the term of the
agreement.
16.5. As the menager and operator of the RGS, the Department of lnformation
Services shallhave the responsibility to:
March 7, 19gs
Page 9
Partlclpatln g Agency Agraement
9rngL4oC$rd-CffiÐ
Rr¡la+C Commudcrt/m gptar
16.5.1. Provide appropriate steff support to the RCS Board of Directors
as requested, within budgetary restraints.
16.5.2. Seek RCS Board of Directors approval of major pol¡cy decisions
related to the RCS.
16.5.3. Develop contracts wilh vendors and submit to RCs Board of
Direstors for approval.
16.5.4. lmplement the regional 800 MHz public safety voice and data
radio systems.
16.5.5. Retain employees and agents.
16.5.6. Acquire, hold or dispose of propefi necessary to operate the
RCS.
t6.5.7. Charge participating agencies for expenses incuned in ongoing
maintenance and operation of the RCS.
16.5.8. lmplementpolicy.
16.5.9. Monitorand maintain RCS performance.
16.5.10. ln conjunction with the RCS Board of Directors, develop and
recommend the annual RCS budget.
16.5.11. Reassign RCS priorities in extraordinary circumstances and
make emergency repairs as required.
16.5.12. Provide information and supprt as neoessary to the RCS Board
of Directors.
16.5.13. Provide operating reports and technical information as necessary
to assist the RCS Board of Directors.
16.5.14. Establish and maintain accounts and records, including
personnel, property, ftnancial, programmatic and other records
deemed neoessary by the RCS Board of Direclors to ensure
proper accounting for all ongoing operations and maintenance
costs.
16.5.15. use the records to justify any adjustment to agency benef¡t
charges.
16.6. The Directorof Dls shall provide the RCS Board of Directors timely
advance notlce of impending personnel changes affecting any
manegement staff assigned RGS responsibilities.
Agency Costs and GSA Benelit Charges
17.1. The Department of lnformation services sha[ imprement, manage and
operate the 800 MHz trunked radio backbone and microwave systems.
17.1.1. Costs for agencies participating at the time the RCS is
implemented are reflec{ed in Exhibit "8". MDS participation
costs are separate from voice radio system costs.
March 7, 1995
Page 10
17.
flrlllf,rto @- brprl¡l6.unty
Partlclpatlng Agency Agreement
17.1.2.Costs for agencies joining subsequent to the implementation of
the RCS:
17.1.2.1. The County of San Diego shall assume the costs of
implementing the voice and data radio backbone
systems in areas where agencíes have not committed
to RCS participation.
17.1.2.1.1. RCS coverage in those areas shall meet
the requirements of the County of San
Diego.
17.1.2.1.2. Costs to enhance coverege to satisfi the
needs of an agency joinlng the RCS
subsequent to the original implementation
shall be the joining agenc¡/s responsibilþ.
17.1.2.2. An agency joining the RCS shall be responsible for
paying their odginal on+time costs as represented in
Exhibit'Bn, plus financing costs that have incuned
slnce the date of this Agreement. Th RCS Board of
Direc{ors shall reim bunìe appropriate fi nancing
expenses to the County of San Diego in relation to
s17.1.2.3.
@fAilEIE If Santee dec¡des to þin tl:p RCS efrør tue yøaæ ot
the 15 year agrcement haw passed, ffieir cosfs wìll indude:
1) tholr eslÍnated onelime oosús as sñowr¡ in Exhìblt'8" and,
2) assocíated frnancing østs forthe frßt frvayeârs, as ehowtt
in ExhÍbit"C'.
The RCS fuardof Dißc1biæshallthen rcimbusotheCounty of
San Dlego for prlncipal and frnncing expenses that nsulted
because of Senfee's abænce during tlrn initial fwe yearc.)
17 .1 .2,3. An agency or jurisdiction that wants to join the RCS
must pay a proportionalcost of the overallvoice ¡adio
backbone and miorowave development investment,
lf the agency or jurisdiction decides to use CSA f 35
for funding, it must llle an application with the San
Diego Coung LocalArea Formation Commission
t AFCO) to join CSA 135. Each agency is
responsible for its own costs associated with the
LAFCO process.
17.1.2.4. Allfunds received from agencies joining the RCS shall
be deposited in the CSA 135 aocount for appropriate
distribution by the RGS Board of Direclors.
17.2- The agency may use a funding method other than csA 13s to pay for its
RCS origination and operating expenses.
March 7, 1995
Page 11
gl,'ngbtoc,,úW
PaÉicipatlng Agency Agreement
17 '3. Ongoing operations and maintenance costs shall be shared equally by the
participating agencies and shallbe based on the established formula. (See
Exhibit "B")
17.4. Monthly Operating Fees
17.4.1. The costs of ongoing operations and maintenance of the trunked
voice radio system, mobile data radio system and microwave
system shall be allocated to the participating agencies on a per
radio basls.
17 .4.1.1. The cost per radio shall be limited to thos€ radios used
on the RCS during normal operations.
17,4.1-2. Radios temporarily added by an agency to handle a
disaster or emergency shall not be a part of
determining the agency's ongoing RCS costs unless
the radios are retained for normaloperations following
resolution of the disaster or emergency.
17.4.1.3. The costs of ongoing operations and maintenance on
the voice system and the mobile data system shall be
determined separately, since not allagencies will
decide to use both systems. Therefore, the monthly
operating fees for radios on each system may be
different.
17.4.2. Afrer resolving which agencies are participating and determining
f¡e aclual number of radios to be included in each system (voice
and data), the cost per egency shall be fi'nalized.
17.4.3. The final cost shall be in effect for a period of one year and shatl
be adjusted annually to reflect actual costs.
17.5. Reserve Funds in CSA 135 Account
17.5.1. One of the responsibilities of the RCS Board of Directons is to
budget the disbursement of money from üe CSA 13S acæunt.
17.5.2. Allfunds received by the county of san Diego from ail RCS
participating agencies, forthe purpose of funding the RCS shall
be deposited into the GSA 135 account.
17.5.3. Reserve funds, inchding interest, shallbe maintained in the CSA
135 account forthe purposes of contingencies and for RCS
upgrades and enhancements.
17.5.4. CSA 135 neserve funds can only be used br Regional
Communications System purposes and on approvatof the RCS
Board of Direc{ors by majority vote.
17.5,5. The RCS Board of Directors shafl review csA 1gs fund levels
annually and take appropriate action.
17.6. CSA 135 Zone Option and Costs
March 7, 1995
Page 12
EÉtdrt
Partlcipa$ng Agency Agreement
i Olcfo CÓr¡ntv - fñFtd Can3y
Raglotrrl Caaualcrgar âyctar
17.6.1. Each participating agency shal! have the ability to custornize their
own CSA 135 requirements for other RCS components, including
user eguipment, communications center equipment and operating
costs, by developing a CSA zone.
17.6.2. Each agency establishing a zone shall have the responsibilÍty to
develop an annual zone budget and zone benefit fee schedule.
17.6'3. The CSA funds generated within the zone may only be utilized to
meetthe requirements of thatzone.
17.7. Unless othenilise agreed, maintenance of agency owned RCS equipment
shall be provlded by Department of lnformation Services staff assigned to
the RCS. All associated maintenance costs shall be included as a part of
the agency monthly operating fees.
17.8. Maintenance and other costs associated with the provision of primary
commercial and back up 1101240 volt A. C. electrical porcr shall be the
responsibility of the egency.
17.9. Unless othenrise determlned by separate agreement, each participating
agency shall be responsible for he costs associated with connec.ting to the
RCS backbone from the polnt of demarcation to the agency radio systern
equipment.
18. Polnt of Demarcation for Reoponalbil¡ty of Equipment
18.1. Unless othenrise determined by separate agreement, the demarcation
point between RCS responsibili$ and agency responsibility is the
microu¡ave radio channel bank equipment termination blocks that are used
to interconnect the agency radio consoles and other electronic devices
used for voice and data communicailons to the channel banks.
18.2. Each participating agency shallbe responsible for allcosts associated with
their mobile data system applícation development, user equipment and
integration from the poÍnt of dernarcation.
19. Purchage of RCS Compaüble Equipment
19.1. Each participating agency agr"es to meet County of San Diego
specifications, including brands and rnodels when appropriate, for
associated equipment used to interconnect to the RCS.
19.2. Participating agencies agree to submit specifications of radio system
related equipment orders to Coun$ RCS stafito ensure compatibilÍty
before purchase.
19.3. Associated equipment may be purchased through the County of San Diego
to insure compatibility and favored pricing.
20. Term of Agreement
The term of agreement is for frfreen years ftom the date of this Agreement.
21. Agreement Modlftcation; Entire Agroement
March 7, 1995
Page 13
9l,nglêto h)trif -Cdrlþl
Participating Agency Agreement
21.1. This Agreement may only be amended in writing with the approval of the
goveming bodies of all parties to this Agreement. Priorto processing an
amendment, a recommendation shall be requested from the RCS Board
of Directors.
21.2. This Agreement constitutes the ent¡re agreement of the parties and any
previous oral orwritten agreements are superseded by this Agreement.
Subsequent agreements may be entered into with CALTRANS and the
County of lmperial conceming RGS matters.
22. Termination of Agreement
22.1. ln order to terminate participation prior to the end of the fifteen year term,
the withdrawing agency must provide no less than a one year vwitten notice
of irrtent to terminate participation.
22.2. Termination shallbe granted provided that the withdrawing party:
22.2.1. Retums to the RCS all equipment for value that the RCS Board of
Directors determines is required to maintain the RCS for all
remaining userc; and,
22.2.2. lf the termination compromises the legality of the CSA benellt
charges in the jurisdiction of the withdrawing agency, sucfi
agency shall be responsible for the remaining debt payments
which would have aggregated from the CSA.
22.2.3. lf an agency that brought frequencies to the RCS opts to
terminate, the RCS Board of Directors shall negotiate a
settlement that either retums the same or equivalent operable
frequencies, or provides equitable compensation íf frequencies
are left with the RCS.
23. Arbitnüon
23J. lf settlement on an issue cannot be reached between the grieving or
terminating agency and the RCS Board of Directors, binding arbitration
shallbe employed to reach a settlement.
23.2. The arbitrator shall be selected by mutual agreement of the RCS Board of
Directors and the termlnating agency.
23.3. lt Ehall be the duty of the arbitratorto hear and consider evidence
submítted by the parties and to thereafier make written findings of fact and
a disposition of the settlement which shall be binding in nature, except as to
lssues of law.
23.4. Each party to a hearing before an arbitrator shall bear his own expenses in
connection therewith.
23.5. All fees and expenses of the arbitrator shall be bome one-half by remaining
members of the RCS and one-half by the grieving orwithdrawing agency.
March 7, 1995
Page 14
âi9bepcd'q-
R.taond Cñû¡dcrllo'!Í}¡r¡t .n
Agpncy Agrcement
lN vlrlrNEss WHEREOF, ttre parties hercto do afïir their signaturcs.
COUNTY OFSÁ'Y DIEGO
Board of. Quperuisorc Approval
Der6:Ît/lAR'7looç
C'TY OF CARLSBAD
CouncilApproval
Date: n¡ncn , l9g5
CouncilApproval
Date: xrne-n zr. lqqs
CITY OF Ifr'PERIAL BEACH
CouncilApproval
Date:
CITY OF IÆMON GROVE
CouncilApproval
C'TY OF POWAY
CouncilApproval
Date:tt - t9 -15
c,TY OF SArìt trÁRcos
Council
C'fY OF SOLANA BEACH
Mayor
Mayor
Mayor
1.
I i
Council
Fa¡a'15
March 7, 1995
aglg,go
hibÍt,'Au
Pañicipating Agency Agreement
PARTIES TO THE MARCH 7, 1995 AGREEMENT
1. Alpine Fire Protection District
2. Bonita-Sunnyside Fire protection District
3. Borrego Springs Fire protection District
4. City of Cartsbad
5. City of Del Mar
6. City of Encinitas
7. City of lmperiat Beacþ
8. Cíty of Lemon Grove
9. City of Poway
10. City of San Marcos
11. Gity of Solana Beach
12. City of Vista
13. Califomia Department of Transportation, District l1
14. County of lmperial (all county and city public safety agencíes, all territories)
15. county of san Diego (county puöric safety and service agencies)
16. Deer Springs Fire protection District
17. East County Fire protection tlstrict
18. Heartland Communications Dispatch Facility JpA
19. Julian - Cuyarnaca Fire protection District
20. Lakeside Fire protection District
21. Lower Sweetwater Fire protection District
22. North County Dispatch JpA
23. Pine Valley Fire protection District
24. Rancho Santa Fe Fire protection District
25. Rural Fire Protection District
26. San MiguelConsolidated Fire protection District
27. Valley Center Fire protectíon District
CrJ¡tty
gf,itün
March 7, 1995
9ll.ü.&
F.tnlcmu¡addtg!ür-nE)û¡bit nB,'
Pañic i pati n g Agen cy Ag reemen t
ESTIMATED AGENCY ONE-NME COSTS
Combtned Voice and Data Backbone
arb t*..ú
t
ÈCJa brht
dø
b.l*tl
Hú
H
HCdICl-t Hú
Ualncorporrd lzg,atg 1,121,110 tl.æ* ta¡t90,52s sô,ts5,256 !m,sr4 ,r.06¡r,312
c-rrb'd 3a,8sr ã8 7ã 5.67* ¡r5:t7$ r.586,650 5a,52f tgt.(B!,
D.l I'l¡¡ a.8A{¡ lg.*til OS4tt ¡B.at3 152,127 5,Zg t8,3lg
Enclolt8 19,7&f ISO,Z*¡ . ¡t¡tã6 3Sa,Z9t lÆ,2g .e,ß{ t¡t8.8tt
Ù!P.fùl!...i a,&16 €3,198 f .76I t¿to,¡ßr /F¿198 16,9t{ 59,271
l¡¡¡on orsvr 6.9,(t ôX2A5 l.8tfú t4{,9€s SO7,9Så i,157 6t,172
on'¡y Il..uJ ltf ,æ,{ 3,tr* zaq?sT B7f ,6s6 29,g6s 1o¡t,gn¡,
t¡ t¡¡em 12.478 ri6,?¡r3 r$* 26g,919 ga1,zgr 3r,7go f Í,it6a
tolar. ¡.*l¡ t2,900 a7.6t8 t.æta 1G,939 tnÐA tztït t[,tæ
vkr¡ t9.eþ 2ß,328 16693 131,ñt 1,5S0.558 3a,4f I iff,ffir¡
ä**i3ï¡\Sl¡Fr$ÃSfi($tllirtUtñl-lr$
ltE:r,åFE$ñSFffitWßãft
Chrl¡vl3t¡ 3tt,652 380,r¿6 to,t¡¡Ttó AO!,Z3:¡ ¿S09.16 g€,s,ts 306¡fO
Goron¡do ro,{s6 B43ss 1.7i* t38,66i ¡ås,sgo r6,6s8 5g,sft
E c¡lon 17.918 z¿to,æ 6.68!a 53|3.ge1 r,8rt,t92 81,3æ U5.3rt{¡
t¡ Lr. l6.rxtr t86,
5..t E f¿ Cc¡ûy.li?rtlcðlct
E û¡b¡t'C"
P art lc Ip atl n g Agen cy Ag rce m e n t
ESNMATED COSTS OF AGENCY ENTERING SYSTEM AFTER MARCH 7, 1gg5
Clty ol Sanfüe
Numbct of Benellt Unlt¡ 125,247
Pcrcent of Tot¡l Beneflt 3.49%
Flnancing Cost¡ of One Tlme Co¡t for 15 year¡ at 8.5!å ApR
Principal ' FlnandngTotalE975,448 $786,510 $1,761,958
Annual Payment
117,464
Annual Payment lf Joln ln year
Year
1
2
3
4
5
6
7II
10
11
12
13
14
15
Annual Payment
8117.464
125,854
135,535
Sl¿16,8Í10
160.178
t176,196
s195,773
822:0,24
2s1,708
s293,660
352,392
140,490
t567,319
880,979
1,761,958
rÁnn¡| ffi
Annual Payment for Late Starting
20m
ItdÞæ
I€
rom
E
s0ææ
0
1 2 ! ¡l 5 6 7 E 0 tOlt 12 t3tat5
Sbrthg Yr
March 7, 1995
SmDlcgo
Cmutrrtfm9¡rtrrExhib¡t'D"
Pañic ip ati n g Age n cy Ag reem ent
GOVERNANCE STRUCTURE
San Dlego Couttty
Board of Søpervisolc
RCS
Boañ of Dìrectorc
RCS
Committees
RCS
MeÍnber Board
Member Agency
County Sfaff
e
Reporting Relationships,
Lines of Communicatíon
March 7, 1995
NextGen RCS Agreement December 3, 2013
1995 RCS Parties Status
Alpine Fire Protection District Existing
Bonita-Sunnyside Fire Protection District Existing
Borrego Springs Fire Protection District Existing
City of Carlsbad Existing
City of Chula Vista Existing
City of Coronado Existing
City of Del Mar Existing
City of El Cajon Existing
City of Encinitas Existing
City of Escondido Existing
City of Imperial Beach Existing
City of La Mesa Existing
City of Lemon Grove Existing
City of National City Existing
City of Oceanside Existing
City of Poway Existing
City of San Marcos Existing
City of Santee Existing
City of Solana Beach Existing
City of Vista Existing
County of San Diego Existing
Deer Springs Fire Protection District Existing
Heartland Communications Facility Joint Powers Authority Existing
Imperial Valley Emergency Communications Authority (IVECA)Existing
Julian-Cuyamaca Fire Protection District Existing
Lakeside Fire Protection District Existing
Metropolitan Transit System Existing
Mira Costa Community College District Existing
North County Dispatch Joint Powers Authority Existing
North County Fire Protection District Existing
North County Transit District Existing
Rancho Santa Fe Fire Protection District Existing
San Diego Rural Fire Protection District Existing
San Diego Unified Port District Existing
San Miguel Consolidated Fire Protection District Existing
Santee School District Existing
State of California Department of Transportation (Caltrans)Existing
State of California, California Highway Patrol/El Cajon CHP Existing
Valley Center Fire Protection District Existing
Viejas Reservation Fire Department Existing
Vista Fire Fire Protection District Existing
Pine Valley Fire Protection District ¹Former
Padre Dam Water District ²Former
East County Fire Protection District ³Former
Original Signator - Never came on system (no radios on system)
Terminated RCS Agreement on January 7, 2013
Consolidated with San Miguel Consolidated Fire District in 2008
1995 RCS Parties
Exhibit B
NextGen RCS Agreement December 3, 2013
Estimated Total Shared Infrastructure Cost 105,000,000$
Less estimated IVECA Infrastructure of $9 Million (includes estimated
proportional share of NexGen core)(9,000,000)$
Less Grants/RCS Trust Fund (10,000,000)$
Estimated Remaining Shared Infrastructure Costs to be Apportioned
among San Diego County NextGen RCS Parties 86,000,000$
Total Estimated NextGen Parties Subscriber Radio Count 13,953 6,163.55$ 308,177$
Remaining Costs to be Apportioned
Estimated Total Subscriber Radio Count
1. Agency X has an average of 50 radios for the two dates.
2. Total Estimated Cost of System divided by the Total Estimated Parties Subscriber Radio Count is $6,164
Exhibit C
x
3. Fifty (50) subscriber radios X $6,164 estimated cost = Estimated Agency Cost $308,177
To Calculate Your Agency's Estimated Cost Apportionment
1. Divide the Remaining Costs to be Apportioned by the Total Estimated NextGen Parties Subscriber Radio Count. Multiply this
number by the projected average number of your agency's subscriber radios for the two dates.
NextGen System Components - Shared Infrastructure
Estimated RCS NextGen System Cost
NextGen Shared Infrastructure Cost
Estimated Total Subscriber Radio Count
Estimated
Agency Cost for
Shared
Infrastructure
Estimated Cost
Two Year Average
Radio Count
Formula
Example
NextGen RCS Agreement December 3, 2013
San Diego County Party Name Radio Count
9/1/13
Radio Count
7/1/2014
Average
Radio Count
Estimated Cost for
San Diego Shared
Infrastructure
Alpine Fire Protection District 26
Bonita-Sunnyside Fire Protection District 16
Borrego Springs Fire Protection District 21
City of Carlsbad 436
City of Chula Vista 694
City of Coronado 182
City of Del Mar 97
City of El Cajon 460
City of Encinitas 246
City of Escondido 752
City of Imperial Beach 117
City of La Mesa 291
City of Lemon Grove 95
City of National City 284
City of Oceanside 744
City of Poway 296
City of San Marcos 419
City of Santee 176
City of Solana Beach 58
City of Vista 284
County of San Diego 5,848
Deer Springs Fire Protection District 21
Heartland Communications Facility JPA 12
Julian-Cuyamaca Fire Protection District 29
Lakeside Fire Protection District 98
Metropolitan Transit System 251
Mira Costa Community College District 20
North County Dispatch JPA 18
North County Fire Protection District 127
North County Transit District 33
Rancho Santa Fe Fire Protection District 92
San Diego Rural Fire Protection District 107
San Diego Unified Port District 299
San Miguel Consolidated Fire Protection District 135
Santee School District 44
State of CA Department of Transportation (Caltrans)893
State of California, CA Highway Patrol/El Cajon CHP 174
Valley Center Fire Protection District 25
Viejas Reservation Fire Department 33
Potential New Party
Potential New Party
Potential New Party
TOTAL 13,953 - -
Cost Apportionment for San Diego County Shared Infrastructure Per Party: Costs are apportioned in two categories--
infrastructure and core. Below are the estimated shared infrastructure apportionment costs per agency
Exhibit C-1
NextGen RCS Agreement December 3, 2013
San Diego County Parties & IVECA Radio Count
9/1/13
Radio Count
7/1/2014
Average
Radio Count
Estimated Cost for
RCS NextGen Core
Alpine Fire Protection District 26
Bonita-Sunnyside Fire Protection District 16
Borrego Springs Fire Protection District 21
City of Carlsbad 436
City of Chula Vista 694
City of Coronado 182
City of Del Mar 97
City of El Cajon 460
City of Encinitas 246
City of Escondido 752
City of Imperial Beach 117
City of La Mesa 291
City of Lemon Grove 95
City of National City 284
City of Oceanside 744
City of Poway 296
City of San Marcos 419
City of Santee 176
City of Solana Beach 58
City of Vista 284
County of San Diego 5,848
Deer Springs Fire Protection District 21
Heartland Communications Facility JPA 12
Julian-Cuyamaca Fire Protection District 29
Lakeside Fire Protection District 98
Metropolitan Transit System 251
Mira Costa Community College District 20
North County Dispatch, JPA 18
North County Fire Protection District 127
North County Transit District 33
Rancho Santa Fe Fire Protection District 92
San Diego Rural Fire Protection District 107
San Diego Unified Port District 299
San Miguel Consolidated Fire Protection District 135
Santee School District 44
State of CA Department of Transportation (Caltrans)893
State of California, CA Highway Patrol/El Cajon CHP 174
Valley Center Fire Protection District 25
Viejas Reservation Fire Department 33
IVECA*1,302
Potential New Party
Potential New Party
Potential New Party
TOTAL 15,255 - -
Cost Apportionment for RCS NextGen Core (Portion of the Shared Infrastructure Costs): Costs are apportioned in
two categories--infrastructure and core. Below are the estimated RCS NextGen Core apportionment costs per agency
for both San Diego County agencies and the Imperial Valley Emergency Communications Authority (IVECA).
Exhibit C-2
IVECA will pay for infrastructure for Imperial County (an estimated $9,000,000 ) and a portion of the NextGen core costs.
NextGen RCS Agreement December 3, 2013
San Diego County Parties & IVECA
Exhibit C-1
Estimated Cost for
San Diego Shared
Infrastructure
Exhibit C-2
Estimated Cost
for RCS NextGen
Core
Combined Estimated
Cost for San Diego
Shared Infrastructure
and NextGen RCS
Core (C-1 + C-2)
Alpine Fire Protection District
Bonita-Sunnyside Fire Protection District
Borrego Springs Fire Protection District
City of Carlsbad
City of Chula Vista
City of Coronado
City of Del Mar
City of El Cajon
City of Encinitas
City of Escondido
City of Imperial Beach
City of La Mesa
City of Lemon Grove
City of National City
City of Oceanside
City of Poway
City of San Marcos
City of Santee
City of Solana Beach
City of Vista
County of San Diego
Deer Springs Fire Protection District
Heartland Communications Facility JPA
Julian-Cuyamaca Fire Protection District
Lakeside Fire Protection District
Metropolitan Transit System
Mira Costa Community College District
North County Dispatch, JPA
North County Fire Protection District
North County Transit District
Rancho Santa Fe Fire Protection District
San Diego Rural Fire Protection District
San Diego Unified Port District
San Miguel Consolidated Fire Protection District
Santee School District
State of CA Department of Transportation (Caltrans)
State of California, CA Highway Patrol/El Cajon CHP
Valley Center Fire Protection District
Viejas Reservation Fire Department
IVECA*
Potential New Party
Potential New Party
Potential New Party
TOTALS
Cost Apportionment for the Combined Infrastructure and RCS NextGen Core: Costs are apportioned in two categories--
infrastructure and core. Below are both the estimated Combined Infrastructure and RCS Core apportionment costs per
agency.
Exhibit C-3
NextGen RCS Agreement December 3, 2013
Potential New Parties Radio Count
Sept 1, 2013
Radio Count
July 1, 2014
Average Radio
Count
Barona Fire Department 35
Cajon Valley Union School District 125
California Department of Corrections & Rehabilitation Division of Adult Parole Operations 109
California Department of Corrections & Rehabilitation Office of Correctional Safety 13
California State University San Marcos (Police)49
Grossmont Union High School District 128
Grossmont-Cuyamaca Community College 16
Jamul-Dulzura Unified School District 15
La Jolla Band of Luiseño Indians (La Jolla Tribal Police)4
Los Coyotes Police Department 6
Olivenhain Municipal Water District 3
Palomar College 41
Pala Band of Mission Indians 25
Pauma Band of Luiseño Mission Indians (Pauma Band of Mission Indians)21
Poway Unified School District 240
Ramona Water District Fire Department 21
Rancho Santa Fe Patrol 17
San Diego Association of Governments (SANDAG)59
San Diego County Regional Airport Authority 164
San Diego Humane Society 34
San Diego State University (Police & Parking)102
Southwestern College Police Dept.22
Sycuan Band of the Kumeyaay Nation (Sycuan Fire/Police Department)72
University of California San Diego (Police and Environment Health & Safety)108
Vista Unified High School District 188
Potential New RCS NextGen Parties
Exhibit D
signature Page to NextGen RCS Agreement
Name of Party: County of San Diego
Party Authorization and Acceptance
On December 3. 2013 (Date), Item or Agenda No. 6,
the San Dieao Countv Board of Supervisors
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Countv of San Dieoo
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Thomas J. Pastuszka
Cleri< of the Board of Supervisors
Signature of Authorized Party Official:
Date of Signature:
1^.1.
Approved as tqform and legality
Senior Deputy
Ail^riByad and/or authorized by ttw
epaMof Sgpeniprslof the Qounty of San Oleso.
l \^ Minute Order No.. ^ {Ue«lbigOate:J[.
By:iL
D^uty
Clei •
mm
ra^uperviiors
61435 PAGE 20
Signature Page to NextGen RGS Agreement
Name of Party:
AI ine Fire Protection District
ine Fire Protection District Board of Directors
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
A1pine Fire Protection District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Date), ltem or Agenda No. 8 ' 1 ,
the A1
on 01 /21 /2014
Patrick D Price Board Presid
of Governing Body)
of AuthorizedPafiName
Sþnaturé of Auth6rized Party Official:
r?/-.?o /q
Date of Signature:
Signature Page to NextGen RGS Agreement
Name Party:
Party Authorization and Acceptance
On 02/Il/2o14(Date), ltem orAgenda No.-7L,
the Board of Directors
Name of Governing Body)
Authorized the Undersígned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
Bonita-Sunnyside Fire Protection District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Signature of Authorized Party
Date of Signaturei
Signature Page to NextGen RGS Agreement
Name or Partv:
ßoRRE Go SÊR l¡J Ês F tRE c ^) 0rs
the fuRR,EÛû SPPI¡JpS FIRÊ P Ro¡ecr/ô^)DrcrRrcr EoaRD
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
ßoÊRFd¿SPR/^JrFs F tfli þþo rg cTtoÑ b srfl rr
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Tyæd Name and Title of Authorized Party Official:
toHÑ N. HAPô cASt-L€t FRe cHtEF
Signature of Authorized Par$ Offìcial
ft,^, d'-
Date of Signat
ølø¡
Signature Page to NextGen RCS Agreement
Nameof Party:
Party Authorization and Acceptance
On /-A/- _(Date), Item or Agenda No. ot.
the Cx^ CMUSM) eery COUUCIL^
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf ofthe
Name of Party)
As reflected In the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Signature of Authorized Party Official:
Date of Signature:
APPROVED AS TO FORM
O »OP CA/2-LS i^D
1
Signature Page to NextGen RGS Agreement
Name of Parly:
Cíty of Chu-le. Vísta
Attest:
o
Donna Norris ty Clerk
Approved as to form and legality
Partv Authorization and Acceptance
On March 11 , 201{Date), ltem or Agenda No. 9. Item/i 14-0r0r
the Chula Vista lit¡¿CounciI
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
Cítv of Chula Vísta
Name of Party)
As reflected in the attached Minute Order or s¡milar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Cheryl Cox
Mayor
Signature of Authorized Party Official:
Date of Sffiature
rfnl,+
ogíns City v
Signature Page to NextGen RCS Agreement
Name of
City of Coronado
åk 1lc. Authorization for the Citv Manager to Execute an Asreement with the County
of San Dieso for the Next Generati Resional Communications Svstem.Under Consent,
the City Council directed the City Manager to execute an agreement with the County of San
Diego for the Next Generation Regional Communications System.
P and nce
On peb. 4. 2014 (Date), ltem or Agenda No. IIc ,
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
As reflected in the attached Minute Ord or similar documentation of the action taken
of Coronado
Name of G overning Body)
Name Party
the Ci Council of the Ci
of Coronado
Typed Name and Title of Authorized Party Official
Blair King
City Manager
Signature of Authorized Party Official
Date of Signature:
z/* / t,/
Signature Page to NextGen RCS Agreement
Name of Party:
Cíty of De1 Mar
Authorization
on 02/03/2.014-(Date), ltem or Agenda No. 4 ,
the Del Mar Citv C í1
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Del Mar
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Scott lü. Ifuth
City Manager
Signature of Authorized Party Official:
Date of Sþnature:
03/0s/2014
Signature Page to NextGen RGS Agreement
Name
CITY OF EL CAJON
Partv and Acceptance
On _J,JJAJ_?ÃJA_(DaIe), ltem orAgenda No. -
4
J ,
the Citv Council
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of El Cajon
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken'
Typed Name and Title of Authorized Party Official:
Douglas l^Iilliford, CitY Manager
Signature of Authorized Party Official:
t--¿
Signature Page to NextGen RCS Agreement
Name of Party:
City of Encinitas
Party Authorization and Acceptance
Qn January 22,2014 (Date), ltem or Agenda No. 8D ,
the Encinitas Citv Council
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Encinitas
Name of Parg)
As reflected in the attached Minute Order or similar documentation of the action taken
Typed Name and Title of Authorized Parly Official
Gus Vina, City Manager
Signature of Authorized Party Otficial:
Date of Signature
t/n l,r
Signatuto Page to NertGen RGS Agreement
City of Escondido
On
the
2tfl2014 (Date), ltem orAçnda No. 25
City of Escondido
Ì,lama Govemlng
Authodzed the Underslgned
to Accept, Agree to and Execute This NextGen RCS Agreernent on behalf of the
Escondido City Council
Name of Party)
As refleded ln the attached Mlnute Order or slmilar documentatlon of the ac{ion taken.
iyped Name and Trtle of Authodzed Party Offrcial:
Sam Abed, Mayor
eatuá
Date of Signature:tu /f . 2atl
Signature Page to NextGen RCS Agreement
Name of Party:
City of Imperial Beach
Partv Authorization and Acceptance
On@tv t%_29l¿(Date), ltem orAgenda No. 5.1 ,
üs City Council of the City of Imperial Beach
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Imperial Beach
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Typed Name and Title of Authorized Pady Official
Andy Hall, City Manager
Signature of Authorized Party Official
Date of Signature:
February 5,2014
Signature Page to NextGen RGS Agreement
Name of Party:
l_'of La Mesa
Partv Authorization and Acceptance
On March 11 . 2014 (Date), ltem or Agenda No. 4 ,
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of La Mesa
As reflected in the attached Minute Order or similar documentation of the action taken
Resolution No. 2OII+-O2O
the i1T,a Mesa Citv Counc
Name of Party)
Typed Name and Title of Authorized Party Official: Arr Madrid, Mayor
l ,",r
Signature rized Party Official
Date of Sig
Signature Page to NextGen RGS Agreement
c,L e^un GnV¿_
Name of Party:
o
Authorization and Acceotance
on ol.-oq- tq (Date), ltem orAgenda ¡s. 5 ,
the
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Ct{.-l Ñ\*.**.^ 6.o d'4--
Name of Paþ¡
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Party Official:
SeçJo!^ /'¡A aToc--
Date of Signature
Ftb ,^-g ï r zo lt{
Signature Page to NextGen RGS Agreement
Name City of National- City
Partv Authorization and Acceotance
On
the
02118/14 (Date), ltem or lúér{údÍW Resol-qtion No. 2014-20
National City City Council
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of National City
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Official:
Mayor Morrison
rty Official:
Date of Signature:
Signature Page to NextGen RCS Agreement
Name of Party:
City of Poway
Party Authorization and Acceptance
gn February 18, 2014 (Date), ltem or Agenda f.fo. I , I , '\,
1¡" CitV of Poway City Council
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Poway
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Typed Name and Title of Authorized Party Official
Tina M. White
lnterim City Manager
Signature of Authorized Party Official
I
Date of Signature:
â, lq ,l t/
Approved as to Form
Dated:I
F Attorney
Attest
By:
By:
ì
ei R. Cobian,
City of Poway
City Cl
Slgnature Page to NextGen RGS Agreement
Name of Party: ClTy OF SAN MARCOS
On
the
1128114 .. (
Date), ttem orAgenda No.
CITY OF SAN MARCOS
Name of Governing Body)
Authorized the Undersígned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
CITY OF SAN MARCOS
Name of Party)
As reflected ín the attached Minute Order or similar documentation of the action taken
V
1t29t14
Signature Page to NextGen RGS Agreement
Name of Party: Ci ty" of Santee
Party Authorization and Acceptance
Name of Governing Body)
Authorized the Undersígned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Santee, Çalifornia
ute Order or similar documentation of the action taken
the Santee City Counci'l
on 2/26/L4 (Date), ltem orAgenda No. 68
Name of Party)
As rerfcted'
Ì'$."0".T 1fi$JU'¡
Typed Name and Title of Authorized Party Official:
Datc of
Approve dasto
By:
Ci ty rney
Signature Page to NextGen RGS Agreement
Name of City of Solana Beach
Party Authorization and Acceptance
Ongebruarv 12, 2or4(Date), ltem or Agenda No. 4.3 ,
the Solana Beach CiLy Council
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
City of Solana Beach
Name of Party)
As refleoted in the attached Minute Order or similar documentation of the action taken.
Name of Governing Body)
Typed Name and Title of Authorized Party Official:
David Ott
City
of
Date of Sìignature:
lIqfT,(ç
Signature Page to NextGen RGS Agreement
Name of Party: CITY OF VISTA
Party Authorlzatlon and Acceptance
On January 28,2014 (Date), ltem orAgenda No, CB ,
the City Council of the Chartered Citv of Vista
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
As reflected in the attached Minute Order or similar documentation of the action taken
of Vista
Name of Party
Typed Name and Title of Authorized Party Official:
Judy Ritter
Mayor
Signature of Authorized Party Official:
W, âK,âDt+
Date oYSignature:
Slgnetun Prgc to l,l¡¡ttGon RGS A3nomrnt
Name of Deer Springs Fire Protection District
Deer Springs Fire Protection District Board of Directors
Narne of Gowming Body)
Ar¡thorized he Undecigned
to Accept. Agree to and Execute Thls Ì,lextGen RCS Agreement on behalf of the
Deer Springs Fire Protection District
Name of Party)
As leflected in the attadred Minute Older or similar docwn€ntation of the action taken-
the
On 2t12t2014 (Date), ltem orAg€nda No,
Chris Amestoy, Fire Chiet
2t13t2014
Date
Signature Page to Ne¡<tGen RGS Agreement
Name
v\1.391D^-
CFA
of the action taken
the
r,?0
similarOrder
rV\
On \,Lø .I+
RCS
As
0^
No. ,
on behalf of the
Name of Party)
of Governing Body)
Date), ltem or
wrnrWñt
Authorized the Undersigned
to Accept, Agree to and Execute This
and Title
I
I
Party
Signature Page to NextGen RGS Agreement
Name of Partv:
rltPERrAr vALr.Ey COUMIINTCATI0NS AUIITORTTy (MCA)
Partv Authorization and Acceotance
on 02/27/2OI4 (Date), ltem orAgenda No. 3 ,
the MCA BOARI)
Name of Governing Body)
Authorized the Undercigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
IUPERTAL VALLEY EXTIERGENCY COff.II]NICATIONS AUITIORITY
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
TONY ROI]HOTAS JR., IVECA PRESIDENT
Typed Name and Title of Authorized Party Official:
1SignatureofAuthorizedPartyOfficial: V
03/13l14
Date of Signature:
Signature Page to NextGen RGS Agreement
Name of Party:
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
As reflected in the attached Minute Order or similar documentation of the action taken
rslçr$ í3o""d o{bìeclo
I
drq,
Date), ltem or Agenda No.onâl tBltL+
Cr,IrnA CA.t*5u\\\T Q-
Name of Body)
Name of Party)
Typed Name and Title of Authorized Party Official:
R..1. l44an;n.{l;
D',s4.;<f CL,.€
Signature of Authorized Party Official
al rt { r't
Date of
Signature Page to NextGen RGS Agreement
Nameof Party: Lakeside Fire Protection District
Party Authorization and Acceptance
On Feb 11 , 2 O@te), ltem or Agenda No. -9-B-,
the Lakeside Fire Go r¡ernìno Roarrl
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
Lakeside Fi re Proteetion Di s,f ri of
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Party Official:
Andy Parr, Fire Chief
Signature of Authorized
Date of Signature
Z- 2s -Lotc¡
rl
Signature Page to NextGen RGS Agreement
Name of Party:raGosta Community College
Partv Authorization and Acceptance
On January 22,2014 (Date), ltem or Agenda No. Vlll.A,
the MiraCosta Community College District Board of Trustees
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Charlie Ng, Vice President, Business a& Administrative Services
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Typed Name and Title of Authorized Party Official:
Charlie Ng, Vice President, Business & Administrative Services
Signature of Authorized Party Official
January 23,2014
Date re
Signature Page to NextGen RGS Agreement
Name of Party:
North County Dispatch Joint Powers Authority
Partv Authorization and Acceptance
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
North County Dispatch Joint Powers Authority
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
the North County Dispatch Joint Powers AuthoriW Board of Directors
On 0212712014 (Date), ltem or Agenda No. 7'C'
Typed Name and Title of Authorized Party Official:
Mark Packard
President, Board of Directors
Signature of Authorized Party Official:
Date of Signature:
February 27,2014
Signature Page to ilcxtGen RCS Agreement
Party:
North County Fire Protection District
Party Authorlzatlon and Accrptancr
Narne of Goveming Body)
A¡¡thorÞed the Undersigned
to Accept, Agree b and Execute This NextGen RCS Agreement on behalf of ttre
North County Fire Protection District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
On 02-24-2014
Board of Directors
Ilate), ltem or Agenda No. 10
Typed Name and TiUe of Authorized Party Offlclal:
William R. Metcalf, Fire Chief/CEO
Signature of Authorized Party Official:
February 25,2014
Signature Page to NextGen RCS Agreement
Name of Party: North County Transit District
Approved as to form and legallty lppmved and/or aurhortæd by $G
lo¡ldof D[rtnd tñr Nordr coürny Trenslt Dbrdct
I t;¡.id¡
l¡orth
a
Authorization and nce
On Januarv 16. 2014 (Date), ltem or Agenda No. 2,
the North Countv Transit District Board of Directors
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
As reflected in the attached Minute Order or similar documentation of the action taken.
North Countv Transit District
Name of Party)
Matthew O. Tucker
Executive Director, North County Transit District
Typed name and Title of Authorized Party Official:
1WàqL o
Signature of Authorized Party Official
Date of Signature:
L
Signature Page to NextGen RCS Agreement
Name of Party: Olivenhain Municipal Water District
Party Authorization and Acceptance
On January 15, 2014(Date), Item or Agenda No. 12,
the Board of Directors
name of Governing Body)
Authorized the Undersigned
to Accept,Agree to and Execute This NextGen RCS Agreement on behalf of the
Olivenhain Municipal Water District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Kimberly A.Thorner, General Manager
Signature of Aut rized Party Official:
Date of Sig ature:
Signature Page to NextGen RCS Agreement
Name of
POI4TAY UNIFIED SCHOOL DISTRICT
and
Unífíed School Distríct Board of Educatíon
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken-
Poway
2-t0-r4 (Date),ltem orAgenda No. E-311
Poway Unífíed School Distríct
On
the
Andy Patapow
Clerk of the Board of Education
OfficialNameandTitleof
P Unífíe
Date of
Signature Page to NextGen RGS Agreement
Nameof Party: Ramona Municipa1 water District
on 01/14/14 (Date), ltem or Agenda No. F.3 . ,
the Ramona Muni ci pal l¡la:Ler Di stri ct Board of Di rectors
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree toiand Execute This NextGen RGS Agreement on behalf of the
Ramona Municipal Water District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
Darrel I Beck,
President, Board of Directors Ràmona Municipal Water District
Signature of Authorized Party Official:
ev.f/14-.L¿
Date of Signature:
4 - Zo r 1
Signature Page to NextGen RCS Agreement
Name of PaÉy: RANCHO SANTA FE FIRE PROTECTION DISTRICT
Partv Authorization and Acceptance
RANCHO SANTA FE FIRE PROTECTION DISTRICT BOARD OF DIRECTORS
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
RANCHO SANTA FIRE FIRE PROTECTION DISTRICT
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Date), ltem or Agenda No. 5a
the
on 2-t2-20I4
Typed Name and Title of Authorized Party Official:
TONY J. MICHEL, FIRE CHIEF
RANCHO SANTA FE FIRE PROTECTION DISTRICT
Signature of Authorized P
Date of Signature
Z- l8-Z-Ð11
Signature Page to NextGen RGS Agreement
Name of Party:
Rancho Santa Fe Patrol
Partv Authorization and Acceotance
On 2 / 6 /201a (Date), ltem orAgenda No. 1 4 ,
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Rancho Santa Fe Patrol
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
the
Name of Governing Body)
Rancho Santa Fe Association
Typed Name and Title of Authorized Party Official:
Ivan Holl-er
Acting Secretary/tt'tanager
Slgnature of Authorized Party Official:
Date
t ,-/ r I
Signature Page to NextGen RCS Agreement
Name of Party
San Humane S and SPCA
g{y Authorization and Acceptance
On (Date), ltem or Agenda No. N/A
the N/A
Name of Governing Body)
Authorized the Undersigned
To Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
N/A
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Typed Name and Title of Authorized Parly Official
Dr. Gary Weitzman, DVM, MPH, CAWA
President / CEO
San Diego Humane Society and SPCA
5500 Gaines Sfreef
San California 92110
sig re of Authorized Party Official
fE
öf sio2|ture:I
March 25 201 4
Signature Page to NextGen RGS Agreement
Name Party:
San Diego Rural Fire Protection District
Authorization and
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
San Diego Rural Fire Protection District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
On
the ict Board ofDirectorsSanl-li e
1 krn Cl
i an fii cl-rPrrraIE'i ro Þrnl- ar.
Name of Governing Body)
Date), ltem or Agenda No.
Typed Name and Title of Authorized Party Official:
David Nissen, Fire Chief
Signature of Authorized Party Official
Date of Sþnatúre:
Signature Page to NextGen RCS Agreement
Name of Party:
San Diego Unified Port District
Party Authorization and Acceptance
On Feb 11, 2014 (Date), Item or Agenda No. 16 ,
tfie Board of Port Commissioners
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
San Diego Unified Port District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
John Bolduc
Vice President, Public Saftey/Chief of Harbor Police
Signature of Authorized Party Official:
Date of Signature:
61435 PAGE 21
Signature Page to NextGen RGS Agreement
Party Authorization and Acceptance
the San Pasqual Band of Mission Indians, Business Cornmittee
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
A11en E. Lawson, Chairman, San Pasqual Band of Mission Indians
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken
Date), ltem or Agenda No. One
Name of Governing Body)
On oi/?7 /itL
Typed Name and Title of Authorized fficial
A11en E. Lawson, Chaiornan San Pasqual Band of lt{ission fndians
Signature of Authorized fficial:
Date of
March 26, 20L4
Name of Party: San Pasqual Band of Mission rndians
Tilda M. Green ording Secretary
Signature Page to NextGen RCS Agreement
Name of Party: <-'
a.a)ôr"tn,r.J L
on and
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
S:*r 0r z.A,v ft¿n ô lÞ- îHz ll ct n ç1a
As reflected in the attached Minute Order or similar documentation of the actíon taken.
On
the I
c, "l
AI /Lt/+7'/ß'rvJ
Date), ltem or Agenda No
ing Body)(Name of
L- C i¡t, ru c-¿ L
Da'^r". \ 3-' Tu ¿k€ n, T' ì\o a\ ctaair '..'^' a'va
Typed Name and Title Party
Signature of Authorized Party Official:
Date of
Lot4Aa*^ ro
AP?ROVED BY LITAL DEPARI MENT
Signature Page to NextGen RCS Agreement
S
Calr&cn,.5o,.. bd^o(ô,mNa ofô Party:th.o+U n¡v¿rs.\
Party Authorization and Acceptance
the'$e R.*o-ey.los ."[ {d¿ $¡1ç¿6.f v of Cä[,Ç-u ".l(
Name oYGoverning Body) U
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
As reflected in the attached Minute Order or similar documentation of the action taken
Date), ltem or Agenda No. ,On
Co.I U
Name of P
Typed Name and Title of Authorized Party Official
B rSen [\r.\rg B,¡., ]E'
Signature of Authorized Party Official
Date of Sign
s,lr^ /r ort l
Signature Page to NextGen RGS Agreement
F Dr
Name of Party:
Partv Authorization and Acceotanc
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
on Yeh'l.n ;Zû\\(Date), ltem or Agenda *". äffiB"
tne VAu¡! An¿@'-høe Rø,.r=srrcr*: Drstt-c-r
V*ur-es C,e^¡'g- Frug fuorrcnouJ Ì)tø¡i+ror
Name of Governing Body)
Typed Name and Title of Authorized Party Official:
JoHrc ßfpsse. ÞáìÑc^O-r NUu.rrttnexroÊ-
Signature of Authorized Party Official:
0,2ltul
of
lln P-A-t+
Signature Page to NextGen RGS Agreement
Name of Pafi:
t A5 A I'lø ñDrA|.]3
Partv Authorization and Acceptance
fl
On (Date),
the ì
Name of ing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RCS Agreement on behalf of the
Name
As reflected in the attached Minute Order or similar documentation of the action taken.
Typed Name and Title of Authorized Party Official:
ÀtJ,tt,.r^..,R. ?ì îJ . Ch rtìr w\arr
Authofi zèd Party Official:
Date of Signature:
lrbtt^..I \?, CorT
Signature Page to NextGen RGS Agreement
Name of Party:
Vísta Unifíed School Dístrict
Party Authorization and Acceptance
Name of Governing Body)
Authorized the Undersigned
to Accept, Agree to and Execute This NextGen RGS Agreement on behalf of the
Vísta Unífíed School District
Name of Party)
As reflected in the attached Minute Order or similar documentation of the action taken.
Copy of Sígned Board Item
Typed Name and Title of Authorized Party Official:
Donna Caperton
Assístant Superintendent-
Business Services
Vísta Unified School Distríct
2/20/14 (Date), ltem or Agenda Jrle. 16 B ,On
the
Signature of Authorized Party Official:
4 /. L,L
Date of Signature: